Bug#904715: startxfce4 fails

[Jörg Frings-Fürst]

Package: xfce4
Version: 4.12.4
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

since the last update from the xorg-server xfce4 fials to start.

Running startxfce2 I get:


(EE)
Fatal server error:
(EE) Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
(EE)
(EE)
Please consult the The X.Org Foundation support
 at http://wiki.x.org
 for help.
(EE)
Invalid MIT-MAGIC-COOKIE-1 keyxinit: giving up
xinit: unable to connect to X server: Resource temporarily unavailable
xinit: server error

CU
Jörg



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

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

Versions of packages xfce4 depends on:
ii  gtk2-engines-xfce3.2.0-3
ii  libxfce4ui-utils 4.12.1-3
ii  orage4.12.1-4
ii  thunar   1.6.15-1
ii  xfce4-appfinder  4.12.0-2
ii  xfce4-panel  4.12.2-1
ii  xfce4-pulseaudio-plugin  0.4.1-1
ii  xfce4-session4.12.1-6
ii  xfce4-settings   4.12.4-1
ii  xfconf   4.12.1-1
ii  xfdesktop4   4.12.4-1
ii  xfwm44.12.4-1

Versions of packages xfce4 recommends:
ii  desktop-base  9.0.7
ii  tango-icon-theme  0.8.90-7
ii  thunar-volman 0.8.1-2
ii  xfce4-notifyd 0.4.2-1
ii  xorg  1:7.7+19

Versions of packages xfce4 suggests:
ii  gtk3-engines-xfce3.2.0-3
ii  xfce4-goodies4.12.4
ii  xfce4-power-manager  1.6.1-1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAltas90ACgkQCfifPIyh
0l2DuA//XTpQCAVpvsNMe9rqxZ2ccgPtG5TCLs95HAjTJ5pSCmRBHTjBfJhn0/lo
itikVAre+U7ZQ1Xk2pV1RG0aNw019T3C241DO/vXJ57laKN2qr7TtZRCVaMbmpn5
rLit7LZWSgGjAVyjf1/8W8LMGrXbLys4JS5jM/6CoXkiXiDpxb50GudTxT9uQ8NC
UhWqkWw+zRhELObXKhoDRU+RWNMFGQWMyPqdEJbiiJe6KPU5O0lhY+AYfrjb8xA0
PVQrU39c3MFHxFayy9Fu3p8qHfJrL+Sv6Gl/YgcDMYpV5X/TterIVfhGMUhlfxqu
OwXv185Rgh5C5EKzgW1Ryj5y6/GdqtUZBQ5Ysx8VHY15lg4zkzAUXQEkf/7hcMZB
u84K5oUlsc2l2bCiCYY3oCeR5qaM6AlhDDDRyt7hnOOzAZjLDexnhW7m2GtX0uNs
+L8ubV0NkJ7ode7MBnvCHcl8NSgkFh/VqC+a53nTnhGRPVCdvMMFjANjLnxSuJ+4
kT20C6P1AbngNSPCNN6f6/njhdeWL2h4xk6k352wyL/RVddPQMkzkUVYrQD2EtFT
78d1KZGlb3bgm1ekdeqsG3nuyuPKTxlMMBHjI+WvwMLzn/KpEqau1xs4MmreJyvt
+x0svS9NhJa7aSU1NvS4S7KUwGgzVhcWXjd2VEDXzg/KM+qTOQw=
=sqRk
-END PGP SIGNATURE-

Bug#904712: marked as done (libmems: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Fri, 27 Jul 2018 05:51:19 +
with message-id 
and subject line Bug#904712: fixed in libmems 1.6.0+4725-6
has caused the Debian Bug report #904712,
regarding libmems: Incomplete debian/copyright?
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.)


-- 
904712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmems
Version: 1.6.0+4725-5
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Andreas Tille 

Hi,

I just ACCEPTed libmems from NEW but noticed it was missing 
attribution in debian/copyright for at least Gerton Lunter
c/o Oxford University.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: libmems
Source-Version: 1.6.0+4725-6

We believe that the bug you reported is fixed in the latest version of
libmems, 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.
Andreas Tille  (supplier of updated libmems 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: Fri, 27 Jul 2018 06:22:19 +0200
Source: libmems
Binary: libmems-dev libmems1
Architecture: source
Version: 1.6.0+4725-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libmems-dev - development library to support DNA string matching and comparativ
 libmems1   - library to support DNA string matching and comparative genomics
Closes: 904712
Changes:
 libmems (1.6.0+4725-6) unstable; urgency=medium
 .
   * Add missing copyright
 Closes: #904712
Checksums-Sha1:
 96a4b15e8f0661a97969f6507ba8c1551ea269ad 2168 libmems_1.6.0+4725-6.dsc
 8bea9436646e68712a8df10326a4f852bb3a7adf 8556 
libmems_1.6.0+4725-6.debian.tar.xz
Checksums-Sha256:
 beb0e86f1af2cf1bc8d72ea8b2c07145506f0e4a82a3019169123cc980283d2d 2168 
libmems_1.6.0+4725-6.dsc
 2c3383ae037fa9741f49233a29a36c9995883ebfc8df59a247a64a52bcf9a598 8556 
libmems_1.6.0+4725-6.debian.tar.xz
Files:
 60218d225ae71fcf3ed9704dfb082b1c 2168 science optional libmems_1.6.0+4725-6.dsc
 193cdfe3749472abbfedffc8cd35aef0 8556 science optional 
libmems_1.6.0+4725-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAltan6ERHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtH/GA/+JT1kH48SoSlcG6i0rZrmgNn9/D6d2rPe
OARmEKSHtA9E14QjhkQFhQ/MhHIk3IioZu8I47UDxsRADcNqIlxT3+b+7l9sDq58
9p95t8M2RZHzBWyComMYuM8N1LvJXIZTyMDmZmdyhn+FVgPDRMd+Rj7Nv5TSKCjy
/UcWJuB2FmOuj3T5gUxSy2WShLn4NWMbJxvRCphOaahHNDW+Qqc9vhJVZb7jlSvL
Y7aVCcCRa7c6cQMFOT/tIIo8iMQ6QcwWdY7dtuiORCqbpTzO/dTDFC5XeeT16Uex
G+epjdKXAEMrbfZl8JOlMv6ViRSHZ4PO9kvckw3bdMvLxbILccL1uWRonO2BsUel
hIE1I9UqjDXWyNdRfVFMnaj9HFSNFiBtE5vwjpHZVtp+tDa+3yvhVfUnvJ4PqNhK
9Z/NwnpDvPU/KNrxIK+ChBmw7UHSDjT0L9ogKYD6Izn23hmzvRCvqfmKGWcDWW68
FQdAHhbzyN26MRDgH8SvKnk7mCGChUamp/wg3h8jreCf5fGphEHKteUZHX/pkADM
qf52z2y1l/YMOdNoJQjz7OoytsAaMIRKn5TjOVQ95tENB5tPSJrGMNdHXC9ijUo/
/811AutChnqnahaEe6K6ajhou/tn9+D1olLP54f5pAXwQxZXHo2fx5m7lcvzBugT
WwzIxPS8fKA=
=fVOp
-END PGP SIGNATURE End Message ---

Bug#904714: wreport ftbfs on arm64 and armel at least

[Matthias Klose]

Package: src:wreport
Version: 3.13-1
Severity: serious
Tags: sid buster

Making all in doc
make[3]: Entering directory '/<>/doc'
No doxygen warnings about undocumented functions. Use ./configure
--enable-doxy-undoc-warnings to turn them on
doxygen libwreport.dox
No doxygen warnings about undocumented functions. Use ./configure
--enable-doxy-undoc-warnings to turn them on
doxygen libwreport.dox
warning: Tag `SYMBOL_CACHE_SIZE' at line 290 of file `libwreport.dox' has become
obsolete.
 To avoid this warning please remove this line from your configuration
file or upgrade it using "doxygen -u"
warning: Tag `SYMBOL_CACHE_SIZE' at line 290 of file `libwreport.dox' has become
obsolete.
 To avoid this warning please remove this line from your configuration
file or upgrade it using "doxygen -u"
warning: Tag `SHOW_DIRECTORIES' at line 490 of file `libwreport.dox' has become
obsolete.
 To avoid this warning please remove this line from your configuration
file or upgrade it using "doxygen -u"
warning: Tag `SHOW_DIRECTORIES' at line 490 of file `libwreport.dox' has become
obsolete.
 To avoid this warning please remove this line from your configuration
file or upgrade it using "doxygen -u"
warning: Tag `HTML_ALIGN_MEMBERS' at line 848 of file `libwreport.dox' has
become obsolete.
 To avoid this warning please remove this line from your configuration
file or upgrade it using "doxygen -u"
warning: Tag `HTML_ALIGN_MEMBERS' at line 848 of file `libwreport.dox' has
become obsolete.
 To avoid this warning please remove this line from your configuration
file or upgrade it using "doxygen -u"
warning: Tag `USE_INLINE_TREES' at line 1033 of file `libwreport.dox' has become
obsolete.
 To avoid this warning please remove this line from your configuration
file or upgrade it using "doxygen -u"
warning: Tag `USE_INLINE_TREES' at line 1033 of file `libwreport.dox' has become
obsolete.
 To avoid this warning please remove this line from your configuration
file or upgrade it using "doxygen -u"
warning: Tag `XML_SCHEMA' at line 1258 of file `libwreport.dox' has become 
obsolete.
 To avoid this warning please remove this line from your configuration
file or upgrade it using "doxygen -u"
warning: Tag `XML_DTD' at line 1264 of file `libwreport.dox' has become 
obsolete.
 To avoid this warning please remove this line from your configuration
file or upgrade it using "doxygen -u"
warning: Tag `XML_SCHEMA' at line 1258 of file `libwreport.dox' has become 
obsolete.
 To avoid this warning please remove this line from your configuration
file or upgrade it using "doxygen -u"
warning: Tag `XML_DTD' at line 1264 of file `libwreport.dox' has become 
obsolete.
 To avoid this warning please remove this line from your configuration
file or upgrade it using "doxygen -u"
warning: doxygen no longer ships with the FreeSans font.
You may want to clear or change DOT_FONTNAME.
Otherwise you run the risk that the wrong font is being used for dot generated
graphs.
warning: doxygen no longer ships with the FreeSans font.
You may want to clear or change DOT_FONTNAME.
Otherwise you run the risk that the wrong font is being used for dot generated
graphs.
error: Could not create output directory /<>/doc/apidocs
make[3]: *** [Makefile:543: apidocs/index.html] Error 1
make[3]: *** Waiting for unfinished jobs
/<>/wreport/style.dox:39: warning: Reached end of file while still
inside a (nested) comment. Nesting level 2 (probable line reference: 3, 1)
/<>/wreport/bulletin.h:343: warning: argument 'buf' of command
@param is not found in the argument list of wreport::BufrBulletin::decode(const
std::string , const char *fname="(memory)", size_t offset=0)
/<>/wreport/bulletin.h:355: warning: The following parameters of
wreport::BufrBulletin::decode(const std::string , const char
*fname="(memory)", size_t offset=0) are not documented:
  parameter 'raw'
/<>/wreport/bulletin.h:373: warning: argument 'buf' of command
@param is not found in the argument list of wreport::BufrBulletin::decode(const
std::string , const BufrCodecOptions , const char *fname="(memory)",
size_t offset=0)
/<>/wreport/bulletin.h:387: warning: The following parameters of
wreport::BufrBulletin::decode(const std::string , const BufrCodecOptions
, const char *fname="(memory)", size_t offset=0) are not documented:
  parameter 'raw'
/<>/wreport/bulletin.h:313: warning: argument 'buf' of command
@param is not found in the argument list of
wreport::BufrBulletin::decode_header(const std::string , const char
*fname="(memory)", size_t offset=0)
/<>/wreport/bulletin.h:325: warning: The following parameters of
wreport::BufrBulletin::decode_header(const std::string , const char
*fname="(memory)", size_t offset=0) are not documented:
  parameter 'raw'
/<>/wreport/bulletin.h:327: warning: argument 'buf' of command
@param is not found in the argument list of
wreport::BufrBulletin::decode_header(const std::string , const

Bug#903525:

[Michael Hudson-Doyle]

fwiw i think the 9.0.0 release fixes this. Although it still has a stub
async.py file and I can't remember how to not bytecompile that with python
3.7 -- I know it's possible though...

Bug#894978: lightning: Unable to create event with experimental version (working before migration to 58)

[Carsten Schoenert]

Hello Eric,

On Thu, Apr 05, 2018 at 09:35:01PM +0200, Eric Valette wrote:
> Wanted to send an event as a reminder and was uable to vreate the
> event either by clicking, or keyboard.

how this looks like in recent version in experimental?
Still not working?

Regards
Carsten

Bug#869639: marked as done (firmware-brcm80211: BroadPwn vulnerability CVE-2017-9417)

[Debian Bug Tracking System]

Your message dated Fri, 27 Jul 2018 04:00:12 +
with message-id 
and subject line Bug#869639: fixed in firmware-nonfree 20180518-1
has caused the Debian Bug report #869639,
regarding firmware-brcm80211: BroadPwn vulnerability CVE-2017-9417
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.)


-- 
869639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-brcm80211
Version: 0.43
Severity: critical
Tags: security upstream
Justification: root security hole

Dear Maintainer,

CVE-2017-8386 "BroadPwn" has been around for a while.

It seems Debian ships the relevant firmware in this package.

Could I impose on you to ensure that all is as it should be?

Many thanks.
Mark

https://nvd.nist.gov/vuln/detail/CVE-2017-8386
https://security-tracker.debian.org/tracker/CVE-2017-9417
https://packages.debian.org/search?keywords=firmware-brcm80211
http://boosterok.com/blog/broadpwn/

-- System Information:
Debian Release: 8.9
  APT prefers testing
  APT policy: (1000, 'testing'), (1000, 'stable'), (1000, 'oldstable'), (500, 
'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: firmware-nonfree
Source-Version: 20180518-1

We believe that the bug you reported is fixed in the latest version of
firmware-nonfree, 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 869...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated firmware-nonfree 
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, 27 Jul 2018 00:56:57 +0800
Source: firmware-nonfree
Binary: firmware-linux firmware-linux-nonfree firmware-amd-graphics 
firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211 
firmware-cavium firmware-intelwimax firmware-intel-sound firmware-ipw2x00 
firmware-ivtv firmware-iwlwifi firmware-libertas firmware-misc-nonfree 
firmware-myricom firmware-netronome firmware-netxen firmware-qcom-media 
firmware-qlogic firmware-realtek firmware-samsung firmware-siano 
firmware-ti-connectivity
Architecture: all source
Version: 20180518-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 869639 885016 891042 891364 892408 893952 898267 899101 900036 900266 
900871
Description: 
 firmware-amd-graphics - Binary firmware for AMD/ATI graphics chips
 firmware-atheros - Binary firmware for Atheros wireless cards
 firmware-bnx2 - Binary firmware for Broadcom NetXtremeII
 firmware-bnx2x - Binary firmware for Broadcom NetXtreme II 10Gb
 firmware-brcm80211 - Binary firmware for Broadcom/Cypress 802.11 wireless cards
 firmware-cavium - Binary firmware for Cavium Ethernet adapters
 firmware-intel-sound - Binary firmware for Intel sound DSPs
 firmware-intelwimax - Binary firmware for Intel WiMAX Connection
 firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 and 2915
 firmware-ivtv - Binary firmware for iTVC15-family MPEG codecs (ivtv and 
pvrusb2 d
 firmware-iwlwifi - Binary firmware for Intel Wireless cards
 firmware-libertas - Binary firmware for Marvell wireless cards
 firmware-linux - Binary firmware for various drivers in the Linux kernel 
(meta-pac
 firmware-linux-nonfree - Binary firmware for various drivers in the Linux 
kernel (meta-pac
 firmware-misc-nonfree - Binary firmware for various drivers in the Linux kernel
 firmware-myricom - Binary firmware for Myri-10G Ethernet adapters
 firmware-netronome - Binary firmware for Netronome network adapters
 firmware-netxen - Binary firmware for QLogic Intelligent Ethernet (3000 and 
3100 Se
 firmware-qcom-media - Binary firmware for Qualcomm graphics/video
 firmware-qlogic - Binary firmware for QLogic HBAs
 firmware-realtek - Binary firmware for Realtek wired/wifi/BT adapters
 firmware-samsung - Binary firmware for Samsung MFC video codecs
 

Bug#904712: libmems: Incomplete debian/copyright?

[Chris Lamb]

Source: libmems
Version: 1.6.0+4725-5
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Andreas Tille 

Hi,

I just ACCEPTed libmems from NEW but noticed it was missing 
attribution in debian/copyright for at least Gerton Lunter
c/o Oxford University.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

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

Bug#896736: marked as done (python-ratelimiter: missing build dependency on dh-python)

[Debian Bug Tracking System]

Your message dated Fri, 27 Jul 2018 03:04:26 +
with message-id 
and subject line Bug#896736: fixed in python-ratelimiter 1.2.0.post0-1
has caused the Debian Bug report #896736,
regarding python-ratelimiter: missing build dependency on dh-python
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.)


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

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

...
 fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 10) line 
1.
BEGIN failed--compilation aborted at (eval 10) line 1.

make: *** [debian/rules:7: clean] Error 2
--- End Message ---
--- Begin Message ---
Source: python-ratelimiter
Source-Version: 1.2.0.post0-1

We believe that the bug you reported is fixed in the latest version of
python-ratelimiter, 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 896...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dylan Aïssi  (supplier of updated python-ratelimiter 
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: Fri, 27 Jul 2018 04:27:28 +0200
Source: python-ratelimiter
Binary: python3-ratelimiter
Architecture: source
Version: 1.2.0.post0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Dylan Aïssi 
Description:
 python3-ratelimiter - simple Python library for limiting the rate of operations
Closes: 896736
Changes:
 python-ratelimiter (1.2.0.post0-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Christian M. Amsüss ]
   * New upstream release.
   * Run tests at build time.
   * Fix Vcs-* URIs.
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Dylan Aïssi ]
   * Add "export LC_ALL=C.UTF-8" in d/rules to fix a build error.
   * Add dh-python to Build-Depends (Closes: #896736).
   * Add python3-pytest to Build-Depends to fix test.
   * Add "Testsuite: autopkgtest-pkg-python" in d/control.
   * Bump Standards-Version: 4.1.5 (no changes needed).
Checksums-Sha1:
 cb064368d0783751012bb5472c94c0c934cb7f0a 2194 
python-ratelimiter_1.2.0.post0-1.dsc
 e30f5643eb02539b47372e1648a902db765fabc5 9182 
python-ratelimiter_1.2.0.post0.orig.tar.gz
 e6b9c1456b1fd9182b1803fb24939879b44f750a 2192 
python-ratelimiter_1.2.0.post0-1.debian.tar.xz
Checksums-Sha256:
 317f9c8529f37dcf4d30756541e5b8d6d0a8b407e60de9c98f04b6b543ddd803 2194 
python-ratelimiter_1.2.0.post0-1.dsc
 5c395dcabdbbde2e5178ef3f89b568a3066454a6ddc223b76473dac22f89b4f7 9182 
python-ratelimiter_1.2.0.post0.orig.tar.gz
 540c461da574d23da6b1dff7a00c08240b9a3f5b2688b76debe7f99bade956e4 2192 
python-ratelimiter_1.2.0.post0-1.debian.tar.xz
Files:
 ef075484d955d541d5a846f8463487bc 2194 python optional 
python-ratelimiter_1.2.0.post0-1.dsc
 5e677cb4049c85d880b6705b84603820 9182 python optional 
python-ratelimiter_1.2.0.post0.orig.tar.gz
 ea4e2e505caa78e737993fa528342c0d 2192 python optional 
python-ratelimiter_1.2.0.post0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAltahCEOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtHKpw//fzX4L6fTqKfWDIVd35IBRKaxs6hSNbOS2hcy
0/EzqMrmoWosonWuxwBjFpAhn7so+aJkXJS1BWZeoMpaEOTqaxf7jIcofZT+NRWQ
7u1l//c+CnqGqx9JxngaBoWqm7kPKXj/3YO1Ryw5UhxPNngTSxP2REoo7cGB21Rl
9O4jp84R2UbMWXmUSYgYxhpdH+hPILXEqwyIBik7w6knyHHFbqe5i3BxxySxxOWo
4LonvBjHIWepY5ECkJpPn9mobX9jiNO9aV1vlCikOdhOnZbc/Fy29VqbvJ5CfDNv
tLp0Fx1IYgXqyT5/RzKksu8vzWpcustMPl5a8N6k65RCj2w2H6KCKio1MoyL6kwX
LD0jr8lI8t1jAvcyFly1pSVaJoZAszeuOXdbI0vOD0Nkw+8KILyCO/rkEmPEAPMY

Processed: Re: zcat -t sometimes crashes with heap corruption

[Debian Bug Tracking System]

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

> reopen 903931
Bug #903931 {Done: Daniel Baumann } [zutils] 
zcat -t sometimes crashes with heap corruption
'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 zutils/1.7-2.
> severity 903931 wishlist
Bug #903931 [zutils] zcat -t sometimes crashes with heap corruption
Severity set to 'wishlist' from 'serious'
> reassign 903931 initramfs-tools
Bug #903931 [zutils] zcat -t sometimes crashes with heap corruption
Bug reassigned from package 'zutils' to 'initramfs-tools'.
Ignoring request to alter found versions of bug #903931 to the same values 
previously set
Ignoring request to alter fixed versions of bug #903931 to the same values 
previously set
> retitle 903931 please use gzip instead of zcat in unmkinitramfs
Bug #903931 [initramfs-tools] zcat -t sometimes crashes with heap corruption
Changed Bug title to 'please use gzip instead of zcat in unmkinitramfs' from 
'zcat -t sometimes crashes with heap corruption'.
> thanks
Stopping processing here.

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

Bug#903931: zcat -t sometimes crashes with heap corruption

[Daniel Baumann]

reopen 903931
severity 903931 wishlist
reassign 903931 initramfs-tools
retitle 903931 please use gzip instead of zcat in unmkinitramfs
thanks

Hi,

asking upstream about it, he sais:

"It seems that there are two ways of implementing *zcat programs out
there. The zcat from zutils is a complete implementation of a cat
program like the one from GNU coreutils[2] but with transparent
decompression. I have invested a lot of work to make it work well.

[2]
http://www.gnu.org/software/coreutils/manual/html_node/cat-invocation.html#cat-invocation

The rest of the *zcat programs out there seem to be just wrapper
scripts. The zcat from gzip boils down to 'exec gzip -cd "$@"'.

The problem, IMO, is in the xcpio() function of unmkinitramfs. It should
use 'gzip -t' instead of 'zcat -t', just as it already uses 'bzip2 -t'
and 'lzop -t'. Think that posix zcat does not document a -t option[3]
and therefore 'zcat -t' is not a portable way to check file integrity."

http://lists.nongnu.org/archive/html/zutils-bug/2018-07/msg1.html

Therefore, reassigning this back to initramfs-tools with the suggestion,
that you use gzip -t instead of zcat -t.

Regards,
Daniel

Bug#896736: Bug #896736 in python-ratelimiter marked as pending

[Dylan Aïssi]

Control: tag -1 pending

Hello,

Bug #896736 in python-ratelimiter 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/modules/python-ratelimiter/commit/a28806c8740b1b46c42ede81122218747611cb58


Add dh-python to Build-Depends (Closes: #896736)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/896736

Processed: Bug #896736 in python-ratelimiter marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #896736 [src:python-ratelimiter] python-ratelimiter: missing build 
dependency on dh-python
Added tag(s) pending.

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

Bug#904671: fwupd: Incomplete debian/copyright?

[Chris Lamb]

Hi Mario,

> https://github.com/hughsie/fwupd/pull/611

Hm. The generated file linked (ie. with many many `Files` entries…)
seems unnecesarily wasteful given that we have wildcard support in
DEP-5.

In fact, this kind of file would be even worse than the current
situation, so I would probabably NACK this change, sorry.


Best wishes,

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

Bug#902760: [Bug #902760] Testsuite fails with ARPACK 3.6 (#1107)

[Andreas Tille]

Hi,

just forwarding the suspicion of igraph upstream that the problem is
caused by arpack.  I'm tempted to reassign bug #902760 but I'd like
to hear your opinion first.

Kind regards

 Andreas.

- Forwarded message from Tamás Nepusz  -

Date: Thu, 26 Jul 2018 11:19:03 -0700
From: Tamás Nepusz 
To: igraph/igraph 
Cc: Andreas Tille , Author 
Subject: Re: [igraph/igraph] Testsuite fails with ARPACK 3.6 (#1107)

Okay, I am pretty certain that this is an inherent issue with ARPACK 3.6; the 
same problem can also be triggered in GNU Octave (4.4.0) when linked with 
ARPACK 3.6 (I tried it on a Mac with Homebrew). The code below produces the 
PageRank matrix of the graph from the igraph test case:

```
octave:1> m = ones(11, 11) * 0.15 / 11;
octave:2> m(1, 2:11) += 0.85;
octave:3> m(2:11, 1) = (1 - m(1, 1)) / 10;
```

and it blows up exactly the same way:

```
octave:4> [v, lambda] = eigs(m, 1)
error: __eigs__: eigs: error - in dnaupd
error: called from
eigs at line 285 column 18
```

I'll file a bug report to `arpack-ng`.

-- 
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/igraph/igraph/issues/1107#issuecomment-408188667

- End forwarded message -

-- 
http://fam-tille.de

Bug#903923:

[Michael Hudson-Doyle]

The fix is just to build-depend on python3-all-dev rather than python3-dev.

Bug#904507: marked as done (libharfbuzz-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libharfbuzz-subset.so -> libharfbuzz-subset.so.0.10800.4)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jul 2018 23:19:08 +
with message-id 
and subject line Bug#904507: fixed in harfbuzz 1.8.4-2
has caused the Debian Bug report #904507,
regarding libharfbuzz-dev: broken symlink: 
/usr/lib/x86_64-linux-gnu/libharfbuzz-subset.so -> 
libharfbuzz-subset.so.0.10800.4
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.)


-- 
904507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libharfbuzz-dev
Version: 1.8.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink:

  /usr/lib/x86_64-linux-gnu/libharfbuzz-subset.so -> 
libharfbuzz-subset.so.0.10800.4

I could not find libharfbuzz-subset.so.* in the archive at all,
there is only a static library.


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: harfbuzz
Source-Version: 1.8.4-2

We believe that the bug you reported is fixed in the latest version of
harfbuzz, 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.
أحمد المحمودي (Ahmed El-Mahmoudy)  (supplier 
of updated harfbuzz 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, 27 Jul 2018 00:55:38 +0200
Source: harfbuzz
Binary: libharfbuzz0b libharfbuzz-gobject0 gir1.2-harfbuzz-0.0 libharfbuzz-icu0 
libharfbuzz-dev libharfbuzz-bin libharfbuzz-doc libharfbuzz0-udeb
Architecture: source
Version: 1.8.4-2
Distribution: unstable
Urgency: medium
Maintainer: أحمد المحمودي (Ahmed El-Mahmoudy) 

Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) 

Description:
 gir1.2-harfbuzz-0.0 - OpenType text shaping engine (GObject introspection data)
 libharfbuzz-bin - OpenType text shaping engine (utility)
 libharfbuzz-dev - Development files for OpenType text shaping engine
 libharfbuzz-doc - Documentation files for the HarfBuzz library
 libharfbuzz-gobject0 - OpenType text shaping engine ICU backend (GObject 
library)
 libharfbuzz-icu0 - OpenType text shaping engine ICU backend
 libharfbuzz0-udeb - OpenType text shaping engine (udeb)
 libharfbuzz0b - OpenType text shaping engine (shared library)
Closes: 896075 904507
Changes:
 harfbuzz (1.8.4-2) unstable; urgency=medium
 .
   * Do not install any file related to hb-subset (Closes: #904507, #896075)
Checksums-Sha1:
 ce118ad0395a752a8b83044c429d4f97f93be7b9 2295 harfbuzz_1.8.4-2.dsc
 448943c032b9c51959c176db9c12e2b67619e174 8828 harfbuzz_1.8.4-2.debian.tar.xz
 0f594799be098c8e7f321540b70bf0be1ef78ca2 7874 harfbuzz_1.8.4-2_source.buildinfo
Checksums-Sha256:
 120485c45b234e8cd43d98baf2944ed6b8d86debcb4a80fd7d1b4c8a9bbc4c8d 2295 
harfbuzz_1.8.4-2.dsc
 dd5751d8b8cb419b74168aec30925daf1c8168ba9bd47989a9449b95a8089e94 8828 
harfbuzz_1.8.4-2.debian.tar.xz
 fd30e938e0f69e279dc5655fff581179bb8bbc062c01742b7e48511e2f9c9142 7874 
harfbuzz_1.8.4-2_source.buildinfo
Files:
 6ef644fd23e3bb18736c1543693a 2295 libs optional harfbuzz_1.8.4-2.dsc
 08cc81cd6060eee2e0f627e5d2e35dc0 8828 libs optional 
harfbuzz_1.8.4-2.debian.tar.xz
 81d92f42c647fc90ad22605b1efc9f34 7874 libs optional 
harfbuzz_1.8.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEcBAEBCgAGBQJbWlHRAAoJELwZapTt3aG3XVQH/RKorV1AWJ1naxRm/VtCVV4q
ibDg831b9zDi1U46pF3lCuje/KS++7lXmIb2v9ATpQape0OaZs8fDaYUSiomYbAh
YSaVsUGxHk05Oa8rtvMTNJVEp60CBB0cGAgm7OuHXwVmJmyOcSpK5EuE1OU+8Ekj
2WCgnBYFZYBpz6WodRz652BU4YbRcN8sQBDUNKw43aZxBA4AsHQojuX51Qfxjhoi
saiv4RL+i+EsBmLsTj8b5TMuVHeJdylv+AF0M6uO0oXz/ePQhpYZGNXLX0aZwmYW
9Z7cDGT5BuVUpYJcEs8UlMFV40LdtbR674K8k87Hc8Ia/w90quR8fvZ5dvUDaCU=
=nI4h
-END PGP SIGNATURE End Message ---

Bug#904511: marked as done (libodb-api-bin: broken symlinks: /usr/bin/odb* -> .odb_deprecated.sh)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jul 2018 21:25:26 +
with message-id 
and subject line Bug#904511: fixed in odb-api 0.18.0-5
has caused the Debian Bug report #904511,
regarding libodb-api-bin: broken symlinks: /usr/bin/odb* -> .odb_deprecated.sh
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.)


-- 
904511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libodb-api-bin
Version: 0.18.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m48.9s ERROR: FAIL: Broken symlinks:
  /usr/bin/odbset -> .odb_deprecated.sh
  /usr/bin/odbheader -> .odb_deprecated.sh
  /usr/bin/odbdump -> .odb_deprecated.sh
  /usr/bin/odbcount -> .odb_deprecated.sh
  /usr/bin/odb_to_request -> .odb_deprecated.sh
  /usr/bin/odb_split -> .odb_deprecated.sh
  /usr/bin/odb_set -> .odb_deprecated.sh
  /usr/bin/odb_prune -> .odb_deprecated.sh
  /usr/bin/odb_more -> .odb_deprecated.sh
  /usr/bin/odb_merge -> .odb_deprecated.sh
  /usr/bin/odb_less -> .odb_deprecated.sh
  /usr/bin/odb_header -> .odb_deprecated.sh
  /usr/bin/odb_gnuplot -> .odb_deprecated.sh
  /usr/bin/odb_dup -> .odb_deprecated.sh
  /usr/bin/odb_dump -> .odb_deprecated.sh
  /usr/bin/odb_diff -> .odb_deprecated.sh
  /usr/bin/odb_count -> .odb_deprecated.sh
  /usr/bin/odb_compress -> .odb_deprecated.sh
  /usr/bin/odb_cat -> .odb_deprecated.sh
  /usr/bin/odb_4to1 -> .odb_deprecated.sh
  /usr/bin/odb_1to4 -> .odb_deprecated.sh


Severity serious for putting broken stuff in /usr/bin


cheers,

Andreas


libodb-api-bin_0.18.0-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: odb-api
Source-Version: 0.18.0-5

We believe that the bug you reported is fixed in the latest version of
odb-api, 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.
Alastair McKinstry  (supplier of updated odb-api 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, 26 Jul 2018 12:14:04 +0100
Source: odb-api
Binary: libodb-api-0d libodb-api-bin libodb-api-data libodb-api-dev 
python3-odb-api
Architecture: source amd64 all
Version: 0.18.0-5
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libodb-api-0d - Observational Data processing API for meteorology
 libodb-api-bin - Tools for the Observational Data Processing (ODB) API
 libodb-api-data - Data used by ECMWF Observational Data Processing (ODB)
 libodb-api-dev - Observational Data processing API for meteorology
 python3-odb-api - Python Observational Data processing API for meteorology
Closes: 904511
Changes:
 odb-api (0.18.0-5) unstable; urgency=medium
 .
   * Fix broken symlinks in /usr/bin. Closes: #904511
   * Update URLs in d/watch
Checksums-Sha1:
 e60da56f2b12cb8010c6c8b7fa88811cd234b310 2517 odb-api_0.18.0-5.dsc
 a8fc6d845fe554534f8d217a1b167c8b558a6a33 18832 odb-api_0.18.0-5.debian.tar.xz
 46838dcabf614ea7b5954aac93d512c418efd5d5 55505848 
libodb-api-0d-dbgsym_0.18.0-5_amd64.deb
 3e9db15707163b4c6316f2084fee1cfbe1b93e00 17763968 
libodb-api-0d_0.18.0-5_amd64.deb
 33bc349c907ad308c22acad67409d275507572f5 1202800 
libodb-api-bin-dbgsym_0.18.0-5_amd64.deb
 05144b61228083e6553c7aaa407fa80ab4e10922 210596 
libodb-api-bin_0.18.0-5_amd64.deb
 b22508916fac524d9916e6cb26b71a0f7d1e7ee8 55104 libodb-api-data_0.18.0-5_all.deb
 d616e99e210bc3340fc0556137f5a1f407a809d5 480336 
libodb-api-dev_0.18.0-5_amd64.deb
 40e5a8a6e810c90e985d3e44c629f63051f2604f 12686 odb-api_0.18.0-5_amd64.buildinfo
 60ab82a95e5306862c96f5443bcf6b816d07f17f 1108792 
python3-odb-api-dbgsym_0.18.0-5_amd64.deb
 c38bc6ff1e42dab491e84256a77e72a2e7c09167 168912 
python3-odb-api_0.18.0-5_amd64.deb
Checksums-Sha256:
 cdb4567e1786a0afe71ba44527f72e4d5a15a32c97183239bcaa512015c34041 2517 
odb-api_0.18.0-5.dsc
 c3510a93c0467395bb060bc4770d39ccd11b7f78f219157adf0231d31b748b6a 18832 
odb-api_0.18.0-5.debian.tar.xz
 

Bug#904255: marked as done (network-manager-vpnc: CVE-2018-10900: privilege escalation)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jul 2018 21:17:09 +
with message-id 
and subject line Bug#904255: fixed in network-manager-vpnc 1.2.4-4+deb9u1
has caused the Debian Bug report #904255,
regarding network-manager-vpnc: CVE-2018-10900: privilege escalation
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.)


-- 
904255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: network-manager-vpnc
Version: 1.2.4-1
Severity: grave
Tags: patch security upstream

Hi,

The following vulnerability was published for network-manager-vpnc.

CVE-2018-10900[0]:
local privilege escalation

A user with enough privileges to create the vpnc connection entry
(group netdev for instance), can use the flaw in network-manager-vpnc
to escalate privileges.

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-10900
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10900
[1] https://pulsesecurity.co.nz/advisories/NM-VPNC-Privesc

Update for stretch is already in preparation.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: network-manager-vpnc
Source-Version: 1.2.4-4+deb9u1

We believe that the bug you reported is fixed in the latest version of
network-manager-vpnc, 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.
Salvatore Bonaccorso  (supplier of updated 
network-manager-vpnc 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: Sun, 22 Jul 2018 14:23:44 +0200
Source: network-manager-vpnc
Binary: network-manager-vpnc network-manager-vpnc-gnome
Architecture: source
Version: 1.2.4-4+deb9u1
Distribution: stretch-security
Urgency: high
Maintainer: Utopia Maintenance Team 

Changed-By: Salvatore Bonaccorso 
Closes: 904255
Description: 
 network-manager-vpnc - network management framework (VPNC plugin core)
 network-manager-vpnc-gnome - network management framework (VPNC plugin GNOME 
GUI)
Changes:
 network-manager-vpnc (1.2.4-4+deb9u1) stretch-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * service: disallow newlinies in configuration values (CVE-2018-10900)
 (Closes: #904255)
Checksums-Sha1: 
 30529f0f4f6c34da0fd90eb12d48122f279c5547 2620 
network-manager-vpnc_1.2.4-4+deb9u1.dsc
 fca590f78467ce120afb02536d944ecde6a62d2e 402428 
network-manager-vpnc_1.2.4.orig.tar.xz
 841670ce8489d7633a4e1d614f8d9576a2947422 6860 
network-manager-vpnc_1.2.4-4+deb9u1.debian.tar.xz
Checksums-Sha256: 
 3d29ca9a4fd23e095e1a32072bd5727bfec421c92e92e426be0912c169555cbb 2620 
network-manager-vpnc_1.2.4-4+deb9u1.dsc
 39c7516418e90208cb534c19628ce40fd50eba0a08b2ebaef8da85720b10fb05 402428 
network-manager-vpnc_1.2.4.orig.tar.xz
 5997fe35142380ce76f38a7ec33c850d0173f82444d8252157093e801249d57b 6860 
network-manager-vpnc_1.2.4-4+deb9u1.debian.tar.xz
Files: 
 c03f7a2b800f42b1c0245d1524361f3c 2620 net optional 
network-manager-vpnc_1.2.4-4+deb9u1.dsc
 b482a231f25d3857fd320d7c0b25c785 402428 net optional 
network-manager-vpnc_1.2.4.orig.tar.xz
 f70c6ecb92cb950c65f3cdb4b79601cd 6860 net optional 
network-manager-vpnc_1.2.4-4+deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAltUelNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EYSkP/3v/dCBfdTev2sVmGo8HY0geOJ5L0MbE
aKxxgIR7o+VwjmfQaVYilTJcbhNvdIh4MSBjgbRc7FNLntLEhov0O0k1+p/V4j4s
TV9y5i/jjKloQtC5mSnifD+xIc6ZGDptWFNzVmg54M7Jf8nmITwg8YVl/CxxMdvL
9ytg5vvmgRSfCVbo1DNkEW+bUDu2Moz0ljQmgCVhbPnTGtmNsTxdlNiLxcaXWd3O
zXhn/FpMj7K/Kw5uYcd96sr/NGvJKHu1NhcOyo7iUI4DtWZCweXGUce5tMZyU359
j9eImJelNUqjAQrnTBZXZDH1wrYNQ34VmP1xJIogCWIdKl3RoClXCnpqVeXdSayI
w2HSP9fv2KMSauqmDzUvFrPbNNiSrkdZgJaKBqTt6JO2ndpVL24W+3KwUM1AoboS
0gxB25m9O5j37EdDQmx+1rzsQUKsOwKAThAdnTlD3Nu5e12WhW0Pkx0EzYlTTUNZ

Bug#903776: marked as done (Kernel 4.9.110-1 sit: non-ECT warnings)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jul 2018 21:17:08 +
with message-id 
and subject line Bug#903776: fixed in linux 4.9.110-3
has caused the Debian Bug report #903776,
regarding Kernel 4.9.110-1 sit: non-ECT warnings
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.)


-- 
903776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-4.9.0-7-amd64
Version: 4.9.110-1

Hi,

after upgrading today I started seeing these:

Jul 14 12:46:18 edi kernel: [   29.601249] sit: IPv6, IPv4 and MPLS over IPv4 
tunneling driver
Jul 14 12:46:24 edi kernel: [   35.920488] sit: non-ECT from 238.163.0.0 with 
TOS=0x2
Jul 14 12:46:24 edi kernel: [   35.956189] sit: non-ECT from 238.163.0.0 with 
TOS=0x2
Jul 14 12:46:24 edi kernel: [   35.980514] sit: non-ECT from 238.163.0.0 with 
TOS=0x2
Jul 14 12:46:25 edi kernel: [   36.207554] sit: non-ECT from 0.12.0.0 with 
TOS=0xb
Jul 14 12:46:25 edi kernel: [   36.230568] sit: non-ECT from 0.12.0.0 with 
TOS=0x6
Jul 14 12:46:25 edi kernel: [   36.413928] sit: non-ECT from 0.12.0.0 with 
TOS=0x6
Jul 14 12:46:25 edi kernel: [   36.437173] sit: non-ECT from 0.12.0.0 with 
TOS=0x6#

Regards
Thomas


signature.asc
Description: Message signed with OpenPGP
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.9.110-3

We believe that the bug you reported is fixed in the latest version of
linux, 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 903...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux 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: Mon, 23 Jul 2018 17:47:13 +0100
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-7 linux-doc-4.9 linux-manual-4.9 
linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9 
libusbip-dev usbip hyperv-daemons linux-headers-4.9.0-7-common 
linux-headers-4.9.0-7-common-rt linux-libc-dev linux-headers-4.9.0-7-all 
linux-headers-4.9.0-7-all-alpha kernel-image-4.9.0-7-alpha-generic-di 
nic-modules-4.9.0-7-alpha-generic-di 
nic-wireless-modules-4.9.0-7-alpha-generic-di 
nic-shared-modules-4.9.0-7-alpha-generic-di 
serial-modules-4.9.0-7-alpha-generic-di 
usb-serial-modules-4.9.0-7-alpha-generic-di 
ppp-modules-4.9.0-7-alpha-generic-di pata-modules-4.9.0-7-alpha-generic-di 
cdrom-core-modules-4.9.0-7-alpha-generic-di 
scsi-core-modules-4.9.0-7-alpha-generic-di 
scsi-modules-4.9.0-7-alpha-generic-di loop-modules-4.9.0-7-alpha-generic-di 
btrfs-modules-4.9.0-7-alpha-generic-di ext4-modules-4.9.0-7-alpha-generic-di 
isofs-modules-4.9.0-7-alpha-generic-di jfs-modules-4.9.0-7-alpha-generic-di
 xfs-modules-4.9.0-7-alpha-generic-di fat-modules-4.9.0-7-alpha-generic-di 
md-modules-4.9.0-7-alpha-generic-di multipath-modules-4.9.0-7-alpha-generic-di 
usb-modules-4.9.0-7-alpha-generic-di 
usb-storage-modules-4.9.0-7-alpha-generic-di 
fb-modules-4.9.0-7-alpha-generic-di input-modules-4.9.0-7-alpha-generic-di 
event-modules-4.9.0-7-alpha-generic-di mouse-modules-4.9.0-7-alpha-generic-di 
nic-pcmcia-modules-4.9.0-7-alpha-generic-di 
pcmcia-modules-4.9.0-7-alpha-generic-di 
nic-usb-modules-4.9.0-7-alpha-generic-di sata-modules-4.9.0-7-alpha-generic-di 
crc-modules-4.9.0-7-alpha-generic-di crypto-modules-4.9.0-7-alpha-generic-di 
crypto-dm-modules-4.9.0-7-alpha-generic-di ata-modules-4.9.0-7-alpha-generic-di 
nbd-modules-4.9.0-7-alpha-generic-di squashfs-modules-4.9.0-7-alpha-generic-di 
virtio-modules-4.9.0-7-alpha-generic-di zlib-modules-4.9.0-7-alpha-generic-di 
fuse-modules-4.9.0-7-alpha-generic-di srm-modules-4.9.0-7-alpha-generic-di 
linux-image-4.9.0-7-alpha-generic
 linux-headers-4.9.0-7-alpha-generic linux-image-4.9.0-7-alpha-generic-dbg 
linux-image-4.9.0-7-alpha-smp linux-headers-4.9.0-7-alpha-smp 
linux-image-4.9.0-7-alpha-smp-dbg linux-headers-4.9.0-7-all-amd64 
kernel-image-4.9.0-7-amd64-di nic-modules-4.9.0-7-amd64-di 
nic-wireless-modules-4.9.0-7-amd64-di nic-shared-modules-4.9.0-7-amd64-di 
serial-modules-4.9.0-7-amd64-di usb-serial-modules-4.9.0-7-amd64-di 
ppp-modules-4.9.0-7-amd64-di 

Bug#904692: seahorse: Segfault few seconds after start

[Tobias Bengfort]

Package: seahorse
Version: 3.20.0-3.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I today noticed that seahorse crashes reliably about a second after it has been 
started.

I get the following output in the console:

   (seahorse:16130): Gtk-WARNING **: 
(/build/gtk+3.0-NmdvYo/gtk+3.0-3.22.11/./gtk/gtkicontheme.c:5493):gtk_icon_theme_lookup_by_gicon_for_scale:
 runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

   (seahorse:16130): Gtk-WARNING **: 
(/build/gtk+3.0-NmdvYo/gtk+3.0-3.22.11/./gtk/gtkicontheme.c:2226):gtk_icon_theme_choose_icon_for_scale:
 runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

   (seahorse:16130): Gtk-WARNING **: 
(/build/gtk+3.0-NmdvYo/gtk+3.0-3.22.11/./gtk/gtkicontheme.c:5493):gtk_icon_theme_lookup_by_gicon_for_scale:
 runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

   (seahorse:16130): Gtk-WARNING **: 
(/build/gtk+3.0-NmdvYo/gtk+3.0-3.22.11/./gtk/gtkicontheme.c:2226):gtk_icon_theme_choose_icon_for_scale:
 runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)
   Segmentation fault

I know that seahorse has worked fine some time ago, but I am not sure when I 
last used it (could be few months).

Directly before trying to launch it I used python3-keyring. I cannot think of 
anything else that could be related.

-- System Information:
Debian Release: 9.5
  APT prefers stable
  APT policy: (800, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-7-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages seahorse depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  gcr  3.20.0-5.1
ii  gnome-keyring3.20.0-3
ii  gnupg2.1.18-8~deb9u2
ii  libatk1.0-0  2.22.0-1
ii  libavahi-client3 0.6.32-2
ii  libavahi-common3 0.6.32-2
ii  libavahi-glib1   0.6.32-2
ii  libc62.24-11+deb9u3
ii  libgck-1-0   3.20.0-5.1
ii  libgcr-base-3-1  3.20.0-5.1
ii  libgcr-ui-3-13.20.0-5.1
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u2
ii  libglib2.0-0 2.50.3-2
ii  libgpgme11   1.8.0-3+b2
ii  libgtk-3-0   3.22.11-1
ii  libldap-2.4-22.4.44+dfsg-5+deb9u2
ii  libsecret-1-00.18.5-3.1
ii  libsoup2.4-1 2.56.0-2+deb9u2

Versions of packages seahorse recommends:
ii  openssh-client  1:7.4p1-10+deb9u3

seahorse suggests no packages.

-- no debconf information

Bug#863631: conf file reset to default

[marc marc]

Hello,

can you reopen the issue ?
I got it today with sympa 6.1.23~dfsg-2+deb8u2

Regards,
Marc

Bug#904690: progressivemauve: broken in buster: error while loading shared libraries: libMUSCLE-3.7.so.1

[Paul Gevers]

Package: progressivemauve
Version: 1.2.0+4713+dfsg-1
Severity: grave
Justification: renders package unusable

Triggered by the failure of the autopkgtest reference¹ I installed
progressivemauve on my buster system. It can't even start.

paul@testavoira ~ $ progressiveMauve
progressiveMauve: error while loading shared libraries: libMUSCLE-3.7.so.1: 
cannot open shared object file: No such file or directory
paul@testavoira ~ $ progressiveMauve -h
progressiveMauve: error while loading shared libraries: libMUSCLE-3.7.so.1: 
cannot open shared object file: No such file or directory

progressivemauve is part of the auto-libgenome transition² which linked me to
the build log which show that it failed to rebuild for libmuscle (I actually
didn't look up why it was binNMUd for that). The current state of
progressivemauve in buster is broken. Please investigate how to fix it.

Paul

¹ https://ci.debian.net/packages/p/progressivemauve/testing/amd64/
² https://release.debian.org/transitions/html/auto-libgenome.html

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (200, 'testing'), (50, 
'testing')
Architecture: amd64 (x86_64)

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

Versions of packages progressiveMauve depends on:
ii  libboost-filesystem1.62.0   1.62.0+dfsg-8
ii  libboost-iostreams1.62.01.62.0+dfsg-8
ii  libboost-program-options1.62.0  1.62.0+dfsg-8
ii  libboost-system1.62.0   1.62.0+dfsg-8
ii  libc6   2.27-3
ii  libgcc1 1:8.1.0-10
ii  libgenome-1.3-0v5   1.3.1-10
ii  libmems-1.6-1v5 1.6.0+4725-4
ii  libmuscle1 [libmuscle-3.7-1]3.7+4565-4
ii  libstdc++6  8.1.0-10

progressiveMauve recommends no packages.

progressiveMauve suggests no packages.

-- no debconf information



signature.asc
Description: OpenPGP digital signature

Bug#903322: firmware-qlogic: firmware checksum fails for qla2100 and qla2000 FC cards with kernel 4.x

[Ben Hutchings]

Control: reassign -1 src:linux 4.16.16-2
Control: found -1 4.9.88-1+deb9u1
Control: severity -1 important

On Sun, 08 Jul 2018 16:00:36 -0400 Andrew Phillips 
 wrote:
> Package: firmware-qlogic
> Version: 20170823-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> after upgrading to any kernel above 3.x, such as 4.9 or 4.16
> on booting, qla2xxx module fails with:
> 
> Failed to initialize adapter
> Setup chip FAILED
> ISP Firmware failed checksum
> 
> this happens with qla2100 and qla2200 FC cards. This happens regardless of 
> the FC cards BIOS settings about loading RISC code.
> This happens regardless of which version of firmware-qlogic is installed, 
> from what I have found.
> 
> After going back and booting a 3.x kernel such as 3.16 , the problem is not 
> there.

If the firmware works under an old kernel version, this is a regression
in the driver, not the firmware!

Ben.
 
-- 
Ben Hutchings
Power corrupts.  Absolute power is kind of neat. - John Lehman


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

Processed: Re: firmware-qlogic: firmware checksum fails for qla2100 and qla2000 FC cards with kernel 4.x

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux 4.16.16-2
Bug #903322 [firmware-qlogic] firmware-qlogic: firmware checksum fails for 
qla2100 and qla2000 FC cards with kernel 4.x
Bug reassigned from package 'firmware-qlogic' to 'src:linux'.
No longer marked as found in versions firmware-nonfree/20170823-1.
Ignoring request to alter fixed versions of bug #903322 to the same values 
previously set
Bug #903322 [src:linux] firmware-qlogic: firmware checksum fails for qla2100 
and qla2000 FC cards with kernel 4.x
Marked as found in versions linux/4.16.16-2.
> found -1 4.9.88-1+deb9u1
Bug #903322 [src:linux] firmware-qlogic: firmware checksum fails for qla2100 
and qla2000 FC cards with kernel 4.x
Marked as found in versions linux/4.9.88-1+deb9u1.
> severity -1 important
Bug #903322 [src:linux] firmware-qlogic: firmware checksum fails for qla2100 
and qla2000 FC cards with kernel 4.x
Severity set to 'important' from 'grave'

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

Bug#904671: fwupd: Incomplete debian/copyright?

[Mario.Limonciello]

Chris,

Thanks for accepting it.  I've made this PR upstream to fill in debian/copyright
properly automatically.  We'll pull that in in the future (unless you or anyone
else has a concern).

https://github.com/hughsie/fwupd/pull/611

Thanks,

> -Original Message-
> From: Chris Lamb [mailto:la...@debian.org]
> Sent: Thursday, July 26, 2018 8:09 AM
> To: sub...@bugs.debian.org
> Subject: Bug#904671: fwupd: Incomplete debian/copyright?
> 
> Source: fwupd
> Version: 1.1.0-1
> Severity: serious
> Justication: Policy 12.5
> X-Debbugs-CC: Mario Limonciello 
> 
> Hi,
> 
> I just ACCEPTed fwupd from NEW but noticed it was missing attribution
> in debian/copyright for at least a bunch of code copies (or similar)
> under "plugins/".
> 
> This is in no way exhaustive so please check over the entire package
> carefully and address these on your next upload. :)
> 
> 
> Regards,
> 
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-

Processed: [bts-link] source package src:lmms

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:lmms
> # 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 #897806 (http://bugs.debian.org/897806)
> # Bug title: lmms: ftbfs with GCC-8
> #  * https://github.com/LMMS/lmms/pull/4353
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 897806 + fixed-upstream
Bug #897806 [src:lmms] lmms: ftbfs with GCC-8
Added tag(s) fixed-upstream.
> usertags 897806 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:i2pd

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:i2pd
> # 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 #897770 (http://bugs.debian.org/897770)
> # Bug title: i2pd: ftbfs with GCC-8
> #  * https://github.com/PurpleI2P/i2pd/issues/1085
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 897770 + fixed-upstream
Bug #897770 [src:i2pd] i2pd: ftbfs with GCC-8
Added tag(s) fixed-upstream.
> usertags 897770 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:measurement-kit

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:measurement-kit
> # 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 #897808 (http://bugs.debian.org/897808)
> # Bug title: measurement-kit: ftbfs with GCC-8
> #  * https://github.com/measurement-kit/measurement-kit/pull/1614
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 897808 + fixed-upstream
Bug #897808 [src:measurement-kit] measurement-kit: ftbfs with GCC-8
Added tag(s) fixed-upstream.
> usertags 897808 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:nasm

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:nasm
> # 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 #897817 (http://bugs.debian.org/897817)
> # Bug title: nasm: ftbfs with GCC-8
> #  * https://bugzilla.nasm.us/show_bug.cgi?id=3392461
> #  * remote status changed: (?) -> CLOSED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 897817 + fixed-upstream
Bug #897817 [src:nasm] nasm: ftbfs with GCC-8
Added tag(s) fixed-upstream.
> usertags 897817 + status-CLOSED resolution-FIXED
There were no usertags set.
Usertags are now: status-CLOSED resolution-FIXED.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:setools

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:setools
> # 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 #897857 (http://bugs.debian.org/897857)
> # Bug title: setools: ftbfs with GCC-8
> #  * https://github.com/SELinuxProject/setools/issues/2
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 897857 + fixed-upstream
Bug #897857 [src:setools] setools: ftbfs with GCC-8
Added tag(s) fixed-upstream.
> usertags 897857 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: limit source to firmware-nonfree, tagging 893952, tagging 900266, tagging 892408, tagging 869639 ...

[Debian Bug Tracking System]

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

> limit source firmware-nonfree
Limiting to bugs with field 'source' containing at least one of 
'firmware-nonfree'
Limit currently set to 'source':'firmware-nonfree'

> tags 893952 + pending
Bug #893952 [firmware-iwlwifi] firmware-iwlwifi: Intel Dual Band Wireless-AC 
8260 WiFi needs iwlwifi-8000C-34.ucode (which isn't provided)
Added tag(s) pending.
> tags 900266 + pending
Bug #900266 [src:firmware-nonfree] firmware-nonfree: include i.MX6/7 SDMA 
firmware
Added tag(s) pending.
> tags 892408 + pending
Bug #892408 [firmware-iwlwifi] firmware-iwlwifi: please package new upstream 
version to get firmware-iwlwifi-8265-34
Added tag(s) pending.
> tags 869639 + pending
Bug #869639 [firmware-brcm80211] firmware-brcm80211: BroadPwn vulnerability 
CVE-2017-9417
Added tag(s) pending.
> tags 899101 + pending
Bug #899101 [firmware-iwlwifi] firmware-iwlwifi: Missing firmware for "Intel 
Corporation Wireless-AC 9260"
Added tag(s) pending.
> tags 891042 + pending
Bug #891042 [firmware-amd-graphics] firmware-amd-graphics: Please include AMD 
Raven Ridge firmware
Added tag(s) pending.
> tags 898267 + pending
Bug #898267 [firmware-misc-nonfree] [firmware-misc-nonfree] Missing firmware 
i915/kbl_dmc_ver1_04.bin
Added tag(s) pending.
> tags 891364 + pending
Bug #891364 [firmware-amd-graphics] firmware-amd-graphics: please update amdgpu 
firmware for polaris10
Added tag(s) pending.
> tags 900871 + pending
Bug #900871 [firmware-misc-nonfree] Missing last i915 firmware versions. 
Package need update for kernel 4.16.0.1 and 4.16.0.2.
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
869639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869639
891042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891042
891364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891364
892408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892408
893952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893952
898267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898267
899101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899101
900266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900266
900871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900871
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903342: marked as done (sshfs-fuse: FTBFS in buster/sid (dh_installdocs: Cannot find "FAQ"))

[Debian Bug Tracking System]

Your message dated Fri, 27 Jul 2018 02:21:32 +1000
with message-id <15350475.umeUvcQifB@deblab>
and subject line Done: sshfs-fuse: FTBFS in buster/sid (dh_installdocs: Cannot 
find "FAQ")
has caused the Debian Bug report #903342,
regarding sshfs-fuse: FTBFS in buster/sid (dh_installdocs: Cannot find "FAQ")
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.)


-- 
903342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sshfs-fuse
Version: 2.10-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --with autoreconf
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking
configure: WARNING: unrecognized options: --disable-maintainer-mode
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no

[... snipped ...]

<./sshfs.1.in >sshfs.1.tmp || exit 1; \
mv sshfs.1.tmp sshfs.1
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_auto_test -a
make -j1 check VERBOSE=1
make[1]: Entering directory '/<>'
Making check in test
make[2]: Entering directory '/<>/test'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory '/<>/test'
make[2]: Entering directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
 fakeroot debian/rules binary-arch
dh binary-arch --with autoreconf
   dh_testroot -a
   dh_prep -a
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
/usr/bin/make install DESTDIR=/<>/debian/sshfs
make[2]: Entering directory '/<>'
Making install in test
make[3]: Entering directory '/<>/test'
make[4]: Entering directory '/<>/test'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/test'
make[3]: Leaving directory '/<>/test'
make[3]: Entering directory '/<>'
make[4]: Entering directory '/<>'
 /bin/mkdir -p '/<>/debian/sshfs/usr/bin'
  /usr/bin/install -c sshfs '/<>/debian/sshfs/usr/bin'
 /bin/mkdir -p '/<>/debian/sshfs/usr/share/man/man1'
 /usr/bin/install -c -m 644 sshfs.1 
'/<>/debian/sshfs/usr/share/man/man1'
make[4]: Leaving directory '/<>'
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_install -a
   dh_installdocs -a
dh_installdocs: Cannot find (any matches for) "README*" (tried in .)

dh_installdocs: Cannot find (any matches for) "FAQ" (tried in .)

debian/rules:6: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.
--- End Message ---
--- Begin Message ---
Source: sshfs-fuse
Version: 2.10+repack-2

I've already fixed that problem few day before this bug was reported...

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


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

Bug#897745: marked as done (etl: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jul 2018 15:33:56 +
with message-id 
and subject line Bug#897745: fixed in etl 1.2.1-1
has caused the Debian Bug report #897745,
regarding etl: ftbfs with GCC-8
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.)


-- 
897745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:etl
Version: 1.2.1-0.1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/etl_1.2.1-0.1_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-8/porting_to.html

[...]
pen.cpp:113:10: warning: invalid suffix on literal; C++11 requires a space 
between literal and string macro [-Wliteral-suffix]
   printf("FAILURE! "__FILE__"@%d: iterator_x inconsistency\n",__LINE__);
  ^
pen.cpp:228:10: warning: invalid suffix on literal; C++11 requires a space 
between literal and string macro [-Wliteral-suffix]
   printf("Um. malloc failure on line %d of "__FILE__"...\n",__LINE__);
  ^
pen.cpp:284:10: warning: invalid suffix on literal; C++11 requires a space 
between literal and string macro [-Wliteral-suffix]
   printf("FAILURE! "__FILE__"@%d: blur result contained %d bad 
values\n",__LINE__,bad_values);
  ^
In file included from ../ETL/pen:32,
 from pen.cpp:31:
../ETL/_pen.h: In member function 'etl::generic_pen::difference_type::value_type& etl::generic_pen::difference_type::operator[](int) const':
../ETL/_pen.h:139:51: error: binding reference of type 'etl::generic_pen::difference_type::value_type&' {aka 'int&'} to 'const value_type' {aka 
'const int'} discards qualifiers
   value_type [](int i)const { return i?y:x; }
   ^
pen.cpp: In function 'int generic_pen_test(int, int)':
pen.cpp:47:2: warning: 'template class std::auto_ptr' is deprecated 
[-Wdeprecated-declarations]
  auto_ptr data(new float[w*h]);
  ^~~~
In file included from /usr/include/c++/8/memory:80,
 from pen.cpp:29:
/usr/include/c++/8/bits/unique_ptr.h:53:28: note: declared here
   template class auto_ptr;
^~~~
pen.cpp: In function 'int box_blur_test()':
pen.cpp:224:2: warning: 'template class std::auto_ptr' is deprecated 
[-Wdeprecated-declarations]
  auto_ptr data(new boxblur_float[w*h]);
  ^~~~
In file included from /usr/include/c++/8/memory:80,
 from pen.cpp:29:
/usr/include/c++/8/bits/unique_ptr.h:53:28: note: declared here
   template class auto_ptr;
^~~~
pen.cpp:225:2: warning: 'template class std::auto_ptr' is deprecated 
[-Wdeprecated-declarations]
  auto_ptr data2(new boxblur_float[w*h]);
  ^~~~
In file included from /usr/include/c++/8/memory:80,
 from pen.cpp:29:
/usr/include/c++/8/bits/unique_ptr.h:53:28: note: declared here
   template class auto_ptr;
^~~~
make[3]: *** [Makefile:683: pen.o] Error 1
make[3]: Leaving directory '/<>/test'
make[2]: *** [Makefile:1022: check-am] Error 2
make[2]: Leaving directory '/<>/test'
make[1]: *** [Makefile:511: check-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:7: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2
--- End Message ---
--- Begin Message ---
Source: etl
Source-Version: 1.2.1-1

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

A 

Bug#904656: visidata: fails to install with Python 3.7

[Anja]

Hi Andreas!

Agreed. We have actually merged in a patch for this upstream:
https://github.com/saulpw/visidata/pull/165 but the update has not made it
to Debian's repository yet.

I will repackage and submit 1.2.1 through the upload process ASAP.

Thanks for the notification and nudge. =)

~Anja

On 26 July 2018 at 02:26, Andreas Beckmann  wrote:

> Package: visidata
> Version: 1.0-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...):
>
>   Setting up visidata (1.0-1) ...
> File "/usr/lib/python3/dist-packages/visidata/__init__.py", line 7
>   from .async import *
> ^
>   SyntaxError: invalid syntax
>
> File "/usr/lib/python3/dist-packages/visidata/canvas.py", line 519
>   @async
>^
>   SyntaxError: invalid syntax
>
> File "/usr/lib/python3/dist-packages/visidata/cmdlog.py", line 286
>   @async
>^
>   SyntaxError: invalid syntax
>
> File "/usr/lib/python3/dist-packages/visidata/data.py", line 226
>   @async
>^
>   SyntaxError: invalid syntax
>
> [...]
>
> File "/usr/lib/python3/dist-packages/visidata/pivot.py", line 32
>   @async
>^
>   SyntaxError: invalid syntax
>
> File "/usr/lib/python3/dist-packages/visidata/tidydata.py", line 15
>   @async
>^
>   SyntaxError: invalid syntax
>
> File "/usr/lib/python3/dist-packages/visidata/vdtui.py", line 452
>   def async(func):
>   ^
>   SyntaxError: invalid syntax
>
>   dpkg: error processing package visidata (--configure):
>installed visidata package post-installation script subprocess returned
> error exit status 1
>
>
> "async" has become a reserved keyword in Python 3.7
>
>
> cheers,
>
> Andreas
>

Bug#897745: Bug #897745 in etl marked as pending

[Dmitry Smirnov]

Control: tag -1 pending

Hello,

Bug #897745 in etl 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/multimedia-team/etl/commit/b21e9faa67f3653050bec4b8548d49f8e3d6fc56


New patch to fix FTBFS with GCC8 (Closes: #897745)

Thanks, Philip Chung.



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/897745

Processed: Bug #897745 in etl marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #897745 [src:etl] etl: ftbfs with GCC-8
Added tag(s) pending.

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

Bug#888366: marked as done (qtwebengine-opensource-src: FTBFS with FFmpeg 4.0)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jul 2018 14:54:37 +
with message-id 
and subject line Bug#888366: fixed in qtwebengine-opensource-src 5.11.1+dfsg-4
has caused the Debian Bug report #888366,
regarding qtwebengine-opensource-src: FTBFS with FFmpeg 4.0
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.)


-- 
888366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtwebengine-opensource-src
Version: 5.9.2+dfsg-2
Severity: important
User: debian-multime...@lists.debian.org
Usertags: ffmpeg-3.5-transition

Hi,

Your package FTBFS with the upcoming version 3.5 of FFmpeg. In FFmpeg 3.5,
there are a number of API changes which will cause many packages to FTBFS.
For this reason I have uploaded an early development snapshot to experimental
before the 3.5 release in an attempt to fix some of these a bit quicker.
While 3.5 has not been finalized and the ABI is not stable yet, there should
not be any significant API breakages before the release.

Incomplete list of changes (based on looking at common build failures):
- Some fields in AVCodecContext have been removed and replaced with private
  options which can be set using the av_opt_set* APIs
- Most CODEC_* constants have been renamed to AV_CODEC_*
- The buffer constants FF_INPUT_BUFFER_PADDING_SIZE and FF_MIN_BUFFER_SIZE
  have been renamed to AV_INPUT_BUFFER_PADDING_SIZE and
  AV_INPUT_BUFFER_MIN_SIZE.
- The old resampling API provided by libavcodec has been removed. Use
  libswresample instead.
- The libavfilter/avfiltergraph.h header has been removed, include
  libavfilter/avfilter.h instead.
- The AVFrac structure (representing mixed rational numbers) has been
  removed.

Build log:
https://people.debian.org/~jcowgill/ffmpeg-3.5-20180122/qtwebengine-opensource-src_amd64.build

Thanks,
James
--- End Message ---
--- Begin Message ---
Source: qtwebengine-opensource-src
Source-Version: 5.11.1+dfsg-4

We believe that the bug you reported is fixed in the latest version of
qtwebengine-opensource-src, 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 888...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
qtwebengine-opensource-src 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, 26 Jul 2018 10:41:58 -0300
Source: qtwebengine-opensource-src
Binary: qtwebengine5-dev qtwebengine5-private-dev libqt5webengine5 
libqt5webenginecore5 libqt5webenginewidgets5 libqt5webengine-data 
qml-module-qtwebengine qtwebengine5-dev-tools qtwebengine5-examples 
qtwebengine5-doc qtwebengine5-doc-html
Architecture: source
Version: 5.11.1+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Description:
 libqt5webengine-data - Web content engine library for Qt - Data
 libqt5webengine5 - Web content engine library for Qt
 libqt5webenginecore5 - Web content engine library for Qt - Core
 libqt5webenginewidgets5 - Web content engine library for Qt - Widget
 qml-module-qtwebengine - Qt WebEngine QML module
 qtwebengine5-dev - Web content engine library for Qt - development files
 qtwebengine5-dev-tools - Qt WebEngine tools
 qtwebengine5-doc - Qt 5 webengine documentation
 qtwebengine5-doc-html - Qt 5 webengine HTML documentation
 qtwebengine5-examples - Qt WebEngine - Examples
 qtwebengine5-private-dev - Web content engine library for Qt - private 
development files
Closes: 888366
Changes:
 qtwebengine-opensource-src (5.11.1+dfsg-4) unstable; urgency=medium
 .
   * Add increase_decoderbuffer_kpaddingsize.patch to fix FTBFS with new FFmpeg
 (Closes: #888366). Thanks *a lot* Sebastian Ramacher for the pointer.
Checksums-Sha1:
 acf641b764a047162a9547d442a3a21401f43c48 4622 
qtwebengine-opensource-src_5.11.1+dfsg-4.dsc
 6da733522a76fc2e3dda1fd9458efa32d7daa6d7 462244 
qtwebengine-opensource-src_5.11.1+dfsg-4.debian.tar.xz
 bec16c815066cc813fc2e5b84e1751fda7511094 13662 
qtwebengine-opensource-src_5.11.1+dfsg-4_source.buildinfo
Checksums-Sha256:
 

Bug#897750: marked as done (freecontact: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jul 2018 13:48:52 +
with message-id 
and subject line Bug#897750: fixed in freecontact 1.0.21-7
has caused the Debian Bug report #897750,
regarding freecontact: ftbfs with GCC-8
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.)


-- 
897750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:freecontact
Version: 1.0.21-6
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/freecontact_1.0.21-6_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-8/porting_to.html

[...]
 /usr/bin/install -c -m 644 freecontact.h 
'/<>/debian/tmp/usr/include'
make[3]: Leaving directory '/<>/lib'
make[2]: Leaving directory '/<>/lib'
Making install in src
make[2]: Entering directory '/<>/src'
make[3]: Entering directory '/<>/src'
 /bin/mkdir -p '/<>/debian/tmp/usr/bin'
  /bin/bash ../libtool   --mode=install /usr/bin/install -c freecontact 
'/<>/debian/tmp/usr/bin'
libtool: warning: '../lib/libfreecontact.la' has not been installed in 
'/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/freecontact 
/<>/debian/tmp/usr/bin/freecontact
 /bin/mkdir -p '/<>/debian/tmp/usr/share/doc/freecontact/examples'
 /usr/bin/install -c -m 644 demo_1000.aln demo_1000.psicov.50 
PF00071_v25_999.fa PF00071_v25_999.xml PF00071_v25_999.evfold.50 
PF00071_v25_999.evfold.50.xml 
'/<>/debian/tmp/usr/share/doc/freecontact/examples'
 /bin/mkdir -p '/<>/debian/tmp/usr/share/freecontact'
 /usr/bin/install -c -m 644 BioXSD-1.1.xsd freecontact_input.xsd 
freecontact_output.xsd '/<>/debian/tmp/usr/share/freecontact'
 /bin/mkdir -p '/<>/debian/tmp/usr/share/freecontact'
 /usr/bin/install -c a2m2aln '/<>/debian/tmp/usr/share/freecontact'
 /bin/mkdir -p '/<>/debian/tmp/usr/share/man/man1'
 /usr/bin/install -c -m 644 freecontact.1 
'/<>/debian/tmp/usr/share/man/man1'
make[3]: Leaving directory '/<>/src'
make[2]: Leaving directory '/<>/src'
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
d-shlibmove --commit \
--multiarch \
--exclude-la \
--devunversioned \
--override s/libblas3-dev/libblas-dev/ \
--v5 \
--override s/libgfortran[34]-dev/libgfortran-7-dev/ \
--override s/libquadmath0-dev/libgcc-7-dev/ \
--override s/liblapack3-dev/liblapack-dev/ \
--movedev debian/tmp/usr/include/* usr/include \
debian/tmp/usr/lib/*/*.so
Library package automatic movement utility
 --> libblas-dev package exists.
 --> libgcc-7-dev package exists.
devlibs error: There is no package matching [libgfortran5-dev] and noone 
provides it, please report bug to d-shlibs maintainer
 --> liblapack-dev package exists.
make[1]: *** [debian/rules:29: override_dh_install] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:13: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2
--- End Message ---
--- Begin Message ---
Source: freecontact
Source-Version: 1.0.21-7

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

A summary of the changes between this version 

Bug#888366: qtwebengine-opensource-src: FTBFS with FFmpeg 4.0

[Lisandro Damián Nicanor Pérez Meyer]

El jueves, 26 de julio de 2018 05:21:43 -03 Sebastian Ramacher escribió:
[snip] 
> > qtwebengine 5.11 almost fixes this. The only thing left is this chromium
> > commit needs cherry-picking:
> > https://github.com/chromium/chromium/commit/a568ded46a678eac8139cb06595819
> > c5ae874177
> Looks like this commit was not included in the last upload to unstable. It
> now FTBFS with:
> 
> ../../3rdparty/chromium/media/ffmpeg/ffmpeg_common.cc:36:43: error: static
> assertion failed: DecoderBuffer padding size does not fit ffmpeg
> requirement static_assert(DecoderBuffer::kPaddingSize >=
> AV_INPUT_BUFFER_PADDING_SIZE, ^

Indeed it slipped just under our noses. Our fault, thanks *a lot* for this 
follow up!

-- 
No pienses que estoy loco, es sólo una manera de actuar
  De mí - Charly García

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Processed: tagging 904554, tagging 904555, tagging 904556, tagging 904561

[Debian Bug Tracking System]

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

> tags 904554 + sid buster
Bug #904554 [libgtk2-spell-perl] libgtk2-spell-perl: Don't ship 
libgtk2-spell-perl in Buster
Added tag(s) buster and sid.
> tags 904555 + sid buster
Bug #904555 [libgtk2-traymanager-perl] libgtk2-traymanager-perl: Don't ship 
libgtk2-traymanager-perl in Buster
Added tag(s) sid and buster.
> tags 904556 + sid buster
Bug #904556 [libgtk2-trayicon-perl] libgtk2-trayicon-perl: Don't ship 
libgtk2-trayicon-perl in Buster
Added tag(s) buster and sid.
> tags 904561 + sid buster
Bug #904561 [libgtk2-gladexml-perl] libgtk2-gladexml-perl: Don't ship 
libgtk2-gladexml-perl in Buster
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#904673: lief: Incomplete debian/copyright?

[Chris Lamb]

Source: lief
Version: 0.8.3-2
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Hilko Bengen 

Hi,

I just ACCEPTed lief from NEW but noticed it was missing attribution 
in debian/copyright for a bunch of files under include/LIEF?

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload. :)


Regards,

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

Bug#887687: [Debconf-devel] Bug#887687: libsmokeqt4-dev: broken symlinks and causes qt4-perl FTBFS

[Colin Watson]

On Fri, Jun 29, 2018 at 10:22:50AM +0300, Niko Tyni wrote:
> On Fri, Jun 29, 2018 at 12:55:50AM +, Scott Kitterman wrote:
> > I had hoped to work on this this week.  It hasn't happened and it's not 
> > going to.
> > 
> > In the end, I the Qt4 stuff has to go, so I wouldn't wait on this for the 
> > transition.
> 
> Okay, thanks. The problem is that we can't really get Perl 5.28 into
> testing if that makes debconf fail to build. So something needs to
> be done.
> 
> I think I'll try to push debconf #629405 ("libqtgui4-perl based frontend
> might need to be removed") then.

That's now fixed, so as far as debconf is concerned you can remove
qt4-perl.

-- 
Colin Watson   [cjwat...@debian.org]

Bug#904671: fwupd: Incomplete debian/copyright?

[Chris Lamb]

Source: fwupd
Version: 1.1.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Mario Limonciello 

Hi,

I just ACCEPTed fwupd from NEW but noticed it was missing attribution 
in debian/copyright for at least a bunch of code copies (or similar)
under "plugins/".

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload. :)


Regards,

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

Bug#901968: marked as done (glusterfs: CVE-2018-10841: access trusted peer group via remote-host command)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jul 2018 13:04:31 +
with message-id 
and subject line Bug#901968: fixed in glusterfs 4.1.2-1
has caused the Debian Bug report #901968,
regarding glusterfs: CVE-2018-10841: access trusted peer group via remote-host 
command
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.)


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

Hi,

The following vulnerability was published for glusterfs.

CVE-2018-10841[0]:
| glusterfs is vulnerable to privilege escalation on gluster server
| nodes. An authenticated gluster client via TLS could use gluster cli
| with --remote-host command to add it self to trusted storage pool and
| perform privileged gluster operations like adding other machines to
| trusted storage pool, start, stop, and delete volumes.

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-10841
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10841
[1] 
http://git.gluster.org/cgit/glusterfs.git/commit/?id=e8d928e34680079e42be6947ffacc4ddd7defca2
[2] https://review.gluster.org/#/c/20328/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: glusterfs
Source-Version: 4.1.2-1

We believe that the bug you reported is fixed in the latest version of
glusterfs, 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 901...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Patrick Matthäi  (supplier of updated glusterfs 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, 26 Jul 2018 14:23:11 +0200
Source: glusterfs
Binary: glusterfs-client glusterfs-server glusterfs-common
Architecture: source amd64
Version: 4.1.2-1
Distribution: unstable
Urgency: high
Maintainer: Patrick Matthäi 
Changed-By: Patrick Matthäi 
Description:
 glusterfs-client - clustered file-system (client package)
 glusterfs-common - GlusterFS common libraries and translator modules
 glusterfs-server - clustered file-system (server package)
Closes: 901968
Changes:
 glusterfs (4.1.2-1) unstable; urgency=high
 .
   * New upstream release.
 - Fixes CVE-2018-10841: Access trusted peer group via remote-host command.
   Closes: #901968
 - Drop patch 02-shell-syntax-error.
 - Install new gsyncd.conf file.
   * Merge 4.0.2-1~bpo9+1 changelog.
   * Remove trailing whitespace from debian/changelog.
   * Adjust lintian warnings.
   * Bump Standards-Version to 4.1.5.
   * Merge patch 03-spelling-errors into 01-spelling-error.
   * Adjust lintian overrides.
   * Correct patch 04-systemd-fixes. The documentation key is placed in the unit
 section now.
Checksums-Sha1:
 59a05faa74424db96b174d26a66695cc6d6db75c 2157 glusterfs_4.1.2-1.dsc
 b0df039cc148680096a64aeab403f3b6b74670f2 7830484 glusterfs_4.1.2.orig.tar.gz
 68f8bdb69ac2a60d5ed537f48681535c8a255ca6 17656 glusterfs_4.1.2-1.debian.tar.xz
 f2aa8cee20dad6ad0a4b29ca82bb697f408d0e21 37608 
glusterfs-client-dbgsym_4.1.2-1_amd64.deb
 1da6d22a093c8413b487d3e6b38d83005ce9dd1f 2352296 
glusterfs-client_4.1.2-1_amd64.deb
 598ad54b57a8abbe866575d315fb8cfc2dcd37c4 18357852 
glusterfs-common-dbgsym_4.1.2-1_amd64.deb
 cf38f814fd22d58ea2c141e7127f3756fd8b9a30 5691720 
glusterfs-common_4.1.2-1_amd64.deb
 50436b5fe58610822cc955b78984263278e281b1 750848 
glusterfs-server-dbgsym_4.1.2-1_amd64.deb
 428710523b26d003b1e6690c8f6dc8c837a8b0a5 2525784 
glusterfs-server_4.1.2-1_amd64.deb
 fb009456779dd73f20285eb085e06544e1809696 10666 
glusterfs_4.1.2-1_amd64.buildinfo
Checksums-Sha256:
 f11e59ae4bb5a3d61ceedb1bd4edabb801c26f88eaf1254fb4479fa66e55600c 2157 
glusterfs_4.1.2-1.dsc
 6f0b01c082fec65134eea43b2e4df8d4b55269f43b7d330e81eaad920d7c63e5 7830484 
glusterfs_4.1.2.orig.tar.gz
 a2e436e1adb968a9cb430fd423d3563ca512a036e3deea607bf8f77c918389f1 17656 
glusterfs_4.1.2-1.debian.tar.xz
 a5621f165ebc60e1d184b171d751369b178218fd5398443bb3f928ee08532479 

Bug#904515: marked as done (x2goserver: fails to reinstall: ln: failed to create symbolic link '/etc/x2go/applications': File exists)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jul 2018 12:51:24 +
with message-id 
and subject line Bug#904515: fixed in x2goserver 4.1.0.0-5
has caused the Debian Bug report #904515,
regarding x2goserver: fails to reinstall: ln: failed to create symbolic link 
'/etc/x2go/applications': File exists
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.)


-- 
904515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: x2goserver
Version: 4.1.0.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package succeeded to install,
but thereafter failed to reinstall the same version over it again.

Like a plain failure on initial install this makes the package too buggy
for a release, thus the severity.

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

2m3.2s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmpijsFHK', 
'apt-get', '-y', 'install', '--reinstall', 'x2goserver=4.1.0.0-4']
2m4.3s DUMP: 
  Reading package lists...
  Building dependency tree...
  Reading state information...
  debconf: delaying package configuration, since apt-utils is not installed
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
  Need to get 0 B/107 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 
(Reading database ... 8797 files and directories currently installed.)
  Preparing to unpack .../x2goserver_4.1.0.0-4_amd64.deb ...
  Unpacking x2goserver (4.1.0.0-4) over (4.1.0.0-4) ...
  Setting up x2goserver (4.1.0.0-4) ...
  ln: failed to create symbolic link '/etc/x2go/applications': File exists
  dpkg: error processing package x2goserver (--configure):
   installed x2goserver package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   x2goserver
  E: Sub-process /usr/bin/dpkg returned an error code (1)
2m4.3s ERROR: Command failed (status=100): ['chroot', 
'/srv/piuparts/tmp/tmpijsFHK', 'apt-get', '-y', 'install', '--reinstall', 
'x2goserver=4.1.0.0-4']


cheers,

Andreas


x2goserver_4.1.0.0-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: x2goserver
Source-Version: 4.1.0.0-5

We believe that the bug you reported is fixed in the latest version of
x2goserver, 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.
Mike Gabriel  (supplier of updated x2goserver 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, 26 Jul 2018 14:36:16 +0200
Source: x2goserver
Binary: x2goserver libx2go-config-perl libx2go-log-perl libx2go-utils-perl 
libx2go-server-db-perl libx2go-server-perl x2goserver-common 
x2goserver-extensions x2goserver-fmbindings x2goserver-printing 
x2goserver-x2goagent x2goserver-xsession
Architecture: source
Version: 4.1.0.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Remote Maintainers 
Changed-By: Mike Gabriel 
Description:
 libx2go-config-perl - Perl X2Go::Config package
 libx2go-log-perl - Perl X2Go::Log package
 libx2go-server-db-perl - Perl X2Go::Server:DB package
 libx2go-server-perl - Perl X2Go::Server package
 libx2go-utils-perl - Perl X2Go::Utils package
 x2goserver - X2Go server
 x2goserver-common - X2Go Server (common files)
 x2goserver-extensions - X2Go server (extension support)
 x2goserver-fmbindings - X2Go Server (file manager bindings)
 x2goserver-printing - X2Go server (printing support)
 x2goserver-x2goagent - X2Go Server's X2Go Agent
 x2goserver-xsession - X2Go server (Xsession runner)
Closes: 904515 904519
Changes:
 x2goserver (4.1.0.0-5) unstable; urgency=medium
 .
   * debian/libx2go-server-db-perl.postrm:
 + Don't remove files when purging that actually belong to 
x2goserver-common.
   (Closes: #904519).
 + Drop file entirely.
   * debian/x2goserver.postinst:
 + When testing for existence of /etc/x2go/applications, also consider it
   being a dangling symlink (dangling symlinks are not caught by 'test -e',
   

Bug#904519: marked as done (libx2go-server-db-perl: purging deletes /etc/x2go/x2gosql/sql which is owned by x2goserver-common)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jul 2018 12:51:24 +
with message-id 
and subject line Bug#904519: fixed in x2goserver 4.1.0.0-5
has caused the Debian Bug report #904519,
regarding libx2go-server-db-perl: purging deletes /etc/x2go/x2gosql/sql which 
is owned by x2goserver-common
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.)


-- 
904519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libx2go-server-db-perl
Version: 4.1.0.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package removes files that
were installed by another package.
The removed files were already present before the package was installed,
they may have been shipped or created by a dependency.

This could be a violation of policy 10.7.4 ("Sharing configuration
files"), see
https://www.debian.org/doc/debian-policy/#sharing-configuration-files
or policy chapter 6 ("Package maintainer scripts..."), see
https://www.debian.org/doc/debian-policy/#package-maintainer-scripts-and-installation-procedure
or policy 7.6 ("Overwriting files..."), see
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

If a directory is used by several packages, all should ship it as part
of the package (possibly empty, using $package.dirs to create it), and
no package should mkdir/rmdir it in the maintainer scripts as dpkg will
take care of this.

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

0m39.7s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmpjP2Kww', 
'dpkg', '--purge', 'libx2go-server-db-perl']
0m39.7s DUMP: 
  (Reading database ... 7091 files and directories currently installed.)
  Purging configuration files for libx2go-server-db-perl (4.1.0.0-4) ...
  Removing X2Go session database
  removed '/etc/x2go/x2gosql/passwords/pgadmin'
  removed '/etc/x2go/x2gosql/sql'
0m39.7s DEBUG: Command ok: ['chroot', '/srv/piuparts/tmp/tmpjP2Kww', 'dpkg', 
'--purge', 'libx2go-server-db-perl']

0m40.5s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /etc/x2go/x2gosql/sql (from x2goserver-common package)


cheers,

Andreas


libx2go-server-db-perl_4.1.0.0-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: x2goserver
Source-Version: 4.1.0.0-5

We believe that the bug you reported is fixed in the latest version of
x2goserver, 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.
Mike Gabriel  (supplier of updated x2goserver 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, 26 Jul 2018 14:36:16 +0200
Source: x2goserver
Binary: x2goserver libx2go-config-perl libx2go-log-perl libx2go-utils-perl 
libx2go-server-db-perl libx2go-server-perl x2goserver-common 
x2goserver-extensions x2goserver-fmbindings x2goserver-printing 
x2goserver-x2goagent x2goserver-xsession
Architecture: source
Version: 4.1.0.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Remote Maintainers 
Changed-By: Mike Gabriel 
Description:
 libx2go-config-perl - Perl X2Go::Config package
 libx2go-log-perl - Perl X2Go::Log package
 libx2go-server-db-perl - Perl X2Go::Server:DB package
 libx2go-server-perl - Perl X2Go::Server package
 libx2go-utils-perl - Perl X2Go::Utils package
 x2goserver - X2Go server
 x2goserver-common - X2Go Server (common files)
 x2goserver-extensions - X2Go server (extension support)
 x2goserver-fmbindings - X2Go Server (file manager bindings)
 x2goserver-printing - X2Go server (printing support)
 x2goserver-x2goagent - X2Go Server's X2Go Agent
 x2goserver-xsession - X2Go server (Xsession runner)
Closes: 904515 904519
Changes:
 x2goserver (4.1.0.0-5) unstable; urgency=medium
 .
   * debian/libx2go-server-db-perl.postrm:
 + Don't remove files when purging that actually belong to 
x2goserver-common.
   (Closes: #904519).
 + Drop file entirely.
   * debian/x2goserver.postinst:
 + When testing for existence of /etc/x2go/applications, also consider it
   

Bug#904524: kdump-tools: fails to install with --install-recommends

[Thadeu Lima de Souza Cascardo]

Package: kdump-tools
Version: 1:1.6.4-1
Followup-For: Bug #904524

A quick test here shows that calling the kernel postinst script will
fail because there is no kernel installed in a chroot. Assuming you used
a chroot for piuparts.

One solution here would be to not fail when the kernel is not found.
Other failures might happen when calling kdump-config as well, so we
will have to test those cases as well.

Cascardo.

Processed: Bug #904515 in x2goserver marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #904515 [x2goserver] x2goserver: fails to reinstall: ln: failed to create 
symbolic link '/etc/x2go/applications': File exists
Added tag(s) pending.

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

Bug#904515: Bug #904515 in x2goserver marked as pending

[Mike Gabriel]

Control: tag -1 pending

Hello,

Bug #904515 in x2goserver 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/debian-remote-team/x2goserver/commit/2063756e0bdf39d47eb04681f6b35aa2091b15c1


debian/x2goserver.postinst: When testing for existence of 
/etc/x2go/applications, also consider it being a dangling symlink (dangling 
symlinks are not caught by 'test -e', but need a 'test -L'. Thanks for Andreas 
Beckmann for helping with this. (Closes: #904515).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/904515

Bug#904667: sumo FTBFS due to a C++ error

[Nicolas Braud-Santoni]

Source: sumo
Version: 0.32.0+dfsg1-1
Severity: serious
Justification: FTBFS

Hi,

While rebuilding packages in preparation of the json-c transition (#904418),
I discovered that sumo fails to build from source, independently of the
transition.

Please find a build log attached.


Best,

  nicoo

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

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#904012: marked as done (wand: depends on old libmagickwand-6.q16-5)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jul 2018 12:05:12 +
with message-id 
and subject line Bug#904012: fixed in wand 0.4.4-2
has caused the Debian Bug report #904012,
regarding wand: depends on old libmagickwand-6.q16-5
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.)


-- 
904012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wand
Version: 0.4.4-1.3
Severity: serious
Control: block 902558 with -1

Hi,

wand depends on libmagickwand-6.q16-5, which has been superseeded
by libmagickwand-6.q16-6. Please update your package to work with
the new SONAME.

Emilio
--- End Message ---
--- Begin Message ---
Source: wand
Source-Version: 0.4.4-2

We believe that the bug you reported is fixed in the latest version of
wand, 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.
Changwoo Ryu  (supplier of updated wand 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, 26 Jul 2018 18:30:30 +0800
Source: wand
Binary: python-wand python3-wand pypy-wand wand-doc
Architecture: source
Version: 0.4.4-2
Distribution: unstable
Urgency: medium
Maintainer: Changwoo Ryu 
Changed-By: Changwoo Ryu 
Description:
 pypy-wand  - Python interface for ImageMagick library (PyPy build)
 python-wand - Python interface for ImageMagick library (Python 2 build)
 python3-wand - Python interface for ImageMagick library (Python 3 build)
 wand-doc   - Python interface for ImageMagick library - documentation
Closes: 904012
Changes:
 wand (0.4.4-2) unstable; urgency=medium
 .
   * Update dependencies on libmagicwand to libmagickwand-6.q16-6 (Closes:
 #904012)
   * Use salsa.d.o for Vcs-*.
   * Depends on python3-sphinx instead of python-sphinx.
   * Remove X-Python-Version: >= 2.6 and X-Python3-Version: >= 3.2, which
 are satisfied by Debian oldstable and not needed anymore.
Checksums-Sha1:
 7e57078cc87dd554a4883361e43688c43dccd389 2179 wand_0.4.4-2.dsc
 a187163c5cb889c234e2e753571081ddf037e576 9920 wand_0.4.4-2.debian.tar.xz
 4087717d3932286dbcdbdfa3a5276f992d74d527 7808 wand_0.4.4-2_source.buildinfo
Checksums-Sha256:
 9ac2b86fa0a752732589bea260cd02d0979c4d317ff787d94c4ebb36e7a43f8e 2179 
wand_0.4.4-2.dsc
 23c126d78c02e78d2297f05c941f3d2d9b36fdd10353c207ca800b42e615a37b 9920 
wand_0.4.4-2.debian.tar.xz
 69c3e4ba504398fd2a6e3ab50ad0bc1844baee4bf2bff90f6faa78c54b65798b 7808 
wand_0.4.4-2_source.buildinfo
Files:
 e7af5bd4b5c476cb960960c9487b8fac 2179 python optional wand_0.4.4-2.dsc
 1783c93b218991f16d2903cc2f349b3c 9920 python optional 
wand_0.4.4-2.debian.tar.xz
 595eaa0ac9d620b9051024b9a09859bb 7808 python optional 
wand_0.4.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEony+ujUlaGU4DgzJ7Bh50HbYq0gFAltZr0MRHGN3cnl1QGRl
Ymlhbi5vcmcACgkQ7Bh50HbYq0gClg//a/qsTGSrIEgDu3KoqzBU+YsMfYuKkdIJ
7S4pfGTewauLT42qxiJRt6e66SHeMhu+pdukal8xs9WOFGfYGXSQuLAjumSZdkAq
UGo8vHiiKtV6+nQeUmHQE25+1GtRFGy96Fixa713kL6i9YherRInt2IH8YQzjkG4
UCGGH80nd84pn1b59xRGwmgbf1l/JcYad3odQhNAFKQfbq/Oxn3jorFBgPH1MmWx
NfGu5WUQMBQAQ6wBR2qOKJjcYFsuUyhpUZpWTEwqEYbX563E/40W08MC2dzW+gb5
KLyk6MaqUdkbuHYTSHly1y8xfJwmZoyIxK3BQJB5Ni9i76ENimhoSXBjBq3M8Udh
yUYtkzVbDa34+uyF+Nf7Cm2GIcPP+IX1G/XhGyFOPh/23Jr0lXWHbXflsTXaQpDM
fNDsW9gDZjlZLJvNkMUIj55b3YgWcS0ZnuL/Y3kPkUYQOFxi3IEgxKajY9R7Yn3S
MPgbsx5hHGtfDOn4gEFt0I/sKsaJlkRQcMuJ4eON9oW0H3GCTvN6aSawTsBqLs5g
ZOPhqlJhGuuWEo8hMIUHIMyYdlEOGgrPiBGB0nPRCUep2SmXt3nLNG6TDCl/mIVW
SI6yZ+QQJUhjjh86ya82kjOvb9CTscW8btrptw50u+hnBqfkQ+ux/okQ2FWRNDlu
aVbeEfiYvRs=
=RN3X
-END PGP SIGNATURE End Message ---

Bug#882932: marked as done (php7cc FTBFS with phpunit 6.4.4-2)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jul 2018 11:23:38 +
with message-id 
and subject line Bug#882932: fixed in php7cc 1.2.1-1
has caused the Debian Bug report #882932,
regarding php7cc FTBFS with phpunit 6.4.4-2
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.)


-- 
882932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php7cc
Version: 1.1.0-1
Severity: serious
Tags: buster sid

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php7cc-1.1.0'
phpunit --verbose
PHP Fatal error:  Class 'PHPUnit_Framework_TestCase' not found in 
/build/1st/php7cc-1.1.0/test/code/CompatibilityViolation/FileContextTest.php on 
line 8
debian/rules:18: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 255
--- End Message ---
--- Begin Message ---
Source: php7cc
Source-Version: 1.2.1-1

We believe that the bug you reported is fixed in the latest version of
php7cc, 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 882...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated php7cc 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, 26 Jul 2018 16:32:40 +1000
Source: php7cc
Binary: php7cc
Architecture: source amd64
Version: 1.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: Dmitry Smirnov 
Description:
 php7cc - command line tool to detect PHP 7 incompatible code
Closes: 882932
Changes:
 php7cc (1.2.1-1) unstable; urgency=medium
 .
   * New upstream release.
 + No longer "FTBFS with phpunit 6.4.4", upstream removed tests...
   (Closes: #882932).
   * Vcs URLs to Salsa.
   * Standards-Version: 4.1.5.
   * debhelper & compat to version 11.
Checksums-Sha1:
 f79a7d784d2df44b35c0090e05b0fb6de7980764 2043 php7cc_1.2.1-1.dsc
 0d3416121a9f131a5f0fd012e586bf3891bcbc6a 24980 php7cc_1.2.1.orig.tar.xz
 0cea2a1b8afa18f7a14c417ddad9106baae6f201 3652 php7cc_1.2.1-1.debian.tar.xz
 d4c28d89aac9ada877f71af01e88873b82a50734 7745 php7cc_1.2.1-1_amd64.buildinfo
 981d0d2558194110196f657c6b34a61a1a584f59 28800 php7cc_1.2.1-1_amd64.deb
Checksums-Sha256:
 6fcf21c3cc3cedc66e77518e96d3d2f8a4a2ccc7a076a1a83323501c3e59d65b 2043 
php7cc_1.2.1-1.dsc
 77f430b05970eb40daf56592f6ee0b5352cea9281fa30029aa99dce43bcbaed5 24980 
php7cc_1.2.1.orig.tar.xz
 bac43c78ba6281f4968a2a2da41907ddca52ea7c448d006c0d720695074823db 3652 
php7cc_1.2.1-1.debian.tar.xz
 3adec84b854e17e560ac9323cfd6d97fdf7bf77a23d9132abfc85462197d3356 7745 
php7cc_1.2.1-1_amd64.buildinfo
 2419ac327fa7484cc3d868b6788617a14f678d0439bbfff73365dffcd9c05620 28800 
php7cc_1.2.1-1_amd64.deb
Files:
 dc410b1ccb8425f76c26aa8c04d30341 2043 utils optional php7cc_1.2.1-1.dsc
 4dbf25c9b10cf6397a1d1bbc141ae364 24980 utils optional php7cc_1.2.1.orig.tar.xz
 065f66cf0c96217e1fac136ee5eae491 3652 utils optional 
php7cc_1.2.1-1.debian.tar.xz
 37f5c1a4a117e8c3c3a6d49ccea4e8db 7745 utils optional 
php7cc_1.2.1-1_amd64.buildinfo
 e4963b26d9f47e42af5487644c98f92a 28800 utils optional php7cc_1.2.1-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAltZppAACgkQUra72VOW
jRvGQg//UOIguRQmu2CjscM3I3sAiV+gN7J0rR/OFwaSmGHmPXjzm7c8zbqzqHPh
SlJbKt+RQTsn7iou0gbhD8h17rmwfcgFMiil0vcOVr26QLlqYmaW+ENuulDRaWGp
pvkNoRbbghLgMTkVRyJ4syqPS/xRQQ8e8RUfQpv0xaXelt2OC17zsAJf0AdWbsr+
hl6CfGPgMFRzNhGiDbd3BSpC2+QVrWFkd+OMejhamCsV4dcDXZKPZsx+Nin0iZtQ
mwufKELfnpQS/45Sl+OGrHmGTJKTIUMamvBrI30j+JUpGsCzf4jAvFN8c5JPC+DA
HREi7/h/3fbVyDevvL8NSBcbibHXdvO59n0xqNuhbSA3SXNjzH/vWKs/7Dc9N7kI
+J6K3KB08qd9PwwawFMvbOH90yKsM3UfC6ZYO+0FKF5Mbvtwcalbt13nl5sXsdIX
eG3Eemgye7MghF3viOASkJ6XqoH18uy/MeQ+5aPOp2b5CN95eVxdZb4uEI4gLBXE
y8ziToW53nqLjQqELrdTuK4Ys6DBchB6NdQJjR8o57bis46EVImMwUqAiWU/K2b6
TD2+g03kegfTEO/8I7hHoLnCswkstQzy7V2ihj2PdUyCJgZxgUEQO73rAYhSnxQb
5JSfWyXjH1Fbfk+hf0OM74YHr5GjGjaOBAPmsHqYzwJmxGg2pDk=
=qeAq
-END PGP SIGNATURE End Message ---

Bug#904459: netdata: modifies conffiles (policy 10.7.3): /etc/netdata/health_alarm_notify.conf

[Andreas Beckmann]

[resent due to bounce]

On 2018-07-26 11:58, Andreas Beckmann wrote:
> On 2018-07-26 11:19, Daniel Baumann wrote:
>> On 07/26/2018 10:39 AM, Andreas Beckmann wrote:
>>> Shipping it as a conffile *and* managing it with debconf/ucf/... at the
>>> same time is a violation, since dpkg will prompt for a modified conffile
>>> once you ship a modified version of the conffile.
>>
>> I'm not sure I understand (please bear with me), let's find out where my
>> misunderstanding is..
>>
>> ..as far as I understand there are only three cases:
>>
>>   1) install the package, accept the debconf default
>>
>>  -> conffile shipps already with default value,
>> no modification happens, everything is fine.
>>
>>  no problem, right?
> 
> This is the case tested by piuparts (using DEBIAN_FRONTEND=noninteractive).
> 
> But the conffile gets modified (debsums reports modifications).
> Otherwise I^Wpiuparts wouldn't have noticed.
> 
>>   2) user changes something else in conffile manually
>>
>>  -> dpkg will ask as expected what to do because
>> the conffile was modified compared to what
>> was shipped.
>>
>>  no problem, right?
> 
> Correct.
> 
>>   3) install (or dpkg-reconfigure) the package, answer
>>  the debconf question with (non-default) 'no'
>>
>>  -> conffile gets changed
>>
>>  when you upgrade the package, dpkg will behave
>>  as expected as the conffile got modified
>>  (just like you had it manually modified).
>>
>>  no problem, right?
> 
> This is wrong. Unneccessary prompting. (Unless you added e.g. a new
> debconf question, but then a dpkg prompt is still wrong.)
> 
> If you used ucf, this would be handled gracefully without prompting.
> 
>>> Try adding a comment
>>> to the file you ship, rebuild the package, install it, ouch.
>>
>> just to be sure i get it: are you talking about the initial installation
>> of such a modified package, or the update from the 'normal' to the
>> 'modifled' one?
> 
> update from current (accepting the default answer) to modified
> 
> 
> Andreas
> 

Bug#902788: python3-minimal needs Breaks for software/modules broken by 3.7

[Andreas Beckmann]

Followup-For: Bug #902788

Hi,

we should now have bug reports for packages in sid currently failing to
install with python3.7 installed and blocking this bug report.
There may be even more failures, but currently hidden behind failing
dependencies.


Andreas

Processed: block 902788 with 904453 ..., block 902788 with 903888, tagging 903888, severity of 903888 is serious ...

[Debian Bug Tracking System]

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

> block 902788 with 904453
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 902650 902817 903145 904298 902766 903030 904648 904382 
904587 903388 904656 904357 904491 902900 904576 904654 904350 904390 904365 
904373 902631 904389 903457 902794 903423 904358 903529 904381 904644 904363 
904603 903525 903784 904579 903522 904364 904615 903016 904642 904367 904361 
904383 904369 904657 903031 904649 904351 903826 902761 904653 902989 904388 
902757 902715 903218 902646 903527 903558 904492 903526 904368 904650 904370 
903528 904371 904343 904581
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904453
> retitle 902788 python3.7: needs Breaks for software/modules broken by 3.7 
> ("async" became a reserved keyword)
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
Changed Bug title to 'python3.7: needs Breaks for software/modules broken by 
3.7 ("async" became a reserved keyword)' from 'python3-minimal needs Breaks for 
software/modules broken by 3.7'.
> block 902788 with 903888
Bug #902788 [python3.7] python3.7: needs Breaks for software/modules broken by 
3.7 ("async" became a reserved keyword)
902788 was blocked by: 902900 904298 902757 904364 903423 903826 902631 904390 
904389 904587 903528 902766 904576 904383 904367 904388 904654 904351 903529 
904581 903145 903784 904656 904357 904615 903218 904363 902794 903558 902761 
904373 904657 902817 904453 904369 904644 903527 902715 903522 904579 904642 
902989 904653 904649 903525 904650 904358 902650 904370 904491 903030 904371 
904648 904382 904492 903526 904350 904343 903031 903388 904361 902646 904365 
904381 904603 903016 904368 903457
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 903888
> tags 903888 + sid buster
Bug #903888 {Done: Thomas Goirand } [python3-trollius] 
python3-trollius: Python3 version of this library fails to install on sid
Added tag(s) sid and buster.
> severity 903888 serious
Bug #903888 {Done: Thomas Goirand } [python3-trollius] 
python3-trollius: Python3 version of this library fails to install on sid
Severity set to 'serious' from 'important'
> severity 904650 serious
Bug #904650 [python3-websockets] python3-websockets: fails to install with 
Python 3.7
Severity set to 'serious' from 'normal'
> tags 904648 + sid buster
Bug #904648 [python3-tweepy] python3-tweepy: fails to install with Python 3.7
Added tag(s) buster and sid.
> tags 904645 + sid buster
Bug #904645 [src:python-acora] python-acora: FTBFS with python 3.7: regenerate 
acora/_{,c}acora.c with newer cython
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#904571: marked as done (libhyperscan5 fails to install)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jul 2018 10:48:53 +
with message-id 
and subject line Bug#904571: fixed in hyperscan 5.0.0-3
has caused the Debian Bug report #904571,
regarding libhyperscan5 fails to install
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.)


-- 
904571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libhyperscan5
Version: 5.0.0-2
Severity: grave

Dear maintainer,

the transition from libhyperscan4 to libhyperscan5 does not work and
apt --fix-broken install results in:

Preparing to unpack .../libhyperscan5_5.0.0-2_amd64.deb ...
Unpacking libhyperscan5 (5.0.0-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/libhyperscan5_5.0.0-2_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libhs.so.5.0.0', which is also 
in package libhyperscan4 5.0.0-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libhyperscan5_5.0.0-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Best regards,
Marcus

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

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

Versions of packages libhyperscan5 depends on:
ii  debconf [debconf-2.0]  1.5.68
ii  libc6  2.27-5
ii  libgcc11:8.1.0-12
ii  libstdc++6 8.1.0-12

libhyperscan5 recommends no packages.

libhyperscan5 suggests no packages.
--- End Message ---
--- Begin Message ---
Source: hyperscan
Source-Version: 5.0.0-3

We believe that the bug you reported is fixed in the latest version of
hyperscan, 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.
Hilko Bengen  (supplier of updated hyperscan 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, 26 Jul 2018 12:21:35 +0200
Source: hyperscan
Binary: libhyperscan-dev libhyperscan5
Architecture: source
Version: 5.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Robert Haist 
Changed-By: Hilko Bengen 
Description:
 libhyperscan-dev - Development files for the Hyperscan library
 libhyperscan5 - High-performance regular expression matching library
Closes: 904571
Changes:
 hyperscan (5.0.0-3) unstable; urgency=medium
 .
   * Add Conflicts/Replaces so that the misnamed libhyperscan4 is removed
 on upgrades (Closes: #904571)
Checksums-Sha1:
 c4ba76d662cb001a85226d2104efea26d0e12c18 2225 hyperscan_5.0.0-3.dsc
 ea63da666148ffd222a55d2ea36a1f6a48625bf4 7580 hyperscan_5.0.0-3.debian.tar.xz
 f6e7ee5ba0494fd5b3a59feded39babb209c18a9 7102 
hyperscan_5.0.0-3_source.buildinfo
Checksums-Sha256:
 2fe7a1171ad9bb02448ec9a0b55d08727003c70dd0d1d793aa7241f5a40d1688 2225 
hyperscan_5.0.0-3.dsc
 feae5a3539928246e1dcfd8830c7d7d4370ece32eec050f34f1653790d529ac3 7580 
hyperscan_5.0.0-3.debian.tar.xz
 2ef45fa20b57ff1b09ede65123f23c6f0302b10f074daebec57b69786ed6f988 7102 
hyperscan_5.0.0-3_source.buildinfo
Files:
 d782946898cf1060900b8dc059c01015 2225 libs optional hyperscan_5.0.0-3.dsc
 7555d1106563a9f62ae23177c3114034 7580 libs optional 
hyperscan_5.0.0-3.debian.tar.xz
 c7225d7720e0245e1eadafca17735fdf 7102 libs optional 
hyperscan_5.0.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAltZoQQSHGJlbmdlbkBk
ZWJpYW4ub3JnAAoJEHW3EGNcITp+inYP/1ERmC1QeYMvJCGp1ITC6IYw+Zyxkhjl
V234o9eM6ZtBZMSHHZs1V1QfZnOQiVj9FJNqo26FArVzaqDIoszDtm+7ptFshrma
M5SfjaIIkt4D+9PoERqbcYg6k+dTiQCXhWHeQ5h2yd7+0dwaXoa7IRx8EdEximm1
DrQ9KBnIwqB86sG5Am74b1z6eRbzzNI8SQOxjb39X1AlNy5TgthIby9Ko+fAClHT
3MmwEyuo9emqJugiwBFpf1yolfg29MlHx9FFHU0v6UIoVkzt+EL/tvLonO8csU4A
fvWPjBzNXVS1POu52FtbKEx9x9E2ihOkIwXv2dsyr+VOxoacXMjnSRMKYilAnvV8

Bug#904661: vtk7 FTBFS due to uninstallable build dependencies

[Nicolas Braud-Santoni]

Source: vtk7
Version: 7.1.1+dfsg1-4
Severity: serious
Justification: FTBFS

While doing a rebuild of all reverse dependencies of json-c (as preparation
for transition #904418), I discovered that vtk7 fails to build due to a broken
build-dependency on python3-autobahn, independently of the upcoming json-c
transition.

Please find the complete sbuild log below.


Best,

  nicoo


> $ sbuild vtk7
> sbuild (Debian sbuild) 0.77.0 (06 July 2018) on localhost
> 
> +==+
> | vtk7 (amd64) Thu, 26 Jul 2018 10:30:30 
> + |
> +==+
> 
> Package: vtk7
> Distribution: unstable
> Machine Architecture: amd64
> Host Architecture: amd64
> Build Architecture: amd64
> Build Type: binary
> 
> I: NOTICE: Log filtering will replace 
> 'var/run/schroot/mount/sid-amd64-sbuild-12147a10-88bb-42b5-bf88-6963affcbbc3' 
> with '<>'
> I: NOTICE: Log filtering will replace 'build/vtk7-ktKPC8/resolver-4dtglN' 
> with '<>'
> 
> +--+
> | Update chroot   
>  |
> +--+
> 
> Get:1 file:/opt/deb/buildarea ./ InRelease
> Ign:1 file:/opt/deb/buildarea ./ InRelease
> Get:2 file:/opt/deb/buildarea ./ Release
> Ign:2 file:/opt/deb/buildarea ./ Release
> Get:3 file:/opt/deb/buildarea ./ Packages
> Ign:3 file:/opt/deb/buildarea ./ Packages
> Get:3 file:/opt/deb/buildarea ./ Packages
> Ign:3 file:/opt/deb/buildarea ./ Packages
> Get:3 file:/opt/deb/buildarea ./ Packages
> Ign:3 file:/opt/deb/buildarea ./ Packages
> Get:3 file:/opt/deb/buildarea ./ Packages
> Ign:3 file:/opt/deb/buildarea ./ Packages
> Get:3 file:/opt/deb/buildarea ./ Packages
> Ign:3 file:/opt/deb/buildarea ./ Packages
> Get:3 file:/opt/deb/buildarea ./ Packages
> Ign:3 file:/opt/deb/buildarea ./ Packages
> Get:3 file:/opt/deb/buildarea ./ Packages [154 kB]
> Get:4 http://localhost:3142/debian sid InRelease [233 kB]
> Get:5 http://localhost:3142/debian sid/main Sources [8618 kB]
> Get:6 http://localhost:3142/debian sid/main amd64 Packages.diff/Index [27.9 
> kB]
> Get:7 http://localhost:3142/debian sid/main amd64 Packages 
> 2018-07-24-0812.36.pdiff [30.1 kB]
> Get:8 http://localhost:3142/debian sid/main amd64 Packages 
> 2018-07-24-1408.05.pdiff [32.9 kB]
> Get:9 http://localhost:3142/debian sid/main amd64 Packages 
> 2018-07-24-2017.15.pdiff [16.2 kB]
> Get:10 http://localhost:3142/debian sid/main amd64 Packages 
> 2018-07-25-0207.37.pdiff [6068 B]
> Get:11 http://localhost:3142/debian sid/main amd64 Packages 
> 2018-07-25-0810.42.pdiff [14.0 kB]
> Get:12 http://localhost:3142/debian sid/main amd64 Packages 
> 2018-07-25-1418.46.pdiff [24.3 kB]
> Get:13 http://localhost:3142/debian sid/main amd64 Packages 
> 2018-07-25-2023.54.pdiff [42.3 kB]
> Get:14 http://localhost:3142/debian sid/main amd64 Packages 
> 2018-07-26-0211.09.pdiff [12.5 kB]
> Get:15 http://localhost:3142/debian sid/main amd64 Packages 
> 2018-07-26-0815.27.pdiff [12.7 kB]
> Get:15 http://localhost:3142/debian sid/main amd64 Packages 
> 2018-07-26-0815.27.pdiff [12.7 kB]
> Fetched 9070 kB in 13s (682 kB/s)
> Reading package lists...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Calculating upgrade...
> The following packages will be upgraded:
>   debconf libdebconfclient0 libexporter-tiny-perl lintian
> 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 1357 kB of archives.
> After this operation, 25.6 kB disk space will be freed.
> Get:1 http://localhost:3142/debian sid/main amd64 debconf all 1.5.69 [145 kB]
> Get:2 http://localhost:3142/debian sid/main amd64 libdebconfclient0 amd64 
> 0.244 [48.6 kB]
> Get:3 http://localhost:3142/debian sid/main amd64 libexporter-tiny-perl all 
> 1.002001-1 [36.9 kB]
> Get:4 http://localhost:3142/debian sid/main amd64 lintian all 2.5.94 [1127 kB]
> debconf: delaying package configuration, since apt-utils is not installed
> Fetched 1357 kB in 0s (12.6 MB/s)
> (Reading database ... 16363 files and directories currently installed.)
> Preparing to unpack .../debconf_1.5.69_all.deb ...
> Unpacking debconf (1.5.69) over (1.5.68) ...
> Setting up debconf (1.5.69) ...
> (Reading database ... 16348 files and directories currently installed.)
> Preparing to unpack .../libdebconfclient0_0.244_amd64.deb ...
> Unpacking libdebconfclient0:amd64 (0.244) over (0.243) ...
> Setting up libdebconfclient0:amd64 (0.244) ...
> (Reading database ... 16348 files and directories currently installed.)
> Preparing to unpack .../libexporter-tiny-perl_1.002001-1_all.deb ...
> Unpacking libexporter-tiny-perl (1.002001-1) over (1.00-2) ...
> Preparing to unpack .../lintian_2.5.94_all.deb ...
> Unpacking lintian (2.5.94) over (2.5.93) ...
> Setting up 

Bug#897716: marked as done (canu: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jul 2018 12:22:46 +0200
with message-id <20180726102246.fgbq245sgdn5p...@an3as.eu>
and subject line New upstream version builds nicely with gcc-8 thus closing
has caused the Debian Bug report #897716,
regarding canu: ftbfs with GCC-8
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.)


-- 
897716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:canu
Version: 1.7+dfsg-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/canu_1.7+dfsg-1_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-8/porting_to.html

[...]
make[2]: Leaving directory '/<>/canu-1.7+dfsg/src'
make[2]: Entering directory '/<>/canu-1.7+dfsg/src'
g++ -o 
/<>/canu-1.7+dfsg/Linux-amd64/obj/lib/libcanu.a/utgcns/libNDalign/NDalgorithm.o
 -c -MD -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>/canu-1.7+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -D_GLIBCXX_PARALLEL -pthread -fopenmp -fPIC 
-Wall -Wextra -Wno-write-strings -Wno-unused -Wno-char-subscripts 
-Wno-sign-compare -Wformat -g3 -O4 -funroll-loops -fexpensive-optimizations 
-finline-functions -fomit-frame-pointer -DNOBACKTRACE 
-I/<>/canu-1.7+dfsg/src -IAS_UTL -Istores -Istores/libsnappy 
-Ialignment -Iutgcns/libNDalign -Iutgcns/libcns -Iutgcns/libpbutgcns 
-Iutgcns/libNDFalcon -Iutgcns/libboost -Imeryl/libleaff -IoverlapInCore 
-IoverlapInCore/libedlib -IoverlapInCore/liboverlap -Ifalcon_sense/libfalcon 
utgcns/libNDalign/NDalgorithm.C
make[2]: Leaving directory '/<>/canu-1.7+dfsg/src'
make[2]: Entering directory '/<>/canu-1.7+dfsg/src'
g++ -o 
/<>/canu-1.7+dfsg/Linux-amd64/obj/lib/libcanu.a/utgcns/libNDalign/NDalgorithm-allocateMoreSpace.o
 -c -MD -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>/canu-1.7+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -D_GLIBCXX_PARALLEL -pthread -fopenmp -fPIC 
-Wall -Wextra -Wno-write-strings -Wno-unused -Wno-char-subscripts 
-Wno-sign-compare -Wformat -g3 -O4 -funroll-loops -fexpensive-optimizations 
-finline-functions -fomit-frame-pointer -DNOBACKTRACE 
-I/<>/canu-1.7+dfsg/src -IAS_UTL -Istores -Istores/libsnappy 
-Ialignment -Iutgcns/libNDalign -Iutgcns/libcns -Iutgcns/libpbutgcns 
-Iutgcns/libNDFalcon -Iutgcns/libboost -Imeryl/libleaff -IoverlapInCore 
-IoverlapInCore/libedlib -IoverlapInCore/liboverlap -Ifalcon_sense/libfalcon 
utgcns/libNDalign/NDalgorithm-allocateMoreSpace.C
make[2]: Leaving directory '/<>/canu-1.7+dfsg/src'
make[2]: Entering directory '/<>/canu-1.7+dfsg/src'
g++ -o 
/<>/canu-1.7+dfsg/Linux-amd64/obj/lib/libcanu.a/utgcns/libNDalign/NDalgorithm-extend.o
 -c -MD -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>/canu-1.7+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -D_GLIBCXX_PARALLEL -pthread -fopenmp -fPIC 
-Wall -Wextra -Wno-write-strings -Wno-unused -Wno-char-subscripts 
-Wno-sign-compare -Wformat -g3 -O4 -funroll-loops -fexpensive-optimizations 
-finline-functions -fomit-frame-pointer -DNOBACKTRACE 
-I/<>/canu-1.7+dfsg/src -IAS_UTL -Istores -Istores/libsnappy 
-Ialignment -Iutgcns/libNDalign -Iutgcns/libcns -Iutgcns/libpbutgcns 
-Iutgcns/libNDFalcon -Iutgcns/libboost -Imeryl/libleaff -IoverlapInCore 
-IoverlapInCore/libedlib -IoverlapInCore/liboverlap -Ifalcon_sense/libfalcon 
utgcns/libNDalign/NDalgorithm-extend.C
make[2]: Leaving directory '/<>/canu-1.7+dfsg/src'
make[2]: Entering directory '/<>/canu-1.7+dfsg/src'
g++ -o 
/<>/canu-1.7+dfsg/Linux-amd64/obj/lib/libcanu.a/utgcns/libNDalign/NDalign.o
 -c 

Bug#904657: voltron: fails to install with Python 3.7

[Andreas Beckmann]

Package: voltron
Version: 0.1.4-2
Severity: serious
Tags: sid buster
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...):

  Setting up voltron (0.1.4-2) ...
File "/usr/lib/python3/dist-packages/voltron/plugins/view/memory.py", line 
14
  async = True
^
  SyntaxError: invalid syntax
  
  dpkg: error processing package voltron (--configure):
   installed voltron package post-installation script subprocess returned error 
exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


voltron=0.1.4-2.log.gz
Description: application/gzip

Processed: voltron: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 903526 904581 902794 904298 904389 904351 904383 904381 
904361 904642 903388 903522 904654 904367 904656 902650 904358 904363 903525 
902766 904653 904370 904373 903558 904648 902757 902989 903218 904644 904382 
904649 902817 902715 903784 902646 904369 904491 904368 904615 904388 904576 
904603 904357 902900 903528 903826 902761 903145 904343 903529 904390 904579 
904587 903527 904650 903423 904492 904364 903016 903457 903030 904365 902631 
904350 903031 904371
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904657

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

Processed: visidata: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 903527 904369 903558 904615 904650 903457 904351 903784 
904388 904491 904390 904357 902766 903526 902646 903529 904370 904644 902757 
904648 904358 904381 903030 902715 904653 903525 903826 902989 902761 904368 
904389 904576 902631 904350 904363 903016 904343 904642 904382 904383 904581 
903388 903145 902817 902794 904361 904364 903423 903031 904654 904649 903218 
904492 904367 904371 904365 904603 903522 904373 902650 902900 904579 903528 
904298 904587
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904656

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

Bug#904656: visidata: fails to install with Python 3.7

[Andreas Beckmann]

Package: visidata
Version: 1.0-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...):

  Setting up visidata (1.0-1) ...
File "/usr/lib/python3/dist-packages/visidata/__init__.py", line 7
  from .async import *
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/visidata/canvas.py", line 519
  @async
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/visidata/cmdlog.py", line 286
  @async
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/visidata/data.py", line 226
  @async
   ^
  SyntaxError: invalid syntax
  
[...]
  
File "/usr/lib/python3/dist-packages/visidata/pivot.py", line 32
  @async
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/visidata/tidydata.py", line 15
  @async
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/visidata/vdtui.py", line 452
  def async(func):
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package visidata (--configure):
   installed visidata package post-installation script subprocess returned 
error exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


visidata=1.0-1.log.gz
Description: application/gzip

Bug#904655: python-line-profiler ftbfs with Python 3.7

[Matthias Klose]

Package: src:python-line-profiler
Version: 2.1-1
Severity: serious
Tags: sid buster

python-line-profiler ftbfs with Python 3.7:

= test session starts ==
platform linux -- Python 3.7.0+, pytest-3.6.2, py-1.5.3, pluggy-0.6.0
rootdir: /home/packages/tmp/python-line-profiler-2.1, inifile:
plugins: hypothesis-3.44.1, case-1.5.3
collected 8 items

tests/test_kernprof.py ...F  [ 50%]
tests/test_line_profiler.py ..F. [100%]

=== FAILURES ===
___ TestKernprof.test_gen_decorator 

args = (10,), kwds = {}, g = , item = 50
input = None

@functools.wraps(func)
def wrapper(*args, **kwds):
g = func(*args, **kwds)
# The first iterate will not be a .send()
self.enable_by_count()
try:
item = next(g)
finally:
self.disable_by_count()
input = (yield item)
# But any following one might be.
while True:
self.enable_by_count()
try:
>   item = g.send(input)
E   StopIteration

kernprof.py:104: StopIteration

The above exception was the direct cause of the following exception:

self = 

def test_gen_decorator(self):
profile = ContextualProfile()
g_wrapped = profile(g)
self.assertEqual(g_wrapped.__name__, g.__name__)
self.assertEqual(g_wrapped.__doc__, g.__doc__)

self.assertEqual(profile.enable_count, 0)
i = g_wrapped(10)
self.assertEqual(profile.enable_count, 0)
self.assertEqual(next(i), 20)
self.assertEqual(profile.enable_count, 0)
self.assertEqual(i.send(30), 50)
self.assertEqual(profile.enable_count, 0)
with self.assertRaises(StopIteration):
>   next(i)
E   RuntimeError: generator raised StopIteration

tests/test_kernprof.py:77: RuntimeError
_ TestLineProfiler.test_gen_decorator __

args = (10,), kwds = {}, g = , item = 50
input = None

@functools.wraps(func)
def wrapper(*args, **kwds):
g = func(*args, **kwds)
# The first iterate will not be a .send()
self.enable_by_count()
try:
item = next(g)
finally:
self.disable_by_count()
input = (yield item)
# But any following one might be.
while True:
self.enable_by_count()
try:
>   item = g.send(input)
E   StopIteration

line_profiler.py:102: StopIteration

The above exception was the direct cause of the following exception:

self = 

def test_gen_decorator(self):
profile = LineProfiler()
g_wrapped = profile(g)
self.assertEqual(g_wrapped.__name__, 'g')
timings = profile.code_map[g.__code__]

self.assertEqual(profile.enable_count, 0)
i = g_wrapped(10)
self.assertEqual(profile.enable_count, 0)
self.assertEqual(next(i), 20)
self.assertEqual(profile.enable_count, 0)
self.assertEqual(len(timings), 1)
self.assertEqual(i.send(30), 50)
self.assertEqual(profile.enable_count, 0)
self.assertEqual(len(timings), 2)
with self.assertRaises(StopIteration):
>   next(i)
E   RuntimeError: generator raised StopIteration

tests/test_line_profiler.py:94: RuntimeError
== 2 failed, 6 passed in 0.24 seconds ==

Processed: salt-common: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 903526 903525 904367 904357 904369 904653 904650 903388 
904350 902761 904343 903527 904298 904615 904363 903784 902900 904579 903558 
904649 904365 902757 904381 904389 903522 903145 904364 903218 902646 903528 
904351 903529 904370 904576 904361 904644 902715 904382 904648 904383 903031 
904368 904642 904388 904371 904373 903030 904390 902817 904603 904581 904587 
904358 903826 902989 903016 902631 902794 903423 902650 903457 904492 902766 
904491
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904654

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

Bug#904654: salt-common: fails to install with Python 3.7

[Andreas Beckmann]

Package: salt-common
Version: 2017.7.4+dfsg1-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...):

  Setting up salt-common (2017.7.4+dfsg1-1) ...
File "/usr/lib/python3/dist-packages/salt/client/mixins.py", line 495
  def async(self, fun, low, user='UNKNOWN', pub=None):
  ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/daemons/masterapi.py", line 1096
  return runner_client.async(fun,
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/master.py", line 1752
  return runner_client.async(fun,
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/minion.py", line 805
  self.io_loop.spawn_callback(self.process_manager.run, async=True)
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/modules/cassandra_cql.py", line 
340
  def cql_query_with_prepare(query, statement_name, statement_arguments, 
async=False,

 ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/modules/saltutil.py", line 909
  def refresh_modules(async=True):
  ^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/salt/returners/cassandra_cql_return.py", line 
208
  async=True)
  ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/runner.py", line 240
  async_pub = self.async(self.opts['fun'],
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/transport/client.py", line 13
  from salt.utils.async import SyncWrapper
  ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/transport/tcp.py", line 25
  import salt.utils.async
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/utils/async.py", line 60
  self.async = method(*args, **kwargs)
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/utils/event.py", line 76
  import salt.utils.async
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/utils/process.py", line 391
  def run(self, async=False):
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/wheel/__init__.py", line 119
  return self.async(fun, low)
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package salt-common (--configure):
   installed salt-common package post-installation script subprocess returned 
error exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


salt-common=2017.7.4+dfsg1-1.log.gz
Description: application/gzip

Processed: libmagick++-6.q16-7: requires rebuild against GCC 7 and symbols/shlibs bump

[Debian Bug Tracking System]

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

> found 871300 imagemagick/8:6.9.7.4+dfsg-16
Bug #871300 {Done: Bastien Roucariès } [src:imagemagick] 
libmagick++-6.q16-7: requires rebuild against GCC 7 and symbols/shlibs bump
Marked as found in versions imagemagick/8:6.9.7.4+dfsg-16 and reopened.
> fixed 871300 imagemagick/8:6.9.9.6+dfsg-1
Bug #871300 [src:imagemagick] libmagick++-6.q16-7: requires rebuild against GCC 
7 and symbols/shlibs bump
Marked as fixed in versions imagemagick/8:6.9.9.6+dfsg-1.
> thanks
Stopping processing here.

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

Bug#904653: python3-yowsup: fails to install with Python 3.7

[Andreas Beckmann]

Package: python3-yowsup
Version: 2.5.7-3
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...):

  Setting up python3-yowsup (2.5.7-3) ...
File "/usr/lib/python3/dist-packages/yowsup/demos/cli/layer.py", line 562
  successFn, self.onUploadError, self.onUploadProgress, async=False)
^
  SyntaxError: invalid syntax

File "/usr/lib/python3/dist-packages/yowsup/layers/interface/interface.py", 
line 128
  successFn, errorFn, progress, async=True)
^
  SyntaxError: invalid syntax

File 
"/usr/lib/python3/dist-packages/yowsup/layers/protocol_media/mediauploader.py", 
line 12
  def __init__(self, jid, accountJid, sourcePath, uploadUrl, resumeOffset = 
0, successClbk = None, errorClbk = None, progressCallback = None, async = True):

  ^
  SyntaxError: invalid syntax

  dpkg: error processing package python3-yowsup (--configure):
   installed python3-yowsup package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   python3-yowsup


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-yowsup=2.5.7-3.log.gz
Description: application/gzip

Processed: python3-yowsup: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 904649 903527 903526 904650 902631 902817 904371 903388 
904381 903522 904642 902650 902794 903218 904383 903145 903423 904388 903525 
902900 904358 903558 904615 904576 904491 903528 902646 903826 902766 904603 
904365 904298 904492 904382 904351 904587 902761 902989 904579 904390 904373 
903030 903031 904363 903016 904364 903529 903784 903457 904581 904350 904389 
904357 904648 904644 904367 904369 904368 902757 902715 904361 904343 904370
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904653

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

Bug#904652: pulseaudio: looses device and replace it with dummy package so no sound possible

[Meinolf Goedde]

Package: pulseaudio
Version: 12.0-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

i didn't do anything.
Upgrading the system like always.
Suddenly there was no sound available.

removing my .config/pulse and the /tmp/pulse-* followed by killing pulseaudio
and restarting it brings the sound back in rhythmbox but not in firefox.
The device is still not present in audio preferencces in gnome-control center.

After rebooting the same problem is back.



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages pulseaudio depends on:
ii  adduser  3.117
ii  libasound2   1.1.6-1
ii  libasound2-plugins   1.1.6-1+b1
ii  libc62.27-5
ii  libcap2  1:2.25-1.2
ii  libdbus-1-3  1.12.8-3
ii  libgcc1  1:8.1.0-12
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-2.1
ii  liborc-0.4-0 1:0.4.28-2
ii  libpulse012.0-1
ii  libsm6   2:1.2.2-1+b3
ii  libsndfile1  1.0.28-4
ii  libsoxr0 0.1.2-3
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   8.1.0-12
ii  libsystemd0  239-7
ii  libtdb1  1.3.15-4
ii  libudev1 239-7
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.5-1
ii  libx11-xcb1  2:1.6.5-1
ii  libxcb1  1.13-2
ii  libxtst6 2:1.2.3-1
ii  lsb-base 9.20170808
ii  pulseaudio-utils 12.0-1

Versions of packages pulseaudio recommends:
ii  dbus-user-session  1.12.8-3
ii  libpam-systemd 239-7
ii  rtkit  0.11-6

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  3.0-4
ii  pavumeter0.9.3-4+b3
ii  udev 239-7

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; 

Bug#871300: libmagick++-6.q16-7: requires rebuild against GCC 7 and symbols/shlibs bump

[Emilio Pozuelo Monfort]

found 871300 imagemagick/8:6.9.7.4+dfsg-16
fixed 871300 imagemagick/8:6.9.9.6+dfsg-1
thanks

Processed: python3-websockets: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 903784 902757 904358 904298 904390 902761 903529 904361 
902631 903457 904642 903558 904491 904648 902817 903423 903527 904383 902715 
904579 904373 904368 904576 904365 903016 904603 903388 904389 902794 903526 
902900 903031 904350 904644 904587 904357 903522 902646 903826 903218 904388 
902989 904351 904370 904382 904363 904364 904615 904581 904371 904381 903528 
904649 904343 904492 903030 902650 903145 904367 904369 903525 902766
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904650

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

Processed: libmagick++-6.q16-7: requires rebuild against GCC 7 and symbols/shlibs bump

[Debian Bug Tracking System]

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

> # the bts thinks this isnt fixed in unstable, probably because the package
> # is no longer built (shbump)
> reassign 871300 src:imagemagick
Bug #871300 {Done: Bastien Roucariès } [libmagick++-6.q16-7] 
libmagick++-6.q16-7: requires rebuild against GCC 7 and symbols/shlibs bump
Bug reassigned from package 'libmagick++-6.q16-7' to 'src:imagemagick'.
No longer marked as found in versions imagemagick/8:6.9.7.4+dfsg-16.
No longer marked as fixed in versions imagemagick/8:6.9.9.6+dfsg-1.
> thanks
Stopping processing here.

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

Bug#894475: marked as done (ntpsec-ntpviz: shares /var/log/ntpstats with ntp, which gets zapped when ntp is purged)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jul 2018 03:42:34 -0500
with message-id 
and subject line Re: ntpsec-ntpviz: shares /var/log/ntpstats with ntp, which 
gets zapped when ntp is purged
has caused the Debian Bug report #894475,
regarding ntpsec-ntpviz: shares /var/log/ntpstats with ntp, which gets zapped 
when ntp is purged
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.)


-- 
894475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ntpsec-ntpviz
Version: 1.0.0+dfsg1-5
Severity: serious

I installed the ntpsec suite, then purged the ntp packages.
Unfortunately, this zapped the /var/log/ntpstats directory, which is
needed by ntpsec-ntpviz.  There needs to either been some agreement
between ntp and ntpsec about the use of this directory, or ntpsec
needs to use a different log directory.

Best wishes,

   ulian

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

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

Versions of packages ntpsec-ntpviz depends on:
ii  adduser   3.117
ii  cron [cron-daemon]3.0pl1-130
ii  fonts-liberation  1:1.07.4-5
ii  gnuplot   5.2.2+dfsg1-2
ii  gnuplot-qt [gnuplot]  5.2.2+dfsg1-2
ii  python3   3.6.4-1
ii  python3-ntp   1.0.0+dfsg1-5
ii  systemd   238-2

Versions of packages ntpsec-ntpviz recommends:
ii  apache2 [httpd]  2.4.29-2
ii  ntpsec   1.0.0+dfsg1-5
ii  python3-psutil   5.4.2-1
ii  systemd  238-2

Versions of packages ntpsec-ntpviz suggests:
ii  python  2.7.14-4
pn  python-gps  

-- no debconf information
--- End Message ---
--- Begin Message ---
On 03/30/2018 05:31 PM, Richard Laager wrote:
> If this coordination is acceptable, I believe it solves the various
> interactions. I'm happy to test more scenarios if anyone thinks I missed
> something.
> 
> If this coordination is not acceptable, I'm open to alternative suggestions.

My current plan is to rename (on the ntpsec side) everything that
conflicts. I have a start on this, and it won't be too bad. There will
be a different set of trade-offs.

-- 
Richard--- End Message ---

Processed: python3-txfixtures: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 904357 903526 903031 904491 904365 902766 904492 903826 
903527 903218 904298 903016 902761 903457 904576 904603 904351 904615 904648 
903423 904383 903030 902817 904373 903522 904358 904642 904367 904369 902900 
903784 903528 904368 902631 904363 902989 903529 904350 904382 903145 903558 
904364 904370 902646 904361 902757 904381 904579 904371 904390 903525 904388 
902650 904389 904581 902794 904587 904343 904644 902715 903388
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904649

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

Bug#904649: python3-txfixtures: fails to install with Python 3.7

[Andreas Beckmann]

Package: python3-txfixtures
Version: 0.2.6-1
Severity: serious
Tags: sid buster
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...):

  Setting up python3-txfixtures (0.2.6-1) ...
File "/usr/lib/python3/dist-packages/txfixtures/_twisted/testing.py", line 
22
  self.async = False
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/txfixtures/tests/test_reactor.py", 
line 113
  self.reactor.async = True
   ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-txfixtures (--configure):
   installed python3-txfixtures package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   python3-txfixtures


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-txfixtures=0.2.6-1.log.gz
Description: application/gzip

Bug#872413: marked as done (kpatch: Please package new upstream version)

[Debian Bug Tracking System]

Your message dated Thu, 26 Jul 2018 08:46:13 +
with message-id 
and subject line Bug#872413: fixed in kpatch 0.6.0-0.1
has caused the Debian Bug report #872413,
regarding kpatch: Please package new upstream 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.)


-- 
872413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kpatch
Version: 0.3.2-3.1
Severity: normal
Tags: patch

Hello,

The version of kpatch in Sid is quite old and doesn't work with
the current kernel. Please consider updating to the latest
upstream version. However it seems that 0.4.0 (latest release) is
not recent enough, so consider using the latest Git version (e.g.
4b2f20e) which works fine me.

The attached patch performs the update to 0.4.0+git4b2f20e and
works fine here (Sid and Stretch). It also adds a few minor
changes to better suit current upstream:

- Upstream uses the kernel's LIVEPATCH per default and only falls
  back to its own kpatch.ko module if LIVEPATCH is not available.
  As LIVEPATCH is supported since Stretch, my patch removes the
  dependency on kpatch-dkms as kpatch works fine without it and
  users of older kernels can install it manully if necessary. Not
  depending on dkms (and thus a compiler) is a nice feature.
- Remove patches which are no longer required:
  create-diff-object-fix-WARN-_ONCE-detection-on-newer.patch
  kmod-core-use-save_stack_trace_tsk-backport.patch
- Update existing patches to apply.
- Add patch to fix uname -p (which always returns unknown on my
  systems); I think this should be upstreamed.
  fix-uname-p.patch
- Add patch to respect CPPFLAGS. Should be upstreamed as well.
  respect-cppflags.patch
- Updates post-dkms.sh which was failing for me. It builds and
  installs fine, but I didn't test it thoroughly and the comment
  from the other bug still applies I think. Maybe the -dkms part
  should be removed completely as upstream is switching to
  LIVEPATCH (and will drop kpatch.ko in the future).

Please also consider making a backport for Stretch (package can
be backported without any issues) as the kpatch version in
Stretch doesn't work with the kernel in Stretch making it rather
useless. The Git version works fine with the Stretch kernel.

Regards
Simon
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
diff -u -N -r kpatch-0.3.2/debian/control kpatch-0.4.0+git4b2f20e/debian/control
--- kpatch-0.3.2/debian/control 2016-06-27 21:03:09.0 +0200
+++ kpatch-0.4.0+git4b2f20e/debian/control  2017-08-14 12:07:25.497788719 
+0200
@@ -10,8 +10,7 @@
 
 Package: kpatch
 Architecture: linux-amd64
-Depends: ${shlibs:Depends}, ${misc:Depends}, kpatch-dkms,
- linux-headers-amd64 | linux-headers-generic
+Depends: ${shlibs:Depends}, ${misc:Depends}, binutils
 Description: Runtime tools for Kpatch
  kpatch is a Linux dynamic kernel patching tool which allows you to patch a
  running kernel without rebooting or restarting any processes.  It enables
@@ -22,7 +21,8 @@
 
 Package: kpatch-dkms
 Architecture: linux-amd64
-Depends: ${shlibs:Depends}, ${misc:Depends}, dkms
+Depends: ${shlibs:Depends}, ${misc:Depends}, dkms,
+ linux-headers-amd64 | linux-headers-generic
 Description: DKMS module for Kpatch
  This package contains the Kpatch module built with DKMS. It installs the 
source
  and makefiles into the appropriate locations in order to handle various kernel
diff -u -N -r kpatch-0.3.2/debian/patches/fix-uname-p.patch 
kpatch-0.4.0+git4b2f20e/debian/patches/fix-uname-p.patch
--- kpatch-0.3.2/debian/patches/fix-uname-p.patch   1970-01-01 
01:00:00.0 +0100
+++ kpatch-0.4.0+git4b2f20e/debian/patches/fix-uname-p.patch2017-08-12 
12:43:07.884688093 +0200
@@ -0,0 +1,18 @@
+Description: detect architecture properly
+ uname -p returns unknown for unknown reasons. uname -m seems to work
+Author: Simon Ruderich 
+Last-Update: 2017-08-11
+
+Index: kpatch-0.4.0.g4b2f20e/Makefile.inc
+===
+--- kpatch-0.4.0.g4b2f20e.orig/Makefile.inc
 kpatch-0.4.0.g4b2f20e/Makefile.inc
+@@ -3,7 +3,7 @@ CC= gcc
+ 
+ INSTALL = /usr/bin/install
+ 
+-ARCH   = $(shell uname -p)
++ARCH   = $(shell uname -m)
+ 
+ PREFIX?= /usr/local
+ LIBDIR?= lib
diff -u -N -r kpatch-0.3.2/debian/patches/kpatch-build-adjust-dirs.patch 
kpatch-0.4.0+git4b2f20e/debian/patches/kpatch-build-adjust-dirs.patch
--- kpatch-0.3.2/debian/patches/kpatch-build-adjust-dirs.patch  2016-02-18 
17:46:39.0 +0100
+++ 

Bug#893542: ntpsec-ntpviz: shares /var/log/ntpstats with ntp, which gets zapped when ntp is purged

[Richard Laager]

On 03/30/2018 05:31 PM, Richard Laager wrote:
> If this coordination is acceptable, I believe it solves the various
> interactions. I'm happy to test more scenarios if anyone thinks I missed
> something.
> 
> If this coordination is not acceptable, I'm open to alternative suggestions.

My current plan is to rename (on the ntpsec side) everything that
conflicts. I have a start on this, and it won't be too bad. There will
be a different set of trade-offs.

-- 
Richard

Processed: python3-tweepy: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 903526 904388 902766 904381 904642 902631 904382 903145 
903522 904491 904357 904361 902757 902794 904367 903031 903826 904615 902761 
902817 904587 904364 904368 903527 904351 903388 904350 903016 903218 904383 
904370 904363 903528 902646 902900 903457 904343 903030 904358 904644 902989 
904369 904579 904298 904390 902715 903558 903529 904581 904365 904389 904492 
904576 903525 904603 903423 904373 903784 902650 904371
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904648

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

Bug#904648: python3-tweepy: fails to install with Python 3.7

[Andreas Beckmann]

Package: python3-tweepy
Version: 3.5.0-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...):

  Setting up python3-tweepy (3.5.0-1) ...
File "/usr/lib/python3/dist-packages/tweepy/streaming.py", line 355
  def _start(self, async):
   ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-tweepy (--configure):
   installed python3-tweepy package post-installation script subprocess 
returned error exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-tweepy=3.5.0-1.log.gz
Description: application/gzip

Bug#904459: netdata: modifies conffiles (policy 10.7.3): /etc/netdata/health_alarm_notify.conf

[Andreas Beckmann]

On 2018-07-26 10:19, Daniel Baumann wrote:
> therefore, I see no (general) violation of policy 10.7.3 here and am
> inclined to (unless there are any implementation bugs that I haven't
> spottet) close the bug as such.

Shipping it as a conffile *and* managing it with debconf/ucf/... at the
same time is a violation, since dpkg will prompt for a modified conffile
once you ship a modified version of the conffile. Try adding a comment
to the file you ship, rebuild the package, install it, ouch.
(For ucf, the template should be in /usr/share, not /etc ...)


Andreas

Bug#904646: python-hypothesis fails imports with Python 3.7

[Matthias Klose]

Package: src:python-hypothesis
Version: 3.44.1-2
Severity: serious
Tags: sid buster

typing.GenericMeta doesn't exist anymore in 3.7

= test session starts ==
platform linux -- Python 3.7.0+, pytest-3.6.2, py-1.5.3, pluggy-0.6.0
rootdir: /tmp/autopkgtest-lxc.ow4u414h/downtmp/build.PPF/src/tests, inifile:
/dev/null
plugins: hypothesis-3.44.1, flaky-3.3.0
collected 2070 items / 1 errors

 ERRORS 
_ ERROR collecting py3/test_lookup.py __
tests/py3/test_lookup.py:38: in 
if isinstance(t, typing.GenericMeta)), key=str)
tests/py3/test_lookup.py:38: in 
if isinstance(t, typing.GenericMeta)), key=str)
E   AttributeError: module 'typing' has no attribute 'GenericMeta'
===Flaky Test Report===


