I have prepared t-p-u upload based on reverted patch we already had in
libjpeg-turbo:
http://anonscm.debian.org/cgit/collab-maint/libjpeg-turbo.git/commit/?h=master-jessieid=a024ab84ab6181270713e2e3f181cbe887582124
I don't care whether we solve this in t-p-u or unstable as long as I
don't caught
On 2015-03-09 15:02, Ondřej Surý wrote:
Hmm, there's something fishy going on.
Installing jhead (Depends: libjpeg-progs) on wheezy and dist-upgrading
to jessie tries to remove jhead instead of pulling libjpeg-turbo-progs.
Installing jhead manually after dist-upgrade works fine.
Looks
Hmm, there's something fishy going on.
Installing jhead (Depends: libjpeg-progs) on wheezy and dist-upgrading
to jessie tries to remove jhead instead of pulling libjpeg-turbo-progs.
Installing jhead manually after dist-upgrade works fine.
Looks like we will need transitional package after all
On Sun, Mar 8, 2015, at 17:47, Niels Thykier wrote:
On 2015-03-08 16:47, Ondřej Surý wrote:
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},
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
On Sat, 07 Mar 2015 at 14:24:32 +0100, Ondřej Surý wrote:
was src:libjpeg9 ever part of jessie? E.g. should I bump epoch on the
upload?
https://tracker.debian.org/pkg/libjpeg9
[2014-10-17] libjpeg9 1:9a-2 MIGRATED to testing (Britney)
and that version's Changes say:
libjpeg9 (1:9a-2)
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.)
On 2015-03-08 16:47, Ondřej Surý wrote:
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
Hi Niels,
was src:libjpeg9 ever part of jessie? E.g. should I bump epoch on the
upload?
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?
Sorry it took so long, I almost forgot about this.
Cheers,
Source: libjpeg-turbo
Version: 1:1.3.1-11
Severity: serious
User: release.debian.org
Usertags: jessie-is-blocker
Hi,
It seems that there is no migration from libjpeg-progs to
libjpeg-turbo-progs. Given that we have decided to not ship libjpeg9
in Jessie (and by extension, libjpeg-progs), this
10 matches
Mail list logo
