Bug#984125: marked as done (flamp: ftbfs with GCC-11)

Your message dated Wed, 13 Oct 2021 04:48:23 + with message-id and subject line Bug#984125: fixed in flamp 2.2.07-1 has caused the Debian Bug report #984125, regarding flamp: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: tagging 994863

Processing commands for cont...@bugs.debian.org: > tags 994863 + pending Bug #994863 [python-cleo-doc] python-cleo-doc: ships /usr/share/doc-base/python-six-doc Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 994863:

Bug#984078: vc-dev: please upload to unstable

Package: vc-dev Version: 1.4.2-1 Followup-For: Bug #984078 Dear all with gcc11 being the default in sid now, please upload vc-dev to unstable, otherwise the FTBFS for other packages continue. Thanks Norbert -- System Information: Debian Release: bookworm/sid APT prefers unstable APT

Bug#995594: libhdf5[-openmpi]-dev: missing Depends: libcurl-dev

Drew Parsons a écrit le 04/10/2021 à 21:14 : On 2021-10-03 12:15, Gilles Filippini wrote: Drew Parsons a écrit le 02/10/2021 à 22:17 : ... Since h5pcc and h5cc invoke -lcurl, libhdf5-openmpi-dev, libhdf5-dev (and probably libhdf5-mpich-dev also) should declare Depends: libcurl-dev ... I

Bug#996324: ruby-netcdf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Segmentation fault at 0x0000000000000034

Source: ruby-netcdf Version: 0.7.2-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-netcdf was found to fail to build in that

Bug#996323: ruby-mono-logger: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 0..1)

Source: ruby-mono-logger Version: 1.1.0-3.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-mono-logger was found to fail to build in

Bug#996322: ruby-mmap2: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: :85:in `require': cannot load such file -- mmap (LoadE

Source: ruby-mmap2 Version: 2.2.7-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-mmap2 was found to fail to build in that

Bug#996321: ruby-mixlib-install: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick

Source: ruby-mixlib-install Version: 3.11.7-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-mixlib-install was found to fail to

Bug#996320: ruby-minitest-excludes: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.

Source: ruby-minitest-excludes Version: 2.0.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-minitest-excludes was found to fail to

Bug#996319: ruby-mini-magick: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(described_class.new(output_path.to_s)).to be_valid

Source: ruby-mini-magick Version: 4.10.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-mini-magick was found to fail to build in

Bug#996318: ruby-messagebus-api: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: expected no Exception, got # with backtrace:

Source: ruby-messagebus-api Version: 3.0.7+git.20130130.97b34ece.REALLY.1.0.3-2.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild,

Bug#996278: marked as done (open3d: autopkgtest needs update for new version of gcc-defaults: output on stderr)

Your message dated Tue, 12 Oct 2021 22:48:53 + with message-id and subject line Bug#996278: fixed in open3d 0.9.0+ds-7 has caused the Debian Bug report #996278, regarding open3d: autopkgtest needs update for new version of gcc-defaults: output on stderr to be marked as done. This means that

Bug#996317: ruby-memory-profiler: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.

Source: ruby-memory-profiler Version: 0.9.14-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-memory-profiler was found to fail to

Bug#996316: ruby-mechanize: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:311:in `to_specs': Could not find 'webrick' (~> 1.6) among 107 total gem(

Source: ruby-mechanize Version: 2.7.7-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-mechanize was found to fail to build in that

Bug#996315: ruby-listen: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error:

Source: ruby-listen Version: 3.2.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-listen was found to fail to build in that

Bug#996314: ruby-liquid: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 1, expected 0)

Source: ruby-liquid Version: 4.0.3-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-liquid was found to fail to build in that

Bug#996313: ruby-libvirt: FTBFS with ruby3.0: common.c:27:10: fatal error: st.h: No such file or directory

Source: ruby-libvirt Version: 0.7.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-libvirt was found to fail to build in that

Bug#996312: ruby-librarian: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc object without a block

Source: ruby-librarian Version: 0.6.4-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-librarian was found to fail to build in that

Bug#996311: ruby-lapack: FTBFS: ERROR: Test "ruby2.7" failed.

