Processed: src:ca-certificates: fails to migrate to testing for too long: unresolved RC bug

2022-01-03 Thread Debian Bug Tracking System
Processing control commands: > close -1 20211016 Bug #1003105 [src:ca-certificates] src:ca-certificates: fails to migrate to testing for too long: unresolved RC bug Marked as fixed in versions ca-certificates/20211016. Bug #1003105 [src:ca-certificates] src:ca-certificates: fails to migrate to

Bug#1003105: src:ca-certificates: fails to migrate to testing for too long: unresolved RC bug

2022-01-03 Thread Paul Gevers
Source: ca-certificates Version: 20210119 Severity: serious Control: close -1 20211016 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 996048 Dear maintainer(s), Julien, The Release Team considers packages that are out-of-sync between

Processed: src:pktanon: fails to migrate to testing for too long: autopkgtest regression on armhf

2022-01-03 Thread Debian Bug Tracking System
Processing control commands: > close -1 2~git20160407.0.2bde4f2+dfsg-8 Bug #1003104 [src:pktanon] src:pktanon: fails to migrate to testing for too long: autopkgtest regression on armhf Marked as fixed in versions pktanon/2~git20160407.0.2bde4f2+dfsg-8. Bug #1003104 [src:pktanon] src:pktanon:

Bug#1003104: src:pktanon: fails to migrate to testing for too long: autopkgtest regression on armhf

