Bug#1000303: liboqs: not yet ready for testing or stable

2021-11-20 Thread Andrius Merkys
Source: liboqs Severity: serious The upstream wishes to keep the package out of stable distributions for now, until the NIST Post-Quantum Cryptography standardization project reaches its conclusion. For the time being the package may be used for prototyping and evaluation in unstable. Andrius

Bug#997878: marked as done (python-click breaks python-softlayer autopkgtest: 'NoneType' object is not iterable)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 06:34:03 + with message-id and subject line Bug#997878: fixed in python-softlayer 5.9.7-1 has caused the Debian Bug report #997878, regarding python-click breaks python-softlayer autopkgtest: 'NoneType' object is not iterable to be marked as done. This

Bug#997878: marked as pending in python-softlayer

2021-11-20 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #997878 in python-softlayer 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#997878 marked as pending in python-softlayer

2021-11-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #997878 [src:python-click, src:python-softlayer] python-click breaks python-softlayer autopkgtest: 'NoneType' object is not iterable Added tag(s) pending. -- 997878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997878 Debian Bug Tracking

Processed: severity of 999513 is serious, severity of 999516 is serious, severity of 999518 is serious ...

2021-11-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > https://tracker.debian.org/news/1279078/accepted-matplotlib-350-1-source-into-unstable/ > severity 999513 serious Bug #999513 [src:aplpy] aplpy: FTBFS with matplotlib 3.5 (in experimental): ImportError: cannot import name 'ImageTk' from

Bug#996126: marked as done (ruby-attr-encrypted: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1))

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 03:48:31 + with message-id and subject line Bug#996126: fixed in ruby-attr-encrypted 3.1.0-4 has caused the Debian Bug report #996126, regarding ruby-attr-encrypted: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments

Bug#999538: pytables: diff for NMU version 3.6.1-5.1

2021-11-20 Thread Stefano Rivera
Control: tags 999538 + patch Control: tags 999538 + pending Dear maintainer, I've prepared an NMU for pytables (versioned as 3.6.1-5.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Also available as an MR:

Processed: pytables: diff for NMU version 3.6.1-5.1

2021-11-20 Thread Debian Bug Tracking System
Processing control commands: > tags 999538 + patch Bug #999538 [src:pytables] pytables: FTBFS with numpy 1.21 (in experimental): dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13 Added tag(s) patch. > tags 999538 + pending Bug #999538 [src:pytables] pytables:

Bug#996126: marked as pending in ruby-attr-encrypted

2021-11-20 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #996126 in ruby-attr-encrypted 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#996126 marked as pending in ruby-attr-encrypted

2021-11-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996126 [src:ruby-attr-encrypted] ruby-attr-encrypted: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1) Added tag(s) pending. -- 996126:

Bug#996128: marked as done (ruby-awesome-print: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 03:18:47 + with message-id and subject line Bug#996128: fixed in ruby-awesome-print 1.9.2-1 has caused the Debian Bug report #996128, regarding ruby-awesome-print: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: to be marked

Processed: tagging 996126

2021-11-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # https://github.com/attr-encrypted/attr_encrypted/pull/383/files > tags 996126 + patch Bug #996126 [src:ruby-attr-encrypted] ruby-attr-encrypted: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given

Bug#996128: marked as pending in ruby-awesome-print

2021-11-20 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #996128 in ruby-awesome-print 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#996128 marked as pending in ruby-awesome-print

2021-11-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996128 [src:ruby-awesome-print] ruby-awesome-print: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Added tag(s) pending. -- 996128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996128 Debian Bug Tracking

Bug#996121: marked as done (ruby-acts-as-tree: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/associations/builder/as

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 02:36:18 + with message-id and subject line Bug#996121: fixed in ruby-acts-as-tree 2.9.1-1 has caused the Debian Bug report #996121, regarding ruby-acts-as-tree: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:

Bug#996119: marked as done (ruby-activerecord-nulldb-adapter: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: Employee.create)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 02:36:11 + with message-id and subject line Bug#996119: fixed in ruby-activerecord-nulldb-adapter 0.8.0-1 has caused the Debian Bug report #996119, regarding ruby-activerecord-nulldb-adapter: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:

Bug#984338: marked as done (slic3r-prusa: ftbfs with GCC-11)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 02:36:33 + with message-id and subject line Bug#984338: fixed in slic3r-prusa 2.3.3+dfsg-2 has caused the Debian Bug report #984338, regarding slic3r-prusa: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt

Bug#1000287: marked as done (python-tornado FTBFS with Python 3.10)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 02:34:05 + with message-id and subject line Bug#1000287: fixed in python-tornado 6.1.0-2 has caused the Debian Bug report #1000287, regarding python-tornado FTBFS with Python 3.10 to be marked as done. This means that you claim that the problem has been

Processed: Bug#1000287 marked as pending in python-tornado

2021-11-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1000287 [src:python-tornado] python-tornado FTBFS with Python 3.10 Added tag(s) pending. -- 1000287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1000287: marked as pending in python-tornado

2021-11-20 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #1000287 in python-tornado 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#996119: marked as pending in ruby-activerecord-nulldb-adapter

2021-11-20 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #996119 in ruby-activerecord-nulldb-adapter 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#996119 marked as pending in ruby-activerecord-nulldb-adapter

2021-11-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996119 [src:ruby-activerecord-nulldb-adapter] ruby-activerecord-nulldb-adapter: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: Employee.create Added tag(s) pending. -- 996119:

Processed: user reproducible-bui...@lists.alioth.debian.org, usertagging 997541, tagging 997541

2021-11-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > user reproducible-bui...@lists.alioth.debian.org Setting user to reproducible-bui...@lists.alioth.debian.org (was p...@debian.org). > usertags 997541 - patch Usertags were: ftbfs patch. Usertags are now: ftbfs. > tags 997541 + patch Bug #997541

Bug#1000265: marked as done (typo in fix for CVE-2021-21996 breaks file.managed on stretch)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 01:41:47 +0100 with message-id <7f29ec6be4db55571badb591100056bedd73cd2a.ca...@debian.org> and subject line Re: typo in fix for CVE-2021-21996 breaks file.managed on stretch has caused the Debian Bug report #1000265, regarding typo in fix for CVE-2021-21996

Bug#997496: marked as done (typer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 00:34:52 + with message-id and subject line Bug#997496: fixed in typer 0.4.0-1 has caused the Debian Bug report #997496, regarding typer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13 to be marked

Bug#1000293: Problems starting jackd: Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1

2021-11-20 Thread Arnaldo Pirrone
Package: jackd2 Version: 1.9.19~dfsg-2 Severity: grave X-Debbugs-Cc: it9...@gmail.com Apparently there is something wrong with Jack and dbus. Also reported here: https://www.reddit.com/r/linuxaudio/comments/qtmynn/problems_starting_jackd_method_requestrelease_is/ Find below the jack server logs.

Bug#996780: gnome-boxes: Systematic system freeze few seconds after launching a Windows WM

2021-11-20 Thread Gunnar Hjalmarsson
Are you possibly using a NVIDIA driver? Asking because of this: https://github.com/NVIDIA/egl-wayland/issues/27#issuecomment-951725683 -- Cheers, Gunnar Hjalmarsson

Bug#998108: reopening 998108

2021-11-20 Thread Christoph Anton Mitterer
On Sat, 2021-11-20 at 15:30 -0800, Josh Triplett wrote: > I'm still experiencing this bug regularly, with complete browser UI > freezes that require killing and restarting Firefox. Hm perhaps something else? At least I haven't suffered from that particular issue since 94.0-2. Cheers, Chris.

Bug#998108: reopening 998108

2021-11-20 Thread Josh Triplett
reopen 998108 94.0-2 thanks I'm still experiencing this bug regularly, with complete browser UI freezes that require killing and restarting Firefox. WebGL or video seems to trigger it more often, as does opening a new tab. Browsing on an existing tab doesn't tend to trigger it.

Bug#1000292: pyhst2: FTBFS against Python 3.10

