Hi Étienne
On Fri, 5 Nov 2021 at 00:03, Étienne Mollier wrote:
> From Andreas Tille's discussion with upstream, this might be
> caused by numpy or scipy, possibly Debian specific.
This sounds a lot like #994457 which was due to a change in lapack 3.10.
Regards
Graham
On 2021/11/05 05:55, Florian Schlichting wrote:
> However, Max: behind this hides another problem, which is why I asked
> Ryan to delete the pid_file configuration: as part of 0.23.3 you added
> the "RuntimeDirectory=mpd" directive to both mpd.service units. In the
> absence of User and Group
Hi Ryan (and Max please see below):
> and have the following minimal mpd.conf:
>
> --
> music_directory "/var/lib/mpd/music"
> db_file "/var/lib/mpd/tag_cache"
> pid_file "/run/mpd/pid"
> state_file
Your message dated Fri, 05 Nov 2021 04:18:50 +
with message-id
and subject line Bug#99: fixed in python-easygui 0.98.1-2
has caused the Debian Bug report #99,
regarding python-easygui: FTBFS: There is a syntax error in your configuration
file: invalid syntax (conf.py, line 276)
to be
-truncate
Version: 2.1.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
&
Processing control commands:
> tag -1 pending
Bug #998610 [src:node-cli-truncate] node-cli-truncate: FTBFS: dh_auto_test:
error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Added tag(s) pending.
--
998610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998610
Debian Bug
package*
Regards
Chris - DarkTrick
* Yes, I'm trying to promote my updates here :)
On 2021/11/05 2:38, Lucas Nussbaum wrote:
Source: gjiten
Version: 2.6-3.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi
Control: tag -1 pending
Hello,
Bug #998610 in node-cli-truncate 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:
Upstream version 0.11.14 seems to fix this issue, but the patch seems to
create a new bug:
https://gitlab.com/sublime-music/sublime-music/-/issues/325
Currently waiting for feedback from upstream.
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau
⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org
Your message dated Fri, 05 Nov 2021 02:45:17 +
with message-id
and subject line Bug#996129: fixed in ruby-axiom-types 0.1.1-2
has caused the Debian Bug report #996129,
regarding ruby-axiom-types: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
RuntimeError:
to be marked as done.
> After 2 weeks, the bug has finally been fixed. But I wonder why the bug
> wasn't tested out in the unstable branch and was pushed into the testing
Because on unstable everything worked. The bug happens only due to
different transition times from unstable to testing. This cannot be
tested in
After 2 weeks, the bug has finally been fixed. But I wonder why the bug
wasn't tested out in the unstable branch and was pushed into the testing
branch.
Processing control commands:
> tag -1 pending
Bug #996129 [src:ruby-axiom-types] ruby-axiom-types: FTBFS with ruby3.0: ERROR:
Test "ruby3.0" failed: RuntimeError:
Added tag(s) pending.
--
996129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996129
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #996129 in ruby-axiom-types 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 01:19:58 +
with message-id
and subject line Bug#997129: fixed in marble 4:21.08.3-1
has caused the Debian Bug report #997129,
regarding marble: FTBFS: dh_install: error: missing files, aborting
to be marked as done.
This means that you claim that the
Your message dated Fri, 05 Nov 2021 01:20:19 +
with message-id
and subject line Bug#996124: fixed in ruby-appraiser 0.2.0-4
has caused the Debian Bug report #996124,
regarding ruby-appraiser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
No such file or directory @ rb_sysopen -
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
>dh_update_autotoo
On Thu, 2021-11-04 at 20:45 +0100, Lucas Nussbaum wrote:
> Source: git-imerge
...
> > ERROR: Could not install packages due to an EnvironmentError:
> > [Errno 13] Permission denied: '/usr/lib/python3.9/dist-packages'
This is apparently caused by a change in dh-python that will be
reverted. For
Control: tag -1 pending
Hello,
Bug #996124 in ruby-appraiser 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 #996124 [src:ruby-appraiser] ruby-appraiser: FTBFS with ruby3.0: ERROR:
Test "ruby3.0" failed: No such file or directory @ rb_sysopen -
http://rubygems.org/api/v1/gems/rails.json
Added tag(s) pending.
--
996124:
ion: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
>dh_update_autotools_config
Your message dated Fri, 05 Nov 2021 00:04:19 +
with message-id
and subject line Bug#998422: fixed in rails 2:6.0.3.7+dfsg-3
has caused the Debian Bug report #998422,
regarding ArgumentError: wrong number of arguments (given 2, expected 3) caused
by lib/active_support/cache.rb:330
to be
Control: tag -1 pending
Hello,
Bug #998422 in rails 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 #998422 [ruby-activesupport] ArgumentError: wrong number of arguments
(given 2, expected 3) caused by lib/active_support/cache.rb:330
Added tag(s) pending.
--
998422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998422
Debian Bug Tracking
essage ---
Source: libscout
Version: 2.3.2-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> deb
act ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apktool
Version: 2.5.0+dfsg.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on
Processing commands for cont...@bugs.debian.org:
> reassign 998531 src:commons-io
Bug #998531 [src:libscout] libscout: FTBFS: Could not resolve
commons-io:commons-io:2.6.
Bug reassigned from package 'src:libscout' to 'src:commons-io'.
No longer marked as found in versions libscout/2.3.2-3.
> bind9-dev : Depends: bind9-libs (= 1:9.16.21-1) but it is not going to be
installed
It looks like bind8 no longer builds the bind9-dev package. It's still present
in
unstable as a cruft package but is uninstallable due to version constraints,
it's
completely gone from testing.
Bind
Your message dated Thu, 04 Nov 2021 23:33:45 +
with message-id
and subject line Bug#996207: fixed in ruby-combustion 1.3.3-1
has caused the Debian Bug report #996207,
regarding ruby-combustion: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
Failure/Error: require "bundler/setup"
to be
Package: libsane1
Version: 1.0.32-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I've upgraded libsane1 package from 1.0.31-4.1 to 1.0.32-4 and my Epson
Perfection 164SU stopped working.
I tried to debug the issue with:
~$ SANE_DEBUG_EPSON2=255 scanimage
Processing commands for cont...@bugs.debian.org:
> reassign 998422 ruby-activesupport
Bug #998422 [src:ruby-active-model-serializers] ArgumentError: wrong number of
arguments (given 2, expected 3) caused by lib/active_support/cache.rb:330
Bug reassigned from package
Processing control commands:
> tag -1 pending
Bug #996207 [src:ruby-combustion] ruby-combustion: FTBFS with ruby3.0: ERROR:
Test "ruby3.0" failed: Failure/Error: require "bundler/setup"
Added tag(s) pending.
--
996207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996207
Debian Bug
Control: tag -1 pending
Hello,
Bug #996207 in ruby-combustion 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 Thu, 04 Nov 2021 23:04:11 +
with message-id
and subject line Bug#996156: fixed in ruby-ahoy-email 1.1.1-1
has caused the Debian Bug report #996156,
regarding ruby-ahoy-email: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
to be marked as done.
This means that you claim
Processing control commands:
> tag -1 pending
Bug #996156 [src:ruby-ahoy-email] ruby-ahoy-email: FTBFS with ruby3.0: ERROR:
Test "ruby3.0" failed.
Ignoring request to alter tags of bug #996156 to the same tags previously set
--
996156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996156
Control: tag -1 pending
Hello,
Bug #996156 in ruby-ahoy-email 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:
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_autoreconf
Control: tag -1 pending
Hello,
Bug #996156 in ruby-ahoy-email 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 #996156 [src:ruby-ahoy-email] ruby-ahoy-email: FTBFS with ruby3.0: ERROR:
Test "ruby3.0" failed.
Added tag(s) pending.
--
996156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996156
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Maybe I am wrong, but, for me, the simplest method to track this bug
down is to check the changes between the two versions, 93.0 and
93.0-1+b1. Firefox code has not changed, only one or some libraries it
depends on. I thought that the only change is in libvpx version, but,
surprisingly, a
Maybe i missed a comment but can someone give a try with the upstream
binary? To see if it happens for you too there?
Merci
Sylvestre
Le jeu. 4 nov. 2021 à 23:15, Josh Triplett a écrit :
> Some additional information that might help track this down: several
> times, I've observed one tab
I have fixed gmsh. It will appear in NEW soon.
Regards
Anton
Your message dated Thu, 04 Nov 2021 22:19:25 +
with message-id
and subject line Bug#996515: fixed in ruby-tilt 2.0.10-2
has caused the Debian Bug report #996515,
regarding ruby-tilt: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
TypeError: no implicit conversion of Hash into String
to be
Processing control commands:
> tag -1 pending
Bug #998477 [src:phyml] phyml: FTBFS: configure.ac:13: error: AM_INIT_AUTOMAKE
expanded multiple times
Added tag(s) pending.
--
998477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998477
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #998477 in phyml 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:
> retitle 997126 nipype: ftbfs: nipype.algorithms.tests.test_CompCor failure
Bug #997126 [src:nipype] nipype: FTBFS: XXX
Changed Bug title to 'nipype: ftbfs: nipype.algorithms.tests.test_CompCor
failure' from 'nipype: FTBFS: XXX'.
> thank you
Some additional information that might help track this down: several
times, I've observed one tab freezing, but the browser itself is still
responsive for a *short* time. I can open a new tab, and close it again,
and the previous tab then renders as a busy symbol.
I'm wondering if one of the tab
--- Begin Message ---
Source: rust-selinux-sys
Version: 0.5.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ./test-debian-distro-in
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build --
: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> sed '/@GENERATED@/,$d' debian/gradle.pod
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> mkdir -p .gradle/init.d
: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --buildsystem=gradle --with javahelper,maven_repo_helper
>dh_update_autotools_config -O--buildsyst
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -- --project-prop osmosisBuild
Processing control commands:
> tags -1 confirmed
Bug #997126 [src:nipype] nipype: FTBFS: XXX
Added tag(s) confirmed.
> forwarded -1 https://github.com/nipy/nipype/issues/3382
Bug #997126 [src:nipype] nipype: FTBFS: XXX
Set Bug forwarded-to-address to 'https://github.com/nipy/nipype/issues/3382'.
Processing commands for cont...@bugs.debian.org:
> close 996621 2.0.7+dfsg-2
Bug #996621 [src:ruby-enumerable-statistics] ruby-enumerable-statistics: FTBFS
on i386: ERROR: Test "ruby2.7" failed: Failure/Error: it { is_expected.to
eq(x) }
Marked as fixed in versions
close 996621 2.0.7+dfsg-2
thanks
Processing control commands:
> tag -1 pending
Bug #996515 [src:ruby-tilt] ruby-tilt: FTBFS with ruby3.0: ERROR: Test
"ruby3.0" failed: TypeError: no implicit conversion of Hash into String
Added tag(s) pending.
--
996515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996515
Debian Bug
Control: tag -1 pending
Hello,
Bug #996515 in ruby-tilt 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:
ontact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-onig
Version: 6.1.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to
Control: tag -1 pending
Hello,
Bug #998606 in commons-io 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 #998606 [src:commons-io] gradle: FTBFS: Could not resolve
commons-io:commons-io:debian.
Bug #998536 [src:commons-io] commons-io: Missing dependency on junit5 for
junit-bom
Bug #998549 [src:commons-io] grengine: FTBFS: dh_auto_test: error: gradle
On 2021-11-04 21:41, Sebastian Ramacher wrote:
On 2021-11-03 22:33:01 +0100, Drew Parsons wrote:
...
The problem that hypre 2.18.1-1 (un-versioned libhypre) intended to
solve is
that hypre is ABI-ignorant
(https://github.com/hypre-space/hypre/issues/56),
so each point patch release would have
System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-onig-sys
Version: 69.5.1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package
Hi,
On Thu, Nov 04, 2021 at 08:49:47PM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23:
> > syntax error
It looks like a
Processing control commands:
> tag -1 pending
Bug #998598 [src:distro-info] distro-info: FTBFS: dh_auto_test: error: make -j4
test returned exit code 2
Ignoring request to alter tags of bug #998598 to the same tags previously set
--
998598:
Control: tag -1 pending
Hello,
Bug #998598 in distro-info 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 Thu, 04 Nov 2021 21:18:45 +
with message-id
and subject line Bug#997655: fixed in diodon 1.11.2-1
has caused the Debian Bug report #997655,
regarding diodon: FTBFS: autoreconf: error: configure.in: AC_INIT not found;
not an autoconf script?
to be marked as done.
This
The packages that will fix this (rust-cargo-util and rust-im-rc) are in NEW.
Processing control commands:
> tag -1 pending
Bug #998598 [src:distro-info] distro-info: FTBFS: dh_auto_test: error: make -j4
test returned exit code 2
Added tag(s) pending.
--
998598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998598
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #998598 in distro-info 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:
> forcemerge 998549 998536
Bug #998549 [src:commons-io] grengine: FTBFS: dh_auto_test: error: gradle
--info --console plain --offline --stacktrace --no-daemon
--refresh-dependencies --gradle-user-home .gradle -Duser.home=.
-Duser.name=debian
The new version of rust-memchr which will fix this is in NEW.
Version: 1.08-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direct
Version: 1.07-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direct
Processing commands for cont...@bugs.debian.org:
> reassign 998606 src:commons-io
Bug #998606 [src:commons-io] gradle: FTBFS: Could not resolve
commons-io:commons-io:debian.
Ignoring request to reassign bug #998606 to the same package
> reassign 998604 src:commons-io
Bug #998604 [src:wala] wala:
reassign 998536 src:commons-io
found 998536 commons-io/2.11.0-1
affects 998536 src:osmosis
retitle 998536 Missing dependency on junit5 for junit-bom
thanks
On 11/4/21 20:56, Lucas Nussbaum wrote:
Putting task artifact state for task ':osmosis-pbf2:compileJava' into context
took 0.0 secs.
Processing commands for cont...@bugs.debian.org:
> close 998566
Bug #998566 [src:golang-github-alecthomas-chroma]
golang-github-alecthomas-chroma: FTBFS:
src/github.com/alecthomas/kong-hcl/loader.go:90:18: invalid operation:
node.Group != "" (mismatched types *kong.Group and untyped string)
Processing commands for cont...@bugs.debian.org:
> reassign 998606 src:commons-io
Bug #998606 [src:gradle] gradle: FTBFS: Could not resolve
commons-io:commons-io:debian.
Bug reassigned from package 'src:gradle' to 'src:commons-io'.
No longer marked as found in versions gradle/4.4.1-13.
Ignoring
Processing commands for cont...@bugs.debian.org:
> retitle 998536 commons-io: Missing dependency on junit5 for junit-bom
Bug #998536 [src:commons-io] Missing dependency on junit5 for junit-bom
Changed Bug title to 'commons-io: Missing dependency on junit5 for junit-bom'
from 'Missing dependency
Processing commands for cont...@bugs.debian.org:
> reassign 998536 src:commons-io
Bug #998536 [src:osmosis] osmosis: FTBFS: Could not resolve
commons-io:commons-io:2.6.
Bug reassigned from package 'src:osmosis' to 'src:commons-io'.
No longer marked as found in versions osmosis/0.48.3-1.
Ignoring
Version: 3.2.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direct
Processing control commands:
> tag -1 pending
Bug #998560 [src:libdate-tiny-perl] libdate-tiny-perl: FTBFS: dh_auto_test:
error: make -j4 test TEST_VERBOSE=1 returned exit code 2
Added tag(s) pending.
--
998560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998560
Debian Bug Tracking
Control: tag -1 pending
Hello,
Bug #998560 in libdate-tiny-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:
Your message dated Thu, 04 Nov 2021 20:49:19 +
with message-id
and subject line Bug#984090: fixed in libbpp-raa 2.4.1-6
has caused the Debian Bug report #984090,
regarding libbpp-raa: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Am Donnerstag, dem 04.11.2021 um 20:54 +0100 schrieb Lucas Nussbaum:
> Source: gradle
> Version: 4.4.1-13
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20211104 ftbfs-bookworm
>
> Hi,
>
> During
On 2021-11-03 22:33:01 +0100, Drew Parsons wrote:
> On 2021-11-03 20:57, Sebastian Ramacher wrote:
> > Source: hypre
> > Severity: serious
> ...
> > The real blocker is hypre, specifically:
> >
> > hypre (2.18.1-1) experimental; urgency=medium
> > .
> >* Team upload.
> >* New upstream
Control: tag -1 pending
Hello,
Bug #998568 in libtime-tiny-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:
Processing control commands:
> tag -1 pending
Bug #998568 [src:libtime-tiny-perl] libtime-tiny-perl: FTBFS: dh_auto_test:
error: make -j4 test TEST_VERBOSE=1 returned exit code 2
Added tag(s) pending.
--
998568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998568
Debian Bug Tracking
Your message dated Thu, 04 Nov 2021 20:36:23 +
with message-id
and subject line Bug#996237: fixed in ruby-gsl 2.1.0.3+dfsg1-4
has caused the Debian Bug report #996237,
regarding ruby-gsl: FTBFS with ruby3.0: include/rb_gsl_common.h:29:1: error:
unknown type name ‘EXTERN’
to be marked as
Processing commands for cont...@bugs.debian.org:
> forwarded 998568 https://github.com/dagolden/Time-Tiny/issues/4
Bug #998568 [src:libtime-tiny-perl] libtime-tiny-perl: FTBFS: dh_auto_test:
error: make -j4 test TEST_VERBOSE=1 returned exit code 2
Set Bug forwarded-to-address to
Processing commands for cont...@bugs.debian.org:
> tags 998601 + confirmed
Bug #998601 [src:libconfig-model-itself-perl] libconfig-model-itself-perl:
FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit
code 2
Added tag(s) confirmed.
> thanks
Stopping processing here.
Processing commands for cont...@bugs.debian.org:
> fixed 998541 4.7~beta2-1
Bug #998541 [src:dynare] dynare: FTBFS: TypeError: 'DynareLexer' object is not
callable
Marked as fixed in versions dynare/4.7~beta2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Source: retro-gtk
Version: 1.0.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Enter
Source: libisocodes
Version: 1.2.4-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Enter
Source: rust-tokio-executor
Version: 0.1.8-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully
Source: canl-java
Version: 2.7.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules bu
Source: node-cli-truncate
Version: 2.1.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> deb
Source: appstream-glib
Version: 0.7.18-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> mak
Source: gnome-logs
Version: 3.36.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Enter
1 - 100 of 270 matches
Mail list logo
