Processing commands for cont...@bugs.debian.org:
> tags 972806 + upstream
Bug #972806 [src:mbedtls] mbedtls security advisories: local side channel
attacks
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
972806: https://bugs.debian.org/cgi-
Your message dated Sat, 24 Oct 2020 06:03:31 +
with message-id
and subject line Bug#972592: fixed in mdtraj 1.9.4+git20201015.068f29a-2
has caused the Debian Bug report #972592,
regarding mdtraj should be Architecture: any-amd64 arm64
to be marked as done.
This means that you claim that the p
Package: nvidia-legacy-340xx-driver
Version: 340.108-7
Followup-For: Bug #972430
Thank you for using the patch I discovered.
Just a heads up. 5.9 has reached testing today and version -8 of nvidia legacy
has not reached unstable yet (at least in the mirror I use).
So, I have put linux-image-amd64
Earlier this year, an issue was filed for security advisories in April:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963159
Source: cura-engine
Version: 1:4.7.1-1
Severity: serious
Tags: ftbfs
A native build of cura-engine on unstable amd64 ends with:
| [ 86%] Building CXX object
CMakeFiles/SparseGridTest.dir/tests/utils/SparseGridTest.cpp.o
| /usr/bin/c++ -DARCUS -DBUILD_TESTS -DBUILD_TESTS=1
-I/usr/include/polycli
Source: mbedtls
Version: 2.16.0-1
Severity: serious
Tags: security
Justification: security
Dear Maintainer,
Mbed TLS 2.16.8 released 1 Sep 2020 addresses 3 security advisories
==> Please update mbedtls in all active Debian releases. Thank you.
https://github.com/ARMmbed/mbedtls/releases
https:/
23.10.2020 19:50, Sebastian Ramacher wrote:
Source: qemu
Version: 1:5.1+dfsg-4
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
binNMUs of qemu for the libbrlapi transition failed to build on armel
and armhf:
| /<>/lin
On Sat, 2020-10-24 at 03:06 +, kpcyrd wrote:
> Yes, running the build.py script would cause reproducible builds issues
> because it's used to take snapshots of Mozilla's trusted root CA
> certificates.
Hmm, I assume that is because it would build from the current snapshot
each time it is run?
On Sat, Oct 24, 2020 at 09:42:40AM +0800, Paul Wise wrote:
> Source: rust-webpki-roots
> Severity: serious
> Tags: security
> X-Debbugs-Cc: Debian Security Team , kpcyrd
>
> Usertags: embed
>
> rust-webpki-roots is essentially a duplicate of ca-certificates.
>
> https://tracker.debian.org/pkg/c
Source: rust-webpki-roots
Severity: serious
Tags: security
X-Debbugs-Cc: Debian Security Team , kpcyrd
Usertags: embed
rust-webpki-roots is essentially a duplicate of ca-certificates.
https://tracker.debian.org/pkg/ca-certificates
https://wiki.debian.org/EmbeddedCopies
AFAICT, rebuilding the p
Your message dated Fri, 23 Oct 2020 22:19:04 +
with message-id
and subject line Bug#972430: fixed in nvidia-graphics-drivers-legacy-340xx
340.108-8
has caused the Debian Bug report #972430,
regarding nvidia-legacy-340xx-driver: Fails to build with kernel 5.9
to be marked as done.
This means
Your message dated Fri, 23 Oct 2020 22:00:13 +
with message-id
and subject line Bug#971721: fixed in mailcap 3.65
has caused the Debian Bug report #971721,
regarding mime-support: missing dependency on perl
to be marked as done.
This means that you claim that the problem has been dealt with.
On Thu, 22 Oct 2020 at 21:47, Simon McVittie wrote:
>
> On Thu, 22 Oct 2020 at 19:14:54 +0100, David Miguel Susano Pinto wrote:
>> gnome-boxes does not start. Trying from command line, issues this error:
>>
>> $ gnome-boxes
>> gnome-boxes: symbol lookup error:
>> /usr/lib/x86_64-linux-gn
On Sun, Oct 18, 2020 at 08:27:30PM +, Joerg Jaspert wrote:
> Hi Maintainer,
>
> c002350518c0bbe87a18994ec6869411 10347 FIXME-(source.section) optional
> rust-kmon_1.3.0-1_amd64.buildinfo
> f6f32a721903d3c2fa78fc2e6b095695 2391 FIXME-(source.section) optional
> rust-kmon_1.3.0-1.dsc
>
> Uh
Your message dated Fri, 23 Oct 2020 14:48:27 -0400
with message-id <87lffw6ao4@digitalmercury.dynalias.net>
and subject line Re: Bug#971214: elpy: FTBFS: tests failed
has caused the Debian Bug report #971214,
regarding elpy: FTBFS: tests failed
to be marked as done.
This means that you claim t
Hi Otto,
On Fri, Oct 23, 2020 at 09:03:16AM +0300, Otto Kekäläinen wrote:
> Hello!
>
> Thanks!
>
> Bullseye is meant to ship with 10.5 and 10.3 should be removed once
> 10.5 has been in Debian testing for a while (currently still in Debian
> unstable due to debci false positive).
Thanks, this s
Source: hg-git
Version: 0.9.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, dulw...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:dulwich
Dear maintainer(s),
With a recent upload of dulwich the autopkgtest of
Processing control commands:
> affects -1 src:dulwich
Bug #972793 [src:hg-git] hg-git: autopkgtest needs update for new version of
dulwich: lots of deprecation *warnings*
Added indication that 972793 affects src:dulwich
--
972793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972793
Debian
On Sat, Oct 17, 2020 at 08:20:10PM +0300, Dmitry Shachnev wrote:
> As this failure is blocking the Qt 5.15 transition, I have uploaded the
> attached debdiff as NMU to DELAYED/5.
It built fine on most architectures, but unfortunately it FTBFS on armel,
so I have to do one more upload to let the ne
Source: qemu
Version: 1:5.1+dfsg-4
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
binNMUs of qemu for the libbrlapi transition failed to build on armel
and armhf:
| cc -iquote /<>/b/qemu/linux-user/m68k -iquote linux-user/m
Processing control commands:
> forwarded -1 https://bugs.launchpad.net/hplip/+bug/1901209
Bug #972339 [printer-driver-hpcups] armhf: hpcups crashes with free() invalid
pointer for some printers
Set Bug forwarded-to-address to 'https://bugs.launchpad.net/hplip/+bug/1901209'.
--
972339: https://b
Control: forwarded -1 https://bugs.launchpad.net/hplip/+bug/1901209
Le vendredi, 23 octobre 2020, 09.42:59 h CEST Didier 'OdyX' Raboud a écrit :
> As this is testable at build-time, I'll add a test for this and upload this
> to experimental. I'll report this to upstream today.
Damn. It seems the
On Fri, Oct 23, 2020 at 03:27:23PM +0200, Guillem Jover wrote:
> If we want to support the interim versions that have never been in a
> stable release, then I think the only way is to bump the minmum
> version in liburing shlibs and symbols files to 0.7, then rebuild the
> couple of packages built
Control: forwarded -1 https://github.com/axboe/liburing/issues/228
Hi!
On Fri, 2020-10-23 at 12:20:30 +0200, Steinar H. Gunderson wrote:
> On Fri, Oct 23, 2020 at 11:33:41AM +0200, Julien Cristau wrote:
> > https://github.com/axboe/liburing/commit/25bbcbef3e0a8bfba8044be55d08d5116c51dccd
> > seem
Processing control commands:
> forwarded -1 https://github.com/axboe/liburing/issues/228
Bug #972758 [liburing1] ABI breakage without soname bump
Set Bug forwarded-to-address to 'https://github.com/axboe/liburing/issues/228'.
--
972758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972758
De
Your message dated Fri, 23 Oct 2020 13:03:41 +
with message-id
and subject line Bug#972664: fixed in kdepim-runtime 4:20.08.2-3
has caused the Debian Bug report #972664,
regarding kdepim-runtime trying to overwrite kcm_ldap.so from
libkf5libkdepim-plugins
to be marked as done.
This means tha
So,
The current head of tree currently fails correctly when it tries to
build against all pythons and fails.
Unfortunately cython3 doesn't appeat to generate code (in some cases)
that works with python 3.9 :
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG
-g -fwra
Processing commands for cont...@bugs.debian.org:
> tags 972762 + upstream pending
Bug #972762 [src:bornagain] bornagain doesn't correctly detects python3.9
Added tag(s) upstream and pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
972762: https://bugs.debi
Your message dated Fri, 23 Oct 2020 12:33:52 +
with message-id
and subject line Bug#972596: fixed in kmail 4:20.08.2-3
has caused the Debian Bug report #972596,
regarding kmail: archivemailwidgettest hangs on armhf/mipsel
to be marked as done.
This means that you claim that the problem has be
Processing commands for cont...@bugs.debian.org:
> severity 972664 serious
Bug #972664 [kdepim-runtime] kdepim-runtime trying to overwrite kcm_ldap.so
from libkf5libkdepim-plugins
Severity set to 'serious' from 'important'
> tags 972664 + pending
Bug #972664 [kdepim-runtime] kdepim-runtime trying
Your message dated Fri, 23 Oct 2020 12:04:48 +
with message-id
and subject line Bug#972224: fixed in zanshin 0.5.71-2
has caused the Debian Bug report #972224,
regarding zanshin: FTBFS against KDEPIM 20.08
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Fri, 23 Oct 2020 11:48:33 +
with message-id
and subject line Bug#972226: fixed in kjots 4:5.0.2-3
has caused the Debian Bug report #972226,
regarding kjots: FTBFS with KDEPIM 20.08
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Fri, 23 Oct 2020 11:33:35 +
with message-id
and subject line Bug#972589: fixed in kitinerary 20.08.2-4
has caused the Debian Bug report #972589,
regarding kitinerary FTBFS on mipsel/mips64el/riscv64: test failures
to be marked as done.
This means that you claim that the pro
On 10/7/20 10:33 PM, Paul Gevers wrote:
> Hi Matthias,
>
> On 21-09-2020 17:52, Paul Gevers wrote:
>>> Apparently
>>> the very same tests don't time out on the buildds.
>>
>> I don't know what timeouts apply to buildds, but indeed I think they are
>> much higher to cope with *building* some extrem
Processing commands for cont...@bugs.debian.org:
> tags 972589 + pending
Bug #972589 [src:kitinerary] kitinerary FTBFS on mipsel/mips64el/riscv64: test
failures
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
972589: https://bugs.debian.org/
Your message dated Fri, 23 Oct 2020 10:50:06 +
with message-id
and subject line Bug#972730: fixed in python-mpd 1.1.0-3
has caused the Debian Bug report #972730,
regarding python-mpd: autopkgtest fails when two python3 versions are supported
to be marked as done.
This means that you claim tha
The actual error seems to be:
#0 0x7fff8e95743c llvm::sys::PrintStackTrace(llvm::raw_ostream&)
/<>/llvm/lib/Support/Unix/Signals.inc:533:13
#1 0x7fff8e9577a0 PrintStackTraceSignalHandler(void*)
/<>/llvm/lib/Support/Unix/Signals.inc:593:3
#2 0x7fff8e954df8 llvm::sys::RunSignalHand
On Fri, Oct 23, 2020 at 12:41:36PM +0200, Julien Cristau wrote:
> All that's needed is a 0.8 release I guess.
Yes, that would fix it. Optionally, one would require something like
a Breaks: liburing (<< 0.7-2) added on all packages compiled against
liburing, plus versioned Breaks on liburing1 on al
Package: mariadb-client-10.3
Version: 1:10.3.25-0+deb10u1
Severity: grave
Hello,
on start mytop a get:
[quote]
> mytop
/usr/bin/env: „perl -w“: Datei oder Verzeichnis nicht gefunden
/usr/bin/env: use -[v]S to pass options in shebang lines
[/quote]
CU
Jörg
--
New:
GPG Fingerprint: 63E0 075F
On Fri, Oct 23, 2020 at 12:20:30PM +0200, Steinar H. Gunderson wrote:
> On Fri, Oct 23, 2020 at 11:33:41AM +0200, Julien Cristau wrote:
> > https://github.com/axboe/liburing/commit/25bbcbef3e0a8bfba8044be55d08d5116c51dccd
> > seems to have bumped SONAME upstream.
>
> That would fix it, yes, but it
Control: reassign -1 googletest
Control: forcemerge 972618 -1
Control: reassign 972775 googletest
Control: forcemerge 972618 972775
Control: affects -1 src:ros-ros src:ros-rospack
Hi Doko,
* Matthias Klose [2020-10-23 12:07]:
ros-ros ftbfs with python3.9 (python3-defaults from experimental), n
Processing control commands:
> reassign -1 googletest
Bug #972774 [src:ros-ros] ros-ros ftbfs
Bug reassigned from package 'src:ros-ros' to 'googletest'.
No longer marked as found in versions ros-ros/1.15.7-1.
Ignoring request to alter fixed versions of bug #972774 to the same values
previously se
On Fri, Oct 23, 2020 at 11:33:41AM +0200, Julien Cristau wrote:
> https://github.com/axboe/liburing/commit/25bbcbef3e0a8bfba8044be55d08d5116c51dccd
> seems to have bumped SONAME upstream.
That would fix it, yes, but it seems to have missed the kflags change
(the commit says all added padding is at
Package: src:zbar
Version: 0.23.1-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
this looks like cython3 is not run during the build (python3-defaults from
experimental).
https://people.debian.org/~ginggs/python3.9-default/zbar_0.23.1-1build1_amd64
Package: src:zeroc-ice
Version: 3.7.4-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
zeroc-ice ftbfs with python3.9 (python3-defaults from experimental):
https://people.debian.org/~ginggs/python3.9-default/zeroc-ice_3.7.4-1build1_amd64-2020-10-23T0
Package: src:talloc
Version: 2.3.1-1
Severity: serious
Tags: sid bullseye ftbfs
talloc ftbfs with python3.9 (python3-defaults from experimental). Looks like
hard-coding a specific python version.
https://people.debian.org/~ginggs/python3.9-default/talloc_2.3.1-1build1_amd64-2020-10-22T15:04:42Z.b
Processing control commands:
> tags -1 confirmed
Bug #970878 [src:ghostscript] ghostscript breaks doc-rfc autopkgtest:
segmentation fault
Added tag(s) confirmed.
--
970878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pro
Package: src:ros-ros
Version: 1.15.7-1
Severity: serious
Tags: sid bullseye ftbfs
ros-ros ftbfs with python3.9 (python3-defaults from experimental), not yet
convinced if that's related to python3.9, looks more like a googletest issue.
https://people.debian.org/~ginggs/python3.9-default/ros-ros_1.
Control: tags -1 confirmed
Quoting Iustin Pop (2020-10-23 00:02:11)
> On 2020-10-10 13:34:16, Bernhard Übelacker wrote:
> > Dear Maintainer,
> > tried to have a look at this one, found the segfault [1],
> > and can point to the place where the pointer gets overwritten [2].
> > Unfortunately Valgri
Package: src:ros-rospack
Version: 2.6.2-1
Severity: serious
Tags: sid bullseye ftbfs
ros-rospack ftbfs with python3.9 (python3-defaults from experimental), not yet
convinced if that's related to python3.9, looks more like a googletest issue.
https://people.debian.org/~ginggs/python3.9-default/ros
Package: src:python-ciso8601
Version: 2.1.3-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
https://people.debian.org/~ginggs/python3.9-default/python-ciso8601_2.1.3-2build1_amd64-2020-10-22T13:38:30Z.build
packaging error, you are mixing b-d's pyt
Package: src:pybdsf
Version: 1.9.2-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
pybdsf ftbfs with python3.9 (python3-defaults from experimenal):
https://people.debian.org/~ginggs/python3.9-default/pybdsf_1.9.2-2build1_amd64-2020-10-22T13:21:38Z.b
Package: src:openstructure
Version: 2.1.0-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
openstructure ftbfs with python3.9 (python3-defaults from experimental), looks
like it still looks for 3.8
https://people.debian.org/~ginggs/python3.9-default/
Package: src:libsigrokdecode
Version: 0.5.3-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
libsigrokdecode ftbfs with python3.9 (python3-defaults from experimental):
https://people.debian.org/~ginggs/python3.9-default/libsigrokdecode_0.5.3-1build1_
Package: src:kissplice
Version: 2.5.3-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
Not sure if that's python 3.9 specific (python3-defaults from experimental was
used). this ends up with a link error:
https://people.debian.org/~ginggs/python3.9-d
Package: src:frr
Version: 7.4-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
frr ftbfs with python3.9 (python3-defaults from experimental)
https://people.debian.org/~ginggs/python3.9-default/frr_7.4-1build1_amd64-2020-10-21T08:19:46Z.build
[...]
On Fri, Oct 23, 2020 at 10:47:57AM +0200, Steinar H. Gunderson wrote:
> On Fri, Oct 23, 2020 at 09:55:36AM +0200, Steinar H. Gunderson wrote:
> > If this were somehow only about newer functionality or critical fixes, it
> > could
> > be fixed by bumping the versioned dependency, but rhis goes both
Processing commands for cont...@bugs.debian.org:
> found 972730 1.1.0-2
Bug #972730 [src:python-mpd] python-mpd: autopkgtest fails when two python3
versions are supported
Marked as found in versions python-mpd/1.1.0-2.
> tags 972730 + bullseye sid
Bug #972730 [src:python-mpd] python-mpd: autopkgt
Package: src:fontforge
Version: 1:20190801~dfsg-5
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
fontforge ftbfs with python3.9 (python3-defaults from experimental). There seem
to be two issues, 3.8 is used instead of 3.9, and d-shlibs isn't aware of
Package: src:cantor
Version: 20.04.3-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
cantor ftbfs with python3.9 (python3-defaults from experimental):
https://people.debian.org/~ginggs/python3.9-default/cantor_20.04.3-1build1_amd64-2020-10-22T21:44:
Package: src:bup
Version: 0.31-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
https://people.debian.org/~ginggs/python3.9-default/bup_0.31-1build1_amd64-2020-10-21T07:33:31Z.build
bup ftbfs with python3.9 (python3-defaults from experimental):
[...
Package: src:bornagain
Version: 1.16.0-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
bornagain ftbfs with python3-defaults from experimental, ending up with a mix of
3.8 and 3.9.
https://people.debian.org/~ginggs/python3.9-default/bornagain_1.16.0
Processing control commands:
> severity -1 serious
Bug #972730 [src:python-mpd] python-mpd: merge changes from accidental NMU
Severity set to 'serious' from 'normal'
> retitle -1 python-mpd: autopkgtest fails when two python3 versions are
> supported
Bug #972730 [src:python-mpd] python-mpd: merge
On Fri, Oct 23, 2020 at 09:55:36AM +0200, Steinar H. Gunderson wrote:
> If this were somehow only about newer functionality or critical fixes, it
> could
> be fixed by bumping the versioned dependency, but rhis goes both ways; if you
> build plocate against liburing 0.6-3, and then upgrade liburin
Package: liburing1
Version: 0.7-1
Severity: grave
Tags: upstream
Hi,
I've had a number of reports from people who are having problems with plocate,
that can be traced to differing versions of liburing1. Specifically, plocate
is built in sid against liburing1 0.7-1 (which gets a versioned dependen
Hi Paul,
Paul Wise wrote:
> On Fri, 2020-10-23 at 08:05 +0200, Axel Beckert wrote:
> > Ack. Just have to think how I make that separation properly. Either by
> > listing all supported previous release names (or maybe just those not
> > yet archived) and defaulting to the new scheme to be comaptibl
Control: found -1 3.20.5+dfsg0-3
Control: tags -1 +bullseye +upstream
Le vendredi, 16 octobre 2020, 14.23:59 h CEST Didier 'OdyX' Raboud a écrit :
> According to the 3.20.9-3 armhf auutopkgtest run for migration testing;
> https://ci.debian.net/data/autopkgtest/testing/armhf/h/hplip/7460676/log.gz
Processing control commands:
> found -1 3.20.5+dfsg0-3
Bug #972339 [printer-driver-hpcups] armhf: hpcups crashes with free() invalid
pointer for some printers
Marked as found in versions hplip/3.20.5+dfsg0-3.
> tags -1 +bullseye +upstream
Bug #972339 [printer-driver-hpcups] armhf: hpcups crashes
On Fri, 2020-10-23 at 08:05 +0200, Axel Beckert wrote:
> Ack. Just have to think how I make that separation properly. Either by
> listing all supported previous release names (or maybe just those not
> yet archived) and defaulting to the new scheme to be comaptible with
> all future releases.
Tha
69 matches
Mail list logo
