[RFH] libxmlezout : out of date on many archs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have uploaded one of the packages I maintain and in the PTS [1] I have many out of date on i386 and so on messages. It seems that was the reason why the previous version (1.01.1-4) didn't reach testing. Since I don't understand this problem, I don't know how can I solve it. Any help, advices, url welcome, Thanks in advance, xavier [1] http://packages.qa.debian.org/libx/libxmlezout.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk65OA8ACgkQVIZi0A5BZF5qswCeKfGVDaZtGRmr6gp8VXsoA/ZJ 7A8AnikqPjsXRO/gabVBRW4dr8g0XM71 =70Th -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4eb93810.7000...@ipno.in2p3.fr
Re: [RFH] libxmlezout : out of date on many archs
Hi! Am 08.11.2011 15:09, schrieb Xavier Grave: I have uploaded one of the packages I maintain and in the PTS [1] I have many out of date on i386 and so on messages. It seems that was the reason why the previous version (1.01.1-4) didn't reach testing. Since I don't understand this problem, I don't know how can I solve it. Any help, advices, url welcome, Thanks in advance, xavier [1] http://packages.qa.debian.org/libx/libxmlezout.html Ha, that's a tricky one. First guess would have been: Not yet build on all archs, however looking at [1] (also linked from the qa site) show's all archs (but hurd) are build successfully and in the archive. So look again at the qa page: It says out of date on i386: libxmlezout0, libxmlezout1-dev (from 1.06-2). It seems you recently droped these two packages. They are still in wheezy and used there, so your package can't migrate without the old packages being removed. That's job of the ftp-team, and usually you don't have to care about that, as the ftp-team get's notified about this cruft, and tries to remove it. See [2] for the current Cruft report which also mentiones your package. As said: Normally the ftp-team does that for you, and you don't have to do anything special. However, in this case the ftp-team could do anything about it. When trying to remove your old package, one sees the following (AFAIK you could try that out on ries.debian.org, if you are an DD, if not apt-cache rdepends might help you): Checking reverse dependencies... # Broken Depends: liblog4ada: liblog4ada1-dev narval: libnarval-dbg [amd64 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc s390 sparc] libnarval1-dev [amd64 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc s390 sparc] libnarval1.10.1 [amd64 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc s390 sparc] narval-generic-actors [amd64 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc s390 sparc] narval-servers [amd64 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc s390 sparc] narval-tests-actors [amd64 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc s390 sparc] # Broken Build-Depends: liblog4ada: libxmlezout1-dev narval: libxmlezout1-dev So, your package can't be removed, because that would break other packages. Brolen Depends can usually be solved by requesting binary NMUs (binNMUs). AFAIK that's easiest done with bug against the release.debian.org apckage. Broken Build-Depends usually means that you have to tell the maintainers of these packages to fix their packages. Once they are uploaded, the old package may be removed, and may migrate to testing. Also note that you don't have to request binNMUs, if the package needs a sourceful upload anyway. 1: https://buildd.debian.org/status/package.php?p=libxmlezout 2: http://ftp-master.debian.org/cruft-report-daily.txt Best regards, Alexander -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4eb9437a.1050...@debian.org
Re: [RFH] libxmlezout : out of date on many archs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 08/11/2011 15:58, Alexander Reichle-Schmehl a écrit : Hi! snip Ha, that's a tricky one. Fixing it with your help will make me learn more about Debian internals, thanks ! First guess would have been: Not yet build on all archs, however looking at [1] (also linked from the qa site) show's all archs (but hurd) are build successfully and in the archive. So look again at the qa page: It says out of date on i386: libxmlezout0, libxmlezout1-dev (from 1.06-2). It seems you recently droped these two packages. They are still in wheezy and used there, so your package can't migrate without the old packages being removed. That's job of the ftp-team, and usually you don't have to care about that, as the ftp-team get's notified about this cruft, and tries to remove it. See [2] for the current Cruft report which also mentiones your package. As said: Normally the ftp-team does that for you, and you don't have to do anything special. However, in this case the ftp-team could do anything about it. When trying to remove your old package, one sees the following (AFAIK you could try that out on ries.debian.org, if you are an DD, if not apt-cache rdepends might help you): I'm not DD but DM. Checking reverse dependencies... # Broken Depends: liblog4ada: liblog4ada1-dev narval: libnarval-dbg [amd64 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc s390 sparc] libnarval1-dev [amd64 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc s390 sparc] libnarval1.10.1 [amd64 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc s390 sparc] narval-generic-actors [amd64 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc s390 sparc] narval-servers [amd64 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc s390 sparc] narval-tests-actors [amd64 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc s390 sparc] # Broken Build-Depends: liblog4ada: libxmlezout1-dev narval: libxmlezout1-dev So, your package can't be removed, because that would break other packages. Brolen Depends can usually be solved by requesting binary NMUs (binNMUs). AFAIK that's easiest done with bug against the release.debian.org apckage. Broken Build-Depends usually means that you have to tell the maintainers of these packages to fix their packages. Once they are uploaded, the old package may be removed, and may migrate to testing. Also note that you don't have to request binNMUs, if the package needs a sourceful upload anyway. liblog4ada is a package of mine, so if I upload it also, it should solve part of the problem ? (I will have to fix narval, polyorb, also) Thanks a lot for all your explanations, I'll go try fix this problem. xavier 1: https://buildd.debian.org/status/package.php?p=libxmlezout 2: http://ftp-master.debian.org/cruft-report-daily.txt Best regards, Alexander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk65Sa8ACgkQVIZi0A5BZF52egCfXOmVtPUaYr0j9+lxrxZrAz0h fQIAn2W5BatLTNWZdZ90YfmxPubLvhX4 =OIYn -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4eb949af.3060...@ipno.in2p3.fr
Re: [RFH] libxmlezout : out of date on many archs
Hi! Am 08.11.2011 16:24, schrieb Xavier Grave: Checking reverse dependencies... # Broken Depends: liblog4ada: liblog4ada1-dev narval: libnarval-dbg [amd64 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc s390 sparc] libnarval1-dev [amd64 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc s390 sparc] libnarval1.10.1 [amd64 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc s390 sparc] narval-generic-actors [amd64 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc s390 sparc] narval-servers [amd64 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc s390 sparc] narval-tests-actors [amd64 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc s390 sparc] # Broken Build-Depends: liblog4ada: libxmlezout1-dev narval: libxmlezout1-dev [..] liblog4ada is a package of mine, so if I upload it also, it should solve part of the problem ? (I will have to fix narval, polyorb, also) Yes, you have to upload liblog4ada. As it build depends on libxmlezout1-dev, which you droped in one of your last uploads, there's no way libxmlezout can migrate to testing without breaking the existing liblog4ad in testing. Same with narval. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4eb950bf.7010...@debian.org