Processed: Bug#1061011 marked as pending in octave-zeromq

2024-01-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1061011 [src:octave-zeromq] octave-zeromq: FTBFS: make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1 Added tag(s) pending. -- 1061011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061011 Debian Bug Tracking System Contact

Bug#1061011: marked as pending in octave-zeromq

2024-01-17 Thread Rafael Laboissière
Control: tag -1 pending Hello, Bug #1061011 in octave-zeromq 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 1060775 is forwarded to https://github.com/tmux-python/tmuxp/issues/902

2024-01-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1060775 https://github.com/tmux-python/tmuxp/issues/902 Bug #1060775 [src:tmuxp] tmuxp: flaky autopkgtest: assert pane.capture_pane()[1] -> IndexError Set Bug forwarded-to-address to 'https://github.com/tmux-python/tmuxp/issues/902'.

Processed: reopening 1060775

2024-01-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 1060775 Bug #1060775 {Done: Sebastien Delafond } [src:tmuxp] tmuxp: flaky autopkgtest: assert pane.capture_pane()[1] -> IndexError Bug reopened Ignoring request to alter fixed versions of bug #1060775 to the same values previously set >

Processed: notfixed 1060775 in 1.34.0-2

2024-01-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfixed 1060775 1.34.0-2 Bug #1060775 {Done: Sebastien Delafond } [src:tmuxp] tmuxp: flaky autopkgtest: assert pane.capture_pane()[1] -> IndexError No longer marked as fixed in versions tmuxp/1.34.0-2. > thanks Stopping processing here. Please

Bug#1035389: marked as pending in ruby-aws-sdk-core

2024-01-17 Thread Vivek K J
Control: tag -1 pending Hello, Bug #1035389 in ruby-aws-sdk-core 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#1035389 marked as pending in ruby-aws-sdk-core

2024-01-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1035389 [ruby-aws-sdk-core] ruby-aws-sdk-core: The VERSION file is not packaged Added tag(s) pending. -- 1035389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035389 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1051424: marked as done (ukui-settings-daemon: broken postinst)

2024-01-17 Thread Debian Bug Tracking System
Your message dated Thu, 18 Jan 2024 07:04:12 + with message-id and subject line Bug#1051424: fixed in ukui-settings-daemon 3.22.0.0-1 has caused the Debian Bug report #1051424, regarding ukui-settings-daemon: broken postinst to be marked as done. This means that you claim that the problem

Processed: bug 1056522 is forwarded to https://github.com/Textualize/rich/issues/3261 ...

2024-01-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1056522 https://github.com/Textualize/rich/issues/3261 Bug #1056522 [src:rich] rich's autopkg tests fail with Python 3.12 Changed Bug forwarded-to-address to 'https://github.com/Textualize/rich/issues/3261' from

Bug#1057613: shed: FTBFS: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}

2024-01-17 Thread Bo YU
Source: shed Followup-For: Bug #1057613 Hi, Just fyi, MRs will fix the issue: https://salsa.debian.org/pkg-security-team/shed/-/merge_requests -- Regards, -- Bo YU signature.asc Description: PGP signature

Bug#1058317: celery: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-17 Thread Jérémy Lal
Source: celery Followup-For: Bug #1058317 Note the segmentation fault at the end of python 3.12 pytest run. Using export PYTHONFAULTHANDLER=1 before running the tests, I only got an error in garbage-collector, no trace. It is a bit like #1055717, which was closed by

Bug#1061016: marked as done (sccache: FTBFS: unsatisfiable build-dependencies)

2024-01-17 Thread Debian Bug Tracking System
Your message dated Thu, 18 Jan 2024 02:13:26 +0100 with message-id <170554040639.2588145.11758063430467644...@auryn.jones.dk> and subject line Re: Bug#1061016: sccache: FTBFS: unsatisfiable build-dependencies has caused the Debian Bug report #1061016, regarding sccache: FTBFS: unsatisfiable

