Bug#998520: marked as done (rust-bstr: FTBFS: unsatisfiable build-dependencies (purely virtual?): librust-memchr-2+std-dev (>= 2.4.0-~~), librust-memchr-2-dev (>= 2.4.0-~~))

2021-12-23 Thread Debian Bug Tracking System
Your message dated Fri, 24 Dec 2021 07:40:23 + with message-id and subject line re: rust-bstr: FTBFS: unsatisfiable build-dependencies (purely virtual?): librust-memchr-2+std-dev (>= 2.4.0-~~), librust-memchr-2-dev (>= 2.4.0-~~) has caused the Debian Bug report #998520, regarding rust-bstr:

Bug#1001371: pytest-twisted: (autopkgtest) needs update for python3.10: E {'warnings': 2} != {'warnings': 1}

2021-12-23 Thread Andrey Rahmatullin
The upstream report at https://github.com/pytest-dev/pytest-twisted/issues/146 was closed as the additional warning is produced by Twisted. The Twisted fix isn't merged yet. TBH as I don't need this package anymore (python3-scrapy doesn't use it anymore) I'm considering orphaning it. -- WBR,

Processed: bug 1002342 is forwarded to https://github.com/scrapy/scrapy/issues/5212, tagging 1002342

2021-12-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1002342 https://github.com/scrapy/scrapy/issues/5212 Bug #1002342 [src:python-scrapy] python-scrapy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13 Set Bug

Bug#965902: bump xom debhelper compat from 5 to 7

2021-12-23 Thread Andrius Merkys
Hi Tony, On 2021-12-23 18:30, tony mancill wrote: > Those Ant and JDK versions in the manifest simply represent version > bumps in the toolchain. That update should be safe to upload. Thanks for confirming. I have uploaded the package with the fix. Best, Andrius

Bug#965902: marked as done (xom: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Fri, 24 Dec 2021 07:03:35 + with message-id and subject line Bug#965902: fixed in xom 1.2.10-3 has caused the Debian Bug report #965902, regarding xom: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the problem

Processed: Re: elixir-lang: autopkgtest fails on armhf: Cannot allocate 512 bytes of memory (of type "bpd").

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > found -1 1.12.2.dfsg-2 Bug #997801 [src:elixir-lang] elixir-lang: autopkgtest fails on armhf: Cannot allocate 512 bytes of memory (of type "bpd"). Marked as found in versions elixir-lang/1.12.2.dfsg-2. -- 997801:

Bug#997801: elixir-lang: autopkgtest fails on armhf: Cannot allocate 512 bytes of memory (of type "bpd").

2021-12-23 Thread Paul Gevers
Control: found -1 1.12.2.dfsg-2 On Sun, 24 Oct 2021 22:21:31 +0200 Paul Gevers wrote: With a recent upload of erlang the autopkgtest of elixir-lang fails in testing when that autopkgtest is run with the binary packages of erlang from unstable. This was reported and fixed, but on armhf the test

Bug#1002119: gr-fcdproplus: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create'

2021-12-23 Thread peter green
Relevant part (hopefully): /usr/bin/ld: CMakeFiles/cmTC_d6505.dir/src.c.o: in function `main': ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create' /usr/bin/ld: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:12: undefined reference to `pthread_detach'

Bug#1002565: src:rust-openssl: fails to migrate to testing for too long

2021-12-23 Thread Paul Gevers
Source: rust-openssl Version: 0.10.29-1 Severity: serious Control: close -1 0.10.36-1 Tags: sid bookworm 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 60

Bug#998520: re: rust-bstr: FTBFS: unsatisfiable build-dependencies (purely virtual?): librust-memchr-2+std-dev (>= 2.4.0-~~), librust-memchr-2-dev (>= 2.4.0-~~)

2021-12-23 Thread Paul Gevers
Hi, On Thu, 4 Nov 2021 21:13:28 + peter green wrote: The new version of rust-memchr which will fix this is in NEW. This seems to have been accepted. Can this bug be closed now? It's severity is preventing rust-bstr from migrating to testing. Paul OpenPGP_signature Description:

Processed: src:rust-openssl: fails to migrate to testing for too long

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.10.36-1 Bug #1002565 [src:rust-openssl] src:rust-openssl: fails to migrate to testing for too long Marked as fixed in versions rust-openssl/0.10.36-1. Bug #1002565 [src:rust-openssl] src:rust-openssl: fails to migrate to testing for too long Marked Bug

Bug#1002229: marked as done (libnet-traceroute-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Fri, 24 Dec 2021 00:49:17 + with message-id and subject line Bug#1002229: fixed in libnet-traceroute-perl 1.15-3 has caused the Debian Bug report #1002229, regarding libnet-traceroute-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 to be

Bug#965836: #965836 tapecalc: Removal of obsolete debhelper compat 5 and 6 in bookworm

2021-12-23 Thread Thomas Dickey
When I find someone to sign my gpg key, I'll provide an NMU for this. It's unlikely that will happen before this deadline. -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature

Bug#1002229: marked as pending in libnet-traceroute-perl

2021-12-23 Thread gregor herrmann
Control: tag -1 pending Hello, Bug #1002229 in libnet-traceroute-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1002229 marked as pending in libnet-traceroute-perl

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1002229 [src:libnet-traceroute-perl] libnet-traceroute-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) pending. -- 1002229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002229 Debian Bug

Bug#1002100: marked as done (gr-rds: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create')

2021-12-23 Thread Debian Bug Tracking System
Your message dated Fri, 24 Dec 2021 00:08:11 + with message-id and subject line Bug#1002100: fixed in gr-rds 3.8.0.39.113b70b-1 has caused the Debian Bug report #1002100, regarding gr-rds: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create' to

Bug#1002551: sqlite3-tools: missing Breaks+Replaces: sqlite3 (<< 3.37.0)

2021-12-23 Thread Andreas Beckmann
Package: sqlite3-tools Version: 3.37.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it

Bug#1002549: sqlite3-tools: /usr/bin/showdb is already shipped by emboss

2021-12-23 Thread Andreas Beckmann
Package: sqlite3-tools Version: 3.37.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. The name /usr/bin/showdb has been used by the emboss

Processed: forcibly merging 999889 1002529

2021-12-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 999889 1002529 Bug #999889 {Done: Michael Biebl } [rsyslog] please keep /etc/init.d/rsyslog Bug #1002529 [rsyslog] removing /etc/init.d/rsyslog on upgrade breaks systems still using sysvinit Severity set to 'wishlist' from 'critical'

Bug#1002548: libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules

2021-12-23 Thread Andreas Beckmann
Package: libfli2,indi-fli Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 2.0-2 Control: found -1 1.5-1 Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has

Processed: libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > found -1 2.0-2 Bug #1002548 [libfli2,indi-fli] libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules There is no source info for the package 'indi-fli' at version '2.0-2' with architecture '' Marked as found in versions libfli/2.0-2. > found -1 1.5-1 Bug

Bug#1002229: libnet-traceroute-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2

2021-12-23 Thread gregor herrmann
On Wed, 22 Dec 2021 21:02:37 +0100, Lucas Nussbaum wrote: > > Do you have any idea how this can happen in your test environment or > > any information for us, what is special about it? > I tried it again and could reproduce it. Thank your very much for taking the extra time to further

Bug#1002424: marked as done (pikepdf: FTBFS: RuntimeError: Non Expected exception in `/<>/docs/topics/images.rst` line 175)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 23:19:33 + with message-id and subject line Bug#1002424: fixed in pikepdf 4.2.0+dfsg-1 has caused the Debian Bug report #1002424, regarding pikepdf: FTBFS: RuntimeError: Non Expected exception in `/<>/docs/topics/images.rst` line 175 to be marked as done.

Bug#1002541: libio-async-perl: autopkgtest regression on ppc64el: Parse errors: No plan found in TAP output

2021-12-23 Thread gregor herrmann
On Thu, 23 Dec 2021 21:59:45 +0100, Paul Gevers wrote: > With a recent upload of libio-async-perl the autopkgtest of libio-async-perl > fails in testing on ppc64el when that autopkgtest is run with the binary > packages of libio-async-perl from unstable. It passes when run with only > packages

