[Pkg-tigervnc-devel] Bug#763360: closed by Ondřej Surý <ondrej at sury.org>

[Ondřej Surý]

On Mon, Oct 6, 2014, at 21:14, Bill Allombert wrote:
> On Mon, Oct 06, 2014 at 11:54:06AM +0000, Debian Bug Tracking System
> wrote:
> > Date: Mon, 06 Oct 2014 13:52:42 +0200
> > From: Ondřej Surý <ondrej at sury.org>
> > To: Bill Allombert <ballombe at debian.org>, Andreas Barth <aba at ayous.org>
> > Cc: Emilio Pozuelo Monfort <pochu at debian.org>, 763360-done at bugs.debian.org
> > Subject: Re: Bug#763360: libjpeg-turbo is hijacking binaries from other
> >  source packages
> > X-Mailer: MessagingEngine.com Webmail Interface - ajax-257eafe9
> > 
> > Version: 1:1.3.1-4
> >
> > My understanding is that this bug can be now closed as
> > the libjpeg-progs are not built from src:libjpeg-progs and
> > libjpeg62* binary package names has been accepted now.
> 
> Excellent news! When do you plan to upload a version libjpeg-turbo that
> does not hijack libjpeg62 anymore ?

JFTR I will list the consequences of any renaming that would happen:

1. libjpeg-turbo62 (as an example) would still contain shared library
libjpeg.so.62, thus it needs to "Conflicts/Provides: libjpeg62", same
applies for the libjpeg62-dev package vs libjpeg-turbo62-dev
("Conflicts/Provides: libjpeg62-dev)

2. Thus libjpeg62 and libjpeg62-dev from src:libjpeg6b will be
uninstallable because libjpeg-turbo62 is a default JPEG library in
Debian and therefore it will be almost always present in the system
where JPEG library is needed. Well, even my stripped down KVM server box
has libjpeg library since qemu-kvm depends on it[1]. Installation of
libjpeg62 from src:libjpeg6b will be possible only in a very specialized
scenarios where the system is stripped down to a bare minimum.

3. yet another transition will be started and buildd cycles spent

Ondrej
-- 
Ondřej Surý <ondrej at sury.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server