Processed: block 1012895 with 1015925

Processing commands for cont...@bugs.debian.org: > block 1012895 with 1015925 Bug #1012895 [src:aptitude] aptitude: ftbfs with GCC-12 1012895 was not blocked by any bugs. 1012895 was not blocking any bugs. Added blocking bug(s) of 1012895: 1015925 > thanks Stopping processing here. Please

Bug#1016625: bart-cuda: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value'

Source: bart-cuda Version: 0.7.00-5 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, bart-cuda recently started to FTBFS in sid, while it still succeeds in testing. /usr//bin/nvcc -DUSE_CUDA -Xcompiler -fPIC -Xcompiler -fopenmp -O3 -I/build/bart-cuda-0.7.00/src/

Processed: nvidia-graphics-drivers: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615

Processing control commands: > clone -1 -2 -3 -4 -5 -6 -7 -8 Bug #1016614 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615 Bug 1016614 cloned as bugs 1016615-1016621 > reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Bug #1016615

Bug#1016614: nvidia-graphics-drivers: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615

Source: nvidia-graphics-drivers Severity: serious Tags: security upstream Control: clone -1 -2 -3 -4 -5 -6 -7 -8 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615 Control:

Bug#1016613: unhide-gui: missing Breaks+Replaces: unhide (<< 20210124-3)

Package: unhide-gui Version: 20210124-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite

Bug#1016603: marked as done (src:rust-onig: fails to migrate to testing for too long: autopkgtest regression)

Your message dated Thu, 04 Aug 2022 00:49:17 + with message-id and subject line Bug#1016603: fixed in rust-onig 6.3.2-1 has caused the Debian Bug report #1016603, regarding src:rust-onig: fails to migrate to testing for too long: autopkgtest regression to be marked as done. This means that

Processed: Bug#1016565 marked as pending in librecast

Processing control commands: > tag -1 pending Bug #1016565 [liblibrecast0.5] liblibrecast0.5: Missing Breaks+Replaces headers against liblibrecast0.4: trying to overwrite '/usr/share/man/man3/lc_ctx_new.3.gz', which is also in package liblibrecast0.4:amd64 0.4.5-1 Added tag(s) pending. --

Bug#1016565: marked as pending in librecast

Control: tag -1 pending Hello, Bug #1016565 in librecast reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1016396: marked as done (squeekboard: fails to build on ppc64el)

Your message dated Wed, 03 Aug 2022 23:34:27 + with message-id and subject line Bug#1016396: fixed in squeekboard 1.19.0-2 has caused the Debian Bug report #1016396, regarding squeekboard: fails to build on ppc64el to be marked as done. This means that you claim that the problem has been

Bug#1012915: marked as done (dustmite: ftbfs with GCC-12)

Your message dated Wed, 03 Aug 2022 23:18:52 + with message-id and subject line Bug#1012915: fixed in dustmite 0.0.430-2 has caused the Debian Bug report #1012915, regarding dustmite: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1016396: marked as pending in squeekboard

Control: tag -1 pending Hello, Bug #1016396 in squeekboard reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1016396 marked as pending in squeekboard

Processing control commands: > tag -1 pending Bug #1016396 [src:squeekboard] squeekboard: fails to build on ppc64el Added tag(s) pending. -- 1016396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016396 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1012915: marked as done (dustmite: ftbfs with GCC-12)

Your message dated Thu, 4 Aug 2022 00:51:25 +0200 with message-id and subject line Re: dustmite: ftbfs with GCC-12 has caused the Debian Bug report #1012915, regarding dustmite: 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#1016569: marked as done (elpa-taxy-magit-section: fails to install with emacs installed)

Your message dated Wed, 03 Aug 2022 22:49:14 + with message-id and subject line Bug#1016569: fixed in taxy-magit-section-el 0.9.1-2 has caused the Debian Bug report #1016569, regarding elpa-taxy-magit-section: fails to install with emacs installed to be marked as done. This means that you

Bug#1016209: Bug stlill present in mangohud 0.6.8-1

Hello, I wanted to report that the bug is still happening in 0.6.8-1. The error is similar: glxgears: symbol lookup error: /usr/lib/x86_64-linux-gnu/mangohud/libMangoHud.so: undefined symbol:

Processed (with 2 errors): Re: [Debian-lego-team] Bug#1015260: Bug#1015260: strace's