Bug#1060957: marked as done (cedar-backup3: FTBFS: make: *** [debian/rules:11: binary] Error 25)

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 21:20:24 + with message-id and subject line Bug#1060957: fixed in cedar-backup3 3.8.0-1 has caused the Debian Bug report #1060957, regarding cedar-backup3: FTBFS: make: *** [debian/rules:11: binary] Error 25 to be marked as done. This means that you claim

Bug#1061041: marked as done (syncthingtray: FTBFS: make[5]: *** [connector/CMakeFiles/check.dir/build.make:73: connector/CMakeFiles/check] Error 8)

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 14:09:54 -0700 with message-id <87plxzd5ul@navis.mail-host-address-is-not-set> and subject line Re: Bug#1061041: syncthingtray: FTBFS: make[5]: *** [connector/CMakeFiles/check.dir/build.make:73: connector/CMakeFiles/check] Error 8 has caused the Debian Bug

Processed: src:path.py: fails to migrate to testing for too long: autopkgtest regression

2024-01-17 Thread Debian Bug Tracking System
Processing control commands: > close -1 16.9.0-1 Bug #1061089 [src:path.py] src:path.py: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions path.py/16.9.0-1. Bug #1061089 [src:path.py] src:path.py: fails to migrate to testing for too long: autopkgtest

Bug#1061089: src:path.py: fails to migrate to testing for too long: autopkgtest regression

2024-01-17 Thread Paul Gevers
Source: path.py Version: 16.7.1-1 Severity: serious Control: close -1 16.9.0-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 30 days as

Processed: src:python-anyio: fails to migrate to testing for too long: autopkgtest issues

2024-01-17 Thread Debian Bug Tracking System
Processing control commands: > close -1 4.1.0-1 Bug #1061088 [src:python-anyio] src:python-anyio: fails to migrate to testing for too long: autopkgtest issues Marked as fixed in versions python-anyio/4.1.0-1. Bug #1061088 [src:python-anyio] src:python-anyio: fails to migrate to testing for too

Bug#1061088: src:python-anyio: fails to migrate to testing for too long: autopkgtest issues

2024-01-17 Thread Paul Gevers
Source: python-anyio Version: 3.7.0-1 Severity: serious Control: close -1 4.1.0-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 30 days

Bug#1060993: marked as done (distro-info: FTBFS: AttributeError: module 'astroid.nodes' has no attribute 'TryExcept')

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 20:56:38 + with message-id <20240117205638.7rtexm5uyrzve...@satie.tumbleweed.org.za> and subject line Re: Bug#1060993: distro-info: FTBFS: AttributeError: module 'astroid.nodes' has no attribute 'TryExcept' has caused the Debian Bug report #1060993,

Processed: notfound 1060993 in 1.7

2024-01-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1060993 1.7 Bug #1060993 [src:distro-info] distro-info: FTBFS: AttributeError: module 'astroid.nodes' has no attribute 'TryExcept' No longer marked as found in versions distro-info/1.7. > thanks Stopping processing here. Please contact

Processed: src:bpfcc: fails to migrate to testing for too long: FTBFS on ppc64el

2024-01-17 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.29.1+ds-1 Bug #1061086 [src:bpfcc] src:bpfcc: fails to migrate to testing for too long: FTBFS on ppc64el Marked as fixed in versions bpfcc/0.29.1+ds-1. Bug #1061086 [src:bpfcc] src:bpfcc: fails to migrate to testing for too long: FTBFS on ppc64el Marked

Bug#1061086: src:bpfcc: fails to migrate to testing for too long: FTBFS on ppc64el

2024-01-17 Thread Paul Gevers
Source: bpfcc Version: 0.26.0+ds-1 Severity: serious Control: close -1 0.29.1+ds-1 Tags: sid trixie ftbfs 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

Bug#1057549: crowdsec: FTBFS: FAIL: TestOneShot/permission_denied

2024-01-17 Thread Cyril Brulebois
Hi Santiago, Santiago Vila (2023-12-05): > […] Thanks for the report. The relevant part didn't appear in the excerpt so I'm quoting the full build log below: > === RUN TestOneShot/permission_denied > file_test.go:234: > Error Trace: >

