Bug#992922: gpgme1.0: diff for NMU version 1.16.0-1.1

Control: tags 992922 + patch Control: tags 992922 + pending Dear Daniel, I've prepared an NMU for gpgme1.0 (versioned as 1.16.0-1.1) and plan to upload it to sid. According to the low-threshold list, your packages don't need to go through delayed queues, but I thought I check back with you. I ha

Processed: gpgme1.0: diff for NMU version 1.16.0-1.1

Processing control commands: > tags 992922 + patch Bug #992922 [src:gpgme1.0] gpgme1.0 FTBFS on 32bit: segfault during tests Added tag(s) patch. > tags 992922 + pending Bug #992922 [src:gpgme1.0] gpgme1.0 FTBFS on 32bit: segfault during tests Added tag(s) pending. -- 992922: https://bugs.debian.

Processed: Re: Bug#993338: octave: Setting up octave fails due to missing libGL.so.1

Processing control commands: > reassign -1 glx-diversions 1.2.0 Bug #993338 [dpkg] octave: Setting up octave fails due to missing libGL.so.1 Bug reassigned from package 'dpkg' to 'glx-diversions'. No longer marked as found in versions dpkg/1.20.9. Ignoring request to alter fixed versions of bug #9

Bug#993724: crashes when I click on PDF-files

The gnome-shell-extension-desktop-icons package isn't adapted to GNOME 40 and will probably be removed from the archive. Hopefully gnome-shell-extension-desktop-icons-ng will soon be available instead, see . It's waiting in the NEW queue. Ubuntu ships it by defa

Bug#993770: [Debian-med-packaging] Bug#993770: dazzdb: autopkgtest failure with glibc 2.32

Hi Aurélien, Aurelien Jarno, on 2021-09-14: > On 2021-09-06 11:59, Graham Inggs wrote: > As this is one of the blocker of the glibc 2.32 transition (the removal > from testing is only planned on October 20th), I have done an NMU to fix > the issue with the fix I suggested in the upstream BTS. > >

Bug#993861: marked as pending in zsh

Control: tag -1 pending Hello, Bug #993861 in zsh 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/debian/zsh/-/commit/e178f1914a35d6bd92c0818ced2d82b085eca000

Processed: Bug#993861 marked as pending in zsh

Processing control commands: > tag -1 pending Bug #993861 [src:zsh] zsh: FTBFS iff transitional package libncursesw5-dev is not installed but a package providing it (dpkg-gencontrol: error: parsing package 'zsh-static') Ignoring request to alter tags of bug #993861 to the same tags previously se

Processed: Re: Bug#993847 closed by Debian FTP Masters (reply to Jonas Smedegaard ) (Bug#993847: fixed in link-grammar 5.10.1~dfsg-2)

Processing control commands: > reopen -1 Bug #993847 {Done: Jonas Smedegaard } [src:link-grammar] link-grammar: FTBFS on 32bit Bug reopened Ignoring request to alter fixed versions of bug #993847 to the same values previously set -- 993847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993

Bug#993847: closed by Debian FTP Masters (reply to Jonas Smedegaard ) (Bug#993847: fixed in link-grammar 5.10.1~dfsg-2)

Control: reopen -1 On Tue, Sep 14, 2021 at 10:51:04PM +, Debian Bug Tracking System wrote: >... > link-grammar (5.10.1~dfsg-2) unstable; urgency=medium > . >* conditionally avoid tests > confirmed upstream to be broken on 32bit archs; >... Unfortunately the tests still fail on 32bi

Processed: notfixed 993847 in 5.10.1~dfsg-2

Processing commands for cont...@bugs.debian.org: > notfixed 993847 5.10.1~dfsg-2 Bug #993847 {Done: Jonas Smedegaard } [src:link-grammar] link-grammar: FTBFS on 32bit The source 'link-grammar' and version '5.10.1~dfsg-2' do not appear to match any binary packages No longer marked as fixed in ver

Bug#993935: marked as done (debian-edu-ltsp-install: Netboot image exposes private data and crypto keys)

Your message dated Tue, 14 Sep 2021 22:48:34 + with message-id and subject line Bug#993935: fixed in debian-edu-config 2.12.2 has caused the Debian Bug report #993935, regarding debian-edu-ltsp-install: Netboot image exposes private data and crypto keys to be marked as done. This means that

