Bug#1059829: node-html5-qrcode: Build using libraries downloaded from Internet during build

2024-01-01 Thread Yadd
On 1/2/24 09:50, Yadd wrote: Package: node-html5-qrcode Version: 2.3.8+repack-3 Severity: serious Justification: not-dfsg X-Debbugs-Cc: y...@debian.org node-html5-qrcode is built using "npm install" which downloads libraries from Internet. This is totally out of DFSG. For now, the --omit-dev

Processed: Re: subj

2024-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 846640 Bug #846640 {Done: Sylvestre Ledru } [lldb-3.8] lldb-3.8: lldb freezes after "run" Warning: Unknown package 'lldb-3.8' Unarchived Bug 846640 Warning: Unknown package 'lldb-3.8' > submitter 846640 ! Bug #846640 {Done: Sylvestre

Bug#1059829: node-html5-qrcode: Build using libraries downloaded from Internet during build

2024-01-01 Thread Yadd
Package: node-html5-qrcode Version: 2.3.8+repack-3 Severity: serious Justification: not-dfsg X-Debbugs-Cc: y...@debian.org node-html5-qrcode is built using "npm install" which downloads libraries from Internet. This is totally out of DFSG.

Processed: Re: subj

2024-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > archive 846531 Bug #846531 {Done: Sylvestre Ledru } [lldb-3.8] lldb-3.8 and lldb-3.9 are completely unusable in stretch (multiply problems); fix them or remove from scretch Warning: Unknown package 'lldb-3.8' Warning: Unknown package 'lldb-3.8'

Processed (with 1 error): Re: subj

2024-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 846531 > submitter 846531 ! Bug #846531 {Done: Sylvestre Ledru } [lldb-3.8] lldb-3.8 and lldb-3.9 are completely unusable in stretch (multiply problems); fix them or remove from scretch Warning: Unknown package 'lldb-3.8' Changed Bug

Processed (with 1 error): Re: subj

2024-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # docs say: "You should not be using unarchive to make trivial changes > to archived bugs, such as changing the submitter". But I don't care :) Unknown command or malformed arguments to command. > unarchive 846531 Bug #846531 {Done: Sylvestre

Bug#1058421: marked as done (freedombox: FTBFS: failed tests)

2024-01-01 Thread Debian Bug Tracking System
Your message dated Tue, 02 Jan 2024 02:50:53 + with message-id and subject line Bug#1058421: fixed in freedombox 24.1 has caused the Debian Bug report #1058421, regarding freedombox: FTBFS: failed tests to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1040988: fixed in picom 10.2-2

2024-01-01 Thread mu mu
On Sun, 31 Dec 2023 00:06:53 +0100 Vincent Bernat wrote: > On Tue, 26 Dec 2023 16:19:12 + Debian FTP Masters > wrote: > > >* Fix infinite loop with GNOME (Closes: #1040988) > > Upstream also added: > https://github.com/yshui/picom/commit/7366553be2b825495c5b1e09be09d0fabde4b9b4 > >

Processed: notfound 1054823 in starlette/0.31.1-1

2024-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1054823 starlette/0.31.1-1 Bug #1054823 [src:starlette] starlette: FTBFS: tests failed No longer marked as found in versions starlette/0.31.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1054823:

Bug#1058085: marked as done (multiqc: FTBFS: ModuleNotFoundError: No module named 'imp')

2024-01-01 Thread Debian Bug Tracking System
Your message dated Tue, 02 Jan 2024 00:20:33 + with message-id and subject line Bug#1058406: fixed in python-lzstring 1.0.4-3 has caused the Debian Bug report #1058406, regarding multiqc: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done. This means that you claim that

Bug#1059630: marked as done (python-sparse: FTBFS in unstable)

2024-01-01 Thread Debian Bug Tracking System
Your message dated Tue, 02 Jan 2024 00:21:00 + with message-id and subject line Bug#1059630: fixed in python-sparse 0.14.0-2 has caused the Debian Bug report #1059630, regarding python-sparse: FTBFS in unstable to be marked as done. This means that you claim that the problem has been dealt

Bug#1058406: marked as done (python-lzstring: FTBFS: ModuleNotFoundError: No module named 'imp')

2024-01-01 Thread Debian Bug Tracking System
Your message dated Tue, 02 Jan 2024 00:20:33 + with message-id and subject line Bug#1058406: fixed in python-lzstring 1.0.4-3 has caused the Debian Bug report #1058406, regarding python-lzstring: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done. This means that you

Bug#1058199: marked as done (python-mbed-host-tests: FTBFS: ModuleNotFoundError: No module named 'imp')

2024-01-01 Thread Debian Bug Tracking System
Your message dated Tue, 02 Jan 2024 00:20:41 + with message-id and subject line Bug#1058199: fixed in python-mbed-host-tests 1.4.4-9 has caused the Debian Bug report #1058199, regarding python-mbed-host-tests: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done. This

Bug#1058271: marked as done (python-schwifty: FTBFS: python3.12: can't open file '/<>/python3.11': [Errno 2] No such file or directory)

2024-01-01 Thread Debian Bug Tracking System
Your message dated Tue, 02 Jan 2024 00:20:52 + with message-id and subject line Bug#1058271: fixed in python-schwifty 2023.10.0+dfsg-1 has caused the Debian Bug report #1058271, regarding python-schwifty: FTBFS: python3.12: can't open file '/<>/python3.11': [Errno 2] No such file or

Bug#1058406: marked as done (python-lzstring: FTBFS: ModuleNotFoundError: No module named 'imp')

2024-01-01 Thread Debian Bug Tracking System
Your message dated Tue, 02 Jan 2024 00:20:33 + with message-id and subject line Bug#1058085: fixed in python-lzstring 1.0.4-3 has caused the Debian Bug report #1058085, regarding python-lzstring: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done. This means that you

Bug#1058085: marked as done (multiqc: FTBFS: ModuleNotFoundError: No module named 'imp')

2024-01-01 Thread Debian Bug Tracking System
Your message dated Tue, 02 Jan 2024 00:20:33 + with message-id and subject line Bug#1058085: fixed in python-lzstring 1.0.4-3 has caused the Debian Bug report #1058085, regarding multiqc: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done. This means that you claim that

Bug#1056481: marked as done (python-mbed-host-tests autopkg tests fail with Python 3.12)

2024-01-01 Thread Debian Bug Tracking System
Your message dated Tue, 02 Jan 2024 00:20:40 + with message-id and subject line Bug#1056481: fixed in python-mbed-host-tests 1.4.4-9 has caused the Debian Bug report #1056481, regarding python-mbed-host-tests autopkg tests fail with Python 3.12 to be marked as done. This means that you claim

Bug#1056481: marked as pending in python-mbed-host-tests

2024-01-01 Thread Alexandre Detiste
Control: tag -1 pending Hello, Bug #1056481 in python-mbed-host-tests 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#1056481 marked as pending in python-mbed-host-tests

2024-01-01 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1056481 [src:python-mbed-host-tests] python-mbed-host-tests autopkg tests fail with Python 3.12 Added tag(s) pending. -- 1056481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056481 Debian Bug Tracking System Contact

Processed: Bug#1058199 marked as pending in python-mbed-host-tests

2024-01-01 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058199 [src:python-mbed-host-tests] python-mbed-host-tests: FTBFS: ModuleNotFoundError: No module named 'imp' Added tag(s) pending. -- 1058199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058199 Debian Bug Tracking System Contact

Bug#1058199: marked as pending in python-mbed-host-tests

2024-01-01 Thread Alexandre Detiste
Control: tag -1 pending Hello, Bug #1058199 in python-mbed-host-tests 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: severity of 1059652 is normal

2024-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1059652 normal Bug #1059652 [ftp.debian.org] RM: slpvm -- RoQA; PVM no longer maintained Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1059652:

Bug#1056486: marked as done (python-mpegdash's autopkg tests fail with Python 3.12)

2024-01-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Jan 2024 22:23:41 + with message-id and subject line Bug#1056486: fixed in python-mpegdash 0.3.1-2 has caused the Debian Bug report #1056486, regarding python-mpegdash's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the

Bug#1058092: marked as done (python-mpegdash: FTBFS: ModuleNotFoundError: No module named 'imp')

2024-01-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Jan 2024 22:23:41 + with message-id and subject line Bug#1058092: fixed in python-mpegdash 0.3.1-2 has caused the Debian Bug report #1058092, regarding python-mpegdash: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done. This means that you

Bug#1059819: g2clib/experimental FTBFS: Could NOT find libaec

2024-01-01 Thread Adrian Bunk
Source: g2clib Version: 1.8.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=g2clib=1.8.0-1 ... CMake Error at /usr/share/cmake-3.28/Modules/FindPackageHandleStandardArgs.cmake:230 (message): Could NOT find libaec (missing: LIBAEC_LIBRARIES LIBAEC_INCLUDE_DIRS)

Processed: fixed 1052856 in httpcore/0.17.3-1

2024-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1052856 httpcore/0.17.3-1 Bug #1052856 {Done: Stefano Rivera } [src:httpcore] httpcore: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 Marked as fixed in versions

Bug#1052666: lvm2 FTBFS when systemd.pc changes systemdsystemunitdir

2024-01-01 Thread Helmut Grohne
On Mon, Sep 25, 2023 at 10:29:14PM +0200, Helmut Grohne wrote: > We want to change the value of systemdsystemunitdir in systemd.pc to > point below /usr. lvm2's upstream build system consumes this variable, > but its packaging hard codes the current value. Consequently, lvm2 FTBFS > when it is

Processed: Re: Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)

