Bug#1052096: marked as done (gnome-shell-extension-flypie: needs update for GNOME Shell 46)

2024-07-16 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jul 2024 06:37:26 + with message-id and subject line Bug#1052096: fixed in gnome-shell-extension-flypie 26-2 has caused the Debian Bug report #1052096, regarding gnome-shell-extension-flypie: needs update for GNOME Shell 46 to be marked as done. This means that you

Bug#1076418: FTBFS: undeclared type `TestClient`

2024-07-16 Thread Reinhard Tartler
Reinhard Tartler writes: > Source: rust-axum > Version: 0.6.20-21 > Severity: serious > Tags: ftbfs > Justification: FTBFS > > Seem the buildds are having trouble building this package: > > error[E0433]: failed to resolve: use of undeclared type `TestClient` > --> axum/src/routing/tests/mod.r

Processed: src:snapd: fails to migrate to testing for too long: autopkgtest regression

2024-07-16 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.63-3 Bug #1076490 [src:snapd] src:snapd: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions snapd/2.63-3. Bug #1076490 [src:snapd] src:snapd: fails to migrate to testing for too long: autopkgtest regression Marke

Bug#1076490: src:snapd: fails to migrate to testing for too long: autopkgtest regression

2024-07-16 Thread Paul Gevers
Source: snapd Version: 2.62-5 Severity: serious Control: close -1 2.63-3 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having

Processed: src:developers-reference: fails to migrate to testing for too long: autopkgtest regression

2024-07-16 Thread Debian Bug Tracking System
Processing control commands: > close -1 13.7 Bug #1076489 [src:developers-reference] src:developers-reference: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions developers-reference/13.7. Bug #1076489 [src:developers-reference] src:developers-reference:

Bug#1076489: src:developers-reference: fails to migrate to testing for too long: autopkgtest regression

2024-07-16 Thread Paul Gevers
Source: developers-reference Version: 13.6 Severity: serious Control: close -1 13.7 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days

Processed: src:libxml-libxslt-perl: fails to migrate to testing for too long: autopkgtest issues

2024-07-16 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.003000-1 Bug #1076488 [src:libxml-libxslt-perl] src:libxml-libxslt-perl: fails to migrate to testing for too long: autopkgtest issues Marked as fixed in versions libxml-libxslt-perl/2.003000-1. Bug #1076488 [src:libxml-libxslt-perl] src:libxml-libxslt-per

Bug#1076488: src:libxml-libxslt-perl: fails to migrate to testing for too long: autopkgtest issues

2024-07-16 Thread Paul Gevers
Source: libxml-libxslt-perl Version: 2.002001-1 Severity: serious Control: close -1 2.003000-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more t

Processed: pdns bugs

2024-07-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1051703 Bug #1051703 [pdns-backend-pgsql] pdns-backend-pgsql: No mention of schema updates in NEWS despite breaking service Marked Bug as done > block 1074780 by 1076286 Bug #1074780 [pdns-backend-mysql] pdns-backend-mysql: autopkgtests use

Processed: src:php-deepcopy: fails to migrate to testing for too long: uploader built arch:all binary

2024-07-16 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.12.0-1 Bug #1076487 [src:php-deepcopy] src:php-deepcopy: fails to migrate to testing for too long: uploader built arch:all binary Marked as fixed in versions php-deepcopy/1.12.0-1. Bug #1076487 [src:php-deepcopy] src:php-deepcopy: fails to migrate to test

Bug#1076487: src:php-deepcopy: fails to migrate to testing for too long: uploader built arch:all binary

2024-07-16 Thread Paul Gevers
Source: php-deepcopy Version: 1.11.1-2 Severity: serious Control: close -1 1.12.0-1 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than

Bug#1076486: src:rust-sequoia-ipc: fails to migrate to testing for too long: triggers autopkgtest issues

2024-07-16 Thread Paul Gevers
Source: rust-sequoia-ipc Version: 0.34.1-1 Severity: serious Control: close -1 0.35.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30

Processed: src:rust-sequoia-ipc: fails to migrate to testing for too long: triggers autopkgtest issues

2024-07-16 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.35.0-1 Bug #1076486 [src:rust-sequoia-ipc] src:rust-sequoia-ipc: fails to migrate to testing for too long: triggers autopkgtest issues Marked as fixed in versions rust-sequoia-ipc/0.35.0-1. Bug #1076486 [src:rust-sequoia-ipc] src:rust-sequoia-ipc: fails t

Bug#1074704: marked as done (wlgreet: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build --release returned exit code 101)

2024-07-16 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jul 2024 03:20:38 + with message-id and subject line Bug#1074704: fixed in wlgreet 0.5.0-2 has caused the Debian Bug report #1074704, regarding wlgreet: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build --release returned exit code 101 to be marked as don

Bug#1075849: marked as done (websockify: FTBFS with systemd (>= 256~rc3-3) due to fileno limit bump)

2024-07-16 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jul 2024 02:57:50 + with message-id and subject line Bug#1075849: fixed in websockify 0.12.0+dfsg1-2 has caused the Debian Bug report #1075849, regarding websockify: FTBFS with systemd (>= 256~rc3-3) due to fileno limit bump to be marked as done. This means that you

Bug#1073188: marked as done (dxvk: FTBFS on arm64 due to x86_64-w64-mingw32-gcc using -mbranch-protection=standard)

2024-07-16 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jul 2024 02:54:09 + with message-id and subject line Bug#1073188: fixed in dxvk 2.4-2 has caused the Debian Bug report #1073188, regarding dxvk: FTBFS on arm64 due to x86_64-w64-mingw32-gcc using -mbranch-protection=standard to be marked as done. This means that yo

Bug#1073188: dxvk: FTBFS on arm64 due to x86_64-w64-mingw32-gcc using -mbranch-protection=standard

2024-07-16 Thread duck
Quack, Thanks for your help. The upload is coming. \_o< -- Marc Dequènes

Processed: sqla 2.x

2024-07-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1073468 zaqar is incompatible with SQLAlchemy 2.x Bug #1073468 [src:zaqar] zaqar: FTBFS: sqlalchemy.exc.ArgumentError: Column expression, FROM clause, or other columns clause element expected, got [Table('Pools', MetaData(), Column('name

Processed: Bug#1075849 marked as pending in websockify

2024-07-16 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1075849 [src:websockify] websockify: FTBFS with systemd (>= 256~rc3-3) due to fileno limit bump Ignoring request to alter tags of bug #1075849 to the same tags previously set -- 1075849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075849

Bug#1075849: marked as pending in websockify

2024-07-16 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #1075849 in websockify 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/openstack-team/python/websockify/-/commit/ab53aecd02c6

Processed: Re: gnome-shell-extension-flypie: needs update for GNOME Shell 46

2024-07-16 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1052096 {Done: Mo Zhou } [gnome-shell-extension-flypie] gnome-shell-extension-flypie: needs update for GNOME Shell 46 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-a

Bug#1052096: gnome-shell-extension-flypie: needs update for GNOME Shell 46

2024-07-16 Thread Jeremy Bícha
Control: reopen -1 Control: tags -1 +patch gnome-shell-extension-flypie is uninstallable in Debian Unstable. Please see https://salsa.debian.org/debian/gnome-shell-extension-flypie/-/merge_requests/1 for the fix. I encourage you to use urgency=high in your upload since the rest of the GNOME Shel

Processed: Re: gpaste: NMU diff for 64-bit time_t transition

2024-07-16 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 45-3 Bug #1062118 {Done: Jérémy Lal } [src:gpaste] gpaste: NMU diff for 64-bit time_t transition Marked as fixed in versions gpaste/45-3. -- 1062118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062118 Debian Bug Tracking System Contact ow...@bugs.d

Bug#1062118: gpaste: NMU diff for 64-bit time_t transition

2024-07-16 Thread Jeremy Bícha
Control: fixed -1 45-3 The libgpaste renaming was dropped in the new release which I guess is ok. I'm updating the BTS so this bug doesn't block migration to Testing at this time. Thank you, Jeremy Bícha

Bug#1076472: rust-hypothesis: FTBFS: test result: FAILED. 7 passed; 11 failed; 0 ignored; 0 measured; 0 filtered out; finished in 54.85s

2024-07-16 Thread Sebastian Ramacher
Source: rust-hypothesis Version: 0.11.5-6 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=rust-hypothesis&arch=amd64&ver=0.11.5-6&stamp=1721056809&raw=0 f

Bug#1076471: rust-sequoia-sop: FTBFS: error: no matching package named `anyhow` found

2024-07-16 Thread Sebastian Ramacher
Source: rust-sequoia-sop Version: 0.35.0-2 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=rust-sequoia-sop&arch=amd64&ver=0.35.0-2%2Bb1&stamp=1721158555&r

Bug#1076468: arpack: FTBFS with mpich as default provider on 32 bit architectures

2024-07-16 Thread Sebastian Ramacher
Source: arpack Version: 3.9.1-1.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=arpack&arch=armel&ver=3.9.1-1.1%2Bb2&stamp=1720769142&raw=0 make[5]: Lea

Bug#1076469: llvm-18-dev: tries to overwrite /usr/lib/llvm-18/lib/libLLVM-18.so.1, which is also in libllvm18:amd64 1:18.1.8-2

