LinuxQuestions.org - apt-get upgrade

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - apt-get upgrade - troubles. (https://www.linuxquestions.org/questions/debian-26/apt-get-upgrade-troubles-223482/)

apt-get upgrade - troubles.

I'm having some problems with apt-get upgrade:

Code:

hehelol:~# apt-get upgrade

Reading Package Lists... Done

Building Dependency Tree... Done

The following packages will be upgraded:

  g++-3.3 gcc-3.3 libstdc++5-3.3-dev

3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

7 not fully installed or removed.

Need to get 0B/4259kB of archives.

After unpacking 0B of additional disk space will be used.

Do you want to continue? [Y/n] 

(Reading database ... 54732 files and directories currently installed.)

Preparing to replace gcc-3.3 1:3.3.4-6sarge1 (using .../gcc-3.3_1%3a3.3.4-6sarge1.1_i386.deb) ...

Unpacking replacement gcc-3.3 ...

dpkg: error processing /var/cache/apt/archives/gcc-3.3_1%3a3.3.4-6sarge1.1_i386.deb (--unpack):

 trying to overwrite `/usr/share/doc/gcc-3.3-base/changelog.Debian.gz', which is also in package gcc-3.3-base

dpkg-deb: subprocess paste killed by signal (Broken pipe)

Preparing to replace libstdc++5-3.3-dev 1:3.3.4-6sarge1 (using .../libstdc++5-3.3-dev_1%3a3.3.4-6sarge1.1_i386.deb) ...

Unpacking replacement libstdc++5-3.3-dev ...

dpkg: error processing /var/cache/apt/archives/libstdc++5-3.3-dev_1%3a3.3.4-6sarge1.1_i386.deb (--unpack):

 trying to overwrite `/usr/share/doc/libstdc++5/changelog.Debian.gz', which is also in package libstdc++5

dpkg-deb: subprocess paste killed by signal (Broken pipe)

Preparing to replace g++-3.3 1:3.3.4-6sarge1 (using .../g++-3.3_1%3a3.3.4-6sarge1.1_i386.deb) ...

Unpacking replacement g++-3.3 ...

dpkg: error processing /var/cache/apt/archives/g++-3.3_1%3a3.3.4-6sarge1.1_i386.deb (--unpack):

 trying to overwrite `/usr/share/doc/gcc-3.3-base/changelog.Debian.gz', which is also in package gcc-3.3-base

dpkg-deb: subprocess paste killed by signal (Broken pipe)

Errors were encountered while processing:

 /var/cache/apt/archives/gcc-3.3_1%3a3.3.4-6sarge1.1_i386.deb

 /var/cache/apt/archives/libstdc++5-3.3-dev_1%3a3.3.4-6sarge1.1_i386.deb

 /var/cache/apt/archives/g++-3.3_1%3a3.3.4-6sarge1.1_i386.deb

E: Sub-process /usr/bin/dpkg returned an error code (1)

Does anyone know how to fix this?..

You can force the overwrite for the packages causing the problem. Try:

Code:

dpkg -i --force-overwrite /var/cache/apt/archives/gcc-3.3_1%3a3.3.4-6sarge1.1_i386.deb

dpkg --configure -a

You can repeat the above command with the other two packages giving you problems. Then "apt-get upgrade" to see if anything else is broken.

I tried that, and got this:

Code:

hehelol:~# dpkg -i --force-overwrite /var/cache/apt/archives/gcc-3.3_1%3a3.3.4-6sarge1.1_i386.deb

(Reading database ... 54732 files and directories currently installed.)

Preparing to replace gcc-3.3 1:3.3.4-6sarge1 (using .../gcc-3.3_1%3a3.3.4-6sarge1.1_i386.deb) ...

Unpacking replacement gcc-3.3 ...

dpkg - warning, overriding problem because --force enabled:

 trying to overwrite `/usr/share/doc/gcc-3.3-base/changelog.Debian.gz', which is also in package gcc-3.3-base

dpkg: dependency problems prevent configuration of gcc-3.3:

 gcc-3.3 depends on cpp-3.3 (>= 1:3.3.4-6sarge1.1); however:

  Package cpp-3.3 is not configured yet.

 gcc-3.3 depends on cpp-3.3 (<< 1:3.3.5); however:

  Package cpp-3.3 is not configured yet.

dpkg: error processing gcc-3.3 (--install):

 dependency problems - leaving unconfigured

Errors were encountered while processing:

 gcc-3.3

It occured to be RC-bugs, so I just removed those packages.

Use Unstable gcc/ccp/g77/etc.

I had the same problem. I just upgraded them all to unstable (Sid). That worked.

Of course, you run unstable/Sid at your own risk. :)

At this point, we can have the discussion that Unstable is more secure than Testing (Sarge), since neither gets "official" Security fixes, but Testing has to wait at least 10 days for fixes to percolate in from Unstable.

You can always "downgrade" back to Sarge once this packaging problem gets fixed.

There are two "Grave" bug reports against gcc and gcc-base for these problems - 268476 and 268700