On Fri, Jan 09, 2009 at 01:42:39AM +0800, jida...@jidanni.org was heard to say:
> "why" should report based on the dependencies of the candidate, not
> the installed version.
>
> # aptitude full-upgrade
> The following NEW packages will be installed:
> curl{a}
> # aptitude why curl
> i apt-file Depends wget | curl
> (So the user panics: "you mean wget is not installed anymore?!")
> # set wget curl
> # for i do dpkg -l $i|tail -n 1; done
> ii wget 1.11.4-2 retrieves files from the web
> un curl <none> (no description available)
> # aptitude -v show apt-file|egrep Version\|Depends
> Version: 2.2.0
> Depends: perl, curl, libconfig-file-perl, libapt-pkg-perl,
> Version: 2.1.6
> Depends: perl, wget | curl, libconfig-file-perl, libapt-pkg-perl,
> # apt-cache policy apt-file
> apt-file:
> Installed: 2.1.6
> Candidate: 2.2.0
>
> The man page says:
> By default aptitude outputs only the "most installed, strongest,
> tightest, shortest" dependency chain.
Could you please explain more explicitly what the bug is? What did
you expect aptitude to display? Are you saying there's a tighter
dependency on curl than the apt-file one?
> Well, "most installed" doesn't mean you should necessarily use the
> dependencies of the installed version over the candidate.
Actually, that's exactly what it means. Maybe I should reword that
manual section to be more clear.
Daniel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
