On Sat, Aug 05, 2017 at 02:15:16PM +0500, Andrey Rahmatullin wrote:
>...
> Besides, while it doesn't imply you shouldn't make an upload that only
> changes the maintainer (unlike 5.9.5. Adopting a package), I think it's
> the usual practice to not make such upload.
For people who are orphaning
On Sat, Aug 05, 2017 at 11:01:41AM +0200, Bill Allombert wrote:
> > > Nowadays orphaning is done by reuploading the package with the
> > > maintainer set to the QA group rather than using a O: wnpp bug.
> > Huh?
>
> See:
>
On Sat, Aug 05, 2017 at 01:55:01AM +0500, Andrey Rahmatullin wrote:
> On Fri, Aug 04, 2017 at 10:46:19PM +0200, Bill Allombert wrote:
> > On Fri, Aug 04, 2017 at 11:59:40AM -0700, Don Armstrong wrote:
> > > > An O: bug means that it is confirmed that the package is orphaned, and
> > > > gives
On Fri, Aug 04, 2017 at 10:46:19PM +0200, Bill Allombert wrote:
> On Fri, Aug 04, 2017 at 11:59:40AM -0700, Don Armstrong wrote:
> > > An O: bug means that it is confirmed that the package is orphaned, and
> > > gives permission to everyone to adopt the package immediately.
> >
> > So just file
On Fri, 04 Aug 2017, Adrian Bunk wrote:
> Regressing on being able to orphan all packages of a known-MIA/retired
> maintainer would be very bad.
>
> Think of it as a 3 step process:
[...]
> 3. for every package where the maintainer is in Maintainer or Uploaders
>the MIA team either orphans
5 matches
Mail list logo