Bug#426063: marked as done (gcc-4.1 upgrade fails)
Your message dated Thu, 31 May 2007 10:44:34 +0200
with message-id <18014.35570.835320.441973@gargle.gargle.HOWL>
and subject line Bug#426063: Problem fixed by umounting /usr/bin/gcc-4.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: gcc-4.1
Version: 4.1_4.1.2-8
Severity: high
Upgrading fails with the following error:
The following packages will be upgraded:
gcc-4.1
1 upgraded, 0 newly installed, 0 to remove and 256 not upgraded.
2 not fully installed or removed.
Need to get 0B/408kB of archives.
After unpacking 90.1kB disk space will be freed.
Do you want to continue [Y/n]?
(Reading database ... 173966 files and directories currently installed.)
Preparing to replace gcc-4.1 4.1.2-7 (using .../gcc-4.1_4.1.2-8_i386.deb) ...
Unpacking replacement gcc-4.1 ...
dpkg: error processing /var/cache/apt/archives/gcc-4.1_4.1.2-8_i386.deb (--unpack):
unable to make backup link of `./usr/bin/gcc-4.1' before installing new version: Invalid cross-device link
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/gcc-4.1_4.1.2-8_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
--- End Message ---
--- Begin Message ---
Daniel O'Neill writes:
>
> Running "mount" showed this:
>
> /usr/bin/gcc-4.1 on /usr/bin/gcc-4.1 type none (rw,bind)
>
>
> Perhaps an earlier instance of the upgrade had broken off after creating
> this symlink. I manually umounted /usr/bin/gcc-4.1 and gcc-4.1 upgraded
> fine.
if you open such reports, please close them yourself as well.
--- End Message ---
Reply to: