Bug#958817: reopening 955817, notfixed 955817 in vtk7/7.1.1+dfsg2-4, fixed 958817 in vtk7/7.1.1+dfsg2-4 ...

reopen 955817 notfixed 955817 vtk7/7.1.1+dfsg2-4 fixed 958817 vtk7/7.1.1+dfsg2-4 close 958817 thanks

Processed: reopening 955817, notfixed 955817 in vtk7/7.1.1+dfsg2-4, fixed 958817 in vtk7/7.1.1+dfsg2-4 ...

Processing commands for cont...@bugs.debian.org: > reopen 955817 Bug #955817 {Done: Gert Wollny } [kazam] kazam: Fails to get audio sources from pulseaudio with python3.8 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need

Bug#925754: Fwd: Fixed in newer release of libopenshot / libopenshot-audio

On Sat, Apr 25, 2020 at 4:41 PM John Scott wrote: > On Fri, 24 Apr 2020 23:33:59 -0400 FeRD wrote: > > What version of libopenshot is that result from? The Clang namespacing > was > > fixed with the merge of 2a1fe80[1] on 2019-10-29, and would be included > in > > both libopenshot-0.2.4 and

Bug#885198: graphviz: please migrate to guile-2.2

It appears that this hasn't actually been resolved. i.e. after grabbing the current sid source (and an ldd on the current libgv-guile .so also indicates it's still built against 2.0): $ rgrep guile | grep -F 2.0 debian/control: guile-2.0-dev, debian/control: This package contains the

Processed (with 1 error): Reopen graphviz guile 2.2 dependency problem

Processing commands for cont...@bugs.debian.org: > Rob Browning writes: Unknown command or malformed arguments to command. > unarchive 885198 Bug #885198 {Done: Laszlo Boszormenyi (GCS) } [src:graphviz] graphviz: please migrate to guile-2.2 Unarchived Bug 885198 > severity 885198 serious Bug

Processed: Re: Bug#956007: mercurial: Remove use of python-subversion

Processing control commands: > severity -1 serious Bug #956007 [src:mercurial] mercurial: Remove use of python-subversion Severity set to 'serious' from 'important' -- 956007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956007 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#885215: mcron: please migrate to guile-2.2 (NMU diff 1.0.8-1.1)

--- configure.ac | 2 +- debian/changelog | 14 ++ debian/control| 4 +- debian/patches/migrate-to-guile-3.0 | 13 ++ debian/patches/series | 1 + debian/rules | 2 +- create

Bug#885215: marked as done (mcron: please migrate to guile-2.2)

Your message dated Sat, 25 Apr 2020 23:18:45 + with message-id and subject line Bug#885215: fixed in mcron 1.0.8-1.1 has caused the Debian Bug report #885215, regarding mcron: please migrate to guile-2.2 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#940992: firefoxdriver: does not work with firefox > 47 at all

On Mon, 23 Sep 2019 12:56:48 +0200 Sascha Girrulat wrote: > Hi, > > the error below does not depend to firefox driver. The firefoxdriver ist > a leftover for older firefox versions. The package documentation[3] > describes how to enable the geckodriver and there is a bug[1] (#874207) > filed for

Bug#955108: marked as done (cloudkitty: FTBFS with Sphinx 2.4: touch: cannot touch '/<>/debian/cloudkitty-doc/usr/share/doc/cloudkitty-doc/html/_static/toggle.js': No such file or directo

Your message dated Sun, 26 Apr 2020 00:33:23 +0200 with message-id <7e4b362c-59d0-d8be-a572-ec0bc50ba...@debian.org> and subject line Bug was in python3-oslosphinx has caused the Debian Bug report #955108, regarding cloudkitty: FTBFS with Sphinx 2.4: touch: cannot touch

Bug#955070: marked as done (python-doc8: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no attribute 'info')

Your message dated Sun, 26 Apr 2020 00:17:25 +0200 with message-id and subject line Bug was in python3-oslosphinx has caused the Debian Bug report #955070, regarding python-doc8: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no attribute 'info' to be marked as done. This means that

Bug#955113: marked as done (python-os-xenapi: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no attribute 'info')

Your message dated Sun, 26 Apr 2020 00:10:11 +0200 with message-id and subject line Bug was in python3-oslosphinx has caused the Debian Bug report #955113, regarding python-os-xenapi: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no attribute 'info' to be marked as done. This means

Bug#955116: marked as done (python-murano-pkg-check: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no attribute 'info')

Your message dated Sun, 26 Apr 2020 00:11:01 +0200 with message-id <112b968a-6e09-fe36-2eb2-2051ee78d...@debian.org> and subject line Bug was in python3-oslosphinx has caused the Debian Bug report #955116, regarding python-murano-pkg-check: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object

Bug#955102: marked as done (python-scciclient: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no attribute 'info')

Your message dated Sun, 26 Apr 2020 00:07:45 +0200 with message-id <3a52a4ea-8847-9191-a893-f925f16c5...@debian.org> and subject line Bug was in python3-oslosphinx has caused the Debian Bug report #955102, regarding python-scciclient: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no

Bug#958852: texlive-base/extra breaks jupyter-sphinx-theme autopkgtest: Builder name pickle not registered or available through entry point

Am 25.04.2020 um 22:10 teilte Paul Gevers mit: Hi Paul, > With recent uploads of texlive-base and texlive-extra the autopkgtest of > jupyter-sphinx-theme fails in testing when that autopkgtest is run with > the binary packages of texlive-base and texlive-extra from unstable. It > passes when run

Bug#955092: marked as done (tempest-horizon: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no attribute 'info')

Your message dated Sat, 25 Apr 2020 23:45:26 +0200 with message-id <1830e8bc-ad8c-33a4-f1f3-135a425e7...@debian.org> and subject line Bug was in python3-oslosphinx has caused the Debian Bug report #955092, regarding tempest-horizon: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no

Processed: Re: Bug#953369: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used

Processing control commands: > tags -1 patch Bug #953369 [libpython3.8-minimal] RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used Bug #953125 [libpython3.8-minimal] libpython3.8-minimal: /usr/lib/python3.8/subprocess.py:838:

Bug#953369: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used

Control: tags -1 patch On 2020-03-09 13:29:52 +0100, Vincent Lefevre wrote: > On 2020-03-09 00:08:45 +0800, 積丹尼 Dan Jacobson wrote: > > Setting up python3-apt (1.9.9) ... > > /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering > > (buffering=1) isn't supported in binary mode,

Bug#925754: Fwd: Fixed in newer release of libopenshot / libopenshot-audio

On Fri, 24 Apr 2020 23:33:59 -0400 FeRD wrote: > Sorry, I realized I might have sent this reply to the wrong bug. Yes, I sent my mail to both of the bugs (am doing now again, I guess). I am also making noise :) > What version of libopenshot is that result from? The Clang namespacing was > fixed

Processed: texlive-base/extra breaks jupyter-sphinx-theme autopkgtest: Builder name pickle not registered or available through entry point

Processing control commands: > found -1 texlive-base/2020.20200417-1 Bug #958852 [src:texlive-base, src:jupyter-sphinx-theme, src:texlive-extra] texlive-base/extra breaks jupyter-sphinx-theme autopkgtest: Builder name pickle not registered or available through entry point Marked as found in

Bug#958852: texlive-base/extra breaks jupyter-sphinx-theme autopkgtest: Builder name pickle not registered or available through entry point

Source: texlive-base, jupyter-sphinx-theme, texlive-extra Control: found -1 texlive-base/2020.20200417-1 Control: found -1 texlive-extra/2020.20200417-1 Control: found -1 jupyter-sphinx-theme/0.0.6+ds1-9 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User:

Processed: initramfs-tools: autopkgtest needs update for new version of shellcheck: SC2086: Double quote to prevent globbing and word splitting.

Processing control commands: > affects -1 src:shellcheck Bug #958851 [src:initramfs-tools] initramfs-tools: autopkgtest needs update for new version of shellcheck: SC2086: Double quote to prevent globbing and word splitting. Added indication that 958851 affects src:shellcheck -- 958851:

Bug#958851: initramfs-tools: autopkgtest needs update for new version of shellcheck: SC2086: Double quote to prevent globbing and word splitting.

Source: initramfs-tools Version: 0.136 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, shellch...@packages.debian.org Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:shellcheck Dear maintainer(s), With a recent upload of shellcheck

Bug#958350: marked as done (devscripts: autopkgtest needs update for new version of debhelper)

Your message dated Sat, 25 Apr 2020 19:33:31 + with message-id and subject line Bug#958350: fixed in devscripts 2.20.3 has caused the Debian Bug report #958350, regarding devscripts: autopkgtest needs update for new version of debhelper to be marked as done. This means that you claim that

Bug#956882: marked as done (statsmodels: FTBFS on armel)

Your message dated Sat, 25 Apr 2020 19:33:59 + with message-id and subject line Bug#956882: fixed in statsmodels 0.11.1-2 has caused the Debian Bug report #956882, regarding statsmodels: FTBFS on armel to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#958842: fsplib: autopkgtest failure: Assertion `fsp_transaction(s,,)==0' failed.

Source: fsplib Version: 0.14-4 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), With a recent upload of fsplib you added an autopkgtest, great. However, it fails. I copied some of the output at the bottom of

Bug#958841: erlang breaks elixir-lang autopkgtest: killed

Source: erlang, elixir-lang Control: found -1 erlang/1:22.3.2+dfsg-1 Control: found -1 elixir-lang/1.9.1.dfsg-1.3 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload

Processed: erlang breaks elixir-lang autopkgtest: killed

Processing control commands: > found -1 erlang/1:22.3.2+dfsg-1 Bug #958841 [src:erlang, src:elixir-lang] erlang breaks elixir-lang autopkgtest: killed Marked as found in versions erlang/1:22.3.2+dfsg-1. > found -1 elixir-lang/1.9.1.dfsg-1.3 Bug #958841 [src:erlang, src:elixir-lang] erlang breaks

Processed: severity of 956543 is serious, severity of 956359 is serious, severity of 956371 is serious

Processing commands for cont...@bugs.debian.org: > severity 956543 serious Bug #956543 [freecad] freecad: FTBFS with new opencascade 7.4 (library transition) Severity set to 'serious' from 'important' > severity 956359 serious Bug #956359 [src:netgen] netgen: FTBFS with new opencascade 7.4

Bug#958840: kmer: autopkgtest regression: No module named 'localAlignerInterface'

Source: kmer Version: 0~20150903+r2013-7 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of kmer the autopkgtest of kmer fails in testing when that autopkgtest is run with the binary

Bug#958566: Wrong package name

I think it should be a bug to package firmware-b43-installer.

Processed: Re: Bug#958830: php-apcu: upgrade to php-apcu 5.1.17->18 breaks nextcloud

Processing control commands: > close -1 Bug #958830 [php-apcu] php-apcu: upgrade to php-apcu 5.1.17->18 breaks nextcloud Marked Bug as done -- 958830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: vulkan-loader breaks openxr-sdk-source autopkgtest: VK_DEBUG_REPORT_OBJECT_TYPE_OBJECT_TABLE_NVX_EXT’ was not declared

Processing control commands: > found -1 vulkan-loader/1.2.135.0-2 Bug #958837 [src:vulkan-loader, src:openxr-sdk-source] vulkan-loader breaks openxr-sdk-source autopkgtest: VK_DEBUG_REPORT_OBJECT_TYPE_OBJECT_TABLE_NVX_EXT’ was not declared Marked as found in versions vulkan-loader/1.2.135.0-2.

Bug#958836: vulkan-loader: autopkgtest failure: missing test dependencies

Source: vulkan-loader Version: 1.2.135.0-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), With a recent upload of vulkan-loader you added an autopkgtest, great. However, it fails. I copied some of the output

Processed: Re: Bug#958830: php-apcu: upgrade to php-apcu 5.1.17->18 breaks nextcloud

Processing control commands: > close -1 Bug #958830 {Done: Ondřej Surý } [php-apcu] php-apcu: upgrade to php-apcu 5.1.17->18 breaks nextcloud Bug 958830 is already marked as done; not doing anything. -- 958830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958830 Debian Bug Tracking System

Bug#958830: php-apcu: upgrade to php-apcu 5.1.17->18 breaks nextcloud

Control: close -1 NextCloud (server) isn’t even packaged for Debian, and it should be using the default PHP version in Debian which is currently PHP7.4. The PHP7.3 has been removed from unstable and it will be shortly removed from testing. Ondrej -- Ondřej Surý > On 25 Apr 2020, at 19:45,

Bug#958837: vulkan-loader breaks openxr-sdk-source autopkgtest: VK_DEBUG_REPORT_OBJECT_TYPE_OBJECT_TABLE_NVX_EXT’ was not declared

Source: vulkan-loader, openxr-sdk-source Control: found -1 vulkan-loader/1.2.135.0-2 Control: found -1 openxr-sdk-source/1.0.8~dfsg1-2 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s),

Bug#885213: make-dfsg: please migrate to guile-2.2

Closes: 885213 --- This is the 4.2.1-1.3 NMU diff against 4.2.1-1.2. The source of the 4.2.1-1.2 code was master at https://salsa.debian.org/benh/make-dfsg The source of this NMU is debian/master at https://salsa.debian.org/rlb/make-dfsg Thanks configure.ac | 4 ++--

Bug#955019: marked as done (php-horde-trean: CVE-2020-8865)

Your message dated Sat, 25 Apr 2020 18:17:24 + with message-id and subject line Bug#955019: fixed in php-horde-trean 1.1.7-1+deb9u1 has caused the Debian Bug report #955019, regarding php-horde-trean: CVE-2020-8865 to be marked as done. This means that you claim that the problem has been

Processed: add fixed version against source package

Processing commands for cont...@bugs.debian.org: > fixed 936076 0.48.0-1 Bug #936076 {Done: Diane Trout } [python3-numba] python3-numba: numba segfaults when run with python 3.7.4 at numba/_dynfunc.c:52 Marked as fixed in versions numba/0.48.0-1. > thanks Stopping processing here. Please

Bug#937144: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).

On 21/04/2020 22:20, Thomas Goirand wrote: So, if I'm following correctly, what you seem to propose, is to remove Python 2 from unittest2. If that's the case, then I agree with such a plan. I just didn't dare to do it yet. Yes, whichever approach is taken to dealing with funcsigs, unittest2

Bug#945682: hatop: Python2 removal in sid/bullseye

Package: hatop Followup-For: Bug #945682 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Fork available at . including patch for python3 support and intention to take over as new upstream long-term. -BEGIN PGP SIGNATURE-

Processed: Re: telegram-purple: FTBFS on big endian architectures

Processing commands for cont...@bugs.debian.org: > forwarded 958828 https://github.com/majn/telegram-purple/issues/538 Bug #958828 [src:telegram-purple] telegram-purple: FTBFS on big endian architectures Set Bug forwarded-to-address to 'https://github.com/majn/telegram-purple/issues/538'. >

Bug#958830: php-apcu: upgrade to php-apcu 5.1.17->18 breaks nextcloud

Package: php-apcu Version: 5.1.18+4.0.11-1+b1 Severity: grave Justification: renders package unusable After the upgrade nextcloud just gives an internal server error The problem seems to be that nextcloud is configured to use apcu as a memory cache and this version of apcu only has php7.4 files.

Bug#958828: telegram-purple: FTBFS on big endian architectures

Source: telegram-purple Severity: serious Justification: FTBFS on release architecture … just so that nobody else reports this bug (I know about it).

Processed: Bug#955094 marked as pending in developers-reference

Processing control commands: > tag -1 pending Bug #955094 [src:developers-reference] developers-reference: FTBFS with Sphinx 2.4: latex errors Added tag(s) pending. -- 955094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955094 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#955094: marked as pending in developers-reference

Control: tag -1 pending Hello, Bug #955094 in developers-reference 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#956672: marked as done (rtkit activation fails, because service unit is installed at the wrong place)

Your message dated Sat, 25 Apr 2020 15:49:18 + with message-id and subject line Bug#956672: fixed in rtkit 0.13-4 has caused the Debian Bug report #956672, regarding rtkit activation fails, because service unit is installed at the wrong place to be marked as done. This means that you claim

Bug#956672: marked as pending in rtkit

Control: tag -1 pending Hello, Bug #956672 in rtkit 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#956672 marked as pending in rtkit

Processing control commands: > tag -1 pending Bug #956672 [rtkit] rtkit activation fails, because service unit is installed at the wrong place Added tag(s) pending. -- 956672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956672 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#958446: nvidia-legacy-340xx-driver: Fails to build with kernel 5.6

Just my 2d,  but I am with Jim P on the whole "nouveau is something I hate even more" thing.  This driver is operational in 5.5.x as we know,  but since that branch went EOL I have just reverted my machines to 5.4.x for the time being )OK for now since 5.4.x is long-term).  The native NVIDIA