Source: ruby-lapack Version: 1.8.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-lapack was found to fail to build in that

Bug#996310: ruby-kyotocabinet: FTBFS with ruby3.0: stdalign.h:93:1: error: template with C linkage

Source: ruby-kyotocabinet Version: 1.33-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-kyotocabinet was found to fail to build in

Bug#996308: ruby-kitchen-salt: FTBFS: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Could not find 'thor' (~> 0.

Source: ruby-kitchen-salt Version: 0.4.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-kitchen-salt was found to fail to build in

Bug#996309: ruby-kubeclient: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: /usr/lib/ruby/vendor_ruby/recursive_open_struct.rb:84:in `alias_method': undefined method `modifiable' for class `Recursi

Source: ruby-kubeclient Version: 4.9.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-kubeclient was found to fail to build in that

Bug#996307: ruby-kitchen-docker: FTBFS: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Could not find 'thor' (~>

Source: ruby-kitchen-docker Version: 2.7.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-kitchen-docker was found to fail to build

Bug#996306: ruby-jsonpath: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: character '|' not supported in query.

Source: ruby-jsonpath Version: 1.0.5-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-jsonpath was found to fail to build in that

Bug#996305: ruby-json: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: NoMethodError: undefined method `assert_separately'

Source: ruby-json Version: 2.5.1+dfsg-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-json was found to fail to build in that

Bug#996304: ruby-json-schema: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Errno::ENOENT: No such file or directory @ rb_sysopen - http://foo.bar/

Source: ruby-json-schema Version: 2.8.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-json-schema was found to fail to build in

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

Source: ruby-json-jwt Version: 1.11.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-json-jwt was found to fail to build in that

Bug#996302: ruby-joiner: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: require 'bundler/setup'

Source: ruby-joiner Version: 0.5.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-joiner was found to fail to build in that

Bug#996301: ruby-jbuilder: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.

Source: ruby-jbuilder Version: 2.10.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-jbuilder was found to fail to build in that

Bug#996300: ruby-jaeger-client: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:

Source: ruby-jaeger-client Version: 1.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-jaeger-client was found to fail to build

Bug#996299: ruby-invisible-captcha: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: require 'bundler/setup' # Set up gems listed in the Gemfile.

Source: ruby-invisible-captcha Version: 1.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-invisible-captcha was found to fail to

Bug#996298: ruby-influxdb: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: specify { expect(conf.proxy_port).to eq(8080) }

Source: ruby-influxdb Version: 0.8.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-influxdb was found to fail to build in that

Bug#996297: ruby-ice-nine: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: expect(subject.end).to be_frozen

Source: ruby-ice-nine Version: 0.11.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-ice-nine was found to fail to build in that

Processed: bug 994257 is forwarded to https://github.com/django-ldapdb/django-ldapdb/pull/202

Processing commands for cont...@bugs.debian.org: > forwarded 994257 https://github.com/django-ldapdb/django-ldapdb/pull/202 Bug #994257 [src:python-django, src:django-ldapdb] python-django breaks django-ldapdb autopkgtest: 'Field' object has no attribute 'attname' Set Bug forwarded-to-address to

Bug#996296: ruby-ice-cube: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:

Source: ruby-ice-cube Version: 0.16.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-ice-cube was found to fail to build in that

Bug#996295: ruby-i18n-inflector-rails: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:

Source: ruby-i18n-inflector-rails Version: 1.0.7-4.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-i18n-inflector-rails was found to

Bug#996294: ruby-httpclient: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.

Source: ruby-httpclient Version: 2.8.3-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-httpclient was found to fail to build in that

Bug#996293: ruby-httparty: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:

Source: ruby-httparty Version: 0.18.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-httparty was found to fail to build in that

Bug#996292: ruby-http: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick

Source: ruby-http Version: 4.4.1-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-http was found to fail to build in that situation.

Bug#996291: ruby-hdfeos5: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: :85:in `require': /<>/debian/ruby-hdfeo

Source: ruby-hdfeos5 Version: 1.2-10 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-hdfeos5 was found to fail to build in that

Bug#959927: marked as done (birdtray: Uninstallable on Debian Buster)

