» libmtp gets this week's OSS project WTF award

What a mess... Having to hack around upstream version numbers involving "rc", "alpha" or "beta" isn't fun but this one tops everything I've seen up to now: libmtp They released a new version today, 0.1.0. Of course, it breaks backwards compatibility and installs itself as libmtp.so.4. Their previous releases, 0.0.18 to 0.0.21 installed as libmtp.so.2. Now you might wonder why they went from .so.2 to .so.3 - in fact, their even older releases, up to 0.0.17 installed as libmtp.so.3. Let's summarize:

0.0.17 ......: libmtp.so.3
0.0.18-0.0.21: libmtp.so.2
0.1.0 .......: libmtp.so.4

Go figure. To fix all that upstream mess, my libmtp-0.1.0 package builds and ships libmtp.so.2 (from upstream 0.0.21), libmtp.so.3 (from upstream 0.0.17) and libmtp.so.4 (from upstream 0.1.0), in order to avoid breaking compatibility with existing packages. I've also rebuilt gnomad2 to compile and link against libmtp-0.1.0 (libmtp.so.4, that is). Packages will be on the mirrors in a few hours. Please let me know whether upgrading libmtp to 0.1.0 breaks something or whether it works for you. At least it seems to work fine with my latest amarok packages.