Your message dated Sun, 2 Apr 2017 16:51:43 +0100 with message-id <[email protected]> and subject line Re: Bug#782332: libgpod-nogtk-dev: fails to upgrade from 'wheezy': Depends: libgpod4-nogtk (= 0.8.3-1.1+b1) but it is not going to be installed has caused the Debian Bug report #782332, regarding libgpod-nogtk-dev: fails to upgrade from 'wheezy': Depends: libgpod4-nogtk (= 0.8.3-1.1+b1) but it is not going to be installed to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 782332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782332 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libgpod-nogtk-dev Version: 0.8.3-1.1 Severity: serious User: [email protected] Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'jessie' fails. >From the attached log (scroll to the bottom...): Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) libgpod-common [ i386 ] < 0.8.3-1.1+b1 > ( libs ) Broken libgpod-common:i386 Depends on libgpod4 [ i386 ] < 0.8.3-1.1+b1 > ( libs ) (>= 0.7.90) Considering libgpod4:i386 -1 as a solution to libgpod-common:i386 1 Added libgpod4:i386 to the remove list Fixing libgpod-common:i386 via keep of libgpod4:i386 Investigating (0) libgpod4-nogtk [ i386 ] < none -> 0.8.3-1.1+b1 > ( libs ) Broken libgpod4-nogtk:i386 Conflicts on libgpod4 [ i386 ] < 0.8.3-1.1+b1 > ( libs ) Considering libgpod4:i386 -1 as a solution to libgpod4-nogtk:i386 -1 Holding Back libgpod4-nogtk:i386 rather than change libgpod4:i386 Investigating (1) libgpod-nogtk-dev [ i386 ] < none -> 0.8.3-1.1+b1 > ( libdevel ) Broken libgpod-nogtk-dev:i386 Depends on libgpod4-nogtk [ i386 ] < none -> 0.8.3-1.1+b1 > ( libs ) (= 0.8.3-1.1+b1) Considering libgpod4-nogtk:i386 -1 as a solution to libgpod-nogtk-dev:i386 9998 Re-Instated libgpod4-nogtk:i386 Investigating (1) libgpod4-nogtk [ i386 ] < none -> 0.8.3-1.1+b1 > ( libs ) Broken libgpod4-nogtk:i386 Conflicts on libgpod4 [ i386 ] < 0.8.3-1.1+b1 > ( libs ) Considering libgpod4:i386 -1 as a solution to libgpod4-nogtk:i386 -1 Holding Back libgpod4-nogtk:i386 rather than change libgpod4:i386 Investigating (2) libgpod-nogtk-dev [ i386 ] < none -> 0.8.3-1.1+b1 > ( libdevel ) Broken libgpod-nogtk-dev:i386 Depends on libgpod4-nogtk [ i386 ] < none -> 0.8.3-1.1+b1 > ( libs ) (= 0.8.3-1.1+b1) Considering libgpod4-nogtk:i386 -1 as a solution to libgpod-nogtk-dev:i386 9998 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libgpod-nogtk-dev : Depends: libgpod4-nogtk (= 0.8.3-1.1+b1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. This problem has shown up recently only, --install-recommends is enabled. It is reproducible, I'm now checking if if appears in other tests, too. Maybe a binNMU screwed up something? cheers, Andreas
libgpod-nogtk-dev_0.8.3-1.1+b1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---Version: 0.8.3-8.1 On Sat, 07 Nov 2015 at 20:45:14 +0100, Andreas Beckmann wrote: > It's an upgrade from wheezy to jessie that only manifests on i386 with > --install-recommends enabled (not without --install-recommends and not > on amd64, I don't about any other arch). ... > Comparing amd64 and i386 upgrade logs, I see that on amd64 > libgpod4-nogtk gets upgraded, while on i386 libgpod4-nogtk gets replaced > with libgpod4 I believe this is fixed in sid by my recent NMU, which turns libgpod4-nogtk into a transitional package that just pulls in libgpod4. These days the only extra dependency that results from this is libgdk-pixbuf2.0-0 (it no longer pulls in all of GTK+), and everything that depends on libgpod in Debian also depends on libgdk-pixbuf2.0-0 anyway, so the theoretical space saving does not seem worth the complexity cost. Prior to that NMU, it was non-deterministic whether libgpod-common will depend on libgpod4 or on libgpod4-nogtk|libgpod4 (the former breaks this upgrade, the latter is OK). As far as I can tell it is purely coincidental that i386 was in the bad set, but amd64 was in the good set, in both jessie and stretch. Regards, S
--- End Message ---