Your message dated Tue, 12 Oct 2021 23:38:31 +0200 with message-id and subject line gone from Buster has caused the Debian Bug report #959927, regarding birdtray: Uninstallable on Debian Buster to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#984009: marked as done (cheesecutter: ftbfs with GCC-11)

Your message dated Tue, 12 Oct 2021 21:33:42 + with message-id and subject line Bug#984009: fixed in cheesecutter 2.9+git20211011-1 has caused the Debian Bug report #984009, regarding cheesecutter: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been

Bug#994561: marked as done (cheesecutter ftbfs with gdc-11)

Your message dated Tue, 12 Oct 2021 21:33:42 + with message-id and subject line Bug#994561: fixed in cheesecutter 2.9+git20211011-1 has caused the Debian Bug report #994561, regarding cheesecutter ftbfs with gdc-11 to be marked as done. This means that you claim that the problem has been

Processed: tagging 995779, tagging 995780, tagging 995781, tagging 995783

Processing commands for cont...@bugs.debian.org: > tags 995779 + sid bookworm Bug #995779 [mailman3] autopkgtest fails with sqlalchemy 1.4.23+ds1 Added tag(s) bookworm and sid. > tags 995780 + sid bookworm Bug #995780 [src:python-agate-sql] python-agate-sql autopkgtest fails with SQLAlchemy

Processed: tagging 995437, tagging 995480, tagging 995597, tagging 995600, tagging 995603, tagging 995623 ...

Processing commands for cont...@bugs.debian.org: > tags 995437 + sid bookworm Bug #995437 {Done: Laszlo Boszormenyi (GCS) } [src:vips] vips: FTBFS Added tag(s) sid and bookworm. > tags 995480 + sid bookworm Bug #995480 [src:ytree] FTBFS: error: format not a string literal and no format

Bug#984257: marked as done (nted: ftbfs with GCC-11)

Your message dated Tue, 12 Oct 2021 21:05:47 + with message-id and subject line Bug#984257: fixed in nted 1.10.18-13 has caused the Debian Bug report #984257, regarding nted: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#970880: [Pkg-freeipa-devel] Bug#970880: Bug#970880: Bug#970880: Bug#970880: Bug#970880: freeipa-server: FreeIPA server installation fails with Certificate issuance failed (CA_REJECTED)

On Tue, Oct 12, 2021 at 2:17 PM Timo Aaltonen wrote: > > On 12.10.2021 20.48, Spencer Olson wrote: > > On Tue, Oct 12, 2021 at 9:53 AM Spencer Olson wrote: > >> > >> On Sun, Oct 10, 2021 at 12:58 PM Timo Aaltonen wrote: > >>> > > > Maybe the CI will finish before I can get back

Bug#984099: marked as done (libebml: ftbfs with GCC-11)

Your message dated Tue, 12 Oct 2021 20:49:06 + with message-id and subject line Bug#984099: fixed in libebml 1.4.2-2 has caused the Debian Bug report #984099, regarding libebml: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#984024: marked as done (connectome-workbench: ftbfs with GCC-11)

Your message dated Tue, 12 Oct 2021 20:48:37 + with message-id and subject line Bug#984024: fixed in connectome-workbench 1.5.0-2 has caused the Debian Bug report #984024, regarding connectome-workbench: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has

Bug#984361: marked as done (tcm: ftbfs with GCC-11)

Your message dated Tue, 12 Oct 2021 20:27:53 + with message-id and subject line Bug#984361: fixed in tcm 2.20+TSQD-7 has caused the Debian Bug report #984361, regarding tcm: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#995737: marked as done (pytest breaks pytest-doctestplus autopkgtest: pytest.PytestAssertRewriteWarning: Module already imported so cannot be rewritten: pytest_doctestplus)

Your message dated Tue, 12 Oct 2021 20:22:47 + with message-id and subject line Bug#995737: fixed in pytest-doctestplus 0.11.0-2 has caused the Debian Bug report #995737, regarding pytest breaks pytest-doctestplus autopkgtest: pytest.PytestAssertRewriteWarning: Module already imported so

Processed: Bug#984099 marked as pending in libebml

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

