Bug#999619: Confirmed to be caused by tcmalloc that is default in 10.0

2021-11-17 Thread Christian Ehrhardt
Hi, I was able to confirm that rebuilding glusterfs without tcmalloc (now also on x86) fixes this issue. Debugging revealed that this is due to tgt late dlopening optional storage backends. So if you have some of them installed like packages tgt-rbd + tgt-glusterfs they will initialize late. Since

Processed: tagging 996234

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 996234 + unreproducible Bug #996234 [src:ruby-github-markup] ruby-github-markup: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Added tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#999823: liboqs: FBTFS: error: argument 1 of type ‘unsigned char[280]’ with mismatched bound [-Werror=array-parameter=]

2021-11-17 Thread Andrius Merkys
Hi Aurelien, Thanks for the report. On 2021-11-17 09:09, Aurelien Jarno wrote: Source: liboqs Version: 0.7.0.15.g9be13d21+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Not sure if "(but built successfully in the past)" is a

Processed: reassign 996296 to src:ruby-i18n

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 996296 src:ruby-i18n Bug #996296 [src:ruby-ice-cube] ruby-ice-cube: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:ArgumentError: Bug reassigned from package 'src:ruby-ice-cube' to 'src:ruby-i18n'. No longer marked as found in

Processed: found 996296 in ruby-i18n/1.18.10-1

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 996296 ruby-i18n/1.18.10-1 Bug #996296 [src:ruby-i18n] ruby-ice-cube: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:ArgumentError: The source ruby-i18n and version 1.18.10-1 do not appear to match any binary packages Marked as f

Bug#999619: Confirmed to be caused by tcmalloc that is default in 10.0

2021-11-17 Thread Paride Legovini
On Wed, 17 Nov 2021 Christian Ehrhardt wrote: Hi, I was able to confirm that rebuilding glusterfs without tcmalloc (now also on x86) fixes this issue. Debugging revealed that this is due to tgt late dlopening optional storage backends. So if you have some of them installed like packages tgt-rbd +

Processed: fixed 996296 in ruby-i18n/1.18.11-1

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 996296 ruby-i18n/1.18.11-1 Bug #996296 [src:ruby-i18n] ruby-ice-cube: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:ArgumentError: The source ruby-i18n and version 1.18.11-1 do not appear to match any binary packages Marked as f

Processed: closing 996296

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 996296 Bug #996296 [src:ruby-i18n] ruby-ice-cube: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:ArgumentError: Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 996296: https://b

Bug#996296: closing 996296

2021-11-17 Thread Cédric Boutillier
close 996296 thanks The upstream version 1.18.11 contains a fix for this bug, which is caused by the new major version 4 of Psych library in ruby3.0.

Processed: Bug#996348 marked as pending in ruby-process-daemon

2021-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996348 [src:ruby-process-daemon] ruby-process-daemon: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick Added tag(s) pending. -- 996348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996348 Debian Bug Trac

Bug#996348: marked as pending in ruby-process-daemon

2021-11-17 Thread Cédric Boutillier
Control: tag -1 pending Hello, Bug #996348 in ruby-process-daemon 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/ruby-team/ruby-process-daemon/-/commit/3137e1c

Processed: tagging 996234, severity of 996234 is important

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 996234 + moreinfo Bug #996234 [src:ruby-github-markup] ruby-github-markup: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Added tag(s) moreinfo. > severity 996234 important Bug #996234 [src:ruby-github-markup] ruby-github-markup: FTBFS wi

Bug#999619: marked as done (glusterfs breaks tgt autopkgtest: glfs not supported)

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 09:35:29 + with message-id and subject line Bug#999619: fixed in glusterfs 10.0-1.2 has caused the Debian Bug report #999619, regarding glusterfs breaks tgt autopkgtest: glfs not supported to be marked as done. This means that you claim that the problem has