2024-01-01 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1055228 [src:plplot] plplot: FTBFS on armhf (test segfault) Bug #1055750 [src:plplot] gfortran: [armhf] Yield SIGBUS when compiling with -fstack-clash-protection Severity set to 'important' from 'serious' Severity set to 'important' from

Bug#1055228: Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)

2024-01-01 Thread Rafael Laboissière
Control: severity -1 important * Sebastiaan Couwenberg [2024-01-01 20:13]: plplot got removed from armhf, the severity of this issue could be lowered to important to not have the package removed from testing. Thanks, I am doing it hereby. Best, Rafael Laboissière

Bug#1059630: fix build with Python 3.12

2024-01-01 Thread Diane Trout
On Mon, 2024-01-01 at 11:22 +0100, Matthias Klose wrote: > Control: tags -1 + patch > > patch at > http://launchpadlibrarian.net/706939750/python-sparse_0.14.0-1_0.14.0-1ubuntu1.diff.gz > I think a better solution to the versioneer fail to build is to remove the embedded versioneer and use the

Bug#1059812: elan - dependency updates.

2024-01-01 Thread Peter Michael Green
Package: elan Version: 3.0.0-1 Severity: serious I just updated the rust-term package, from 0.5 to 0.7 as a result elan needs to stop patching it's cargo dependency on term and update it's Debian build-dependency. While doing test builds I noticed a couple of other dependency issues. The

Bug#1058444: marked as done (python-msrest: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-01-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Jan 2024 19:51:51 + with message-id and subject line Bug#1058444: fixed in python-msrest 0.6.21-3 has caused the Debian Bug report #1058444, regarding python-msrest: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned

Processed: Bug#1058444 marked as pending in python-msrest

2024-01-01 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058444 [src:python-msrest] python-msrest: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Added tag(s) pending. -- 1058444:

Bug#1058444: marked as pending in python-msrest

2024-01-01 Thread Luca Boccassi
Control: tag -1 pending Hello, Bug #1058444 in python-msrest 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#1056791: marked as done (azure-uamqp-python: ftbfs with cython 3.0.x)

2024-01-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Jan 2024 19:19:39 + with message-id and subject line Bug#1056791: fixed in azure-uamqp-python 1.6.5-2 has caused the Debian Bug report #1056791, regarding azure-uamqp-python: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem

Bug#1055228: Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)

2024-01-01 Thread Sebastiaan Couwenberg
plplot got removed from armhf, the severity of this issue could be lowered to important to not have the package removed from testing. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1

Bug#1059431: marked as done (linux: FTBFS on mips64el: make[3]: *** [/<>/Makefile:246: __sub-make] Error 2)

2024-01-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Jan 2024 19:02:08 + with message-id and subject line Bug#1059431: fixed in linux 6.6.9-1 has caused the Debian Bug report #1059431, regarding linux: FTBFS on mips64el: make[3]: *** [/<>/Makefile:246: __sub-make] Error 2 to be marked as done. This means that you

Bug#1056791: marked as pending in azure-uamqp-python

2024-01-01 Thread Luca Boccassi
Control: tag -1 pending Hello, Bug #1056791 in azure-uamqp-python 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#1056791 marked as pending in azure-uamqp-python

2024-01-01 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1056791 [src:azure-uamqp-python] azure-uamqp-python: ftbfs with cython 3.0.x Added tag(s) pending. -- 1056791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: tagging 1059349

2024-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1059349 + ftbfs Bug #1059349 [src:deal.ii] deal.ii ftbfs on ppc64el (with boost1.83) Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1059349:

Bug#1058167: marked as done (mat2: FTBFS: AssertionError: 'VideoFullRangeFlag' not found in {'AverageBitrate': 465641, 'BufferSize': 0, 'ColorPrimaries': 'BT.709', 'ColorProfiles': 'nclx', 'ColorRepre

2024-01-01 Thread Debian Bug Tracking System
Your message dated Mon, 1 Jan 2024 18:28:36 +0100 with message-id <75b1faf9-b7dd-4472-b2e3-9bc8340a6...@debian.org> and subject line Re: mat2: test failure has caused the Debian Bug report #1058167, regarding mat2: FTBFS: AssertionError: 'VideoFullRangeFlag' not found in {'AverageBitrate':

Bug#1059802: troffcvt: Broken with groff 1.23.0: .de1 etc. unimplemented

2024-01-01 Thread Colin Watson
Package: troffcvt Version: 1.04+repack1-1 Severity: grave Justification: renders package unusable groff 1.23.0 makes more use of the .de1 request (and probably others) than previous versions did. This causes troffcvt to be unable to even format its own documentation, with this error:

Bug#1057573: linpac: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’}

2024-01-01 Thread Dave Hibberd
Hi there! Yeah I’ve pushed his patch already to our git, so if anyone else on the team wants to upload it they can - I am still waiting on our account managers to finalise my Debian developer application before I have free reign to upload things, and I’ll switch this package to fall under my

Bug#1057573: linpac: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’}

2024-01-01 Thread David Ranch
Hello DaveH, I have pushed the required fixes to the develop branch of Linpac. I do plan on adding some other enhancements to Linpac before publishing an new official release but I don't know if getting out this fix is important to the Debian release process. Maybe the similar third party

Bug#1056594: marked as done (mat2: test failure)

2024-01-01 Thread Debian Bug Tracking System
Your message dated Mon, 1 Jan 2024 17:11:57 +0100 with message-id and subject line Re: mat2: test failure has caused the Debian Bug report #1056594, regarding mat2: test failure 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

Bug#1059777: marked as done (rust-signature: Fails to build from source)

2024-01-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Jan 2024 16:09:08 + with message-id and subject line Bug#1059777: fixed in rust-signature 2.2.0+ds-2 has caused the Debian Bug report #1059777, regarding rust-signature: Fails to build from source to be marked as done. This means that you claim that the problem has

Bug#1058129: marked as done (python-scruffy: FTBFS: ModuleNotFoundError: No module named 'imp')

2024-01-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Jan 2024 16:08:04 + with message-id and subject line Bug#1058129: fixed in python-scruffy 0.3.8.2-1 has caused the Debian Bug report #1058129, regarding python-scruffy: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done. This means that you