Bug#1001303: marked as done (alure: FTBFS: -pthread: not found)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 22:33:40 + with message-id and subject line Bug#1001303: fixed in alure 1.2-9 has caused the Debian Bug report #1001303, regarding alure: FTBFS: -pthread: not found to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Bug#1001303 marked as pending in alure

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1001303 [src:alure] alure: FTBFS: -pthread: not found Added tag(s) pending. -- 1001303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1001303: marked as pending in alure

2021-12-23 Thread Bastian Germann
Control: tag -1 pending Hello, Bug #1001303 in alure reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#922396: [Pkg-mozext-maintainers] Bug#922396: Updated package / patch and status information

2021-12-23 Thread Jonathan Rubenstein
On Sun, 9 Aug 2020 02:09:59 +0100 Ximin Luo wrote: The reason why I haven't updated it since 2018 is because I've moved onto using umatrix personally and also maintaining it in debian. umatrix gives you more fine-grained permissions including cookies, XHR, etc, so you don't need to install

Processed: python-requests-cache breaks howdoi autopkgtest: 'requests_cache' has no attribute 'install_cache'

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > found -1 python-requests-cache/0.8.1-2 Bug #1002542 [src:python-requests-cache, src:howdoi] python-requests-cache breaks howdoi autopkgtest: 'requests_cache' has no attribute 'install_cache' Marked as found in versions python-requests-cache/0.8.1-2. > found -1

Bug#1002542: python-requests-cache breaks howdoi autopkgtest: 'requests_cache' has no attribute 'install_cache'

2021-12-23 Thread Paul Gevers
Source: python-requests-cache, howdoi Control: found -1 python-requests-cache/0.8.1-2 Control: found -1 howdoi/1.1.9-1 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent

Bug#1002540: condor: CVE-2021-45101

2021-12-23 Thread Salvatore Bonaccorso
Source: condor Version: 8.6.8~dfsg.1-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for condor. CVE-2021-45101[0]: | An issue was discovered in HTCondor before

Bug#1002541: libio-async-perl: autopkgtest regression on ppc64el: Parse errors: No plan found in TAP output

2021-12-23 Thread Paul Gevers
Source: libio-async-perl Version: 0.801-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of libio-async-perl the autopkgtest of libio-async-perl fails in testing on ppc64el when that

Bug#999117: marked as done (triangle: missing required debian/rules targets build-arch and/or build-indep)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 20:49:39 + with message-id and subject line Bug#999117: fixed in triangle 1.6-4 has caused the Debian Bug report #999117, regarding triangle: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

Bug#1002522: chkrootkit: autopkgtest failure everywhere except amd64

2021-12-23 Thread Paul Gevers
Hi, On 23-12-2021 21:13, Richard Lewis wrote: Sorry, I'm confused - is this a bug report against version 0.55-3 (which has been superseded by 0.55-4), or is this saying that 0.55-4 still fails? I didn't see 0.55-4 yet. I don't see any results for 0.55-4 at

Bug#1002525: r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package version inconsistency detected.

2021-12-23 Thread Dirk Eddelbuettel
On 23 December 2021 at 20:03, Paul Gevers wrote: | Source: r-cran-tmb | Version: 1.7.22-1 | Severity: serious | X-Debbugs-CC: debian...@lists.debian.org, rmat...@packages.debian.org | Tags: sid bookworm | User: debian...@lists.debian.org | Usertags: needs-update | Control: affects -1 src:rmatrix

Bug#1002536: rsplib: missing valgrind for armel

2021-12-23 Thread Bastian Germann
Source: rsplib Version: 3.3.3-1 Severity: serious The build dependency valgrind is not available for armel. If this is optional, please make the package build without it on armel or exclude armel from the build architectures.

Bug#1000496: upgrade-reports: libvirt/kvm/qemu/grub - XML-generated VMs working under buster fail with bullseye

2021-12-23 Thread Paul Gevers
Control: reassign -1 grub2 Hi Ulrich, Sorry it took so long to get back to you. On 24-11-2021 09:28, amodia wrote: after the upgrade from buster to bullseye virtual machines generated with libvirt do not start. Expected outcome was that all VMs start as usual (under buster). Introspecting