Processing commands for cont...@bugs.debian.org: > * Nicolas Schodet [2022-07-22 18:24]: Unknown command or malformed arguments to command. > > Are you sure you have set up nqc to connect using USB? Unknown command or malformed arguments to command. > severity 1015260 normal Bug #1015260 [nqc]

Bug#1016498: marked as done (rope: autopkgtest regression: No module named 'pkg_resources')

Your message dated Wed, 03 Aug 2022 21:54:24 + with message-id and subject line Bug#1016498: fixed in rope 1.2.0-2 has caused the Debian Bug report #1016498, regarding rope: autopkgtest regression: No module named 'pkg_resources' to be marked as done. This means that you claim that the

Bug#1016337: marked as done (libgnatcoll-bindings: FTBFS: gprconfig: can't find a native toolchain for language 'C')

Your message dated Wed, 03 Aug 2022 21:20:32 + with message-id and subject line Bug#1016337: fixed in libgnatcoll-bindings 22.0.0-4 has caused the Debian Bug report #1016337, regarding libgnatcoll-bindings: FTBFS: gprconfig: can't find a native toolchain for language 'C' to be marked as

Processed: python2.7 removal in bookworm

Processing commands for cont...@bugs.debian.org: > severity 936507 serious Bug #936507 [src:fbpanel] fbpanel: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 1011132 serious Bug #1011132 [src:metakernel] metakernel: please s/python2-doc/python3-doc/ Severity set

Bug#1016341: marked as done (libncursesada: FTBFS: gprconfig: can't find a native toolchain for language 'C')

Your message dated Wed, 03 Aug 2022 21:04:15 + with message-id and subject line Bug#1016341: fixed in libncursesada 6.3.20211021-4 has caused the Debian Bug report #1016341, regarding libncursesada: FTBFS: gprconfig: can't find a native toolchain for language 'C' to be marked as done. This

Bug#937085: [Pkg-mozext-maintainers] Bug#937085: mozilla-devscripts: Python2 removal in sid/bullseye

Hi, On 01-08-2022 21:36, Paul Gevers wrote: On Wed, 27 Jul 2022 10:37:25 +0200 =?UTF-8?Q?H=c3=a5vard_F=2e_Aasen?= wrote: I have continued working on the redland-bindings package, cleaned it up a bit, and enabled the Python 3 testsuite. I created an MR [1]. I believe redland-bindings is ready

Processed: tagging 1012914

Processing commands for cont...@bugs.debian.org: > tags 1012914 + ftbfs Bug #1012914 [src:dub] dub: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012914 Debian Bug

Processed: tagging 1013043

Processing commands for cont...@bugs.debian.org: > tags 1013043 + ftbfs Bug #1013043 [src:stressapptest] stressapptest: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013043:

Processed: tagging 1012893

Processing commands for cont...@bugs.debian.org: > tags 1012893 + ftbfs Bug #1012893 [src:anfo] anfo: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012893 Debian

Processed: tagging 1012902

Processing commands for cont...@bugs.debian.org: > tags 1012902 + ftbfs Bug #1012902 [src:centreon-clib] centreon-clib: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012902:

Processed: tagging 1012887

Processing commands for cont...@bugs.debian.org: > tags 1012887 + ftbfs Bug #1012887 [src:aces3] aces3: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012887 Debian

Processed: tagging 1013071

Processing commands for cont...@bugs.debian.org: > tags 1013071 + ftbfs Bug #1013071 [src:xstow] xstow: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013071 Debian

Processed: tagging 1013007

Processing commands for cont...@bugs.debian.org: > tags 1013007 + ftbfs Bug #1013007 [src:oomd] oomd: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013007 Debian

Processed: tagging 1013047

Processing commands for cont...@bugs.debian.org: > tags 1013047 + ftbfs Bug #1013047 [src:target-factory] target-factory: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013047:

Processed: tagging 1012975

Processing commands for cont...@bugs.debian.org: > tags 1012975 + ftbfs Bug #1012975 [src:libcypher-parser] libcypher-parser: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012975:

Processed: tagging 1012993

Processing commands for cont...@bugs.debian.org: > tags 1012993 + ftbfs Bug #1012993 [src:lomiri-thumbnailer] lomiri-thumbnailer: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012993:

Processed: tagging 1012988

