Package: droopy
Version: 0.20160830-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear maintainer.
I launched droopy earlier to transfer some files, and it failed like so
$ droopy
Traceback (most recent call last):
File "/usr/bin/droopy", line 81, in
import
Dear Ilias Tsitsimpis,
does your intention to remove haskell-edison-api mean that Agda 2.6.1 will
be packaged for Debian bullseye?
--
Regards,
Marko Dimjašević
https://dimjasevic.net/marko
Mastodon: https://mamot.fr/@mdimjasevic
PGP key ID: 056E61A6F3B6C9323049DBF9565EE9641503F0AA
Learn
Your message dated Wed, 24 Jun 2020 19:41:11 -0300
with message-id
and subject line Fixed in latest upload
has caused the Debian Bug report #963631,
regarding qtwebengine-opensource-src: FTBFS everywhere
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Samuel Henrique writes ("Bug#963489: dgit mirror ssh wrapper breaks due to
rsync update"):
> Hello Ian,
> > src:dgit contains a wrapper script which is intended for use in an ssh
> > restricted command invoked by rsync, as part of a mirroring setup.
>
> Ahh, so that was the issue, I got confused
Hello Ian,
> src:dgit contains a wrapper script which is intended for use in an ssh
> restricted command invoked by rsync, as part of a mirroring setup.
Ahh, so that was the issue, I got confused and was about to ping you
to help me figure it out.
> This whole situation is not very good but it
Processing commands for cont...@bugs.debian.org:
> # typoed the bug number
> reopen 963631
Bug #963631 {Done: Sebastian Ramacher }
[src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS everywhere
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed
Your message dated Wed, 24 Jun 2020 21:33:37 +
with message-id
and subject line Bug#963631: fixed in breathe 4.19.2-1
has caused the Debian Bug report #963631,
regarding qtwebengine-opensource-src: FTBFS everywhere
to be marked as done.
This means that you claim that the problem has been
Source: qtwebengine-opensource-src
Version: 5.14.2+dfsg1-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
Builds of qtwebengine-opensource-src failed to build everywhere:
| /usr/bin/g++ -MMD -MF
Your message dated Wed, 24 Jun 2020 20:34:31 +
with message-id
and subject line Bug#953227: fixed in garagemq 0.0~git20200204.15e6a9d+ds-3
has caused the Debian Bug report #953227,
regarding garagemq: autopkgtest failure:
github.com/valinurovam/garagemq/srvstorage [no test files]
to be
Your message dated Wed, 24 Jun 2020 20:34:26 +
with message-id
and subject line Bug#954070: fixed in fdroidserver 1.1.9-1
has caused the Debian Bug report #954070,
regarding fdroidserver: Incorrect Litecoin address validation
to be marked as done.
This means that you claim that the problem
Hi,
On Thu, Jun 25, 2020 at 03:16:25AM +0800, Shengjing Zhu wrote:
> Control: reopen -1
> Control: notfixed -1 0.0~git20200204.15e6a9d+ds-2
> Control: tags -1 + ftbfs
>
> Hi Andreas,
>
> You just disabled the autopkgtest. But the test is not only running in
> autopkgtest, but also during
Control: tag -1 pending
Hello,
Bug #953227 in garagemq 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 #953227 [src:garagemq] garagemq: autopkgtest failure:
github.com/valinurovam/garagemq/srvstorage [no test files]
Added tag(s) pending.
--
953227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953227
Debian Bug Tracking System
Contact
Your message dated Wed, 24 Jun 2020 19:48:38 +
with message-id
and subject line Bug#953800: fixed in gpgme1.0 1.13.1-8
has caused the Debian Bug report #953800,
regarding gpgme1.0: don't fail checky2106 on 32bit systems
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> found 953800 1.13.1-6
Bug #953800 [src:gpgme1.0] gpgme1.0: don't fail checky2106 on 32bit systems
Marked as found in versions gpgme1.0/1.13.1-6.
--
953800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953800
Debian Bug Tracking System
Contact
Control: found 953800 1.13.1-6
If checky2106 will always fail on 32-bit systems, that's a clear
indication that GnuPG will fail on those systems when it encounters
objects that have a timestamp that lands about 86 years out from now.
For example, an OpenPGP certificate with a 100-year expiration
Package: node-jest
Severity: serious
Dear Maintainer,
Node-jest fails with the following on all the node-modules I've tried yet.
Sample examples on
node-compression-webpack-plugin version 2.0.0-3
and
node-proper-lockfile version 4.1.1-2
internal/modules/cjs/loader.js:800
throw err;
^
Processing commands for cont...@bugs.debian.org:
> unarchive 953227
Bug #953227 {Done: Andreas Henriksson } [src:garagemq]
garagemq: autopkgtest failure: github.com/valinurovam/garagemq/srvstorage [no
test files]
Unarchived Bug 953227
> reopen 953227
Bug #953227 {Done: Andreas Henriksson }
Your message dated Wed, 24 Jun 2020 15:47:24 -0300
with message-id
and subject line autopkgtest flaky on arm64
has caused the Debian Bug report #961032,
regarding autopkgtest flaky on arm64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Wed, 24 Jun 2020 18:03:33 +
with message-id
and subject line Bug#961216: fixed in glibmm2.4 2.64.2-2
has caused the Debian Bug report #961216,
regarding inkscape: symbol resolution problem
to be marked as done.
This means that you claim that the problem has been dealt
On Wed, 24 Jun 2020 at 19:05:51 +0200, Mattia Rizzolo wrote:
> > > _ZN3Gio11Application35set_option_context_parameter_stringERKN4Glib7ustringE
>
> So, that set_option_context_parameter_string thing comes from Glib 2.56
For future reference: glibmm, not GLib. The GLib family of libraries
(GLib,
Processing control commands:
> tag -1 pending
Bug #961216 [libglibmm-2.4-dev] inkscape: symbol resolution problem
Added tag(s) pending.
--
961216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #961216 in glibmm2.4 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 commands for cont...@bugs.debian.org:
> tags 961216 =
Bug #961216 [libglibmm-2.4-dev] inkscape: symbol resolution problem
Removed tag(s) unreproducible and moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
961216:
Control: reassign -1 libglibmm-2.4-dev 2.56.0-1
So, talking with people over at the Gnome team, this came out:
On Fri, May 22, 2020 at 10:30:20AM +1000, Peter Eckersley wrote:
> However this somehow fixed the problem?
>
> $ sudo apt-get build-dep inkscape
...
> The following packages will be
Processing control commands:
> reassign -1 libglibmm-2.4-dev 2.56.0-1
Bug #961216 [inkscape] inkscape: symbol resolution problem
Bug reassigned from package 'inkscape' to 'libglibmm-2.4-dev'.
No longer marked as found in versions inkscape/1.0-1.
Ignoring request to alter fixed versions of bug
Your message dated Wed, 24 Jun 2020 16:48:29 +
with message-id
and subject line Bug#963609: fixed in golang-github-francoispqt-gojay 1.2.13-3
has caused the Debian Bug report #963609,
regarding golang-github-francoispqt-gojay FTBFS on 32bit
to be marked as done.
This means that you claim
Hey Salvatore!
On Wed, Jun 24, 2020 at 05:57:42PM +0200, Salvatore Bonaccorso wrote:
>Control: found -1 4.19.118-1
>Control: tags -1 + upstream
>
>Hi Steve,
>
>On Mon, Jun 22, 2020 at 12:58:35PM +0100, Steve McIntyre wrote:
>> Source: linux
>> Version: 4.19.118-2+deb10u1
>> Severity: serious
>>
Processing control commands:
> found -1 4.19.118-1
Bug #963493 [src:linux] Repeatable hard lockup running strace testsuite using
4.19.118+2+deb10u1, 4.19.98+1+deb10u1 works fine
Marked as found in versions linux/4.19.118-1.
> tags -1 + upstream
Bug #963493 [src:linux] Repeatable hard lockup
Control: found -1 4.19.118-1
Control: tags -1 + upstream
Hi Steve,
On Mon, Jun 22, 2020 at 12:58:35PM +0100, Steve McIntyre wrote:
> Source: linux
> Version: 4.19.118-2+deb10u1
> Severity: serious
>
> Hi folks,
>
> Trying to reproduce #963462 on my Thinkpad T470, I'm repeatedly
> getting a
Processing commands for cont...@bugs.debian.org:
> tags 961496 + pending
Bug #961496 [rinse] rinse: fails to extract rpms
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
961496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961496
Debian
Source: golang-github-francoispqt-gojay
Version: 1.2.13-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=golang-github-francoispqt-gojay=sid
...
# github.com/francoispqt/gojay [github.com/francoispqt/gojay.test]
Timo Jyrinki kirjoitti 18.6.2020 klo 18.18:
> I managed to fix it thanks to message #34, changing
> /usr/src/wireguard-1.0.20200520/compat/compat.h slightly and running dpkg
> --configure -a. It built fine both against 4.19.0-6-marvell and
> 4.19.0-9-marvell.
Likewise for
Your message dated Wed, 24 Jun 2020 09:48:50 +
with message-id
and subject line Bug#963454: fixed in grml2usb 0.18.3
has caused the Debian Bug report #963454,
regarding grml2usb: FTBFS: grml2usb:920:17: F523 '...'.format(...) has unused
arguments at position(s): 0
to be marked as done.
This
Hello,
On Wed, 24 Jun 2020 02:08:23 +0300 Jussi Pakkanen wrote:
> On Tue, 23 Jun 2020 at 16:36, Gianfranco Costamagna
> wrote:
>
> > Hello, as you can see, two tests can't be run on ppc64el and s390x, because
> > of missing:
> > g++-arm-linux-gnueabihf and ldc
> >
Your message dated Wed, 24 Jun 2020 09:18:34 +
with message-id
and subject line Bug#962724: fixed in iptables 1.8.5-2
has caused the Debian Bug report #962724,
regarding iptables: autopkgtest regression: nft Unsupported command?
to be marked as done.
This means that you claim that the
Re: Felix Lechner
> There may be an alternative for some cases mentioned here. The wolfSSL
> encryption library is a FIPS-certified, commercial product with a
> fully usable, although incomplete, OpenSSL compatibility layer.
Interesting pointer, thanks.
For postgresql-12, it fails at the
Your message dated Wed, 24 Jun 2020 07:34:11 +
with message-id
and subject line Bug#963344: fixed in python-urwid-utils 0.1.2.dev2-2
has caused the Debian Bug report #963344,
regarding python-urwid-utils: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.8
Your message dated Wed, 24 Jun 2020 07:34:06 +
with message-id
and subject line Bug#963400: fixed in python-panwid 0.3.0.dev15-2
has caused the Debian Bug report #963400,
regarding python-panwid: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.8 returned exit
Your message dated Wed, 24 Jun 2020 08:56:05 +0200
with message-id
and subject line Re: Bug#962743: cnvkit FTBFS on mips64el/ppc64el: test failure
has caused the Debian Bug report #962743,
regarding cnvkit FTBFS on mips64el/ppc64el: test failure
to be marked as done.
This means that you claim
Michael,
you did the last update of this package. The bug is blocking testing
migration of python-biopython which creates regularly a lot of noise.
Could you confirm that you are working on this or do you need help?
Kind regards
Andreas.
--
http://fam-tille.de
Package: sysdig
Version: 0.26.7-2
Severity: grave
Hi. sysdig used to work, but now it doesn't. I'm running Debian/sid, so
probably something about my set of dependencies doesn't agree with
sysdig, but we should figure out what that is.
Earlier today I was seeing a segfault when running some
42 matches
Mail list logo