Bug#984099: marked as pending in libebml

Control: tag -1 pending Hello, Bug #984099 in libebml 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#993184: Please switch upstream

Dear maintainer, I suggest to switch upstream to https://github.com/fer-moreira/floating-dock which is a fork of https://github.com/micheleg/dash-to-dock/. Floating-dock works perfectly fine for me in my bookworm installation. Cheers, Sven -- GPG Fingerprint 3DF5 E8AA 43FC 9FDF D086 F195 ADF5

Processed: simde: autopkgtest needs update for new version of gcc-defaults: x86/sse2/native/c(pp|) failed

Processing control commands: > affects -1 src:gcc-defaults Bug #996281 [src:simde] simde: autopkgtest needs update for new version of gcc-defaults: x86/sse2/native/c(pp|) failed Added indication that 996281 affects src:gcc-defaults -- 996281:

Bug#996281: simde: autopkgtest needs update for new version of gcc-defaults: x86/sse2/native/c(pp|) failed

Source: simde Version: 0.7.2-4 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:gcc-defaults [X-Debbugs-CC: debian...@lists.debian.org, gcc-defau...@packages.debian.org] Dear maintainer(s), With a recent upload of gcc-defaults

Bug#970880: [Pkg-freeipa-devel] Bug#970880: Bug#970880: Bug#970880: Bug#970880: Bug#970880: freeipa-server: FreeIPA server installation fails with Certificate issuance failed (CA_REJECTED)

On 12.10.2021 20.48, Spencer Olson wrote: On Tue, Oct 12, 2021 at 9:53 AM Spencer Olson wrote: On Sun, Oct 10, 2021 at 12:58 PM Timo Aaltonen wrote: Maybe the CI will finish before I can get back to my testing. And it did, this error is fixed now :) But it fails later on, so there's

Processed: seqan3: autopkgtest needs update for new version of gcc-defaults

Processing control commands: > affects -1 src:gcc-defaults Bug #996280 [src:seqan3] seqan3: autopkgtest needs update for new version of gcc-defaults Added indication that 996280 affects src:gcc-defaults -- 996280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996280 Debian Bug Tracking

Bug#996280: seqan3: autopkgtest needs update for new version of gcc-defaults

Source: seqan3 Version: 3.0.2+ds-9 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:gcc-defaults [X-Debbugs-CC: debian...@lists.debian.org, gcc-defau...@packages.debian.org] Dear maintainer(s), With a recent upload of

Bug#996279: xmds2: autopkgtest needs update for new version of gcc-defaults: 5 tests fail to build

Source: xmds2 Version: 3.0.0+dfsg-5 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:gcc-defaults [X-Debbugs-CC: debian...@lists.debian.org, gcc-defau...@packages.debian.org] Dear maintainer(s), With a recent upload of

Processed: xmds2: autopkgtest needs update for new version of gcc-defaults: 5 tests fail to build

Processing control commands: > affects -1 src:gcc-defaults Bug #996279 [src:xmds2] xmds2: autopkgtest needs update for new version of gcc-defaults: 5 tests fail to build Added indication that 996279 affects src:gcc-defaults -- 996279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996279

Bug#996028: [debian-mysql] Bug#996028: InnoDB: corrupted TRX_NO after upgrading to 10.3.31

On Sunday 10 October 2021 23:58:12 Otto Kekäläinen wrote: > > The problem is in the ibdata1 file (about 450MB). Deleted other database > > directories and it still crashes, deleted ibdata1 and it runs. > > > > How to bisect mariadb from git? Tried: > > $ git bisect good mariadb-10.3.29 > > $ git

Processed: Re: Bug#995362: zint breaks zbar autopkgtest: unable to open file `/tmp/magick-VxkNk3KeW43pSnBYixIpsF9xU8qRmIzE': No such file or directory @ error/constitute.c/ReadImage/614

Processing control commands: > severity -1 important Bug #995362 [zbar-tools] zint breaks zbar autopkgtest: unable to open file `/tmp/magick-VxkNk3KeW43pSnBYixIpsF9xU8qRmIzE': No such file or directory @ error/constitute.c/ReadImage/614 Severity set to 'important' from 'serious' -- 995362:

Bug#995362: zint breaks zbar autopkgtest: unable to open file `/tmp/magick-VxkNk3KeW43pSnBYixIpsF9xU8qRmIzE': No such file or directory @ error/constitute.c/ReadImage/614

Control: severity -1 important On Thu, 30 Sep 2021 23:32:21 + John Scott wrote: > On Thu, 2021-09-30 at 09:18 -0400, John Scott wrote: > > Outside a minimal chroot, on my desktop system, zbarimg seems to > > process SVGs just fine. So this may be a case of a Recommends > > (somewhere) not

Processed: open3d: autopkgtest needs update for new version of gcc-defaults: output on stderr

Processing control commands: > affects -1 src:gcc-defaults Bug #996278 [src:open3d] open3d: autopkgtest needs update for new version of gcc-defaults: output on stderr Added indication that 996278 affects src:gcc-defaults -- 996278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996278

Bug#996278: open3d: autopkgtest needs update for new version of gcc-defaults: output on stderr

Source: open3d Version: 0.9.0+ds-6 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:gcc-defaults [X-Debbugs-CC: debian...@lists.debian.org, gcc-defau...@packages.debian.org] Dear maintainer(s), With a recent upload of

Processed: deal.ii: autopkgtest needs update for new version of gcc-defaults: An error occurred in line <1048> of file <./source/fe/mapping_q_generic.cc> in function

Processing control commands: > affects -1 src:gcc-defaults Bug #996277 [src:deal.ii] deal.ii: autopkgtest needs update for new version of gcc-defaults: An error occurred in line <1048> of file <./source/fe/mapping_q_generic.cc> in function Added indication that 996277 affects src:gcc-defaults

Bug#996277: deal.ii: autopkgtest needs update for new version of gcc-defaults: An error occurred in line <1048> of file <./source/fe/mapping_q_generic.cc> in function

Source: deal.ii Version: 9.3.0-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:gcc-defaults [X-Debbugs-CC: debian...@lists.debian.org, gcc-defau...@packages.debian.org] Dear maintainer(s), With a recent upload of

Bug#996188: marked as done (RuntimeError: populate() isn't reentrant)

Your message dated Tue, 12 Oct 2021 20:51:11 +0200 with message-id <024a686c-cf8b-6b27-de85-0a907ac5a...@debian.org> and subject line Re: Bug#996188: RuntimeError: populate() isn't reentrant has caused the Debian Bug report #996188, regarding RuntimeError: populate() isn't reentrant to be marked

Bug#995928: acorn: doc directory shipped by both binaries

Hi release team, concerning this bug, I'd like to hear advice from you on how you'd best like to see this fixed in stable. The current bug causes trouble for reproducible builds operations (basically, it throws away all build involving node-acorn in bullseye). See the last paragraph on my

Processed: found 994300 in 0.7.0-2

Processing commands for cont...@bugs.debian.org: > found 994300 0.7.0-2 Bug #994300 {Done: Picca Frédéric-Emmanuel } [src:gpyfft] gpyfft: Removal of the python3-*-dbg packages in sid/bookworm Marked as found in versions gpyfft/0.7.0-2. > thanks Stopping processing here. Please contact me if you

Processed: severity of 993622 is serious

Processing commands for cont...@bugs.debian.org: > severity 993622 serious Bug #993622 {Done: Timo Röhling } [python3-open3d] python3-open3d: Missing dependency on python3-numpy Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance.

Bug#970880: [Pkg-freeipa-devel] Bug#970880: Bug#970880: Bug#970880: Bug#970880: freeipa-server: FreeIPA server installation fails with Certificate issuance failed (CA_REJECTED)

On Tue, Oct 12, 2021 at 9:53 AM Spencer Olson wrote: > > On Sun, Oct 10, 2021 at 12:58 PM Timo Aaltonen wrote: > > > > > > > > > > > Maybe the CI will finish before I can get back to my testing. > > > > And it did, this error is fixed now :) > > > > But it fails later on, so there's some work

Bug#995815: marked as done (ruby-eventmachine FTBFS on IPV6-only buildds)

