Bug#1003644: src:frr: fails to migrate to testing for too long: FTBFS on mips64el & non-migrating new dependency

Source: frr Version: 7.5.1-1.1 Severity: serious Control: close -1 8.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 days

Processed: src:frr: fails to migrate to testing for too long: FTBFS on mips64el & non-migrating new dependency

Processing control commands: > close -1 8.1-1 Bug #1003644 [src:frr] src:frr: fails to migrate to testing for too long: FTBFS on mips64el & non-migrating new dependency Marked as fixed in versions frr/8.1-1. Bug #1003644 [src:frr] src:frr: fails to migrate to testing for too long: FTBFS on

Bug#1003643: src:lintian: fails to migrate to testing for too long: unresolved RC bug

Source: lintian Version: 2.111.0 Severity: serious Control: close -1 2.114.0 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 999768 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and

Processed: src:lintian: fails to migrate to testing for too long: unresolved RC bug

Processing control commands: > close -1 2.114.0 Bug #1003643 [src:lintian] src:lintian: fails to migrate to testing for too long: unresolved RC bug Marked as fixed in versions lintian/2.114.0. Bug #1003643 [src:lintian] src:lintian: fails to migrate to testing for too long: unresolved RC bug

Bug#1000717: supysonic: FTBFS on Python 3.10

forwarded 1000717 https://github.com/spl0k/supysonic/issues/229 thanks Pony has been updated to a version that supports python3.10, but using it, I get this testsuite error, so I can't build: == FAIL: test_add_nowait_stop

Processed: Re: supysonic: FTBFS on Python 3.10

Processing commands for cont...@bugs.debian.org: > forwarded 1000717 https://github.com/spl0k/supysonic/issues/229 Bug #1000717 [src:supysonic] supysonic: FTBFS on Python 3.10 Set Bug forwarded-to-address to 'https://github.com/spl0k/supysonic/issues/229'. > thanks Stopping processing here.

Bug#1003540: marked as done (gsl-doc: please update to 2.7.1)

Your message dated Thu, 13 Jan 2022 02:49:13 + with message-id and subject line Bug#1003540: fixed in gsl-doc 2.7.1-1 has caused the Debian Bug report #1003540, regarding gsl-doc: please update to 2.7.1 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1003540: gsl-doc: please update to 2.7.1

On 13 January 2022 at 02:29, Andreas Beckmann wrote: | On 11/01/2022 17.54, Dirk Eddelbuettel wrote: | > On 11 January 2022 at 17:31, Andreas Beckmann wrote: | > | Package: gsl-doc | > | Version: 2.6-2 | > | Severity: serious | > | > Why would that be a serious bug rather normal or even minor?

Bug#1003540: gsl-doc: please update to 2.7.1

On 11/01/2022 17.54, Dirk Eddelbuettel wrote: On 11 January 2022 at 17:31, Andreas Beckmann wrote: | Package: gsl-doc | Version: 2.6-2 | Severity: serious Why would that be a serious bug rather normal or even minor? Feel free to downgrade, but try to have the versions in sync for the

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

Your message dated Thu, 13 Jan 2022 00:33:28 + with message-id and subject line Bug#965703: fixed in liece 2.0+0.20030527cvs-13 has caused the Debian Bug report #965703, regarding liece: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim

Bug#1003617: libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken

Control: tags -1 moreinfo unreproducible On Wed, Jan 12, 2022 at 06:28:45PM +0100, Vincent-Xavier JUMEL wrote: > Package: libpam-runtime > Version: 1.4.0-11 > Severity: critical > Justification: breaks the whole system > Dear Maintainer, > >* Upgrade to the unstable version of

Processed: Re: Bug#1003617: libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken

Processing control commands: > tags -1 moreinfo unreproducible Bug #1003617 [libpam-runtime] libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken Added tag(s) moreinfo and unreproducible. -- 1003617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003617 Debian Bug

Bug#997599: marked as done (python-libusb1: FTBFS: error in libusb1 setup command: use_2to3 is invalid.)