Bug#1059772: marked as done (fp-utils-3.2.2 has an undeclared file conflict on /usr/bin/fp-fix-timestamps)

2024-01-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Jan 2024 15:29:03 + with message-id and subject line Bug#1059772: fixed in fpc 3.2.2+dfsg-28 has caused the Debian Bug report #1059772, regarding fp-utils-3.2.2 has an undeclared file conflict on /usr/bin/fp-fix-timestamps to be marked as done. This means that you

Bug#1059799: obs-studio FTBFS: tests fail to link

2024-01-01 Thread Adrian Bunk
Source: obs-studio Version: 30.0.2+dfsg-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=obs-studio=30.0.2%2Bdfsg-1 ... FAILED: test/cmocka/test_serializer : && /usr/bin/cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat

Bug#1059136: marked as done (ecflow: FTBFS on armel and armhf)

2024-01-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Jan 2024 15:24:17 + with message-id and subject line Bug#1059136: fixed in ecflow 5.11.4-2 has caused the Debian Bug report #1059136, regarding ecflow: FTBFS on armel and armhf to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: [python3-diagrams] Bug #1057174: forward to upstream issue

2024-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1057174 https://github.com/mingrammer/diagrams/issues/832 Bug #1057174 [python3-diagrams] python3-diagrams: depends on no longer available python3-typed-ast Set Bug forwarded-to-address to

Bug#1055547: marked as done (urwid fails one test with Python 3.12)

2024-01-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Jan 2024 14:12:46 + with message-id and subject line Bug#1055547: fixed in urwid 2.1.2-4.1 has caused the Debian Bug report #1055547, regarding urwid fails one test with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt

Bug#1056594: mat2: test failure

2024-01-01 Thread gregor herrmann
On Mon, 01 Jan 2024 09:50:42 +0100, Paul Gevers wrote: > On Thu, 23 Nov 2023 18:03:45 +0100 gregor herrmann > wrote: > > I've locally added upstream commit > > https://0xacab.org/jvoisin/mat2/-/commit/bbd5b2817c9d64013e2f5ed670aca8d4738bb484 > > as a quilt patch, and the tests pass both during

Processed: Bug#1055547 marked as pending in urwid

2024-01-01 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1055547 [src:urwid] urwid fails one test with Python 3.12 Added tag(s) pending. -- 1055547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1055547: marked as pending in urwid

2024-01-01 Thread Matthias Klose
Control: tag -1 pending Hello, Bug #1055547 in urwid 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 (with 1 error): xfce4-panel-profiles: python3-psutil does not get pulled in when installing xfce4-panel-profiles

2024-01-01 Thread Debian Bug Tracking System
Processing control commands: > severity -1 grave Bug #1056704 [xfce4-panel-profiles] xfce4-panel-profiles: python3-psutil does not get pulled in when installing xfce4-panel-profiles Severity set to 'grave' from 'important' > tags patch Unknown command or malformed arguments to command. --

Bug#1059772: marked as done (fp-utils-3.2.2 has an undeclared file conflict on /usr/bin/fp-fix-timestamps)

2024-01-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Jan 2024 12:36:45 + with message-id and subject line Bug#1059772: fixed in fpc 3.2.2+dfsg-28~1 has caused the Debian Bug report #1059772, regarding fp-utils-3.2.2 has an undeclared file conflict on /usr/bin/fp-fix-timestamps to be marked as done. This means that

Bug#1055488: please build for all supported Python3 versions

2024-01-01 Thread Matthias Klose
Control: reopen -1 Control: severity -1 important with the recent upload to only build for the default Python3 version, at least the build of the package onboard fails, because it tries to build for all supported Python3 versions. Please also build pycairo for all supported Python versions,

Processed: please build for all supported Python3 versions

2024-01-01 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1055488 {Done: Jeremy Bícha } [src:pycairo] pycairo b-d on python3-all-dev, but only builds for the default python '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

Processed: Re: Bug#1053825: Screensaver with only blank does not work after suspend