Processed: Re: Bug#1000496: upgrade-reports: libvirt/kvm/qemu/grub - XML-generated VMs working under buster fail with bullseye

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 grub2 Bug #1000496 [upgrade-reports] upgrade-reports: libvirt/kvm/qemu/grub - XML-generated VMs working under buster fail with bullseye Bug reassigned from package 'upgrade-reports' to 'grub2'. Ignoring request to alter found versions of bug #1000496 to

Bug#1002533: wheel: autopkgtest needs update for new version of setuptools: deprecation warning on stderr

2021-12-23 Thread Paul Gevers
Source: wheel Version: 0.34.2-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, setupto...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:setuptools Dear maintainer(s), With a recent upload of setuptools the

Processed: wheel: autopkgtest needs update for new version of setuptools: deprecation warning on stderr

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:setuptools Bug #1002533 [src:wheel] wheel: autopkgtest needs update for new version of setuptools: deprecation warning on stderr Added indication that 1002533 affects src:setuptools -- 1002533:

Bug#1002532: pygments breaks ruby-pygments.rb autopkgtest: UTF-8 != ASCII-8BIT

2021-12-23 Thread Paul Gevers
Source: pygments, ruby-pygments.rb Control: found -1 pygments/2.10.0+dfsg-1 Control: found -1 ruby-pygments.rb/1.2.1-2 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent

Processed: pygments breaks ruby-pygments.rb autopkgtest: UTF-8 != ASCII-8BIT

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > found -1 pygments/2.10.0+dfsg-1 Bug #1002532 [src:pygments, src:ruby-pygments.rb] pygments breaks ruby-pygments.rb autopkgtest: UTF-8 != ASCII-8BIT Marked as found in versions pygments/2.10.0+dfsg-1. > found -1 ruby-pygments.rb/1.2.1-2 Bug #1002532 [src:pygments,

Bug#1002529: removing /etc/init.d/rsyslog on upgrade breaks systems still using sysvinit

2021-12-23 Thread Marvin Renich
Package: rsyslog Version: 8.2110.0-4 Severity: critical On systems still running sysvinit, the removal of /etc/init.d/rsyslog during upgrade of rsyslog causes complete data loss of critical system information that was intended to be logged after the next reboot. I understand that many

Bug#1002527: postinst ignores USER from /etc/default/milter-greylist when invoking chown ... /var/lib/milter-greylist

2021-12-23 Thread Marvin Renich
Package: milter-greylist Version: 4.6.4-1 Severity: critical With an existing installation of milter-greylist set up to work with chrooted postfix (i.e. USER="postfix" in /etc/default/milter-greylist), every upgrade sets the owner of the directory /var/lib/milter-greylist to "greylist" regardless

Processed: python-django-extensions: autopkgtest needs update for new version of pygments: textual change

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:pygments Bug #1002526 [src:python-django-extensions] python-django-extensions: autopkgtest needs update for new version of pygments: textual change Added indication that 1002526 affects src:pygments -- 1002526:

Bug#1002526: python-django-extensions: autopkgtest needs update for new version of pygments: textual change

2021-12-23 Thread Paul Gevers
Source: python-django-extensions Version: 3.1.5-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, pygme...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:pygments Dear maintainer(s), With a recent upload of

Bug#1002525: r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package version inconsistency detected.

2021-12-23 Thread Paul Gevers
Source: r-cran-tmb Version: 1.7.22-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, rmat...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:rmatrix Dear maintainer(s), With a recent upload of rmatrix the

Processed: r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package version inconsistency detected.

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:rmatrix Bug #1002525 [src:r-cran-tmb] r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package version inconsistency detected. Added indication that 1002525 affects src:rmatrix -- 1002525:

Bug#997368: marked as done (FTBFS in sid)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 19:00:09 + with message-id and subject line Bug#998290: fixed in gnunet 0.15.3-1 has caused the Debian Bug report #998290, regarding FTBFS in sid to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#998290: marked as done (debianutils demoved tempfile, use mktemp)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 19:00:09 + with message-id and subject line Bug#998290: fixed in gnunet 0.15.3-1 has caused the Debian Bug report #998290, regarding debianutils demoved tempfile, use mktemp to be marked as done. This means that you claim that the problem has been dealt

