On Mon, May 30, 2022 at 03:55:48PM +0530, Abhijith PA wrote:
> I own this package. Last upload was done by Jeremy Bicha as their 
> Ubuntu release was due that even without notifying me prior. Now I can 
> see there is also another QA upload.

An ITA really doesn't lock a package forever.  You have been claiming
this ITA since 1½ years (January 2022), but you only done one upload to
stretch-security (which was under a NMU according to the changelog).

Then you closed this ITA/O with a version that doesn't actually change
Maintainer but only does another QA upload (the one fro jbicha that you
mention): such upload really doesn't conclude the adoption process, but
in fact leaves it in an inconsistent state, so I really don't understand
why would even do that.


Effectively as long as you don't upload this package to unstable with a
changed Maintainer field you really don't "own" anything.  ITAs are
supposed to be used for coordinating and preventing two people to adopt
the same package, but I really don't think it's fair to say you "own"
the package for years without ever uploading it just because of the
metadata of a bug and with that preventing a QA upload.
https://www.debian.org/devel/wnpp/#howto-o


All that said as a preamble, I reopened the bug because this package came
up in a list of packages with inconsistent metadata ("orphaned without
associated O bug"), that's how I found it this morning.


-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
More about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature

Reply via email to