Processing commands for cont...@bugs.debian.org:
> tags 995676 + pending
Bug #995676 [kmymoney] kmymoney FTBFS in bookworm.
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
995676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995676
Processing commands for cont...@bugs.debian.org:
> forwarded 984123 https://github.com/wojdyr/fityk/issues/37
Bug #984123 [src:fityk] fityk: ftbfs with GCC-11
Set Bug forwarded-to-address to 'https://github.com/wojdyr/fityk/issues/37'.
> thanks
Stopping processing here.
Please contact me if you
Your message dated Tue, 12 Oct 2021 03:33:40 +
with message-id
and subject line Bug#973905: fixed in python-typing-inspect 0.7.1-1
has caused the Debian Bug report #973905,
regarding python-typing-inspect's autopkg test fails
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 12 Oct 2021 03:33:40 +
with message-id
and subject line Bug#972803: fixed in python-typing-inspect 0.7.1-1
has caused the Debian Bug report #972803,
regarding python-typing-inspect fails tests with python3.9
to be marked as done.
This means that you claim that the
Hi Gianfranco,
On Sun, Mar 28, 2021 at 09:11:49PM +0200, Gianfranco Costamagna wrote:
> control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=27659
> control: affects -1 src:binutils
>
> Invoking the clang with -V shows a failure in ld.bdf linker, a failure that
> doesn't happen
Control: reassign -1 src:python-biopython 1.78+dfsg-5
Control: affects -1 src:python-reportlab 3.5.67-2
Control: tags -1 confirmed
Hi there,
Graham Inggs, on 2021-10-04:
> I noticed that python-biopython already has a Recommends on
> python3-renderpm. One solution would be to bump this to a
Package: graphite-web
Version: 1.1.8-1
Severity: grave
Dear Maintainer,
Installed graphite-web on a fresh bullseye machine and migrated the apache
virtualhost configuration from a running buster machine.
Attempting to load the page results in the error listed in the subject.
Full traceback:
Processing commands for cont...@bugs.debian.org:
> forwarded 983996 https://github.com/DanielStutzbach/blist/issues/98
Bug #983996 [src:blist] blist: ftbfs with GCC-11
Set Bug forwarded-to-address to
'https://github.com/DanielStutzbach/blist/issues/98'.
> thanks
Stopping processing here.
Please
Processing commands for cont...@bugs.debian.org:
> found 996171 2.64.2-2
Bug #996171 [src:glibmm2.4] glibmm2.4: FTBFS on buildds / reproducible builds
without network access
Marked as found in versions glibmm2.4/2.64.2-2.
> tags 996171 bookworm sid
Bug #996171 [src:glibmm2.4] glibmm2.4: FTBFS on
Your message dated Mon, 11 Oct 2021 22:05:17 +
with message-id
and subject line Bug#995689: fixed in python-biopython 1.78+dfsg-6
has caused the Debian Bug report #995689,
regarding python-reportlab breaks autopkgtest of python-biopython
to be marked as done.
This means that you claim that
On Sun, 3 Oct 2021 17:10:22 +0200 Kurt Roeckx wrote:
Package: lbeibiou
Version: 3.61.2-1
Severity: serious
Hi,
During an upgrade, I get the following:
dpkg: considering deconfiguration of lebiniou-data, which would be broken by
installation of lebiniou ...
dpkg: yes, will deconfigure
Processing commands for cont...@bugs.debian.org:
> affects 984399 src:pcl
Bug #984399 [src:vtk9] vtk9: ftbfs with GCC-11
Added indication that 984399 affects src:pcl
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984399:
Processing commands for cont...@bugs.debian.org:
> close 983976
Bug #983976 [src:ayatana-indicator-application] ayatana-indicator-application:
ftbfs with GCC-11
Marked Bug as done
> close 983980
Bug #983980 [src:ayatana-indicator-messages] ayatana-indicator-messages: ftbfs
with GCC-11
Marked
Your message dated Mon, 11 Oct 2021 20:28:34 +
with message-id
and subject line Bug#996168: fixed in retext 7.2.2-1
has caused the Debian Bug report #996168,
regarding retext does not start: xsettings.py:126 RuntimeError:
ffi_prep_cif_var failed
to be marked as done.
This means that you
Processing control commands:
> tags -1 patch
Bug #984353 [src:surf-alggeo] surf-alggeo: ftbfs with GCC-11
Added tag(s) patch.
--
984353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 patch
On Wed, 03 Mar 2021 16:17:45 + Matthias Klose wrote:
> ../../../yaccsrc/Script.cc: In static member function âstatic void
> Script::clearScreen()â:
> ../../../yaccsrc/Script.cc:910:23: error: reference to âbyteâ is ambiguous
> 910 | *intensity =
Processing control commands:
> reassign -1 src:python-biopython 1.78+dfsg-5
Bug #995689 [src:python-reportlab, src:python-biopython] python-reportlab
breaks autopkgtest of python-biopython
Bug reassigned from package 'src:python-reportlab, src:python-biopython' to
'src:python-biopython'.
No
Hello,
On Thu, 26 Aug 2021 12:08:03 +0200 Vincent Lefevre
wrote:
>
> After the upgrade to 15.0+dfsg1-2, pulseaudio no longer detects
> my bluetooth headphones when I switch them on.
As apparently there is a workaround and/or the problem is coming from
bluez, do you think we should keep
Processing control commands:
> tag -1 pending
Bug #996168 [retext] retext does not start: xsettings.py:126 RuntimeError:
ffi_prep_cif_var failed
Added tag(s) pending.
--
996168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996168
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Control: tag -1 pending
Hello,
Bug #996168 in retext 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 #996166 [docker.io] FTBFS: oci/devices_linux.go:15:16: undefined:
configs.Device
Added tag(s) pending.
--
996166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #996166 in docker.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:
Hi Afif,
On 10-10-2021 22:56, Afif Elghraoui wrote:
>> The test if timing out nowadays too, so I'll block it from being tested
>> to avoid stress on our infrastructure until this bug is fixed.
>
> This bug has been fixed for about a week now but nvchecker still appears
> to be blocked from
On Mon, Oct 11, 2021 at 06:17:51PM +, Thorsten Glaser wrote:
>> Is there any good reason why the plocate group would disappear
>> that you know of?
> Not that… wait, doesn’t schroot copy groups? Let me see…
>
> AH! It does! And since my main system is now
> bullseye, not sid,
Your message dated Mon, 11 Oct 2021 18:17:51 + (UTC)
with message-id
and subject line Re: Bug#996167: dpkg: unrecoverable fatal error, aborting:
unknown system group 'plocate' in statoverride file;
has caused the Debian Bug report #996167,
regarding dpkg: unrecoverable fatal error, aborting:
Source: glibmm2.4
Version: 2.66.2-1
Severity: serious
Tags: upstream ftbfs
Justification: Debian Policy 4.9
According to Debian Policy 4.9:
| For packages in the main archive, required targets must not attempt
| network access, except, via the loopback interface, to services on the
| build host
Your message dated Mon, 11 Oct 2021 18:07:44 +
with message-id
and subject line Bug#984407: fixed in xva-img 1.4.2-1
has caused the Debian Bug report #984407,
regarding xva-img: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
On Mon, Oct 11, 2021 at 07:33:19PM +0200, Thorsten Glaser wrote:
> Package: plocate
> Version: 1.1.12-1
> Severity: critical
> Justification: breaks unrelated software
> X-Debbugs-Cc: t...@mirbsd.de
>
> I'm encountering this:
>
> [... apt-get dist-upgrade ...]
Can you say something about what
Source: linux
Version: 5.10.70-1
Severity: serious
Tags: ftbfs patch upstream
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: nwfila...@gmail.com
Dear Maintainer,
Attempting to build kernel packages using the machinery of
Processing commands for cont...@bugs.debian.org:
> tags 995392 - moreinfo
Bug #995392 [ghostscript] ghostscript: ps2pdf trashes some characters
Removed tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
995392:
Dixi quod…
>dpkg: unrecoverable fatal error, aborting:
> unknown system group 'plocate' in statoverride file; the system group got
> removed
>before the override, which is most probably a packaging bug, to recover you
>can remove the override manually with dpkg-statoverride
Before I do that,
Package: retext
Version: 7.2.1-3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: re...@cs.unibo.it
Dear Maintainer,
This is the traceback of the error.
~$ retext
Using configuration file: /home/renzo/.config/ReText project/ReText.conf
Traceback (most recent call last):
Package: plocate
Version: 1.1.12-1
Severity: critical
Justification: breaks unrelated software
X-Debbugs-Cc: t...@mirbsd.de
I'm encountering this:
[... apt-get dist-upgrade ...]
Extracting templates from packages: 100%
Control: severity -1 minor
On 2021-10-11 17:35:04 +0200, Laurent Bigonville wrote:
> On Thu, 26 Aug 2021 12:08:03 +0200 Vincent Lefevre
> wrote:
>
> > After the upgrade to 15.0+dfsg1-2, pulseaudio no longer detects
> > my bluetooth headphones when I switch them on.
>
> As apparently there is a
Processing control commands:
> severity -1 minor
Bug #993011 [pulseaudio-module-bluetooth] pulseaudio-module-bluetooth: no
longer detects bluetooth headphones
Severity set to 'minor' from 'grave'
--
993011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993011
Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:cheesecutter
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user
Your message dated Mon, 11 Oct 2021 17:09:00 +
with message-id
and subject line Bug#994457: fixed in r-cran-gnm 1.1-1-3
has caused the Debian Bug report #994457,
regarding r-cran-gnm 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 984220 + confirmed
Bug #984220 [src:lnav] lnav: ftbfs with GCC-11
Added tag(s) confirmed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984220
Processing commands for cont...@bugs.debian.org:
> severity 979462 serious
Bug #979462 [aplus-fsf] aplus-fsf: FTBFS against glibc 2.32
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979462:
Processing commands for cont...@bugs.debian.org:
> tags 979462 + ftbfs bookworm sid
Bug #979462 [aplus-fsf] aplus-fsf: FTBFS against glibc 2.32
Added tag(s) sid, bookworm, and ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979462:
Dear Heather,
Please find attached the patch that I am going to apply to r-cran-gnm
in Debian.
With this patch applied, the test now works with both lapack 3.9 and
3.10.
Feel free to use it (or not) for the next release of gnm.
Best wishes,
Le lundi 27 septembre 2021 à 12:01 +0100, Heather
Control: tags -1 patch
The attached patch fixes the issue by updating the symbols file and
overriding dh_makeshlibs to use the upstream version and not failing on
changes to fix this permanently.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146
Processing control commands:
> tags -1 patch
Bug #984206 [src:libquazip] libquazip: ftbfs with GCC-11
Added tag(s) patch.
--
984206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Mon, 11 Oct 2021 17:01:22 +0200
with message-id
and subject line Re: mpfi: ftbfs with GCC-11
has caused the Debian Bug report #984240,
regarding mpfi: 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 the
Your message dated Mon, 11 Oct 2021 15:06:34 +
with message-id
and subject line Bug#995021: fixed in osmnx 1.1.1+ds-3
has caused the Debian Bug report #995021,
regarding osmnx: autopkgtest regression on armhf: iteration over a 0-d array
to be marked as done.
This means that you claim that
Source: ruby-rmagick
Version: 2.16.0-7
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-rmagick was found to fail to build in that
Source: ruby-eventmachine
Version: 1.3~pre20201020-b50c135-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-eventmachine was found to
Processing control commands:
> tags -1 pending
Bug #996146 [src:r-cran-maotai] r-cran-maotai FTBFS: dependencies 'labdsv',
'shapes', 'dbscan', 'RcppDist' are not available
Added tag(s) pending.
> block -1 by 995723
Bug #996146 [src:r-cran-maotai] r-cran-maotai FTBFS: dependencies 'labdsv',
Control: tags -1 pending
Control: block -1 by 995723
Am Mon, Oct 11, 2021 at 04:07:22PM +0300 schrieb Adrian Bunk:
> I: Building using R version 4.1.1-2
> I: R API version: r-api-4.0
> I: Using built-time from d/changelog: Mon, 04 Oct 2021 15:52:01 +0200
> mkdir -p
>
Control: severity 995392 grave
Control: severity 995678 normal
Control: tags 995678 - moreinfo
Please be careful with the bug numbers...
On 2021-10-11 08:27:55 +0900, Norbert Preining wrote:
> Then, this is by far not a grave bug in TL. pdflatex is **not**
> affected, since it generated pdf
Source: ruby-batch-loader
Version: 2.0.1+dfsg-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-batch-loader was found to fail to
Processing control commands:
> severity 995392 grave
Bug #995392 [ghostscript] ghostscript: ps2pdf trashes some characters
Severity set to 'grave' from 'normal'
> severity 995678 normal
Bug #995678 [texlive-base] texlive-base: pdflatex in TeX Live 2021 potentially
generates invalid PDF, making
Source: ruby-clean-test
Version: 1.0.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-clean-test was found to fail to build in
Source: ruby-ahoy-email
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-ahoy-email was found to fail to build in that
Source: origami-pdf
Version: 2.1.0-1~exp1
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, origami-pdf was found to fail to build in that
Source: obexftp
Version: 0.24-6
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, obexftp was found to fail to build in that situation.
To
Source: libsemanage
Version: 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, libsemanage was found to fail to build in that
Maybe this: https://bugs.freebsd.org/bugzilla//show_bug.cgi?id=257728
Processing control commands:
> reopen -1
Bug #995223 {Done: Matthias Klose } [src:libffi] libffi:
autoconf incompatibility causes baseline violation
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug
Control: reopen -1
Hello!
This did not fix the bug, unfortunately. libffi is still being built with
"-mcpu=power8" on ppc64, see the full build log in [1].
We didn't need --enable-portable before, so this isn't the issue but I assume
the problem is the new autoconf version which is not
Hello.
Same here after mariadb update
1:10.3.29-0+deb10u1 -> 1:10.3.31-0+deb10u1
After downgrade there is no corruptions.
We have i386 arch with amd64 kernel.
Regards,
JK
211010 17:47:31 mysqld_safe Starting mysqld daemon with databases from
/var/lib/mysql
2021-10-10 17:47:31 0 [Note]
Source: ruby-capybara
Version: 3.12.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-capybara was found to fail to build in that
Source: r-cran-maotai
Version: 0.2.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=r-cran-maotai=0.2.1-1
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/r-cran-maotai.html
...
dh_auto_install --destdir=debian/r-cran-maotai/ -O--buildsystem=R
Source: ruby-byebug
Version: 11.1.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-byebug was found to fail to build in that
Source: ruby-buff-config
Version: 2.0.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-buff-config was found to fail to build in
Source: ruby-bunny
Version: 2.14.4-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-bunny was found to fail to build in that
Source: ruby-bootsnap
Version: 1.4.6-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-bootsnap was found to fail to build in that
Your message dated Mon, 11 Oct 2021 13:03:23 +
with message-id
and subject line Bug#995597: fixed in bsdgames 2.17-29
has caused the Debian Bug report #995597,
regarding FTBFS: error: format not a string literal and no format arguments
to be marked as done.
This means that you claim that the
Source: ruby-bogus
Version: 0.1.6-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-bogus was found to fail to build in that
Source: ruby-bluefeather
Version: 0.41-5.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-bluefeather was found to fail to build in
Source: ruby-bio
Version: 2.0.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-bio was found to fail to build in that situation.
Source: ruby-binding-of-caller
Version: 0.7.2+debian1-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-binding-of-caller was found to
Source: ruby-beaker-hostgenerator
Version: 1.1.22-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-beaker-hostgenerator was found
Source: ruby-bindex
Version: 0.5.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-bindex was found to fail to build in that
Source: ruby-benchmark-memory
Version: 0.1.2-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-benchmark-memory was found to fail to
Source: ruby-barby
Version: 0.6.8+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-barby was found to fail to build in that
Source: clickhouse
Version: 18.16.1+ds-7.2
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/logs.php?pkg=clickhouse=18.16.1%2Bds-7.2%2Bb2
...
/<>/dbms/src/IO/copyData.cpp: In function ‘void
DB::copyData(DB::ReadBuffer&, DB::WriteBuffer&)’:
Source: ruby-backports
Version: 3.16.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-backports was found to fail to build in that
Source: ruby-axiom-types
Version: 0.1.1-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-axiom-types was found to fail to build in
Source: ruby-awesome-print
Version: 1.8.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-awesome-print was found to fail to build
Source: ruby-avl-tree
Version: 1.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-avl-tree was found to fail to build in that
Source: ruby-attr-encrypted
Version: 3.1.0-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-attr-encrypted was found to fail to build
Source: ruby-arbre
Version: 1.2.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-arbre was found to fail to build in that
Source: ruby-appraiser
Version: 0.2.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-appraiser was found to fail to build in that
Source: ruby-api-pagination
Version: 4.8.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-api-pagination was found to fail to build
Source: ruby-addressable
Version: 2.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-addressable was found to fail to build in
Source: ruby-acts-as-tree
Version: 2.8.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-acts-as-tree was found to fail to build
Control: tag -1 pending
Hello,
Bug #995597 in bsdgames 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 #995597 [src:bsdgames] FTBFS: error: format not a string literal and no
format arguments
Added tag(s) pending.
--
995597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Source: ruby-acts-as-list
Version: 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-acts-as-list was found to fail to build in
Source: ruby-activerecord-nulldb-adapter
Version: 0.4.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-activerecord-nulldb-adapter
Source: pry
Version: 0.13.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, pry was found to fail to build in that situation.
To
Source: r10k
Version: 3.7.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, r10k was found to fail to build in that situation.
To
Source: ruby-active-model-serializers
Version: 0.10.10-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-active-model-serializers was
Your message dated Mon, 11 Oct 2021 12:34:34 +
with message-id
and subject line Bug#995223: fixed in libffi 3.4.2-3
has caused the Debian Bug report #995223,
regarding libffi: autoconf incompatibility causes baseline violation
to be marked as done.
This means that you claim that the problem
Source: atig
Version: 0.6.1-6
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, atig was found to fail to build in that situation.
To
Source: libmodulemd
Version: 2.12.0-1
Severity: serious
Hello,
Without knowing all in and odds of libmodulemd, GObject introspection
override files are runtime files, not development files. That means that
the file must be moved to the gir1.2-modulemd-2.0 package (and the
python3 dependency
Your message dated Mon, 11 Oct 2021 12:15:01 +
with message-id
and subject line Bug#984181: fixed in htmlcxx 0.87-2
has caused the Debian Bug report #984181,
regarding htmlcxx: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Mon, 11 Oct 2021 12:15:23 +
with message-id
and subject line Bug#994150: fixed in licensecheck 3.2.13-1
has caused the Debian Bug report #994150,
regarding licensecheck FTBFS: test failures
to be marked as done.
This means that you claim that the problem has been dealt
Il 03/03/2021 17:15, Matthias Klose ha scritto:
Package: src:muffin
Version: 4.8.1-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the
1 - 100 of 121 matches
Mail list logo