Bug#996348: marked as done (ruby-process-daemon: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick)

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 09:48:48 + with message-id and subject line Bug#996348: fixed in ruby-process-daemon 1.0.1-3 has caused the Debian Bug report #996348, regarding ruby-process-daemon: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick to be

Bug#999813: util-linux: Upgrade from buster to bullseye fails because of util-linux

2021-11-17 Thread Chris Hofstaedtler
* tomas k [27 02:33]: > Package: util-linux > Version: 2.36.1-8 Hi tomas k, > I was upgrading 'buster' to 'bullseye' using simple instructions here: > https://linuxiac.com/upgrade-debian-10-buster-to-debian-11-bullseye/ I understand your system is now broken, possibly still in the middle of

Processed: fixed 993247 in 0.15.3-1

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 993247 0.15.3-1 Bug #993247 [src:gnunet] FTBFS in sid (libunistring) Marked as fixed in versions gnunet/0.15.3-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 993247: https://bugs.debian.org/cgi-bin/bugre

Processed: fixed 996349 in 4.0.6+ds-1, fixed 996122 in 4.0.6+ds-1

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 996349 4.0.6+ds-1 Bug #996349 [src:ruby-public-suffix] ruby-public-suffix: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1) Marked as fixed in versions ruby-public-suffix/4.0.

Processed: closing 996349

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 996349 4.0.6+ds-1 Bug #996349 [src:ruby-public-suffix] ruby-public-suffix: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1) Ignoring request to alter fixed versions of bug #99

Processed: closing 996122

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 996122 4.0.6+ds-1 Bug #996122 [src:ruby-public-suffix] ruby-addressable: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Ignoring request to alter fixed versions of bug #996122 to the same values previously set Bug #9

Bug#996122: closing 996122

2021-11-17 Thread Cédric Boutillier
close 996122 4.0.6+ds-1 thanks This bug has been closed by the upload of 4.0.6+ds-1.

Bug#996349: closing 996349

2021-11-17 Thread Cédric Boutillier
close 996349 4.0.6+ds-1 thanks This bug has been closed by the upload of 4.0.6+ds-1.

Bug#996125: reassign to ruby-rspec-rails or rails?

2021-11-17 Thread Cédric Boutillier
The actual part reporting the error seems to be: > An error occurred while loading ./spec/rails/integration/forms_spec.rb. > Failure/Error: require 'rspec/rails' > > ArgumentError: > wrong number of arguments (given 4, expected 3) > # > /usr/share/rubygems-integration/all/gems/activesupport-6.

Processed (with 1 error): forcibly merging 996377 996125

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 996377 996125 Bug #996377 [ruby-activesupport] ruby-rspec-rails: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Unable to merge bugs because: package of #996125 is 'src:ruby-arbre' not 'ruby-activesupport' Failed to f

Bug#998679: Firefox freezes

2021-11-17 Thread Michel Le Bihan
Hello, I experience freezes on Debian testing Bookworm (with mesa 21.2.5). They happen very often when I open a link in new tab or open a new tab, enter a URL and press Enter. The proposed workaround of setting `gfx.x11-egl.force-disabled` to `true` didn't solve the issue. Michel Le Bihan

Processed: found 996353 in ruby-rack/2.1.4-3

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 996353 ruby-rack/2.1.4-3 Bug #996353 [src:ruby-rack] ruby-rack: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Marked as found in versions ruby-rack/2.1.4-3. > thanks Stopping processing here. Please contact me if you need assistance. -

Bug#995879: marked as done (uninstallable due to dependency on ansible-core)

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 11:00:09 + with message-id and subject line Bug#995879: fixed in ansible-core 2.11.6-1 has caused the Debian Bug report #995879, regarding uninstallable due to dependency on ansible-core to be marked as done. This means that you claim that the problem has b

Processed: Re: gkrelluim: broken rebuild