2024-01-01 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #1053825 [src:linux] Screensaver with only blank does not work after suspend Severity set to 'normal' from 'serious' -- 1053825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053825 Debian Bug Tracking System Contact

Bug#1053825: Screensaver with only blank does not work after suspend

2024-01-01 Thread Bastian Blank
Control: severity -1 normal Hi Klaus On Thu, Oct 12, 2023 at 06:57:20AM +0100, Klaus Ethgen wrote: > -- System Information: > Debian Release: trixie/sid > merged-usr: no I just realized that this system is in an unsupported state. Bookworm and later is not longer supported without merged-/usr,

Bug#1058369: marked as done (python-ruyaml: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-01-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Jan 2024 11:51:46 + with message-id and subject line Bug#1058369: fixed in python-ruyaml 0.91.0-3 has caused the Debian Bug report #1058369, regarding python-ruyaml: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned

Bug#1042677: marked as done (flask-security: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:25: override_dh_sphinxdoc] Error 2)

2024-01-01 Thread Debian Bug Tracking System
Your message dated Mon, 1 Jan 2024 12:38:05 +0100 with message-id and subject line Re: Bug#1042677: flask-security: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:25: override_dh_sphinxdoc] Error 2 has caused the Debian Bug report #1042677, regarding flask-security: FTBFS with

Processed: reassign 1059652 to ftp.debian.org, retitle 1059652 to RM: slpvm -- RoQA; PVM no longer maintained

2024-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1059652 ftp.debian.org Bug #1059652 [src:slpvm] Proposed-RM: slpvm -- RoQA; PVM no longer maintained Bug reassigned from package 'src:slpvm' to 'ftp.debian.org'. No longer marked as found in versions slpvm/0.1.5-17. Ignoring request to

Bug#1057693: valgrind: i386 vex x86->IR: unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26

2024-01-01 Thread Simon Josefsson
Sam James writes: > Thanks, I've reported this on the Valgrind bugzilla at > https://bugs.kde.org/show_bug.cgi?id=478624. Thank you for reporting this! Upstream has fixed it: https://sourceware.org/git/?p=valgrind.git;a=commitdiff;h=d35005cef8ad8207542738812705ceabf137d7e0 It would be nice

Processed: closing 1056820

2024-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1056820 3.1.5-2 Bug #1056820 [src:mpi4py] mpi4py: ftbfs with cython 3.0.x Marked as fixed in versions mpi4py/3.1.5-2. Bug #1056820 [src:mpi4py] mpi4py: ftbfs with cython 3.0.x Marked Bug as done > thanks Stopping processing here. Please

Bug#1053825: Screensaver with only blank does not work after suspend

2024-01-01 Thread Klaus Ethgen
Hi Salvatore, Thanks for helping keeping the bug alive. Am Mi den 27. Dez 2023 um 21:24 schrieb Salvatore Bonaccorso: > > That would take many time to recompile kernel, test it for several hours > > and try again. > > I do realize, but given we have nobody else reporting similar > behaviour we

Processed: Re: systemtap: version 5.0-1 FTBFS on i386, ppc64el, riscv64

2024-01-01 Thread Debian Bug Tracking System
Processing control commands: > found -1 4.9-1 Bug #1057205 [systemtap] systemtap: FTBFS with g++-13 on i386, ppc64el, riscv64 Marked as found in versions systemtap/4.9-1. > severity -1 important Bug #1057205 [systemtap] systemtap: FTBFS with g++-13 on i386, ppc64el, riscv64 Severity set to

Bug#1057205: systemtap: version 5.0-1 FTBFS on i386, ppc64el, riscv64

2024-01-01 Thread Paul Gevers
Control: found -1 4.9-1 Control: severity -1 important On Fri, 1 Dec 2023 16:53:50 +0100 Emanuele Rocca wrote: Package: systemtap Version: 5.0-1 Severity: serious I have lowered the severity to enable migration, given that 5.0-2 works around the problem. The builds on r-b [1] show that

Processed: tagging 1056883

2024-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1056883 + ftbfs Bug #1056883 [src:renpy] renpy: ftbfs with cython 3.0.x Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056883

