Processed: pulseaudio: FTBFS cpu-volume-test fails
Processing control commands: > affects -1 src:pulseaudio Bug #1067458 [src:orc] pulseaudio: FTBFS cpu-volume-test fails Added indication that 1067458 affects src:pulseaudio > block 1036884 by -1 Bug #1036884 [release.debian.org] transition: time64_t 1036884 was blocked by: 1067069 1067193 1065787 1067171 1062847 1065973 1067189 1067192 1067190 1066794 1066049 1055530 1065816 1067170 1067175 1055352 1036884 was not blocking any bugs. Added blocking bug(s) of 1036884: 1067458 -- 1036884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036884 1067458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067430: marked as done (nmu: graphviz_2.42.2-9)
Your message dated Thu, 21 Mar 2024 15:41:44 +0100 with message-id and subject line Re: Bug#1067430: nmu: graphviz_2.42.2-9 has caused the Debian Bug report #1067430, regarding nmu: graphviz_2.42.2-9 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.) -- 1067430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal X-Debbugs-Cc: graph...@packages.debian.org, debian-...@lists.debian.org Control: affects -1 + src:graphviz User: release.debian@packages.debian.org Usertags: binnmu libgvc6_2.42.2-9_armel depends on libglib2.0-0t64 (the "new" side of the 64-bit time_t transition) but also on libgts-0.7-5 (the "old" side), which was only successfully NMU'd recently; the original NMU seems to have had a symbols file bug that made it uninstallable. nmu graphviz_2.42.2-9 . armel armhf . unstable . -m "rebuild against libgts-0.7-5t64" dw graphviz_2.42.2-9 . armel armhf . -m 'libgts-dev (>= 0.7.6+darcs121130-5.2)' This is blocking the pending rebuild of sane-backends. ignition-common might need similar treatment. The other rdeps of libgts-0.7-5 seem to have rebuilds pending and stuck in BD-Uninstallable on armel/armhf for other reasons, so they probably don't need a binNMU. I have to wonder whether a library that is only available as a VCS snapshot from 2012 is something that ought to be in our critical path for re-bootstrapping... but apparently graphviz needs it for "interconnected triangles support", whatever that means. smcv --- End Message --- --- Begin Message --- On 2024-03-21 14:17:44 +, Simon McVittie wrote: > Package: release.debian.org > Severity: normal > X-Debbugs-Cc: graph...@packages.debian.org, debian-...@lists.debian.org > Control: affects -1 + src:graphviz > User: release.debian@packages.debian.org > Usertags: binnmu > > libgvc6_2.42.2-9_armel depends on libglib2.0-0t64 (the "new" side of > the 64-bit time_t transition) but also on libgts-0.7-5 (the "old" side), > which was only successfully NMU'd recently; the original NMU seems to > have had a symbols file bug that made it uninstallable. > > nmu graphviz_2.42.2-9 . armel armhf . unstable . -m "rebuild against > libgts-0.7-5t64" > dw graphviz_2.42.2-9 . armel armhf . -m 'libgts-dev (>= > 0.7.6+darcs121130-5.2)' Scheduled > This is blocking the pending rebuild of sane-backends. > > ignition-common might need similar treatment. The other rdeps of > libgts-0.7-5 seem to have rebuilds pending and stuck in BD-Uninstallable > on armel/armhf for other reasons, so they probably don't need a binNMU. I'll check the auto- tracker and schedule as necessary. Cheers -- Sebastian Ramacher--- End Message ---
Bug#1067429: marked as done (nmu: iproute2_6.8.0-1)
Your message dated Thu, 21 Mar 2024 15:39:48 +0100 with message-id and subject line Re: Bug#1067429: nmu: iproute2_6.8.0-1 has caused the Debian Bug report #1067429, regarding nmu: iproute2_6.8.0-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.) -- 1067429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal X-Debbugs-Cc: iprou...@packages.debian.org Control: affects -1 + src:iproute2 User: release.debian@packages.debian.org Usertags: binnmu nmu iproute2_6.8.0-1 . armel armhf . unstable . -m "Rebuild with libelf1t64" See https://packages.debian.org/unstable/iproute2 --- End Message --- --- Begin Message --- On 2024-03-21 19:03:11 +0500, Andrey Rakhmatullin wrote: > Package: release.debian.org > Severity: normal > X-Debbugs-Cc: iprou...@packages.debian.org > Control: affects -1 + src:iproute2 > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu iproute2_6.8.0-1 . armel armhf . unstable . -m "Rebuild with libelf1t64" Thanks, scheduled Cheers -- Sebastian Ramacher--- End Message ---
Processed: nmu: graphviz_2.42.2-9
Processing control commands: > affects -1 + src:graphviz Bug #1067430 [release.debian.org] nmu: graphviz_2.42.2-9 Added indication that 1067430 affects src:graphviz -- 1067430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067430: nmu: graphviz_2.42.2-9
Package: release.debian.org Severity: normal X-Debbugs-Cc: graph...@packages.debian.org, debian-...@lists.debian.org Control: affects -1 + src:graphviz User: release.debian@packages.debian.org Usertags: binnmu libgvc6_2.42.2-9_armel depends on libglib2.0-0t64 (the "new" side of the 64-bit time_t transition) but also on libgts-0.7-5 (the "old" side), which was only successfully NMU'd recently; the original NMU seems to have had a symbols file bug that made it uninstallable. nmu graphviz_2.42.2-9 . armel armhf . unstable . -m "rebuild against libgts-0.7-5t64" dw graphviz_2.42.2-9 . armel armhf . -m 'libgts-dev (>= 0.7.6+darcs121130-5.2)' This is blocking the pending rebuild of sane-backends. ignition-common might need similar treatment. The other rdeps of libgts-0.7-5 seem to have rebuilds pending and stuck in BD-Uninstallable on armel/armhf for other reasons, so they probably don't need a binNMU. I have to wonder whether a library that is only available as a VCS snapshot from 2012 is something that ought to be in our critical path for re-bootstrapping... but apparently graphviz needs it for "interconnected triangles support", whatever that means. smcv
Processed: nmu: iproute2_6.8.0-1
Processing control commands: > affects -1 + src:iproute2 Bug #1067429 [release.debian.org] nmu: iproute2_6.8.0-1 Added indication that 1067429 affects src:iproute2 -- 1067429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067429: nmu: iproute2_6.8.0-1
Package: release.debian.org Severity: normal X-Debbugs-Cc: iprou...@packages.debian.org Control: affects -1 + src:iproute2 User: release.debian@packages.debian.org Usertags: binnmu nmu iproute2_6.8.0-1 . armel armhf . unstable . -m "Rebuild with libelf1t64" See https://packages.debian.org/unstable/iproute2
Bug#1067421: marked as done (nmu: gstreamer1.0_1.24.0-1)
Your message dated Thu, 21 Mar 2024 13:12:44 +0100 with message-id <2659a112-9b0a-4ea6-a819-eea6534ee...@debian.org> and subject line Re: Bug#1067421: nmu: gstreamer1.0_1.24.0-1 has caused the Debian Bug report #1067421, regarding nmu: gstreamer1.0_1.24.0-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.) -- 1067421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal X-Debbugs-Cc: gstreamer...@packages.debian.org, debian-...@lists.debian.org Control: affects -1 + src:gstreamer1.0 User: release.debian@packages.debian.org Usertags: binnmu gst-plugins-base1.0 is currently unbuildable on armel and armhf due to gstreamer1.0 having been built before libdw1 transitioned to libdw1t64. Please consider: nmu gstreamer1.0_1.24.0-1 . armel armhf . unstable . -m "rebuild against libdw1t64" (or maybe rebuild on all architectures if avoiding multi-arch skew is considered to be important). This is one of several things blocking gtk4 being rebuilt for the time64 transition, which in turn prevents rebuilds of a lot of the GTK ecosystem from being tried. In the short term I'm intending to work around that by disabling its GStreamer plugin on the affected architectures, but upstream considers this to be an unsupported configuration, so we should put it back as soon as we can. Thanks, smcv --- End Message --- --- Begin Message --- On 21/03/2024 12:49, Simon McVittie wrote: Package: release.debian.org Severity: normal X-Debbugs-Cc: gstreamer...@packages.debian.org, debian-...@lists.debian.org Control: affects -1 + src:gstreamer1.0 User: release.debian@packages.debian.org Usertags: binnmu gst-plugins-base1.0 is currently unbuildable on armel and armhf due to gstreamer1.0 having been built before libdw1 transitioned to libdw1t64. Please consider: nmu gstreamer1.0_1.24.0-1 . armel armhf . unstable . -m "rebuild against libdw1t64" Scheduled. Thanks, Emilio--- End Message ---
Bug#1067421: nmu: gstreamer1.0_1.24.0-1
On Thu, 21 Mar 2024 at 11:49:22 +, Simon McVittie wrote: > gst-plugins-base1.0 is currently unbuildable on armel and armhf due to > gstreamer1.0 having been built before libdw1 transitioned to libdw1t64. > Please consider: > > nmu gstreamer1.0_1.24.0-1 . armel armhf . unstable . -m "rebuild against > libdw1t64" I should have mentioned that gstreamer1.0 has a FTBFS (test failure) bug reported (https://bugs.debian.org/1066797), but when I tried the build in armel and armhf chroots on the porterbox amdahl, it succeeded - so I think it's worth trying the binNMU anyway, in the hope that the FTBFS either doesn't affect these architectures or is intermittent. smcv
Processed: nmu: gstreamer1.0_1.24.0-1
Processing control commands: > affects -1 + src:gstreamer1.0 Bug #1067421 [release.debian.org] nmu: gstreamer1.0_1.24.0-1 Added indication that 1067421 affects src:gstreamer1.0 -- 1067421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067421: nmu: gstreamer1.0_1.24.0-1
Package: release.debian.org Severity: normal X-Debbugs-Cc: gstreamer...@packages.debian.org, debian-...@lists.debian.org Control: affects -1 + src:gstreamer1.0 User: release.debian@packages.debian.org Usertags: binnmu gst-plugins-base1.0 is currently unbuildable on armel and armhf due to gstreamer1.0 having been built before libdw1 transitioned to libdw1t64. Please consider: nmu gstreamer1.0_1.24.0-1 . armel armhf . unstable . -m "rebuild against libdw1t64" (or maybe rebuild on all architectures if avoiding multi-arch skew is considered to be important). This is one of several things blocking gtk4 being rebuilt for the time64 transition, which in turn prevents rebuilds of a lot of the GTK ecosystem from being tried. In the short term I'm intending to work around that by disabling its GStreamer plugin on the affected architectures, but upstream considers this to be an unsupported configuration, so we should put it back as soon as we can. Thanks, smcv
Bug#1067417: marked as done (nmu: ghostscript_10.02.1~dfsg-3)
Your message dated Thu, 21 Mar 2024 11:22:54 +0100 with message-id and subject line Re: Bug#1067417: nmu: ghostscript_10.02.1~dfsg-3 has caused the Debian Bug report #1067417, regarding nmu: ghostscript_10.02.1~dfsg-3 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.) -- 1067417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal X-Debbugs-Cc: ghostscr...@packages.debian.org Control: affects -1 + src:ghostscript User: release.debian@packages.debian.org Usertags: binnmu nmu ghostscript_10.02.1~dfsg-3 . armhf . unstable . -m "Rebuild for libcups2t64" For some reason ghostscript on armhf was built with non-t64 libcups2 in the previous binNMU, other arches look correct, looking at https://packages.debian.org/sid/libgs10. --- End Message --- --- Begin Message --- On 2024-03-21 15:16:35 +0500, Andrey Rakhmatullin wrote: > Package: release.debian.org > Severity: normal > X-Debbugs-Cc: ghostscr...@packages.debian.org > Control: affects -1 + src:ghostscript > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu ghostscript_10.02.1~dfsg-3 . armhf . unstable . -m "Rebuild for > libcups2t64" Thanks, scheduled. Cheers -- Sebastian Ramacher--- End Message ---
Processed: nmu: ghostscript_10.02.1~dfsg-3
Processing control commands: > affects -1 + src:ghostscript Bug #1067417 [release.debian.org] nmu: ghostscript_10.02.1~dfsg-3 Added indication that 1067417 affects src:ghostscript -- 1067417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067417: nmu: ghostscript_10.02.1~dfsg-3
Package: release.debian.org Severity: normal X-Debbugs-Cc: ghostscr...@packages.debian.org Control: affects -1 + src:ghostscript User: release.debian@packages.debian.org Usertags: binnmu nmu ghostscript_10.02.1~dfsg-3 . armhf . unstable . -m "Rebuild for libcups2t64" For some reason ghostscript on armhf was built with non-t64 libcups2 in the previous binNMU, other arches look correct, looking at https://packages.debian.org/sid/libgs10.