2021-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 bullseye bookworm sid patch Bug #999353 [gkrelluim] gkrelluim: broken rebuild Added tag(s) bookworm, patch, bullseye, and sid. -- 999353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999353 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

Bug#999353: gkrelluim: broken rebuild

2021-11-17 Thread Andreas Beckmann
Control: tag -1 bullseye bookworm sid patch On Wed, 10 Nov 2021 13:03:16 +0100 mwgam...@gmail.com wrote: Package: gkrelluim Version: 0.3.1-7+b2 The latest NMU made gkrelluim completely unusbale. It seems to be missing all of its dependencies and doesn't load at all. debdiff says: Control

Bug#993301: prototypejs: FTBFS

2021-11-17 Thread Andreas Beckmann
Control: tag -1 moreinfo On Mon, 30 Aug 2021 12:23:22 + "=?utf-8?q?Bastien_Roucari=C3=A8s?=" wrote: Source: prototypejs Severity: serious Justification: 4 Dear Maintainer, The source is https://github.com/prototypejs/prototype/tree/master and need rake for building... So FTBFS I can r

Processed: Re: prototypejs: FTBFS

2021-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo Bug #993301 [src:prototypejs] prototypejs: FTBFS Added tag(s) moreinfo. -- 993301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: tagging 999817, tagging 998345

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 999817 + bookworm sid Bug #999817 [libstdc++-arm-none-eabi] libstdc++-arm-none-eabi build-depends on removed package. Added tag(s) sid and bookworm. > tags 998345 + bookworm sid Bug #998345 {Done: Jonas Smedegaard } [librust-quickcheck+env-

Bug#999823: liboqs: FBTFS: error: argument 1 of type ‘unsigned char[280]’ with mismatched bound [-Werror=array-parameter=]

2021-11-17 Thread Aurelien Jarno
control: severity -1 important On 2021-11-17 10:52, Andrius Merkys wrote: > Hi Aurelien, > > Thanks for the report. > > On 2021-11-17 09:09, Aurelien Jarno wrote: > > Source: liboqs > > Version: 0.7.0.15.g9be13d21+dfsg-1 > > Severity: serious > > Tags: ftbfs > > Justification: fails to build fro

Processed: Re: Bug#999823: liboqs: FBTFS: error: argument 1 of type ‘unsigned char[280]’ with mismatched bound [-Werror=array-parameter=]

2021-11-17 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #999823 [src:liboqs] liboqs: FBTFS: error: argument 1 of type ‘unsigned char[280]’ with mismatched bound [-Werror=array-parameter=] Severity set to 'important' from 'serious' -- 999823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=99

Bug#998224: hplip: HPLIP incorrectly links to obsolete or missing libhpdiscovery.so

2021-11-17 Thread Andreas Beckmann
Control: severity -1 normal On Thu, 11 Nov 2021 09:53:08 +1100 Troy Rollo wrote: I suspect reproducing will not be straight-forward as it requires a system that still has the version of hplip from buster, but has otherwise been upgraded to bullseye. I cannot spare the time right now to set u

Processed: Re: hplip: HPLIP incorrectly links to obsolete or missing libhpdiscovery.so

2021-11-17 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #998224 [hplip] hplip: HPLIP incorrectly links to obsolete or missing libhpdiscovery.so Severity set to 'normal' from 'grave' -- 998224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998224 Debian Bug Tracking System Contact ow...@bugs.d

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

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 12:33:32 + with message-id and subject line Bug#997153: fixed in asyncpg 0.25.0-1 has caused the Debian Bug report #997153, regarding asyncpg: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13 to be mar

Processed: Bug#999818 marked as pending in node-regenerate-unicode-properties

2021-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #999818 [node-regenerate-unicode-properties] node-regenerate-unicode-properties build-depends on removed package. Ignoring request to alter tags of bug #999818 to the same tags previously set -- 999818: https://bugs.debian.org/cgi-bin/bugreport.

