[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Upgrade 3.0beta->3.0r0->3.0r1 in den Graben gefahren ?



Hallo,

Ist Debians Upgrade-Mechanismus wirklich absolut supä ??  #-]
Oder hab' ich da doch einen Bedienungsfehler gemacht: :-/

Mit 

apt-cdrom add
apt-get update
apt-get upgrade

habe ich erst von 3.0 beta auf 3.0 r0 mittels komplettem CD-Satz upgegradet,
da gabs offensichtlich kein Gemöhne und keine Fehlermeldungen.

Das selbe Spiel dann gleich mit der offiziellen sog. Update-CD von 3.0 r0 auf 3.0 r1
und da gabs dann folgende Meldungen:

Reading Package Lists...
Building Dependency Tree...
The following packages have been kept back
  a2ps adduser apt aptitude at autoclass ...usw.
...  usw. ....xterm xvfb zlib1g 
1 packages upgraded, 0 newly installed, 0 to remove and 279 not upgraded.
Sorry, but the following packages have unmet dependencies:
  communicator: Depends: communicator-smotif-473 but 4.73-18 is to be installed
                Depends: netscape-java-473 but 4.73-18 is to be installed
                Conflicts: netscape-base-407 but it is not installable
                Conflicts: netscape-base-408 but it is not installable
                Conflicts: netscape-base-45 but it is not installable
                Conflicts: netscape-base-451 but it is not installable
                Conflicts: netscape-base-46 but it is not installable
                Conflicts: netscape-base-472 but it is not installable
  communicator-smotif-473: Depends: libstdc++2.9-glibc2.1 but 2.91.66-4 is to be installed
                           Depends: libxpm4
                           Depends: communicator-base-473 but 4.73-18 is to be installed
                           Depends: netscape-base-4 (>= 1:4.72-24) but 1:4.77-2 is to be installed
                           Conflicts: communicator-smotif-473-libc5 but it is not installable
  gdm: Depends: xlib6g (>= 3.3.6) but 3.3.6-11potato32 is to be installed
       Depends: libpam-modules (>= 0.72-1) but 0.72-9 is to be installed
  libnspr3: Conflicts: libnspr20 but it is not installable
  libssl09: Conflicts: ssleay (< 0.9.2b) but it is not going to be installed
  mozilla: Depends: libstdc++2.10 but 1:2.95.2-14 is to be installed
           Depends: libnspr3 (>= M14) but M14-2 is to be installed
  ssh: Depends: libz1
       Conflicts: ssh-nonfree but it is not going to be installed
  task-gnome-apps: Depends: gnome-audio but 1.4.0-4 is to be installed
                   Depends: gnome-admin but 1.0.3-2 is to be installed
                   Depends: gnotes but 1.74 is to be installed
  xaw3dg: Depends: libc6 (>= 2.1.2) but 2.1.3-20 is to be installed
          Conflicts: axe (< 6.1.2-2) but it is not going to be installed
  xext: Depends: libc6 (>= 2.1.2) but 2.1.3-20 is to be installed
  xf86setup: Depends: tk8.2 (>= 8.2.2) but 8.2.3-4 is to be installed
  xmanpages: Conflicts: xman but it is not installable
  xprt: Depends: libc6 (>= 2.1.2) but 2.1.3-20 is to be installed
  xserver-vga16: Depends: libc6 (>= 2.1.2) but 2.1.3-20 is to be installed


Die /etc/apt/sources.list sieht dazu folgendermassen aus:

# standard
deb cdrom:[Debian GNU/Linux 3.0r1 Update CD 20030109: i386]/ woody contrib main non-US/contrib non-US/main non-US/non-free non-free
deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-7 (20020718)]/ unstable contrib main non-US/contrib non-US/main
deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-6 (20020718)]/ unstable contrib main non-US/contrib non-US/main
deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-5 (20020718)]/ unstable contrib main non-US/contrib non-US/main
deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-4 (20020718)]/ unstable contrib main non-US/contrib non-US/main
deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-3 (20020718)]/ unstable contrib main non-US/contrib non-US/main
deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-2 (20020718)]/ unstable contrib main non-US/contrib non-US/main
deb cdrom:[Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-1 (20020718)]/ unstable contrib main non-US/contrib non-US/main
deb cdrom:[Debian GNU/Linux 3.0 beta _Woody_ - fsn.hu unofficial i386 Binary-8 (20020514)]/ unstable contrib main non-US/contrib non-US/main non-US/non-free non-free
deb cdrom:[Debian GNU/Linux 3.0 beta _Woody_ - fsn.hu unofficial i386 Binary-7 (20020514)]/ unstable contrib main non-US/contrib non-US/main non-US/non-free non-free
deb cdrom:[Debian GNU/Linux 3.0 beta _Woody_ - fsn.hu unofficial i386 Binary-6 (20020514)]/ unstable contrib main non-US/contrib non-US/main non-US/non-free non-free
deb cdrom:[Debian GNU/Linux 3.0 beta _Woody_ - fsn.hu unofficial i386 Binary-5 (20020514)]/ unstable contrib main non-US/contrib non-US/main non-US/non-free non-free
deb cdrom:[Debian GNU/Linux 3.0 beta _Woody_ - fsn.hu unofficial i386 Binary-4 (20020514)]/ unstable contrib main non-US/contrib non-US/main non-US/non-free non-free
deb cdrom:[Debian GNU/Linux 3.0 beta _Woody_ - fsn.hu unofficial i386 Binary-3 (20020514)]/ unstable contrib main non-US/contrib non-US/main non-US/non-free non-free
deb cdrom:[Debian GNU/Linux 3.0 beta _Woody_ - fsn.hu unofficial i386 Binary-2 (20020514)]/ unstable contrib main non-US/contrib non-US/main non-US/non-free non-free
deb cdrom:[Debian GNU/Linux 3.0 beta _Woody_ - fsn.hu unofficial i386 Binary-1 (20020514)]/ unstable contrib main non-US/contrib non-US/main non-US/non-free non-free
deb cdrom:[Debian GNU/Linux 2.2 r6 _Potato_ - Official i386 Binary-3 (20020405)]/ unstable contrib main non-US/contrib non-US/main
deb cdrom:[Debian GNU/Linux 2.2 r6 _Potato_ - Official i386 Binary-2 (20020405)]/ unstable contrib main non-US/contrib non-US/main
deb cdrom:[Debian GNU/Linux 2.2 r6 _Potato_ - Official i386 Binary-1 (20020405)]/ unstable contrib main non-US/contrib non-US/main

Das System ist jetzt einem solchen Zustand, dass ich jetzt auch
dselect nicht mehr richtig benutzen kann, um gewünschte Pakte zu installieren.

Kann es sein dass es event. Unvollständigkeiten in der Update-CD gibt 
und hat jemand ne Idee, wie kann man das System wieder auf einen 
konsistenten Pakete-Zustand bringen kann?

Danke fürs Interesse,
Grüsse

Christoph Walther



Reply to: