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

Bug#763480: libindi: Please change build dependency to libjpeg-dev (libjpeg-turbo transition)



Source: libindi
Version: 0.9.8.1-5
Severity: important
Tags: patch
User: ondrej@debian.org
Usertags: libjpeg-turbo-transition

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Dear maintainer(s),

Debian is transitioning from IJG JPEG library (src:libjpeg8) to
libjpeg-turbo implementation (src:libjpeg-turbo)[1] of libjpeg62 API
with "decode from memory buffer" interface (jpeg_mem_{src,dest}).

Your package cannot be transitioned automatically as it explicitly
build depends on specific API/ABI (libjpeg8-dev) and this build
dependency needs to be changed to libjpeg-dev.  In most if not all
cases this should be sufficient to build against libjpeg-turbo.

I am in process of testing each package in question to compile against
libjpeg-turbo and I will provide a suitable patch for each package
when I will succeed.

On the other hand please note that the winter^Wfreeze is coming and
if your package is not updated in due time it might be NMUed by the
release team (or by me with the full ack of release team).

That also means that if you are OK with NMU then please respond to
this bug report and I will prepare and upload the recompiled packages
for you.

Cheers,
Ondrej

1. The full Technical Committee decision can be found here:
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717076#235

- -- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, '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

iQJ8BAEBCgBmBQJUKqrOXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHY9AQALBFlLRbUWZzeR3WOpdkjDhE
baaNHaXrGqOi7mrQ28KcGEZcbFaWTt4S2PPvgoC8XIAQSAz2NWEbRiTCcA69dP0m
bqhuZrTJoOGkY/5S8D4zZdSRoqKQmjuaG8hwzYFF0h6GV/q0LWr7EWk/nQE/MEWN
37M/rS/6W2zunNc/ven4tpS5LjbPSb35QBwuVIBCnGzeTWUKpoiNooUyyKZc2xrm
dN/A61Pp7RI9idWTWTWhMqDEJXrkV47KRpo6fNpxraO0q547npnAq+4Ipsnta8/T
P5glcu7h/S58UdwXpsqoVJoHgnHv1pbczERjxEaUQHFiaRe5Veh7eJ6v7QdK8lrG
TvrxJrYAUDEvG1KVjIht/w67vtq+cYBfhFURhlRQ9yu2/dRY3BIWSa7OlO5G41qz
m8AMdRginua1zP5Y7PR7hIoA5hkI3zRlsUnNMcpo0RWGriUgtdbi7Zih6eWXThzA
nxjmGslHt7rpbKkbEwvXl03gdexFjXG0+jgS3fjJfkcq0laiFfJxiP8LbRMdxNDI
7EfWbAHy7an7HrRN9yaDpLBBNdCUT2K+RG51fe3wPsPKAkTwCuKk9t6bQX9wlgIc
C989I0wQUKB22lchmkiWCJNN2q67ji3L5bXDxgebcYdzDtsxO2S9oy2Z+/GCjb2C
T50e2FiGm1nsjnLp+nV+
=6iQw
-----END PGP SIGNATURE-----


Reply to: