Bug#941616: codelite: Should codelite be removed from Debian?
Source: codelite Version: 12.0+dfsg-1 Severity: normal I think it's time to remove the codelite package: * orphaned for more than 2.5 years with no expressions of interest in adoption * package is currently uninstallable (in unstable and probably testing too) and so RC buggy * has no reverse dependencies (according to dak rm) * there's a newer upstream version, but it's a rather complex package to update to a new upstream as a QA upload * a blocker for the current wxwidgets3.0-gtk3 transition, but upstream's changelog for 13.0 includes "Make CodeLite compile and run against GTK3" so updating to a new upstream seems likely to be required * upstream offer "unofficial" packages built for debian stretch and buster If there are no objections within two weeks, I'll turn this into an RM bug. Cheers, Olly
Bug#941623: RM: xenwatch -- RoQA; unmaintained, depends on libgtk-vnc-1.0-0
Package: ftp.debian.org X-Debbugs-Cc: xenwa...@packages.debian.org Please remove xenwatch from Debian. xenwatch was orphaned a decade ago and hasn't had an upstream release since then. It is currently blocking the upload of gtk-vnc 1.0.0 because the new version of gtk-vnc drops the old gtk2 bindings (libgtk-vnc-1.0-0). xenwatch is the only package in Debian to depend on the gtk2 library. I've never used xenwatch, but I believe there are alternative maintained apps in Debian like virt-manager, virt-viewer, and gnome-boxes. Orphan bug: https://bugs.debian.org/540593 https://gitlab.gnome.org/GNOME/gtk-vnc/blob/master/NEWS Thanks, Jeremy Bicha
Bug#941623: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: xenwatch |0.5.4-4 | source xenwatch | 0.5.4-4+b1 | amd64, i386 --- Reason --- RoQA; unmaintained, depends on libgtk-vnc-1.0-0 -- 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 941...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/941623 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)
Bug#941623: Removed package(s) from unstable
Version: 0.5.4-4+rm Dear submitter, as the package xenwatch has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/941623 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. 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)
