Hello Don,
I am just checking whether the tech-ctte has all the info they need to
make informed decision on this bug, or do you need any extra input? E.g.
take all the time you need, but I want to be sure that it's not stalled
on my or Mike's side and you are waiting for something from us now.
Ch
On Tue, Jul 23, 2013 at 02:52:43PM -0700, Don Armstrong wrote:
> 1) Does libjpeg-turbo (LJT) now completely support the libjpeg8 ABI?
I think it is more relevant to follow the ABI used by the rest of Linux
community. Pretty much everyone but Debian is moving to LJT, most users
still using the IJG
Hi Ondřej,
On Fr 26 Jul 2013 13:43:05 CEST Ondřej Surý wrote:
On Thu, Jul 25, 2013 at 6:16 PM, Don Armstrong wrote:
On Thu, 25 Jul 2013, Mike Gabriel wrote:
> I have been using the compat mode in LJT since Debian squeeze. As
> part of upstream X2Go I build packages just like the one in Debia
Hi Don, et al.
On Do 25 Jul 2013 18:16:06 CEST Don Armstrong wrote:
On Thu, 25 Jul 2013, Mike Gabriel wrote:
I have been using the compat mode in LJT since Debian squeeze. As
part of upstream X2Go I build packages just like the one in Debian
but with compat mode enabled. The packages (still 1.
On Thu, Jul 25, 2013 at 6:16 PM, Don Armstrong wrote:
> On Thu, 25 Jul 2013, Mike Gabriel wrote:
> > I have been using the compat mode in LJT since Debian squeeze. As
> > part of upstream X2Go I build packages just like the one in Debian
> > but with compat mode enabled. The packages (still 1.2.9
On Thu, Jul 25, 2013 at 09:16:06AM -0700, Don Armstrong wrote:
> On Thu, 25 Jul 2013, Mike Gabriel wrote:
> This is a good start. However, the package should also build libjpeg-dev
> or whatever is appropriate so that the transition can be completely
> tested. It would also be good to have all of t
On Thu, 25 Jul 2013, Mike Gabriel wrote:
> I have been using the compat mode in LJT since Debian squeeze. As
> part of upstream X2Go I build packages just like the one in Debian
> but with compat mode enabled. The packages (still 1.2.90) can be
> obtained from
>
> deb http://packages.x2go.org/deb
On Wed, Jul 24, 2013 at 09:10:51AM +0200, Ondřej Surý wrote:
> Compression several replies into one.
>
> > Couple of quick questions:
> >
> > 1) Does libjpeg-turbo (LJT) now completely support the libjpeg8 ABI?
>
> AFAIK it doesn't support the SmartScale, but it does support full libjpeg8
> ABI.
Hi Don, hi Ondřej, dear Committee members, dear all,
On Mi 24 Jul 2013 09:38:23 CEST Don Armstrong wrote:
Thus I think this needs a decision from tech-ctte before we make the
switch to different implementation of libjpeg.
I'm personally concerned about switching from IJG to an as-of-yet
untes
On Wed, 24 Jul 2013, Ondřej Surý wrote:
> > Finally, it doesn't currently look like the libjpeg-turbo packages are
> > at all in a state to replace the libjpeg8 or libjpeg6b packages. I'm not
> > sure why the CTTE should rule to replace the IJG packages when the work
> > and testing necessary to ma
Compression several replies into one.
> Couple of quick questions:
>
> 1) Does libjpeg-turbo (LJT) now completely support the libjpeg8 ABI?
AFAIK it doesn't support the SmartScale, but it does support full libjpeg8
ABI.
More on the ABI compatibility can be read in the article where LJT author
ex
On Tue, 23 Jul 2013, Don Armstrong wrote:
> http://bugs.debian.org/632949 has more information from a previous
> discussion around 2011; I'm Cc:'ing that bug to make sure the logs have
> a connection between the two.
The ITP for libjpeg-turbo also has some emails:
http://bugs.debian.org/cgi-bin/bu
On Tue, Jul 16, 2013 at 04:08:33PM +0200, Ondřej Surý wrote:
> Package: tech-ctte
> Severity: normal
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dear Technical Committee,
>
> I have raised the question of libjpeg8 vs. jpeg-turbo as a default
> libjpeg library for Debian in debian-dev
http://bugs.debian.org/632949 has more information from a previous
discussion around 2011; I'm Cc:'ing that bug to make sure the logs have
a connection between the two.
Couple of quick questions:
1) Does libjpeg-turbo (LJT) now completely support the libjpeg8 ABI?
2) Do we have benchmark results
On 17/07/13 22:49, Ian Jackson wrote:
> Perhaps we could just patch our libjpeg6b to have the necessary
> function. It sounds like an API deficiency that it's missing.
It appears that libjpeg-turbo 1.3+ has a libjpeg8-compatible
jpeg_mem_(src|dest) by default, even if it's told to implement a
lib
Simon McVittie writes ("Bug#717076: tech-ctte: Decide what jpeg library the
Debian project will use"):
> Upstream's solution was to bundle libjpeg-6b plus a copy of the memory source,
> then later to upgrade their bundled libjpeg to libjpeg-8c. Debian's solution
> w
On Wed, 2013-07-17 at 21:29:58 +0200, Florian Weimer wrote:
> * Simon McVittie:
> > That package might have been ioquake3, which needs the jpeg_mem_src from
> > libjpeg8 (I think it was actually added in libjpeg7) to allow decoding
> > JPEGs from a memory buffer instead of a libc FILE*. I suspect t
* Simon McVittie:
> That package might have been ioquake3, which needs the jpeg_mem_src from
> libjpeg8 (I think it was actually added in libjpeg7) to allow decoding
> JPEGs from a memory buffer instead of a libc FILE*. I suspect that's
> a somewhat common use-case, and it isn't part of the libjpe
On Tue, 16 Jul 2013 at 16:08:33 +0200, Ondřej Surý wrote:
> I think we can use the libjpeg8 compatibility layer of libjpeg-turbo.
>
> Although I am not sure if it is really needed as there was only one
> package needing new API from libjpeg8 I have heard and that should be
> trivial to fix.
That
Package: tech-ctte
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Technical Committee,
I have raised the question of libjpeg8 vs. jpeg-turbo as a default
libjpeg library for Debian in debian-devel[1], but we were not able to
reach a consensus. I spoke to our DPL and he reco
20 matches
Mail list logo
