Bug#1020819: subtitlecomposer: Cannot load any video: "Option refcounted_frames not found" error (removed from FFmpeg)

Package: subtitlecomposer Version: 0.7.1-3 Severity: grave Tags: fixed-upstream patch Justification: renders package unusable Forwarded: https://invent.kde.org/multimedia/subtitlecomposer/-/issues/68 Dear Maintainer, I cannot load any video into Subtitle Composer. After I select a video from

Bug#1020062: marked as done (django-cors-headers: FTBFS: ModuleNotFoundError: No module named 'setuptools')

Your message dated Tue, 27 Sep 2022 04:18:57 + with message-id and subject line Bug#1020062: fixed in django-cors-headers 3.13.0-1 has caused the Debian Bug report #1020062, regarding django-cors-headers: FTBFS: ModuleNotFoundError: No module named 'setuptools' to be marked as done. This

Bug#1020818: abi-dumper: abi-dumper 1.2 doesn't work with today's binaries

Package: abi-dumper Version: 1.2-1 Severity: serious X-Debbugs-Cc: none, Dima Kogan Hi. abi-dumper doesn't work anymore. Build tools we ship today use DWARF 5, which abi-dumper 1.2 doesn't work with. There are reports about it: https://github.com/lvc/abi-dumper/issues/33 I see this when I

Processed: affects 1020204

Processing commands for cont...@bugs.debian.org: > affects 1020204 + elisp-refs Bug #1020204 [dh-elpa] elisp-refs: FTBFS: make: *** [debian/rules:4: binary] Error 25 Bug #1020179 [dh-elpa] "dh_elpa_test should not cache native code in non-writable $HOME" Bug #1020186 [dh-elpa] markdown-toc-el:

Processed: do not affect testing

Processing commands for cont...@bugs.debian.org: > tag 1020177 sid Bug #1020177 {Done: David Bremner } [src:gnuplot-mode] gnuplot-mode: FTBFS: mkdir: cannot create directory ‘././sbuild-nonexistent’: Permission denied Ignoring request to alter tags of bug #1020177 to the same tags previously

Processed: cleanup dh_elpa_test bugs 7/n

Processing commands for cont...@bugs.debian.org: > reassign 1020186 dh-elpa Bug #1020186 [src:markdown-toc-el] markdown-toc-el: FTBFS: make: *** [debian/rules:4: binary] Error 25 Bug reassigned from package 'src:markdown-toc-el' to 'dh-elpa'. No longer marked as found in versions

Processed: cleanup dh_elpa_test bugs 7/n

Processing commands for cont...@bugs.debian.org: > reassign 1020210 dh-elpa Bug #1020210 [src:emacs-websocket] emacs-websocket: FTBFS: make: *** [debian/rules:4: binary] Error 25 Bug reassigned from package 'src:emacs-websocket' to 'dh-elpa'. No longer marked as found in versions

Processed: cleanup dh_elpa_test bugs 6/n

Processing commands for cont...@bugs.debian.org: > reassign 1020042 elpa-evil Bug #1020042 [src:emacs-bind-map] emacs-bind-map: FTBFS: Errors while processing: elpa-evil sbuild-build-depends-main-dummy Bug reassigned from package 'src:emacs-bind-map' to 'elpa-evil'. No longer marked as found

Processed: cleanup dh_elpa_test bugs 5/n

Processing commands for cont...@bugs.debian.org: > reassign 1020196 dh-elpa Bug #1020196 [src:use-package] use-package: FTBFS: make: *** [debian/rules:4: binary] Error 25 Bug reassigned from package 'src:use-package' to 'dh-elpa'. No longer marked as found in versions use-package/2.4.1-1.

Processed: cleanup dh_elpa_test bugs 4/n

Processing commands for cont...@bugs.debian.org: > reassign 1020191 dh-elpa Bug #1020191 [src:ebib] ebib: FTBFS: make: *** [debian/rules:4: build] Error 25 Bug reassigned from package 'src:ebib' to 'dh-elpa'. No longer marked as found in versions ebib/2.38.1-1. Ignoring request to alter fixed

Processed: fix affects

Processing commands for cont...@bugs.debian.org: > affects 1020179 +package-lint-el Bug #1020179 [dh-elpa] "dh_elpa_test should not cache native code in non-writable $HOME" Bug #1020203 [dh-elpa] package-lint-el: FTBFS: make: *** [debian/rules:4: binary] Error 25 Bug #1020204 [dh-elpa]

