Bug#709942: RM: gir1.2-libgsf-1
On Mon, 2013-05-27 at 11:42 +1000, Dmitry Smirnov wrote: On Mon, 27 May 2013 11:22:05 Dmitry Smirnov wrote: It's the first time I'm experiencing such issue so I'm not sure what's best to do. Apparently libgsf-gnome-1-dev was dropped earlier as well as libgsf-gnome-1-114. Perhaps they also could be removed. How shall I get outdated binaries fixed? Please advise... As far as I understand the policy [1] I need to declare Conflicts: obsolete-package Replaces: obsolete-package Only if they share files. Would that be enough to drop obsolete packages? No. You need to make sure they have no reverse-dependencies and then either ask ftp-master to remove them (via a bug such as this) or wait for that to happen semi-automagically. See http://wiki.debian.org/ftpmaster_Removals The current version of the cruft report mentioned there contains: - broken Build-Depends: planner: libgsf-gnome-1-dev So that would need resolving first. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709942: RM: gir1.2-libgsf-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove package gir1.2-libgsf-1 from testing. As per #695599 this package was renamed in unstable: gir1.2-libgsf-1 -- gir1.2-gsf-1 but libgsf can't migrate to testing because of (missing 1 binary: gir1.2-libgsf-1) What's the best practice to handle such situation? Please advise if libgsf migration can be ensured without removal of gir1.2-libgsf-1. Thank you. Cheers, Dmitry Smirnov GPG key : 4096R/53968D1B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709942: RM: gir1.2-libgsf-1
Control: reassign -1 ftp.debian.org On Mon, 2013-05-27 at 08:33 +1000, Dmitry Smirnov wrote: Please remove package gir1.2-libgsf-1 from testing. We can't. Partly because only source packages get removed from testing, not single binary packages, and partly because the package you named doesn't exist in testing to begin with. As per #695599 this package was renamed in unstable: gir1.2-libgsf-1 -- gir1.2-gsf-1 but libgsf can't migrate to testing because of (missing 1 binary: gir1.2-libgsf-1) It needs removing from unstable, not from testing; reassigning. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709942: RM: gir1.2-libgsf-1
On Mon, 2013-05-27 at 01:17 +0100, Adam D. Barratt wrote: On Mon, 2013-05-27 at 08:33 +1000, Dmitry Smirnov wrote: but libgsf can't migrate to testing because of (missing 1 binary: gir1.2-libgsf-1) There are more issues: $ grep-excuses libgsf libgsf (1.14.21-2.1 to 1.14.26-1) Maintainer: J.H.M. Dassen (Ray) 83 days old (needed 5 days) out of date on i386: gir1.2-libgsf-1 (from 1.14.25-1); libgsf-gnome-1-114, libgsf-gnome-1-114-dbg, libgsf-gnome-1-dev (from 1.14.21-2.1) [and so on for each architecture] You need to get all of the outdated binaries fixed, not just the ones that got most recently dropped. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709942: RM: gir1.2-libgsf-1
Hi Adam, On Mon, 27 May 2013 10:34:32 Adam D. Barratt wrote: On Mon, 2013-05-27 at 01:17 +0100, Adam D. Barratt wrote: On Mon, 2013-05-27 at 08:33 +1000, Dmitry Smirnov wrote: but libgsf can't migrate to testing because of (missing 1 binary: gir1.2-libgsf-1) There are more issues: $ grep-excuses libgsf libgsf (1.14.21-2.1 to 1.14.26-1) Maintainer: J.H.M. Dassen (Ray) 83 days old (needed 5 days) out of date on i386: gir1.2-libgsf-1 (from 1.14.25-1); libgsf-gnome-1-114, libgsf-gnome-1-114-dbg, libgsf-gnome-1-dev (from 1.14.21-2.1) [and so on for each architecture] You need to get all of the outdated binaries fixed, not just the ones that got most recently dropped. It's the first time I'm experiencing such issue so I'm not sure what's best to do. Apparently libgsf-gnome-1-dev was dropped earlier as well as libgsf-gnome-1-114. Perhaps they also could be removed. How shall I get outdated binaries fixed? Please advise... Thank you. Regards, Dmitry Smirnov. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709942: RM: gir1.2-libgsf-1
On Mon, 27 May 2013 11:22:05 Dmitry Smirnov wrote: It's the first time I'm experiencing such issue so I'm not sure what's best to do. Apparently libgsf-gnome-1-dev was dropped earlier as well as libgsf-gnome-1-114. Perhaps they also could be removed. How shall I get outdated binaries fixed? Please advise... As far as I understand the policy [1] I need to declare Conflicts: obsolete-package Replaces: obsolete-package Would that be enough to drop obsolete packages? Thanks. [1]: http://www.debian.org/doc/debian-policy/ch-relationships.html#s7.6.2 Regards, Dmitry Smirnov GPG key : 4096R/53968D1B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
