Processed: fixed 1014828 in 3.1.4-1, found 1014828 in 2.5.7-1

2022-07-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # two fixedin 3.1.3-1 and one in 3.1.4-1 > fixed 1014828 3.1.4-1 Bug #1014828 [src:openexr] openexr: CVE-2021-3933 CVE-2021-3941 CVE-2021-45942 Marked as fixed in versions openexr/3.1.4-1. > found 1014828 2.5.7-1 Bug #1014828 [src:openexr]

Bug#1013702: marked as done (pytest-pylint: FTBFS: pytest7 regression, AssertionError)

2022-07-12 Thread Debian Bug Tracking System
Your message dated Wed, 13 Jul 2022 04:49:41 + with message-id and subject line Bug#1013702: fixed in pytest-pylint 0.18.0-4 has caused the Debian Bug report #1013702, regarding pytest-pylint: FTBFS: pytest7 regression, AssertionError to be marked as done. This means that you claim that the

Processed: Bug#1013702 marked as pending in pytest-pylint

2022-07-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1013702 [src:pytest-pylint] pytest-pylint: FTBFS: pytest7 regression, AssertionError Added tag(s) pending. -- 1013702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013702 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1013702: marked as pending in pytest-pylint

2022-07-12 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #1013702 in pytest-pylint 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 1013702 is forwarded to https://github.com/carsongee/pytest-pylint/issues/169

2022-07-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1013702 https://github.com/carsongee/pytest-pylint/issues/169 Bug #1013702 [src:pytest-pylint] pytest-pylint: FTBFS: pytest7 regression, AssertionError Set Bug forwarded-to-address to

Bug#1014487: marked as done (python-parameterized: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - AssertionError)

2022-07-12 Thread Debian Bug Tracking System
Your message dated Wed, 13 Jul 2022 04:04:37 + with message-id and subject line Bug#1014487: fixed in python-parameterized 0.8.1-4 has caused the Debian Bug report #1014487, regarding python-parameterized: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration

Bug#965921: marked as done (zemberek-server: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-07-12 Thread Debian Bug Tracking System
Your message dated Wed, 13 Jul 2022 03:51:09 + with message-id and subject line Bug#965921: fixed in zemberek-server 0.7.1-12.4 has caused the Debian Bug report #965921, regarding zemberek-server: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that

Processed: Bug#1014487 marked as pending in python-parameterized

2022-07-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1014487 [src:python-parameterized] python-parameterized: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - AssertionError Added tag(s) pending. -- 1014487:

Bug#1014487: marked as pending in python-parameterized

2022-07-12 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #1014487 in python-parameterized 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#1008447: marked as done (amanda: FTBFS: dh_auto_test: error: make -j8 check VERBOSE=1 returned exit code 2)

2022-07-12 Thread Debian Bug Tracking System
Your message dated Wed, 13 Jul 2022 02:34:03 + with message-id and subject line Bug#1008447: fixed in amanda 1:3.5.1-9 has caused the Debian Bug report #1008447, regarding amanda: FTBFS: dh_auto_test: error: make -j8 check VERBOSE=1 returned exit code 2 to be marked as done. This means that

Bug#1014841: libguvcview-2.1-2: Missing Breaks+Replaces header → trying to overwrite '/usr/lib/x86_64-linux-gnu/libgviewaudio-2.0.so.2.0.0', which is also in package libguvcview-2.0-2:amd64 2.0.7-2-1

2022-07-12 Thread Axel Beckert
Package: libguvcview-2.1-2 Severity: serious Version: 2.0.8-1 Upgrading gucview with the switch to a new library package name (probably due to an SONAME bump) fails as follows due to missing Breaks and Replaces headers in libguvcview-2.1-2: Preparing to unpack

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

2022-07-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Jul 2022 21:48:59 + with message-id and subject line Bug#996068: fixed in gnome-shell-extension-panel-osd 1.0.50.gc032923-2 has caused the Debian Bug report #996068, regarding gnome-shell-extension-panel-osd: does not declare compatibility with GNOME Shell 41 to

Bug#1014090: marked as done (python3-poetry: Missing dependency on python3-cachecontrol)

2022-07-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Jul 2022 23:14:00 +0200 with message-id <081affa8-4677-f7aa-9702-76d671367...@debian.org> and subject line Re: python3-poetry: Missing dependency on python3-cachecontrol has caused the Debian Bug report #1014090, regarding python3-poetry: Missing dependency on

Processed: tagging 1014830, tagging 1014828

2022-07-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1014830 + upstream Bug #1014830 [src:php-laravel-framework] php-laravel-framework: CVE-2021-37298 Added tag(s) upstream. > tags 1014828 + upstream Bug #1014828 [src:openexr] openexr: CVE-2021-3933 CVE-2021-3941 CVE-2021-45942 Added tag(s)