2021-11-20 Thread Andreas Beckmann
Source: pyhst2 Version: 2020c-3 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, 2020c-3 FTBFS since Python 3.10 got added as a supported version: [ creating build creating build/temp.linux-x86_64-3.10 creating build/temp.linux-x86_64-3.10/PyHST creating

Processed: tagging 1000263, fixed 982737 in 0.3.1-1, fixed 979170 in 2.31.1-1, fixed 981574 in 1.1.90-1 ...

2021-11-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1000263 + sid bookworm Bug #1000263 [tt-rss] package broken after php8 upgrade Added tag(s) sid and bookworm. > fixed 982737 0.3.1-1 Bug #982737 {Done: Sebastien Bacher } [src:gnome-autoar] gnome-autoar: CVE-2020-36241 Marked as fixed in

Bug#1000265: typo in fix for CVE-2021-21996 breaks file.managed on stretch

2021-11-20 Thread Markus Koschany
On Sat, 20 Nov 2021 16:46:34 + Jamie Heilman wrote: > Package: salt-common > Version: 2016.11.2+ds-1+deb9u8 > Severity: grave > > The patch for 994016 in the > /usr/lib/python2.7/dist-packages/salt/fileclient.py file included: > > +    # clean_path returns an empty string if the check

Bug#999904: marked as done (Uncoordinated split of debugedit package out of src:rpm)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sun, 21 Nov 2021 00:22:57 +0200 with message-id and subject line Re: Bug#04: Uncoordinated split of debugedit package out of src:rpm has caused the Debian Bug report #04, regarding Uncoordinated split of debugedit package out of src:rpm to be marked as done. This

Bug#999904: Uncoordinated split of debugedit package out of src:rpm

2021-11-20 Thread Peter Pentchev
Version: 4.17.0+dfsg1-1 On Thu, Nov 18, 2021 at 12:19:10PM +0200, Peter Pentchev wrote: > control: tag -1 + confirmed pending > > On Thu, Nov 18, 2021 at 09:45:06AM +0100, Laurent Bigonville wrote: > > Source: debugedit,rpm > > Severity: serious > > Tags: sid bookworm > > > > Hello, > > > >

Bug#1000210: [regression] uscan die: filenamemangle failed

2021-11-20 Thread Yadd
OK, let's do that -- Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.

Bug#1000210: [regression] uscan die: filenamemangle failed

2021-11-20 Thread Mattia Rizzolo
This is not the problem here really. It's the different matching base. Together with the previous versification I also verified that such filenamemangle (like systemd's) don't match anymore. That's equally problematic (if not more!) than the program exiting with an error. I can agree however

Bug#987468: marked as done (rpm: Please drop the build-dependencies against libsepol1-dev and libsemanage1-dev)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 22:07:06 + with message-id and subject line Bug#999816: fixed in rpm 4.17.0+dfsg1-1 has caused the Debian Bug report #999816, regarding rpm: Please drop the build-dependencies against libsepol1-dev and libsemanage1-dev to be marked as done. This means

Bug#999816: marked as done (rpm - build-depends on removed package.)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 22:07:06 + with message-id and subject line Bug#999816: fixed in rpm 4.17.0+dfsg1-1 has caused the Debian Bug report #999816, regarding rpm - build-depends on removed package. to be marked as done. This means that you claim that the problem has been dealt

Bug#984120: marked as done (fcoe-utils: ftbfs with GCC-11)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 22:03:40 + with message-id and subject line Bug#984120: fixed in fcoe-utils 1.0.34-1 has caused the Debian Bug report #984120, regarding fcoe-utils: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1000210: [regression] uscan die: filenamemangle failed

2021-11-20 Thread Yadd
Le 20/11/2021 à 13:36, Mattia Rizzolo a écrit : > On Sat, Nov 20, 2021 at 01:14:23PM +0100, Yadd wrote: >> Le 20/11/2021 à 12:23, Mattia Rizzolo a écrit : >>> So, effectively, the change broke the specification. >> >> It looks like the specification was not good. A filename isn't an URL > > Be

Bug#917829: marked as done (python-intbitset: FTBFS when built with dpkg-buildpackage -A)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 21:54:07 + with message-id and subject line Bug#917829: fixed in python-intbitset 2.3.0-3.2 has caused the Debian Bug report #917829, regarding python-intbitset: FTBFS when built with dpkg-buildpackage -A to be marked as done. This means that you claim

Bug#997135: marked as done (abydos: FTBFS: You must configure the bibtex_bibfiles setting)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 21:48:46 + with message-id and subject line Bug#997135: fixed in abydos 0.5.0+git20201231.344346a-4 has caused the Debian Bug report #997135, regarding abydos: FTBFS: You must configure the bibtex_bibfiles setting to be marked as done. This means that you

Bug#1000287: python-tornado FTBFS with Python 3.10

2021-11-20 Thread Adrian Bunk
Source: python-tornado Version: 6.1.0-1 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/package.php?p=python-tornado ... == ERROR: test_asyncio_accessor

Bug#999398: marked as done (zodbpickle ftbfs with Python 3.10 (test failures))

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 20:47:08 + with message-id and subject line Bug#999398: fixed in zodbpickle 2.2.0-1 has caused the Debian Bug report #999398, regarding zodbpickle ftbfs with Python 3.10 (test failures) to be marked as done. This means that you claim that the problem has

Bug#999402: marked as done (pyasn ftbfs with Python 3.10 (test failures))

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 20:39:24 + with message-id and subject line Bug#999402: fixed in pyasn 1.6.1-3 has caused the Debian Bug report #999402, regarding pyasn ftbfs with Python 3.10 (test failures) to be marked as done. This means that you claim that the problem has been dealt

Bug#1000269: marked as done (python3-cxx-dev lacks support for Python 3.10)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 20:39:29 + with message-id and subject line Bug#1000269: fixed in pycxx 7.1.4-0.2 has caused the Debian Bug report #1000269, regarding python3-cxx-dev lacks support for Python 3.10 to be marked as done. This means that you claim that the problem has been

Bug#999626: marked as done (maxima-emacs: fails to install with xemacs21)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 20:37:38 + with message-id and subject line Bug#999626: fixed in maxima 5.45.1-5 has caused the Debian Bug report #999626, regarding maxima-emacs: fails to install with xemacs21 to be marked as done. This means that you claim that the problem has been

Processed: severity of 1000279 is serious

2021-11-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1000279 serious Bug #1000279 [src:openscap] FTBFS: CMake Error: Unknown argument --enable-perl Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000279:

Processed: Merge duplicates

2021-11-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 999816 src:rpm Bug #999816 [rpm] rpm - build-depends on removed package. Bug reassigned from package 'rpm' to 'src:rpm'. No longer marked as found in versions rpm/4.16.1.2+dfsg1-3. Ignoring request to alter fixed versions of bug #999816

Processed: Bug#999398 marked as pending in zodbpickle

2021-11-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #999398 [src:zodbpickle] zodbpickle ftbfs with Python 3.10 (test failures) Added tag(s) pending. -- 999398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#999398: marked as pending in zodbpickle

2021-11-20 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #999398 in zodbpickle 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#1000274: py7zr FTBFS with python 3.10

2021-11-20 Thread Adrian Bunk
Source: py7zr Version: 0.11.3+dfsg-1 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/logs.php?pkg=py7zr=0.11.3%2Bdfsg-1%2Bb1 ... = test session starts == platform linux -- Python 3.10.0+, pytest-6.2.5, py-1.10.0,

Bug#996303: marked as done (ruby-json-jwt: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error:)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 19:19:40 + with message-id and subject line Bug#996303: fixed in ruby-json-jwt 1.11.0-2 has caused the Debian Bug report #996303, regarding ruby-json-jwt: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: to be marked as done. This

Processed: Bug#996303 marked as pending in ruby-json-jwt

2021-11-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996303 [src:ruby-json-jwt] ruby-json-jwt: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: Added tag(s) pending. -- 996303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996303 Debian Bug Tracking System Contact

Bug#996303: marked as pending in ruby-json-jwt

2021-11-20 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #996303 in ruby-json-jwt 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#997246: marked as done (opensaml: FTBFS: add_reference.hpp:27:16: error: forming reference to qualified function type ‘opensaml::saml2::Attribute*() const noexcept’)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 19:03:35 + with message-id and subject line Bug#997246: fixed in opensaml 3.2.1-1 has caused the Debian Bug report #997246, regarding opensaml: FTBFS: add_reference.hpp:27:16: error: forming reference to qualified function type

Processed: teach bts the right meta info

2021-11-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 995358 src:ruby-graphql 1.11.8-2 Bug #995358 {Done: Daniel Leidert } [src:ruby-graphql] ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant GraphQL::StaticValidation::Validator::Timeout Ignoring request to

Bug#1000271: jupyter-client breaks dask.distributed autopkgtest: ERROR - Workers don't have promised key: ['tcp://127.0.0.1:33937']

2021-11-20 Thread Paul Gevers
Source: jupyter-client, dask.distributed Control: found -1 jupyter-client/7.0.6-2 Control: found -1 dask.distributed/2021.09.1+ds.1-2 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s),

Processed: jupyter-client breaks dask.distributed autopkgtest: ERROR - Workers don't have promised key: ['tcp://127.0.0.1:33937']

2021-11-20 Thread Debian Bug Tracking System
Processing control commands: > found -1 jupyter-client/7.0.6-2 Bug #1000271 [src:jupyter-client, src:dask.distributed] jupyter-client breaks dask.distributed autopkgtest: ERROR - Workers don't have promised key: ['tcp://127.0.0.1:33937'] Marked as found in versions jupyter-client/7.0.6-2. >

