Processed: Re: Bug#1072038: ffmpeg: [patches] avoid VA-API failures with modern Mesa3D
Processing control commands: > tags -1 upstream Bug #1072038 [ffmpeg] ffmpeg: [patches] avoid VA-API failures with modern Mesa3D Added tag(s) upstream. -- 1072038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1072339 is serious, severity of 1072398 is serious, severity of 1072399 is serious ...
n/bugreport.cgi?bug=1072449 1072450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072450 1072451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072451 1072453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072453 1072455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072455 1072456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072456 1072457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072457 1072462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072462 1072463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072463 1072464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1076567: marked as done (ffmpeg: Please break build dependency loop through libcaca)
Your message dated Sun, 28 Jul 2024 17:49:55 + with message-id and subject line Bug#1076567: fixed in ffmpeg 7:7.0.1-3 has caused the Debian Bug report #1076567, regarding ffmpeg: Please break build dependency loop through libcaca 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 ow...@bugs.debian.org immediately.) -- 1076567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ffmpeg Version: 7:6.1.1-4+b4 Severity: important Hello, We have a build dependency loop: ffmpeg <- libcaca-dev <- libcaca <- libimlib2-dev <- imlib2 <- libheif-dev <- libheif <- libavcodec-dev <- ffmpeg Could you make the libcaca-dev build-dependency to break this loop? Thanks, Samuel -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'unreleased'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 6.9.8-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ffmpeg depends on: ii libavcodec607:6.1.1-4+b4 ii libavdevice60 7:6.1.1-4+b4 ii libavfilter97:6.1.1-4+b4 ii libavformat60 7:6.1.1-4+b4 ii libavutil58 7:6.1.1-4+b4 ii libc6 2.38-14 ii libpostproc57 7:6.1.1-4+b4 ii libsdl2-2.0-0 2.30.4+dfsg-1 ii libswresample4 7:6.1.1-4+b4 ii libswscale7 7:6.1.1-4+b4 ffmpeg recommends no packages. Versions of packages ffmpeg suggests: pn ffmpeg-doc -- no debconf information -- Samuel "c'est pas nous qui sommes à la rue, c'est la rue qui est à nous" --- End Message --- --- Begin Message --- Source: ffmpeg Source-Version: 7:7.0.1-3 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of ffmpeg, 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 1076...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated ffmpeg 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 28 Jul 2024 19:13:03 +0200 Source: ffmpeg Architecture: source Version: 7:7.0.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 1076567 Changes: ffmpeg (7:7.0.1-3) unstable; urgency=medium . [ Bastian Germann ] * Build with libssh's default flavor . [ Sebastian Ramacher ] * Upload to unstable * debian/: Disable libcaca in stage1 (Closes: #1076567) Checksums-Sha1: fc0d966c2546132de948a6135e3c20b0593662a5 5820 ffmpeg_7.0.1-3.dsc 22711d9e732d4dc44c6363f57ba7d230d01aec19 53600 ffmpeg_7.0.1-3.debian.tar.xz fcd3e31675a10ded30c4cc9bce8bd99de544ad0f 33273 ffmpeg_7.0.1-3_amd64.buildinfo Checksums-Sha256: 237436cfd3141b2a05fac6faec8708877af479caad1d7d864dbd251e05ef3c4c 5820 ffmpeg_7.0.1-3.dsc 32caaf3601e46f20df64033ad3fb3d0c03beb9960f4ca346c8ba6ae55ec11ee3 53600 ffmpeg_7.0.1-3.debian.tar.xz 0c51f65a596a546e11cf842a39cadb504eec8c49dd9994318bdec600d09651ef 33273 ffmpeg_7.0.1-3_amd64.buildinfo Files: f41f5e72578773b790a7b5c5a7df37ae 5820 video optional ffmpeg_7.0.1-3.dsc 24ddf22fe8d50f528de38a1bf8aec6f5 53600 video optional ffmpeg_7.0.1-3.debian.tar.xz bdddf4b94d7a40913b7a5a023d198b98 33273 video optional ffmpeg_7.0.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZqaA2AAKCRAhk2s2YA/N iZXBAP0dQ9pnu34XZSreZGXArKVsXK0mQE7FmZEA8twsLYqxCQD/QfIws9cTp02b 77B10GKO4NldKVr+Sk0ZQMMLOpyi+AA= =Ko89 -END PGP SIGNATURE- pgp4wOEp2Mnbw.pgp Description: PGP signature --- End Message ---
Processed: found 1074370 in ffmpeg/7:6.1.1-4
Processing commands for cont...@bugs.debian.org: > found 1074370 ffmpeg/7:6.1.1-4 Bug #1074370 [src:ffmpeg] Enable asm support on armel and armhf Ignoring request to alter found versions of bug #1074370 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1074370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1074370
Processing commands for cont...@bugs.debian.org: > tags 1074370 - ftbfs Bug #1074370 [src:ffmpeg] Enable asm support on armel and armhf Removed tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1077262: marked as done (libheif1:i386: :i386 not co-installable with :amd64?)
Your message dated Sun, 28 Jul 2024 00:20:57 +0200 with message-id and subject line Re: Bug#1077262: libheif1:i386: :i386 not co-installable with :amd64? has caused the Debian Bug report #1077262, regarding libheif1:i386: :i386 not co-installable with :amd64? 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 ow...@bugs.debian.org immediately.) -- 1077262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077262 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libheif1 Version: 1.17.6-4+b3 Severity: normal X-Debbugs-Cc: ole.laur...@gmail.com I'm trying to install the wine32 package but can't as something is depending on libheif1:386 which won't install. If I try to install the libheif1:386 packages manually, it looks like apt tries to remove the :amd64 versions and thus GNOME. Not sure why, but I noticed libheif1:i386 is +b3 and libheif1:amd64 is +b2? Anyway, I'm stuck and can't install wine32. Here's the output: sudo apt install 'libheif-plugin-libde265:i386' 'libheif1:i386' 'libheif-plugin-aomdec:i386' [...] Installing: libheif-plugin-aomdec:i386 libheif-plugin-libde265:i386 libheif1:i386 Installing dependencies: emacs-pgtk libde265-0:i386 libheif-plugin-aomenc:i386 libheif-plugin-x265:i386 Suggested packages: emacs-common-non-dfsg libheif-plugin-jpegdec:i386 libheif-plugin-j2kdec:i386 libheif-plugin-kvazaar:i386 libheif-plugin-svtenc:i386 libheif-plugin-ffmpegdec:i386 libheif-plugin-jpegenc:i386 libheif-plugin-j2kenc:i386 libheif-plugin-rav1e:i386 REMOVING: colord gnome-color-manager gnome-core heif-gdk-pixbuf libc-devtools libgphoto2-6t64libheif-plugin-dav1d libheif1 libmagickcore-6.q16-7-extra libmagickwand-6.q16-7t64 libwine simple-scan wine64 emacs-gtk gnome-control-center gvfs-backends heif-thumbnailer libgd3 libheif-plugin-aomdec libheif-plugin-libde265 libm17n-0 libmagickcore-6.q16-7t64 libsane1 sane-utils wine xiccd Summary: Upgrading: 0, Installing: 7, Removing: 26, Not Upgrading: 0 Download size: 7.446 kB / 7.642 kB Freed space: 723 MB Continue? [J/n] n -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.12-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- On 2024-07-27 15:40:01 +0200, Ole Laursen wrote: > Package: libheif1 > Version: 1.17.6-4+b3 > Severity: normal > X-Debbugs-Cc: ole.laur...@gmail.com > > I'm trying to install the wine32 package but can't as something is > depending on libheif1:386 which won't install. If I try to install the > libheif1:386 packages manually, it looks like apt tries to remove the > :amd64 versions and thus GNOME. Not sure why, but I noticed > libheif1:i386 is +b3 and libheif1:amd64 is +b2? Scheduled binNMUs to fix the version skew. Cheers > > Anyway, I'm stuck and can't install wine32. Here's the output: > > sudo apt install 'libheif-plugin-libde265:i386' 'libheif1:i386' > 'libheif-plugin-aomdec:i386' > [...] > > Installing: > libheif-plugin-aomdec:i386 libheif-plugin-libde265:i386 libheif1:i386 > > Installing dependencies: > emacs-pgtk libde265-0:i386 libheif-plugin-aomenc:i386 > libheif-plugin-x265:i386 > > Suggested packages: > emacs-common-non-dfsg libheif-plugin-jpegdec:i386 > libheif-plugin-j2kdec:i386 libheif-plugin-kvazaar:i386 > libheif-plugin-svtenc:i386 > libheif-plugin-ffmpegdec:i386 libheif-plugin-jpegenc:i386 > libheif-plugin-j2kenc:i386 libheif-plugin-rav1e:i386 > > REMOVING: > colord gnome-color-manager gnome-core heif-gdk-pixbuf > libc-devtools libgphoto2-6t64libheif-plugin-dav1d libheif1 > libmagickcore-6.q16-7-extra libmagickwand-6.q16-7t64 libwine > simple-scan wine64 > emacs-gtk gnome-control-center gvfs-backends heif-thumbnailer libgd3 > libheif-plugin-aomdec libheif-plugin-libde265 libm17n-0 > libmagickcore-6.q16-7t64 libsane1 sane-utils wine > xiccd > > Summary: > Upgrading: 0, Installing: 7, Removing: 26, Not Upgrading: 0 > Download size: 7.446 kB / 7.642 kB > Freed space: 723 MB > > Continue? [J
Bug#1072584: marked as done (Fwd: ffmpeg installation on testing trixie results install 6.1 while sudo update reports 7.1.)
Your message dated Sun, 28 Jul 2024 00:16:45 +0200 with message-id and subject line Re: Bug#1072584: Fwd: ffmpeg installation on testing trixie results install 6.1 while sudo update reports 7.1. has caused the Debian Bug report #1072584, regarding Fwd: ffmpeg installation on testing trixie results install 6.1 while sudo update reports 7.1. 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 ow...@bugs.debian.org immediately.) -- 1072584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ffmpeg Version: 6.1.1-4+b2 ffmpeg installation on testing trixie results install 6.1.1-4+b2 while sudo update reports 7.1. --- End Message --- --- Begin Message --- On 2024-06-04 14:52:27 -0500, elias wrote: > Package: ffmpeg > > Version: 6.1.1-4+b2 > > ffmpeg installation on testing trixie results install 6.1.1-4+b2 while sudo > update reports 7.1. The ffmpeg version in trixie is currently 6.1.1-5. If you see a version starting with 7, that is experimental. I see no bug here. Cheers -- Sebastian Ramacher--- End Message ---
Processed: Bug#1076567 marked as pending in ffmpeg
Processing control commands: > tag -1 pending Bug #1076567 [ffmpeg] ffmpeg: Please break build dependency loop through libcaca Added tag(s) pending. -- 1076567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033992: marked as done (tiatracker FTCBFS: hard codes the build architecture qmake)
Your message dated Sat, 27 Jul 2024 15:21:40 + with message-id and subject line Bug#1033992: fixed in tiatracker 1.3-5 has caused the Debian Bug report #1033992, regarding tiatracker FTCBFS: hard codes the build architecture qmake 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 ow...@bugs.debian.org immediately.) -- 1033992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tiatracker Version: 1.3-3 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs tiatracker fails to cross build from source, because debian/rules hard codes the build architecture qmake. Just deferring it all to dh_auto_configure fixes the cross build. I'm attaching a patch for your convenience. Helmut diff --minimal -Nru tiatracker-1.3/debian/changelog tiatracker-1.3/debian/changelog --- tiatracker-1.3/debian/changelog 2020-03-21 17:54:26.0 +0100 +++ tiatracker-1.3/debian/changelog 2023-04-05 11:38:50.0 +0200 @@ -1,3 +1,10 @@ +tiatracker (1.3-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Drop unnecessary override_dh_auto_configure. (Closes: #-1) + + -- Helmut Grohne Wed, 05 Apr 2023 11:38:50 +0200 + tiatracker (1.3-3) unstable; urgency=medium * Add desktop file. diff --minimal -Nru tiatracker-1.3/debian/rules tiatracker-1.3/debian/rules --- tiatracker-1.3/debian/rules 2019-12-04 13:45:46.0 +0100 +++ tiatracker-1.3/debian/rules 2023-04-05 11:38:49.0 +0200 @@ -15,8 +15,5 @@ %: dh $@ -override_dh_auto_configure: - qmake TIATracker.pro - override_dh_auto_install: @echo skip install \ No newline at end of file --- End Message --- --- Begin Message --- Source: tiatracker Source-Version: 1.3-5 Done: Alex Myczko We believe that the bug you reported is fixed in the latest version of tiatracker, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alex Myczko (supplier of updated tiatracker 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 27 Jul 2024 11:40:26 + Source: tiatracker Architecture: source Version: 1.3-5 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Alex Myczko Closes: 1033992 Changes: tiatracker (1.3-5) unstable; urgency=medium . * Fix FTCBFS: drop unnecessary override_dh_auto_configure. (Closes: #1033992) Thanks Helmut Grohne. Checksums-Sha1: 2986deac2ba71f1a77c391d0487d0a52417a9deb 1992 tiatracker_1.3-5.dsc acaa90702d63bb8ee34814f722766ccafd3653ea 2992 tiatracker_1.3-5.debian.tar.xz 8261e59b308453e1a05d6a493ad28a909620adce 15838 tiatracker_1.3-5_source.buildinfo Checksums-Sha256: 270292f914d7c6c33db6e7ed59cba812aa33d23554aa5a4f6b1765b237b4216d 1992 tiatracker_1.3-5.dsc 87f942aa7c1410c9d6e788bf142b039f95217477be7ef74da776d6320cdbae56 2992 tiatracker_1.3-5.debian.tar.xz 1c089ce438c4000c3770a97b14ea9c77edaad0bd0ba0034092b3d0562b2dd2f3 15838 tiatracker_1.3-5_source.buildinfo Files: 633283fe656c9cd208547262d3ca8e62 1992 sound optional tiatracker_1.3-5.dsc f40f601bfdd53f2ddf3744c51de8f407 2992 sound optional tiatracker_1.3-5.debian.tar.xz 7eb17e059a8121f7fae4823a81f6ef30 15838 sound optional tiatracker_1.3-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmalBiAACgkQEWhSvN91 FcArMQ//a0rwChtPpw+Ng932yPg9LPg4CDVr3R1oGDN9n23kpKFiwyIpZrfYa2tN MPEK2UEVfFS3LQMC6R9OnoKdGFeGSkRvjgVxwoJqNDkFg67LFzbamnaNQngpZoVo Ec2xLF4ErD+mwV4WsBA4bOf2oBA0fmhsnI0Ia2TW2xp80HouKdVIyGAC5ZxHaxHd nwNxvI3vlRk8aPY6sD0GHrSlq+ii3FG6TtTNMRSqZer/zPc++JO8PD1YYwCAY0CX DVx7m4VdCXCYcJyalmVknK9KSWdATVAvzXolguZ0T4UhvjW7WGNhqGfuZMtXSk5i cwI4vOUZoL19UzisGSfUkAS/NGnAnQuvqfObUfT95YMhvXodqR3ffbsAuRwf4fm4 76/NJlUp8GWcGADUIrQLza+MlFsY2VweBhT9vwNiAG2Fe41NVO84R+yrQxWvvjt9 PYfCtroKwqrioYduspYkLdvnkmLHDWFJpc3gP6XU0zhaSnhqcBEkIaeXJmOR7oYN JCggZ39V/eIz37Ow8RFehE18Ih4Rc2zqXjfbEcBPcvYiDNvuYgjoSrCYE3M9TAJ8 q2PWnkE3o6QucMOW/9BT2xrEDlG5Ie3tE3vQDabf+hzNhX4EquSSwkZGdc6k0fMg pOfxOC/y3ItBhTOb3foxhhv1+b/uXG5ZIGAbx2bXsJzi77Oqfe8= =MGQS -END PGP SIGNATURE
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 1075117 fixed-upstream Bug #1075117 [src:kodi] kodi: ftbfs with GCC-14 Added tag(s) fixed-upstream. > forwarded 1075117 https://github.com/xbmc/xbmc/pull/25106 Bug #1075117 [src:kodi] kodi: ftbfs with GCC-14 Set Bug forwarded-to-address to 'https://github.com/xbmc/xbmc/pull/25106'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1075117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 1074370 to Enable asm support on armel and armhf
Processing commands for cont...@bugs.debian.org: > retitle 1074370 Enable asm support on armel and armhf Bug #1074370 [src:ffmpeg] ffmpeg: Fails to build on armel & armhf Changed Bug title to 'Enable asm support on armel and armhf' from 'ffmpeg: Fails to build on armel & armhf'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1074370: marked as done (ffmpeg: Fails to build on armel & armhf)
Processing commands for cont...@bugs.debian.org:
> reopen 1074370
Bug #1074370 {Done: Jeremy Bícha } [src:ffmpeg]
ffmpeg: Fails to build on armel & armhf
Bug reopened
Ignoring request to alter fixed versions of bug #1074370 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1074370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#980295: marked as done (davs2: please make the build reproducible)
Your message dated Fri, 26 Jul 2024 18:58:38 +
with message-id
and subject line Bug#1075984: Removed package(s) from unstable
has caused the Debian Bug report #980295,
regarding davs2: please make the build reproducible
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 ow...@bugs.debian.org
immediately.)
--
980295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: davs2
Version: 1.6-1~exp2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0] we noticed that
davs2 could not be built reproducibly.
This is because it embeds the build time via the XBUILD_TIME macro. A
patch is attached that uses SOURCE_DATE_EPOCH [1].
[0] https://reproducible-builds.org/
[1] https://reproducible-builds.org/specs/source-date-epoch/
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--- a/debian/patches/1003_reproducible_build.patch 1970-01-01
01:00:00.0 +0100
--- b/debian/patches/1003_reproducible_build.patch 2021-01-17
12:50:09.947620440 +
@@ -0,0 +1,15 @@
+Description: Make the build reproducible
+Author: Chris Lamb
+Last-Update: 2021-01-17
+
+--- davs2-1.6.orig/version.sh
davs2-1.6/version.sh
+@@ -24,7 +24,7 @@ VER_MAJOR=`echo $(($api / 10))`
+ VER_MINOR=`echo $(($api % 10))`
+
+ # date and time information
+-BUILD_TIME=`date "+%Y-%m-%d %H:%M:%S"`
++BUILD_TIME=`date --utc --date="@${SOURCE_DATE_EPOCH:-$(date +%s)}" "+%Y-%m-%d
%H:%M:%S"`
+
+ # generate the file version.h
+ echo "//
===" >
version.h
--- a/debian/patches/series 2021-01-17 12:45:19.141640553 +
--- b/debian/patches/series 2021-01-17 12:50:08.675611780 +
@@ -4,3 +4,4 @@
020181224~5645e27.patch
1001_allow_preseeded_revision.patch
1002_fix_arch_optimizations.patch
+1003_reproducible_build.patch
--- End Message ---
--- Begin Message ---
Version: 1.6-1+rm
Dear submitter,
as the package davs2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1075984
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#919084: marked as done (davs2: FTBFS on !amd64)
Your message dated Fri, 26 Jul 2024 18:58:38 + with message-id and subject line Bug#1075984: Removed package(s) from unstable has caused the Debian Bug report #919084, regarding davs2: FTBFS on !amd64 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 ow...@bugs.debian.org immediately.) -- 919084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: davs2 Version: 1.6-1~exp2 Severity: serious Justification: fails to build from source Hi, davs2 did FTBFS on all buildds (except kfreebsd-amd64): https://buildd.debian.org/status/package.php?p=davs2=experimental Andreas --- End Message --- --- Begin Message --- Version: 1.6-1+rm Dear submitter, as the package davs2 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1075984 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1024722: marked as done (davs2: Keep out of testing until it is used)
Your message dated Fri, 26 Jul 2024 18:58:38 + with message-id and subject line Bug#1075984: Removed package(s) from unstable has caused the Debian Bug report #1024722, regarding davs2: Keep out of testing until it is used 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 ow...@bugs.debian.org immediately.) -- 1024722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: davs2 Version: 1.6-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org The library is not used, so let's not include it in bookworm. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Version: 1.6-1+rm Dear submitter, as the package davs2 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1075984 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1000786: marked as done (davs2 FTCBFS: configures for the build architecture)
Your message dated Fri, 26 Jul 2024 18:58:38 +
with message-id
and subject line Bug#1075984: Removed package(s) from unstable
has caused the Debian Bug report #1000786,
regarding davs2 FTCBFS: configures for the build architecture
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 ow...@bugs.debian.org
immediately.)
--
1000786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: davs2
Version: 1.6-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags ftcbfs
davs2 fails to cross build from source, because it configures for the
build architecture. The upstream configure script is very much unlike
autoconf and ignores --host as passed by dh_auto_configure. Instead one
is supposed to pass --cross-prefix. Please consider applying the
attached patch.
Helmut
diff --minimal -Nru davs2-1.6/debian/changelog davs2-1.6/debian/changelog
--- davs2-1.6/debian/changelog 2021-04-11 16:02:46.0 +0200
+++ davs2-1.6/debian/changelog 2021-11-28 14:04:33.0 +0100
@@ -1,3 +1,10 @@
+davs2 (1.6-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTCBFS: Pass --cross-prefix to configure. (Closes: #-1)
+
+ -- Helmut Grohne Sun, 28 Nov 2021 14:04:33 +0100
+
davs2 (1.6-1) unstable; urgency=medium
[ Ondřej Nový ]
diff --minimal -Nru davs2-1.6/debian/rules davs2-1.6/debian/rules
--- davs2-1.6/debian/rules 2021-04-11 15:55:39.0 +0200
+++ davs2-1.6/debian/rules 2021-11-28 14:04:32.0 +0100
@@ -1,5 +1,6 @@
#!/usr/bin/make -f
+include /usr/share/dpkg/architecture.mk
include /usr/share/dpkg/pkg-info.mk
manpage = debian/davs2.1
@@ -10,6 +11,7 @@
override_dh_auto_configure:
VER_SHA="$(DEB_DISTRIBUTION)" dh_auto_configure -- \
+ --cross-prefix=$(DEB_HOST_GNU_TYPE)- \
--enable-shared \
--enable-pic \
--extra-cflags="${CPPFLAGS} -fvisibility=hidden -DDAVS2_EXPORTS"
--- End Message ---
--- Begin Message ---
Version: 1.6-1+rm
Dear submitter,
as the package davs2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1075984
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1019358: marked as done (davs2: CVE-2022-36647)
Your message dated Fri, 26 Jul 2024 18:58:38 + with message-id and subject line Bug#1075984: Removed package(s) from unstable has caused the Debian Bug report #1019358, regarding davs2: CVE-2022-36647 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 ow...@bugs.debian.org immediately.) -- 1019358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: davs2 Version: 1.6-1 Severity: important Tags: security upstream Forwarded: https://github.com/pkuvcl/davs2/issues/29 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for davs2. CVE-2022-36647[0]: | PKUVCL davs2 v1.6.205 was discovered to contain a global buffer | overflow via the function parse_sequence_header() at | source/common/header.cc:269. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-36647 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-36647 [1] https://github.com/pkuvcl/davs2/issues/29 [2] https://github.com/pkuvcl/davs2/commit/b41cf117452e2d73d827f02d3e30aa20f1c721ac Regards, Salvatore --- End Message --- --- Begin Message --- Version: 1.6-1+rm Dear submitter, as the package davs2 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1075984 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#952493: marked as done (xavs2: please make the build reproducible)
Your message dated Fri, 26 Jul 2024 18:57:49 +
with message-id
and subject line Bug#1075983: Removed package(s) from unstable
has caused the Debian Bug report #952493,
regarding xavs2: please make the build reproducible
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 ow...@bugs.debian.org
immediately.)
--
952493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xavs2
Version: 1.3-1~exp2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0] we noticed that
xavs2 could not be built reproducibly.
Patch attached, although that xavs2 will still vary due to the
embedding the path in calls to assert(...).
[0] https://reproducible-builds.org/
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--- a/debian/patches/1003_reproducible_build.patch 1969-12-31
16:00:00.0 -0800
--- b/debian/patches/1003_reproducible_build.patch 2020-02-24
15:38:11.940987381 -0800
@@ -0,0 +1,17 @@
+Description: Make the build reproducible
+Author: Chris Lamb
+Last-Update: 2020-02-24
+
+--- xavs2-1.3.orig/version.sh
xavs2-1.3/version.sh
+@@ -24,7 +24,9 @@ VER_MAJOR=`echo $(($api / 10))`
+ VER_MINOR=`echo $(($api % 10))`
+
+ # date and time information
+-BUILD_TIME=`date "+%Y-%m-%d %H:%M:%S"`
++DATE_FMT="+%Y-%m-%d %H:%M:%S"
++SOURCE_DATE_EPOCH="${SOURCE_DATE_EPOCH:-$(date +%s)}"
++BUILD_TIME=$(date -u -d "@$SOURCE_DATE_EPOCH" "$DATE_FMT" 2>/dev/null || date
-u -r "$SOURCE_DATE_EPOCH" "$DATE_FMT" 2>/dev/null || date -u "$DATE_FMT")
+
+ # generate the file version.h
+ echo "//
===" >
version.h
--- a/debian/patches/series 2020-02-24 15:30:28.338962779 -0800
--- b/debian/patches/series 2020-02-24 15:38:10.548980153 -0800
@@ -2,3 +2,4 @@
020181225~ffa8095.patch
1001_allow_preseeded_revision.patch
1002_fix_arch_optimizations.patch
+1003_reproducible_build.patch
--- End Message ---
--- Begin Message ---
Version: 1.3-1+rm
Dear submitter,
as the package xavs2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1075983
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1024723: marked as done (xavs2: do not release with bookworm)
Your message dated Fri, 26 Jul 2024 18:57:49 + with message-id and subject line Bug#1075983: Removed package(s) from unstable has caused the Debian Bug report #1024723, regarding xavs2: do not release with bookworm 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 ow...@bugs.debian.org immediately.) -- 1024723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024723 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xavs2 Version: 1.3-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org The library is currently not used, so let's not release it with bookworm. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Version: 1.3-1+rm Dear submitter, as the package xavs2 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1075983 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1074370: marked as done (ffmpeg: Fails to build on armel & armhf)
Your message dated Fri, 26 Jul 2024 14:22:52 -0400 with message-id and subject line Re: Bug#1074370: ffmpeg: Fails to build on armel & armhf has caused the Debian Bug report #1074370, regarding ffmpeg: Fails to build on armel & armhf 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 ow...@bugs.debian.org immediately.) -- 1074370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ffmpeg Version: 7:6.1.1-4 Severity: serious Tags: ftbfs User: debian-...@lists.debian.org Usertags: armel armhf X-Debbugs-CC: debian-...@lists.debian.org ffmpeg is failing to build on armel & armhf (but not arm64). This was noticed while rebuilding ffmpeg for the ongoing jpeg-xl 0.9 transition. I don't believe the build failure is related to the new version of jpeg-xl. The last successful official build before this was on June 9. Build log excerpt -- src/libavcodec/arm/mlpdsp_armv5te.S: Assembler messages: src/libavcodec/arm/mlpdsp_armv5te.S:232: Error: junk at end of line, first unrecognized character is `0' src/libavcodec/arm/mlpdsp_armv5te.S:367: Info: macro invoked from here src/libavcodec/arm/mlpdsp_armv5te.S:393: Info: macro invoked from here src/libavcodec/arm/mlpdsp_armv5te.S:414:Info: macro invoked from here src/libavcodec/arm/mlpdsp_armv5te.S:244: Error: garbage following instruction -- `bne 01b' src/libavcodec/arm/mlpdsp_armv5te.S:367: Info: macro invoked from here src/libavcodec/arm/mlpdsp_armv5te.S:393: Info: macro invoked from here src/libavcodec/arm/mlpdsp_armv5te.S:414:Info: macro invoked from here Full build logs -- https://buildd.debian.org/status/package.php?p=ffmpeg Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- ffmpeg is building now. I guess this bug is a duplicate of the now fixed https://bugs.debian.org/1076067 https://buildd.debian.org/status/package.php?p=ffmpeg Thank you, Jeremy Bícha--- End Message ---
Processed: BTS housekeeping
bin/bugreport.cgi?bug=1075337 1075338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075338 1075422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075422 1075430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075430 1075435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075435 1075437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075437 1075439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075439 1075444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075444 1075446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075446 1075486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075486 1075487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075487 1075496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075496 1075502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075502 1075503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075503 1075522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075522 1075575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075575 1075618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071820: marked as done (blender:FTBFS:compile failed(error: cast from ‘void*’ to ‘CUdeviceptr’ loses precision))
Your message dated Fri, 26 Jul 2024 14:58:52 +0100
with message-id
and subject line Re: Bug#1071820: blender:FTBFS:compile failed(error: cast from
‘void*’ to ‘CUdeviceptr’ loses precision)
has caused the Debian Bug report #1071820,
regarding blender:FTBFS:compile failed(error: cast from ‘void*’ to
‘CUdeviceptr’ loses precision)
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 ow...@bugs.debian.org
immediately.)
--
1071820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: blender
Version: 4.0.2+dfsg-1
Severity: important
Tags: FTBFS, patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org
Dear llvmlite Maintainer,
The blender compile failed on riscv64 caused by losing precision when cast
from ‘void*’ to ‘CUdeviceptr’.The crucial buildd log below:
```
/<>/intern/cycles/device/cuda/device_impl.cpp:528:25:
error: cast from ‘void*’ to ‘CUdeviceptr’ {aka ‘unsigned int’} loses
precision [-fpermissive]
528 | cuda_assert(cuMemFree((CUdeviceptr)device_pointer));
| ^~~
/<>/intern/cycles/device/../device/cuda/util.h:32:25:
note: in definition of macro ‘cuda_device_assert’
32 | CUresult result = stmt; \
| ^~~~
/<>/intern/cycles/device/cuda/device_impl.cpp:528:3:
note: in expansion of macro ‘cuda_assert’
528 | cuda_assert(cuMemFree((CUdeviceptr)device_pointer));
| ^~~
/<>/intern/cycles/device/cuda/device_impl.cpp: In member
function ‘virtual void ccl::CUDADevice::copy_host_to_device(void*,
void*, size_t)’:
/<>/intern/cycles/device/cuda/device_impl.cpp:558:28:
error: cast from ‘void*’ to ‘CUdeviceptr’ {aka ‘unsigned int’} loses
precision [-fpermissive]
558 | cuda_assert(cuMemcpyHtoD((CUdeviceptr)device_pointer,
host_pointer, size));
```
The full buildd log is here:
https://buildd.debian.org/status/fetch.php?pkg=blender=riscv64=4.0.2%2Bdfsg-1=1704028470=0
My solution to this issue:
Convert the problematic conversion code to a uintptr_t intermediate type.I
have tested this modification in local ,and it works well.Please let me
know wheather this patch can be accepted. The patch is in the attachment.
Gui-Yue
Best Regards
--- End Message ---
--- Begin Message ---
On 2024-05-25 14:11, Yue Gui wrote:
> Source: blender
> Version: 4.0.2+dfsg-1
> Severity: important
> Tags: FTBFS, patch
> User: debian-ri...@lists.debian.org
> Usertags: riscv64
> X-Debbugs-Cc: debian-ri...@lists.debian.org
>
> Dear llvmlite Maintainer,
> The blender compile failed on riscv64 caused by losing precision when cast
> from ‘void*’ to ‘CUdeviceptr’.The crucial buildd log below:
> ```
blender now builds fine on riscv64. Closing the bug.
Regards
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net--- End Message ---
Processed (with 1 error): BTS housekeeping
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074829 1074835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074835 1074843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074843 1074845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074845 1074851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074851 1074853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074853 1074855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074855 1074868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074868 1074897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074897 1074903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074903 1074905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074905 1074917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074917 1074952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074952 1074985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074985 1074998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074998 1075001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075001 1075044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075044 1075063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075063 1075077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075077 1075118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075118 1075119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075119 1075120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075120 1075134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075134 1075136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075136 1075156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075156 1075159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075159 1075223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075223 1075247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075247 1075251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075251 1075262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075262 1075278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075278 1075282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075282 1075283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075283 1075292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075292 1075316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075316 1075331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075331 1075335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075335 1075336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075336 1075337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075337 1075338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075338 1075411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075411 1075422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075422 1075435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075435 1075437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075437 1075439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075439 1075443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075443 1075444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075444 1075486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075486 1075488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075488 1075502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075502 1075503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075503 1075510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075510 1075573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075573 1075575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075575 1075612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075612 1075640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075640 1075644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075644 1075682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075682 1075695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075695 1075699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075699 1075707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075707 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Patch
Processing control commands: > tags -1 patch Bug #1075650 [src:xawtv] xawtv: ftbfs with GCC-14 Added tag(s) patch. -- 1075650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1076379: marked as done (jackd2: Example clients (cli tools) missing since 1.9.22)
Your message dated Fri, 26 Jul 2024 12:35:22 + with message-id and subject line Bug#1076379: fixed in jackd2 1.9.22~dfsg-3 has caused the Debian Bug report #1076379, regarding jackd2: Example clients (cli tools) missing since 1.9.22 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 ow...@bugs.debian.org immediately.) -- 1076379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jackd2 Version: 1.9.22~dfsg-2 Severity: important X-Debbugs-Cc: vermee...@vermwa.re Dear Maintainer, It appears that upstream has split all CLI tools, also called example clients, from the main jack2 build system. I noticed this in the changelog: https://github.com/jackaudio/jack2/releases/tag/v1.9.22 I noticed that after the upgrade my jack setup was no longer functional, as critical utilities like jack_load were missing. It seems very likely that for many users and applications expecting the standard jack CLI tools to be in place this will also result in breakage as only the core of jack2 remains. https://packages.debian.org/bookworm/amd64/jackd2/filelist https://packages.debian.org/trixie/amd64/jackd2/filelist I tried searching but could not find an additional optional package in Debian that would now contain these missing tools. The description of jackd2 package also still shows "(server and example clients)", so it seems to be an oversight. For reference, it seems that Arch Linux has decided on the creation of a new package jack-example-tools. Most likely jackd2 should recommend this package if this approach is taken in Debian as well. https://github.com/jackaudio/jack-example-tools Could you please take a look? Workaround for now is downgrading and holding the packages. Thanks, Melvin Vermeeren. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.9.7-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages jackd2 depends on: ii debconf [debconf-2.0] 1.5.87 ii libasound2t64 1.2.12-1 ii libc6 2.38-14 ii libdbus-1-31.14.10-4+b1 ii libexpat1 2.6.2-1 ii libgcc-s1 14-20240330-1 ii libjack-jackd2-0 1.9.22~dfsg-2 ii libopus0 1.5.2-2 ii libsamplerate0 0.2.2-4+b1 ii libstdc++6 14-20240330-1 ii libsystemd0256.2-1 ii python33.12.3-1 ii python3-dbus 1.3.2-5+b3 Versions of packages jackd2 recommends: ii jackd2-firewire 1.9.22~dfsg-2 ii libpam-modules 1.5.3-7 ii qjackctl 0.9.91-1 Versions of packages jackd2 suggests: ii jack-tools 20131226-2 ii meterbridge 0.9.2-14 -- debconf information: * jackd/tweak_rt_limits: true --- End Message --- --- Begin Message --- Source: jackd2 Source-Version: 1.9.22~dfsg-3 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of jackd2, 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 1076...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated jackd2 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Jul 2024 14:04:45 +0200 Source: jackd2 Architecture: source Version: 1.9.22~dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 1076379 Changes: jackd2 (1.9.22~dfsg-3) unstable; urgency=medium . * debian/control: Recommend jack-example-tools (Closes: #1076379) Checksums-Sha1: 2fd2db64536d196604c84ae8d53ebb85e070c4b9 1802 jackd2_1.9.22~dfsg-3.dsc f068a85cbf42aa69a9c16337c74d0e720d13fc34 65800 jackd2_1.9.22~dfsg-3.debian.tar.xz 99b984aaa717027bf7d859ea7870a1efd3df3ed0 6939 jackd2_1.9.22~dfsg-3_source.buildinfo Checks
Bug#1076836: marked as done (jack-example-tools: Package can't be installed)
Your message dated Fri, 26 Jul 2024 12:22:26 +
with message-id
and subject line Bug#1076836: fixed in jack-example-tools 4-2
has caused the Debian Bug report #1076836,
regarding jack-example-tools: Package can't be installed
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 ow...@bugs.debian.org
immediately.)
--
1076836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jack-example-tools
Version: 4-1
Severity: important
Tags: patch
Dear Maintainer,
The current version of jack-example-tools can't be installed because of
a typo in the control file. (The version of jack it depens on is 1.92.22
instead of 1.9.22.) It's an easy fix, but I've included a patch anyway.
Cheers,
Aaron
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.9.10-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages jack-example-tools depends on:
ii jackd 5+nmu1
ii libasound2t64 1.2.12-1
ii libc6 2.39-5
ii libgcc-s1 14.1.0-5
ii libjack-jackd2-0 1.9.22~dfsg-2
ii libopus0 1.5.2-2
ii libreadline8t648.2-4
ii libsamplerate0 0.2.2-4+b1
ii libsndfile11.2.2-1+b2
ii libstdc++6 14.1.0-5
ii libzita-alsa-pcmi0t64 0.6.1-1.1
ii libzita-resampler1 1.11.2-1+b1
jack-example-tools recommends no packages.
jack-example-tools suggests no packages.
-- no debconf information
Fix to allow the package to be installed alongside the current version of jackd2
Index: jack-example-tools-4/debian/control
===
--- jack-example-tools-4.orig/debian/control
+++ jack-example-tools-4/debian/control
@@ -28,8 +28,8 @@ Depends:
${misc:Depends},
${shlibs:Depends},
jackd
-Breaks: jackd2 (<< 1.92.22~dfsg-1~)
-Replaces: jackd2 (<< 1.92.22~dfsg-1~)
+Breaks: jackd2 (<< 1.9.22~dfsg-1~)
+Replaces: jackd2 (<< 1.9.22~dfsg-1~)
Description: JACK Audio Connection Kit (example clients)
JACK is a low-latency sound server, allowing multiple applications to
connect to one audio device, and to share audio between themselves.
--- End Message ---
--- Begin Message ---
Source: jack-example-tools
Source-Version: 4-2
Done: Sebastian Ramacher
We believe that the bug you reported is fixed in the latest version of
jack-example-tools, 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 1076...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastian Ramacher (supplier of updated
jack-example-tools 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 ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 26 Jul 2024 13:59:47 +0200
Source: jack-example-tools
Architecture: source
Version: 4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Sebastian Ramacher
Closes: 1076836
Changes:
jack-example-tools (4-2) unstable; urgency=medium
.
[ Aaron Wyatt ]
* Fix version in Breaks and Replaces (Closes: #1076836)
Checksums-Sha1:
ed28254c81e6d88240fb538f820ce16fc484f4c0 1557 jack-example-tools_4-2.dsc
a38909168bc1c257fc4d154bcc5a839df18e9fde 17296
jack-example-tools_4-2.debian.tar.xz
3bde04f15492476acb10687defd7691d76cb906f 7378
jack-example-tools_4-2_source.buildinfo
Checksums-Sha256:
3de35bb751a596ba60556160b78c00c0989816bf1905db8040a255a0d7d63887 1557
jack-example-tools_4-2.dsc
ff642bbbea0f513c4c16523eeaf4cdcfa1ecc66b0cd0a53103a842789148c798 17296
jack-example-tools_4-2.debian.tar.xz
97408090883bbdc7edcf930a80c522c6e0a0b536fe89537296f1a756d18aff73 7378
jack-example-tools_4-2_source.buildinfo
Files:
08a5565ab9a12436a7d116ae7614f5a0 1557 sound optional jack-example-tools_4-2.dsc
de902b10c1d142b5f4e4954ffd29a75a 17296 sound optional
jack-example
Bug#1076931: marked as done (vlevel: FTBFS: undefined reference to `jack_client_open')
Your message dated Fri, 26 Jul 2024 12:07:05 + with message-id and subject line Bug#1076931: fixed in vlevel 0.5.2-1 has caused the Debian Bug report #1076931, regarding vlevel: FTBFS: undefined reference to `jack_client_open' 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 ow...@bugs.debian.org immediately.) -- 1076931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:vlevel Version: 0.5.1-4 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build -- 'CC=$(CXX)' make -j2 "INSTALL=install --strip-program=true" CC=\$\(CXX\) make[2]: Entering directory '/<>' make -C volumeleveler all make[3]: Entering directory '/<>/volumeleveler' g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -fPIC -DPIC -Wdate-time -D_FORTIFY_SOURCE=2 -c -o volumeleveler.o volumeleveler.cpp cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ make[3]: Leaving directory '/<>/volumeleveler' make -C vlevel-bin all make[3]: Entering directory '/<>/vlevel-bin' g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -fPIC -DPIC -Wdate-time -D_FORTIFY_SOURCE=2 -c -o vlevel-bin.o vlevel-bin.cpp g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -fPIC -DPIC -Wdate-time -D_FORTIFY_SOURCE=2 -c -o commandline.o commandline.cpp cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ g++ -Wl,-z,relro -Wl,-z,now vlevel-bin.o commandline.o ../volumeleveler/volumeleveler.o -o vlevel-bin make[3]: Leaving directory '/<>/vlevel-bin' make -C vlevel-ladspa all make[3]: Entering directory '/<>/vlevel-ladspa' g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -fPIC -DPIC -Wdate-time -D_FORTIFY_SOURCE=2 -c -o vlevel-ladspa.o vlevel-ladspa.cpp cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ vlevel-ladspa.cpp:46:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings] 46 | "Look-ahead (seconds)", | ^~ vlevel-ladspa.cpp:47:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings] 47 | "Strength", | ^~ vlevel-ladspa.cpp:48:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings] 48 | "Limit Multiplier", | ^~ vlevel-ladspa.cpp:49:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings] 49 | "Multiplier Limit", | ^~ vlevel-ladspa.cpp:50:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings] 50 | "Undo", |
Processed: tagging 1076931, tagging 1077072, tagging 1077092, tagging 1077093, tagging 1077094, tagging 1077095 ...
ary-contrib: needs rebuild against dh-elpa
>=2.1.5
Added tag(s) sid and trixie.
> tags 1077129 + sid trixie
Bug #1077129 [src:verbiste] verbiste: needs rebuild against dh-elpa >=2.1.5
Added tag(s) sid and trixie.
> tags 1077130 + sid trixie
Bug #1077130 {Done: Stéphane Glondu } [src:tuareg-mode]
tuareg-mode: needs rebuild against dh-elpa >=2.1.5
Added tag(s) trixie and sid.
> tags 1077131 + sid trixie
Bug #1077131 [src:xcscope-el] xcscope-el: needs rebuild against dh-elpa >=2.1.5
Added tag(s) trixie and sid.
> tags 1077132 + sid trixie
Bug #1077132 [src:yatex] yatex: needs rebuild against dh-elpa >=2.1.5
Added tag(s) sid and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1076931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076931
1077072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077072
1077092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077092
1077093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077093
1077094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077094
1077095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077095
1077096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077096
1077097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077097
1077098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077098
1077099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077099
1077100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077100
1077101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077101
1077102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077102
1077104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077104
1077105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077105
1077106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077106
1077107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077107
1077108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077108
1077110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077110
1077111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077111
1077112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077112
1077113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077113
1077114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077114
1077116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077116
1077118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077118
1077119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077119
1077120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077120
1077121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077121
1077122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077122
1077123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077123
1077124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077124
1077125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077125
1077126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077126
1077127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077127
1077128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077128
1077129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077129
1077130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077130
1077131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077131
1077132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1075049: marked as done (gsequencer: ftbfs with GCC-14)
Your message dated Fri, 26 Jul 2024 11:05:41 + with message-id and subject line Bug#1075049: fixed in gsequencer 6.16.16-1 has caused the Debian Bug report #1075049, regarding gsequencer: ftbfs with GCC-14 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 ow...@bugs.debian.org immediately.) -- 1075049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gsequencer Version: 6.13.5-1 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/gsequencer_6.13.5-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] from /usr/include/libinstpatch-2/libinstpatch/IpatchBase.h:33, from /usr/include/libinstpatch-2/libinstpatch/libinstpatch.h:30, from ./ags/audio/ags_sf2_synth_generator.h:31, from ./ags/libags-audio.h:128: /usr/include/libinstpatch-2/libinstpatch/IpatchItem.h:74:5: warning: ‘GStaticRecMutex’ is deprecated: Use 'GRecMutex' instead [-Wdeprecated-declarations] 74 | GStaticRecMutex *mutex; /* pointer to mutex (could be a parent's mutex) */ | ^~~ In file included from /usr/include/glib-2.0/glib.h:115, from ./ags/app/ags_composite_editor_callbacks.h:23: /usr/include/glib-2.0/glib/deprecated/gthread.h:161:8: note: declared here 161 | struct _GStaticRecMutex |^~~~ In file included from /usr/include/libinstpatch-2/libinstpatch/IpatchSF2Zone.h:27, from /usr/include/libinstpatch-2/libinstpatch/IpatchSF2PZone.h:26, from /usr/include/libinstpatch-2/libinstpatch/IpatchSF2Preset.h:27, from /usr/include/libinstpatch-2/libinstpatch/IpatchBase.h:35: /usr/include/libinstpatch-2/libinstpatch/IpatchSF2Gen.h:239:13: warning: Deprecated pre-processor symbol: replace with "const" 239 | G_CONST_RETURN char *ipatch_sf2_gen_get_prop_name(guint genid); | ^~~ In file included from /usr/include/libinstpatch-2/libinstpatch/IpatchSF2Mod.h:45, from /usr/include/libinstpatch-2/libinstpatch/IpatchSF2Zone.h:28: /usr/include/libinstpatch-2/libinstpatch/IpatchSF2ModList.h:50:13: warning: Deprecated pre-processor symbol: replace with "const" 50 | G_CONST_RETURN GSList *ipatch_sf2_mod_list_get_default(void); | ^ In file included from /usr/include/libinstpatch-2/libinstpatch/IpatchDLS2.h:33, from /usr/include/libinstpatch-2/libinstpatch/libinstpatch.h:38: /usr/include/libinstpatch-2/libinstpatch/IpatchDLS2Info.h:62:13: warning: Deprecated pre-processor symbol: replace with "const" 62 | G_CONST_RETURN char *ipatch_dls2_info_peek(IpatchDLS2Info *info, | ^~~~ In file included from /usr/include/libinstpatch-2/libinstpatch/libinstpatch.h:107: /usr/include/libinstpatch-2/libinstpatch/IpatchXml.h:78:13: warning: Deprecated pre-processor symbol: replace with "const" 78 | G_CONST_RETURN char *ipatch_xml_get_name(GNode *node); | ^~ /usr/include/libinstpatch-2/libinstpatch/IpatchXml.h:80:13: warning: Deprecated pre-processor symbol: replace with "const" 80 | G_C
Processed: found 1073348 in 1.3+ds-1
Processing commands for cont...@bugs.debian.org: > found 1073348 1.3+ds-1 Bug #1073348 [src:inkscape] inkscape: FTBFS: uri.cpp:86:9: error: ‘xmlFree’ was not declared in this scope; did you mean ‘xmlFreeURI’? Marked as found in versions inkscape/1.3+ds-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1073348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1076865: ardour: FTBFS: IndexError: list index out of range
Processing commands for cont...@bugs.debian.org:
> reassign 1076865 dpkg-dev
Bug #1076865 [src:ardour] ardour: FTBFS: IndexError: list index out of range
Bug reassigned from package 'src:ardour' to 'dpkg-dev'.
No longer marked as found in versions ardour/1:8.6.0+ds-1.
Ignoring request to alter fixed versions of bug #1076865 to the same values
previously set
> found 1076865 1.22.8
Bug #1076865 [dpkg-dev] ardour: FTBFS: IndexError: list index out of range
Marked as found in versions dpkg/1.22.8.
> close 1076865 1.22.9
Bug #1076865 [dpkg-dev] ardour: FTBFS: IndexError: list index out of range
Marked as fixed in versions dpkg/1.22.9.
Bug #1076865 [dpkg-dev] ardour: FTBFS: IndexError: list index out of range
Marked Bug as done
> forcemerge 1076863 1076865
Bug #1076863 {Done: Guillem Jover } [dpkg-dev] dpkg-dev:
DEB_VERSION_UPSTREAM_REVISION seems to be broken
Bug #1076878 {Done: Santiago Vila } [dpkg-dev] ejabberd:
FTBFS: rm: cannot remove
'/<>/debian/ejabberd/usr/lib/x86_64-linux-gnu/ejabberd-23.10-1/priv/bin/captcha.sh':
No such file or directory
Bug #1076900 {Done: Guillem Jover } [dpkg-dev]
onioncircuits: FTBFS: help2man failure
Bug #1076939 {Done: Guillem Jover } [dpkg-dev] dpkg-dev: no
longer resolves variable DEB_VERSION_UPSTREAM_REVISION in core make
Bug #1076865 {Done: Santiago Vila } [dpkg-dev] ardour:
FTBFS: IndexError: list index out of range
Added indication that 1076865 affects
src:dsda-doom,src:ejabberd,src:onioncircuits,src:radicale,src:pd-mrpeach,src:fonts-urw-base35,src:dutch
Added tag(s) pending.
Bug #1076878 {Done: Santiago Vila } [dpkg-dev] ejabberd:
FTBFS: rm: cannot remove
'/<>/debian/ejabberd/usr/lib/x86_64-linux-gnu/ejabberd-23.10-1/priv/bin/captcha.sh':
No such file or directory
Bug #1076900 {Done: Guillem Jover } [dpkg-dev]
onioncircuits: FTBFS: help2man failure
Bug #1076939 {Done: Guillem Jover } [dpkg-dev] dpkg-dev: no
longer resolves variable DEB_VERSION_UPSTREAM_REVISION in core make
Merged 1076863 1076865 1076878 1076900 1076939
> affects 1076863 + src:ardour
Bug #1076863 {Done: Guillem Jover } [dpkg-dev] dpkg-dev:
DEB_VERSION_UPSTREAM_REVISION seems to be broken
Bug #1076865 {Done: Santiago Vila } [dpkg-dev] ardour:
FTBFS: IndexError: list index out of range
Bug #1076878 {Done: Santiago Vila } [dpkg-dev] ejabberd:
FTBFS: rm: cannot remove
'/<>/debian/ejabberd/usr/lib/x86_64-linux-gnu/ejabberd-23.10-1/priv/bin/captcha.sh':
No such file or directory
Bug #1076900 {Done: Guillem Jover } [dpkg-dev]
onioncircuits: FTBFS: help2man failure
Bug #1076939 {Done: Guillem Jover } [dpkg-dev] dpkg-dev: no
longer resolves variable DEB_VERSION_UPSTREAM_REVISION in core make
Added indication that 1076863 affects src:ardour
Added indication that 1076865 affects src:ardour
Added indication that 1076878 affects src:ardour
Added indication that 1076900 affects src:ardour
Added indication that 1076939 affects src:ardour
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1076863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076863
1076865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076865
1076878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076878
1076900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076900
1076939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1063004: marked as done (synfig: NMU diff for 64-bit time_t transition)
Your message dated Wed, 24 Jul 2024 19:34:35 +
with message-id
and subject line Bug#1063004: fixed in synfig 1.5.1+dfsg-4
has caused the Debian Bug report #1063004,
regarding synfig: NMU diff for 64-bit time_t transition
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 ow...@bugs.debian.org
immediately.)
--
1063004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: synfig
Version: 1.5.1+dfsg-3
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
synfig as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for synfig
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru synfig-1.5.1+dfsg/debian/changelog synfig-1.5.1+dfsg/debian/changelog
--- synfig-1.5.1+dfsg/debian/changelog 2022-07-05 05:06:27.0 +
+++ synfig-1.5.1+dfsg/debian/changelog 2024-02-04 11:33:06.0 +
@@ -1,3 +1,10 @@
+synfig (1.5.1+dfsg-3.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek Sun, 04 Feb 2024 11:33:06 +
+
synfig (1.5.1+dfsg-3) unstable; urgency=medium
* New upstream patch to fix FTBFS with ffmpeg-5.0 (Closes: #1013460).
diff -Nru synfig-1.5.1+dfsg/debian/control synfig-1.5.1+dfsg/debian/control
--- synfig-1.5.1+dfsg/debian/control2022-04-10 03:50:20.0 +
+++ synfig-1.5.1+dfsg/debian/control2024-02-04 11:33:06.0 +
@@ -49,7 +49,9 @@
This package contains the command-line renderer, for the GUI animation
editor, please install synfigstudio.
-Package: libsynfig0a
+Package: libsynfig0t64
+Provides: ${t64:Provides}
+X-Time64-Compat: libsynfig0a
Section: libs
Architecture: any
Multi-Arch: same
@@ -60,9 +62,9 @@
imagemagick
Recommends: ${misc:Recommends}
,libdv-bin
-Breaks: synfigstudio (<< 0.64.2)
+Breaks: libsynfig0a (<< ${source:Version}), synfigstudio (<< 0.64.2)
Conflicts: libsynfig0v5, libsynfig0
-Replaces: libsynfig0v5, libsynfig0
+Replaces: libsynfig0a, libsynfig0v5, libsynfig0
Description: render library and plugins for synfig 2D animation
synfig is a vector based 2D animation package. It is designed to be
capable of producing feature-film quality animation.
@@ -72,7 +74,7 @@
Package: libsynfig-dev
Section: libdevel
Architecture: any
-Depends: ${misc:Depends} ,libsynfig0a (= ${binary:Version})
+Depends: ${misc:Depends} ,libsynfig0t64 (= ${binary:Version})
,etl-dev (>= 1.4.0~)
,libavcodec-dev
,libavformat-dev
diff -Nru synfig-1.5.1+dfsg/debian/libsynfig0a.install
synfig-1.5.1+dfsg/debian/libsynfig0a.install
--- synfig-1.5.1+dfsg/debian/libsynfig0a.install2015-09-29
08:05:44.0 +
Bug#1059750: marked as done (qmidiarp FTCBFS: abuses AC_CHECK_FILE)
Your message dated Wed, 24 Jul 2024 09:49:18 + with message-id and subject line Bug#1059750: fixed in qmidiarp 0.7.0+ds-3 has caused the Debian Bug report #1059750, regarding qmidiarp FTCBFS: abuses AC_CHECK_FILE 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 ow...@bugs.debian.org immediately.) -- 1059750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qmidiarp Version: 0.7.0+ds-1 Tags: patch upstream User: debian-cr...@lists.debian.org Usertags: ftcbfs qmidiarp fails to cross build from source, because it abuses AC_CHECK_FILE. The macro is meant to check for files on the host system and thus fails in a cross build. qmidiarp however uses it to locate files on the build system. It should rather use "test -e" for that. I'm attaching a patch for your convenience. Helmut --- qmidiarp-0.7.0+ds.orig/configure.ac +++ qmidiarp-0.7.0+ds/configure.ac @@ -111,9 +111,9 @@ QT_INCLUDE_DIR=`$PKG_CONFIG --variable=includedir QtGui` QT_CXXFLAGS=`$PKG_CONFIG --cflags QtCore QtGui` EXTRA_QT_INCLUDE_DIR="$QT_INCLUDE_DIR/Qt" - AC_CHECK_FILE([$QT_INCLUDE_DIR/QWidget], + AS_IF([test -e $QT_INCLUDE_DIR/QWidget], AC_MSG_NOTICE([No extra QT_INCLUDE_DIR needed]), - AC_CHECK_FILE([$EXTRA_QT_INCLUDE_DIR/QWidget], + AS_IF([test -e $EXTRA_QT_INCLUDE_DIR/QWidget], QT_CPPFLAGS="$QT_CPPFLAGS -I$EXTRA_QT_INCLUDE_DIR", AC_MSG_WARN([QWidget not found]))) @@ -137,9 +137,9 @@ QT_CXXFLAGS=`$PKG_CONFIG --cflags Qt5Core Qt5Gui Qt5Widgets` QT_CXXFLAGS="$QT_CXXFLAGS -fPIC" EXTRA_QT_INCLUDE_DIR="$QT_INCLUDE_DIR/Qt" - AC_CHECK_FILE([$QT_INCLUDE_DIR/QtWidgets/QWidget], + AS_IF([test -e $QT_INCLUDE_DIR/QtWidgets/QWidget], AC_MSG_NOTICE([No extra QT_INCLUDE_DIR needed]), - AC_CHECK_FILE([$EXTRA_QT_INCLUDE_DIR/QtWidgets/QWidget], + AS_IF([test -e $EXTRA_QT_INCLUDE_DIR/QtWidgets/QWidget], QT_CPPFLAGS="$QT_CPPFLAGS -I$EXTRA_QT_INCLUDE_DIR", AC_MSG_WARN([QWidget not found]))) --- End Message --- --- Begin Message --- Source: qmidiarp Source-Version: 0.7.0+ds-3 Done: Dennis Braun We believe that the bug you reported is fixed in the latest version of qmidiarp, 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 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dennis Braun (supplier of updated qmidiarp 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 24 Jul 2024 09:55:37 +0200 Source: qmidiarp Architecture: source Version: 0.7.0+ds-3 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Dennis Braun Closes: 1059750 Changes: qmidiarp (0.7.0+ds-3) unstable; urgency=medium . * Fix cross building. Thanks Helmut! (Closes: #1059750) * Apply wrap-and-sort -ast Checksums-Sha1: 9fc77967a07f1fea11ee9f95a26223943bcebd08 2174 qmidiarp_0.7.0+ds-3.dsc 02ba7a25d095eeb12e0be8de114b9b97c39b9c2f 8040 qmidiarp_0.7.0+ds-3.debian.tar.xz 1439e0fdda3ba5287c8514cda025445fdd59bbb1 7078 qmidiarp_0.7.0+ds-3_source.buildinfo Checksums-Sha256: c09b9537c2749f667659a79dcadd3dbd2b400f15b6b81991ea654747e681cee6 2174 qmidiarp_0.7.0+ds-3.dsc ed95ca498f279a076013b82aa806626ea58d01d565e90e47a538ec98a5a497fa 8040 qmidiarp_0.7.0+ds-3.debian.tar.xz fa91d615adc89ff42bb1cd7ac0def95cca4ae929c9d0398ba5422ccfc4fb8617 7078 qmidiarp_0.7.0+ds-3_source.buildinfo Files: 58bec51bcdb54bd692320b74bb9f6f00 2174 sound optional qmidiarp_0.7.0+ds-3.dsc 486dd94faf59fe3a1975ae42f8def81c 8040 sound optional qmidiarp_0.7.0+ds-3.debian.tar.xz dcd858540753d106b5611423e54ab99d 7078 sound optional qmidiarp_0.7.0+ds-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEPLfDAq+1fmGoxhfdY06lXZArmDYFAmags7APHHNuZEBkZWJp YW4ub3JnAAoJEGNOpV2QK5g2nucQAKmy1EBaKZW2Ji51SAIJ51XKW45hGJcy6h83 q5U59W/KRePXtnUN6T4A3ynHbC62VxpVHXYjURX1mjtQOczlZ57MJgs0++ifuT4M dZ1a
Processed: Bug#1059750 marked as pending in qmidiarp
Processing control commands: > tag -1 pending Bug #1059750 [src:qmidiarp] qmidiarp FTCBFS: abuses AC_CHECK_FILE Added tag(s) pending. -- 1059750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: dpf-plugins: FTBFS with RtAudio 6
Processing commands for cont...@bugs.debian.org: > # rtaudio6 is in testing and unstable > severity 1051558 serious Bug #1051558 [src:dpf-plugins] dpf-plugins: FTBFS with RtAudio 6 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1051558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: simplescreenrecorder: FTBFS with ffmpeg 7.0: AudioEncoder.cpp:169:43: error: ‘AVFrame’ {aka ‘struct AVFrame’} has no member named ‘channels’ no member named ‘channels’
Processing control commands:
> forwarded -1 https://github.com/MaartenBaert/ssr/pull/1031/
Bug #1072451 [src:simplescreenrecorder] simplescreenrecorder: FTBFS with ffmpeg
7.0: AudioEncoder.cpp:169:43: error: ‘AVFrame’ {aka ‘struct AVFrame’} has no
member named ‘channels’
Set Bug forwarded-to-address to
'https://github.com/MaartenBaert/ssr/pull/1031/'.
> tag -1 +upstream +fixed-upstream
Bug #1072451 [src:simplescreenrecorder] simplescreenrecorder: FTBFS with ffmpeg
7.0: AudioEncoder.cpp:169:43: error: ‘AVFrame’ {aka ‘struct AVFrame’} has no
member named ‘channels’
Added tag(s) upstream.
Bug #1072451 [src:simplescreenrecorder] simplescreenrecorder: FTBFS with ffmpeg
7.0: AudioEncoder.cpp:169:43: error: ‘AVFrame’ {aka ‘struct AVFrame’} has no
member named ‘channels’
Added tag(s) fixed-upstream.
--
1072451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: notfound 1060600 in 1.2-6
Processing commands for cont...@bugs.debian.org:
> notfound 1060600 1.2-6
Bug #1060600 {Done: Michael Biebl } [src:midisport-firmware]
midisport-firmware: Please switch Build-Depends to systemd-dev
No longer marked as found in versions midisport-firmware/1.2-6.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1060600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1076509: marked as done (libavif: missing deps?)
Your message dated Fri, 19 Jul 2024 16:49:17 + with message-id and subject line Bug#1076509: fixed in libavif 1.1.0-3 has caused the Debian Bug report #1076509, regarding libavif: missing deps? 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 ow...@bugs.debian.org immediately.) -- 1076509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libavid Version: 1.1.0-2 Severity: serious Hello, $ pkg-config --cflags libavif Package dav1d was not found in the pkg-config search path. Perhaps you should add the directory containing `dav1d.pc' to the PKG_CONFIG_PATH environment variable Package 'dav1d', required by 'libavif', not found Package 'rav1e', required by 'libavif', not found Package 'SvtAv1Enc', required by 'libavif', not found Package 'aom', required by 'libavif', not found apt install libdav1d-dev librav1e-dev libaom-dev libsvtav1enc-dev fixes the issue for me G. OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: libavif Source-Version: 1.1.0-3 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of libavif, 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 1076...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated libavif 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 19 Jul 2024 12:25:37 -0400 Source: libavif Architecture: source Version: 1.1.0-3 Distribution: unstable Urgency: high Maintainer: Debian Multimedia Maintainers Changed-By: Boyuan Yang Closes: 1076509 Changes: libavif (1.1.0-3) unstable; urgency=high . * debian/control: Manually record dependency to various dev packages for libavif-dev: libaom-dev, libdav1d-dev, librav1e-dev (some archs), libsvtav1enc-dev, libyuv-dev. (Closes: #1076509) Checksums-Sha1: 40aae8d8ba0d273a16407d6c5af3c17e3fa6dacf 2585 libavif_1.1.0-3.dsc 112deef2a2a51b55c391c7fae8ea22a8f0870e96 13642536 libavif_1.1.0.orig.tar.gz 67d072609046a6db1528636885be4cb16896912d 10520 libavif_1.1.0-3.debian.tar.xz ce0012e2dfd234210d310c8e1bb8278691679fad 10968 libavif_1.1.0-3_amd64.buildinfo Checksums-Sha256: 9f2a73731d593fa5c380bfbe9555aedfdcb0e92ecace97101788f8b1278e5228 2585 libavif_1.1.0-3.dsc edb31951005d7a143be1724f24825809599a4832073add50eaf987733defb5c8 13642536 libavif_1.1.0.orig.tar.gz ba1fb88b319036cd711a6cf9919e6fe48775cc28f7c36c78f6e8176bbaec3127 10520 libavif_1.1.0-3.debian.tar.xz d4ae6b6b890b7b1634623f1a344a0dcef1c08829de18715e2f2375fe773d37f7 10968 libavif_1.1.0-3_amd64.buildinfo Files: 1339daacbc5289bc3f4224e55f397374 2585 libs optional libavif_1.1.0-3.dsc cc9c6014b4c83a56e1714099b4892d7f 13642536 libs optional libavif_1.1.0.orig.tar.gz ef912841dcc09bc0d5e4a3d3caae94ef 10520 libs optional libavif_1.1.0-3.debian.tar.xz fd72132a324abc1b2a5cce0af4aa6a83 10968 libs optional libavif_1.1.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmaalJ8ACgkQwpPntGGC Ws4OdA//U06bLRhHG3z2d+uixBEgo8tgyJ1I+LbHSLhsv/vc+PgqPluBBTHZ+L7U ygqNEW1u+HnmeCF/DbJ2dgUrW2IfDtW0B5Rz03hHvSjh5sFrV0Zya94ITFLvJnkl nE1PEiV04S5zOhUBxZGLl5mvqALiUbgViSJf5t2EgI2QUp1RkGUOwLFPa1tRTtc0 BWWqI9nCvehtVpN3b/aLs+rwlfYQMSDVdoRpO3L4/1okIhaA9ry3RW6huBCPSjRu Vyz77D2kzWVdyJjHHdX4blEHx/QVYvs6q7qI/sacPMrLUroBrGD2WjpK1KkqUAeK gZhd5Oye5LjD/aWLNszxk9Eafx/sErDduK7dErRxnBKhEKOEmYn1DcDfrHwqnZ6/ HDfTcLutYPfMLZPkDu0zzdkDuYh06/kQsdqJ3r53VKWDWUG4iOZFb+/eTUxoP6vH PoYyddDuECHz24TWlJ7jypS735PuEqhBdMsG0EA9igUnye9qr6oeeTUXjDR/OQCi bp0b7vJ1T9sK/UGi6IJyLeytlfb42Sy6El2nYjPHOXRBvYP+KNN13gdCGNO+FtRA 0r3jR0Sswqv9DB2B5vnzgC5q9qJhFRT2mD35rS4mUau0Ax6iTq3pfnuBP7GH31pX zTlb5Kurv92lpmV9vsp+ZPhH+Ilu34bq022Gy69kxVp8TVB0Dr4= =PEUT -END PGP SIGNATURE- pgpZxB8jo1vcT.pgp Description: PGP signature --- End Message ---
Processed: [bts-link] source package svt-av1
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package svt-av1 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1022870 (http://bugs.debian.org/1022870) > # Bug title: libsvtav1enc1: Fails to allocate memory on 32-bit arm > architectures > # * https://gitlab.com/AOMediaCodec/SVT-AV1/-/issues/1893 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1022870 + fixed-upstream Bug #1022870 [libsvtav1enc1] libsvtav1enc1: Fails to allocate memory on 32-bit arm architectures Added tag(s) fixed-upstream. > usertags 1022870 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1022870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1075374: marked as done (pd-plugin: ftbfs with GCC-14)
Your message dated Thu, 18 Jul 2024 10:05:05 + with message-id and subject line Bug#1075374: fixed in pd-plugin 0.2.1-10 has caused the Debian Bug report #1075374, regarding pd-plugin: ftbfs with GCC-14 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 ow...@bugs.debian.org immediately.) -- 1075374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pd-plugin Version: 0.2.1-9 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/pd-plugin_0.2.1-9_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] /usr/include/pd/m_pd.h:629:27: note: declared here 629 | PD_DEPRECATED EXTERN void verbose(int level, const char *fmt, ...) ATTRIBUTE_FORMAT_PRINTF(2, 3); /* avoid this: use logpost() instead */ | ^~~ plugin~.c: In function ‘plugin_tilde_open_plugin’: plugin~.c:437:3: warning: ‘verbose’ is deprecated [-Wdeprecated-declarations] 437 | verbose(2, "plugin~: open_plugin (x, \"%s\", \"%s\", %ld);", name, lib_name, sample_rate); | ^~~ /usr/include/pd/m_pd.h:629:27: note: declared here 629 | PD_DEPRECATED EXTERN void verbose(int level, const char *fmt, ...) ATTRIBUTE_FORMAT_PRINTF(2, 3); /* avoid this: use logpost() instead */ | ^~~ plugin~.c:443:5: warning: ‘verbose’ is deprecated [-Wdeprecated-declarations] 443 | verbose(1, "plugin~: plugin active"); | ^~~ /usr/include/pd/m_pd.h:629:27: note: declared here 629 | PD_DEPRECATED EXTERN void verbose(int level, const char *fmt, ...) ATTRIBUTE_FORMAT_PRINTF(2, 3); /* avoid this: use logpost() instead */ | ^~~ plugin~.c: In function ‘plugin_tilde_close_plugin’: plugin~.c:452:3: warning: ‘verbose’ is deprecated [-Wdeprecated-declarations] 452 | verbose(2, "plugin~: close_plugin (x)"); | ^~~ /usr/include/pd/m_pd.h:629:27: note: declared here 629 | PD_DEPRECATED EXTERN void verbose(int level, const char *fmt, ...) ATTRIBUTE_FORMAT_PRINTF(2, 3); /* avoid this: use logpost() instead */ | ^~~ plugin~.c:454:3: warning: ‘verbose’ is deprecated [-Wdeprecated-declarations] 454 | verbose(1, "plugin~: destructed plugin successfully"); | ^~~ /usr/include/pd/m_pd.h:629:27: note: declared here 629 | PD_DEPRECATED EXTERN void verbose(int level, const char *fmt, ...) ATTRIBUTE_FORMAT_PRINTF(2, 3); /* avoid this: use logpost() instead */ | ^~~ plugin~.c: In function ‘plugin_tilde_ladspa_search_plugin_callback’: plugin~.c:534:15: warning: ‘verbose’ is deprecated [-Wdeprecated-declarations] 534 | verbose(1, "plugin~: found plugin \"%s\" in library \"%s\"", | ^~~ /usr/include/pd/m_pd.h:629:27: note: declared here 629 | PD_DEPRECATED EXTERN void verbose(int level, const char *fmt, ...) ATTRIBUTE_FORMAT_PRINTF(2, 3); /* avoid this: use logpost() instead */ | ^~~ plugin~.c: In function ‘plugin_tilde_ladspa_open_plugin’: plugin~.c:603:3: warning: ‘verbose’ is deprecated [-Wdeprecated-declarations] 603 | verbose(1, "plugin~: constructed plugin \"%s\" successfully", x->plugin.ladspa.type->Name); | ^~~ /usr/include/pd/m_pd.h:629:27: note: declared here 629 | PD_DEPRECATED EXTER
Processed: Bug#1075374 marked as pending in pd-plugin
Processing control commands: > tag -1 pending Bug #1075374 [src:pd-plugin] pd-plugin: ftbfs with GCC-14 Added tag(s) pending. -- 1075374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967787: marked as done (unicap: depends on deprecated GTK 2)
Your message dated Wed, 17 Jul 2024 19:59:01 +
with message-id
and subject line Bug#967787: fixed in unicap
0.9.12+repack20150328.0.git2c600ae-5
has caused the Debian Bug report #967787,
regarding unicap: depends on deprecated GTK 2
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 ow...@bugs.debian.org
immediately.)
--
967787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unicap
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1
This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.
GTK 2 was superseded by GTK 3 in 2011 (see
<https://bugs.debian.org/947713>). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.
GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.
A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html
Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.
A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.
Regards,
smcv
--- End Message ---
--- Begin Message ---
Source: unicap
Source-Version: 0.9.12+repack20150328.0.git2c600ae-5
Done: IOhannes m zmölnig (Debian/GNU)
We believe that the bug you reported is fixed in the latest version of
unicap, 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 967...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU) (supplier of updated
unicap 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 ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 17 Jul 2024 21:03:48 +0200
Source: unicap
Architecture: source
Version: 0.9.12+repack20150328.0.git2c600ae-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: IOhannes m zmölnig (Debian/GNU)
Closes: 967787 1074621
Changes:
unicap (0.9.12+repack20150328.0.git2c600ae-5) unstable; urgency=medium
.
* Upload to unstable.
.
* Add patch to fix FTBFS dues to invalid empty charset declaration
(Closes: #1074621)
* B-D on pkgconf instead of pkg-config
* Use execute_{before,after}_dh_* instead of override_dh_* where applicable
* Use d/clean
* Update copyright information
+ Modernize 'licensecheck' target
+ Re-generate d/copyright_hints
* Apply 'wrap-and-sort -ast'
* Bump standards version to 4.7.0
.
unicap (0.9.12+repack20150328.0.git2c600ae-4exp1) experimental; urgency=medium
.
[ IOhannes m z
Bug#1076246: marked as done (sndfile-tools: Unused build-dependency on GNU autogen)
Your message dated Wed, 17 Jul 2024 19:58:54 + with message-id and subject line Bug#1076246: fixed in sndfile-tools 1.5-4 has caused the Debian Bug report #1076246, regarding sndfile-tools: Unused build-dependency on GNU autogen 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 ow...@bugs.debian.org immediately.) -- 1076246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sndfile-tools Version: 1.5-3 Severity: normal User: ametz...@debian.org Usertags: autogen-eol Good morning, afaict sndfile-tools' build-dependency on GNU autogen is unused: ametzler@argenau:/tmp/sndfile-tools-1.5$ grep -ril autogen debian/control debian/copyright_hints cu Andreas --- End Message --- --- Begin Message --- Source: sndfile-tools Source-Version: 1.5-4 Done: IOhannes m zmölnig (Debian/GNU) We believe that the bug you reported is fixed in the latest version of sndfile-tools, 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 1076...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated sndfile-tools 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 17 Jul 2024 21:07:36 +0200 Source: sndfile-tools Architecture: source Version: 1.5-4 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 1076246 Changes: sndfile-tools (1.5-4) unstable; urgency=medium . * Drop unused B-D on 'autogen' (Closes: #1076246) * Replace B-D on pkg-config with pkgconf * Bump standards version to 4.7.0 Checksums-Sha1: 3201fbf21b5d37f6007875ca2e4ec3e5499526a1 2365 sndfile-tools_1.5-4.dsc f14ad358814b0ec9b049fc10a267b7100154 5028 sndfile-tools_1.5-4.debian.tar.xz Checksums-Sha256: af0734241554d6babe5398117876713151af686c57ad7a579968cc0f08bf4b12 2365 sndfile-tools_1.5-4.dsc d8d963b190f1cb3d65131fd48b04fdd6d7e67e4db80c1d6ed4f4c29aa8cc9a73 5028 sndfile-tools_1.5-4.debian.tar.xz Files: 79c041b1df7f2f01d77935246a368c90 2365 sound optional sndfile-tools_1.5-4.dsc 99b35d076c4972e280385ac3aaa40d51 5028 sound optional sndfile-tools_1.5-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmaYFqcWHGZvcnVtQHVt bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+BQVD/4+CrUHHajHgSTSRCArYQBF3w/9 cJYj1nt3QjhEKtiSHeLJs/qfmdvUL3u4UxmvHHAaEXHtEm2lBWsJyajsUKLnRn88 bTO13bhS52NY6LI28ZdvogLa7ljB1pTfdL3zvBO+VnCGPfPQpx9OJDw/B2ej0zFx M2Rx0Lh96OkKBptzyoqf3Q427A8id6gZ50ausZ+I+iv9mTxMZ5StO56ajqYf+Fh8 bkuOCPkoNMuXD46tKamVof04Jg0vdfonpE5gSqdJs33H37oWEmKAlBmdgJDUW70d nNsU14A0R93HtpsxBXhR31NomNDDuWcBfP36DIlucSGb4rrmXsacWc6/0XVYLXrc 2S2CJj0gSYLxQYDyXUK7FDOha8NsQf/8ddV3UIo3/MV6fhsGvmKBILkNnjbOJ923 Rz0M2QoVDpi3Xfdm27buLmUE9+GOqExoxfAQFnJvnCVTYaZ9YVQasF+QIgMr9wA5 fsjzf6nYC01w6A5+5AO4VVYZAbdi55bmGQVnCrlrVO8dGK+A0zx2dAN8xls6cQMt RdiFzhPxRwuz3rkL8mqFINdgBsn/1zta8bive1a0wK3YkoXYZFObvYwRw5u2lslP cCSXN60e+f5bzf4IJ9sayz4aDUYYW01MMUvjw7umboT3qUHlQsEIRhTEbwjerFcu J8sAkSjyVo5w+BmuNg== =xGmi -END PGP SIGNATURE- pgpKQelO1Ihmy.pgp Description: PGP signature --- End Message ---
Bug#1074621: marked as done (unicap: FTBFS: /usr/bin/msgfmt: present charset "" is not a portable encoding name)
Your message dated Wed, 17 Jul 2024 19:59:01 +
with message-id
and subject line Bug#1074621: fixed in unicap
0.9.12+repack20150328.0.git2c600ae-5
has caused the Debian Bug report #1074621,
regarding unicap: FTBFS: /usr/bin/msgfmt: present charset "" is not a portable
encoding name
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 ow...@bugs.debian.org
immediately.)
--
1074621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unicap
Version: 0.9.12+repack20150328.0.git2c600ae-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: si...@josefsson.org
Usertags: ftbfs-trixie
Hi. I have tried to rebuild unicap in sid and it fails:
Making all in po
make[3]: Entering directory '/builds/jas/unicap/debian/output/source_dir/po'
file=`echo de | sed 's,.*/,,'`.gmo \
&& rm -f $file && /usr/bin/msgfmt -o $file de.po
file=`echo fr | sed 's,.*/,,'`.gmo \
&& rm -f $file && /usr/bin/msgfmt -o $file fr.po
de.po: warning: Charset "" is not a portable encoding name.
Message conversion to user's charset might not work.
/usr/bin/msgfmt: present charset "" is not a portable encoding name
make[3]: *** [Makefile:94: de.gmo] Error 1
make[3]: *** Waiting for unfinished jobs
See complete build log here:
https://salsa.debian.org/jas/unicap/-/jobs/5917741
/Simon
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: unicap
Source-Version: 0.9.12+repack20150328.0.git2c600ae-5
Done: IOhannes m zmölnig (Debian/GNU)
We believe that the bug you reported is fixed in the latest version of
unicap, 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 1074...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU) (supplier of updated
unicap 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 ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 17 Jul 2024 21:03:48 +0200
Source: unicap
Architecture: source
Version: 0.9.12+repack20150328.0.git2c600ae-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: IOhannes m zmölnig (Debian/GNU)
Closes: 967787 1074621
Changes:
unicap (0.9.12+repack20150328.0.git2c600ae-5) unstable; urgency=medium
.
* Upload to unstable.
.
* Add patch to fix FTBFS dues to invalid empty charset declaration
(Closes: #1074621)
* B-D on pkgconf instead of pkg-config
* Use execute_{before,after}_dh_* instead of override_dh_* where applicable
* Use d/clean
* Update copyright information
+ Modernize 'licensecheck' target
+ Re-generate d/copyright_hints
* Apply 'wrap-and-sort -ast'
* Bump standards version to 4.7.0
.
unicap (0.9.12+repack20150328.0.git2c600ae-4exp1) experimental; urgency=medium
.
[ IOhannes m zmölnig (Debian/GNU) ]
* Set libunicap-doc to MultiArch:foreign
* Rename libunicap-docs to libunicap-doc
* Drop obsolete ${devlibs:Depends}
* Drop unnecessary dependency on libgtk2.0-dev (Closes: #967787)
* Add Build-Depends to symbols file
* Bump standards version to 4.6.0
.
[ Debian Janitor ]
* Use secure URI in Homepage field.
* Set upstream metadata fields: Bug-Database, Bug-Submit.
.
[ Jenkins ]
* Apply multi-arch hints. + libunicap2, libunicap2-dev: Add Multi-Arch: same.
Checksums-Sha1:
1dcef6df9bb2ef050af3ebb7eb432a832acd1fe1 2530
unicap_0.9.12+repack20150328.0.git2c600ae-5.dsc
b209ac5b073ce054835f1f44c9ba24d1c3cb49c3 10716
unicap_0.9.12+repack20150328.0.git2c600ae-5.debian.tar.xz
Checksums-Sha256:
187e9958996921dc33580f2a38c6508bbf35327bb2206cae5f732281fac281ab 2530
unicap_0.9.12+repack20150328.0.git2c600ae-5.dsc
2e168422a583fb63b961ee3b726aee36f65a714e4672d1c9fce246b636b63a39 10716
unicap_0.9.12+repack20150328.0.git2c600ae-5.debian.tar.xz
Files:
bb975eb5412de125a264dc9b216877c3 2530 libs optional
unicap_0.9.12+repack20150328.0.git2c600ae-5.dsc
00f9745668a927997655b9fd8f1c9e08 10716 libs optional
unicap_0.9.12+repack20150328.0.git2c600ae-5.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96
Processed: Re: libavif: missing deps?
Processing commands for cont...@bugs.debian.org: > reassign 1076509 libavif 1.1.0-2 Bug #1076509 [src:libavid] libavif: missing deps? Warning: Unknown package 'src:libavid' Bug reassigned from package 'src:libavid' to 'libavif'. No longer marked as found in versions libavid/1.1.0-2. Ignoring request to alter fixed versions of bug #1076509 to the same values previously set Bug #1076509 [libavif] libavif: missing deps? There is no source info for the package 'libavif' at version '1.1.0-2' with architecture '' Unable to make a source version for version '1.1.0-2' Marked as found in versions 1.1.0-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1076509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060600: marked as done (midisport-firmware: Please switch Build-Depends to systemd-dev)
Your message dated Wed, 17 Jul 2024 15:55:08 +0200 with message-id <1158e40a-8a34-4d7c-826b-f4d777974...@debian.org> and subject line Re: midisport-firmware: Please switch Build-Depends to systemd-dev has caused the Debian Bug report #1060600, regarding midisport-firmware: Please switch Build-Depends to systemd-dev 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 ow...@bugs.debian.org immediately.) -- 1060600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: midisport-firmware Version: 1.2-6 Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: systemd-dev Hi, your package midisport-firmware declares a Build-Depends on systemd and/or udev. In most cases, this build dependency is added to get the paths that are defined in udev.pc or systemd.pc (via pkgconfig). Since systemd_253-2 [1], these two pkgconfig files have been split into a separate package named systemd-dev. This package is arch:all, so even available on non-Linux architectures, which will simplify the installation of upstream provided service files / udev rules. To not make existing source packages FTBFS, the systemd and udev package have a Depends: systemd-dev. This dependency will be removed at some point though before trixie is released. Once this happens, this issue will be bumped to RC. Please update your build dependencies accordingly at your earliest convenience. If all you need is the systemd.pc or udev.pc pkgconfig file, please replace any systemd or udev Build-Depends with systemd-dev. In most cases that should be sufficient. If your package needs further resources from systemd or udev to build successfully, it's fine to keep those Build-Depends in addition to systemd-dev. To ease stable backports, a version of systemd with those changes is provided via bookworm-backports. In case you have further questions, please contact the systemd team at . On behalf of the systemd team, Michael [1] https://salsa.debian.org/systemd-team/systemd/-/merge_requests/196 --- End Message --- --- Begin Message --- Version: 1.2-6 It appears this was fixed by https://salsa.debian.org/multimedia-team/midisport-firmware/-/commit/9ff0731c1f5caa0f10cb6e81c0a20e419667c977 OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message ---
Processed: Bug#1074621 marked as pending in unicap
Processing control commands: > tag -1 pending Bug #1074621 [src:unicap] unicap: FTBFS: /usr/bin/msgfmt: present charset "" is not a portable encoding name Added tag(s) pending. -- 1074621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074621 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021606: marked as done (libyuv: FTBFS on hppa - broken googletest)
Your message dated Tue, 16 Jul 2024 15:36:09 + with message-id and subject line Bug#1021606: fixed in libyuv 0.0.1888.20240710-3 has caused the Debian Bug report #1021606, regarding libyuv: FTBFS on hppa - broken googletest 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 ow...@bugs.debian.org immediately.) -- 1021606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libyuv Version: 0.0~git20220923.b9adaef-1 Severity: normal Tags: ftbfs patch Dear Maintainer, The following tests fail on hppa: [--] Global test environment tear-down [==] 3211 tests from 8 test suites ran. (1597834 ms total) [ PASSED ] 3169 tests. [ FAILED ] 42 tests, listed below: [ FAILED ] LibYUVConvertTest.TestNoDither [ FAILED ] LibYUVConvertTest.TestDither [ FAILED ] LibYUVConvertTest.I420ToARGBToRGB565_Any [ FAILED ] LibYUVConvertTest.I420ToARGBToRGB565_Unaligned [ FAILED ] LibYUVConvertTest.I420ToARGBToRGB565_Invert [ FAILED ] LibYUVConvertTest.I420ToARGBToRGB565_Opt [ FAILED ] LibYUVConvertTest.I422ToARGBToRGB565_Any [ FAILED ] LibYUVConvertTest.I422ToARGBToRGB565_Unaligned [ FAILED ] LibYUVConvertTest.I422ToARGBToRGB565_Invert [ FAILED ] LibYUVConvertTest.I422ToARGBToRGB565_Opt [ FAILED ] LibYUVConvertTest.ARGBToAR30ToARGB_Any [ FAILED ] LibYUVConvertTest.ARGBToAR30ToARGB_Unaligned [ FAILED ] LibYUVConvertTest.ARGBToAR30ToARGB_Invert [ FAILED ] LibYUVConvertTest.ARGBToAR30ToARGB_Opt [ FAILED ] LibYUVConvertTest.ABGRToAR30ToABGR_Any [ FAILED ] LibYUVConvertTest.ABGRToAR30ToABGR_Unaligned [ FAILED ] LibYUVConvertTest.ABGRToAR30ToABGR_Invert [ FAILED ] LibYUVConvertTest.ABGRToAR30ToABGR_Opt [ FAILED ] LibYUVConvertTest.AR30ToARGBToABGR_Any [ FAILED ] LibYUVConvertTest.AR30ToARGBToABGR_Unaligned [ FAILED ] LibYUVConvertTest.AR30ToARGBToABGR_Invert [ FAILED ] LibYUVConvertTest.AR30ToARGBToABGR_Opt [ FAILED ] LibYUVConvertTest.AR30ToABGRToARGB_Any [ FAILED ] LibYUVConvertTest.AR30ToABGRToARGB_Unaligned [ FAILED ] LibYUVConvertTest.AR30ToABGRToARGB_Invert [ FAILED ] LibYUVConvertTest.AR30ToABGRToARGB_Opt [ FAILED ] LibYUVConvertTest.ARGBToAB30ToARGB_Any [ FAILED ] LibYUVConvertTest.ARGBToAB30ToARGB_Unaligned [ FAILED ] LibYUVConvertTest.ARGBToAB30ToARGB_Invert [ FAILED ] LibYUVConvertTest.ARGBToAB30ToARGB_Opt [ FAILED ] LibYUVConvertTest.ABGRToAB30ToABGR_Any [ FAILED ] LibYUVConvertTest.ABGRToAB30ToABGR_Unaligned [ FAILED ] LibYUVConvertTest.ABGRToAB30ToABGR_Invert [ FAILED ] LibYUVConvertTest.ABGRToAB30ToABGR_Opt [ FAILED ] LibYUVConvertTest.AB30ToARGBToABGR_Any [ FAILED ] LibYUVConvertTest.AB30ToARGBToABGR_Unaligned [ FAILED ] LibYUVConvertTest.AB30ToARGBToABGR_Invert [ FAILED ] LibYUVConvertTest.AB30ToARGBToABGR_Opt [ FAILED ] LibYUVConvertTest.AB30ToABGRToARGB_Any [ FAILED ] LibYUVConvertTest.AB30ToABGRToARGB_Unaligned [ FAILED ] LibYUVConvertTest.AB30ToABGRToARGB_Invert [ FAILED ] LibYUVConvertTest.AB30ToABGRToARGB_Opt 42 FAILED TESTS YOU HAVE 40 DISABLED TESTS I believe these are caused by broken googletest on big-endian architectures. Please add hppa to the list of arches with broken googletest. Thanks, Dave Anglin -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: hppa (parisc64) Kernel: Linux 5.19.14+ (SMP w/4 CPU threads) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) --- rules.save 2022-10-11 17:05:53.037246365 + +++ rules 2022-10-11 17:06:19.267489103 + @@ -26,7 +26,7 @@ endif # Known broken googletest -ifneq (,$(filter $(DEB_HOST_ARCH), armel s390x powerpc ppc64 sparc64)) +ifneq (,$(filter $(DEB_HOST_ARCH), armel hppa s390x powerpc ppc64 sparc64)) LIBYUV_TEST_FLAG = OFF endif --- End Message --- --- Begin Message --- Source: libyuv Source-Version: 0.0.1888.20240710-3 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of libyuv, 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 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated libyuv package) (This message was generated automatically
Bug#899241: marked as done (Amplifier detected by source from program developer but not by Debian package.)
Your message dated Tue, 16 Jul 2024 12:50:13 +0200
with message-id
and subject line Re: Amplifier detected by source from program developer but
not by Debian package.
has caused the Debian Bug report #899241,
regarding Amplifier detected by source from program developer but not by Debian
package.
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 ow...@bugs.debian.org
immediately.)
--
899241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mustang-plugVersion: 1.2-1+b1Severity: grave
PROBLEMDear Maintainer,
I own a Mustang IV and Mustang I (both v2) and am used to using the
Fender Fuse software to control both (this works perfectly with both).
I have a reasonably solid understanding of Linux, have come across your
"Plug" package and would like to use it.
Before I was aware of your package, I had installed the Plug software
directly from the develope's website (v1.2). The install went
perfectly: - unpacked to /home/me/Programs/Plug, - ran: apt install
qt4.dev libusb-1.0-0-dev - ran: qmake plug.pro - ran make (lots of
output...) - ran: export PATH=$PATH:/home/me/Programs/PlugEntering
"plug" into a terminal as user "me", ran the program and it showed
sound patches I had saved in both amps themselves. So... great:
connection no problem, loading from amps, no problem.
Then I became aware of your package and, as always, would prefer to use
the Stretch repos than source. So, I installed your package. It
installed with no error or messages.
I connected to my Mustang I. It connected immediately and I was able to
load the sound patches from the amp. Great. But when I connected to my
Mustang IV... nothing.
So, I checked the developer's website and there was some advice... - I
checked the existence of the group "plugdev"; it existed and I was
already a member of it. - I followed the developer's advice to create a
file called "50-mustang.rules" in /etc/udev/rules.d and added the
following to it:
***SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0004",
GROUP="plugdev"SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0005",
GROUP="plugdev"SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0006",
GROUP="plugdev"SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0007",
GROUP="plugdev"SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0010",
GROUP="plugdev"SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0011",
GROUP="plugdev"SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0012",
GROUP="plugdev"SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0013",
GROUP="plugdev"SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0014",
GROUP="plugdev"SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0015",
GROUP="plugdev"SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0016",
GROUP="plugdev"SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0017", GROUP="plugdev*** -
restarted udev.Nothing: the Mustang I still worked; the Mustang IV, no
joy.
- I added myself to the udev group. No joy. - I updated firmware using
FUSE, no joy.END PROBLEM
REPORTBUG OUTPUT-- System Information:Debian Release: 9.4 APT prefers
stable-updates APT policy: (500, 'stable-updates'), (500,
'stable')Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-6-amd64 (SMP w/8 CPU cores)Locale: LANG=en_GB.UTF-
8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8
(charmap=UTF-8)Shell: /bin/sh linked to /bin/dashInit: systemd (via
/run/systemd/system)
Versions of packages mustang-plug depends on:ii libc6
Processed (with 5 errors): Re: Bug#1076414: libavif16: multiple dependencies on librav1e
Processing commands for cont...@bugs.debian.org: > reassign 1076414 librav1e0.7 Bug #1076414 [libavif16] libavif16: multiple dependencies on librav1e Bug reassigned from package 'libavif16' to 'librav1e0.7'. No longer marked as found in versions libavif/1.1.0-2. Ignoring request to alter fixed versions of bug #1076414 to the same values previously set > found 1076414 librav1e0.7/0.7.1-3 Bug #1076414 [librav1e0.7] libavif16: multiple dependencies on librav1e The source librav1e0.7 and version 0.7.1-3 do not appear to match any binary packages Marked as found in versions librav1e0.7/0.7.1-3. > fixed 1076414 librav1e0.7/0.7.1-4 Bug #1076414 [librav1e0.7] libavif16: multiple dependencies on librav1e The source librav1e0.7 and version 0.7.1-4 do not appear to match any binary packages Marked as fixed in versions librav1e0.7/0.7.1-4. > close 1076414 Bug #1076414 [librav1e0.7] libavif16: multiple dependencies on librav1e Marked Bug as done > On Mon, Jul 15, 2024 at 05:13:08PM -0600, hhe07 wrote: Unknown command or malformed arguments to command. > > Package: libavif16 Unknown command or malformed arguments to command. > [..] Unknown command or malformed arguments to command. > > dpkg: error processing archive > > /var/cache/apt/archives/librav1e0.7_0.7.1-3+b1_amd64.deb (--unpack): Unknown command or malformed arguments to command. > > trying to overwrite '/usr/lib/x86_64-linux-gnu/librav1e.so.0.7.1', which > > is also in package librav1e0:amd64 0.7.1-2 Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 1076414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072423: marked as done (handbrake: FTBFS with ffmpeg 7.0: ../libhb/audio_resample.c:93:19: error: ‘AV_CH_LAYOUT_NATIVE’ undeclared (first use in this function); did you mean ‘AV_CH_LAYOUT_CUBE’?)
Your message dated Sat, 13 Jul 2024 21:35:19 + with message-id and subject line Bug#1072423: fixed in handbrake 1.8.1+ds1-1 has caused the Debian Bug report #1072423, regarding handbrake: FTBFS with ffmpeg 7.0: ../libhb/audio_resample.c:93:19: error: ‘AV_CH_LAYOUT_NATIVE’ undeclared (first use in this function); did you mean ‘AV_CH_LAYOUT_CUBE’? 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 ow...@bugs.debian.org immediately.) -- 1072423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: handbrake Version: 1.7.2+ds1-1 Severity: important Tags: trixie sid ftbfs Usertags: ffmpeg-7.0 Hi, during a rebuild of the reverse dependencies for the transition to ffmpeg 7.0, your package failed to build Relevant part (hopefully): > /usr/bin/gcc -std=gnu99 -pipe -fmessage-length=0 -Wall -Wno-format-truncation > -g2 -O3 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -mbranch-protection=standard -fstack-protector-strong > -D_FORTIFY_SOURCE=2 -D__LIBHB__ -DSYS_LINUX -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 -DHAS_STRERROR_R -I./libhb/ -I./contrib/include > -I/usr/include/libxml2 -c ../libhb/audio_resample.c -o libhb/audio_resample.o > ../libhb/audio_resample.c: In function ‘is_mono’: > ../libhb/audio_resample.c:93:19: error: ‘AV_CH_LAYOUT_NATIVE’ undeclared > (first use in this function); did you mean ‘AV_CH_LAYOUT_CUBE’? >93 | if (layout == AV_CH_LAYOUT_NATIVE) > | ^~~ > | AV_CH_LAYOUT_CUBE > ../libhb/audio_resample.c:93:19: note: each undeclared identifier is reported > only once for each function it appears in > make[1]: *** [../libhb/module.rules:12: libhb/audio_resample.o] Error 1 The full build log is available from: https://people.debian.org/~sramacher/ffmpeg-7.0/handbrake_arm64.build ffmpeg 7.0 is available in experimental. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: handbrake Source-Version: 1.8.1+ds1-1 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of handbrake, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated handbrake 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 13 Jul 2024 23:08:59 +0200 Source: handbrake Architecture: source Version: 1.8.1+ds1-1 Distribution: experimental Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 1072423 Changes: handbrake (1.8.1+ds1-1) experimental; urgency=medium . * New upstream version 1.8.1+ds1 - Fix build with ffmpeg 7.0 (Closes: #1072423) * debian/control: - Bump Standards-Version - Bump libav* build dependencies - Add pkgconf to Build-Depends - Switch libgtk-3-dev to libgtk-4-dev - Remove gstreamer (Build-)Depends * debian/patches: Refresh patches Checksums-Sha1: 0161f8a70289d29a339082087cb79a63a18b2133 2165 handbrake_1.8.1+ds1-1.dsc 5ec8ba1546c8f7a2480c6b44f2d09de84092e635 5574036 handbrake_1.8.1+ds1.orig.tar.xz b838358cd577c410ddd2926435e3f35a3cc8d362 23916 handbrake_1.8.1+ds1-1.debian.tar.xz 68da1bd1a7d8057a966d5fe6c1845fb6c03c9eeb 18882 handbrake_1.8.1+ds1-1_source.buildinfo Checksums-Sha256: 6ffc70cfcec8ba16fd17a5f941f9660777922631f7c863bc826c79a561a584b6 2165 handbrake_1.8.1+ds1-1.dsc a93ad652f8b338086e83751a0dba18a1d5a90b9052ede5737a2dcf3b80c4ac46 5574036 handbrake_1.8.1+ds1.orig.tar.xz 4b8bb19ba905630fae42a03a2edda2b8dd5d8dc9657f194e2f2fe0d5a0942bc7 23916 handbrake_1.8.1+ds1-1.debian.tar.xz bd5adf7b331d3154568a93429d5d0887953e9a0eef9f38d5bc1cdc756489aa17 18882 handbrake_1.8.1+ds1-1_source.buildinfo Files: 5dcc6bf9bb0289c3ee9867eba175895f 2165 graphics optional handbrake_1.8.1+ds1-1.dsc 68dbdd04334ac98dce67f703580ef12f 5
Processed: notfound 1076266 in 1.13-1, found 1076266 in 1.2.2-1
Processing commands for cont...@bugs.debian.org: > notfound 1076266 1.13-1 Bug #1076266 [src:libsndfile] libsndfile: Build-Depends on GNU autogen The source 'libsndfile' and version '1.13-1' do not appear to match any binary packages No longer marked as found in versions libsndfile/1.13-1. > # fixup copy and paste error > found 1076266 1.2.2-1 Bug #1076266 [src:libsndfile] libsndfile: Build-Depends on GNU autogen Marked as found in versions libsndfile/1.2.2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1076266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072007: marked as done (Build kvazaar plugin)
Your message dated Sat, 13 Jul 2024 11:00:14 + with message-id and subject line Bug#1072007: fixed in libheif 1.17.6-4 has caused the Debian Bug report #1072007, regarding Build kvazaar plugin 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 ow...@bugs.debian.org immediately.) -- 1072007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libheif Version: 1.17.6-1 Severity: wishlist Now that kvazaar is available in Debian [1], the corresponding plugin should be built for libheif. [1] https://packages.debian.org/source/sid/kvazaar OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: libheif Source-Version: 1.17.6-4 Done: Joachim Bauch We believe that the bug you reported is fixed in the latest version of libheif, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joachim Bauch (supplier of updated libheif 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Jun 2024 09:43:29 +0200 Source: libheif Binary: heif-gdk-pixbuf heif-gdk-pixbuf-dbgsym heif-thumbnailer heif-thumbnailer-dbgsym libheif-dev libheif-examples libheif-examples-dbgsym libheif-plugin-aomdec libheif-plugin-aomdec-dbgsym libheif-plugin-aomenc libheif-plugin-aomenc-dbgsym libheif-plugin-dav1d libheif-plugin-dav1d-dbgsym libheif-plugin-ffmpegdec libheif-plugin-ffmpegdec-dbgsym libheif-plugin-j2kdec libheif-plugin-j2kdec-dbgsym libheif-plugin-j2kenc libheif-plugin-j2kenc-dbgsym libheif-plugin-jpegdec libheif-plugin-jpegdec-dbgsym libheif-plugin-jpegenc libheif-plugin-jpegenc-dbgsym libheif-plugin-kvazaar libheif-plugin-kvazaar-dbgsym libheif-plugin-libde265 libheif-plugin-libde265-dbgsym libheif-plugin-rav1e libheif-plugin-rav1e-dbgsym libheif-plugin-svtenc libheif-plugin-svtenc-dbgsym libheif-plugin-x265 libheif-plugin-x265-dbgsym libheif1 libheif1-dbgsym Architecture: source arm64 Version: 1.17.6-4 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Joachim Bauch Description: heif-gdk-pixbuf - ISO/IEC 23008-12:2017 HEIF file format decoder - gdk-pixbuf loade heif-thumbnailer - ISO/IEC 23008-12:2017 HEIF file format decoder - thumbnailer libheif-dev - ISO/IEC 23008-12:2017 HEIF file format decoder - development file libheif-examples - ISO/IEC 23008-12:2017 HEIF file format decoder - examples libheif-plugin-aomdec - ISO/IEC 23008-12:2017 HEIF file format decoder - aomdec plugin libheif-plugin-aomenc - ISO/IEC 23008-12:2017 HEIF file format decoder - aomenc plugin libheif-plugin-dav1d - ISO/IEC 23008-12:2017 HEIF file format decoder - dav1d plugin libheif-plugin-ffmpegdec - ISO/IEC 23008-12:2017 HEIF file format decoder - ffmpegdec plugin libheif-plugin-j2kdec - ISO/IEC 23008-12:2017 HEIF file format decoder - j2kdec plugin libheif-plugin-j2kenc - ISO/IEC 23008-12:2017 HEIF file format decoder - j2kenc plugin libheif-plugin-jpegdec - ISO/IEC 23008-12:2017 HEIF file format decoder - jpegdec plugin libheif-plugin-jpegenc - ISO/IEC 23008-12:2017 HEIF file format decoder - jpegenc plugin libheif-plugin-kvazaar - ISO/IEC 23008-12:2017 HEIF file format decoder - kvazaar plugin libheif-plugin-libde265 - ISO/IEC 23008-12:2017 HEIF file format decoder - libde265 plugin libheif-plugin-rav1e - ISO/IEC 23008-12:2017 HEIF file format decoder - rav1e plugin libheif-plugin-svtenc - ISO/IEC 23008-12:2017 HEIF file format decoder - svtenc plugin libheif-plugin-x265 - ISO/IEC 23008-12:2017 HEIF file format decoder - x265 plugin libheif1 - ISO/IEC 23008-12:2017 HEIF file format decoder - shared library Closes: 1072007 Changes: libheif (1.17.6-4) unstable; urgency=medium . * Add kvazaar plugin (Closes: #1072007). * d/copyright: Update DEP-5 license ids, add missing exceptions. Checksums-Sha1: 6b52bd7015fb575c3df2d255ef6814b69127f76d 3497 libheif_1.17.6-4.dsc 161ae1fd91f56156298e881f3ba51611910e9c4c 1433302 libheif_1.17.6.orig.tar.gz eaa8f0ecaa3b4c9d74d706f4aebc00eb82ea153f 11292 libheif_1.17.6-4
Bug#1070492: marked as done (mixxx: Tries to use the network during build)
Your message dated Fri, 12 Jul 2024 23:18:06 + with message-id and subject line Bug#1070492: fixed in mixxx 2.4.0+dfsg-3 has caused the Debian Bug report #1070492, regarding mixxx: Tries to use the network during build 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 ow...@bugs.debian.org immediately.) -- 1070492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mixxx Version: 2.4.0+dfsg-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] --- LOG END --- error: downloading 'https://github.com/xsco/libdjinterop/archive/refs/tags/0.20.1.tar.gz' failed status_code: 6 status_string: "Couldn't resolve host name" log: --- LOG BEGIN --- Could not resolve host: github.com Closing connection --- LOG END --- error: downloading 'https://launchpad.net/~xsco/+archive/ubuntu/djinterop/+sourcefiles/libdjinterop/0.20.1-0ubuntu1/libdjinterop_0.20.1.orig.tar.gz' failed status_code: 6 status_string: "Couldn't resolve host name" log: --- LOG BEGIN --- Could not resolve host: launchpad.net Closing connection --- LOG END --- make[4]: *** [CMakeFiles/libdjinterop.dir/build.make:102: libdjinterop-prefix/src/libdjinterop-stamp/libdjinterop-download] Error 1 make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[3]: *** [CMakeFiles/Makefile2:317: CMakeFiles/libdjinterop.dir/all] Error 2 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[2]: *** [Makefile:169: all] Error 2 make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j2 "INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2 make[1]: *** [debian/rules:21: override_dh_auto_build] Error 25 make[1]: Leaving directory '/<>' make: *** [debian/rules:15: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 The build was made using the unshare backend of sbuild, which does not allow network access. If you need a full build log, it also fails here for the same reason: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mixxx.html (X-Debian-Cc: Jochen, as we are tracking all packages which ftbfs with unshare) Thanks. --- End Message --- --- Begin Message --- Source: mixxx Source-Version: 2.4.0+dfsg-3 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of mixxx, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated mixxx 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 12 Jul 2024 17:10:10 -0400 Source: mixxx Architecture: source Version: 2.4.0+dfsg-3 Distribution: unstable Urgency: high Maintainer: Debian Multimedia Maintainers Changed-By: Boyuan Yang Closes: 1070492 Changes: mixxx (2.4.0+dfsg-3) unstable; urgency=high . * Team upload. * debian/patches/0005-Allow-libdjinterop-0.21.0.patch: Add patch to allow libdjinterop 0.21.0. * debian/control: + Add missing build-dependency on libdjinterop-dev. (Closes: #1070492) + Remove hardcoded build-dependency on libvamp-*. Use the development package vamp-plugin-sdk instead to implicitly pull them in and to avoid the t64 library suffix problem. Checksums-Sha1: 6459d444795b89ae85c514a7cc0dc61f6ee6e451 3018 mixxx_2.4.0+dfsg-3.dsc a136b9cb1c432a3854a3f4c8756ce006a2e378f4 22070072 mixxx_2.4.0+dfsg.orig.tar.xz be9297b67ec2135c4a6fdc220f98b11a376be7bd 28244 mixxx_2.4.0+dfsg-3.debian.tar.xz 7388d37742eeb1c4a963075885fed6053183eae0 18855 mixxx_2.4.0+dfsg-3_amd64.buildinfo Checksums-Sha256: 5592e91
Processed: kodi: please rebuild against flatbuffers
Processing control commands: > affects -1 + src:flatbuffers Bug #1076176 [src:kodi] kodi: please rebuild against flatbuffers Added indication that 1076176 affects src:flatbuffers -- 1076176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: (No Subject)
Processing commands for cont...@bugs.debian.org: > forwarded 1022870 https://gitlab.com/AOMediaCodec/SVT-AV1/-/issues/1893 Bug #1022870 [libsvtav1enc1] libsvtav1enc1: Fails to allocate memory on 32-bit arm architectures Set Bug forwarded-to-address to 'https://gitlab.com/AOMediaCodec/SVT-AV1/-/issues/1893'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1022870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1074370 is important
Processing commands for cont...@bugs.debian.org: > # temporarily disabled asm support on armel and armhf > severity 1074370 important Bug #1074370 [src:ffmpeg] ffmpeg: Fails to build on armel & armhf Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1074370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031925: marked as done ([INTL:ro] Romanian debconf templates translation of jackd2)
Your message dated Mon, 08 Jul 2024 21:19:43 + with message-id and subject line Bug#1031925: fixed in jackd2 1.9.22~dfsg-2 has caused the Debian Bug report #1031925, regarding [INTL:ro] Romanian debconf templates translation of jackd2 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 ow...@bugs.debian.org immediately.) -- 1031925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031925 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jackd2 Severity: wishlist Tags: l10n, patch Dear Maintainer, Please find attached the Romanian translation of the jackd2 file. Thanks, Remus-Gabriel jackd2_debconf_ro.po Description: Binary data --- End Message --- --- Begin Message --- Source: jackd2 Source-Version: 1.9.22~dfsg-2 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of jackd2, 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 1031...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated jackd2 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Jul 2024 23:06:15 +0200 Source: jackd2 Architecture: source Version: 1.9.22~dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 1031925 Changes: jackd2 (1.9.22~dfsg-2) unstable; urgency=medium . [ Remus-Gabriel Chelu ] * Add translation for Romanian (Closes: #1031925) . [ Sebastian Ramacher ] * debian/control: - Drop unused Build-Depends - Restrict libffado-dev Build-Depends to architectures where needed Checksums-Sha1: a0901fcc9fee636db5ed0064bf6465cb53e5f623 1801 jackd2_1.9.22~dfsg-2.dsc 19a36473bb94c0c31bdf435ffd4cb25116ae32ad 65788 jackd2_1.9.22~dfsg-2.debian.tar.xz 1b9a2507443bcad34951726b570e21ffd15e41ec 8872 jackd2_1.9.22~dfsg-2_amd64.buildinfo Checksums-Sha256: 650fe02e80d52803142edfad7bbeddc3106686e7720abd11fe363193924ca7d5 1801 jackd2_1.9.22~dfsg-2.dsc 08b536f6f55e077562102d035b0691654c02c43ea7f00cea9a52eb4a872f3cd0 65788 jackd2_1.9.22~dfsg-2.debian.tar.xz 310e485d984ab5353d3f9dbffca153bdf5f69c1a22543280bb69a837a30c22f3 8872 jackd2_1.9.22~dfsg-2_amd64.buildinfo Files: 393c4d10c4b02157bda5808d1b2dc621 1801 sound optional jackd2_1.9.22~dfsg-2.dsc 4d0547c15d9f786bbea3f7a257f287d0 65788 sound optional jackd2_1.9.22~dfsg-2.debian.tar.xz 4965770d69793a9f4d7a5b80450a22c0 8872 sound optional jackd2_1.9.22~dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZoxWBQAKCRAhk2s2YA/N iXUAAQCgiHNthI317SmWAKQpUI+xpDTodpTUzg1gYuROEsBZCwEA2fPnmTjTedGk 5pl4vzPo10ouJEbLqsNEYYYH/dswTw4= =bxzf -END PGP SIGNATURE- pgpz6T3yvEMtE.pgp Description: PGP signature --- End Message ---
Processed: closing 773329
Processing commands for cont...@bugs.debian.org: > # invalid; fixed in rosegarden > close 773329 Bug #773329 [libjack-jackd2-dev] Incorrect Cflags line in jack.pc Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 773329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773329 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 795316
Processing commands for cont...@bugs.debian.org: > # not affected by g++5 ABI transition > close 795316 Bug #795316 [jackd2] jackd2: Suggestion to fix overly-liberal shlibs for libjacknet Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 795316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 670112
Processing commands for cont...@bugs.debian.org: > # fixed a long time ago > close 670112 1.9.14_dfsg-1 Bug #670112 [jackd2] jackd2: Jackd will not start if X not running. There is no source info for the package 'jackd2' at version '1.9.14_dfsg-1' with architecture '' Unable to make a source version for version '1.9.14_dfsg-1' Marked as fixed in versions 1.9.14_dfsg-1. Bug #670112 [jackd2] jackd2: Jackd will not start if X not running. Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 670112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 979094
Processing commands for cont...@bugs.debian.org: > # readline dependency was dropped > close 979094 1.9.22~dfsg-1 Bug #979094 [jackd2] Legally problematic GPL-3+ readline dependency There is no source info for the package 'jackd2' at version '1.9.22~dfsg-1' with architecture '' Unable to make a source version for version '1.9.22~dfsg-1' Marked as fixed in versions 1.9.22~dfsg-1. Bug #979094 [jackd2] Legally problematic GPL-3+ readline dependency Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 979094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074647: marked as done (jackd2: FTBFS: ModuleNotFoundError: No module named 'imp')
Your message dated Mon, 08 Jul 2024 13:34:08 +
with message-id
and subject line Bug#1074647: fixed in jackd2 1.9.22~dfsg-1
has caused the Debian Bug report #1074647,
regarding jackd2: FTBFS: ModuleNotFoundError: No module named 'imp'
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 ow...@bugs.debian.org
immediately.)
--
1074647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jackd2
Version: 1.9.21~dfsg-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 ./waf configure \
> --prefix=/usr --classic --example-tools \
> --libdir=/usr/lib/x86_64-linux-gnu \
> --alsa --dbus --firewire \
> CC='x86_64-linux-gnu-gcc' CXX='x86_64-linux-gnu-g++'
> PKGCONFIG='x86_64-linux-gnu-pkgconf'
> /<>/waflib/Utils.py:733: SyntaxWarning: invalid escape sequence
> '\d'
> return re.split('\d+$', s)[0]
> /<>/waflib/ConfigSet.py:14: SyntaxWarning: invalid escape
> sequence '\ '
> re_imp = re.compile('^(#)*?([^#=]*?)\ =\ (.*?)$', re.M)
> /<>/waflib/ansiterm.py:267: SyntaxWarning: invalid escape
> sequence '\['
> ansi_tokens = re.compile('(?:\x1b\[([0-9?;]*)([a-zA-Z])|([^\x1b]+))')
> /<>/waflib/Context.py:610: SyntaxWarning: invalid escape
> sequence '\_'
> """
> Traceback (most recent call last):
> File "/<>/./waf", line 166, in
> from waflib import Scripting
> File "/<>/waflib/Scripting.py", line 10, in
> from waflib import Utils, Configure, Logs, Options, ConfigSet, Context,
> Errors, Build, Node
> File "/<>/waflib/Configure.py", line 16, in
> from waflib import ConfigSet, Utils, Options, Logs, Context, Build, Errors
> File "/<>/waflib/Options.py", line 14, in
> from waflib import Logs, Utils, Context, Errors
> File "/<>/waflib/Context.py", line 9, in
> import os, re, imp, sys
> ModuleNotFoundError: No module named 'imp'
> make[1]: *** [debian/rules:22: override_dh_auto_configure] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/07/02/jackd2_1.9.21~dfsg-3_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240702=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: jackd2
Source-Version: 1.9.22~dfsg-1
Done: Sebastian Ramacher
We believe that the bug you reported is fixed in the latest version of
jackd2, 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 1074...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastian Ramacher (supplier of updated jackd2 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 ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 08 Jul 2024 15:25:39 +0200
Source: jackd2
Architecture: source
Version: 1.9.22~dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Sebastian Ramacher
Closes: 1074647
Changes:
jackd2 (1.9.22~dfsg-1) unstable; urgency=medium
.
* Team upload
.
[ Nicholas D Steeves ]
* Mark reproducibility patches as forwarded, and set URL
.
[ Sebastian Ramacher ]
* New upstream version 1.9.22~dfsg
* debian/patches:
- Remove patch
Processed: Bug#1074647 marked as pending in jackd2
Processing control commands: > tag -1 pending Bug #1074647 [src:jackd2] jackd2: FTBFS: ModuleNotFoundError: No module named 'imp' Added tag(s) pending. -- 1074647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: mplayer: ftbfs with GCC-14
Processing control commands: > forwarded -1 https://trac.mplayerhq.hu/ticket/2424 Bug #1075294 [src:mplayer] mplayer: ftbfs with GCC-14 Set Bug forwarded-to-address to 'https://trac.mplayerhq.hu/ticket/2424'. > tags -1 upstream Bug #1075294 [src:mplayer] mplayer: ftbfs with GCC-14 Added tag(s) upstream. -- 1075294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075294 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074079: marked as done (libass9: regression from 0.17.1 causes wrong font width variant to be selected)
Your message dated Thu, 04 Jul 2024 18:04:24 + with message-id and subject line Bug#1074079: fixed in libass 1:0.17.3-1 has caused the Debian Bug report #1074079, regarding libass9: regression from 0.17.1 causes wrong font width variant to be selected 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 ow...@bugs.debian.org immediately.) -- 1074079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libass9 Version: 1:0.17.2-2 Severity: normal X-Debbugs-Cc: cherri...@protonmail.com Dear Maintainer, A regression bug in 0.17.2 causes the default variant for Noto Sans to be Noto Sans Condensed, not Noto Sans Regular. Potentially, a lot of other fonts are affected as well. This causes the default user interface in mpv to display text that is harder to read. The bug is solved in the latest git version. A temporary workaround is to set osd-font and sub-font to Noto Sans Regular for mpv, instead of the default value of sans-serif. This might also affect ASS subtitles that specify a certain font, though I haven't tested it. https://github.com/libass/libass/issues/770 Additional screenshots of the issue can be found at this forum discussion: https://forum.manjaro.org/t/mpv-has-switched-to-a-very-narrow-font/162390 -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.8.12-amd64 (SMP w/24 CPU threads; PREEMPT) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: libass Source-Version: 1:0.17.3-1 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of libass, 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 1074...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated libass 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 04 Jul 2024 19:58:16 +0200 Source: libass Architecture: source Version: 1:0.17.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 1074079 Changes: libass (1:0.17.3-1) unstable; urgency=medium . * New upstream version 0.17.3 - Fix regression with font selection (Closes: #1074079) * debian/libass9.symbols: Add new symbols Checksums-Sha1: 8b2293f50c1696db3183fb79f843c25227d02314 1765 libass_0.17.3-1.dsc 022a457e71e69086938d401a9ad100c9c884567e 442744 libass_0.17.3.orig.tar.xz c6af8b9bb3f411540e1d4608af8326f0cf13b0b5 858 libass_0.17.3.orig.tar.xz.asc d8a7342f70d07d346ee8abb464a44ef8b68e3d1e 16772 libass_0.17.3-1.debian.tar.xz 08c7d5be7fe40dbd3e11427101ae77692dd7fefc 8519 libass_0.17.3-1_amd64.buildinfo Checksums-Sha256: e46786cf1e89bb54a07fc97f27bb0b69ac0d83f6a80b3720c6ce3c6ca07c7cd3 1765 libass_0.17.3-1.dsc eae425da50f0015c21f7b3a9c7262a910f0218af469e22e2931462fed3c50959 442744 libass_0.17.3.orig.tar.xz 71383b2d1138bf13008d2919da911a2c381bb196fe546571e2698e44d336b7b1 858 libass_0.17.3.orig.tar.xz.asc 2c5202d794459c5ac71251453981e445e84092751435d8d83ac715faf97587f4 16772 libass_0.17.3-1.debian.tar.xz e6c221a4cc24aa7b2ef4624c084bd192187b88b96e989fc0309f72feac779a67 8519 libass_0.17.3-1_amd64.buildinfo Files: e6dfd62cf4535e3ae69a9f9bf11e472b 1765 libs optional libass_0.17.3-1.dsc baed6dfc87bed705c1955cc6b932d7f6 442744 libs optional libass_0.17.3.orig.tar.xz 11c348df3684666e124547faa0d2a318 858 libs optional libass_0.17.3.orig.tar.xz.asc c1819988a31511df1ea89b1f2f5dceaa 16772 libs optional libass_0.17.3-1.debian.tar.xz ba12f28f0e33ee88b713a9fb0b74ab08 8519 libs optional libass_0.17.3-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZobjCgAKCRAhk2s2YA/N iX1FAP0ef7MmLIJkjSBzcWTU+jNLAlxyIGyBYoV+6S71OdsRiQD+L3OBW5+SjnAy aH7uZCzL9biM8SP83jNQBIrbAuf+8gU= =RKeq -END PGP SIGNATURE- pgpFxAIilsoZ8.pgp
Processed: (No Subject)
Processing commands for cont...@bugs.debian.org: > tag 1021438 moreinfo Bug #1021438 [libsndfile1] libsndfile1: undefined symbol: vorbis_version_string Added tag(s) moreinfo. > End of message, stopping processing here. Please contact me if you need assistance. -- 1021438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: (No Subject)
Processing commands for cont...@bugs.debian.org: > forwarded 761240 https://github.com/libsndfile/libsndfile/issues/277 Bug #761240 [libsndfile1] libsndfile1-dev: fails with multipart Ogg/Vorbis files Set Bug forwarded-to-address to 'https://github.com/libsndfile/libsndfile/issues/277'. > End of message, stopping processing here. Please contact me if you need assistance. -- 761240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761240 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1073303: marked as done (kodi-pvr-stalker: FTBFS: xmltv.c:51:13: error: implicit declaration of function ‘malloc’ [-Werror=implicit-function-declaration])
Your message dated Wed, 03 Jul 2024 04:33:54 + with message-id and subject line Bug#1073303: fixed in kodi-pvr-stalker 20.3.1+ds1-2 has caused the Debian Bug report #1073303, regarding kodi-pvr-stalker: FTBFS: xmltv.c:51:13: error: implicit declaration of function ‘malloc’ [-Werror=implicit-function-declaration] 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 ow...@bugs.debian.org immediately.) -- 1073303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kodi-pvr-stalker Version: 20.3.1+ds1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/obj-x86_64-linux-gnu/lib/libstalkerclient && /usr/bin/cc > -DBUILD_KODI_ADDON -I/<>/lib -I/usr/include/libxml2 > -I/usr/include/jsoncpp -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DTARGET_POSIX -DTARGET_LINUX > -D_GNU_SOURCE -DHAVE_LINUX_UDMABUF=1 -DHAVE_LINUX_DMA_HEAP=1 > -DHAVE_LINUX_DMA_BUF=1 -DHAVE_MKOSTEMP=1 -DHAVE_LINUX_MEMFD=1 -DHAVE_STATX=1 > -DHAVE_SSE=1 -DHAVE_SSE2=1 -DHAVE_SSE3=1 -DHAVE_SSSE3=1 -DHAVE_SSE4_1=1 -MD > -MT lib/libstalkerclient/CMakeFiles/stalkerclient.dir/xmltv.c.o -MF > CMakeFiles/stalkerclient.dir/xmltv.c.o.d -o > CMakeFiles/stalkerclient.dir/xmltv.c.o -c > /<>/lib/libstalkerclient/xmltv.c > /<>/lib/libstalkerclient/xmltv.c: In function ‘sc_xmltv_create’: > /<>/lib/libstalkerclient/xmltv.c:51:13: error: implicit > declaration of function ‘malloc’ [-Werror=implicit-function-declaration] >51 | strct = malloc(size); > | ^~ > /<>/lib/libstalkerclient/xmltv.c:31:1: note: include > ‘’ or provide a declaration of ‘malloc’ >30 | #include > +++ |+#include >31 | > /<>/lib/libstalkerclient/xmltv.c:51:13: warning: incompatible > implicit declaration of built-in function ‘malloc’ > [-Wbuiltin-declaration-mismatch] >51 | strct = malloc(size); > | ^~ > /<>/lib/libstalkerclient/xmltv.c:51:13: note: include > ‘’ or provide a declaration of ‘malloc’ > /<>/lib/libstalkerclient/xmltv.c: In function > ‘sc_xmltv_list_free’: > /<>/lib/libstalkerclient/xmltv.c:90:5: error: implicit > declaration of function ‘free’ [-Werror=implicit-function-declaration] >90 | free(*list); > | ^~~~ > /<>/lib/libstalkerclient/xmltv.c:90:5: note: include > ‘’ or provide a declaration of ‘free’ > /<>/lib/libstalkerclient/xmltv.c:90:5: warning: incompatible > implicit declaration of built-in function ‘free’ > [-Wbuiltin-declaration-mismatch] > /<>/lib/libstalkerclient/xmltv.c:90:5: note: include > ‘’ or provide a declaration of ‘free’ > /<>/lib/libstalkerclient/xmltv.c: In function ‘sc_xmltv_free’: > /<>/lib/libstalkerclient/xmltv.c:101:25: warning: incompatible > implicit declaration of built-in function ‘free’ > [-Wbuiltin-declaration-mismatch] > 101 | if (c->id_) free(c->id_); > | ^~~~ > /<>/lib/libstalkerclient/xmltv.c:101:25: note: include > ‘’ or provide a declaration of ‘free’ > /<>/lib/libstalkerclient/xmltv.c:114:29: warning: incompatible > implicit declaration of built-in function ‘free’ > [-Wbuiltin-declaration-mismatch] > 114 | if (p->channel) free(p->channel); > | ^~~~ > /<>/lib/libstalkerclient/xmltv.c:114:29: note: include > ‘’ or provide a declaration of ‘free’ > /<>/lib/libstalkerclient/xmltv.c:116:27: warning: incompatible > implicit declaration of built-in function ‘free’ > [-Wbuiltin-declaration-mismatch] > 116 | if (p->title) free(p->title); > | ^~~~ > /<>/lib/libstalkerclient/xmltv.c:116:27: note: include > ‘’ or provide a declaration of ‘free’ > /<>/lib/libstalkerclient/xmltv.c:118:31: warning: incompatible > implicit declaration of built-in function ‘free’ > [-Wbuiltin-declaration-mismatch] > 118 | if (p->sub_ti
Bug#1069299: marked as done (kodi-visualization-waveform FTBFS on arm*: does not agree on gl vs gles)
Your message dated Wed, 03 Jul 2024 04:18:57 + with message-id and subject line Bug#1069299: fixed in kodi-visualization-shadertoy 20.3.0+ds1-2 has caused the Debian Bug report #1069299, regarding kodi-visualization-waveform FTBFS on arm*: does not agree on gl vs gles 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 ow...@bugs.debian.org immediately.) -- 1069299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kodi-visualization-waveform Version: 20.2.1+ds1-1 Severity: serious Tags: ftbfs kodi-visualization-waveform fails to build from source on arm architectures. A build fails like this: | CMake Error at /usr/share/cmake-3.28/Modules/FindPackageHandleStandardArgs.cmake:230 (message): | Could NOT find OpenGLES (missing: OPENGLES_gl_LIBRARY OPENGLES_INCLUDE_DIR) | Call Stack (most recent call first): | /usr/share/cmake-3.28/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE) | FindOpenGLES.cmake:37 (find_package_handle_standard_args) | CMakeLists.txt:41 (find_package) Looking into CMakeLists.txt, one can see that it takes the APP_RENDER_SYSTEM=gles path. I guess this is rooted in kodi recently having changed this for all arm architectures via #1056563. Now kodi-visualization-waveform does not have any dependency on gles libraries but happens to pull gl libraries transitively. As a result the build now fails. I'm not sure whether this is to be fixed in kodi-visualization-waveform or kodi. The end result is that this very package FTBFS. Hence filing here initially, but reassigning may still make sense. Helmut --- End Message --- --- Begin Message --- Source: kodi-visualization-shadertoy Source-Version: 20.3.0+ds1-2 Done: Vasyl Gello We believe that the bug you reported is fixed in the latest version of kodi-visualization-shadertoy, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vasyl Gello (supplier of updated kodi-visualization-shadertoy 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 03 Jul 2024 03:59:31 + Source: kodi-visualization-shadertoy Architecture: source Version: 20.3.0+ds1-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Vasyl Gello Closes: 1069299 Changes: kodi-visualization-shadertoy (20.3.0+ds1-2) unstable; urgency=medium . * Bmp copyright years * d/watch: Fix repack suffix * d/gbp.conf: Fix debian and upstream branches * debian: Pull GLES build-deps on arm* (Closes: #1069299) Checksums-Sha1: a8321a2b254c3046a8944beaee7ddd8faa8e8dc8 2488 kodi-visualization-shadertoy_20.3.0+ds1-2.dsc d7308d1a1ae8065ae998f4622e906b71c8821b97 4600 kodi-visualization-shadertoy_20.3.0+ds1-2.debian.tar.xz 304758f0749ce6730adb4bcd36e5fb21b06bd18e 5888 kodi-visualization-shadertoy_20.3.0+ds1-2_source.buildinfo Checksums-Sha256: 72a32ae84ad84ed7ff480f15d79950e983724ef1d40ce4802862b6da9cdd6580 2488 kodi-visualization-shadertoy_20.3.0+ds1-2.dsc ce0d1b2002ead314de04f05a158c8e85701b0bd69599da74576fa05984b67700 4600 kodi-visualization-shadertoy_20.3.0+ds1-2.debian.tar.xz 525a3fa90f40ddc6e4d57603e87176657e6a681e01a8a22b649b636b564186f0 5888 kodi-visualization-shadertoy_20.3.0+ds1-2_source.buildinfo Files: d0d52bfd453408c7f14396a8b9b868e6 2488 libs optional kodi-visualization-shadertoy_20.3.0+ds1-2.dsc 368cf2562893ac82e2b3ba4c06792962 4600 libs optional kodi-visualization-shadertoy_20.3.0+ds1-2.debian.tar.xz d58d5bff6a630af961884afa3ac76285 5888 libs optional kodi-visualization-shadertoy_20.3.0+ds1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEKG46uNMbcWWMwf6pRcPahUxsbF4FAmaEzZEACgkQRcPahUxs bF6zdBAAyf2jj9Dbbo2eTqn7djPx7R9OhywED47QgY4wZGKJ03OiNXVotAAM+DMF pZWIkwCIyV4xGVGaGKLdBe1JLuh3LmBFKK4VR4T/kGPdcICQiRnzzmbaBNJqQVGR OuM2/RR3SfXdnkf1PBI8RH4/u6vlEPz6tj5C+3uzB92GQZiyn2RTIr4Vu/nUABQn 29DmaHGoXMHjV6MLnPfRPuVmoXYSLk055OYjPwu7JRBckxnvLR00a+b2FuhFNea6 6vQVVTOkd6EtFO39seshYbPxkorhPWFUBjfj+FDma5uKNDtCLD0o82uvOMnbResn 5FNzRvlMlQxpM8prH5stcrdNLt/kdUHIlBV8UgnV0p+hmgNxSyjouHl+E2VPPKa
Processed: bug 1074440 is forwarded to https://github.com/xbmc/xbmc/issues/24069
Processing commands for cont...@bugs.debian.org:
> forwarded 1074440 https://github.com/xbmc/xbmc/issues/24069
Bug #1074440 {Done: Vasyl Gello } [kodi] kodi dies with
"PyImport_AppendInittab() may not be called after Py_Initialize()"
Set Bug forwarded-to-address to 'https://github.com/xbmc/xbmc/issues/24069'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1074440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1074440: marked as done (kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()")
Your message dated Wed, 03 Jul 2024 04:04:39 +
with message-id
and subject line Bug#1074440: fixed in kodi 2:20.5+dfsg-3
has caused the Debian Bug report #1074440,
regarding kodi dies with "PyImport_AppendInittab() may not be called after
Py_Initialize()"
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 ow...@bugs.debian.org
immediately.)
--
1074440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kodi
Version: 2:20.5+dfsg-2+b2
kodi dies immediately with
{harri@cecil:~ (master) 1032} kodi
/usr/bin/kodi: 1: ulimit: error setting limit (Operation not permitted)
kodi: ulimit is unsupported by this shell
libva info: VA-API version 1.21.0
libva error: vaGetDriverNames() failed with unknown libva error
Fatal Python error: PyImport_AppendInittab: PyImport_AppendInittab() may not be
called after Py_Initialize()
Python runtime state: core initialized
Thread 0x7fa184c006c0 (most recent call first):
File "", line 1648 in _fill_cache
File "", line 1605 in find_spec
File "", line 1502 in _get_spec
File "", line 1528 in find_spec
File "", line 1262 in _find_spec
File "", line 1322 in _find_and_load_unlocked
File "", line 1360 in _find_and_load
Aborted
According to
https://www.reddit.com/r/kodi/comments/1coowz1/crash_in_pyimport_appendinittab_pyimport/?rdt=36220
this is a regression with python 3.12. If I move back to 3.11 the problem
disappears.
According to the reddit link the problem has been fixed with kodi 21. Looking
at the code in git this could be commit
1bfa3ef9e3b6d25d581bb1f48f6a740fca1c06cf.
Regards
Harri
--- End Message ---
--- Begin Message ---
Source: kodi
Source-Version: 2:20.5+dfsg-3
Done: Vasyl Gello
We believe that the bug you reported is fixed in the latest version of
kodi, 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 1074...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Vasyl Gello (supplier of updated kodi 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 ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 03 Jul 2024 03:26:36 +
Source: kodi
Architecture: source
Version: 2:20.5+dfsg-3
Distribution: unstable
Urgency: high
Maintainer: Debian Multimedia Maintainers
Changed-By: Vasyl Gello
Closes: 1074440
Changes:
kodi (2:20.5+dfsg-3) unstable; urgency=high
.
* Add Python3.12 workaround (Closes: #1074440)
* Add pcre2 Use-After-Free fixup
Checksums-Sha1:
55d0d379721cb740329d1390d3ad32a8519b391e 5872 kodi_20.5+dfsg-3.dsc
3d234e03b3d5bed1ed580793c894dc5eb0bd6904 2588108 kodi_20.5+dfsg-3.debian.tar.xz
c6c502bf62ec84c838082571d73b4fc61b2025bd 7002 kodi_20.5+dfsg-3_source.buildinfo
Checksums-Sha256:
eeab1f47ad613f0827b6070d948aeaeebd5024f0cfc4ac89e0a5e78c8465ed39 5872
kodi_20.5+dfsg-3.dsc
4725745ea03a8b7ceaae59196d85dbb32c41147c65790f721c02f315504ba6ab 2588108
kodi_20.5+dfsg-3.debian.tar.xz
e3512a731436d0c07abc946ed17872a3c687a13a84d01c273e853c7a959e795c 7002
kodi_20.5+dfsg-3_source.buildinfo
Files:
eeecb28f15111c1b49c814ea91d2de56 5872 video optional kodi_20.5+dfsg-3.dsc
f428638a0d9f903afe1d18268c400cb4 2588108 video optional
kodi_20.5+dfsg-3.debian.tar.xz
ca02c10ba6ee821deccab901fcdb4100 7002 video optional
kodi_20.5+dfsg-3_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEKG46uNMbcWWMwf6pRcPahUxsbF4FAmaEydEACgkQRcPahUxs
bF6B/w/+IghTXt0iHVWgnhMpAjeTEsflOFTpgBpMXC3yH8xhe8DNUg3Ny3tBzluo
lf5s5fNEpXLQXYdZZNmYw0XXihkxSKM4eFN8frSkJjz/GjUuKJjFedA/BrVP265D
Ot2OACZWp1/gLFEwEtdT5NNx/eQ4fbBsw2YEA9CdFSkf64UoWcQcc/RsVaCk/JDz
ERSCxATnSMWVG5GKiw7l5GtLWVJSjCr5bwPKEG0UU48HQTJFt9zCLdQr76Utd9Md
sT9GL2uMCQaFNjWzi8xzLgdVokblgJeCYVeT83Z4kn1m9fIBoy9v1m7fn+3UVHiQ
9aAY+/x2WGvUJ1BlT/UNi/JkhsPTnYI/4a8gmjL/NofkdsxM8UeelgwcoLoQ+Y6H
kjsm/sApr4kK7Sjb1ZG88y2R8yLBzDRaPc5msCprQsAD89ak36Ui/N1a+J7WTmMb
jjuvcxlpqZiAsf85Z4gMDN0L+vXWi8VKG5DbHlu4SUY19TbG/CFM/nFAQNdHqHX+
+anXUw7Xbx12TI4bS6x6Bnstc/iA4RRAPqtQOh4LgDOI/CWOeDTqjoTyHOXPP5SI
cVI/mt9scXm87ADw3gxJsRmWFfTW+U01crG/VPziiw7tYVtw/0aa/P2MlNa0DyCM
mjhwXumF1VDHJl+gFdN82/QiycZuXPWcEL1lb6GJynnhVKGFOQ0=
=oUag
-END PGP SIGNATURE-
pgphjR3c_vutk.pgp
Description: PGP signature
--- End Message ---
Processed: Bug#1074440 marked as pending in kodi
Processing control commands:
> tag -1 pending
Bug #1074440 {Done: Vasyl Gello } [kodi] kodi dies with
"PyImport_AppendInittab() may not be called after Py_Initialize()"
Added tag(s) pending.
--
1074440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1069130, tagging 1074739, tagging 1074733, tagging 1074680, tagging 1074621, tagging 1074729 ...
Processing commands for cont...@bugs.debian.org: > tags 1069130 - sid trixie Bug #1069130 [src:python-mapnik] python-mapnik: FTBFS with Mapnik 4.0.0 Bug #1074660 [src:python-mapnik] python-mapnik: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: 'mapnik-config' Removed tag(s) trixie and sid. Removed tag(s) trixie and sid. > tags 1074739 + experimental Bug #1074739 [src:hisat2] hisat2: FTBFS: make[1]: *** [debian/rules:39: override_dh_auto_build] Error 1 Added tag(s) experimental. > tags 1074733 - sid trixie Bug #1074733 [src:rust-async-std] rust-async-std: FTBFS: dh_auto_test: error: env DEB_BUILDDIR= /<>/debian/dh-cargo/bin/cargo test --no-fail-fast -- --skip io_timeout returned exit code 101 Removed tag(s) sid and trixie. > tags 1074680 - sid trixie Bug #1074680 [src:osc] osc: FTBFS: ModuleNotFoundError: No module named 'imp' Removed tag(s) trixie and sid. > tags 1074621 + experimental Bug #1074621 [src:unicap] unicap: FTBFS: /usr/bin/msgfmt: present charset "" is not a portable encoding name Added tag(s) experimental. > tags 1074729 - sid trixie Bug #1074729 [src:golang-github-safchain-ethtool] golang-github-safchain-ethtool: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/safchain/ethtool github.com/safchain/ethtool/example returned exit code 1 Removed tag(s) trixie and sid. > tags 1069495 - sid trixie Bug #1069495 [src:wacomtablet] wacomtablet: FTBFS: failing tests Removed tag(s) sid and trixie. > tags 1073508 + sid trixie Bug #1073508 [libxml2] libxml2: just another API+ABI break; please bump soname Ignoring request to alter tags of bug #1073508 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1069130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069130 1069495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069495 1073508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073508 1074621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074621 1074660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074660 1074680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074680 1074729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074729 1074733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074733 1074739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061795: marked as done (csound fails its autopkg tests with Python 3.12)
Your message dated Tue, 02 Jul 2024 07:04:28 + with message-id and subject line Bug#1061795: fixed in csound 1:6.18.1+dfsg-2 has caused the Debian Bug report #1061795, regarding csound fails its autopkg tests with Python 3.12 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 ow...@bugs.debian.org immediately.) -- 1061795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061795 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:csound Version: 1:6.18.1+dfsg-1 Severity: important Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 With python3-defaults from experimental, the package fails its autopkg tests: [...] 3648s autopkgtest [14:30:36]: test command5: - - - - - - - - - - results - - - - - - - - - - 3648s autopkgtest [14:30:36]: summary 3648s python3-csound PASS (superficial) 3648s upstream-testsuite FAIL stderr: /tmp/autopkgtest.TOrCP4/build.Mx9/src/tests/commandline/test.py:196: SyntaxWarning: invalid escape sequence '\c' 3648s command1 PASS --- End Message --- --- Begin Message --- Source: csound Source-Version: 1:6.18.1+dfsg-2 Done: IOhannes m zmölnig (Debian/GNU) We believe that the bug you reported is fixed in the latest version of csound, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated csound 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 01 Jul 2024 15:20:47 +0200 Source: csound Architecture: source Version: 1:6.18.1+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 1061795 Changes: csound (1:6.18.1+dfsg-2) unstable; urgency=medium . * Add patch to fix autopkgtest with Python3.12 (Closes: #1061795) * Allow stderr for autopkgtests * Bump standards version to 4.7.0 Checksums-Sha1: a22950dc7c90490e66278de9430431c71561e6df 3384 csound_6.18.1+dfsg-2.dsc 3cdde665daf39edaecb650a3b50fcbe90e3030bd 52972 csound_6.18.1+dfsg-2.debian.tar.xz Checksums-Sha256: b6dd707ccdc94107928847fcb64c55c074caac3e2b5434f0bd0643bdabf274c1 3384 csound_6.18.1+dfsg-2.dsc 9c2f0a816439d633a0626cce49a44dd770dcef7e6ee8dccb295876188077dbbc 52972 csound_6.18.1+dfsg-2.debian.tar.xz Files: 29f0edf1418d743f8af70d140b8ac81f 3384 sound optional csound_6.18.1+dfsg-2.dsc 1c965874a0874644ef10004bc1546a04 52972 sound optional csound_6.18.1+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAmaDoW8ACgkQtlAZxH96 Nvh51A/5AbnHHkfr3b/FQVYc474oRsdZfbJIeSDC01zkSEA71Ane7u3nqtFx8aYw I3PtC73uxclMnkOsDqDoTdYW10WiF+RYjLLvR2xZwrgDaVQe+vLSwHboF4rjJDoG mxKMTljjifzj7n0TlvJqdR/3EsIA6k9Hn+D1QR55plddAfthksh4mJOY55g9iZPw MbB/cwNrKfssOsZpmtzhOUjqa2bQyCmzNgl/zlHPuZaqzAz5tEWJtAUtyADijxWI wvDFrn3z5TEhLeh5H1bV4IZ5H4NOB8xvVlE+Oe0XC5dLtrhWqbwEgI5fed55mCYX CXVP2i94Wsu88YyQoyVAhPzTAgVWzSeCPBoDTfeTJO/XvGsv1FieM2z0rHwrEI2X HXb9iFBP7QWur5VkmzXQRMlWB1RQj4HF1Ul3zy3O/y9b7ZzGB9S7CtU/fq60Ibgh azYan1MHKcEw58m/fEHePRyuVDlA4yD2ayGpTFT2oiaNiHEOpdGXCchvflClFajH KfSJpNde34YBeHWgVAZPxwl4lKWpQTn7UJdVTWaYtkHNvGnn6W68sMx2Mht0qc8q noIICLsVALC0VeDHb+4eattTpdLY2D7fXB9B9R4iLClIQttOVZOEpWIyWijRd20y CFwRYKRpPrDnUHPTATokpyMdcVMd1iNLfD6Gkgtzys9BYCfC9ZY= =TtUQ -END PGP SIGNATURE- pgp49Rvi3dq6Z.pgp Description: PGP signature --- End Message ---
Processed: Re: inkscape: Fails to build with poppler 24.06
Processing control commands: > tags -1 +patch Bug #1074460 [src:inkscape] inkscape: Fails to build with poppler 24.06 Added tag(s) patch. -- 1074460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: inkscape: FTBFS: uri.cpp:86:9: error: ‘xmlFree’ was not declared in this scope; did you mean ‘xmlFreeURI’?
Processing control commands: > tags -1 patch Bug #1073348 [src:inkscape] inkscape: FTBFS: uri.cpp:86:9: error: ‘xmlFree’ was not declared in this scope; did you mean ‘xmlFreeURI’? Added tag(s) patch. -- 1073348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1061795 marked as pending in csound
Processing control commands: > tag -1 pending Bug #1061795 [src:csound] csound fails its autopkg tests with Python 3.12 Added tag(s) pending. -- 1061795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061795 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bump severity of python 3.12 autopkgtest bugs
Processing commands for cont...@bugs.debian.org: > severity 1061795 serious Bug #1061795 [src:csound] csound fails its autopkg tests with Python 3.12 Severity set to 'serious' from 'important' > severity 1061824 serious Bug #1061824 [src:python-cloudflare] python-cloudflare fails its autopkg tests with Python 3.12 Severity set to 'serious' from 'important' > severity 1061833 serious Bug #1061833 [src:pywebdav] pywebdav autopkg fails its autopkg tests with Python 3.12 Severity set to 'serious' from 'important' > severity 1061836 serious Bug #1061836 [src:recon-ng] recon-ng fails its autopkg tests with Python 3.12 Severity set to 'serious' from 'important' > severity 1061841 serious Bug #1061841 [src:rstcheck] rstcheck fails its autopkg tests with Python 3.12 Severity set to 'serious' from 'important' > severity 1061842 serious Bug #1061842 [src:sdkmanager] sdkmanager fails its autopkg tests with Python 3.12 Severity set to 'serious' from 'important' > severity 1069219 serious Bug #1069219 [src:pymatgen] pymatgen ftbfs with Python 3.12 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1061795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061795 1061824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061824 1061833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061833 1061836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061836 1061841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061841 1061842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061842 1069219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072459: marked as done (wxsvg: FTBFS with ffmpeg 7.0: mediadec_ffmpeg.cpp:168:75: error: ‘AVCodecParameters’ {aka ‘struct AVCodecParameters’} has no member named ‘channels’)
Your message dated Sat, 29 Jun 2024 12:22:22 +
with message-id
and subject line Bug#1072459: fixed in wxsvg 2:1.5.25+dfsg-1
has caused the Debian Bug report #1072459,
regarding wxsvg: FTBFS with ffmpeg 7.0: mediadec_ffmpeg.cpp:168:75: error:
‘AVCodecParameters’ {aka ‘struct AVCodecParameters’} has no member named
‘channels’
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 ow...@bugs.debian.org
immediately.)
--
1072459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wxsvg
Version: 2:1.5.24+dfsg-2.1
Severity: important
Tags: trixie sid ftbfs
Usertags: ffmpeg-7.0
Hi,
during a rebuild of the reverse dependencies for the transition to
ffmpeg 7.0, your package failed to build
Relevant part (hopefully):
> /bin/bash ../libtool --tag=CXX --mode=compile g++ -DPACKAGE_NAME=\"wxsvg\"
> -DPACKAGE_TARNAME=\"wxsvg\" -DPACKAGE_VERSION=\"1.5.24\"
> -DPACKAGE_STRING=\"wxsvg\ 1.5.24\"
> -DPACKAGE_BUGREPORT=\"http://wxsvg.sourceforge.net/\; -DPACKAGE_URL=\"\"
> -DPACKAGE=\"wxsvg\" -DVERSION=\"1.5.24\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1
> -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1
> -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1
> -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -I. -I../include -I../include/wxSVG
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -mbranch-protection=standard -I/usr/include/cairo
> -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/pixman-1
> -DUSE_RENDER_CAIRO -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
> -I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6
> -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16
> -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi
> -I/usr/include/cairo -I/usr/include/pixman-1 -pthread
> -I/usr/lib/aarch64-linux-gnu/wx/include/gtk3-unicode-3.2
> -I/usr/include/wx-3.2 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__
> -pthread -DUSE_LIBAV -I/usr/include/aarch64-linux-gnu -c -o
> mediadec_ffmpeg.lo mediadec_ffmpeg.cpp
> libtool: compile: g++ -DPACKAGE_NAME=\"wxsvg\" -DPACKAGE_TARNAME=\"wxsvg\"
> -DPACKAGE_VERSION=\"1.5.24\" "-DPACKAGE_STRING=\"wxsvg 1.5.24\""
> -DPACKAGE_BUGREPORT=\"http://wxsvg.sourceforge.net/\; -DPACKAGE_URL=\"\"
> -DPACKAGE=\"wxsvg\" -DVERSION=\"1.5.24\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1
> -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1
> -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1
> -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -I. -I../include -I../include/wxSVG
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -mbranch-protection=standard -I/usr/include/cairo
> -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/pixman-1
> -DUSE_RENDER_CAIRO -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
> -I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6
> -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16
> -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi
> -I/usr/include/cairo -I/usr/include/pixman-1 -pthread
> -I/usr/lib/aarch64-linux-gnu/wx/include/gtk3-unicode-3.2
> -I/usr/include/wx-3.2 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__
> -pthread -DUSE_LIBAV -I/usr/include/aarch64-linux-gnu -c mediadec_ffmpeg.cpp
> -fPIC -DPIC -o .libs/mediadec_ffmpeg.o
> mediadec_ffmpeg.cpp: In member function ‘int
> wxFfmpegMediaDecoder::GetChannelNumber(unsigned int)’:
> mediadec_ffmpeg.cpp:168:75: error: ‘AVCodecParameters’ {aka ‘struct
> AVCodecParameters’} has no member named ‘channels’
> 168 | return m_formatCtx ?
> m_formatCtx->streams[streamIndex]->codecpar->channels : -1;
> |
> ^~~~
> mediadec_ffmpeg.cpp: In member function ‘void
> wxFfmpegMediaDecoder::CloseVideoDecoder()’:
> mediadec_ffmpeg.cpp:217:22: warning: ‘int avcodec_cl
Bug#1071931: marked as done (libaacs: FTBFS against libgcrypt 1.11)
Your message dated Sat, 29 Jun 2024 10:56:02 + with message-id and subject line Bug#1071931: fixed in libaacs 0.11.1-4 has caused the Debian Bug report #1071931, regarding libaacs: FTBFS against libgcrypt 1.11 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 ow...@bugs.debian.org immediately.) -- 1071931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libaacs Version: 0.5.0-2 Severity: important Tags: ftbfs patch User: ametz...@debian.org Usertags: libgcrypt-config-removal Control: block 714589 by -1 Hello, libaacs FTBFS against libgcrypt 1.11 which drops libgcrypt-config. Since it ships an outdated version of AM_PATH_LIBGCRYPT() in m4/libgcrypt.m4 that cannot handle this autoreconf does not help. Simply removing this copy (m4/libgcrypt.m4) lets the build succeed. A development snapshot of the yet-unreleased libgcrypt 1.11 is available in experimental. cu Andreas --- End Message --- --- Begin Message --- Source: libaacs Source-Version: 0.11.1-4 Done: Dylan Aïssi 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dylan Aïssi (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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 29 Jun 2024 08:49:50 +0200 Source: libaacs Architecture: source Version: 0.11.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Dylan Aïssi Closes: 1071931 Changes: libaacs (0.11.1-4) unstable; urgency=medium . * Team upload. . [ Christoph Anton Mitterer ] * Update debian/copyright . [ Dylan Aïssi ] * Remove m4/libgcrypt.m4 which ships an outdated version of AM_PATH_LIBGCRYPT() (Closes: #1071931) * Remove unneeded debian/salsa-ci.yml * Standards-Version: 4.7.0 (no changes required) Checksums-Sha1: 1c2cff3f0a57491920133957cba36b7ec8f607e8 2105 libaacs_0.11.1-4.dsc 4e0cbb2beba96d425df9264b265904219c97731f 4872 libaacs_0.11.1-4.debian.tar.xz bf972906a54506505b5d7b5c9323f4472fc4f02f 6910 libaacs_0.11.1-4_amd64.buildinfo Checksums-Sha256: 1a7ac1341d0bbcf1395351fdd591fc9241e709dd7dee23cad8a21f08e6075b6d 2105 libaacs_0.11.1-4.dsc 21bf79323d31af8adf2dbb4aeffad8ae7dd8a4a88af374c256a498df885f2715 4872 libaacs_0.11.1-4.debian.tar.xz 3846780c934118b7f237154e5a0f1b44ebee865fcef6ed3ddf9e30ea85d1a3b7 6910 libaacs_0.11.1-4_amd64.buildinfo Files: fde8fff2ccc2c33d004458f87444f54a 2105 video optional libaacs_0.11.1-4.dsc bd3832657a43a5098b80f1a205f7373f 4872 video optional libaacs_0.11.1-4.debian.tar.xz 944f716cf80ef0cbe8c4199d2907a7f5 6910 video optional libaacs_0.11.1-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAmZ/s8YACgkQYS7xYT4F D1S20BAAiR2hVT/zq+08SPiFX153UZSC2Gk/pZ5s2e8EwdcMeV+QzGDJCN8go20E Di7+//0WnEQ0jCwH1vqF87bW7NTsJQx/LaYsold3ipuolHbEd9igqYae8+sWnMEl QzxZGCBvY508y51yp4VAXk1Q3dMgICHeu4yWuiFei1um8/5+Qfg+ECcrQfJ3hT9I jNzNM+NwCMgEg3QCimZfq8QTBY5kNhDZCjEdZgIkqKPnjUjeVs6lju6ECQlOD19O hpP/RjBcfk8tF6G3BL1jv/jCyctWuieXyeghghxS3B8fUyzTSfwihznBtXnQHOEj 8jE1naNkZLoQr2i+pAdXWD/sotUvqcLI7yiojKAgqwaJLO5F2Tdythb4KSH4WFng dP2ziLACzTQqAuRBclEe/iwkqPuKntzxWVsJUpuO/pkO71CiWxscCjjT8aplkqoA w8fjA3uEWrggsqqoyyrlJZ00GvOUtoLqDqHm5Q1/mnAWIW/6sPIAqGdT9xygYO61 5dHOGmRvsmznElQXR2VRN9cz/cB7JSKBK2toR7bIhrMlJd0FuAYnNW95RU5QzWVo 6QV2MmJDyCtp7/SbsrjLemr3y6+KfCXp4g0/dgs9ApVFHsJNeglLwHtpWEUqxnqU JGP+o9UaGIb6wFM0zSP3N5B31Gm1TdBgAlwEYKQ6GjaaHk22e/4= =W3tI -END PGP SIGNATURE- pgpvNODcpTZ0_.pgp Description: PGP signature --- End Message ---
Bug#1071932: marked as done (libbdplus: FTBFS against libgcrypt 1.11)
Your message dated Sat, 29 Jun 2024 10:56:10 + with message-id and subject line Bug#1071932: fixed in libbdplus 0.2.0-4 has caused the Debian Bug report #1071932, regarding libbdplus: FTBFS against libgcrypt 1.11 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 ow...@bugs.debian.org immediately.) -- 1071932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbdplus Version: 0.2.0-3 Severity: important Tags: ftbfs User: ametz...@debian.org Usertags: libgcrypt-config-removal Control: block 714589 by -1 Hello, libbdplus uses libgcrypt-config to locate libgcrypt. This breaks against libgcrypt 1.11 which does not ship libgcrypt-config anymore. Please use pkg-config/pkgconf instead. A development snapshot of the yet-unreleased libgcrypt 1.11 is available in experimental. cu Andreas --- End Message --- --- Begin Message --- Source: libbdplus Source-Version: 0.2.0-4 Done: Dylan Aïssi We believe that the bug you reported is fixed in the latest version of libbdplus, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dylan Aïssi (supplier of updated libbdplus 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 29 Jun 2024 10:13:06 +0200 Source: libbdplus Architecture: source Version: 0.2.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Dylan Aïssi Closes: 1071932 Changes: libbdplus (0.2.0-4) unstable; urgency=medium . * Team upload. * Rely on pkgconf to detect libgcrypt instead of libgcrypt-config (Closes: #1071932) * Switch to pkgconf in Build-Deps * Standards-Version: 4.7.0 (no changes required) Checksums-Sha1: 92e2b4fdb318501a2217e4cfe594063eb62ad8ee 2076 libbdplus_0.2.0-4.dsc c29f65d764c50098e52857acafb019eb9ec5d392 3916 libbdplus_0.2.0-4.debian.tar.xz 3103d907bb4c82553ea7bc52c1666c62ac6d7dcc 6458 libbdplus_0.2.0-4_amd64.buildinfo Checksums-Sha256: 1640d16319d2e271c748663d1352e8e6421f4e25dab8be6bb468ea634c88e209 2076 libbdplus_0.2.0-4.dsc 23ee4ebdaeb6a4992b8a48d75cc6aea81317e7615eeead2d38ad3c4736ca2134 3916 libbdplus_0.2.0-4.debian.tar.xz 2c51277923f712d16f0a26d60f9a357463acecdc26cd3105fc29008a9a2d049a 6458 libbdplus_0.2.0-4_amd64.buildinfo Files: 4cd7aac26898c933e66ffd4f916c3de9 2076 libs optional libbdplus_0.2.0-4.dsc 9a83b07f9abb2976efc7e9d23d381223 3916 libs optional libbdplus_0.2.0-4.debian.tar.xz 712e96c1becd34c84526e2f6da889076 6458 libs optional libbdplus_0.2.0-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAmZ/wz4ACgkQYS7xYT4F D1TYfQ//QNddJXNLjPysUiu9PC/H/lYUYy7kz+IVz46wPTKPd18lFYJ0df+YEunE WJBDgIxWkxWLZocqldEVCXDIGU6cCAInjoZbNDwzKWRTkfjmQIMAtF2E8shXfEGz Y+6/msoCnYnq6bXIvTOlyrwnGWlirU+/e82SOgIHL97rPE5sJR3E34ZxVOKw5RLi eKLJ1Pxocbqx65agpbRZKgfPmBwlZ760GGz1cQp815xYPkpo2Cy+glZO0Et6eCKt DBHZ/+26iAENrBLOhN6kHk1OoQkbdR4q2WL7yVlL7FVSLegzUUMxLTmQUIy1XJdv BKmeatVGLccaeCjcyt7YXTTVLDSyH/HhQt4n8qB655moJX0FnhICgXZB95pbtkxq 9HeaW33ZjTJdzZ/CnAQb6vrlOatHYxZNFJcI9SVkomsFphUPSMJaUgyplPq8EMop c9Me50HJvT4sJWf9yubhXyAKtJ/9UBbjsbH9Hmp/ci8sBhboL0crAkM/EvrfnbBe R/jSDnM/3sQrwZ3TUQHoklTM3zJkh/z+WSTfaX5MAbrgU4Bd2DvhCwRAC7LIUYiF jRue07w96rwpxUVwxOvWkGm7hopAWBOIpFuW/Al+VRejKBe19rAg7VEJjjNM4Eed QvTZF72t0B3NoSdU22mHALpnKZlMzgVTs4HSNFpZ7Pu9pwj6cEw= =Ifro -END PGP SIGNATURE- pgpcCbKq9Qhzz.pgp Description: PGP signature --- End Message ---
Processed: Bug#1071932 marked as pending in libbdplus
Processing control commands: > tag -1 pending Bug #1071932 [src:libbdplus] libbdplus: FTBFS against libgcrypt 1.11 Added tag(s) pending. -- 1071932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1071931 marked as pending in libaacs
Processing control commands: > tag -1 pending Bug #1071931 [src:libaacs] libaacs: FTBFS against libgcrypt 1.11 Added tag(s) pending. -- 1071931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1074431, tagging 1074430, tagging 1074429, tagging 1074426 ..., tagging 1074425 ...
Processing commands for cont...@bugs.debian.org: > tags 1074431 + upstream Bug #1074431 [src:arm-trusted-firmware] arm-trusted-firmware: CVE-2024-6287 CVE-2024-6285 Added tag(s) upstream. > tags 1074430 + upstream Bug #1074430 [src:adminer] adminer: CVE-2023-45196 CVE-2023-45195 Added tag(s) upstream. > tags 1074429 + upstream Bug #1074429 [src:xml-security-c] xml-security-c: CVE-2024-34580 Added tag(s) upstream. > tags 1074426 + upstream Bug #1074426 [src:golang-golang-x-image] golang-golang-x-image: CVE-2024-24792 Ignoring request to alter tags of bug #1074426 to the same tags previously set > forwarded 1074426 https://github.com/golang/go/issues/67624 Bug #1074426 [src:golang-golang-x-image] golang-golang-x-image: CVE-2024-24792 Ignoring request to change the forwarded-to-address of bug#1074426 to the same value > tags 1074425 + upstream Bug #1074425 [src:openvpn-auth-ldap] openvpn-auth-ldap: CVE-2024-28820 Ignoring request to alter tags of bug #1074425 to the same tags previously set > forwarded 1074425 https://github.com/threerings/openvpn-auth-ldap/pull/92 Bug #1074425 [src:openvpn-auth-ldap] openvpn-auth-ldap: CVE-2024-28820 Ignoring request to change the forwarded-to-address of bug#1074425 to the same value > tags 1074414 + upstream Bug #1074414 [src:gpac] gpac: CVE-2024-6061 CVE-2024-6062 CVE-2024-6063 CVE-2024-6064 Added tag(s) upstream. > tags 1074415 + upstream Bug #1074415 [src:slic3r-prusa] slic3r-prusa: CVE-2020-28594 CVE-2020-28595 CVE-2020-28596 CVE-2020-28598 Added tag(s) upstream. > tags 1074416 + upstream Bug #1074416 [src:libde265] libde265: CVE-2024-38949 CVE-2024-38950 Added tag(s) upstream. > forwarded 1074416 https://github.com/strukturag/libde265/issues/460 Bug #1074416 [src:libde265] libde265: CVE-2024-38949 CVE-2024-38950 Set Bug forwarded-to-address to 'https://github.com/strukturag/libde265/issues/460'. > tags 1074417 + upstream Bug #1074417 [src:zziplib] zziplib: CVE-2024-39133 Ignoring request to alter tags of bug #1074417 to the same tags previously set > forwarded 1074417 https://github.com/gdraheim/zziplib/issues/164 Bug #1074417 [src:zziplib] zziplib: CVE-2024-39133 Ignoring request to change the forwarded-to-address of bug#1074417 to the same value > tags 1074418 + upstream Bug #1074418 [src:libmodbus] libmodbus: CVE-2023-26793 Added tag(s) upstream. > forwarded 1074418 https://github.com/stephane/libmodbus/issues/683 Bug #1074418 [src:libmodbus] libmodbus: CVE-2023-26793 Set Bug forwarded-to-address to 'https://github.com/stephane/libmodbus/issues/683'. > tags 1074419 + upstream Bug #1074419 [src:bluez] bluez: CVE-2023-51596 Added tag(s) upstream. > tags 1074421 + upstream Bug #1074421 [src:grpc] grpc: CVE-2023-44487 Added tag(s) upstream. > tags 1074422 + upstream Bug #1074422 [src:libmodbus] libmodbus: CVE-2024-36843 CVE-2024-36844 CVE-2024-36845 Added tag(s) upstream. > tags 1074423 + upstream Bug #1074423 [src:nltk] nltk: CVE-2024-39705 Ignoring request to alter tags of bug #1074423 to the same tags previously set > tags 1074424 + upstream Bug #1074424 [src:zziplib] zziplib: CVE-2024-39134 Ignoring request to alter tags of bug #1074424 to the same tags previously set > forwarded 1074424 https://github.com/gdraheim/zziplib/issues/165 Bug #1074424 [src:zziplib] zziplib: CVE-2024-39134 Ignoring request to change the forwarded-to-address of bug#1074424 to the same value > thanks Stopping processing here. Please contact me if you need assistance. -- 1074414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074414 1074415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074415 1074416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074416 1074417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074417 1074418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074418 1074419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074419 1074421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074421 1074422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074422 1074423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074423 1074424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074424 1074425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074425 1074426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074426 1074429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074429 1074430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074430 1074431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1074370: ffmpeg: Fails to build on armel & armhf
Processing control commands: > forwarded -1 https://trac.ffmpeg.org/ticket/11074 Bug #1074370 [src:ffmpeg] ffmpeg: Fails to build on armel & armhf Set Bug forwarded-to-address to 'https://trac.ffmpeg.org/ticket/11074'. > tags -1 upstream Bug #1074370 [src:ffmpeg] ffmpeg: Fails to build on armel & armhf Added tag(s) upstream. -- 1074370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1074370 in 7:6.1.1-3
Processing commands for cont...@bugs.debian.org: > found 1074370 7:6.1.1-3 Bug #1074370 [src:ffmpeg] ffmpeg: Fails to build on armel & armhf Marked as found in versions ffmpeg/7:6.1.1-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:inkscape
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:inkscape > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1073953 (http://bugs.debian.org/1073953) > # Bug title: inkscape: Stop using libsoup2.4 > # * https://gitlab.com/inkscape/inbox/-/issues/7873 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1073953 + fixed-upstream Bug #1073953 [src:inkscape] inkscape: Stop using libsoup2.4 Added tag(s) fixed-upstream. > usertags 1073953 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1073953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1061422
Processing commands for cont...@bugs.debian.org: > close 1061422 4.1.1+dfsg-1 Bug #1061422 [src:blender] blender ftbfs with Python 3.12 as the default Marked as fixed in versions blender/4.1.1+dfsg-1. Bug #1061422 [src:blender] blender ftbfs with Python 3.12 as the default Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1061422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1074175, reassign 1069317 to src:vamp-plugin-sdk, fixed 1069317 in 2.10.0-5~exp ...
Processing commands for cont...@bugs.debian.org:
> tags 1074175 + sid trixie
Bug #1074175 [src:netkit-rwho] netkit-rwho: remove for trixie?
Added tag(s) trixie and sid.
> reassign 1069317 src:vamp-plugin-sdk 2.10.0-4
Bug #1069317 {Done: IOhannes m zmölnig (Debian/GNU) }
[libvamp-hostsdk3v5] FTBFS: tests failed
Bug #1074226 {Done: IOhannes m zmölnig (Debian/GNU) }
[libvamp-hostsdk3v5] sonic-visualiser: FTBFS on armel/armhf
Bug reassigned from package 'libvamp-hostsdk3v5' to 'src:vamp-plugin-sdk'.
Bug reassigned from package 'libvamp-hostsdk3v5' to 'src:vamp-plugin-sdk'.
Ignoring request to alter found versions of bug #1069317 to the same values
previously set
Ignoring request to alter found versions of bug #1074226 to the same values
previously set
No longer marked as fixed in versions vamp-plugin-sdk/2.10.0-5~exp and
vamp-plugin-sdk/2.10.0-5.
No longer marked as fixed in versions vamp-plugin-sdk/2.10.0-5 and
vamp-plugin-sdk/2.10.0-5~exp.
Bug #1069317 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:vamp-plugin-sdk] FTBFS: tests failed
Bug #1074226 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:vamp-plugin-sdk] sonic-visualiser: FTBFS on armel/armhf
Marked as found in versions vamp-plugin-sdk/2.10.0-4.
Marked as found in versions vamp-plugin-sdk/2.10.0-4.
> fixed 1069317 2.10.0-5~exp
Bug #1069317 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:vamp-plugin-sdk] FTBFS: tests failed
Bug #1074226 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:vamp-plugin-sdk] sonic-visualiser: FTBFS on armel/armhf
Marked as fixed in versions vamp-plugin-sdk/2.10.0-5~exp.
Marked as fixed in versions vamp-plugin-sdk/2.10.0-5~exp.
> fixed 1069317 2.10.0-5
Bug #1069317 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:vamp-plugin-sdk] FTBFS: tests failed
Bug #1074226 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:vamp-plugin-sdk] sonic-visualiser: FTBFS on armel/armhf
The source 'vamp-plugin-sdk' and version '2.10.0-5' do not appear to match any
binary packages
Marked as fixed in versions vamp-plugin-sdk/2.10.0-5.
Marked as fixed in versions vamp-plugin-sdk/2.10.0-5.
> tags 1074250 + sid trixie
Bug #1074250 [ifupdown2] ifupdown2 not working with python3.12
Added tag(s) trixie and sid.
> found 1074241 1.5.8.1-1
Bug #1074241 [opensnitch] opensnitch can no longer be built on ppc64el.
Marked as found in versions opensnitch/1.5.8.1-1.
> tags 1074241 + sid trixie experimental
Bug #1074241 [opensnitch] opensnitch can no longer be built on ppc64el.
Added tag(s) sid, trixie, and experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1069317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069317
1074175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074175
1074226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074226
1074241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074241
1074250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1069317: marked as done (FTBFS: tests failed)
Your message dated Wed, 26 Jun 2024 14:55:29 + with message-id and subject line Bug#1069317: fixed in vamp-plugin-sdk 2.10.0-5 has caused the Debian Bug report #1069317, regarding FTBFS: tests failed 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 ow...@bugs.debian.org immediately.) -- 1069317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sonic-visualiser Version: 4.5.2-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=sonic- visualiser=armel=4.5.2-2%2Bb3=1713251413=0 FAIL! : TestVampRealTime::fromTimeval() Compared values are not the same Loc: [test-svcore-base.p/../../svcore/base/test/TestVampRealTime.h(144)] -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: vamp-plugin-sdk Source-Version: 2.10.0-5 Done: IOhannes m zmölnig (Debian/GNU) We believe that the bug you reported is fixed in the latest version of vamp-plugin-sdk, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated vamp-plugin-sdk 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Jun 2024 15:51:23 +0200 Source: vamp-plugin-sdk Architecture: source Version: 2.10.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 1069317 Changes: vamp-plugin-sdk (2.10.0-5) unstable; urgency=medium . * Team upload. . * Upload to unstable. * Add time64 compat hints . vamp-plugin-sdk (2.10.0-5~exp) experimental; urgency=medium . * Team upload. . * Rename libraries for 64-bit time_t transition. (Closes: #1069317) * B-D on 'pkgconf' rather than 'pkg-config' * Add autopkgtest * Streamlined copyright information + Add 'licensecheck' target + Generate d/copyright_hints * Apply 'wrap-and-sort -ast' * Bump standards version to 4.7.0 Checksums-Sha1: 2df0215a14e3d5a73d6a9e732606136f1ad41e22 2635 vamp-plugin-sdk_2.10.0-5.dsc 85989bc09f0beac10662d1e8afbb0edbea4483a9 12836 vamp-plugin-sdk_2.10.0-5.debian.tar.xz Checksums-Sha256: 2313c3ad36c3433a25d81d609bbadd959526a02c814b389e0e984a016c449e1d 2635 vamp-plugin-sdk_2.10.0-5.dsc de7f5cfc96d7fe72e247af5fa15cea0c037377801fbf760b6f5db8c7f848dd03 12836 vamp-plugin-sdk_2.10.0-5.debian.tar.xz Files: a5b1748a5ae7dcbf1085f0b5db0fd883 2635 libs optional vamp-plugin-sdk_2.10.0-5.dsc 3aac92b45b529d6c4f1aa55ab56ca3ec 12836 libs optional vamp-plugin-sdk_2.10.0-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmZ8HXUWHGZvcnVtQHVt bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+EoaD/wLsoTSD/XG7soPsOOF7CmRrkT+ qEawm2mdJJO8y9ccqEFdXhcofTo/TLOZGC99qaZPR0fST9qS0yGfR5X0KObEl5QX Q4dThWXgPuyRParYibAU013hpuLKuVZUObc59+UduW62aUP4227w/r+ofTP7lGXc UKl438lv1jxUv8BsDMN45WoM5hSMJl+g3NsguDNp0a8QZIYh+jgpMacIRddmXU5x 1gVe5A8Y9OM5+wrvgVzdUCCfoKtpiJOQbxkoMLN7SPYd9E3tIuNmi0xfDBl2dVJt 5M4X/iCL6pA0YAgfML87QAIaLdBL3WFBLTk9pM/iHM+qpP91qLmhx3yNllp/Vram NYv2EZvG7HYDLtsXdEq+ZabP1+LNKw/Yxw0c3eCp8v4akqIHY3Do4Xr5G8hJg7z8 VkzILh6C+6Mhs/5c3lBT7vJu19TL3jqlQ/cyqvqxK6HO8Tht/OOOtdYj/ZHpuuzn cjLXpjHDWGL7Y5mJe+KuNSFYH083ZDi1LeleTHkKmDRZ9Veji3/PfMaRaul2+ewR OFO8it6cqIHV2IzsPNxOtYk8RTSKci0rkycGmJJdEAVD3R5zUPxANM6sJXLO6qaX Olm8AjlFFOAyA2rqIXvFGjnhlpz2eWqDhq0lvpSg6DixqNRJbE2oC9+Tva8qzPx2 2fqMExXI73P3ohsegA== =hxc4 -END PGP SIGNATURE- pgpWJcU9c2qiJ.pgp Description: PGP signature --- End Message ---
Bug#1074226: marked as done (sonic-visualiser: FTBFS on armel/armhf)
Your message dated Wed, 26 Jun 2024 14:55:29 + with message-id and subject line Bug#1069317: fixed in vamp-plugin-sdk 2.10.0-5 has caused the Debian Bug report #1069317, regarding sonic-visualiser: FTBFS on armel/armhf 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 ow...@bugs.debian.org immediately.) -- 1069317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sonic-visualiser Version: 4.5.2-2 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package FTBFS on armel/armhf is therefore stuck on unsatisfiable dependencies. See https://buildd.debian.org/status/fetch.php?pkg=sonic-visualiser=armel=4.5.2-2%2Bb3=1713251413=0 and https://buildd.debian.org/status/fetch.php?pkg=sonic-visualiser=armhf=4.5.2-2%2Bb3=1713249425=0 -- Regards Patrick Franz --- End Message --- --- Begin Message --- Source: vamp-plugin-sdk Source-Version: 2.10.0-5 Done: IOhannes m zmölnig (Debian/GNU) We believe that the bug you reported is fixed in the latest version of vamp-plugin-sdk, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated vamp-plugin-sdk 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Jun 2024 15:51:23 +0200 Source: vamp-plugin-sdk Architecture: source Version: 2.10.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 1069317 Changes: vamp-plugin-sdk (2.10.0-5) unstable; urgency=medium . * Team upload. . * Upload to unstable. * Add time64 compat hints . vamp-plugin-sdk (2.10.0-5~exp) experimental; urgency=medium . * Team upload. . * Rename libraries for 64-bit time_t transition. (Closes: #1069317) * B-D on 'pkgconf' rather than 'pkg-config' * Add autopkgtest * Streamlined copyright information + Add 'licensecheck' target + Generate d/copyright_hints * Apply 'wrap-and-sort -ast' * Bump standards version to 4.7.0 Checksums-Sha1: 2df0215a14e3d5a73d6a9e732606136f1ad41e22 2635 vamp-plugin-sdk_2.10.0-5.dsc 85989bc09f0beac10662d1e8afbb0edbea4483a9 12836 vamp-plugin-sdk_2.10.0-5.debian.tar.xz Checksums-Sha256: 2313c3ad36c3433a25d81d609bbadd959526a02c814b389e0e984a016c449e1d 2635 vamp-plugin-sdk_2.10.0-5.dsc de7f5cfc96d7fe72e247af5fa15cea0c037377801fbf760b6f5db8c7f848dd03 12836 vamp-plugin-sdk_2.10.0-5.debian.tar.xz Files: a5b1748a5ae7dcbf1085f0b5db0fd883 2635 libs optional vamp-plugin-sdk_2.10.0-5.dsc 3aac92b45b529d6c4f1aa55ab56ca3ec 12836 libs optional vamp-plugin-sdk_2.10.0-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmZ8HXUWHGZvcnVtQHVt bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+EoaD/wLsoTSD/XG7soPsOOF7CmRrkT+ qEawm2mdJJO8y9ccqEFdXhcofTo/TLOZGC99qaZPR0fST9qS0yGfR5X0KObEl5QX Q4dThWXgPuyRParYibAU013hpuLKuVZUObc59+UduW62aUP4227w/r+ofTP7lGXc UKl438lv1jxUv8BsDMN45WoM5hSMJl+g3NsguDNp0a8QZIYh+jgpMacIRddmXU5x 1gVe5A8Y9OM5+wrvgVzdUCCfoKtpiJOQbxkoMLN7SPYd9E3tIuNmi0xfDBl2dVJt 5M4X/iCL6pA0YAgfML87QAIaLdBL3WFBLTk9pM/iHM+qpP91qLmhx3yNllp/Vram NYv2EZvG7HYDLtsXdEq+ZabP1+LNKw/Yxw0c3eCp8v4akqIHY3Do4Xr5G8hJg7z8 VkzILh6C+6Mhs/5c3lBT7vJu19TL3jqlQ/cyqvqxK6HO8Tht/OOOtdYj/ZHpuuzn cjLXpjHDWGL7Y5mJe+KuNSFYH083ZDi1LeleTHkKmDRZ9Veji3/PfMaRaul2+ewR OFO8it6cqIHV2IzsPNxOtYk8RTSKci0rkycGmJJdEAVD3R5zUPxANM6sJXLO6qaX Olm8AjlFFOAyA2rqIXvFGjnhlpz2eWqDhq0lvpSg6DixqNRJbE2oC9+Tva8qzPx2 2fqMExXI73P3ohsegA== =hxc4 -END PGP SIGNATURE- pgp6jssX8k2b6.pgp Description: PGP signature --- End Message ---
Processed: Re: wxsvg: FTBFS with ffmpeg 7.0: me diadec_ffmpeg.cpp:168:75: error: ‘AVCodecPa rameters’ {aka ‘struct AVCodecParameters ’} has no member named ‘channels’
Processing control commands:
> tag -1 +upstream +fixed-upstream
Bug #1072459 [src:wxsvg] wxsvg: FTBFS with ffmpeg 7.0:
mediadec_ffmpeg.cpp:168:75: error: ‘AVCodecParameters’ {aka ‘struct
AVCodecParameters’} has no member named ‘channels’
Added tag(s) upstream.
Bug #1072459 [src:wxsvg] wxsvg: FTBFS with ffmpeg 7.0:
mediadec_ffmpeg.cpp:168:75: error: ‘AVCodecParameters’ {aka ‘struct
AVCodecParameters’} has no member named ‘channels’
Added tag(s) fixed-upstream.
--
1072459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1074226: marked as done (sonic-visualiser: FTBFS on armel/armhf)
Your message dated Tue, 25 Jun 2024 19:00:21 + with message-id and subject line Bug#1069317: fixed in vamp-plugin-sdk 2.10.0-5~exp has caused the Debian Bug report #1069317, regarding sonic-visualiser: FTBFS on armel/armhf 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 ow...@bugs.debian.org immediately.) -- 1069317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sonic-visualiser Version: 4.5.2-2 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package FTBFS on armel/armhf is therefore stuck on unsatisfiable dependencies. See https://buildd.debian.org/status/fetch.php?pkg=sonic-visualiser=armel=4.5.2-2%2Bb3=1713251413=0 and https://buildd.debian.org/status/fetch.php?pkg=sonic-visualiser=armhf=4.5.2-2%2Bb3=1713249425=0 -- Regards Patrick Franz --- End Message --- --- Begin Message --- Source: vamp-plugin-sdk Source-Version: 2.10.0-5~exp Done: IOhannes m zmölnig (Debian/GNU) We believe that the bug you reported is fixed in the latest version of vamp-plugin-sdk, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated vamp-plugin-sdk 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Jun 2024 16:12:45 +0200 Source: vamp-plugin-sdk Binary: libvamp-hostsdk3t64 libvamp-hostsdk3t64-dbgsym libvamp-sdk2t64 libvamp-sdk2t64-dbgsym vamp-examples vamp-examples-dbgsym vamp-plugin-sdk vamp-plugin-sdk-doc Architecture: source amd64 all Version: 2.10.0-5~exp Distribution: experimental Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Description: libvamp-hostsdk3t64 - helper library for Vamp hosts written in C++ libvamp-sdk2t64 - helper library for Vamp plugins written in C++ vamp-examples - example Vamp plugins, host and RDF generator vamp-plugin-sdk - audio analysis and feature extraction plugins (SDK) vamp-plugin-sdk-doc - audio analysis and feature extraction plugins (API documentation) Closes: 1069317 Changes: vamp-plugin-sdk (2.10.0-5~exp) experimental; urgency=medium . * Team upload. . * Rename libraries for 64-bit time_t transition. (Closes: #1069317) * B-D on 'pkgconf' rather than 'pkg-config' * Add autopkgtest * Streamlined copyright information + Add 'licensecheck' target + Generate d/copyright_hints * Apply 'wrap-and-sort -ast' * Bump standards version to 4.7.0 Checksums-Sha1: f6c3500756f02d7069619b43b92326cd9155cff7 2497 vamp-plugin-sdk_2.10.0-5~exp.dsc d52edfb5ef8b352f8f4e923d9c0921b033ba3a9e 12788 vamp-plugin-sdk_2.10.0-5~exp.debian.tar.xz f7f9428530f9e1aba3710f8c13309bf400160d8d 1160836 libvamp-hostsdk3t64-dbgsym_2.10.0-5~exp_amd64.deb 8a4d5cb2bdea757dc8c3d5abc0c56410b639c407 97204 libvamp-hostsdk3t64_2.10.0-5~exp_amd64.deb cb4e9173cbed256cae8d2e3e0a60df3571b3eced 310360 libvamp-sdk2t64-dbgsym_2.10.0-5~exp_amd64.deb e0a11e46097f2fc66787fe98d7e2bb715e3ac55e 48128 libvamp-sdk2t64_2.10.0-5~exp_amd64.deb e0f0f679cd4f02d47c1102fc8d42b064e00fce9c 2962668 vamp-examples-dbgsym_2.10.0-5~exp_amd64.deb 0180ed7b07d6aea9a66060aa8d7b00d8a22ea06e 166456 vamp-examples_2.10.0-5~exp_amd64.deb 77d86219a121294c398f37b8c0fc2de7341cf7ca 2364024 vamp-plugin-sdk-doc_2.10.0-5~exp_all.deb fb76fe375a8d539789643a6304dc74a0e97c13c7 11311 vamp-plugin-sdk_2.10.0-5~exp_amd64.buildinfo 76c9552087fa0090bfb04688ac0b36d4d9f11100 139784 vamp-plugin-sdk_2.10.0-5~exp_amd64.deb Checksums-Sha256: e0214fffbd4a9ab31e200bf8ab6f050771cfe15d485aba39d60958d19c456b6c 2497 vamp-plugin-sdk_2.10.0-5~exp.dsc 376a73436cc9dfc229edf5d804e351474bc037a84bc862fc19966e705ca7a3e4 12788 vamp-plugin-sdk_2.10.0-5~exp.debian.tar.xz 12694ad4022bdbac6acb028965ca48537d3536485d01a54df5e158a5ddb0d04c 1160836 libvamp-hostsdk3t64-dbgsym_2.10.0-5~exp_amd64.deb fd8d4d66dfbe62b0cb99aefcee2d53c1b9844caedb2fa6e98cb57df2cb4ad7e7 97204 libvamp-hostsdk3t64_2.10.0-5~exp_amd64.deb 29cc09513bd72e04747f6deaf6a2a37f5b2c9589f8d20fee0f2a090550bdd77e 310360 libvamp
Bug#1069317: marked as done (FTBFS: tests failed)
Your message dated Tue, 25 Jun 2024 19:00:21 + with message-id and subject line Bug#1069317: fixed in vamp-plugin-sdk 2.10.0-5~exp has caused the Debian Bug report #1069317, regarding FTBFS: tests failed 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 ow...@bugs.debian.org immediately.) -- 1069317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sonic-visualiser Version: 4.5.2-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=sonic- visualiser=armel=4.5.2-2%2Bb3=1713251413=0 FAIL! : TestVampRealTime::fromTimeval() Compared values are not the same Loc: [test-svcore-base.p/../../svcore/base/test/TestVampRealTime.h(144)] -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: vamp-plugin-sdk Source-Version: 2.10.0-5~exp Done: IOhannes m zmölnig (Debian/GNU) We believe that the bug you reported is fixed in the latest version of vamp-plugin-sdk, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated vamp-plugin-sdk 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Jun 2024 16:12:45 +0200 Source: vamp-plugin-sdk Binary: libvamp-hostsdk3t64 libvamp-hostsdk3t64-dbgsym libvamp-sdk2t64 libvamp-sdk2t64-dbgsym vamp-examples vamp-examples-dbgsym vamp-plugin-sdk vamp-plugin-sdk-doc Architecture: source amd64 all Version: 2.10.0-5~exp Distribution: experimental Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Description: libvamp-hostsdk3t64 - helper library for Vamp hosts written in C++ libvamp-sdk2t64 - helper library for Vamp plugins written in C++ vamp-examples - example Vamp plugins, host and RDF generator vamp-plugin-sdk - audio analysis and feature extraction plugins (SDK) vamp-plugin-sdk-doc - audio analysis and feature extraction plugins (API documentation) Closes: 1069317 Changes: vamp-plugin-sdk (2.10.0-5~exp) experimental; urgency=medium . * Team upload. . * Rename libraries for 64-bit time_t transition. (Closes: #1069317) * B-D on 'pkgconf' rather than 'pkg-config' * Add autopkgtest * Streamlined copyright information + Add 'licensecheck' target + Generate d/copyright_hints * Apply 'wrap-and-sort -ast' * Bump standards version to 4.7.0 Checksums-Sha1: f6c3500756f02d7069619b43b92326cd9155cff7 2497 vamp-plugin-sdk_2.10.0-5~exp.dsc d52edfb5ef8b352f8f4e923d9c0921b033ba3a9e 12788 vamp-plugin-sdk_2.10.0-5~exp.debian.tar.xz f7f9428530f9e1aba3710f8c13309bf400160d8d 1160836 libvamp-hostsdk3t64-dbgsym_2.10.0-5~exp_amd64.deb 8a4d5cb2bdea757dc8c3d5abc0c56410b639c407 97204 libvamp-hostsdk3t64_2.10.0-5~exp_amd64.deb cb4e9173cbed256cae8d2e3e0a60df3571b3eced 310360 libvamp-sdk2t64-dbgsym_2.10.0-5~exp_amd64.deb e0a11e46097f2fc66787fe98d7e2bb715e3ac55e 48128 libvamp-sdk2t64_2.10.0-5~exp_amd64.deb e0f0f679cd4f02d47c1102fc8d42b064e00fce9c 2962668 vamp-examples-dbgsym_2.10.0-5~exp_amd64.deb 0180ed7b07d6aea9a66060aa8d7b00d8a22ea06e 166456 vamp-examples_2.10.0-5~exp_amd64.deb 77d86219a121294c398f37b8c0fc2de7341cf7ca 2364024 vamp-plugin-sdk-doc_2.10.0-5~exp_all.deb fb76fe375a8d539789643a6304dc74a0e97c13c7 11311 vamp-plugin-sdk_2.10.0-5~exp_amd64.buildinfo 76c9552087fa0090bfb04688ac0b36d4d9f11100 139784 vamp-plugin-sdk_2.10.0-5~exp_amd64.deb Checksums-Sha256: e0214fffbd4a9ab31e200bf8ab6f050771cfe15d485aba39d60958d19c456b6c 2497 vamp-plugin
Bug#1044283: marked as done (gmerlin-encoders: Fails to build source after successful build)
Your message dated Tue, 25 Jun 2024 09:48:55 + with message-id and subject line Bug#1044283: fixed in gmerlin-encoders 2.0.0~svn6278-5 has caused the Debian Bug report #1044283, regarding gmerlin-encoders: Fails to build source after successful build 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 ow...@bugs.debian.org immediately.) -- 1044283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gmerlin-encoders Version: 2.0.0~svn6278-4 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > --- > > dpkg-buildpackage: info: source package gmerlin-encoders > dpkg-buildpackage: info: source version 2.0.0~svn6278-4 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by IOhannes m zmölnig (Debian/GNU) > > dpkg-source --before-build . > debian/rules clean > dh clean >dh_auto_clean > make -j8 distclean > make[1]: Entering directory '/<>' > Making distclean in po > make[2]: Entering directory '/<>/po' > rm -f *.insert-header > rm -f remove-potcdate.sed > rm -f stamp-poT > rm -f core core.* gmerlin-encoders.po gmerlin-encoders.1po > gmerlin-encoders.2po *.new.po > rm -fr *.o > rm -f Makefile Makefile.in POTFILES *.mo > make[2]: Leaving directory '/<>/po' > Making distclean in lib > make[2]: Entering directory '/<>/lib' > rm -rf .libs _libs > test -z "libgmerlin_encoders.la libbgflac.la libbgshout.la" || rm -f > libgmerlin_encoders.la libbgflac.la libbgshout.la > rm -f *.o > rm -f *.lo > rm -f *.tab.c > test -z "" || rm -f > rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags > test . = "." || test -z "" || rm -f > rm -f ./so_locations > rm -f ./.deps/id3v1.Plo > rm -f ./.deps/libbgflac_la-bgflac.Plo > rm -f ./.deps/libbgshout_la-bgshout.Plo > rm -f ./.deps/vorbiscomment.Plo > rm -f Makefile > make[2]: Leaving directory '/<>/lib' > Making distclean in include > make[2]: Entering directory '/<>/include' > rm -rf .libs _libs > rm -f *.lo > test -z "" || rm -f > rm -f config.h stamp-h1 > rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags > test . = "." || test -z "" || rm -f > rm -f Makefile > make[2]: Leaving directory '/<>/include' > Making distclean in plugins > make[2]: Entering directory '/<>/plugins' > Making distclean in ogg > make[3]: Entering directory '/<>/plugins/ogg' > test -z "e_vorbis.la c_vorbisenc.la c_theoraenc.la e_speex.la c_speexenc.la > e_opus.la c_opusenc.la c_flacenc.la b_ogg.la " || rm -f e_vorbis.la > c_vorbisenc.la c_theoraenc.la e_speex.la c_speexenc.la e_opus.la c_opusenc.la > c_flacenc.la b_ogg.la > rm -rf .libs _libs > rm -f *.o > rm -f *.lo > rm -f *.tab.c > test -z "" || rm -f > rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags > test . = "." || test -z "" || rm -f > rm -f ./so_locations > rm -f ./.deps/b_ogg_la-b_ogg.Plo > rm -f ./.deps/b_ogg_la-ogg_common.Plo > rm -f ./.deps/b_ogg_la-opus.Plo > rm -f ./.deps/b_ogg_la-speex.Plo > rm -f ./.deps/b_ogg_la-theora.Plo > rm -f ./.deps/b_ogg_la-vorbis.Plo > rm -f ./.deps/c_flacenc_la-c_flacenc.Plo > rm -f ./.deps/c_flacenc_la-flac.Plo > rm -f ./.deps/c_flacenc_la-ogg_common.Plo > rm -f ./.deps/c_opusenc_la-c_opusenc.Plo > rm -f ./.deps/c_opusenc_la-ogg_common.Plo > rm -f ./.deps/c_opusenc_la-opus.Plo > rm -f ./.deps/c_sch
Bug#1072415: marked as done (gmerlin-encoders: FTBFS with ffmpeg 7.0: codec.c:340:8: error: ‘AVCodecContext’ has no member named ‘channels’)
Your message dated Tue, 25 Jun 2024 09:48:55 + with message-id and subject line Bug#1072415: fixed in gmerlin-encoders 2.0.0~svn6278-5 has caused the Debian Bug report #1072415, regarding gmerlin-encoders: FTBFS with ffmpeg 7.0: codec.c:340:8: error: ‘AVCodecContext’ has no member named ‘channels’ 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 ow...@bugs.debian.org immediately.) -- 1072415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gmerlin-encoders Version: 2.0.0~svn6278-4 Severity: important Tags: trixie sid ftbfs Usertags: ffmpeg-7.0 Hi, during a rebuild of the reverse dependencies for the transition to ffmpeg 7.0, your package failed to build Relevant part (hopefully): > /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../../include -I../../include -Wdate-time -D_FORTIFY_SOURCE=2 > -I/usr/include/aarch64-linux-gnu -I/usr/include/aarch64-linux-gnu > -DLOCALE_DIR=\"/usr/share/locale\" -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -mbranch-protection=standard -D_REENTRANT > -D_FILE_OFFSET_BITS=64 -O3 -fomit-frame-pointer -ffast-math > -I/usr/include/libxml2 -Wall -Wmissing-declarations > -Wdeclaration-after-statement -c -o codec.lo codec.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../include -I../../include > -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/aarch64-linux-gnu > -I/usr/include/aarch64-linux-gnu -DLOCALE_DIR=\"/usr/share/locale\" -g -O2 > -Werror=implicit-function-declaration "-ffile-prefix-map=/<>=." > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -mbranch-protection=standard -D_REENTRANT > -D_FILE_OFFSET_BITS=64 -O3 -fomit-frame-pointer -ffast-math > -I/usr/include/libxml2 -Wall -Wmissing-declarations > -Wdeclaration-after-statement -c codec.c -fPIC -DPIC -o .libs/codec.o > codec.c: In function ‘find_encoder’: > codec.c:54:19: warning: assignment discards ‘const’ qualifier from pointer > target type [-Wdiscarded-qualifiers] >54 | if(!(ctx->codec = avcodec_find_encoder(ctx->id))) > | ^ > codec.c: In function ‘flush_audio’: > codec.c:212:3: warning: ‘av_init_packet’ is deprecated > [-Wdeprecated-declarations] > 212 | av_init_packet(); > | ^~ > In file included from > /usr/include/aarch64-linux-gnu/libavcodec/codec_par.h:33, > from > /usr/include/aarch64-linux-gnu/libavformat/avformat.h:312, > from ffmpeg_common.h:24, > from codec.c:22: > /usr/include/aarch64-linux-gnu/libavcodec/packet.h:653:6: note: declared here > 653 | void av_init_packet(AVPacket *pkt); > | ^~ > codec.c:255:5: warning: ‘av_init_packet’ is deprecated > [-Wdeprecated-declarations] > 255 | av_init_packet(); > | ^~ > /usr/include/aarch64-linux-gnu/libavcodec/packet.h:653:6: note: declared here > 653 | void av_init_packet(AVPacket *pkt); > | ^~ > codec.c: In function ‘bg_ffmpeg_set_audio_format_avctx’: > codec.c:340:8: error: ‘AVCodecContext’ has no member named ‘channels’ > 340 | avctx->channels= fmt->num_channels; > |^~ > codec.c: In function ‘bg_ffmpeg_set_audio_format_params’: > codec.c:350:8: error: ‘AVCodecParameters’ has no member named ‘channels’ > 350 | avctx->channels= fmt->num_channels; > |^~ > codec.c: In function ‘bg_ffmpeg_codec_open_audio’: > codec.c:370:15: error: ‘AVCodecContext’ has no member named ‘channel_layout’; > did you mean ‘ch_layout’? > 370 | ctx->avctx->channel_layout = > | ^~ > | ch_layout > codec.c:405:13: warning: assignment discards ‘const’ qualifier from pointer > target type [-Wdiscarded-qualifiers] > 405 | ((ofmt = guess_format(ctx->format->short_name, NULL, NULL)) && > | ^ > codec.c: In function ‘flush_video’: > codec.c:509:5: warning: ‘av_init_packet’ is deprecated > [-Wdeprecated-declarations] > 509 | av_init_packet(); > | ^~ > /usr/include/aarch64-linux-gnu/libavcodec/packet.h:653:6: n
Processed: Bug#1072414 marked as pending in gmerlin-avdecoder
Processing control commands: > tag -1 pending Bug #1072414 [src:gmerlin-avdecoder] gmerlin-avdecoder: FTBFS with ffmpeg 7.0: demux_ffmpeg.c:756:27: error: ‘const struct AVInputFormat’ has no member named ‘read_seek’ Added tag(s) pending. -- 1072414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1072415 marked as pending in gmerlin-encoders
Processing control commands: > tag -1 pending Bug #1072415 [src:gmerlin-encoders] gmerlin-encoders: FTBFS with ffmpeg 7.0: codec.c:340:8: error: ‘AVCodecContext’ has no member named ‘channels’ Added tag(s) pending. -- 1072415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1073324: marked as done (gmerlin-avdecoder: FTBFS: options.c:46:45: error: implicit declaration of function ‘atoi’ [-Werror=implicit-function-declaration])
Your message dated Tue, 25 Jun 2024 09:19:13 + with message-id and subject line Bug#1073324: fixed in gmerlin-avdecoder 2.0.0~svn6298~dfsg0-4 has caused the Debian Bug report #1073324, regarding gmerlin-avdecoder: FTBFS: options.c:46:45: error: implicit declaration of function ‘atoi’ [-Werror=implicit-function-declaration] 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 ow...@bugs.debian.org immediately.) -- 1073324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073324 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gmerlin-avdecoder Version: 2.0.0~svn6298~dfsg0-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../include -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -ffast-math > -I/usr/include/libxml2 -DLOCALE_DIR=\"/usr/share/locale\" -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -D_REENTRANT -D_FILE_OFFSET_BITS=64 > -Wall -Wmissing-declarations -Wdeclaration-after-statement -c -o i_dvd.lo > i_dvd.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../include -I../include > -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -ffast-math -I/usr/include/libxml2 > -DLOCALE_DIR=\"/usr/share/locale\" -g -O2 > -Werror=implicit-function-declaration "-ffile-prefix-map=/<>=." > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -D_REENTRANT -D_FILE_OFFSET_BITS=64 > -Wall -Wmissing-declarations -Wdeclaration-after-statement -c avdec_common.c > -fPIC -DPIC -o .libs/avdec_common.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../include -I../include > -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -ffast-math -I/usr/include/libxml2 > -DLOCALE_DIR=\"/usr/share/locale\" -g -O2 > -Werror=implicit-function-declaration "-ffile-prefix-map=/<>=." > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -D_REENTRANT -D_FILE_OFFSET_BITS=64 > -Wall -Wmissing-declarations -Wdeclaration-after-statement -c c_avdec_audio.c > -fPIC -DPIC -o .libs/c_avdec_audio.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../include -I../include > -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -ffast-math -I/usr/include/libxml2 > -DLOCALE_DIR=\"/usr/share/locale\" -g -O2 > -Werror=implicit-function-declaration "-ffile-prefix-map=/<>=." > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -D_REENTRANT -D_FILE_OFFSET_BITS=64 > -Wall -Wmissing-declarations -Wdeclaration-after-statement -c c_avdec_video.c > -fPIC -DPIC -o .libs/c_avdec_video.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../include -I../include > -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -ffast-math -I/usr/include/libxml2 > -DLOCALE_DIR=\"/usr/share/locale\" -g -O2 > -Werror=implicit-function-declaration "-ffile-prefix-map=/<>=." > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -D_REENTRANT -D_FILE_OFFSET_BITS=64 > -Wall -Wmissing-declarations -Wdeclaration-after-statement -c i_dvd.c -fPIC > -DPIC -o .libs/i_dvd.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../include -I../include > -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -ffast-math -I/usr/include/libxml2 > -DLOCALE_DIR=\"/usr/share/locale\" -g -O2 > -Werror=implicit-function-declaration "-ffile-prefix-map=/<>=." > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -D_REENTRANT -D_FILE_OFFSET_BITS=64 > -Wall -Wmissing-declarations -Wdeclaration-after-statement -c i_vcd.c -fPIC > -DPIC -o .libs/i_vcd.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../include -I../include > -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -ffast-math -I/usr/include/libxml2 > -DLOCALE_DIR=\"/usr/share/locale\" -g -O2 > -Werror=implicit-function-declaration "-ffile-prefix-map=/<>=." > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protecti