Bug#998190: marked as done (sagemath: package new upstream version)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 19:00:42 + with message-id and subject line Bug#998190: fixed in sagemath 9.4-1 has caused the Debian Bug report #998190, regarding sagemath: package new upstream version to be marked as done. This means that you claim that the problem has been dealt with.

Bug#993247: marked as done (FTBFS in sid (libunistring))

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 19:00:09 + with message-id and subject line Bug#993247: fixed in gnunet 0.15.3-1 has caused the Debian Bug report #993247, regarding FTBFS in sid (libunistring) to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#993149: marked as done (sagemath FTBFS with eclib 20210625-1)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 19:00:42 + with message-id and subject line Bug#993149: fixed in sagemath 9.4-1 has caused the Debian Bug report #993149, regarding sagemath FTBFS with eclib 20210625-1 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#984326: marked as done (sagemath: ftbfs with GCC-11)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 19:00:42 + with message-id and subject line Bug#984326: fixed in sagemath 9.4-1 has caused the Debian Bug report #984326, regarding sagemath: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1002116: marked as done (gr-air-modes: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create')

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 19:00:12 + with message-id and subject line Bug#1002116: fixed in gr-air-modes 0.0.20210211-1 has caused the Debian Bug report #1002116, regarding gr-air-modes: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to

Bug#1000824: marked as done (The library package ships common files)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 19:00:44 + with message-id and subject line Bug#1000824: fixed in xapp 2.2.6-1 has caused the Debian Bug report #1000824, regarding The library package ships common files to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1002524: sqlobject: autopkgtest needs update for new version of setuptools: deprecation warning on stderr

2021-12-23 Thread Paul Gevers
Source: sqlobject Version: 3.9.0+dfsg-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, setupto...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:setuptools Dear maintainer(s), With a recent upload of setuptools

Processed: sqlobject: autopkgtest needs update for new version of setuptools: deprecation warning on stderr

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:setuptools Bug #1002524 [src:sqlobject] sqlobject: autopkgtest needs update for new version of setuptools: deprecation warning on stderr Added indication that 1002524 affects src:setuptools -- 1002524:

Bug#1002523: setuptools-scm: autopkgtest needs update for new version of setuptools: deprecation warning is treated as error

2021-12-23 Thread Paul Gevers
Source: setuptools-scm Version: 6.3.2-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, setupto...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:setuptools Dear maintainer(s), With a recent upload of setuptools

Processed: setuptools-scm: autopkgtest needs update for new version of setuptools: deprecation warning is treated as error

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:setuptools Bug #1002523 [src:setuptools-scm] setuptools-scm: autopkgtest needs update for new version of setuptools: deprecation warning is treated as error Added indication that 1002523 affects src:setuptools -- 1002523:

Processed: owner 965604

2021-12-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > owner 965604 ! Bug #965604 [src:jesd] jesd: Removal of obsolete debhelper compat 5 and 6 in bookworm Owner recorded as tony mancill . > thanks Stopping processing here. Please contact me if you need assistance. -- 965604:

Processed: src:fail2ban: fails to migrate to testing for too long: FTBFS

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.11.2-3 Bug #1002521 [src:fail2ban] src:fail2ban: fails to migrate to testing for too long: FTBFS The source 'fail2ban' and version '0.11.2-3' do not appear to match any binary packages Marked as fixed in versions fail2ban/0.11.2-3. Bug #1002521

Bug#1002521: src:fail2ban: fails to migrate to testing for too long: FTBFS

2021-12-23 Thread Paul Gevers
Source: fail2ban Version: 0.11.2-2 Severity: serious Control: close -1 0.11.2-3 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 997601 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and

Bug#1002520: src:xdg-utils-cxx: fails to migrate to testing for too long: FTBFS everywhere except amd64, arm64 and kfreebsd-amd64

2021-12-23 Thread Paul Gevers
Source: xdg-utils-cxx Version: 1.0.1-2 Severity: serious Control: close -1 1.0.1-3 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than

Processed: src:xdg-utils-cxx: fails to migrate to testing for too long: FTBFS everywhere except amd64, arm64 and kfreebsd-amd64

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.0.1-3 Bug #1002520 [src:xdg-utils-cxx] src:xdg-utils-cxx: fails to migrate to testing for too long: FTBFS everywhere except amd64, arm64 and kfreebsd-amd64 Marked as fixed in versions xdg-utils-cxx/1.0.1-3. Bug #1002520 [src:xdg-utils-cxx]

Processed: src:calcurse: fails to migrate to testing for too long: FTBFS on s390x

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > close -1 4.7.1-1 Bug #1002519 [src:calcurse] src:calcurse: fails to migrate to testing for too long: FTBFS on s390x Marked as fixed in versions calcurse/4.7.1-1. Bug #1002519 [src:calcurse] src:calcurse: fails to migrate to testing for too long: FTBFS on s390x

Bug#1002519: src:calcurse: fails to migrate to testing for too long: FTBFS on s390x

2021-12-23 Thread Paul Gevers
Source: calcurse Version: 4.6.0-2 Severity: serious Control: close -1 4.7.1-1 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60

Processed: block 1002254 with 1001591, affects 1001591

2021-12-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1002254 with 1001591 Bug #1002254 [src:lookatme] lookatme: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13 1002254 was not blocked by any bugs. 1002254 was not blocking any bugs.

Bug#1002318: python-nest-asyncio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

2021-12-23 Thread Diego M. Rodriguez
Control: tag -1 pending Hello Lucas, thanks for the bug report - I have prepared an upload of a new upstream version that includes a fix [2] for Python 3.10 support. Best, [1] https://salsa.debian.org/python-team/packages/python-nest-asyncio [2]

Processed: Re: python-nest-asyncio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1002318 [src:python-nest-asyncio] python-nest-asyncio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13 Added tag(s) pending. -- 1002318:

Bug#1002518: fwupd-unsigned: missing Breaks+Replaces: fwupd (<< ???)

2021-12-23 Thread Andreas Beckmann
Package: fwupd-unsigned Version: 1:1.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6

Bug#1001424: python-nest-asyncio: (autopkgtest) needs update for python3.10: TypeError: gather() got an unexpected keyword argument 'loop'

2021-12-23 Thread Diego M. Rodriguez
Control: tag -1 pending Hi Paul, thanks for the bug report - I have prepared an upload of a new upstream version that includes a fix [2] for Python 3.10 support. Best, [1] https://salsa.debian.org/python-team/packages/python-nest-asyncio [2]

Processed: Re: python-nest-asyncio: (autopkgtest) needs update for python3.10: TypeError: gather() got an unexpected keyword argument 'loop'

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1001424 [src:python-nest-asyncio] python-nest-asyncio: (autopkgtest) needs update for python3.10: TypeError: gather() got an unexpected keyword argument 'loop' Added tag(s) pending. -- 1001424:

Bug#1002208: marked as done (git-reintegrate: FTBFS: IndexError: tuple index out of range)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 17:39:10 +0100 with message-id and subject line no longer reproducible, closing has caused the Debian Bug report #1002208, regarding git-reintegrate: FTBFS: IndexError: tuple index out of range to be marked as done. This means that you claim that the problem

Bug#1002283: marked as done (gromit-mpx: FTBFS: -- Package 'ayatana-indicator3-0.4', required by 'ayatana-appindicator3-0.1', not found)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 17:39:10 +0100 with message-id and subject line no longer reproducible, closing has caused the Debian Bug report #1002283, regarding gromit-mpx: FTBFS: -- Package 'ayatana-indicator3-0.4', required by 'ayatana-appindicator3-0.1', not found to be marked as

Bug#1002405: marked as done (cxxtest: FTBFS: dh_installdocs: error: Cannot find (any matches for) "doc/guide.pdf" (tried in .))

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 17:39:10 +0100 with message-id and subject line no longer reproducible, closing has caused the Debian Bug report #1002405, regarding cxxtest: FTBFS: dh_installdocs: error: Cannot find (any matches for) "doc/guide.pdf" (tried in .) to be marked as done. This

Bug#1002193: marked as done (package-update-indicator: FTBFS: package-update-indicator.c:25:10: fatal error: gtk/gtk.h: No such file or directory)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 17:39:10 +0100 with message-id and subject line no longer reproducible, closing has caused the Debian Bug report #1002193, regarding package-update-indicator: FTBFS: package-update-indicator.c:25:10: fatal error: gtk/gtk.h: No such file or directory to be

Bug#1002120: marked as done (gxkb: FTBFS: configure: error: Package requirements (ayatana-appindicator3-0.1 >= 0.2.4) were not met)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 17:39:10 +0100 with message-id and subject line no longer reproducible, closing has caused the Debian Bug report #1002120, regarding gxkb: FTBFS: configure: error: Package requirements (ayatana-appindicator3-0.1 >= 0.2.4) were not met to be marked as done.

Bug#1002117: marked as done (guake-indicator: FTBFS: configure: error: Package requirements (ayatana-appindicator3-0.1 >= 0.0.13) were not met)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 17:39:10 +0100 with message-id and subject line no longer reproducible, closing has caused the Debian Bug report #1002117, regarding guake-indicator: FTBFS: configure: error: Package requirements (ayatana-appindicator3-0.1 >= 0.0.13) were not met to be marked

Bug#1002114: marked as done (puma: FTBFS: ERROR: Test "ruby2.7" failed.)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 17:39:10 +0100 with message-id and subject line no longer reproducible, closing has caused the Debian Bug report #1002114, regarding puma: FTBFS: ERROR: Test "ruby2.7" failed. to be marked as done. This means that you claim that the problem has been dealt

Bug#1002089: marked as done (libcoap3: FTBFS: configure: error: ==> Install the packages that contains the docbook DTD and XSL stylesheets (presumably docbook, docbook-xml) or disable the build of the

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 17:39:10 +0100 with message-id and subject line no longer reproducible, closing has caused the Debian Bug report #1002089, regarding libcoap3: FTBFS: configure: error: ==> Install the packages that contains the docbook DTD and XSL stylesheets (presumably

Bug#1002086: marked as done (libcoap2: FTBFS: configure: error: ==> Install the packages that contains the docbook DTD and XSL stylesheets (presumably docbook, docbook-xml) or disable the build of the

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 17:39:10 +0100 with message-id and subject line no longer reproducible, closing has caused the Debian Bug report #1002086, regarding libcoap2: FTBFS: configure: error: ==> Install the packages that contains the docbook DTD and XSL stylesheets (presumably

Bug#1002085: marked as done (clipit: FTBFS: configure: error: Package requirements (ayatana-appindicator3-0.1 >= 0.2.4) were not met)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 17:39:10 +0100 with message-id and subject line no longer reproducible, closing has caused the Debian Bug report #1002085, regarding clipit: FTBFS: configure: error: Package requirements (ayatana-appindicator3-0.1 >= 0.2.4) were not met to be marked as done.

Bug#965902: bump xom debhelper compat from 5 to 7

2021-12-23 Thread tony mancill
On Thu, Dec 23, 2021 at 09:13:33AM +0200, Andrius Merkys wrote: > Control: tags -1 + patch > > Hello, > > I have locally bumped debhelper compat to 7, rebuilt the package and ran > diffoscope between archive-provided and locally built > libxom-java_1.2.10-2_all.deb. The single change is in >

Bug#1002150: marked as done (usbguard: FTBFS: IndexError: tuple index out of range)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 17:20:03 +0100 with message-id and subject line Re: Bug#1002150: usbguard: FTBFS: IndexError: tuple index out of range has caused the Debian Bug report #1002150, regarding usbguard: FTBFS: IndexError: tuple index out of range to be marked as done. This means

Bug#1002107: marked as done (appindicator3-sharp: FTBFS: configure: error: Package requirements (ayatana-appindicator3-0.1) were not met)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 17:19:03 +0100 with message-id and subject line Re: Bug#1002107: appindicator3-sharp: FTBFS: configure: error: Package requirements (ayatana-appindicator3-0.1) were not met has caused the Debian Bug report #1002107, regarding appindicator3-sharp: FTBFS:

Bug#1000336: Upgrading tbb

2021-12-23 Thread Andreas Tille
Hi, Am Thu, Dec 23, 2021 at 11:03:56AM -0500 schrieb M. Zhou: > > I've just finished my final exams so I could do something during > the holiday. Great. Hope you finished the exams successfully. ;-) > That TBB repository is still work-in-progress and > FTBFS from the master branch is

Bug#1000336: Upgrading tbb

2021-12-23 Thread M. Zhou
Hi all, I'm back. I've just finished my final exams so I could do something during the holiday. That TBB repository is still work-in-progress and FTBFS from the master branch is something expected. I will finalize it soon. Andreas said in previous posts that we prefer a faster NEW queue process.

Bug#965795: marked as done (python-pysnmp4-mibs: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 16:21:36 +0100 with message-id <2f4b4920-6bd2-5e2e-115a-f54d37140...@debian.org> and subject line Re: python-pysnmp4-mibs: Removal of obsolete debhelper compat 5 and 6 in bookworm has caused the Debian Bug report #965795, regarding python-pysnmp4-mibs: Removal

Processed: tagging 984270

2021-12-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 984270 - fixed Bug #984270 [src:onednn] onednn: ftbfs with GCC-11 Removed tag(s) fixed. > thanks Stopping processing here. Please contact me if you need assistance. -- 984270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984270 Debian

Bug#999329: marked as done (libfile-rsyncp-perl: missing required debian/rules targets build-arch and/or build-indep)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 15:00:23 + with message-id and subject line Bug#1002499: Removed package(s) from unstable has caused the Debian Bug report #999329, regarding libfile-rsyncp-perl: missing required debian/rules targets build-arch and/or build-indep to be marked as done.

Bug#999173: marked as done (tidy-proxy: missing required debian/rules targets build-arch and/or build-indep)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 14:58:43 + with message-id and subject line Bug#1002483: Removed package(s) from unstable has caused the Debian Bug report #999173, regarding tidy-proxy: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means

Bug#965638: marked as done (libfile-rsyncp-perl: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 15:00:23 + with message-id and subject line Bug#1002499: Removed package(s) from unstable has caused the Debian Bug report #965638, regarding libfile-rsyncp-perl: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means

Bug#945242: marked as done (libfile-rsyncp-perl misses source for FileList/configure)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 15:00:23 + with message-id and subject line Bug#1002499: Removed package(s) from unstable has caused the Debian Bug report #945242, regarding libfile-rsyncp-perl misses source for FileList/configure to be marked as done. This means that you claim that the

Bug#1002439: marked as done (python-os-collect-config: FTBFS: testtools.matchers._impl.MismatchError:)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 14:37:47 + with message-id and subject line Bug#1002439: fixed in python-os-collect-config 12.0.0-2 has caused the Debian Bug report #1002439, regarding python-os-collect-config: FTBFS: testtools.matchers._impl.MismatchError: to be marked as done. This

Bug#1002441: marked as done (python-pycdlib: FTBFS: ERROR tests/integration/test_facade.py::test_facade_iso9660_get_file_from_iso)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 14:37:53 + with message-id and subject line Bug#1002441: fixed in python-pycdlib 1.12.0+ds1-3 has caused the Debian Bug report #1002441, regarding python-pycdlib: FTBFS: ERROR tests/integration/test_facade.py::test_facade_iso9660_get_file_from_iso to be

Bug#1002427: marked as done (neutron-taas: FTBFS: RuntimeError: 'auto_spec' might be a typo; use unsafe=True if this is intended)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 14:36:52 + with message-id and subject line Bug#1002427: fixed in neutron-taas 8.0.0-1 has caused the Debian Bug report #1002427, regarding neutron-taas: FTBFS: RuntimeError: 'auto_spec' might be a typo; use unsafe=True if this is intended to be marked as

Processed: Bug#1002427 marked as pending in neutron-taas

2021-12-23 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1002427 [src:neutron-taas] neutron-taas: FTBFS: RuntimeError: 'auto_spec' might be a typo; use unsafe=True if this is intended Added tag(s) pending. -- 1002427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002427 Debian Bug Tracking

Bug#1002427: marked as pending in neutron-taas

2021-12-23 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #1002427 in neutron-taas reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#965452: marked as done (chiark-tcl: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2021-12-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Dec 2021 13:48:57 + with message-id and subject line Bug#965452: fixed in chiark-tcl 1.3.5 has caused the Debian Bug report #965452, regarding chiark-tcl: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that

  1   2   >