Hi David,
maybe you can shed some light on this issue.
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).
The failure actually occurs (in jessie) while installing the package
that has disappeared during the upgrade (wheezy 2 jessie), but more
interesting to investigate is *why* it disappeared at all.
Comparing amd64 and i386 upgrade logs, I see that on amd64
libgpod4-nogtk gets upgraded, while on i386 libgpod4-nogtk gets replaced
with libgpod4:
i386:
2 libgpod4 [ i386 ] < none -> 0.8.3-1.1+b1 > ( libs )
(no score for libgpod4-nogtk, so probably 0)
-1 libgpod-nogtk-dev [ i386 ] < 0.8.2-7 -> 0.8.3-1.1+b1 > ( libdevel )
...
Investigating (0) libgpod4 [ i386 ] < none -> 0.8.3-1.1+b1 > ( libs )
Broken libgpod4:i386 Conflicts on libgpod4-nogtk [ i386 ] < 0.8.2-7 ->
0.8.3-1.1+b1 > ( libs )
Considering libgpod4-nogtk:i386 0 as a solution to libgpod4:i386 2
Added libgpod4-nogtk:i386 to the remove list
Conflicts//Breaks against version 0.8.2-7 for libgpod4-nogtk but
that is not InstVer, ignoring
Fixing libgpod4:i386 via remove of libgpod4-nogtk:i386
amd64:
2 libgpod4-nogtk [ amd64 ] < 0.8.2-7 -> 0.8.3-1.1+b1 > ( libs )
1 libgpod4 [ amd64 ] < none -> 0.8.3-1.1+b1 > ( libs )
-1 libgpod-nogtk-dev [ amd64 ] < 0.8.2-7 -> 0.8.3-1.1+b1 > ( libdevel )
...
no decision regarding libgpod4/libgpod4-nogtk had to be taken
The full i386 log with pkgResolver debug info can be found here:
https://bugs.debian.org/782332
I can now easily rerun the test and get an interactive shell in the
piuparts chroot after the failure, in case you want me to further
investigate things.
If it's helpful, I might try to rerun this upgrade with upgrading apt to
jessie first and the remaining packages thereafter.
Thanks
Andreas
On Fri, 10 Apr 2015 16:28:55 +0200 Andreas Beckmann <a...@debian.org> wrote:
> Package: libgpod-nogtk-dev
> Version: 0.8.3-1.1
> Severity: serious
> User: debian...@lists.debian.org
> 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
