[aur-general] Duplicate Package Removal and Disown Request
hashcat-bin [1] is very out-of-date and no longer serves a purpose as far as I can tell. Upstream packages the GUI separately, so the default package is the binary only anyway. Thus, the naming of the package is redundant, it doesn't follow the naming convention upstream and the sources it uses no longer exist. It should be removed in favor of hashcat [2]. However, the maintainer of hashcat appears to not be active (last update in AUR: 2012-09-28, last update upstream: 2013-03-22). I would be more than happy to take over the package's maintainence if it would first be disowned. All the best, -Sam 1. https://aur.archlinux.org/packages/hashcat-bin/ 2. https://aur.archlinux.org/packages/hashcat/
On 2013-04-07 16:57, Sam Stuewe wrote:
hashcat-bin [1] is very out-of-date and no longer serves a purpose as far as I can tell. Upstream packages the GUI separately, so the default package is the binary only anyway. Thus, the naming of the package is redundant, it doesn't follow the naming convention upstream and the sources it uses no longer exist.
It should be removed in favor of hashcat [2]. However, the maintainer of hashcat appears to not be active (last update in AUR: 2012-09-28, last update upstream: 2013-03-22). I would be more than happy to take over the package's maintainence if it would first be disowned.
All the best,
-Sam
1. https://aur.archlinux.org/packages/hashcat-bin/ 2. https://aur.archlinux.org/packages/hashcat/
Correction: hashcat-bin's sources do exist, but they probably shouldn't be distributed over the AUR anyway, and the PKGBUILD fails to note the correct makedepends. All the best, -Sam
On Sun, Apr 7, 2013 at 5:03 PM, Sam Stuewe <halosghost@archlinux.info>wrote:
On 2013-04-07 16:57, Sam Stuewe wrote:
hashcat-bin [1] is very out-of-date and no longer serves a purpose as far as I can tell. Upstream packages the GUI separately, so the default package is the binary only anyway. Thus, the naming of the package is redundant, it doesn't follow the naming convention upstream and the sources it uses no longer exist.
It should be removed in favor of hashcat [2]. However, the maintainer of hashcat appears to not be active (last update in AUR: 2012-09-28, last update upstream: 2013-03-22). I would be more than happy to take over the package's maintainence if it would first be disowned.
All the best,
-Sam
1. https://aur.archlinux.org/**packages/hashcat-bin/<https://aur.archlinux.org/packages/hashcat-bin/> 2. https://aur.archlinux.org/**packages/hashcat/<https://aur.archlinux.org/packages/hashcat/>
Correction: hashcat-bin's sources do exist, but they probably shouldn't be distributed over the AUR anyway, and the PKGBUILD fails to note the correct makedepends.
All the best,
-Sam
Deleted hashcat-bin, thx. -- Maxime
On 2013-04-07 23:15, Maxime GAUDUIN wrote:
Deleted hashcat-bin, thx.
Anytime. Given the several month long break between updates for hashcat, will the package be disowned? I have an updated and overhauled package ready to be uploaded. As I mentioned, it has been several months since the maintainer has pushed an update for the package. All the best, -Sam
On Apr 7, 2013 11:47 PM, "Sam Stuewe" <halosghost@archlinux.info> wrote:
On 2013-04-07 23:15, Maxime GAUDUIN wrote:
Deleted hashcat-bin, thx.
Anytime. Given the several month long break between updates for hashcat,
will the package be disowned? I have an updated and overhauled package ready to be uploaded. As I mentioned, it has been several months since the maintainer has pushed an update for the package.
All the best,
-Sam
I understand, still the protocol requires you to send an email to the current maintainer. Only after 2 weeks without an answer can I disown it for you. Ping me again when it's done :) Cheers. -- Maxime
On 2013-04-07 23:56, Maxime GAUDUIN wrote:
I understand, still the protocol requires you to send an email to the current maintainer. Only after 2 weeks without an answer can I disown it for you. Ping me again when it's done :) Ahh, I had forgotten that was still the case with such a long delay. Evenso, I sent the maintainer an email earlier today. I'll let you know if he doesn't get back to me in a couple of weeks. Thank you again for your help.
All the best, -Sam
On 2013-04-08 00:10, Sam Stuewe wrote:
I sent the maintainer an email earlier today. I'll let you know if he doesn't get back to me in a couple of weeks.
I just got a message from the domain postmaster that the email account is no longer valid. Given that there is now no way to contact the maintainer (as far as I can find), would you please disown hashcat? Thank you. All the best, -Sam
On Fri, Apr 12, 2013 at 4:25 PM, Sam Stuewe <halosghost@archlinux.info>wrote:
On 2013-04-08 00:10, Sam Stuewe wrote:
I sent the maintainer an email earlier today. I'll let you know if he doesn't get back to me in a couple of weeks.
I just got a message from the domain postmaster that the email account is no longer valid. Given that there is now no way to contact the maintainer (as far as I can find), would you please disown hashcat? Thank you.
All the best,
-Sam
Disowned, go ahead and grab it. Cheers. -- Maxime
On 2013-04-12 17:49, Maxime GAUDUIN wrote:
On Fri, Apr 12, 2013 at 4:25 PM, Sam Stuewe <halosghost@archlinux.info>wrote:
On 2013-04-08 00:10, Sam Stuewe wrote:
I sent the maintainer an email earlier today. I'll let you know if he doesn't get back to me in a couple of weeks.
I just got a message from the domain postmaster that the email account is no longer valid. Given that there is now no way to contact the maintainer (as far as I can find), would you please disown hashcat? Thank you.
All the best,
-Sam
Disowned, go ahead and grab it.
Cheers.
Awesome, thank you. Adopted, and updated. All the best, -Sam
participants (2)
-
Maxime GAUDUIN
-
Sam Stuewe