Processed: src:tracker-miners: fails to migrate to testing for too long: FTBFS

2024-01-01 Thread Debian Bug Tracking System
Processing control commands: > close -1 3.4.6-2 Bug #1059788 [src:tracker-miners] src:tracker-miners: fails to migrate to testing for too long: FTBFS Marked as fixed in versions tracker-miners/3.4.6-2. Bug #1059788 [src:tracker-miners] src:tracker-miners: fails to migrate to testing for too

Bug#1059788: src:tracker-miners: fails to migrate to testing for too long: FTBFS

2024-01-01 Thread Paul Gevers
Source: tracker-miners Version: 3.4.6-1 Severity: serious Control: close -1 3.4.6-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1057617 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and

Processed: src:xfce4-power-manager: fails to migrate to testing for too long: uploader built arch:all binaries

2024-01-01 Thread Debian Bug Tracking System
Processing control commands: > close -1 4.18.3-1 Bug #1059787 [src:xfce4-power-manager] src:xfce4-power-manager: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions xfce4-power-manager/4.18.3-1. Bug #1059787 [src:xfce4-power-manager]

Bug#1059787: src:xfce4-power-manager: fails to migrate to testing for too long: uploader built arch:all binaries

2024-01-01 Thread Paul Gevers
Source: xfce4-power-manager Version: 4.18.2-1 Severity: serious Control: close -1 4.18.3-1 Tags: sid trixie 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

Processed: fix build with Python 3.12

2024-01-01 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1059630 [python3-sparse] python-sparse: FTBFS in unstable Added tag(s) patch. -- 1059630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1059630: fix build with Python 3.12

2024-01-01 Thread Matthias Klose
Control: tags -1 + patch patch at http://launchpadlibrarian.net/706939750/python-sparse_0.14.0-1_0.14.0-1ubuntu1.diff.gz

Processed: Re: mat2: test failure

2024-01-01 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #1056594 [src:mat2] mat2: test failure Added tag(s) pending. -- 1056594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1056594: mat2: test failure

2024-01-01 Thread Paul Gevers
Control: tags -1 pending On 01-01-2024 09:50, Paul Gevers wrote: I'm going to NMU with this patch shortly. @gregor, any reason why you didn't the upload to DELAYED after you built it already? I have uploaded the attached changes. Paul diff --git a/debian/changelog b/debian/changelog index

Bug#1056594: mat2: test failure

2024-01-01 Thread Paul Gevers
Dear all, On Thu, 23 Nov 2023 18:03:45 +0100 gregor herrmann wrote: Currently mat2's test suite fails, maybe due to newer libimage-exiftool-perl releases. This can be seen on ci.debian.net, but the same failures occur during the build tests, so the package FTBFS. I've locally added upstream

Bug#1058181: marked as done (exabgp: FTBFS: ModuleNotFoundError: No module named 'exabgp.vendoring.six.moves')

2024-01-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Jan 2024 08:49:04 + with message-id and subject line Bug#1058181: fixed in exabgp 4.2.21-2 has caused the Debian Bug report #1058181, regarding exabgp: FTBFS: ModuleNotFoundError: No module named 'exabgp.vendoring.six.moves' to be marked as done. This means that

Processed: benchmark breaks ABI without SONAME bump

2024-01-01 Thread Debian Bug Tracking System
Processing control commands: > found -1 benchmark/1.8.3-1 Bug #1059785 [src:benchmark] benchmark breaks ABI without SONAME bump Marked as found in versions benchmark/1.8.3-1. -- 1059785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059785 Debian Bug Tracking System Contact

Bug#1059785: benchmark breaks ABI without SONAME bump

2024-01-01 Thread Paul Gevers
Source: benchmark Control: found -1 benchmark/1.8.3-1 Severity: serious Tags: sid trixie Dear maintainer(s), With a recent upload of benchmark the autopkgtest of pytorch fails in testing when that autopkgtest is run with the binary packages of benchmark from unstable. It passes when run with