Bug#999818: marked as pending in node-regenerate-unicode-properties

2021-11-17 Thread Yadd
Control: tag -1 pending Hello, Bug #999818 in node-regenerate-unicode-properties 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/js-team/node-regenerate-unicod

Bug#999818: marked as pending in node-regenerate-unicode-properties

2021-11-17 Thread Yadd
Control: tag -1 pending Hello, Bug #999818 in node-regenerate-unicode-properties 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/js-team/node-regenerate-unicod

Processed: Bug#999818 marked as pending in node-regenerate-unicode-properties

2021-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #999818 [node-regenerate-unicode-properties] node-regenerate-unicode-properties build-depends on removed package. Added tag(s) pending. -- 999818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999818 Debian Bug Tracking System Contact ow...@

Bug#999818: marked as done (node-regenerate-unicode-properties build-depends on removed package.)

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 13:03:59 + with message-id and subject line Bug#999818: fixed in node-regenerate-unicode-properties 9.0.0+ds-1 has caused the Debian Bug report #999818, regarding node-regenerate-unicode-properties build-depends on removed package. to be marked as done. Th

Processed: block 996125 with 996377

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 996125 with 996377 Bug #996125 [src:ruby-arbre] ruby-arbre: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: 996125 was not blocked by any bugs. 996125 was not blocking any bugs. Added blocking bug(s) of 996125: 996377 > than

Processed: reassign 992419 to src:u-boot, tagging 996353, tagging 998772, tagging 998541, tagging 999429 ...

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 992419 src:u-boot 2021.07+dfsg-1 Bug #992419 [u-boot-sifive] U-Boot using wrong memory type for device-trees. Warning: Unknown package 'u-boot-sifive' Bug reassigned from package 'u-boot-sifive' to 'src:u-boot'. No longer marked as found

Processed: block 996125 with 996147

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 996125 with 996147 Bug #996125 [src:ruby-arbre] ruby-arbre: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: 996125 was blocked by: 996377 996125 was not blocking any bugs. Added blocking bug(s) of 996125: 996147 > thanks Sto

Bug#999353: marked as done (gkrelluim: broken rebuild)

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 14:49:06 + with message-id and subject line Bug#999353: fixed in gkrelluim 0.3.1-8 has caused the Debian Bug report #999353, regarding gkrelluim: broken rebuild to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: ripperx: diff for NMU version 2.8.0-2.1

2021-11-17 Thread Debian Bug Tracking System
Processing control commands: > tags 978893 + patch Bug #978893 [src:ripperx] ripperx: ftbfs with autoconf 2.70 Added tag(s) patch. > tags 978893 + pending Bug #978893 [src:ripperx] ripperx: ftbfs with autoconf 2.70 Added tag(s) pending. -- 978893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bu

Bug#998261: marked as done (jsbundle-web-interfaces: autopkgtest regression: node: command not found)

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 16:03:55 + with message-id and subject line Bug#998261: fixed in jsbundle-web-interfaces 1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-3 has caused the Debian Bug report #998261, regarding jsbundle-web-interfaces: autopkgtest regression: node: command not found to be

Bug#986770: marked as done (shapetools: FTBFS with glibc 2.32)

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 17:21:18 + with message-id and subject line Bug#986770: fixed in shapetools 1.4pl6-15 has caused the Debian Bug report #986770, regarding shapetools: FTBFS with glibc 2.32 to be marked as done. This means that you claim that the problem has been dealt with.

Processed: tagging 986487

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 986487 + pending Bug #986487 [caftools] caftools: FTBFS with glibc >= 2.32 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 986487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=98648

Processed: your mail

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 999751 ftbfs Bug #999751 [src:di-netboot-assistant] di-netboot-assistant: please drop shellcheck autopkgtest Added tag(s) ftbfs. > -- Stopping processing here. Please contact me if you need assistance. -- 999751: https://bugs.debian.org/cg

Bug#908017: network-manager-iodine: diff for NMU version 1.2.0-3.1

2021-11-17 Thread Boyuan Yang
Control: tags 908017 + pending X-Debbugs-CC: a...@sigxcpu.org a...@debian.org Dear maintainer, I've prepared an NMU for network-manager-iodine (versioned as 1.2.0-3.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. I believe the correct patch should be htt

Processed: network-manager-iodine: diff for NMU version 1.2.0-3.1

2021-11-17 Thread Debian Bug Tracking System
Processing control commands: > tags 908017 + pending Bug #908017 [src:network-manager-iodine] network-manager-iodine FTBFS with glib 2.58 Added tag(s) pending. -- 908017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908017 Debian Bug Tracking System Contact ow...@bugs.debian.org with probl

Bug#999817: marked as done (libstdc++-arm-none-eabi build-depends on removed package.)

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 17:49:02 + with message-id and subject line Bug#999817: fixed in gcc-arm-none-eabi 15:10.3-2021.07-4 has caused the Debian Bug report #999817, regarding libstdc++-arm-none-eabi build-depends on removed package. to be marked as done. This means that you clai

Processed: reassign bug to the package that closed it

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # The version tracking systems get confused if a package is closed by a > package other than the one it's filed against > reassign 999817 gcc-arm-none-eabi Bug #999817 {Done: Keith Packard } [libstdc++-arm-none-eabi] libstdc++-arm-none-eabi buil

Bug#999853: src:boost1.74: fails to migrate to testing for too long: FTBFS on armhf

2021-11-17 Thread Paul Gevers
Source: boost1.74 Version: 1.74.0-9 Severity: serious Control: close -1 1.74.0-12 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 6

Processed: src:boost1.74: fails to migrate to testing for too long: FTBFS on armhf

2021-11-17 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.74.0-12 Bug #999853 [src:boost1.74] src:boost1.74: fails to migrate to testing for too long: FTBFS on armhf Marked as fixed in versions boost1.74/1.74.0-12. Bug #999853 [src:boost1.74] src:boost1.74: fails to migrate to testing for too long: FTBFS on arm

Bug#998608: marked as done (canl-java: FTBFS: [ERROR] /<>/src/main/java/eu/emi/security/authn/x509/helpers/trust/OpensslTruststoreHelper.java:[80,17]

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 18:19:07 + with message-id and subject line Bug#998608: fixed in canl-java 2.7.0-2 has caused the Debian Bug report #998608, regarding canl-java: FTBFS: [ERROR] /<>/src/main/java/eu/emi/security/authn/x509/helpers/trust/OpensslTruststoreHelper.java:[80,17]

Bug#978836: heimdal: ftbfs with autoconf 2.70

2021-11-17 Thread Christoph Reiter
There is an upstream fix available here: https://github.com/heimdal/heimdal/pull/771

Bug#996589: marked as done (cloudcompare FTBFS on !amd64)

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 19:18:39 + with message-id and subject line Bug#996589: fixed in cloudcompare 2.11.3-4 has caused the Debian Bug report #996589, regarding cloudcompare FTBFS on !amd64 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#999856: cheetah with python 3.10 as supported version

2021-11-17 Thread Adrian Bunk
Source: cheetah Version: 3.2.6-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=cheetah&ver=3.2.6-2%2Bb1 ... == ERROR: test_import_bootlocale (Cheetah.Tests.ImportHooks.ImportHooksTest) --

Bug#999857: mod-wsgi FTBFS with python 3.10 as supported version

2021-11-17 Thread Adrian Bunk
Source: mod-wsgi Version: 4.7.1-3 Severity: serious Tags: ftbfs bookworm sid Forwarded: https://github.com/GrahamDumpleton/mod_wsgi/pull/688 https://buildd.debian.org/status/logs.php?pkg=mod-wsgi&ver=4.7.1-3%2Bb2 ... In file included from src/server/mod_wsgi.c:22: src/server/wsgi_python.h:44:10:

Bug#984208: marked as done (libsass: ftbfs with GCC-11)

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 19:51:09 + with message-id and subject line Bug#984208: fixed in libsass 3.6.5+2021-2 has caused the Debian Bug report #984208, regarding libsass: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Bug#996147 marked as pending in ruby-capybara

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

Bug#996147: marked as pending in ruby-capybara

2021-11-17 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #996147 in ruby-capybara 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/ruby-team/ruby-capybara/-/commit/d8c2ed1980c13f17e9d

Processed: Bug#999819 marked as pending in node-regexpu-core

2021-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #999819 [node-regexpu-core] node-regexpu-core build-depends on removed package. Added tag(s) pending. -- 999819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#999819: marked as pending in node-regexpu-core

2021-11-17 Thread Yadd
Control: tag -1 pending Hello, Bug #999819 in node-regexpu-core 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/js-team/node-regexpu-core/-/commit/ee0c32fa5b61d

Processed: Bug#999819 marked as pending in node-regexpu-core

2021-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #999819 [node-regexpu-core] node-regexpu-core build-depends on removed package. Ignoring request to alter tags of bug #999819 to the same tags previously set -- 999819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999819 Debian Bug Tracking

Bug#999819: marked as pending in node-regexpu-core

2021-11-17 Thread Yadd
Control: tag -1 pending Hello, Bug #999819 in node-regexpu-core 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/js-team/node-regexpu-core/-/commit/ee0c32fa5b61d

Bug#999860: python3-cylc fails to install

2021-11-17 Thread Adrian Bunk
Package: python3-cylc Version: 8.0~b3-1 Severity: serious https://piuparts.debian.org/sid/fail/python3-cylc_8.0~b3-1.log ... Setting up python3-cylc (8.0~b3-1) ... File "/usr/lib/python3/dist-packages/cylc/flow/batch_sys_handlers/at.py", line 1 <<< HEAD:cylc/flow/batch_sys_handle

Bug#978836: marked as done (heimdal: ftbfs with autoconf 2.70)

2021-11-17 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 07:36:24 +1100 with message-id <87sfvuzfhz@canidae.wired.pri> and subject line Re: Bug#978836: heimdal: ftbfs with autoconf 2.70 has caused the Debian Bug report #978836, regarding heimdal: ftbfs with autoconf 2.70 to be marked as done. This means that you c

Processed: teach the bts the right meta data

2021-11-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 999619 src:glusterfs 10.0-1 Bug #999619 {Done: Christian Ehrhardt } [src:glusterfs, src:tgt] glusterfs breaks tgt autopkgtest: glfs not supported Bug reassigned from package 'src:glusterfs, src:tgt' to 'src:glusterfs'. No longer marked a

Processed: Bug#996366 marked as pending in ruby-regexp-parser

2021-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996366 [src:ruby-regexp-parser] ruby-regexp-parser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: (min..max).tap { |r| r.define_singleton_method(:minmax) { [min, max] } } Added tag(s) pending. -- 996366: https://bugs.d

Bug#996366: marked as pending in ruby-regexp-parser

2021-11-17 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #996366 in ruby-regexp-parser 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/ruby-team/ruby-regexp-parser/-/commit/82a4d330a

Bug#999862: sso.debian.org: SSO no longer seems to work

2021-11-17 Thread Julian Gilbey
Package: sso.debian.org Severity: serious I'm trying to log in to tracker.debian.org. I've manually created a fresh certificate and loaded it into both Firefox (94.0-1) and Chrome (from Google), I visit tracker.debian.org but it does not recognise it at all. I also tried curl, as described on th

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

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 21:06:19 + with message-id and subject line Bug#996147: fixed in ruby-capybara 3.36.0+ds-1 has caused the Debian Bug report #996147, regarding ruby-capybara: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: to be marked as done. This means

Bug#996366: marked as done (ruby-regexp-parser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: (min..max).tap { |r| r.define_singleton_method(:minmax) { [min, max] } })

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 21:06:25 + with message-id and subject line Bug#996366: fixed in ruby-regexp-parser 1.7.1-2 has caused the Debian Bug report #996366, regarding ruby-regexp-parser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: (min..max).tap { |r| r

Bug#999819: marked as done (node-regexpu-core build-depends on removed package.)

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 21:05:51 + with message-id and subject line Bug#999819: fixed in node-regexpu-core 4.8.0-1 has caused the Debian Bug report #999819, regarding node-regexpu-core build-depends on removed package. to be marked as done. This means that you claim that the probl

Processed: Bug#996353 marked as pending in ruby-rack

2021-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996353 [src:ruby-rack] ruby-rack: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Added tag(s) pending. -- 996353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#996353: marked as pending in ruby-rack

2021-11-17 Thread Cédric Boutillier
Control: tag -1 pending Hello, Bug #996353 in ruby-rack 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/ruby-team/ruby-rack/-/commit/a8c225e28999038432249af1b24

Bug#996353: marked as done (ruby-rack: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.)

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 21:20:45 + with message-id and subject line Bug#996353: fixed in ruby-rack 2.1.4-4 has caused the Debian Bug report #996353, regarding ruby-rack: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. to be marked as done. This means that you claim that the prob

Processed: Bug#984006 marked as pending in caja-eiciel

2021-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #984006 [src:caja-eiciel] caja-eiciel: ftbfs with GCC-11 Added tag(s) pending. -- 984006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#984006: marked as pending in caja-eiciel

2021-11-17 Thread Mike Gabriel
Control: tag -1 pending Hello, Bug #984006 in caja-eiciel 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-mate-team/caja-eiciel/-/commit/2166da9391291b58

Bug#984006: marked as done (caja-eiciel: ftbfs with GCC-11)

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 21:33:43 + with message-id and subject line Bug#984006: fixed in caja-eiciel 1.20.1-3 has caused the Debian Bug report #984006, regarding caja-eiciel: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#999764: marked as done (gcc-12: file conflicts with gcc-11 due to missing Breaks+Replaces or renaming)

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 21:34:04 + with message-id and subject line Bug#999764: fixed in gcc-12 12-2027-1 has caused the Debian Bug report #999764, regarding gcc-12: file conflicts with gcc-11 due to missing Breaks+Replaces or renaming to be marked as done. This means that

Bug#998575: marked as done (bind-dyndb-ldap: FTBFS: build-dependency not installable: bind9-libs (= 1:9.16.21-1))

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 21:48:39 + with message-id and subject line Bug#998575: fixed in bind-dyndb-ldap 11.9-4 has caused the Debian Bug report #998575, regarding bind-dyndb-ldap: FTBFS: build-dependency not installable: bind9-libs (= 1:9.16.21-1) to be marked as done. This mean

Bug#995220: Components to add to ts-node

2021-11-17 Thread Yadd
$ pkgjs-depends ts-node DEPENDENCIES: node-acorn (acorn, acorn-walk) node-arg (arg) node-create-require (create-require) node-diff (diff) node-make-error (make-error) node-yn (yn) MISSING: ts-node └── @cspotcode/source-map-support (0.7.0) └── @cspotcode/source-map-consumer (0.8.0

Bug#996523: marked as pending in ruby-websocket

2021-11-17 Thread Cédric Boutillier
Control: tag -1 pending Hello, Bug #996523 in ruby-websocket 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/ruby-team/ruby-websocket/-/commit/5c6191644cb3e7b4a

Processed: Bug#996523 marked as pending in ruby-websocket

2021-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996523 [src:ruby-websocket] ruby-websocket: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick Added tag(s) pending. -- 996523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996523 Debian Bug Tracking Syste

Bug#996523: marked as done (ruby-websocket: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick)

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 23:18:40 + with message-id and subject line Bug#996523: fixed in ruby-websocket 1.2.9-2 has caused the Debian Bug report #996523, regarding ruby-websocket: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick to be marked as

Bug#996871: wmnet: crashes on launch

2021-11-17 Thread Adrian Bunk
On Tue, Oct 19, 2021 at 07:48:57PM -0700, Thomas Groman wrote: > Package: wmnet > Version: 1.06-1+b2 > Severity: grave > Justification: renders package unusable > > Launching wmnet causes it to crash on launch with the following output: > $ wmnet > wmnet: using devstats driver to monitor eth0 > X

Processed: Bug#996518 marked as pending in ruby-typhoeus

2021-11-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996518 [src:ruby-typhoeus] ruby-typhoeus: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: require 'rack/handler/webrick' Added tag(s) pending. -- 996518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996518 Debian

Bug#996518: marked as pending in ruby-typhoeus

2021-11-17 Thread Cédric Boutillier
Control: tag -1 pending Hello, Bug #996518 in ruby-typhoeus 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/ruby-team/ruby-typhoeus/-/commit/2c84dedfbe670b56f27

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

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 23:57:38 + with message-id and subject line Bug#997102: fixed in ktexteditor 5.88.0-1 has caused the Debian Bug report #997102, regarding ktexteditor: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output b

Bug#996518: marked as done (ruby-typhoeus: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: require 'rack/handler/webrick')

2021-11-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Nov 2021 23:58:19 + with message-id and subject line Bug#996518: fixed in ruby-typhoeus 1.4.0-2 has caused the Debian Bug report #996518, regarding ruby-typhoeus: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: require 'rack/handler/webrick'[0

Bug#983996: blist: ftbfs with GCC-11

2021-11-17 Thread Steve Langasek
Package: blist Version: 1.3.6-7 Followup-For: Bug #983996 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch Control: tags -1 patch Hello, I've been able to get blist to build with gcc-11 in Ubuntu by reducing the optimization level from -O2 (default) to -O1. Please s

Processed: Re: blist: ftbfs with GCC-11

2021-11-17 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #983996 [src:blist] blist: ftbfs with GCC-11 Added tag(s) patch. -- 983996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#996386: other error with mechanize 2.7.7-3

2021-11-17 Thread Cédric Boutillier
The error in the log comes from ruby-mechanize < 2.7.7-3 not depending on ruby-webrick. Now, there are 7 test failures of the following kind: > 1) ShamRack mounted Rack application can be accessed using open-uri > Failure/Error: response = open("http://www.greetings.com";) > > Errno::E

Bug#997064: marked as done (emscripten: FTBFS: BlockingIOError: [Errno 11] write could not complete without blocking)

2021-11-17 Thread Debian Bug Tracking System
Your message dated Thu, 18 Nov 2021 01:18:50 + with message-id and subject line Bug#997064: fixed in emscripten 2.0.26~dfsg-5 has caused the Debian Bug report #997064, regarding emscripten: FTBFS: BlockingIOError: [Errno 11] write could not complete without blocking to be marked as done. Thi

Bug#999862: sso.debian.org: SSO no longer seems to work

2021-11-17 Thread Paul Wise
On Wed, 2021-11-17 at 20:55 +, Julian Gilbey wrote: > So it would seem that sso.debian.org may no longer be functional, > which prevents me from logging into tracker.debian.org. My current certificate still works on tracker.d.o and the sso test URL. I created a new cert and imported it into

Bug#999873: python3-eventlet: Eventlet greendns incompatible with dnspython 2.1.0

2021-11-17 Thread Scott Kitterman
Package: python3-eventlet Version: 0.30.2-4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, Once again, eventlet is incompatible with dnspython and needs fixing. The specific test that is failing is tests.socket_test.

  1   2   >