Processed: found 906315 in 0.12.8-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 906315 0.12.8-1
Bug #906315 [src:spice] spice: CVE-2018-10873: Missing check in 
demarshal.py:write_validate_array_item() allows for buffer overflow and denial 
of service
Marked as found in versions spice/0.12.8-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
906315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 906316 in 0.33-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 906316 0.33-1
Bug #906316 [src:spice-gtk] spice-gtk: CVE-2018-10873: Missing check in 
demarshal.py:write_validate_array_item() allows for buffer overflow and denial 
of service
Marked as found in versions spice-gtk/0.33-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
906316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#906315: spice: CVE-2018-10873: Missing check in demarshal.py:write_validate_array_item() allows for buffer overflow and denial of service

[Salvatore Bonaccorso]

Source: spice
Version: 0.14.0-1
Severity: grave
Tags: patch security upstream
Control: clone -1 -2
Control: reassign -2 src:spice-gtk 0.34-1.1
Control: retitle -2 spice-gtk: CVE-2018-10873: Missing check in 
demarshal.py:write_validate_array_item() allows for buffer overflow and denial 
of service

Hi,

The following vulnerability was published for spice.

CVE-2018-10873[0]:
|Missing check in demarshal.py:write_validate_array_item() allows for
|buffer overflow and denial of service

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-10873
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10873
[1] http://www.openwall.com/lists/oss-security/2018/08/17/1
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1596008
[3] 
https://gitlab.freedesktop.org/spice/spice-common/commit/bb15d4815ab586b4c4a20f4a565970a44824c42c

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: spice: CVE-2018-10873: Missing check in demarshal.py:write_validate_array_item() allows for buffer overflow and denial of service

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #906315 [src:spice] spice: CVE-2018-10873: Missing check in 
demarshal.py:write_validate_array_item() allows for buffer overflow and denial 
of service
Bug 906315 cloned as bug 906316
> reassign -2 src:spice-gtk 0.34-1.1
Bug #906316 [src:spice] spice: CVE-2018-10873: Missing check in 
demarshal.py:write_validate_array_item() allows for buffer overflow and denial 
of service
Bug reassigned from package 'src:spice' to 'src:spice-gtk'.
No longer marked as found in versions spice/0.14.0-1.
Ignoring request to alter fixed versions of bug #906316 to the same values 
previously set
Bug #906316 [src:spice-gtk] spice: CVE-2018-10873: Missing check in 
demarshal.py:write_validate_array_item() allows for buffer overflow and denial 
of service
Marked as found in versions spice-gtk/0.34-1.1.
> retitle -2 spice-gtk: CVE-2018-10873: Missing check in 
> demarshal.py:write_validate_array_item() allows for buffer overflow and 
> denial of service
Bug #906316 [src:spice-gtk] spice: CVE-2018-10873: Missing check in 
demarshal.py:write_validate_array_item() allows for buffer overflow and denial 
of service
Changed Bug title to 'spice-gtk: CVE-2018-10873: Missing check in 
demarshal.py:write_validate_array_item() allows for buffer overflow and denial 
of service' from 'spice: CVE-2018-10873: Missing check in 
demarshal.py:write_validate_array_item() allows for buffer overflow and denial 
of service'.

-- 
906315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906315
906316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: llvm-6.0 unable to build julia 0.7/1.0

[Debian Bug Tracking System]

Processing control commands:

> block 905807 by -1
Bug #905807 [julia] julia 0.7.0-1 doesn't build on ppc64el
905807 was not blocked by any bugs.
905807 was not blocking any bugs.
Added blocking bug(s) of 905807: 906314
> tag -1 +patch +confirmed
Bug #906314 [llvm-6.0-dev] llvm-6.0 unable to build julia 0.7/1.0
Added tag(s) patch.
Bug #906314 [llvm-6.0-dev] llvm-6.0 unable to build julia 0.7/1.0
Added tag(s) confirmed.

-- 
905807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905807
906314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#897739: close bug

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #897739 {Done: Yanhao Mo } [src:deepin-movie-reborn] 
deepin-movie-reborn: ftbfs with GCC-8
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions deepin-movie-reborn/3.2.8-1.

-- 
897739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#897739: close bug

[Adrian Bunk]

Control: reopen -1

On Mon, Jul 30, 2018 at 10:11:25AM +0800, Yanhao Mo wrote:
>...
> I believe this bug was fixed in newer version.

It was fixed for 64bit architectures, but not completely fixed for 32bit 
architectures:
https://buildd.debian.org/status/package.php?p=deepin-movie-reborn

> Yanhao Mo

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: fixed 897739 in 3.2.8-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 897739 3.2.8-1
Bug #897739 {Done: Yanhao Mo } [src:deepin-movie-reborn] 
deepin-movie-reborn: ftbfs with GCC-8
Marked as fixed in versions deepin-movie-reborn/3.2.8-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
897739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#905327: marked as done (Some apps hang randomly)

[Debian Bug Tracking System]

Your message dated Thu, 16 Aug 2018 23:49:10 +
with message-id 
and subject line Bug#905327: fixed in qtcurve 1.8.18+git20160320-3d8622c-6
has caused the Debian Bug report #905327,
regarding Some apps hang randomly
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
905327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kde-style-qtcurve-qt5
Version: 1.8.18+git20160320-3d8622c-5+b4
Severity: important

After a recent dist-upgrade and a restart I get random hangs in kvirc and
konsole. I'm not sure that QtCurve is the culprit but it's at the top of the
backtrace. When an app hangs it starts using 100% CPU and stops redrawing the
window. I think it happens when activating an inactive app window. Some things
from gdb with kvirc:


Thread 1 (Thread 0x7fffe44f35c0 (LWP 6161)):
#0  0x7fffe00ba064 in QtCurve::updateMenuBarEvent(QMouseEvent*, QMenuBar*)
(event=event@entry=0x7fffdbc0, menu=menu@entry=0x55e56770) at
./qt5/style/qtcurve_utils.cpp:250
#1  0x7fffe0091deb in QtCurve::Style::eventFilter(QObject*, QEvent*)
(this=0x55beb6a0, object=0x55e56770, event=0x7fffdbc0) at
./qt5/style/qtcurve_api.cpp:968
#2  0x7244c28b in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*)
(receiver=0x55e56770, event=0x7fffdbc0) at
kernel/qcoreapplication.cpp:1174
#3  0x72dae491 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x55b7dc80, receiver=receiver@entry=0x55e56770,
e=e@entry=0x7fffdbc0) at kernel/qapplication.cpp:3723
#4  0x72db5d28 in QApplication::notify(QObject*, QEvent*)
(this=, receiver=0x55e56770, e=0x7fffdbc0) at
kernel/qapplication.cpp:3203
#5  0x7244c579 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55e56770, event=0x7fffdbc0) at
../../include/QtCore/5.11.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:307
#6  0x72db5029 in QCoreApplication::sendEvent(QObject*, QEvent*)
(event=, receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234
#7  0x72db5029 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool)
(receiver=receiver@entry=0x55e56770, event=event@entry=0x7fffdbc0,
alienWidget=alienWidget@entry=0x55e56770, nativeWidget=0x55d9fae0,
buttonDown=buttonDown@entry=0x732a6870 ,
lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:2695
#8  0x72e07304 in QWidgetWindow::handleMouseEvent(QMouseEvent*)
(this=0x56043810, event=0x7fffdfc0) at
/usr/include/c++/8/bits/atomic_base.h:390
#9  0x72e09e8e in QWidgetWindow::event(QEvent*) (this=0x56043810,
event=0x7fffdfc0) at kernel/qwidgetwindow.cpp:280
#10 0x72dae4a1 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x55b7dc80, receiver=receiver@entry=0x56043810,
e=e@entry=0x7fffdfc0) at kernel/qapplication.cpp:3727
#11 0x72db5ae0 in QApplication::notify(QObject*, QEvent*)
(this=0x55b7dbb0, receiver=0x56043810, e=0x7fffdfc0) at
kernel/qapplication.cpp:3486
#12 0x7244c579 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x56043810, event=0x7fffdfc0) at
../../include/QtCore/5.11.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:307
#13 0x727eb53b in QCoreApplication::sendSpontaneousEvent(QObject*,
QEvent*) (event=0x7fffdfc0, receiver=0x56043810) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:237
#14 0x727eb53b in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
(e=0x56649530) at kernel/qguiapplication.cpp:2081
#15 0x727ed435 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
(e=e@entry=0x56649530) at kernel/qguiapplication.cpp:1816
#16 0x727c7b6b in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
(flags=...) at kernel/qwindowsysteminterface.cpp:1032
#17 0x7fffe35ffe5b in
QPAEventDispatcherGlib::processEvents(QFlags)
(this=0x55bc2a90, flags=...) at qeventdispatcher_glib.cpp:70
#18 0x7244b24b in
QEventLoop::exec(QFlags) (this=0x7fffe240,
flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140
#19 0x724533c2 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#20 0x556347cf in  ()
#21 

Bug#905354: marked as done (Some apps hang randomly)

[Debian Bug Tracking System]

Your message dated Thu, 16 Aug 2018 23:49:10 +
with message-id 
and subject line Bug#905354: fixed in qtcurve 1.8.18+git20160320-3d8622c-6
has caused the Debian Bug report #905354,
regarding Some apps hang randomly
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
905354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kde-style-qtcurve-qt5
Version: 1.8.18+git20160320-3d8622c-5+b4
Severity: important

After a recent dist-upgrade and a restart I get random hangs in kvirc and
konsole. I'm not sure that QtCurve is the culprit but it's at the top of the
backtrace. When an app hangs it starts using 100% CPU and stops redrawing the
window. I think it happens when activating an inactive app window. Some things
from gdb with kvirc:


Thread 1 (Thread 0x7fffe44f35c0 (LWP 6161)):
#0  0x7fffe00ba064 in QtCurve::updateMenuBarEvent(QMouseEvent*, QMenuBar*)
(event=event@entry=0x7fffdbc0, menu=menu@entry=0x55e56770) at
./qt5/style/qtcurve_utils.cpp:250
#1  0x7fffe0091deb in QtCurve::Style::eventFilter(QObject*, QEvent*)
(this=0x55beb6a0, object=0x55e56770, event=0x7fffdbc0) at
./qt5/style/qtcurve_api.cpp:968
#2  0x7244c28b in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*)
(receiver=0x55e56770, event=0x7fffdbc0) at
kernel/qcoreapplication.cpp:1174
#3  0x72dae491 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x55b7dc80, receiver=receiver@entry=0x55e56770,
e=e@entry=0x7fffdbc0) at kernel/qapplication.cpp:3723
#4  0x72db5d28 in QApplication::notify(QObject*, QEvent*)
(this=, receiver=0x55e56770, e=0x7fffdbc0) at
kernel/qapplication.cpp:3203
#5  0x7244c579 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55e56770, event=0x7fffdbc0) at
../../include/QtCore/5.11.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:307
#6  0x72db5029 in QCoreApplication::sendEvent(QObject*, QEvent*)
(event=, receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234
#7  0x72db5029 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool)
(receiver=receiver@entry=0x55e56770, event=event@entry=0x7fffdbc0,
alienWidget=alienWidget@entry=0x55e56770, nativeWidget=0x55d9fae0,
buttonDown=buttonDown@entry=0x732a6870 ,
lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:2695
#8  0x72e07304 in QWidgetWindow::handleMouseEvent(QMouseEvent*)
(this=0x56043810, event=0x7fffdfc0) at
/usr/include/c++/8/bits/atomic_base.h:390
#9  0x72e09e8e in QWidgetWindow::event(QEvent*) (this=0x56043810,
event=0x7fffdfc0) at kernel/qwidgetwindow.cpp:280
#10 0x72dae4a1 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x55b7dc80, receiver=receiver@entry=0x56043810,
e=e@entry=0x7fffdfc0) at kernel/qapplication.cpp:3727
#11 0x72db5ae0 in QApplication::notify(QObject*, QEvent*)
(this=0x55b7dbb0, receiver=0x56043810, e=0x7fffdfc0) at
kernel/qapplication.cpp:3486
#12 0x7244c579 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x56043810, event=0x7fffdfc0) at
../../include/QtCore/5.11.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:307
#13 0x727eb53b in QCoreApplication::sendSpontaneousEvent(QObject*,
QEvent*) (event=0x7fffdfc0, receiver=0x56043810) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:237
#14 0x727eb53b in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
(e=0x56649530) at kernel/qguiapplication.cpp:2081
#15 0x727ed435 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
(e=e@entry=0x56649530) at kernel/qguiapplication.cpp:1816
#16 0x727c7b6b in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
(flags=...) at kernel/qwindowsysteminterface.cpp:1032
#17 0x7fffe35ffe5b in
QPAEventDispatcherGlib::processEvents(QFlags)
(this=0x55bc2a90, flags=...) at qeventdispatcher_glib.cpp:70
#18 0x7244b24b in
QEventLoop::exec(QFlags) (this=0x7fffe240,
flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140
#19 0x724533c2 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#20 0x556347cf in  ()
#21 

Bug#904521: pypy-py: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/pypy-py/examples/genhtml.py

[Stefano Rivera]

Hi Niels (2018.08.16_15:03:27_-0700)

> > Any update on this bug?
> 
> Working on a solution. I'll filter /usr/share/doc in
> pypy{clean,compile}.

My thinking there is that it never makes sense to byte-compile things in
/usr/share/doc. (Unless specifically requested, not using the -p flag).

Piotr: The same bug exists in the fallback code that dh_pypy generates,
e.g.

# Automatically added by dh_pypy:
if which pypycompile >/dev/null 2>&1; then
pypycompile -p pypy-py
elif pypy -m py_compile >/dev/null 2>&1; then
dpkg -L pypy-py | grep '\.py$' | pypy -m py_compile - >/dev/null
fi

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#904521: pypy-py: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/pypy-py/examples/genhtml.py

[Stefano Rivera]

> Any update on this bug?

Working on a solution. I'll filter /usr/share/doc in
pypy{clean,compile}.

And I'll add a temporary cleanup task to pypyclean that runs on only .py
files in /usr/share/doc, and ignores errors. We'll have to carry that
for some years, I think.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#899940: marked as done (ntp: Invalid maintainer address pkg-ntp-maintain...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Thu, 16 Aug 2018 21:19:51 +
with message-id 
and subject line Bug#899940: fixed in ntp 1:4.2.8p12+dfsg-1
has caused the Debian Bug report #899940,
regarding ntp: Invalid maintainer address 
pkg-ntp-maintain...@lists.alioth.debian.org
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
899940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899940
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ntp
Version: 1:4.2.8p11+dfsg-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of ntp,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package ntp since the list address
pkg-ntp-maintain...@lists.alioth.debian.org used in the Maintainer:
field was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-ntp-maintain...@lists.alioth.debian.org is 1.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ntp
Source-Version: 1:4.2.8p12+dfsg-1

We believe that the bug you reported is fixed in the latest version of
ntp, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bernhard Schmidt  (supplier of updated ntp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Aug 2018 22:20:29 +0200
Source: ntp
Binary: ntp ntpdate ntp-doc sntp
Architecture: source
Version: 1:4.2.8p12+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NTP Team 
Changed-By: Bernhard Schmidt 
Description:
 ntp- Network Time Protocol daemon and utility programs
 ntp-doc- Network Time Protocol documentation
 ntpdate- client for setting system time from NTP servers (deprecated)
 sntp   - Network Time Protocol - sntp client
Closes: 476491 515246 899940
Changes:
 ntp (1:4.2.8p12+dfsg-1) unstable; urgency=medium
 .
   [ Bernhard Schmidt ]
   * New upstream version 4.2.8p12
   * Update Maintainer address to n...@packages.debian.org (Closes: #899940)
   * Update ntpdate.8 from ntpdate.html (Closes: #476491, #515246)
 .
   [ Peter Eisentraut ]
   * Remove Peter Eisentraut from Uploaders
Checksums-Sha1:
 ec7a2c2208e61bd3c7add2ebec8e2bbfdeb4fcd2 2276 ntp_4.2.8p12+dfsg-1.dsc
 59aaa1b64990d7a961467a90cb88a145cd7ab614 4366448 ntp_4.2.8p12+dfsg.orig.tar.xz
 6ef5d97830f9d5ecd1a2189012738e4099c21579 47920 
ntp_4.2.8p12+dfsg-1.debian.tar.xz
 392519e8c23612bebb6afd680b6688788ce094ee 8123 
ntp_4.2.8p12+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 ea7977c895ece45f2ae885583c391dd09d2233568546b02e72adbeda65af7afb 2276 

Bug#906308: CVE-2018-14348

[Moritz Muehlenhoff]

Source: libcgroup
Severity: grave
Tags: security

This was assigned CVE-2018-14348:
https://bugzilla.suse.com/show_bug.cgi?id=1100365
(cgred seems to be cgrulesengd in Debian)

Patch:
https://sourceforge.net/p/libcg/libcg/ci/0d88b73d189ea3440ccaab00418d6469f76fa590/

Cheers,
Moritz

Processed: block 906307 with 870537

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 906307 with 870537
Bug #906307 [src:clsync] clsync: pre-depends on multiarch-support in buster
906307 was not blocked by any bugs.
906307 was not blocking any bugs.
Added blocking bug(s) of 906307: 870537
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
906307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 906307

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 906307 + sid
Bug #906307 [src:clsync] clsync: pre-depends on multiarch-support in buster
Added tag(s) sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
906307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#906307: clsync: pre-depends on multiarch-support in buster

[Aurelien Jarno]

Source: clsync
Version: 0.4.1-1
Severity: serious
Tags: buster

The multiarch-support package is scheduled for removal in buster.
clsync is one of the last package in buster that still depends on
it. The dependency is added by old versions of debhelper, so in theory
the package would just need to get rebuild and migrated to testing.
Unfortunately it's not something possible as the package doesn't build
on most architectures due to bug#844778 which is opened for more almost
two years now.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#905615: marked as done (healpy: FTBFS with python 3.7)

[Debian Bug Tracking System]

Your message dated Thu, 16 Aug 2018 20:35:34 +
with message-id 
and subject line Bug#905615: fixed in healpy 1.12.3-1
has caused the Debian Bug report #905615,
regarding healpy: FTBFS with python 3.7
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
905615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: healpy
Version: 1.11.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

healpy fails to build in the python 3.7 build. From the build log:

...

| x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -flto -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/healpix_cxx -I/usr/include/python3.7m 
-I/usr/lib/python3/dist-packages/numpy/core/include -c 
healpy/src/_query_disc.cpp -o 
build/temp.linux-amd64-3.7/healpy/src/_query_disc.o -fopenmp
| In file included from /usr/include/python3.7m/numpy/ndarraytypes.h:1816:0,
|  from /usr/include/python3.7m/numpy/ndarrayobject.h:18,
|  from /usr/include/python3.7m/numpy/arrayobject.h:4,
|  from healpy/src/_query_disc.cpp:449:
| /usr/include/python3.7m/numpy/npy_1_7_deprecated_api.h:15:2: warning: 
#warning "Using deprecated NumPy API, disable it by " "#defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
|  #warning "Using deprecated NumPy API, disable it by " \
|   ^~~
| healpy/src/_query_disc.cpp: In function 'PyObject* 
__Pyx_PyCFunction_FastCall(PyObject*, PyObject**, Py_ssize_t)':
| healpy/src/_query_disc.cpp:9364:69: error: too many arguments to function
|  return (*((__Pyx_PyCFunctionFast)meth)) (self, args, nargs, NULL);
|  ^
| healpy/src/_query_disc.cpp: In function 'void 
__Pyx__ExceptionSave(PyThreadState*, PyObject**, PyObject**, PyObject**)':
| healpy/src/_query_disc.cpp:9676:21: error: 'PyThreadState {aka struct _ts}' 
has no member named 'exc_type'; did you mean 'curexc_type'?
|  *type = tstate->exc_type;
|  ^~~~
|  curexc_type
| healpy/src/_query_disc.cpp:9677:22: error: 'PyThreadState {aka struct _ts}' 
has no member named 'exc_value'; did you mean 'curexc_value'?
|  *value = tstate->exc_value;
|   ^
|   curexc_value
| healpy/src/_query_disc.cpp:9678:19: error: 'PyThreadState {aka struct _ts}' 
has no member named 'exc_traceback'; did you mean 'curexc_traceback'?
|  *tb = tstate->exc_traceback;
|^
|curexc_traceback
| healpy/src/_query_disc.cpp: In function 'void 
__Pyx__ExceptionReset(PyThreadState*, PyObject*, PyObject*, PyObject*)':
| healpy/src/_query_disc.cpp:9685:24: error: 'PyThreadState {aka struct _ts}' 
has no member named 'exc_type'; did you mean 'curexc_type'?
|  tmp_type = tstate->exc_type;
| ^~~~
| curexc_type
| healpy/src/_query_disc.cpp:9686:25: error: 'PyThreadState {aka struct _ts}' 
has no member named 'exc_value'; did you mean 'curexc_value'?
|  tmp_value = tstate->exc_value;
|  ^
|  curexc_value
| healpy/src/_query_disc.cpp:9687:22: error: 'PyThreadState {aka struct _ts}' 
has no member named 'exc_traceback'; did you mean 'curexc_traceback'?
|  tmp_tb = tstate->exc_traceback;
|   ^
|   curexc_traceback
| healpy/src/_query_disc.cpp:9688:13: error: 'PyThreadState {aka struct _ts}' 
has no member named 'exc_type'; did you mean 'curexc_type'?
|  tstate->exc_type = type;
|  ^~~~
|  curexc_type
| healpy/src/_query_disc.cpp:9689:13: error: 'PyThreadState {aka struct _ts}' 
has no member named 'exc_value'; did you mean 'curexc_value'?
|  tstate->exc_value = value;
|  ^
|  curexc_value
| healpy/src/_query_disc.cpp:9690:13: error: 'PyThreadState {aka struct _ts}' 
has no member named 'exc_traceback'; did you mean 'curexc_traceback'?
|  tstate->exc_traceback = tb;
|  ^
|  curexc_traceback
| healpy/src/_query_disc.cpp: In function 'int 
__Pyx__GetException(PyThreadState*, PyObject**, PyObject**, PyObject**)':
| healpy/src/_query_disc.cpp:9745:24: error: 'PyThreadState {aka struct _ts}' 
has no member named 'exc_type'; did you mean 'curexc_type'?
|  tmp_type = 

Bug#885679: marked as done (gnusim8085: Depends on unmaintained gtksourceview2)

[Debian Bug Tracking System]

Your message dated Fri, 17 Aug 2018 00:22:39 +0530
with message-id 

and subject line Fixed in latest upload
has caused the Debian Bug report #885679,
regarding gnusim8085: Depends on unmaintained gtksourceview2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
885679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnusim8085
Version: 1.3.7-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gtksourceview2
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends on gtksourceview2 which has not had a new release
since 2010.

Please port your package to GTK3 and gtksourceview3 and related
maintained libraries. Otherwise, please consider requesting that your
package be removed from Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Package: gnusim8085
Version: 1.4.1-1

The latest upstream version is using GTK 3 and GtkSourceView 3 as
build and runtime dependencies. This version is now available in
unstable and has been successfully built on all architectures.

Regards,
Onkar
-- 
Passion - Some people climb mountains - others write Free software.
Don't ask why - the reason is the same.--- End Message ---

Processed: [bts-link] source package aiopg

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package aiopg
> # 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 user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #904361 (http://bugs.debian.org/904361)
> # Bug title: python3-aiopg: fails to install with Python 3.7
> #  * https://github.com/aio-libs/aiopg/issues/436
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 904361 + fixed-upstream
Bug #904361 [python3-aiopg] python3-aiopg: fails to install with Python 3.7
Added tag(s) fixed-upstream.
> usertags 904361 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
904361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 906292

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 906292 + ftbfs
Bug #906292 [src:ocserv] ocserv build depends on the removed libprotobuf-c0-dev 
provides
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
906292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 906293

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 906293 + ftbfs
Bug #906293 [src:virtio-forwarder] virtio-forwarder build depends on the 
removed libprotobuf-c0-dev provides
Warning: Unknown package 'src:virtio-forwarder'
Added tag(s) ftbfs.
Warning: Unknown package 'src:virtio-forwarder'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
906293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#906293: virtio-forwarder build depends on the removed libprotobuf-c0-dev provides

[Adrian Bunk]

Source: virtio-forwarder
Version: 1.1.99.13-1~unstable
Severity: serious

The libprotobuf-c0-dev build dependency must be
updated to libprotobuf-c-dev.

Bug#906292: ocserv build depends on the removed libprotobuf-c0-dev provides

[Adrian Bunk]

Source: ocserv
Version: 0.11.9-1
Severity: serious

The libprotobuf-c0-dev build dependency must be
updated to libprotobuf-c-dev.

Processed: ITP: ruby-aes-key-wrap -- Ruby implementation of AES Key Wrap

[Debian Bug Tracking System]

Processing control commands:

> block 902721 by -1
Bug #902721 [ruby-json-jwt] CVE-2018-1000539
902721 was not blocked by any bugs.
902721 was not blocking any bugs.
Added blocking bug(s) of 902721: 906289

-- 
902721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902721
906289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: unblock 905379 with 906256

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unblock 905379 with 906256
Bug #905379 [anki] hangs after "'NoneType' object has no attribute 
'installEventFilter'"
905379 was blocked by: 906256
905379 was not blocking any bugs.
Removed blocking bug(s) of 905379: 906256
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
905379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#906256: Bug#905379: anki: hangs after "'NoneType' object has no attribute 'installEventFilter'"

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 906256 minor
Bug #906256 [libqt5webengine5] libqt5webview5: stack_trace_posix.cc failed to 
open file breaks other packages
Severity set to 'minor' from 'grave'
> retitle 906256 libqt5webview5: stack_trace_posix.cc failed to open file
Bug #906256 [libqt5webengine5] libqt5webview5: stack_trace_posix.cc failed to 
open file breaks other packages
Changed Bug title to 'libqt5webview5: stack_trace_posix.cc failed to open file' 
from 'libqt5webview5: stack_trace_posix.cc failed to open file breaks other 
packages'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
906256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#906256: Bug#905379: anki: hangs after "'NoneType' object has no attribute 'installEventFilter'"

[Julian Gilbey]

severity 906256 minor
retitle 906256 libqt5webview5: stack_trace_posix.cc failed to open file
thanks

Dear Qt maintainers,

I spoke too soon, it turns out; I tried anki on another machine and it
didn't give this error, yet it still bombed out.  So it seems that
this is not the cause of the anki bug.

The message is still occurring, though, but it seems as if it's
probably mostly harmless.

Still got no idea about the cause of the anki bug, mind you!

Best wishes,

   Julian

Bug#865505: php-horde-image 2.3.6-1+deb9u1 (CVE-2017-9773, CVE-2017-9774 & CVE-2017-14650)

[Chris Lamb]

Dear Sébastien,

> > I've prepared an upload to fix the following:
> > 
> >  php-horde-image (2.3.6-1+deb9u1) stretch-security; urgency=high
> >   
> >   * CVE-2017-9773: [...]
> >   * CVE-2017-9774: [...]
> >   * CVE-2017-14650: [...]
[…]
> it looks OK to me, please upload to security-master.

Uploaded to security-master.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#903533: marked as done (yapf FTBFS with Python 3.7 as supported version)

[Debian Bug Tracking System]

Your message dated Thu, 16 Aug 2018 15:04:39 +
with message-id 
and subject line Bug#903533: fixed in yapf 0.22.0-3
has caused the Debian Bug report #903533,
regarding yapf FTBFS with Python 3.7 as supported version
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
903533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yapf
Version: 0.22.0-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/yapf.html

...
I: pybuild base:217: cd 
/build/1st/yapf-0.22.0/.pybuild/cpython3_3.7_yapf/build; python3.7 -m nose 
.F...F..F...
==
FAIL: testAsyncAsNonKeyword 
(yapftests.reformatter_basic_test.BasicReformatterTest)
--
Traceback (most recent call last):
  File 
"/build/1st/yapf-0.22.0/.pybuild/cpython3_3.7_yapf/build/yapftests/reformatter_basic_test.py",
 line 2489, in testAsyncAsNonKeyword
self.assertCodeEqual(code, reformatter.Reformat(uwlines, verify=False))
  File 
"/build/1st/yapf-0.22.0/.pybuild/cpython3_3.7_yapf/build/yapftests/yapf_test_helper.py",
 line 57, in assertCodeEqual
self.fail('\n'.join(msg))
AssertionError: Code format mismatch:
Expected:
 > from util import async
 > 
 > 
 > class A(object):
 > def foo(self):
 > async.run()
 > 
 > def bar(self):
 > pass
Actual:
 > from util import async
 > 
 > 
 > class A(object):
 > def foo(self):
 > async .run()
 > 
 > def bar(self):
 > pass
Diff:
--- actual
+++ expected
@@ -3,7 +3,7 @@
 
 class A(object):
 def foo(self):
-async .run()
+async.run()
 
 def bar(self):
 pass

==
FAIL: testListComprehensionPreferThreeLinesForLineWrap 
(yapftests.reformatter_basic_test.BasicReformatterTest)
--
Traceback (most recent call last):
  File 
"/build/1st/yapf-0.22.0/.pybuild/cpython3_3.7_yapf/build/yapftests/reformatter_basic_test.py",
 line 526, in testListComprehensionPreferThreeLinesForLineWrap
self.assertCodeEqual(expected_formatted_code, reformatter.Reformat(uwlines))
  File 
"/build/1st/yapf-0.22.0/.pybuild/cpython3_3.7_yapf/build/yapftests/yapf_test_helper.py",
 line 57, in assertCodeEqual
self.fail('\n'.join(msg))
AssertionError: Code format mismatch:
Expected:
 > def given(y):
 >   long_variable_name = [
 >   long_var_name + 1
 >   for long_var_name, number_two in ()
 >   if long_var_name == 2 and number_two == 3
 >   ]
Actual:
 > def given(y):
 >   long_variable_name = [
 >   long_var_name + 1 for long_var_name, number_two in ()
 >   if long_var_name == 2 and number_two == 3
 >   ]
Diff:
--- actual
+++ expected
@@ -1,5 +1,6 @@
 def given(y):
   long_variable_name = [
-  long_var_name + 1 for long_var_name, number_two in ()
+  long_var_name + 1
+  for long_var_name, number_two in ()
   if long_var_name == 2 and number_two == 3
   ]

==
FAIL: testStronglyConnected (yapftests.split_penalty_test.SplitPenaltyTest)
--
Traceback (most recent call last):
  File 
"/build/1st/yapf-0.22.0/.pybuild/cpython3_3.7_yapf/build/yapftests/split_penalty_test.py",
 line 205, in testStronglyConnected
(']', None),
  File 
"/build/1st/yapf-0.22.0/.pybuild/cpython3_3.7_yapf/build/yapftests/split_penalty_test.py",
 line 72, in _CheckPenalties
self.assertEqual(list_of_expected, FlattenRec(tree))
AssertionError: Lists differ: [('['[25 chars]or', 0), ('a', 3000), ('in', 
3000), ('foo', 30[93 chars]one)] != [('['[25 chars]or', None), ('a', None), 
('in', None), ('foo',[99 chars]one)]

First differing element 2:
('for', 0)
('for', None)

  [('[', None),
   ('a', None),
-  ('for', 0),
?  ^

+  ('for', None),
?  

-  ('a', 3000),
-  ('in', 3000),
- 

Bug#905130: marked as done (hedgewars: FTBFS on armhf (tests fails))

[Debian Bug Tracking System]

Your message dated Thu, 16 Aug 2018 14:59:28 + (UTC)
with message-id <1814004333.12053160.1534431568...@mail.yahoo.com>
and subject line Re: Bug#905130: hedgewars: FTBFS on armhf (tests fails))
has caused the Debian Bug report #905130,
regarding hedgewars: FTBFS on armhf (tests fails)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
905130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hedgewars
Version: 0.9.24.1-dfsg-4
Severity: serious
Justification: FTBFS

Hi! durent the ongoing Qt transition your package FTBFS on armhf due to tests 
failures.

5/7 Test #1: drillrockets_boom.lua    Passed8.23 sec
6/7 Test #2: drillrockets_drill.lua ...   Passed   14.54 sec
7/7 Test #7: twothousandmines.lua .   Passed   82.14 sec

86% tests passed, 1 tests failed out of 7

Total Test time (real) =  84.47 sec

The following tests FAILED:
  6 - stuckcake.lua (Failed)
Errors while running CTest
make[1]: *** [Makefile:144: test] Error 8
make[1]: Leaving directory '/<>/obj-arm-linux-gnueabihf'
dh_auto_test: cd obj-arm-linux-gnueabihf && make -j4 test ARGS\+=-j4 returned 
exit code 2
make: *** [debian/rules:4: build-arch] Error 2

Regards, Lisandro.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'buildd-unstable'), (500, 'testing'), (500, 'stable'), 
(1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Hello,
>Oh, oops, sorry - it was Gianfranco!


Since hedgewars is now out from testing, qt has migrated, can we please close 
it?
I don't want to forget to close it once ftpmasters removes armhf architecture :)

I prefer to keep bugs open if sourceful fixes are needed

G.--- End Message ---

Processed: found 906277 in 1:6.0.0-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 906277 1:6.0.0-2
Bug #906277 [src:manila] manila: FTBFS on amd64: RecursionError during tests
Marked as found in versions manila/1:6.0.0-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
906277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#905960: amdgpu: After login the screen is corrupted, it is unusable in this state

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 xserver-xorg-video-ati 1:18.0.1-1
Bug #905960 [xserver-xorg-video-amdgpu] amdgpu: After login the screen is 
corrupted, it is unusable in this state
Bug reassigned from package 'xserver-xorg-video-amdgpu' to 
'xserver-xorg-video-ati'.
No longer marked as found in versions xserver-xorg-video-amdgpu/18.0.1-1.
Ignoring request to alter fixed versions of bug #905960 to the same values 
previously set
Bug #905960 [xserver-xorg-video-ati] amdgpu: After login the screen is 
corrupted, it is unusable in this state
Marked as found in versions xserver-xorg-video-ati/1:18.0.1-1.
> severity -1 important
Bug #905960 [xserver-xorg-video-ati] amdgpu: After login the screen is 
corrupted, it is unusable in this state
Severity set to 'important' from 'critical'
> forwarded -1 https://bugs.freedesktop.org/105381
Bug #905960 [xserver-xorg-video-ati] amdgpu: After login the screen is 
corrupted, it is unusable in this state
Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/105381'.
> tag -1 + upstream fixed-upstream
Bug #905960 [xserver-xorg-video-ati] amdgpu: After login the screen is 
corrupted, it is unusable in this state
Added tag(s) fixed-upstream and upstream.

-- 
905960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#905960: amdgpu: After login the screen is corrupted, it is unusable in this state

[Julien Cristau]

Control: reassign -1 xserver-xorg-video-ati 1:18.0.1-1
Control: severity -1 important
Control: forwarded -1 https://bugs.freedesktop.org/105381
Control: tag -1 + upstream fixed-upstream

On 08/15/2018 11:07 AM, Michel Dänzer wrote:
> On 2018-08-12 02:01 PM, Andrew Goodbody wrote:
>> Package: xserver-xorg-video-amdgpu
>> Version: 18.0.1-1+b1
>> Severity: critical
>> File: amdgpu
>> Justification: breaks the whole system
> 
> No it doesn't, so the severity is inflated. The package is wrong as
> well, should be xserver-xorg-video-radeon.
> 
> 
> Anyway, this looks like another instance of
> https://bugs.freedesktop.org/105381 , fixed in upstream xf86-video-ati
> Git master. Meanwhile, you can avoid the problem with
> 
>   Option  "AccelMethod" "EXA"
> 
> or the modesetting driver.
> 
> 
Updating bug metadata.  Thanks Michel!

Cheers,
Julien

Bug#876400: php-horde-image 2.3.6-1+deb9u1 (CVE-2017-9773, CVE-2017-9774 & CVE-2017-14650)

[Sébastien Delafond]

On Jun/23, Chris Lamb wrote:
> I've prepared an upload to fix the following:
> 
>  php-horde-image (2.3.6-1+deb9u1) stretch-security; urgency=high
>   
>   * CVE-2017-9773: [...]
> 
>   * CVE-2017-9774: [...]
> 
>   * CVE-2017-14650: [...]
>   
> The full debdiff is attached. Please let me know if it is okay to
> upload.

Hi Chris,

it looks OK to me, please upload to security-master.

Cheers,

--Seb

Bug#892539: Bug

[Ivo Blöchliger]

>
>   $ java -jar /usr/share/pdftk/pdftk.jar mypdf.pdf burst
>   Unhandled Java Exception in create_output():
>   java.lang.NoClassDefFoundError:
org/apache/commons/lang3/StringEscapeUtils

Same problem here, solved it by calling pdftk with the following wrapper
script (which might need editing to suit your needs, further missing
jar-files might be needed):

#!/bin/bash
/usr/bin/java -cp
/usr/share/java/commons-lang3.jar:/usr/local/bin/pdftk.jar pdftk "$@"

For reasons I did not follow or verify any further, the classpath (-cp)
option seems to have no effect when running the application with java -jar

Regards

Ivo

Processed: tagging 854555

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 854555 + buster sid
Bug #854555 [src:mpqc3] mpqc3: FTBFS on i386 and others: virtual memory 
exhausted
Added tag(s) buster and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
854555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: The result seems clearly grave for many users

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 903514 grave
Bug #903514 [src:glibc] Deadlock in _dl_close join-ing threads accessing TLS
Bug #904544 [src:glibc] gimp hangs on startup if libopenblas-base is installed
Bug #906152 [src:glibc] libopenblas-base: version 0.3.2+ds-1 makes gimp hang 
indefinitely
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
903514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903514
904544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904544
906152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: affects 906118

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 906118 src:esys-particle src:liggghts src:yorick
Bug #906118 [src:openmpi] openmpi: some builds and autopkgtests time out on 
i386, armhf
Added indication that 906118 affects src:esys-particle, src:liggghts, and 
src:yorick
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
906118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#900813: vm: fails to byte-compile with unversioned emacs

[Ian Jackson]

Ian Jackson writes ("vm: fails to byte-compile with unversioned emacs"):
> I'm just a user of VM but I need it to stay in Debian.  Accordingly I
> intend to NMU this time very soon.  I may well make mistakes.  Hints
> and tips welcome.
> 
> Manoj, if you don't want me to NMU this please upload a fix
> immediately.

I am still working on this.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#906274: php-apcu broken. apcu_entry() hangs, crashing the php interpreter.

[Peter Bosch]

Package: php-apcu
Version: 5.1.8+4.0.11-1
Severity: grave
Tags: patch fixed-upstream

I had originally reported this to ubuntu because we first noticed it on a 
machine running ubuntu, however, ubuntu doesnt seem to maintain this pkg so
therefore I am reporting this here.

After upgrading our testing server to bionic, our web application stopped
responding entirely after the second request. We traced this to a problem in 
php-apcu where it would block upon the second call to apcu_entry and completely
lock up the php processes causing the server to become unresponsive to any 
further requests.

This issue was already reported and fixed upstream (release 5.1.11) and I
have attached the diff for the corresponding commit, though I would like to
note that there have been 3 bugfix releases since the packaged version (5.1.9).

Upstream issue: https://github.com/krakjoe/apcu/issues/246

Affected systems: Anything running apcu with either php-fpm or apache with
  mod-php.


diff --git a/apc_cache.c b/apc_cache.c
index 3892c9e..8605525 100644
--- a/apc_cache.c
+++ b/apc_cache.c
@@ -1910,7 +1910,7 @@ PHP_APCU_API void apc_cache_entry(apc_cache_t *cache, zval *key, zend_fcall_info
 }
 			}
 		} else apc_cache_fetch_internal(cache, Z_STR_P(key), entry, now, _value);
-	}, apc_cache_entry_try_begin());
+	}, apc_cache_entry_try_end());
 }/*}}}*/
 #undef apc_cache_entry_try_begin
 #undef apc_cache_entry_try_end