Processed: cleanup dh_elpa_test bugs 3/n

Processing commands for cont...@bugs.debian.org: > reassign 1020204 dh-elpa Bug #1020204 [src:elisp-refs] elisp-refs: FTBFS: make: *** [debian/rules:4: binary] Error 25 Bug reassigned from package 'src:elisp-refs' to 'dh-elpa'. No longer marked as found in versions elisp-refs/1.4-1. Ignoring

Bug#1020017: marked as done (bats: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

Your message dated Mon, 26 Sep 2022 21:48:58 + with message-id and subject line Bug#1020017: fixed in bats 1.8.0-1 has caused the Debian Bug report #1020017, regarding bats: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity to be marked as done. This means that you

Bug#1017299: golang-gopkg-hlandau-service.v2: FTBFS: cannot find package "github.com/erikdubbelboer/gspt"

Source: golang-gopkg-hlandau-service.v2 Version: 2.0.16-4 Followup-For: Bug #1017299 Control: tags -1 patch I have prepared a debdiff patch to fix this issue. Please find it in the attachment. Regards, ~ Arun Kumar Pariyar diff -Nru golang-gopkg-hlandau-service.v2-2.0.16/debian/changelog

Processed: Re: golang-gopkg-hlandau-service.v2: FTBFS: cannot find package "github.com/erikdubbelboer/gspt"

Processing control commands: > tags -1 patch Bug #1017299 [src:golang-gopkg-hlandau-service.v2] golang-gopkg-hlandau-service.v2: FTBFS: cannot find package "github.com/erikdubbelboer/gspt" Added tag(s) patch. -- 1017299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017299 Debian Bug

Processed: cleanup dh_elpa_test bugs 2/n

Processing commands for cont...@bugs.debian.org: > reassign 1020203 dh-elpa Bug #1020203 [src:package-lint-el] package-lint-el: FTBFS: make: *** [debian/rules:4: binary] Error 25 Bug reassigned from package 'src:package-lint-el' to 'dh-elpa'. No longer marked as found in versions

Processed: gmap: FTBFS on avx512 host in buster

Processing control commands: > fixed -1 2021-02-22+ds-1 Bug #1020793 [src:gmap] gmap: FTBFS on avx512 host in buster Marked as fixed in versions gmap/2021-02-22+ds-1. -- 1020793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020793 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1020793: gmap: FTBFS on avx512 host in buster

Source: gmap Version: 2019-01-24-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Control: fixed -1 2021-02-22+ds-1 Hi, during a local rebuild of all contrib and non-free packages I noticed that gmap/buster did FTBFS while it

Bug#1019586: marked as done (gnome-shell-extension-weather: Extension not compatible with libsoup3)

Your message dated Mon, 26 Sep 2022 19:20:19 + with message-id and subject line Bug#1019586: fixed in gnome-shell-extension-weather 119-1 has caused the Debian Bug report #1019586, regarding gnome-shell-extension-weather: Extension not compatible with libsoup3 to be marked as done. This

Processed: Re: Please update nvidia-cuda-toolkit to 11.5.1 or later

Processing control commands: > reopen -1 Bug #1016625 {Done: Andreas Beckmann } [nvidia-cuda-toolkit] Please update nvidia-cuda-toolkit to 11.5.1 or later 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them.

Bug#1016625: Please update nvidia-cuda-toolkit to 11.5.1 or later

Control: reopen -1 Control: reassign -1 src:bart-cuda 0.7.00-5 Control: affects -1 = Control: retitle -1 bart-cuda: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value' Control: tag -1 + patch CUDA 11.5.2 is now in sid (and 11.6.0 in experimental), but bart-cuda

Bug#1020218: marked as done (vcmi: luajit got removed on ppc64el, please either drop vcmi on ppc64el or switch to lua)

Your message dated Mon, 26 Sep 2022 21:01:49 +0200 with message-id <20220926190149.4ocombohjdb64...@sk2.org> and subject line Re: Bug#1020218: vcmi: luajit got removed on ppc64el, please either drop vcmi on ppc64el or switch to lua has caused the Debian Bug report #1020218, regarding vcmi: luajit

Processed: Re: pyhst2: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value'

