Hi, got a problem report via the fediverse.
== Background libassuan-3.0.0.tar.bz2 came on 2024-06-18 and six days later there is 3.0.1 as quick-release upgrading the soname to what it should have been (see citation below). == Problem description Arch Linux packaged the 3.0.0 release and has problems upgrading from it now. Here is the problem description: " with the release of 3.0.0 the soname changed from libassuan.so.0 to libassuan.so.9. Only with 3.0.1 the symbols have been changed from LIBASSUAN_1.0 to LIBASSUAN_2.0 (which is the ABI breaking change that the soname change is supposed to indicate). Since #pacman requires the library transitively via #gpgme, there now is no clean way to upgrade this without patching all consumers in some intermediate step. (The staging build environment would otherwise have a broken pacman and thus not be functional). We are stuck on 3.0.0 because our packaging environment now requires libassuan.so.9 with symbols LIBASSUAN_1.0. " Does anybody have some ideas how to solve this for Arch Linux in an elegant and efficiant way? Best Regards, Bernhard On 2024-06-24 Werner Koch <[email protected]> wrote: > On Sat, 22 Jun 2024 18:18, Andreas Metzler said: > > Could you do a quick 3.0.1 release to fix this before it has found its > > way into the major distributions? > > Just did this: > > #+macro: libassuan_ver 3.0.1 > #+macro: libassuan_date 2024-06-24 > #+macro: libassuan_size 578k > #+macro: libassuan_sha1 776aac6fe4a64f29406bb498e0b2b73f2622c799 > #+macro: libassuan_sha2 > c8f0f42e6103dea4b1a6a483cb556654e97302c7465308f58363778f95f194b1 > > 776aac6fe4a64f29406bb498e0b2b73f2622c799 libassuan-3.0.1.tar.bz2 -- https://intevation.de/~bernhard +49 541 33 508 3-3 Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Gnupg-devel mailing list [email protected] https://lists.gnupg.org/mailman/listinfo/gnupg-devel