Bug#908017: marked as done (network-manager-iodine FTBFS with glib 2.58)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 18:19:10 + with message-id and subject line Bug#908017: fixed in network-manager-iodine 1.2.0-3.1 has caused the Debian Bug report #908017, regarding network-manager-iodine FTBFS with glib 2.58 to be marked as done. This means that you claim that the

Bug#997757: marked as done (kxd: FTBFS: go: go.mod file not found in current directory or any parent directory; see 'go help modules')

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 18:05:34 + with message-id and subject line Bug#997757: fixed in kxd 0.15-3 has caused the Debian Bug report #997757, regarding kxd: FTBFS: go: go.mod file not found in current directory or any parent directory; see 'go help modules' to be marked as done.

Bug#997721: marked as done (postgresql-semver: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 18:00:09 + with message-id and subject line Bug#997721: fixed in postgresql-semver 0.31.2-1 has caused the Debian Bug report #997721, regarding postgresql-semver: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext

Bug#999376: marked as done (python-gmpy2 ftbfs with Python 3.10)

2021-11-20 Thread Martin Kelly
On 11/19/21 1:45 PM, Debian Bug Tracking System wrote: Your message dated Fri, 19 Nov 2021 21:40:53 + with message-id and subject line Bug#999376: fixed in python-gmpy2 2.1.0~b5-1 has caused the Debian Bug report #999376, regarding python-gmpy2 ftbfs with Python 3.10 to be marked as done.

Bug#1000269: python3-cxx-dev lacks support for Python 3.10

2021-11-20 Thread Adrian Bunk
Package: python3-cxx-dev Version: 7.1.4-0.1 Severity: serious Tags: ftbfs bookworm sid Control: affects -1 src:pysvn https://buildd.debian.org/status/logs.php?pkg=pysvn=1.9.12-2%2Bb1 ... debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' set -e && for i in 3.10 3.9; do

Processed: python3-cxx-dev lacks support for Python 3.10

2021-11-20 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:pysvn Bug #1000269 [python3-cxx-dev] python3-cxx-dev lacks support for Python 3.10 Added indication that 1000269 affects src:pysvn -- 1000269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000269 Debian Bug Tracking System Contact

Bug#1000268: ros-ros-comm FTBFS on IPV6-only buildds

2021-11-20 Thread Adrian Bunk
Source: ros-ros-comm Version: 1.15.13+ds1-5 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=ros-ros-comm=amd64=1.15.13%2Bds1-5%2Bb1=1637417945=0 ... [roswtf.rosunit-roswtf_command_line_online/test_cmd_help][passed]

Processed: Bug#997757 marked as pending in kxd

2021-11-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #997757 [src:kxd] kxd: FTBFS: go: go.mod file not found in current directory or any parent directory; see 'go help modules' Added tag(s) pending. -- 997757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997757 Debian Bug Tracking System

Bug#997757: marked as pending in kxd

2021-11-20 Thread Alberto Bertogli
Control: tag -1 pending Hello, Bug #997757 in kxd reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/kxd/-/commit/060e537f720f6d2b7e3210bce867b774041fd727

Bug#1000265: typo in fix for CVE-2021-21996 breaks file.managed on stretch

2021-11-20 Thread Jamie Heilman
Package: salt-common Version: 2016.11.2+ds-1+deb9u8 Severity: grave The patch for 994016 in the /usr/lib/python2.7/dist-packages/salt/fileclient.py file included: +# clean_path returns an empty string if the check fails +root_path = salt.utils.path.join(cachedir, "extrn_files",

Bug#1000263: package broken after php8 upgrade

2021-11-20 Thread VA
Package: tt-rss Version: 21~git20210204.b4cbc79+dfsg-1 Severity: serious Since upgrade from php packages 7.4 to 8.1, tt-rss is unusable. Logs contain several occurrences of: [Sat Nov 20 17:11:06.950555 2021] [php:error] [pid 2895803] [client 127.0.0.1:40988] PHP Fatal error: Uncaught

Bug#1000210: [regression] uscan die: filenamemangle failed

2021-11-20 Thread Yadd
Le 20/11/2021 à 13:36, Mattia Rizzolo a écrit : > On Sat, Nov 20, 2021 at 01:14:23PM +0100, Yadd wrote: >> Le 20/11/2021 à 12:23, Mattia Rizzolo a écrit : >>> So, effectively, the change broke the specification. >> >> It looks like the specification was not good. A filename isn't an URL > > Be

Bug#999397: marked as done (siphashc ftbfs with Python 3.10 (test failures))

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 13:55:30 + with message-id and subject line Bug#999397: fixed in siphashc 2.1-0.1 has caused the Debian Bug report #999397, regarding siphashc ftbfs with Python 3.10 (test failures) to be marked as done. This means that you claim that the problem has been

Bug#999397: siphashc: diff for NMU version 2.1-0.1

2021-11-20 Thread Stefano Rivera
Control: tags 999397 + patch Dear maintainer, I've prepared an NMU for siphashc (versioned as 2.1-0.1). The diff is attached to this message. Regards. SR diff -Nru siphashc-1.2/appveyor.yml siphashc-2.1/appveyor.yml --- siphashc-1.2/appveyor.yml 2018-10-04 06:47:17.0 -0400 +++

Processed: siphashc: diff for NMU version 2.1-0.1

2021-11-20 Thread Debian Bug Tracking System
Processing control commands: > tags 999397 + patch Bug #999397 [src:siphashc] siphashc ftbfs with Python 3.10 (test failures) Added tag(s) patch. -- 999397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#999395: marked as done (python-zstd ftbfs with Python 3.10 (test failures))

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 12:48:59 + with message-id and subject line Bug#999395: fixed in python-zstd 1.5.0.2-1 has caused the Debian Bug report #999395, regarding python-zstd ftbfs with Python 3.10 (test failures) to be marked as done. This means that you claim that the problem

Processed: Bug#998528 marked as pending in file-roller

2021-11-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #998528 [src:file-roller] file-roller: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "magic" Added tag(s) pending. -- 998528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998528 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#998528: marked as pending in file-roller

2021-11-20 Thread Andreas Henriksson
Control: tag -1 pending Hello, Bug #998528 in file-roller 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#1000210: [regression] uscan die: filenamemangle failed

2021-11-20 Thread Mattia Rizzolo
On Sat, Nov 20, 2021 at 01:14:23PM +0100, Yadd wrote: > Le 20/11/2021 à 12:23, Mattia Rizzolo a écrit : > > So, effectively, the change broke the specification. > > It looks like the specification was not good. A filename isn't an URL Be that as it may, we can't break something like that without

Bug#1000210: [regression] uscan die: filenamemangle failed

2021-11-20 Thread Yadd
Le 20/11/2021 à 12:23, Mattia Rizzolo a écrit : > Yadd: > > Looking better, I think we do have a small problem here: > > On Fri, Nov 19, 2021 at 08:16:37PM +0100, Michael Biebl wrote: >> uscan info: Looking at $base = >> https://github.com/systemd/systemd-stable/tags with >> $filepattern =

Bug#1000210: [regression] uscan die: filenamemangle failed

2021-11-20 Thread Mattia Rizzolo
Yadd: Looking better, I think we do have a small problem here: On Fri, Nov 19, 2021 at 08:16:37PM +0100, Michael Biebl wrote: > uscan info: Looking at $base = https://github.com/systemd/systemd-stable/tags > with > $filepattern = .*/v?(\d\S*)\.tar\.gz found > $newfile = >

Bug#998395: marked as done (FTBFS: very wrong python dependency)

2021-11-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Nov 2021 09:18:57 + with message-id and subject line Bug#998395: fixed in google-auth-httplib2 0.1.0-2 has caused the Debian Bug report #998395, regarding FTBFS: very wrong python dependency to be marked as done. This means that you claim that the problem has been

Bug#1000255: mpv: autopkgtest failures

2021-11-20 Thread Gianfranco Costamagna
Source: mpv Version: 0.34.0-1 Severity: serious Hello, the last version 0.34.0 is regressed on arm64 armhf and probably other architectures. Look, e.g. https://ci.debian.net/data/autopkgtest/testing/arm64/p/python-mpv/16812363/log.gz (Reading database ... 16518 files and directories currently

Processed (with 2 errors): severity of 987468 is serious, forcibly merging 987468 999816, tagging 987468

2021-11-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 987468 serious Bug #987468 [src:rpm] rpm: Please drop the build-dependencies against libsepol1-dev and libsemanage1-dev Severity set to 'serious' from 'important' > forcemerge 987468 999816 Bug #987468 [src:rpm] rpm: Please drop the