Processed: [libsass-python] RC Bug #1058362: forward to upstream commit that fixes the FTBFS

2024-01-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1058362 > https://github.com/sass/libsass-python/commit/f0dc392782754e0f5632190c2e9940cc282eef53 Bug #1058362 [src:libsass-python] libsass-python: FTBFS: TypeError: not all arguments converted during string formatting Set Bug

Bug#1058381: casa-formats-io: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-17 Thread s3v
Dear Maintainer, > ERRORS > > _ ERROR collecting > .pybuild/cpython3_3.12_casa-formats-io/build/casa_formats_io/glue_factory.py _ > /usr/lib/python3/dist-packages/_pytest/runner.py:341: in from_call > result:

Bug#1058432: glyphslib: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-17 Thread s3v
Dear Maintainer, > = test session starts > == > platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0 > rootdir: /<>/.pybuild/cpython3_3.12/build > configfile: pyproject.toml > collected 0 items / 29 errors > >

Bug#1058388: fontmake: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

2024-01-17 Thread s3v
Dear Maintainer, > fontmake/font_project.py:946: > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ > fontmake/font_project.py:1006: in _run_from_designspace_static > ufos.extend( > fontmake/font_project.py:744: in interpolate_instance_ufos > from

Bug#1060989: marked as done (astap: FTBFS: make[1]: *** [debian/rules:14: override_dh_auto_build] Error 2)

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 19:04:26 + with message-id and subject line Bug#1060989: fixed in astap 2024.01.16-1 has caused the Debian Bug report #1060989, regarding astap: FTBFS: make[1]: *** [debian/rules:14: override_dh_auto_build] Error 2 to be marked as done. This means that

Bug#1060740: marked as done (regripper: autopkgtest failure with Perl 5.38: changed diagnostics)

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 19:05:34 + with message-id and subject line Bug#1060740: fixed in regripper 3.0~git20221205.d588019+dfsg-1.1 has caused the Debian Bug report #1060740, regarding regripper: autopkgtest failure with Perl 5.38: changed diagnostics to be marked as done. This

Bug#1060999: marked as done (octave-sockets: FTBFS: make: *** [debian/rules:5: binary] Error 25)

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 18:50:26 + with message-id and subject line Bug#1060999: fixed in octave-sockets 1.4.1-3 has caused the Debian Bug report #1060999, regarding octave-sockets: FTBFS: make: *** [debian/rules:5: binary] Error 25 to be marked as done. This means that you claim

Bug#1060740: regripper: diff for NMU version 3.0~git20221205.d588019+dfsg-1.1

2024-01-17 Thread gregor herrmann
Dear maintainer, I've prepared and uploaded an NMU for regripper (versioned as 3.0~git20221205.d588019+dfsg-1.1). The diff is attached to this message. Sorry for the rush, this was one of the last blockers of the ongoing perl 5.38 migration. Cheers, gregor -- .''`.

Bug#1060710: marked as done (dnsenum: autopkgtest failure with Perl 5.38: Smartmatch is deprecated)

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 18:49:08 + with message-id and subject line Bug#1060710: fixed in dnsenum 1.3.1-1.1 has caused the Debian Bug report #1060710, regarding dnsenum: autopkgtest failure with Perl 5.38: Smartmatch is deprecated to be marked as done. This means that you claim

Processed: Bug#1060999 marked as pending in octave-sockets

2024-01-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1060999 [src:octave-sockets] octave-sockets: FTBFS: make: *** [debian/rules:5: binary] Error 25 Added tag(s) pending. -- 1060999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060999 Debian Bug Tracking System Contact

Bug#1060999: marked as pending in octave-sockets

2024-01-17 Thread Rafael Laboissière
Control: tag -1 pending Hello, Bug #1060999 in octave-sockets 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#1060709: marked as done (dh-runit: autopkgtest failure with Perl 5.38: given is deprecated)

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 18:34:13 + with message-id and subject line Bug#1060709: fixed in dh-runit 2.16.2 has caused the Debian Bug report #1060709, regarding dh-runit: autopkgtest failure with Perl 5.38: given is deprecated to be marked as done. This means that you claim that

Bug#1060710: dnsenum: diff for NMU version 1.3.1-1.1

2024-01-17 Thread gregor herrmann
Dear maintainer, I've prepared an NMU for dnsenum (versioned as 1.3.1-1.1). The diff is attached to this message. Sorry for the rush, this was one of the last blockers of the ongoing perl 5.38 migration. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer

Bug#1060276: marked as done (pygalmesh: autopkgtest regression in testing)

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 18:22:17 + with message-id and subject line Bug#1060276: fixed in pygalmesh 0.10.6-2 has caused the Debian Bug report #1060276, regarding pygalmesh: autopkgtest regression in testing to be marked as done. This means that you claim that the problem has been

Bug#1061063: armhf: h5py's tests expose unaligned memory accesses during the build

2024-01-17 Thread Aurelien Jarno
On 2024-01-17 09:33, Matthias Klose wrote: > Package: src:h5py > Version: 3.10.0-1 > Severity: serious > Tags: sid trixie > > armhf: h5py's tests expose unaligned memory accesses during the build, this > not seen with with the 3.9.0 version. You don't see this on the Debian > buildds itself,

Processed: Bug#1061035 marked as pending in libconfig-model-dpkg-perl

2024-01-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1061035 [src:libconfig-model-dpkg-perl] libconfig-model-dpkg-perl: FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 255 Added tag(s) pending. -- 1061035:

Bug#1061035: marked as pending in libconfig-model-dpkg-perl

2024-01-17 Thread Dominique Dumont
Control: tag -1 pending Hello, Bug #1061035 in libconfig-model-dpkg-perl 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#1060983: marked as done (dwarf2sources: FTBFS: build-dependency not installable: librust-gimli-0+indexmap-dev (>= 0.26))

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 16:06:38 + with message-id and subject line Bug#1060983: fixed in dwarf2sources 0.2.4-1 has caused the Debian Bug report #1060983, regarding dwarf2sources: FTBFS: build-dependency not installable: librust-gimli-0+indexmap-dev (>= 0.26) to be marked as

Bug#1061077: golang-github-gookit-color: FTBFS in ubuntu due to unknown TERM env

2024-01-17 Thread upils
Package: golang-github-gookit-color Version: 1.5.4-2 Severity: serious Tags: ftbfs patch Justification: fails to build from source X-Debbugs-Cc: paul.m...@canonical.com Dear Maintainer, In ubuntu this package FTBFS because the TERM env var is set to unknown, thus preventing some tests from

Bug#1061076: kbtin: FTBFS with stack-clash-protection on armhf due to valgrind segfault

2024-01-17 Thread Emanuele Rocca
Source: kbtin Version: 2.1-2 Severity: serious Tags: patch User: debian-...@lists.debian.org Usertags: 32bit-stackclash Hi, kbtin currently fails to build from source on armhf. The failure is due to an incompatibility between valgrind and stack-clash-protection on 32bit arm reported upstream at:

Bug#1000068: libapache2-mod-auth-cas: depends on obsolete pcre3 library

2024-01-17 Thread Thijs Kinkhorst
Hi, > Your package still depends on the old, obsolete PCRE3[0] libraries > (i.e. libpcre3-dev). Thanks for the report. Indeed there's work ongoing upstream to fix this. I'm monitoring this and we hope to get a working version well in time for trixie. Kind regards, Thijs

Bug#1060658: [Debian-on-mobile-maintainers] Bug#1060658: Bug#1060658: megapixels don't start could not find any config file

2024-01-17 Thread Guido Günther
Hi, On Wed, Jan 17, 2024 at 02:17:53PM +0530, Pirate Praveen wrote: > > > On 16/01/24 10:01 pm, Arnaud Ferraris wrote: > > Hi, > > > > Le 12/01/2024 à 10:37, Pirate Praveen a écrit : > > > Package: megapixels > > > Version: 1.7.0-1 > > > Severity: grave > > > > > > Running megapixels from

Bug#1061067: marked as done (qml6-module-qtqml-statemachine and qml6-module-qtscxml have an undeclared file conflict)

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 14:50:11 + with message-id and subject line Bug#1061067: fixed in qt6-scxml 6.6.1-2 has caused the Debian Bug report #1061067, regarding qml6-module-qtqml-statemachine and qml6-module-qtscxml have an undeclared file conflict to be marked as done. This

Bug#1058937: Bug#1060700: Requesting advice regarding the impact of problems caused by aliasing on declared Conflicts

2024-01-17 Thread Helmut Grohne
On Fri, Jan 12, 2024 at 01:31:18PM +0100, Helmut Grohne wrote: > The relevant situation is not entirely trivial to construct: > > * Package $first contains an aliased file $file and this is moved to >package $second in an update. >OR >Package $first diverts aliased location $file

Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

2024-01-17 Thread Scott Kitterman
On Wednesday, January 17, 2024 9:03:29 AM EST Richard Rosner wrote: > I've updated all mariadb packages to 10.11.6 and all postfix packages. > Everything still working. > Excellent news. Thanks for testing. Scott K signature.asc Description: This is a digitally signed message part.

Bug#1060917: postfix-mysql broken in 3.7.9, results in unsupported dictionary type

2024-01-17 Thread Richard Rosner
I've updated all mariadb packages to 10.11.6 and all postfix packages. Everything still working. Am Mittwoch, 17. Januar 2024 00:34 CET, schrieb Scott Kitterman :  They accepted mariadb 10.11.6 as a proposed update and I rebuilt postfix again. Updated packages (and the first ones also, note

Processed: Bug#1058097 marked as pending in python-openstackclient

2024-01-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058097 [src:python-openstackclient] python-openstackclient: FTBFS: AttributeError: module 'sys' has no attribute 'builtin_module_names' Added tag(s) pending. -- 1058097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058097 Debian Bug

Bug#1058097: marked as pending in python-openstackclient

2024-01-17 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #1058097 in python-openstackclient 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#1060943: marked as done (mricron: FTBFS: InitializeFppkg failed: Unable to create file "/sbuild-nonexistent/.config/fppkg.cfg": No such file or directory)

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 13:34:30 + with message-id and subject line Bug#1060943: fixed in mricron 1.2.20211006+dfsg-5 has caused the Debian Bug report #1060943, regarding mricron: FTBFS: InitializeFppkg failed: Unable to create file "/sbuild-nonexistent/.config/fppkg.cfg": No

Bug#1060101: Boost 1.81 removal

2024-01-17 Thread Dirk Eddelbuettel
On 14 January 2024 at 06:49, Dirk Eddelbuettel wrote: | | FYI two days before you filed #1060101 I actually happened to have updated | r-cran-bh to 1.84.0 (upstream, which is me, went to the 1.84.0 version | released in December as Boost releases every four months) using 1.83: | |r-cran-bh

Bug#1056420: marked as done (logbook's autopkg tests fail with Python 3.12)

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 13:59:10 +0100 with message-id and subject line last upload does build has caused the Debian Bug report #1056420, regarding logbook's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1056814: marked as done (logbook: ftbfs with cython 3.0.x)

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 13:59:10 +0100 with message-id and subject line last upload does build has caused the Debian Bug report #1056814, regarding logbook: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1055691: marked as done (logbook ftbfs with Python 3.12)

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 13:59:10 +0100 with message-id and subject line last upload does build has caused the Debian Bug report #1055691, regarding logbook ftbfs with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Processed: Re: Bug#1061018: octave-splines: FTBFS: make: *** [debian/rules:5: binary] Error 134

2024-01-17 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 1061049 Bug #1061018 [src:octave-splines] octave-splines: FTBFS: make: *** [debian/rules:5: binary] Error 134 1061018 was not blocked by any bugs. 1061018 was not blocking any bugs. Added blocking bug(s) of 1061018: 1061049 -- 1061018:

Bug#1061018: octave-splines: FTBFS: make: *** [debian/rules:5: binary] Error 134

2024-01-17 Thread Sébastien Villemot
Control: block -1 by 1061049 Le mardi 16 janvier 2024 à 20:43 +0100, Lucas Nussbaum a écrit : > Source: octave-splines > Version: 1.3.5-2 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240115 ftbfs-trixie > > Hi, > > During a

Processed: Re: Bug#1061017: octave-divand: FTBFS: make: *** [debian/rules:5: binary] Error 134

2024-01-17 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 1061049 Bug #1061017 [src:octave-divand] octave-divand: FTBFS: make: *** [debian/rules:5: binary] Error 134 1061017 was not blocked by any bugs. 1061017 was not blocking any bugs. Added blocking bug(s) of 1061017: 1061049 -- 1061017:

Bug#1061017: octave-divand: FTBFS: make: *** [debian/rules:5: binary] Error 134

2024-01-17 Thread Sébastien Villemot
Control: block -1 by 1061049 Le mardi 16 janvier 2024 à 20:43 +0100, Lucas Nussbaum a écrit : > Source: octave-divand > Version: 1.1.2+dfsg-6 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240115 ftbfs-trixie > > During a rebuild

Processed: Merge duplicates

2024-01-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1060990 src:libwacom Bug #1060990 [src:wacomtablet] wacomtablet: FTBFS: make: *** [debian/rules:8: binary] Error 2 Bug reassigned from package 'src:wacomtablet' to 'src:libwacom'. No longer marked as found in versions

Bug#1042681: marked as done (logbook: FTBFS with Sphinx 7.1, docutils 0.20: intersphinx inventory '/usr/share/doc/python2.7/html/objects.inv' not fetchable due to : [Errno 2

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 11:34:00 + with message-id and subject line Bug#1042681: fixed in logbook 1.7.0-1.0 has caused the Debian Bug report #1042681, regarding logbook: FTBFS with Sphinx 7.1, docutils 0.20: intersphinx inventory '/usr/share/doc/python2.7/html/objects.inv' not

Bug#1061067: qml6-module-qtqml-statemachine and qml6-module-qtscxml have an undeclared file conflict

2024-01-17 Thread Helmut Grohne
Package: qml6-module-qtscxml,qml6-module-qtqml-statemachine Version: 6.6.1-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libqt6scxmlqml6 libqt6statemachineqml6 qml6-module-qtqml-statemachine and qml6-module-qtscxml have an undeclared file

Processed: qml6-module-qtqml-statemachine and qml6-module-qtscxml have an undeclared file conflict

2024-01-17 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + libqt6scxmlqml6 libqt6statemachineqml6 Bug #1061067 [qml6-module-qtscxml,qml6-module-qtqml-statemachine] qml6-module-qtqml-statemachine and qml6-module-qtscxml have an undeclared file conflict Added indication that 1061067 affects libqt6scxmlqml6 and

Bug#1060775: marked as done (tmuxp: flaky autopkgtest: assert pane.capture_pane()[1] -> IndexError)

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 10:35:19 + with message-id and subject line Bug#1060775: fixed in tmuxp 1.34.0-2 has caused the Debian Bug report #1060775, regarding tmuxp: flaky autopkgtest: assert pane.capture_pane()[1] -> IndexError to be marked as done. This means that you claim that

Bug#1058226: marked as done (python-qmix: FTBFS: ImportError: Numba could not be imported.)

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 10:19:25 + with message-id and subject line Bug#1058226: fixed in python-qmix 1.0.6-6 has caused the Debian Bug report #1058226, regarding python-qmix: FTBFS: ImportError: Numba could not be imported. to be marked as done. This means that you claim that

Processed: tagging 1054813

2024-01-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1054813 + pending Bug #1054813 [src:python-dmidecode] python-dmidecode: FTBFS: make[2]: *** [Makefile:4: test] Error 1 Ignoring request to alter tags of bug #1054813 to the same tags previously set > thanks Stopping processing here. Please

Processed: Bug#1054813 marked as pending in python-dmidecode

2024-01-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1054813 [src:python-dmidecode] python-dmidecode: FTBFS: make[2]: *** [Makefile:4: test] Error 1 Added tag(s) pending. -- 1054813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054813 Debian Bug Tracking System Contact

Bug#1054813: marked as pending in python-dmidecode

2024-01-17 Thread Alexandre Detiste
Control: tag -1 pending Hello, Bug #1054813 in python-dmidecode 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#1061064: tomopy: FTBFS with two supported python versions

2024-01-17 Thread Andreas Beckmann
Source: tomopy Version: 1.14.1+ds1-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, tomopy FTBFS if there are two supported python versions because the target wildcard expands to more than one directory: debian/rules execute_before_dh_auto_test make[1]: Entering

Bug#1060658: [Debian-on-mobile-maintainers] Bug#1060658: megapixels don't start could not find any config file

2024-01-17 Thread Pirate Praveen
On 16/01/24 10:01 pm, Arnaud Ferraris wrote: Hi, Le 12/01/2024 à 10:37, Pirate Praveen a écrit : Package: megapixels Version: 1.7.0-1 Severity: grave Running megapixels from commandline on mobian trixie fails with this error /usr/share/megapixels/config/purism,librem5r4.ini not found.

Bug#1059669: marked as done (python-sure: autopkgtest failure with Python 3.12)

2024-01-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jan 2024 08:36:01 + with message-id and subject line Bug#1059669: fixed in python-sure 2.0.1-0.1 has caused the Debian Bug report #1059669, regarding python-sure: autopkgtest failure with Python 3.12 to be marked as done. This means that you claim that the problem

Processed: affects 1061049

2024-01-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1061049 + octave ceres-solver Bug #1061049 [libsuitesparse-dev] libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6" Added indication that 1061049 affects octave and ceres-solver >

Processed: affects 1061049

2024-01-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1061049 + libdogleg2 Bug #1061049 [libsuitesparse-dev] libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6" Added indication that 1061049 affects libdogleg2 > thanks Stopping

Bug#1061063: armhf: h5py's tests expose unaligned memory accesses during the build

2024-01-17 Thread Matthias Klose
Package: src:h5py Version: 3.10.0-1 Severity: serious Tags: sid trixie armhf: h5py's tests expose unaligned memory accesses during the build, this not seen with with the 3.9.0 version. You don't see this on the Debian buildds itself, because they ignore these misalignments. Already happens

Processed: tagging 1061049 ...

2024-01-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1061049 + upstream Bug #1061049 [libsuitesparse-dev] libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6" Added tag(s) upstream. > forwarded 1061049 >

Bug#1061049: libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6"

2024-01-17 Thread Dima Kogan
Thanks. In case you're unaware, there're tools that can report ABI and API breaks. I usually use abi-compliance-checker (works great). And there's also abigail (have't tried it myself, but supposedly works well). Both are in Debian. Cheers.

