[Pkg-gtkpod-devel] New packages uploads to experimental

[Yves-Alexis Perez]

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

Hey people,

as you may have noticed, upstream recently released tarballs for some of the
project under its umbrella.

I've started packaging and uploading things to experimental. Upstream changed
to library name on basically all libraries, so for example libplist.so.3 is
now libplist-2.0.so.3, while there is no symbols changed in that release.

Rather than renaming the packages, going through NEW and asking our
dependencies to update their builds, I've shipped compatibility symlinks in
the packages. 

So for example libusbmuxd6 contains:

/usr/lib/x86_64-linux-gnu/libusbmuxd-2.0.so -> libusbmuxd-2.0.so.6.0.0
/usr/lib/x86_64-linux-gnu/libusbmuxd-2.0.so.6 -> libusbmuxd-2.0.so.6.0.0

but also:

/usr/lib/x86_64-linux-gnu/libusbmuxd.so.6 -> libusbmuxd-2.0.so.6

and libusbmuxd-dev contains:

/usr/lib/x86_64-linux-gnu/libusbmuxd.so -> libusbmuxd-2.0.so
/usr/lib/x86_64-linux-gnu/pkgconfig/libusbmuxd.pc -> libusbmuxd-2.0.pc

That should transparently allow dependencies to run against newer libusbmux
(et al.) as well as build correctly.

Sebastien Bacher (on CC:) should be able to do some build and run tests on
dependencies (mostly GNOME).

If noone stop any obvious mistake I did, I'll proceed to the upload to
unstable, likely next week.

I'll also take a look at the other packages we might have.

Regards,
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl7qRc8ACgkQ3rYcyPpX
RFu3SQgAwL7pERogJRCLVe6LooYH7PYHJca1A26pjiJSKPnKLsovieywvq30/Gmw
+Q8FE1c4q9WB1LlE+FLUKqw4Cq50JItkVoF7k8PuF+C1aD3FaRZIDFB/BHJ5Ahft
ZfqJxo4iK7qGmW+7zpA2RIJMLFv8e5yxrBZb3ijVNUCRxOqhQhZRRgZ88LHLM8Z2
KJWS01Bgv3EbwSDs2Vn27G5UMEu7vT++UR1W/m2Zl7jvy2PStEH4NCpOLx5oU4KK
7TtxgWOE8DZh/ve7Xi0umCypcE5vgi46a5yjQ8zNgNjXjzUgo3FOpgWes6yGV7ok
cifmU0nedigdSol9jg7KYls03fgcXw==
=+gfN
-----END PGP SIGNATURE-----