Package: racon
Version: 1.4.21-1
Severity: serious
X-Debbugs-Cc: ni...@thykier.net
Hi,
A new version of libedlib (with a new ABI) has been uploaded to
unstable and that causes racon to fail to build from source.
Relevant parts of the amd64 log:
```
> /usr/bin/cmake -E cmake_link_script
Source: yard
Version: 0.9.24-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, yard was found to fail to build in that situation.
To
Source: vagrant
Version: 2.2.14+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, vagrant was found to fail to build in that
Source: test-kitchen
Version: 1.23.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, test-kitchen was found to fail to build in that
Source: sup-mail
Version: 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, sup-mail was found to fail to build in that situation.
Source: rubygems
Version: 3.2.27-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, rubygems was found to fail to build in that situation.
Source: ruby-whitequark-parser
Version: 2.7.1.4-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-whitequark-parser was found to fail
Source: ruby-xmlrpc
Version: 0.3.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-xmlrpc was found to fail to build in that
Source: ruby-websocket
Version: 1.2.8-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-websocket was found to fail to build in that
Source: ruby-vips
Version: 2.0.17-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-vips was found to fail to build in that situation.
Source: ruby-vcr
Version: 6.0.0+really5.0.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-vcr was found to fail to build in that
Source: ruby-varia-model
Version: 0.6.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-varia-model was found to fail to build in
Source: ruby-vagrant-cloud
Version: 3.0.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-vagrant-cloud was found to fail to build
Source: ruby-typhoeus
Version: 1.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-typhoeus was found to fail to build in that
Source: ruby-tty-command
Version: 0.9.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-tty-command was found to fail to build in
Source: ruby-toml-rb
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-toml-rb was found to fail to build in that
Source: ruby-tilt
Version: 2.0.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-tilt was found to fail to build in that situation.
Source: ruby-terrapin
Version: 0.6.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-terrapin was found to fail to build in that
Source: ruby-stackprof
Version: 0.2.15-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-stackprof was found to fail to build in that
Source: ruby-spy
Version: 0.4.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-spy was found to fail to build in that situation.
Source: ruby-sprockets
Version: 3.7.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-sprockets was found to fail to build in that
Source: ruby-spring
Version: 2.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-spring was found to fail to build in that
Source: ruby-slop
Version: 4.6.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-slop was found to fail to build in that
Your message dated Thu, 14 Oct 2021 22:48:34 +
with message-id
and subject line Bug#984182: fixed in ignition-common 3.14.0+dfsg-1
has caused the Debian Bug report #984182,
regarding ignition-common: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> tag -1 pending
Bug #994833 [intel-opencl-icd] OpenCL programs abort when intel-opencl-icd is
installed
Added tag(s) pending.
--
994833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
On 22/09/2021 15.59, Giuseppe Bilotta wrote:
The virtual ABI package sounds like the best choice.
I've tried to implement this in src:intel-graphics-compiler and
src:intel-compute-runtime. Couldn't test the first one due to the gcc 11
ftbfs, but the second one does
On 14 October 2021 at 23:20, Sebastian Ramacher wrote:
| On 2021-10-14 15:52:03 -0500, Dirk Eddelbuettel wrote:
| >
| > Hi Sebastian,
| >
| > On 14 October 2021 at 22:46, Sebastian Ramacher wrote:
| > | Hi Dirk
| > |
| > | On 2021-08-30 16:27:49 -0500, Dirk Eddelbuettel wrote:
| > | >
| > |
Processing commands for cont...@bugs.debian.org:
> tags 984260 upstream fixed-upstream
Bug #984260 [src:nut] nut: ftbfs with GCC-11
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984260:
On 2021-10-14 15:52:03 -0500, Dirk Eddelbuettel wrote:
>
> Hi Sebastian,
>
> On 14 October 2021 at 22:46, Sebastian Ramacher wrote:
> | Hi Dirk
> |
> | On 2021-08-30 16:27:49 -0500, Dirk Eddelbuettel wrote:
> | >
> | > On 30 August 2021 at 23:42, Niko Tyni wrote:
> | > | Package: libgsl25
> |
Your message dated Thu, 14 Oct 2021 21:06:22 +
with message-id
and subject line Bug#984317: fixed in rheolef 7.1-7
has caused the Debian Bug report #984317,
regarding rheolef: 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 Thu, 14 Oct 2021 21:03:28 +
with message-id
and subject line Bug#996490: fixed in audacious-plugins 4.0.5-2
has caused the Debian Bug report #996490,
regarding audacious-plugins: cannot install last binNMU 4.0.5-1+b1
to be marked as done.
This means that you claim that the
Hi Sebastian,
On 14 October 2021 at 22:46, Sebastian Ramacher wrote:
| Hi Dirk
|
| On 2021-08-30 16:27:49 -0500, Dirk Eddelbuettel wrote:
| >
| > On 30 August 2021 at 23:42, Niko Tyni wrote:
| > | Package: libgsl25
| > | Version: 2.7+dfsg-2
| > | Control: affects -1 libmath-gsl-perl
| > |
Hi Dirk
On 2021-08-30 16:27:49 -0500, Dirk Eddelbuettel wrote:
>
> On 30 August 2021 at 23:42, Niko Tyni wrote:
> | Package: libgsl25
> | Version: 2.7+dfsg-2
> | Control: affects -1 libmath-gsl-perl
> | Severity: serious
> |
> | gsl 2.7 broke libmath-gsl-perl on runtime, as seen in the
Your message dated Thu, 14 Oct 2021 20:41:53 +
with message-id
and subject line Bug#991497: fixed in rust-ammonia 3.1.2-1
has caused the Debian Bug report #991497,
regarding RUSTSEC-2021-0074
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Processing control commands:
> severity -1 serious
Bug #996490 [audacious-plugins] audacious-plugins: cannot install last binNMU
4.0.5-1+b1
Severity set to 'serious' from 'normal'
--
996490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996490
Debian Bug Tracking System
Contact
Your message dated Thu, 14 Oct 2021 19:20:12 +
with message-id
and subject line Bug#984319: fixed in ri-li 2.0.1+ds-11
has caused the Debian Bug report #984319,
regarding ri-li: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Source: wlroots
Version: 0.12.0-2
Severity: serious
Tags: ftbfs
wlroots fails to build from source in unstable on amd64. A non-parallel
build now ends as follows:
| FAILED: examples/dmabuf-capture.p/dmabuf-capture.c.o
| cc -Iexamples/dmabuf-capture.p -Iexamples -I../examples -Iprotocol
Processing control commands:
> close -1 1.1.2-3
Bug #996496 [src:golang-gopkg-square-go-jose.v1]
src:golang-gopkg-square-go-jose.v1: fails to migrate to testing for too long:
uploader built arch:all binary
Marked as fixed in versions golang-gopkg-square-go-jose.v1/1.1.2-3.
Bug #996496
Source: golang-gopkg-square-go-jose.v1
Version: 1.1.2-2
Severity: serious
Control: close -1 1.1.2-3
X-Debbugs-CC: jel...@debian.org
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are
Processing control commands:
> tag -1 pending
Bug #984319 [src:ri-li] ri-li: ftbfs with GCC-11
Added tag(s) pending.
--
984319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984319
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #984319 in ri-li 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:
> close -1 3.32.2+dfsg1-3
Bug #996491 [src:gnome-authenticator] src:gnome-authenticator: fails to migrate
to testing for too long: uploader built arch:all
Marked as fixed in versions gnome-authenticator/3.32.2+dfsg1-3.
Bug #996491 [src:gnome-authenticator]
Processing control commands:
> close -1 0.0~git20190325.f02dbb0-3
Bug #996493 [src:golang-github-getlantern-hidden]
src:golang-github-getlantern-hidden: fails to migrate to testing for too long:
uploader built arch:all binary
Marked as fixed in versions
Source: golang-github-getlantern-hidden
Version: 0.0~git20190325.f02dbb0-2
Severity: serious
Control: close -1 0.0~git20190325.f02dbb0-3
X-Debbugs-CC: jel...@debian.org
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release
Source: gnome-authenticator
Version: 3.32.2+dfsg1-2
Severity: serious
Control: close -1 3.32.2+dfsg1-3
X-Debbugs-CC: jel...@debian.org
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are
Hi Georges,
On 14-10-2021 17:43, Georges Khaznadar wrote:
> If I upload another package, without the new features (and the new
> binary artifact), is there a chance that it will be taken in
> consideration by the build system ? I fear that it would compete with
> the other package in the NEW
Control: tags -1 + patch
Am 27.09.2021 um 22:25 schrieb Helmut Grohne:
> Source: horst
> Version: 5.1-2
> Severity: serious
> Tags: ftbfs
>
> horst fails to build from source in unstable on amd64 due to ncurses
> having become stricter about format strings. A build now ends as
> follows:
>
> |
Processing control commands:
> tags -1 + patch
Bug #995202 [src:horst] horst FTBFS: error: format not a string literal and no
format arguments
Added tag(s) patch.
--
995202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> reassign -1 src:pytorch 1.7.1-7
Bug #994423 [src:pytorch-vision] pytorch-vision: FTBFS on armhf: Illegal
instruction
Bug reassigned from package 'src:pytorch-vision' to 'src:pytorch'.
No longer marked as found in versions pytorch-vision/0.8.2-1.
Ignoring request to
Control: reassign -1 src:pytorch 1.7.1-7
Control: retitle -1 pytorch: Baseline violation on armhf
Control: affects -1 python3-torch src:pytorch-vision
On Wed, Sep 15, 2021 at 10:00:09PM +0200, Sebastian Ramacher wrote:
> Source: pytorch-vision
> Version: 0.8.2-1
> Severity: serious
> Tags: ftbfs
Your message dated Thu, 14 Oct 2021 17:54:31 +
with message-id
and subject line Bug#994424: fixed in spice-vdagent 0.20.0-3
has caused the Debian Bug report #994424,
regarding spice-vdagent FTBFS: error: ‘g_memdup’ is deprecated: Use 'g_memdup2'
instead [-Werror=deprecated-declarations]
to
Processing control commands:
> tags -1 + patch
Bug #995624 [src:pktstat] pktstat FTBFS: error: format not a string literal and
no format arguments [-Werror=format-security]
Added tag(s) patch.
--
995624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995624
Debian Bug Tracking System
Control: tags -1 + patch
Am 03.10.2021 um 12:00 schrieb Helmut Grohne:
> Source: pktstat
> Version: 1.8.5-7
> Severity: serious
> Tags: ftbfs
>
> pktstat fails to build from source in unstable on amd64. A non-parallel
> build ends as follows:
>
> | gcc -DHAVE_CONFIG_H -I.
Your message dated Thu, 14 Oct 2021 17:49:43 +
with message-id
and subject line Bug#995584: fixed in ht-el 2.3-2
has caused the Debian Bug report #995584,
regarding ht-el build-depends on removed transitional package.
to be marked as done.
This means that you claim that the problem has been
I fixed it and created a pull request upstream:
https://gitlab.com/bertoldia/gnome-shell-trash-extension/-/merge_requests/23
e46f76c9749d7758765ba274a212cfc2dcf3eeb8 is the first bad commit
commit e46f76c9749d7758765ba274a212cfc2dcf3eeb8
Author: Marko Mäkelä
Date: Mon Jun 21 12:34:07 2021 +0300
MDEV-15912: Remove traces of insert_undo
Let us simply refuse an upgrade from earlier versions if the
upgrade
Processing control commands:
> reassign -1 libleveldb1d
Bug #996486 [libleveldb1d] bitcoind: fails to start with undefined symbol:
_ZTIN7leveldb6LoggerE
Ignoring request to reassign bug #996486 to the same package
> affects -1 bitcoind
Bug #996486 [libleveldb1d] bitcoind: fails to start with
Control: reassign -1 libleveldb1d
Control: affects -1 bitcoind
Quoting Vincas Dargis (2021-10-14 19:16:00)
> Package: bitcoind
> Version: 22.0-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> Since 2021-10-12 bitcoind fails to start on my machine:
>
> ```
Processing control commands:
> reassign -1 libleveldb1d
Bug #996486 [bitcoind] bitcoind: fails to start with undefined symbol:
_ZTIN7leveldb6LoggerE
Bug reassigned from package 'bitcoind' to 'libleveldb1d'.
No longer marked as found in versions bitcoin/22.0-1.
Ignoring request to alter fixed
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package prometheus
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Package: bitcoind
Version: 22.0-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Since 2021-10-12 bitcoind fails to start on my machine:
```
# fgrep leveldb /var/log/syslog
Oct 12 20:00:34 vinco bitcoind[1103]: /usr/bin/bitcoind: symbol lookup error:
Processing commands for cont...@bugs.debian.org:
> close 984103 1.2.7-1
Bug #984103 [src:libedlib] libedlib: ftbfs with GCC-11
Marked as fixed in versions libedlib/1.2.7-1.
Bug #984103 [src:libedlib] libedlib: ftbfs with GCC-11
Marked Bug as done
> thanks
Stopping processing here.
Please contact
Your message dated Thu, 14 Oct 2021 16:18:41 +
with message-id
and subject line Bug#984004: fixed in briquolo 0.5.7-10
has caused the Debian Bug report #984004,
regarding briquolo: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Thu, 14 Oct 2021 16:18:35 +
with message-id
and subject line Bug#983986: fixed in berusky 1.7.2-2
has caused the Debian Bug report #983986,
regarding berusky: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing control commands:
> tag -1 pending
Bug #984004 [src:briquolo] briquolo: ftbfs with GCC-11
Added tag(s) pending.
--
984004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #984004 in briquolo 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 #983986 [src:berusky] berusky: ftbfs with GCC-11
Added tag(s) pending.
--
983986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #983986 in berusky 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:
Dear Paul,
thank you for your e-mail.
I believed that I fixed the FTBFS bug when I uploaded the release 4.2-1
of units-filter approximately one month ago. However, I probably did too
much work: I enriched the package with a new graphic user interface, so
the new package is now in the NEW queue.
Source: mp3blaster
Version: 1:3.2.6-2
Severity: serious
Tags: ftbfs
mp3blaster fails to build from source in unstable due to ncurses having
gained format string annotations. A non-parallel build now ends as
follows:
| g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/ncurses -I. -I/usr/include
Source: dvbstreamer
Version: 2.1.0-5.1
Severity: serious
Tags: sid bookworm
dvbstreamer fails building with autoconf 2.71. A build log of an
unrelated NMU can be seen at
https://buildd.debian.org/status/fetch.php?pkg=dvbstreamer=amd64=2.1.0-5.3=1634219631
(On my test machine there was still
Package: checkinstall
Version: 1.6.2+git20170426.d24a630-2
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch
X-Debbugs-Cc: sl...@ubuntu.com
Dear Maintainer,
Your message dated Thu, 14 Oct 2021 13:54:12 +
with message-id
and subject line Bug#991970: fixed in piuparts 1.1.5
has caused the Debian Bug report #991970,
regarding piuparts: ftbfs with golang-1.16
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Thu, 14 Oct 2021 13:33:26 +
with message-id
and subject line Bug#983971: fixed in asc 2.6.1.0-8
has caused the Debian Bug report #983971,
regarding asc: 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
Processing control commands:
> tag -1 pending
Bug #983971 [src:asc] asc: ftbfs with GCC-11
Added tag(s) pending.
--
983971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #983971 in asc 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, 14 Oct 2021 13:03:36 +
with message-id
and subject line Bug#996408: fixed in libepoxy 1.5.9-2
has caused the Debian Bug report #996408,
regarding libepoxy: autopkgtest failure: No such build data file as
On 13.10.2021 22.09, Paul Gevers wrote:
Source: libepoxy
Version: 1.5.9-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You recently added an autopkgtest to your package libepoxy, great.
However, it fails.
On Wed, 13 Oct 2021 10:58:34 +0200 =?UTF-8?Q?Bernhard_=c3=9cbelacker?=
wrote:
> On Tue, 28 Sep 2021 15:01:22 +0200 uninsubria.it
wrote:
>
> > example from 'dmesg' output:
> > [Tue Sep 28 11:05:22 2021] omshell[4604]: segfault at 0 ip
55623cdd06dc sp 7ffd5a2c7c78 error 4 in
On 14 October 2021 at 10:55, Paul Gevers wrote:
| Source: gsl
| Version: 2.6+dfsg-2
| Severity: serious
| Control: close -1 2.7+dfsg-2
| Tags: sid bookworm
| User: release.debian@packages.debian.org
| Usertags: out-of-sync
|
| Dear maintainer(s),
|
| The Release Team considers packages
Your message dated Thu, 14 Oct 2021 12:04:46 +
with message-id
and subject line Bug#996462: fixed in llvm-toolchain-13 1:13.0.0-5
has caused the Debian Bug report #996462,
regarding libc++-13-dev: uninstallable on s390x
to be marked as done.
This means that you claim that the problem has
On Thu, Oct 14, 2021 at 11:06:52AM +0200, Diederik de Haas wrote:
> On 7 Oct 2021 18:35:18 +0200 Francesco Poli wrote:
> > This seems to be exactly the same issue that was reported in #995448,
> > which is marked as affecting package apt-listbugs.
> >
> > However, I see that you are using
Hi, it appears that I cannot reproduce the issue on the armhf porterbox
amdahl.debian.org .
Cheers Jerome
OpenPGP_signature
Description: OpenPGP digital signature
Your message dated Thu, 14 Oct 2021 11:00:10 +
with message-id
and subject line Bug#790576: fixed in ghextris 0.9.0-4
has caused the Debian Bug report #790576,
regarding ghextris: depends on python-gnome2 which is deprecated
to be marked as done.
This means that you claim that the problem
Processing control commands:
> reopen -1
Bug #995021 {Done: Jerome Benoit } [src:osmnx] osmnx:
autopkgtest regression on armhf: iteration over a 0-d array
'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.
Control: reopen -1
Hi,
On 11-10-2021 17:09, Debian Bug Tracking System wrote:
> osmnx (1.1.1+ds-3) unstable; urgency=medium
> .
>* Debianization:
[...]
> - d/tests/control:
>- online tests:
> - Restrictions field, add needs-internet (Closes: #995021).
This doesn't
Le 14/10/2021 à 12:17, Sebastian Ramacher a écrit :
Package: libc++-13-dev
Version: 1:13.0.0-3
Severity: serious
Fixing #998510 causes installability issues on s390x:
$ apt-get install libc++-13-dev
Reading package lists...
Building dependency tree...
Reading state information...
Some packages
Upstream has removed all the dynamic exception specfications. I've
created a merge-request to add the upstream patch to the Debian Salsa
repo.
J.
signature.asc
Description: PGP signature
Package: libc++-13-dev
Version: 1:13.0.0-3
Severity: serious
Fixing #998510 causes installability issues on s390x:
$ apt-get install libc++-13-dev
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
Your message dated Thu, 14 Oct 2021 09:48:43 +
with message-id
and subject line Bug#994822: fixed in pat 0.10.0-2
has caused the Debian Bug report #994822,
regarding pat: /usr/bin/pat is already shipped by the (unrelated) dist package
to be marked as done.
This means that you claim that the
Tested upstream mariadb packages. 10.3.30 works, 10.3.31 fails.
--
Ondrej Zary
On Thursday 14 October 2021, Yves-Alexis Perez wrote:
> On Thu, 2021-10-14 at 00:03 -0700, Otto Kekäläinen wrote:
> > Right. Here is for Buster:
> >
> > https://salsa.debian.org/mariadb-team/mariadb-10.3/-/commit/8ccf2240960cbb609cedfeb269df22d43ccbba21
> >
On 7 Oct 2021 18:35:18 +0200 Francesco Poli wrote:
> This seems to be exactly the same issue that was reported in #995448,
> which is marked as affecting package apt-listbugs.
>
> However, I see that you are using oldstable: I don't know whether a
> fixed version of ruby-httpclient will ever be
Yeah, that's a little weird. And it only occurs on i386? Sounds like a
CGAL bug then.
On Wed, Oct 13, 2021 at 3:24 PM Drew Parsons wrote:
>
> On 2021-10-13 13:42, Nico Schlömer wrote:
> > Or PR upstream. I can merge and release any time.
>
> Thanks Nico. I'll check which tolerances it needs and
Source: healpix-cxx
Version: 3.60.0-2
Severity: serious
Control: close -1 3.80.0-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days
Processing control commands:
> close -1 3.80.0-1
Bug #996452 [src:healpix-cxx] src:healpix-cxx: fails to migrate to testing for
too long: soname bump (fixed in experimental)
Marked as fixed in versions healpix-cxx/3.80.0-1.
Bug #996452 [src:healpix-cxx] src:healpix-cxx: fails to migrate to
Processing control commands:
> close -1 2.7+dfsg-2
Bug #996451 [src:gsl] src:gsl: fails to migrate to testing for too long:
unresolved RC bug (found by autopkgtest breakage)
Marked as fixed in versions gsl/2.7+dfsg-2.
Bug #996451 [src:gsl] src:gsl: fails to migrate to testing for too long:
Source: gsl
Version: 2.6+dfsg-2
Severity: serious
Control: close -1 2.7+dfsg-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as
Processing control commands:
> close -1 1.7.1-1
Bug #996450 [src:scipy] src:scipy: fails to migrate to testing for too long:
build depends on blocked package and unresolved RC bug
Marked as fixed in versions scipy/1.7.1-1.
Bug #996450 [src:scipy] src:scipy: fails to migrate to testing for too
Source: scipy
Version: 1.6.0-2
Severity: serious
Control: close -1 1.7.1-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 992676 950598
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and
1 - 100 of 127 matches
Mail list logo
