[aur-general] Orphaning request - chromium-beta and clamav-devel
lists at baums-on-web.de
Thu Sep 23 17:07:13 EDT 2010
Am Thu, 23 Sep 2010 15:30:22 -0500
schrieb Brad Fanella <bradfanella at archlinux.us>:
> Please. There is obviously some sort of miscommunication between you
> two, so arguing is redundant.
There's no miscommunication at least not on my side.
> Now, to clarify: Bumping a package everytime there is a version is the
> *definition* of maintaining a package.
Of course this is the definition of maintaining a package. But this
doesn't have to be done within 2 or 3 hours after upstream has released
a new version. And an orphan request shouldn't be sent 2 or 3 hours
after upstream has released the new version.
And one (in this case Det) should decide if one wants to maintain the
package or not. That is, one shouldn't adopt a package, update it,
orphan it, wait until the package is adopted by someone else, and then
send an orphan request to the mailing list, because the new maintainer
of a package which oneself doesn't use doesn't update it within 2 or 3
These are the issues I have with Det.
Btw., it also happens every now and then that it takes some weeks until
a package in [core] and [extra] is updated even if it's flagged as
out-of-date. And there's no problem with that.
More information about the aur-general