g++-3.3 gcc-3.3 libstdc++5-3.3-dev will not update sarge

Moloko · 08-27-2004, 05:23 PM

I'm getting lots of errors trying to upgrade:

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.
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 ... 62914 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

Anyone having the same and/or know of a fix?

ToniT · 08-27-2004, 05:51 PM

It is a known issue and will be probably fixed soon.

Moloko · 08-28-2004, 12:15 AM

Abject · 08-28-2004, 12:23 PM

In the meantime, there are a couple of workarounds in this thread .

Moloko · 08-29-2004, 12:18 AM

It has been fixed as you may or may not have noticed

emmkay · 08-29-2004, 07:15 AM

Quote:

It has been fixed as you may or may not have noticed

I've just installed sarge after getting fed up with how old woody is.

So I am having the same problem as that mentioned above (and in at least 2 other threads too, I notice). However, you're saying it has been fixed; but does that mean I should be able to do something about it right now? I've apt-get update'd on my box and tried again but it still does not work.

I'm probably missing something obvious here...

dochyde · 08-29-2004, 07:53 AM

Hi all

Me too I am running testing and I still cannot upgrade correctly.
Can anything else be done?

Thanks

doc

emmkay · 08-29-2004, 08:15 AM

As it happens, I decided to go for the --force-overwrite option (while holding my breath) and that indeed resolved the problem for me.

However, I'd still be interested to know how the "official" fix for this is to be deployed, as if something like this happens again I'm not entirely sure whether I should be forcing the install through or not?

Abject · 08-29-2004, 10:43 AM

Quote:

However, I'd still be interested to know how the "official" fix for this is to be deployed, as if something like this happens again I'm not entirely sure whether I should be forcing the install through or not?

The Testing package will be repaired and replaced ASAP. Debian is in the throes of preparing to make Sarge the "Stable" release (replacing Woody), so you can bet that this is a priority for somebody.

My solution was to upgrade the afflicted packages to Unstable. The Unstable packages don't have this bug. Unstable has a scary-sounding name, but, honestly, it doesn't break very often. Testing breaks even more rarely but, as you can see, sh*t happens there, too. If the unstable packages are broken, I'll just downgrade to testing an use --force-overwrite. No biggie.

emmkay · 08-29-2004, 11:38 AM

Another daft question... but how would you upgrade just one package to sid while leaving the rest on sarge?

Abject · 08-29-2004, 01:04 PM

Quote:

... how would you upgrade just one package to sid while leaving the rest on sarge?

[list=1][*]Add the unstable sources to your /etc/apt/sources.list if they aren't already there. You should see lines like this:

Code:

deb http://mirrors.kernel.org/debian/ unstable main contrib non-free
deb http://linux.csua.berkeley.edu/debian-non-US/ unstable/non-US main contrib non-free

[*]I assume that you're running with Sarge / Testing as your default distro. Add these two lines to /etc/apt/apt.conf:

Code:

APT::Default-Release "testing";
APT::Cache-Limit 16777216;

The first one says Testing is your default distro. The second one keeps you from overflowing your apt-cache due to the larger number of sources you're using.[*]# apt-get update[*]# apt-get install apt-show-versions[*]# apt-get -t unstable -u install libstdc++5-3.3-dev g++-3.3 gcc-3.3[*]You may get some dependency conflicts, things that look like:

Code:

  xyzzy: Depends: plugh (>= 4:3.3.0) but 4:3.2.3-2 is to be installed

you'll have to upgrade the things on the right-hand side first and then try again, e.g.:

Code:

# apt-get -t unstable -u plugh
(plugh gets installed...)
# apt-get -t unstable -u install libstdc++5-3.3-dev g++-3.3 gcc-3.3

You may have to repeat this process with dependency conflicts more than once. [*]From now on, what used to be:

Code:

# apt-get update
# apt-get upgrade

becomes:

Code:

# apt-get update
# apt-get install `apt-show-versions -u -b | grep unstable`
# apt-get upgrade

Those single quote / accent things are really important. So is the order [/list=1]

If you'd like to become a psuedo-expert like me, Give the APT HowTo a good read, especially Sections 3.8 and 3.9 !

emmkay · 08-29-2004, 01:46 PM

Wow; top answer! Many thanks...

macondo · 08-29-2004, 04:25 PM

The gcc 3.3 bug has been fixed, just did an update/dist-upgrade and worked fine.

utanja · 08-29-2004, 04:35 PM

Quote:

Originally posted by macondo
The gcc 3.3 bug has been fixed, just did an update/dist-upgrade and worked fine.

at the risk of being overly cautious and not offensive....are you sure..

macondo · 08-29-2004, 05:09 PM

you mean it's all a figment of my imagination?