Processing commands for cont...@bugs.debian.org: > tags 1012988 + ftbfs Bug #1012988 [src:librg-blast-parser-perl] librg-blast-parser-perl: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012988:

Processed: tagging 1013063

Processing commands for cont...@bugs.debian.org: > tags 1013063 + ftbfs Bug #1013063 [src:w1retap] w1retap: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013063

Processed: tagging 1012888

Processing commands for cont...@bugs.debian.org: > tags 1012888 + ftbfs Bug #1012888 [src:acm] acm: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012888 Debian Bug

Processed: tagging 1012889

Processing commands for cont...@bugs.debian.org: > tags 1012889 + ftbfs Bug #1012889 [src:afnix] afnix: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012889 Debian

Processed: tagging 1013039

Processing commands for cont...@bugs.debian.org: > tags 1013039 + ftbfs Bug #1013039 [src:skypat] skypat: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013039

Processed: tagging 1012918

Processing commands for cont...@bugs.debian.org: > tags 1012918 + ftbfs Bug #1012918 [src:edb-debugger] edb-debugger: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012918:

Processed: tagging 1012909

Processing commands for cont...@bugs.debian.org: > tags 1012909 + ftbfs Bug #1012909 [src:darkradiant] darkradiant: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012909:

Processed: tagging 1013060

Processing commands for cont...@bugs.debian.org: > tags 1013060 + ftbfs Bug #1013060 [src:veyon] veyon: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013060 Debian

Processed: tagging 1012915

Processing commands for cont...@bugs.debian.org: > tags 1012915 + ftbfs Bug #1012915 [src:dustmite] dustmite: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012915

Processed: tagging 1013062

Processing commands for cont...@bugs.debian.org: > tags 1013062 + ftbfs Bug #1013062 [src:visualboyadvance] visualboyadvance: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013062:

Processed: tagging 1012912

Processing commands for cont...@bugs.debian.org: > tags 1012912 + ftbfs Bug #1012912 [src:diagnostics] diagnostics: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012912:

Processed: tagging 1013061

Processing commands for cont...@bugs.debian.org: > tags 1013061 + ftbfs Bug #1013061 [src:vg] vg: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013061 Debian Bug

Processed: tagging 1013040

Processing commands for cont...@bugs.debian.org: > tags 1013040 + ftbfs Bug #1013040 [src:sleef] sleef: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013040 Debian

Processed: tagging 1013066

Processing commands for cont...@bugs.debian.org: > tags 1013066 + ftbfs Bug #1013066 [src:widelands] widelands: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013066:

Processed: src:rust-onig: fails to migrate to testing for too long: autopkgtest regression

Processing control commands: > close -1 6.3.1-1 Bug #1016603 [src:rust-onig] src:rust-onig: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions rust-onig/6.3.1-1. Bug #1016603 [src:rust-onig] src:rust-onig: fails to migrate to testing for too long:

Bug#1016603: src:rust-onig: fails to migrate to testing for too long: autopkgtest regression

Source: rust-onig Version: 6.1.0-1 Severity: serious Control: close -1 6.3.1-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days

Processed: python-mne: vtk[6,7] removal

Processing control commands: > block 1016597 by -1 Bug #1016597 [src:vtk7] vtk7: do not release with bookworm 1016597 was blocked by: 1013190 1016598 1016601 1013153 1016599 1013157 1013156 1013158 1016600 1016597 was not blocking any bugs. Added blocking bug(s) of 1016597: 1016602 -- 1016597:

Bug#1016602: python-mne: vtk[6,7] removal

Source: python-mne Version: 0.23.4+dfsg-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org Tags: sid bookworm Control: block 1016597 by -1 User: gl...@debian.org Usertags: vtk6_vtk7_removal Based on #1013156 and similar bugs: Dear maintainer, Debian archive has now three major versions of

Processed: vistrails: vtk[6,7] removal

Processing control commands: > block 1016597 by -1 Bug #1016597 [src:vtk7] vtk7: do not release with bookworm 1016597 was blocked by: 1016599 1013157 1016600 1016598 1013153 1013190 1013158 1013156 1016597 was not blocking any bugs. Added blocking bug(s) of 1016597: 1016601 -- 1016597:

Bug#1016601: vistrails: vtk[6,7] removal