===End Flaky Test Report===

Bug#904645: python-acora: FTBFS with python 3.7: regenerate acora/_{,c}acora.c with newer cython

[Emilio Pozuelo Monfort]

Source: python-acora
Version: 2.0-2
Severity: serious

Hi,

acora/_{,c}acora.c are prebuilt and dist in the python-acora tarball. They
were built with a too old cython and are now incompatible with Python 3.7,
and thus need to be rebuilt. It would be best to stop shipping those files
in the tarball and just build-dep on cython and generate them at build time.

Cheers,
Emilio

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Bug#904644: python3-slixmpp: fails to install with Python 3.7

[Andreas Beckmann]

Package: python3-slixmpp
Version: 1.3.0+git20180331-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...):

  Setting up python3-slixmpp (1.3.0+git20180331-1) ...
File "/usr/lib/python3/dist-packages/slixmpp/plugins/xep_0009/remote.py", 
line 423
  def async(self, callback):
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-slixmpp (--configure):
   installed python3-slixmpp package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   python3-slixmpp


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-slixmpp=1.3.0+git20180331-1.log.gz
Description: application/gzip

Processed: python3-slixmpp: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 904350 903784 904642 902900 904357 902646 904492 904579 
904383 904373 903457 902631 904388 903145 904370 902794 902715 904369 902757 
903525 903528 904368 904603 903388 903527 904365 904389 904615 904371 904361 
904390 902817 904382 903529 903423 904298 904491 903526 903030 904381 903522 
904351 904364 902989 904358 904576 904363 903031 904367 904343 902761 904581 
903826 903218 904587 903558 902766 902650 903016
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904644

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

Bug#888366: qtwebengine-opensource-src: FTBFS with FFmpeg 4.0

[Sebastian Ramacher]

Control: found -1 5.11.1+dfsg-3

On 2018-06-15 20:45:42, James Cowgill wrote:
> Hi,
> 
> On Wed, 24 Jan 2018 22:26:50 + jcowg...@debian.org wrote:
> > Source: qtwebengine-opensource-src
> > Version: 5.9.2+dfsg-2
> > Severity: important
> > User: debian-multime...@lists.debian.org
> > Usertags: ffmpeg-3.5-transition
> > 
> > Hi,
> > 
> > Your package FTBFS with the upcoming version 3.5 of FFmpeg.
> 
> qtwebengine 5.11 almost fixes this. The only thing left is this chromium
> commit needs cherry-picking:
> https://github.com/chromium/chromium/commit/a568ded46a678eac8139cb06595819c5ae874177

Looks like this commit was not included in the last upload to unstable. It
now FTBFS with:

../../3rdparty/chromium/media/ffmpeg/ffmpeg_common.cc:36:43: error: static 
assertion failed: DecoderBuffer padding size does not fit ffmpeg requirement
 static_assert(DecoderBuffer::kPaddingSize >= AV_INPUT_BUFFER_PADDING_SIZE,
   ^

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: Re: Bug#888366: qtwebengine-opensource-src: FTBFS with FFmpeg 4.0

[Debian Bug Tracking System]

Processing control commands:

> found -1 5.11.1+dfsg-3
Bug #888366 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS 
with FFmpeg 4.0
The source 'qtwebengine-opensource-src' and version '5.11.1+dfsg-3' do not 
appear to match any binary packages
Marked as found in versions qtwebengine-opensource-src/5.11.1+dfsg-3.

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

Processed: Re: netdata: modifies conffiles (policy 10.7.3): /etc/netdata/health_alarm_notify.conf

[Debian Bug Tracking System]

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

> tag 904459 + moreinfo
Bug #904459 [netdata] netdata: modifies conffiles (policy 10.7.3): 
/etc/netdata/health_alarm_notify.conf
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#904459: netdata: modifies conffiles (policy 10.7.3): /etc/netdata/health_alarm_notify.conf

[Daniel Baumann]

tag 904459 + moreinfo
thanks

Hi Andreas,

thank you taking the time to report this bug.

While I fully agree with policy 10.7.3, I don't think policy means this
in the case of using debconf to modify configuration files. Let me
explain why..

  * imho policy 10.7.3 means that that no unsupervised
changing of conffiles should happen with the aim,
that any changes to a conffile needs to be approved by the
admin/user, so no silent changes can sneek in/be overwritten.

  * netdata uses debconf to ask the user a setting to make the
configuration more suitable for the users use case.

this happens in, depending on the debconf priority/frontend,
an interactive or non-interactive way.

  * regardless of it being interactive or not, the way debconf is
used in netdata preserves local modifications in the conffile
and is idempotent.

  * imho there is no difference in principle wrt/ 10.7.3 between e.g.
using ucf to handle a configuration update, or use debconf to
change settings like it is done in netdata.

and using ucf clearly is no policy 10.7.3 violation, right?

therefore, I see no (general) violation of policy 10.7.3 here and am
inclined to (unless there are any implementation bugs that I haven't
spottet) close the bug as such.

What do you think?

Regards,
Daniel

Processed: python3-signaller: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 902989 904351 904373 903388 903145 904492 904371 904358 
904365 903528 904388 904363 903016 904603 904389 904369 904576 903526 904367 
904298 903826 902715 904381 904370 904368 903522 904357 904615 902650 904390 
902766 904579 902817 904491 902646 904343 903423 904581 902794 903527 903558 
904587 904364 902631 904350 903031 903529 903784 902900 903525 904361 904382 
903457 904383 903218 902757 903030 902761
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 904642

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

Bug#904642: python3-signaller: fails to install with Python 3.7

[Andreas Beckmann]

Package: python3-signaller
Version: 1.1.0-1
Severity: serious
Tags: sid buster
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...):

  Setting up python3-signaller (1.1.0-1) ...
File "/usr/lib/python3/dist-packages/signaller.py", line 110
  asyncio.async(ref(*args, **kwargs), loop=self.loop)
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-signaller (--configure):
   installed python3-signaller package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   python3-signaller


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-signaller=1.1.0-1.log.gz
Description: application/gzip

Bug#900533: chromium 67.0.3396.62-1: youtube video, gif's, html5, and movies no longer work

[Askar Safin]

Package: chromium
Version: 67.0.3396.87-1~deb9u1
Followup-For: Bug #900533

My system is Debian Stretch amd64. My sources.list is this:
===
deb http://mirror.yandex.ru/debian stretch main non-free contrib
deb-src http://mirror.yandex.ru/debian stretch main non-free contrib

deb http://security.debian.org/debian-security stretch/updates main contrib 
non-free
deb-src http://security.debian.org/debian-security stretch/updates main contrib 
non-free

deb http://mirror.yandex.ru/debian stretch-updates main contrib non-free
deb-src http://mirror.yandex.ru/debian stretch-updates main contrib non-free

deb http://mirror.yandex.ru/debian stretch-backports main
deb-src http://mirror.yandex.ru/debian stretch-backports main
===

The bug still exists in latest version in stable security repo 
67.0.3396.87-1~deb9u1 as of today (2018-07-26 UTC+03).

