Control: tag -1 pending
Hello,
Bug #935552 in nomad 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:
https://salsa.debian.org/go-team/packages/nomad/commit/977675c3e209c75e1008bc4bc75382
Processing control commands:
> tag -1 pending
Bug #935552 [src:nomad] nomad: FTBFS
Added tag(s) pending.
--
935552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: python3-fiat
Version: 2019.1.0-2
Followup-For: Bug #942237
Upstream does have a patch, but it requires a new package pytest_cases.
There was some debate upstream about whether it would be better to
prepare the tests without needing to depend on the new package. I'm
waiting for that debat
Control: tags -1 +patch
The attached patch fixes the problem for me. It comes from [1].
Thanks,
Adrian
> [1] https://www.spinics.net/lists/git/msg368292.html
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.
Processing control commands:
> tags -1 +patch
Bug #942674 [src:git] git: FTBFS on big-endian targets - testsuite failure
Added tag(s) patch.
--
942674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Sat, 19 Oct 2019 23:49:28 +
with message-id
and subject line Bug#942119: fixed in libproxy 0.4.15-8
has caused the Debian Bug report #942119,
regarding libproxy: depends on mono for build-arch; mono not universally present
to be marked as done.
This means that you claim tha
Processing control commands:
> tag -1 pending
Bug #942119 [src:libproxy] libproxy: depends on mono for build-arch; mono not
universally present
Added tag(s) pending.
--
942119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942119
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Source: elixir-lang
Version: 1.9.1.dfsg-1.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
The latest upload failed to build on a few architectures:
https://buildd.debian.org/status/package.php?p=elixir-lang&suite=sid
I tried building it locally and it worked. I the
Control: tag -1 pending
Hello,
Bug #942119 in libproxy 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:
https://salsa.debian.org/gnome-team/libproxy/commit/54783bbd78a96c7c2fdb850be804a5
Hi,
> In fact, the proposed "fix" I'm working on is to actually get the
> version that is currently in backports directly in the oldstable
> distribution, but I need to tweak it a bit as to do that I need to
> reintroduce the 'letsencrypt.sh' compatibility packages/scripts.
unfortunately, that ve
Control: tags 938530 + patch
Dear maintainer,
I've prepared an NMU for sphinxcontrib-actdiag (versioned as 0.8.5-1.1). The
diff
is attached to this message.
i've uploaded directly to unstable becaues it fixes a RC bug
Regards.
diff -Nru sphinxcontrib-actdiag-0.8.5/debian/changelog sphinxcont
Processing control commands:
> tags 938530 + patch
Bug #938530 [src:sphinxcontrib-actdiag] sphinxcontrib-actdiag: Python2 removal
in sid/bullseye
Added tag(s) patch.
--
938530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Source: git
Version: 1:2.24.0~rc0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
User: debian-s...@lists.debian.org
Usertags: s390x
Hi!
git currently fails to build from source on all big-endian targets due
to test suite failures. This includes powerpc, ppc64, sparc64 a
On Sat, Oct 19, 2019 at 08:14:33PM +0200, Florian Zumbiehl wrote:
> Is there any plan to fix this bug before then, or will users have to work
> around this individually to avoid running into expired certificates? And if
> the latter, what is the recommended workaround? Is the current backports
> ve
Package: src:cracklib
Version: 2.9.6-2
Severity: serious
Tags: sid bullseye
cracklib2 ignores build failures, not setting -e for all the loops iterating
over python versions. Seen with 3.8 as a supported python version.
Le mardi 15 octobre 2019 à 21:08:17+0200, Paul Gevers a écrit :
> Hi,
>
> On 15-10-2019 21:00, Paul Gevers wrote:
> > github.com/CanonicalLtd/raft-membership
> >dh_auto_test -O--buildsystem=golang
> > cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2
> > github.com/CanonicalLtd/raft-mem
Processing commands for cont...@bugs.debian.org:
> tags 922566 + sid bullseye
Bug #922566 [src:actiona] FTBFS against opencv 4.0.1 (exp)
Added tag(s) sid and bullseye.
> tags 922573 + sid bullseye
Bug #922573 [src:darknet] FTBFS against opencv 4.0.1 (exp)
Added tag(s) bullseye and sid.
> tags 9225
Hi,
as the recommended strategy by LetsEncrypt is to renew certificates 30 days
before their expiry, and we are approaching 30 days since the change that
exposed this bug that thus is preventing certificate renewal since then,
certificates generated using dehydrated are going to start expiring in
Processing control commands:
> tags 938466 + patch
Bug #938466 [src:seqdiag] seqdiag: Python2 removal in sid/bullseye
Added tag(s) patch.
--
938466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags 938466 + patch
Dear maintainer,
I've prepared an NMU for seqdiag (versioned as 0.9.5+dfsg-1.2). The diff
is attached to this message.
I've uploaded directly to unstable as it fixes an RC bug, and it's an NMU of
an NMU
Regards.
diff -Nru seqdiag-0.9.5+dfsg/debian/changelog seqdia
On Thu, Oct 17, 2019 at 10:02 AM Moritz Muehlenhoff wrote:
> IMHO for stretch-security/buster-security we should rather rebase the old
> 4.9.2ish packages to 4.9.3, given that it creates new system users etc.
> it seems not really suitable for a security update.
Ok, that is what I did. Review wel
Source: celery-batches
Version: 0.2-1
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: ftpmas...@debian.org, deba...@debian.org, rodrilopez@gmail.com
Hi,
I just ACCEPTed celery-batches from NEW but the FTP team noticed docs/
has a different license not mentioned in debian/copyright.
Processing commands for cont...@bugs.debian.org:
> tags 933642 + pending
Bug #933642 [devscripts] devscripts: leaves multiple test/uscan/server.py
processes running after build
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
933642: https://
Processing commands for cont...@bugs.debian.org:
> found 933642 2.19.4
Bug #933642 [devscripts] devscripts: leaves multiple test/uscan/server.py
processes running after build
Marked as found in versions devscripts/2.19.4.
> thanks
Stopping processing here.
Please contact me if you need assistanc
Your message dated Sat, 19 Oct 2019 12:20:23 +
with message-id
and subject line Bug#942629: fixed in golang-1.12 1.12.12-1
has caused the Debian Bug report #942629,
regarding golang-1.12: CVE-2019-17596: invalid public key causes panic in
dsa.Verify
to be marked as done.
This means that you
Your message dated Sat, 19 Oct 2019 12:04:43 +
with message-id
and subject line Bug#942628: fixed in golang-1.13 1.13.3-1
has caused the Debian Bug report #942628,
regarding golang-1.13: CVE-2019-17596: invalid public key causes panic in
dsa.Verify
to be marked as done.
This means that you c
Your message dated Sat, 19 Oct 2019 11:49:24 +
with message-id
and subject line Bug#937745: fixed in python-fabio 0.9.0+dfsg-2
has caused the Debian Bug report #937745,
regarding python-fabio: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> retitle 942629 golang-1.12: CVE-2019-17596: invalid public key causes panic
> in dsa.Verify
Bug #942629 [src:golang-1.12] golang-1.13: CVE-2019-17596: invalid public key
causes panic in dsa.Verify
Changed Bug title to 'golang-1.12: CVE-2019-1759
Your message dated Sat, 19 Oct 2019 11:35:23 +
with message-id
and subject line Bug#938481: fixed in silx 0.11.0+dfsg-2
has caused the Debian Bug report #938481,
regarding silx: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt wit
Package: apt-cacher-ng
Version: 3.2-2
Severity: grave
Justification: renders package unusable
Dear maintainer,
apt-cacher-ng stopped working recently when used to cache the debian/sid
suite. It reports the following error:
| An error occurred while reading this file, some contents may have been
I can conform that the recent introduction of uhd 3.14.1.1-1 has fixed
the FTBFS and the package is building fine again.
--
- Harald Welte http://laforge.gnumonks.org/
"Privacy in residential applications is
Processing commands for cont...@bugs.debian.org:
> tags 941999 + pending
Bug #941999 [src:kopanocore] kopanocore: autopkgtest tries to install packages
itself but doesn't exit appropriately if that fails
Added tag(s) pending.
> tags 939751 + pending
Bug #939751 [kopano-server] Kopano-Server in St
32 matches
Mail list logo