Bug#993847: marked as done (link-grammar: FTBFS on 32bit)

Your message dated Tue, 14 Sep 2021 22:49:35 + with message-id and subject line Bug#993847: fixed in link-grammar 5.10.1~dfsg-2 has caused the Debian Bug report #993847, regarding link-grammar: FTBFS on 32bit to be marked as done. This means that you claim that the problem has been dealt with

Processed: affects 994276

Processing commands for cont...@bugs.debian.org: > affects 994276 + xtel Bug #994276 [xutils-dev] xutils-dev: imake shouldn't pass l to ar Added indication that 994276 affects xtel > thanks Stopping processing here. Please contact me if you need assistance. -- 994276: https://bugs.debian.org/cgi

Bug#994276: xutils-dev: imake shouldn't pass l to ar

Package: xutils-dev Version: 1:7.7+5+b1 Severity: serious Tags: patch Justification: Makes xtel FTBFS Hello, xtel started failing to build in bullseye, e.g. https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/xtel_3.3.0-24.rbuild.log.gz “ ar clq libVideotex.a Videotex.o tvr_jpg.o t

Bug#994274: syslinux: FTBFS with gnu-efi 3.0.13

Source: syslinux Version: 3:6.04~git20190206.bf6db5b4+dfsg1-3 Severity: serious Tags: ftbfs With the new version of gnu-efi that was recently uploaded [1] to unstable, syslinux fails to build from source. So far I tried applying a simple fix from the upstream mailing list [2] which result in a s

Processed: Re: [Pkg-zsh-devel] Bug#993861: FTBFS: dpkg-gencontrol: error: parsing package 'zsh-static'

Processing control commands: > retitle -1 zsh: FTBFS iff transitional package libncursesw5-dev is not > installed but a package providing it (dpkg-gencontrol: error: parsing package > 'zsh-static') Bug #993861 [src:zsh] zsh: FTBFS related to libncursesw5-dev (dpkg-gencontrol: error: parsing pac

Bug#993861: [Pkg-zsh-devel] Bug#993861: FTBFS: dpkg-gencontrol: error: parsing package 'zsh-static'

Control: retitle -1 zsh: FTBFS iff transitional package libncursesw5-dev is not installed but a package providing it (dpkg-gencontrol: error: parsing package 'zsh-static') Control: tag -1 + confirmed pending Hi Vincent, Vincent Lefevre wrote: > > make[1]: Entering directory '/home/vinc17/tmp/zs

Bug#994270: marked as done (ghostscript/experimental: binary-any FTBFS)

Your message dated Tue, 14 Sep 2021 22:18:49 + with message-id and subject line Bug#994270: fixed in ghostscript 9.54.0~dfsg-4 has caused the Debian Bug report #994270, regarding ghostscript/experimental: binary-any FTBFS to be marked as done. This means that you claim that the problem has be

Bug#992898: marked as done (debian-parl build-depends on obsolete version of boxer-data)

Your message dated Tue, 14 Sep 2021 22:18:34 + with message-id and subject line Bug#992898: fixed in debian-parl 1.9.28 has caused the Debian Bug report #992898, regarding debian-parl build-depends on obsolete version of boxer-data to be marked as done. This means that you claim that the prob

Bug#992897: marked as done (debian-design build-depends on obsolete version of boxer-data)

Your message dated Tue, 14 Sep 2021 22:18:29 + with message-id and subject line Bug#992897: fixed in debian-design 3.0.23 has caused the Debian Bug report #992897, regarding debian-design build-depends on obsolete version of boxer-data to be marked as done. This means that you claim that the

Bug#993973: nss FTBFS with glibc 2.32: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull]

On 2021-09-09 00:52, Aurelien Jarno wrote: > control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=27476 > > On 2021-09-09 00:21, Helmut Grohne wrote: > > Source: nss > > Version: 2:3.70-1 > > Severity: serious > > Tags: ftbfs > > X-Debbugs-Cc: debian-gl...@lists.debian.org > > >

Bug#994006: marked as done (libc6: NSS modules changes require a restart of systemd-logind, which is not possible)

Your message dated Tue, 14 Sep 2021 22:04:06 + with message-id and subject line Bug#994006: fixed in glibc 2.32-3 has caused the Debian Bug report #994006, regarding libc6: NSS modules changes require a restart of systemd-logind, which is not possible to be marked as done. This means that yo

Bug#994102: marked as done (unistd.h: non-null check not correct for getcwd())

Your message dated Tue, 14 Sep 2021 22:04:06 + with message-id and subject line Bug#993973: fixed in glibc 2.32-3 has caused the Debian Bug report #993973, regarding unistd.h: non-null check not correct for getcwd() to be marked as done. This means that you claim that the problem has been dea

Bug#993973: marked as done (nss FTBFS with glibc 2.32: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull])

Your message dated Tue, 14 Sep 2021 22:04:06 + with message-id and subject line Bug#993973: fixed in glibc 2.32-3 has caused the Debian Bug report #993973, regarding nss FTBFS with glibc 2.32: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull] to b

Bug#993628: marked as done (openvdb FTBFS: Could NOT find GTest)

Your message dated Tue, 14 Sep 2021 22:04:58 + with message-id and subject line Bug#993628: fixed in openvdb 8.1.0-2 has caused the Debian Bug report #993628, regarding openvdb FTBFS: Could NOT find GTest to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#994006: marked as pending in glibc

Control: tag -1 pending Hello, Bug #994006 in glibc 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/glibc-team/glibc/-/commit/5c42bc1216d2b59e3be423f3788c500188

Processed: Bug#994006 marked as pending in glibc

Processing control commands: > tag -1 pending Bug #994006 [libc6] libc6: NSS modules changes require a restart of systemd-logind, which is not possible Ignoring request to alter tags of bug #994006 to the same tags previously set -- 994006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=9940

Processed: Bug#993973 marked as pending in glibc

Processing control commands: > tag -1 pending Bug #993973 [libc6-dev] nss FTBFS with glibc 2.32: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull] Bug #994102 [libc6-dev] unistd.h: non-null check not correct for getcwd() Ignoring request to alter tags

Bug#993973: marked as pending in glibc

Control: tag -1 pending Hello, Bug #993973 in glibc 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/glibc-team/glibc/-/commit/096db86fcbb754c30a5ede856edd46d827

Bug#993628: marked as pending in openvdb

Control: tag -1 pending Hello, Bug #993628 in openvdb 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/multimedia-team/openvdb/-/commit/b734f43d0d43c9d7defbf950d

Processed: Bug#993628 marked as pending in openvdb

Processing control commands: > tag -1 pending Bug #993628 [src:openvdb] openvdb FTBFS: Could NOT find GTest Added tag(s) pending. -- 993628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993628 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#993973: marked as pending in glibc

Control: tag -1 pending Hello, Bug #993973 in glibc 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/glibc-team/glibc/-/commit/096db86fcbb754c30a5ede856edd46d827

Processed: Bug#993973 marked as pending in glibc

Processing control commands: > tag -1 pending Bug #993973 [libc6-dev] nss FTBFS with glibc 2.32: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull] Bug #994102 [libc6-dev] unistd.h: non-null check not correct for getcwd() Added tag(s) pending. Added ta

Bug#994105: marked as done (squashfs-tools-ng FTBFS on i386 due to bogus test)

Your message dated Tue, 14 Sep 2021 21:19:53 + with message-id and subject line Bug#994105: fixed in squashfs-tools-ng 1.1.3-2 has caused the Debian Bug report #994105, regarding squashfs-tools-ng FTBFS on i386 due to bogus test to be marked as done. This means that you claim that the problem

Bug#994270: ghostscript/experimental: binary-any FTBFS

Source: ghostscript Version: 9.54.0~dfsg-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=ghostscript&suite=experimental ... dh_missing -a -O--no-parallel dh_missing: warning: usr/share/ghostscript/9.54.0/Resource/CIDFSubst/DroidSansFallback.ttf exists in debian

Bug#994269: node-jest/experimental FTBFS: build hang

Source: node-jest Version: 27.1.0~ds+~cs67.45.23-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd64/node-jest.html https://buildd.debian.org/status/package.php?p=node-jest&suite=experimental ... dh_auto_build --buildsystem=nodejs Found debian/no

Bug#971319: marked as done (aubio: uses deprecated libavresample)

Your message dated Tue, 14 Sep 2021 20:35:35 + with message-id and subject line Bug#971319: fixed in aubio 0.4.9-4.1 has caused the Debian Bug report #971319, regarding aubio: uses deprecated libavresample to be marked as done. This means that you claim that the problem has been dealt with. I

Processed: Re: Bug#994265: pypy breaks python-virtualenv autopkgtest on ppc64el: RuntimeError: maximum recursion depth exceeded

Processing control commands: > forwarded -1 https://foss.heptapod.net/pypy/pypy/-/issues/3463 Bug #994265 [src:pypy, src:python-virtualenv] pypy breaks python-virtualenv autopkgtest on ppc64el: RuntimeError: maximum recursion depth exceeded Set Bug forwarded-to-address to 'https://foss.heptapod.

Bug#994265: pypy breaks python-virtualenv autopkgtest on ppc64el: RuntimeError: maximum recursion depth exceeded

Control: forwarded -1 https://foss.heptapod.net/pypy/pypy/-/issues/3463 Yeah, aware of this issue. I'm going to have to disable the JIT on PPC until it's fixed upstream, I think. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#953032: Please import fix

Can you please update so we can see if https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/137 really fixes the problem? My disks are reaching the breaking point.

Processed: pyjwt breaks azure-cli autopkgtest: Could not deserialize key data. The data may be in an incorrect format or it may be encrypted with an unsupported algorithm.

Processing control commands: > found -1 pyjwt/2.1.0-1 Bug #994266 [src:pyjwt, src:azure-cli] pyjwt breaks azure-cli autopkgtest: Could not deserialize key data. The data may be in an incorrect format or it may be encrypted with an unsupported algorithm. Marked as found in versions pyjwt/2.1.0-1.

Bug#994266: pyjwt breaks azure-cli autopkgtest: Could not deserialize key data. The data may be in an incorrect format or it may be encrypted with an unsupported algorithm.

Source: pyjwt, azure-cli Control: found -1 pyjwt/2.1.0-1 Control: found -1 azure-cli/2.18.0-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 upload of pyjwt the autopkgt

Bug#994265: pypy breaks python-virtualenv autopkgtest on ppc64el: RuntimeError: maximum recursion depth exceeded

Source: pypy, python-virtualenv Control: found -1 pypy/7.3.5+dfsg-2 Control: found -1 python-virtualenv/20.4.0+ds-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 upload

Processed: pypy breaks python-virtualenv autopkgtest on ppc64el: RuntimeError: maximum recursion depth exceeded

Processing control commands: > found -1 pypy/7.3.5+dfsg-2 Bug #994265 [src:pypy, src:python-virtualenv] pypy breaks python-virtualenv autopkgtest on ppc64el: RuntimeError: maximum recursion depth exceeded Marked as found in versions pypy/7.3.5+dfsg-2. > found -1 python-virtualenv/20.4.0+ds-2 Bug

Bug#983473: marked as done (libcloudflare-client-perl: broken and seemingly dead upstream)

Your message dated Tue, 14 Sep 2021 19:45:13 + with message-id and subject line Bug#992387: Removed package(s) from unstable has caused the Debian Bug report #983473, regarding libcloudflare-client-perl: broken and seemingly dead upstream to be marked as done. This means that you claim that t

Bug#991296: marked as done (Should deltachat-core be shipped in bullseye?)

Your message dated Tue, 14 Sep 2021 19:38:58 + with message-id and subject line Bug#991284: Removed package(s) from unstable has caused the Debian Bug report #991296, regarding Should deltachat-core be shipped in bullseye? to be marked as done. This means that you claim that the problem has b

Bug#990219: marked as done (libprotocol-acme-perl implements ACMEv1 protocol which is no longer usable)

Your message dated Tue, 14 Sep 2021 19:35:02 + with message-id and subject line Bug#990292: Removed package(s) from unstable has caused the Debian Bug report #990219, regarding libprotocol-acme-perl implements ACMEv1 protocol which is no longer usable to be marked as done. This means that yo

Bug#994259: resfinder: autopkgtest regression on armhf and i386: db_resfinder --kmaPath /usr/bin/kma' returned non-zero exit status 1

Source: resfinder Version: 4.1.5-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 resfinder the autopkgtest of resfinder fails in testing on armhf and i386 when that autopkgtest is run wi

Bug#990042: marked as done (libnet-amazon-perl: Net::Amazon broken with Amazon API changes?)

Your message dated Tue, 14 Sep 2021 19:31:04 + with message-id and subject line Bug#990159: Removed package(s) from unstable has caused the Debian Bug report #990042, regarding libnet-amazon-perl: Net::Amazon broken with Amazon API changes? to be marked as done. This means that you claim that