2022-01-03 Thread Paul Gevers
Source: pktanon Version: 2~git20160407.0.2bde4f2+dfsg-7 Severity: serious Control: close -1 2~git20160407.0.2bde4f2+dfsg-8 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 999620 Dear maintainer(s), Sascha, [What follows is a template,

Processed: slim: diff for NMU version 1.3.6-5.3

2022-01-03 Thread Debian Bug Tracking System
Processing control commands: > tags 984339 + patch Bug #984339 [src:slim] slim: ftbfs with GCC-11 Added tag(s) patch. > tags 984339 + pending Bug #984339 [src:slim] slim: ftbfs with GCC-11 Added tag(s) pending. -- 984339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984339 Debian Bug

Bug#984339: slim: diff for NMU version 1.3.6-5.3

2022-01-03 Thread Christoph Biedl
Control: tags 984339 + patch Control: tags 984339 + pending Dear maintainer, To resolve the sitatuation, I've prepared an NMU for slim (versioned as 1.3.6-5.3), upload to DELAYED/2 will follow shortly. Please feel free to tell me if I should delay it longer. Regards. diff -Nru

Bug#984339: slim: ftbfs with GCC-11

2022-01-03 Thread Christoph Biedl
Slavko wrote... > i use slim, thus i wonder about its future. The patch proposed by > Hugo Torres doesn't look as solution for me, but searching lead me > to gentoo's bug tracker and and it's git, where i found: > > + the bugreport with the same problem at https://bugs.gentoo.org/786498 > +

Processed: console-cyrillic: diff for NMU version 0.9-17.2

2022-01-03 Thread Debian Bug Tracking System
Processing control commands: > tags 999069 + patch Bug #999069 [src:console-cyrillic] console-cyrillic: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999069 + pending Bug #999069 [src:console-cyrillic] console-cyrillic: missing required

Bug#999069: console-cyrillic: diff for NMU version 0.9-17.2

2022-01-03 Thread Adrian Bunk
Control: tags 999069 + patch Control: tags 999069 + pending Dear maintainer, I've prepared an NMU for console-cyrillic (versioned as 0.9-17.2) and uploaded it to DELAYED/7. Please feel free to tell me if I should cancel it. cu Adrian diff -u console-cyrillic-0.9/debian/changelog

Bug#999169: cconv: diff for NMU version 0.6.2-1.2

2022-01-03 Thread Adrian Bunk
Control: tags 679383 + pending Control: tags 999169 + patch Control: tags 999169 + pending Dear maintainer, I've prepared an NMU for cconv (versioned as 0.6.2-1.2) and uploaded it to DELAYED/7. Please feel free to tell me if I should cancel it. cu Adrian diff -u cconv-0.6.2/debian/changelog

Processed: cconv: diff for NMU version 0.6.2-1.2

2022-01-03 Thread Debian Bug Tracking System
Processing control commands: > tags 679383 + pending Bug #679383 [cconv] cconv: package description review Added tag(s) pending. > tags 999169 + patch Bug #999169 [src:cconv] cconv: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999169 + pending

Processed: cconv: diff for NMU version 0.6.2-1.2

2022-01-03 Thread Debian Bug Tracking System
Processing control commands: > tags 679383 + pending Bug #679383 [cconv] cconv: package description review Ignoring request to alter tags of bug #679383 to the same tags previously set > tags 999169 + patch Bug #999169 [src:cconv] cconv: missing required debian/rules targets build-arch and/or

Bug#1003103: Clients are missing from the package

2022-01-03 Thread Arto Jantunen
Package: elpa-lsp-mode Version: 8.0.0-2 Severity: grave Tags: patch X-Debbugs-Cc: tho...@koch.ro A large part of the program isn't included in the package, see a debdiff between version 8.0.0-2 and a correctly built package: Files in first .deb but not in second

Bug#1002982: marked as done (elpa-org: post-installation script subprocess returned error exit status 1)

2022-01-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Jan 2022 02:38:50 + with message-id and subject line Bug#1002982: fixed in org-mode 9.5.2+dfsh-3 has caused the Debian Bug report #1002982, regarding elpa-org: post-installation script subprocess returned error exit status 1 to be marked as done. This means that

Bug#1002982: elpa-org: post-installation script subprocess returned error exit status 1

2022-01-03 Thread Sean Whitton
control: reopen -1 Hello Gregory, On Mon 03 Jan 2022 at 10:09pm +01, Gregory Mounie wrote: > Thanks for the addition of org-version.el but I suspect another bug > still exist in the auto-generation of the file: > > The org-version and org-git-version strings in >

Processed: Re: Bug#1002982: elpa-org: post-installation script subprocess returned error exit status 1

2022-01-03 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1002982 {Done: Sean Whitton } [elpa-org] elpa-org: post-installation script subprocess returned error exit status 1 Bug reopened Ignoring request to alter fixed versions of bug #1002982 to the same values previously set -- 1002982:

Bug#1002708: marked as done (python3-gleetex: needs Depends: dvisvgm)

2022-01-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Jan 2022 01:33:32 + with message-id and subject line Bug#1002708: fixed in gladtex 3.1.0-2 has caused the Debian Bug report #1002708, regarding python3-gleetex: needs Depends: dvisvgm to be marked as done. This means that you claim that the problem has been dealt

Bug#965679: ..

2022-01-03 Thread Martina Ferrari
Somehow I had missed this bug report. I will prepare a new upload ASAP. -- Martina Ferrari (Tina)

Bug#1001168: Info received (Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py))

2022-01-03 Thread PICCA Frederic-emmanuel
Built with gcc-11 and -fno-lto it doesn not work. (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ ../../../test.py Segmentation fault (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ PYTHONPATH=. ../../../test.py Segmentation fault

Bug#998534: intel-gpu-tools: FTBFS: ../lib/meson.build:155:4: ERROR: Function does not take positional arguments.

2022-01-03 Thread Páder Rezső
Hello, FYI, this error is fixed in upstream git: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/commit/963917a3565466832a3b2fc22e9285d34a0bf944 -- R.

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 21:33:40 + with message-id and subject line Bug#999149: fixed in dhcp-helper 1.2-3 has caused the Debian Bug report #999149, regarding dhcp-helper: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that

Bug#1003043: marked as done (kicad: b-d on libpython3-all-dev, but not built for all supported Python3 versions)

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 21:33:56 + with message-id and subject line Bug#1003043: fixed in kicad 6.0.0+dfsg1-2 has caused the Debian Bug report #1003043, regarding kicad: b-d on libpython3-all-dev, but not built for all supported Python3 versions to be marked as done. This means

Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py)

2022-01-03 Thread PICCA Frederic-emmanuel
I tested matplotlib built with numpy 0.17 0.19 0.21. each time I got the segfault. another difference was the gcc compiler. So I switched to gcc-10 (sid_mips64el-dchroot)picca@eller:~/matplotlib$ CC=gcc-10 python3 setup.py build if failed with this error lto1: fatal error: bytecode stream in

Bug#1002982: elpa-org: post-installation script subprocess returned error exit status 1

2022-01-03 Thread Gregory Mounie
Package: elpa-org Version: 9.5.2+dfsh-2 Followup-For: Bug #1002982 Dear Maintainer, Thanks for the addition of org-version.el but I suspect another bug still exist in the auto-generation of the file: The org-version and org-git-version strings in

Bug#1002142: marked as done (shasta: FTBFS: PythonModule.cpp:40:29: error: expected primary-expression before ‘(’ token)

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 20:43:10 + with message-id and subject line Bug#1002142: fixed in shasta 0.8.0-2 has caused the Debian Bug report #1002142, regarding shasta: FTBFS: PythonModule.cpp:40:29: error: expected primary-expression before ‘(’ token to be marked as done. This

Processed: tagging 1002323

2022-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1002323 + pending Bug #1002323 [src:flask-jwt-simple] flask-jwt-simple: FTBFS: dh_auto_test: error: pybuild --test --test-tox -i python{version} -p "3.10 3.9" returned exit code 13 Added tag(s) pending. > thanks Stopping processing here.

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 19:51:21 + with message-id and subject line Bug#1002518: fixed in fwupd-efi 1:1.1-2 has caused the Debian Bug report #1002518, regarding fwupd-unsigned: missing Breaks+Replaces: fwupd (<< ???) to be marked as done. This means that you claim that the

Processed: closing 997227

2022-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 997227 2021.11.001-1 Bug #997227 [src:elpa] elpa: FTBFS: ./build/conftest.F90:2: undefined reference to `dgemm_' Marked as fixed in versions elpa/2021.11.001-1. Bug #997227 [src:elpa] elpa: FTBFS: ./build/conftest.F90:2: undefined

Bug#966742: marked as done (git-hub: Unversioned Python removal in sid/bullseye)

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 19:00:26 + with message-id and subject line Bug#943037: fixed in git-hub 2.1.1-1 has caused the Debian Bug report #943037, regarding git-hub: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#943037: marked as done (git-hub: Python2 removal in sid/bullseye)

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 19:00:26 + with message-id and subject line Bug#943037: fixed in git-hub 2.1.1-1 has caused the Debian Bug report #943037, regarding git-hub: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

2022-01-03 Thread Andres Salomon
Thanks for testing! Are you doing this under sid? On 1/3/22 7:39 AM, Mattia Rizzolo wrote: On Sun, Jan 02, 2022 at 06:53:52PM +0100, Mattia Rizzolo wrote: the v96 branch of https://salsa.debian.org/dilinger/chromium FWIW, I'm trying to build it myself as well Here it started chrashing as

Bug#1003077: lesana: autopkgtest failure: No module named 'git'

2022-01-03 Thread Paul Gevers
Source: lesana Version: 0.9.1-1 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 lesana, great. However, it fails. Currently this failure is blocking the

Processed: Bug#995393: fakeroot: diff for NMU version 1.26-1.2

2022-01-03 Thread Debian Bug Tracking System
Processing control commands: > tags 995393 + pending Bug #995393 [src:fakeroot] fakeroot: FTBFS on ppc64el Added tag(s) pending. > tags 1001961 + pending Bug #1001961 {Done: Christoph Biedl } [fakeroot] No longer properly hooks the stat call Added tag(s) pending. -- 1001961:

Processed: Bug#995393: fakeroot: diff for NMU version 1.26-1.2

2022-01-03 Thread Debian Bug Tracking System
Processing control commands: > tags 995393 + pending Bug #995393 [src:fakeroot] fakeroot: FTBFS on ppc64el Ignoring request to alter tags of bug #995393 to the same tags previously set > tags 1001961 + pending Bug #1001961 {Done: Christoph Biedl } [fakeroot] No longer properly hooks the stat

Bug#1003045: New information : problem seems to be xorg/wayland conflict.

2022-01-03 Thread Rene Engelhard
Hi Am 03.01.22 um 18:46 schrieb Rene Engelhard: > my clean testing VM which I just dist_upgraded. Lo starts fine with the > default session there which is Xorg. Nevermind, it was wayland actually but also "GNOME on Xorg" works. Regards, Rene

Bug#984270: marked as done (onednn: ftbfs with GCC-11)

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 17:48:40 + with message-id and subject line Bug#984270: fixed in onednn 2.2.4+ds-1 has caused the Debian Bug report #984270, regarding onednn: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1001733: marked as done (dh-sysuser: autopkgtest failure: FAILED: user _runit-log exists after purge or environment is not clean)

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 17:48:25 + with message-id and subject line Bug#1001733: fixed in dh-sysuser 1.3.7+really1.4.1 has caused the Debian Bug report #1001733, regarding dh-sysuser: autopkgtest failure: FAILED: user _runit-log exists after purge or environment is not clean to

Bug#1003045: libreoffice: Since testing update on Jan 2, 2021, libreoffice doesn't start.

2022-01-03 Thread Rene Engelhard
Hi, Am 03.01.22 um 09:48 schrieb Emmanuel Charpentier: > similarly, launching an application from a console's command line returns > after > a few seconds. Nothing on the command line? Can't be a general problem since https://ci.debian.net/packages/libr/libreoffice/testing/amd64/ passes

Processed: Re: Bug#1003045: New information : problem seems to be xorg/wayland conflict.

2022-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 1003045 + unreproducible Bug #1003045 [libreoffice] libreoffice: Since testing update on Jan 2, 2021, libreoffice doesn't start. Added tag(s) unreproducible. > tag 1003045 + moreinfo Bug #1003045 [libreoffice] libreoffice: Since testing

Processed: [bts-link] source package src:diskcache

2022-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:diskcache > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Bug#1003016: marked as done (node-chart.js breaks cacti autopkgtest: did Chart.js just got renamed to chart.js?)

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 16:48:38 + with message-id and subject line Bug#1003016: fixed in node-chart.js 3.7.0+~0.1.9-2 has caused the Debian Bug report #1003016, regarding node-chart.js breaks cacti autopkgtest: did Chart.js just got renamed to chart.js? to be marked as done.

Bug#997845: Info received (Bug#997845: growlight: autopkgtest regression: log repeats until it times out)

2022-01-03 Thread nick black
wait, i just might have reproduced a failure. it doesn't look like our failure in autopkgtests, but this is an assert() blowing up, and i'm not certain we build with those. if not, maybe we're hitting a case that locks up. let's hope so! this would once again presumably be a notcurses fix. the

Processed: Bug#1003013 marked as pending in ceph

2022-01-03 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1003013 [ceph-osd] ceph-volume: ModuleNotFoundError Added tag(s) pending. -- 1003013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003013 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1003013: marked as pending in ceph

2022-01-03 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #1003013 in ceph 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#1003016 marked as pending in node-chart.js

2022-01-03 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1003016 [src:node-chart.js] node-chart.js breaks cacti autopkgtest: did Chart.js just got renamed to chart.js? Added tag(s) pending. -- 1003016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003016 Debian Bug Tracking System Contact

Bug#1003016: marked as pending in node-chart.js

2022-01-03 Thread Yadd
Control: tag -1 pending Hello, Bug #1003016 in node-chart.js 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#997845: Info received (Bug#997845: growlight: autopkgtest regression: log repeats until it times out)

2022-01-03 Thread nick black
further investigation: i uploaded -4 with a change to simply redirect input from /dev/null, rather than echoing 'blockdev -v' into the process. the result was pretty much the exact same: we don't see the input show up, and we get a time out. of course, attempting to reproduce this locally leads to

Bug#1000178: marked as done (llvmlite: FTBFS with Python 3.10)

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 16:03:31 + with message-id and subject line Bug#1000178: fixed in llvmlite 0.38.0~rc1-1 has caused the Debian Bug report #1000178, regarding llvmlite: FTBFS with Python 3.10 to be marked as done. This means that you claim that the problem has been dealt

Bug#973181: marked as done (camljava: FTBFS: Please specify at most one of -pack, -a, -c, -output-obj)

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 15:18:29 + with message-id and subject line Bug#973181: fixed in camljava 0.3-4 has caused the Debian Bug report #973181, regarding camljava: FTBFS: Please specify at most one of -pack, -a, -c, -output-obj to be marked as done. This means that you claim

Processed: Bug#973181 marked as pending in camljava

2022-01-03 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #973181 [src:camljava] camljava: FTBFS: Please specify at most one of -pack, -a, -c, -output-obj Added tag(s) pending. -- 973181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973181 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#973181: marked as pending in camljava

2022-01-03 Thread Stéphane Glondu
Control: tag -1 pending Hello, Bug #973181 in camljava 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#1003061: dmrgpp: autopkgtest failure on armhf: segmentation fault

2022-01-03 Thread Paul Gevers
Source: dmrgpp Version: 6.02-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always timeout Dear maintainer(s), You recently added an autopkgtest to your package dmrgpp, great. However, it fails. Currently this failure is blocking

Bug#1002872: libgl1-mesa-dri: crashes on pre-SSE2 CPUs due to movsd

2022-01-03 Thread NoSSE2
Package: libgl1-mesa-dri Version: 21.3.0~rc5-1 Followup-For: Bug #1002872 X-Debbugs-Cc: karogyoker2+deb...@gmail.com Dear Maintainer, glxinfo was not able to run due to the same issue. gdb glxinfo Thread 1 "glxinfo" received signal SIGILL, Illegal instruction. 0xb5fdfa2e in ?? () from

Bug#1002419: marked as done (montage-wrapper: FTBFS: OSError: File /tmp/montage_mosaic_raw_nk94s2pn/images_raw_all.tbl already exists. If you mean to replace it then use the argument "overwrite=True".

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 14:27:32 + with message-id and subject line Bug#1003051: Removed package(s) from unstable has caused the Debian Bug report #1002419, regarding montage-wrapper: FTBFS: OSError: File /tmp/montage_mosaic_raw_nk94s2pn/images_raw_all.tbl already exists. If you

Bug#1000986: marked as done (Montage-wrapper does not play well with astropy 5.0)

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 14:27:32 + with message-id and subject line Bug#1003051: Removed package(s) from unstable has caused the Debian Bug report #1000986, regarding Montage-wrapper does not play well with astropy 5.0 to be marked as done. This means that you claim that the

Bug#1003045: New information : problem seems to be xorg/wayland conflict.

2022-01-03 Thread copropriete27ruemoret
It turns out that the problem is slightly larger than that... After this update, somme applications such as LibreOffice, but also Firefox, do not "work" in an xorg session but do in a Wayland session. More precisely, these applications run (I can see them in `ps augwx`, their icons are marked

Bug#1002754: marked as done (newsboat: FTBFS: build-dependency not installable: librust-time-0.1-dev)

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 3 Jan 2022 14:15:04 + with message-id and subject line re: newsboat: FTBFS: build-dependency not installable: librust-time-0.1-dev has caused the Debian Bug report #1002754, regarding newsboat: FTBFS: build-dependency not installable: librust-time-0.1-dev to be

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 3 Jan 2022 14:07:28 +0100 with message-id and subject line Re: Bug#965843: tmpreaper: Removal of obsolete debhelper compat 5 and 6 in bookworm has caused the Debian Bug report #965843, regarding tmpreaper: Removal of obsolete debhelper compat 5 and 6 in bookworm to be

Bug#1002406: marked as done (khal: FTBFS: packaging.version.InvalidVersion: Invalid version: '0.10.4-ds')

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 13:18:30 + with message-id and subject line Bug#1002406: fixed in khal 1:0.10.4~ds-3 has caused the Debian Bug report #1002406, regarding khal: FTBFS: packaging.version.InvalidVersion: Invalid version: '0.10.4-ds' to be marked as done. This means that you

Processed: Bug#1002406 marked as pending in khal

2022-01-03 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1002406 [src:khal] khal: FTBFS: packaging.version.InvalidVersion: Invalid version: '0.10.4-ds' Added tag(s) pending. -- 1002406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002406 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1002406: marked as pending in khal

2022-01-03 Thread Jonas Smedegaard
Control: tag -1 pending Hello, Bug #1002406 in khal 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#998946: marked as done (tmpreaper: missing required debian/rules targets build-arch and/or build-indep)

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 13:03:54 + with message-id and subject line Bug#998946: fixed in tmpreaper 1.6.15 has caused the Debian Bug report #998946, regarding tmpreaper: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

Processed: severity of 1002668 is grave

2022-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1002668 grave Bug #1002668 [gif2apng] gif2apng: CVE-2021-45909: Heap based buffer overflow in the DecodeLZW function Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance.

Processed: severity of 1002687 is grave

2022-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1002687 grave Bug #1002687 [gif2apng] gif2apng: CVE-2021-45911: Heap based buffer overflow in processing of delays in the main function Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if

Processed: severity of 1002667 is grave

2022-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1002667 grave Bug #1002667 [gif2apng] gif2apng: CVE-2021-45910: Heap based buffer overflow in the main function Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

2022-01-03 Thread Mattia Rizzolo
On Mon, Jan 03, 2022 at 01:39:21PM +0100, Mattia Rizzolo wrote: > On Sun, Jan 02, 2022 at 06:53:52PM +0100, Mattia Rizzolo wrote: > > > > the v96 branch of https://salsa.debian.org/dilinger/chromium > > > > FWIW, I'm trying to build it myself as well > > Here it started chrashing as soon as I

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

2022-01-03 Thread Mattia Rizzolo
On Sun, Jan 02, 2022 at 06:53:52PM +0100, Mattia Rizzolo wrote: > > > the v96 branch of https://salsa.debian.org/dilinger/chromium > > FWIW, I'm trying to build it myself as well Here it started chrashing as soon as I tried to open a new tab, and after that it refuses to load my main profile

Bug#1002772: nfs-ganesha: FTBFS: internal.h:50:2: error: #error rados/rgw_file.h version unsupported (require >= 1.1.1)

2022-01-03 Thread Christoph Martin
On 28.12.21 21:05, Lucas Nussbaum wrote: /<>/src/FSAL/FSAL_RGW/internal.h:50:2: error: #error rados/rgw_file.h version unsupported (require >= 1.1.1) 50 | #error rados/rgw_file.h version unsupported (require >= 1.1.1) | ^ Thanks for the report. The problem is fixed in

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

2022-01-03 Thread Andres Salomon
On Sun, 2 Jan 2022 15:32:28 -0500 Andres Salomon wrote: > On Sun, 2 Jan 2022 20:15:01 +0100 > Moritz Muehlenhoff wrote: > > > On Sat, Jan 01, 2022 at 01:23:09PM -0500, Andres Salomon wrote: > > > How should I handle this? NMU to sid, let people try it out, and > > > then deal with

Bug#996057: marked as done (gnome-shell-extension-gamemode: does not declare compatibility with GNOME Shell 41)

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 10:08:29 + with message-id and subject line Bug#996057: fixed in gnome-shell-extension-gamemode 6-1 has caused the Debian Bug report #996057, regarding gnome-shell-extension-gamemode: does not declare compatibility with GNOME Shell 41 to be marked as done.

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:35:32 + with message-id and subject line Bug#999273: fixed in postal 0.76+nmu1 has caused the Debian Bug report #999273, regarding postal: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:35:36 + with message-id and subject line Bug#998927: fixed in poster 1:20050907-2.1 has caused the Debian Bug report #998927, regarding poster: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:35:41 + with message-id and subject line Bug#998949: fixed in wrapsrv 1.0.0-1.1 has caused the Debian Bug report #998949, regarding wrapsrv: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:34:07 + with message-id and subject line Bug#999290: fixed in geki3 1.0.3-8.2 has caused the Debian Bug report #999290, regarding geki3: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:35:27 + with message-id and subject line Bug#999269: fixed in mhddfs 0.1.39+nmu2 has caused the Debian Bug report #999269, regarding mhddfs: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:33:37 + with message-id and subject line Bug#999261: fixed in boolector 1.5.118.6b56be4.121013-1.1 has caused the Debian Bug report #999261, regarding boolector: missing required debian/rules targets build-arch and/or build-indep to be marked as done.

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:35:10 + with message-id and subject line Bug#999232: fixed in mapivi 0.9.7-1.3 has caused the Debian Bug report #999232, regarding mapivi: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:34:12 + with message-id and subject line Bug#999214: fixed in gkrellm-reminder 2.0.0-3.1 has caused the Debian Bug report #999214, regarding gkrellm-reminder: missing required debian/rules targets build-arch and/or build-indep to be marked as done.

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:33:58 + with message-id and subject line Bug#999203: fixed in gav 0.9.0-3.1 has caused the Debian Bug report #999203, regarding gav: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:34:43 + with message-id and subject line Bug#999176: fixed in impose+ 0.2-12.2 has caused the Debian Bug report #999176, regarding impose+: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:35:23 + with message-id and subject line Bug#999168: fixed in mh-book 200605-2.2 has caused the Debian Bug report #999168, regarding mh-book: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:34:16 + with message-id and subject line Bug#999157: fixed in gkrellm-thinkbat 0.2.2-1.1 has caused the Debian Bug report #999157, regarding gkrellm-thinkbat: missing required debian/rules targets build-arch and/or build-indep to be marked as done.

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:34:21 + with message-id and subject line Bug#999130: fixed in gkrellm-xkb 1.05-5.1 has caused the Debian Bug report #999130, regarding gkrellm-xkb: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:34:03 + with message-id and subject line Bug#999092: fixed in gav-themes 0.7.3-2.4 has caused the Debian Bug report #999092, regarding gav-themes: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:34:48 + with message-id and subject line Bug#999098: fixed in ips 4.0-1.1 has caused the Debian Bug report #999098, regarding ips: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim that

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:33:42 + with message-id and subject line Bug#999072: fixed in bootp 2.4.3-19.1 has caused the Debian Bug report #999072, regarding bootp: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:35:01 + with message-id and subject line Bug#999070: fixed in libranlip 1.0-4.3 has caused the Debian Bug report #999070, regarding libranlip: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:34:34 + with message-id and subject line Bug#999067: fixed in ifstat 1.1-8.2 has caused the Debian Bug report #999067, regarding ifstat: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:34:52 + with message-id and subject line Bug#999065: fixed in jnettop 0.13.0-1.2 has caused the Debian Bug report #999065, regarding jnettop: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:35:05 + with message-id and subject line Bug#999055: fixed in logtools 0.13e+nmu2 has caused the Debian Bug report #999055, regarding logtools: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:34:39 + with message-id and subject line Bug#999052: fixed in imgsizer 2.10-0.2 has caused the Debian Bug report #999052, regarding imgsizer: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:34:25 + with message-id and subject line Bug#999019: fixed in gkrelltop 2.2.13-1.1 has caused the Debian Bug report #999019, regarding gkrelltop: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:34:57 + with message-id and subject line Bug#999008: fixed in jtex-base 2.1-1.3 has caused the Debian Bug report #999008, regarding jtex-base: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:34:30 + with message-id and subject line Bug#999000: fixed in gltron 0.70final-12.3 has caused the Debian Bug report #999000, regarding gltron: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:35:27 + with message-id and subject line Bug#965728: fixed in mhddfs 0.1.39+nmu2 has caused the Debian Bug report #965728, regarding mhddfs: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:33:28 + with message-id and subject line Bug#998993: fixed in beav 1:1.40-18.1 has caused the Debian Bug report #998993, regarding beav: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:35:10 + with message-id and subject line Bug#965716: fixed in mapivi 0.9.7-1.3 has caused the Debian Bug report #965716, regarding mapivi: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:34:48 + with message-id and subject line Bug#965598: fixed in ips 4.0-1.1 has caused the Debian Bug report #965598, regarding ips: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the problem

Bug#965593: marked as done (impose+: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:34:43 + with message-id and subject line Bug#965593: fixed in impose+ 0.2-12.2 has caused the Debian Bug report #965593, regarding impose+: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the

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

2022-01-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jan 2022 09:34:39 + with message-id and subject line Bug#965592: fixed in imgsizer 2.10-0.2 has caused the Debian Bug report #965592, regarding imgsizer: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that

  1   2   >