Your message dated Sat, 06 Nov 2021 04:03:41 +
with message-id
and subject line Bug#996344: fixed in ruby-openstack 2.0.2-2
has caused the Debian Bug report #996344,
regarding ruby-openstack: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
Error: test_rebuild_server(ServersTest):
Processing control commands:
> tag -1 pending
Bug #996344 [src:ruby-openstack] ruby-openstack: FTBFS with ruby3.0: ERROR:
Test "ruby3.0" failed: Error: test_rebuild_server(ServersTest): NoMethodError:
undefined method `encode' for URI:Module
Added tag(s) pending.
--
996344:
Control: tag -1 pending
Hello,
Bug #996344 in ruby-openstack 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:
Your message dated Sat, 06 Nov 2021 03:04:31 +
with message-id
and subject line Bug#996341: fixed in ruby-ntlm 0.6.3-1
has caused the Debian Bug report #996341,
regarding ruby-ntlm: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
Failure/Error: dec.encrypt.update(plain) + dec.final
to
> I was also experiencing this problem and was monitoring this bug
> report for potential solutions, but the problem seems to have
> recently disappeared.
I cannot confirm this.
I've just upgraded to 94.0-1 (with everything else on my system
upgraded to the current state of unstable, well
Since I recently dist-upgraded sid.
Tried to:
1) run with empty profile
2) do apt-get dist-upgrade just now, restart - doesn't help
it seems to be freezing during rendering of the websites, seems like
eventually running out of some resource and java-script heavy sites
freeze it very soon.
For
Hello! Gazebo maintainer here, affected by this RC bug. Looking into
upstream repository there is a potential commit that can be used to patch
this problem until new versions land in Debian:
https://github.com/InsightSoftwareConsortium/ITK/commit/840f22feb351739359a8fdb55304124823a3a8c9
Let me
Your message dated Sat, 06 Nov 2021 00:20:42 +
with message-id
and subject line Bug#996311: fixed in ruby-lapack 1.8.2-1
has caused the Debian Bug report #996311,
regarding ruby-lapack: FTBFS: ERROR: Test "ruby2.7" failed.
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 06 Nov 2021 00:20:42 +
with message-id
and subject line Bug#994241: fixed in ruby-lapack 1.8.2-1
has caused the Debian Bug report #994241,
regarding ruby-lapack autopkgtest needs to be adapted for LAPACK 3.10
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> tags 984276 + patch
Bug #984276 [src:opencolorio] opencolorio: ftbfs with GCC-11
Added tag(s) patch.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
984276:
Hello! Gazebo maintainer here, affected by this RC bug on opencolorio. I've
looked in the problem and seems something easy to fix:
diff --git a/src/core/ImageDesc.cpp b/src/core/ImageDesc.cpp
index 63156c8..e96e758 100644
--- a/src/core/ImageDesc.cpp
+++ b/src/core/ImageDesc.cpp
@@ -57,8 +57,8 @@
Your message dated Sat, 06 Nov 2021 00:05:05 +
with message-id
and subject line Bug#996133: fixed in ruby-barby 0.6.8+dfsg-2
has caused the Debian Bug report #996133,
regarding ruby-barby: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
:85:in
`require': cannot load such file --
Processing control commands:
> tag -1 pending
Bug #996133 [src:ruby-barby] ruby-barby: FTBFS with ruby3.0: ERROR: Test
"ruby3.0" failed:
:85:in
`require': cannot load such file -- sorted_set (LoadError)
Added tag(s) pending.
--
996133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996133
Control: tag -1 pending
Hello,
Bug #996133 in ruby-barby 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:
Your message dated Fri, 05 Nov 2021 22:18:29 +
with message-id
and subject line Bug#998479: fixed in aevol 5.0+ds-3
has caused the Debian Bug report #998479,
regarding aevol: FTBFS: configure.ac:301: error: AM_INIT_AUTOMAKE expanded
multiple times
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> block 992899 with 994559
Bug #992899 {Done: Paul Gevers } [src:dub] src:dub: fails to
migrate to testing for too long
992899 was blocked by: 981229
992899 was not blocking any bugs.
Added blocking bug(s) of 992899: 994559
> thanks
Stopping
Hi,
I was also experiencing this problem and was monitoring this bug report for
potential solutions, but the problem seems to have recently disappeared. I
haven't experienced it since yesterday (2021-11-05) even on sites that I
knew to trigger it previously. Like everyone else, the problem
Your message dated Fri, 05 Nov 2021 22:03:28 +
with message-id
and subject line Bug#998237: fixed in arb 6.0.6-5
has caused the Debian Bug report #998237,
regarding arb: FTBFS with glibc 2.32 due to rpc header removal
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> tag -1 pending
Bug #998126 [src:pipewire] pipewire-pulse-dbgsym: dbgsym files overlap between
packages
Added tag(s) pending.
--
998126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #998126 in pipewire 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:
Your message dated Fri, 05 Nov 2021 21:48:49 +
with message-id
and subject line Bug#996132: fixed in ruby-backports 3.21.0-1
has caused the Debian Bug report #996132,
regarding ruby-backports: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
Control: tag -1 pending
Hello,
Bug #998237 in arb 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:
Processing control commands:
> tag -1 pending
Bug #998237 [src:arb] arb: FTBFS with glibc 2.32 due to rpc header removal
Added tag(s) pending.
--
998237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tags -1 + patch
Bug #997314 [src:python-hbmqtt] python-hbmqtt: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p 3.9 returned exit code 13
Added tag(s) patch.
--
997314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997314
Debian Bug Tracking
Processing control commands:
> tag -1 pending
Bug #998479 [src:aevol] aevol: FTBFS: configure.ac:301: error: AM_INIT_AUTOMAKE
expanded multiple times
Ignoring request to alter tags of bug #998479 to the same tags previously set
--
998479:
Control: tags -1 + patch
On Sat, Oct 23, 2021 at 09:40:41PM +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
Please find a fix attached.
Helmut
--- python-hbmqtt-0.9.6.orig/hbmqtt/adapters.py
+++
Control: tag -1 pending
Hello,
Bug #998479 in aevol 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:
Your message dated Fri, 05 Nov 2021 21:35:40 +
with message-id
and subject line Bug#996343: fixed in ruby-openid 2.9.2debian-2
has caused the Debian Bug report #996343,
regarding ruby-openid: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
:85:in
`require': cannot load such file --
Your message dated Fri, 05 Nov 2021 21:35:48 +
with message-id
and subject line Bug#996522: fixed in ruby-vips 2.0.17-3
has caused the Debian Bug report #996522,
regarding ruby-vips: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
ArgumentError:
to be marked as done.
This means that
Control: tag -1 pending
Hello,
Bug #996522 in ruby-vips 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:
Processing control commands:
> tag -1 pending
Bug #996522 [src:ruby-vips] ruby-vips: FTBFS with ruby3.0: ERROR: Test
"ruby3.0" failed: ArgumentError:
Added tag(s) pending.
--
996522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996522
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #996343 in ruby-openid 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:
Processing control commands:
> tag -1 pending
Bug #996343 [src:ruby-openid] ruby-openid: FTBFS with ruby3.0: ERROR: Test
"ruby3.0" failed:
:85:in
`require': cannot load such file -- webrick (LoadError)
Added tag(s) pending.
--
996343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996343
Your message dated Fri, 05 Nov 2021 21:19:47 +
with message-id
and subject line Bug#996316: fixed in ruby-mechanize 2.7.7-2
has caused the Debian Bug report #996316,
regarding ruby-mechanize: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
Your message dated Fri, 05 Nov 2021 21:04:55 +
with message-id
and subject line Bug#984247: fixed in mstflint 4.17.0+1-1
has caused the Debian Bug report #984247,
regarding mstflint: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Fri, 05 Nov 2021 21:05:17 +
with message-id
and subject line Bug#996230: fixed in ruby-friendly-id 5.4.2-1
has caused the Debian Bug report #996230,
regarding ruby-friendly-id: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
Processing control commands:
> tag -1 pending
Bug #996316 [src:ruby-mechanize] 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(s)
(Gem::MissingSpecError)
Control: tag -1 pending
Hello,
Bug #996316 in ruby-mechanize 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:
Processing commands for cont...@bugs.debian.org:
> reassign 998519 src:commons-io
Bug #998519 [src:commmons-io] picard-tools: FTBFS: Could not resolve
commons-io:commons-io:debian.
Warning: Unknown package 'src:commmons-io'
Bug reassigned from package 'src:commmons-io' to 'src:commons-io'.
Processing control commands:
> tags -1 + patch pending
Bug #998479 [src:aevol] aevol: FTBFS: configure.ac:301: error: AM_INIT_AUTOMAKE
expanded multiple times
Added tag(s) pending and patch.
--
998479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998479
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> reassign 998519 src:commmons-io
Bug #998519 [src:picard-tools] picard-tools: FTBFS: Could not resolve
commons-io:commons-io:debian.
Bug reassigned from package 'src:picard-tools' to 'src:commmons-io'.
Warning: Unknown package 'src:commmons-io'
On Friday, November 05 2021, Sebastiaan Couwenberg wrote:
> On 11/5/21 20:58, Sergio Durigan Junior wrote:
>> - The netcdf upstream project seems to be inactive, to say the least.
>>The last release happened in 2015, and I could not find a git
>>repository for it.
>
> Upstream development
In other words, I don't see what value these bug reports are adding.
As long as the package is not in Debian Testing, there are very excellent
status pages developed by the Debian Release team to make us aware of the
problem. Additional bug reports informing us of what we already know
Your message dated Fri, 05 Nov 2021 20:41:56 +
with message-id
and subject line Bug#996512: fixed in ruby-spy 1.0.1-1
has caused the Debian Bug report #996512,
regarding ruby-spy: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
ArgumentError: tried to create Proc object without a block
to
On 11/5/21 20:58, Sergio Durigan Junior wrote:
- The netcdf upstream project seems to be inactive, to say the least.
The last release happened in 2015, and I could not find a git
repository for it.
Upstream development is not healthy, but not entirely dead:
On Tue, Sep 21, 2021 at 03:31:17AM +0200, Vincent Lefevre wrote:
> Alternatively, I wonder whether w3c-sgml-lib (which appears to be
> correct) could replace w3-dtd-mathml,
>...
--- /usr/share/xml/schema/w3c/mathml/dtd/mathml2.dtd2001-06-20
17:45:45.0 +
+++
Your message dated Fri, 05 Nov 2021 20:34:18 +
with message-id
and subject line Bug#994266: fixed in azure-cli 2.30.0-1
has caused the Debian Bug report #994266,
regarding pyjwt breaks azure-cli autopkgtest: Could not deserialize key data.
The data may be in an incorrect format or it may be
Due to the nature of the Rust upstream ecosystem, bugs like this are expected
from time to time as we update dependent crates.
A reversion in terms of downgrading the version using +really-like schemes is
not feasible at the current time, see
Control: tag -1 - pending
On Wed, Oct 27, 2021 at 09:13:11AM +, Yadd wrote:
> Control: tag -1 pending
>
> Hello,
>
> Bug #997736 in moment-timezone.js 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
Processing control commands:
> tag -1 - pending
Bug #997736 [src:moment-timezone.js] moment-timezone.js: FTBFS: grep -q '^#
version 2021a$' /usr/share/zoneinfo/tzdata.zi => fails
Removed tag(s) pending.
--
997736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997736
Debian Bug Tracking
On Thu, Jan 28, 2021 at 01:01:15AM +0100, Matthias Klumpp wrote:
> Am Do., 28. Jan. 2021 um 00:33 Uhr schrieb Sebastian Ramacher
> :
> >
> > Source: dub
> > Version: 1.24.0-1
> > Severity: serious
> > X-Debbugs-Cc: sramac...@debian.org
> >
> > | autopkgtest [03:11:10]: test run:
On Tuesday, October 12 2021, Antonio Terceiro wrote:
> 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 situation.
>
> To reproduce this locally, you need to install ruby-all-dev from experimental
> on an unstable
Processing control commands:
> severity -1 important
Bug #994910 [tripwire] tripwire segfaults while reading files in /etc
Severity set to 'important' from 'grave'
--
994910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: severity -1 important
On Wed, Sep 22, 2021 at 08:06:31PM -0400, Ron Murray wrote:
> Package: tripwire
> Version: 2.4.3.7-3+b3
> Severity: grave
> Justification: renders package unusable
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Dear Maintainer,
>
> I've been using
Processing control commands:
> tags 984372 + patch
Bug #984372 [src:tripwire] tripwire: ftbfs with GCC-11
Added tag(s) patch.
> tags 984372 + pending
Bug #984372 [src:tripwire] tripwire: ftbfs with GCC-11
Added tag(s) pending.
--
984372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984372
Control: tags 984372 + patch
Control: tags 984372 + pending
Dear maintainer,
I've prepared an NMU for tripwire (versioned as 2.4.3.7-3.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I should
cancel it.
cu
Adrian
diff -Nru tripwire-2.4.3.7/debian/changelog
Your message dated Fri, 05 Nov 2021 19:33:46 +
with message-id
and subject line Bug#998589: fixed in gnome-shell 41.1-1
has caused the Debian Bug report #998589,
regarding gnome-shell: FTBFS: ../meson.build:1:0: ERROR: Unknown options:
"bash_completion"
to be marked as done.
This means that
Your message dated Fri, 05 Nov 2021 19:34:14 +
with message-id
and subject line Bug#998574: fixed in ionit 0.4.0-1
has caused the Debian Bug report #998574,
regarding ionit: FTBFS: dh_auto_test: error: pybuild --test -i python{version}
-p 3.9 returned exit code 13
to be marked as done.
This
Control: tag -1 pending
Hello,
Bug #998589 in gnome-shell 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:
Control: tags 998625 + pending
Dear maintainer,
I've prepared an NMU for python-spinners (versioned as
0.0~git20200220.a73d561-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
Regards.
SR
diff -Nru
Processing control commands:
> tag -1 pending
Bug #998589 [src:gnome-shell] gnome-shell: FTBFS: ../meson.build:1:0: ERROR:
Unknown options: "bash_completion"
Added tag(s) pending.
--
998589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998589
Debian Bug Tracking System
Contact
Processing control commands:
> tags 998625 + pending
Bug #998625 [src:python-spinners] python-spinners: FTBFS with dh-python
5.20211105 due to missing dependencies
Added tag(s) pending.
--
998625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998625
Debian Bug Tracking System
Contact
Control: tags 998623 + pending
Dear maintainer,
I've prepared an NMU for pysha3 (versioned as 1.0.2-4.2) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
Regards.
SR
diff -Nru pysha3-1.0.2/debian/changelog pysha3-1.0.2/debian/changelog
---
Processing control commands:
> tags 998623 + pending
Bug #998623 [src:pysha3] pysha3: FTBFS with dh-python 5.20211105 due to missing
tox.ini
Added tag(s) pending.
--
998623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Your message dated Fri, 05 Nov 2021 18:03:36 +
with message-id
and subject line Bug#998551: fixed in gtk4 4.4.1+ds1-2
has caused the Debian Bug report #998551,
regarding gtk4: FTBFS: ../../../meson.build:1:0: ERROR: Unknown options: "sassc"
to be marked as done.
This means that you claim
Control: tags -1 upstream
On 11/4/21 20:49, Lucas Nussbaum wrote:
sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23:
syntax error
This seems to be caused by the recent switch to sip6 in pyqt5.
Upstream recently added support for sip6 in their non-LTR, but those
Processing control commands:
> tags -1 upstream
Bug #998567 [src:qgis] qgis: FTBFS: sip:
/usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax
error
Added tag(s) upstream.
--
998567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998567
Debian Bug Tracking System
Your message dated Fri, 5 Nov 2021 13:36:01 -0400
with message-id <6063a2a2-e81a-f678-365f-5da063260...@babelouest.org>
and subject line Close bug report #993176: libssh2 FTBFS: configure.ac:130:
error: m4_undefine: undefined macro: backend
has caused the Debian Bug report #993176,
regarding
Processing control commands:
> tag -1 pending
Bug #994257 {Done: Carsten Schoenert }
[src:python-django, src:django-ldapdb] python-django breaks django-ldapdb
autopkgtest: 'Field' object has no attribute 'attname'
Added tag(s) pending.
--
994257:
Your message dated Fri, 05 Nov 2021 17:18:26 +
with message-id
and subject line Bug#994257: fixed in django-ldapdb 1.5.1-3
has caused the Debian Bug report #994257,
regarding python-django breaks django-ldapdb autopkgtest: 'Field' object has no
attribute 'attname'
to be marked as done.
This
Control: tag -1 pending
Hello,
Bug #994257 in django-ldapdb 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:
Control: tags 994257 + patch
Control: tags 994257 + pending
Dear maintainer,
I've prepared an NMU for django-ldapdb (versioned as 1.5.1-2.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I should
cancel it.
cu
Adrian
diff -Nru django-ldapdb-1.5.1/debian/changelog
Processing control commands:
> tags 994257 + patch
Bug #994257 [src:python-django, src:django-ldapdb] python-django breaks
django-ldapdb autopkgtest: 'Field' object has no attribute 'attname'
Added tag(s) patch.
> tags 994257 + pending
Bug #994257 [src:python-django, src:django-ldapdb]
Processing commands for cont...@bugs.debian.org:
> found 998581 dh-python/5.20211022
Bug #998581 {Done: Stefano Rivera } [src:git-imerge]
git-imerge: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p
3.9 returned exit code 13
Marked as found in versions dh-python/5.20211022.
>
Processing commands for cont...@bugs.debian.org:
> found 997485 dh-python/5.20211022
Bug #997485 {Done: Stefano Rivera } [src:python-prettylog]
python-prettylog: FTBFS: dh_auto_test: error: pybuild --test -i python{version}
-p 3.9 returned exit code 13
Marked as found in versions
Hi Steve,
On Sun, 19 Sep 2021 19:20:43 + Debian FTP Masters
wrote:
googletest (1.11.0-2) unstable; urgency=medium
.
[ Timo Röhling ]
* [d803038] Separate GTest and GMock targets in CMake (Closes: #994419)
.
Shouldn't we also fix this in Bullseye via stable-updates?
Cheers
Timo
Your message dated Fri, 05 Nov 2021 16:18:35 +
with message-id
and subject line Bug#997768: fixed in golang-github-gotk3-gotk3 0.6.1-1
has caused the Debian Bug report #997768,
regarding golang-github-gotk3-gotk3: FTBFS:
src/github.com/gotk3/gotk3/gtk/accel.go:247:5: val.accel_flags
Your message dated Fri, 05 Nov 2021 15:51:49 +
with message-id
and subject line Bug#996142: fixed in ruby-buff-config 2.0.0-3
has caused the Debian Bug report #996142,
regarding ruby-buff-config: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
RuntimeError:
to be marked as done.
This
Control: tag -1 pending
Hello,
Bug #996142 in ruby-buff-config 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:
>> But I guess you had, or some cosmic radiation induced bit switch did it
>> for you on your hard disk ;-) The default for all installations is being
>> on.
> yeah, then lets say "maybe" or "probably" I did that, nevertheless, at least
it was a couple of years ago and I cannot remeber ;-)
Processing control commands:
> tag -1 pending
Bug #996142 [src:ruby-buff-config] ruby-buff-config: FTBFS with ruby3.0: ERROR:
Test "ruby3.0" failed: RuntimeError:
Added tag(s) pending.
--
996142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996142
Debian Bug Tracking System
Contact
Your message dated Fri, 05 Nov 2021 15:12:18 +
with message-id
and subject line Bug#996521: fixed in ruby-vcr 6.0.0+really5.0.0-2
has caused the Debian Bug report #996521,
regarding ruby-vcr: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot
load such file -- webrick
to be marked as
Your message dated Fri, 05 Nov 2021 15:04:51 +
with message-id
and subject line Bug#996334: fixed in libics 1.6.5-2
has caused the Debian Bug report #996334,
regarding libics: binary-all FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Fri, 05 Nov 2021 14:49:47 +
with message-id
and subject line Bug#996525: fixed in ruby-xmlrpc 0.3.2-1
has caused the Debian Bug report #996525,
regarding ruby-xmlrpc: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 pending
Bug #996521 [src:ruby-vcr] ruby-vcr: FTBFS with ruby3.0: ERROR: Test "ruby3.0"
failed: cannot load such file -- webrick
Added tag(s) pending.
--
996521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996521
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #996521 in ruby-vcr 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:
Your message dated Fri, 05 Nov 2021 14:37:19 +
with message-id
and subject line Bug#996516: fixed in ruby-toml-rb 2.1.0-1
has caused the Debian Bug report #996516,
regarding ruby-toml-rb: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
Segmentation fault
to be marked as done.
This means
Your message dated Fri, 05 Nov 2021 14:37:12 +
with message-id
and subject line Bug#996138: fixed in ruby-bio 2.0.2-3
has caused the Debian Bug report #996138,
regarding ruby-bio: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error:
test_target(Bio::TestSiRNAPair): NoMethodError:
Package: luarocks
Version: 3.7.0+dfsg1-1
Followup-For: Bug #996781
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
The luarocks postinst sript was updated
Processing control commands:
> tags -1 patch
Bug #996781 [luarocks] luarocks: Installation fails with dpkg error
Added tag(s) patch.
--
996781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Fri, 05 Nov 2021 14:34:22 +
with message-id
and subject line Bug#998584: fixed in gnome-desktop3 41.1-1
has caused the Debian Bug report #998584,
regarding gnome-desktop3: FTBFS: ../meson.build:1:0: ERROR: Unknown options:
"desktop-docs"
to be marked as done.
This means
Probably the best way is to do the rolling release. Another solution is
to make each package synced downstream at the same time, but it's too hard
to achieve.
Jérôme Pouiller 于2021年11月5日周五 下午6:11写道：
> On Friday 5 November 2021 03:02:13 CET Norbert Preining wrote:
> > > After 2 weeks, the
On 05/11/2021 07:21, Timo Aaltonen wrote:
I'd have assumed that reverse build-depends are checked before migration to
testing?
They aren't :(
Processing control commands:
> tag -1 pending
Bug #996138 [src:ruby-bio] ruby-bio: FTBFS with ruby3.0: ERROR: Test "ruby3.0"
failed: Error: test_target(Bio::TestSiRNAPair): NoMethodError: undefined method
`subseq' for "cuuucggugcggacguaaggagu":String
Added tag(s) pending.
--
996138:
Control: tag -1 pending
Hello,
Bug #996138 in ruby-bio 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:
Control: reassign 997504 python3-gi 3.42.0-1
Control: affects 997504 src:terminator
Hi,
On Sat, 23 Oct 2021 22:41:30 +0200 Lucas Nussbaum wrote:
> collecting ... Trace/breakpoint trap
> E: pybuild pybuild:354: test: plugin distutils failed with: exit code=133: cd
Processing control commands:
> reassign 997504 python3-gi 3.42.0-1
Bug #997504 [src:terminator] terminator: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p 3.9 returned exit code 13
Bug reassigned from package 'src:terminator' to 'python3-gi'.
No longer marked as
Processing control commands:
> tag -1 pending
Bug #998584 [src:gnome-desktop3] gnome-desktop3: FTBFS: ../meson.build:1:0:
ERROR: Unknown options: "desktop-docs"
Ignoring request to alter tags of bug #998584 to the same tags previously set
--
998584:
Control: tag -1 pending
Hello,
Bug #998584 in gnome-desktop3 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:
Control: tag -1 pending
Hello,
Bug #998551 in gtk+4 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:
1 - 100 of 161 matches
Mail list logo
