Moritz, I didn't upload new releases simply because there were none, and there were none simply because the required upgrade - to gtk 3 and gobject introspection - has so far not been completed. There was already a bug¹ tracking that problem.
This was not an abandoned package, I was fully aware it had this problematic dependency on pygtk, that it would eventually be removed from unstable if the problem was not solved, and I was in contact with upstream to understand if an upgrade plan was feasible. I would have expected someone to try to contact me/the upstream developer - respectively - before declaring it "dead upstream" and "unmaintained" and removing it in 1 day. (Then, what I don't understand is why I didn't receive any email yesterday when this bug was opened. Had the package already been reassigned?!) Thanks for any clarification. I certainly won't claim I'm a model maintainer, but I would like to better understand in what conditions packages with open problems can disappear all of a sudden without the maintainer being informed. Pietro Battiston ¹ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885470 Il giorno lun, 04/11/2019 alle 07.45 +0000, Debian FTP Masters ha scritto: > We believe that the bug you reported is now fixed; the following > package(s) have been removed from unstable: > > python-sqlkit | 0.9.6.1-2 | all > python-sqlkit-doc | 0.9.6.1-2 | all > sqlkit | 0.9.6.1-2 | source > > ------------------- Reason ------------------- > RoQA; Dead upstream, unmaintained, depends on legacy libs > ---------------------------------------------- > > Note that the package(s) have simply been removed from the tag > database and may (or may not) still be in the pool; this is not a > bug. > The package(s) will be physically removed automatically when no suite > references them (and in the case of source, when no binary references > it). Please also remember that the changes have been done on the > master archive and will not propagate to any mirrors until the next > dinstall run at the earliest. > > Packages are usually not removed from testing by hand. Testing tracks > unstable and will automatically remove packages which were removed > from unstable when removing them from testing causes no dependency > problems. The release team can force a removal from testing if it is > really needed, please contact them if this should be the case. > > We try to close bugs which have been reported against this package > automatically. But please check all old bugs, if they were closed > correctly or should have been re-assigned to another package. > > Thank you for reporting the bug, which will now be closed. If you > have further comments please address them to 944...@bugs.debian.org. > > The full log for this bug can be viewed at > https://bugs.debian.org/944082 > > This message was generated automatically; if you believe that there > is > a problem with it please contact the archive administrators by > mailing > ftpmas...@ftp-master.debian.org. > > Debian distribution maintenance software > pp. > Scott Kitterman (the ftpmaster behind the curtain)