Your message dated Tue, 12 Oct 2021 17:34:40 + with message-id and subject line Bug#995815: fixed in ruby-eventmachine 1.3~pre20201020-b50c135-4 has caused the Debian Bug report #995815, regarding ruby-eventmachine FTBFS on IPV6-only buildds to be marked as done. This means that you claim

Bug#996263: ctop: Should this package be removed?

Package: ctop Severity: serious Version: 1.0.0-2.1 X-Debbugs-CC: czc...@debian.org Dear Debian ctop package maintainer, As discussed in https://bugs.debian.org/922061 , the current ctop software in Debian is unmaintained, incompatible with Debian 11 and later, and has a dead upstream. I believe

Bug#995815: marked as pending in ruby-eventmachine

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

Processing control commands: > tag -1 pending Bug #995815 [src:ruby-eventmachine] ruby-eventmachine FTBFS on IPV6-only buildds Added tag(s) pending. -- 995815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#996258: marked as done (FTBFS: test failure in t/06-replicated.t)

Your message dated Tue, 12 Oct 2021 17:03:39 + with message-id and subject line Bug#996258: fixed in libdbicx-sugar-perl 0.0200-2 has caused the Debian Bug report #996258, regarding FTBFS: test failure in t/06-replicated.t to be marked as done. This means that you claim that the problem has

Bug#984092: marked as done (libbpp-seq-omics: ftbfs with GCC-11)

Your message dated Tue, 12 Oct 2021 17:03:35 + with message-id and subject line Bug#984092: fixed in libbpp-seq-omics 2.4.1-7 has caused the Debian Bug report #984092, regarding libbpp-seq-omics: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been

Bug#995021: osmnx: autopkgtest regression on armhf: Restriction not respected

Hi, On 12-10-2021 10:12, Jerome BENOIT wrote: > Hello Paul, it seems that the Restriction needs-internet is not respected. All our hosts have unlimited internet access, so the restriction is currently not "meaning" anything on ci.d.n infrastructure. Hosts that have no unlimited internet access

Bug#996160: closing 996160

close 996160 1.3~pre20201020-b50c135-3 thanks

Processed: closing 996160

Processing commands for cont...@bugs.debian.org: > close 996160 1.3~pre20201020-b50c135-3 Bug #996160 [src:ruby-eventmachine] ruby-eventmachine: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Marked as fixed in versions ruby-eventmachine/1.3~pre20201020-b50c135-3. Bug #996160

Processed: Bug#996258 marked as pending in libdbicx-sugar-perl

Processing control commands: > tag -1 pending Bug #996258 [src:libdbicx-sugar-perl] FTBFS: test failure in t/06-replicated.t Added tag(s) pending. -- 996258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#996258: marked as pending in libdbicx-sugar-perl

Control: tag -1 pending Hello, Bug #996258 in libdbicx-sugar-perl 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 996258 is forwarded to https://github.com/ironcamel/DBICx-Sugar/issues/6

Processing commands for cont...@bugs.debian.org: > forwarded 996258 https://github.com/ironcamel/DBICx-Sugar/issues/6 Bug #996258 [src:libdbicx-sugar-perl] FTBFS: test failure in t/06-replicated.t Set Bug forwarded-to-address to 'https://github.com/ironcamel/DBICx-Sugar/issues/6'. > thanks

Bug#996258: FTBFS: test failure in t/06-replicated.t

Source: libdbicx-sugar-perl Version: 0.0200-1 Severity: serious Tags: ftbfs bookworm sid Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As noticed on ci.debian.net, the package's testsuite fails, and does so also during build in a sid chroot:

Bug#970880: [Pkg-freeipa-devel] Bug#970880: Bug#970880: Bug#970880: Bug#970880: freeipa-server: FreeIPA server installation fails with Certificate issuance failed (CA_REJECTED)

On Sun, Oct 10, 2021 at 12:58 PM Timo Aaltonen wrote: > > > > > > > Maybe the CI will finish before I can get back to my testing. > > And it did, this error is fixed now :) > > But it fails later on, so there's some work still to catch up with the > current distro, but at least this particular