Bug#951537: marked as done (php-horde-data: CVE-2020-8518)

Your message dated Sat, 25 Apr 2020 15:17:25 + with message-id and subject line Bug#951537: fixed in php-horde-data 2.1.4-3+deb9u1 has caused the Debian Bug report #951537, regarding php-horde-data: CVE-2020-8518 to be marked as done. This means that you claim that the problem has been dealt

Bug#955020: marked as done (php-horde-form: CVE-2020-8866)

Your message dated Sat, 25 Apr 2020 15:17:26 + with message-id and subject line Bug#955020: fixed in php-horde-form 2.0.15-1+deb9u2 has caused the Debian Bug report #955020, regarding php-horde-form: CVE-2020-8866 to be marked as done. This means that you claim that the problem has been

Bug#958817: vtk7: FTBFS (error: cannot convert ‘bool*’ to ‘my_bool*’ {aka ‘char*’} in assignment)

Source: vtk7 Version: 7.1.1+dfsg2-3 Severity: serious Tags: ftbfs Justification: makes the package in question unusable or mostly so Control: block 955807 by -1 Dear Maintainer, Your package FTBFS: [ 16%] Building CXX object IO/MySQL/CMakeFiles/vtkIOMySQL.dir/vtkMySQLQuery.cxx.o cd

Processed: vtk7: FTBFS (error: cannot convert ‘bool*’ to ‘my_bool*’ {aka ‘char*’} in assignment)

Processing control commands: > block 955807 by -1 Bug #955807 [release.debian.org] transition: netcdf 955807 was blocked by: 955749 955806 955715 955807 was not blocking any bugs. Added blocking bug(s) of 955807: 958817 -- 955807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955807 958817:

Bug#950840: marked as done (English India selected during installation breaks locale in lxc)

Your message dated Sat, 25 Apr 2020 15:02:11 + with message-id and subject line Bug#950840: fixed in lxc-templates 3.0.4-0+deb10u1 has caused the Debian Bug report #950840, regarding English India selected during installation breaks locale in lxc to be marked as done. This means that you

Bug#951537: marked as done (php-horde-data: CVE-2020-8518)

Your message dated Sat, 25 Apr 2020 15:02:13 + with message-id and subject line Bug#951537: fixed in php-horde-data 2.1.4-5+deb10u1 has caused the Debian Bug report #951537, regarding php-horde-data: CVE-2020-8518 to be marked as done. This means that you claim that the problem has been

Bug#948215: marked as done (FTBFS after ruby-i18n has been updated to version 1.x)

Your message dated Sat, 25 Apr 2020 15:02:10 + with message-id and subject line Bug#948215: fixed in jekyll 3.8.3+dfsg-4+deb10u1 has caused the Debian Bug report #948215, regarding FTBFS after ruby-i18n has been updated to version 1.x to be marked as done. This means that you claim that the

Bug#955019: marked as done (php-horde-trean: CVE-2020-8865)

Your message dated Sat, 25 Apr 2020 15:02:14 + with message-id and subject line Bug#955019: fixed in php-horde-trean 1.1.9-3+deb10u1 has caused the Debian Bug report #955019, regarding php-horde-trean: CVE-2020-8865 to be marked as done. This means that you claim that the problem has been

Bug#955020: marked as done (php-horde-form: CVE-2020-8866)

Your message dated Sat, 25 Apr 2020 15:02:14 + with message-id and subject line Bug#955020: fixed in php-horde-form 2.0.18-3.1+deb10u1 has caused the Debian Bug report #955020, regarding php-horde-form: CVE-2020-8866 to be marked as done. This means that you claim that the problem has been

Bug#956834: marked as done (insighttoolkit4: installs Python 3.8 extensions in the folder for Python 3.7)

Your message dated Sat, 25 Apr 2020 14:33:45 + with message-id and subject line Bug#956834: fixed in insighttoolkit4 4.13.2-dfsg1-9 has caused the Debian Bug report #956834, regarding insighttoolkit4: installs Python 3.8 extensions in the folder for Python 3.7 to be marked as done. This

Bug#958493: marked as done (sphinxcontrib-bibtex: autopkgtest regression)

Your message dated Sat, 25 Apr 2020 15:33:10 +0100 with message-id <5a0e26b3-c6d2-f5bf-cbf7-8ec2f60fe...@p10link.net> and subject line re: sphinxcontrib-bibtex: autopkgtest regression has caused the Debian Bug report #958493, regarding sphinxcontrib-bibtex: autopkgtest regression to be marked as

Bug#954866: marked as done (subversion build depends on cruft package swig3.0)

Your message dated Sat, 25 Apr 2020 14:18:45 + with message-id and subject line Bug#954866: fixed in subversion 1.13.0-4 has caused the Debian Bug report #954866, regarding subversion build depends on cruft package swig3.0 to be marked as done. This means that you claim that the problem has

Bug#958802: gap-float: please update for new GAP ABI

Package: gap-float Version: 0.9.1+ds-5 Severity: serious Dear Debian Science Maintainers, Please update gap-float for the new GAP ABI. 1) GAP 4.11.0 includes libgap7, libgap-dev as a normal Debian shared library package. 2) There is now an officially supported ABI for the GAP kernel. the

Bug#958798: cpufreqd: FTBFs on ppc64el

Source: cpufreqd Version: 2.4.2-2.2 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) cpufreqd failed to build on ppc64el: https://buildd.debian.org/status/fetch.php?pkg=cpufreqd=ppc64el=2.4.2-2.2%2Bb2=1587771408=0 Cheers --

Bug#937051: mininet: Python2 removal in sid/bullseye

Thanks, upstream claims that mininet is python3-compatible in master [1]. I'll try to make the package stop using python2. [1] https://github.com/mininet/mininet/issues/898 signature.asc Description: PGP signature

Bug#958446: nvidia-legacy-340xx-driver: Fails to build with kernel 5.6

I'm running into similar problems with backported Linux 5.6 support patches breaking Linux 4.19 on all other driver series ... I'm now testing my own backport, and if you are lucky, that shows me the solution for 340xx, too :-) Andreas

Processed: bug 958789 is forwarded to https://github.com/ingydotnet/module-manifest-skip-pm/issues/7 ...

Processing commands for cont...@bugs.debian.org: > forwarded 958789 > https://github.com/ingydotnet/module-manifest-skip-pm/issues/7 Bug #958789 [src:libmodule-manifest-skip-perl] libmodule-manifest-skip-perl: FTBFS and unusable: Can't locate object method "_install_subs" Set Bug

Bug#951925: flare-engine FTBFS: Could NOT find SDL2

Fwiw, https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/flare-engine.html seems to build successfully. I'm don't see this build failure on my local Sid system either. Maybe it got resolved after library changes in the meantime? -- mvh / best regards Hans Joachim Desserud

Bug#958789: libmodule-manifest-skip-perl: FTBFS and unusable: Can't locate object method "_install_subs"

Source: libmodule-manifest-skip-perl Version: 0.23-1 Severity: grave Tags: bullseye sid ftbfs This package fails to build from source on current sid/amd64. The whole module seems to be unusable. Looking at the test build history at

Bug#958788: blueman: broken dependency on iptables

Package: blueman Version: 2.1.2-1+b1 Severity: grave Justification: renders package unusable iptables 1.8.4-3 doesn't contain /sbin/iptables anymore, which breaks blueman. On startup, I get the following error: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.Failed: Traceback (most

Processed: Re: Bug#958467: libonig: set --enable-posix-api=yes again

Processing commands for cont...@bugs.debian.org: > severity 958467 grave Bug #958467 [libonig] libonig: set --enable-posix-api=yes again Severity set to 'grave' from 'important' > tags 958467 pending Bug #958467 [libonig] libonig: set --enable-posix-api=yes again Added tag(s) pending. > thanks

Processed: Re: Bug#956219: Error out when DISPLAY is unset

Processing commands for cont...@bugs.debian.org: > reopen 956219 Bug #956219 {Done: Alberto Garcia } [webkit2gtk] Error out when DISPLAY is unset 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug

Bug#958446: nvidia-legacy-340xx-driver: Fails to build with kernel 5.6

Package: nvidia-legacy-340xx-driver Version: 340.108-4 Followup-For: Bug #958446 I know the command I have to run, I just don't know the path to use there. And last time I patched the file manually, because it was only one file, I wrote that one line by hand :D If you show me the way, e.e. the