Processed: Re: Bug#1100615: cifs-utils: Mounting of shares fails on boot

Processing control commands: > tag -1 - moreinfo unreproducible Bug #1100615 [cifs-utils] cifs-utils: Mounting of shares fails on boot Removed tag(s) moreinfo and unreproducible. > tag -1 + confirmed upstream Bug #1100615 [cifs-utils] cifs-utils: Mounting of shares fails on boot Added tag(s) confi

Bug#1100615: cifs-utils: Mounting of shares fails on boot

Control: tag -1 - moreinfo unreproducible Control: tag -1 + confirmed upstream Control: severity -1 normal Control: forwarded -1 https://bugzilla.samba.org/show_bug.cgi?id=15830 17.03.2025 00:09, Joe wrote: cifs: Bad value for 'password2' ... Sorry, I don't know what password2 is. If it helps

Bug#1098531: marked as done (libsignal-protocol-c-dev: missing dependency on libprotobuf-c-)

Your message dated Mon, 17 Mar 2025 04:39:46 +0100 with message-id and subject line has caused the Debian Bug report #1098531, regarding libsignal-protocol-c-dev: missing dependency on libprotobuf-c- to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#1100588: encfs: After the upgrade to libtinyxml2-10_10.1.0, encfs no longer works

clone 1100588 -1 reassign -1 libtinyxml2-10 retitle -1 libtinyxml2-10: apparent ABI break thanks Hi, see below for the description. I can confirm, with stacktrace. Maybe time to create a custom SONAME version? Program received signal SIGSEGV, Segmentation fault. 0x778fd6ce in tinyxml2::X

Bug#1100349: marked as done (rust-axum: FTBFS: error[E0433]: failed to resolve: could not find `test` in the crate root)

Your message dated Sun, 16 Mar 2025 21:10:56 + with message-id and subject line Bug#1100349: fixed in rust-axum 0.7.9-11 has caused the Debian Bug report #1100349, regarding rust-axum: FTBFS: error[E0433]: failed to resolve: could not find `test` in the crate root to be marked as done. This

Processed (with 2 errors): libsignal-protocol-c-dev: missing dependency on libprotobuf-c-dev

Processing commands for cont...@bugs.debian.org: > reassign 1098531 libsignal-protocol-c-dev Bug #1098531 [src:axc] axc: FTBFS: /usr/bin/ld: cannot find -lprotobuf-c: No such file or directory Bug reassigned from package 'src:axc' to 'libsignal-protocol-c-dev'. No longer marked as found in versio

Bug#1100658: marked as done (rust-tonic - autopkgtest failure)

Your message dated Sun, 16 Mar 2025 21:12:01 + with message-id and subject line Bug#1100658: fixed in rust-tonic 0.12.3+dfsg-2 has caused the Debian Bug report #1100658, regarding rust-tonic - autopkgtest failure to be marked as done. This means that you claim that the problem has been dealt

Bug#1084331: marked as done (python-directv: FTBFS: ValueError: Host '#' cannot contain '#' (at position 0))

Your message dated Sun, 16 Mar 2025 22:19:59 + with message-id and subject line Bug#1084331: fixed in python-directv 0.4.0-3 has caused the Debian Bug report #1084331, regarding python-directv: FTBFS: ValueError: Host '#' cannot contain '#' (at position 0) to be marked as done. This means th

Processed: reopening, c-t-b-mipsen is still unfixed

Processing control commands: > reopen -1 Bug #1100544 {Done: Aurelien Jarno } [libc6-dev-i386] glibc adds some conflicts letting gcc-14-cross ftbfs Bug reopened Ignoring request to alter fixed versions of bug #1100544 to the same values previously set -- 1100544: https://bugs.debian.org/cgi-bi

Bug#1092397: marked as done (cross-toolchain-base-ports: FTBFS: make: *** [debian/rules:446: stamp-dir/init-glibc] Error 1)

Your message dated Mon, 17 Mar 2025 02:56:23 +0100 with message-id <094979f5-d98a-44bc-bbed-41e87b31e...@debian.org> and subject line fixed in 71 has caused the Debian Bug report #1092397, regarding cross-toolchain-base-ports: FTBFS: make: *** [debian/rules:446: stamp-dir/init-glibc] Error 1 to be

Bug#1100544: reopening, c-t-b-mipsen is still unfixed

Control: reopen -1 reopening, c-t-b-mipsen is still unfixed. I'm fine to drop the intermediate patch in c-t-b and c-t-b-ports.

Bug#1093308: marked as done (inkscape: FTBFS against poppler 25.01)

Your message dated Mon, 17 Mar 2025 00:52:33 + with message-id and subject line Bug#1093308: fixed in inkscape 1.4-4 has caused the Debian Bug report #1093308, regarding inkscape: FTBFS against poppler 25.01 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1100671: packaging-dev: get out of testing

Source: packaging-dev Version: 0.8.2 Severity: serious While packaging-dev was probably useful when it was actively maintained, it hasn't been for the last 10 or so years. Currently it reocmmends packages no longer existing in Debian, that itself is an rc-bug. But really, lets just get rid of

Bug#1100238: lintian: FTBFS: make[1]: *** No rule to make target '/usr/share/cdbs/1/rules/simple-patchsys.mk'. Stop.

Hi, CDBS is still full of _others_ deprecated rules to test for. I'd suggest to test for one of these 5 ones instead of simple-patchsys.mk: /usr/share/cdbs/1/class/ant.mk /usr/share/cdbs/1/class/cmake.mk /usr/share/cdbs/1/class/gnome.mk /usr/share/cdbs/1/class/qmake.mk /usr/share/

Bug#1098552: marked as done (golang-github-fullsailor-pkcs7: FTBFS: verify_test.go:563: Verify failed with error: pkcs7: failed to verify certificate chain)

Your message dated Sun, 16 Mar 2025 22:04:39 + with message-id and subject line Bug#1098552: fixed in golang-github-fullsailor-pkcs7 0.0~git20210826.33d0574-3 has caused the Debian Bug report #1098552, regarding golang-github-fullsailor-pkcs7: FTBFS: verify_test.go:563: Verify failed with er

Bug#1096226: marked as done (receptor: FTBFS: dh_auto_test: error)

Your message dated Mon, 17 Mar 2025 00:29:07 + with message-id and subject line Bug#1096226: fixed in receptor 1.5.3-1 has caused the Debian Bug report #1096226, regarding receptor: FTBFS: dh_auto_test: error to be marked as done. This means that you claim that the problem has been dealt with

Bug#1099228: marked as done (evil-el: FTBFS: Unknown JSON error)

Your message dated Mon, 17 Mar 2025 00:21:58 + with message-id and subject line Bug#1099228: fixed in evil-el 1.14.2-4 has caused the Debian Bug report #1099228, regarding evil-el: FTBFS: Unknown JSON error to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1074641: marked as done (lapackpp: FTBFS: device.hh:67:30: error: invalid conversion from ‘int64_t’ {aka ‘long int’} to ‘blas::Queue::stream_t’ {aka ‘void*’} [-fpermissive])

Your message dated Sun, 16 Mar 2025 23:45:38 +0100 with message-id <67d75493.500a0220.3233e5.0...@mx.google.com> and subject line Re: [Debichem-devel] Bug#1074641: lapackpp: FTBFS: device.hh:67:30: error: invalid conversion from ‘int64_t’ {aka ‘long int’} to ‘blas::Queue::stream_t’ {aka ‘void*’}

Processed: severity of 985184 is important

Processing commands for cont...@bugs.debian.org: > severity 985184 important Bug #985184 [src:reminiscence] reminiscence: New upstream version is not licensed Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 985184: https

Bug#1093352: marked as done (psi4: FTBFS: error: could not find git for clone of qcelemental_external)

Your message dated Sun, 16 Mar 2025 22:56:42 + with message-id and subject line Bug#1093352: fixed in psi4 1:1.3.2+dfsg-6 has caused the Debian Bug report #1093352, regarding psi4: FTBFS: error: could not find git for clone of qcelemental_external to be marked as done. This means that you cl

Bug#1098698: linux: Segfault and system hang on larger network file transfers

Hi, I’m not sure if the error depends on the files size (or if another thing is causing my problem in my case) Problem started after Updating from 6.1.0 to 6.12.12. See the update history: Commandline: apt dist-upgrade Install: linux-image-6.12.12+bpo-amd64:amd64 (6.12.12-1~bpo12+1, automatic) Up

Bug#1099655: initramfs-tools 146 generates incorrect initramfs : does not boot, does not find root fs

On 16/03/2025 21:01, Ben Hutchings wrote: On Sun, 2025-03-16 at 20:21 +0100, Eric Valette wrote: And yet module loading is going wrong in a way that can't be reproduced elsewhere. So please check. I rather did check after unpacking the initrd as it was needed anyway kmod binaries are ident

Bug#1100226: marked as done (jack: FTBFS: pyproject_hooks._impl.BackendUnavailable: Cannot import 'setuptools.build_meta')

Your message dated Sun, 16 Mar 2025 22:54:47 + with message-id and subject line Bug#1100226: fixed in jack 4~git20241202.3410dc1-2 has caused the Debian Bug report #1100226, regarding jack: FTBFS: pyproject_hooks._impl.BackendUnavailable: Cannot import 'setuptools.build_meta' to be marked as

Processed: Bug#1093352 marked as pending in psi4

Processing control commands: > tag -1 pending Bug #1093352 [src:psi4] psi4: FTBFS: error: could not find git for clone of qcelemental_external Added tag(s) pending. -- 1093352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093352 Debian Bug Tracking System Contact ow...@bugs.debian.org wit

Bug#1093352: marked as pending in psi4

Control: tag -1 pending Hello, Bug #1093352 in psi4 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: https://salsa.debian.org/debichem-team/psi4/-/commit/a1bf91870bff89376eb04d27ddc9e209