Bug#984264: marked as done (oasis3: ftbfs with GCC-11)

Your message dated Tue, 12 Oct 2021 15:34:28 + with message-id and subject line Bug#984264: fixed in oasis3 3.mct+dfsg.121022-16 has caused the Debian Bug report #984264, regarding oasis3: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#984416: marked as done (xmltooling: ftbfs with GCC-11)

Your message dated Tue, 12 Oct 2021 15:19:04 + with message-id and subject line Bug#984222: fixed in log4shib 2.0.0-3 has caused the Debian Bug report #984222, regarding xmltooling: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#984329: marked as done (shibboleth-resolver: ftbfs with GCC-11)

Your message dated Tue, 12 Oct 2021 15:19:04 + with message-id and subject line Bug#984222: fixed in log4shib 2.0.0-3 has caused the Debian Bug report #984222, regarding shibboleth-resolver: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt

Bug#984327: marked as done (shibboleth-sp: ftbfs with GCC-11)

Your message dated Tue, 12 Oct 2021 15:19:04 + with message-id and subject line Bug#984222: fixed in log4shib 2.0.0-3 has caused the Debian Bug report #984222, regarding shibboleth-sp: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#984241: marked as done (moonshot-gss-eap: ftbfs with GCC-11)

Your message dated Tue, 12 Oct 2021 15:19:04 + with message-id and subject line Bug#984222: fixed in log4shib 2.0.0-3 has caused the Debian Bug report #984222, regarding moonshot-gss-eap: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#984277: marked as done (opensaml: ftbfs with GCC-11)

Your message dated Tue, 12 Oct 2021 15:19:04 + with message-id and subject line Bug#984222: fixed in log4shib 2.0.0-3 has caused the Debian Bug report #984222, regarding opensaml: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#984222: marked as done (log4shib: ftbfs with GCC-11)

Your message dated Tue, 12 Oct 2021 15:19:04 + with message-id and subject line Bug#984222: fixed in log4shib 2.0.0-3 has caused the Debian Bug report #984222, regarding log4shib: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: bug 994736 is forwarded to https://github.com/leto/math--gsl/issues/243

Processing commands for cont...@bugs.debian.org: > forwarded 994736 https://github.com/leto/math--gsl/issues/243 Bug #994736 [src:libmath-gsl-perl] libmath-gsl-perl: FTBFS on several architectures: undefined symbol: gsl_matrix_char_norm1 Set Bug forwarded-to-address to

Bug#996251: marked as done (libdbd-pg-perl: FTBFS with postgresql 14: test failures)

Your message dated Tue, 12 Oct 2021 15:04:55 + with message-id and subject line Bug#996251: fixed in libdbd-pg-perl 3.15.0-2 has caused the Debian Bug report #996251, regarding libdbd-pg-perl: FTBFS with postgresql 14: test failures to be marked as done. This means that you claim that the

Bug#984336: marked as done (skycat: ftbfs with GCC-11)

Your message dated Tue, 12 Oct 2021 15:05:51 + with message-id and subject line Bug#984336: fixed in skycat 3.1.2+starlink1~b+dfsg-6 has caused the Debian Bug report #984336, regarding skycat: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt

Processed: tagging 996251

Processing commands for cont...@bugs.debian.org: > tags 996251 + bookworm sid Bug #996251 [src:libdbd-pg-perl] libdbd-pg-perl: FTBFS with postgresql 14: test failures Added tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 996251:

Processed: fixed 996251 in 3.15.0-1

Processing commands for cont...@bugs.debian.org: > fixed 996251 3.15.0-1 Bug #996251 [src:libdbd-pg-perl] libdbd-pg-perl: FTBFS with postgresql 14: test failures Marked as fixed in versions libdbd-pg-perl/3.15.0-1. > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: notfound 994370 in 1.2.2-2

Processing commands for cont...@bugs.debian.org: > notfound 994370 1.2.2-2 Bug #994370 {Done: Gordon Ball } [src:python-setproctitle] python-setproctitle: Removal of the python3-*-dbg packages in sid/bookworm No longer marked as found in versions python-setproctitle/1.2.2-2. > thanks Stopping

  1   2   >