I'm using Debian 2.0 which comes with libc6_2.0.7t-1. I also had to install 
libc6-dev_2.0.7t-1 and libc6-pic_2.0.7t-1. Later I needed the 2.0.7u version 
(for some packages which I can't remember - WindowMaker was probably one of 
them) so I downloaded libc6_2.0.7u-4 (just that one) from the Debian archive, 
and it installed ok. Of course my installed packages didn't look quite right:

ii  libc6        2.0.7u-4
ii  libc6-dev    2.0.7t-1
ii  libc6-pic    2.0.7t-1

but everything worked fine.

Now the problems:

1) A few days later, when I got back to get the other packages ( -dev and -pic) 
they were gone from the Debian archive! The only libc6 stuff to be found there 
were the 2.0.7t version and a new 2.0.7.19981211 version.
2) I tried to use apt to upgrade my system (if I was to upgrade such a 
fundamental piece why not the rest as well?). This is the output of apt-get:

meneltarma:~# apt-get -s upgrade
Updating package status cache...done
Checking system integrity...dependency error
You might want to run `apt-get -f install' to correct these.
Sorry, but the following packages are broken - this means they have unmet
dependencies:
  libc6-dev: Depends:libc6

and then:

meneltarma:~# apt-get -f install
Updating package status cache...done
Checking system integrity...dependency error
Correcting dependencies...ok
The following packages will be REMOVED:
  popt newt0.21-dev libg++272-dev xpm4g-dev slang0.99.38-dev slang0.99.38-pic 
xlib6g-dev ncurses3.4-dev tk8.0-dev tcl8.0-dev boot-floppies
  libc6-dev libc6-pic 
0 packages upgraded, 0 newly installed, 13 to remove and 1 not upgraded.
Need to get 0b of archives. After unpacking 26.6M will be freed.
Do you want to continue? [Y/n] n

I must say that does seem a little drastic.
Should I use dpkg to force the downgrade of libc6 from the t version to the u 
version and then rerun apt-get upgrade?
Will it break the packages that depend on libc6_2.0.7u only temporarily?
Or are there other options?

TIA

Carlos

Reply via email to