Bug#989657: marked as done (Current sogo-connector does not work with current Mozilla Thunderbird)

Your message dated Tue, 14 Sep 2021 19:28:49 + with message-id and subject line Bug#989788: Removed package(s) from unstable has caused the Debian Bug report #989657, regarding Current sogo-connector does not work with current Mozilla Thunderbird to be marked as done. This means that you clai

Bug#979581: marked as done (OpenJDK 15 should stay out of testing)

Your message dated Tue, 14 Sep 2021 19:29:21 + with message-id and subject line Bug#990015: Removed package(s) from unstable has caused the Debian Bug report #979581, regarding OpenJDK 15 should stay out of testing to be marked as done. This means that you claim that the problem has been deal

Bug#992973: plib: CVE-2021-38714

Am Wed, Aug 25, 2021 at 09:23:37PM +0200 schrieb Salvatore Bonaccorso: > Source: plib > Version: 1.8.5-8 > Severity: grave > Tags: security upstream > Justification: user security hole > Forwarded: https://sourceforge.net/p/plib/bugs/55/ > X-Debbugs-Cc: car...@debian.org, Debian Security Team > >

Processed: python-django breaks lava autopkgtest: PASSWORD_RESET_TIMEOUT_DAYS/PASSWORD_RESET_TIMEOUT are mutually exclusive.

Processing control commands: > found -1 python-django/2:3.2.7-4 Bug #994258 [src:python-django, src:lava] python-django breaks lava autopkgtest: PASSWORD_RESET_TIMEOUT_DAYS/PASSWORD_RESET_TIMEOUT are mutually exclusive. Marked as found in versions python-django/2:3.2.7-4. > found -1 lava/2020.12

Bug#994258: python-django breaks lava autopkgtest: PASSWORD_RESET_TIMEOUT_DAYS/PASSWORD_RESET_TIMEOUT are mutually exclusive.

Source: python-django, lava Control: found -1 python-django/2:3.2.7-4 Control: found -1 lava/2020.12-5 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 upload of python-dj

Bug#989288: marked as done (CVE-2021-29629)

Your message dated Tue, 14 Sep 2021 19:26:44 + with message-id and subject line Bug#989402: Removed package(s) from unstable has caused the Debian Bug report #989288, regarding CVE-2021-29629 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#994257: python-django breaks django-ldapdb autopkgtest: 'Field' object has no attribute 'attname'

Source: python-django, django-ldapdb Control: found -1 python-django/2:3.2.7-4 Control: found -1 django-ldapdb/1.5.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 upl

Processed: python-django breaks django-ldapdb autopkgtest: 'Field' object has no attribute 'attname'

Processing control commands: > found -1 python-django/2:3.2.7-4 Bug #994257 [src:python-django, src:django-ldapdb] python-django breaks django-ldapdb autopkgtest: 'Field' object has no attribute 'attname' Marked as found in versions python-django/2:3.2.7-4. > found -1 django-ldapdb/1.5.1-2 Bug #9

Bug#929781: marked as done (rkt: CVE-2019-10144 CVE-2019-10145 CVE-2019-10147)

Your message dated Tue, 14 Sep 2021 19:19:20 + with message-id and subject line Bug#988672: Removed package(s) from unstable has caused the Debian Bug report #929781, regarding rkt: CVE-2019-10144 CVE-2019-10145 CVE-2019-10147 to be marked as done. This means that you claim that the problem h

Bug#880914: marked as done (flannel FTBFS with golang-github-vishvananda-netlink-dev 0.0~git20170407.0.1e86b2b-1)

Your message dated Tue, 14 Sep 2021 19:19:54 + with message-id and subject line Bug#988677: Removed package(s) from unstable has caused the Debian Bug report #880914, regarding flannel FTBFS with golang-github-vishvananda-netlink-dev 0.0~git20170407.0.1e86b2b-1 to be marked as done. This mea

Bug#994256: django-axes: autopkgtest needs update for new version of python-django: warnings changed

Source: django-axes Version: 5.4.3-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, python-dja...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:python-django Dear maintainer(s), With a recent upload of python-dj

Processed: django-axes: autopkgtest needs update for new version of python-django: warnings changed

Processing control commands: > affects -1 src:python-django Bug #994256 [src:django-axes] django-axes: autopkgtest needs update for new version of python-django: warnings changed Added indication that 994256 affects src:python-django -- 994256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=

Bug#994255: djangorestframework: autopkgtest needs update for new version of python-django: error changed

Source: djangorestframework Version: 3.12.1-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, python-dja...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:python-django Dear maintainer(s), With a recent upload of

Processed: djangorestframework: autopkgtest needs update for new version of python-django: error changed

Processing control commands: > affects -1 src:python-django Bug #994255 [src:djangorestframework] djangorestframework: autopkgtest needs update for new version of python-django: error changed Added indication that 994255 affects src:python-django -- 994255: https://bugs.debian.org/cgi-bin/bugre

Bug#992244: marked as done (mongo-cxx-driver: keep out of testing)

Your message dated Tue, 14 Sep 2021 19:12:53 + with message-id and subject line Bug#988388: Removed package(s) from unstable has caused the Debian Bug report #992244, regarding mongo-cxx-driver: keep out of testing to be marked as done. This means that you claim that the problem has been deal

Bug#991389: marked as done (Should keytouch-editor get removed from bullseye?)

Your message dated Tue, 14 Sep 2021 19:13:33 + with message-id and subject line Bug#988541: Removed package(s) from unstable has caused the Debian Bug report #991389, regarding Should keytouch-editor get removed from bullseye? to be marked as done. This means that you claim that the problem h

Bug#991388: marked as done (Should prometheus-nginx-vts-exporter be removed from bullseye?)

Your message dated Tue, 14 Sep 2021 19:10:54 + with message-id and subject line Bug#988002: Removed package(s) from unstable has caused the Debian Bug report #991388, regarding Should prometheus-nginx-vts-exporter be removed from bullseye? to be marked as done. This means that you claim that

Bug#862786: marked as done (pdmenu depends on the obsolete Debian menu)

Your message dated Tue, 14 Sep 2021 19:05:31 + with message-id and subject line Bug#987483: Removed package(s) from unstable has caused the Debian Bug report #862786, regarding pdmenu depends on the obsolete Debian menu to be marked as done. This means that you claim that the problem has been

Bug#980024: marked as done (pdmenu: FTBFS with GCC 10)

Your message dated Tue, 14 Sep 2021 19:05:31 + with message-id and subject line Bug#987483: Removed package(s) from unstable has caused the Debian Bug report #980024, regarding pdmenu: FTBFS with GCC 10 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#993770: marked as done (dazzdb: autopkgtest failure with glibc 2.32)

Your message dated Tue, 14 Sep 2021 19:03:48 + with message-id and subject line Bug#993770: fixed in dazzdb 1.0+git20201103.8d98c37-1.1 has caused the Debian Bug report #993770, regarding dazzdb: autopkgtest failure with glibc 2.32 to be marked as done. This means that you claim that the prob

Bug#987926: marked as done (RM: gimp-dcraw, upstream gone, possible security flaws)

Your message dated Tue, 14 Sep 2021 19:03:18 + with message-id and subject line Bug#987443: Removed package(s) from unstable has caused the Debian Bug report #987926, regarding RM: gimp-dcraw, upstream gone, possible security flaws to be marked as done. This means that you claim that the prob

Bug#991387: marked as done (Should librpcsecgss be shipped in bullseye?)

Your message dated Tue, 14 Sep 2021 19:01:16 + with message-id and subject line Bug#986300: Removed package(s) from unstable has caused the Debian Bug report #991387, regarding Should librpcsecgss be shipped in bullseye? to be marked as done. This means that you claim that the problem has bee

Bug#944872: marked as done (libindicator FTBFS: error: G_ADD_PRIVATE [-Werror])

Your message dated Tue, 14 Sep 2021 18:57:26 + with message-id and subject line Bug#895038: Removed package(s) from unstable has caused the Debian Bug report #944872, regarding libindicator FTBFS: error: G_ADD_PRIVATE [-Werror] to be marked as done. This means that you claim that the problem

Bug#895038: marked as done (RM: libindicator -- RoQA; deprecated, no longer used)

Your message dated Tue, 14 Sep 2021 18:57:22 + with message-id and subject line Bug#895038: Removed package(s) from unstable has caused the Debian Bug report #895038, regarding RM: libindicator -- RoQA; deprecated, no longer used to be marked as done. This means that you claim that the proble

