[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#754988: marked as done (transition: libjpeg-turbo)

Your message dated Tue, 06 Jan 2015 21:03:29 +0100
with message-id <54AC3F91.8010500@thykier.net>
and subject line Re: Bug#754988: transition: libjpeg-turbo
has caused the Debian Bug report #754988,
regarding transition: libjpeg-turbo
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
754988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754988
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

As voted by tech-ctte in #717076, we are going to prepare the
transition from IIJ jpeg to libjpeg-turbo implementation.

The transition plan as asked in the resolution:

1. Since nothing depends on libjpeg8 API we will bump back to
   libjpeg.so.62 with extra "decode from memory buffer" interface
   (jpeg_mem_src/jpeg_mem_dest).

   NOTES:
   * Fedora/OpenSUSE has also settled down on libjpeg.so.62, so that
     would make us cross-distro compatible.

   * Ubuntu has already transitioned to libjpeg-turbo8, so it will be
     up to them if they bump back to libjpeg62.

2. The proposed libjpeg-turbo packages implementing libjpeg62 will be
   uploaded to experimental before end of July 2014.  We will announce
   that to debian-devel and leave a reasonable period of time for
   people to test their packages to recompile against libjpeg-turbo.

   I propose we provide libjpeg-dev dummy (not virtual) package in
   experimental, so there's no clash between libjpeg8-dev and
   libjpeg-turbo-dev.

3. The updated libjpeg-turbo packages implementing libjpeg62 and
   libjpeg-turbo-dev (providing libjpeg-dev virtual package) will be
   uploaded to unstable at the end of August 2014.  This upload will
   be synchronized with libjpeg8 maintainer (or NMUed) to remove
   virtual libjpeg-dev from libjpeg8-dev at the same time (or very
   close to it).

Cheers,
Ondrej

Ben file:

title = "libjpeg-turbo";
is_affected = .depends ~ "libjpeg8" | .depends ~ "libjpeg62";
is_good = .depends ~ "libjpeg62";
is_bad = .depends ~ "libjpeg8";


- -- System Information:
Debian Release: 7.5
  APT prefers stable
  APT policy: (900, 'stable'), (800, 'testing'), (700, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJTxp6iAAoJEAyZtw70/LsHiREQAKkK/frYX82dgEL4EPzbybmm
CagX8tN9apnL5LGOddMrrCn5TznvGY6Wgz7Tq1JPqKoVUWUmeeoHt2Ofj7lOjwex
AfpALupSQEv0nJSHZJj8nwotMnZemFifHnmg+T7+aQaswcFpVxsyVjuS5EN5rTI2
BIUs1ar7t9MPlkskOEPrDv6hJE01PTMW5MDDI2pEDRNtCUdiLIgWG7TVaiH4Am9Y
81FbV2y9MYXOhzqDo1MpdLT6tsgbP4PQbIjVGAPTCVhrcCYv/HlpvdcD2PIrYVc+
KXgFFQVFs1ppwElYobEmXmy5dlAIawW9uFGwCSjHofOBp08gDV/5yXDmFDqqfuOr
e/6YsvIA/tlnF/CM2gmAJbRnKJc867DGyVM3GmKWOgEOvGQXq5wh1MUwSdDcAL+t
UP1Wo8PHoUTe5Eq+yz5gK51qaM+9YabNOaVvw61j6LFrWfOfZv7eHMGYjhKjPaJd
2aPZS/onKcKB3yLGAIENOpxogoVZNfZ2FsNUWdE5YfXwRDLAkSd2R8QGGwy2mefT
5s6s6SbZqwPn27h4hN3qxHRvcnYt+izH9SY6zokqX+6u0GzbSCO4BAd0cGB4Agh0
9jV+ew/BrmHUKI/dJGfKZ50rQFTumPjBObr4Ci46Cmi+e+C9qJ2qA3Zgz100YU6f
UlvdYPNK/7OfPwBDB648
=GTZa
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
On 2014-07-16 17:47, Ondřej Surý wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: transition
> 
> As voted by tech-ctte in #717076, we are going to prepare the
> transition from IIJ jpeg to libjpeg-turbo implementation.
> 
> The transition plan as asked in the resolution:
> 
> [...]
> 
> Cheers,
> Ondrej
> 
> Ben file:
> 
> [...]

Hi,

I believe this transition is over, so lets close this bug.

Ondrej: Thanks for your hard work on this one. :)

~Niels

--- End Message ---
Reply to: