Bug#1069357: Fwd: Re: Bug#1069357: cpp-httplib: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test --timeout-m
Messaggio originale Da: Andrea Pappacoda Inviato il: 3 maggio 2024 07:39:59 CEST A: Stuart Prescott Oggetto: Re: Bug#1069357: cpp-httplib: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test --timeout-multiplier=3 --test-args=--gtest_filter=-\*_Online returned exit code 1 Hi Stuart, thanks for the ping. I've been aware of these test failures for a while, but haven't been able to determine the cause of them. They actually ran successfully when I first uploaded the package, but broke after some package upload which I haven't yet identified. It is possible that this is indeed a bug in cpp-httplib, but it has only showed up after an unknown package has been updated in unstable. Citing a previous mail of mine, sent to Bastian Germann the 7th of April: > When I uploaded the package to mentors the tests ran fine in an unstable > chroot, and still do when running them on my local machine (which runs > Testing). I haven't yet tried running them in a chroot which pulls things > from experimental, but if I run them now in an unstable chroot I get a > failure in the SSLClientServerTest.ClientCertPresent test, and a timeout > afterwards. The issue shows up in cpp-httplib's Server::listen() function. Do you have any suggestions regarding how I can "bisect" such an issue? Thanks! P.S. this mail may look broken - I've sent it from my phone.
Processed (with 1 error): Tagging 1069843
Processing commands for cont...@bugs.debian.org: > tag 1069843 + pending Bug #1069843 [src:zarr] zarr: FTBFS: failing tests Added tag(s) pending. > thansk Unknown command or malformed arguments to command. > -- Stopping processing here. Please contact me if you need assistance. -- 1069843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070274: bibledit: The current version currently has partially broken javascript
Source: bibledit Version: 5.1.002-1 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: teusbensc...@debian.org Dear Maintainer, The version of upstream code, included in this package, has broken javascript. This cripples some parts of the program, in particular the verse editor. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1070273: bibledit-cloud: The current version currently has partially broken javascript
Source: bibledit-cloud Version: 5.1.005-1 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: teusbensc...@debian.org Dear Maintainer, The uptream version, included in this package, has partially broken javascript. This cripples some parts of the Bible editors. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Processed: Re: Bug#1070266: nmu: chromium_124.0.6367.118-1
Processing control commands: > tags -1 +moreinfo Bug #1070266 [release.debian.org] nmu: chromium_124.0.6367.118-1 Added tag(s) moreinfo. -- 1070266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070266: marked as done (nmu: chromium_124.0.6367.118-1)
Your message dated Fri, 3 May 2024 07:26:19 +0200 with message-id and subject line Re: Bug#1070266: nmu: chromium_124.0.6367.118-1 has caused the Debian Bug report #1070266, regarding nmu: chromium_124.0.6367.118-1 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 now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1070266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org User: release.debian@packages.debian.org Usertags: binnmu Severity: serious Hello, Snappy 1.2.0-1 was uploaded with broken symbols (see https://bugs.debian.org/1070217). This is fixed in snappy 1.2.0-2, but chromium in sid had already built against the broken version of snappy. Please rebuild chromium against snappy 1.2.0-2 to fix its broken symbol dependencies. Because this chromium release has CVE fixes (and there's 20-something pending CVEs in trixie already that would be fixed by chromium migration), I'm filing this with a higher severity than usual. nmu chromium_124.0.6367.118-1 . ANY . -m 'Rebuild against libsnappy1v5 to fix broken symbols (#1070217)' OpenPGP_0x645D0247C36E7637.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- On 2024-05-02 18:54:20 -0400, Andres Salomon wrote: > Package: release.debian.org > User: release.debian@packages.debian.org > Usertags: binnmu > Severity: serious > > Hello, > > Snappy 1.2.0-1 was uploaded with broken symbols (see > https://bugs.debian.org/1070217). This is fixed in snappy 1.2.0-2, but > chromium in sid had already built against the broken version of snappy. > > Please rebuild chromium against snappy 1.2.0-2 to fix its broken symbol > dependencies. Because this chromium release has CVE fixes (and there's > 20-something pending CVEs in trixie already that would be fixed by chromium > migration), I'm filing this with a higher severity than usual. > > nmu chromium_124.0.6367.118-1 . ANY . -m 'Rebuild against libsnappy1v5 to > fix broken symbols (#1070217)' Scheduled. Cheers -- Sebastian Ramacher--- End Message ---
Bug#1070266: nmu: chromium_124.0.6367.118-1
Control: tags -1 +moreinfo On Fri, May 3, 2024 at 12:57 AM Andres Salomon wrote: > Snappy 1.2.0-1 was uploaded with broken symbols (see > https://bugs.debian.org/1070217). This is fixed in snappy 1.2.0-2, but > chromium in sid had already built against the broken version of snappy. Nope, the symbols were _not_ broken, some were missing as of the 1.1.10-1 version. I have added those back in the 1.2.0-2 package version. > Please rebuild chromium against snappy 1.2.0-2 to fix its broken symbol > dependencies. Because this chromium release has CVE fixes (and there's > 20-something pending CVEs in trixie already that would be fixed by > chromium migration), I'm filing this with a higher severity than usual. It is _not_ needed. the ABI of 1.2.0-1 is not changed in 1.2.0-2, I've even installed the new snappy library version and can still use chromium without problems. Do you experience any odd behaviour? Regards, Laszlo/GCS
Bug#1069357: cpp-httplib: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test --timeout-multiplier=3 --test-arg
Hi Andrea Gentle ping on this bug - there are a few packages lined up for autoremoval and/or can't migrate due to this bug. Looking at the test suite, there seems to be three tests (all within SSLClientServerTest) that now hang on multiple architectures. I don't think this is simply a matter of increasing the timeout on the test as these seem to sit for 15 minutes with no CPU activity. The tests fail not only on arm64 as reported in this bug but also on amd64 and i386, both on salsa-ci and tested locally by me. Skipping these tests by extending the test filter in d/rules is enough to get the package to build; I have not investigated what is leading to these tests failing. --gtest_filter=-*_Online:*ClientCertPresent*:*TrustDirOptional*:*CustomizeServerSSLCtx* Of course skipping failing tests may well build a broken package — I don't know this package well enough to make a judgement call on that, hence I have not NMUd to skip the tests. Please let me know if you think it is indeed appropriate and would like me to NMU the above change. cheers Stuart -- Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386
On Thu, 2 May 2024 19:05:22 +0300 Jussi Pakkanen wrote: > > Along the way I found other bugs, such as bindgen not working at all > out of the box. I filed > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070241 for that. > > All in all this is getting into very deep Debian toolchain magic, of > which I have little knowledge. :( > If real solution for this requires upstream involvement, may be it's worth disabling these tests, until upstream is actually not broken? That would at least move things forward, otherwise it might be stuck for who knows how long? I don't know what's the usual recommended approach for handling such cases. Regards, Shmerl.
Bug#1070272: rust-sequoia-octopus-librnp: FTBFS on armel/armhf: tv_usec: duration.subsec_micros() as libc::suseconds_t, expected `i64`, found `i32`
Source: rust-sequoia-octopus-librnp Version: 1.8.1-4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) User: debian-...@lists.debian.org Usertags: time-t rust-sequoia-octopus-librnp FTBFS on armel/armhf due to the t64 transition: https://buildd.debian.org/status/fetch.php?pkg=rust-sequoia-octopus-librnp=armel=1.8.1-4=1713865768=0 Compiling socket2 v0.5.5 Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=socket2 CARGO_MANIFEST_DIR=/<>/registry/socket2-0.5.5 CARGO_PKG_AUTHORS='Alex Crichton :Thomas de Zeeuw ' CARGO_PKG_DESCRIPTION='Utilities for handling networking sockets with a maximal amount of configuration possible intended. ' CARGO_PKG_HOMEPAGE='https://github.com/rust-lang/socket2' CARGO_PKG_LICENSE='MIT OR Apache-2.0' CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=socket2 CARGO_PKG_REPOSITORY='https://github.com/rust-lang/socket2' CARGO_PKG_RUST_VERSION=1.63 CARGO_PKG_VERSION=0.5.5 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=5 CARGO_PKG_VERSION_PATCH=5 CARGO_PKG_VERSION_PRE='' LD_LIBRARY_PATH='/<>/target/release/deps:/usr/lib' rustc --crate-name socket2 --edition=2021 /<>/registry/socket2-0.5.5/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="all"' -C metadata=2c09183bf02940c5 -C extra-filename=-2c09183bf02940c5 --out-dir /<>/target/armv5te-unknown-linux-gnueabi/release/deps --target armv5te-unknown-linux-gnueabi -L dependency=/<>/target/armv5te-unknown-linux-gnueabi/release/deps -L dependency=/<>/target/release/deps --extern libc=/<>/target/armv5te-unknown-linux-gnueabi/release/deps/liblibc-da839ea29c615453.rmeta --cap-lints warn -C debuginfo=2 --cap-lints warn -C linker=arm-linux-gnueabi-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix /<>=/usr/share/cargo/registry/sequoia-octopus-librnp-1.8.1 --remap-path-prefix /<>/registry=/usr/share/cargo/registry` error[E0308]: mismatched types --> /usr/share/cargo/registry/socket2-0.5.5/src/sys/unix.rs:1137:22 | 1137 | tv_usec: duration.subsec_micros() as libc::suseconds_t, | ^ expected `i64`, found `i32` For more information about this error, try `rustc --explain E0308`. error: could not compile `socket2` due to previous error Caused by: process didn't exit successfully: `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=socket2 CARGO_MANIFEST_DIR=/<>/registry/socket2-0.5.5 CARGO_PKG_AUTHORS='Alex Crichton :Thomas de Zeeuw ' CARGO_PKG_DESCRIPTION='Utilities for handling networking sockets with a maximal amount of configuration possible intended. ' CARGO_PKG_HOMEPAGE='https://github.com/rust-lang/socket2' CARGO_PKG_LICENSE='MIT OR Apache-2.0' CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=socket2 CARGO_PKG_REPOSITORY='https://github.com/rust-lang/socket2' CARGO_PKG_RUST_VERSION=1.63 CARGO_PKG_VERSION=0.5.5 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=5 CARGO_PKG_VERSION_PATCH=5 CARGO_PKG_VERSION_PRE='' LD_LIBRARY_PATH='/<>/target/release/deps:/usr/lib' rustc --crate-name socket2 --edition=2021 /<>/registry/socket2-0.5.5/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="all"' -C metadata=2c09183bf02940c5 -C extra-filename=-2c09183bf02940c5 --out-dir /<>/target/armv5te-unknown-linux-gnueabi/release/deps --target armv5te-unknown-linux-gnueabi -L dependency=/<>/target/armv5te-unknown-linux-gnueabi/release/deps -L dependency=/<>/target/release/deps --extern libc=/<>/target/armv5te-unknown-linux-gnueabi/release/deps/liblibc-da839ea29c615453.rmeta --cap-lints warn -C debuginfo=2 --cap-lints warn -C linker=arm-linux-gnueabi-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix /<>=/usr/share/cargo/registry/sequoia-octopus-librnp-1.8.1 --remap-path-prefix /<>/registry=/usr/share/cargo/registry` (exit status: 1) Andreas
Processed: found 1068209 in 8.9, tagging 1069984, tagging 1039809, found 1063190 in 5.2.1.13040+dfsg-1~exp1 ...
Processing commands for cont...@bugs.debian.org:
> found 1068209 8.9
Bug #1068209 {Done: Nicolas Boulenguez } [dh-ada-library]
libgtkada: FTBFS on all: dh_ada_library: error:
debian/tmp/usr/lib/x86_64-linux-gnu/ada/adalib/gtkada/*.ali are missing
Marked as found in versions dh-ada-library/8.9.
> tags 1069984 + sid trixie experimental
Bug #1069984 [src:alire] alire: Build-depends on NBS package libgnatcoll21-dev
Added tag(s) sid, experimental, and trixie.
> tags 1039809 + experimental
Bug #1039809 {Done: James Valleroy }
[src:php-nikic-fast-route] php-nikic-fast-route: FTBFS with phpunit 10:
make[1]: *** [debian/rules:21: override_dh_auto_test] Error 1
Added tag(s) experimental.
> found 1063190 5.2.1.13040+dfsg-1~exp1
Bug #1063190 {Done: Benjamin Drung } [src:owncloud-client]
owncloud-client: NMU diff for 64-bit time_t transition
Marked as found in versions owncloud-client/5.2.1.13040+dfsg-1~exp1 and
reopened.
> found 1063190 5.2.1.13040+dfsg-1
Bug #1063190 [src:owncloud-client] owncloud-client: NMU diff for 64-bit time_t
transition
Marked as found in versions owncloud-client/5.2.1.13040+dfsg-1.
> fixed 1062322 1.3-3
Bug #1062322 {Done: Lukas Märdian } [src:lib2geom] lib2geom:
NMU diff for 64-bit time_t transition
Marked as fixed in versions lib2geom/1.3-3.
> tags 1062115 + experimental
Bug #1062115 {Done: Steve Langasek } [src:google-glog]
google-glog: NMU diff for 64-bit time_t transition
Added tag(s) experimental.
> fixed 1062125 2.99.18-1
Bug #1062125 {Done: Jeremy Bícha } [src:gimp] gimp: NMU diff
for 64-bit time_t transition
Marked as fixed in versions gimp/2.99.18-1.
> tags 1062981 - sid trixie
Bug #1062981 {Done: Benjamin Drung } [src:thrift] thrift:
NMU diff for 64-bit time_t transition
Removed tag(s) sid and trixie.
> notfound 1066103 1.3.2-1
Bug #1066103 {Done: David Kunz } [icingaweb2-module-cube]
icingaweb2-module-cube: [INTL:de] updated German po file translation
No longer marked as found in versions icingaweb2-module-cube/1.3.2-1.
> fixed 1065787 0.70.1+ds1-3
Bug #1065787 {Done: Emanuele Rocca } [cargo] cargo: needs
re-bootstrapping on armel,armhf for 64-bit time_t
Marked as fixed in versions cargo/0.70.1+ds1-3.
> fixed 1062065 18.2.1+ds-1
Bug #1062065 {Done: Steve Langasek } [src:ceph] ceph: NMU
diff for 64-bit time_t transition
Marked as fixed in versions ceph/18.2.1+ds-1.
> reassign 1059068 src:svt-av1 1.7.0+dfsg-2
Bug #1059068 {Done: Dylan Aïssi } [libsvtav1enc1d1] apt:
fails to resolve dependencies
Bug reassigned from package 'libsvtav1enc1d1' to 'src:svt-av1'.
No longer marked as found in versions svt-av1/1.7.0+dfsg-2.
No longer marked as fixed in versions svt-av1/2.0.0+dfsg-1.
Bug #1059068 {Done: Dylan Aïssi } [src:svt-av1] apt: fails
to resolve dependencies
Marked as found in versions svt-av1/1.7.0+dfsg-2.
> fixed 1059068 2.0.0+dfsg-1
Bug #1059068 {Done: Dylan Aïssi } [src:svt-av1] apt: fails
to resolve dependencies
Marked as fixed in versions svt-av1/2.0.0+dfsg-1.
> tags 1064332 - sid trixie
Bug #1064332 {Done: Benjamin Drung } [src:petsc] petsc: NMU
diff for 64-bit time_t transition
Removed tag(s) sid and trixie.
> fixed 1064264 3.3.0-1
Bug #1064264 {Done: Benjamin Drung } [src:openssl] openssl:
NMU diff for 64-bit time_t transition
Marked as fixed in versions openssl/3.3.0-1.
> fixed 1064264 3.2.1-3
Bug #1064264 {Done: Benjamin Drung } [src:openssl] openssl:
NMU diff for 64-bit time_t transition
Marked as fixed in versions openssl/3.2.1-3.
> tags 1064251 + experimental
Bug #1064251 {Done: Benjamin Drung } [src:nodejs] nodejs:
NMU diff for 64-bit time_t transition
Added tag(s) experimental.
> fixed 1064251 20.12.2+dfsg-1
Bug #1064251 {Done: Benjamin Drung } [src:nodejs] nodejs:
NMU diff for 64-bit time_t transition
Marked as fixed in versions nodejs/20.12.2+dfsg-1.
> tags 1064248 - sid trixie
Bug #1064248 {Done: Benjamin Drung } [src:mutter] mutter:
NMU diff for 64-bit time_t transition
Removed tag(s) trixie and sid.
> fixed 1064248 46.0-1
Bug #1064248 {Done: Benjamin Drung } [src:mutter] mutter:
NMU diff for 64-bit time_t transition
Marked as fixed in versions mutter/46.0-1.
> fixed 1064095 1.14.3+repack-1~exp1
Bug #1064095 {Done: Steve Langasek } [src:hdf5] hdf5: NMU
diff for 64-bit time_t transition
Marked as fixed in versions hdf5/1.14.3+repack-1~exp1.
> tags 1063315 - sid trixie
Bug #1063315 {Done: Steve Langasek } [src:zydis] zydis: NMU
diff for 64-bit time_t transition
Removed tag(s) trixie and sid.
> tags 1063314 - sid trixie
Bug #1063314 {Done: Steve Langasek } [src:zycore-c]
zycore-c: NMU diff for 64-bit time_t transition
Removed tag(s) trixie and sid.
> tags 1063267 - sid trixie
Bug #1063267 {Done: Steve Langasek } [src:vtk9] vtk9: NMU
diff for 64-bit time_t transition
Removed tag(s) trixie and sid.
> fixed 1063267 9.3.0+dfsg1-1~exp4
Bug #1063267 {Done: Steve Langasek } [src:vtk9] vtk9: NMU
diff for 64-bit time_t transition
Marked as fixed in versions vtk9/9.3.0+dfsg1-1~exp4.
> tags 1070254 + sid trixie
Bug #1070254 [src:ktp-text-ui]
Bug#1070270: riseup-vpn: client no longer works due to cert verification problem
Package: riseup-vpn Version: 0.21.11+ds1-5+b1 Severity: grave When attempting to run the bookworm riseup-vpn package, it fails to connect to riseup's servers and gives the following output: 2024/05/01 18:21:23 Error fetching eip v3 json:https://api.black.riseup.net/3/config/eip-service.json My understanding is that this is due to the package failing to be able to verify the current LetsEncrypt cert that host is using. More details at https://0xacab.org/leap/bitmask-vpn/-/issues/768 (supposedly the current upstream snap has this fixed, but I haven't tried it) As this breaks what the package is supposed to do (at least when using riseup as provider, maybe there is a way to point it elsewhere?) I think this is grave. Also I think it might be a good candidate for being fixed in a stable release update. Thanks, -- Matt Taggart m...@lackof.org
Bug#1068390: src:translate-toolkit: unsatisfied build dependency in testing: python3-levenshtein
Update: - python3-levenshtein is now fixed in unstable - python-levenshtein can't migrate because of a long chain that gets back to #1069357 (cpp-httplib: FTBFS on arm64). -- Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Bug#1069195: marked as done (librust-prost-build-dev: FTBFS)
Your message dated Fri, 3 May 2024 00:16:13 +0100 with message-id <8b493f77-cdac-44d7-81d9-319d8d9b0...@debian.org> and subject line Re: librust-prost-build-dev: FTBFS has caused the Debian Bug report #1069195, regarding librust-prost-build-dev: FTBFS 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 now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-prost-build-dev Version: 0.11.9-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Unsatisfiable build-dependency on librust-heck-0.5+default-dev -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmYgJKgACgkQLHwxRsGg ASGRAw/7B4pWiR2c4LDM2ca6emb9CAHkEAVYVDUK4KKzUQ7uvs9oSTE5ZKqRKNT5 r6tcWEp1IitiB5bt7dimQbzkIGODLFT2MdrXnZqrYglUlMBOXfNnvfevGhWuI+FI PWDE1oEvxf2ZvTOsMkEc+ywXbfxJKjw4TeoFA+L9g979U18wmTYRB0RCz2nwVOI5 cFhueAR6+IKEPxUk6zYieyJtCddxwsYKR+7uWrktMpRA4hOFK8hyqhZ17wlJs4+y DD00q2uiUFEK4F3vsj+wCYpbVFRPIkD1p6/rLNZgHDN/EAD5wdDUyH+V9kGGIc6P uqPaheyLiRlRU1kydwH+mnXcW6+w9YzSnqA8X/e+7qmU76KFn1SpXpDF1rk7EBRN ujKY+ji6M53WbmnkedF0AT6dPqkUp7+sJZpd4jyxmb+4fWlxl/MBhr5eXjaIj/rI CFUgIsFuNaHE/GeSeXYfZZh12PXWYUDn+q9KPUIM386fnrhOPeQOIJZuXYzjiE3a zcSjSyXnDdMtGuZRBMTdJMhmAFgic42k7y082v7SO5XovptInLP1tG5lzePCc52f F+KPqxptX95WY/8Y6Y79cFcgJaef3Zp5Bzv3vd64ewOwdfes3oUic9a2EL8da+YR nHuEO6+s2+6WNE8lEelgR29bYXLO78nzSxkIf9rtlgvWc+r41mc= =V4jZ -END PGP SIGNATURE- --- End Message --- --- Begin Message --- On 26/04/2024 14:24, Peter Green wrote: Unsatisfiable build-dependency on librust-heck-0.5+default-dev There seems to be an error here. the version of librust-prost-dev in sid (build-)depends on librust-heck-0.4+default-dev. The version in experimental does depend on librust-heck-0.5+default-dev as it's first choice, but that's fine because version 0.5 of rust-heck is available in experimental. Closing as invalid.--- End Message ---
Bug#1070266: nmu: chromium_124.0.6367.118-1
Package: release.debian.org User: release.debian@packages.debian.org Usertags: binnmu Severity: serious Hello, Snappy 1.2.0-1 was uploaded with broken symbols (see https://bugs.debian.org/1070217). This is fixed in snappy 1.2.0-2, but chromium in sid had already built against the broken version of snappy. Please rebuild chromium against snappy 1.2.0-2 to fix its broken symbol dependencies. Because this chromium release has CVE fixes (and there's 20-something pending CVEs in trixie already that would be fixed by chromium migration), I'm filing this with a higher severity than usual. nmu chromium_124.0.6367.118-1 . ANY . -m 'Rebuild against libsnappy1v5 to fix broken symbols (#1070217)' OpenPGP_0x645D0247C36E7637.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1064170: marked as done (mediastreamer2: NMU diff for 64-bit time_t transition)
Your message dated Thu, 2 May 2024 23:37:12 +0200
with message-id
and subject line Re: mediastreamer2: NMU diff for 64-bit time_t transition
has caused the Debian Bug report #1064170,
regarding mediastreamer2: NMU diff for 64-bit time_t transition
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 now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1064170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mediastreamer2
Version: 1:5.2.0+dfsg-3.1
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
mediastreamer2 as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for mediastreamer2
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru mediastreamer2-5.2.0+dfsg/debian/changelog
mediastreamer2-5.2.0+dfsg/debian/changelog
--- mediastreamer2-5.2.0+dfsg/debian/changelog 2024-01-30 14:30:19.0
+
+++ mediastreamer2-5.2.0+dfsg/debian/changelog 2024-02-18 00:13:01.0
+
@@ -1,3 +1,10 @@
+mediastreamer2 (1:5.2.0+dfsg-3.2) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek Sun, 18 Feb 2024 00:13:01 +
+
mediastreamer2 (1:5.2.0+dfsg-3.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru mediastreamer2-5.2.0+dfsg/debian/control
mediastreamer2-5.2.0+dfsg/debian/control
--- mediastreamer2-5.2.0+dfsg/debian/control2024-01-30 14:30:14.0
+
+++ mediastreamer2-5.2.0+dfsg/debian/control2024-02-18 00:13:01.0
+
@@ -58,7 +58,10 @@
Vcs-Browser:
https://salsa.debian.org/pkg-voip-team/linphone-stack/mediastreamer2
Description: Multimedia streaming engine for telephony
-Package: libmediastreamer13
+Package: libmediastreamer13t64
+Provides: ${t64:Provides}
+Replaces: libmediastreamer13
+Breaks: libmediastreamer13 (<< ${source:Version})
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
@@ -86,7 +89,7 @@
Section: libdevel
Architecture: any
Multi-Arch: same
-Depends: libmediastreamer13 (= ${binary:Version}),
+Depends: libmediastreamer13t64 (= ${binary:Version}),
${misc:Depends},
# the .pc file mentions these 2, so a Depends: is needed
# also the headers reference files from these 2
diff -Nru mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13.install
mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13.install
--- mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13.install 2024-01-30
14:20:36.0 +
+++ mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13.install 1970-01-01
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/libmediastreamer.so.*
diff -Nru
Bug#1070236: [Pkg-samba-maint] Bug#1070236: python3-samba: SyntaxError during configuration phase of package on upgrade
02.05.2024 23:36, Michael Biebl wrote: Control: reopen -1 Control: found -1 2:4.19.6+dfsg-3 On Thu, 2 May 2024 11:58:59 -0700 "Leo L. Schwab" wrote: Did you fix this one, too? --- Performing actions... Setting up python3-samba (2:4.19.6+dfsg-2) ... File "/usr/lib/python3/dist-packages/samba/ms_schema_markdown.py", line 25 try ^ SyntaxError: expected ':' I also get File "/usr/lib/python3/dist-packages/samba/ms_schema_markdown.py", line 27 except ImportError e: ^ SyntaxError: invalid syntax All this is fixed in -3. /mjt -- GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24. New key: rsa4096/61AD3D98ECDF2C8E 9D8B E14E 3F2A 9DD7 9199 28F1 61AD 3D98 ECDF 2C8E Old key: rsa2048/457CE0A0804465C5 6EE1 95D1 886E 8FFB 810D 4324 457C E0A0 8044 65C5 Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt
Processed: severity of 1070236 is serious
Processing commands for cont...@bugs.debian.org: > severity 1070236 serious Bug #1070236 [python3-samba] python3-samba: SyntaxError during configuration phase of package on upgrade Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1070236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070246: marked as done (libayatana-appindicator version of Debian package does not match the upstream version)
Your message dated Thu, 02 May 2024 20:36:04 + with message-id and subject line Bug#1070246: fixed in libayatana-appindicator 0.5.93+really-1 has caused the Debian Bug report #1070246, regarding libayatana-appindicator version of Debian package does not match the upstream version 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 now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1070246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libayatana-appindicator Severity: serious Version: 0.5.92-1 Version: 0.5.93-1 The package of libayatana-appindicator on Debian is not building from the right orig tarball as indicated on the package version. Both package versions on Debian 12 and testing (versions 0.5.92-1 and 0.5.93-1) are actually version 0.5.90 of upstream. $ apt-cache policy libayatana-appindicator3-1 libayatana-appindicator3-1: Installed: 0.5.92-1 Candidate: 0.5.92-1 Version table: *** 0.5.92-1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 100 /var/lib/dpkg/status $ zcat /usr/share/doc/libayatana-appindicator3-1/changelog.gz|head Overview of changes in libayatana-appindicator 0.5.90 - Mono bindings: Change namespace from ayatana-appindicator-sharp3 to ayatana-appindicator3-sharp (and similar). - Port to CMake. - Default to GTK+-3.0 as default build flavour. - Add Travis CI configuration. - Add --keep-env option to dbus-test-runner calls. Allows propagating e.g. a build HOME into the DBus test environment. See how on the upstream changelog file it says version "0.5.90" I have triple checked this by comparing the orig.tar.gz tarball from the Debian packages VS the ones at https://github.com/AyatanaIndicators/libayatana-appindicator/tags And the version shipped on Debian (both for 0.5.92-1 and 0.5.93-1) is actually the upstream 0.5.90 version Please fix this Thanks --- End Message --- --- Begin Message --- Source: libayatana-appindicator Source-Version: 0.5.93+really-1 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of libayatana-appindicator, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated libayatana-appindicator package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 May 2024 21:27:44 +0200 Source: libayatana-appindicator Architecture: source Version: 0.5.93+really-1 Distribution: unstable Urgency: medium Maintainer: Ayatana Packagers Changed-By: Mike Gabriel Closes: 1070246 Changes: libayatana-appindicator (0.5.93+really-1) unstable; urgency=medium . * Upstream re-release of 0.5.93 tarball. (Closes: #1070246). - The previous 0.5.93 orig tarball was actually a 0.5.90 release. Thanks to Carlos Alberto Lopez Perez for spotting this. * debian/copyright: + Update copyright attributions. * debian/libayatana-appindicator3-1.symbols: + Update symbols. Private symbol removed. * debian/control: + Switch from gobject-introspection to gobject-introspection-bin. Thanks, lintian. + Bump Standards-Version to 4.7.0. No changes needed. Checksums-Sha1: f263a348b11d1e4643c7064e038464a65a73b0d8 3108 libayatana-appindicator_0.5.93+really-1.dsc fddebde0ada948ce9f0ad3b288f90ddfe6701438 138256 libayatana-appindicator_0.5.93+really.orig.tar.gz c9ab546238dcf23bea98aaa54d95cae0c1549f22 833 libayatana-appindicator_0.5.93+really.orig.tar.gz.asc 9585ae38738da4b0ab6ee89164f355ce00d90e17 17940 libayatana-appindicator_0.5.93+really-1.debian.tar.xz 3143b4906bd6e09b641796956f832b25f96ee4e4 18908 libayatana-appindicator_0.5.93+really-1_source.buildinfo Checksums-Sha256: 992b96adf0a6d45ee60ae8e7f36e7f0d68581aa61eaf40dbd6eb5562d01d5f41 3108 libayatana-appindicator_0.5.93+really-1.dsc 645099374bd83c0548d3df8a64a8974cccb3b626ae75d5976a1791087bf4e8f3 138256 libayatana-appindicator_0.5.93+really.orig.tar.gz 61b7076005d262b35a3c5897badc2061e9ee83d9c8e692bc539d08c5762163a4 833 libayatana-appindicator_0.5.93+really.orig.tar.gz.asc
Bug#1067661: condor: unable to install condor on armhf in Ubuntu
My apologies. I cut and pasted the wrong bug number. However, thank you for the patch. I have included it in the upcoming 23.6.2 release in Debian. I have also incorporated this patch upstream. -- Tim Theisen (he, him, his) Release Manager HTCondor & Open Science Grid Center for High Throughput Computing Department of Computer Sciences University of Wisconsin - Madison 4261 Computer Sciences and Statistics 1210 W Dayton St Madison, WI 53706-1685 +1 608 265 5736
Processed: ruby-rack: diff for NMU version 2.2.7-1.1
Processing control commands: > tags 1064516 + patch Bug #1064516 [src:ruby-rack] ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146 Added tag(s) patch. > tags 1064516 + pending Bug #1064516 [src:ruby-rack] ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146 Added tag(s) pending. -- 1064516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1064516: ruby-rack: diff for NMU version 2.2.7-1.1
Control: tags 1064516 + patch
Control: tags 1064516 + pending
Dear maintainer,
I've prepared an NMU for ruby-rack (versioned as 2.2.7-1.1) and uploaded
it to DELAYED/2. Please feel free to tell me if I should cancel it.
cu
Adrian
diffstat for ruby-rack-2.2.7 ruby-rack-2.2.7
changelog | 10 +
patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch | 51 ++
patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch | 46 +
patches/0003-Fixing-ReDoS-in-header-parsing.patch | 30 +
patches/series |3
5 files changed, 140 insertions(+)
diff -Nru ruby-rack-2.2.7/debian/changelog ruby-rack-2.2.7/debian/changelog
--- ruby-rack-2.2.7/debian/changelog 2023-07-10 17:32:41.0 +0300
+++ ruby-rack-2.2.7/debian/changelog 2024-05-02 22:55:26.0 +0300
@@ -1,3 +1,13 @@
+ruby-rack (2.2.7-1.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * CVE-2024-25126: ReDoS in Content Type header parsing
+ * CVE-2024-26141: Reject Range headers which are too large
+ * CVE-2024-26146: ReDoS in Accept header parsing
+ * Closes: #1064516
+
+ -- Adrian Bunk Thu, 02 May 2024 22:55:26 +0300
+
ruby-rack (2.2.7-1) unstable; urgency=medium
* Team Upload
diff -Nru ruby-rack-2.2.7/debian/patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch ruby-rack-2.2.7/debian/patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch
--- ruby-rack-2.2.7/debian/patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch 1970-01-01 02:00:00.0 +0200
+++ ruby-rack-2.2.7/debian/patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch 2024-05-02 22:55:26.0 +0300
@@ -0,0 +1,51 @@
+From e5c0e03f70624433d7132a5eb039f5f04787d20c Mon Sep 17 00:00:00 2001
+From: Jean Boussier
+Date: Wed, 6 Dec 2023 18:32:19 +0100
+Subject: Avoid 2nd degree polynomial regexp in MediaType
+
+---
+ lib/rack/media_type.rb | 13 +
+ 1 file changed, 9 insertions(+), 4 deletions(-)
+
+diff --git a/lib/rack/media_type.rb b/lib/rack/media_type.rb
+index 41937c99..7fc1e39d 100644
+--- a/lib/rack/media_type.rb
b/lib/rack/media_type.rb
+@@ -4,7 +4,7 @@ module Rack
+ # Rack::MediaType parse media type and parameters out of content_type string
+
+ class MediaType
+-SPLIT_PATTERN = %r{\s*[;,]\s*}
++SPLIT_PATTERN = /[;,]/
+
+ class << self
+ # The media type (type/subtype) portion of the CONTENT_TYPE header
+@@ -15,7 +15,11 @@ module Rack
+ # http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7
+ def type(content_type)
+ return nil unless content_type
+-content_type.split(SPLIT_PATTERN, 2).first.tap &:downcase!
++if type = content_type.split(SPLIT_PATTERN, 2).first
++ type.rstrip!
++ type.downcase!
++ type
++end
+ end
+
+ # The media type parameters provided in CONTENT_TYPE as a Hash, or
+@@ -27,9 +31,10 @@ module Rack
+ return {} if content_type.nil?
+
+ content_type.split(SPLIT_PATTERN)[1..-1].each_with_object({}) do |s, hsh|
++ s.strip!
+ k, v = s.split('=', 2)
+-
+- hsh[k.tap(&:downcase!)] = strip_doublequotes(v)
++ k.downcase!
++ hsh[k] = strip_doublequotes(v)
+ end
+ end
+
+--
+2.30.2
+
diff -Nru ruby-rack-2.2.7/debian/patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch ruby-rack-2.2.7/debian/patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch
--- ruby-rack-2.2.7/debian/patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch 1970-01-01 02:00:00.0 +0200
+++ ruby-rack-2.2.7/debian/patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch 2024-05-02 22:55:26.0 +0300
@@ -0,0 +1,46 @@
+From e4a334bba45d1f66499973d65ba4db2679129153 Mon Sep 17 00:00:00 2001
+From: Aaron Patterson
+Date: Tue, 13 Feb 2024 13:34:34 -0800
+Subject: Return an empty array when ranges are too large
+
+If the sum of the requested ranges is larger than the file itself,
+return an empty array. In other words, refuse to respond with any bytes.
+
+[CVE-2024-26141]
+---
+ lib/rack/utils.rb | 3 +++
+ test/spec_utils.rb | 4
+ 2 files changed, 7 insertions(+)
+
+diff --git a/lib/rack/utils.rb b/lib/rack/utils.rb
+index c8e61ea1..72700503 100644
+--- a/lib/rack/utils.rb
b/lib/rack/utils.rb
+@@ -380,6 +380,9 @@ module Rack
+ end
+ ranges << (r0..r1) if r0 <= r1
+ end
++
++ return [] if ranges.map(&:size).sum > size
++
+ ranges
+ end
+
+diff --git a/test/spec_utils.rb b/test/spec_utils.rb
+index 90676258..6b069914 100644
+--- a/test/spec_utils.rb
b/test/spec_utils.rb
+@@ -590,6 +590,10 @@ describe Rack::Utils, "cookies" do
+ end
+
+ describe Rack::Utils, "byte_range" do
++ it "returns an empty list if the sum of the ranges is too large" do
++
Bug#968415: susv4: Patch
Package: susv4 Version: 7.20180621 Followup-For: Bug #968415 X-Debbugs-Cc: mlukow...@sdf.org --- debian/susv4.postinst.orig 2024-05-02 15:56:25.243665232 -0400 +++ debian/susv4.postinst 2024-05-02 15:56:34.133076612 -0400 @@ -8,7 +8,7 @@ wget -P $TEMPDIR http://pubs.opengroup.org/onlinepubs/9699919799/download/susv4-2018.tar.bz2 echo Verifying SHA512 checksum... -SHA512SUM="c356d8b9b311201bef8900add7aab18b822af0e6e1a0c63b141c7c5f5e401bf25f39dcf9976577e934b7bfc939574c965ebefd63fef7a57ad6feb875e237fd7d" +SHA512SUM="2484d24d19b9731808c61219b61d63cdf4d8dff6498fb4655478b76808a583064a5cfbcfcf18f1d27c56e03a6b47cc6833f94483784ec29059bef063724c2567" [ x"$(sha512sum $TEMPDIR/susv4-2018.tar.bz2 | cut -f1 -d\ )" = x"$SHA512SUM" ] || (rm -rf $TEMPDIR; exit 1) echo Untarring... -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages susv4 depends on: ii bzip2 1.0.8-5.1 ii wget 1.24.5-1 susv4 recommends no packages. susv4 suggests no packages. -- no debconf information
Bug#968415: susv4: Patch with new sha512sum
Package: susv4 Version: 7.20180621 Followup-For: Bug #968415 X-Debbugs-Cc: mlukow...@sdf.org Dear Maintainer, --- debian/susv4/DEBIAN/postinst.orig 2024-05-02 15:49:52.972725058 -0400 +++ debian/susv4/DEBIAN/postinst2024-05-02 15:50:01.506839488 -0400 @@ -8,7 +8,7 @@ wget -P $TEMPDIR http://pubs.opengroup.org/onlinepubs/9699919799/download/susv4-2018.tar.bz2 echo Verifying SHA512 checksum... -SHA512SUM="c356d8b9b311201bef8900add7aab18b822af0e6e1a0c63b141c7c5f5e401bf25f39dcf9976577e934b7bfc939574c965ebefd63fef7a57ad6feb875e237fd7d" +SHA512SUM="2484d24d19b9731808c61219b61d63cdf4d8dff6498fb4655478b76808a583064a5cfbcfcf18f1d27c56e03a6b47cc6833f94483784ec29059bef063724c2567" [ x"$(sha512sum $TEMPDIR/susv4-2018.tar.bz2 | cut -f1 -d\ )" = x"$SHA512SUM" ] || (rm -rf $TEMPDIR; exit 1) echo Untarring... -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages susv4 depends on: ii bzip2 1.0.8-5.1 ii wget 1.24.5-1 susv4 recommends no packages. susv4 suggests no packages. -- no debconf information
Bug#1070254: ktp-text-ui FTBFS: undefined reference to `snappy::RawCompress(char const*, unsigned long, char*, unsigned long*)'
Hej, Am Donnerstag, 2. Mai 2024, 15:24:07 CEST schrieb Helmut Grohne: > Source: ktp-text-ui > Version: 22.12.3-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in > the past) > > ktp-text-ui fails to build from source in unstable on amd64. The [...] > | /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.10 /usr/bin/ld: > | /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5.15.15: undefined > | reference to `snappy::RawCompress(char const*, unsigned long, > | char*, unsigned long*)' collect2: error: ld returned 1 exit status That looks like it's https://bugs.debian.org/cgi-bin/bugreport.cgi? bug=1070254 for which a fix has been uploaded. I guess trying to rebuild it tomorrow will fix this build error. -- Med vänliga hälsningar Patrick Franz
Bug#1065956: marked as done (mtd-utils: FTBFS on arm{el,hf}: FAIL mtdlib_test (exit status: 17))
Your message dated Thu, 02 May 2024 19:12:17 +
with message-id
and subject line Bug#1065956: fixed in mtd-utils 1:2.2.0-2
has caused the Debian Bug report #1065956,
regarding mtd-utils: FTBFS on arm{el,hf}: FAIL mtdlib_test (exit status: 17)
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 now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1065956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065956
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mtd-utils
Version: 1:2.1.6-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=mtd-utils=armel=1%3A2.1.6-1%2Bb2=1709994938=0
[ FAILED ] test_mtd_get_dev_info1
[==] tests: 17 test(s) run.
[ PASSED ] 0 test(s).
[ FAILED ] tests: 17 test(s), listed below:
[ FAILED ] test_libmtd_open
[ FAILED ] test_mtd_is_bad
[ FAILED ] test_mtd_mark_bad
[ FAILED ] test_mtd_lock
[ FAILED ] test_mtd_unlock
[ FAILED ] test_mtd_is_locked
[ FAILED ] test_mtd_regioninfo
[ FAILED ] test_mtd_erase_multi
[ FAILED ] test_mtd_erase
[ FAILED ] test_mtd_read
[ FAILED ] test_mtd_write_nooob
[ FAILED ] test_mtd_write_withoob
[ FAILED ] test_mtd_read_oob
[ FAILED ] test_mtd_write_oob
[ FAILED ] test_mtd_dev_present
[ FAILED ] test_mtd_get_info
[ FAILED ] test_mtd_get_dev_info1
17 FAILED TEST(S)
FAIL mtdlib_test (exit status: 17)
Testsuite summary for mtd-utils 2.1.6
# TOTAL: 2
# PASS: 0
# SKIP: 0
# XFAIL: 0
# FAIL: 2
# XPASS: 0
# ERROR: 0
See ./test-suite.log
Please report to linux-...@lists.infradead.org
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: mtd-utils
Source-Version: 1:2.2.0-2
Done: Bastian Germann
We believe that the bug you reported is fixed in the latest version of
mtd-utils, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bastian Germann (supplier of updated mtd-utils package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 02 May 2024 18:37:36 +
Source: mtd-utils
Architecture: source
Version: 1:2.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Bastian Germann
Closes: 1065956
Changes:
mtd-utils (1:2.2.0-2) unstable; urgency=medium
.
* QA upload
* Skip tests on armel and armhf due to broken mocking (Closes: #1065956)
Checksums-Sha1:
29df0ad524b88ed5ba0a40c67633711dbc3ef28e 1973 mtd-utils_2.2.0-2.dsc
66eb07b1f763b2e5c5e53d477ab270b92d4f75a7 8948 mtd-utils_2.2.0-2.debian.tar.xz
69c3bbc6ee748e90d73a1a3d2586efcacd134f6b 5919
mtd-utils_2.2.0-2_source.buildinfo
Checksums-Sha256:
28ee35a1a35e4054f83eef12750c908eeccfb17f3cab462918159ba538b60205 1973
mtd-utils_2.2.0-2.dsc
7d259b8342965e21002e67a0ef4d10e970af224e18e8359eab720512bcc708f7 8948
mtd-utils_2.2.0-2.debian.tar.xz
562f3fb843a73c91b3d932211f53efc0914b197fbbd0f6d5260691c4a03736ab 5919
mtd-utils_2.2.0-2_source.buildinfo
Files:
13d52e2edb353b046e453a8993b2c505 1973 utils optional mtd-utils_2.2.0-2.dsc
d4dd74eded51666096c7d95400087f84 8948 utils optional
mtd-utils_2.2.0-2.debian.tar.xz
becce2c0404f9d4ce948cf772d9de174 5919 utils optional
mtd-utils_2.2.0-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmYz3k8QHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFIzlC/4oH20ua3lxfKgyWlGEmOWl80OgKqudboeO
g1D0z8OjgH9LZ6papfAyN0wF+hEW6nKenNlVVQg59dCsBV1tC27rTi98eK/CgYKI
0DiZvURTmcixx5C9xIu169VmVYTgFVia8xTnwRXV9wQb0G38VcTpuvVLpUHKklFl
nYNEz4aVeDIri51wOS5JUtEIPJs08rA5ySq7vHHbsx3Zq4/aqkt5HUGp0+uvZjrc
5TfWopH+VOZZrcbZFyRS22BkDd9Ex9do+EQ9dmED8UIjESrZHvgs4PbJFEjI/9v8
u4ZJfHMZHU4tawNPVZbFekKZFfS1zY9jJeoVbkg+pXAYG1PPjIuDD+zuD6sQBsQP
Bug#1070256: libcxx-serial FTBFS with the nocheck build profile
Source: libcxx-serial Version: 1.2.1-5 Severity: serious Justification: nocheck ftbfs is rc since trixie Tags: ftbfs trixie sid libcxx-serial fails to build from source when enabling the nocheck build profile. I think the relevant part is: | -- catkin 0.8.10 | -- BUILD_SHARED_LIBS is on | CMake Error at /usr/share/catkin/cmake/test/tests.cmake:21 (message): | () is not available when tests are not enabled. The CMake code should only | use it inside a conditional block which checks that testing is enabled: | | if(CATKIN_ENABLE_TESTING) | | (...) | | endif() | | Call Stack (most recent call first): | tests/CMakeLists.txt:20 (catkin_add_gtest) | | | -- Configuring incomplete, errors occurred! | cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt | ==> CMakeCache.txt <== Helmut
Bug#1070254: ktp-text-ui FTBFS: undefined reference to `snappy::RawCompress(char const*, unsigned long, char*, unsigned long*)'
Source: ktp-text-ui Version: 22.12.3-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) ktp-text-ui fails to build from source in unstable on amd64. The relevant log probably is: | [ 76%] Linking CXX executable ktp-text-ui | cd /<>/obj-x86_64-linux-gnu/app && /usr/bin/cmake -E cmake_link_script CMakeFiles/ktp-text-ui.dir/link.txt --verbose=1 | /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Werror=init-self -Wvla -Wdate-time -Wsuggest-override -Wlogical-op -Wl,--enable-new-dtags -Wl,-z,relro "CMakeFiles/ktp-text-ui.dir/ktp-text-ui_autogen/mocs_compilation.cpp.o" "CMakeFiles/ktp-text-ui.dir/main.cpp.o" "CMakeFiles/ktp-text-ui.dir/telepathy-chat-ui.cpp.o" "CMakeFiles/ktp-text-ui.dir/chat-window.cpp.o" "CMakeFiles/ktp-text-ui.dir/chat-tab.cpp.o" "CMakeFiles/ktp-text-ui.dir/emoticon-text-edit-action.cpp.o" "CMakeFiles/ktp-text-ui.dir/emoticon-text-edit-selector.cpp.o" "CMakeFiles/ktp-text-ui.dir/invite-contact-dialog.cpp.o" -o ktp-text-ui -Wl,-rpath,/<>/obj-x86_64-linux-gnu/lib:/<>/obj-x86_64-linux-gnu/image-sharer: /usr/lib/x86_64-linux-gnu/libQt5WebEngine.so.5.15.15 ../lib/libktpchat.so /usr/lib/x86_64-linux-gnu/libKF5PeopleWidgets.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5Emoticons.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKTpWidgets.so.22.12.3 /usr/lib/x86_64-linux-gnu/libKTpModels.so.22.12.3.abi1 /usr/lib/x86_64-linux-gnu/libKF5NotifyConfig.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5TextWidgets.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5SonnetUi.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5SonnetCore.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKTpLogger.so.22.12.3.abi1 /usr/lib/x86_64-linux-gnu/libKTpCommonInternals.so.22.12.3.abi1 /usr/lib/x86_64-linux-gnu/libKF5Wallet.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5.107.0 /usr/lib/x86_64-linux-gnu/libtelepathy-logger-qt.so.0.9.80.0 /usr/lib/x86_64-linux-gnu/libtelepathy-qt5.so.0.0.9.8 /usr/lib/x86_64-linux-gnu/libQt5WebEngineWidgets.so.5.15.15 /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5.15.15 /usr/lib/x86_64-linux-gnu/libQt5WebChannel.so.5.15.10 /usr/lib/x86_64-linux-gnu/libQt5Positioning.so.5.15.10 /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5.15.10 /usr/lib/x86_64-linux-gnu/libQt5QmlModels.so.5.15.10 /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5.15.10 /usr/lib/x86_64-linux-gnu/libQt5PrintSupport.so.5.15.10 ../image-sharer/libktpimagesharer.so /usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5KIOGui.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5Service.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5Solid.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5Completion.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5ConfigGui.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5Codecs.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5Auth.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5AuthCore.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5Archive.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5.107.0 /usr/lib/x86_64-linux-gnu/libX11.so /usr/lib/x86_64-linux-gnu/libQt5Concurrent.so.5.15.10 /usr/lib/x86_64-linux-gnu/libKTpOTR.so.22.12.3 /usr/lib/x86_64-linux-gnu/libtelepathy-qt5.so.0.0.9.8 /usr/lib/x86_64-linux-gnu/libQt5Network.so.5.15.10 /usr/lib/x86_64-linux-gnu/libQt5Xml.so.5.15.10 -fPIC /usr/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5People.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5.107.0 /usr/lib/x86_64-linux-gnu/libKF5I18n.so.5.107.0 /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.15.10 /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.15.10 /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.15.10 /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.10 | /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5.15.15: undefined reference to `snappy::RawCompress(char const*, unsigned long, char*, unsigned long*)' | collect2: error: ld returned 1 exit status | make[3]: *** [app/CMakeFiles/ktp-text-ui.dir/build.make:220: app/ktp-text-ui] Error 1 | make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' | make[2]: *** [CMakeFiles/Makefile2:1633: app/CMakeFiles/ktp-text-ui.dir/all] Error 2 | make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' | make[1]: *** [Makefile:149: all] Error 2 |
Bug#1067661: marked as done (condor: unable to install condor on armhf in Ubuntu)
Your message dated Thu, 2 May 2024 13:40:28 -0500
with message-id <0a5dbd46-f97b-466e-beba-880208495...@cs.wisc.edu>
and subject line Re: htcondor: preemption not working if NEGOTIATOR_INTERVAL is
set
has caused the Debian Bug report #1067661,
regarding condor: unable to install condor on armhf in Ubuntu
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 now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1067661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: condor
Severity: wishlist
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Dear Maintainer,
The package d/control file hardcodes dependencies to libssl, libscitokens0 and
libvomsapi1v5 that were renamed to t64 suffix due to the time_t transition. I
have applied a proposed fix[1] to generate the library name in
override_dh_gencontrol and validated that the package builds and installs in
sid chroot.
In Ubuntu, the attached patch was applied to achieve the following:
* Don't hard-code dependency on a shared library (LP: #2058880).
Thanks for considering the patch.
[1] https://lists.ubuntu.com/archives/ubuntu-devel/2024-March/042948.html
-- System Information:
Debian Release: trixie/sid
APT prefers mantic-updates
APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500,
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-25-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru condor-23.4.0+dfsg/debian/control condor-23.4.0+dfsg/debian/control
--- condor-23.4.0+dfsg/debian/control 2024-03-23 09:07:04.0 +1300
+++ condor-23.4.0+dfsg/debian/control 2024-03-25 15:56:46.0 +1300
@@ -25,6 +24,7 @@
libpcre2-dev,
libpq-dev,
libscitokens-dev,
+ libssl-dev,
libsqlite3-dev,
libsystemd-dev,
libvirt-dev,
@@ -59,12 +59,10 @@
libkrb5-3,
libkrb5support0,
libmunge2,
- libssl3t64,
- libscitokens0,
- libvomsapi1v5,
net-tools,
libjs-bootstrap,
libjs-jquery,
+ ${lib:Depends},
${misc:Depends},
${perl:Depends},
${python3:Depends},
diff -Nru condor-23.4.0+dfsg/debian/rules condor-23.4.0+dfsg/debian/rules
--- condor-23.4.0+dfsg/debian/rules 2024-03-23 09:07:04.0 +1300
+++ condor-23.4.0+dfsg/debian/rules 2024-03-25 15:56:46.0 +1300
@@ -132,3 +132,10 @@
override_dh_auto_test:
+override_dh_gencontrol:
+ dh_gencontrol -- \
+ -Vlib:Depends="$(foreach package, libscitokens libssl, \
+ $(shell dpkg-query -W -f '$${Depends}' $(package)-dev \
+ | sed -E
's/.*($(package)[[:alnum:].-]+).*/\1,/' )) \
+ $(shell dpkg-query -W -f '$${Depends}' voms-dev \
+ | sed -E
's/.*(libvomsapi[[:alnum:].-]+).*/\1,/' )"
--- End Message ---
--- Begin Message ---
I am sorry that I did not see this bug for a very long time. It was
filed against and old version of HTCondor. I'll close this now. Feel
free to open another bug report if this is still a problem.
...Tim Theisen
--
Tim Theisen (he, him, his)
Release Manager
HTCondor & Open Science Grid
Center for High Throughput Computing
Department of Computer Sciences
University of Wisconsin - Madison
4261 Computer Sciences and Statistics
1210 W Dayton St
Madison, WI 53706-1685
+1 608 265 5736--- End Message ---
Bug#1069350: marked as done (netavark: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)
Your message dated Thu, 02 May 2024 18:37:22 +
with message-id
and subject line Bug#1069350: fixed in netavark 1.4.0-4.1
has caused the Debian Bug report #1069350,
regarding netavark: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo
build returned exit code 101
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 now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1069350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netavark
Version: 1.4.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64
Hi,
During a rebuild of all packages in sid, your package failed to build
on arm64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> printf '{"package":"%s","files":{}}\n' $(sha256sum Cargo.toml | grep -Po
> '^\S+') > debian/cargo-checksum.json;
> make[1]: Leaving directory '/<>'
>dh_auto_configure -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=4'] []
> ['-j4'] 0
> debian cargo wrapper: rust_type, gnu_type: aarch64-unknown-linux-gnu,
> aarch64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into
> /<>/debian/cargo_registry/
>dh_auto_build -O--buildsystem=cargo
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=4'] []
> ['-j4'] 0
> debian cargo wrapper: rust_type, gnu_type: aarch64-unknown-linux-gnu,
> aarch64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose',
> '-j4', '--target', 'aarch64-unknown-linux-gnu'],) {}
> error: failed to select a version for the requirement `sysctl = "^0.4"`
> candidate versions found which didn't match: 0.5.5
> location searched: directory source `/<>/debian/cargo_registry`
> (which is replacing registry `crates-io`)
> required by package `netavark v1.4.0 (/<>)`
> perhaps a crate was updated and forgotten to be re-vendored?
> dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
The full build log is available from:
http://qa-logs.debian.net/2024/04/20/netavark_1.4.0-4_unstable-arm64.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: netavark
Source-Version: 1.4.0-4.1
Done: Peter Michael Green
We believe that the bug you reported is fixed in the latest version of
netavark, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Peter Michael Green (supplier of updated netavark package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 02 May 2024 17:08:20 +
Source: netavark
Architecture: source
Version: 1.4.0-4.1
Distribution: unstable
Urgency: medium
Maintainer: Reinhard Tartler
Changed-By: Peter Michael Green
Closes: 1064580 1069350
Changes:
netavark (1.4.0-4.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Apply upstream patch for new version of rust-nix (Closes: #1064580)
* Relax cargo dependency on sysctl crate (Closes: #1069350)
Checksums-Sha1:
de0efccf3d31b33ab89c90017dcec0c99d812195 2700 netavark_1.4.0-4.1.dsc
856657734fe21e706ec2b561669cb4623f020496 5568 netavark_1.4.0-4.1.debian.tar.xz
c3e9e9efa0857ac878c040c3a71c9750b3f49667 23666
netavark_1.4.0-4.1_source.buildinfo
Checksums-Sha256:
Bug#1067299: marked as done (ada-reference-manual: FTBFS: debian/rules:31: /usr/share/ada/debian_packaging.mk: No such file or directory)
Your message dated Thu, 02 May 2024 18:04:25 + with message-id and subject line Bug#1067299: fixed in ada-reference-manual 1:2020.1commit85143dcb-5 has caused the Debian Bug report #1067299, regarding ada-reference-manual: FTBFS: debian/rules:31: /usr/share/ada/debian_packaging.mk: No such file or directory 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 now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1067299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ada-reference-manual Version: 1:2020.1commit85143dcb-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240319 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules clean > dh /usr/share/ada/debian_packaging.mk --sourcedirectory=build > dh: error: Unknown sequence /usr/share/ada/debian_packaging.mk (choose from: > binary binary-arch binary-indep build build-arch build-indep clean install > install-arch install-indep) > debian/rules:31: /usr/share/ada/debian_packaging.mk: No such file or directory > make: *** [debian/rules:34: /usr/share/ada/debian_packaging.mk] Error 25 The full build log is available from: http://qa-logs.debian.net/2024/03/19/ada-reference-manual_2020.1commit85143dcb-4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240319;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240319=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: ada-reference-manual Source-Version: 1:2020.1commit85143dcb-5 Done: Nicolas Boulenguez We believe that the bug you reported is fixed in the latest version of ada-reference-manual, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Boulenguez (supplier of updated ada-reference-manual package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 May 2024 16:37:23 + Source: ada-reference-manual Architecture: source Version: 1:2020.1commit85143dcb-5 Distribution: unstable Urgency: medium Maintainer: Ludovic Brenta Changed-By: Nicolas Boulenguez Closes: 1067299 Changes: ada-reference-manual (1:2020.1commit85143dcb-5) unstable; urgency=medium . * * Stop pretending that DOCUMENTS is not hardcoded. * Standards-Version (no changes). * Fix the format of a patch header. * Prevent new compiler warnings from breaking Debian builds. * Update copyright years. * Build-Depend: dh-ada-library for packaging.mk. Closes: #1067299. Checksums-Sha1: b7adbc80518dad83cd64719fbabbe1e4bc138ec4 2435 ada-reference-manual_2020.1commit85143dcb-5.dsc 7f702c1cc7ba8676ea0c874dc147ec143a65fc76 7176 ada-reference-manual_2020.1commit85143dcb-5.debian.tar.xz b9f608a9cf2e464af725011e826e85cf78b8f8bc 8507 ada-reference-manual_2020.1commit85143dcb-5_source.buildinfo Checksums-Sha256: 24323ec133c3bf7eb29fb833fb186ac4bd723f3faa9128bdf5e243640b38a704 2435 ada-reference-manual_2020.1commit85143dcb-5.dsc c808ebde028b992e1d5de607a5b4e7d17f7e80b8f5021ad34d7f8bfd0916e979 7176 ada-reference-manual_2020.1commit85143dcb-5.debian.tar.xz 8835428fc8f57d38ff2761b37d56fd9477a0c180cab99ad793efe99f83cec4d7 8507 ada-reference-manual_2020.1commit85143dcb-5_source.buildinfo Files: 92d1a701047bd650baf6d1612552b4cc 2435 doc optional ada-reference-manual_2020.1commit85143dcb-5.dsc 4f2517661965709726fe6a22f1d6fcb9 7176 doc optional ada-reference-manual_2020.1commit85143dcb-5.debian.tar.xz
Processed: merge accidental duplicates
Processing commands for cont...@bugs.debian.org: > merge 1070247 1070250 Bug #1070247 [src:telepathy-glib] telepathy-glib: Fails to build with glib 2.80 Bug #1070250 [src:telepathy-glib] telepathy-glib: Fails to build with glib 2.80 Merged 1070247 1070250 > End of message, stopping processing here. Please contact me if you need assistance. -- 1070247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070247 1070250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070252: sublime-music: playback broken by libmpv 0.38
Package: sublime-music
Version: 0.12.0-1
Severity: critical
Forwarded: https://github.com/sublime-music/sublime-music/issues/462
Using libmpv2 0.38, the playback is broken an results in the following trace:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/sublime_music/dbus/manager.py", line 24,
in wrapper
function(*args)
File "/usr/lib/python3/dist-packages/sublime_music/app.py", line 629, in
on_play_pause
self.play_song(self.app_config.state.current_song_index)
File "/usr/lib/python3/dist-packages/sublime_music/app.py", line 1415, in
play_song
song_details_future.add_done_callback(
File "/usr/lib/python3/dist-packages/sublime_music/adapters/manager.py", line
140, in add_done_callback
fn(self, *args)
File "/usr/lib/python3/dist-packages/sublime_music/app.py", line 1416, in
lambda f: do_play_song(self.song_playing_order_token, f.result())
^^^
File "/usr/lib/python3/dist-packages/sublime_music/dbus/manager.py", line 24,
in wrapper
function(*args)
File "/usr/lib/python3/dist-packages/sublime_music/app.py", line 1166, in
do_play_song
self.player_manager.play_media(
File "/usr/lib/python3/dist-packages/sublime_music/players/manager.py", line
188, in play_media
current_player.play_media(uri, progress, song)
File "/usr/lib/python3/dist-packages/sublime_music/players/mpv.py", line 137,
in play_media
self.mpv.command(
File "/usr/lib/python3/dist-packages/mpv.py", line 1233, in command
_mpv_command_node(self.handle, ppointer, out)
File "/usr/lib/python3/dist-packages/mpv.py", line 148, in raise_for_ec
raise ex
ValueError: ('Invalid value for mpv parameter', -4, (,
, ))
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau
⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org
⠈⠳⣄
Bug#1070250: telepathy-glib: Fails to build with glib 2.80
Source: telepathy-glib Severity: serious Version: 0.24.2-0.3 Tags: ftbfs upstream X-Debbugs-CC: bi...@debian.org Please cherry-pick the glib commit from https://gitlab.freedesktop.org/telepathy/telepathy-glib/-/commits/master to fix the build with glib 2.80 (currently in experimental but will be uploaded to Unstable as soon as the t64 transitions clear out). There is also a commit there to port examples from Python 2 to 3. Thank you, Jeremy Bícha
Bug#1070227: Fails to start with undefined symbol
Thanks. This is a duplicate (https://bugs.debian.org/1070217), but I'm leaving it open to ensure that chromium doesn't accidentally migrate to trixie while built against a broken libsnappy. And as a reminder that we'll probably need a binNMU once snappy is fixed, unless upstream has a new release On Thu, 2 May 2024 10:57:25 +0200 Yuri D'Elia wrote: Package: chromium Version: 124.0.6367.78-1 Severity: grave The current package in debian unstable fails to start with the following missing symbol: $ chromium grep: warning: stray \ before - /usr/lib/chromium/chromium: symbol lookup error: /usr/lib/chromium/chromium: undefined symbol: _ZN6snappy11RawCompressEPKcmPcPm -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chromium depends on: ii chromium-common124.0.6367.78-1 ii libasound2t64 1.2.11-1+b1 ii libatk-bridge2.0-0t64 2.52.0-1 ii libatk1.0-0t64 2.52.0-1 ii libatomic1 14-20240429-1 ii libatspi2.0-0t64 2.52.0-1 ii libc6 2.38-6 ii libcairo2 1.18.0-3+b1 ii libcups2t642.4.7-1.2+b1 ii libdbus-1-31.14.10-4+b1 ii libdouble-conversion3 3.3.0-1+b1 ii libdrm22.4.120-2 ii libevent-2.1-7t64 2.1.12-stable-8.1+b3 ii libexpat1 2.6.2-1 ii libflac12t64 1.4.3+ds-2.1 ii libfontconfig1 2.15.0-1.1 ii libfreetype6 2.13.2+dfsg-1+b4 ii libgbm124.1.0~rc1-1 ii libgcc-s1 14-20240429-1 ii libglib2.0-0t642.78.4-7 ii libgtk-3-0t64 3.24.41-4 ii libjpeg62-turbo1:2.1.5-3 ii libjsoncpp25 1.9.5-6+b2 ii liblcms2-2 2.14-2+b1 ii libminizip1t64 1:1.3.dfsg-3.1 ii libnspr4 2:4.35-1.1+b1 ii libnss32:3.99-1 ii libopenh264-7 2.4.1+dfsg-1 ii libopenjp2-7 2.5.0-2+b3 ii libopus0 1.4-1+b1 ii libpango-1.0-0 1.52.1+ds-1 ii libpng16-16t64 1.6.43-5 ii libpulse0 16.1+dfsg1-5 OpenPGP_0x645D0247C36E7637.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1070228: marked as done (dependency: libsnappy1v5: After update from 1.1.10-1+b1 to 1.2.0-1 symbol lookup error)
Your message dated Thu, 02 May 2024 17:52:34 + with message-id and subject line Bug#1070217: fixed in snappy 1.2.0-2 has caused the Debian Bug report #1070217, regarding dependency: libsnappy1v5: After update from 1.1.10-1+b1 to 1.2.0-1 symbol lookup error 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 now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1070217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libqt5webenginecore5 Version: 5.15.15+dfsg-3 Severity: important Dear Maintainer, after updating libsnapp1v5 from version 1.1.10-1+b1 to 1.2.0-1 the following error occurs when using libQt5WebEngineCore.so.5 (by kmail or akregator, e.g.): symbol lookup error: /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5: undefined symbol: _ZN6snappy11RawCompressEPKcmPcPm Workaround: downgrading libsnappy1v5 to previous version [Maybe libqt5webenginecore5 5.15.15+dfsg-3 should insist on libsnappy1v5 < 1.2.] -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.22 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libqt5webenginecore5 depends on: ii libasound2t641.2.11-1+b1 ii libc62.37-19 ii libdbus-1-3 1.14.10-4+b1 ii libevent-2.1-7t642.1.12-stable-8.1+b3 ii libexpat12.6.2-1 ii libfontconfig1 2.15.0-1.1 ii libfreetype6 2.13.2+dfsg-1+b4 ii libgcc-s114-20240429-1 ii libglib2.0-0t64 2.78.4-7 ii libharfbuzz-subset0 8.3.0-2+b1 ii libharfbuzz0b8.3.0-2+b1 ii libicu72 72.1-4+b1 ii libjpeg62-turbo 1:2.1.5-3 ii liblcms2-2 2.14-2+b1 ii libminizip1t64 1:1.3.dfsg-3.1 ii libnspr4 2:4.35-1.1+b1 ii libnss3 2:3.99-1 ii libopenjp2-7 2.5.0-2+b3 ii libopus0 1.4-1+b1 ii libpng16-16t64 1.6.43-5 ii libqt5core5t64 [qtbase-abi-5-15-10] 5.15.10+dfsg-7.2+b1 ii libqt5gui5t645.15.10+dfsg-7.2+b1 ii libqt5network5t645.15.10+dfsg-7.2+b1 ii libqt5positioning5 5.15.10+dfsg-3+b2 ii libqt5qml5 5.15.10+dfsg-2+b2 ii libqt5quick5 5.15.10+dfsg-2+b2 ii libqt5webchannel55.15.10-2+b2 ii libqt5webengine-data 5.15.15+dfsg-3 ii libre2-1020230301-3+b1 ii libsnappy1v5 1.1.10-1+b1 ii libstdc++6 14-20240429-1 ii libvpx8 1.13.1-2+b1 ii libwebp7 1.3.2-0.4+b1 ii libwebpdemux21.3.2-0.4+b1 ii libwebpmux3 1.3.2-0.4+b1 ii libx11-6 2:1.8.7-1+b1 ii libx11-xcb1 2:1.8.7-1+b1 ii libxcb1 1.17.0-1 ii libxcomposite1 1:0.4.5-1+b1 ii libxdamage1 1:1.1.6-1+b1 ii libxext6 2:1.3.4-1+b1 ii libxfixes3 1:6.0.0-2+b1 ii libxml2 2.9.14+dfsg-1.3+b3 ii libxrandr2 2:1.5.4-1 ii libxslt1.1 1.1.35-1+b1 ii libxtst6 2:1.2.3-1.1+b1 ii zlib1g 1:1.3.dfsg-3.1 libqt5webenginecore5 recommends no packages. libqt5webenginecore5 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: snappy Source-Version: 1.2.0-2 Done: Laszlo Boszormenyi (GCS) We believe that the bug you reported is fixed in the latest version of snappy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian
Bug#1070217: marked as done (chromium: Symbol lookup error with libsnappy1v5>=1.2.0)
Your message dated Thu, 02 May 2024 17:52:34 + with message-id and subject line Bug#1070217: fixed in snappy 1.2.0-2 has caused the Debian Bug report #1070217, regarding chromium: Symbol lookup error with libsnappy1v5>=1.2.0 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 now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1070217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chromium Version: 124.0.6367.78-1 Severity: important X-Debbugs-Cc: jet...@jethron.id.au Dear Maintainer, Attempting to run chromium fails with: /usr/lib/chromium/chromium: symbol lookup error: /usr/lib/chromium/chromium: undefined symbol: _ZN6snappy11RawCompressEPKcmPcPm I suspect this is due to the upload of 1.2.0-1 of libsnappy1v5 on 2024-05-01. The closest symbol I can find in the newer libsnappy.so.* files is _ZN6snappy11RawCompressEPKcmPcPmNS_18CompressionOptionsE Thank you for your work packaging chromium! Kind regards, Jethro -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.8.7-1-siduction-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chromium depends on: ii chromium-common 124.0.6367.78-1 ii libasound2t641.2.11-1+b1 ii libatk-bridge2.0-0t642.52.0-1 ii libatk1.0-0t64 2.52.0-1 ii libatomic1 14-20240429-1 ii libatspi2.0-0t64 2.52.0-1 ii libc62.37-19 ii libcairo21.18.0-3+b1 ii libcups2t64 2.4.7-1.2+b1 ii libdbus-1-3 1.14.10-4+b1 ii libdouble-conversion33.3.0-1+b1 ii libdrm2 2.4.120-2 ii libevent-2.1-7t642.1.12-stable-8.1+b3 ii libexpat12.6.2-1 ii libflac12t64 1.4.3+ds-2.1 ii libfontconfig1 2.15.0-1.1 ii libfreetype6 2.13.2+dfsg-1+b4 ii libgbm1 24.0.6-1+b1 ii libgcc-s114-20240429-1 ii libglib2.0-0t64 2.78.4-7 ii libgtk-3-0t643.24.41-4 ii libjpeg62-turbo 1:2.1.5-3 ii libjsoncpp25 1.9.5-6+b2 ii liblcms2-2 2.14-2+b1 ii libminizip1t64 1:1.3.dfsg-3.1 ii libnspr4 2:4.35-1.1+b1 ii libnss3 2:3.99-1 ii libopenh264-72.4.1+dfsg-1 ii libopenjp2-7 2.5.0-2+b3 ii libopus0 1.4-1+b1 ii libpango-1.0-0 1.52.1+ds-1 ii libpng16-16t64 1.6.43-5 ii libpulse016.1+dfsg1-5 ii libsnappy1v5 1.2.0-1 ii libstdc++6 14-20240429-1 ii libwoff1 1.0.2-2+b1 ii libx11-6 2:1.8.7-1+b1 ii libxcb1 1.17.0-1 ii libxcomposite1 1:0.4.5-1+b1 ii libxdamage1 1:1.1.6-1+b1 ii libxext6 2:1.3.4-1+b1 ii libxfixes3 1:6.0.0-2+b1 ii libxkbcommon01.6.0-1+b1 ii libxml2 2.9.14+dfsg-1.3+b3 ii libxnvctrl0 535.171.04-1 ii libxrandr2
Bug#1070247: telepathy-glib: Fails to build with glib 2.80
Source: telepathy-glib Severity: serious Version: 0.24.2-0.3 Tags: ftbfs upstream X-Debbugs-CC: bi...@debian.org Please cherry-pick the glib commit from https://gitlab.freedesktop.org/telepathy/telepathy-glib/-/commits/master to fix the build with glib 2.80 (currently in experimental but will be uploaded to Unstable as soon as the t64 transitions clear out). There is also a commit there to port examples from Python 2 to 3. Thank you, Jeremy Bícha
Bug#1070246: libayatana-appindicator version of Debian package does not match the upstream version
Source: libayatana-appindicator Severity: serious Version: 0.5.92-1 Version: 0.5.93-1 The package of libayatana-appindicator on Debian is not building from the right orig tarball as indicated on the package version. Both package versions on Debian 12 and testing (versions 0.5.92-1 and 0.5.93-1) are actually version 0.5.90 of upstream. $ apt-cache policy libayatana-appindicator3-1 libayatana-appindicator3-1: Installed: 0.5.92-1 Candidate: 0.5.92-1 Version table: *** 0.5.92-1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 100 /var/lib/dpkg/status $ zcat /usr/share/doc/libayatana-appindicator3-1/changelog.gz|head Overview of changes in libayatana-appindicator 0.5.90 - Mono bindings: Change namespace from ayatana-appindicator-sharp3 to ayatana-appindicator3-sharp (and similar). - Port to CMake. - Default to GTK+-3.0 as default build flavour. - Add Travis CI configuration. - Add --keep-env option to dbus-test-runner calls. Allows propagating e.g. a build HOME into the DBus test environment. See how on the upstream changelog file it says version "0.5.90" I have triple checked this by comparing the orig.tar.gz tarball from the Debian packages VS the ones at https://github.com/AyatanaIndicators/libayatana-appindicator/tags And the version shipped on Debian (both for 0.5.92-1 and 0.5.93-1) is actually the upstream 0.5.90 version Please fix this Thanks
Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386
On Thu, 2 May 2024 at 01:48, Shmerl wrote: > > Ubuntu fixed it with this patch: > > https://launchpadlibrarian.net/715235929/meson_1.3.2-1_1.3.2-1ubuntu1.diff.gz > > > > Can this fix be added to Debian? Meson has been stuck without > moving to testing for a very long time and now it seems to be > stalling Mesa in result too. I looked into this and the answer is sadly no. That patch explicitly adds -lc to every link which breaks other tests that depend on it not being there. These tests have been added after Ubuntu made that change, so they won't show up there. They will once they update Meson to a newer version. Along the way I found other bugs, such as bindgen not working at all out of the box. I filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070241 for that. All in all this is getting into very deep Debian toolchain magic, of which I have little knowledge. :(
Bug#1070237: wsclean: error while loading shared libraries: libradler.so: cannot open shared object file
Package: wsclean Version: 3.4-1+b2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: offri...@gmail.com Dear Maintainer, There is something wrong with the packaging of WSClean; running WSClean fails with the following error: wsclean: error while loading shared libraries: libradler.so: cannot open shared object file: No such file or directory Radler is a component of wsclean that is normally compiled along wsclean, linked into a static library and subsequently linked into the wsclean binary. I think that Debian's WSClean package builds radler as a shared object, but does not ship the library. Thanks, André -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_NL.UTF-8, LC_CTYPE=en_NL.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wsclean depends on: ii libboost-filesystem1.83.0 1.83.0-2+b2 ii libc6 2.37-18 ii libcasa-casa7 3.5.0-2+b3 ii libcasa-fits7 3.5.0-2+b3 ii libcasa-measures7 3.5.0-2+b3 ii libcasa-ms7 3.5.0-2+b3 ii libcasa-tables7 3.5.0-2+b3 ii libcfitsio10t64 [libcfitsio10] 4.3.1-1.1+b1 ii libfftw3-double33.3.10-1+b1 ii libfftw3-single33.3.10-1+b1 ii libgcc-s1 14-20240330-1 ii libgsl272.7.1+dfsg-6+b1 ii libhdf5-103-1 1.10.10+repack-3+b1 ii libhdf5-cpp-103-1 1.10.10+repack-3+b1 ii libstdc++6 14-20240330-1 wsclean recommends no packages. Versions of packages wsclean suggests: pn wsclean-dev -- no debconf information
Bug#1068209: marked as done (libgtkada: FTBFS on all: dh_ada_library: error: debian/tmp/usr/lib/x86_64-linux-gnu/ada/adalib/gtkada/*.ali are missing)
Your message dated Thu, 02 May 2024 15:04:45 + with message-id and subject line Bug#1068209: fixed in dh-ada-library 9.4 has caused the Debian Bug report #1068209, regarding libgtkada: FTBFS on all: dh_ada_library: error: debian/tmp/usr/lib/x86_64-linux-gnu/ada/adalib/gtkada/*.ali are missing 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 now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1068209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libgtkada Version: 24.0.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org mkdir -p debian/tmp/usr/share/doc/gtkada/gtkada_ug cp --reflink=auto -aftdebian/tmp/usr/share/doc/gtkada/gtkada_ug \ docs/gtkada_ug/_build/html/* \ docs/gtkada_ug/_build/latex/GtkAda.pdf make[1]: Leaving directory '/<>' dh_install -i dh_installdocs -i dh_sphinxdoc -i dh_installchangelogs -i dh_installexamples -i dh_installman -i dh_ada_library -i dh_ada_library: error: debian/tmp/usr/lib/x86_64-linux-gnu/ada/adalib/gtkada/*.ali are missing Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: dh-ada-library Source-Version: 9.4 Done: Nicolas Boulenguez We believe that the bug you reported is fixed in the latest version of dh-ada-library, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Boulenguez (supplier of updated dh-ada-library package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 May 2024 12:39:30 + Source: dh-ada-library Architecture: source Version: 9.4 Distribution: unstable Urgency: medium Maintainer: Nicolas Boulenguez Changed-By: Nicolas Boulenguez Closes: 1068209 Changes: dh-ada-library (9.4) unstable; urgency=medium . * Only report missing files for processed packages. Closes: #1068209. Add regression test. Checksums-Sha1: e38ae9a30238f8adfb30402dc52da1b41b06 1722 dh-ada-library_9.4.dsc d9f316ad08258a8e5c12a2a4cddfd6090c36731d 22596 dh-ada-library_9.4.tar.xz Checksums-Sha256: 201096d7c762e46f539f04745037dd0ba35b752fd5faffa9d4defbc9788cc0bf 1722 dh-ada-library_9.4.dsc bd2563be4750da0ecbb55d74e4b58370270049ab8a69c0da805cbf4a7fd28f13 22596 dh-ada-library_9.4.tar.xz Files: 0c966056047bb848fcf8c8cab34bc767 1722 devel optional dh-ada-library_9.4.dsc 0bf7416c2fa555a2dc59d69534685ee4 22596 devel optional dh-ada-library_9.4.tar.xz -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEEawm/6zYhqkfTAKHtFHKayZgPCdIFAmYzo9ITHG5pY29sYXNA ZGViaWFuLm9yZwAKCRAUcprJmA8J0trWD/9hWiVspA/Hgn/ctR/kkmObV9ycaUPD z1h6nnB+Vb3YQqvTwrev0O6QgIRNXyTgiKEOxBGUX7B0kF/YKGvYrz1+INMIBtgV uV46LRsHrjFdmPTb76r86RY344uRzwIYOg6UqXtI1ygtuM9Gx+KlH7kfoiZ6N9gy /E2pttqUaTVvzdGSvKGA+twDQPsqpIdR71o92+ml7/9euGOEPcP0fNgxnPYWL0L0 IhHqDYrIdYK9z0mruvcDxQoJsM/TKO7vBtk1crspXXdY0FPj/C+FZ8LyAmTKetXe l8VW+Qt96ZDWfRpr+7s20KEu85sUmDL+zSn3A6L5/Z+IOVp9a11b2yH1I4M8rewT iYn5rtMEn3C738fZJx9rEnj/2BkVAF/inBV8faaDfKrylkd8R9RpjV85CF01Be+L cszegTNpGV6iEY7ytS+PemN7y4yBS8tcJ+KUPuGVR3SFhBMXztajrv1HKQAwqBaw 678+dMohFOQhBjKjc5PdZjYBeCjznrGsZ+9zSZlF5dEoORfWOF9CMw9bdyMrjqWU T1VjnCL37ld5cQ03xL98PJsxwTGJYFxeQnfMatZZOlZEL+thnM1oIB2tz0WZopnB HmK5j13j/Q9+kkR7XwyuHzT3UcgJtwq5OwXL+w4pNHRko84nQ3WAVZtzBfvmIAxa y5EOmgQ2NUOeNQ== =eE2e -END PGP SIGNATURE- pgp9gPFNOllAn.pgp Description: PGP signature --- End Message ---
Bug#1070217: chromium: Symbol lookup error with libsnappy1v5>=1.2.0
Work-around for affected users: Download and install libsnappy1v5_1.1.10-1+b1_amd64.deb from https://snapshot.debian.org/archive/debian/20240210T223313Z/pool/main/s/snappy/ Temporary protection: % cat /etc/apt/preferences.d/libsnappy Explanation: Debian#1070217: chromium: Symbol lookup error with libsnappy1v5>=1.2.0 Explanation: https://bugs.debian.org/1070217 Package: libsnappy1v5 Pin: version * Pin-Priority: -3 Please remove once bug is fixed. Thanks, -- Martin
Bug#1070172: Exception when invoked without options
Hi,
On Thu, May 02, 2024 at 03:55:53PM +0200, Guido Günther wrote:
> Hi,
> On Wed, May 01, 2024 at 12:27:41PM +0200, Guido Günther wrote:
> > Package: gcovr
> > Version: 7.2-1
> > Severity: grave
> >
> > Hi,
> > invoking gcovr 7.2 in an empty directory fails like
> >
> > $ gcovr
> > --
> >GCC Code Coverage Report
> > Traceback (most recent call last):
> > File "/usr/bin/gcovr", line 1972, in
> > print_text_report(covdata)
> > File "/usr/bin/gcovr", line 822, in print_text_report
> > OUTPUT.write("Directory: "+options.root+"\n")
> > ~^
> > TypeError: can only concatenate str (not "NoneType") to str
> >
> >
> > This makes meson think gcovr is not available, e.g.:
> >
> >
> > https://gitlab.gnome.org/World/Phosh/phosh-mobile-settings/-/jobs/3839480#L3265
> >
> > I've marked this as grave as it breaks CI pipelines.
>
> Just had a closer look. It seems verson 3.2 instead of 7.2 got
> imported. I'll propose a fix.
Uploaded to delayed/3. MR is at
https://salsa.debian.org/debian/gcovr/-/merge_requests/5
Cheers,
-- Guido
>
> Cheers,
> -- Guido
>
> >
> > Cheers,
> > -- Guido
> >
> >
> > -- System Information:
> > Debian Release: trixie/sid
> > APT prefers testing
> > APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
> > 'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1,
> > 'experimental')
> > Architecture: amd64 (x86_64)
> > Foreign Architectures: arm64
> >
> > Kernel: Linux 6.6.15-amd64 (SMP w/12 CPU threads; PREEMPT)
> > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE
> > not set
> > Shell: /bin/sh linked to /usr/bin/dash
> > Init: systemd (via /run/systemd/system)
> > LSM: AppArmor: enabled
> >
> > Versions of packages gcovr depends on:
> > ii python33.11.6-1
> > ii python3-pkg-resources 68.1.2-2
> >
> > gcovr recommends no packages.
> >
> > gcovr suggests no packages.
> >
> > -- no debconf information
Bug#1070172: Exception when invoked without options
Hi,
On Wed, May 01, 2024 at 12:27:41PM +0200, Guido Günther wrote:
> Package: gcovr
> Version: 7.2-1
> Severity: grave
>
> Hi,
> invoking gcovr 7.2 in an empty directory fails like
>
> $ gcovr
> --
>GCC Code Coverage Report
> Traceback (most recent call last):
> File "/usr/bin/gcovr", line 1972, in
> print_text_report(covdata)
> File "/usr/bin/gcovr", line 822, in print_text_report
> OUTPUT.write("Directory: "+options.root+"\n")
> ~^
> TypeError: can only concatenate str (not "NoneType") to str
>
>
> This makes meson think gcovr is not available, e.g.:
>
>
> https://gitlab.gnome.org/World/Phosh/phosh-mobile-settings/-/jobs/3839480#L3265
>
> I've marked this as grave as it breaks CI pipelines.
Just had a closer look. It seems verson 3.2 instead of 7.2 got
imported. I'll propose a fix.
Cheers,
-- Guido
>
> Cheers,
> -- Guido
>
>
> -- System Information:
> Debian Release: trixie/sid
> APT prefers testing
> APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
> 'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1,
> 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: arm64
>
> Kernel: Linux 6.6.15-amd64 (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages gcovr depends on:
> ii python33.11.6-1
> ii python3-pkg-resources 68.1.2-2
>
> gcovr recommends no packages.
>
> gcovr suggests no packages.
>
> -- no debconf information
Processed: reassign bugs
Processing commands for cont...@bugs.debian.org: > reassign 1068209 dh-ada-library Bug #1068209 [src:libgtkada] libgtkada: FTBFS on all: dh_ada_library: error: debian/tmp/usr/lib/x86_64-linux-gnu/ada/adalib/gtkada/*.ali are missing Bug reassigned from package 'src:libgtkada' to 'dh-ada-library'. No longer marked as found in versions libgtkada/24.0.0-2. Ignoring request to alter fixed versions of bug #1068209 to the same values previously set > affects 1068209 libgtkada libtemplates-parser Bug #1068209 [dh-ada-library] libgtkada: FTBFS on all: dh_ada_library: error: debian/tmp/usr/lib/x86_64-linux-gnu/ada/adalib/gtkada/*.ali are missing Added indication that 1068209 affects libgtkada and libtemplates-parser > End of message, stopping processing here. Please contact me if you need assistance. -- 1068209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070053: marked as done (prometheus-process-exporter: FTBFS: cannot use status.UIDs[1] (variable of type uint64) as string value in argument to strconv.ParseInt)
Your message dated Thu, 02 May 2024 12:50:47 + with message-id and subject line Bug#1070053: fixed in prometheus-process-exporter 0.8.2-1 has caused the Debian Bug report #1070053, regarding prometheus-process-exporter: FTBFS: cannot use status.UIDs[1] (variable of type uint64) as string value in argument to strconv.ParseInt 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 now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1070053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:prometheus-process-exporter Version: 0.7.10-4 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem=golang --builddirectory=/<>/build dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=/<>/build dh_autoreconf -O--buildsystem=golang -O--builddirectory=/<>/build dh_auto_configure -O--buildsystem=golang -O--builddirectory=/<>/build debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build -- -tags "" -ldflags " -X github.com/prometheus/common/version.Version=0.7.10 -X github.com/prometheus/common/version.Revision=0.7.10-4 -X github.com/prometheus/common/version.Branch=debian/sid -X github.com/prometheus/common/version.BuildUser=team+pkg...@tracker.debian.org -X github.com/prometheus/common/version.BuildDate=20240321-15:19:54 -X github.com/prometheus/common/version.GoVersion=go1.22.2" cd build && go install -trimpath -v -p 2 -tags -ldflags " -X github.com/prometheus/common/version.Version=0.7.10 -X github.com/prometheus/common/version.Revision=0.7.10-4 -X github.com/prometheus/common/version.Branch=debian/sid -X github.com/prometheus/common/version.BuildUser=team+pkg...@tracker.debian.org -X github.com/prometheus/common/version.BuildDate=20240321-15:19:54 -X github.com/prometheus/common/version.GoVersion=go1.22.2" github.com/ncabatoff/process-exporter github.com/ncabatoff/process-exporter/cmd/process-exporter github.com/ncabatoff/process-exporter/collector github.com/ncabatoff/process-exporter/config github.com/ncabatoff/process-exporter/proc internal/goarch internal/unsafeheader internal/cpu internal/abi internal/bytealg internal/chacha8rand internal/coverage/rtcov internal/godebugs internal/goexperiment internal/goos runtime/internal/atomic runtime/internal/math runtime/internal/sys runtime/internal/syscall internal/itoa math/bits runtime math unicode/utf8 internal/race sync/atomic unicode cmp slices encoding internal/nettrace log/internal unicode/utf16 container/list crypto/internal/alias crypto/subtle crypto/internal/boring/sig vendor/golang.org/x/crypto/cryptobyte/asn1 vendor/golang.org/x/crypto/internal/alias google.golang.org/protobuf/internal/flags google.golang.org/protobuf/internal/set internal/reflectlite sync internal/testlog internal/bisect errors sort strconv io internal/oserror reflect syscall internal/syscall/unix time internal/poll internal/fmtsort internal/safefilepath internal/syscall/execenv path strings io/fs os bytes bufio encoding/binary fmt path/filepath github.com/prometheus/procfs/internal/util golang.org/x/sys/unix github.com/ncabatoff/process-exporter flag github.com/ncabatoff/go-seq/seq encoding/hex github.com/prometheus/procfs/internal/fs context vendor/golang.org/x/net/dns/dnsmessage internal/godebug internal/singleflight internal/intern net/netip runtime/cgo regexp/syntax regexp log encoding/base64 encoding/json net os/user compress/flate hash hash/crc32 compress/gzip crypto crypto/cipher crypto/internal/boring crypto/internal/randutil math/rand math/big crypto/rand crypto/aes crypto/des crypto/internal/edwards25519/field crypto/internal/nistec/fiat github.com/prometheus/procfs embed crypto/internal/nistec crypto/ecdh crypto/elliptic crypto/internal/bigmod crypto/internal/boring/bbig crypto/sha512 encoding/asn1 github.com/ncabatoff/process-exporter/proc # github.com/ncabatoff/process-exporter/proc src/github.com/ncabatoff/process-exporter/proc/read.go:397:40: cannot use status.UIDs[1] (variable of type uint64) as string value in argument to strconv.ParseInt crypto/internal/edwards25519 vendor/golang.org/x/crypto/cryptobyte crypto/ed25519 crypto/hmac crypto/md5 crypto/ecdsa crypto/rc4 crypto/rsa crypto/sha1 crypto/sha256 crypto/dsa crypto/x509/pkix encoding/pem net/url vendor/golang.org/x/crypto/chacha20 vendor/golang.org/x/crypto/internal/poly1305 crypto/x509
Bug#1070217: chromium: Symbol lookup error with libsnappy1v5>=1.2.0
Same issue with nextcloud (package nextcloud-desktop): $ nextcloud nextcloud: symbol lookup error: /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5: undefined symbol: _ZN6snappy11RawCompressEPKcmPcPm
Bug#1067369: fixed in cowsql 1.15.6-1
(Touching bug to reset AUTORM countdown.) signature.asc Description: This is a digitally signed message part
Processed: affects 1070217
Processing commands for cont...@bugs.debian.org: > affects 1070217 chromium Bug #1070217 [libsnappy1v5] chromium: Symbol lookup error with libsnappy1v5>=1.2.0 Bug #1070228 [libsnappy1v5] dependency: libsnappy1v5: After update from 1.1.10-1+b1 to 1.2.0-1 symbol lookup error Added indication that 1070217 affects chromium Added indication that 1070228 affects chromium > thanks Stopping processing here. Please contact me if you need assistance. -- 1070217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070217 1070228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069504: marked as done (libosmo-sccp: FTBFS on armhf: build-dependency not installable: libosmo-netif-dev (>= 1.2.0))
Your message dated Thu, 2 May 2024 11:30:36 +0200 with message-id <1f540de6-e4f6-5b97-e7f3-e3a75d2e6...@debian.org> and subject line Re: libosmo-sccp: FTBFS on armhf: build-dependency not installable: libosmo-netif-dev (>= 1.2.0) has caused the Debian Bug report #1069504, regarding libosmo-sccp: FTBFS on armhf: build-dependency not installable: libosmo-netif-dev (>= 1.2.0) 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 now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069504 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libosmo-sccp Version: 1.6.0+dfsg1-3.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf Hi, During a rebuild of all packages in sid, your package failed to build on armhf. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), > pkg-config, libosmocore-dev (>= 1.7.0), autoconf, automake, libtool, doxygen, > libdpkg-perl, libosmo-netif-dev (>= 1.2.0), libsctp-dev, build-essential, > fakeroot > Filtered Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), > pkg-config, libosmocore-dev (>= 1.7.0), autoconf, automake, libtool, doxygen, > libdpkg-perl, libosmo-netif-dev (>= 1.2.0), libsctp-dev, build-essential, > fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [609 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [774 B] > Get:5 copy:/<>/apt_archive ./ Packages [806 B] > Fetched 2189 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: libosmo-netif-dev (>= 1.2.0) but > it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2024/04/20/libosmo-sccp_1.6.0+dfsg1-3.1_unstable-armhf.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Version: 1.6.0+dfsg1-4 libosmo-sccp has been removed from all 32-bit architectures Andreas--- End Message ---
Processed: fix severity
Processing commands for cont...@bugs.debian.org: > severity 1070228 serious Bug #1070228 [libsnappy1v5] dependency: libsnappy1v5: After update from 1.1.10-1+b1 to 1.2.0-1 symbol lookup error Bug #1070217 [libsnappy1v5] chromium: Symbol lookup error with libsnappy1v5>=1.2.0 Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' > -- Stopping processing here. Please contact me if you need assistance. -- 1070217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070217 1070228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign
Processing control commands: > reassign -1 libsnappy1v5 Bug #1070228 [libqt5webenginecore5] dependency: libsnappy1v5: After update from 1.1.10-1+b1 to 1.2.0-1 symbol lookup error Bug reassigned from package 'libqt5webenginecore5' to 'libsnappy1v5'. No longer marked as found in versions qtwebengine-opensource-src/5.15.15+dfsg-3. Ignoring request to alter fixed versions of bug #1070228 to the same values previously set > forcemerge -1 1070217 Bug #1070228 [libsnappy1v5] dependency: libsnappy1v5: After update from 1.1.10-1+b1 to 1.2.0-1 symbol lookup error Bug #1070228 [libsnappy1v5] dependency: libsnappy1v5: After update from 1.1.10-1+b1 to 1.2.0-1 symbol lookup error Marked as found in versions snappy/1.2.0-1. Bug #1070217 [libsnappy1v5] chromium: Symbol lookup error with libsnappy1v5>=1.2.0 Severity set to 'important' from 'serious' Merged 1070217 1070228 > affects 1070217 libqt5webenginecore5 kmail Bug #1070217 [libsnappy1v5] chromium: Symbol lookup error with libsnappy1v5>=1.2.0 Bug #1070228 [libsnappy1v5] dependency: libsnappy1v5: After update from 1.1.10-1+b1 to 1.2.0-1 symbol lookup error Added indication that 1070217 affects libqt5webenginecore5 and kmail Added indication that 1070228 affects libqt5webenginecore5 and kmail -- 1070217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070217 1070228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070217: abi change upstream
looks like it was an abi change upstream https://github.com/google/snappy/commit/ 766d24c95e345d4d06bfd3cc5787c2da3e025fab#diff- ec7058c429b88797a43d7c3ef3a244980e46f8219844cd2550eaf4bcdc36e961 without an accompanying soname change. It doesn't look like something where the abi can't easily be restored. Just add a set of wrapper functions with the old signature adding a defaulted compression options when forwarding to the new one. Though a package name change is also a way forward. /Sune -- I didn’t stop pretending when I became an adult, it’s just that when I was a kid I was pretending that I fit into the rules and structures of this world. And now that I’m an adult, I pretend that those rules and structures exist. - zefrank
Bug#1070227: Fails to start with undefined symbol
Package: chromium Version: 124.0.6367.78-1 Severity: grave The current package in debian unstable fails to start with the following missing symbol: $ chromium grep: warning: stray \ before - /usr/lib/chromium/chromium: symbol lookup error: /usr/lib/chromium/chromium: undefined symbol: _ZN6snappy11RawCompressEPKcmPcPm -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chromium depends on: ii chromium-common124.0.6367.78-1 ii libasound2t64 1.2.11-1+b1 ii libatk-bridge2.0-0t64 2.52.0-1 ii libatk1.0-0t64 2.52.0-1 ii libatomic1 14-20240429-1 ii libatspi2.0-0t64 2.52.0-1 ii libc6 2.38-6 ii libcairo2 1.18.0-3+b1 ii libcups2t642.4.7-1.2+b1 ii libdbus-1-31.14.10-4+b1 ii libdouble-conversion3 3.3.0-1+b1 ii libdrm22.4.120-2 ii libevent-2.1-7t64 2.1.12-stable-8.1+b3 ii libexpat1 2.6.2-1 ii libflac12t64 1.4.3+ds-2.1 ii libfontconfig1 2.15.0-1.1 ii libfreetype6 2.13.2+dfsg-1+b4 ii libgbm124.1.0~rc1-1 ii libgcc-s1 14-20240429-1 ii libglib2.0-0t642.78.4-7 ii libgtk-3-0t64 3.24.41-4 ii libjpeg62-turbo1:2.1.5-3 ii libjsoncpp25 1.9.5-6+b2 ii liblcms2-2 2.14-2+b1 ii libminizip1t64 1:1.3.dfsg-3.1 ii libnspr4 2:4.35-1.1+b1 ii libnss32:3.99-1 ii libopenh264-7 2.4.1+dfsg-1 ii libopenjp2-7 2.5.0-2+b3 ii libopus0 1.4-1+b1 ii libpango-1.0-0 1.52.1+ds-1 ii libpng16-16t64 1.6.43-5 ii libpulse0 16.1+dfsg1-5 ii libsnappy1v5 1.2.0-1 ii libstdc++6 14-20240429-1 ii libwoff1 1.0.2-2+b1 ii libx11-6 2:1.8.7-1+b1 ii libxcb11.17.0-1 ii libxcomposite1 1:0.4.5-1+b1 ii libxdamage11:1.1.6-1+b1 ii libxext6 2:1.3.4-1+b1 ii libxfixes3 1:6.0.0-2+b1 ii libxkbcommon0 1.6.0-1+b1 ii libxml22.9.14+dfsg-1.3+b3 ii libxnvctrl0535.171.04-1 ii libxrandr2 2:1.5.4-1 ii libxslt1.1 1.1.35-1+b1 ii zlib1g 1:1.3.dfsg-3.1 Versions of packages chromium recommends: pn chromium-sandbox Versions of packages chromium suggests: pn chromium-driver pn chromium-l10n pn chromium-shell Versions of packages chromium-common depends on: ii libc6 2.38-6 ii libdrm2 2.4.120-2 ii libjsoncpp25 1.9.5-6+b2 ii libstdc++614-20240429-1 ii libx11-6 2:1.8.7-1+b1 ii libxnvctrl0 535.171.04-1 ii x11-utils 7.7+6+b1 ii xdg-utils 1.1.3-4.1 ii zlib1g1:1.3.dfsg-3.1 Versions of packages chromium-common recommends: pn chromium-sandbox ii dunst [notification-daemon] 1.11.0-1 ii fonts-liberation 1:2.1.5-3 ii libgl1-mesa-dri 24.1.0~rc1-1 pn libu2f-udev pn system-config-printer pn upower
Bug#1061874: marked as done (colpack: NMU diff for 64-bit time_t transition)
Your message dated Thu, 02 May 2024 08:49:20 +
with message-id
and subject line Bug#1061874: fixed in colpack 1.0.10-8
has caused the Debian Bug report #1061874,
regarding colpack: NMU diff for 64-bit time_t transition
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 now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1061874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: colpack
Version: 1.0.10-7
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
colpack as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for colpack
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-15-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru colpack-1.0.10/debian/changelog colpack-1.0.10/debian/changelog
--- colpack-1.0.10/debian/changelog 2023-01-04 21:44:51.0 +
+++ colpack-1.0.10/debian/changelog 2024-01-29 22:36:02.0 +
@@ -1,3 +1,10 @@
+colpack (1.0.10-7.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ --Mon, 29 Jan 2024 22:36:02 +
+
colpack (1.0.10-7) unstable; urgency=medium
* Track upstream
diff -Nru colpack-1.0.10/debian/control colpack-1.0.10/debian/control
--- colpack-1.0.10/debian/control 2023-01-04 21:44:51.0 +
+++ colpack-1.0.10/debian/control 2024-01-29 22:36:02.0 +
@@ -28,13 +28,16 @@
This package contains the development library, header files, and
documentation.
-Package: libcolpack0v5
+Package: libcolpack0t64
+Provides: ${t64:Provides}
+X-Time64-Compat: libcolpack0v5
+Breaks: libcolpack0v5 (<< ${source:Version})
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends}, ${misc:Depends}
Conflicts: libcolpack0
-Replaces: libcolpack0
+Replaces: libcolpack0v5, libcolpack0
Description: Specialized graph vertex coloring library, shared library
ColPack is a package comprising of implementation of algorithms for
specialized vertex coloring problems that arise in sparse derivative
diff -Nru colpack-1.0.10/debian/libcolpack0t64.install
colpack-1.0.10/debian/libcolpack0t64.install
--- colpack-1.0.10/debian/libcolpack0t64.install1970-01-01
00:00:00.0 +
+++ colpack-1.0.10/debian/libcolpack0t64.install2023-01-04
21:44:51.0 +
@@ -0,0 +1 @@
+/usr/lib/*/lib*.so.*
diff -Nru colpack-1.0.10/debian/libcolpack0t64.lintian-overrides
colpack-1.0.10/debian/libcolpack0t64.lintian-overrides
--- colpack-1.0.10/debian/libcolpack0t64.lintian-overrides 1970-01-01
00:00:00.0 +
+++ colpack-1.0.10/debian/libcolpack0t64.lintian-overrides 2024-01-29
22:36:02.0 +
@@ -0,0 +1 @@
+libcolpack0t64: package-name-doesnt-match-sonames
Processed: reassign 1070217 to libsnappy1v5
Processing commands for cont...@bugs.debian.org: > reassign 1070217 libsnappy1v5 1.2.0-1 Bug #1070217 [snappy] chromium: Symbol lookup error with libsnappy1v5>=1.2.0 Bug reassigned from package 'snappy' to 'libsnappy1v5'. No longer marked as found in versions 1.2.0-1. Ignoring request to alter fixed versions of bug #1070217 to the same values previously set Bug #1070217 [libsnappy1v5] chromium: Symbol lookup error with libsnappy1v5>=1.2.0 Marked as found in versions snappy/1.2.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1070217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1070217 in 1.2.0-1
Processing commands for cont...@bugs.debian.org: > found 1070217 1.2.0-1 Bug #1070217 [snappy] chromium: Symbol lookup error with libsnappy1v5>=1.2.0 There is no source info for the package 'snappy' at version '1.2.0-1' with architecture '' Unable to make a source version for version '1.2.0-1' Marked as found in versions 1.2.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1070217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070116: marked as done (python-zeep: Build-depends on NBS libraries libxmlsec1 and libxmlsec1-openssl)
Your message dated Thu, 02 May 2024 07:51:20 + with message-id and subject line Bug#1070116: fixed in python-zeep 4.2.1-3 has caused the Debian Bug report #1070116, regarding python-zeep: Build-depends on NBS libraries libxmlsec1 and libxmlsec1-openssl 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 now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1070116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-zeep Version: 4.2.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source Once xmlsec1 is decrufted, python-zeep will FTBFS. The build-depends need to be updated to libxmlsec1t64 and libxmlsec1t64-openssl. Scott K --- End Message --- --- Begin Message --- Source: python-zeep Source-Version: 4.2.1-3 Done: Mathias Behrle We believe that the bug you reported is fixed in the latest version of python-zeep, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathias Behrle (supplier of updated python-zeep package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 May 2024 09:17:41 +0200 Source: python-zeep Architecture: source Version: 4.2.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Tryton Maintainers Changed-By: Mathias Behrle Closes: 1070116 Changes: python-zeep (4.2.1-3) unstable; urgency=medium . [ Alexandre Detiste ] * remove obsolete ref. to python3-mock . [ Mathias Behrle ] * Update the libxmlsec1 build dependencies to follow the t64 transition (Closes: #1070116). Checksums-Sha1: 8c97b396740b0776b9110eb4b9b0d26038155a54 2503 python-zeep_4.2.1-3.dsc f47a8bd44c8f5317c7aa25712a627206e58e4d6d 12460 python-zeep_4.2.1-3.debian.tar.xz c21f01c7dd039f4e66b1d2719e5d8938550a091a 8755 python-zeep_4.2.1-3_amd64.buildinfo Checksums-Sha256: ffb2b306c8a135e2c1e0b3a4fd1e1d3e8606df759039e27ce1e0340d8b81e21f 2503 python-zeep_4.2.1-3.dsc 90bb89c44905c664744775e2fe500d17adcaa65f060822265fa8aa3c49b5e82d 12460 python-zeep_4.2.1-3.debian.tar.xz 601546ed1cdd439f6fc4418d2f6f9eb5d5e4c6234ee102325cb2bd871644fa62 8755 python-zeep_4.2.1-3_amd64.buildinfo Files: 7e89f0a863797091de76cd31d46801c4 2503 python optional python-zeep_4.2.1-3.dsc e4ea73b19aff4e1750a73de32fa11202 12460 python optional python-zeep_4.2.1-3.debian.tar.xz 97f017e15f82f1fa32a26e1e7571ed27 8755 python optional python-zeep_4.2.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- Comment: Signed by Mathias Behrle iQIzBAEBCgAdFiEErCl+XEa50LYccXaB1tCb5IQFu/YFAmYzQwoACgkQ1tCb5IQF u/YJgA/+NDPHRENGd1BCsppGGyYdgEbKrr98F33pR802b9r+SscZKn6nCpTYwjKE 1yzVKCgsZM6ml/lpVy+WqgHRZZeiSTLplxu95aX0BncAqsOfj7USCUmS05ssY6cf tnNQij5SinpfkR9Wg+lOfpN1hdAPrvMxj0gGUP8GwzTyjcLiw1w42daBYUtE9xT/ ku/5AL58nbhLtOsXBzObQ6RB7k3cgSE3UmuM7P3GlXx3+xlAG7/NYc9jW1FE8YYS 1Y1OeunRUoxQSPGGJdX3cieLwqy5dlZDos9YERdldIy4ane7JqIdu2vtQ/ZbAphn 4xNg5aUOwS1mprJT6aIDDOjZCvogEh7GgxO5l0KuzmWzNJ7V7Ev8eflBmtrUhlQs 9m27MOeXFlUbyig4q575H/hX1QcZs35pioWXeWzfymGt3yaWSBDUlbKwjUtnjquQ sbC1Lw8UTwci356Pkp22pxPdZSeOFV63WNkamg/hldIztK2NQeYvrvwo0Hg7qDWt MDarUyRcWeoEZIkivXXddTj2RIueqzBo0tYrR+vt1F9XvUXSBc4+ZSjQ1GD/2hKZ LA7GztePo+NpWictI6CcW3AMwqaCLeMNOVnx7l10k7x9r8qWOd7XTVUjzrDyNKcn u67fp0mOoVK5evmnJYXbayTwz0vXtYyvXdY93Y96yYRO6nKZ1Gw= =NZIP -END PGP SIGNATURE- pgptTQU61VKwf.pgp Description: PGP signature --- End Message ---
Bug#999957: sniproxy: diff for NMU version 0.6.1+git20240321-0.1
On Tue, 30 Apr 2024 20:07:07 -0400 Boyuan Yang wrote: I've prepared an NMU for sniproxy (versioned as 0.6.1+git20240321-0.1) and uploaded it to DELAYED/14. Please feel free to tell me if I sniproxy is orphaned, so you should rather do an undelayed QA upload (instead of a NMU) and update the maintainer as well. There is also a Janitor merge request open on salsa.d.o, you should integrate that as well. Thanks! Andreas
Bug#1070116: marked as done (python-zeep: Build-depends on NBS libraries libxmlsec1 and libxmlsec1-openssl)
Your message dated Thu, 02 May 2024 07:04:29 + with message-id <66333afd217bc_54c94c...@godard.mail> and subject line Bug#1070116 fixed in python-zeep has caused the Debian Bug report #1070116, regarding python-zeep: Build-depends on NBS libraries libxmlsec1 and libxmlsec1-openssl 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 now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1070116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-zeep Version: 4.2.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source Once xmlsec1 is decrufted, python-zeep will FTBFS. The build-depends need to be updated to libxmlsec1t64 and libxmlsec1t64-openssl. Scott K --- End Message --- --- Begin Message --- Hello, Bug #1070116 in python-zeep reported by you has been fixed in the Git repository. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/tryton-team/python-zeep/-/commit/284df48f9e3dccd712c9e34eff02f826fdd41787 Update the libxmlsec1 build dependencies to follow the t64 transition (Closes: #1070116). (this message was generated automatically) -- Greetings https://bugs.debian.org/1070116--- End Message ---
Processed: Bug#1070116 marked as pending in python-zeep
Processing control commands:
> tag -1 pending
Bug #1070116 {Done: Mathias Behrle } [src:python-zeep]
python-zeep: Build-depends on NBS libraries libxmlsec1 and libxmlsec1-openssl
Added tag(s) pending.
--
1070116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1070116: marked as pending in python-zeep
Control: tag -1 pending Hello, Bug #1070116 in python-zeep 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/tryton-team/python-zeep/-/commit/284df48f9e3dccd712c9e34eff02f826fdd41787 Update the libxmlsec1 build dependencies to follow the t64 transition (Closes: #1070116). (this message was generated automatically) -- Greetings https://bugs.debian.org/1070116
Bug#1042251: marked as done (python-omegaconf: FTBFS: E ModuleNotFoundError: No module named 'attr')
Your message dated Thu, 02 May 2024 06:38:19 + with message-id and subject line Bug#1042251: fixed in python-omegaconf 2.3.0-1 has caused the Debian Bug report #1042251, regarding python-omegaconf: FTBFS: E ModuleNotFoundError: No module named 'attr' 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 now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-omegaconf Version: 2.2.2-2.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > make[1]: pyversions: No such file or directory > py3versions: no X-Python3-Version in control file, using supported versions > pkgos-dh_auto_install --no-py2 --in-tmp > + PKGOS_IN_TMP=no > + echo WARNING: --no-py2 is deprecated and always on. > WARNING: --no-py2 is deprecated and always on. > + shift > + PKGOS_IN_TMP=yes > + shift > + dpkg-parsechangelog -SSource > + SRC_PKG_NAME=python-omegaconf > + echo python-omegaconf > + sed s/python-// > + PY_MODULE_NAME=omegaconf > + py3versions -vr > + PYTHON3S=3.11 > + [ yes = yes ] > + TARGET_DIR=tmp > + pwd > + python3.11 setup.py install --install-layout=deb --root > /<>/debian/tmp > /<>/setup.py:13: DeprecationWarning: pkg_resources is deprecated > as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html > import pkg_resources > running install > /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: > SetuptoolsDeprecationWarning: setup.py install is deprecated. > !! > > > > Please avoid running ``setup.py`` directly. > Instead, use pypa/build, pypa/installer or other > standards-based tools. > > See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html > for details. > > > > !! > self.initialize_options() > running build > running build_py > running clean > Generating parsers with antlr4 > running antlr > Generating parser for Python3: ['java', '-jar', > '/<>/build_helpers/bin/antlr-4.9.3-complete.jar', > '-Dlanguage=Python3', '-o', '/<>/omegaconf/grammar/gen', > '-Xexact-output-dir', '-visitor', > '/<>/omegaconf/grammar/OmegaConfGrammarLexer.g4'] > Generating parser for Python3: ['java', '-jar', > '/<>/build_helpers/bin/antlr-4.9.3-complete.jar', > '-Dlanguage=Python3', '-o', '/<>/omegaconf/grammar/gen', > '-Xexact-output-dir', '-visitor', > '/<>/omegaconf/grammar/OmegaConfGrammarParser.g4'] > creating build > creating build/lib > creating build/lib/omegaconf > copying omegaconf/nodes.py -> build/lib/omegaconf > copying omegaconf/grammar_visitor.py -> build/lib/omegaconf > copying omegaconf/omegaconf.py -> build/lib/omegaconf > copying omegaconf/version.py -> build/lib/omegaconf > copying omegaconf/__init__.py -> build/lib/omegaconf > copying omegaconf/dictconfig.py -> build/lib/omegaconf > copying omegaconf/errors.py -> build/lib/omegaconf > copying omegaconf/_utils.py -> build/lib/omegaconf > copying omegaconf/basecontainer.py -> build/lib/omegaconf > copying omegaconf/listconfig.py -> build/lib/omegaconf > copying omegaconf/grammar_parser.py -> build/lib/omegaconf > copying omegaconf/base.py -> build/lib/omegaconf > copying omegaconf/_impl.py -> build/lib/omegaconf > creating build/lib/omegaconf/grammar > copying omegaconf/grammar/__init__.py -> build/lib/omegaconf/grammar > creating build/lib/omegaconf/grammar/gen > copying omegaconf/grammar/gen/__init__.py -> build/lib/omegaconf/grammar/gen > copying omegaconf/grammar/gen/OmegaConfGrammarLexer.py -> > build/lib/omegaconf/grammar/gen > copying omegaconf/grammar/gen/OmegaConfGrammarParser.py -> > build/lib/omegaconf/grammar/gen > copying omegaconf/grammar/gen/OmegaConfGrammarParserVisitor.py -> > build/lib/omegaconf/grammar/gen > copying omegaconf/grammar/gen/OmegaConfGrammarParserListener.py -> > build/lib/omegaconf/grammar/gen > creating build/lib/omegaconf/resolvers > copying omegaconf/resolvers/__init__.py -> build/lib/omegaconf/resolvers > creating build/lib/omegaconf/resolvers/oc > copying omegaconf/resolvers/oc/__init__.py -> build/lib/omegaconf/resolvers/oc > copying omegaconf/resolvers/oc/dict.py -> build/lib/omegaconf/resolvers/oc > creating build/lib/pydevd_plugins > copying