Bug#1014831: android-platform-frameworks-base: aapt2 command does not work at all

2022-07-12 Thread Roger Shimizu
Package: android-platform-frameworks-base Version: 1:13~beta3-1~exp1 Severity: serious Justification: must Dear Maintainer, aapt2 does not work at all, even `aapt2 version` fails. So I disabled the aapt2 invoking while building for 1:13~beta3-1~exp1: -

Bug#1014828: openexr: CVE-2021-3933 CVE-2021-3941 CVE-2021-45942

2022-07-12 Thread Moritz Mühlenhoff
Source: openexr X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for openexr. CVE-2021-3933[0]: | An integer overflow could occur when OpenEXR processes a crafted file | on systems where size_t 64 bits. This could cause an

Bug#1014689: leiningen-clojure breaks cljx-clojure autopkgtest: artifact nrepl:nrepl:jar:0.9.0 has not been downloaded

2022-07-12 Thread Louis-Philippe Véronneau
The autopkgtests pass locally, but britney is stuck in a loop where: * leiningen-clojure 2.9.1-6 can't migrate because it breaks the cljx-clojure autopkgtest * nrepl-clojure 0.9.0-1 can't migrate because it breaks the cljx-clojure autopkgtest * leiningen-clojure 2.9.1-6 needs nrepl-clojure

Processed: Re: cifs-utils non-parallel FTBFS

2022-07-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 993014 + patch Bug #993014 [src:cifs-utils] cifs-utils non-parallel FTBFS Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 993014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993014

Bug#993014: cifs-utils non-parallel FTBFS

2022-07-12 Thread Santiago Vila
tags 993014 + patch thanks El 26/8/21 a las 12:31, Helmut Grohne escribió: | make install-exec-hook | make[5]: Entering directory '/<>' | (cd /<>/debian/cifs-utils/sbin && ln -sf mount.cifs mount.smb3) | /bin/bash: line 1: cd: /<>/debian/cifs-utils/sbin: No such file or directory Hi. I can

Bug#1011967: trapperkeeper-clojure: autopkgtest regression: FileNotFoundException

2022-07-12 Thread Jérôme Charaoui
Hello, This bug has been fixed by uploading core-async-clojure version 1.3.610-5 which includes this change: https://salsa.debian.org/clojure-team/core-async-clojure/-/commit/afae424e1de2e423e1842dec6d23085f31a5bc9c Thanks! -- Jerome

Bug#1011967: marked as done (trapperkeeper-clojure: autopkgtest regression: FileNotFoundException)

2022-07-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Jul 2022 12:16:30 -0400 with message-id <3b2b824a-98a5-7ce7-f08c-f83974c7b...@riseup.net> and subject line Re: trapperkeeper-clojure: autopkgtest regression: FileNotFoundException has caused the Debian Bug report #1011967, regarding trapperkeeper-clojure: autopkgtest

Processed: tagging 1004616, found 1004616 in 1.1+git20190701.9928c27-4

2022-07-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1004616 + experimental Bug #1004616 [src:performous] performous: FTBFS with ffmpeg 5.0 Added tag(s) experimental. > found 1004616 1.1+git20190701.9928c27-4 Bug #1004616 [src:performous] performous: FTBFS with ffmpeg 5.0 Marked as found in

Bug#1004630: marked as done (guvcview: FTBFS with ffmpeg 5.0)

2022-07-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Jul 2022 16:00:09 + with message-id and subject line Bug#1004630: fixed in guvcview 2.0.8-1 has caused the Debian Bug report #1004630, regarding guvcview: FTBFS with ffmpeg 5.0 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1014795: libtorrent-rasterbar-dev: pkg-config --libs is wrong, leads to FTBFS, again.

2022-07-12 Thread Christian Marillat
On 12 juil. 2022 10:08, Hilko Bengen wrote: > Package: libtorrent-rasterbar-dev > Version: 2.0.6-4 > Severity: grave > X-Debbugs-Cc: none, Hilko Bengen > > Dear Maintainer, > > apparently the bug described (and fixed) in #1009875 has re-appeared in > the most recent version. Hack to fix this

Bug#1014627: marked as done (maude: FTBFS with glibc 2.34)

2022-07-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Jul 2022 14:36:00 + with message-id and subject line Bug#1014627: fixed in maude 3.2-2 has caused the Debian Bug report #1014627, regarding maude: FTBFS with glibc 2.34 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1014486: marked as done (python-etelemetry: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - non-zero exit status 1)

2022-07-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Jul 2022 14:36:18 + with message-id and subject line Bug#1014486: fixed in python-etelemetry 0.3.0-2 has caused the Debian Bug report #1014486, regarding python-etelemetry: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration -

Bug#1014482: marked as done (nibabel: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - ResourceWarning: unclosed file)

2022-07-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Jul 2022 14:36:11 + with message-id and subject line Bug#1014482: fixed in nibabel 3.2.2-2 has caused the Debian Bug report #1014482, regarding nibabel: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - ResourceWarning:

Bug#1012336: dcm2niix: autopkgtest failure on s390x: 1 computed checksum did NOT match

2022-07-12 Thread Nilesh Patra
Bilal, Since you added autopkgtest for it, can you take a look and fix? Thanks. On Sat, 4 Jun 2022 21:12:59 +0200 Paul Gevers wrote: > Source: dcm2niix > Version: 1.0.20211006-4 > Severity: serious > User: debian...@lists.debian.org > Usertags: fails-always > > Dear maintainer(s), > > You

Bug#1014486: python-etelemetry: autopkgtest regression on amd64; arm64; armhf; i386; ppc64el; s390x: pytest7 migration - non-zero exit status 1

2022-07-12 Thread Nilesh Patra
Hi Pollo, On Wed, 6 Jul 2022 14:39:13 -0400 =?UTF-8?Q?Louis-Philippe_V=c3=a9ronneau?= wrote: > Source: python-etelemetry > Version: 0.3.0-1 > Control: affects -1 src:pytest > [...] > You can find the CI logs here: > https://ci.debian.net/packages/d/python-etelemetry/ Nitpicking: The above link

Processed: tagging 1014807, bug 1014807 is forwarded to https://github.com/jmespath/jmespath.rb/pull/55 ...

2022-07-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1014807 + upstream Bug #1014807 [src:ruby-jmespath] ruby-jmespath: CVE-2022-32511 Added tag(s) upstream. > forwarded 1014807 https://github.com/jmespath/jmespath.rb/pull/55 Bug #1014807 [src:ruby-jmespath] ruby-jmespath: CVE-2022-32511 Set

Processed: tagging 1014783, tagging 1014785

2022-07-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1014783 + upstream Bug #1014783 [src:faust] faust: CVE-2021-41736 CVE-2021-41737 Ignoring request to alter tags of bug #1014783 to the same tags previously set > tags 1014785 + upstream Bug #1014785 [src:dojo] dojo: CVE-2021-23450 Ignoring

Bug#1014817: mercurial: broken fsmonitor extension in 6.2

2022-07-12 Thread Julien Cristau
Package: mercurial Version: 6.2-1 Severity: serious Tags: upstream Upstream commit be9bf75a837c looks like it broke the fsmonitor extension: > File "/usr/lib/python3/dist-packages/hgext/fsmonitor/__init__.py", line > 338, in > if e._v1_state() != b"n" or e._v1_mtime() == -1 >

Bug#1014730: liburi-perl: Breaks apt-cacher with "Can't locate Regexp/IPv6.pm" error

2022-07-12 Thread Mark Hindley
Hi, On Tue, Jul 12, 2022 at 07:31:48AM +0100, Mark Hindley wrote: > > Corresponding untested patch against apt-cacher attached. > > The problem with this approach is that errors from apt-cacher's own evals will > be skipped as well. I think the patch below might be a better approach. It

Bug#1014749: marked as pending in openvswitch

2022-07-12 Thread Luca Boccassi
Control: tag -1 pending Hello, Bug #1014749 in openvswitch 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#1014749 marked as pending in openvswitch

