Control: tags 966184 + patch
Control: tags 966184 + pending
--
Dear maintainer,
I've prepared an NMU for xfractint (versioned as 20.4.10-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.
--
Regards
Sudip
diff -u xfractint-20.4.10/debian/changelog
Processing control commands:
> tags 966184 + patch
Bug #966184 [src:xfractint] xfractint: FTBFS with GCC 10: multiple definition
of ... due to -fno-common
Added tag(s) patch.
> tags 966184 + pending
Bug #966184 [src:xfractint] xfractint: FTBFS with GCC 10: multiple definition
of ... due to
Control: tags 957996 + patch
Control: tags 957996 + pending
--
Dear maintainer,
I've prepared an NMU for xppaut (versioned as 6.11b+1.dfsg-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.
--
Regards
Sudip
diff -Nru xppaut-6.11b+1.dfsg/debian/changelog
Processing control commands:
> tags 957996 + patch
Bug #957996 [src:xppaut] xppaut: ftbfs with GCC-10
Added tag(s) patch.
> tags 957996 + pending
Bug #957996 [src:xppaut] xppaut: ftbfs with GCC-10
Added tag(s) pending.
--
957996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957996
Debian
Your message dated Wed, 16 Dec 2020 17:33:40 +
with message-id
and subject line Bug#970580: fixed in licenseutils 0.0.9-4
has caused the Debian Bug report #970580,
regarding licenseutils: Memory access error
to be marked as done.
This means that you claim that the problem has been dealt
Dear Maintainer,
after adding
#include
in qt/trafficgraphwidget.cpp, litecoin builds fine in a pbuilder
sid chroot.
Kind Regards
Processing control commands:
> block 975535 by -1
Bug #975535 [src:elpy] elpy's autopkg tests fail with Python 3.9
975535 was not blocked by any bugs.
975535 was not blocking any bugs.
Added blocking bug(s) of 975535: 977558
--
975535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975535
Your message dated Wed, 16 Dec 2020 19:18:27 +
with message-id
and subject line Bug#977222: fixed in dolfin 2019.2.0~git20200629.946dbd3+lfs-4
has caused the Debian Bug report #977222,
regarding dolfin: FTBFS: error: ‘min_element’ is not a member of ‘std’; did you
mean ‘tuple_element’?
to be
On Wed, Dec 16, 2020 at 04:43:55PM +0100, Emmanuel Bourg wrote:
> Le 13/12/2020 à 00:38, Markus Koschany a écrit :
>
> > In this case I believe the RC severity is correct because the arch:any or
> > jni
> > version of the package FTBFS on ppc64el. We should try to fix the problem on
> > ppc64el
Source: gnutls28
Version: 3.6.15-1
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source
Forwarded: https://gitlab.com/gnutls/gnutls/-/issues/1135
autopkgtests and build fail now due to an expired certificate
Not After : Dec 13 08:24:54 2020 GMT
cu Andreas
Control: tag -1 pending
Hello,
Bug #976578 in golang-github-labstack-gommon 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 #976578 [src:golang-github-labstack-gommon] golang-github-labstack-gommon:
FTBFS on arm64,ppc64el (arch:all-only src pkg): dh_auto_test: error: cd
obj-aarch64-linux-gnu && go test -vet=off -v -p 4 github.com/labstack/gommon
Your message dated Wed, 16 Dec 2020 18:33:26 +
with message-id
and subject line Bug#976578: fixed in golang-github-labstack-gommon 0.2.6-2
has caused the Debian Bug report #976578,
regarding golang-github-labstack-gommon: FTBFS on arm64,ppc64el (arch:all-only
src pkg): dh_auto_test: error:
On Wed, Dec 09, 2020 at 01:27:11PM +0100, Adam Borowski wrote:
> On Wed, Dec 09, 2020 at 09:39:08AM +0100, Lucas Nussbaum wrote:
> > Source: memkind
> > Version: 1.10.1-1
>
> > During a rebuild of all packages in sid, your package failed to build
> > on ppc64el. At the same time, it did not fail
Processing commands for cont...@bugs.debian.org:
> forwarded 976939 https://github.com/golang/go/issues/43222
Bug #976939 [src:golang-golang-x-arch] golang-golang-x-arch: FTBFS on ppc64el
(arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu &&
go test -vet=off -v -p 160
Package: src:libxmlada
Version: 21.0.0-2
Severity: serious
Tags: sid bullseye
see at
https://ci.debian.net/data/autopkgtest/testing/amd64/libx/libxmlada/8859011/log.gz
autopkgtest [19:16:13]: test link-with-shared: [---
gprbuild: raised CONSTRAINT_ERROR : gpr-proc.adb:696
Your message dated Wed, 16 Dec 2020 17:04:41 +
with message-id
and subject line Bug#975845: fixed in ruby-redis 4.2.5-1
has caused the Debian Bug report #975845,
regarding ruby-redis: FTBFS: ERROR: Test "ruby2.7" failed.
to be marked as done.
This means that you claim that the problem has
Control: tag -1 pending
Hello,
Bug #970580 in licenseutils 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 #970580 [licenseutils] licenseutils: Memory access error
Added tag(s) pending.
--
970580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Wed, 16 Dec 2020 17:18:50 +
with message-id
and subject line Bug#973171: fixed in scapy 2.4.4-3
has caused the Debian Bug report #973171,
regarding dhcpcanon: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.9 3.8" returned exit code 13
to
Your message dated Wed, 16 Dec 2020 18:03:29 +
with message-id
and subject line Bug#977408: fixed in gcc-11 11-20201216-1
has caused the Debian Bug report #977408,
regarding libstdc++-11-doc: missing Conflicts: libstdc++-10-doc
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 16 Dec 2020 18:03:29 +
with message-id
and subject line Bug#977409: fixed in gcc-11 11-20201216-1
has caused the Debian Bug report #977409,
regarding libgm2-17: contains only libraries with SOVERSION 15
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 16 Dec 2020 18:03:29 +
with message-id
and subject line Bug#977461: fixed in gcc-11 11-20201216-1
has caused the Debian Bug report #977461,
regarding gcc-1[01]-offload-amdgcn,gcc-1[01]-hppa64-linux-gnu: shipping
unversioned binaries causes file conflicts
to be marked
Control: severity -1 import
On Sun, Dec 13, 2020 at 2:15 AM Andreas Henriksson wrote:
>
> Hello!
>
> On Wed, Dec 09, 2020 at 10:03:39AM +0100, Lucas Nussbaum wrote:
> > Source: golang-github-coreos-bbolt
> > Version: 1.3.5-1
> > Severity: serious
> > Justification: FTBFS on ppc64el
> > Tags:
Processing commands for cont...@bugs.debian.org:
> severity 976926 important
Bug #976926 [src:golang-github-coreos-bbolt] golang-github-coreos-bbolt: FTBFS
on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd
obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 -short go.etcd.io/bbolt
Your message dated Wed, 16 Dec 2020 14:52:04 +
with message-id
and subject line Bug#974210: fixed in pytorch 1.7.1-1
has caused the Debian Bug report #974210,
regarding pytorch's autopkg tests fail
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 16 Dec 2020 16:19:36 +
with message-id
and subject line Bug#977134: fixed in qtmir 0.6.1-5
has caused the Debian Bug report #977134,
regarding qtmir-tests: Cannot fulfill the dependencies
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 16 Dec 2020 12:56:36 +
with message-id
and subject line Bug#977235: fixed in sentencepiece 0.1.94-2
has caused the Debian Bug report #977235,
regarding sentencepiece FTBFS on armel/mipsel: undefined reference to
`__atomic_fetch_add_8'
to be marked as done.
This means
Package: bpftrace
Version: 0.11.3-3
Severity: grave
Justification: renders package unusable
Any attempt of running bpftrace programs fails on my sid workstation:
$ sudo bpftrace -e 'kprobe:do_nanosleep { printf("PID %d sleeping\n", pid); }'
Two passes with the same argument (-tti) attempted to
Le 13/12/2020 à 00:38, Markus Koschany a écrit :
> In this case I believe the RC severity is correct because the arch:any or jni
> version of the package FTBFS on ppc64el. We should try to fix the problem on
> ppc64el or, if upstream doesn't support ppc64el, remove the architecture from
> the
Package: src:gprbuild
Version: 2021.0.0.0778b109-3
Severity: serious
Tags: sid bullseye
two tests fail:
autopkgtest [18:06:29]: test gpr-wrapper: [---
==Messages for file:
/tmp/autopkgtest-lxc.a8l7fm0h/downtmp/autopkgtest_tmp/p.gpr
1. with "gpr.gpr";
Processing control commands:
> block 975535 by -1
Bug #975535 [src:elpy] elpy's autopkg tests fail with Python 3.9
975535 was blocked by: 977558
975535 was not blocking any bugs.
Added blocking bug(s) of 975535: 977563
--
975535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975535
977563:
Processing commands for cont...@bugs.debian.org:
> close 975187 0.1.15-2
Bug #975187 [src:rust-libmount] rust-libmount: FTBFS: build-dependency not
installable: librust-nix-0.16+default-dev
Marked as fixed in versions rust-libmount/0.1.15-2.
Bug #975187 [src:rust-libmount] rust-libmount: FTBFS:
Control: tag -1 pending
Hello,
Bug #977243 in ceph 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 957499 + patch
Control: tags 957499 + pending
--
Dear maintainer,
I've prepared an NMU for logtools (versioned as 0.13e+nmu1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.
--
Regards
Sudip
diff -Nru logtools-0.13e/changes.txt
Processing control commands:
> tags 957499 + patch
Bug #957499 [src:logtools] logtools: ftbfs with GCC-10
Added tag(s) patch.
> tags 957499 + pending
Bug #957499 [src:logtools] logtools: ftbfs with GCC-10
Added tag(s) pending.
--
957499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957499
Your message dated Wed, 16 Dec 2020 21:34:11 +
with message-id
and subject line Bug#975771: fixed in fbxkb 0.6-2.1
has caused the Debian Bug report #975771,
regarding fbxkb: FTBFS: fbxkb.c:17:10: fatal error: gtk/gtk.h: No such file or
directory
to be marked as done.
This means that you
Your message dated Wed, 16 Dec 2020 21:34:11 +
with message-id
and subject line Bug#975673: fixed in fbxkb 0.6-2.1
has caused the Debian Bug report #975673,
regarding fbxkb: requires gdk-pixbuf-xlib-2.0.pc but does not build-depend on a
package containing it
to be marked as done.
This means
Your message dated Wed, 16 Dec 2020 21:49:55 +
with message-id
and subject line Bug#977449: fixed in scram 0.16.2-2
has caused the Debian Bug report #977449,
regarding slic3r: FTBFS with boost 1.74
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
severity 976909 normal
tags 976909 +moreinfo
thanks
Hi Lucas,
thanks for filing the bug. But I cannot reproduce this failure
and it looks like the last upload of the package h2o into the
archive was successfully built of ppc64el [1].
Could you please check your setup and provide more
Processing commands for cont...@bugs.debian.org:
> severity 976909 normal
Bug #976909 [src:h2o] h2o: FTBFS on ppc64el: ld:
/usr/lib/gcc/powerpc64le-linux-gnu/10/../../../powerpc64le-linux-gnu/Scrt1.o:(.data.rel.ro.local+0x8):
undefined reference to `main'
Severity set to 'normal' from 'serious'
I have checked and your package can easily be switched to the unversioned
dev-package.
Regards
Anton
Your message dated Wed, 16 Dec 2020 22:33:38 +
with message-id
and subject line Bug#957378: fixed in isoqlog 2.2.1-9.1
has caused the Debian Bug report #957378,
regarding isoqlog: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Control: tag -1 patch
Just submitted a MR which fixes this issue:
https://salsa.debian.org/debian/raspi-firmware/-/merge_requests/18
signature.asc
Description: This is a digitally signed message part.
Processing control commands:
> tag -1 patch
Bug #975943 [raspi-firmware] raspi-firmware: arm_64bit is missing and
linux-image-arm64 unbootable
Added tag(s) patch.
--
975943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Source: xml-security-c
Severity: serious
Tags: patch upstream
Hi,
xalan-c 1.12 is currently in experimental and contains some changes that
cause xml-security-c to FTBFS.
The attached quilt patch contains the necessary updates and allows for
compilation with either 1.11 and 1.12.
Best regards,
Processing commands for cont...@bugs.debian.org:
> # boost 1.74 is the default in unstable
> severity 975590 serious
Bug #975590 {Done: Chris Hofstaedtler } [pdns] pdns: FTBFS
against boost_1.74
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if
Processing commands for cont...@bugs.debian.org:
> fixed 975660 0.16.2-2
Bug #975660 [scram] scram: FTBFS against boost_1.74
There is no source info for the package 'scram' at version '0.16.2-2' with
architecture ''
Unable to make a source version for version '0.16.2-2'
Marked as fixed in
Processing commands for cont...@bugs.debian.org:
> reopen 977449
Bug #977449 {Done: Anton Gladky } [slic3r] slic3r: FTBFS with
boost 1.74
'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 reopened
No
Your message dated Wed, 16 Dec 2020 23:00:26 +0100
with message-id
and subject line Close
has caused the Debian Bug report #975660,
regarding scram: FTBFS against boost_1.74
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Processing control commands:
> tag -1 pending
Bug #977243 [src:ceph] ceph FTBFS with Boost 1.74
Added tag(s) pending.
--
977243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Wed, 16 Dec 2020 20:48:46 +
with message-id
and subject line Bug#977409: fixed in gcc-11 11-20201216-2
has caused the Debian Bug report #977409,
regarding libgm2-17: contains only libraries with SOVERSION 15
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 16 Dec 2020 20:48:46 +
with message-id
and subject line Bug#977461: fixed in gcc-11 11-20201216-2
has caused the Debian Bug report #977461,
regarding gcc-1[01]-offload-amdgcn,gcc-1[01]-hppa64-linux-gnu: shipping
unversioned binaries causes file conflicts
to be marked
[Matthias Klose]
> /<>/source/corvusoft/restbed/response.cpp: In member function
> ‘void restbed::Response::get_header(const string&, long long int&, long long
> int) const’:
> /<>/source/corvusoft/restbed/response.cpp:146:23: error: ISO C++
> forbids declaration of ‘invalid_argument’ with no
Your message dated Wed, 16 Dec 2020 20:48:46 +
with message-id
and subject line Bug#977408: fixed in gcc-11 11-20201216-2
has caused the Debian Bug report #977408,
regarding libstdc++-11-doc: missing Conflicts: libstdc++-10-doc
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 16 Dec 2020 22:19:21 +
with message-id
and subject line Bug#975167: fixed in supercollider 1:3.11.2+repack-1
has caused the Debian Bug report #975167,
regarding supercollider: FTBFS: ../QtCollider/primitives/prim_QPen.cpp:37:21:
error: aggregate ‘QPainterPath path’
Your message dated Wed, 16 Dec 2020 22:19:01 +
with message-id
and subject line Bug#977282: fixed in ros-roscpp-core 0.7.2-5
has caused the Debian Bug report #977282,
regarding libroscpp-core-dev has a runtime dependency on runtime libraries
without depending on these
to be marked as done.
Your message dated Wed, 16 Dec 2020 22:19:21 +
with message-id
and subject line Bug#975667: fixed in supercollider 1:3.11.2+repack-1
has caused the Debian Bug report #975667,
regarding supercollider: FTBFS against boost_1.74
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 16 Dec 2020 20:39:04 +
with message-id
and subject line Bug#977260: fixed in svgpp 1.3.0+dfsg1-4
has caused the Debian Bug report #977260,
regarding all autopkg tests fail with boost1.74
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 16 Dec 2020 08:39:40 +
with message-id
and subject line Bug#973605: fixed in odoo 14.0.0+dfsg.2-1
has caused the Debian Bug report #973605,
regarding odoo: Multiple privacy-breach-generic (fetching data from an external
website at runtime)
to be marked as done.
This
Your message dated Wed, 16 Dec 2020 23:39:56 +
with message-id
and subject line Bug#977551: fixed in gprbuild 2021.0.0.0778b109-4
has caused the Debian Bug report #977551,
regarding gprbuild's autopkg tests fail
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 17 Dec 2020 00:04:53 +
with message-id
and subject line Bug#977185: fixed in nheko 0.7.2-3
has caused the Debian Bug report #977185,
regarding nheko: switch to Boost 1.74
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
tags 977226 +pending +patch
user team+bo...@tracker.debian.org
usertag 977226 +boost174
thanks
Dear maintainer,
I have prepared an NMU (versioned as 0.46.0-1.1) and
uploaded to DELAYED/5.
Please feel free to tell me if I should delay it longer, cancel
or reschedule.
Diff is attached. MR is
Processing commands for cont...@bugs.debian.org:
> tags 977226 +pending +patch
Bug #977226 [src:openmw] openmw FTBFS: error: ‘for_each’ is not a member of
‘std’
Added tag(s) pending.
Bug #977226 [src:openmw] openmw FTBFS: error: ‘for_each’ is not a member of
‘std’
Added tag(s) patch.
> user
Hi Peter,
are you sure about your bug report?
The control file of osmo-bsc/1.6.1+dfsg1-3 contains:
Build-Depends: debhelper-compat (= 12),
pkg-config,
libosmocore-dev (>= 1.4.0),
libosmo-sccp-dev (>= 1.3.0),
On 16/12/2020 21:48, Thorsten Alteholz wrote:
Hi Peter,
are you sure about your bug report?
The control file of osmo-bsc/1.6.1+dfsg1-3 contains:
Build-Depends: debhelper-compat (= 12),
pkg-config,
libosmocore-dev (>= 1.4.0),
Processing commands for cont...@bugs.debian.org:
> block 973905 by 972803
Bug #973905 [src:python-typing-inspect] python-typing-inspect's autopkg test
fails
973905 was not blocked by any bugs.
973905 was not blocking any bugs.
Added blocking bug(s) of 973905: 972803
> fixed 973905 0.6.0-2
Bug
block 973905 by 972803
fixed 973905 0.6.0-2
thanks
This bug has been fixed in git [1], but can't be uploaded since the
package doesn't build with python 3.9 (#972803).
[1]:
https://salsa.debian.org/python-team/packages/python-typing-inspect/-/commit/7d1368bad8b2a76c83018195bb35fe85ebc480d2
--
Hi Alexandre,
Any update on this bug?
It's stopping the migration to testing and it would be nice to have
this tool in the next stable release of Debian.
Thanks!
--
Martin Michlmayr
https://www.cyrius.com/
https://salsa.debian.org/3dprinting-team/cura/-/commit/871fcb258aa11077c3a6e16651fbcb44953e932e
did not build cf.
https://salsa.debian.org/3dprinting-team/cura/-/pipelines/205268
Best regards
Heinrich
Your message dated Wed, 16 Dec 2020 09:33:53 +
with message-id
and subject line Bug#975843: fixed in sopt 3.0.1-11
has caused the Debian Bug report #975843,
regarding sopt: FTBFS: core.h:270: undefined reference to
`fmt::v6::internal::assert_fail(char const*, int, char const*)'
to be marked
Processing commands for cont...@bugs.debian.org:
> notfound 976420 1:12.1.4-1
Bug #976420 {Done: =?utf-8?q?Jos=C3=A9_Luis_Blanco_Claraco?=
} [src:mrpt] mrpt: ftbfs with libjsoncpp/experimental
The source 'mrpt' and version '1:12.1.4-1' do not appear to match any binary
packages
No longer marked
Processing commands for cont...@bugs.debian.org:
> # reproducible in buster but not in stretch
> tags 975242 + buster bullseye sid
Bug #975242 [openjade] segfault on all architectures if recompiled as of today
Added tag(s) bullseye, buster, and sid.
> thanks
Stopping processing here.
Please
73 matches
Mail list logo