Your message dated Wed, 12 Jan 2022 23:18:31 + with message-id and subject line Bug#997599: fixed in python-libusb1 1.10.1-0.1 has caused the Debian Bug report #997599, regarding python-libusb1: FTBFS: error in libusb1 setup command: use_2to3 is invalid. to be marked as done. This means

Bug#1003150: marked as done (python3-wheel: Missing depends on python3-distutils)

Your message dated Wed, 12 Jan 2022 23:00:10 + with message-id and subject line Bug#1003150: fixed in wheel 0.37.1-1 has caused the Debian Bug report #1003150, regarding python3-wheel: Missing depends on python3-distutils to be marked as done. This means that you claim that the problem has

Bug#1002533: marked as done (wheel: autopkgtest needs update for new version of setuptools: deprecation warning on stderr)

Your message dated Wed, 12 Jan 2022 23:00:10 + with message-id and subject line Bug#1002533: fixed in wheel 0.37.1-1 has caused the Debian Bug report #1002533, regarding wheel: autopkgtest needs update for new version of setuptools: deprecation warning on stderr to be marked as done. This

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

Your message dated Wed, 12 Jan 2022 22:49:13 + with message-id and subject line Bug#1002523: fixed in setuptools-scm 6.3.2-2 has caused the Debian Bug report #1002523, regarding setuptools-scm: autopkgtest needs update for new version of setuptools: deprecation warning is treated as error to

Bug#1002523: marked as pending in setuptools-scm

Control: tag -1 pending Hello, Bug #1002523 in setuptools-scm 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#1002523 marked as pending in setuptools-scm

Processing control commands: > tag -1 pending Bug #1002523 [src:setuptools-scm] setuptools-scm: autopkgtest needs update for new version of setuptools: deprecation warning is treated as error Added tag(s) pending. -- 1002523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002523 Debian Bug

Bug#1000650: marked as done (phploc: Failing testsuite with PHP 8.1)

Your message dated Wed, 12 Jan 2022 22:19:19 + with message-id and subject line Bug#1000650: fixed in phploc 7.0.2-2 has caused the Debian Bug report #1000650, regarding phploc: Failing testsuite with PHP 8.1 to be marked as done. This means that you claim that the problem has been dealt

Processed: severity of 1003578 is serious

Processing commands for cont...@bugs.debian.org: > severity 1003578 serious Bug #1003578 [hash-slinger] hash-slinger: Unnecessary dependency on python3-ipaddr Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1003578:

Processed: limit source to phploc, tagging 1000650

Processing commands for cont...@bugs.debian.org: > limit source phploc Limiting to bugs with field 'source' containing at least one of 'phploc' Limit currently set to 'source':'phploc' > tags 1000650 + pending Bug #1000650 [phploc] phploc: Failing testsuite with PHP 8.1 Added tag(s) pending. >

Bug#1003606: marked as done (python3-flask-httpauth: missing Breaks+Replaces: python-flask-httpauth-doc (<< 4))

Your message dated Wed, 12 Jan 2022 21:07:31 + with message-id and subject line Bug#1003606: fixed in python-flask-httpauth 4.5.0-2 has caused the Debian Bug report #1003606, regarding python3-flask-httpauth: missing Breaks+Replaces: python-flask-httpauth-doc (<< 4) to be marked as done.

Bug#1003563: aide: autopkgtest regression: unexpected character: '@' in /etc/aide/aide.conf.d/31_aide_spamassassin

tags #1003563 confirmed pending thanks On Tue, Jan 11, 2022 at 10:29:55PM +0100, Paul Gevers wrote: > With a recent upload of aide the autopkgtest of aide fails in testing when > that autopkgtest is run with the binary packages of aide from unstable. I somehow forgot to upload the fixed package

Bug#999074: iec16022: missing required debian/rules targets build-arch and/or build-indep

Debdiff attached -- ceterum censeo microsoftem esse delendam. iec16022_0.2.4-1.3.debdiff Description: Binary data pgp1MGui9kV9T.pgp Description: OpenPGP digital signature

Bug#965679: marked as done (libpixels-java: Removal of obsolete debhelper compat 5 and 6 in bookworm)

Your message dated Wed, 12 Jan 2022 20:33:04 + with message-id and subject line closing has caused the Debian Bug report #965679, regarding libpixels-java: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the problem has been

Bug#1003606: python3-flask-httpauth: missing Breaks+Replaces: python-flask-httpauth-doc (<< 4)

Argh, this was removed by `cme fix dpkg` and I trusted it.. :-/ Thanks for the report! On 12/01/2022 14:15, Andreas Beckmann wrote: Package: python3-flask-httpauth Version: 4.5.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed

Bug#1003628: imdbpy: autopkgtest failure on arm64: AssertionError: assert '' == 'Mandariinid'

Source: imdbpy Version: 2021.04.18-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package imdbpy, great. However, it fails. Currently this failure is blocking the

Bug#1003627: fpc: autopkgtest regression on ppc64el:

Source: fpc Version: 3.2.2+dfsg-5 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of fpc the autopkgtest of fpc fails in testing when that autopkgtest is run with the binary packages of

Bug#1003621: marked as done (emscripten: test_icu and test_pthread_icu attempt to download files from github)

Your message dated Wed, 12 Jan 2022 19:33:49 + with message-id and subject line Bug#1003621: fixed in emscripten 3.1.1~dfsg+~1.39.6-3 has caused the Debian Bug report #1003621, regarding emscripten: test_icu and test_pthread_icu attempt to download files from github to be marked as done.

Processed: tagging 999074

Processing commands for cont...@bugs.debian.org: > tags 999074 + pending Bug #999074 [src:iec16022] iec16022: missing required debian/rules targets build-arch and/or build-indep Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 999074:

Bug#984049: enblend-enfuse: ftbfs with GCC-11

Control: tags -1 help Hi, Am Tue, Dec 14, 2021 at 06:27:47PM +0100 schrieb Heinz Repp: > > /usr/include/vigra/separableconvolution.hxx:1413:13: error: ISO C++17 does > > not allow dynamic exception specifications > > /usr/include/vigra/stdconvolution.hxx:796:13: error: ISO C++17 does not > >

Processed: Re: enblend-enfuse: ftbfs with GCC-11

Processing control commands: > tags -1 help Bug #984049 [src:libvigraimpex] enblend-enfuse: ftbfs with GCC-11 Bug #984213 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-11 Bug #1003547 [src:libvigraimpex] hugin: Hugun begins to block for a great number of packages Bug #1003549

Processed: Bug#1003621 marked as pending in emscripten

Processing control commands: > tag -1 pending Bug #1003621 [src:emscripten] emscripten: test_icu and test_pthread_icu attempt to download files from github Added tag(s) pending. -- 1003621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003621 Debian Bug Tracking System Contact

Bug#1003621: marked as pending in emscripten

Control: tag -1 pending Hello, Bug #1003621 in emscripten 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#1003621: [Pkg-javascript-devel] Bug#1003621: emscripten: test_icu and test_pthread_icu attempt to download files from github

Quoting Mike Gerow (2022-01-12 19:40:33) > The test_icu and test_pthread_icu tests both attempt to download the > file > . > This leads to an error like this on builders where access to the > network is

Bug#1001545: [Pkg-opencl-devel] Bug#1001545: pyopencl, build-depends on package that is no longer in testing

On 2022-01-12 20:00, Rebecca N. Palmer wrote: On 12/01/2022 12:50, Drew Parsons wrote: mesa-opencl-icd is running and passing its own tests on these arches. What is pyopencl doing in build and tests that's different from what mesa-opencl-icd itself does? Probably that pyopencl's tests

Processed: block 1003573 with 1003618, block 1002444 with 1003618, tagging 1002444

Processing commands for cont...@bugs.debian.org: > block 1003573 with 1003618 Bug #1003573 [python-pip-whl] python-pip-whl: Migrate from dirtbike back to individual wheel packages 1003573 was not blocked by any bugs. 1003573 was not blocking any bugs. Added blocking bug(s) of 1003573: 1003618 >

Bug#1003309: marked as done (vdr-plugin-streamdev FTBFS: error: invalid conversion from ‘cChannel*’ to ‘int’)

Your message dated Wed, 12 Jan 2022 19:03:58 + with message-id and subject line Bug#1003309: fixed in vdr-plugin-streamdev 0.6.1+git20180514-5 has caused the Debian Bug report #1003309, regarding vdr-plugin-streamdev FTBFS: error: invalid conversion from ‘cChannel*’ to ‘int’ to be marked as

Bug#1002020: marked as done (php-proxy-manager: Failing testsuite with PHP 8.1)

Your message dated Wed, 12 Jan 2022 18:49:18 + with message-id and subject line Bug#1002020: fixed in php-proxy-manager 2.11.1+1.0.5-2 has caused the Debian Bug report #1002020, regarding php-proxy-manager: Failing testsuite with PHP 8.1 to be marked as done. This means that you claim that

Processed: limit source to php-proxy-manager, tagging 1002020

Processing commands for cont...@bugs.debian.org: > limit source php-proxy-manager Limiting to bugs with field 'source' containing at least one of 'php-proxy-manager' Limit currently set to 'source':'php-proxy-manager' > tags 1002020 + pending Bug #1002020 [php-proxy-manager] php-proxy-manager:

Bug#1000647: marked as done (php-phpseclib3: Failing testsuite with PHP 8.1)

Your message dated Wed, 12 Jan 2022 18:19:02 + with message-id and subject line Bug#1000647: fixed in php-phpseclib3 3.0.12-2 has caused the Debian Bug report #1000647, regarding php-phpseclib3: Failing testsuite with PHP 8.1 to be marked as done. This means that you claim that the problem

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

Control: found -1 249.7-1 Control: severity -1 important Am 12.01.22 um 18:20 schrieb Christian Weeks: I don't see anything in the journal, I've had a fairly long look. I do not have the coredump utility installed. As I have mentioned, rebooting fixed whatever caused the problem during the

Processed: Re: Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

Processing control commands: > found -1 249.7-1 Bug #1003611 [systemd] systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable Marked as found in versions systemd/249.7-1. > severity -1 important Bug #1003611 [systemd] systemd: Upgrade from

Bug#1003617: libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken

Package: libpam-runtime Version: 1.4.0-11 Severity: critical Justification: breaks the whole system Dear Maintainer, * Upgrade to the unstable version of libpam-runtime_1.14.0_11_all with ``` auth[success=0 default=ignore] pam_ssh.so use_first_pass ``` * Login then

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

I don't see anything in the journal, I've had a fairly long look. I do not have the coredump utility installed. As I have mentioned, rebooting fixed whatever caused the problem during the upgrade, so I have no idea how I can help you further. In looking at my running system since, I notice that

Bug#1001811: marked as done (postgresql-mysql-fdw: autopkgtest regression on armhf and i386: failed to look up symbol "evalexpr_19_0")

Your message dated Wed, 12 Jan 2022 17:18:45 + with message-id and subject line Bug#1001811: fixed in postgresql-mysql-fdw 2.7.0-2 has caused the Debian Bug report #1001811, regarding postgresql-mysql-fdw: autopkgtest regression on armhf and i386: failed to look up symbol "evalexpr_19_0" to

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

Control: tags -1 + moreinfo Hello, systemd freezes execution when it crashes (you should see a corresponding log message in the journal). For this bug report to be actionable, we will need at the very least a backtrace of the crash. In case you had systemd-coredump installed, coredumpctl

Processed: Re: Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

Processing control commands: > tags -1 + moreinfo Bug #1003611 [systemd] systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable Added tag(s) moreinfo. -- 1003611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003611 Debian Bug Tracking

Processed: Bug#1001811 marked as pending in postgresql-mysql-fdw

Processing control commands: > tag -1 pending Bug #1001811 [src:postgresql-mysql-fdw] postgresql-mysql-fdw: autopkgtest regression on armhf and i386: failed to look up symbol "evalexpr_19_0" Added tag(s) pending. -- 1001811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001811 Debian Bug

Bug#1001811: marked as pending in postgresql-mysql-fdw

Control: tag -1 pending Hello, Bug #1001811 in postgresql-mysql-fdw 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: limit source to php-phpseclib3, tagging 1000647

Processing commands for cont...@bugs.debian.org: > limit source php-phpseclib3 Limiting to bugs with field 'source' containing at least one of 'php-phpseclib3' Limit currently set to 'source':'php-phpseclib3' > tags 1000647 + pending Bug #1000647 [php-phpseclib3] php-phpseclib3: Failing

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

The reboot fixed the issue - I now have a working computer again, though getting to a reboot was a bit painful. > systemctl reboot Failed to reboot system via logind: Connection timed out Failed to start reboot.target: Connection timed out See system logs and 'systemctl status reboot.target' for

Bug#1003611: systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable

Package: systemd Version: 250.2-1 Severity: critical Justification: breaks the whole system Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I upgraded my local sid installation, which was about a week out of

Processed: Re: mpqc: ftbfs with GCC-11

Processing control commands: > forwarded -1 https://github.com/ValeevGroup/mpqc/issues/60 Bug #984244 [src:mpqc] mpqc: ftbfs with GCC-11 Set Bug forwarded-to-address to 'https://github.com/ValeevGroup/mpqc/issues/60'. -- 984244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984244 Debian

Bug#984244: mpqc: ftbfs with GCC-11

Control: forwarded -1 https://github.com/ValeevGroup/mpqc/issues/60

Bug#984121: fbreader: ftbfs with GCC-11

Hi, this patches fixes the bug. I'll do QA uploads soon. Yours, Paul Description: Fix FTBFS for gcc 11 Comparator operator() have to be const in gcc 11. Bug-Debian: http://bugs.debian.org/984121 Author: Ying-Chun Liu (PaulLiu) Index:

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

Your message dated Wed, 12 Jan 2022 15:43:52 +0100 with message-id <37cf8428-0fa8-60dc-8578-2736a666a...@debian.org> and subject line Re: lgrind: missing required debian/rules targets build-arch and/or build-indep has caused the Debian Bug report #999122, regarding lgrind: missing required

Processed: Re: aspell-cs: missing required debian/rules targets build-arch and/or build-indep

Processing control commands: > tag -1 patch pending Bug #998937 [src:aspell-cs] aspell-cs: missing required debian/rules targets build-arch and/or build-indep Added tag(s) pending and patch. -- 998937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998937 Debian Bug Tracking System Contact

Bug#998937: aspell-cs: missing required debian/rules targets build-arch and/or build-indep

Followup-For: Bug #998937 Control: tag -1 patch pending Hi, I've just uploaded a NMU to DELAYED/10 to fix this issue. Please let me know if I should delay it longer. Andreas diff -Nru aspell-cs-0.51.0/debian/changelog aspell-cs-0.51.0/debian/changelog --- aspell-cs-0.51.0/debian/changelog

Processed: do not autoremove

Processing commands for cont...@bugs.debian.org: > severity 984953 normal Bug #984953 [gparted] libgtkmm-3.0-1v5: GParted crashes on Gdk::Pixbuf::get_width() const () Severity set to 'normal' from 'grave' > severity 948739 normal Bug #948739 [gparted] gparted should not mask .mount units

Bug#1003606: python3-flask-httpauth: missing Breaks+Replaces: python-flask-httpauth-doc (<< 4)

Package: python3-flask-httpauth Version: 4.5.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 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to

Processed: reassign 990183 to src:openscap, fixed 990183 in 1.3.5-0.1, reassign 1003256 to src:linux ...

Processing commands for cont...@bugs.debian.org: > reassign 990183 src:openscap 1.3.4-1 Bug #990183 {Done: Hideki Yamane } [libopenscap8] libopenscap8: libopenscap.so.8 is missing from libopenscap8 and is expected by scap-workbench Bug reassigned from package 'libopenscap8' to 'src:openscap'.

Bug#1003561: mypy breaks python-sop autopkgtest: Missing type parameters for generic type "_SubParsersAction"

On Tue, Jan 11, 2022 at 10:22:44PM +0100, Paul Gevers wrote: > Source: mypy, python-sop > Control: found -1 mypy/0.931-1 > Control: found -1 python-sop/0.2.0-1.1 > Severity: serious > Tags: sid bookworm > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags:

Bug#1001545: pyopencl, build-depends on package that is no longer in testing

On 2022-01-12 00:04, Rebecca N. Palmer wrote: That's probably a good idea for runtime Depends, but *not* Build-Depends and test-Depends: those are likely to be run on GPU-less servers, where only CPU ICDs (i.e. pocl-opencl-icd) will work. (Roughly: pocl-opencl-icd = CPUs, mesa-opencl-icd =

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

Your message dated Wed, 12 Jan 2022 11:33:35 + with message-id and subject line Bug#999107: fixed in htag 0.0.24-2 has caused the Debian Bug report #999107, regarding htag: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim

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

Your message dated Wed, 12 Jan 2022 11:33:35 + with message-id and subject line Bug#965581: fixed in htag 0.0.24-2 has caused the Debian Bug report #965581, regarding htag: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the

Bug#1000892: marked as done (cvise: Please upgrade to llvm-toolchain-12 or 13)

Your message dated Wed, 12 Jan 2022 11:33:29 + with message-id and subject line Bug#1000892: fixed in cvise 2.4.0-2.1 has caused the Debian Bug report #1000892, regarding cvise: Please upgrade to llvm-toolchain-12 or 13 to be marked as done. This means that you claim that the problem has

Bug#1003113: python-django: CVE-2021-45115, CVE-2021-45116 & CVE-2021-45452

Hi Moritz, >> I was just looking at these CVEs for ELTS and LTS, but before I make >> a move there, I was just wondering if you were planning on (or would >> like) a DSA. > > Hi Chris, > these both seem rather harmless to me, I'd say we postpone them until > the next round of more serious Django

Processed: Forwarded to PR addressing the issue

Processing commands for cont...@bugs.debian.org: > forwarded 1002360 https://github.com/zopefoundation/zope.exceptions/pull/23 Bug #1002360 [src:zope.exceptions] zope.exceptions: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13 Set Bug

Processed: libjavascript-rpc-perl: diff for salvaging upload version 0.10-2

Processing control commands: > tags 999265 + patch pending Bug #999265 [src:libjavascript-rpc-perl] libjavascript-rpc-perl: missing required debian/rules targets build-arch and/or build-indep Ignoring request to alter tags of bug #999265 to the same tags previously set > tags 1001975 + patch

Bug#999265: libjavascript-rpc-perl: diff for salvaging upload version 0.10-2

Control: tags 999265 + patch pending Control: tags 1001975 + patch pending Dear maintainer, to fix the issues with this package, I've prepared a salvaging upload for libjavascript-rpc-perl (versioned as 0.10-2), debdiff below. An upload to DELAYED/14 will follow shortly. Please feel free to tell

Processed: libcgi-ssi-parser-perl: diff for salvaging upload version 0.01-2

Processing control commands: > tags 466397 + patch pending Bug #466397 [libcgi-ssi-parser-perl] Odd description Ignoring request to alter tags of bug #466397 to the same tags previously set > tags 999223 + patch pending Bug #999223 [src:libcgi-ssi-parser-perl] libcgi-ssi-parser-perl: missing

Bug#998954: libppd: diff for salvaging upload version 2:0.10-8

Control: tags 912689 + patch pending Control: tags 998954 + patch pending Control: tags 1001976 + patch pending Dear maintainer, to fix the issues with this package, I've prepared a salvaging upload for libppd (versioned as 2:0.10-8), debdiff below. An upload to DELAYED/14 will follow shortly.

Bug#999223: libcgi-ssi-parser-perl: diff for salvaging upload version 0.01-2

Control: tags 466397 + patch pending Control: tags 999223 + patch pending Control: tags 1001973 + patch pending Dear maintainer, to fix the issues with this package, I've prepared a salvaging upload for libcgi-ssi-parser-perl (versioned as 0.01-2), debdiff below. An upload to DELAYED/14 will

Processed: libppd: diff for salvaging upload version 2:0.10-8

Processing control commands: > tags 912689 + patch pending Bug #912689 [src:libppd] libppd FTCBFS: multiple reasons Ignoring request to alter tags of bug #912689 to the same tags previously set > tags 998954 + patch pending Bug #998954 [src:libppd] libppd: missing required debian/rules targets

Bug#998918: libdebian-package-html-perl: diff for salvaging upload version 0.1-3

Control: tags 610178 + patch pending Control: tags 998918 + patch pending Control: tags 1001974 + patch pending Dear maintainer, to fix the issues with this package, I've prepared a salvaging upload for libdebian-package-html-perl (versioned as 0.1-3), debdiff below. An upload to DELAYED/14 will

Processed: libdebian-package-html-perl: diff for salvaging upload version 0.1-3

Processing control commands: > tags 610178 + patch pending Bug #610178 [libdebian-package-html-perl] libdebian-package-html-perl: Examples URLs are no longer valid Ignoring request to alter tags of bug #610178 to the same tags previously set > tags 998918 + patch pending Bug #998918

Processed: libppd: diff for salvaging upload version 2:0.10-8

Processing control commands: > tags 912689 + patch pending Bug #912689 [src:libppd] libppd FTCBFS: multiple reasons Ignoring request to alter tags of bug #912689 to the same tags previously set > tags 998954 + patch pending Bug #998954 [src:libppd] libppd: missing required debian/rules targets

Processed: libdebian-package-html-perl: diff for salvaging upload version 0.1-3

Processing control commands: > tags 610178 + patch pending Bug #610178 [libdebian-package-html-perl] libdebian-package-html-perl: Examples URLs are no longer valid Ignoring request to alter tags of bug #610178 to the same tags previously set > tags 998918 + patch pending Bug #998918

Processed: libcgi-ssi-parser-perl: diff for salvaging upload version 0.01-2

Processing control commands: > tags 466397 + patch pending Bug #466397 [libcgi-ssi-parser-perl] Odd description Ignoring request to alter tags of bug #466397 to the same tags previously set > tags 999223 + patch pending Bug #999223 [src:libcgi-ssi-parser-perl] libcgi-ssi-parser-perl: missing

Processed: libppd: diff for salvaging upload version 2:0.10-8

Processing control commands: > tags 912689 + patch pending Bug #912689 [src:libppd] libppd FTCBFS: multiple reasons Added tag(s) pending. > tags 998954 + patch pending Bug #998954 [src:libppd] libppd: missing required debian/rules targets build-arch and/or build-indep Added tag(s) pending and

Processed: libjavascript-rpc-perl: diff for salvaging upload version 0.10-2

Processing control commands: > tags 999265 + patch pending Bug #999265 [src:libjavascript-rpc-perl] libjavascript-rpc-perl: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch and pending. > tags 1001975 + patch pending Bug #1001975 [src:libjavascript-rpc-perl]

Processed: libdebian-package-html-perl: diff for salvaging upload version 0.1-3

Processing control commands: > tags 610178 + patch pending Bug #610178 [libdebian-package-html-perl] libdebian-package-html-perl: Examples URLs are no longer valid Added tag(s) patch and pending. > tags 998918 + patch pending Bug #998918 [src:libdebian-package-html-perl]

Processed: libcgi-ssi-parser-perl: diff for salvaging upload version 0.01-2

Processing control commands: > tags 466397 + patch pending Bug #466397 [libcgi-ssi-parser-perl] Odd description Added tag(s) pending and patch. > tags 999223 + patch pending Bug #999223 [src:libcgi-ssi-parser-perl] libcgi-ssi-parser-perl: missing required debian/rules targets build-arch and/or

Bug#1003424: marked as done (halide13-api-doc: missing Breaks+Replaces: libhalide13-doc (<< 13.0.3))

Your message dated Wed, 12 Jan 2022 11:28:00 +0300 with message-id and subject line Re: Accepted halide 13.0.3-2 (source) into unstable has caused the Debian Bug report #1003424, regarding halide13-api-doc: missing Breaks+Replaces: libhalide13-doc (<< 13.0.3) to be marked as done. This means