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

2022-02-11 Thread Debian Bug Tracking System
Your message dated Sat, 12 Feb 2022 03:53:40 + with message-id and subject line Bug#96: fixed in glurp 0.12.3-1.1 has caused the Debian Bug report #96, regarding glurp: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the

Bug#997406: marked as done (kdsoap: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

2022-02-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Feb 2022 23:49:05 + with message-id and subject line Bug#997406: fixed in kdsoap 1.9.1+dfsg-3 has caused the Debian Bug report #997406, regarding kdsoap: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

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

2022-02-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Feb 2022 21:39:19 + with message-id and subject line Bug#1002541: fixed in libio-async-perl 0.801-2 has caused the Debian Bug report #1002541, regarding libio-async-perl: autopkgtest regression on ppc64el: Parse errors: No plan found in TAP output to be marked as

Processed: bug 1005281 is forwarded to https://github.com/shlomif/perl-XML-LibXML/issues/71

2022-02-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1005281 https://github.com/shlomif/perl-XML-LibXML/issues/71 Bug #1005281 {Done: Niko Tyni } [libxml-libxml-perl] libxml-libxml-perl: breaks validation, which succeeds even though the DTD could not be loaded Ignoring request to change

Bug#1005281: marked as done (libxml-libxml-perl: breaks validation, which succeeds even though the DTD could not be loaded)

2022-02-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Feb 2022 20:40:05 + with message-id and subject line Bug#1005281: fixed in libxml-libxml-perl 2.0207+dfsg+really+2.0134-1 has caused the Debian Bug report #1005281, regarding libxml-libxml-perl: breaks validation, which succeeds even though the DTD could not be

Bug#1004146: marked as done (libfuture-io-perl: autopkgtest failure on ppc64el)

2022-02-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Feb 2022 20:39:35 + with message-id and subject line Bug#1004146: fixed in libfuture-io-perl 0.11-2 has caused the Debian Bug report #1004146, regarding libfuture-io-perl: autopkgtest failure on ppc64el to be marked as done. This means that you claim that the

Bug#1004146: marked as pending in libfuture-io-perl

2022-02-11 Thread Niko Tyni
Control: tag -1 pending Hello, Bug #1004146 in libfuture-io-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1004146 marked as pending in libfuture-io-perl

2022-02-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1004146 [src:libfuture-io-perl] libfuture-io-perl: autopkgtest failure on ppc64el Added tag(s) pending. -- 1004146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004146 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1005255: telegram-desktop: error: ‘Config’ is not a member of ‘webrtc’

2022-02-11 Thread Nicholas Guriev
Hello! The error in the tgcalls module happened due to an incompatibility with the libtgowt package. I was updating Telegram Desktop, and it is tied a much to the library, dedicated WebRTC fork. I uploaded a new upstream version yesterday and the error was gone. Sorry for the inconvenience.

Bug#1005329: marked as done (python3-zlmdb: ships /usr/lib/python3/dist-packages/flatbuffers/*.py)

2022-02-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Feb 2022 19:20:47 + with message-id and subject line Bug#1005329: fixed in zlmdb 22.1.2-1 has caused the Debian Bug report #1005329, regarding python3-zlmdb: ships /usr/lib/python3/dist-packages/flatbuffers/*.py to be marked as done. This means that you claim that

Bug#1001995: libcrypto++: ftbfs on armhf

2022-02-11 Thread Jeffrey Walton
Hi Everyone, The patch to work around the failed compile is located at https://github.com/weidai11/cryptopp/issues/1094#issuecomment-1035656572 . The patch is against Crypto++ 8.6. The patch was tested in a Debian Unstable QEMU/Chroot for armel and armhf. It tested Ok. The changes in the diff

Processed: also affects llvm-toolchain-13