Bug#895037: marked as done (RM: libappindicator -- RoQA; deprecated, no longer used)

Your message dated Tue, 14 Sep 2021 18:56:51 + with message-id and subject line Bug#895037: Removed package(s) from unstable has caused the Debian Bug report #895037, regarding RM: libappindicator -- RoQA; deprecated, no longer used to be marked as done. This means that you claim that the pro

Bug#994109: scilab FTBFS with hdf5 1.10.7

Julien Puydt a écrit le 13/09/2021 à 08:51 : Excellent! Please commit to salsa but don't upload yet Done. Best, _g.

Bug#993770: dazzdb: autopkgtest failure with glibc 2.32

On 2021-09-06 11:59, Graham Inggs wrote: > Source: dazzdb > Version: 1.0+git20201103.8d98c37-1 > Severity: serious > Forwarded: https://github.com/thegenemyers/DAZZ_DB/issues/41 > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: needs-update > > Hi Maintainer

Bug#994006: marked as pending in glibc

Control: tag -1 pending Hello, Bug #994006 in glibc 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/glibc-team/glibc/-/commit/5c42bc1216d2b59e3be423f3788c500188

Processed: Bug#994006 marked as pending in glibc

Processing control commands: > tag -1 pending Bug #994006 [libc6] libc6: NSS modules changes require a restart of systemd-logind, which is not possible Added tag(s) pending. -- 994006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994006 Debian Bug Tracking System Contact ow...@bugs.debian.

Bug#978898: marked as done (rofi: ftbfs with autoconf 2.70)

Your message dated Tue, 14 Sep 2021 18:49:45 + with message-id and subject line Bug#978898: fixed in rofi 1.5.4-1.1 has caused the Debian Bug report #978898, regarding rofi: ftbfs with autoconf 2.70 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#993946: marked as done (fakechroot: adduser fails with glibc 2.32)

Your message dated Tue, 14 Sep 2021 18:49:25 + with message-id and subject line Bug#993946: fixed in fakechroot 2.19-3.5 has caused the Debian Bug report #993946, regarding fakechroot: adduser fails with glibc 2.32 to be marked as done. This means that you claim that the problem has been deal

Bug#994006: libc6: NSS modules changes require a restart of systemd-logind, which is not possible

On 2021-09-14 08:56, Simon McVittie wrote: > On Mon, 13 Sep 2021 at 22:59:32 +0200, Aurelien Jarno wrote: > > - running the operation on a non-existing user, but as loginctl does a > > check that the user exists, it has to be done directly with the dbus > > API, for instance "gdbus call --syste

Bug#993750: rgtk2: FTBFS on s390x: smoke-test failure: caught segfault

Hi Philipp, Hi Simon, If we have no resolution on this I will have no other way than to re-upload r-cran-rgtk2 with a build exclusion for s390 as I now have an autoremoval notice for it (and another package I look after than depends on it). Or do we have other/better options? Dirk -- https:/

Bug#994106: marked as done (libhdf4: FTBFS with TIRPC)

Your message dated Tue, 14 Sep 2021 15:48:37 + with message-id and subject line Bug#994106: fixed in libhdf4 4.2.15-4 has caused the Debian Bug report #994106, regarding libhdf4: FTBFS with TIRPC to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: tagging 994106 ...

Processing commands for cont...@bugs.debian.org: > tags 994106 + upstream Bug #994106 [src:libhdf4] libhdf4: FTBFS with TIRPC Added tag(s) upstream. > forwarded 994106 > https://jira.hdfgroup.org/servicedesk/customer/portal/2/SUPPORT-1571 Bug #994106 [src:libhdf4] libhdf4: FTBFS with TIRPC Set Bu

Bug#994241: ruby-lapack autopkgtest needs to be adapted for LAPACK 3.10

Package: ruby-lapack Version: 1.8.1-1 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: needs-update Dear Maintainer, Since the upload of lapack 3.10.0-1, the autopkgtest of ruby-lapack fails in unstable. See for example: http

Processed: retitle 895037 to RM: libappindicator -- RoQA; deprecated, no longer used ...

Processing commands for cont...@bugs.debian.org: > retitle 895037 RM: libappindicator -- RoQA; deprecated, no longer used Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s) Changed Bug title to 'RM:

Processed: retitle 895038 to RM: libindicator -- RoQA; deprecated, no longer used ...

Processing commands for cont...@bugs.debian.org: > retitle 895038 RM: libindicator -- RoQA; deprecated, no longer used Bug #895038 [src:libindicator] libindicator: deprecated in Debian, switch to libayatana-indicator instead Changed Bug title to 'RM: libindicator -- RoQA; deprecated, no longer us

Bug#994214: nomad FTBFS in unstable

On Tuesday, 14 September 2021 5:20:03 AM AEST Steve Langasek wrote: > The nomad package fails to build from source in Ubuntu, so in the process > of investigating this build failure I confirmed that it also fails to > build in Debian unstable: Thanks for reporting but most certainly I won't be abl

Processed: Re: Bug#993338: octave: Setting up octave fails due to missing libGL.so.1

Processing control commands: > reassign -1 dpkg 1.20.9 Bug #993338 [octave] octave: Setting up octave fails due to missing libGL.so.1 Bug reassigned from package 'octave' to 'dpkg'. No longer marked as found in versions octave/6.2.0-1. Ignoring request to alter fixed versions of bug #993338 to the

Bug#993338: octave: Setting up octave fails due to missing libGL.so.1

Control: reassign -1 dpkg 1.20.9 Dear Witold, Le dimanche 12 septembre 2021 à 15:24 +, Witold Baryluk a écrit : > Package: octave > Version: 6.2.0-1 > Followup-For: Bug #993338 > X-Debbugs-Cc: witold.bary...@gmail.com > > After a lof of trial and error and minimizing my package list from ~70

Bug#971322: marked as done (performous: uses deprecated libavresample)

Your message dated Tue, 14 Sep 2021 08:50:46 + with message-id and subject line Bug#971322: fixed in performous 1.1+git20190701.9928c27-4 has caused the Debian Bug report #971322, regarding performous: uses deprecated libavresample to be marked as done. This means that you claim that the prob

Bug#971322: marked as done (performous: uses deprecated libavresample)

Your message dated Tue, 14 Sep 2021 08:35:59 + with message-id and subject line Bug#971322: fixed in performous 1.1+git20181118-5 has caused the Debian Bug report #971322, regarding performous: uses deprecated libavresample to be marked as done. This means that you claim that the problem has

Bug#971322: marked as pending in performous

Control: tag -1 pending Hello, Bug #971322 in performous 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/games-team/performous/-/commit/b956fb874c11789769c148a3

Processed: Bug#971322 marked as pending in performous

Processing control commands: > tag -1 pending Bug #971322 [src:performous] performous: uses deprecated libavresample Ignoring request to alter tags of bug #971322 to the same tags previously set -- 971322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971322 Debian Bug Tracking System Contac

Bug#971322: marked as pending in performous

Control: tag -1 pending Hello, Bug #971322 in performous 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/games-team/performous/-/commit/b956fb874c11789769c148a3

Processed: Bug#971322 marked as pending in performous

Processing control commands: > tag -1 pending Bug #971322 [src:performous] performous: uses deprecated libavresample Added tag(s) pending. -- 971322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971322 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: reassign to gfortran

Processing commands for cont...@bugs.debian.org: > clone 993992 -1 -2 Bug #993992 [src:ncl] ncl: FTBFS on i386, mipsel, mips64el Bug 993992 cloned as bugs 994227-994228 992563 was blocked by: 992527 992528 993992 992563 was not blocking any bugs. Added blocking bug(s) of 992563: 994227 992563 was

Processed: affects 994006

Processing commands for cont...@bugs.debian.org: > affects 994006 + monkeysphere Bug #994006 [libc6] libc6: NSS modules changes require a restart of systemd-logind, which is not possible Added indication that 994006 affects monkeysphere > thanks Stopping processing here. Please contact me if you

Processed: affects 994006

Processing commands for cont...@bugs.debian.org: > affects 994006 + wlr-randr Bug #994006 [libc6] libc6: NSS modules changes require a restart of systemd-logind, which is not possible Added indication that 994006 affects wlr-randr > thanks Stopping processing here. Please contact me if you need

Processed: affects 994006

Processing commands for cont...@bugs.debian.org: > affects 994006 + matplotlib Bug #994006 [libc6] libc6: NSS modules changes require a restart of systemd-logind, which is not possible Added indication that 994006 affects matplotlib > thanks Stopping processing here. Please contact me if you nee

  1   2   >