Source: vistrails Version: 3.0~git+9dc22bd-3 Severity: serious X-Debbugs-Cc: sramac...@debian.org Tags: sid bookworm Control: block 1016597 by -1 User: gl...@debian.org Usertags: vtk6_vtk7_removal Based on #1013156 and similar bugs: Dear maintainer, Debian archive has now three major versions

Processed: siconos: vtk[6,7] removal

Processing control commands: > block 1016597 by -1 Bug #1016597 [src:vtk7] vtk7: do not release with bookworm 1016597 was blocked by: 1013153 1013190 1013158 1016599 1013156 1016598 1013157 1016597 was not blocking any bugs. Added blocking bug(s) of 1016597: 1016600 -- 1016597:

Bug#1016600: siconos: vtk[6,7] removal

Source: siconos Version: 4.3.1+dfsg-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org Tags: sid bookworm Control: block 1016597 by -1 User: gl...@debian.org Usertags: vtk6_vtk7_removal Based on #1013156 and similar bugs: Dear maintainer, Debian archive has now three major versions of the

Bug#1016599: mayavi2: vtk[6,7] removal

Source: mayavi2 Version: 4.8.0-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org Tags: sid bookworm Control: block 1016597 by -1 User: gl...@debian.org Usertags: vtk6_vtk7_removal Based on #1013156 and similar bugs: Dear maintainer, Debian archive has now three major versions of the VTK

Processed: mayavi2: vtk[6,7] removal

Processing control commands: > block 1016597 by -1 Bug #1016597 [src:vtk7] vtk7: do not release with bookworm 1016597 was blocked by: 1013190 1016598 1013156 1013157 1013153 1013158 1016597 was not blocking any bugs. Added blocking bug(s) of 1016597: 1016599 -- 1016597:

Bug#1011888: marked as done (python-libzim: FTBFS: FAILED tests/test_libzim_creator.py::test_creator_metadata - RuntimeError: Im...)

Your message dated Wed, 03 Aug 2022 20:38:51 + with message-id and subject line Bug#1011888: fixed in python-libzim 1.1.1+ds-1 has caused the Debian Bug report #1011888, regarding python-libzim: FTBFS: FAILED tests/test_libzim_creator.py::test_creator_metadata - RuntimeError: Im... to be

Bug#1016318: marked as done (libtexttools: FTBFS: gprconfig: can't find a native toolchain for language 'C')

Your message dated Wed, 03 Aug 2022 20:37:43 + with message-id and subject line Bug#1016318: fixed in libtexttools 2.1.0-22 has caused the Debian Bug report #1016318, regarding libtexttools: FTBFS: gprconfig: can't find a native toolchain for language 'C' to be marked as done. This means

Bug#1016598: binoculars: vtk[6,7] removal

Source: binoculars Version: 0.0.11-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org Tags: sid bookworm Control: block 1016597 by -1 User: gl...@debian.org Usertags: vtk6_vtk7_removal Based on #1013156 and similar bugs: Dear maintainer, Debian archive has now three major versions of the

Processed: binoculars: vtk[6,7] removal

Processing control commands: > block 1016597 by -1 Bug #1016597 [src:vtk7] vtk7: do not release with bookworm 1016597 was blocked by: 1013190 1013158 1013153 1013156 1013157 1016597 was not blocking any bugs. Added blocking bug(s) of 1016597: 1016598 -- 1016597:

Bug#1004612: marked as done (kodi: FTBFS with ffmpeg 5.0)

Your message dated Wed, 03 Aug 2022 20:37:30 + with message-id and subject line Bug#1004612: fixed in kodi 2:20.0~alpha2+dfsg1-1 has caused the Debian Bug report #1004612, regarding kodi: FTBFS with ffmpeg 5.0 to be marked as done. This means that you claim that the problem has been dealt

Processed: vtk7: do not release with bookworm

Processing control commands: > block -1 by 1013153 1013158 1013156 1013157 1013190 Bug #1016597 [src:vtk7] vtk7: do not release with bookworm 1016597 was not blocked by any bugs. 1016597 was not blocking any bugs. Added blocking bug(s) of 1016597: 1013157, 1013158, 1013156, 1013153, and 1013190

Bug#1016597: vtk7: do not release with bookworm

Source: vtk7 Version: 7.1.1+dfsg2-10.1 Severity: serious Tags: sid bookworm Control: block -1 by 1013153 1013158 1013156 1013157 1013190 X-Debbugs-Cc: sramac...@debian.org Bugs have been filed against (some of?) the reverse dependencies. This bug is here to ensure that vtk7 is not released with

