Re: package stuck in unstable after switching to AutomaticDebugPackages
On 05/08/2016 11:55 PM, Mattia Rizzolo wrote: > On Sun, May 08, 2016 at 09:40:02PM +, Niels Thykier wrote: >> James Cowgill: >>> On Sun, 2016-05-08 at 20:17 +0200, Alex Mestiashvili wrote: gearmand package has stuck in unstable due to missing -dbg packages: https://release.debian.org/migration/testing.pl?package=gearmand >>> >>> It's not migrating because the old dbg packages are still in sid. >> >> The note from testing.pl is (now) just an informational message. Have a >> look at [1], which notes the following items of interest: > > In general, testing.pl is imho more confusing than anything else. And > really reading the message in tracker.d.o is usually more than enough to > understand what's wrong. Not in this case, but here testing.pl didn't > either... > >>> Usually stuff like this is removed automatically by dak's auto >>> decrufter but apparently not this time. >>> >> >> Hmm, apparently the auto-decrufter thinks that the removal of >> libgearman7-dbg would break libgearman-dbg. I suspect part of the issue >> is that libgearman-dbg is an arch:all package (which has a different >> heuristic for depending when it should be decrufted). >> >>> If you file a NBS removal bug against ftp.debian.org then the package >>> should migrate after the dbg packages are removed manually. >>> >>> James >>> >> >> I agree that it would probably help. :) > > I agree that a NBS removal for libgearman-dbg should be enough. > Then the autodecrufter will be able to remove libgearman7-dbg, and then > gearmand will be able to migrate. > Thank you for the details, I am preparing a new upload fixing a couple of minor issues and will file the NBS removal bug. Best regards, Alex
Re: package stuck in unstable after switching to AutomaticDebugPackages
On 05/08/2016 09:00 PM, James Cowgill wrote: > On Sun, 2016-05-08 at 19:57 +0100, James Cowgill wrote: >> Hi, >> >> On Sun, 2016-05-08 at 20:17 +0200, Alex Mestiashvili wrote: >>> >>> Hi All, >>> >>> gearmand package has stuck in unstable due to missing -dbg >>> packages: >>> >>> https://release.debian.org/migration/testing.pl?package=gearmand >>> >>> The debug packages were removed after switching to automatic debug >>> packages [0]. >>> >>> How do I force the migration ? What is the right way to switch to >>> automatic -dbgsym packages ? >> >> It's not migrating because the old dbg packages are still in sid. >> Usually stuff like this is removed automatically by dak's auto >> decrufter but apparently not this time. >> >> If you file a NBS removal bug against ftp.debian.org then the package >> should migrate after the dbg packages are removed manually. > > And you also should have a call to dh_strip --dbgsym-migration in your > debian/rules (see dh_strip(1)). This wont prevent testing migration > though. > > James > I see, thanks for the hint! Best regards, Alex
Re: package stuck in unstable after switching to AutomaticDebugPackages
On Sun, May 08, 2016 at 09:40:02PM +, Niels Thykier wrote: > James Cowgill: > > On Sun, 2016-05-08 at 20:17 +0200, Alex Mestiashvili wrote: > >> gearmand package has stuck in unstable due to missing -dbg packages: > >> > >> https://release.debian.org/migration/testing.pl?package=gearmand > > > > It's not migrating because the old dbg packages are still in sid. > > The note from testing.pl is (now) just an informational message. Have a > look at [1], which notes the following items of interest: In general, testing.pl is imho more confusing than anything else. And really reading the message in tracker.d.o is usually more than enough to understand what's wrong. Not in this case, but here testing.pl didn't either... > > Usually stuff like this is removed automatically by dak's auto > > decrufter but apparently not this time. > > > > Hmm, apparently the auto-decrufter thinks that the removal of > libgearman7-dbg would break libgearman-dbg. I suspect part of the issue > is that libgearman-dbg is an arch:all package (which has a different > heuristic for depending when it should be decrufted). > > > If you file a NBS removal bug against ftp.debian.org then the package > > should migrate after the dbg packages are removed manually. > > > > James > > > > I agree that it would probably help. :) I agree that a NBS removal for libgearman-dbg should be enough. Then the autodecrufter will be able to remove libgearman7-dbg, and then gearmand will be able to migrate. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Re: package stuck in unstable after switching to AutomaticDebugPackages
James Cowgill: > Hi, > Hi, > On Sun, 2016-05-08 at 20:17 +0200, Alex Mestiashvili wrote: >> Hi All, >> >> gearmand package has stuck in unstable due to missing -dbg packages: >> >> https://release.debian.org/migration/testing.pl?package=gearmand >> >> The debug packages were removed after switching to automatic debug >> packages [0]. >> >> How do I force the migration ? What is the right way to switch to >> automatic -dbgsym packages ? > > It's not migrating because the old dbg packages are still in sid. I suspect you may be right about that though it is not clear to me that we agree on why. :) So I'll just clarify one point: The note from testing.pl is (now) just an informational message. Have a look at [1], which notes the following items of interest: - "Valid candidate" => Nothing listed is a blocker for migration - "old binaries left ... (but ignoring cruft, so nevermind)" (which is the part where this is just an informational message) It does not migrate currently because it would make things uninstallable. Admittedly, I did a TL;DR on the britney log, so I don't know the details and you could be right about the old "-dbg" causing the issue. (Mind you, in the "old" days, Britney would ignore the package until had been decrufted) > Usually stuff like this is removed automatically by dak's auto > decrufter but apparently not this time. > Hmm, apparently the auto-decrufter thinks that the removal of libgearman7-dbg would break libgearman-dbg. I suspect part of the issue is that libgearman-dbg is an arch:all package (which has a different heuristic for depending when it should be decrufted). > If you file a NBS removal bug against ftp.debian.org then the package > should migrate after the dbg packages are removed manually. > > James > I agree that it would probably help. :) Thanks, ~Niels [1] https://tracker.debian.org/pkg/gearmand signature.asc Description: OpenPGP digital signature
Re: package stuck in unstable after switching to AutomaticDebugPackages
On Sun, 2016-05-08 at 19:57 +0100, James Cowgill wrote: > Hi, > > On Sun, 2016-05-08 at 20:17 +0200, Alex Mestiashvili wrote: > > > > Hi All, > > > > gearmand package has stuck in unstable due to missing -dbg > > packages: > > > > https://release.debian.org/migration/testing.pl?package=gearmand > > > > The debug packages were removed after switching to automatic debug > > packages [0]. > > > > How do I force the migration ? What is the right way to switch to > > automatic -dbgsym packages ? > > It's not migrating because the old dbg packages are still in sid. > Usually stuff like this is removed automatically by dak's auto > decrufter but apparently not this time. > > If you file a NBS removal bug against ftp.debian.org then the package > should migrate after the dbg packages are removed manually. And you also should have a call to dh_strip --dbgsym-migration in your debian/rules (see dh_strip(1)). This wont prevent testing migration though. James signature.asc Description: This is a digitally signed message part
Re: package stuck in unstable after switching to AutomaticDebugPackages
Hi, On Sun, 2016-05-08 at 20:17 +0200, Alex Mestiashvili wrote: > Hi All, > > gearmand package has stuck in unstable due to missing -dbg packages: > > https://release.debian.org/migration/testing.pl?package=gearmand > > The debug packages were removed after switching to automatic debug > packages [0]. > > How do I force the migration ? What is the right way to switch to > automatic -dbgsym packages ? It's not migrating because the old dbg packages are still in sid. Usually stuff like this is removed automatically by dak's auto decrufter but apparently not this time. If you file a NBS removal bug against ftp.debian.org then the package should migrate after the dbg packages are removed manually. James signature.asc Description: This is a digitally signed message part
package stuck in unstable after switching to AutomaticDebugPackages
Hi All, gearmand package has stuck in unstable due to missing -dbg packages: https://release.debian.org/migration/testing.pl?package=gearmand The debug packages were removed after switching to automatic debug packages [0]. How do I force the migration ? What is the right way to switch to automatic -dbgsym packages ? Thanks, Alex [0] https://wiki.debian.org/AutomaticDebugPackages