Processed: notfound 1061049 in 1:7.3.1+dfsg-2, found 1061049 in 1:7.4.0+dfsg-1

2024-01-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1061049 1:7.3.1+dfsg-2 Bug #1061049 [libsuitesparse-dev] libsuitesparse-dev: libsuitesparse-dev 7.4.0 has an ABI break in libcholmod5 without bumping to "libcholmod6" No longer marked as found in versions suitesparse/1:7.3.1+dfsg-2. >

Processed: unarchiving 1051592, fixed 1051592 in 0.9.8-3.1+deb11u2, tagging 1051592

2024-01-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 1051592 Bug #1051592 {Done: Salvatore Bonaccorso } [src:nftables] linux: Regression - upgrade to 6.1.52-1 breaks nftables Unarchived Bug 1051592 > fixed 1051592 0.9.8-3.1+deb11u2 Bug #1051592 {Done: Salvatore Bonaccorso }

Processed: retitle 1057717 to libuv1: io_uring support randomly segfaults after signal on ppc64el/ppc64 ...

2024-01-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1057717 libuv1: io_uring support randomly segfaults after signal on > ppc64el/ppc64 Bug #1057717 [libuv1] cmake ftbfs on ppc64el (and ppc64) Changed Bug title to 'libuv1: io_uring support randomly segfaults after signal on