Your message dated Thu, 17 Oct 2019 05:04:29 +
with message-id
and subject line Bug#922569: fixed in caffe 1.0.0+git20180821.99bd997-3
has caused the Debian Bug report #922569,
regarding FTBFS against opencv 4.0.1 (exp)
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 17 Oct 2019 04:19:05 +
with message-id
and subject line Bug#942113: fixed in 3depict 0.0.22-1.1
has caused the Debian Bug report #942113,
regarding 3depict: FTBFS on PPC64EL - POWERPC macro not always defined
to be marked as done.
This means that you claim that the
Processing control commands:
> tags -1 + pending
Bug #942113 [3depict] 3depict: FTBFS on PPC64EL - POWERPC macro not always
defined
Added tag(s) pending.
--
942113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942113
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + pending
On Thu, Oct 17, 2019 at 04:12:35PM +1300, Olly Betts wrote:
> And why does this only cause an error on one architecture? I downloaded
> and compared the headers in the amd64 and ppc64el libqhull-dev packages
> and they're identical. If neither __MWERKS__ nor
On Wed, Oct 16, 2019 at 11:30:47AM +0200, Thierry fa...@linux.ibm.com wrote:
> I've personally always used __powerpc__ .
> Here is my reference, very useful for all arch related defines :
> https://wiki.debian.org/ArchitectureSpecificsMemo
That page documents what's defined by GCC on Debian, but
Hi,
I uploaded a NMU to 5-day/delay queue. Feel free to cancel this
upload if needed.
Thanks.
Regards,
Thiago Andrade
diff -Nru fbcat-0.3/debian/changelog fbcat-0.3/debian/changelog
--- fbcat-0.3/debian/changelog 2012-05-13 18:02:07.0 -0300
+++ fbcat-0.3/debian/changelog
Processing commands for cont...@bugs.debian.org:
> severity 922566 serious
Bug #922566 [src:actiona] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from 'important'
> severity 922569 serious
Bug #922569 [src:caffe] FTBFS against opencv 4.0.1 (exp)
Severity set to 'serious' from
On Wed, Oct 16, 2019 at 7:45 PM peter green wrote:
> So it seems that to fix this the following steps are needed.
Yes, I'm keeping an eye on this package & the Noto Emoji font.
It was a mistake for fonttools to drop its Python2 package as early as
it did before important reverse dependencies
Hi Axel,
thanks for the immediate check and fix, very much appreciated.
> Why are you using bash here? The script has a "#!/bin/sh" shebang line
No special reason but simply habit ;-)
Best
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. + IFMGA
I can get the CVEs.
I can also backport the patches into stable along with the previous set.
Curiously, there were 6 patchsets and 6 security bugs. But not all of them
match up.
For example, two patchsets fix one bug and another patchset fixes a
directory traversal which isn't mentioned at all.
Your message dated Thu, 17 Oct 2019 03:22:23 +0200
with message-id <2019101701.hzdws42vv6ohb...@sym.noone.org>
and subject line Re: Bug#942481: unclutter-startup: fails to configure on
installation
has caused the Debian Bug report #942481,
regarding unclutter-startup: fails to configure on
Processing control commands:
> tag -1 confirmed pending
Bug #942481 [unclutter-startup] unclutter-startup: fails to configure on
installation
Added tag(s) pending and confirmed.
--
942481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942481
Debian Bug Tracking System
Contact
Control: tag -1 confirmed pending
Hi Norbert,
Norbert Preining wrote:
> I am not sure whether this is the failure of unclutter-startup or
> debconf, so please reassign if necessary.
Thanks for the bug report! I can reproduce this in a clean pbuilder
sid + experimental chroot.
It seems as if I
Package: unclutter-startup
Version: 8-22
Severity: serious
Hi,
I am not sure whether this is the failure of unclutter-startup or
debconf, so please reassign if necessary.
unclutter-startup cannot --configure properly and always terminates with
post-installation script subprocess
Processing commands for cont...@bugs.debian.org:
> severity 938407 serious
Bug #938407 [src:routes] routes: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> block 938816 by 938407
Bug #938816 [src:webtest] webtest: Python2 removal in sid/bullseye
938816 was blocked by:
Processing commands for cont...@bugs.debian.org:
> severity 938015 serious
Bug #938015 [src:python-pecan] python-pecan: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> block 938816 by 938015
Bug #938816 [src:webtest] webtest: Python2 removal in sid/bullseye
938816 was
Hi,
The assaultcube-data (1.2.0.2.1-3) package includes "XS-Autobuild: yes" in the
header portion of "debian/control"[1] and the disclaimer compliance with the
licenses contained in "debian/copyright"[2] where It's okay to create the
software automatically across multiple architectures and
Processing commands for cont...@bugs.debian.org:
> severity 936665 serious
Bug #936665 [src:grokmirror] grokmirror: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936665:
Hi.
As I posted earlier nototools build-depends on python-fonttools which is no
longer built by the fonttools source package. Since this package turned out not
to be eligable for autoremoval I decided to take a slightly deeper look.
nototools builds a single binary package, python-nototools
Hi,
Em sáb, 12 de out de 2019 às 13:23, Sebastiaan Couwenberg
escreveu:
>
> I suggest to first update src:openscenegraph to 3.6.
>
> Once that's in unstable file bugreports for the src:openscenegraph-3.4
> rdeps to have them migrate to 3.6.
I uploaded the new version on Alberto's behalf,
Greetings:
If you'd like a pcap file showing the client side of this bug, just
holler. The big picture of it in action is at:
https://www.artsackett.com/apt_fail.png
The wireshark window is showing apt's nausea -- in the whole .pcap file
there's the usual drop scenario: three requests
Package: apt
Version: 1.8.2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Attempting to install Debian10.1/AMD64 and/or updating/upgrading
existing
>
>
http://debomatic-i386.debian.net/distribution#unstable/llvm-toolchain-9/9-2/buildlog
>
> can't reproduce on a clean sbuild environmen, neither on builders.
>
> Please make sure you have all the build-deps installed, and share
> something more wrt build log and environment.
>
> G.
I did
Your message dated Wed, 16 Oct 2019 22:35:17 +
with message-id
and subject line Bug#871933: fixed in xsynth-dssi 0.9.4-4
has caused the Debian Bug report #871933,
regarding xsynth-dssi: no Gui for plugin after loading
to be marked as done.
This means that you claim that the problem has been
> libgnatvsn ftbfs in 9.2.1-10
Sorry for the mess.
After a successful build, it seems that I have incorrectly played the
autoreconf/quilt refresh/scp/git commit music.
A build currently tests the following fix.
--- a/debian/patches/ada-libgnatvsn.diff
+++ b/debian/patches/ada-libgnatvsn.diff
@@
Your message dated Wed, 16 Oct 2019 22:19:30 +
with message-id
and subject line Bug#941960: fixed in gnome-shell-extension-log-out-button
1.0.8-1
has caused the Debian Bug report #941960,
regarding gnome-shell-extension-log-out-button: fails to load under gnome-shell
3.34: TypeError:
On Wed, Oct 16, 2019 at 9:48 PM Salvatore Bonaccorso wrote:
> Ideally given the issues are denial of service issues, this would have
> been okay via a point release. But we discussed this coincidentally in
> the team concluding we could as well release it via security. But we
> were thinking of
Sorry, the correct URL to the edit history of core/loki/Visitor.h is
https://gitlab.kitware.com/xdmf/xdmf/commits/master/core/loki/Visitor.h
--
Jonas Lippuner, PhD
Scientist
Computational Physics and Methods, CCS-2
Center for Theoretical Astrophysics
Los Alamos National Laboratory
Package: libxdmf-dev
Version: 3.0+git20160803-5+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Starting in version 3.0+git20190531-1 of this package, the libloki header were
removed and the dependency on libloki-dev was introduced. Unfortunately,
libxdmf has modified
Source: jss
Version: 4.6.1-3
Severity: grave
Tags: security upstream
Forwarded: https://github.com/dogtagpki/jss/pull/284
Hi,
The following vulnerability was published for jss.
CVE-2019-14823[0]:
| A flaw was found in the "Leaf and Chain" OCSP policy implementation in
| JSS' CryptoManager
Your message dated Wed, 16 Oct 2019 19:50:40 +
with message-id
and subject line Bug#942322: fixed in sudo 1.8.27-1.1
has caused the Debian Bug report #942322,
regarding sudo: CVE-2019-14287: Potential bypass of Runas user restrictions
to be marked as done.
This means that you claim that the
Hi Romain,
On Wed, Oct 16, 2019 at 08:30:44PM +0200, Romain Francoise wrote:
> Hi Guillem,
>
> On Mon, Oct 14, 2019 at 3:45 PM Guillem Jover wrote:
> > With the latest upload to oldoldstable-security, the versions in
> > oldstable and stable are now lower. This means that upgrades will
> > not
[sent again with ASCII-only header, to not upset Debian mailservers]
Quoting Alexandre Rossi (2019-10-16 20:06:46)
> > >Do you require some assistance regarding a new upload of uwsgi? I'm
> > >eager to dedicate some time to it if you can't do so. :)
> >
> > I have a patch but I have not been
Source: wordpress
Version: 5.2.3+dfsg1-1
Severity: grave
Tags: security upstream
Justification: user security hole
Hi Craig,
See https://wordpress.org/news/2019/10/wordpress-5-2-4-security-release/
As in previous rounds, could you please requests the CVEs as neededfor
the found issues?
Hello,
Am 16.10.19 um 20:30 schrieb Romain Francoise:
> Hi Guillem,
>
> On Mon, Oct 14, 2019 at 3:45 PM Guillem Jover wrote:
>> With the latest upload to oldoldstable-security, the versions in
>> oldstable and stable are now lower. This means that upgrades will
>> not take effect for this
Hi Guillem,
On Mon, Oct 14, 2019 at 3:45 PM Guillem Jover wrote:
> With the latest upload to oldoldstable-security, the versions in
> oldstable and stable are now lower. This means that upgrades will
> not take effect for this package, which will be left built against
> libraries and packaging
Your message dated Wed, 16 Oct 2019 18:09:24 +
with message-id
and subject line Bug#941890: fixed in llvm-toolchain-9 1:9-3
has caused the Debian Bug report #941890,
regarding python-clang-7: missing dependency on libclang-7-dev
to be marked as done.
This means that you claim that the
Hi,
> >Do you require some assistance regarding a new upload of uwsgi? I'm
> >eager to dedicate some time to it if you can't do so. :)
>
> I have a patch but I have not been able to test it yet because the py2
> removal makes the package FTBS... I'm close to fix it though. I'll post an
>
Simon,
On Tue, Aug 27, 2019 at 05:46:32PM +0100, Mark Hindley wrote:
> Simon,
>
> I think I have finally got to the bottom of this. As you suspected it is apt's
> invocation of dpkg. See #935910.
This is now resolved in apt version 1.8.4 which is in both sid and bullseye.
I can no longer
Hi,
I can reproduce this issue:
Oct 16 18:00:46 localhost gnome-session[1169]: gnome-session-binary[1169]:
WARNING: Falling back to non-systemd startup procedure due to error:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.systemd1 was not provided by any
Source: python-flask-marshmallow
Version: 0.10.1-1
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: ftpmas...@debian.org, guptautkarsh2...@gmail.com,
python-modules-t...@lists.alioth.debian.org
I just accepted python-flask-marshmallow from NEW.
docs/_themes/flask/static/flasky.css_t
Your message dated Wed, 16 Oct 2019 17:06:09 +
with message-id
and subject line Bug#935562: fixed in python-googleapi 1.7.11-3
has caused the Debian Bug report #935562,
regarding Missing dependency on 'google-auth-httplib2>=0.0.3'
to be marked as done.
This means that you claim that the
Your message dated Wed, 16 Oct 2019 16:34:54 +
with message-id
and subject line Bug#942279: fixed in
golang-github-circonus-labs-circonus-gometrics 2.3.1-1
has caused the Debian Bug report #942279,
regarding golang-github-hashicorp-go-retryablehttp breaks
On Monday, 14 October 2019 6:40:17 AM AEDT Paul Gevers wrote:
> With a recent upload of golang-github-hashicorp-go-retryablehttp the
> autopkgtest of golang-github-circonus-labs-circonus-gometrics fails in
> testing when that autopkgtest is run with the binary packages of
>
Processing commands for cont...@bugs.debian.org:
> tags 942279 + pending
Bug #942279 [src:golang-github-hashicorp-go-retryablehttp,
src:golang-github-circonus-labs-circonus-gometrics]
golang-github-hashicorp-go-retryablehttp breaks
golang-github-circonus-labs-circonus-gometrics autopkgtest
Processing commands for cont...@bugs.debian.org:
> notfound 942279 golang-github-hashicorp-go-retryablehttp/0.6.2-1
Bug #942279 [src:golang-github-hashicorp-go-retryablehttp,
src:golang-github-circonus-labs-circonus-gometrics]
golang-github-hashicorp-go-retryablehttp breaks
Processing commands for cont...@bugs.debian.org:
> found 942279 golang-github-circonus-labs-circonus-gometrics/2.0.0-1
Bug #942279 [src:golang-github-hashicorp-go-retryablehttp,
src:golang-github-circonus-labs-circonus-gometrics]
golang-github-hashicorp-go-retryablehttp breaks
Processing commands for cont...@bugs.debian.org:
> notfound 942279 golang-github-circonus-labs-circonus-gometrics/2.0.0-1
Bug #942279 [src:golang-github-hashicorp-go-retryablehttp,
src:golang-github-circonus-labs-circonus-gometrics]
golang-github-hashicorp-go-retryablehttp breaks
Processing commands for cont...@bugs.debian.org:
> tags 934716 + fixed pending
Bug #934716 [src:cross-toolchain-base-mipsen] binutils patch applied, package
now ftbfs
Added tag(s) fixed and pending.
> tags 941057 + fixed pending
Bug #941057 [src:cross-toolchain-base-mipsen] c-t-b-mipsen tries to
Your message dated Wed, 16 Oct 2019 22:53:54 +0800
with message-id
and subject line Re: gcc-9-cross-mipsen: FTBFS (/usr/bin/python: bad
interpreter: No such file or directory)
has caused the Debian Bug report #935752,
regarding gcc-9-cross-mipsen: FTBFS (/usr/bin/python: bad interpreter: No
Processing commands for cont...@bugs.debian.org:
> tags 942442 + ftbfs
Bug #942442 [src:gcc-9] libgnatvsn ftbfs in 9.2.1-10
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
942442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942442
Debian
On Wed, 16 Oct 2019 04:19:58 -0700, Mo Zhou wrote:
> 2019.07.1-7 in experimental should be able to address all the remaining
> issues. If the upgrading process didn't automatically trigger the
> reinstallation of vendored modules (fixed in master branch), the manual
> invokation of
PCAP and VDE network transports require linking with userspace
libraries. The current build system has no means of passing these
as arguments.
This patch adds a script to expand the library list for linking
for these transports as well as any future driver that needs to
rely on additional
Source: mysql-5.7
Version: 5.7.26-1
Severity: grave
Tags: security upstream
Justification: user security hole
Hi
See
https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html#AppendixMSQL
for a list of CVEs affecting src:mysql-5.7.
Regards,
Salvatore
Package: src:gcc-9
Version: 9.2.1-10
Severity: serious
Tags: sid bullseye
libgnatvsn ftbfs in 9.2.1-10
[...]
make[5]: *** No rule to make target 'alloc.lo', needed by 'libgnatvsn.la'.
Stop.
make[5]: *** Waiting for unfinished jobs
Hi
2019.07.1-7 in experimental should be able to address all the remaining
issues. If the upgrading process didn't automatically trigger the
reinstallation of vendored modules (fixed in master branch), the manual
invokation of rakudo-helper.pl -R should be able to address the
problems.
Could you
Just did a test on sid up-to-date, and tests were fine.
Will be difficult to forward upstream with bug occuring "sometimes" and
not really reproducible.
On 10/15/19 9:35 PM, Paul Gevers wrote:
> Source: discosnp
> Version: 2.3.0-2
> Severity: serious
> Tags: sid bullseye
> X-Debbugs-CC:
Processing commands for cont...@bugs.debian.org:
> tags 942270 + pending confirmed
Bug #942270 [src:tasksel] task-spanish depends on removed manpages-es
Added tag(s) pending and confirmed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
942270:
Processing commands for cont...@bugs.debian.org:
> found 942418 3.34.0-4
Bug #942418 [libmutter-5-0] libmutter-5-0: Blank screen after upgrading to
bullseye, caused by failing wayland
Marked as found in versions mutter/3.34.0-4.
>
End of message, stopping processing here.
Please contact me if
Processing commands for cont...@bugs.debian.org:
> found 942165 2.1.6-1
Bug #942165 {Done: Moritz Schlarb }
[libapache2-mod-auth-openidc] CVE-2019-14857
Marked as found in versions libapache2-mod-auth-openidc/2.1.6-1.
> found 942165 2.3.10.2-1
Bug #942165 {Done: Moritz Schlarb }
Your message dated Wed, 16 Oct 2019 10:00:15 +
with message-id
and subject line Bug#940463: fixed in falkon 3.1.0+dfsg1-4
has caused the Debian Bug report #940463,
regarding falkon: Falkon crashes and even freezes entire desktop.
to be marked as done.
This means that you claim that the
Your message dated Wed, 16 Oct 2019 10:00:31 +
with message-id
and subject line Bug#942287: fixed in python-exif 2.2.0-4
has caused the Debian Bug report #942287,
regarding python3-exif: package name should be python3-exifread
to be marked as done.
This means that you claim that the problem
Same for stretch:
https://salsa.debian.org/debian/libapache2-mod-auth-openidc/commit/e0b3eac21212b12562721ab3c903c4f24eef9e8f
On 16.10.19 11:19, Moritz Schlarb wrote:
> Hi everyone,
>
> I have prepared a backport of the patches for the version packaged in
> Buster:
>
Processing commands for cont...@bugs.debian.org:
> severity 936270 important
Bug #936270 [src:calibre] calibre: Python2 removal in sid/bullseye
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936270:
severity 936270 important
thanks
Hi Stuart, hi Thomas,
@Thomas, thanks for reintroducing python-cherrypy3!
On Mon, 14 Oct 2019, Stuart Prescott wrote:
> bullseye would currently fail because there would be no Python 2 module for
> cherrypy3 available.
>
> While python-cherrypy3 should not yet
Hello
I've personally always used __powerpc__ .
Here is my reference, very useful for all arch related defines :
https://wiki.debian.org/ArchitectureSpecificsMemo
Cheers
Thierry
I've Cc:-ed tille as his was the most recent upload. Let me know if
you'd like me to NMU with a
Hi everyone,
I have prepared a backport of the patches for the version packaged in
Buster:
https://salsa.debian.org/debian/libapache2-mod-auth-openidc/commit/17e31b94a71ef02d1417bee6b0ef7b7379b40375
If you deem necessary and sufficient, please release as a security
update or otherwise I'll try
On 16/10/2019 08:53, Anton Ivanov wrote:
Signed-off-by: Anton Ivanov
---
arch/um/drivers/Makefile | 8
scripts/link-vmlinux.sh | 2 +-
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/arch/um/drivers/Makefile b/arch/um/drivers/Makefile
index 693319839f69..34355057ec85
Your message dated Wed, 16 Oct 2019 08:38:39 +
with message-id
and subject line Bug#942165: fixed in libapache2-mod-auth-openidc 2.4.0.3-1
has caused the Debian Bug report #942165,
regarding CVE-2019-14857
to be marked as done.
This means that you claim that the problem has been dealt with.
Signed-off-by: Anton Ivanov
---
arch/um/drivers/Makefile | 8
scripts/link-vmlinux.sh | 2 +-
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/arch/um/drivers/Makefile b/arch/um/drivers/Makefile
index 693319839f69..34355057ec85 100644
--- a/arch/um/drivers/Makefile
+++
Hi all,
A patch to fix the build for these follows.
I will stick to my original suggestion - pcap should be obsoleted in favour of
vector raw + BPF firmware load. The latter will work on interfaces where gso/gro
is enabled. The original pcap will fail on that due to the 1500 bytes size limit
in
Processing commands for cont...@bugs.debian.org:
> forwarded 942193 https://sourceware.org/bugzilla/show_bug.cgi?id=25109
Bug #942193 [dwz] dwz: dh_dwz freecad build regression: write_die: Assertion
`value && refdcu->cu_kind != CU_ALT' failed.
Set Bug forwarded-to-address to
Looks good to me! Thanks again for all your work on this.
Best,
--
Antoine Amarilli
On Wed, Oct 16, 2019 at 12:57:16AM -, Chris Lamb wrote:
> Hi Antoine,
>
> > Looks great! There's a grammar problem "This fix does not the situation"
> > but it doesn't matter.
>
> Whoops, fixed in:
>
>
73 matches
Mail list logo
