[aur-general] [AUR4] Unsure whether to adopt, wait for maintainer to re-upload, and/or merge packages
These were the original uploaded PKGBUILDs, still referencing to a stale source: 1. https://aur4.archlinux.org/packages/mse-mtg/ 2. https://aur4.archlinux.org/packages/mse-mtg-phyrexian/ These were the uploads with the new content re-hosting, but the maintainer hasn't contacted me back about wanting to maintain the other MtG templates that're floating around (there's a few more): 1. https://aur4.archlinux.org/packages/magicseteditor-mtg/ 2. https://aur4.archlinux.org/packages/magicseteditor-mtg-base/ I was planning to wait until August to make a decision, but, like the title says, I'm not sure whether I should just submit updated packages on the AUR4 that point to the same sources as magicseteditor-mtg, wait for elegua to re-upload the packages for magicseteditor-mtg*, or upload the second set of links and add elegua as a contributor to make sure he still has write rights. I originally orphaned the first two links because I was thinking that elegua might be interested in merging it into the packages he uploaded so there aren't duplicate packages floating around.
AFAIK time was given to allocate the packages to authors. I think it's OK
to proceed.
On Tue, Jul 14, 2015, 17:26 ShadowKyogre
These were the original uploaded PKGBUILDs, still referencing to a stale source: 1. https://aur4.archlinux.org/packages/mse-mtg/ 2. https://aur4.archlinux.org/packages/mse-mtg-phyrexian/
These were the uploads with the new content re-hosting, but the maintainer hasn't contacted me back about wanting to maintain the other MtG templates that're floating around (there's a few more): 1. https://aur4.archlinux.org/packages/magicseteditor-mtg/ 2. https://aur4.archlinux.org/packages/magicseteditor-mtg-base/
I was planning to wait until August to make a decision, but, like the title says, I'm not sure whether I should just submit updated packages on the AUR4 that point to the same sources as magicseteditor-mtg, wait for elegua to re-upload the packages for magicseteditor-mtg*, or upload the second set of links and add elegua as a contributor to make sure he still has write rights. I originally orphaned the first two links because I was thinking that elegua might be interested in merging it into the packages he uploaded so there aren't duplicate packages floating around.
Em 14-07-2015 12:26, ShadowKyogre escreveu:
I was planning to wait until August to make a decision, but, like the title says, I'm not sure whether I should just submit updated packages on the AUR4 that point to the same sources as magicseteditor-mtg, wait for elegua to re-upload the packages for magicseteditor-mtg*, or upload the second set of links and add elegua as a contributor to make sure he still has write rights. I originally orphaned the first two links because I was thinking that elegua might be interested in merging it into the packages he uploaded so there aren't duplicate packages floating around. I was faced with same decision yesterday. The original submitter of the tinyssh package didn't migrated to AUR4. I've contacted him by e-mail and he not only updated the packaged, as he made me his co-maintainer. I know people had warnings and all, but it wont hurt to be polite and ask.
Cheers, Giancarlo Razzolini
On 07/14/2015 09:26 AM, Giancarlo Razzolini wrote:
I was planning to wait until August to make a decision, but, like the title says, I'm not sure whether I should just submit updated packages on the AUR4 that point to the same sources as magicseteditor-mtg, wait for elegua to re-upload the packages for magicseteditor-mtg*, or upload the second set of links and add elegua as a contributor to make sure he still has write rights. I originally orphaned the first two links because I was thinking that elegua might be interested in merging it into the packages he uploaded so there aren't duplicate packages floating around. I was faced with same decision yesterday. The original submitter of
Em 14-07-2015 12:26, ShadowKyogre escreveu: the tinyssh package didn't migrated to AUR4. I've contacted him by e-mail and he not only updated the packaged, as he made me his co-maintainer. I know people had warnings and all, but it wont hurt to be polite and ask.
Cheers, Giancarlo Razzolini Decided to email the submitter yesterday. Should I wait for a response for about a week?
- ShadowKyogre
Decided to email the submitter yesterday. Should I wait for a response for about a week? I don't think there are any hard rules on that. I mailed him on a Friday. If I didn't got a response, by Monday I'd took over the package. Truth be told, they had 2 months, at least, to be aware and do something. I think this was just a courtesy, but in my case the
Em 15-07-2015 13:45, ShadowKyogre escreveu: maintainer did answered me. In yours it might do down differently. Cheers, Giancarlo Razzolini
On 07/17/2015 02:34 PM, Giancarlo Razzolini wrote:
Decided to email the submitter yesterday. Should I wait for a response for about a week? I don't think there are any hard rules on that. I mailed him on a Friday. If I didn't got a response, by Monday I'd took over the
Em 15-07-2015 13:45, ShadowKyogre escreveu: package. Truth be told, they had 2 months, at least, to be aware and do something. I think this was just a courtesy, but in my case the maintainer did answered me. In yours it might do down differently.
Cheers, Giancarlo Razzolini I re-uploaded the relevant PKGBUILD to the AUR4 at https://aur4.archlinux.org/packages/mse-mtg/ (I still need to adjust the descriptions and dependencies, but everything is split properly).
With the packages that're still here, https://aur4.archlinux.org/packages/magicseteditor-mtg/, should I file merge and/or deletion requests? - ShadowKyogre
participants (3)
-
Giancarlo Razzolini
-
Javier Domingo Cansino
-
ShadowKyogre