Processed: vtk7: diff for NMU version 7.1.1+dfsg2-10.2

Processing control commands: > tags 1004793 + patch Bug #1004793 [src:vtk7] vtk7: FTBFS with ffmpeg 5.0 Added tag(s) patch. > tags 1004793 + pending Bug #1004793 [src:vtk7] vtk7: FTBFS with ffmpeg 5.0 Added tag(s) pending. -- 1004793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004793

Bug#1004793: vtk7: diff for NMU version 7.1.1+dfsg2-10.2

Control: tags 1004793 + patch Control: tags 1004793 + pending Dear maintainer, I've prepared an NMU for vtk7 (versioned as 7.1.1+dfsg2-10.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru

Bug#1016251: marked as done (python-lark: FTBFS: Handler for event 'source-read' threw an exception (exception: TableProcessor.__init__() missing 1 required

Your message dated Wed, 03 Aug 2022 19:49:27 + with message-id and subject line Bug#1016251: fixed in sphinx-markdown-tables 0.0.17-1 has caused the Debian Bug report #1016251, regarding python-lark: FTBFS: Handler for event 'source-read' threw an exception (exception:

Bug#1004612: marked as pending in kodi

Control: tag -1 pending Hello, Bug #1004612 in kodi reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1004612 marked as pending in kodi

Processing control commands: > tag -1 pending Bug #1004612 [src:kodi] kodi: FTBFS with ffmpeg 5.0 Ignoring request to alter tags of bug #1004612 to the same tags previously set -- 1004612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004612 Debian Bug Tracking System Contact

Bug#1016129: ipv6toolkit does not work with libpcap > 1.8

Octavio Alvarez dixit: > On 31/07/22 14:57, Thorsten Glaser wrote: >> debdiff (±version) attached. Would you prefer for me to NMU, do a >> maintainer-agreed regular upload (as -2), or handle this yourself, >> Octavio? > > I can handle it. By the way, did the fix work for you? Yes, the debdiff I

Bug#1004612: marked as pending in kodi

Control: tag -1 pending Hello, Bug #1004612 in kodi reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1004612 marked as pending in kodi

Processing control commands: > tag -1 pending Bug #1004612 [src:kodi] kodi: FTBFS with ffmpeg 5.0 Added tag(s) pending. -- 1004612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004612 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1016363: libx11-6 1.8.1 also breaks glxinfo

On Wed, 03 Aug 2022 20:06:28 +0200, Richard B. Kreckel wrote: > So, should Debian build with --disable-thread-safety-constructor, at > least for a while? I can confirm that the following trivial change avoids the issues I'm seeing in glxinfo and xscreensaver-gl-visual: #v+ ---

Bug#1002227: Move to templexxx-xorsimd? (Was: Bug#1002227: golang-github-templexxx-xor: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/templexxx/xor returne

This bug is causing and has caused autoremovals unfortunately. Taking a look at upstream, this seems abandoned and upstream moved to xorsimd[1] instead. On brief testing, tests seem to pass for new package and botht the reverse-deps for templexxx-xor have also migrated to new package in later

Processed: bug 1016363 is forwarded to https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/157 ...

Processing commands for cont...@bugs.debian.org: > forwarded 1016363 https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/157 Bug #1016363 [libx11-6] libx11 v1.8.1 does fail in a subtle way withj modale dialogs Set Bug forwarded-to-address to

Bug#1016363: libx11-6 1.8.1 also breaks glxinfo