2024-07-16 Thread Vincent Lefevre
Package: llvm-18-dev Version: 1:18.1.8-3 Severity: serious When upgrading the llvm-toolchain-18 packages: Unpacking llvm-18-dev (1:18.1.8-3) over (1:18.1.8-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-kf5zST/10-llvm-18-dev_1%3a18.1.8-3_amd64.deb (--unpack): trying to overwrite '/

Processed: Re: Bug#1073859: gopacket: FTBFS with glibc 2.39 due to internal type __time64_t

2024-07-16 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + pending Bug #1073859 [src:gopacket] gopacket: FTBFS with glibc 2.39 due to internal type __time64_t Added tag(s) pending. -- 1073859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073859 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

Bug#1073859: gopacket: FTBFS with glibc 2.39 due to internal type __time64_t

2024-07-16 Thread Aurelien Jarno
control: tag -1 + pending Dear maintainer, On 2024-06-19 23:07, Aurelien Jarno wrote: > Source: gopacket > Version: 1.1.19-6 > Severity: important > Tags: patch ftbfs > User: debian-gl...@lists.debian.org > Usertags: glibc2.39 > Control: affects -1 bettercap > > Dear maintainer, > > gopacket fa

Bug#1076467: pytest-mpi: autpkgtest regression with mpich as default provider on 32 bit architectures

2024-07-16 Thread Sebastian Ramacher
Source: pytest-mpi Version: 0.6-5 Severity: serious X-Debbugs-Cc: sramac...@debian.org https://ci.debian.net/packages/p/pytest-mpi/testing/armel/49095724/ 61s cls = , lines = [] 61s 61s @classmethod 61s def parse_summary_nouns(cls, lines) -> Dict[str, int]: 61s """Extract th

Bug#1076466: dijitso: autopkgtest regressions with mpich as default provider on 32 bit architectures

2024-07-16 Thread Sebastian Ramacher
Source: dijitso Version: 2019.2.0~git20190418.c92dcb0-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org https://ci.debian.net/packages/d/dijitso/testing/armel/49095715/ 76s test/test_mpi_dijitso.py = test session starts == 76s platfo

Bug#1076465: lammps: autopkgtest regressions with mpich as default provider on 32 bit architectures

2024-07-16 Thread Sebastian Ramacher
Source: lammps Version: 20240207+dfsg-1.1 Severity: serious X-Debbugs-Cc: sramac...@debian.org https://ci.debian.net/packages/l/lammps/testing/armel/49095719/ 107s autopkgtest [08:13:20]: test crack: [--- 108s [mpiexec@ci-197-dd577e49] match_arg (lib/utils/args.c:166): unrecog

Bug#1076464: src:requests: fails to migrate to testing for too long: triggers autopkgtest issues

2024-07-16 Thread Paul Gevers
Source: requests Version: 2.31.0+dfsg-2 Severity: serious Control: close -1 2.32.3+dfsg-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 3

Processed: src:requests: fails to migrate to testing for too long: triggers autopkgtest issues

2024-07-16 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.32.3+dfsg-1 Bug #1076464 [src:requests] src:requests: fails to migrate to testing for too long: triggers autopkgtest issues Marked as fixed in versions requests/2.32.3+dfsg-1. Bug #1076464 [src:requests] src:requests: fails to migrate to testing for too

Processed: src:python-urllib3: fails to migrate to testing for too long: unresolved RC bug

2024-07-16 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.0.7-2 Bug #1076463 [src:python-urllib3] src:python-urllib3: fails to migrate to testing for too long: unresolved RC bug Marked as fixed in versions python-urllib3/2.0.7-2. Bug #1076463 [src:python-urllib3] src:python-urllib3: fails to migrate to testing

Bug#1076279: pcb-rnd: Package dependencies must be librnd4t64, not librnd4

2024-07-16 Thread Bdale Garbee
Adrian Bunk writes: > librnd4t64 provides librnd4 only on the architectures > where no ABI change was done for 64bit time_t. I think this is a consequence of trying to ensure librnd4 is at version 4.2.0 or later, rather than just letting ${shlibs:Depends} do the right thing. Bdale signature.

Bug#1076463: src:python-urllib3: fails to migrate to testing for too long: unresolved RC bug

2024-07-16 Thread Paul Gevers
Source: python-urllib3 Version: 1.26.18-2 Severity: serious Control: close -1 2.0.7-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1073396 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and

Bug#1073480: llvm-17-dev: shipped Findzstd.cmake conflicts with cmake module provided by libzstd-dev

2024-07-16 Thread Pino Toscano
Source: qt6-base Followup-For: Bug #1073480 X-Debbugs-Cc: pkg-llvm-t...@lists.alioth.debian.org Control: reassign -1 llvm-17-dev Control: severity -1 important Hi, after a big of debugging, I think I got to the actual reason for this failure. In particular, starting from LLVM 16, there is a ship

Processed: llvm-17-dev: shipped Findzstd.cmake conflicts with cmake module provided by libzstd-dev

2024-07-16 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 llvm-17-dev Bug #1073480 [src:qt6-base] zstdTargets.cmake: missing targets zstd::libzstd_shared, zstd::libzstd_static, zstd::libzstd Bug reassigned from package 'src:qt6-base' to 'llvm-17-dev'. Ignoring request to alter found versions of bug #1073480 to

Bug#1076408: marked as done (rust-fs4: Failing autopkgtests)

2024-07-16 Thread Debian Bug Tracking System
Your message dated Tue, 16 Jul 2024 18:51:10 + with message-id and subject line Bug#1076408: fixed in rust-fs4 0.8.4-4 has caused the Debian Bug report #1076408, regarding rust-fs4: Failing autopkgtests to be marked as done. This means that you claim that the problem has been dealt with. If t

Processed: reassign 1073435 from augur to python3-zstandard properly

2024-07-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1073435 python3-zstandard 0.22.0-1 Bug #1073435 {Done: Étienne Mollier } [src:augur] augur: FTBFS: unsatisfiable build-dependency: libzstd1 (< 1.5.6~) but 1.5.6+dfsg-1 is to be installed Bug reassigned from package 'src:augur' to 'pytho

Bug#1076456: iptables-netflow-dkms: No more builds on Debian 11 Bullseye since kernel linux-image-5.10.0-31-amd64 (5.10.221-1) due to "unexport find_module" kernel backport from 5.12

2024-07-16 Thread Axel Beckert
Package: iptables-netflow-dkms Version: 2.5.1-2 Severity: grave Tags: patch bullseye Since linux-image-5.10.0-31-amd64/5.10.221-1, ipt_NETFLOW.ko no more builds on Debian 11 Bullseye: Citing from /var/lib/dkms/ipt-netflow/2.5.1/build/make.log: DKMS make.log for ipt-netflow-2.5.1 for kernel 5.10.

Bug#1069425: [Pkg-sssd-devel] Bug#1069450: socket_wrapper and the time_t 64-bit is hard

2024-07-16 Thread Simon Josefsson
Luca Boccassi writes: > On Mon, 29 Apr 2024 13:03:22 +1200 Andrew Bartlett > wrote: >> Just a warning that trying to brute force a fix for this is likely to >> end badly.  A lot of developer time was spent to get to this current >> delicate situation, which relied on the narrow behaviour that is

Bug#1076407: marked as done (rust-oo7: autopkgtest regression)

2024-07-16 Thread Debian Bug Tracking System
Your message dated Tue, 16 Jul 2024 15:51:09 + with message-id and subject line Bug#1076407: fixed in rust-oo7 0.3.3-3 has caused the Debian Bug report #1076407, regarding rust-oo7: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1076441: python3-flasgger: syntax error while comparing versions

2024-07-16 Thread Francesco Potortì
Sorry, by further investigation it appears that the error was on my part, as uiversion should be a number rather than a string. Please close this bug Sincerely -- Francesco Potortì (ricercatore)ISTI - CNR, Pisa, Italy Web:http://fly.isti.cnr.it Skype: wnla

Bug#1076449: mercurial: does not start anymore with python 3.12.4-3, hgdemandimport problem

2024-07-16 Thread Daniel Serpell
Package: mercurial Version: 6.8-1 Severity: grave Justification: renders package unusable Dear maintainer, In current sid, with python 3.12.4-3, mercurial fails at load with: ~$ hg Traceback (most recent call last): File "/usr/bin/hg", line 57, in from mercurial import dispatch Fi

Bug#1074517: marked as done (changeme: autopkgtest failure with Python 3.12)

2024-07-16 Thread Debian Bug Tracking System
Your message dated Tue, 16 Jul 2024 15:04:40 + with message-id and subject line Bug#1074517: fixed in changeme 1.2.3-5 has caused the Debian Bug report #1074517, regarding changeme: autopkgtest failure with Python 3.12 to be marked as done. This means that you claim that the problem has been

Bug#1076350: nodejs: segfault in node when running browserify script on i386 when building node-prop-types

2024-07-16 Thread Сергей Сёмин
It's interesting that problem is reproducible in Debian Bookworm i386 in other cases when building node packages from source. The same problem with browserify occurs when building source package node-prop-types_15.8.1+~15.7.5-2. As earlier, I took Debian Bookworm i386 with repos: deb http://deb.de

Bug#1076314: qiime hard-codes python 3.11 without depending on it

2024-07-16 Thread Andreas Tille
Hi Matthias, Am Tue, Jul 16, 2024 at 12:52:56PM +0200 schrieb Matthias Klose: > > Just to let me understand correctly: Its definitely a mistake to > > (Build-)Depend: python3-all. However, am I understand you correctly > > that (Build-)Depend from python3.11 could save the packag in testing? > >

Bug#1072469: shc: FTBFS: build-depends on ash which does no longer exist

2024-07-16 Thread Dominik Viererbe
Hi, I also noticed the reverse build dependency of shc on ash in Ubuntu (see: https://bugs.launchpad.net/debian/+source/shc/+bug/2073141). > The trivial fix is to build-depend on dash instead, as in the attached patch. Even though this technically works, test/ttest.sh fails the build, because of f

Bug#1076245: lintian-brush: hangs and when killed leaved lock in Git repository

2024-07-16 Thread Jelmer Vernooij
On Sat, Jul 13, 2024 at 08:38:04PM +0200, Andreas Tille wrote: > Hi Jelmer, > > Am Sat, Jul 13, 2024 at 02:13:24PM + schrieb Jelmer Vernooij: > > > This is not only true for this specific package but for *all* packages > > > I tried in the last couple of weeks. > > > > It looks like it's an is

Bug#1076441: python3-flasgger: syntax error while comparing versions

2024-07-16 Thread Francesco Potortì
Package: python3-flasgger Version: 0.9.7.2~dev2+dfsg-3 Severity: grave Traceback (most recent call last): File "/home/work/loca/evaalapi/./demo", line 15, in from evaalapi import statefmt, estfmt File "/home/work/loca/evaalapi/evaalapi.py", line 162, in Swagger(app, config=swagger_co

Bug#1076314: qiime hard-codes python 3.11 without depending on it

2024-07-16 Thread Matthias Klose
On 16.07.24 11:03, Andreas Tille wrote: Hi Matthias, Am Sun, Jul 14, 2024 at 10:57:14AM +0200 schrieb Matthias Klose: Package: src:qiime Version: 2024.5.0-1 Severity: serious Tags: sid trixie * Only build for Python 3.11 until upstream catches up with Python 3.12. dear debian-med, ple

Bug#1074517: marked as pending in changeme

2024-07-16 Thread Sven Geuer
Control: tag -1 pending Hello, Bug #1074517 in changeme 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/pkg-security-team/changeme/-/commit/c29a3d1b51c60d4b3d8d

Processed: Bug#1074517 marked as pending in changeme

2024-07-16 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1074517 [src:changeme] changeme: autopkgtest failure with Python 3.12 Added tag(s) pending. -- 1074517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1071648: marked as done (busybox: FTBFS with Linux 6.8+)

2024-07-16 Thread Debian Bug Tracking System
Your message dated Tue, 16 Jul 2024 10:19:24 + with message-id and subject line Bug#1071648: fixed in busybox 1:1.36.1-8 has caused the Debian Bug report #1071648, regarding busybox: FTBFS with Linux 6.8+ to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1076148: marked as done (libpmix2t64: libpmix.so.2: cannot open shared object file: No such file or directory)

2024-07-16 Thread Debian Bug Tracking System
Your message dated Tue, 16 Jul 2024 09:55:55 + with message-id and subject line Bug#1076148: fixed in pmix 5.0.3-2 has caused the Debian Bug report #1076148, regarding libpmix2t64: libpmix.so.2: cannot open shared object file: No such file or directory to be marked as done. This means that y

Bug#1074664: marked as done (python-questplus: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)

2024-07-16 Thread Debian Bug Tracking System
Your message dated Tue, 16 Jul 2024 09:56:04 + with message-id and subject line Bug#1074664: fixed in python-questplus 2023.1-1 has caused the Debian Bug report #1074664, regarding python-questplus: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean

Bug#1076237: marked as done (gpaste: Uploaded needed for ongoing gnome-shell 46 transition)

2024-07-16 Thread Debian Bug Tracking System
Your message dated Tue, 16 Jul 2024 09:50:28 + with message-id and subject line Bug#1076237: fixed in gpaste 45-3 has caused the Debian Bug report #1076237, regarding gpaste: Uploaded needed for ongoing gnome-shell 46 transition to be marked as done. This means that you claim that the problem

Bug#1076314: qiime hard-codes python 3.11 without depending on it

2024-07-16 Thread Andreas Tille
Hi Matthias, Am Sun, Jul 14, 2024 at 10:57:14AM +0200 schrieb Matthias Klose: > Package: src:qiime > Version: 2024.5.0-1 > Severity: serious > Tags: sid trixie > > * Only build for Python 3.11 until upstream catches up with Python > 3.12. > > dear debian-med, please don't do that. It doesn

Processed: closing 1062118

2024-07-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1062118 Bug #1062118 [src:gpaste] gpaste: NMU diff for 64-bit time_t transition Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1062118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1

Bug#1076426: boost1.83: autopkgtest regression with CMake 3.30+

2024-07-16 Thread Timo Röhling
Source: boost1.83 Version: 1.83.0-3 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package has a autopkgtest regression with CMake 3.30, due to a new policy regarding the deprecation of the built-in find_package Boost module in favor of upstream's Boost

Bug#1073168: marked as done (src:mold: fails to migrate to testing for too long: FTBFS on armel)

2024-07-16 Thread Debian Bug Tracking System
Your message dated Tue, 16 Jul 2024 08:36:47 + with message-id and subject line Bug#1073168: fixed in mold 2.32.1+dfsg-2 has caused the Debian Bug report #1073168, regarding src:mold: fails to migrate to testing for too long: FTBFS on armel to be marked as done. This means that you claim that

Processed: affects 1076388

2024-07-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1076388 node-xterm Bug #1076388 [inwasm] node-xterm: Unable to build package node-xterm in Debian Trixie i386 due to LinkError in WebAssembly.Instance() Bug #1076425 [inwasm] inwasm: Estimated memorySettings.descriptor.maximum is wrong o

Processed: forcibly merging 1076388 1076425

2024-07-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1076388 1076425 Bug #1076388 [inwasm] node-xterm: Unable to build package node-xterm in Debian Trixie i386 due to LinkError in WebAssembly.Instance() Bug #1076425 [inwasm] inwasm: Estimated memorySettings.descriptor.maximum is wrong o

Processed: Re: node-xterm: Unable to build package node-xterm in Debian Trixie i386 due to LinkError in WebAssembly.Instance()

2024-07-16 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 inwasm Bug #1076388 [src:node-xterm] node-xterm: Unable to build package node-xterm in Debian Trixie i386 due to LinkError in WebAssembly.Instance() Bug reassigned from package 'src:node-xterm' to 'inwasm'. No longer marked as found in versions node-xter

Bug#1076388: node-xterm: Unable to build package node-xterm in Debian Trixie i386 due to LinkError in WebAssembly.Instance()

2024-07-16 Thread Jérémy Lal
Source: node-xterm Version: 5.3.0-2 Followup-For: Bug #1076388 Control: reassign -1 inwasm This is an issue with inwasm, I think. Reassigning. Meanwhile, node-xterm can use attached patch. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Ar

Bug#1065873: marked as done (hamster-time-tracker: Please drop dependencies on python3-distutils)

2024-07-16 Thread Debian Bug Tracking System
Your message dated Tue, 16 Jul 2024 07:49:31 + with message-id and subject line Bug#1065873: fixed in hamster-time-tracker 3.0.3-1.1 has caused the Debian Bug report #1065873, regarding hamster-time-tracker: Please drop dependencies on python3-distutils to be marked as done. This means that y

Processed: glibc 2.39 reached sid, bumping severity

2024-07-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1070441 serious Bug #1070441 [src:cbmc] cbmc: arm64 FTBFS with glibc 2.38 Severity set to 'serious' from 'important' > severity 1070443 serious Bug #1070443 [src:aspectc++] aspectc++: arm64 FTBFS with glibc 2.38 Severity set to 'serious'

Bug#1076374: libplayeronecamera2t64: ineffective replaces for /usr/lib/udev/rules.d/99-player_one_astronomy.rules causes file loss

2024-07-16 Thread Helmut Grohne
Hi Thorsten and Chris, On Mon, Jul 15, 2024 at 07:07:37PM +0200, Chris Hofstaedtler wrote: > The following upgrade scenario demonstrates the loss. It may be > possible to construct a simpler scenario. (This needs mmdebstrap 1.5.1-4 or > better.) Thank you. > mmdebstrap \ > --components="main n