Re: Bug#746271: Misinterprets dstat's versioned dependency on python:any
Control: reassign -1 apt
[ Reassigning and leaving most of the context for apt's team benefit,
please see at the end. Thanks Sven for the triaging. ]
Hi!
On Mon, 2014-04-28 at 19:32:49 +0200, Andras Korn wrote:
> On Mon, Apr 28, 2014 at 07:13:31PM +0200, Sven Joachim wrote:
> > > I tried to install dstat on a relatively recent sid system:
> >
> > What does "relatively recent" mean?
>
> How can I quantify that? I don't know specifically when the last full
> dist-upgrade was, but dpkg and apt in particular were eventually up to date
> (see below).
>
> > > # apt-get -u install dstat
> > > [...]
> > > The following NEW packages will be installed:
> > > dstat
> > > 0 upgraded, 1 newly installed, 0 to remove and 323 not upgraded.
> > > Need to get 50.5 kB of archives.
> > > After this operation, 351 kB of additional disk space will be used.
> > > Get:1 http://cdn.debian.net/debian/ sid/main dstat all 0.7.2-4 [50.5 kB]
> > > Fetched 50.5 kB in 6s (8,254 B/s)
> > > Selecting previously unselected package dstat.
> > > (Reading database ... 38323 files and directories currently installed.)
> > > Unpacking dstat (from .../archives/dstat_0.7.2-4_all.deb) ...
> > > Processing triggers for man-db ...
> > > dpkg: dependency problems prevent configuration of dstat:
> > > dstat depends on python:any (>= 2.6.6-7~).
> > >
> > > dpkg: error processing dstat (--configure):
> > > dependency problems - leaving unconfigured
> > > Errors were encountered while processing:
> > > dstat
> > > E: Sub-process /usr/bin/dpkg returned an error code (1)
> > >
> > > Huh? apt-get should've taken care of that, surely?
> >
> > Yes, if you have at least apt 0.9.12.
> >
> > > So it turns out the python package was already 2.7.5-3, but for some reason
> > > that didn't satisfy a dependency on python:any (>= 2.6.6-7~) as far as dpkg
> > > was concerned, but did satisfy it as far as apt-get was concerned.
> >
> > Only python 2.7.5-5 added the necessary "Multi-Arch: allowed" field,
> > that's why you got the error with earlier versions.
> >
> > > To me it looks like apt-get was right and dpkg was wrong.
> >
> > No, it's the other way around. See #723586 if your apt package is older
> > than 0.9.12.
>
> Hmmm. I started with apt 0.9.9.4, but thinking that it could be a problem
> with apt, I upgraded to apt 1.0.2 and apt-get -f install still didn't fix
> the dependency problem.
>
> I started with dpkg 1.17.1 and upgraded to 1.17.7 (at the same time I
> upgraded apt).
>
> This is what I did, in sequence (taken from my zsh_history file):
>
> : 1398699459:0;apt-get -u install dstat
> : 1398699480:0;apt-get update
> : 1398699508:0;apt-get -f install
> : 1398699518:0;apt-get -u install dpkg apt
> : 1398699553:0;apt-get -f install
> : 1398699565:0;apt-get -u install python
>
> So, with apt 1.0.2 apt-get -f install definitely didn't resolve the missing
> dependency.
If apt did not fix it with -f, then I supposed that could be
considered an apt bug, but that's probably for them to decide.
Definitely not a dpkg bug.
Thanks,
Guillem
Reply to: