On Wed, 06 Jan 2021 16:58:00 +0100 Ansgar wrote:
> Source: libnet-ipaddress-perl
> Version: 1.10-3
> Severity: serious
> Tags: bullseye sid
> X-Debbugs-Cc: Cyril Bouthors , Cyril Bouthors
> , Holger Levsen
>
> The maintainer address is invalid, see below.
>
> Ansgar
>
>
Your message dated Wed, 27 Jan 2021 04:34:02 +
with message-id
and subject line Bug#972134: fixed in chromium 88.0.4324.96-1
has caused the Debian Bug report #972134,
regarding chromium: please, consider moving the package to team-maintainance to
properly maintain it
to be marked as done.
Your message dated Wed, 27 Jan 2021 02:35:24 +
with message-id
and subject line Bug#980086: fixed in picolibc 1.5.1-2
has caused the Debian Bug report #980086,
regarding broken autopkg test, no aarch64 cross targets on armhf.
to be marked as done.
This means that you claim that the problem
Processing control commands:
> block 978567 by -1
Bug #978567 [src:godot] src:godot: fails to migrate to testing for too long:
FTBFS on mips64el
978567 was not blocked by any bugs.
978567 was not blocking any bugs.
Added blocking bug(s) of 978567: 981154
--
978567:
Hi Jorg,
Do you need sponsoring for the upload of the last upstream version in
unstable? Can we see this moving forward?
Cheers,
Thomas Goirand (zigo)
Your message dated Wed, 27 Jan 2021 00:34:02 +
with message-id
and subject line Bug#963411: fixed in libisocodes 1.2.3-1
has caused the Debian Bug report #963411,
regarding libisocodes: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1
returned exit code 2
to be marked as done.
This
On Mon, 18 Jan 2021 19:19:14 -0800 Benjamin Kaduk wrote:
On Mon, Jan 18, 2021 at 06:04:39PM +, Jeremy Stanley wrote:
> Thanks for pulling this into unstable and testing! Is there any work
> in progress to fix it in stable as well? I took a quick peek in
> Salsa and didn't see any merge
Dear Jonas,
TL;DR:
The following list of packages allows to build Monero under sid:
build-essential cmake pkg-config libboost-all-dev libssl-dev libzmq3-dev
libunbound-dev libsodium-dev libunwind8-dev liblzma-dev libreadline6-dev
libldns-dev libexpat1-dev libpgm-dev libhidapi-dev
Package: loggedfs
Version: 0.9+ds-2
Severity: serious
When I try to run loggedfs on a system without fuse/fuse3 installed I
get an error because the fusermount binary is not found.
$ dir=$(mktemp --directory tmp-XX)
$ loggedfs -f `pwd`/$dir
2021-01-27 07:14:50,851 INFO [default]
Package: loggedfs
Version: 0.9+ds-2
Severity: serious
When I try to use loggedfs I get an error, presumably because loggedfs
wants fuse rather than fuse3, but I can't install fuse because other
things I have installed want fuse3 instead of fuse.
$ dir=$(mktemp --directory tmp-XX)
$
Package: todo.txt-gtd
Version: 0.5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other
Processing control commands:
> notfound -1 0.36-2
Bug #975472 {Done: Ilias Tsitsimpis } [src:xmobar] xmobar:
autopkgtest regression on ppc64el: Not found
No longer marked as found in versions xmobar/0.36-2.
--
975472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975472
Debian Bug Tracking
Control: notfound -1 0.36-2
Hi,
On Tue, 26 Jan 2021 20:25:27 +0200 Ilias Tsitsimpis
wrote:
> Version: 0.36-2
I think this alone is not enough to mark the bug as not affecting the
version and the bts still block the package. Hopefully this mail fixes that.
Paul
OpenPGP_signature
Processing commands for cont...@bugs.debian.org:
> unarchive 949571
Bug #949571 {Done: Federico Ceratto } [src:naev] naev
should not use the private binutils shared libraries
Unarchived Bug 949571
> reopen 949571
Bug #949571 {Done: Federico Ceratto } [src:naev] naev
should not use the private
Hey Colin,
Am 26.01.21 um 11:12 schrieb Colin Watson:
On Mon, Jan 25, 2021 at 10:59:28PM +, Colin Watson wrote:
On Sat, Jan 02, 2021 at 12:24:05AM +, Debian Bug Tracking System wrote:
* Disable test `test_not_stackable` which fails for python3.9
(Closes: #970148)
Thanks
Hello!
It looks like this particular issue has been fixed in gparted 1.2.0 which
was just released a few days ago [1]:
> - Don't try to mask non-existent Systemd \xe2\x97\x8f.service (#129, !64)
Might be an idea to update gparted to version 1.2.0 before the Bullseye freeze
which is coming in
Processing commands for cont...@bugs.debian.org:
> severity 980331 serious
Bug #980331 [src:tokyotyrant] tokyotyrant: should ship with bullseye?
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
980331:
Your message dated Tue, 26 Jan 2021 18:48:37 +
with message-id
and subject line Bug#973837: fixed in evdi 1.9.0+dfsg-1
has caused the Debian Bug report #973837,
regarding evdi module fails to compile on Linux 5.9.0
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 26 Jan 2021 20:25:27 +0200
with message-id <20210126182527.mdaaebaiep6xt...@iliastsi.net>
and subject line Re: Bug#975472: xmobar: autopkgtest regression on ppc64el: Not
found
has caused the Debian Bug report #975472,
regarding xmobar: autopkgtest regression on ppc64el:
On Mon, 23 Nov 2020 20:15:52 +0100 Simon Josefsson wrote:
> severity 975030 serious
> severity 974997 serious
> severity 974996 serious
> severity 974995 serious
> severity 974994 serious
> severity 974993 serious
> thanks
>
> It was suggested to me on IRC that the severity of this could be
>
Processing control commands:
> tags 975030 + pending
Bug #975030 [wget2] Please build-depend on libidn2-dev instead of obsolete
transition package libidn2-0-dev
Added tag(s) pending.
--
975030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975030
Debian Bug Tracking System
Contact
Control: tags 975030 + pending
Dear maintainer,
I've prepared an NMU for wget2 (versioned as 1.99.1-2.2) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.
Regards,
Boyuan Yang
diff -Nru wget2-1.99.1/debian/changelog wget2-1.99.1/debian/changelog
---
Your message dated Tue, 26 Jan 2021 15:49:23 +
with message-id
and subject line Bug#957771: fixed in sagan 1.2.0-1.2
has caused the Debian Bug report #957771,
regarding sagan: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Control: tags 957771 + patch
Dear maintainer,
I've released an NMU for sagan (versioned as 1.2.0-1.2). The diff
is attached to this message.
Regards.
diff -Nru sagan-1.2.0/debian/changelog sagan-1.2.0/debian/changelog
--- sagan-1.2.0/debian/changelog2019-09-10 16:15:15.0 +0200
Processing control commands:
> tags 957771 + patch
Bug #957771 [src:sagan] sagan: ftbfs with GCC-10
Added tag(s) patch.
--
957771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Tue, 26 Jan 2021 15:33:51 +
with message-id
and subject line Bug#980697: fixed in borgmatic 1.5.12-2
has caused the Debian Bug report #980697,
regarding borgmatic: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p 3.9 returned exit code 13
to
Processing commands for cont...@bugs.debian.org:
> forwarded 957771 https://github.com/quadrantsec/sagan/issues/6
Bug #957771 [src:sagan] sagan: ftbfs with GCC-10
Set Bug forwarded-to-address to 'https://github.com/quadrantsec/sagan/issues/6'.
> thanks
Stopping processing here.
Please contact me
On Tue, Jan 26, 2021 at 01:44:47PM +0100, Julian Andres Klode wrote:
> On Tue, Jan 26, 2021 at 12:52:52PM +0100, Aurelien Jarno wrote:
> > The break hasn't been added randomly, but in response to upstream
> > release notes and bug #965932. In short the openssh seccomp filters in
> > buster are too
Your message dated Tue, 26 Jan 2021 08:22:00 -0500
with message-id
and subject line Re: [hydrogen] Future Qt4 removal from Buster
has caused the Debian Bug report #874907,
regarding [hydrogen] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> forwarded 971149 https://github.com/py4n6/pytsk/issues/71
Bug #971149 [src:dfvfs] dfvfs: FTBFS: AttributeError: 'pytsk3.TSK_FS_INFO'
object has no attribute 'ftype'
Set Bug forwarded-to-address to 'https://github.com/py4n6/pytsk/issues/71'.
>
Your message dated Tue, 26 Jan 2021 13:18:26 +
with message-id
and subject line Bug#979406: fixed in lilypond 2.22.0-5
has caused the Debian Bug report #979406,
regarding lilypond-doc: missing Breaks+Replaces: lilypond-doc-html (<< 2.21)
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> reopen 979406
Bug #979406 {Done: Anthony Fok } [lilypond-doc] lilypond-doc:
missing Breaks+Replaces: lilypond-doc-html (<< 2.21)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you
Tianon pointed to
p11-kit's "trust extract --format=java-cacerts ..." works pretty well in my
experience (that's how Alpine Linux solves this particular problem:
https://gitlab.alpinelinux.org/alpine/aports/-/blob/bd4e89c6a26bf7c247c3335b8a7aef053815dfc7/community/java-cacerts/APKBUILD#L18-19)
On Tue, Jan 26, 2021 at 12:52:52PM +0100, Aurelien Jarno wrote:
> reassign 979970 src:glibc,src:libselinux,src:apt,src:openssh
> thanks
>
> On 2021-01-25 11:59, Laurent Bigonville wrote:
> > reassign 979970 src:glibc 2.30-1
> > affects 979970 + libselinux1
> > thanks
> >
> > On Tue, 12 Jan 2021
Your message dated Tue, 26 Jan 2021 09:42:15 -0300
with message-id
and subject line golang-github-caarlos0-env: FTBFS: TestParseInvalidURL fails
has caused the Debian Bug report #964043,
regarding golang-github-caarlos0-env: FTBFS: TestParseInvalidURL fails
to be marked as done.
This means that
Your message dated Tue, 26 Jan 2021 05:32:42 -0700
with message-id
and subject line Bug#979406: fixed in lilypond 2.21.82-1~exp2
has caused the Debian Bug report #979406,
regarding lilypond-doc: missing Breaks+Replaces: lilypond-doc-html (<< 2.21)
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> reassign 979970 src:glibc,src:libselinux,src:apt,src:openssh
Bug #979970 [src:glibc] libselinux1: dependency to newer libc6 ignored
by/missing for aptitude
Bug reassigned from package 'src:glibc' to
reassign 979970 src:glibc,src:libselinux,src:apt,src:openssh
thanks
On 2021-01-25 11:59, Laurent Bigonville wrote:
> reassign 979970 src:glibc 2.30-1
> affects 979970 + libselinux1
> thanks
>
> On Tue, 12 Jan 2021 13:31:19 +0100 Charlemagne Lasse
> wrote:
>
> > Right now, an update from buster
Your message dated Tue, 26 Jan 2021 11:50:18 +
with message-id
and subject line Bug#980972: fixed in xxsds-dynamic
1.0~alpha.1+2020072524git5390b6c-3
has caused the Debian Bug report #980972,
regarding xxsds-dynamic: Changelog entry missing trailer line
to be marked as done.
This means that
Thank you, Logan.
I just fixed that and uploaded. Nothing new from upstream.
Steffen
Your message dated Tue, 26 Jan 2021 11:34:22 +
with message-id
and subject line Bug#921257: fixed in khal 1:0.10.2-0.1
has caused the Debian Bug report #921257,
regarding khal: FTBFS randomly when built
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing control commands:
> tags 921257 + patch
Bug #921257 [src:khal] khal: FTBFS randomly when built
Added tag(s) patch.
--
921257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
On 1/25/21 3:13 PM, Antonio Terceiro wrote:
> Control: tags -1 + unreproducible moreinfo
>
> On Sun, 24 Jan 2021 08:28:21 +0100 lenny wrote:
>> Package: libpython3.9
>> Version: 3.9.1-3
>> Severity: critical
>> Justification: breaks the whole system
>> X-Debbugs-Cc: lenni_...@yahoo.de
>>
>> Dear
Processing control commands:
> tags -1 upstream
Bug #980082 [src:r-bioc-shortread] r-bioc-shortread: autopkgtest failure in
testing and unstable
Added tag(s) upstream.
> forwarded -1 Bioconductor Package Maintainer
Bug #980082 [src:r-bioc-shortread] r-bioc-shortread: autopkgtest failure in
Control: tags -1 upstream
Control: forwarded -1 Bioconductor Package Maintainer
Hi,
the Debian packaged ShortRead is tested in CI test on different hardware
architectures. On the debci page[1] you can see the matrix for success
and failure which shows that amd64 and i386 are passing the
On Mon, Jan 25, 2021 at 10:59:28PM +, Colin Watson wrote:
> On Sat, Jan 02, 2021 at 12:24:05AM +, Debian Bug Tracking System wrote:
> >* Disable test `test_not_stackable` which fails for python3.9
> > (Closes: #970148)
>
> Thanks for sorting out the immediate issue, but this
Control: tags -1 moreinfo, unreproducible
Control: severity -1 important
Hi Lucas,
I've build r-cran-rstan in a clean chroot and it builds nicely as
expected. May be the issue you observed has vanished?
Could you please re-check whether I'm missing something? I've
set severity to important
Processing control commands:
> tags -1 moreinfo, unreproducible
Bug #978198 [src:r-cran-rstan] r-cran-rstan: FTBFS: Eigen_NumTraits.hpp:200:77:
error: wrong number of template arguments (8, should be 9)
Added tag(s) moreinfo and unreproducible.
> severity -1 important
Bug #978198
Your message dated Tue, 26 Jan 2021 09:51:30 +
with message-id <90a232db-6c7f-1f9a-432e-d25de1869...@debian.org>
and subject line close
has caused the Debian Bug report #980917,
regarding libpmix-dev fails to upgrade from 3.2.2~rc1-1 to 4.0.0-4
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> tags 980776 + pending
Bug #980776 [namazu2-index-tools] namazu2: contents of namazu2-index-tools
different when built separately from arch specific binaries
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need
Control: severity -1 important
> resolved and I've marked the bug with RC severity
Bernhard, wait what? This is not a grave bug at all, it doesn’t make package
unusable to everybody, but just in this specific ACL configuration.
Ondrej
--
Ondřej Surý (He/Him)
ond...@sury.org
> On 26. 1. 2021,
Processing control commands:
> severity -1 important
Bug #980786 [bind9] named: segfault with named ACL
Severity set to 'important' from 'grave'
--
980786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> forwarded -1
Unknown command or malformed arguments to command.
> severity -1 grave
Bug #980786 [bind9] named: after upgrade to bind9=1:9.16.11-1 named is killed
with status=11/SEGV
Severity set to 'grave' from 'important'
> retitle -1 named: segfault with named
Processing commands for cont...@bugs.debian.org:
> severity 976913 important
Bug #976913 [src:golang-github-henrydcase-nobs] golang-github-henrydcase-nobs:
FTBFS on ppc64el (arch:all-only src pkg): dh_auto_build: error: cd
obj-powerpc64le-linux-gnu && go install -trimpath -v -p 160
Package: golang-github-nrdcg-goinwx-dev
Version: 0.8.1-1
Severity: serious
Control: block 975789 by -1
excuses:
Migration status for golang-github-nrdcg-goinwx (0.6.1-3 to 0.8.1-1):
BLOCKED: Rejected/violates migration policy/introduces a regression
Issues preventing migration:
Processing control commands:
> block 975789 by -1
Bug #975789 {Done: Arnaud Rebillout }
[src:golang-github-xenolf-lego] golang-github-xenolf-lego: FTBFS:
src/github.com/go-acme/lego/providers/dns/inwx/inwx.go:85:6: assignment
mismatch: 1 variable but d.client.Account.Login returns 2 values
Your message dated Tue, 26 Jan 2021 08:21:54 +
with message-id
and subject line Bug#980740: fixed in r-bioc-geoquery 2.58.0+dfsg-2
has caused the Debian Bug report #980740,
regarding r-bioc-geoquery: flaky autopkgtests failing to download test data
to be marked as done.
This means that you
57 matches
Mail list logo
