Hello, I just ran into this as well. On Sat, Oct 25, 2014 at 06:56:05PM +0200, Bill Allombert wrote: > On Sat, Oct 25, 2014 at 05:57:39PM +0200, Michael Banck wrote: > > severity 766353 serious > > thanks > > > > On Wed, Oct 22, 2014 at 04:30:54PM +0200, Bill Allombert wrote: > > > On Wed, Oct 22, 2014 at 03:20:41PM +0200, Rafael Belmonte wrote: > > > > Package: libjpeg-progs > > > > Version: 1:9a-2 > > > > Severity: important > > > > > > > > --- Please enter the report below this line. --- > > > > The package is not installable or upgradable if libjpeg-turbo-progs > > > > is already installed. > > > > This is the apt-get output: > > > > dpkg: error processing archive > > > > /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_i386.deb (--unpack): > > > > trying to overwrite '/usr/share/man/man1/exifautotran.1.gz', which > > > > is also in package libjpeg-turbo-progs 1:1.3.1-3 > > > > I ran into this as well just now when upgrading jessie. > > > > > Indeed, you need to remove the broken libjpeg-turbo-progs 1:1.3.1-3 > > > before the upgrade. Later version of libjpeg-turbo-progs are fixed. > > > > Erm, in that case, there should be additional Conflicts/Replaces > > whatever relationships, methinks? > > libjpeg-turbo-progs 1:1.3.1-3 is RC buggy and has never been part of a stable > release, so I do not think this is necessary.
Why?
a) On my machine, which run stable up to about ~1.5 month ago I never
explicitly installed libjpeg-turbo-progs, so stable users who upgrade
are most likly affected.
(I only run dist-ugprade)
b) It is (more than) a courtesy for users / developers who run testing
c) RC-buggy packages are removed from the testing suite in the
archives, but not from users machines
(and, btw. libjpeg-turbo is no longer rc-buggy)
d) Looking at debian-policy, I read:
It is usually an error for a package to contain files which
are on the system in another package.
I do not see an exception for rc-buggy relationships or such.
Further as I understand it, it is the normal procedure for taking
over files, to use breaks/replaces.
e) Is there any problem of uploading libjpeg-progs just with the
appropriate breaks/relationship? I think the RMs would have no
problem accelerating this into testing.
> The cause of the breackage you see is that the fixed libjpeg-turbo-progs
> 1:1.3.1-d for d>3 reached much later than I expected and in particular after
> libjpeg-progs 9-2.
Sorry, I don't understand this sentence.
Greetings
Helge
--
Dr. Helge Kreutzmann deb...@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: Digital signature
