Bug#1020911: marked as done (libaacs0: still references libbluray1)
Your message dated Fri, 10 Feb 2023 17:21:00 +0000
with message-id <E1pQX52-000DKU-Hy@fasolo.debian.org>
and subject line Bug#1020911: fixed in libaacs 0.11.1-2
has caused the Debian Bug report #1020911,
regarding libaacs0: still references libbluray1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1020911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020911
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libaacs0
Version: 0.9.0-2
Severity: normal
Dear maintainers,
libbluray1 was replaced by libbluray2 more than five years ago, but here
in debian/control there is still 'Enhances: libbluray1' instead of
'Enhances: libbluray2'. Could you please adapt this line?
Thank you in advance!
Thomas Uhle
-- System Information:
Debian Release: 11.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf
Kernel: Linux 5.10.0-18-arm64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libaacs0 depends on:
ii libc6 2.31-13+deb11u4
ii libgcrypt20 1.8.7-6
ii libgpg-error0 1.38-2
Versions of packages libaacs0 recommends:
ii libbdplus0 0.1.2-3
libaacs0 suggests no packages.
--- End Message ---
--- Begin Message ---
Source: libaacs
Source-Version: 0.11.1-2
Done: Dylan Aïssi <daissi@debian.org>
We believe that the bug you reported is fixed in the latest version of
libaacs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1020911@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dylan Aïssi <daissi@debian.org> (supplier of updated libaacs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 10 Feb 2023 17:44:51 +0100
Source: libaacs
Architecture: source
Version: 0.11.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Changed-By: Dylan Aïssi <daissi@debian.org>
Closes: 1020911
Changes:
libaacs (0.11.1-2) unstable; urgency=medium
.
* Team upload.
* libaacs0: enhances libbluray2 instead of libbluray1 (Closes: #1020911)
* Standards-Version: 4.6.2 (no changes required)
Checksums-Sha1:
e232b57ba04de68210d91d72472a5af3e573f553 2051 libaacs_0.11.1-2.dsc
c05a7f4b39ec2370773e51de12668519091df1e4 4472 libaacs_0.11.1-2.debian.tar.xz
7ab12bb0dd88771d8c5f09aaee919ca7a3e03b5b 6635 libaacs_0.11.1-2_amd64.buildinfo
Checksums-Sha256:
f91b07210cb2aac34a02abd2abd5b4e090375252ad60878e2631d3123d93a485 2051 libaacs_0.11.1-2.dsc
2c617ea3fc16d3815169165935c246aa88e144941b9cdbcfae63dd315ca39f4a 4472 libaacs_0.11.1-2.debian.tar.xz
451b440997bb54db2a717416261933fcb7f0081b3b484edad3563292a9718cc0 6635 libaacs_0.11.1-2_amd64.buildinfo
Files:
1d7b34d1a70fdbe6f820a6bf0d39a8ec 2051 video optional libaacs_0.11.1-2.dsc
0b4303b6a65070c3171e5e50cafa4f67 4472 video optional libaacs_0.11.1-2.debian.tar.xz
4170626db679afdaf82a4fedd9ea1abf 6635 video optional libaacs_0.11.1-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAmPmdSgACgkQYS7xYT4F
D1Sf2g/7BwZURXFFNQeB0cekE1euYWT7mqBPFTuy92vz7vw1OGB+Q+ikZpkRyYB9
NVoHmcrAQjgtwEHmNZu3APSP8CsN1D316ZIwn3j13GWuqqeWjmOF/iU/QDWL7Na9
6Wjj0aStHoRWPwJhOGbbzc3PiDlBCJ+tRGWaB5Pnj6CakXgBtrv4hdromd5Y+ej7
+LRD9+NVDBgbaWDQHLks66Gum9XG5U7XnLjqZ9W/WP5rbIBRlwbmD+xSUWo5X3GX
6WOpD7r0gqvUMic74WP+DVIL933NpYrpGXE17dy/mN5q5GbU/Bg0Jcqu9IjnowEg
BLwXKmS+QMThB047eR/NhHaNeZIFZEV6o6UayOPwAhYJ52b4I/+GyR/Vi8GtHmxh
PLVRQngPj0YJ8LrArI1+0z6SnIJ4tWlImpUSPzcfFBgL+YZhKm5DmTwMwdqRZ5v/
jh1m1B/Vi3dydo2hYCGuBN7sQmVJR65g6TiVNJ2tVj8k3r7VEI5ATtZr1tOAPenR
5iBhOxbZCGegCkYz32kDzOLZAEK5Ni56vZIckYiSWWN9OiHRcZLYPi/YYXdf7vjK
HNduAl6QoHSlhkBfg0h9zqr5S35INpYf9UilVnACyHhCarPX4SmJmWOwRPs4MFyp
C74Z0HdcY768037AHmgLrL4/syJ/Qr24Zyp04fAM2yE7LqwYMOQ=
=UL4R
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: