Daniel Burrows <[EMAIL PROTECTED]> wrote: >> > If you jump into >> > the visual UI (run without any argument) or run "aptitude install", do you >> > still see all that stuff being installed? >> >> Running the TUI and pressing "g" gives nothing except the remark about >> the held-back apt stuff, "aptitude install" is silent. Even more >> strange, with all those supposedly unmet dependencies? Let's have a >> look what dpkg thinks: > > Hm, so those two commands *DON'T* install all that extra stuff?
No, the don't install it. There doesn't seem to be a reason for that... >> I don't get it. As a test, I have now installed one of the libs which >> aptitude wanted (libpci2, one which doesn't pull in anything) and tried again >> dist-upgrade - no change. In the TUI, no information is shown for a >> view of the packages I tried which would discriminate them from all s/view/few/... > 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. 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. # cat $HOME/.aptitude/config aptitude ""; aptitude::Keep-Unused-Pattern ""; aptitude::Delete-Unused-Pattern ""; Anyway, after installing lsb-release "aptitude dist-upgrade" behaves more understandable, it says The following packages will be upgraded: apt apt-utils libsasl2-2 python-apt and later it reports the problem about aptitude and the suggestion of holding back those packages. Regards, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