2022-02-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 1004923 -1 Bug #1004923 [src:llvm-toolchain-12] autopkgtest failure due to removed libRemoteIndex*.a Bug 1004923 cloned as bug 1005345 > reassign -1 src:llvm-toolchain-13 1:13.0.1-2 Bug #1005345 [src:llvm-toolchain-12] autopkgtest failure

Bug#1005298: marked as done (libdevel-nytprof-perl: autopkgtest failure with Perl 5.34: t/test62-subcaller1-b.t)

2022-02-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Feb 2022 15:50:05 + with message-id and subject line Bug#1005298: fixed in libdevel-nytprof-perl 6.11+dfsg-3 has caused the Debian Bug report #1005298, regarding libdevel-nytprof-perl: autopkgtest failure with Perl 5.34: t/test62-subcaller1-b.t to be marked as

Bug#1005298: marked as pending in libdevel-nytprof-perl

2022-02-11 Thread gregor herrmann
Control: tag -1 pending Hello, Bug #1005298 in libdevel-nytprof-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1005298 marked as pending in libdevel-nytprof-perl

2022-02-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1005298 [libdevel-nytprof-perl] libdevel-nytprof-perl: autopkgtest failure with Perl 5.34: t/test62-subcaller1-b.t Added tag(s) pending. -- 1005298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005298 Debian Bug Tracking System Contact

Bug#1005299: marked as done (mutter: FBTFS: Program cvt found: NO)

2022-02-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Feb 2022 13:04:45 + with message-id and subject line Bug#1005299: fixed in mutter 41.3-3 has caused the Debian Bug report #1005299, regarding mutter: FBTFS: Program cvt found: NO to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Re: Bug#1004863: Bootstrapping a Fedora produces a system with an empty package database

2022-02-11 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1004863 [dnf] Bootstrapping a Fedora produces a system with an empty package database Severity set to 'important' from 'serious' -- 1004863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004863 Debian Bug Tracking System Contact

Bug#1004863: Bootstrapping a Fedora produces a system with an empty package database

2022-02-11 Thread Holger Levsen
control: severity -1 important On Wed, Feb 02, 2022 at 06:05:24PM +0100, Enrico Zini wrote: > thank you for packaging dnf in Debian! thank you for filing this bug report, Enrico! However I've downgraded it to important as eg Qubes 4.1 uses dnf on Debian to download upgrades for dom0, which is

Bug#1005329: python3-zlmdb: ships /usr/lib/python3/dist-packages/flatbuffers/*.py

2022-02-11 Thread Andreas Beckmann
Package: python3-zlmdb Version: 21.1.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...):

Bug#1005287: marked as done (node-csstype: Build drops ";" in typescript declarations)

2022-02-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Feb 2022 11:35:12 + with message-id and subject line Bug#1005287: fixed in node-mdn-browser-compat-data 4.1.0-2 has caused the Debian Bug report #1005287, regarding node-csstype: Build drops ";" in typescript declarations to be marked as done. This means that you

Bug#1005287: marked as done (node-csstype: Build drops ";" in typescript declarations)

2022-02-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Feb 2022 11:35:06 + with message-id and subject line Bug#1005287: fixed in node-csstype 3.0.10-3 has caused the Debian Bug report #1005287, regarding node-csstype: Build drops ";" in typescript declarations to be marked as done. This means that you claim that the

Bug#1005287: marked as pending in node-mdn-browser-compat-data

2022-02-11 Thread Yadd
Control: tag -1 pending Hello, Bug #1005287 in node-mdn-browser-compat-data 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#1005287 marked as pending in node-csstype

2022-02-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1005287 [node-csstype] node-csstype: Build drops ";" in typescript declarations Ignoring request to alter tags of bug #1005287 to the same tags previously set -- 1005287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005287 Debian Bug

Bug#1005287: marked as pending in node-csstype

2022-02-11 Thread Yadd
Control: tag -1 pending Hello, Bug #1005287 in node-csstype 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#1005287 marked as pending in node-mdn-browser-compat-data