Processing control commands: > tag -1 + patch Bug #1016633 [src:pyhst2] pyhst2: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value' Added tag(s) patch. -- 1016633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016633 Debian Bug Tracking System Contact

Bug#1016633: pyhst2: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value'

Control: tag -1 + patch On Thu, 4 Aug 2022 11:57:15 +0100 Neil Williams wrote: I note that the path reported is c++/10/ and there were issues with nvidia-cuda-toolkit and g++-11 in other packages. gcc-defaults now points at g++-12 AFAIK, CUDA (even the unpackaged versions) do not yet support

Bug#1020788: dh-raku: Failed to create directory '/sbuild-nonexistent/.raku/short'

Package: dh-raku Version: 0.13 Severity: serious Tags: ftbfs Control: affects -1 src:raku-getopt-long src:raku-log src:raku-tap-harness src:raku-librarycheck src:raku-file-find https://buildd.debian.org/status/logs.php?pkg=raku-getopt-long=0.3.3-2%2Bb3

Processed: dh-raku: Failed to create directory '/sbuild-nonexistent/.raku/short'

Processing control commands: > affects -1 src:raku-getopt-long src:raku-log src:raku-tap-harness > src:raku-librarycheck src:raku-file-find Bug #1020788 [dh-raku] dh-raku: Failed to create directory '/sbuild-nonexistent/.raku/short' Added indication that 1020788 affects src:raku-getopt-long,

Bug#1019694: pikepdf: FTBFS with qpdf 11.0.0

Hello, On Sun 25 Sep 2022 at 10:32PM -07, James Barlow wrote: > Upgrading to pikepdf 6.0.2 will resolve this issue. pikepdf 5 is not > compatible > with qpdf 11. Thanks for confirming. I prepared the update in git some weeks ago, but I'm blocked on uploading on someone packaging

Bug#1012250: Fixing CI bugs for a package on the REJECT list

Hi Jeff, On 26-09-2022 12:53, Jeff wrote: Short of closing #1012250, how do I get CI pipeline to pick up gscan2pdf again to debug the flaky tests? I'd appreciate any pointers. The bug has a user specified for the usertag and explicitly mentions: """ Don't hesitate to reach out if you need

Processed: [bts-link] source package src:bats

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:bats > # 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

Processed: [bts-link] source package doxygen

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package doxygen > # 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

Bug#1020714: cryptsetup: cryptroot-* autopkgtests fall-back to shell and hang on errors

Hi Guilhem, On 26-09-2022 16:58, Guilhem Moulin wrote: This is pretty bad for our infrastructure as normally your test is much faster and it shouldn't wait for the time out. Can you please fix that? Very sorry for that! Don't worry too much, those things happen. It's the fast response I

Bug#1020776: qemu-system-data in bullseye-backports is too old

