Bug#1001348: marked as done (dask: autopkgtest failures on 32 bit with pandas 1.3: Buffer type mismatch)

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sun, 27 Feb 2022 07:52:14 + with message-id <1c123171-ec21-b078-fdfc-4a627cc77...@debian.org> and subject line re: dask: autopkgtest failures on 32 bit with pandas 1.3: Buffer type mismatch has caused the Debian Bug report #1001348, regarding dask: autopkgtest failures on

Bug#1006535: sphinx-remove-toctrees - source-only upload required.

2022-02-26 Thread Peter Michael Green
Package: sphinx-remove-toctrees Version: 0.0.3-1 Severity: serious The release team have decreed that only binaries build on the buildd network can migrate to testing, please make a source-only upload so your package can migrate.

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

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sun, 27 Feb 2022 05:34:33 + with message-id and subject line Bug#1006042: fixed in rich 11.2.0-1 has caused the Debian Bug report #1006042, regarding rich: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13 to be

Bug#1006042: marked as pending in rich

2022-02-26 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #1006042 in rich 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#1006042 marked as pending in rich

2022-02-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1006042 [src:rich] rich: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13 Added tag(s) pending. -- 1006042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006042 Debian Bug

Bug#1005527: python-wsproto: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

2022-02-26 Thread Paul Wise
On Sun, 13 Feb 2022 08:45:58 +0100 Lucas Nussbaum wrote: > Source: python-wsproto ... > During a rebuild of all packages in sid, your package failed to build > on amd64. Upstream has fixed this in git, so I asked them to make a new release: https://github.com/python-hyper/wsproto/issues/171

Processed: bug 1005527 is forwarded to https://github.com/python-hyper/wsproto/commit/76c130fe6309235bb40161ed0e9fc9721ec55ab1 https://github.com/python-hyper/wsproto/pull/170 https://github.com/pytho

2022-02-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1005527 > https://github.com/python-hyper/wsproto/commit/76c130fe6309235bb40161ed0e9fc9721ec55ab1 > https://github.com/python-hyper/wsproto/pull/170 > https://github.com/python-hyper/wsproto/issues/169 Bug #1005527

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

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sun, 27 Feb 2022 03:48:39 + with message-id and subject line Bug#1005547: fixed in fastapi 0.74.1-1 has caused the Debian Bug report #1005547, regarding fastapi: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

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

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sun, 27 Feb 2022 03:48:39 + with message-id and subject line Bug#1005635: fixed in fastapi 0.74.1-1 has caused the Debian Bug report #1005635, regarding sqlmodel: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code

Processed: Bug#1005547 marked as pending in fastapi

2022-02-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1005547 [src:fastapi] fastapi: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13 Added tag(s) pending. -- 1005547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005547 Debian

Processed: Bug#1005635 marked as pending in fastapi

2022-02-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1005635 [src:sqlmodel] sqlmodel: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13 Added tag(s) pending. -- 1005635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005635 Debian

Bug#1005635: marked as pending in fastapi

2022-02-26 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #1005635 in fastapi 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#1005547: marked as pending in fastapi

2022-02-26 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #1005547 in fastapi 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#1005393: marked as done (tvnamer: Fails with traceback)

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sun, 27 Feb 2022 02:48:45 + with message-id and subject line Bug#1005393: fixed in tvdb-api 3.1-2 has caused the Debian Bug report #1005393, regarding tvnamer: Fails with traceback to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1006534: pagekite: Fails to accept client connections

2022-02-26 Thread Francois Marier
Package: pagekite Version: 1.5.2.200603-2 Severity: grave Tags: patch Justification: renders package unusable As described in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004295, incoming pagekite connections don't work on Debian 11. If you run your own frontend on that version of Debian

Bug#1005393: marked as pending in tvdb-api

2022-02-26 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #1005393 in tvdb-api 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#1005393 marked as pending in tvdb-api

2022-02-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1005393 [tvdb-api] tvnamer: Fails with traceback Added tag(s) pending. -- 1005393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1005858: gh,gitsome: File conflict, both ship /usr/bin/gh

2022-02-26 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/donnemartin/gitsome/issues/177 Bug #1005858 [gh,gitsome] gh,gitsome: File conflict, both ship /usr/bin/gh Ignoring request to change the forwarded-to-address of bug#1005858 to the same value -- 1005858:

Bug#1005858: gh,gitsome: File conflict, both ship /usr/bin/gh

2022-02-26 Thread Paul Wise
Control: forwarded -1 https://github.com/donnemartin/gitsome/issues/177 On Sat, 26 Feb 2022 23:43:14 +0800 SZ Lin (林上智) wrote: > The "gitsome" has used "gh" since 2017, and thus would you mind renaming > the "gh" in your package to avoid the conflict issue? Since gh is the official GitHub

Bug#1005393: tvnamer: Fails with traceback

2022-02-26 Thread Sandro Tosi
control: reassign -1 tvdb-api > File "/usr/share/tvnamer/main.py", line 18, in > import tvdb_api > File "/usr/lib/python3/dist-packages/tvdb_api.py", line 34, in > from requests_cache.backends.base import _to_bytes, _DEFAULT_HEADERS > ImportError: cannot import name '_to_bytes' from

Processed: Re: Bug#1005393: tvnamer: Fails with traceback

2022-02-26 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 tvdb-api Bug #1005393 [tvnamer] tvnamer: Fails with traceback Bug reassigned from package 'tvnamer' to 'tvdb-api'. No longer marked as found in versions tvnamer/3.0.4-1. Ignoring request to alter fixed versions of bug #1005393 to the same values

Processed: bug 1005858 is forwarded to https://github.com/donnemartin/gitsome/issues/177

2022-02-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1005858 https://github.com/donnemartin/gitsome/issues/177 Bug #1005858 [gh,gitsome] gh,gitsome: File conflict, both ship /usr/bin/gh Set Bug forwarded-to-address to 'https://github.com/donnemartin/gitsome/issues/177'. > thanks Stopping

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

2022-02-26 Thread Alyssa Rosenzweig
Hi, I've been prepared an NMU and will be having it uploaded to DELAYED/4. Patch below. Alyssa --- diff -u mesa-21.3.5/debian/changelog mesa-21.3.5/debian/changelog --- mesa-21.3.5/debian/changelog +++ mesa-21.3.5/debian/changelog @@ -1,3 +1,12 @@ +mesa (21.3.5-1.1) unstable; urgency=medium +

Bug#995580: marked as done (wine build-depends on unicode-data (< 14) but testing/unstable has 14.0.0-1)

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Feb 2022 22:59:37 + with message-id and subject line Bug#995580: fixed in wine 6.0.2~repack-1 has caused the Debian Bug report #995580, regarding wine build-depends on unicode-data (< 14) but testing/unstable has 14.0.0-1 to be marked as done. This means that you

Bug#991822: marked as done (src:wine: dh_auto_clean deletes unrelated files outside of package source)

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Feb 2022 22:59:37 + with message-id and subject line Bug#991822: fixed in wine 6.0.2~repack-1 has caused the Debian Bug report #991822, regarding src:wine: dh_auto_clean deletes unrelated files outside of package source to be marked as done. This means that you

Bug#984402: marked as done (wine: ftbfs with GCC-11)

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Feb 2022 22:59:37 + with message-id and subject line Bug#984402: fixed in wine 6.0.2~repack-1 has caused the Debian Bug report #984402, regarding wine: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1005463: marked as done (python3-rdflib: incompatible with pyparser v3)

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Feb 2022 21:31:43 + with message-id and subject line Bug#1005463: fixed in rdflib 6.1.1-1 has caused the Debian Bug report #1005463, regarding python3-rdflib: incompatible with pyparser v3 to be marked as done. This means that you claim that the problem has been

Bug#1005840: claws-mail-themes: includes non-free content (CC-by-nc-sa-v3.0)

2022-02-26 Thread Ricardo Mones
On Tue, 15 Feb 2022 22:12:54 +0100 "Francesco Poli (wintermute)" wrote: > Package: claws-mail-themes > Version: 20140629+dfsg2-1 > Severity: serious > Justification: Policy 2.2.1 > > Hello and thanks for maintaining claws-mail. > > I noticed that one of the themes shipped in package

Bug#1005696: marked as done (cgal: -latomic not added on mipsel)

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Feb 2022 19:50:26 + with message-id and subject line Bug#1005696: fixed in cgal 5.4-2 has caused the Debian Bug report #1005696, regarding cgal: -latomic not added on mipsel to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1005895: marked as done (expat: CVE-2022-25236)

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Feb 2022 19:47:34 + with message-id and subject line Bug#1005895: fixed in expat 2.2.6-2+deb10u3 has caused the Debian Bug report #1005895, regarding expat: CVE-2022-25236 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1005894: marked as done (expat: CVE-2022-25235)

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Feb 2022 19:47:34 + with message-id and subject line Bug#1005894: fixed in expat 2.2.6-2+deb10u3 has caused the Debian Bug report #1005894, regarding expat: CVE-2022-25235 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1006119: marked as done (uwsgi: FTBFS with ruby3.0 as default)

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Feb 2022 19:04:55 + with message-id and subject line Bug#1006119: fixed in uwsgi 2.0.20-2.1 has caused the Debian Bug report #1006119, regarding uwsgi: FTBFS with ruby3.0 as default to be marked as done. This means that you claim that the problem has been dealt

Bug#1005895: marked as done (expat: CVE-2022-25236)

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Feb 2022 18:47:18 + with message-id and subject line Bug#1005895: fixed in expat 2.2.10-2+deb11u2 has caused the Debian Bug report #1005895, regarding expat: CVE-2022-25236 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1005894: marked as done (expat: CVE-2022-25235)

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Feb 2022 18:47:18 + with message-id and subject line Bug#1005894: fixed in expat 2.2.10-2+deb11u2 has caused the Debian Bug report #1005894, regarding expat: CVE-2022-25235 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1006374: marked as done (graphicsmagick breaks ruby-mini-magick autopkgtest: Failure/Error: expect(subject["EXIF:Flash"]).to eq "0")

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Feb 2022 17:48:42 + with message-id and subject line Bug#1006374: fixed in graphicsmagick 1.4+really1.3.37+hg16670-1 has caused the Debian Bug report #1006374, regarding graphicsmagick breaks ruby-mini-magick autopkgtest: Failure/Error:

Bug#907691: petri-foo: License incompatibility: links with OpenSSL

2022-02-26 Thread Sebastian Andrzej Siewior
On 2018-08-31 15:03:38 [+0300], Yavor Doganov wrote: > Package: petri-foo > Version: 0.1.87-4 > Severity: serious > > This package is licensed under GPLv2 only but links with the OpenSSL > library which makes it impossible for distribution as the licenses are > incompatible. See > >

Bug#1006374: graphicsmagick breaks ruby-mini-magick autopkgtest: Failure/Error: expect(subject["EXIF:Flash"]).to eq "0"

2022-02-26 Thread GCS
On Sat, Feb 26, 2022 at 4:56 PM Bob Friesenhahn wrote: > I believe that the problem is that mini-magick is retrieving EXIF > attributes in 'ping' mode but the changeset which caused the problem > only returns the attributes if the image data was read. The solution > was just to move some code.

Bug#1006119: uwsgi: FTBFS with ruby3.0 as default

2022-02-26 Thread Antonio Terceiro
On Sun, Feb 20, 2022 at 03:26:42PM -0300, Antonio Terceiro wrote: > Control: tag -1 + patch > > On Sat, 19 Feb 2022 14:19:46 +0100 Paul Gevers wrote: > > Source: uwsgi > > Version: 2.0.20-2 > > Severity: serious > > Tags: ftbfs > > Justification: FTBFS > > Control: block -1 by 1004915 > > > >

Bug#1006374: graphicsmagick breaks ruby-mini-magick autopkgtest: Failure/Error: expect(subject["EXIF:Flash"]).to eq "0"

2022-02-26 Thread Bob Friesenhahn
On Fri, 25 Feb 2022, László Böszörményi wrote: This should be it. Is your GM the latest version from Mercurial? Image: /home/bfriesen/src/minimagick.git/spec/fixtures/exif.jpg Exif Version: 0220 Date Time Original: 2016:11:12 09:17:56 Flash: 0 Package ruby-mini-magick check

Bug#1006286: marked as done (hivex: wrongly detects ruby versions during build)

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Feb 2022 15:49:34 + with message-id and subject line Bug#1006286: fixed in hivex 1.3.21-1.1 has caused the Debian Bug report #1006286, regarding hivex: wrongly detects ruby versions during build to be marked as done. This means that you claim that the problem has

Bug#1001217: marked as done (FTBFS against Ruby 3.0)

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Feb 2022 15:49:10 + with message-id and subject line Bug#1001217: fixed in dislocker 0.7.3-2.1 has caused the Debian Bug report #1001217, regarding FTBFS against Ruby 3.0 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1005858: gh,gitsome: File conflict, both ship /usr/bin/gh

2022-02-26 Thread 林上智
Hi, gh package maintainer Axel Beckert 於 2022年2月16日 週三 下午2:15寫道: > Package: gh,gitsome > Severity: serious > Control: found -1 gitsome/0.8.0+ds-6 > Control: found -1 gh/2.4.0+dfsg1-1 > > Hi, > > installing gh fails for me as follows: > > Unpacking gh (2.4.0+dfsg1-1) ... > dpkg: error processing

Bug#1006500: Missing bnx2x firmware 7.13.21.0 renders NIC unusable with Linux 5.16

2022-02-26 Thread Etienne Dechamps
Package: firmware-bnx2x Version: 20210818-1 Severity: grave On Linux 5.16, the bnx2x module requests firmware 7.13.21.0: # modinfo bnx2x filename: /lib/modules/5.16.0-2-amd64/kernel/drivers/net/ethernet/broadcom/bnx2x/bnx2x.ko firmware: bnx2x/bnx2x-e2-7.13.21.0.fw firmware:

Processed: tagging 1005684

2022-02-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1005684 + pending Bug #1005684 [src:kate] kate: FTBFS: dh_missing: warning: usr/share/kservices5/plasma-applet-org.kde.plasma.katesessions.desktop exists in debian/tmp but is not installed to anywhere Added tag(s) pending. > thanks

Bug#1004935: marked as done (connman: CVE-2022-23096 CVE-2022-23097 CVE-2022-23098)

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Feb 2022 10:34:08 + with message-id and subject line Bug#1004935: fixed in connman 1.36-2.4 has caused the Debian Bug report #1004935, regarding connman: CVE-2022-23096 CVE-2022-23097 CVE-2022-23098 to be marked as done. This means that you claim that the problem

Bug#1004935: connman: CVE-2022-23096 CVE-2022-23097 CVE-2022-23098

2022-02-26 Thread Bastian Germann
As no package maintainer stepped up to fix this, I am NMUing the package with the enclosed changes.diff -Nru connman-1.36/debian/changelog connman-1.36/debian/changelog --- connman-1.36/debian/changelog 2021-10-09 22:49:52.0 +0200 +++ connman-1.36/debian/changelog 2022-02-26

Bug#1006368: marked as done (upowerd: cannot open '/dev/input/event3': Success)

2022-02-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Feb 2022 10:05:40 + with message-id and subject line Bug#1006368: fixed in upower 0.99.16-2 has caused the Debian Bug report #1006368, regarding upowerd: cannot open '/dev/input/event3': Success to be marked as done. This means that you claim that the problem has

Bug#1005438: pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ --exclude opengl"

2022-02-26 Thread Marcin Owsiany
Dnia Tue, Feb 22, 2022 at 08:57:25AM +0100, Andreas Tille napisał(a): > I had a look into this issue since a Debian Med package received a > testing removal warning. I can confirm the build fails with > >Segmentation fault > > in the build time test suite. Just out of curiosity I ran the

Bug#1006485: fscrypt: CVE-2022-25326 CVE-2022-25327 CVE-2022-25328

2022-02-26 Thread Salvatore Bonaccorso
Source: fscrypt Version: 0.3.1-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for fscrypt. CVE-2022-25326[0]: | fscrypt through v0.3.2 creates a world-writable directory by default | when setting

Processed: bug 1006333 is forwarded to https://lab.louiz.org/louiz/biboumi/-/issues/3465

2022-02-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1006333 https://lab.louiz.org/louiz/biboumi/-/issues/3465 Bug #1006333 [biboumi] biboumi: fail to start after libexpat1 update Set Bug forwarded-to-address to 'https://lab.louiz.org/louiz/biboumi/-/issues/3465'. > thanks Stopping

Processed: bug #1005618 forwarded to upstream fix

2022-02-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1005618 https://github.com/vagnum08/cpupower-gui/commit/97f8ac02 Bug #1005618 [src:cpupower-gui] cpupower-gui: FTBFS: ../data/meson.build:12:0: ERROR: Function does not take positional arguments. Set Bug forwarded-to-address to