2022-02-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1005287 [node-csstype] node-csstype: Build drops ";" in typescript declarations Added tag(s) pending. -- 1005287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1005287: node-csstype: Build drops "; " in typescript declarations

2022-02-11 Thread Yadd
On 11/02/2022 11:10, Yadd wrote: On 11/02/2022 09:18, Julien Puydt wrote: Le jeudi 10 février 2022 à 16:20 +0100, Yadd a écrit : On 10/02/2022 15:38, Yadd wrote: Package: node-csstype Version: 3.0.10-1 Severity: grave Justification: renders package unusable debian/rules launches `ts-node

Bug#1005287: node-csstype: Build drops "; " in typescript declarations

2022-02-11 Thread Yadd
On 11/02/2022 11:42, Yadd wrote: On 11/02/2022 11:10, Yadd wrote: On 11/02/2022 09:18, Julien Puydt wrote: Le jeudi 10 février 2022 à 16:20 +0100, Yadd a écrit : On 10/02/2022 15:38, Yadd wrote: Package: node-csstype Version: 3.0.10-1 Severity: grave Justification: renders package unusable

Bug#991384: libwine-development fails to install on arm*: head: cannot open '/usr/aarch64-w64-mingw32/lib/zlib*.dll' for reading: No such file or directory

2022-02-11 Thread duck
Quack, Could you have a look at this bug please? I'm trying to fix cross-compilation problems on dxvk but cannot even get a test build to run because of this issue: https://salsa.debian.org/aviau/dxvk/-/jobs/2455425 Regards. \_o< -- Marc Dequènes

Bug#1005318: Please rebase cloud-init version to >= 21.1 in next debian release

2022-02-11 Thread Thomas Goirand
On 2/11/22 09:22, Yuhua Zou wrote: Package: cloud-init Version: 20.4.1 Severity:Serious The version of package cloud-init in Debian 11.2 is 20.4.1. Ubuntu 20.4 have bundled cloud-init 21.4 in official repository. Please rebase cloud-init version to >= 21.1 in next debian release. thanks *Why

Processed: Severity: wishlist

2022-02-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1005318 wishlist Bug #1005318 [cloud-init] Please rebase cloud-init version to >= 21.1 in next debian release Severity set to 'wishlist' from 'serious' > End of message, stopping processing here. Please contact me if you need

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-02-11 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1003865 {Done: "Adam D. Barratt" } [apt-cacher-ng] GPG error: http://deb.debian.org/debian sid InRelease: The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian Archive Automatic Signing Key (10/buster) Severity set to

Processed: Updating ownership of bugs

2022-02-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > owner 985022 Nick Morrott Bug #985022 {Done: Nick Morrott } [python3-mbed-ls] python3-mbed-ls: SyntaxWarning during package installation Owner recorded as Nick Morrott . > owner 919752 Nick Morrott Bug #919752 [mu-editor] mu-editor: Explain

Bug#1005318: Please rebase cloud-init version to >= 21.1 in next debian release

2022-02-11 Thread Yuhua Zou
Package: cloud-init Version: 20.4.1 Severity: Serious The version of package cloud-init in Debian 11.2 is 20.4.1. Ubuntu 20.4 have bundled cloud-init 21.4 in official repository. Please rebase cloud-init version to >= 21.1 in next debian release. thanks Why cloud-init are needed to upgrade to >=

Bug#1005287: [Pkg-javascript-devel] Bug#1005287: node-csstype: Build drops "; " in typescript declarations

2022-02-11 Thread Julien Puydt
Le jeudi 10 février 2022 à 16:20 +0100, Yadd a écrit : > On 10/02/2022 15:38, Yadd wrote: > > Package: node-csstype > > Version: 3.0.10-1 > > Severity: grave > > Justification: renders package unusable > > > > debian/rules launches `ts-node --files build.ts --start` which > > (only) > > modifies