GCC4: dselect and lilo
Today, on upgrading my gcc4 test system (deb
http://debian-ppc64.alioth.debian.org/gcc4 unstable main contrib
non-free) I noticed that there was a newer lilo package. Unfortunately,
it doesn't help with the original problem described on this list
earlier. Does it seem likely that this can/will be fixed or should it
perhaps be documented that for gcc4, lilo isn't an option? At least not
the packaged version.
Second issue. dselect was kept back due to:
tsukasa-nfs01:~# aptitude install dselect
Reading Package Lists... Done
Building Dependency Tree
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
E: Unable to correct problems, you have held broken packages.
E: Unable to correct dependencies, some packages cannot be installed
E: Unable to resolve some dependencies!
Some packages had unmet dependencies. 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 packages have unmet dependencies:
dselect: Depends: libgcc1 (>= 1:4.0.0-7) but 1:4.0.0-2 is installed.
Depends: libstdc++6 (>= 4.0.0-7) but 4.0.0-2 is installed.
The typical tricks of using apt-get clean, reinstalling these two
libraries, etc. didn't help.
/v\
Reply to: