Bug#1004477: virt-top fails to start with OCaml 4.13.1

2022-01-28 Thread Adrian Bunk
Package: virt-top Version: 1.0.9-1.1 Severity: serious X-Debbugs-Cc: Debian OCaml Maintainers $ virt-top the file '/usr/bin/virt-top' has not the right magic number: expected Caml1999X030, got Caml1999X028 $

Processed: Bug#1004311: found in 1.22-2, not found in 1.22-4

2022-01-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1004311 1.22-2 Bug #1004311 {Done: Domenico Andreoli } [pahole] pahole segfaults during kernel build Ignoring request to alter found versions of bug #1004311 to the same values previously set > notfound 1004311 1.22-4 Bug #1004311 {Done:

Bug#1004478: emscripten: attempts internet communication during build

2022-01-28 Thread Gianfranco Costamagna
Source: emscripten Version: 3.1.1~dfsg+~1.39.6-5 Severity: serious Hello, some tests are trying to reach googleapis test_global_inits (test_other.other) ... skipped 'relies on fastcomp EXIT_RUNTIME=0 optimization not implemented/disabled' ports:INFO: retrieving port: giflib from

Processed: Re: Bug#974836: openconnect FTBFS on IPV6-only buildds

2022-01-28 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #974836 [src:openconnect] openconnect FTBFS on IPV6-only buildds Severity set to 'serious' from 'important' -- 974836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974836 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1004453: marked as done (libcmark-dev generates broken dependencies.)

2022-01-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Jan 2022 09:19:00 + with message-id and subject line Bug#1004453: fixed in cmark 0.30.2-5 has caused the Debian Bug report #1004453, regarding libcmark-dev generates broken dependencies. to be marked as done. This means that you claim that the problem has been

Bug#974836: marked as done (openconnect FTBFS on IPV6-only buildds)

2022-01-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Jan 2022 14:39:37 + with message-id and subject line Bug#974836: fixed in openconnect 8.10-7 has caused the Debian Bug report #974836, regarding openconnect FTBFS on IPV6-only buildds to be marked as done. This means that you claim that the problem has been dealt

Bug#733094: 20 GB senseless logfile

2022-01-28 Thread karsten
I have the same problem here with Debian 11 (bullseye). The only solution seems to be apt-get purge uvcdynctrl After that my webcam still works. So this package can be seen as unusable, harmful and dispensable. This should not be installed and all dependencies snatched. Best regards karsten

Processed: Bug#1004478 marked as pending in emscripten

2022-01-28 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1004478 [src:emscripten] emscripten: attempts internet communication during build Added tag(s) pending. -- 1004478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004478 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1004478: marked as pending in emscripten

2022-01-28 Thread Jonas Smedegaard
Control: tag -1 pending Hello, Bug #1004478 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#1004478: marked as done (emscripten: attempts internet communication during build)

2022-01-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Jan 2022 13:33:44 + with message-id and subject line Bug#1004478: fixed in emscripten 3.1.2~dfsg+~1.39.6-3 has caused the Debian Bug report #1004478, regarding emscripten: attempts internet communication during build to be marked as done. This means that you claim

Bug#974836: marked as pending in openconnect

2022-01-28 Thread Luca Boccassi
Control: tag -1 pending Hello, Bug #974836 in openconnect 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#974836 marked as pending in openconnect

2022-01-28 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #974836 [src:openconnect] openconnect FTBFS on IPV6-only buildds Added tag(s) pending. -- 974836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1003865: GPG error: http://deb.debian.org/debian sid InRelease: The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian Archive Automatic Signing Key (10/buster)

2022-01-28 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 apt-cacher-ng Bug #1003865 {Done: "Adam D. Barratt" } [debian-archive-keyring] GPG error: http://deb.debian.org/debian sid InRelease: The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian Archive Automatic Signing Key (10/buster) Bug

Bug#1004482: liblog4j1.2-java: CVE-2022-23307 CVE-2022-23305 CVE-2022-23302

2022-01-28 Thread Christoph Anton Mitterer
Package: liblog4j1.2-java Version: 1.2.17-10 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: Debian Security Team Hey. A number of holes was found in the 1.2 branch of log4j. The following is apparently critical (code injection):

Bug#1004465: libklibc-dev: headers not installed

2022-01-28 Thread Thorsten Glaser
found 1004465 2.0.10-1 thanks Dixi quod… >Quite some files are missing: […] >/usr/lib/klibc/include/alloca.h […] >/usr/lib/klibc/include/arpa/inet.h > /usr/lib/klibc/include/asm > /usr/lib/klibc/include/asm-generic >/usr/lib/klibc/include/assert.h […] From this

Processed: Re: Bug#1004465: libklibc-dev: headers not installed

2022-01-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1004465 2.0.10-1 Bug #1004465 [libklibc-dev] libklibc-dev: headers not installed Marked as found in versions klibc/2.0.10-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1004465:

Bug#1001057: grub2: hold 2.06 in unstable for now

2022-01-28 Thread Paul Gevers
Hi Colin, On Fri, 3 Dec 2021 11:17:26 + Colin Watson wrote: GRUB 2.06 is a pretty big change over 2.04. I'd like to hold this in unstable for a while longer to let things shake out before we allow it to move to testing. grub2 showed up in my out-of-sync tracking script output. Do you

Bug#1004464: marked as pending in python-django

2022-01-28 Thread Chris Lamb
Control: tag -1 pending Hello, Bug #1004464 in python-django 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#1004464 marked as pending in python-django

2022-01-28 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1004464 [src:python-django] python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase) Ignoring request to alter tags of bug #1004464 to the same tags previously set -- 1004464:

Bug#1004211: dirty.js: autopkgtest failure on armhf and ppc64el

2022-01-28 Thread Yadd
Control: tags -1 + moreinfo Hi, I'm unable to reproduce using a porterbox

Processed: Re: dirty.js: autopkgtest failure on armhf and ppc64el

2022-01-28 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #1004211 [src:dirty.js] dirty.js: autopkgtest failure on armhf and ppc64el Added tag(s) moreinfo. -- 1004211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004211 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1004464: python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase)

2022-01-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1004464 2:3.2.11-1 Bug #1004464 [src:python-django] python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase) The source 'python-django' and version '2:3.2.11-1' do not appear to match any binary packages Marked as

Bug#1004464: python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase)

2022-01-28 Thread Adrian Bunk
On Fri, Jan 28, 2022 at 08:42:44AM -0800, Chris Lamb wrote: > found 1004464 2:3.2.11-1 > thanks > > Hi Adrian, > > > Version: 2:3.2.7-1 > > Just to point out that you specified the 'Version' here as 2:3.2.7, > whilst the traceback you linked to: > > >

Bug#1004477: virt-top fails to start with OCaml 4.13.1

2022-01-28 Thread Stéphane Glondu
Le 28/01/2022 à 13:10, Adrian Bunk a écrit : > Package: virt-top > Version: 1.0.9-1.1 > Severity: serious > X-Debbugs-Cc: Debian OCaml Maintainers > > $ virt-top > the file '/usr/bin/virt-top' has not the right magic number: expected > Caml1999X030, got Caml1999X028 /usr/bin/virt-top is a

Bug#1004464: marked as pending in python-django

2022-01-28 Thread Chris Lamb
Control: tag -1 pending Hello, Bug #1004464 in python-django 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#1004464 marked as pending in python-django

2022-01-28 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1004464 [src:python-django] python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase) Added tag(s) pending. -- 1004464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004464 Debian Bug Tracking System Contact

Bug#1004464: marked as done (python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase))

2022-01-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Jan 2022 17:04:31 + with message-id and subject line Bug#1004464: fixed in python-django 2:4.0.1-2 has caused the Debian Bug report #1004464, regarding python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase) to be marked as done. This

Bug#1004464: python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase)

2022-01-28 Thread Chris Lamb
Hi, >> Just to point out that you specified the 'Version' here as 2:3.2.7, >> whilst the traceback you linked to: >> >> > https://buildd.debian.org/status/fetch.php?pkg=python-django=all=2%3A3.2.11-1=1641309500=0 >> >> ... refers to a different version: 2:3.2.11. [..] > That was intentional: >

Bug#1004464: marked as done (python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase))

2022-01-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Jan 2022 17:04:24 + with message-id and subject line Bug#1004464: fixed in python-django 2:3.2.11-2 has caused the Debian Bug report #1004464, regarding python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase) to be marked as done. This

Bug#1004464: python-django FTBFS: FAIL: test_custom_fields (inspectdb.tests.InspectDBTestCase)

2022-01-28 Thread Chris Lamb
found 1004464 2:3.2.11-1 thanks Hi Adrian, > Version: 2:3.2.7-1 Just to point out that you specified the 'Version' here as 2:3.2.7, whilst the traceback you linked to: > https://buildd.debian.org/status/fetch.php?pkg=python-django=all=2%3A3.2.11-1=1641309500=0 ... refers to a different

Bug#1003017: dulwich: autopkgtest regression: src/debian/tests/testsuite3: 10: -m: not found

2022-01-28 Thread Gianfranco Costamagna
control: tags -1 patch for py in $(py3versions -s); do echo "= Running tests with $py ==" if ! $py3 -m unittest dulwich.tests.test_suite; then rv=1 this should really be for py3 in $(py3versions -s); do echo "= Running tests with $py ==" if ! $py3

Processed: Re: dulwich: autopkgtest regression: src/debian/tests/testsuite3: 10: -m: not found

2022-01-28 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1003017 [src:dulwich] dulwich: autopkgtest regression: src/debian/tests/testsuite3: 10: -m: not found Added tag(s) patch. -- 1003017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003017 Debian Bug Tracking System Contact

Processed: severity of 1000934 is important

2022-01-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1000934 important Bug #1000934 [src:clazy] clazy: FTBFS on i386 with llvm-toolchain-13 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000934:

Bug#996380: marked as done (ruby-safe-yaml: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)

2022-01-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Jan 2022 22:06:32 + with message-id and subject line Bug#996380: fixed in ruby-safe-yaml 1.0.5-2 has caused the Debian Bug report #996380, regarding ruby-safe-yaml: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: to be marked as done. This

Bug#997287: marked as done (zeitgeist: FTBFS: where-clause.vala:219.35-219.63: error: The name `pdata' does not exist in the context of `GLib.PtrArray*')

2022-01-28 Thread Debian Bug Tracking System
Your message dated Sat, 29 Jan 2022 00:19:33 + with message-id and subject line Bug#997287: fixed in zeitgeist 1.0.3-7 has caused the Debian Bug report #997287, regarding zeitgeist: FTBFS: where-clause.vala:219.35-219.63: error: The name `pdata' does not exist in the context of

Bug#1004490: libkcapi: binary-all FTBFS

2022-01-28 Thread Adrian Bunk
Source: libkcapi Version: 1.3.1-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=libkcapi=all=1.3.1-2=1643387702=0 ... dh_missing -i dh_missing: warning: usr/lib/x86_64-linux-gnu/libkcapi.la exists in debian/tmp but is not installed to anywhere dh_missing:

Bug#1004409: marked as done (libslurm-dev: slurm/slurm_version.h is missing)

2022-01-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Jan 2022 23:34:02 + with message-id and subject line Bug#1004409: fixed in slurm-wlm 21.08.5-2 has caused the Debian Bug report #1004409, regarding libslurm-dev: slurm/slurm_version.h is missing to be marked as done. This means that you claim that the problem has

Bug#965431: bfbtester: diff for NMU version 2.0.1-7.2

2022-01-28 Thread Joao Eriberto Mota Filho
Control: tags 965431 + patch Control: tags 965431 + pending Dear maintainer, I've prepared an NMU for bfbtester (versioned as 2.0.1-7.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer or cancel it. Regards, Eriberto diff -u bfbtester-2.0.1/debian/rules

Processed: bfbtester: diff for NMU version 2.0.1-7.2

2022-01-28 Thread Debian Bug Tracking System
Processing control commands: > tags 965431 + patch Bug #965431 [src:bfbtester] bfbtester: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965431 + pending Bug #965431 [src:bfbtester] bfbtester: Removal of obsolete debhelper compat 5 and 6 in bookworm Added

Bug#998540: marked as done (shared-mime-info: FTBFS: Error: cannot open mo file /<>/obj-x86_64-linux-gnu/po/*.gmo)

2022-01-28 Thread Debian Bug Tracking System
Your message dated Sat, 29 Jan 2022 00:10:32 +0100 with message-id and subject line Re: Bug#998540: shared-mime-info: FTBFS: Error: cannot open mo file /<>/obj-x86_64-linux-gnu/po/*.gmo has caused the Debian Bug report #998540, regarding shared-mime-info: FTBFS: Error: cannot open mo file

Bug#1002213: dmitry: diff for NMU version 1.3a-1.2

2022-01-28 Thread Joao Eriberto Mota Filho
Control: tags 1002213 + patch Control: tags 1002213 + pending Dear maintainer, I've prepared an NMU for dmitry (versioned as 1.3a-1.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer or cancel the upload. Regards, Eriberto diff -u

Processed: dmitry: diff for NMU version 1.3a-1.2

2022-01-28 Thread Debian Bug Tracking System
Processing control commands: > tags 1002213 + patch Bug #1002213 [src:dmitry] dmitry: FTBFS: dh_clean: error: Compatibility levels before 7 are no longer supported (level 5 requested) Added tag(s) patch. > tags 1002213 + pending Bug #1002213 [src:dmitry] dmitry: FTBFS: dh_clean: error:

Bug#1002548: marked as done (libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules)

2022-01-28 Thread Debian Bug Tracking System
Your message dated Sat, 29 Jan 2022 01:19:11 + with message-id and subject line Bug#1002548: fixed in indi-fli 1.5-2 has caused the Debian Bug report #1002548, regarding libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules to be marked as done. This means that you claim that the

Bug#931519: marked as done (wajig: upgradesecurity references testing/updates instead of testing-security)

2022-01-28 Thread Debian Bug Tracking System
Your message dated Fri, 28 Jan 2022 20:07:06 -0600 with message-id <25076.41290.269608.599...@rob.eddelbuettel.com> and subject line 931519 resolved has caused the Debian Bug report #931519, regarding wajig: upgradesecurity references testing/updates instead of testing-security to be marked as

Processed: 931519 resolved

2022-01-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 931519 4.0.3 Bug #931519 {Done: Dirk Eddelbuettel } [wajig] wajig: upgradesecurity references testing/updates instead of testing-security Ignoring request to alter fixed versions of bug #931519 to the same values previously set > thanks

Bug#990345: zookeeper: various security issues

2022-01-28 Thread Christoph Anton Mitterer
Further for the records (for a future upgrade to newer ZK versions): There will likely need to be a NEWS.Debian entry about the following: https://issues.apache.org/jira/browse/ZOOKEEPER-3056 In short: - apparently they've added a check that prevents ZK from starting, when no snapshots were

Bug#931519: 931519 resolved

2022-01-28 Thread Dirk Eddelbuettel
On 29 January 2022 at 10:38, Paul Wise wrote: | Control: fixed -1 4.0.3 | | On Fri, 2022-01-28 at 20:07 -0600, Dirk Eddelbuettel wrote: | | > Per email by Graham from 14 Nov 2020 this has been resolved. | | Resolved upstream in 2020 but not in Debian until 2021. Correct. Graham (as author)

Processed: Re: 931519 resolved

2022-01-28 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 4.0.3 Bug #931519 {Done: Dirk Eddelbuettel } [wajig] wajig: upgradesecurity references testing/updates instead of testing-security Marked as fixed in versions wajig/4.0.3. -- 931519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931519 Debian Bug

Bug#931519: 931519 resolved

2022-01-28 Thread Paul Wise
Control: fixed -1 4.0.3 On Fri, 2022-01-28 at 20:07 -0600, Dirk Eddelbuettel wrote: > Per email by Graham from 14 Nov 2020 this has been resolved. Resolved upstream in 2020 but not in Debian until 2021. > By now we have an even newer version 4.0.3. Please use a versioned -done message next