Your message dated Fri, 12 Jun 2020 10:35:37 +0500
with message-id <87bllo7snq.fsf@localhost>
and subject line
has caused the Debian Bug report #960131,
regarding swi-prolog: flaky autopkgtest: test set "file" ... aborted
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 12 Jun 2020 05:18:41 +
with message-id
and subject line Bug#962399: fixed in vmdb2 0.16-2
has caused the Debian Bug report #962399,
regarding vmdb2 FTBFS: help2man: can't get `--help' info from vmdb2
to be marked as done.
This means that you claim that the problem has
Hi Craig,
On Fri, Jun 12, 2020 at 09:40:34AM +1000, Craig Small wrote:
> Source: wordpress
> Version: 5.4.1+dfsg1-1
> Severity: grave
> Tags: security upstream
> Justification: user security hole
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> WordPress 5.4.2 is out and fixes the
Processing commands for cont...@bugs.debian.org:
> severity 962681 important
Bug #962681 [linux] battery drain during system shutdown
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
962681:
Your message dated Fri, 12 Jun 2020 04:03:34 +
with message-id
and subject line Bug#952499: fixed in python-csa 0.1.12-1.1
has caused the Debian Bug report #952499,
regarding python-csa: needs a source-only upload
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 12 Jun 2020 02:48:31 +
with message-id
and subject line Bug#962673: fixed in cunit 2.1-3-dfsg-2.3
has caused the Debian Bug report #962673,
regarding cunit: autopkgtest failure: stdio.h: No such file or directory
to be marked as done.
This means that you claim that
Your message dated Fri, 12 Jun 2020 02:33:28 +
with message-id
and subject line Bug#925672: fixed in efivar 37-2.1
has caused the Debian Bug report #925672,
regarding efivar: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Fri, 12 Jun 2020 00:33:34 +
with message-id
and subject line Bug#962606: fixed in csound 1:6.14.0~dfsg-6
has caused the Debian Bug report #962606,
regarding csound: Build-depends on removed package ttf-dejavu
to be marked as done.
This means that you claim that the problem
Upstream is asking me to use version 83 when reporting bugs.
Source: wordpress
Version: 5.4.1+dfsg1-1
Severity: grave
Tags: security upstream
Justification: user security hole
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
WordPress 5.4.2 is out and fixes the following vulnerabilities:
Props to Sam Thomas (jazzy2fives) for finding an XSS issue where
Your message dated Thu, 11 Jun 2020 23:19:25 +
with message-id
and subject line Bug#960421: fixed in libpwiz 3.0.18342-3
has caused the Debian Bug report #960421,
regarding libpwiz: FTBFS with boost 1.71
to be marked as done.
This means that you claim that the problem has been dealt with.
If
tag 935614 + patch
thanks
Hello,
Thank you for looking into this issue.
The problem is due to reliance on particular ordering when iterating
hash table in tests. The bug is triggered by a minor tweak to hash table
algorithm in glib.
I proposed two patches on the upstream issue to fix the
Processing commands for cont...@bugs.debian.org:
> tag 935614 + patch
Bug #935614 [src:libinfinity] libinfinity: FTBFS on all architectures
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
935614:
Package: python-memprof
Version: 0.3.6-2
Followup-For: Bug #962100
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu groovy ubuntu-patch
Dear Maintainer,
I've discovered a fix which allows the autopkg tests to pass.
In Ubuntu, the attached patch was applied to achieve the following:
Bit more experimentation on this issue.
I tried a very small C program meant to create files with fewer
permissions bits set. This succeeded which strengthens the theory of
the umask getting ignored.
I haven't seen anything hinting whether this is more a client or server
issue.
I can speculate
Adrian Bunk 于 2020年6月9日周二 下午11:18写道：
> Source: mlpack
> Version: 3.3.1-1
> Severity: serious
> Tags: ftbfs
>
> It seems Boost 1.67 -> 1.71 increased something:
>
>
> https://buildd.debian.org/status/fetch.php?pkg=mlpack=mips64el=3.3.1-1%2Bb1=1591444281=0
>
> ...
> /usr/bin/c++ -g -O2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Sebastian,
On 2020-06-11 at 20:28, sramac...@debian.org wrote:
> Hi Bret
>
> The build on mipsel failed:
>
https://buildd.debian.org/status/fetch.php?pkg=openmw=mipsel=0.46.0-1=1591883193=0
>
> It's missing -latomic. But I'm wondiering if it
Your message dated Thu, 11 Jun 2020 21:34:45 +
with message-id
and subject line Bug#960760: fixed in tree-puzzle 5.3~rc16+dfsg-3
has caused the Debian Bug report #960760,
regarding tree-puzzle FTBFS on !amd64: test failures
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 11 Jun 2020 21:18:37 +
with message-id
and subject line Bug#960758: fixed in libcamera 0~git20200513+924778e-1.1
has caused the Debian Bug report #960758,
regarding libcamera FTBFS: missing boost build dependencies
to be marked as done.
This means that you claim that
Package: linux
Version: 4.19.0-4 +
Severity: grave
A regression was introduced in 4.13-rc1(Mainline) and newer kernels. This
regression caused battery drain during system suspend, hibernation or
shutdown for some PCI devices that are not allowed by user space to wake
up the system from sleep (or
Source: janus
Version: 0.10.0-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/meetecho/janus-gateway/pull/2214
Hi,
The following vulnerabilities were published for janus.
CVE-2020-13898[0]:
| An issue was discovered in janus-gateway (aka
Hi Bret
On 2020-06-11 02:36:15 -0700, bret curtis wrote:
> Hello Sebastian,
> On 2020-06-11 at 09:11, sramac...@debian.org wrote:
> > Hi bret
> >
> > On 2020-06-09 18:28:02 +0200, bret curtis wrote:
> > > OpenMW 0.46 has been released and I've uploaded it here, it just
> > > someone kind and just
Processing commands for cont...@bugs.debian.org:
> tags 936832 + experimental
Bug #936832 {Done: =?utf-8?q?Santiago_Ruano_Rinc=C3=B3n?=
} [src:ldns] ldns: Python2 removal in sid/bullseye
Added tag(s) experimental.
> tags 962616 - sid bullseye
Bug #962616 [src:webkit2gtk] webkit2gtk: FTBFS on
Processing commands for cont...@bugs.debian.org:
> # the bts/britney combination doesn't consider the current source
> # package as fixing this bug
> reassign 959409 src:pbcopper 1.4.0+dfsg-1
Bug #959409 {Done: Andreas Tille } [libpbcopper1.3.0]
pbcopper breaks pbbam (autopkgtest):
Source: cunit
Version: 2.1-3-dfsg-2.2
Severity: serious
Autopkgtest fails since last NMU with the following messages:
autopkgtest [17:33:49]: test test.sh: [---
debian/tests/test.c:1:10: fatal error: stdio.h: No such file or directory
1 | #include
|
Your message dated Thu, 11 Jun 2020 20:17:31 +0200
with message-id <159189945107.4184237.2610750283687514...@auryn.jones.dk>
and subject line Re: Bug#940093: radicale 1.1.1: --export-storage option missing
has caused the Debian Bug report #940093,
regarding radicale 1.1.1: --export-storage option
All right with build now! \o/
However, I can see the CI tests failing again and we will need a new
NMU. We will work over it now (using Salsa to approve the local
changes in tests). I will open a bug.
Em qui., 11 de jun. de 2020 às 13:22, Adrian Bunk escreveu:
>
> Something unrelated missing on
Package: qbittorrent-nox
Version: 4.2.4-1+b1
Followup-For: Bug #962645
The same thing happens on the gui version of qbittorrent, at least on amd64!
The torrent is added as usual, it downloads as it should and once it is done,
qbittorrent crashes with the following output
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:svgpp
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package meson
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting
On 11/06/2020 18:34, Michael Borg wrote:
> Yep I know but I cannot tell all my customers to run this workaround, some
> of our users are not experienced at all The only thing I see here is
> that I need to provide a hotfix ourselves. We cannot wait for days... You
> are saying we cannot make
On Thu, Jun 11, 2020 at 11:45:45AM -0300, Eriberto wrote:
>...
> So, I did a double
> check using my sponsor checklist[1], I ran debuild and cowbuilder.
> After this I did a debuild -S and the trash inside debian/ was sent.
> Sorry for this.
>
> [1] http://bit.ly/pkgcheck
>...
When I sponsor
Your message dated Thu, 11 Jun 2020 16:21:44 +
with message-id
and subject line Bug#960011: fixed in libmath-gsl-perl 0.41-1
has caused the Debian Bug report #960011,
regarding libmath-gsl-perl: FTBFS with gsl 2.6
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 11 Jun 2020 16:21:44 +
with message-id
and subject line Bug#960011: fixed in libmath-gsl-perl 0.41-1
has caused the Debian Bug report #960011,
regarding libmath-gsl-perl: FBTFS (unsupported version: 2.6 at Build.PL line 80)
to be marked as done.
This means that you
Your message dated Thu, 11 Jun 2020 15:48:46 +
with message-id
and subject line Bug#962643: fixed in cunit 2.1-3-dfsg-2.2
has caused the Debian Bug report #962643,
regarding cunit: broken NMU does FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing control commands:
> severity -1 serious
Bug #962596 [ca-certificates] ca-certificates: Removal of GeoTrust Global CA
requires investigation
Severity set to 'serious' from 'important'
> tags -1 + pending
Bug #962596 [ca-certificates] ca-certificates: Removal of GeoTrust Global CA
Processing control commands:
> severity -1 serious
Bug #943322 [python3-llvmlite] llvmlite lags behind upstream verison; blocks
Numba update
Severity set to 'serious' from 'normal'
> block 962176 by -1
Bug #962176 [src:numba] numba: fails autopktest with numpy 1.18
962176 was not blocked by any
Hi Adrian, how are you?
Em qui., 11 de jun. de 2020 às 03:15, Adrian Bunk escreveu:
>
> On Thu, Jun 11, 2020 at 08:46:23AM +0300, Adrian Bunk wrote:
> >...
> > The diffstat of this NMU is
> > 510 files changed, 139791 insertions(+), 3 deletions(-)
> >
> > It is the responsibility of the sponsor
On Thu, Jun 11, 2020 at 11:19:10AM +0300, Adrian Bunk wrote:
> > > | Exception: gtkdoc-scangobj produced a non-zero return code 250
> > > | Command:
> > > | gtkdoc-scangobj --module=webkit2gtk-4.0
> > > | Error output:
> > > |
> > > |
> > > | ninja: build stopped: subcommand failed.
> >
> >
Processing control commands:
> tags 925746 + pending
Bug #925746 [src:libidn] libidn: ftbfs with GCC-9
Added tag(s) pending.
--
925746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags 925746 + pending
Dear maintainer,
I've prepared an NMU for libidn (versioned as 1.33-2.3) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer or cancel the NMU.
I've uploaded to experimental and if this fix work fine i'll
send a new upload to
Processing commands for cont...@bugs.debian.org:
> block 960495 with 949027
Bug #960495 [release.debian.org] transition: gdal
960495 was blocked by: 960369 953138 962641
960495 was not blocking any bugs.
Added blocking bug(s) of 960495: 949027
> thanks
Stopping processing here.
Please contact me
Processing commands for cont...@bugs.debian.org:
> tags 949027 + ftbfs
Bug #949027 [src:node-srs] node-srs: uses old python to build
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
949027:
Processing control commands:
> block 962651 by -1
Bug #962651 [rst2pdf] rst2pdf depends and build depends on python3-pdfrw that
might not be in bullseye
962651 was not blocked by any bugs.
962651 was blocking: 958362
Added blocking bug(s) of 962651: 962653
--
962651:
Source: davical
Version: 1.1.9.3-1
Severity: serious
Control: block 962651 by -1
davical build depends on rst2pdf that might not be in bullseye
due to #962651.
Your message dated Thu, 11 Jun 2020 10:00:41 +
with message-id
and subject line Bug#950127: fixed in pyside2 5.15.0-1~exp1
has caused the Debian Bug report #950127,
regarding pyside2 fails all autopkg tests
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Thu, 11 Jun 2020 10:00:11 +
with message-id
and subject line Bug#936832: fixed in ldns 1.7.1-1
has caused the Debian Bug report #936832,
regarding ldns: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Thu, 11 Jun 2020 10:00:40 +
with message-id
and subject line Bug#949339: fixed in pyside2 5.15.0-1~exp1
has caused the Debian Bug report #949339,
regarding libshiboken2-py3-5.14: missing Breaks+Replaces: libshiboken2-py3-5.13
to be marked as done.
This means that you claim
Your message dated Thu, 11 Jun 2020 10:00:41 +
with message-id
and subject line Bug#950126: fixed in pyside2 5.15.0-1~exp1
has caused the Debian Bug report #950126,
regarding pyside2 ftbfs in experimental
to be marked as done.
This means that you claim that the problem has been dealt with.
Package: rst2pdf
Version: 0.97-2
Severity: serious
Control: block 958362 by -1
rst2pdf depends and build depends on python3-pdfrw
that might not be in bullseye due to #958362.
Processing control commands:
> block 958362 by -1
Bug #958362 [src:pdfrw] pdfrw: fails with python 3.7+ -- abandoned upstream
958362 was not blocked by any bugs.
958362 was not blocking any bugs.
Added blocking bug(s) of 958362: 962651
--
958362:
On Thu, 25 Jul 2019 12:10:45 +0200 Johannes Rohr wrote:
> It would be great to have firefox (or the next firefox-esr) in
> buster-backports, as it has important new functionality relevant for
> privacy and data protection, such as the multi account containers
> function. However, this bug
Your message dated Thu, 11 Jun 2020 09:36:00 +
with message-id
and subject line Bug#958917: fixed in openmw 0.46.0-1
has caused the Debian Bug report #958917,
regarding openmw: random crashes
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Sebastian,
On 2020-06-11 at 09:11, sramac...@debian.org wrote:
> Hi bret
>
> On 2020-06-09 18:28:02 +0200, bret curtis wrote:
> > OpenMW 0.46 has been released and I've uploaded it here, it just
> > someone kind and just to review and upload.
Your message dated Thu, 11 Jun 2020 09:36:00 +
with message-id
and subject line Bug#961536: fixed in openmw 0.46.0-1
has caused the Debian Bug report #961536,
regarding openmw FTBFS with openscenegraph 3.6.5
to be marked as done.
This means that you claim that the problem has been dealt
Hi bret
On 2020-06-09 18:28:02 +0200, bret curtis wrote:
> OpenMW 0.46 has been released and I've uploaded it here, it just
> someone kind and just to review and upload. :)
>
> https://salsa.debian.org/games-team/openmw
>
> Once uploaded and built, this bug should be closed.
Thanks, uploaded
On Tue, Jun 09, 2020 at 03:21:37PM -0400, Olek Wojnar wrote:
> Any advice on this? I really want to do what's "right" and what's best for
> this package and the greater Debian infrastructure but I wonder if
> insisting on shipping symbols files is actually doing more harm than good.
> (e.g. I'm
On Wed, Jun 10, 2020 at 08:46:21PM +0200, Alberto Garcia wrote:
> On Wed, Jun 10, 2020 at 08:08:27PM +0200, Sebastian Ramacher wrote:
> > | Exception: gtkdoc-scangobj produced a non-zero return code 250
> > | Command:
> > | gtkdoc-scangobj --module=webkit2gtk-4.0
> > | Error output:
> > |
> >
Your message dated Thu, 11 Jun 2020 09:10:58 +0100
with message-id
and subject line re: openvdb: FTBFS with boost 1.71
has caused the Debian Bug report #960500,
regarding openvdb: FTBFS with boost 1.71
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
The Debian BTS does not automatically Cc anyone except the maintainer,
I only saw this message by chance.
On Fri, May 29, 2020 at 01:02:33PM +0200, Iñaki Malerba wrote:
>...
> Thanks for the upload, but that change is not going to pass autopkgtests
> (as it needs the dependencies for the tests),
Hi!
Sorry for my late reply.
I tried to exporting QT_XCB_GL_INTEGRATION=xcb_egl and it still reported an
error. libglvnd-dev package was originally installed.
Do you need other information?
Thank you in advance.
BRs
//Zongli
Hi,
This bug is still there:
DKMS make.log for wireguard-1.0.20200520 for kernel 4.19.0-8-amd64 (x86_64)
Thu 11 Jun 2020 08:42:36 AM CEST
make: Entering directory '/usr/src/linux-headers-4.19.0-8-amd64'
CC [M] /var/lib/dkms/wireguard/1.0.20200520/build/main.o
CC [M]
Processing commands for cont...@bugs.debian.org:
> severity 962629 serious
Bug #962629 [rainloop] rainloop: Rainloop stores passwords in cleartext in
logfile
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
962629:
Control: tags 868190 + pending
Dear maintainer,
I've prepared an NMU for gatling (versioned as 0.13-6.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer or cancel my upload.
Regards,
Fabio
diff -Nru gatling-0.13/debian/changelog
Your message dated Thu, 11 Jun 2020 06:18:44 +
with message-id
and subject line Bug#962253: fixed in esys-particle 2.3.5+dfsg2-1
has caused the Debian Bug report #962253,
regarding esys-particle: Broken section number in manpage
to be marked as done.
This means that you claim that the
On Thu, Jun 11, 2020 at 08:46:23AM +0300, Adrian Bunk wrote:
>...
> The diffstat of this NMU is
> 510 files changed, 139791 insertions(+), 3 deletions(-)
>
> It is the responsibility of the sponsor (Cc'ed) to verify that
> sponsored uploads are not broken:
>
Felix Lechner wrote:
> It would also give me more time to understand the possibly
> unreasonable burden on Lintian users across Debian and the derivative
> ecosystem. Simon may receive feedback from Ubuntu, a significant
> derivative. If there are real problems, I am happy to discuss a
> solution
Package: qbittorrent-nox
Version: 4.2.4-1+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Qbittorrent-nox has become unusable on both amd64 and i386 since the last
binary update (4.2.4-1 to 4.2.4-1+b1) which was 7 days ago. It worked as it
should before that update,
68 matches
Mail list logo
