Well, in my case, the ARM compiler in the distribution (Ubuntu)
stopped working (from 16.04 to 18.04). So I had to install a third
party ARM compiler .deb .
I was going to argue that packaging error can be avoided if there
would be an easy tool that scans an entire repository for duplicate
files, but in this case the ubuntu team would've come up clean.
And again, it can be said that BOTH packages are wrong in installing
that file there.
But still leaving a potential "dataloss" situation in existance seems
"wrong" to me.
Roger.
On Tue, Jan 29, 2019 at 10:36:03AM +0000, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the dpkg package:
>
> #918778: dpkg does not report all files to be overwritten.
>
> It has been closed by Guillem Jover <guil...@debian.org>.
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Guillem Jover
> <guil...@debian.org> by
> replying to this email.
>
>
> --
> 918778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918778
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
> Date: Tue, 29 Jan 2019 11:31:30 +0100
> From: Guillem Jover <guil...@debian.org>
> To: Roger Wolff <r.e.wo...@bitwizard.nl>, 918778-d...@bugs.debian.org
> Subject: Re: Bug#918778: dpkg does not report all files to be overwritten.
> X-Spam-Status: No, score=-22.5 required=4.0 tests=ALL_TRUSTED,BAYES_00,
> FROMDEVELOPER,HAS_BUG_NUMBER,TXREP autolearn=ham autolearn_force=no
> version=3.4.2-bugs.debian.org_2005_01_02
>
> 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
> Date: Wed, 9 Jan 2019 10:43:08 +0100
> From: Roger Wolff <r.e.wo...@bitwizard.nl>
> To: sub...@bugs.debian.org
> Subject: dpkg does not report all files to be overwritten.
> X-Spam-Status: No, score=-10.0 required=4.0 tests=BAYES_00,HAS_PACKAGE,
> RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham autolearn_force=no
> version=3.4.2-bugs.debian.org_2005_01_02
>
> 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.
>
> --
> ** r.e.wo...@bitwizard.nl ** 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.
--
** r.e.wo...@bitwizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 **
** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 **
The plan was simple, like my brother-in-law Phil. But unlike
Phil, this plan just might work.