2022-07-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1014749 [openvswitch-test,python3-openvswitch] openvswitch-test,python3-openvswitch: both ship /usr/lib/python3/dist-packages/ovstest/*.py Added tag(s) pending. -- 1014749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014749 Debian Bug

Bug#1014797: FTBFS: test failures with new libgd3

2022-07-12 Thread Andreas Tille
Control: tags -1 upstream Control: forwarded -1 https://github.com/GMOD/GBrowse/issues/64

Processed: Re: Bug#1014797: FTBFS: test failures with new libgd3

2022-07-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream Bug #1014797 [src:gbrowse] FTBFS: test failures with new libgd3 Added tag(s) upstream. > forwarded -1 https://github.com/GMOD/GBrowse/issues/64 Bug #1014797 [src:gbrowse] FTBFS: test failures with new libgd3 Set Bug forwarded-to-address to

Bug#1011443: faker,ruby-faker: error when trying to install together

2022-07-12 Thread duck
Quack, On 2022-07-06 06:18, Antonio Terceiro wrote: I just did that. Remember that you need to add Breaks:/Replaces: on your package for upgrades to work. Thanks Antonio. The initial report did not have this analysis and I did not did not have time to dig into it. Regards. \_o< -- Marc

Bug#1014807: ruby-jmespath: CVE-2022-32511

2022-07-12 Thread Moritz Mühlenhoff
Source: ruby-jmespath X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for ruby-jmespath. CVE-2022-32511[0]: | jmespath.rb (aka JMESPath for Ruby) before 1.6.1 uses JSON.load in a | situation where JSON.parse is preferable.

Bug#1014806: tortoisehg: uninstallable with mercurial 6.2

2022-07-12 Thread Julien Cristau
Source: tortoisehg Version: 6.1.1-3 Severity: serious I uploaded mercurial 6.2-1 to sid yesterday, making thg uninstallable. Cheers, Julien

Bug#1014803: ruby-yajl: CVE-2022-24795

2022-07-12 Thread Moritz Mühlenhoff
Source: ruby-yajl X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for ruby-yajl. CVE-2022-24795[0]: | yajl-ruby is a C binding to the YAJL JSON parsing and generation | library. The 1.x branch and the 2.x branch of `yajl`

Processed: src:php-excimer: fails to migrate to testing for too long: FTBFS on mipsel

2022-07-12 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.0.4-1 Bug #1014801 [src:php-excimer] src:php-excimer: fails to migrate to testing for too long: FTBFS on mipsel Marked as fixed in versions php-excimer/1.0.4-1. Bug #1014801 [src:php-excimer] src:php-excimer: fails to migrate to testing for too long:

Bug#1014801: src:php-excimer: fails to migrate to testing for too long: FTBFS on mipsel

2022-07-12 Thread Paul Gevers
Source: php-excimer Version: 1.0.2-1 Severity: serious Control: close -1 1.0.4-1 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than

Bug#1014799: src:python-aiortc: fails to migrate to testing for too long: autopkgtest regression

2022-07-12 Thread Paul Gevers
Source: python-aiortc Version: 1.3.1-2 Severity: serious Control: close -1 1.3.2-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1013365 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and

Processed: src:python-aiortc: fails to migrate to testing for too long: autopkgtest regression

2022-07-12 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.3.2-1 Bug #1014799 [src:python-aiortc] src:python-aiortc: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions python-aiortc/1.3.2-1. Bug #1014799 [src:python-aiortc] src:python-aiortc: fails to migrate to testing

Bug#1014797: FTBFS: test failures with new libgd3

2022-07-12 Thread gregor herrmann
Source: gbrowse Version: 2.56+dfsg-10 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 While working on libgd-perl and libgd-graph-perl (#1014741) I noticed that gbrowse has issues with

Bug#1014795: libtorrent-rasterbar-dev: pkg-config --libs is wrong, leads to FTBFS, again.

2022-07-12 Thread Hilko Bengen
Package: libtorrent-rasterbar-dev Version: 2.0.6-4 Severity: grave X-Debbugs-Cc: none, Hilko Bengen Dear Maintainer, apparently the bug described (and fixed) in #1009875 has re-appeared in the most recent version. , | (sid-amd64)bengen@ataraxia: $ dpkg-query --show libtorrent-rasterbar-dev

Bug#1014749: debian/clean already fixed in git

2022-07-12 Thread Christian Ehrhardt
Turns out the dh_clena issue was already fixed [1] in git (where I checked for trailing /) and not yet in experimental where you and I tested against :-/ Confusion resolved :-) We just need to work on the discussion on the python fixes and then can upload a fixed version. [1]:

Bug#1014749: Work in progress

2022-07-12 Thread Christian Ehrhardt
tags 1014749 + confirmed FYI fixes to the python file duplication are proposed and discussed in Salsa at [1] For the d/clean portion I'm still puzzled ... The file already has trailing slashes $ cat debian/clean _debian/ _dpdk/ This works just fine: $ mkdir _debian $ touch debian/foo $

Bug#1014747: marked as done (node-jest-debbundle: mising Breaks+Replaces: jest (<< 28.1.2~))

2022-07-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Jul 2022 06:49:28 + with message-id and subject line Bug#1014747: fixed in node-jest 28.1.2~ds+~cs70.48.26-3 has caused the Debian Bug report #1014747, regarding node-jest-debbundle: mising Breaks+Replaces: jest (<< 28.1.2~) to be marked as done. This means that

Bug#1014730: liburi-perl: Breaks apt-cacher with "Can't locate Regexp/IPv6.pm" error

2022-07-12 Thread Mark Hindley
Niko, On Mon, Jul 11, 2022 at 09:26:12PM +0300, Niko Tyni wrote: > [apt-cacher maintainers: the context here is that URI.pm introduced an > optional dependency on Regexp::IPv6 by requiring it in an eval block, > but the apt-cacher __DIE__ handler exits when the require fails.] Thanks for

Bug#1014749: Thanks

2022-07-12 Thread Christian Ehrhardt
Odd, we had piuparts running as part of the CI pipeline every time. Thank you for the report, we will have a look...