Bug#1100464: marked as done (opensaml: Parameter manipulation allows the forging of signed SAML messages)

Your message dated Sun, 16 Mar 2025 21:34:03 +0100 with message-id and subject line Re: Accepted opensaml 3.3.1-1 (source) into unstable has caused the Debian Bug report #1100464, regarding opensaml: Parameter manipulation allows the forging of signed SAML messages to be marked as done. This mea

Processed: limit source to linux, tagging 1099591, tagging 1098698

Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > tags 1099591 + pending Bug #1099591 [src:linux] linux-image-6.12.12-amd64: crash in netfs module when copying (l

Bug#1099897: marked as done (src:netavark: unsatisfied build dependency in testing: librust-zbus-4-dev (>= 4.3.1))

Your message dated Sun, 16 Mar 2025 22:18:52 + with message-id and subject line Bug#1099897: fixed in netavark 1.14.0-2 has caused the Debian Bug report #1099897, regarding src:netavark: unsatisfied build dependency in testing: librust-zbus-4-dev (>= 4.3.1) to be marked as done. This means t

Bug#1093690: marked as done (netavark: Upcoming update of zbus to v5)

Your message dated Sun, 16 Mar 2025 22:18:52 + with message-id and subject line Bug#1093690: fixed in netavark 1.14.0-2 has caused the Debian Bug report #1093690, regarding netavark: Upcoming update of zbus to v5 to be marked as done. This means that you claim that the problem has been dealt

Processed: tagging 1099823, tagging 1099831, tagging 1100005, tagging 1100533, tagging 1098886, tagging 1095129

Processing commands for cont...@bugs.debian.org: > tags 1099823 + sid trixie Bug #1099823 [src:libglade2] libglade2: please migrate away from /usr/share/cdbs/1/class/gnome.mk Added tag(s) trixie and sid. > tags 1099831 + sid trixie Bug #1099831 [src:atitvout] Should atitvout be removed from unsta

Bug#1098552: marked as pending in golang-github-fullsailor-pkcs7

Control: tag -1 pending Hello, Bug #1098552 in golang-github-fullsailor-pkcs7 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: https://salsa.debian.org/go-team/packages/golang-github-fu

Bug#1100663: ns3: Not built on buildd: arch all binaries uploaded by mquinson, a new source-only upload is needed to allow migration

Source: ns3 Version: 3.43-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org Dear maintainer, ns3 is currently unable to migrate: Migration status for ns3 (3.42-2 to 3.43-1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: Not built on b

Bug#1100171: marked as done (libtree-sitter0: Crashes Emacs with "stack smashing detected" when python language grammar is installed)

Your message dated Sun, 16 Mar 2025 21:14:18 + with message-id and subject line Bug#1100171: fixed in tree-sitter 0.22.6-6 has caused the Debian Bug report #1100171, regarding libtree-sitter0: Crashes Emacs with "stack smashing detected" when python language grammar is installed to be marked

Processed: Bug#1098552 marked as pending in golang-github-fullsailor-pkcs7

Processing control commands: > tag -1 pending Bug #1098552 [src:golang-github-fullsailor-pkcs7] golang-github-fullsailor-pkcs7: FTBFS: verify_test.go:563: Verify failed with error: pkcs7: failed to verify certificate chain Added tag(s) pending. -- 1098552: https://bugs.debian.org/cgi-bin/bugre

Processed: closing 1096250

Processing commands for cont...@bugs.debian.org: > close 1096250 1:18.1.8-17 Bug #1096250 [src:llvm-toolchain-18] llvm-toolchain-18: FTBFS: make[1]: *** [debian/rules:748: stamps/configure] Error 1 Marked as fixed in versions llvm-toolchain-18/1:18.1.8-17. Bug #1096250 [src:llvm-toolchain-18] llv

Bug#1096250: closing 1096250

close 1096250 1:18.1.8-17 thanks llvm-toolchain-18 (1:18.1.8-17) unstable; urgency=medium . [ Matthias Klose ] * d/control, d/t/control: Add binutils-gold as explicit build dependency. Will fix arm64 test failures . [ Sylvestre Ledru ] * Enable sse2 back on i386 for rustc

Processed: Re: Bug#1100588: encfs: After the upgrade to libtinyxml2-10_10.1.0, encfs no longer works

Processing commands for cont...@bugs.debian.org: > clone 1100588 -1 Bug #1100588 [encfs] encfs: After the upgrade to libtinyxml2-10_10.1.0, encfs no longer works Bug 1100588 cloned as bug 1100661 > reassign -1 libtinyxml2-10 Bug #1100661 [encfs] encfs: After the upgrade to libtinyxml2-10_10.1.0,

Bug#1099655: initramfs-tools 146 generates incorrect initramfs : does not boot, does not find root fs

On 16/03/2025 20:13, Ben Hutchings wrote: Control: tag -1 moreinfo unreproducible On Sat, 2025-03-08 at 12:29 +0100, Eric Valette wrote: On Fri, 7 Mar 2025 20:43:08 +0100 Marc Haber wrote: On Fri, Mar 07, 2025 at 05:44:00PM +0100, Eric Valette wrote: CONFIG_MODULE_DECOMPRESS=y So the cul

Bug#1100464: Accepted opensaml 3.3.1-1 (source) into unstable

Source: opensaml Source-Version: 3.3.1-1 On Sun, Mar 16, 2025 at 03:51:53PM +, Debian FTP Masters wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Format: 1.8 > Date: Sun, 16 Mar 2025 14:41:33 +0100 > Source: opensaml > Architecture: source > Version: 3.3.1-1 > Distribution: uns

Bug#1099655: initramfs-tools 146 generates incorrect initramfs : does not boot, does not find root fs

On Sun, 2025-03-16 at 20:21 +0100, Eric Valette wrote: > On 16/03/2025 20:13, Ben Hutchings wrote: [...] > > Does your initramfs image include the right version of modprobe? > > Boot with "break=top" and run "modprobe --version" to check this. > > It use wahever is put in. I did not make any chna

Bug#1099708: freerdp3: FTBFS: make[4]: *** No rule to make target 'channels/rdpear/common/CMakeFiles/rdpear-common-obj.dir/ndr.c.o', needed by 'client/common/libfreerdp-client3.so.3.13.0'. Stop.

15.03.2025 11:29, Michael Tokarev wrote: I just tried to build 3.14 in a qemu/kvm VM with single CPU.  It fails - just like 3.13 did - in tests, in TestFreeRDPCodecH264 (SEGFAULT).  Is it the same failure as in your testing? https://github.com/FreeRDP/FreeRDP/pull/11358 fixes this failure for

Bug#1066985: marked as done (gdis: FTBFS: crystal_graph.c:180:3: error: implicit declaration of function ‘type_dreiding_gasteiger’ [-Werror=implicit-function-declaration])

Your message dated Sun, 16 Mar 2025 19:34:46 + with message-id and subject line Bug#1066985: fixed in gdis 0.90+git20210921.6a2605f-1 has caused the Debian Bug report #1066985, regarding gdis: FTBFS: crystal_graph.c:180:3: error: implicit declaration of function ‘type_dreiding_gasteiger’ [-We

Processed: Re: Bug#1099655: initramfs-tools 146 generates incorrect initramfs : does not boot, does not find root fs

Processing control commands: > tag -1 moreinfo unreproducible Bug #1099655 [initramfs-tools] initramfs-tools 146 generates incorrect initramfs : does not boot, does not find root fs Added tag(s) unreproducible and moreinfo. -- 1099655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099655 D

Processed (with 1 error): Re: initramfs-tools: causes autopkgtest regressions in cryptsetup, multipath-tools, maybe intel-microcode

Processing control commands: > affects -1 src:cryptsetup Unknown command or malformed arguments to command. > affects -1 src:multipath-tools Bug #118 [src:initramfs-tools] initramfs-tools: causes autopkgtest regressions in cryptsetup, multipath-tools, maybe intel-microcode Added indication t

Bug#1100658: rust-tonic - autopkgtest failure

Package: rust-tonic Version: 0.12.3+dfsg-1 Severity: serious rust-tonic's autopkgtests are failing due to a couple of issues. 1. Api differences between rustls-native-certs 0.8 (expected by upstream) and 0.6 (currently in Debian) 2. Typos in debian/control and debian/tests/control. A debdiff ad

Processed: Re: balsa: Remove from Debian?

Processing commands for cont...@bugs.debian.org: > severity 1094887 important Bug #1094887 [src:balsa] balsa: Remove from Debian? Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 1094887: https://bugs.debian.org/c

Bug#1099419: gimp 3.0 crash on startup due to incorrect dependency on librsvg2

On Mon, Mar 3, 2025 at 7:27 AM Woody Suwalski wrote: > I have found that dependencies of the Gimp package are incorrect - it > depends on > librsvg2, but it should have depended on librsvg2-common, which would have > pulled in librsvg2 as well. librsvg2-2 Recommends librsvg2-common. Please don't

Processed: affects 1100008

Processing commands for cont...@bugs.debian.org: > affects 118 src:cryptsetup Bug #118 [src:initramfs-tools] initramfs-tools: causes autopkgtest regressions in cryptsetup, multipath-tools, maybe intel-microcode Added indication that 118 affects src:cryptsetup > thanks Stopping process

Bug#1100656: asahi-audio: Volume cannot be turned down (or up)

Package: asahi-audio Version: 3.1-1 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: noisyc...@tutanota.com After upgrading from 3.0-3 to 3.1-1, volume cannot be turned down (or up, but the default is almost full volume so this is less of an issue) on an M1 Mini

Processed: Re: [Pkg-samba-maint] Bug#1100615: cifs-utils: Mounting of shares fails on boot

Processing control commands: > tag -1 + moreinfo unreproducible Bug #1100615 [cifs-utils] cifs-utils: Mounting of shares fails on boot Added tag(s) unreproducible and moreinfo. -- 1100615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100615 Debian Bug Tracking System Contact ow...@bugs.deb

Bug#1100615: [Pkg-samba-maint] Bug#1100615: cifs-utils: Mounting of shares fails on boot

Control: tag -1 + moreinfo unreproducible 16.03.2025 13:41, Joe wrote: Package: cifs-utils Version: 2:7.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? On boot, no shares were mounted Upgraded yesterday, next boot this morning

Bug#1100289: marked as done (python-sphobjinv: FTBFS: pytest.PytestAssertRewriteWarning: Module already imported so cannot be rewritten: pytest_check.check_functions)

Your message dated Sun, 16 Mar 2025 17:54:51 + with message-id and subject line Bug#1100289: fixed in python-sphobjinv 2.3.1.2-2 has caused the Debian Bug report #1100289, regarding python-sphobjinv: FTBFS: pytest.PytestAssertRewriteWarning: Module already imported so cannot be rewritten: pyt

Bug#1094887: Balsa release

Thank you so much for your wake-up call… The Balsa 2.6.4 release is actually almost 2½ years old, and in the meantime, lots of bugs have been fixed (I *think* [hope…] including those referenced in this bug report), and some new features have been added. We were just too lazy (or had too much

Bug#1100008: initramfs-tools: causes autopkgtest regressions in cryptsetup, multipath-tools, maybe intel-microcode

Control: affects -1 src:cryptsetup Control: affects -1 src:multipath-tools Control: affects -1 src:intel-microcode Control: tag -1 patch A potential fix for this is in . However, I am not able to re-run the autopkgtests wi

Bug#1100318: marked as done (sigil: FTBFS: /usr/include/x86_64-linux-gnu/qt6/QtCore/qchar.h:66:2: error: #error This macro has been removed in Qt 6.8.)

Your message dated Sun, 16 Mar 2025 17:21:48 + with message-id and subject line Bug#1100318: fixed in sigil 2.4.2+dfsg-1 has caused the Debian Bug report #1100318, regarding sigil: FTBFS: /usr/include/x86_64-linux-gnu/qt6/QtCore/qchar.h:66:2: error: #error This macro has been removed in Qt 6.

Bug#1100252: marked as done (poetry-plugin-export: FTBFS: E assert 'bar==1.1.0 ;...ion < "4.0"\n' == 'bar==1.1.0 ;...on == "2.7"\n')

Your message dated Sun, 16 Mar 2025 17:35:23 + with message-id and subject line Bug#1100252: fixed in poetry-plugin-export 1.9.0-2 has caused the Debian Bug report #1100252, regarding poetry-plugin-export: FTBFS: E assert 'bar==1.1.0 ;...ion < "4.0"\n' == 'bar==1.1.0 ;...on == "2.7"\n'

Bug#1100077: marked as done (jupyterhub: creates /usr/alembic.ini)

Your message dated Sun, 16 Mar 2025 17:05:59 + with message-id and subject line Bug#1100077: fixed in jupyterhub 5.2.1+ds1-2 has caused the Debian Bug report #1100077, regarding jupyterhub: creates /usr/alembic.ini to be marked as done. This means that you claim that the problem has been deal

Bug#1099838: bacon has an undeclared file conflict on /usr/bin/bacon

On 14/03/2025 15:34, Antonio Terceiro wrote: On Thu, Mar 13, 2025 at 02:49:31PM +, Blair Noctis wrote: Thus I suggest: 1. Update d/control of ruby-faraday, ruby-rack, ruby-em-spec, ruby-temple to remove obsolete B-D 2. Update ruby-rack-cache to latest/newer version (1.2 in Debian, 1.17 up

Bug#1100081: marked as done (pyspread: creates /usr/pyspread/share/applications/ instead of using /usr/share/applications/)

Your message dated Sun, 16 Mar 2025 17:20:50 + with message-id and subject line Bug#1100081: fixed in pyspread 2.3.1-3 has caused the Debian Bug report #1100081, regarding pyspread: creates /usr/pyspread/share/applications/ instead of using /usr/share/applications/ to be marked as done. This

Bug#1096242: golang-k8s-kube-openapi: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 k8s.io/kube-openapi/cmd/openapi-gen [...] k8s.io/kube-openapi/test/integration/testutil returned

On 13/03/2025 16:28, Nicolas Peugnet wrote: After investigation, this panic also occurs from an upstream checkout: $ git checkout ab13479 $ go test ./pkg/generators/ E0313 16:22:11.669135 3181592 openapi.go:322] Error when generating: StringToArray, StringToArray map[string]map[string]map[int]s

Processed: Bug#1100081 marked as pending in pyspread

Processing control commands: > tag -1 pending Bug #1100081 [src:pyspread] pyspread: creates /usr/pyspread/share/applications/ instead of using /usr/share/applications/ Added tag(s) pending. -- 1100081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100081 Debian Bug Tracking System Contact

Bug#1100654: mbtserver: using icu but missing libicu-dev explicit dependency

Source: mbtserver Version: 0.17-1 Severity: serious Tags: patch Hello, looks like mbtserver uses directly icu ./configure.ac:AC_OSX_PKG( [icu4c] ) ./configure.ac:PKG_CHECK_MODULES([ICU], [icu-uc >= 50 icu-io] ) But misses a build-dependency on libicu-dev. Note: currently this is added via lib

Bug#1100081: marked as pending in pyspread

Control: tag -1 pending Hello, Bug #1100081 in pyspread 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: https://salsa.debian.org/python-team/packages/pyspread/-/commit/ac6e692ccc6954f8e

Bug#1100258: marked as done (python-aiohttp-security: FTBFS: ModuleNotFoundError: No module named 'setuptools')

Your message dated Sun, 16 Mar 2025 16:50:40 + with message-id and subject line Bug#1100258: fixed in python-aiohttp-security 0.5.0-2 has caused the Debian Bug report #1100258, regarding python-aiohttp-security: FTBFS: ModuleNotFoundError: No module named 'setuptools' to be marked as done. T

Bug#1100077: marked as pending in jupyterhub

Control: tag -1 pending Hello, Bug #1100077 in jupyterhub 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: https://salsa.debian.org/python-team/packages/jupyterhub/-/commit/6b2eb6c63d73c

Processed: Bug#1100077 marked as pending in jupyterhub

Processing control commands: > tag -1 pending Bug #1100077 [src:jupyterhub] jupyterhub: creates /usr/alembic.ini Added tag(s) pending. -- 1100077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1100276: marked as done (python-opt-einsum: FTBFS: ModuleNotFoundError: No module named 'mkdocs_get_deps')

Your message dated Sun, 16 Mar 2025 16:38:55 + with message-id and subject line Bug#1100276: fixed in python-opt-einsum 3.4.0-2 has caused the Debian Bug report #1100276, regarding python-opt-einsum: FTBFS: ModuleNotFoundError: No module named 'mkdocs_get_deps' to be marked as done. This mea

Bug#1100475: marked as done (python3-zstandard: Package not installable when libzstd1=1.5.7)

Your message dated Sun, 16 Mar 2025 16:39:07 + with message-id and subject line Bug#1100475: fixed in python-zstandard 0.23.0-4 has caused the Debian Bug report #1100475, regarding python3-zstandard: Package not installable when libzstd1=1.5.7 to be marked as done. This means that you claim t

Bug#1100652: timblserver: using icu but missing libicu-dev explicit dependency

Source: timblserver Version: 1.19-1 Severity: serious Tags: patch Hello, looks like timblserver uses directly icu, as said in other bug reports already :) ./configure.ac:AC_OSX_PKG( [icu4c] ) ./configure.ac:PKG_CHECK_MODULES([ICU], [icu-uc >= 50 icu-io] ) But misses a build-dependency on lib

Bug#1098501: marked as done ([multiple architectures] haskell-gi-vte: FTBFS:build failed ( Could not load module ‘GI.GdkPixbuf.Objects.Pixbuf’))

Your message dated Sun, 16 Mar 2025 16:34:41 + with message-id and subject line Bug#1098501: fixed in haskell-gi-vte 2.91.33-2 has caused the Debian Bug report #1098501, regarding [multiple architectures] haskell-gi-vte: FTBFS:build failed ( Could not load module ‘GI.GdkPixbuf.Objects.Pixbuf’

Processed: Bug#1100258 marked as pending in python-aiohttp-security

Processing control commands: > tag -1 pending Bug #1100258 [src:python-aiohttp-security] python-aiohttp-security: FTBFS: ModuleNotFoundError: No module named 'setuptools' Added tag(s) pending. -- 1100258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100258 Debian Bug Tracking System Conta

Bug#1095367: marked as done (python-asyncclick: FTBFS: E ModuleNotFoundError: No module named 'trio')

Your message dated Sun, 16 Mar 2025 16:28:31 + with message-id and subject line Re: Bug#1095367: python-asyncclick: FTBFS: E ModuleNotFoundError: No module named 'trio' has caused the Debian Bug report #1095367, regarding python-asyncclick: FTBFS: E ModuleNotFoundError: No module named '

Bug#1100258: marked as pending in python-aiohttp-security

Control: tag -1 pending Hello, Bug #1100258 in python-aiohttp-security 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: https://salsa.debian.org/python-team/packages/python-aiohttp-secur

Bug#1100283: marked as done (python-redfish: FTBFS: pyproject_hooks._impl.BackendUnavailable: Cannot import 'setuptools.build_meta')

Your message dated Sun, 16 Mar 2025 16:21:27 + with message-id and subject line Bug#1100283: fixed in python-redfish 3.2.7-4 has caused the Debian Bug report #1100283, regarding python-redfish: FTBFS: pyproject_hooks._impl.BackendUnavailable: Cannot import 'setuptools.build_meta' to be marked

Bug#1100475: python3-zstandard: Package not installable when libzstd1=1.5.7

On Fri, 14 Mar 2025 10:57:04 + Simon McVittie wrote: > On Fri, 14 Mar 2025 at 10:42:09 +, Luca Boccassi wrote: > >Bumping severity as the package is uninstallable due to this issue. > > > >d/control hardcodes the version range, so it needs a source update: > > > >Package: python3-zstandard

Processed: Bug#1100475 marked as pending in python-zstandard

Processing control commands: > tag -1 pending Bug #1100475 [python3-zstandard] python3-zstandard: Package not installable when libzstd1=1.5.7 Added tag(s) pending. -- 1100475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100475 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1100475: marked as pending in python-zstandard

Control: tag -1 pending Hello, Bug #1100475 in python-zstandard 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: https://salsa.debian.org/python-team/packages/python-zstandard/-/commit/1

Bug#1100279: marked as done (python-pyfunceble: FTBFS: ModuleNotFoundError: No module named 'mkdocs_get_deps')

Your message dated Sun, 16 Mar 2025 15:55:08 + with message-id and subject line Re: Bug#1100279: python-pyfunceble: FTBFS: ModuleNotFoundError: No module named 'mkdocs_get_deps' has caused the Debian Bug report #1100279, regarding python-pyfunceble: FTBFS: ModuleNotFoundError: No module named

Bug#1100270: marked as done (python-markdown: FTBFS: ModuleNotFoundError: No module named 'mkdocs_get_deps')

Your message dated Sun, 16 Mar 2025 15:52:36 + with message-id and subject line Re: Bug#1100270: python-markdown: FTBFS: ModuleNotFoundError: No module named 'mkdocs_get_deps' has caused the Debian Bug report #1100270, regarding python-markdown: FTBFS: ModuleNotFoundError: No module named 'm

Bug#1100263: marked as done (python-django-pgtrigger: FTBFS: ModuleNotFoundError: No module named 'mkdocs_get_deps')

Your message dated Sun, 16 Mar 2025 15:50:49 + with message-id and subject line Re: Bug#1100263: python-django-pgtrigger: FTBFS: ModuleNotFoundError: No module named 'mkdocs_get_deps' has caused the Debian Bug report #1100263, regarding python-django-pgtrigger: FTBFS: ModuleNotFoundError: No

Bug#1100205: marked as done (cmd2: FTBFS: ModuleNotFoundError: No module named 'mkdocs_get_deps')

Your message dated Sun, 16 Mar 2025 15:48:57 + with message-id and subject line Re: Bug#1100205: cmd2: FTBFS: ModuleNotFoundError: No module named 'mkdocs_get_deps' has caused the Debian Bug report #1100205, regarding cmd2: FTBFS: ModuleNotFoundError: No module named 'mkdocs_get_deps' to be m

Bug#1074649: marked as done (gau2grid: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)

Your message dated Sun, 16 Mar 2025 15:50:09 + with message-id and subject line Bug#1074649: fixed in gau2grid 2.0.7-3 has caused the Debian Bug report #1074649, regarding gau2grid: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParse

Bug#1099520: yubikey-manager-qt: ImportError: cannot import name '_PrepareUploadFailed' from 'ykman.otp' - Qt application is EOL and uses outdated ykman API

Control: tags -1 patch Dear Maintainer, Please find in attachment a patch that you can drop in the debian/patches/ directory to fix compatibility with ykman 5.5 Please don't remove yubikey-manager-qt even if it's upstream developer puts an EOL stamp on it. We don't have a viable replacement

Processed: Re: yubikey-manager-qt: ImportError: cannot import name '_PrepareUploadFailed' from 'ykman.otp' - Qt application is EOL and uses outdated ykman API

Processing control commands: > tags -1 patch Bug #1099520 [yubikey-manager-qt] yubikey-manager-qt: ImportError: cannot import name '_PrepareUploadFailed' from 'ykman.otp' - Qt application is EOL and uses outdated ykman API Added tag(s) patch. -- 1099520: https://bugs.debian.org/cgi-bin/bugrepo

Bug#1066984: marked as done (gabedit: FTBFS: Preferences.c:2254:23: error: implicit declaration of function ‘selectionOfDir’; did you mean ‘selctionOfDir’? [-Werror=implicit-function-declaration])

Your message dated Sun, 16 Mar 2025 15:34:35 + with message-id and subject line Bug#1066984: fixed in gabedit 2.5.1+ds-2 has caused the Debian Bug report #1066984, regarding gabedit: FTBFS: Preferences.c:2254:23: error: implicit declaration of function ‘selectionOfDir’; did you mean ‘selction

Bug#1074649: marked as pending in $i

Control: tag -1 pending Hello, Bug #1074649 in $i 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: https://salsa.debian.org/debichem-team/gau2grid/-/commit/64c8c2049c2b8ea07cd1eeeaa3e84b

Processed: Bug#1074649 marked as pending in $i

Processing control commands: > tag -1 pending Bug #1074649 [src:gau2grid] gau2grid: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'? Added tag(s) pending. -- 1074649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074649 Deb

Processed: Bug#1066984 marked as pending in gabedit

Processing control commands: > tag -1 pending Bug #1066984 [src:gabedit] gabedit: FTBFS: Preferences.c:2254:23: error: implicit declaration of function ‘selectionOfDir’; did you mean ‘selctionOfDir’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066984: https://bugs.debian.

Bug#1066984: marked as pending in gabedit

Control: tag -1 pending Hello, Bug #1066984 in gabedit 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: https://salsa.debian.org/debichem-team/gabedit/-/commit/1cd8a54638ed38265ac75a6436

Bug#1077608: marked as done (devicexlib fails to build on ppc64el: MPIF90 not found)

Your message dated Sun, 16 Mar 2025 15:19:25 + with message-id and subject line Bug#1077608: fixed in devicexlib 0.8.5-2 has caused the Debian Bug report #1077608, regarding devicexlib fails to build on ppc64el: MPIF90 not found to be marked as done. This means that you claim that the problem

Bug#1077607: marked as done (devicexlib fails to build on armel/armhf/hppa/m68k/sh4 - invalid memory reference in dp_r4d)

Your message dated Sun, 16 Mar 2025 15:19:25 + with message-id and subject line Bug#1077607: fixed in devicexlib 0.8.5-2 has caused the Debian Bug report #1077607, regarding devicexlib fails to build on armel/armhf/hppa/m68k/sh4 - invalid memory reference in dp_r4d to be marked as done. This

Bug#1100588: encfs: After the upgrade to libtinyxml2-10_10.1.0, encfs no longer works

Dear Maintainer, I can confirm that on my system, a local rebuild of the encfs package, without any manual changes, fixes the problem. -- Toto

Bug#1095364: marked as done (orange-spectroscopy: FTBFS: `np.float_` was removed in the NumPy 2.0 release. Use `np.float64` instead.)

Your message dated Sun, 16 Mar 2025 14:58:52 + with message-id and subject line Bug#1095364: fixed in orange-spectroscopy 0.8.1-2 has caused the Debian Bug report #1095364, regarding orange-spectroscopy: FTBFS: `np.float_` was removed in the NumPy 2.0 release. Use `np.float64` instead. to be

Bug#1100288: marked as done (python-sqlite-migrate: FTBFS: pyproject_hooks._impl.BackendUnavailable: Cannot import 'setuptools.build_meta')

Your message dated Sun, 16 Mar 2025 14:59:33 + with message-id and subject line Bug#1100288: fixed in python-sqlite-migrate 0.1~beta0-3 has caused the Debian Bug report #1100288, regarding python-sqlite-migrate: FTBFS: pyproject_hooks._impl.BackendUnavailable: Cannot import 'setuptools.build_

Bug#1100645: opencv: build-depends on removed package libopenjpip-server

Source: opencv Version: 4.10.0+dfsg-3 Severity: serious Justification: FTBFS in testing, and will in unstable when libopenjpip-server gets decrufted Hello, opencv build-depends on libopenjpip-server, but openjpeg2 dropped this package in its version 2.5.3-2 Samuel -- System Information: Debian

Bug#1100226: jack: FTBFS: pyproject_hooks._impl.BackendUnavailable: Cannot import 'setuptools.build_meta'

Hi. I made some tests. There is a missing build-depends on python3-setuptools, that's all. Thanks.

Bug#1100226: jack: FTBFS: pyproject_hooks._impl.BackendUnavailable: Cannot import 'setuptools.build_meta'

Minor nitpick to myself: The list of packages in my chroot includes eatmydata because at some point I was using it for my archive rebuilds in the past. Maybe I should remove it to avoid confusion, but I don't think it's related with the current failure. I also have fakeroot installed, but I beli

Bug#1100640: database corrupted somehow

Package: reprepro Version: 5.4.6+really5.3.2-1 Severity: serious uploading a source package into my local repo for sid fails with % reprepro includedsc sid iproute2_6.13.0-1.1.dsc BDB1015 references: duplicate sort specified but not supported in database db_open(/var/www/debian/db/references.db:r

Bug#1100282: marked as done (python-pytest-venv: FTBFS: pyproject_hooks._impl.BackendUnavailable: Cannot import 'setuptools.build_meta')

Your message dated Sun, 16 Mar 2025 13:51:36 + with message-id and subject line Bug#1100282: fixed in python-pytest-venv 0.3-5 has caused the Debian Bug report #1100282, regarding python-pytest-venv: FTBFS: pyproject_hooks._impl.BackendUnavailable: Cannot import 'setuptools.build_meta' to be

Bug#1100226: jack: FTBFS: pyproject_hooks._impl.BackendUnavailable: Cannot import 'setuptools.build_meta'

El 16/3/25 a las 13:58, Cord Beermann escribió: Hallo! Du (Santiago Vila) hast geschrieben: Package: src:jack Version: 4~git20241202.3410dc1-1 Severity: serious Tags: ftbfs trixie sid I updated my build-chroot to latest unstable and hadn't any problems. Can you provide information about the i

  1   2   >