Your message dated Tue, 29 Jan 2019 11:31:30 +0100 with message-id <[email protected]> and subject line Re: Bug#918778: dpkg does not report all files to be overwritten. has caused the Debian Bug report #918778, regarding dpkg does not report all files to be overwritten. 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 918778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918778 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: dpkg Version: 1.19.0.5 When installing gcc-avr, I got the error message: dpkg: error processing archive /var/cache/apt/archives/gcc-avr_1%3a5.4.0+Atmel3.6.0-1build1_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcc1.so.0.0.0', which is also in package gcc-arm-embedded 7-2018q2-1~bionic1 So because I need the gcc-avr package now, and "not today" the gcc-ARM compiler, I decided to make a backup of the offending file and then force the install of gcc-avr. Then I get: dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/libcc1.so', which is also in package gcc-arm-embedded 7-2018q2-1~bionic1 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/lib/libcc1.so.0', which is also in package gcc-arm-embedded 7-2018q2-1~bionic1 so now it has overwritten two files that I did NOT make a backup of! I can probably recover by telling dpkg to force-overwrite during a reinstall of the ARM compiler, and it is of course a packaging error of those compilers to use a shared place to store these libraries, but dpkg should have allowed me to make a backup of the files without me having to figure out how to reinstall that ARM compiler while overwriting these shared files. Roger. -- ** [email protected] ** http://www.BitWizard.nl/ ** +31-15-2049110 ** ** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 ** *-- BitWizard writes Linux device drivers for any device you may have! --* The plan was simple, like my brother-in-law Phil. But unlike Phil, this plan just might work.
--- End Message ---
--- Begin Message ---Hi! On Wed, 2019-01-09 at 10:43:08 +0100, Roger Wolff wrote: > Package: dpkg > Version: 1.19.0.5 > When installing gcc-avr, I got the error message: > dpkg: error processing archive > /var/cache/apt/archives/gcc-avr_1%3a5.4.0+Atmel3.6.0-1build1_amd64.deb > (--unpack): > trying to overwrite '/usr/lib/libcc1.so.0.0.0', which is also in package > gcc-arm-embedded 7-2018q2-1~bionic1 > > So because I need the gcc-avr package now, and "not today" the > gcc-ARM compiler, I decided to make a backup of the offending file > and then force the install of gcc-avr. > > Then I get: > > dpkg: warning: overriding problem because --force enabled: > dpkg: warning: trying to overwrite '/usr/lib/libcc1.so', which is also in > package gcc-arm-embedded 7-2018q2-1~bionic1 > dpkg: warning: overriding problem because --force enabled: > dpkg: warning: trying to overwrite '/usr/lib/libcc1.so.0', which is also in > package gcc-arm-embedded 7-2018q2-1~bionic1 > > so now it has overwritten two files that I did NOT make a backup of! Right. > I can probably recover by telling dpkg to force-overwrite during > a reinstall of the ARM compiler, and it is of course a packaging > error of those compilers to use a shared place to store these > libraries, but dpkg should have allowed me to make a backup > of the files without me having to figure out how to reinstall > that ARM compiler while overwriting these shared files. The problem with this request is that the code just errors out on the first file conflict, and changing the code to keep going so that it can report all other instances would make it messier and error-prone, for something that only happens due to packaging errors, when using a force option marked as possibly damaging the system, and possibly when not having the .debs for the installed packages anymore. :) So, I'd rather keep the code as is. What I'd recommend though, which might still not help fully in case a package takes over files from multiple packages, is to use dpkg-repack to archive the installed package contents. But if you can install the other package any time, you can always force that in too. I'm thus closing this report, sorry! Thanks, Guillem
--- End Message ---