Bug#905253: marked as done (python-txtorcon: fails to install with Python 3.7)

[Debian Bug Tracking System]

Your message dated Thu, 16 Aug 2018 12:19:48 +
with message-id 
and subject line Bug#905253: fixed in txtorcon 18.0.2-2
has caused the Debian Bug report #905253,
regarding python-txtorcon: fails to install with Python 3.7
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
905253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-txtorcon
Version: 18.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package python-txtorcon.
  (Reading database ... 
(Reading database ... 6833 files and directories currently installed.)
  Preparing to unpack .../python-txtorcon_18.0.2-1_all.deb ...
  Unpacking python-txtorcon (18.0.2-1) ...
  Setting up python-txtorcon (18.0.2-1) ...
File "/usr/lib/python2.7/dist-packages/txtorcon/controller_py3.py", line 13
  async def __aenter__(self):
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python-txtorcon (--configure):
   installed python-txtorcon package post-installation script subprocess 
returned error exit status 101
  Errors were encountered while processing:
   python-txtorcon


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python-txtorcon_18.0.2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: txtorcon
Source-Version: 18.0.2-2

We believe that the bug you reported is fixed in the latest version of
txtorcon, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Iain R. Learmonth  (supplier of updated txtorcon package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Aug 2018 12:50:11 +0100
Source: txtorcon
Binary: python3-txtorcon python-txtorcon-doc
Architecture: source all
Version: 18.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers 

Changed-By: Iain R. Learmonth 
Description:
 python-txtorcon-doc - Twisted-based asynchronous Tor control protocol 
implementation (D
 python3-txtorcon - Twisted-based asynchronous Tor control protocol 
implementation (P
Closes: 905253
Changes:
 txtorcon (18.0.2-2) unstable; urgency=medium
 .
   * No longer builds a Python 2 package (Closes: #905253)
   * Removes tor from suggests for python-txtorcon-doc
Checksums-Sha1:
 a23e498769e3b1f6067f275b1fa3dc33b7155d5e  txtorcon_18.0.2-2.dsc
 c01ea72ab886661f51f43c5a13189dad97c0b001 7904 txtorcon_18.0.2-2.debian.tar.xz
 c53d6a8fbe5356593c433b349b86abde9f06778b 175616 
python-txtorcon-doc_18.0.2-2_all.deb
 79cf6278b1832038b14c9ad5de7e1e78bc08fea7 109680 
python3-txtorcon_18.0.2-2_all.deb
 0b91c102e728892995f2e80d04bff6af50f7fb97 9689 txtorcon_18.0.2-2_amd64.buildinfo
Checksums-Sha256:
 5aafa6b6631ee42b3cf994f88ee4e460803f13bf7daa0fbbf0ed2ac922cb1fb7  
txtorcon_18.0.2-2.dsc
 69896539e9e5c83c719b9ed5ac4e8885b8b0cf490a85762440606ca44140d4b1 7904 
txtorcon_18.0.2-2.debian.tar.xz
 8242bdcae1878d01ab40d564918509e46eac675f0ab110821e5f5cf782c996da 175616 
python-txtorcon-doc_18.0.2-2_all.deb
 a069c9de924d8e5e1c934a85e9aa1b96d27fc42b1c2c98e6c4681e25794a8d0c 109680 
python3-txtorcon_18.0.2-2_all.deb
 10010e27fd7f83d4a80a48ecc8d583a4919c9f595520b03fea402d8b66b0896f 9689 
txtorcon_18.0.2-2_amd64.buildinfo
Files:
 3b352a688d92827d6b0979ed23324108  python optional txtorcon_18.0.2-2.dsc
 c8c5a0d146504171d851c53f52800680 7904 python optional 
txtorcon_18.0.2-2.debian.tar.xz
 ee51eb72257a206d69e11b439857e733 175616 doc optional 
python-txtorcon-doc_18.0.2-2_all.deb
 91624097c3dca6950be1f8eb97c86226 109680 python optional 
python3-txtorcon_18.0.2-2_all.deb
 c40adcf08fe165d04fa07822af3e4887 9689 python optional 
txtorcon_18.0.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Processed: Re: Bug#906220: kcalutils FTBFS with Qt 5.11

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #906219 [src:kcalutils] kcalutils build depends on libical2-dev
Added tag(s) pending.

-- 
906219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#906219: Bug#906220: kcalutils FTBFS with Qt 5.11

[Sandro Knauß]

Control: tag -1 pending

I currently prepare the new usptream version 18.08, that will upload soon to 
experimental, that fixes the issue.

hefee

signature.asc
Description: This is a digitally signed message part.

Processed: Re: Bug#906220: kcalutils FTBFS with Qt 5.11

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #906220 [src:kcalutils] kcalutils FTBFS with Qt 5.11
Added tag(s) pending.

-- 
906220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#906256: Bug#905379: anki: hangs after "'NoneType' object has no attribute 'installEventFilter'"

[Julian Gilbey]

Dear Qt maintainers,

I've cloned this bug reported against anki to libqt5webengine5, as it
seems that this is the source of the bug.  I don't know enough about
Qt's internals to be able to track it down.  It seems as though this
is a known problem: https://bugreports.qt.io/browse/QTBUG-68547
It's possible that the bug is in PyQt5, but that would seem unlikely.
But either way, something somewhere is very broken, and I don't know
exactly where.

The original report for your ease of reference, followed by a more
detailed explanation:

-

Package: anki
Version: 2.1.0+dfsg~rc2-2
Severity: grave
Justification: renders package unusable

Anki presents a dialog with the following error message at startup and
then hangs after the dialog is dismissed:

Error during startup:
Traceback (most recent call last):
  File "/usr/share/anki/aqt/main.py", line 50, in __init__
self.setupUI()
  File "/usr/share/anki/aqt/main.py", line 75, in setupUI
self.setupMainWindow()
  File "/usr/share/anki/aqt/main.py", line 585, in setupMainWindow
tweb =3D self.toolbarWeb =3D aqt.webview.AnkiWebView()
  File "/usr/share/anki/aqt/webview.py", line 114, in __init__
self.focusProxy().installEventFilter(self)
AttributeError: 'NoneType' object has no attribute 'installEventFilter'

Sending ^c after waiting for a minute or so of waiting produces the
error:

Exception ignored in: 
Traceback (most recent call last):
  File "/usr/lib/python3.6/threading.py", line 1294, in _shutdown
t.join()
  File "/usr/lib/python3.6/threading.py", line 1056, in join
self._wait_for_tstate_lock()
  File "/usr/lib/python3.6/threading.py", line 1072, in _wait_for_tstate_lock
elif lock.acquire(block, timeout):
KeyboardInterrupt

-

My analysis:

Anki runs (/usr/share/anki/aqt/webview.py, line 18):

QWebEngineView.__init__(self, parent=parent)

which seems to run fine, but something seems wrong, as
self.focusProxy() is Null after this.  A few lines later, it runs
(line 18):

QWebEnginePage.__init__(self)

which gives the error:

[0816/101823.790400:WARNING:stack_trace_posix.cc(699)] Failed to open file: 
/tmp/.gloFZVqc (deleted)
  Error: No such file or directory

And it's all downhill from there: a few lines later, it tries to call
self.focusProxy().installEventFilter(self), but as self.focusProxy()
is Null, it bombs out.

   Julian

Bug#867028: marked as done (uvloop FTBFS on armel/armhf: Test_UV_UnixSSL.test_create_unix_server_ssl_1 fails)

[Debian Bug Tracking System]

Your message dated Thu, 16 Aug 2018 11:46:29 +0200
with message-id 

and subject line Fixed with new upstream version
has caused the Debian Bug report #867028,
regarding uvloop FTBFS on armel/armhf: 
Test_UV_UnixSSL.test_create_unix_server_ssl_1 fails
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
867028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uvloop
Version: 0.8.0+ds1-1
Severity: serious

https://buildd.debian.org/status/package.php?p=uvloop

...
= test session starts ==
platform linux -- Python 3.5.3, pytest-3.0.6, py-1.4.32, pluggy-0.4.0
rootdir: /«BUILDDIR»/uvloop-0.8.0+ds1, inifile: 
collected 414 items

tests/test_aiohttp.py ..
tests/test_base.py ..ssssss...
tests/test_cython.py .
tests/test_dns.py s..
tests/test_executors.py 
tests/test_futures.py 
.
tests/test_pipes.py ..
tests/test_process.py ..
tests/test_signals.py ..
tests/test_sockets.py .
tests/test_tasks.py 

tests/test_tcp.py ..
tests/test_testbase.py ...
tests/test_udp.py .
tests/test_unix.py 
F/«BUILDDIR»/uvloop-0.8.0+ds1/.pybuild/pythonX.Y-dbg_3.5/build/uvloop/_testbase.py:81:
 ResourceWarning: unclosed resource 
  self.loop.close()
/usr/lib/python3.5/asyncio/sslproto.py:334: ResourceWarning: unclosed transport 

  warnings.warn("unclosed transport %r" % self, ResourceWarning)
/usr/lib/python3.5/asyncio/selector_events.py:630: ResourceWarning: unclosed 
transport <_SelectorSocketTransport fd=31>
  warnings.warn("unclosed transport %r" % self, ResourceWarning)
/usr/lib/python3.5/asyncio/selector_events.py:630: ResourceWarning: unclosed 
transport <_SelectorSocketTransport fd=32>
  warnings.warn("unclosed transport %r" % self, ResourceWarning)
/usr/lib/python3.5/asyncio/selector_events.py:630: ResourceWarning: unclosed 
transport <_SelectorSocketTransport fd=10>
  warnings.warn("unclosed transport %r" % self, ResourceWarning)
/usr/lib/python3.5/asyncio/selector_events.py:630: ResourceWarning: unclosed 
transport <_SelectorSocketTransport fd=12>
  warnings.warn("unclosed transport %r" % self, ResourceWarning)
/usr/lib/python3.5/asyncio/selector_events.py:630: ResourceWarning: unclosed 
transport <_SelectorSocketTransport fd=26>
  warnings.warn("unclosed transport %r" % self, ResourceWarning)
/usr/lib/python3.5/asyncio/selector_events.py:630: ResourceWarning: unclosed 
transport <_SelectorSocketTransport fd=27>
  warnings.warn("unclosed transport %r" % self, ResourceWarning)
/usr/lib/python3.5/asyncio/selector_events.py:630: ResourceWarning: unclosed 
transport <_SelectorSocketTransport fd=28>
  warnings.warn("unclosed transport %r" % self, ResourceWarning)
/usr/lib/python3.5/asyncio/selector_events.py:630: ResourceWarning: unclosed 
transport <_SelectorSocketTransport fd=29>
  warnings.warn("unclosed transport %r" % self, ResourceWarning)
/usr/lib/python3.5/asyncio/selector_events.py:630: ResourceWarning: unclosed 
transport <_SelectorSocketTransport fd=30>
  warnings.warn("unclosed transport %r" % self, ResourceWarning)
/«BUILDDIR»/uvloop-0.8.0+ds1/.pybuild/pythonX.Y-dbg_3.5/build/uvloop/_testbase.py:81:
 ResourceWarning: unclosed resource 
  self.loop.close()
_GatheringFuture exception was never retrieved
future: <_GatheringFuture finished exception=CancelledError()>
concurrent.futures._base.CancelledError
..

=== FAILURES ===
 Test_UV_UnixSSL.test_create_unix_server_ssl_1 _

self = 

def test_create_unix_server_ssl_1(self):
CNT = 0   # number of clients that were successful
TOTAL_CNT = 25# total number of clients that test will create
TIMEOUT = 5.0 # timeout for this test

A_DATA = b'A' * 1024 * 1024
B_DATA = b'B' * 1024 * 1024

sslctx = self._create_server_ssl_context(self.ONLYCERT, self.ONLYKEY)
client_sslctx = self._create_client_ssl_context()

clients = []

async def handle_client(reader, writer):
nonlocal CNT

data = await reader.readexactly(len(A_DATA))

Processed: found 906256 in 5.11.1+dfsg-5

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 906256 5.11.1+dfsg-5
Bug #906256 [libqt5webengine5] libqt5webview5: stack_trace_posix.cc failed to 
open file breaks other packages
Marked as found in versions qtwebengine-opensource-src/5.11.1+dfsg-5.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
906256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 906256 to libqt5webengine5

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 906256 libqt5webengine5
Bug #906256 [libqt5webview5] libqt5webview5: stack_trace_posix.cc failed to 
open file breaks other packages
Bug reassigned from package 'libqt5webview5' to 'libqt5webengine5'.
No longer marked as found in versions 5.11.1+dfsg-5.
Ignoring request to alter fixed versions of bug #906256 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
906256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: block 905379 with 906256

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 905379 with 906256
Bug #905379 [anki] hangs after "'NoneType' object has no attribute 
'installEventFilter'"
905379 was not blocked by any bugs.
905379 was not blocking any bugs.
Added blocking bug(s) of 905379: 906256
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
905379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#904995: xserver-common: black screen with mouse on screen rotate.

[Michel Dänzer]

On 2018-08-16 10:27 AM, Simon Polack wrote:
> The issue seems to be not limited to ATI/AMD graphics, as i face it on
> intel aswell.

That's probably a separate bug in the modesetting driver, which might
indeed be fixed in upstream xserver 1.20.1.


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer

Bug#904616: marked as done (keystone: CVE-2018-14432: GET /v3/OS-FEDERATION/projects leaks project information)

[Debian Bug Tracking System]

Your message dated Thu, 16 Aug 2018 08:49:20 +
with message-id 
and subject line Bug#904616: fixed in keystone 2:13.0.0-7
has caused the Debian Bug report #904616,
regarding keystone: CVE-2018-14432: GET /v3/OS-FEDERATION/projects leaks 
project information
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
904616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: keystone
Version: 2:13.0.0-1
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for keystone.

CVE-2018-14432[0]:
GET /v3/OS-FEDERATION/projects leaks project information

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-14432
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14432
[1] http://www.openwall.com/lists/oss-security/2018/07/25/2

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: keystone
Source-Version: 2:13.0.0-7

We believe that the bug you reported is fixed in the latest version of
keystone, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 904...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated keystone package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 06 Apr 2018 11:08:58 +
Source: keystone
Binary: keystone keystone-doc python3-keystone
Architecture: source all
Version: 2:13.0.0-7
Distribution: unstable
Urgency: high
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 keystone   - OpenStack identity service
 keystone-doc - OpenStack identity service - documentation
 python3-keystone - OpenStack identity service - library
Closes: 904616
Changes:
 keystone (2:13.0.0-7) unstable; urgency=high
 .
   [ Michal Arbet ]
   * Remove auth-token stuff
 .
   [ Thomas Goirand ]
   * Removed using twice --bootstrap-region-id ${REGION_NAME} when doing the
 keystone bootstraping.
   * CVE-2018-14432: authenticated user may discover projects they have no
 authority to access, leaking all projects in the deployment and their
 attributes. Applie upstream patch for Ocata rebased to Newton: "Reduce
 duplication in federated auth APIs (Closes: #904616).
 .
   [ Ondřej Nový ]
   * d/control: Use team+openst...@tracker.debian.org as maintainer
Checksums-Sha1:
 0eb3c39711f8f56864744ae43904cc1204979e79 3762 keystone_13.0.0-7.dsc
 0b4abd8f4d28a6a53be375df09cc16946817d1e8 39564 keystone_13.0.0-7.debian.tar.xz
 3d4118600e6291093d63b019db94e208c7a36b6b 1297036 keystone-doc_13.0.0-7_all.deb
 4465e69c0536d7b0567fe33fdab8f67e5ded3419 67068 keystone_13.0.0-7_all.deb
 0ef078ded42b2b80adf189fbdbedae2e9039155d 16371 
keystone_13.0.0-7_amd64.buildinfo
 c0ebf8a615b5f659844a31a908a85794f8c89fe0 605392 
python3-keystone_13.0.0-7_all.deb
Checksums-Sha256:
 cde5afd662faac19ace7d6a3926b636aa4e763972c3a87855ddc03df95c5ef93 3762 
keystone_13.0.0-7.dsc
 66bac4b9f5903e0fb5964ea3d5937ac3d51c99d4b55a64ae948b94c5964add02 39564 
keystone_13.0.0-7.debian.tar.xz
 3e48a79cab7cd3729dafce0a3bcca5b1cfd80cd5e1deb57da99e91b4e886 1297036 
keystone-doc_13.0.0-7_all.deb
 60dc5daa8349c6908af33d824d4affe66471b4c32fb4fccf35acdbe3805fb14d 67068 
keystone_13.0.0-7_all.deb
 caa4890398fe46c6f007bbf67a5ca1e836a4cbe4b45747067b19eb286f654046 16371 
keystone_13.0.0-7_amd64.buildinfo
 4fe99ea2a39a70eaf2b975927318b2df7f5685b7e112681f72e5aadbe1857f85 605392 
python3-keystone_13.0.0-7_all.deb
Files:
 4a4bbb6c3562354380e19b0fc7974b9b 3762 net optional keystone_13.0.0-7.dsc
 0bec547cc7a9fb10101656754bb4eaa8 39564 net optional 
keystone_13.0.0-7.debian.tar.xz
 c4c14dc13fa2a83768a40516815f2790 1297036 doc optional 
keystone-doc_13.0.0-7_all.deb
 46f0478ba3970b73eb675fa1e2aecc98 67068 net optional keystone_13.0.0-7_all.deb
 76d296c78c3d4cc84e3cf41a6dcb8b00 16371 net optional 
keystone_13.0.0-7_amd64.buildinfo
 fd7f6308ecd715ef0238eead2ef0153d 605392 python 

Bug#906164: marked as done (uvloop not compatible with Python 3.7)

[Debian Bug Tracking System]

Your message dated Thu, 16 Aug 2018 08:39:31 +
with message-id 
and subject line Bug#906164: fixed in uvloop 0.11.2+ds1-1
has caused the Debian Bug report #906164,
regarding uvloop not compatible with Python 3.7
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
906164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906164
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:uvloop
Version: 0.9.1+ds1-1
Tags: sid buster fixed-upstream
Severity: serious

uvloop is not compatible with Python 3.7. this is fixed upstream in 0.11.2.
--- End Message ---
--- Begin Message ---
Source: uvloop
Source-Version: 0.11.2+ds1-1

We believe that the bug you reported is fixed in the latest version of
uvloop, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 906...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated uvloop package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Aug 2018 10:10:13 +0200
Source: uvloop
Binary: python3-uvloop python3-uvloop-dbg
Architecture: source
Version: 0.11.2+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski 
Changed-By: Ondřej Nový 
Description:
 python3-uvloop - fast implementation of asyncio event loop on top of libuv
 python3-uvloop-dbg - fast implementation of asyncio event loop on top of libuv 
- dbg
Closes: 906164
Changes:
 uvloop (0.11.2+ds1-1) unstable; urgency=medium
 .
   * Team upload.
   * Uploading to unstable
   * New upstream release (Closes: #906164)
   * Convert git repository from git-dpm to gbp layout
   * Add python3-psutil to B-D
   * Bump debhelper compat level to 11
   * Enable autopkgtest-pkg-python testsuite
   * d/control: Deduplicate short description of -dbg package
   * Disable pipe tests - doesn't work inside sbuild
   * d/copyright: Adapt for new upstream release
   * Enable all hardening
   * Standards-Version is 4.2.0 (no changes)
   * Add upstream metadata
   * Disable timing/unreliable tests
Checksums-Sha1:
 36e8c6cee5cb9644fd6aea355e2d94ddd4c5ce7f 2207 uvloop_0.11.2+ds1-1.dsc
 d282ad9da747f2fe48c58af84e3f66f30d98de35 826697 uvloop_0.11.2+ds1.orig.tar.gz
 ca7518ee8822c23ac2455d9b3b72d8e0f16a3ceb 6772 uvloop_0.11.2+ds1-1.debian.tar.xz
 dd6514d13eec40c7d0ff5d8962d526649852e506 7702 
uvloop_0.11.2+ds1-1_amd64.buildinfo
Checksums-Sha256:
 f3e327fdfe3ef258b9bef9bae2f6752f615d929762908e1001bc1b4584ade86c 2207 
uvloop_0.11.2+ds1-1.dsc
 059a7de0335593815af66eb7f1ee9880ce959858078fa7dbddac8b95c5e3c580 826697 
uvloop_0.11.2+ds1.orig.tar.gz
 628e4065e8df6053c8dd74434cbe1a6a2ff543b72640e202c53620c0c281238e 6772 
uvloop_0.11.2+ds1-1.debian.tar.xz
 740a76d7209e680b12840541396517ac75c86ffa0a638a5ed3789d1dcbfba266 7702 
uvloop_0.11.2+ds1-1_amd64.buildinfo
Files:
 fb2de0cdc937f02ae1928f53e1a1 2207 python optional uvloop_0.11.2+ds1-1.dsc
 9394781aced62c4578bc23359030270f 826697 python optional 
uvloop_0.11.2+ds1.orig.tar.gz
 5835534e0ec3cc987ff060135f826364 6772 python optional 
uvloop_0.11.2+ds1-1.debian.tar.xz
 e4a501e46f9813b79fce609a6ef4fa35 7702 python optional 
uvloop_0.11.2+ds1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAlt1NOMACgkQNXMSVZ0e
BktypRAAjhnhZIufjNQGw5mAf3zijW4b718/IoJ2iu9xOwcd4uxchoxzlZTc0vE+
xlxQUJQpA+vAeJTM36WoVuumS1hrTvNrw3P6jzOrBckxQRDXUr2ruL+MZVaShSFw
qTLr99cHoJ4NZSfvZ3wQboAOGhqfxaN6RW/wFQh1rlbzqAVebPnCt6EDsclrvR5a
/810FzID6ZNrzYyh9hDafEDEgYEZ7zc10x7AJ/z3fAgcJZi9szLF0kdX/XNfyQbm
4HxpePqQUWsE8jVQnrguVBr53r9xZlp1yFMZIgLPabNgfCSPz7S1VuVuYoa7o0Z7
g9l9SWfivK8h7vaYPLkEto8/kIDfadeIvyMQ6UnNLuwrG58VqPHyPY35cYkavzDw
7nBaaTsSt35EjJusnqakBMcuHFKXYTKZMQ74C1DmiZxnUzpI8C1wNRcwBMmjfHQj
bNZCeWsFUNHHtAgFopPhuaD1OLbaFNyOD/ZWZF7DjCQRvvX8BLjWdeJ1SNRaA1VU
fJDqM9Ac5m8ja7H+U2WNPJf+T2k5ASFKARL175lvGgQgdpdvbzd+jodkfIVo5Fl/
XVDKO2ti5FESvovt4fz14p5X9P6T6Zzkb9Ub1HsTRT8hszRVLGKsRDVctgafKHPY
OnlDcrFHEfbQQRnmxAj5WeWSPj0ibmoJ+wK2R1fP+NyMlVM0WRE=
=xgC0
-END PGP SIGNATURE End Message ---

Bug#905193: Bug #905193 in alot marked as pending

[Jordan Justen]

Control: tag -1 pending

Hello,

Bug #905193 in alot 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/python-team/applications/alot/commit/872c3add437d3e53d8c711b25d556afc6b0f49e3


d/scripts: Use symlink_to_dir to fix piuparts upgrade failure. Closes: #905193

Convert to using symlink_to_dir.

Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905193
Signed-off-by: Jordan Justen 



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/905193

Processed: Bug #905193 in alot marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #905193 [alot-doc] alot-doc: unhandled symlink to directory conversion: 
/usr/share/doc/alot/html -> ../alot-doc/html
Ignoring request to alter tags of bug #905193 to the same tags previously set

-- 
905193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 897764 is forwarded to deve...@faert.net

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 897764 deve...@faert.net
Bug #897764 [src:guymager] guymager: ftbfs with GCC-8
Set Bug forwarded-to-address to 'deve...@faert.net'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
897764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#904995: xserver-common: black screen with mouse on screen rotate.

[Simon Polack]

The issue seems to be not limited to ATI/AMD graphics, as i face it on
intel aswell. Downgrading to 1.19 fixes all issues.

On Tue, 14 Aug 2018 12:33:20 +0200 =?UTF-8?Q?Michel_D=c3=a4nzer?=
 wrote:
> On 2018-08-14 11:34 AM, Simon Polack wrote:
> > Package: xserver-common
> > Version: 2:1.20.0-3
> > Followup-For: Bug #904995
> > 
> > Dear Maintainer,
> > 
> > please upgrade to current upstream bugfix release 1.20.1. Thank you a
> > lot.
> 
> It probably won't make a difference for this particular bug, though, as
> it's an xf86-video-ati bug.
> 
> 
> -- 
> Earthling Michel Dänzer   |   http://www.amd.com
> Libre software enthusiast | Mesa and X developer
> 
> 

Bug#905193: Bug #905193 in alot marked as pending

[Jordan Justen]

Control: tag -1 pending

Hello,

Bug #905193 in alot 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/python-team/applications/alot/commit/e5b4fc804d4afe6d691611f68bfc227fd8b816f9


d/preinst: Add preinst to fix piuparts upgrade failure. Closes: #905193

This pre-install script removes old package symlinks. These symlinks
cause trouble for package upgrades, and piuparts was flagging this
error.

Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905193
Signed-off-by: Jordan Justen 



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/905193

Processed: Bug #905193 in alot marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #905193 [alot-doc] alot-doc: unhandled symlink to directory conversion: 
/usr/share/doc/alot/html -> ../alot-doc/html
Added tag(s) pending.

-- 
905193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: cloning 905379, reassign -1 to libqt5webview5 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 905379 -1
Bug #905379 [anki] hangs after "'NoneType' object has no attribute 
'installEventFilter'"
Bug 905379 cloned as bug 906256
> reassign -1 libqt5webview5 5.11.1+dfsg-5
Bug #906256 [anki] hangs after "'NoneType' object has no attribute 
'installEventFilter'"
Bug reassigned from package 'anki' to 'libqt5webview5'.
No longer marked as found in versions anki/2.1.0+dfsg~rc2-2 and 
anki/2.1.0+dfsg-1.
Ignoring request to alter fixed versions of bug #906256 to the same values 
previously set
Bug #906256 [libqt5webview5] hangs after "'NoneType' object has no attribute 
'installEventFilter'"
There is no source info for the package 'libqt5webview5' at version 
'5.11.1+dfsg-5' with architecture ''
Unable to make a source version for version '5.11.1+dfsg-5'
Marked as found in versions 5.11.1+dfsg-5.
> retitle -1 libqt5webview5: stack_trace_posix.cc failed to open file breaks 
> other packages
Bug #906256 [libqt5webview5] hangs after "'NoneType' object has no attribute 
'installEventFilter'"
Changed Bug title to 'libqt5webview5: stack_trace_posix.cc failed to open file 
breaks other packages' from 'hangs after "'NoneType' object has no attribute 
'installEventFilter'"'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
905379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905379
906256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug #904616 in keystone marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #904616 [src:keystone] keystone: CVE-2018-14432: GET 
/v3/OS-FEDERATION/projects leaks project information
Added tag(s) pending.

-- 
904616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#904616: Bug #904616 in keystone marked as pending

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #904616 in keystone 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/openstack-team/services/keystone/commit/83ae87061a0a40a208431a57d3518c8ad33a35da


  * CVE-2018-14432: authenticated user may discover projects they have no
authority to access, leaking all projects in the deployment and their
attributes. Applie upstream patch for Ocata rebased to Newton: "Reduce
duplication in federated auth APIs (Closes: #904616).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/904616

Bug#906253: linpsn: FTBFS: invalid use of incomplete type 'class QButtonGroup'

[Damyan Ivanov]

Package: src:linpsk
Version: 1.3.5-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

Taken from the attached build log:

-
g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -D_REEN
TRANT -Wall -W -fPIC -DQT_NO_DEBUG -DWITH_HAMLIB -DQT_NO_DEBUG -DQT_WIDGETS_LIB 
-DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -I. -Isrc -Igui -isystem /u
sr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include
/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -isystem /usr/include/libdrm -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mksp
ecs/linux-g++ -o modemenu.o gui/modemenu.cpp
gui/modemenu.cpp: In constructor 'ModeMenu::ModeMenu(QStringList, QWidget*, 
Qt::WindowFlags)':
gui/modemenu.cpp:37:31: error: invalid use of incomplete type 'class 
QButtonGroup'
 Stopbits=new QButtonGroup(this);
   ^
In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qpushbutton.h:44,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QPushButton:1,
 from ./ui_modemenu.h:18,
 from gui/modemenu.h:26,
 from gui/modemenu.cpp:22:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qabstractbutton.h:53:7: note: 
forward declaration of 'class QButtonGroup'
 class QButtonGroup;
   ^~~~
gui/modemenu.cpp:38:9: error: invalid use of incomplete type 'class 
QButtonGroup'
 Stopbits->addButton(One,0);
 ^~
-

-- dam
sbuild (Debian sbuild) 0.77.0 (06 July 2018) on pc1.creditreform.bg

+==+
| linpsk (amd64)   Thu, 16 Aug 2018 05:30:24 + |
+==+

Package: linpsk
Distribution: sid
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/sid-b53f9505-1f87-44a4-90e1-7aef5fb1dc55' with 
'<>'
I: NOTICE: Log filtering will replace 'build/linpsk-BQpjkA/resolver-V4KMFF' 
with '<>'

+--+
| Update chroot|
+--+

Get:1 http://proxy:/debian sid InRelease [233 kB]
Get:2 http://proxy:/debian sid/main Sources.diff/Index [27.9 kB]
Get:3 http://proxy:/debian sid/main amd64 Packages.diff/Index [27.9 kB]
Get:4 http://proxy:/debian sid/main Sources 2018-08-15-2015.35.pdiff [6423 
B]
Get:4 http://proxy:/debian sid/main Sources 2018-08-15-2015.35.pdiff [6423 
B]
Get:5 http://proxy:/debian sid/main amd64 Packages 2018-08-15-2015.35.pdiff 
[54.5 kB]
Get:5 http://proxy:/debian sid/main amd64 Packages 2018-08-15-2015.35.pdiff 
[54.5 kB]
Fetched 349 kB in 1s (314 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

+--+
| Fetch source files   |
+--+


Check APT
-

Checking available source versions...

Download source files with APT
--

Reading package lists...
NOTICE: 'linpsk' packaging is maintained in the 'Git' version control system at:
https://anonscm.debian.org/git/pkg-hamradio/linpsk.git
Please use:
git clone https://anonscm.debian.org/git/pkg-hamradio/linpsk.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 129 kB of source archives.
Get:1 http://proxy:/debian sid/main linpsk 1.3.5-1 (dsc) [1630 B]
Get:2 http://proxy:/debian sid/main linpsk 1.3.5-1 (tar) [122 kB]
Get:3 http://proxy:/debian sid/main linpsk 1.3.5-1 (diff) [5168 B]
Fetched 129 kB in 0s (0 B/s)
Download complete and in download only mode
I: NOTICE: Log filtering will replace 'build/linpsk-BQpjkA/linpsk-1.3.5' with 
'<>'
I: NOTICE: Log filtering will replace 'build/linpsk-BQpjkA' with '<>'

+--+
| Install package build dependencies   |
+--+


Setup apt archive
-

Merged Build-Depends: debhelper (>> 9), qtbase5-dev, libasound2-dev, 
libcsnd-dev, libfftw3-dev, libhamlib-dev, pkg-config, 

Bug#905616: marked as done (FTBFS: ariba/ext/minimap_ariba.cpp:15:10: fatal error: Python.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 16 Aug 2018 06:34:07 +
with message-id 
and subject line Bug#905616: fixed in ariba 2.12.1+ds-2
has caused the Debian Bug report #905616,
regarding FTBFS: ariba/ext/minimap_ariba.cpp:15:10: fatal error: Python.h: No 
such file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
905616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ariba
Version: 2.12.1+ds-1
Severity: serious

ariba fails to build in a clean amd64 sid chroot:

---
building 'minimap_ariba' extension
creating build
creating build/temp.linux-amd64-3.7
creating build/temp.linux-amd64-3.7/ariba
creating build/temp.linux-amd64-3.7/ariba/ext
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/minimap -I/usr/include/python3.7m -c ariba/ext/minimap_ariba.cpp 
-o build/temp.linux-amd64-3.7/ariba/ext/minimap_ariba.o
ariba/ext/minimap_ariba.cpp:15:10: fatal error: Python.h: No such file or 
directory
 #include "Python.h"
  ^~
compilation terminated.
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3.7 setup.py build
dh_auto_build: pybuild --build --test-nose -i python{version} -p "3.7 3.6" 
returned exit code 13
make: *** [debian/rules:10: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


Full build log attached.

-- dam
sbuild (Debian sbuild) 0.77.0 (06 July 2018) on pc1.creditreform.bg

+==+
| ariba 2.12.1+ds-1 (amd64)Tue, 07 Aug 2018 08:12:52 + |
+==+

Package: ariba
Version: 2.12.1+ds-1
Source Version: 2.12.1+ds-1
Distribution: sid
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/sid-fa0d2234-8ccc-4429-af64-e6dcf305c240' with 
'<>'
I: NOTICE: Log filtering will replace 'build/ariba-HGdlhW/resolver-UgWMEb' with 
'<>'

+--+
| Update chroot|
+--+

Hit:1 http://pc1.modsoftsys.net/public sid InRelease
Get:2 http://proxy:/debian sid InRelease [233 kB]
Get:3 http://proxy:/debian sid/main amd64 Packages.diff/Index [27.9 kB]
Ign:3 http://proxy:/debian sid/main amd64 Packages.diff/Index
Get:3 http://proxy:/debian sid/main amd64 Packages.diff/Index [27.9 kB]
Ign:3 http://proxy:/debian sid/main amd64 Packages.diff/Index
Get:4 http://proxy:/debian sid/main amd64 Packages [8191 kB]
Fetched 8452 kB in 2s (5227 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
  bsdutils fdisk gcc-8-base gzip libblkid1 libfdisk1 libgcc1 libmount1
  libpcre3 libsmartcols1 libstdc++6 libuuid1 make mount patch util-linux
16 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 3814 kB of archives.
After this operation, 8192 B of additional disk space will be used.
Get:1 http://proxy:/debian sid/main amd64 bsdutils amd64 1:2.32-0.4 [117 kB]
Get:2 http://proxy:/debian sid/main amd64 gzip amd64 1.9-2 [119 kB]
Get:3 http://proxy:/debian sid/main amd64 libuuid1 amd64 2.32-0.4 [77.6 kB]
Get:4 http://proxy:/debian sid/main amd64 libblkid1 amd64 2.32-0.4 [190 kB]
Get:5 http://proxy:/debian sid/main amd64 libfdisk1 amd64 2.32-0.4 [229 kB]
Get:6 http://proxy:/debian sid/main amd64 libmount1 amd64 2.32-0.4 [201 kB]
Get:7 http://proxy:/debian sid/main amd64 libsmartcols1 amd64 2.32-0.4 [146 
kB]
Get:8 http://proxy:/debian sid/main amd64 fdisk amd64 2.32-0.4 [168 kB]
Get:9 http://proxy:/debian sid/main amd64 util-linux amd64 2.32-0.4 [974 kB]
Get:10 http://proxy:/debian sid/main amd64 mount amd64 2.32-0.4 [164 kB]
Get:11 http://proxy:/debian sid/main amd64 gcc-8-base amd64 8.2.0-3 [186 kB]
Get:12 http://proxy:/debian sid/main amd64 libstdc++6 amd64 

Bug#899881: marked as done (idm-console-framework: Invalid maintainer address pkg-fedora-ds-maintain...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Thu, 16 Aug 2018 06:35:07 +
with message-id 
and subject line Bug#899881: fixed in idm-console-framework 1.2.0-1
has caused the Debian Bug report #899881,
regarding idm-console-framework: Invalid maintainer address 
pkg-fedora-ds-maintain...@lists.alioth.debian.org
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
899881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:idm-console-framework
Version: 1.1.14-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of idm-console-framework,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package idm-console-framework since the list address
pkg-fedora-ds-maintain...@lists.alioth.debian.org used in the
Maintainer: field was not transferred to the alioth-lists service that
provides a continuation for the lists in the @lists.alioth.debian.org
domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-fedora-ds-maintain...@lists.alioth.debian.org is 10.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: idm-console-framework
Source-Version: 1.2.0-1

We believe that the bug you reported is fixed in the latest version of
idm-console-framework, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated idm-console-framework 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 16 Aug 2018 09:12:23 +0300
Source: idm-console-framework
Binary: libidm-console-framework-java
Architecture: source
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Description:
 libidm-console-framework-java - IDM Console Framework for the 389 Directory 
Server Console
Closes: 899881
Changes:
 idm-console-framework (1.2.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * control: Update maintainer address. (Closes: #899881)
   * control: Drop Michele from uploaders.
   * control: Update vcs urls.
   * watch: Updated.
   * control: Bump depends on libjss-java and libldap-java.
Checksums-Sha1:
 fd4705017eb4d961e59d0580328151ed37471cae 2149 idm-console-framework_1.2.0-1.dsc
 433fa1331e3f35153f952349ef536a2cdb2bc708 574852 
idm-console-framework_1.2.0.orig.tar.xz
 b4b9fe15f0cd4389893dcfa92127090e9c3d5263 2364 
idm-console-framework_1.2.0-1.debian.tar.xz
 73009de2dae50797f39d4b2267645bf762a31583 8611 
idm-console-framework_1.2.0-1_source.buildinfo
Checksums-Sha256:
 147c8bfc17aa9f927794fe71b5dd1966c4f561ee4e326f0323fd70d8db582994 2149