On Mon, 01 Aug 2022 14:57:59 +0200, Hermann Meyer wrote: > With libx11-6 1.8.1 I get: > > |glxinfo name of display: :0 glxinfo: ../nptl/pthread_mutex_lock.c:424: > __pthread_mutex_lock_full: Assertion `e != ESRCH || !robust' failed. > Abgebrochen| Same here. With xscreensaver I also see

Bug#1016363: libx11-6 1.8.1 also breaks glxinfo

Why isn't the bug being fixed? That is obviously the correct solution. On 8/3/22, Richard B. Kreckel wrote: > This is issue 157 upstream: > https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/157 > Apparently, they do not want to revert it. > > So, should Debian build with

Bug#1016363: libx11-6 1.8.1 also breaks glxinfo

This is issue 157 upstream: https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/157 Apparently, they do not want to revert it. So, should Debian build with --disable-thread-safety-constructor, at least for a while? (Remember that this bug will soon block other packages from migrating, e.g.

Bug#864423: Software RAID is not activated at boot time

On Wed, Aug 3, 2022 at 1:44 AM Chris Hofstaedtler wrote: > * Holger Wansing [220802 23:37]: > > I have merged the merge requests filed by Chris (partman-base, partman-auto, > > hw-detect, grub-installer). > > > > The packages build fine with those changings. > > And a locally built mini.iso with

Bug#1004640: marked as done (unpaper: FTBFS with ffmpeg 5.0)

Your message dated Wed, 03 Aug 2022 16:15:45 + with message-id and subject line Bug#1004640: fixed in unpaper 7.0.0-0.1 has caused the Debian Bug report #1004640, regarding unpaper: FTBFS with ffmpeg 5.0 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1012985: marked as done (libpfm4: ftbfs with GCC-12)

Your message dated Wed, 03 Aug 2022 15:21:29 + with message-id and subject line Bug#1012985: fixed in libpfm4 4.11.1+git74-g5140ce5-1 has caused the Debian Bug report #1012985, regarding libpfm4: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been

Bug#1014335: marked as done (lnav: FTBFS: 1 test fails due to quoting differences)

Your message dated Wed, 03 Aug 2022 14:35:32 + with message-id and subject line Bug#1014335: fixed in lnav 0.10.1-3 has caused the Debian Bug report #1014335, regarding lnav: FTBFS: 1 test fails due to quoting differences to be marked as done. This means that you claim that the problem has

Bug#1015042: marked as done (qepcad: FTBFS: ./source/saclib/GCSI.c:31: undefined reference to `GCM')

Your message dated Wed, 03 Aug 2022 14:36:50 + with message-id and subject line Bug#1015042: fixed in saclib 2.2.8-6 has caused the Debian Bug report #1015042, regarding qepcad: FTBFS: ./source/saclib/GCSI.c:31: undefined reference to `GCM' to be marked as done. This means that you claim

Bug#1015873: libtirpc: diff for NMU version 1.3.2-2.1

Hi, On Wed, Aug 03, 2022 at 04:17:43PM +0200, Salvatore Bonaccorso wrote: > Hi Josue, > > On Wed, Aug 03, 2022 at 07:42:33AM -0600, Josue Ortega wrote: > > On Mon, Aug 01, 2022 at 09:55:07PM +0200, Salvatore Bonaccorso wrote: > > > Control: tags 1015873 + patch > > > Control: tags 1015873 +

Bug#1015873: libtirpc: diff for NMU version 1.3.2-2.1

Hi Josue, On Wed, Aug 03, 2022 at 07:42:33AM -0600, Josue Ortega wrote: > On Mon, Aug 01, 2022 at 09:55:07PM +0200, Salvatore Bonaccorso wrote: > > Control: tags 1015873 + patch > > Control: tags 1015873 + pending > > > > > > Dear maintainer, > > > > I've prepared an NMU for libtirpc

Bug#1015873: libtirpc: diff for NMU version 1.3.2-2.1

On Mon, Aug 01, 2022 at 09:55:07PM +0200, Salvatore Bonaccorso wrote: > Control: tags 1015873 + patch > Control: tags 1015873 + pending > > > Dear maintainer, > > I've prepared an NMU for libtirpc (versioned as 1.3.2-2.1) and > uploaded it to DELAYED/5. Please feel free to tell me if I > should

Bug#1015042: qepcad: FTBFS: ./source/saclib/GCSI.c:31: undefined reference to `GCM'

Control: reassign -1 src:saclib 2.2.8-4 Control: affects -1 src:qepcad On Sat, 16 Jul 2022 15:23:42 +0200 Lucas Nussbaum wrote: Source: qepcad Version: 1.74+ds-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi,

Processed: Re: qepcad: FTBFS: ./source/saclib/GCSI.c:31: undefined reference to `GCM'

Processing control commands: > reassign -1 src:saclib 2.2.8-4 Bug #1015042 [src:qepcad] qepcad: FTBFS: ./source/saclib/GCSI.c:31: undefined reference to `GCM' Bug reassigned from package 'src:qepcad' to 'src:saclib'. No longer marked as found in versions qepcad/1.74+ds-3. Ignoring request to

Bug#1016525: marked as done (python-h5netcdf: CI tests fail with h5py 3.7.0)

Your message dated Wed, 03 Aug 2022 13:05:28 + with message-id and subject line Bug#1016525: fixed in python-h5netcdf 1.0.2-1 has caused the Debian Bug report #1016525, regarding python-h5netcdf: CI tests fail with h5py 3.7.0 to be marked as done. This means that you claim that the problem

Bug#953630: [Debichem-devel] Bug#953630: openbabel autopkg tests fail on non-amd64 architectures

Hello, IMO it is high time to revisit this issue. On 2020-03-11 14:33, Matthias Klose wrote: > openbabel autopkg tests areq quiet interesting. Working around the timeout on > arm64 hides the fact that two other tests fail on every non-amd64 > architecture. I agree that the way the autopkgtest

Processed: tagging 1014964

Processing commands for cont...@bugs.debian.org: > tags 1014964 + ftbfs Bug #1014964 [netgen] netgen: FTBFS with opencascade 7.6.2 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1014964:

Bug#1015044: Not a setuptools-scm issue?

Hi, I'm sorry, but I don't see why you think this is a problem with setuptools-scm. sshuttle's debian/rules asks setuptools-scm to generate a version file in its clean target. So setuptools-scm does so, and it doesn't look invalid. But it doesn't not correspond to the version file as shipped,

Bug#1013042: spring: ftbfs with GCC-12

Control: tags -1 pending On Fri, 17 Jun 2022 00:56:44 +0200 Reiner Herrmann wrote: > Control: tags -1 + fixed-upstream > > The build failure has been fixed upstream [0]. > The fix is already contained in the new upstream release 106.0. > > [0]

Processed: Re: spring: ftbfs with GCC-12

Processing control commands: > tags -1 pending Bug #1013042 [src:spring] spring: ftbfs with GCC-12 Added tag(s) pending. -- 1013042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1013054: marked as done (titanion: ftbfs with GCC-12)

Your message dated Wed, 03 Aug 2022 09:35:44 + with message-id and subject line Bug#1013054: fixed in titanion 0.3.dfsg1-8 has caused the Debian Bug report #1013054, regarding titanion: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1013001: marked as done (mu-cade: ftbfs with GCC-12)

Your message dated Wed, 03 Aug 2022 09:35:08 + with message-id and subject line Bug#1013001: fixed in mu-cade 0.11.dfsg1-13 has caused the Debian Bug report #1013001, regarding mu-cade: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1013055: marked as done (torus-trooper: ftbfs with GCC-12)

Your message dated Wed, 03 Aug 2022 09:20:25 + with message-id and subject line Bug#1013055: fixed in torus-trooper 0.22.dfsg1-13 has caused the Debian Bug report #1013055, regarding torus-trooper: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been

Bug#1013049: marked as done (tatan: ftbfs with GCC-12)

Your message dated Wed, 03 Aug 2022 09:19:59 + with message-id and subject line Bug#1013049: fixed in tatan 1.0.dfsg2-1 has caused the Debian Bug report #1013049, regarding tatan: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1013016: marked as done (projectl: ftbfs with GCC-12)

Your message dated Wed, 03 Aug 2022 09:19:29 + with message-id and subject line Bug#1013016: fixed in projectl 1.001.dfsg2-1 has caused the Debian Bug report #1013016, regarding projectl: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1012949: marked as done (ii-esu: ftbfs with GCC-12)

Your message dated Wed, 03 Aug 2022 09:19:02 + with message-id and subject line Bug#1012949: fixed in ii-esu 1.0a.dfsg2-1 has caused the Debian Bug report #1012949, regarding ii-esu: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1013056: marked as done (tumiki-fighters: ftbfs with GCC-12)

Your message dated Wed, 03 Aug 2022 09:05:52 + with message-id and subject line Bug#1013056: fixed in tumiki-fighters 0.2.dfsg1-10 has caused the Debian Bug report #1013056, regarding tumiki-fighters: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been

Bug#1013059: marked as done (val-and-rick: ftbfs with GCC-12)

Your message dated Wed, 03 Aug 2022 09:06:00 + with message-id and subject line Bug#1013059: fixed in val-and-rick 0.1a.dfsg1-7 has caused the Debian Bug report #1013059, regarding val-and-rick: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt

  1   2   >