Steps to reproduce. Log in to https://vk.com , then go to https://vk.com/audio 
. You will not be able to listen any audio.

There is no bug in latest version in stable repo 63.0.3239.84-1~deb9u1 as of 
today. So, this is clear regression,
introduced by security update.

That daily motion link doesn't work in stable security, too (note: daily motion 
is banned in Russia).

https://hpr.dogphilosophy.net/test/ doesn't work, too.

-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-0.bpo.2-amd64 (SMP w/8 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages chromium depends on:
ii  libasound2   1.1.3-5
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 7:3.2.11-1~deb9u1
ii  libavformat577:3.2.11-1~deb9u1
ii  libavutil55  7:3.2.11-1~deb9u1
ii  libc62.24-11+deb9u3
ii  libcairo21.14.8-1
ii  libcups2 2.2.1-8+deb9u2
ii  libdbus-1-3  1.10.26-0+deb9u1
ii  libevent-2.0-5   2.0.21-stable-3
ii  libexpat12.2.0-2+deb9u1
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u2
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libicu57 57.1-6+deb9u2
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26.2-1.1+deb9u1
ii  libopus0 1.2~alpha2-1
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpng16-16  1.6.28-1
ii  libpulse010.0-1+deb9u1
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.3-3
ii  libstdc++6   6.3.0-18+deb9u1
ii  libvpx4  1.6.1-3+deb9u1
ii  libwebp6 0.5.2-1
ii  libwebpdemux20.5.2-1
ii  libwebpmux2  0.5.2-1
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.14-1+deb9u1
ii  libxdamage1  1:1.1.4-2+b3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-2.2+deb9u2
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-2.1
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.3-1
ii  x11-utils7.7+3+b1
ii  xdg-utils1.1.1-1+deb9u1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2
ii  libgl1-mesa-dri   13.0.6-1+b2

Versions of packages chromium suggests:
pn  chromium-driver
pn  chromium-l10n  
pn  chromium-shell 
pn  chromium-widevine  

-- no debconf information

Bug#904635: paramiko requires pytest << 3.6, and autopkg tests require pytest

[Matthias Klose]

Package: src:paramiko
Version: 2.4.0-1
Severity: serious
Tags: sid buster patch

According to
https://bugzilla.redhat.com/show_bug.cgi?id=1594896
paramiko needs an update for pytest 3.6.

Also the debian autopkg tests need an update to use pytest. patch at
http://launchpadlibrarian.net/380090902/paramiko_2.4.0-1_2.4.0-1ubuntu1.diff.gz

Bug#904630: python-kubernetes needs an update for Python 3.7

[Matthias Klose]

Package: src:python-kubernetes
Version: 7.0.0~a1-1
Severity: serious
Tags: sid buster

According to the Debian changelog, this needs an update ...

Setting up python3-kubernetes (4.0.0-2) ...
  File "/usr/lib/python3/dist-packages/kubernetes/client/api_client.py", line 
281
response_type=None, auth_settings=None, async=None,
^
SyntaxError: invalid syntax

  File
"/usr/lib/python3/dist-packages/kubernetes/client/apis/admissionregistration_api.py",
line 120
async=params.get('async'),
^
SyntaxError: invalid syntax

  File
"/usr/lib/python3/dist-packages/kubernetes/client/apis/admissionregistration_v1alpha1_api.py",
line 132
async=params.get('async'),
^
SyntaxError: invalid syntax