On 26 Sep 2022 14:39:55 Justin Ossevoort wrote: > Package: qemu-system-data > > The latest packages in Debian Bullseye Backports depend on > >qemu-system-data (>> 1:7.1+dfsg~) > > But the current version in the Debian APT archives (and according to >

Bug#1020782: Removal notice: obsolete

Source: haskell-hashmap Version: 1.3.3-3 Severity: serious I intend to remove this package: * It has no rev dependencies * Deprecated in favor of unordered-containers If you believe we should keep this package in Debian, please close this bug report. -- Ilias

Bug#1020088: marked as done (xr-hardware: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2)

Your message dated Mon, 26 Sep 2022 15:11:25 + with message-id and subject line Bug#1020088: fixed in xr-hardware 1.1.0-1 has caused the Debian Bug report #1020088, regarding xr-hardware: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2 to be marked as done. This means that

Bug#1020779: slic3r-prusa: FTBFS on 32-bit arches

Source: slic3r-prusa Version: 2.5.0+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, slic3r-prusa 2.5.0+dfsg-1 FTBFS on 32-bit arches (armhf, i386, mipsel). Log snippet: Run Build Command(s):/usr/bin/gmake -f

Bug#1020103: marked as done (prosody: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)

Your message dated Mon, 26 Sep 2022 15:08:13 + with message-id and subject line Bug#1020103: fixed in prosody 0.12.1-2 has caused the Debian Bug report #1020103, regarding prosody: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 to be

Processed: Re: Bug#1020714: cryptsetup: cryptroot-* autopkgtests fall-back to shell and hang on errors

Processing control commands: > tag -1 pending Bug #1020714 [src:cryptsetup] cryptsetup: cryptroot-* autopkgtests fall-back to shell and hang on errors Added tag(s) pending. -- 1020714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020714 Debian Bug Tracking System Contact

Processed: Forwarding bitrotted Apertium pairs

Processing commands for cont...@bugs.debian.org: > forwarded 1016338 https://github.com/apertium/organisation/issues/32 Bug #1016338 [src:apertium-fra-frp] apertium-fra-frp: FTBFS: make[2]: *** [Makefile:885: fra-frp.t1x.bin] Error 1 Set Bug forwarded-to-address to

Bug#1020714: cryptsetup: cryptroot-* autopkgtests fall-back to shell and hang on errors

Control: tag -1 pending Hi Paul, On Sun, 25 Sep 2022 at 20:09:09 +0200, Paul Gevers wrote: > However, the reason for that long run was not the failure itself, but > the fact that your tests drop to shell on error and apparently waits > for user input. One failure with 2:2.5.0-3 in unstable has

Bug#1016327: Forwarding bitrotted Apertium pairs

forwarded 1016338 https://github.com/apertium/organisation/issues/32 forwarded 1016327 https://github.com/apertium/organisation/issues/32 thanks -- Tino Didriksen OpenPGP_signature Description: OpenPGP digital signature

Bug#1020776: qemu-system-data in bullseye-backports is too old

Package: qemu-system-data Version: 1:5.2+dfsg-11+deb11u2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: deb...@internetionals.nl Dear Maintainer, The latest packages in Debian Bullseye Backports depend on qemu-system-data (>> 1:7.1+dfsg~) But the current version in

Bug#1020642: webkit2gtk: FTBFS on mipsel: virtual memory exhausted

On Mon, Sep 26, 2022 at 09:22:50AM -0400, Jeremy Bicha wrote: > On Mon, Sep 26, 2022 at 9:03 AM Adrian Bunk wrote: > > I had the worst possible outcome on the porterbox: > > The reference build succeeded unchanged. :-( > > You mean you got 2.38.0-1 to build successfully once? Yes. > I

Bug#1020642: webkit2gtk: FTBFS on mipsel: virtual memory exhausted

On Mon, Sep 26, 2022 at 9:03 AM Adrian Bunk wrote: > I had the worst possible outcome on the porterbox: > The reference build succeeded unchanged. :-( You mean you got 2.38.0-1 to build successfully once? I expected it would succeed some of the time because I don't think much changed since the

Bug#1020642: webkit2gtk: FTBFS on mipsel: virtual memory exhausted

On Mon, Sep 26, 2022 at 04:00:30PM +0300, Adrian Bunk wrote: > I had the worst possible outcome on the porterbox: > The reference build succeeded unchanged. :-( > > I'll check again if your disabling of unified builds does not work. I decided to upload 2.38.0-2 without unified builds, hopefully

Bug#1013052: marked as done (tgt: ftbfs with GCC-12)

Your message dated Mon, 26 Sep 2022 13:07:19 + with message-id and subject line Bug#1013052: fixed in tgt 1:1.0.84-1 has caused the Debian Bug report #1013052, regarding tgt: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1020642: webkit2gtk: FTBFS on mipsel: virtual memory exhausted

On Sat, Sep 24, 2022 at 09:59:15PM +, Alberto Garcia wrote: > On Sat, Sep 24, 2022 at 06:39:25PM +0100, Simon McVittie wrote: > > > webkit2gtk repeatedly failed to compile on the mipsel buildds: > > > > :

Processed: forcibly merging 1017425 1019402

Processing commands for cont...@bugs.debian.org: > forcemerge 1017425 1019402 Bug #1017425 {Done: Salvatore Bonaccorso } [src:linux] [i386] Unconditional LFENCE instructions in FILL_RETURN_BUFFER Bug #1017494 {Done: Salvatore Bonaccorso } [src:linux] [i386] Unconditional LFENCE instructions in

Bug#1020185: persists with dh-elpa 2.0.12

here's the failed build with dh-elpa 2.0.12 dh_elpa_test emacs -batch -Q -l package --eval "(setq native-compile-target-directory \"/tmp/NpGLjk7chP\")" --eval "(add-to-list 'package-directory-list \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list 'package-directory-list

Processed: cleanup dh_elpa_test bugs 1/n

Processing commands for cont...@bugs.debian.org: > reassign 1020179 dh-elpa Bug #1020179 [src:elfeed] elfeed: FTBFS: make: *** [debian/rules:4: binary] Error 25 Bug reassigned from package 'src:elfeed' to 'dh-elpa'. No longer marked as found in versions elfeed/3.4.1-1. Ignoring request to alter

Bug#1020642: webkit2gtk: FTBFS on mipsel: virtual memory exhausted

On Sun, Sep 25, 2022 at 10:03:15AM +0200, Mathieu Malaterre wrote: > On Sat, Sep 24, 2022 at 7:42 PM Simon McVittie wrote: > > webkit2gtk repeatedly failed to compile on the mipsel buildds: > > Here is the trick I used on those arches for openvdb: > > [...] > # Disable optimization on mipsel

Bug#1001262: marked as done (monado: FTBFS with glibc 2.34)

Your message dated Mon, 26 Sep 2022 08:47:20 + with message-id and subject line Bug#1001262: fixed in monado 21.0.0~dfsg1-2.1 has caused the Debian Bug report #1001262, regarding monado: FTBFS with glibc 2.34 to be marked as done. This means that you claim that the problem has been dealt

Bug#1017251: marked as done (monado: FTBFS: catch.hpp:10794:58: error: call to non-‘constexpr’ function ‘long int sysconf(int)’)

Your message dated Mon, 26 Sep 2022 08:47:20 + with message-id and subject line Bug#1001262: fixed in monado 21.0.0~dfsg1-2.1 has caused the Debian Bug report #1001262, regarding monado: FTBFS: catch.hpp:10794:58: error: call to non-‘constexpr’ function ‘long int sysconf(int)’ to be marked

Bug#1020765: Does Debian 11.x 32 bit support NVDIMM?

Package: ndctl Version: 71.1-1 Severity: serious For Debian 11.5 32 bit, I got below info: apt-cache search ndctl libndctl-dev - Development files for libndctl libndctl6 - Utility library for managing the libnvdimm subsystem ndctl - Utility for managing the nvdimm subsystem It is same to

Bug#1017175: marked as done (minicoredumper: FTBFS: daemon.c:227:9: error: ‘pthread_mutexattr_setrobust_np’ is deprecated: pthread_mutexattr_setrobust_np is deprecated, use pthread_mutexattr_setrobust

Your message dated Mon, 26 Sep 2022 07:53:17 + with message-id and subject line Bug#1017175: fixed in minicoredumper 2.0.1-1.1 has caused the Debian Bug report #1017175, regarding minicoredumper: FTBFS: daemon.c:227:9: error: ‘pthread_mutexattr_setrobust_np’ is deprecated:

Bug#1020702: prusa-slicer: SEGV on start

Control: notfound -1 2.4.2+dfsg-1 As the backtrace hinted that direction, I yesterday did a local rebuild using libwxgtk3.0-gtk3-dev: This version does NOT segfault. So I guess there is either a bug in wxwidgets 3.2, or in prusa-slicer which has been exposed with the new wxWidgets. (The

Processed: Re: prusa-slicer: SEGV on start

Processing control commands: > notfound -1 2.4.2+dfsg-1 Bug #1020702 [prusa-slicer] prusa-slicer: SEGV on start Ignoring request to alter found versions of bug #1020702 to the same values previously set -- 1020702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020702 Debian Bug Tracking

Bug#1017165: marked as done (tarantool: FTBFS: guard.cc:31:23: error: size of array ‘stack_buf’ is not an integral constant-expression)

Your message dated Mon, 26 Sep 2022 07:39:41 + with message-id and subject line Bug#1001354: fixed in tarantool 2.6.0-1.1 has caused the Debian Bug report #1001354, regarding tarantool: FTBFS: guard.cc:31:23: error: size of array ‘stack_buf’ is not an integral constant-expression to be

Bug#1001354: marked as done (tarantool: FTBFS with glibc 2.34)

Your message dated Mon, 26 Sep 2022 07:39:41 + with message-id and subject line Bug#1001354: fixed in tarantool 2.6.0-1.1 has caused the Debian Bug report #1001354, regarding tarantool: FTBFS with glibc 2.34 to be marked as done. This means that you claim that the problem has been dealt