On Fri, Jun 15, 2007 at 04:58:14PM +0200, Frank Küster <[EMAIL PROTECTED]> was heard to say: > Daniel Burrows <[EMAIL PROTECTED]> wrote: > > Aha. If you look at the aptitude output earlier in your mail, it looks > > like lsb-core is required by lsb. lsb is recommended by lsb-release, and > > lsb-release is required by python-apt. > > > > So the only bug I see here is that it's too hard to get a sensible > > explanation of where autoinstalls (the ones done internally by libapt) > > come from. > > Yes, that seems to be the point. I'm not sure how to make that clearer, > though. This upgrade scenario seems to be a very special case.
If aptitude jumps into its regular resolver, you can get output like python-apt Depends lsb-release --> installing lsb-release lsb-release Recommends lsb --> installing lsb lsb Depends lsb-core --> installing lsb-core ... I think that might help a little. Now that Michael has merged the automarking patch, maybe I should see if I can hack apt so that it instruments its autoinstalls with the information I'd need to do a topological sort like this. It's been a persistent problem for ages; "-D" tries to reverse-engineer apt to figure out what just happened, but it can't provide this level of detail. > Here's one more strange thing. In order to investigate what happens, I > did this: > > # aptitude install lsb-release > Reading package lists... Done > Building dependency tree... Done > Reading extended state information > Initializing package states... Done > Building tag database... Done > The following packages have been kept back: > apt apt-utils libsasl2-2 python-apt > The following NEW packages will be installed: > lsb-release > The following packages are RECOMMENDED but will NOT be installed: > lsb > 0 packages upgraded, 1 newly installed, 0 to remove and 4 not upgraded. > Need to get 16,2kB of archives. After unpacking 45,1kB will be used. > Writing extended state information... Done > Get:1 http://localhost sid/main lsb-release 3.1-23.1 [16,2kB] > Fetched 16,2kB in 0s (88,4kB/s) > Selecting previously deselected package lsb-release. > (Reading database ... 73681 files and directories currently installed.) > Unpacking lsb-release (from .../lsb-release_3.1-23.1_all.deb) ... > Setting up lsb-release (3.1-23.1) ... > > Why does it not install the recommended package? In the UI, I have > selected to install Recommends. ... and also it's the default. > # cat $HOME/.aptitude/config > aptitude ""; > aptitude::Keep-Unused-Pattern ""; > aptitude::Delete-Unused-Pattern ""; That's root's $HOME, right? Just to check, what's in your own home directory's .aptitude/config (if it exists)? Daniel
