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

Accepted libcdio 2.2.0-2 (source) into unstable



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

Format: 1.8
Date: Thu, 13 Mar 2025 21:19:48 -0700
Source: libcdio
Architecture: source
Version: 2.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Gabriel F. T. Gomes <gabriel@debian.org>
Changed-By: Gabriel F. T. Gomes <gabriel@debian.org>
Changes:
 libcdio (2.2.0-2) unstable; urgency=medium
 .
   * Make libiso9660 explicitly depend on libcdio19t64 version 2.2.0.
     - The ABI change in libiso9660 causes segmentation faults when a process
       using libiso9660 dynamically links the older version of libcdio.
     - The update makes Debian's libiso9660-12 depend on libcdio19t64 version
       2.2.0, instead of the old 2.1.0.
     - Notice how libcdio19t64 did not have its SONAME bumped.
     - Do the same for libcdio++ since libiso9660 also had an ABI break.
Checksums-Sha1:
 32057f782ad2eaf1e7ea6b3399bb892cf4763234 2585 libcdio_2.2.0-2.dsc
 56b65df7b177a8d4ee0374b2458d6f620189671c 12520 libcdio_2.2.0-2.debian.tar.xz
 f8f8c379a02d031401ac7b9ffbf839c1a50beb77 10615 libcdio_2.2.0-2_amd64.buildinfo
Checksums-Sha256:
 b6283864265075ea0e6071b0ff63072d7c6fef80446d1dc3ea62cd2fc2634b7a 2585 libcdio_2.2.0-2.dsc
 607711f4c0e28695fb2dfd55918bc17647040d1c2bcbed269c28371b6329a862 12520 libcdio_2.2.0-2.debian.tar.xz
 ecd4707d17bd7832cf3ed14e01a522341a1f21c79534b9420a0f3b5f534523aa 10615 libcdio_2.2.0-2_amd64.buildinfo
Files:
 c37ed4267d4ef26c41f3835c5183e1e1 2585 libs optional libcdio_2.2.0-2.dsc
 7ea7c459da3370b29802a187e50d03ca 12520 libs optional libcdio_2.2.0-2.debian.tar.xz
 e382360ae3e8d52c415809d122534c1b 10615 libs optional libcdio_2.2.0-2_amd64.buildinfo


-----BEGIN PGP SIGNATURE-----

iQJHBAEBCgAxFiEE+wUJHFVUA1wadvc8rpsRODhuyvIFAmfXUgMTHGdhYnJpZWxA
ZGViaWFuLm9yZwAKCRCumxE4OG7K8vkoD/9sg0coyKAW1QQdJSMkhiJvD9CGMMKX
/i90lZem28Ujjnmy3MejJcqpMhDKJ2vOiJN91u3sF19/SxFVObJZG19jlPfbhVFO
TDjjb82p1FFi2pheKIJJ4RoW+ywwjc1PhdSS0E0CDsnLoh5PXKzEGKYvUzbBHEwu
oWVefs4CG3X7xtXQDnjvvdzj6v2in7E29jGiR5Z1AbNOiNIZKnKG7NAzhgp7CPTo
tvNIk527VCK4xpJjAUT5TTsWs++q4znhT2CZtyii7+zbLYB6rNY63+DiEO+x66lx
0uPYBSe0bgmmP9/q7BKYHTgd4qGthJCLY94BDqPI2u9omK8HmQLtTPPnZCcHFmip
IBfGb6khAb45lOq0sDGV5eIJJNZXyMsHG7x1jfI6QKssL3ceIbcUDr+7eFRyYJxX
sHNAusPWY3EeBVvX54yGVCG0fCZMpAThH6zz3DC6v2oyg81+wqT6NO+Llf9IxmYq
DLsWkzWwUK2kqJmZnw7pZbD0rjTpKYS2Pbj5YnnAZS6DZPrQQdH79JVWF65T7v7h
Rj8myr6y/WpYAbxhZ0wIhmbShFR+xrD/3m8qxbeq5cHZTVtmbTngYxSkN8wteQCb
af3niLhfElkx5Ixy4Tc5kpAAeNG+KnLnQBS/x6VAB5TzpsBq6M4duLelCf9TZe8S
cOnEI0cwLyN3jA==
=QU6w
-----END PGP SIGNATURE-----

Attachment: pgpovWLSKZMsg.pgp
Description: PGP signature


Reply to: