I don't have time working on this program, so I ask for a adopter.
Hello, I see that in latest upload[1] of spice-vdagent in unstable you have changed maintainer to Debian QA. If this is the case, shouldn't we close 911430[2]. Or is it still up for adoption ?
The Debian QA group is the maintainer of all packages that are up for adoption: https://www.debian.org/doc/manuals/developers-reference/pkgs.html#orphaning cu Adrian
retitle 911430 ITA: spice-vdagent -- spice agent for linux I would like to update this package. I personally use spice-vdagent and recently made a security upload to stretch of the same.
Hallo, ich bin Frau Elizabeth Liu, wenn Sie als vor der Covid-19-Epidemie geschützt markiert wurden, meine Gebete mit Ihnen. Ich möchte Ihnen ein Geschäft im Wert von $7,400,000.00 USD anbieten. Wenn Sie interessiert sind, kontaktieren Sie mich privat. E-Mail: elizabethliu@winghangbnk.com Elizabeth Liu
version: 0.22.1-1 New upload done on 2022-02-24.
retitle 911430 ITA: spice-vdagent -- spice agent for linux thanks 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.
I could argue atleast some activity was happening in repo. https://salsa.debian.org/debian/spice-vdagent/-/commits/master I *adopted this package. Sorry if "own" is a strong word. Now, have I stopped anyone from uploading. No. Like you said its about coordination. I could've changed the maintainer field and closed this bug in changelog if I was notified prior to uploading. I manually closed this as I don't want ITA to be in pending state for long time. In evening I saw a closed bug reopened and re-titled to Orphan. So I gave my explanation.
Right, which is exactly what was uploaded? We have a problem within Debian in general of many maintainers piling up changes in git but never uploading it; in some teams (like the Perl team, where uploads pretty much only happen when there is a new upstream release) is quite worse than others.. Right. If you plan to keep working on adopting it, by all means please do retitle it to ITA as see fit. Just that until you actually "complete" the adoption people might come around and "touch" it every so often. My assumption when I saw it closed after 1+ year of silence was that you weren't interested in it anymore... :)
We believe that the bug you reported is fixed in the latest version of spice-vdagent, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 911430@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jelmer Vernooij <jelmer@debian.org> (supplier of updated spice-vdagent package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) Format: 1.8 Date: Tue, 31 May 2022 20:33:55 +0100 Source: spice-vdagent Architecture: source Version: 0.22.1-3 Distribution: unstable Urgency: medium Maintainer: Abhijith PA <abhijith@debian.org> Changed-By: Jelmer Vernooij <jelmer@debian.org> Closes: 911430 Changes: spice-vdagent (0.22.1-3) unstable; urgency=medium . [ Abhijith PA ] * New maintainer (Closes: #911430) Checksums-Sha1: f2f0bfe504ea28ceb09640c53e6304b3fcb77430 2192 spice-vdagent_0.22.1-3.dsc 4f686daeace7f40bfeba410735cb85f55854bf48 15188 spice-vdagent_0.22.1-3.debian.tar.xz 0d1e5e4440f9a0aaa9f48f9d77809dceaaf3ea22 14273 spice-vdagent_0.22.1-3_amd64.buildinfo Checksums-Sha256: 88dbbc01ae1a87daca9e3d731293941cc43af201050b3dff1273098f6ab9bb50 2192 spice-vdagent_0.22.1-3.dsc 3194ce0e98ae53ac2a8ec3ad0507c621c818121be5a6b02d01ba38de2e4ee43b 15188 spice-vdagent_0.22.1-3.debian.tar.xz f5d4771d31fdd592a66aaae54e655e1c464327881a1771a5c0b6b9c5caeab8ef 14273 spice-vdagent_0.22.1-3_amd64.buildinfo Files: 49dd4c7fde13e7e0f0e6693343f5d5fc 2192 x11 optional spice-vdagent_0.22.1-3.dsc 83c541db90e36b340f4fe1e457b2340c 15188 x11 optional spice-vdagent_0.22.1-3.debian.tar.xz fbb71c5d4c645352beb839971ef04f34 14273 x11 optional spice-vdagent_0.22.1-3_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAmKWbecACgkQV5wWDUye I+gRExAApUSv6zdC5V+Qp0e3y90qvO2WcFkzCtV6yvwo2Y9NN80MY5n31Xin5B/V jkwPygPXswgEBWofklDETaha5GZxmplp2Fv3XShSjZqhHNfVhKDCKuC+zGU6Qa+v Qkpu08yF2xXkPUUd6LljZ/SNPiFlkKdsmHdkHJSHrThgDGInG1Swf2QBhKskvi+9 +RYDg2iLJabJLgrv5iHQ2xcIgUFl/3ai9BHTw9fjVI8l44wBim6KyDsmOmpdVcs7 IXvJ9batwPBuULWw/yWNAwbOIgSyO7Wodd23Lr+yFV7yZ7iv8hs2AP4ZRO0EN/5u 4YpBRdqNUwVbCmMC+NmHgl4DmqGQpSHVyv+SMndzd/xV6AtVrjie0q2wwMPiilrT hS8JcdyKgbRbrZqYv1sgCcRF4W3wqjAIYpdL5ibQ10aiaSrTfkRr77+47FntlcD3 Uz8o9Aj3Su2s7bQDFHKVsswUyOXSOlYMo16JzDo2iG1crv/GUd2eFAWwH0ymdPFi tToI/g753xI9R4inFwS1S5iGj997pwAe7GIxOq9VFhQ3cTcp3WHyhkIRkZBYyo55 sct4LdtOGLn36o2Rjs5L2K394/3c9TRdznZETjI47lEUq4U5wpikjaib0hoQydZx hC76X/CAtwUTLFqfFBoMuxzqyRfl+DlJsoiNtFX0arlXokMnBKo= =RyxJ -----END PGP SIGNATURE-----