Hi Niels,
what if I just do:
Package: libjpeg62-turbo
[...]
Conflicts: libjpeg-progs (>> 2:0), libjpeg-progs (<< 1:0)
(or more precise Conflicts: libjpeg-progs (>> ${binary:Version},
libjpeg-progs (<< ${binary:Version})
That should push libjpeg-progs from other sources out
Cheers,
Ondrej
On Sun, Mar 8, 2015, at 16:42, Niels Thykier wrote:
> On 2015-03-07 14:24, Ondřej Surý wrote:
> > Hi Niels,
> >
>
> Hi,
>
> :)
>
> > was src:libjpeg9 ever part of jessie? E.g. should I bump epoch on the
> > upload?
> >
>
> I believe Simon covered this one.
>
> > Also do you think I should fill bug on libjpeg9 asking maintainer to
> > rename libjpeg-progs to (f.e.) libjpeg9-progs to have a plan for
> > jessie+1?
> >
>
> Honestly, I think it is best if only changed libjpeg-turbo at this
> point. At least, I suspect that is the least controversial solution and
> also the fastest one to implement.
> Mind you, I assume here that this is in fact possible without actually
> having looked at the technical details.
>
> I do certainly not mind if it takes an upload testing-proposed-update,
> if we can solve it that way.
>
> > Sorry it took so long, I almost forgot about this.
> >
> > Cheers,
> > Ondrej
> >
>
> Don't worry and thanks for picking it up again, :)
> ~Niels
>
>
--
Ondřej Surý <ond...@sury.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
