On Sun, Oct 26, 2014 at 07:58:44AM +0100, Helge Kreutzmann wrote: > Hello, > I just ran into this as well. > > 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)
You only see the bug because libjpeg-turbo-progs has hijacked the libjpeg-progs package in jessie for a time, but no users of stable will have libjpeg-turbo-progs installed. I have no responsibility in the libjpeg-turbo-progs mess. > b) It is (more than) a courtesy for users / developers who run testing I agree with that one, but it is too late now. > 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. Indeed, that why libjpeg-turbo-progs -3 should have added Conflicts/Replaces but did not. Hence it was buggy. Since libjpeg-turbo-progs needs to Conflicts/Replaces libjpeg-progs because libjpeg-progs was in stable, there is no point in libjpeg-progs to also Conflicts/Replaces with libjpeg-turbo-progs. And anyway I cannot chnage the stable version which clearly does not. The real fix would be for libjpeg-turbo-progs to use different filename than libjpeg-progs and then use the alternative system. > 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. This would be pointless since the bug was in libjpeg-turbo-progs and is now fixed and is not more reproducible when starting from wheezy or current testing. The number of users still having the broken libjpeg-turbo-progs is smaller everyday. > > 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. The plan was that libjpeg-turbo-progs would be fixed in testing before libjpeg-progs 9-2 would move to testing. But the libjpeg-turbo-progs maintainers uploaded 5 new versions, which delayed the transition. Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
