On Sun, Aug 30, 2020 at 12:02:03PM +0200, Bas Couwenberg wrote:
> Source: openjfx
> Version: 11.0.7+0-3
> Severity: serious
> Tags: ftbfs
> Justification: makes the package in question unusable or mostly so
>
> Dear Maintainer,
>
> openjfx (11.0.7+0-3) FTFBS everywhere due to issues with the
Processing control commands:
> severity -1 serious
Bug #965960 [chromium] chromium: Received signal 11 SEGV_ACCERR 04c03193.
can't load pages and extensions
Severity set to 'serious' from 'important'
> forcemerge -1 969395
Bug #965960 [chromium] chromium: Received signal 11 SEGV_ACCERR
Processing control commands:
> forwarded -1 https://bugreports.qt.io/browse/QTBUG-81313
Bug #969360 [libqt5webengine5] kmail freezes when selecting a read mail to show
Bug #967011 [libqt5webengine5] [i386] **CRASHING**:seccomp-bpf failure in
syscall 0403
Set Bug forwarded-to-address to
Control: forwarded -1 https://bugreports.qt.io/browse/QTBUG-81313
Control: tags -1 upstream fixed-upstream
It turns out it is a clash both with Chromium (powers Qt WebEngine) and glibc.
Check out the Red Hat bugs
https://bugzilla.redhat.com/show_bug.cgi?id=1812482 (Qt)
Processing control commands:
> severity -1 serious
Bug #967011 [libqt5webengine5] [i386] **CRASHING**:seccomp-bpf failure in
syscall 0403
Bug #969360 [libqt5webengine5] kmail freezes when selecting a read mail to show
Severity set to 'serious' from 'important'
Severity set to 'serious' from
Your message dated Tue, 01 Sep 2020 22:48:34 +
with message-id
and subject line Bug#957262: fixed in gdigi 0.4.0-1.1
has caused the Debian Bug report #957262,
regarding gdigi: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Package: sleef
Version: 3.4.1-4
Severity: serious
The most recent upload of sleef fixed the build on amd64, armhf, i386 and
ppc64el. Unfortunately
it is still failing on arm64, with the following error.
In file included from /<>/src/libm/sleefsimdsp.c:209:
/<>/src/arch/helpersve.h:94:27:
Package: chromium
Version: 83.0.4103.116-3+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Chromium crashes immediately with screen awsnap errorcode 256
Log;
Sep 1 20:37:43 debian dbus-daemon[439]: [system] Activating via systemd:
service name='org.bluez'
Forwarding our private conversation to the BTS (I hope none will mind, I
don't see anything private that shouldn't be public in the tracker here...)
Cheers,
Thomas Goirand (zigo)
Forwarded Message
Subject: Re: [Pkg-dpdk-devel] OVS cannot find DPDK
Date: Tue, 1 Sep 2020
Your message dated Tue, 01 Sep 2020 20:34:22 +
with message-id
and subject line Bug#969152: fixed in teckit 2.5.10+ds1-3
has caused the Debian Bug report #969152,
regarding teckit FTBFS on most architectures: symbol differences
to be marked as done.
This means that you claim that the problem
Hi,
intrigeri writes:
>> I hope that upstream will port the code to GTK 3 in time for the
>> Bullseye freeze :)
When I received your initial bug report, I followed the advice given in
Perl's Gtk3 module documentation to "run s/Gtk2/Gtk3/ on [the]
application." Unfortunately, that didn't work at
Processing commands for cont...@bugs.debian.org:
> reassign 966921 libdpdk-dev
Bug #966921 [src:openvswitch] openvswitch: FTBFS: configure: error: Could not
find DPDK library in default search path, Use --with-dpdk to specify the DPDK
library installed in non-standard location
Bug reassigned
Processing commands for cont...@bugs.debian.org:
> forcemerge 966846 968509
Bug #966846 [src:linux] Kernel panic (4.19.0-10): RIP
__cgroup_bpf_run_filter_skb
Bug #968625 [src:linux] Kernel null pointer deref in the TCP stack
Bug #969350 [src:linux] linux-image-4.19.0-10-amd64: Kernel regularly
Your message dated Tue, 01 Sep 2020 19:03:38 +
with message-id
and subject line Bug#968858: fixed in rust-curl-sys 0.4.36-1
has caused the Debian Bug report #968858,
regarding rust-curl-sys: autpkgtest failure
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 01 Sep 2020 19:03:31 +
with message-id
and subject line Bug#958632: fixed in lxdm 0.5.3-3
has caused the Debian Bug report #958632,
regarding lxdm: Build-Depends on deprecated dh-systemd which is going away
to be marked as done.
This means that you claim that the
Your message dated Tue, 01 Sep 2020 16:49:56 +
with message-id
and subject line Bug#969372: fixed in uwsgi 2.0.19.1-2
has caused the Debian Bug report #969372,
regarding uwsgi-emperor: SysV init script does nothing
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 01 Sep 2020 16:34:43 +
with message-id
and subject line Bug#964651: fixed in rust-core-arch 0.1.5-4
has caused the Debian Bug report #964651,
regarding rust-core-arch: FTBFS: dh_auto_test: error:
/usr/share/cargo/bin/cargo build returned exit code 101
to be marked as
Your message dated Tue, 01 Sep 2020 16:33:33 +
with message-id
and subject line Bug#964557: fixed in mini-buildd 1.9.1
has caused the Debian Bug report #964557,
regarding mini-buildd: FTBFS: help2man fails to generate
src/mini-buildd-super-portext.1
to be marked as done.
This means that you
Control: tag -1 pending
On salsa is the new upstream release 3.5.0.
Processing control commands:
> tag -1 pending
Bug #883157 [src:libapache2-mod-python] libapache2-mod-python: Please support
for Python3
Ignoring request to alter tags of bug #883157 to the same tags previously set
--
883157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883157
Debian Bug
Processing commands for cont...@bugs.debian.org:
> tags 883157 + pending
Bug #883157 [src:libapache2-mod-python] libapache2-mod-python: Please support
for Python3
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
883157:
On 30/08/2020 13:37, Richard Kettlewell wrote:
> On 30/08/2020 13:22, Salvatore Bonaccorso wrote:
>> Hi Richard,
Would you be able to test 4.19.142?
>>>
>>> If you can give me a route to getting .deb files for that version then
>>> sure - a download or a pointer to instructions.
>>
>>
Your message dated Tue, 01 Sep 2020 15:23:07 +
with message-id
and subject line Bug#937232: fixed in paleomix 1.3.0-1
has caused the Debian Bug report #937232,
regarding paleomix: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 01 Sep 2020 14:58:23 +
with message-id
and subject line Bug#969367: fixed in python-django 2:3.1.1-1
has caused the Debian Bug report #969367,
regarding python-django: CVE-2020-24583 CVE-2020-24584
to be marked as done.
This means that you claim that the problem has
Package: mailman-hyperkitty
Version: 1.1.0-9
Followup-For: Bug #954604
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu groovy ubuntu-patch
Dear Maintainer,
since the last update to setuptools the autopkgtest/dh_auto_test is not
running properly anymore, as pybuild tries to trigger
tags 969115 + wontfix
thanks
Hi,
Thank you for the FTBFS report. As it happens src:mysql-5.7 has been
deprecated by src:mysql-8.0 and I filed a removal bug 969095 for
src:mysql-5.7. So it seems pointless to fix this now.
Robie
On Thu, Aug 27, 2020 at 09:48:21PM +0200, Aurelien Jarno wrote:
>
Processing commands for cont...@bugs.debian.org:
> tags 969115 + wontfix
Bug #969115 [src:mysql-5.7] mysql-5.7: FTBFS with GCC 10: multiple definition
of symbols
Added tag(s) wontfix.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
969115:
Processing commands for cont...@bugs.debian.org:
> found 968947 1:3.1+dfsg-8+deb10u7
Bug #968947 [src:qemu] qemu: CVE-2020-14364: usb: out-of-bounds r/w access issue
Marked as found in versions qemu/1:3.1+dfsg-8+deb10u7.
> found 968947 1:3.1+dfsg-8
Bug #968947 [src:qemu] qemu: CVE-2020-14364:
Package: uwsgi-emperor
Version: 2.0.18-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After installing uwsgi-emperor 2.0.18 it's impossible to change the
running state of the service, as the provided init-script is doing
nothing. This can be easily seen by the script
Processing commands for cont...@bugs.debian.org:
> severity 968947 grave
Bug #968947 [src:qemu] qemu: CVE-2020-14364: usb: out-of-bounds r/w access issue
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
968947:
Your message dated Tue, 01 Sep 2020 11:35:09 +
with message-id
and subject line Bug#969367: fixed in python-django 2:2.2.16-1
has caused the Debian Bug report #969367,
regarding python-django: CVE-2020-24583 CVE-2020-24584
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> tags 969367 + upstream fixed-upstream
Bug #969367 [python-django] python-django: CVE-2020-24583 CVE-2020-24584
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
969367:
Processing commands for cont...@bugs.debian.org:
> found 969367 2:2.2.15-2
Bug #969367 [python-django] python-django: CVE-2020-24583 CVE-2020-24584
There is no source info for the package 'python-django' at version '2:2.2.15-2'
with architecture ''
Unable to make a source version for version
Package: python-django
Version: 1:1.10.7-2+deb9u9
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerabilities were published for python-django.
CVE-2020-24583
CVE-2020-24584
If you fix the vulnerabilities please also make sure to include the
CVE
Processing commands for cont...@bugs.debian.org:
> forwarded 957999 xsd-us...@codesynthesis.com
Bug #957999 [src:xsd] xsd: ftbfs with GCC-10
Set Bug forwarded-to-address to 'xsd-us...@codesynthesis.com'.
> --
Stopping processing here.
Please contact me if you need assistance.
--
957999:
Your message dated Tue, 01 Sep 2020 11:04:32 +
with message-id
and subject line Bug#967107: fixed in hasktags 0.71.2-2
has caused the Debian Bug report #967107,
regarding hasktags: FTBFS: unsatisfiable build-dependencies: Depends:
libghc-json-dev (< 0.10) but 0.10-1 is to be installed
to be
findent-3.1.7-1 is now available in sid.
On Tue, 4 Aug 2020 08:43:50 +0200 Willem Vermin wrote:
Hi Lucas,
thanks for mentioning the failing rebuild of findent.
It is caused by a change in bison-3.7. In this version the generated
file parser.hpp is now included in the generated parser.cpp.
Your message dated Tue, 01 Sep 2020 11:04:41 +
with message-id
and subject line Bug#957660: fixed in paraview 5.7.0-5
has caused the Debian Bug report #957660,
regarding paraview: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Hello,
On Wed, 19 Aug 2020 22:39:03 +0200 =?UTF-8?B?SsOpcsOpbXkgTGFs?=
wrote:
> Le mer. 19 ao??t 2020 ?? 21:12, Gianfranco Costamagna <
> locutusofb...@debian.org> a ??crit :
>
> > Source: nodejs
> > Version: 12.18.2~dfsg-1
> > Severity: serious
> >
> > Hello, looks like node-create-hask,
Source: ignition-math
Version: 6.4.0+ds-9
Severity: serious
Hello, your package failed to build on arm64, ppc64el, s390x, ia64, powerpc,
ppc64, riscv64
because of a testsuite error:
Start 22: UNIT_Pose_TEST
22/46 Test #22: UNIT_Pose_TEST ...***Failed0.00 sec
Running
On Tuesday, 1 September 2020 4:57:56 AM AEST Moritz Mühlenhoff wrote:
> There's radio silence on https://bugs.mysql.com/bug.php?id=98839,
They are not very transparent and their public bug tracker is somewhat
redundant, I think... They are also slow to make transitional changes...
> let's
Control: tags -1 pending
Hi,
I pushed the latest upstream version that supports Python3 to Git. The
only remaining issue is in the build-time test:
...
> raise child_exception_type(errno_num, err_msg, err_filename)
E FileNotFoundError: [Errno 2] No such file or
Processing control commands:
> tags -1 pending
Bug #937232 [src:paleomix] paleomix: Python2 removal in sid/bullseye
Added tag(s) pending.
--
937232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937232
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Tue, 1 Sep 2020 11:38:10 +0300
with message-id
and subject line Re: [debian-mysql] Bug#951059: marked as done
(mariadb-server-10.3: lc_messages=fr_FR leads to upgrade crash with apt)
has caused the Debian Bug report #951059,
regarding mariadb-server-10.3: lc_messages=fr_FR
Control: severity -1 normal
Severity: normal
Downgrading severity since ia64 is an esoteric platform and not worth
preventing the whole mariadb-10.3 from migrating from unstable to
testing for everybody.
Processing control commands:
> severity -1 normal
Bug #968914 [src:mariadb-10.3] mariadb-10.3: FTBFS on ia64: test
main.func_regexp_pcre crashes server
Severity set to 'normal' from 'serious'
--
968914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968914
Debian Bug Tracking System
Contact
Control: severity -1 important
On Fri, 21 Aug 2020 02:40:13 +0200 Frank Heckenbach wrote:
> % apt-get update
> Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
> Hit:2 http://archive.raspberrypi.org/debian buster InRelease
> Traceback (most recent call last):
...
> KeyError: 'rpi'
Processing control commands:
> severity -1 important
Bug #968757 [command-not-found] command-not-found: breaks apt-get update
Severity set to 'important' from 'critical'
--
968757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968757
Debian Bug Tracking System
Contact ow...@bugs.debian.org
48 matches
Mail list logo
