Processed: closing 898444

[Debian Bug Tracking System]

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

> close 898444 1:10.1.34-1
Bug #898444 [src:mariadb-10.1] mariadb-10.1: CVE-2018-2562 CVE-2018-2622 
CVE-2018-2640 CVE-2018-2665 CVE-2018-2668 CVE-2018-2612 (fixed in 10.1.31)
The source 'mariadb-10.1' and version '1:10.1.34-1' do not appear to match any 
binary packages
Marked as fixed in versions mariadb-10.1/1:10.1.34-1.
Bug #898444 [src:mariadb-10.1] mariadb-10.1: CVE-2018-2562 CVE-2018-2622 
CVE-2018-2640 CVE-2018-2665 CVE-2018-2668 CVE-2018-2612 (fixed in 10.1.31)
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 898445

[Debian Bug Tracking System]

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

> close 898445 1:10.1.34-1
Bug #898445 [src:mariadb-10.1] mariadb-10.1: CVE-2018-2782 CVE-2018-2784 
CVE-2018-2787 CVE-2018-2766 CVE-2018-2755 CVE-2018-2819 CVE-2018-2817 
CVE-2018-2761 CVE-2018-2781 CVE-2018-2771 CVE-2018-2813 (fixed in 10.1.33)
The source 'mariadb-10.1' and version '1:10.1.34-1' do not appear to match any 
binary packages
Marked as fixed in versions mariadb-10.1/1:10.1.34-1.
Bug #898445 [src:mariadb-10.1] mariadb-10.1: CVE-2018-2782 CVE-2018-2784 
CVE-2018-2787 CVE-2018-2766 CVE-2018-2755 CVE-2018-2819 CVE-2018-2817 
CVE-2018-2761 CVE-2018-2781 CVE-2018-2771 CVE-2018-2813 (fixed in 10.1.33)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#898445: closing 898445

[Salvatore Bonaccorso]

close 898445 1:10.1.34-1
thanks

Bug#902762:

[Matthias Klose]

Control: tags -1 + patch

issues are fixed in 0.11 plus one pending upstream fix to relax test results on
i386.

See https://launchpad.net/ubuntu/+source/py-ubjson/0.11.0-0ubuntu2

Processed: Re:

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #902762 [src:py-ubjson] py-ubjson FTBFS with Python 3.7: NameError: name 
'TYPE_INT8' is not defined
Bug #904661 [src:py-ubjson] vtk7 FTBFS due to uninstallable build dependencies
Added tag(s) patch.
Added tag(s) patch.

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

Bug#905163: marked as done (lftp: CVE-2018-10916: Exploit in reverse mirror job deletes cwd on source)

[Debian Bug Tracking System]

Your message dated Thu, 02 Aug 2018 04:49:22 +
with message-id 
and subject line Bug#905163: fixed in lftp 4.8.4-1
has caused the Debian Bug report #905163,
regarding lftp: CVE-2018-10916: Exploit in reverse mirror job deletes cwd on 
source
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.)


-- 
905163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905163
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lftp
Version: 4.8.3-1
Severity: grave
Tags: patch security upstream
Forwarded: https://github.com/lavv17/lftp/issues/452

Hi,

The following vulnerability was published for lftp, were in cse revers
mirror option is used can lead on data loss on source.

CVE-2018-10916[0]:
Exploit in reverse mirror job deletes cwd on source

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-10916
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10916
[1] https://github.com/lavv17/lftp/issues/452
[2] 
https://github.com/lavv17/lftp/commit/a27e07d90a4608ceaf928b1babb27d4d803e1992

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: lftp
Source-Version: 4.8.4-1

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

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

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

Debian distribution maintenance software
pp.
Noël Köthe  (supplier of updated lftp 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, 02 Aug 2018 05:47:42 +0200
Source: lftp
Binary: lftp
Architecture: source amd64
Version: 4.8.4-1
Distribution: unstable
Urgency: high
Maintainer: Noël Köthe 
Changed-By: Noël Köthe 
Description:
 lftp   - Sophisticated command-line FTP/HTTP/BitTorrent client programs
Closes: 905163
Changes:
 lftp (4.8.4-1) unstable; urgency=high
 .
   * New upstream version 4.8.4 fixes CVE-2018-10916 closes: Bug#905163
   * updated Standards-Version; no changes needed
   * switched to debhelper 11
   * fix lintian warning about trailing whitespaces
   * updated signing key from Alexander V. Lukyanov 
Checksums-Sha1:
 2da3957370852fe96bc6dd87ed135351e18b7968 1992 lftp_4.8.4-1.dsc
 fa97429d4376c87dd0b6a9b27ed89184fb2a9149 1633444 lftp_4.8.4.orig.tar.xz
 bf814cfba676c0334c3f7d7280fa218806690b12 155 lftp_4.8.4.orig.tar.xz.asc
 005127b3897625ec3e815ea5e333b1a558ec1b97 21400 lftp_4.8.4-1.debian.tar.xz
 d3549fbb7491c9711d7eb72cc87d8bfed66797c7 3399668 lftp-dbgsym_4.8.4-1_amd64.deb
 73aa5f1dd78262e0ffab7fa2609ab78812783411 7000 lftp_4.8.4-1_amd64.buildinfo
 d9402d5c85e6c49745a93f1e1cb1d58751d2281d 723952 lftp_4.8.4-1_amd64.deb
Checksums-Sha256:
 3d22a0a4856c85f94419250694408dde6613bb9a5da656a6cb340e06e0b6e40e 1992 
lftp_4.8.4-1.dsc
 4ebc271e9e5cea84a683375a0f7e91086e5dac90c5d51bb3f169f75386107a62 1633444 
lftp_4.8.4.orig.tar.xz
 851013e7f5768083512e20236748f6c40db3583f922ef99c6cd5cd4eb4d991e5 155 
lftp_4.8.4.orig.tar.xz.asc
 999238c6d75d66f9cfafdd84b636bbd65870917687caecff4c1ad5161769303f 21400 
lftp_4.8.4-1.debian.tar.xz
 80a9ad76141c845710efb81fd6c2e322a1e11148aa655e2ad8aec27d7752d2fe 3399668 
lftp-dbgsym_4.8.4-1_amd64.deb
 36a9d492cf77d57556f32132545d2986e5438125eeec85f35a67d35f741c9821 7000 
lftp_4.8.4-1_amd64.buildinfo
 e3c275a343bd0c26391022a91eac317979cd2174f3486a6cfbdea28ae1f2b86a 723952 
lftp_4.8.4-1_amd64.deb
Files:
 a9f58bec5e5aec16e29d3f5a3ed79ab6 1992 net optional lftp_4.8.4-1.dsc
 b75c43797e817529d486be640232d708 1633444 net optional lftp_4.8.4.orig.tar.xz
 f9118a67f41c6f7e93a13be1c5051b6a 155 net optional lftp_4.8.4.orig.tar.xz.asc
 80cd6e23b68f23ea124016b86c0ef00a 21400 net optional lftp_4.8.4-1.debian.tar.xz
 54d868364c30aef0668ba299c872a8df 3399668 debug optional 
lftp-dbgsym_4.8.4-1_amd64.deb
 e6d9f28950d53a02c243f2449c8f42b6 7000 net optional lftp_4.8.4-1_amd64.buildinfo
 2d6f2ff576ca92a8b07d83e38da7f783 723952 net optional lftp_4.8.4-1_amd64.deb

-BEGIN PGP SIGNATURE-

Bug#905207: marked as done (fabio-viewer,python-fabio: both ship usr/share/doc/python-fabio-doc/html/_static/mathjax)

[Debian Bug Tracking System]

Your message dated Thu, 02 Aug 2018 04:34:14 +
with message-id 
and subject line Bug#905207: fixed in python-fabio 0.7.0+dfsg-2
has caused the Debian Bug report #905207,
regarding fabio-viewer,python-fabio: both ship 
usr/share/doc/python-fabio-doc/html/_static/mathjax
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.)


-- 
905207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fabio-viewer,python-fabio
Version: 0.7.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package python-fabio.
  Preparing to unpack .../18-python-fabio_0.7.0+dfsg-1_amd64.deb ...
  Unpacking python-fabio (0.7.0+dfsg-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-YgDMUP/18-python-fabio_0.7.0+dfsg-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/doc/python-fabio-doc/html/_static/mathjax', 
which is also in package fabio-viewer 0.7.0+dfsg-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-YgDMUP/18-python-fabio_0.7.0+dfsg-1_amd64.deb


cheers,

Andreas


fabio-viewer=0.7.0+dfsg-1_python-fabio=0.7.0+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-fabio
Source-Version: 0.7.0+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated python-fabio 
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: Wed, 01 Aug 2018 23:37:51 +0200
Source: python-fabio
Binary: fabio-viewer python-fabio python-fabio-dbg python3-fabio 
python3-fabio-dbg python-fabio-doc
Architecture: source
Version: 0.7.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Description:
 fabio-viewer - Viewer for images produced by 2D X-ray detector
 python-fabio - I/O library for images produced by 2D X-ray detector - Python2
 python-fabio-dbg - I/O library for images produced by 2D X-ray detector - 
Python2 de
 python-fabio-doc - I/O library for images produced by 2D X-ray detector - 
documentat
 python3-fabio - I/O library for images produced by 2D X-ray detector - Python3
 python3-fabio-dbg - I/O library for images produced by 2D X-ray detector - 
Python3 de
Closes: 905207
Changes:
 python-fabio (0.7.0+dfsg-2) unstable; urgency=medium
 .
   * d/rules
 - Installed the mathjax link only in the python-fabio-doc packages
 (Closes: #905207)
Checksums-Sha1:
 c38ec665f2e93d2fd8c79f9f3cdde9e374e371e4 3401 python-fabio_0.7.0+dfsg-2.dsc
 a8b98b6be0bbf0df0123c4a131bc5a07a2c0660d 7880 
python-fabio_0.7.0+dfsg-2.debian.tar.xz
Checksums-Sha256:
 f2e4cbd6519b23ccd4ef42a2c6f6fa15e32a7e2a88f87750ca4e5a89f96b972e 3401 
python-fabio_0.7.0+dfsg-2.dsc
 3ce9b280605e67fdc0e3baf69c183c5f902c6a3522188074dfed61a4d7665312 7880 
python-fabio_0.7.0+dfsg-2.debian.tar.xz
Files:
 f5234d0864b6adc3d287cd9fd556a01d 3401 science optional 
python-fabio_0.7.0+dfsg-2.dsc
 9caaa8164f5283e0c093a73cb1826869 7880 science optional 
python-fabio_0.7.0+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAltiheIRHHBpY2NhQGRl
Ymlhbi5vcmcACgkQW/VOXhK5ALukmA/8C3lwfjk7B4WmZo6Az2LAjxBSU0mD8eFa
YM692CnNFwd4wQQ2LeyaxGmsiJRgwItT0Y/62bb/KIV491m7593w0dzJSplGxDGP
XorL+Z3iJG+YeUW8qUXUxh5Cp9/3dYXaAsa9Ej15fBfzuCmqKU5lBMlymKr5WlAv
2RM9PYqR4r+s4VbmYEn/6sVMiPij6tOPWOYeNnvFz3EoJPEed7q/5+BV9XuGyS6s
OUSNhu0PomUupJ+Z4mrcGyULG1jXfsXIG9Vm0vfHiUGpJHWl3I+c5hLw1OJMuhg3
hm8BaFiSRTtWcenDwjUfOaVzEIQ5VDE4eJqJpkaMbItcQBHd4mrVRQ3TlNxZscKj
KEXR71xdIOSp8bmdjWvhvFJ2u60+HsV/j5g+yuwmWhmO5YRsmHI6WwM21nU7+bWf
Z/EKF/tvsiGCDdjKGr90+fguzXMg++Q5BjmN/E1Sr72o4pOR7/xq/YqPxZfkYibd
CAN7oMojlOsUUPlf2fq+yLOTk3FGHkcJY0yNUIzRgvqIIDGhRIr5a1RevUrINGkS

Bug#904853: marked as done (casacore ftbfs in unstable)

[Debian Bug Tracking System]

Your message dated Thu, 02 Aug 2018 04:04:50 +
with message-id 
and subject line Bug#904853: fixed in casacore 2.4.1-2
has caused the Debian Bug report #904853,
regarding casacore ftbfs in unstable
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.)


-- 
904853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:casacore
Version: 2.4.1-1
Severity: serious
Tags: sid buster

casacore ftbfs in unstable:

Start 460: tConvert
460/460 Test #460: tConvert .***Failed0.21 sec
187c187
< [45. 46.]
---
> [ 45.  46.]
191c191
< [45.]
---
> [ 45.]
193c193
< [45. 46.]
---
> [ 45.  46.]
309c309
< [1.3 4.  5.  6. ]
---
> [ 1.3  4.   5.   6. ]
311c311
< [10.-11.j  1. +2.j]
---
> [ 10.-11.j   1. +2.j]
323c323
< [10.-11.j  1. +2.j]
---
> [ 10.-11.j   1. +2.j]
332c332
< [3. 5. 7. 9.]
---
> [ 3.  5.  7.  9.]
334c334
< [3. 5. 7. 9.]
---
> [ 3.  5.  7.  9.]
336c336
< [3. 5. 7. 9.]
---
> [ 3.  5.  7.  9.]
338c338
< [20.+10.j]
---
> [ 20.+10.j]
340c340
< [21.]
---
> [ 21.]
346c346
< [2, 1.3, array([ True, False])]
---
> [2, 1.3, array([ True, False], dtype=bool)]
FAIL (output not verified): ./tConvert


99% tests passed, 1 tests failed out of 460

Total Test time (real) = 105.75 sec

The following tests FAILED:
460 - tConvert (Failed)
Errors while running CTest
make[2]: *** [Makefile:144: test] Error 8
--- End Message ---
--- Begin Message ---
Source: casacore
Source-Version: 2.4.1-2

We believe that the bug you reported is fixed in the latest version of
casacore, 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.
Ole Streicher  (supplier of updated casacore 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, 02 Aug 2018 10:56:27 +0800
Source: casacore
Binary: casacore-dev casacore-doc casacore-tools libcasa-casa2 libcasa-scimath2 
libcasa-scimath-f2 libcasa-python2 libcasa-python3-2 libcasa-tables2 
libcasa-measures2 libcasa-lattices2 libcasa-fits2 libcasa-ms2 
libcasa-derivedmscal2 libcasa-msfits2 libcasa-coordinates2 libcasa-images2 
libcasa-meas2 libcasa-mirlib2
Architecture: source
Version: 2.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Description:
 casacore-dev - CASA core library development files
 casacore-doc - CASA core library (documentation)
 casacore-tools - Tools built with CASA
 libcasa-casa2 - CASA core modules
 libcasa-coordinates2 - CASA coordinates library
 libcasa-derivedmscal2 - CASA derived mscal library
 libcasa-fits2 - CASA FITS library
 libcasa-images2 - CASA image processing library
 libcasa-lattices2 - CASA lattice library
 libcasa-meas2 - CASA functions handling measures
 libcasa-measures2 - CASA measures library
 libcasa-mirlib2 - CASA mirlib library
 libcasa-ms2 - CASA MeasurementSet library
 libcasa-msfits2 - CASA msfits library
 libcasa-python2 - CASA Python bindings
 libcasa-python3-2 - CASA Python bindings
 libcasa-scimath-f2 - CASA scimath F library
 libcasa-scimath2 - CASA basic mathematical modules
 libcasa-tables2 - CASA table system
Closes: 904853
Changes:
 casacore (2.4.1-2) unstable; urgency=medium
 .
   * Update VCS fields to use salsa.d.o
   * Removed unused manpage of showtable (1)
   * Keep numpy 1.13 printoption for numpy 1.14 or above (Closes: #904853)
   * Push Standards-Version to 4.1.5. No changes needed.
   * Push compat to 11
Checksums-Sha1:
 be52f6c7060e8497f727bf44670727e4a1ff1bdd 3317 casacore_2.4.1-2.dsc
 4e875def3c2bd5803811361dd55d4d0d91b418d6 22696 casacore_2.4.1-2.debian.tar.xz
Checksums-Sha256:
 737d06961c9d2e2fcc72c68aabffe5c3b0bb7ee9ff1898cf63173f258b8ca728 3317 
casacore_2.4.1-2.dsc
 66bf9381edd13cb65b68ad3293567d4182095841c5d8274e452d6d90dd309c06 22696 
casacore_2.4.1-2.debian.tar.xz
Files:
 ffc92391a8f279ffb764395df162f167 3317 science optional casacore_2.4.1-2.dsc
 3a3486501ec617b49d75c504c4d0da0e 22696 science optional 
casacore_2.4.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

Processed: tagging 902467

[Debian Bug Tracking System]

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

> tags 902467 - fixed-upstream
Bug #902467 [src:golang-github-kardianos-osext] golang-github-kardianos-osext: 
FTBFS in buster/sid (failing tests)
Removed tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#905124: Acknowledgement (abcde: Can't use an undefined value as an ARRAY reference at /usr/bin/abcde-musicbrainz-tool line 98)

[Steve McIntyre]

On Wed, Aug 01, 2018 at 06:03:50PM +0200, Helge Kreutzmann wrote:
>Hello Maintainer(s),
>I read in #892480 (which seems a similar issue) that you need the
>output of abcde with "-D" added.
>
>I attached it to this e-mail.

ACK, thanks. There's an upstream fix for this already and I just need
to roll out a new release. Coming very soon - I'm at DebConf at the
moment so time is tight for the next few days.

See https://git.einval.com/cgi-bin/gitweb.cgi?p=abcde.git
for the latest code if you're interested.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Google-bait:   http://www.debian.org/CD/free-linux-cd
  Debian does NOT ship free CDs. Please do NOT contact the mailing
  lists asking us to send them to you.

Bug#905165: debootstrap - fails in docker environment

[Hideki Yamane]

On Wed, 1 Aug 2018 07:55:07 +0200
Bastian Blank  wrote:
> Package: debootstrap
> Version: 1.0.106
> Severity: grave
> 
> debootstrap fails in docker environment completely by:

 Could you try 1.0.107 in git repo, please?
 I was in trouble with uploading it, but it would be better one.

 And if it still happens, please describe reproduce step for it.

-- 
Hideki Yamane 

Bug#904954: marked as done (emacs: uninstallable in sid)

[Debian Bug Tracking System]

Your message dated Thu, 02 Aug 2018 09:39:08 +0900
with message-id <74165d49088802dfe79bffe95cb43...@debian.org>
and subject line Re: emacs: uninstallable in sid
has caused the Debian Bug report #904954,
regarding emacs: uninstallable in sid
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.)


-- 
904954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs
Version: 1:25.2+1-8
Severity: serious
Justification: uninstallable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Rob;

emacs depends transitively on emacsen-common >= 3.0.0, which is
unavailable in sid, afaict.


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

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

Versions of packages emacs depends on:
ii  emacs-gtk  1:25.2+1-7

emacs recommends no packages.

emacs suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAlteQz0ACgkQ8gKXHaSn
nix25Qv9GNyPhiFRAfl+2Ni+HCzF23tmaKxU05eajCA4RQHlFIunt/2sBy7/zabF
ikDamSD5GZc26sA3yMRhGqOkcZ2R+HS7JrSlxLSOYE8PL/5ETAOtIhXP927O/1ZS
vfwyXvDcZvbtDMmauArD+fl7lh8VaRxMuSat3JEy+kSJ1/hejAEYloGXR9HaWxqe
W8zI1R8YXBI3Z1kB88h4GGXv0AuW+S9KK8kI4g1gBKSfn6VtHS9aN3vyGLPUVGl7
AP3tgzSQPzLEZv+i4n5Abp14yqvHMaqewmhaqo7Or4cfLRE4TJC/yWrD4QP1nMSf
sKuRR/tPDJRikZ3uKiAYZ/s5dmVzeNQ2ZaEAx4I+752iNDzLOacocEZhHxuW3gfv
nkGkP4Wj8B9IElxuqy5c6xK4pHdWAfTMMRscBMXq/OFE1tWnPDnRkoTB8RMw0UD8
ZbwohIwSH/9AVzhg7IpBdTNnTkAz9p62/fI0nnfFwFaFWHCYDUahSUMfnlrDTxX5
rAckFiiz
=JhAV
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---

Hi,

emacsen-common 3.0.2 was uploaded to sid on 30th so closing this bug.

Regards,
Arnaud Fontaine--- End Message ---

Processed: reopening 903663, severity of 903663 is normal

[Debian Bug Tracking System]

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

> reopen 903663
Bug #903663 {Done: Adrian Bunk } [python3-numpy] 
python3-numpy: Should not depend on python3.7
Bug reopened
Ignoring request to alter fixed versions of bug #903663 to the same values 
previously set
> severity 903663 normal
Bug #903663 [python3-numpy] python3-numpy: Should not depend on python3.7
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#897707: arrayfire: ftbfs with GCC-8

[Bernhard Übelacker]

Hello,
just tried to have a look at #892288 but got stopped by this one.

Upstream handled this issue in [arrayfire/2148] and [arrayfire/2149].
Unfortunately this patch does not apply.

Also the pull request mentions another change is needed in the
boost library [boostorg/776].

Kind regards,
Bernhard


[arrayfire/2148] https://github.com/arrayfire/arrayfire/issues/2148
[arrayfire/2149] https://github.com/arrayfire/arrayfire/pull/2149
[boostorg/776]   https://github.com/boostorg/compute/pull/776

Bug#902989: python3-pyatspi: fresh installation breaks

[Samuel Thibault]

Hello,

Control: severity -1 important

Wolfgang Schweer, le mer. 04 juil. 2018 16:47:46 +0200, a ecrit:
>   File "/usr/lib/python3/dist-packages/pyatspi/registry.py", line 114
> self.async = False# not fully supported yet

As mentioned previously, this is a problem with python 3.7.  I have now
uploaded version debian/2.26.0+dfsg-3 which prevents from using python
3.7 with python3-pyatspi.  This is not a proper long-term fix of course,
but that should allow us to have buster/sid working fine with python 3.6
while upstream decides how to fix it.

Samuel

Bug#897844: marked as done (qtscript-opensource-src: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Thu, 2 Aug 2018 00:31:15 +0300
with message-id <20180801213115.GA11646@localhost>
and subject line Re: Bug#897844: qtscript-opensource-src: ftbfs with GCC-8
has caused the Debian Bug report #897844,
regarding qtscript-opensource-src: 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.)


-- 
897844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qtscript-opensource-src
Version: 5.10.1+dfsg-2
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/qtscript-opensource-src_5.10.1+dfsg-2_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

[...]
   Loc: [tst_qscriptclass.cpp(1358)]
PASS   : tst_QScriptClass::defaultImplementations()
PASS   : tst_QScriptClass::scriptClassObjectInPrototype()
PASS   : tst_QScriptClass::scriptClassWithNullEngine()
PASS   : tst_QScriptClass::scriptClassInOtherEngine()
PASS   : tst_QScriptClass::cleanupTestCase()
Totals: 16 passed, 8 failed, 0 skipped, 0 blacklisted, 10ms
* Finished testing of tst_QScriptClass *
make[5]: *** [Makefile:296: check] Error 8
make[5]: Leaving directory 
'/<>/qtscript-opensource-src-5.10.1+dfsg/tests/auto/qscriptclass'
make[4]: *** [Makefile:1078: sub-qscriptclass-check] Error 2
make[5]: Nothing to be done for 'check'.
make[5]: Entering directory 
'/<>/qtscript-opensource-src-5.10.1+dfsg/tests/auto/qscriptcontextinfo'
/<>/qtscript-opensource-src-5.10.1+dfsg/tests/auto/qscriptcontextinfo/target_wrapper.sh
  ./tst_qscriptcontextinfo 
* Start testing of tst_QScriptContextInfo *
Config: Using QtTest library 5.10.1, Qt 5.10.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 7.3.0)
PASS   : tst_QScriptContextInfo::initTestCase()
XFAIL  : tst_QScriptContextInfo::nativeFunction() QTBUG-17602: columnNumber 
doesn't work
   Loc: [tst_qscriptcontextinfo.cpp(139)]
PASS   : tst_QScriptContextInfo::nativeFunction()
XFAIL  : tst_QScriptContextInfo::scriptFunction() QTBUG-17602: columnNumber 
doesn't work
   Loc: [tst_qscriptcontextinfo.cpp(171)]
XFAIL  : tst_QScriptContextInfo::scriptFunction() QTBUG-17602: columnNumber 
doesn't work
   Loc: [tst_qscriptcontextinfo.cpp(190)]
PASS   : tst_QScriptContextInfo::scriptFunction()
FAIL!  : tst_QScriptContextInfo::qtFunction() Compared values are not the same
   Actual   (info.functionParameterNames().size()): 1
   Expected (pnames.size())   : 2
   Loc: [tst_qscriptcontextinfo.cpp(236)]
PASS   : tst_QScriptContextInfo::qtPropertyFunction()
PASS   : tst_QScriptContextInfo::nullContext()
PASS   : tst_QScriptContextInfo::streaming()
PASS   : tst_QScriptContextInfo::comparison_null()
PASS   : tst_QScriptContextInfo::assignmentAndComparison()
PASS   : tst_QScriptContextInfo::cleanupTestCase()
Totals: 9 passed, 1 failed, 0 skipped, 0 blacklisted, 4ms
* Finished testing of tst_QScriptContextInfo *
make[5]: *** [Makefile:296: check] Error 1
make[5]: Leaving directory 
'/<>/qtscript-opensource-src-5.10.1+dfsg/tests/auto/qscriptcontextinfo'
make[4]: *** [Makefile:1081: sub-qscriptcontextinfo-check] Error 2
make[3]: *** [Makefile:297: sub-auto-check] Error 2
make[2]: *** [Makefile:398: sub-tests-check] Error 2
make[2]: *** Waiting for unfinished jobs
make[5]: Nothing to be done for 'check'.
make[5]: Nothing to be done for 'check'.
dh_auto_test: make -j8 -Oline check returned exit code 2
make[1]: *** [debian/rules:42: override_dh_auto_test-arch] Error 25
make[1]: Leaving directory 

Bug#897886: marked as done (wfmath: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Thu, 2 Aug 2018 00:23:38 +0300
with message-id <20180801212338.GA27154@localhost>
and subject line Re: Bug#897886: wfmath: ftbfs with GCC-8
has caused the Debian Bug report #897886,
regarding wfmath: 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.)


-- 
897886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wfmath
Version: 1.0.2+dfsg1-4
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/wfmath_1.0.2+dfsg1-4_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

[...]
@@ -527,7 +527,7 @@
  _ZN6WFMath9IntersectINS_5PointILi2EEENS_6RotBoxILi2EbRKT_RKT0_b@Base 
0.3.11
  _ZN6WFMath9IntersectINS_5PointILi2EEENS_7AxisBoxILi2EbRKT_RKT0_b@Base 
0.3.11
  _ZN6WFMath9IntersectINS_5PointILi2EEENS_7PolygonILi2EbRKT_RKT0_b@Base 
0.3.11
- 
(optional)_ZN6WFMath9IntersectINS_5PointILi2EEENS_7PolygonILi3EbRKT_RKT0_b@Base
 0.3.11
+#MISSING: 1.0.2+dfsg1-4# 
(optional)_ZN6WFMath9IntersectINS_5PointILi2EEENS_7PolygonILi3EbRKT_RKT0_b@Base
 0.3.11
  _ZN6WFMath9IntersectINS_5PointILi2EEENS_7SegmentILi2EbRKT_RKT0_b@Base 
0.3.11
  _ZN6WFMath9IntersectINS_5PointILi3EEENS_4BallILi3EbRKT_RKT0_b@Base 0.3.11
  _ZN6WFMath9IntersectINS_5PointILi3EEENS_6RotBoxILi3EbRKT_RKT0_b@Base 
0.3.11
@@ -1007,25 +1007,27 @@
  _ZNK6WFMath9RotMatrixILi3EE9isEqualToERKS1_f@Base 1.0.0
  _ZNK6WFMath9RotMatrixILi3EEeqERKS1_@Base 0.3.11
  _ZNK6WFMath9RotMatrixILi3EEneERKS1_@Base 0.3.11
- 
(optional=inline)_ZNSs12_S_constructIPcEES0_T_S1_RKSaIcESt20forward_iterator_tag@Base
 0.3.12
- 
(optional=inline)_ZNSt10_List_baseIN6WFMath11_PolyReaderILi3EEESaIS2_EE8_M_clearEv@Base
 0.3.12
- 
(optional=inline)_ZNSt10_List_baseIN6WFMath9_miniball13Wrapped_arrayILi2EEESaIS3_EE8_M_clearEv@Base
 0.3.12
- 
(optional=inline)_ZNSt6vectorIN6WFMath5PointILi2EEESaIS2_EE13_M_insert_auxIIRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.0.2
+#MISSING: 1.0.2+dfsg1-4# 
(optional=inline)_ZNSs12_S_constructIPcEES0_T_S1_RKSaIcESt20forward_iterator_tag@Base
 0.3.12
+#MISSING: 1.0.2+dfsg1-4# 
(optional=inline)_ZNSt10_List_baseIN6WFMath11_PolyReaderILi3EEESaIS2_EE8_M_clearEv@Base
 0.3.12
+#MISSING: 1.0.2+dfsg1-4# 
(optional=inline)_ZNSt10_List_baseIN6WFMath9_miniball13Wrapped_arrayILi2EEESaIS3_EE8_M_clearEv@Base
 0.3.12
+#MISSING: 1.0.2+dfsg1-4# 
(optional=inline)_ZNSt6vectorIN6WFMath5PointILi2EEESaIS2_EE13_M_insert_auxIIRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.0.2
  
(regex)_ZNSt6vectorIN6WFMath5PointILi2EEESaIS2_EE17_M_default_appendE[jm]@Base 
1.0.2
  
_ZNSt6vectorIN6WFMath5PointILi2EEESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.0.2+dfsg1-4~
- 
(optional=inline)_ZNSt6vectorIN6WFMath5PointILi2EEESaIS2_EE19_M_emplace_back_auxIIRKS2_EEEvDpOT_@Base
 1.0.2
+#MISSING: 1.0.2+dfsg1-4# 
(optional=inline)_ZNSt6vectorIN6WFMath5PointILi2EEESaIS2_EE19_M_emplace_back_auxIIRKS2_EEEvDpOT_@Base
 1.0.2
  (optional=inline)_ZNSt6vectorIN6WFMath5PointILi2EEESaIS2_EEaSERKS4_@Base 
0.3.11
- 
(optional=inline)_ZNSt6vectorIN6WFMath5PointILi3EEESaIS2_EE13_M_insert_auxIIRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.0.0
+#MISSING: 1.0.2+dfsg1-4# 
(optional=inline)_ZNSt6vectorIN6WFMath5PointILi3EEESaIS2_EE13_M_insert_auxIIRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.0.0
  
_ZNSt6vectorIN6WFMath5PointILi3EEESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 1.0.2+dfsg1-4~
  

Bug#897874: marked as done (systemtap: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Thu, 2 Aug 2018 00:21:05 +0300
with message-id <20180801212104.GA13331@localhost>
and subject line Re: Bug#897874: systemtap: ftbfs with GCC-8
has caused the Debian Bug report #897874,
regarding systemtap: 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.)


-- 
897874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:systemtap
Version: 3.1-3
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/systemtap_3.1-3_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

[...]
./includes/sys/sdt.h:119:75: error: type qualifiers ignored on cast result type 
[-Werror=ignored-qualifiers]
 template<> struct __sdt_type { static const bool __sdt_signed = ((T)(-1) < 
1); };
   ^
./includes/sys/sdt.h:146:1: note: in expansion of macro '__SDT_COND_SIGNED'
 __SDT_COND_SIGNED(const volatile char)
 ^
./includes/sys/sdt.h:119:75: error: type qualifiers ignored on cast result type 
[-Werror=ignored-qualifiers]
 template<> struct __sdt_type { static const bool __sdt_signed = ((T)(-1) < 
1); };
   ^
./includes/sys/sdt.h:147:1: note: in expansion of macro '__SDT_COND_SIGNED'
 __SDT_COND_SIGNED(const volatile wchar_t)
 ^
cc1plus: all warnings being treated as errors
make[4]: *** [Makefile:1148: stap-main.o] Error 1
make[4]: Leaving directory '/<>'
make[4]: *** Waiting for unfinished jobs
make[4]: Entering directory '/<>'
gcc -DHAVE_CONFIG_H -I.  -DBINDIR='"/usr/bin"' -DSYSCONFDIR='"/etc"' 
-DPKGDATADIR='"/usr/share/systemtap"' -DPKGLIBDIR='"/usr/lib/systemtap"' 
-DLOCALEDIR='"/usr/share/locale"' -DDOCDIR='"/usr/share/doc/systemtap"' 
-DPYEXECDIR='"/usr/lib/python2.7/dist-packages"' -DPY3EXECDIR='""' -I./includes 
-I./includes/sys -DSTAP_SDT_V2 -D_REENTRANT -I/usr/include/nss 
-I/usr/include/nspr  -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -fexceptions 
-Wall -Wextra -Werror -Wunused -Wformat=2 -W -I/usr/include/nss 
-I/usr/include/nspr -DSTAP -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fstack-protector-all 
-D_FORTIFY_SOURCE=2 -c -o stap-loc2c.o `test -f 'loc2c.c' || echo './'`loc2c.c
make[4]: Leaving directory '/<>'
make[4]: Entering directory '/<>'
g++ -DHAVE_CONFIG_H -I.  -DBINDIR='"/usr/bin"' -DSYSCONFDIR='"/etc"' 
-DPKGDATADIR='"/usr/share/systemtap"' -DPKGLIBDIR='"/usr/lib/systemtap"' 
-DLOCALEDIR='"/usr/share/locale"' -DDOCDIR='"/usr/share/doc/systemtap"' 
-DPYEXECDIR='"/usr/lib/python2.7/dist-packages"' -DPY3EXECDIR='""' -I./includes 
-I./includes/sys -DSTAP_SDT_V2 -D_REENTRANT -I/usr/include/nss 
-I/usr/include/nspr  -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror 
-D_REENTRANT -I/usr/include/nss -I/usr/include/nspr -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fstack-protector-all -D_FORTIFY_SOURCE=2 -c -o 
stap-staptree.o `test -f 'staptree.cxx' || echo './'`staptree.cxx
make[4]: Leaving directory '/<>'
make[4]: Entering directory '/<>'
g++ -DHAVE_CONFIG_H -I.  -DBINDIR='"/usr/bin"' -DSYSCONFDIR='"/etc"' 
-DPKGDATADIR='"/usr/share/systemtap"' -DPKGLIBDIR='"/usr/lib/systemtap"' 
-DLOCALEDIR='"/usr/share/locale"' -DDOCDIR='"/usr/share/doc/systemtap"' 
-DPYEXECDIR='"/usr/lib/python2.7/dist-packages"' -DPY3EXECDIR='""' -I./includes 
-I./includes/sys -DSTAP_SDT_V2 -D_REENTRANT -I/usr/include/nss 

Processed: Merge duplicates and link to the upstream issue

[Debian Bug Tracking System]

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

> reassign 897857 swig
Bug #897857 [src:setools] setools: ftbfs with GCC-8
Bug reassigned from package 'src:setools' to 'swig'.
No longer marked as found in versions setools/4.1.1-3.
Ignoring request to alter fixed versions of bug #897857 to the same values 
previously set
> unblock 897857 by 900420
Bug #897857 [swig] setools: ftbfs with GCC-8
897857 was blocked by: 900420
897857 was not blocking any bugs.
Removed blocking bug(s) of 897857: 900420
> severity 900420 serious
Bug #900420 [swig] setools: ftbfs with GCC-8
Severity set to 'serious' from 'normal'
> forcemerge 900420 897857
Bug #900420 [swig] setools: ftbfs with GCC-8
Bug #897857 [swig] setools: ftbfs with GCC-8
Unset Bug forwarded-to-address
Added indication that 897857 affects setools
Marked as found in versions swig/3.0.12-1.
Bug #900420 [swig] setools: ftbfs with GCC-8
Added tag(s) fixed-upstream.
Merged 897857 900420
> affects 897857 src:setools
Bug #897857 [swig] setools: ftbfs with GCC-8
Bug #900420 [swig] setools: ftbfs with GCC-8
Added indication that 897857 affects src:setools
Added indication that 900420 affects src:setools
> forwarded 897857 https://github.com/swig/swig/issues/1259
Bug #897857 [swig] setools: ftbfs with GCC-8
Bug #900420 [swig] setools: ftbfs with GCC-8
Set Bug forwarded-to-address to 'https://github.com/swig/swig/issues/1259'.
Set Bug forwarded-to-address to 'https://github.com/swig/swig/issues/1259'.
> tags 897857 fixed-upstream
Bug #897857 [swig] setools: ftbfs with GCC-8
Bug #900420 [swig] setools: ftbfs with GCC-8
Ignoring request to alter tags of bug #897857 to the same tags previously set
Ignoring request to alter tags of bug #900420 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 897879 src:aspectc++
Bug #897879 [src:undertaker] undertaker: ftbfs with GCC-8
Bug reassigned from package 'src:undertaker' to 'src:aspectc++'.
No longer marked as found in versions undertaker/1.6.1-4.1.
Ignoring request to alter fixed versions of bug #897879 to the same values 
previously set
> unarchive 897709
Bug #897709 {Done: Reinhard Tartler } [src:aspectc++] 
aspectc++: ftbfs with GCC-8
Unarchived Bug 897709
> severity 897709 serious
Bug #897709 {Done: Reinhard Tartler } [src:aspectc++] 
aspectc++: ftbfs with GCC-8
Severity set to 'serious' from 'normal'
> forcemerge 897709 897879
Bug #897709 {Done: Reinhard Tartler } [src:aspectc++] 
aspectc++: ftbfs with GCC-8
Bug #897879 [src:aspectc++] undertaker: ftbfs with GCC-8
Marked Bug as done
Marked as fixed in versions aspectc++/1:2.2+git20170823-6.
Marked as found in versions aspectc++/1:2.2+git20170823-5.
Added tag(s) upstream.
Merged 897709 897879
> affects 897709 src:undertaker
Bug #897709 {Done: Reinhard Tartler } [src:aspectc++] 
aspectc++: ftbfs with GCC-8
Bug #897879 {Done: Reinhard Tartler } [src:aspectc++] 
undertaker: ftbfs with GCC-8
Added indication that 897709 affects src:undertaker
Added indication that 897879 affects src:undertaker
> thanks
Stopping processing here.

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

Processed: affects 897895

[Debian Bug Tracking System]

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

> affects 897895 src:rsbackup
Bug #897895 [libsigc++-2.0-dev] rsbackup: ftbfs with GCC-8
Added indication that 897895 affects src:rsbackup
> thanks
Stopping processing here.

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

Bug#897788: marked as done (libfm-qt: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Wed, 1 Aug 2018 22:41:49 +0300
with message-id <20180801194149.GB26939@localhost>
and subject line Fixed in 0.13.1-6
has caused the Debian Bug report #897788,
regarding libfm-qt: 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.)


-- 
897788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libfm-qt
Version: 0.12.0-17
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/libfm-qt_0.12.0-17_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

[...]
+ 
_ZNSt6vectorIPN2Fm16DirTreeModelItemESaIS2_EE12emplace_backIJS2_EEEvDpOT_@Base 
0.12.0-17
+ 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base
 0.12.0-17
+ 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag@Base
 0.12.0-17
  fm_search_add_dir@Base 0.10.0
  fm_search_add_mime_type@Base 0.10.0
  fm_search_dup_path@Base 0.10.0
@@ -1022,13 +1029,13 @@
  (c++|arch= !amd64 !arm64 !mips64el !ppc64el !s390x !alpha !ia64 
!kfreebsd-amd64 !ppc64 !riscv64 !sparc64 
)"std::_Hashtable, 
std::allocator > const, std::pair, std::allocator > const, 
std::shared_ptr >, 
std::allocator, std::allocator > const, 
std::shared_ptr > >, std::__detail::_Select1st, 
std::equal_to, 
std::allocator > const>, std::hash, std::allocator > >, 
std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, 
std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_find_before_node(unsigned int, 
std::__cxx11::basic_string, std::allocator
  > const&, unsigned int) const@Base" 0.12.0
  (c++|arch= !armel !armhf !i386 !mips !mipsel !hppa !hurd-i386 !kfreebsd-i386 
!m68k !powerpc !sh4 !x32 )"std::_Hashtable, std::allocator > const, 
std::pair, 
std::allocator > const, std::shared_ptr >, 
std::allocator, std::allocator > const, 
std::shared_ptr > >, std::__detail::_Select1st, 
std::equal_to, 
std::allocator > const>, std::hash, std::allocator > >, 
std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, 
std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_find_before_node(unsigned long, 
std::__cxx11::basic_string, std::allocator >
  const&, unsigned long) const@Base" 0.12.0
  (c++|arch= !amd64 !arm64 !mips64el !ppc64el !s390x !alpha !ia64 
!kfreebsd-amd64 !ppc64 !riscv64 !sparc64 
)"std::_Hashtable, 
std::allocator > const, std::pair, std::allocator > const, 
std::shared_ptr >, 
std::allocator, std::allocator > const, 
std::shared_ptr > >, std::__detail::_Select1st, 
std::equal_to, 
std::allocator > const>, std::hash, std::allocator > >, 
std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, 
std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_insert_unique_node(unsigned int, unsigned int, 
std::__detail::_Hash_node, std::allocator > const, 
std::shared_ptr >, true>*)@Base" 0.12.0
- (c++|arch= !armel !armhf !i386 !mips !mipsel !hppa !hurd-i386 !kfreebsd-i386 
!m68k !powerpc !sh4 !x32 )"std::_Hashtable, std::allocator > const, 
std::pair, 
std::allocator > const, std::shared_ptr >, 
std::allocator, std::allocator > const, 
std::shared_ptr > >, std::__detail::_Select1st, 
std::equal_to, 
std::allocator > const>, std::hash, std::allocator > >, 
std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, 
std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_insert_unique_node(unsigned long, unsigned 

Processed: forcibly merging 897721 891544

[Debian Bug Tracking System]

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

> forcemerge 897721 891544
Bug #897721 [src:chiark-tcl] chiark-tcl: ftbfs with GCC-8
Bug #891544 [src:chiark-tcl] chiark-tcl: FTBFS with GCC 8 - error: division 
'sizeof (const int *) / sizeof (int)' does not compute the number of array 
elements
Severity set to 'serious' from 'important'
Added tag(s) buster and sid.
Merged 891544 897721
> thanks
Stopping processing here.

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

Processed: bug 905140 is forwarded to https://gitlab.kitware.com/cmake/cmake/merge_requests/2169, tagging 905140

[Debian Bug Tracking System]

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

> forwarded 905140 https://gitlab.kitware.com/cmake/cmake/merge_requests/2169
Bug #905140 [src:cmake] cmake: FTBFS with recent version of libuv1
Set Bug forwarded-to-address to 
'https://gitlab.kitware.com/cmake/cmake/merge_requests/2169'.
> tags 905140 + fixed-upstream
Bug #905140 [src:cmake] cmake: FTBFS with recent version of libuv1
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#905188: [pkg-cryptsetup-devel] Bug#905188: cryptsetup-initramfs: fails to install, remove, distupgrade, and install again

[Andreas Beckmann]

Hi Guilhem,

On 2018-08-01 19:01, Guilhem Moulin wrote:
> On Wed, 01 Aug 2018 at 13:20:37 +0200, Andreas Beckmann wrote:
>> Configuration file '/etc/cryptsetup-initramfs/conf-hook'
>>  ==> Deleted (by you or by a script) since installation.
>>  ==> Package distributor has shipped an updated version.
>>What would you like to do about it ?  Your options are:
>> Y or I  : install the package maintainer's version
>> N or O  : keep your currently-installed version
>>   D : show the differences between the versions
>>   Z : start a shell to examine the situation
>>  The default action is to keep your current version.
>> *** conf-hook (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package 
>> cryptsetup-initramfs (--configure):
>>  end of file on stdin at conffile prompt
>> dpkg: dependency problems prevent configuration of cryptsetup:
>>  cryptsetup depends on cryptsetup-initramfs (>= 2:2.0.3-1); however:
>>   Package cryptsetup-initramfs is not configured yet.
> 
> I wonder if it's a false positive?  Following the same upgrade path in a
No, already asking the question about the conffile that was *not*
modified by the user is a policy violation. That's the the piuparts bug
template for this error in "normal" upgrade scenarios:

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/#behavior,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

Andreas

Processed: Re: Bug#905177: bind9: prompting due to modified conffiles which were not modified by the user: /etc/bind/named.conf.options

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #905177 [bind9] bind9: prompting due to modified conffiles which were not 
modified by the user: /etc/bind/named.conf.options
Added tag(s) help.

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

Bug#905177: bind9: prompting due to modified conffiles which were not modified by the user: /etc/bind/named.conf.options

[Bernhard Schmidt]

Control: tags -1 help

Am 01.08.2018 um 18:56 schrieb Andreas Beckmann:

Hi,

> Suggestion: In the preinst check whether you are upgrading from <<
> 9.11.2+dfsg-6 and whether the file matches the version installed in
> stretch (md5sum/...) and move it aside (maybe there were more possible
> files installed by older versions, check for all of them). In the
> postinst delete the backup. Restore it on failed-upgrade.
> 
> If the file was manually modified (i.e. does not match any known hash),
> do nothing and let dpkg prompt the user.
> 
> I don't mind reviewing some patches.

Thanks for the suggestion, sounds like a plan. I'll see what I can come
up with. Not really much time at the moment though, so any takers would
be welcome.

Bernhard

Bug#898113: ltrace crashes and hangs on armhf

[Christoph Biedl]

Jens wrote...

>* Further information
>   This bug is known and a patch is documented in 
> https://code.kodo.org.uk/dom/buildroot/commit/efee851c614926dd9ed0f49c4808a6d9b4f64eb0

Tried to handle this bug but it seems this fix doesn't help - and
honestly I fail to see how adding a definition in
sysdeps/linux-gnu/arm/plt.c should help against the problem.

>   You will also need 
> https://github.com/openembedded/meta-openembedded/blob/master/meta-oe/recipes-devtools/ltrace/ltrace/0001-replace-readdir_r-with-readdir.patch
>  to compile it against the latest glibc

FWIW, that was fixed before in ,
the patch can be found at


Regards,

Christoph


signature.asc
Description: PGP signature

Bug#905124: Acknowledgement (abcde: Can't use an undefined value as an ARRAY reference at /usr/bin/abcde-musicbrainz-tool line 98)

[Helge Kreutzmann]

Hello Maintainers,
I'm trying to debug this. I added 
my $key;
my $value;
foreach $key (keys %$response )
{
# $value = %$response ($key);
$value = $response->{$key};
print "Schlüssel: $key  Wert: $value\n";
}
before the offending line and got the additional output:
Schlüssel: tracks  Wert: ARRAY(0x557516e32b38)
Schlüssel: title  Wert: Die Olchis im Bann des Magiers
Schlüssel: track-count  Wert: 10
Schlüssel: id  Wert: 15hnoNO43l2LUGvUkfXAwvWnOhQ-
Schlüssel: barcode  Wert: 9783837306460
Schlüssel: artist  Wert: Erhard Dietl read by Rainer Schmitt
Schlüssel: disambiguation  Wert: CD 2 / 2

The values are as expected, but there is no key "releease" (and
subsequently no ARRAY behind it).

Sorry, I guess that is all I can do to debug this myself, please tell
me what other information are helpful for you.

Greetings

 Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#905188: [pkg-cryptsetup-devel] Bug#905188: cryptsetup-initramfs: fails to install, remove, distupgrade, and install again

[Guilhem Moulin]

Control: tag -1 moreinfo

Hi Andreas,

On Wed, 01 Aug 2018 at 13:20:37 +0200, Andreas Beckmann wrote:
> Configuration file '/etc/cryptsetup-initramfs/conf-hook'
>  ==> Deleted (by you or by a script) since installation.
>  ==> Package distributor has shipped an updated version.
>What would you like to do about it ?  Your options are:
> Y or I  : install the package maintainer's version
> N or O  : keep your currently-installed version
>   D : show the differences between the versions
>   Z : start a shell to examine the situation
>  The default action is to keep your current version.
> *** conf-hook (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package 
> cryptsetup-initramfs (--configure):
>  end of file on stdin at conffile prompt
> dpkg: dependency problems prevent configuration of cryptsetup:
>  cryptsetup depends on cryptsetup-initramfs (>= 2:2.0.3-1); however:
>   Package cryptsetup-initramfs is not configured yet.

I wonder if it's a false positive?  Following the same upgrade path in a
stretch chroot:

$ apt install cryptsetup
$ apt remove cryptsetup
$ sed -i s/stretch/buster/g /etc/apt/sources.list.d/debian.sources 
$ apt update
$ apt dist-upgrade
$ apt install cryptsetup

The log differs as follows:

Configuration file '/etc/cryptsetup-initramfs/conf-hook'
 ==> Deleted (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** conf-hook (Y/I/N/O/D/Z) [default=N] ? 
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
debconf: falling back to frontend: Readline
update-initramfs: deferring update (trigger activated)
Setting up cryptsetup (2:2.0.3-6) ...
Processing triggers for initramfs-tools (0.132) ...

And the upgrade path is successful.  AFICT piuparts's dpkg processes
fail because there is no working standard input.  But normal systems
have a working standard input, and the upgrade path is function there. 
AFAIK automatic configuration tools install with

DEBIAN_FRONTEND=noninteractive apt-get install -o 
"Dpkg::Options::=--force-confdef" -o "Dpkg::Options::=--force-confold" -y

which also works.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#831519: Processed: severity of 831519 is serious, severity of 860298 is serious, severity of 858583 is serious

[Raúl Benencia]

Dear Jason, 

On Wed, Aug 01, 2018 at 12:07:45PM -0400, Jason J. Herne wrote:
> I'm the author of Vizigrep. It needs to be converted to Python-3. I'll work
> on the conversion but I need a little info on Debian's process.

Thanks for taking care of the package!

> 1. Is there some sort of deadline to ensure Vizigrep does not get dropped?

The package will get dropped from testing in two weeks, that's Aug 14th.
You can get more information here:

  https://tracker.debian.org/pkg/vizigrep 

> 2. What is the process for submitting my changes once I am done? I used to
> know this at one time... Is there a wiki page I should follow?

So, there are many ways in which you can package your software.
Personally, I like to use git for keeping track of all the packaging
code. Check the wiki[0] page for getting started if you want to give
this method a try. I also encourage you to take a look to the New
Maintainer's guide[1].

   [0] https://wiki.debian.org/PackagingWithGit 
   [1] https://www.debian.org/doc/manuals/maint-guide/

Once you have your package ready, you have to find a sponsor for it.
For this, I encourage you to contact the person that sponsored the package
for the first time.

Cheers,
Rul

Processed: Re: [pkg-cryptsetup-devel] Bug#905188: cryptsetup-initramfs: fails to install, remove, distupgrade, and install again

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #905188 [cryptsetup-initramfs] cryptsetup-initramfs: fails to install, 
remove, distupgrade, and install again
Added tag(s) moreinfo.

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

Bug#905177: bind9: prompting due to modified conffiles which were not modified by the user: /etc/bind/named.conf.options

[Andreas Beckmann]

On 2018-08-01 18:05, Bernhard Schmidt wrote:
> So the file is there and not marked as conffile, because it has been
> created in postinst. Now in Buster the file is properly shipped as
> conffile (since commit 9ddbb41a71236815d246180b454850ec4ef7862d,
> included in 9.11.2+dfsg-6.
> 
> It is only appearing now because the named.conf.options has now been
> changed from the version contained in Stretch in 9.11.4+dfsg-2.

> But the
> underlying bug is in Stretch.

Not really. There is nothing wrong with the handling in stretch.
Using conffiles is just superior :-)
You just need to migrate properly ...

> I have no idea how to properly deal with this.

Suggestion: In the preinst check whether you are upgrading from <<
9.11.2+dfsg-6 and whether the file matches the version installed in
stretch (md5sum/...) and move it aside (maybe there were more possible
files installed by older versions, check for all of them). In the
postinst delete the backup. Restore it on failed-upgrade.

If the file was manually modified (i.e. does not match any known hash),
do nothing and let dpkg prompt the user.

I don't mind reviewing some patches.


Andreas

Bug#905124: Acknowledgement (abcde: Can't use an undefined value as an ARRAY reference at /usr/bin/abcde-musicbrainz-tool line 98)

[Helge Kreutzmann]

Hello Maintainer(s),
I read in #892480 (which seems a similar issue) that you need the
output of abcde with "-D" added.

I attached it to this e-mail.

Greetings

  Helge

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/
+ getopts 1a:bBc:C:d:DefgGhj:klLmMnNo:pPQ:r:s:S:t:T:UvVxX:w:W:z opt
+ case "$opt" in
+ OUTPUTTYPE=mp3
+ getopts 1a:bBc:C:d:DefgGhj:klLmMnNo:pPQ:r:s:S:t:T:UvVxX:w:W:z opt
+ case "$opt" in
+ PADTRACKS=y
+ getopts 1a:bBc:C:d:DefgGhj:klLmMnNo:pPQ:r:s:S:t:T:UvVxX:w:W:z opt
+ case "$opt" in
+ EXTRAVERBOSE=1
+ getopts 1a:bBc:C:d:DefgGhj:klLmMnNo:pPQ:r:s:S:t:T:UvVxX:w:W:z opt
+ case "$opt" in
+ EJECTCD=y
+ getopts 1a:bBc:C:d:DefgGhj:klLmMnNo:pPQ:r:s:S:t:T:UvVxX:w:W:z opt
+ case "$opt" in
+ COMMENT='Ripped 01.08.2018 on samd'
+ getopts 1a:bBc:C:d:DefgGhj:klLmMnNo:pPQ:r:s:S:t:T:UvVxX:w:W:z opt
+ shift 8
+ '[' n = y ']'
+ echo /dev/cdrom
+ grep -i '.flac$'
+ '[' -n '' ']'
+ '[' '' = flac ']'
+ '[' '' = '' ']'
+ for DEFAULT_CDROMREADER in $DEFAULT_CDROMREADERS
+ new_checkexec cdparanoia
+ '[' '!' cdparanoia = '' ']'
++ echo cdparanoia
++ cut '-d ' -f2
+ X=cdparanoia
++ which cdparanoia
+ WHICH=/usr/bin/cdparanoia
+ '[' -z /usr/bin/cdparanoia ']'
+ '[' '!' -x /usr/bin/cdparanoia ']'
+ return 0
+ CDROMREADERSYNTAX=cdparanoia
+ break
+ '[' cdparanoia = '' ']'
+ '[' '' = y ']'
+ '[' 0 -gt 0 ']'
+ DOCDDB=n
+ DOREAD=n
+ DONORMALIZE=n
+ DOPREPROCESS=n
+ DOENCODE=n
+ DOPOSTPROCESS=n
+ DOTAG=n
+ DOMOVE=n
+ DOREPLAYGAIN=n
+ DOPLAYLIST=n
+ DOCLEAN=n
+ '[' '' '!=' y ']'
+ DOCUE=n
++ echo cddb,read,encode,tag,move,clean
++ tr , ' '
+ for ACTION in $(echo "$ACTIONS" | tr , \ )
+ case $ACTION in
+ DOCDDB=y
+ for ACTION in $(echo "$ACTIONS" | tr , \ )
+ case $ACTION in
+ DOREAD=y
+ for ACTION in $(echo "$ACTIONS" | tr , \ )
+ case $ACTION in
+ DOENCODE=y
+ DOREAD=y
+ for ACTION in $(echo "$ACTIONS" | tr , \ )
+ case $ACTION in
+ DOTAG=y
+ DOREAD=y
+ DOENCODE=y
+ DOCDDB=y
+ for ACTION in $(echo "$ACTIONS" | tr , \ )
+ case $ACTION in
+ DOMOVE=y
+ DOTAG=y
+ DOREAD=y
+ DOENCODE=y
+ DOCDDB=y
+ for ACTION in $(echo "$ACTIONS" | tr , \ )
+ case $ACTION in
+ DOCLEAN=y
+ '[' n = y ']'
++ echo year,genre
++ tr , ' '
+ for SHOWCDDBFIELD in $(echo "$SHOWCDDBFIELDS" | tr , \ )
+ case $SHOWCDDBFIELD in
+ SHOWCDDBYEAR=y
+ for SHOWCDDBFIELD in $(echo "$SHOWCDDBFIELDS" | tr , \ )
+ case $SHOWCDDBFIELD in
+ SHOWCDDBGENRE=y
+ '[' X/dev/cdrom '!=' X ']'
+ '[' '' = y ']'
+ '[' '!' -e /dev/cdrom ']'
+ '[' X = Xy ']'
+ '[' X = Xy ']'
+ '[' n = y ']'
+ '[' Xmp3 = X ']'
+ case "$CDROMREADERSYNTAX" in
+ CDROMREADER=cdparanoia
+ CDROMREADEROPTS=
+ case "$NORMALIZERSYNTAX" in
+ NORMALIZER=normalize-audio
+ NORMALIZEROPTS=
+ case "$OUTPUTTYPE" in
++ echo mp3
++ tr , ' '
+ for OUTPUT in $(echo "$OUTPUTTYPE" | tr , \ )
+ case $OUTPUT in
+ '[' default = default ']'
+ MP3ENCODERSYNTAX=lame
+ '[' y = y ']'
+ NEEDTAGGER=y
+ '[' n = y ']'
+ '[' '' = y ']'
+ case "$MP3ENCODERSYNTAX" in
+ MP3ENCODEROPTS=
+ MP3ENCODER=lame
+ case "$OGGENCODERSYNTAX" in
+ case "$OPUSENCODERSYNTAX" in
+ case "$MKAENCODERSYNTAX" in
+ case "$AIFFENCODERSYNTAX" in
+ case "$FLACENCODERSYNTAX" in
+ case "$SPEEXENCODERSYNTAX" in
+ case "$MPCENCODERSYNTAX" in
+ case "$WVENCODERSYNTAX" in
+ case "$TTAENCODERSYNTAX" in
+ case "$APENCODERSYNTAX" in
+ case "$MP2ENCODERSYNTAX" in
+ case "$AACENCODERSYNTAX" in
+ case "$ID3TAGV" in
+ TAGGER=eyeD3
+ '[' 6 -lt 6 ']'
+ eyeD3 --help
+ grep -q -- --set-encoding
+ ID3SYNTAX=eyed3
+ TAGGEROPTS='--encoding utf16 '
+ '[' n = y ']'
+ case "$CUEREADERSYNTAX" in
+ CUEREADEROPTS=/dev/cdrom
+ CUEREADER=mkcue
+ case "$CDDBTOOL" in
+ '[' X = Xogg ']'
+ '[' 10 ']'
+ ENCNICE='-n 10'
+ '[' 10 ']'
+ READNICE='-n 10'
+ '[' 10 ']'
+ DISTMP3NICE='-n 10'
+ '[' '' ']'
+ '[' n = y ']'
+ '[' y = y ']'
+ NEEDEJECT=y
+ '[' '!' y = n ']'
+ '[' y = y ']'
+ case $CDDBMETHOD in
+ '[' n = y ']'
+ '[' X '!=' X ']'
+ '[' '' = y ']'
+ PIPERIPPER_cdparanoia=-
+ PIPERIPPER_libcdio=-
+ PIPERIPPER_cdda2wav=-
+ PIPERIPPER_debug=-
+ PIPERIPPER_flac='-c '
+ PIPERIPPER_pird=-
+ PIPE_mp3enc=-sti
+ PIPE_lame=-
+ PIPE_bladeenc=stdin
+ PIPE_oggenc=-
+ PIPE_opusenc=-
+ PIPE_flac=-
+ PIPE_speexenc=-
+ PIPE_mpcenc=-
+ PIPE_wavpack=-
+ PIPE_faac=-
+ PIPE_qaac=-
+ PIPE_fhgaacenc=-
+ PIPE_ffmpeg=-
+ PIPE_tta=-
+ PIPE_ttaenc=-
+ PIPE_neroAacEnc=-
+ PIPE_fdkaac=-
+ '[' '' = y ']'
+ for X in $CDROMREADER $CDDISCID ${NEEDTAGGER+$TAGGER} $MP3ENCODER $OGGENCODER 
$OPUSENCODER $MKAENCODER $FLACENCODER $SPEEXENCODER $MPCENCODER $AACENCODER 
$WVENCODER $CDDBTOOL $APENCODER $MP2ENCODER $TTAENCODER $AIFFENCODER 
${NEEDHTTPGET+$HTTPGET} ${NEEDDISTMP3+$DISTMP3} ${NEEDCOMMENTER+$VORBISCOMMENT} 
${NEEDMETAFLAC+$METAFLAC} ${NEEDNORMALIZER+$NORMALIZER} ${NEEDEJECT+$EJECT} 
${NEEDDISKUTIL+diskutil} ${NEEDCDSPEED+$CDSPEED} ${NEEDVORBISGAIN+$VORBISGAIN} 

Bug#905177: bind9: prompting due to modified conffiles which were not modified by the user: /etc/bind/named.conf.options

[Bernhard Schmidt]

Am 01.08.2018 um 12:00 schrieb Andreas Beckmann:

Hi,
I can reproduce this in a container upgrading Stretch to Buster.

Configuration file '/etc/bind/named.conf.options'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** named.conf.options (Y/I/N/O/D/Z) [default=N] ? d
--- /etc/bind/named.conf.options2018-08-01 15:40:01.840772576 +
+++ /etc/bind/named.conf.options.dpkg-new   2018-07-16
18:49:50.0 +
@@ -20,7 +20,5 @@

//
dnssec-validation auto;

-   auth-nxdomain no;# conform to RFC1035
listen-on-v6 { any; };
 };
-


AFAICT this is caused by the version in Stretch, which did not ship
/etc7bind/named.conf.options at all, but created it in postinst

===
if [ -f /etc/bind/named.conf.options ]; then
[...]

else
cp /usr/share/bind9/named.conf.options
/etc/bind/named.conf.options
chmod 644 /etc/bind/named.conf.options
fi
===

So the file is there and not marked as conffile, because it has been
created in postinst. Now in Buster the file is properly shipped as
conffile (since commit 9ddbb41a71236815d246180b454850ec4ef7862d,
included in 9.11.2+dfsg-6.

It is only appearing now because the named.conf.options has now been
changed from the version contained in Stretch in 9.11.4+dfsg-2. But the
underlying bug is in Stretch.

I have no idea how to properly deal with this.

Best Regards,
Bernhard

Bug#905229: python3-stem: missing Depends: python3-distutils

[Andreas Beckmann]

Package: python3-stem
Version: 1.6.0-3
Severity: serious
Control: affects -1 onionshare

$ onionshare
Traceback (most recent call last):
  File "/usr/bin/onionshare", line 21, in 
import onionshare
  File "/usr/lib/python3/dist-packages/onionshare/__init__.py", line 24, in 

from .onion import *
  File "/usr/lib/python3/dist-packages/onionshare/onion.py", line 21, in 

from stem.control import Controller
  File "/usr/lib/python3/dist-packages/stem/control.py", line 265, in 
import stem.descriptor.microdescriptor
  File "/usr/lib/python3/dist-packages/stem/descriptor/__init__.py", line 55, 
in 
import stem.util.system
  File "/usr/lib/python3/dist-packages/stem/util/system.py", line 70, in 

import distutils.spawn
ModuleNotFoundError: No module named 'distutils.spawn'


Andreas

Bug#905223: python-rosgraph: /usr/bin/rosgraph fails to run: ImportError: No module named rospkg

[Andreas Beckmann]

Package: python-rosgraph
Version: 1.14.2+ds1-4
Severity: serious

$ /usr/bin/rosgraph
Traceback (most recent call last):
  File "/usr/bin/rosgraph", line 36, in 
import rosgraph.rosgraph_main
  File "/usr/lib/python2.7/dist-packages/rosgraph/rosgraph_main.py", line 39, 
in 
from . import roslogging
  File "/usr/lib/python2.7/dist-packages/rosgraph/roslogging.py", line 46, in 

import rospkg
ImportError: No module named rospkg


Andreas

Bug#902788: python3.7: needs Breaks for software/modules broken by 3.7 ("async" became a reserved keyword)

[Andreas Beckmann]

Followup-For: Bug #902788

Hi,

Breaks are missing against

* python3-pyatspi (<= 2.26.0+dfsg-1)#902989


Andreas

Bug#905210: marked as done (golang-github-pzhin-go-sophia: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Wed, 01 Aug 2018 15:19:05 +
with message-id 
and subject line Bug#905210: fixed in golang-github-pzhin-go-sophia 
0.0~git20180715.8bdc218-2
has caused the Debian Bug report #905210,
regarding golang-github-pzhin-go-sophia: 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.)


-- 
905210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-pzhin-go-sophia
Version: 0.0~git20180715.8bdc218-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Sascha Steinbiss , 
ftpmas...@debian.org

Hi,

I just ACCEPTed golang-github-pzhin-go-sophia from NEW but noticed it 
was missing attribution in debian/copyright for at least sophia.c.

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: golang-github-pzhin-go-sophia
Source-Version: 0.0~git20180715.8bdc218-2

We believe that the bug you reported is fixed in the latest version of
golang-github-pzhin-go-sophia, which is due to be installed in the Debian FTP 
archive.

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

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

Debian distribution maintenance software
pp.
Sascha Steinbiss  (supplier of updated 
golang-github-pzhin-go-sophia 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: Wed, 01 Aug 2018 16:49:33 +0200
Source: golang-github-pzhin-go-sophia
Binary: golang-github-pzhin-go-sophia-dev
Architecture: source all
Version: 0.0~git20180715.8bdc218-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Sascha Steinbiss 
Description:
 golang-github-pzhin-go-sophia-dev - Golang binding for the Sophia database
Closes: 905210
Changes:
 golang-github-pzhin-go-sophia (0.0~git20180715.8bdc218-2) unstable; 
urgency=medium
 .
   * Add missing copyright holders in d/copyright. Thanks to Chris Lamb for
 noticing this.
 Closes: #905210
Checksums-Sha1:
 1450a2e4a42ccdf75e7333414a962d8e2aa6366d 2416 
golang-github-pzhin-go-sophia_0.0~git20180715.8bdc218-2.dsc
 de4a52100c5c85ac3af580cbbbc396618e697323 2344 
golang-github-pzhin-go-sophia_0.0~git20180715.8bdc218-2.debian.tar.xz
 6520f81e6a4e45415755fe6b5412aa370e4a5e25 145604 
golang-github-pzhin-go-sophia-dev_0.0~git20180715.8bdc218-2_all.deb
 dce6ea8707e3bfd2bfba5ab37af84eda0e67f6db 6069 
golang-github-pzhin-go-sophia_0.0~git20180715.8bdc218-2_amd64.buildinfo
Checksums-Sha256:
 5053d8fe07add2e388b9d24b6c986fc86992eaf04e2316a56fc5b29b3de2b134 2416 
golang-github-pzhin-go-sophia_0.0~git20180715.8bdc218-2.dsc
 28efbab758f478a3b4b0f2ce11f74e019a58c7b29bdf625137ee8d5b7ac3ad5c 2344 
golang-github-pzhin-go-sophia_0.0~git20180715.8bdc218-2.debian.tar.xz
 2bd3cb18fb5ab82ce9e7abfcff0a3dabd1d0e89aadc078ae5b9b774771023f3f 145604 
golang-github-pzhin-go-sophia-dev_0.0~git20180715.8bdc218-2_all.deb
 fb1059ba5f8928aa6bdc68c6d24090a868fc655a938821537d50814031f70f74 6069 
golang-github-pzhin-go-sophia_0.0~git20180715.8bdc218-2_amd64.buildinfo
Files:
 545f6a67d22e1b775827c6fa8c0a3589 2416 devel optional 
golang-github-pzhin-go-sophia_0.0~git20180715.8bdc218-2.dsc
 a26fc2d706d79272552293397c743f4f 2344 devel optional 
golang-github-pzhin-go-sophia_0.0~git20180715.8bdc218-2.debian.tar.xz
 7ad2b1851b0237bdb6128049fa0833a4 145604 devel optional 
golang-github-pzhin-go-sophia-dev_0.0~git20180715.8bdc218-2_all.deb
 e4ec037c5cfc31e49be6ff8e7b982003 6069 devel optional 
golang-github-pzhin-go-sophia_0.0~git20180715.8bdc218-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEWzS6WqtVB+kDQm6F6NN64vCfSHIFAlthyUwACgkQ6NN64vCf
SHL6nxAAh7+isZ9+wxDVYrm7S+AAcsQUKhJC38+voVzgruAEyWrwpafY4K7D0CJK
9eCNkNuqVrlBXe6gg59o/0yLY7bxs7jjB/QD1jIkMbeUMbc3JCGY8nTwLGUbfBde
wt07DJt/SLddOAJ5/ENUuT5nWnJuZ2MvEvt5e4QPQtMAu9CIejj91rf4oNd0fdEt
Z/yC+eFiFO/2YhuNFAuO+rtekkokk47wEUmojOJT7b1EZE5CvBrnYCBl6TNlZZAV
MUJHWZJUdbClLDhR22/SZJP+JlwPhuEAaJu2o0L6jsUx2g4iYZLf5D+KFPTPejUC

Bug#905222: spambayes: several binaries fail to run: ImportError: cannot import name asyncore

[Andreas Beckmann]

Package: spambayes
Version: 1.1b1-4
Severity: serious

e.g.

$ /usr/bin/core_server
Traceback (most recent call last):
  File "/usr/bin/core_server", line 83, in 
from spambayes import Dibbler
  File "/usr/lib/python2.7/dist-packages/spambayes/Dibbler.py", line 186, in 

from spambayes import asyncore, asynchat
ImportError: cannot import name asyncore


Andreas

Processed: Re: python-django: CVE-2018-14574: Open redirect possibility in CommonMiddleware

[Debian Bug Tracking System]

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

> reassign 905218 src:python-django
Bug #905218 [python-django] python-django: CVE-2018-14574
Bug reassigned from package 'python-django' to 'src:python-django'.
No longer marked as found in versions 1.4.22-1+deb7u4.
Ignoring request to alter fixed versions of bug #905218 to the same values 
previously set
> forcemerge 905216 905218
Bug #905216 [src:python-django] python-django: CVE-2018-14574: Open redirect 
possibility in CommonMiddleware
Bug #905217 [src:python-django] python-django: Django security releases issued: 
2.0.8 and 1.11.15
Bug #905218 [src:python-django] python-django: CVE-2018-14574
Severity set to 'important' from 'grave'
Marked as found in versions python-django/1:1.11.14-1.
Added tag(s) upstream.
Bug #905217 [src:python-django] python-django: Django security releases issued: 
2.0.8 and 1.11.15
Merged 905216 905217 905218
> thanks
Stopping processing here.

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

Bug#905220: sssd-tools: /usr/sbin/sss_obfuscate fails to run: ImportError: No module named pysss

[Andreas Beckmann]

Package: sssd-tools
Version: 1.16.2-1
Severity: serious

# sss_obfuscate
Traceback (most recent call last):
  File "/usr/sbin/sss_obfuscate", line 8, in 
import pysss
ImportError: No module named pysss


Andreas

Bug#905218: python-django: CVE-2018-14574

[Chris Lamb]

Package: python-django
Version: 1.4.22-1+deb7u4
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for python-django.

CVE-2018-14574[0]:
Open redirect possibility in CommonMiddleware

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-14574
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14574


Regards,

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

Bug#905131: marked as done (dde-qt5integration: FTBFS on amd64 and mipsel)

[Debian Bug Tracking System]

Your message dated Wed, 01 Aug 2018 14:46:21 +
with message-id 
and subject line Bug#905131: fixed in dde-qt5integration 0.3.2-1
has caused the Debian Bug report #905131,
regarding dde-qt5integration: FTBFS on amd64 and mipsel
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.)


-- 
905131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905131
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dde-qt5integration
Version: 0.3.0-2
Severity: serious
Justification: FTBFS

Hi! During the ongoing Qt transition your package FTBFS on at least amd64 and 
mipsel.

It seems that it can not find local headers, which is strange.

Please take a look whenever possible.

Kinds regards, Lisandro.

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

Kernel: Linux 4.17.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: dde-qt5integration
Source-Version: 0.3.2-1

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

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

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

Debian distribution maintenance software
pp.
Yanhao Mo  (supplier of updated dde-qt5integration 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: Wed, 01 Aug 2018 11:23:53 +0800
Source: dde-qt5integration
Binary: dde-qt5integration
Architecture: source amd64
Version: 0.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Deepin Packaging Team 

Changed-By: Yanhao Mo 
Description:
 dde-qt5integration - Qt5 theme integration for Deepin application
Closes: 905131
Changes:
 dde-qt5integration (0.3.2-1) unstable; urgency=medium
 .
   * New upstream version 0.3.2 (Closes: #905131)
Checksums-Sha1:
 fb2ad30fa312bd49ac49089ee5ef08688c7facd2 2354 dde-qt5integration_0.3.2-1.dsc
 34a37a6b1763c46d3b223367c390fe606ea546e3 354714 
dde-qt5integration_0.3.2.orig.tar.gz
 cfc7c3640570909f9482e4d0314f4ff0ab7284b0 3360 
dde-qt5integration_0.3.2-1.debian.tar.xz
 8b9fed5f2d7424b0127c4615eb8ae2fc9ce448fc 6418164 
dde-qt5integration-dbgsym_0.3.2-1_amd64.deb
 21fb92aa0bc0886ed968d83b8a7cdc06d5ee0087 15217 
dde-qt5integration_0.3.2-1_amd64.buildinfo
 70658bf1e70cc527d0d8ccdfa3a7c60456645278 359780 
dde-qt5integration_0.3.2-1_amd64.deb
Checksums-Sha256:
 f26476a4be5fa7e5860f4a204b306dd62cc9e9247f2c4ff1bad253f728c60592 2354 
dde-qt5integration_0.3.2-1.dsc
 b64e1dde74b2756c9b3d0cb2b10e88cc8c81e305083a7b2423f6320b006e921d 354714 
dde-qt5integration_0.3.2.orig.tar.gz
 4c2d6fa514264924ea9efc2675c61086c0750330f738a24d738073d0b9e3f1cd 3360 
dde-qt5integration_0.3.2-1.debian.tar.xz
 c677d2dcf2bb17f699aad057714c04f9b86d6ca67246a29aa39a9fcafdea7eb2 6418164 
dde-qt5integration-dbgsym_0.3.2-1_amd64.deb
 5fa32af1da8a2d1ddf0f844e67a8c6c3d179c9f6af9663e1c21e871542a24443 15217 
dde-qt5integration_0.3.2-1_amd64.buildinfo
 0c6d34558d021cfa201db58696b20473ef11a056ed21af6a12e130b2232c9c1c 359780 
dde-qt5integration_0.3.2-1_amd64.deb
Files:
 e39783012bb10ebd6da7370b1ffc7ffd 2354 libs optional 
dde-qt5integration_0.3.2-1.dsc
 c828ab8dfca78981694d231e0b508043 354714 libs optional 
dde-qt5integration_0.3.2.orig.tar.gz
 f66224cabc625980792e712254b48f32 3360 libs optional 
dde-qt5integration_0.3.2-1.debian.tar.xz
 63a55d53da0f92445cabec5de9bb6814 6418164 debug optional 
dde-qt5integration-dbgsym_0.3.2-1_amd64.deb
 3528919b07ee2a4bb1d3deb57966b1e3 15217 libs optional 
dde-qt5integration_0.3.2-1_amd64.buildinfo
 bbeed8dceb55bbef3ae732a761234147 359780 libs optional 
dde-qt5integration_0.3.2-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEb9bJQfCTGv6uM2+ujv2XAviIsq4FAlthwaYTHHlhbmhhb2Nz
QGdtYWlsLmNvbQAKCRCO/ZcC+IiyruYTEACF2uujNoiTV/Ez+1nwaHNzWFeebwFI

Bug#905215: CVE-2018-2941

[Moritz Muehlenhoff]

Source: openjfx
Severity: grave
Tags: security

http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html
fixed CVE-2018-2941 in JavaFX, which should affect our openjfx package.

Cheers,
Moritz

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

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#905214: isc-kea: Incomplete debian/copyright?

[Chris Lamb]

Source: isc-kea
Version: 1.4.0.P1-3
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: Ondřej Surý , ftpmas...@debian.org

Hi,

I just ACCEPTed isc-kea from NEW but noticed it was missing 
attribution in debian/copyright for at least the files under
src/lib/dhcpsrv/benchmarks.

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#905213: python3-pyghmi: fails to install with Python 3.7

[Andreas Beckmann]

Package: python3-pyghmi
Version: 1.0.32-4
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-pyghmi (1.0.32-4) ...
File "/usr/lib/python3/dist-packages/pyghmi/ipmi/private/session.py", line 
502
  self.async = False
   ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-pyghmi (--configure):
   installed python3-pyghmi package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   python3-pyghmi


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-pyghmi=1.0.32-4.log.gz
Description: application/gzip

Bug#905210: golang-github-pzhin-go-sophia: Incomplete debian/copyright?

[Chris Lamb]

Source: golang-github-pzhin-go-sophia
Version: 0.0~git20180715.8bdc218-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Sascha Steinbiss , 
ftpmas...@debian.org

Hi,

I just ACCEPTed golang-github-pzhin-go-sophia from NEW but noticed it 
was missing attribution in debian/copyright for at least sophia.c.

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#897792: marked as done (libqaccessibilityclient: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Wed, 01 Aug 2018 14:11:16 +
with message-id 
and subject line Bug#897792: fixed in libqaccessibilityclient 0.2.0-1
has caused the Debian Bug report #897792,
regarding libqaccessibilityclient: 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.)


-- 
897792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897792
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libqaccessibilityclient
Version: 0.1.1-5
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/libqaccessibilityclient_0.1.1-5_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[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++  
-DQACCESSIBILITYCLIENT_LIBRARY -DQT_CORE_LIB -DQT_GUI_LIB 
-DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG 
-DQT_USE_FAST_CONCATENATION -DQT_USE_FAST_OPERATOR_PLUS 
-Dqaccessibilityclient_EXPORTS 
-I/<>/obj-x86_64-linux-gnu/src/qaccessibilityclient_autogen/include
 -I/<>/obj-x86_64-linux-gnu -I/<> -isystem 
/usr/include/qt4 -isystem /usr/include/qt4/QtGui -isystem 
/usr/include/qt4/QtCore -I/usr/include/qt4/QtDBus 
-I/<>/obj-x86_64-linux-gnu/src -I/<>/src  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fvisibility-inlines-hidden 
-Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -fPIC   -o 
CMakeFiles/qaccessibilityclient.dir/qaccessibilityclient/registry.cpp.o -c 
/<>/src/qaccessibilityclient/registry.cpp
In file included from /<>/src/qaccessibilityclient/registry.h:27,
 from /<>/src/qaccessibilityclient/registry.cpp:21:
/<>/src/qaccessibilityclient/accessibleobject.h:718:81: error: 
'QDebug QAccessibleClient::operator<<(QDebug, const 
QAccessibleClient::AccessibleObject&)' should have been declared inside 
'QAccessibleClient'
 friend QDebug QAccessibleClient::operator<<(QDebug, const AccessibleObject 
&);

 ^
In file included from /<>/src/qaccessibilityclient/registry_p.h:38,
 from /<>/src/qaccessibilityclient/registry.cpp:22:
/<>/src/qaccessibilityclient/cachestrategy_p.h: In member function 
'virtual bool QAccessibleClient::CacheWeakStrategy::remove(const QString&)':
/<>/src/qaccessibilityclient/cachestrategy_p.h:59:5: warning: no 
return statement in function returning non-void [-Wreturn-type]
 }
 ^
/<>/src/qaccessibilityclient/cachestrategy_p.h: In member function 
'virtual bool QAccessibleClient::CacheStrongStrategy::remove(const QString&)':
/<>/src/qaccessibilityclient/cachestrategy_p.h:100:5: warning: no 
return statement in function returning non-void [-Wreturn-type]
 }
 ^
make[3]: *** [src/CMakeFiles/qaccessibilityclient.dir/build.make:92: 
src/CMakeFiles/qaccessibilityclient.dir/qaccessibilityclient/registry.cpp.o] 
Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++  
-DQACCESSIBILITYCLIENT_LIBRARY -DQT_CORE_LIB -DQT_GUI_LIB 
-DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG 
-DQT_USE_FAST_CONCATENATION -DQT_USE_FAST_OPERATOR_PLUS 
-Dqaccessibilityclient_EXPORTS 
-I/<>/obj-x86_64-linux-gnu/src/qaccessibilityclient_autogen/include
 -I/<>/obj-x86_64-linux-gnu -I/<> -isystem 
/usr/include/qt4 -isystem /usr/include/qt4/QtGui -isystem 
/usr/include/qt4/QtCore -I/usr/include/qt4/QtDBus 
-I/<>/obj-x86_64-linux-gnu/src -I/<>/src  -g -O2 

Bug#905208: emms: fails to upgrade from 'stretch': emms-setup.el:98:15:Error: Cannot open load file: No such file or directory, seq

[Andreas Beckmann]

Package: emms
Version: 5.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails.

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

  Setting up emms (5.0-1) ...
  Install emacsen-common for emacs24
  emacsen-common: Handling install of emacsen flavor emacs24
  Wrote /etc/emacs24/site-start.d/00debian-vars.elc
  Wrote /usr/share/emacs24/site-lisp/debian-startup.elc
  Install emms for emacs24
  install/emms: byte-compiling for emacs24, logging in /tmp/elc.Rs5KQDTWAN3v
  ERROR: install script from emms package failed
  dpkg: error processing package emms (--configure):
   installed emms package post-installation script subprocess returned error 
exit status 1
  Setting up libtagc0:amd64 (1.11.1+dfsg.1-0.2+b1) ...
  Setting up librsvg2-2:amd64 (2.40.20-2) ...
  Setting up librsvg2-common:amd64 (2.40.20-2) ...
  Setting up adwaita-icon-theme (3.28.0-1) ...
  Setting up libgtk-3-0:amd64 (3.22.30-2) ...
  Setting up emacs25 (25.2+1-6+b2) ...
  update-alternatives: using /usr/bin/emacs25-x to provide /usr/bin/emacs 
(emacs) in auto mode
  Install emacsen-common for emacs25
  emacsen-common: Handling install of emacsen flavor emacs25
  Install emms for emacs25
  install/emms: byte-compiling for emacs25, logging in /tmp/elc.Mo5TKnEAl1mc
  install/emms: deleting /tmp/elc.Mo5TKnEAl1mc
  Setting up emacs (47.0) ...
  Processing triggers for libc-bin (2.27-5) ...
  Processing triggers for systemd (239-7) ...
  Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.11-2) ...
  Errors were encountered while processing:
   emms

The emacs24 logfile contains:

Loading 00debian-vars...
Loading /etc/emacs/site-start.d/50emms.el (source)...
Wrote /usr/share/emacs24/site-lisp/emms/emms-auto.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-bookmarks.elc

In toplevel form:
emms-browser.el:292:1:Error: Cannot open load file: No such file or directory, 
seq
Wrote /usr/share/emacs24/site-lisp/emms/emms-cache.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-compat.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-cue.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-history.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-i18n.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-info-libtag.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-info-metaflac.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-info-mp3info.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-info-ogginfo.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-info-opusinfo.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-info.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-last-played.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-librefm-scrobbler.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-librefm-stream.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-lyrics.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-maint.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-mark.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-metaplaylist-mode.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-mode-line-icon.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-mode-line.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-player-mpd.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-player-mpg321-remote.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-player-mplayer.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-player-mpv.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-player-simple.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-player-vlc.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-player-xine.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-playing-time.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-playlist-limit.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-playlist-mode.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-playlist-sort.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-score.elc

In toplevel form:
emms-setup.el:98:15:Error: Cannot open load file: No such file or directory, seq
Wrote /usr/share/emacs24/site-lisp/emms/emms-show-all.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-source-file.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-source-playlist.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-stream-info.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-streams.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-tag-editor.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-url.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-volume-amixer.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-volume-pulse.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms-volume.elc
Wrote /usr/share/emacs24/site-lisp/emms/emms.elc
Wrote /usr/share/emacs24/site-lisp/emms/jack.elc
Wrote /usr/share/emacs24/site-lisp/emms/later-do.elc


cheers,

Andreas


emms_5.0-1.log.gz
Description: application/gzip

Bug#905207: fabio-viewer,python-fabio: both ship usr/share/doc/python-fabio-doc/html/_static/mathjax

[Andreas Beckmann]

Package: fabio-viewer,python-fabio
Version: 0.7.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package python-fabio.
  Preparing to unpack .../18-python-fabio_0.7.0+dfsg-1_amd64.deb ...
  Unpacking python-fabio (0.7.0+dfsg-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-YgDMUP/18-python-fabio_0.7.0+dfsg-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/doc/python-fabio-doc/html/_static/mathjax', 
which is also in package fabio-viewer 0.7.0+dfsg-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-YgDMUP/18-python-fabio_0.7.0+dfsg-1_amd64.deb


cheers,

Andreas


fabio-viewer=0.7.0+dfsg-1_python-fabio=0.7.0+dfsg-1.log.gz
Description: application/gzip

Processed: affects 905146, user debian...@lists.debian.org, usertagging 901632, usertagging 902445 ...

[Debian Bug Tracking System]

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

> affects 905146 + libpqxx-dev
Bug #905146 [libpqxx-6.2] libpqxx-6.2: missing Breaks+Replaces: libpqxx6 (>= 
6.2)
Added indication that 905146 affects libpqxx-dev
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 901632 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 902445 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 905148 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 902729 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 902729 + libmariadb-dev neko
Bug #902729 [libmariadb3] Missing Conflicts with libmariadb2
Added indication that 902729 affects libmariadb-dev and neko
> affects 903450 + veusz
Bug #903450 [python3-veusz] python3-veusz: fails to upgrade from 'testing' - 
trying to overwrite /usr/share/veusz/VERSION
Added indication that 903450 affects veusz
> found 864280 3.mct+dfsg.121022-11
Bug #864280 [liboasis3-0d] liboasis3-0d: does not ship SONAME link
Marked as found in versions oasis3/3.mct+dfsg.121022-11.
> affects 864280 + liboasis3-dev
Bug #864280 [liboasis3-0d] liboasis3-0d: does not ship SONAME link
Added indication that 864280 affects liboasis3-dev
> thanks
Stopping processing here.

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

Bug#897338: sddm: Cannot launch SDDM at boot time and from console

[Boris Pek]

Hi,

> Hi, I am on Debian Unstable on real hardware and I have the same problem,
> SDDM launches but there is dark screen on TTY7 with only my mouse.

Try instructions from Debian wiki [1]. They solved this problem for NVIDIA
GeForce GTX 1050 Ti Mobile on my laptop.

[1] https://wiki.debian.org/NvidiaGraphicsDrivers/Optimus

Best wishes,
Boris

Bug#905196: Properly reassign bug (pike8.0-web-sass: Previous binary upload on amd64 linked against dropped libsass0, blocking transition, needs rebuild)

[Boyuan Yang]

Control: reassign -1 pike8.0-web-sass

Re-assigning the bug to the correct package.

--
Regards,
Boyuan Yang

Processed: Bug#905196: Properly reassign bug (pike8.0-web-sass: Previous binary upload on amd64 linked against dropped libsass0, blocking transition, needs rebuild)

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 pike8.0-web-sass
Bug #905196 [pick8.0-web-sass] pike8.0-web-sass: Previous binary upload on 
amd64 linked against dropped libsass0, blocking transition, needs rebuild
Warning: Unknown package 'pick8.0-web-sass'
Bug reassigned from package 'pick8.0-web-sass' to 'pike8.0-web-sass'.
No longer marked as found in versions 8.0.610-1.
Ignoring request to alter fixed versions of bug #905196 to the same values 
previously set

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

Bug#905201: libgeda-dev,geda-doc,geda: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: libgeda-dev,geda-doc,geda
Version: 1:1.8.2-8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  stretch -> buster

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

1m21.2s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libgeda-dev/HACKING (libgeda-dev) != 
/usr/share/doc/libgeda-common/HACKING (?)
/usr/share/doc/libgeda-dev -> libgeda-common
  /usr/share/doc/libgeda-dev/changelog.Debian.gz (libgeda-dev) != 
/usr/share/doc/libgeda-common/changelog.Debian.gz (libgeda-common)
/usr/share/doc/libgeda-dev -> libgeda-common
  /usr/share/doc/libgeda-dev/changelog.gz (libgeda-dev) != 
/usr/share/doc/libgeda-common/changelog.gz (libgeda-common)
/usr/share/doc/libgeda-dev -> libgeda-common
  /usr/share/doc/libgeda-dev/copyright (libgeda-dev) != 
/usr/share/doc/libgeda-common/copyright (libgeda-common)
/usr/share/doc/libgeda-dev -> libgeda-common

0m52.4s INFO: dirname part contains a symlink:
  /usr/share/doc/geda/AUTHORS (geda-doc) != /usr/share/doc/geda-doc/AUTHORS (?)
/usr/share/doc/geda -> geda-doc
  /usr/share/doc/geda/NEWS.gz (geda-doc) != /usr/share/doc/geda-doc/NEWS.gz (?)
/usr/share/doc/geda -> geda-doc


cheers,

Andreas


libgeda-dev_1:1.8.2-8.log.gz
Description: application/gzip

Bug#905045: marked as done (erlang-dev: broken symlinks: /usr/lib/libic.a /usr/include/ic.h /usr/include/erlang.idl)

[Debian Bug Tracking System]

Your message dated Wed, 01 Aug 2018 12:35:35 +
with message-id 
and subject line Bug#905045: fixed in erlang 1:21.0.4+dfsg-1~exp1
has caused the Debian Bug report #905045,
regarding erlang-dev: broken symlinks: /usr/lib/libic.a /usr/include/ic.h 
/usr/include/erlang.idl
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.)


-- 
905045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: erlang-dev
Version: 1:21.0.3+dfsg-1~exp1
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...):

0m33.7s ERROR: FAIL: Broken symlinks:
  /usr/lib/libic.a -> erlang/usr/lib/libic.a
  /usr/include/ic.h -> ../lib/erlang/usr/include/ic.h
  /usr/include/erlang.idl -> ../lib/erlang/usr/include/erlang.idl

cheers,

Andreas


erlang-dev_1:21.0.3+dfsg-1~exp1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: erlang
Source-Version: 1:21.0.4+dfsg-1~exp1

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

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

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

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated erlang 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: Wed, 01 Aug 2018 14:45:50 +0300
Source: erlang
Binary: erlang-base erlang-base-hipe erlang-asn1 erlang-common-test 
erlang-crypto erlang-debugger erlang-dialyzer erlang-diameter erlang-doc 
erlang-edoc erlang-eldap erlang-erl-docgen erlang-et erlang-eunit erlang-ftp 
erlang-inets erlang-manpages erlang-megaco erlang-mnesia erlang-observer 
erlang-odbc erlang-os-mon erlang-parsetools erlang-public-key erlang-reltool 
erlang-runtime-tools erlang-snmp erlang-ssh erlang-ssl erlang-syntax-tools 
erlang-tftp erlang-tools erlang-wx erlang-xmerl erlang-dev erlang-src 
erlang-examples erlang-jinterface erlang-mode erlang-nox erlang-x11 erlang
Architecture: source amd64 all
Version: 1:21.0.4+dfsg-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Erlang Packagers 
Changed-By: Sergei Golovan 
Description:
 erlang - Concurrent, real-time, distributed functional language
 erlang-asn1 - Erlang/OTP modules for ASN.1 support
 erlang-base - Erlang/OTP virtual machine and base applications
 erlang-base-hipe - Erlang/OTP HiPE enabled virtual machine and base 
applications
 erlang-common-test - Erlang/OTP application for automated testing
 erlang-crypto - Erlang/OTP cryptographic modules
 erlang-debugger - Erlang/OTP application for debugging and testing
 erlang-dev - Erlang/OTP development libraries and headers
 erlang-dialyzer - Erlang/OTP discrepancy analyzer application
 erlang-diameter - Erlang/OTP implementation of RFC 6733 protocol
 erlang-doc - Erlang/OTP HTML/PDF documentation
 erlang-edoc - Erlang/OTP module for generating documentation
 erlang-eldap - Erlang/OTP LDAP library
 erlang-erl-docgen - Erlang/OTP documentation stylesheets
 erlang-et  - Erlang/OTP event tracer application
 erlang-eunit - Erlang/OTP module for unit testing
 erlang-examples - Erlang/OTP application examples
 erlang-ftp - Erlang/OTP FTP client
 erlang-inets - Erlang/OTP Internet clients and servers
 erlang-jinterface - Java communication tool to Erlang
 erlang-manpages - Erlang/OTP manual pages
 erlang-megaco - Erlang/OTP implementation of Megaco/H.248 protocol
 erlang-mnesia - Erlang/OTP distributed relational/object hybrid database
 erlang-mode - Erlang major editing mode for Emacs
 erlang-nox - Erlang/OTP applications that don't require X Window System
 erlang-observer - Erlang/OTP application for investigating distributed systems
 erlang-odbc - Erlang/OTP interface to SQL databases
 erlang-os-mon - Erlang/OTP operating system monitor
 erlang-parsetools - Erlang/OTP parsing tools
 erlang-public-key - Erlang/OTP public key infrastructure
 erlang-reltool - Erlang/OTP release management tool
 erlang-runtime-tools - Erlang/OTP runtime tracing/debugging tools
 erlang-snmp 

Bug#905200: natpmp-utils,libnatpmp-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: natpmp-utils,libnatpmp-dev
Version: 20150609-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  stretch -> buster

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m28.4s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/natpmp-utils/changelog.Debian.gz (natpmp-utils) != 
/usr/share/doc/libnatpmp1/changelog.Debian.gz (libnatpmp1)
/usr/share/doc/natpmp-utils -> libnatpmp1
  /usr/share/doc/natpmp-utils/changelog.gz (natpmp-utils) != 
/usr/share/doc/libnatpmp1/changelog.gz (libnatpmp1)
/usr/share/doc/natpmp-utils -> libnatpmp1
  /usr/share/doc/natpmp-utils/copyright (natpmp-utils) != 
/usr/share/doc/libnatpmp1/copyright (libnatpmp1)
/usr/share/doc/natpmp-utils -> libnatpmp1

0m27.9s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libnatpmp-dev/changelog.Debian.gz (libnatpmp-dev:amd64) != 
/usr/share/doc/libnatpmp1/changelog.Debian.gz (libnatpmp1)
/usr/share/doc/libnatpmp-dev -> libnatpmp1
  /usr/share/doc/libnatpmp-dev/changelog.gz (libnatpmp-dev:amd64) != 
/usr/share/doc/libnatpmp1/changelog.gz (libnatpmp1)
/usr/share/doc/libnatpmp-dev -> libnatpmp1
  /usr/share/doc/libnatpmp-dev/copyright (libnatpmp-dev:amd64) != 
/usr/share/doc/libnatpmp1/copyright (libnatpmp1)
/usr/share/doc/libnatpmp-dev -> libnatpmp1


cheers,

Andreas


natpmp-utils_20150609-4.log.gz
Description: application/gzip

Bug#905198: python-ldap-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: python-ldap-dbg
Version: 3.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  stretch -> buster

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m38.4s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/python-ldap-dbg/changelog.Debian.amd64.gz (python-ldap-dbg) != 
/usr/share/doc/python-ldap/changelog.Debian.amd64.gz (python-ldap:amd64)
/usr/share/doc/python-ldap-dbg -> python-ldap
  /usr/share/doc/python-ldap-dbg/changelog.Debian.gz (python-ldap-dbg) != 
/usr/share/doc/python-ldap/changelog.Debian.gz (python-ldap:amd64)
/usr/share/doc/python-ldap-dbg -> python-ldap
  /usr/share/doc/python-ldap-dbg/changelog.gz (python-ldap-dbg) != 
/usr/share/doc/python-ldap/changelog.gz (python-ldap:amd64)
/usr/share/doc/python-ldap-dbg -> python-ldap
  /usr/share/doc/python-ldap-dbg/copyright (python-ldap-dbg) != 
/usr/share/doc/python-ldap/copyright (python-ldap:amd64)
/usr/share/doc/python-ldap-dbg -> python-ldap


cheers,

Andreas


python-ldap-dbg_3.1.0-1+b1.log.gz
Description: application/gzip

Bug#905196: pike8.0-web-sass: Previous binary upload on amd64 linked against dropped libsass0, blocking transition, needs rebuild

[Boyuan Yang]

Package: pick8.0-web-sass
Version: 8.0.610-1
Severity: serious
Control: affects -1 + libsass1

Dear pike8.0 maintainer,

Your previous upload pike8.0 8.0.610-1 was not a source-only upload
[1], which brings binary packages for amd64 architecture onto the
Archive. However, it was built against the old libsass source and
pike8.0-web-sass is linked against the old libsass0 library, which
should now be removed from the Archive.

Please consider making another upload to make sure that pike8.0 is
built against new libsass / libsass1 library. BinNMU might be
applicable but considering that the Testing migration is already
blocked by some other problems [2], it might be better to fix the
problem together with another upload.

--
Regards,
Boyuan Yang

[1] https://tracker.debian.org/news/969383
[2] https://qa.debian.org/excuses.php?package=pike8.0

Bug#905197: libcue-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: libcue-dev
Version: 2.2.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  stretch -> buster

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m28.7s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libcue-dev/changelog.Debian.gz (libcue-dev:amd64) != 
/usr/share/doc/libcue1/changelog.Debian.gz (libcue1)
/usr/share/doc/libcue-dev -> libcue1
  /usr/share/doc/libcue-dev/changelog.gz (libcue-dev:amd64) != 
/usr/share/doc/libcue1/changelog.gz (libcue1)
/usr/share/doc/libcue-dev -> libcue1
  /usr/share/doc/libcue-dev/copyright (libcue-dev:amd64) != 
/usr/share/doc/libcue1/copyright (libcue1)
/usr/share/doc/libcue-dev -> libcue1


cheers,

Andreas


libcue-dev_2.2.1-1.log.gz
Description: application/gzip

Processed: pike8.0-web-sass: Previous binary upload on amd64 linked against dropped libsass0, blocking transition, needs rebuild

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libsass1
Bug #905196 [pick8.0-web-sass] pike8.0-web-sass: Previous binary upload on 
amd64 linked against dropped libsass0, blocking transition, needs rebuild
Warning: Unknown package 'pick8.0-web-sass'
Added indication that 905196 affects libsass1
Warning: Unknown package 'pick8.0-web-sass'

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

Bug#905195: e2fslibs-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: e2fslibs-dev
Version: 1.44.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  stretch -> buster

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m30.5s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/e2fslibs-dev/changelog.Debian.gz (e2fslibs-dev) != 
/usr/share/doc/e2fslibs/changelog.Debian.gz (e2fslibs:amd64)
/usr/share/doc/e2fslibs-dev -> e2fslibs
  /usr/share/doc/e2fslibs-dev/copyright (e2fslibs-dev) != 
/usr/share/doc/e2fslibs/copyright (e2fslibs:amd64)
/usr/share/doc/e2fslibs-dev -> e2fslibs


cheers,

Andreas


e2fslibs-dev_1.44.3-1.log.gz
Description: application/gzip

Bug#905193: alot-doc: unhandled symlink to directory conversion: /usr/share/doc/alot/html -> ../alot-doc/html

[Andreas Beckmann]

Package: alot-doc
Version: 0.7-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  stretch -> buster

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m29.5s INFO: dirname part contains a symlink:
  /usr/share/doc/alot/html/_sources (alot-doc) != 
/usr/share/doc/alot-doc/html/_sources (?)
/usr/share/doc/alot/html -> ../alot-doc/html
  /usr/share/doc/alot/html/_sources/api (alot-doc) != 
/usr/share/doc/alot-doc/html/_sources/api (?)
/usr/share/doc/alot/html -> ../alot-doc/html
  /usr/share/doc/alot/html/_sources/api/commands.rst.txt (alot-doc) != 
/usr/share/doc/alot-doc/html/_sources/api/commands.rst.txt (?)
/usr/share/doc/alot/html -> ../alot-doc/html
  /usr/share/doc/alot/html/_sources/api/contributing.rst.txt (alot-doc) != 
/usr/share/doc/alot-doc/html/_sources/api/contributing.rst.txt (?)
/usr/share/doc/alot/html -> ../alot-doc/html
  /usr/share/doc/alot/html/_sources/api/crypto.rst.txt (alot-doc) != 
/usr/share/doc/alot-doc/html/_sources/api/crypto.rst.txt (?)
/usr/share/doc/alot/html -> ../alot-doc/html
  /usr/share/doc/alot/html/_sources/api/database.rst.txt (alot-doc) != 
/usr/share/doc/alot-doc/html/_sources/api/database.rst.txt (?)
/usr/share/doc/alot/html -> ../alot-doc/html
  /usr/share/doc/alot/html/_sources/api/index.rst.txt (alot-doc) != 
/usr/share/doc/alot-doc/html/_sources/api/index.rst.txt (?)
/usr/share/doc/alot/html -> ../alot-doc/html
[...]
  /usr/share/doc/alot/html/usage/modes/search.html (alot-doc) != 
/usr/share/doc/alot-doc/html/usage/modes/search.html (?)
/usr/share/doc/alot/html -> ../alot-doc/html
  /usr/share/doc/alot/html/usage/modes/taglist.html (alot-doc) != 
/usr/share/doc/alot-doc/html/usage/modes/taglist.html (?)
/usr/share/doc/alot/html -> ../alot-doc/html
  /usr/share/doc/alot/html/usage/modes/thread.html (alot-doc) != 
/usr/share/doc/alot-doc/html/usage/modes/thread.html (?)
/usr/share/doc/alot/html -> ../alot-doc/html
  /usr/share/doc/alot/html/usage/signals.html (alot-doc) != 
/usr/share/doc/alot-doc/html/usage/signals.html (?)
/usr/share/doc/alot/html -> ../alot-doc/html
  /usr/share/doc/alot/html/usage/synopsis.html (alot-doc) != 
/usr/share/doc/alot-doc/html/usage/synopsis.html (?)
/usr/share/doc/alot/html -> ../alot-doc/html


This is probably caused by a behavioral change of dh_installdocs
in debhelper compat level 11.


cheers,

Andreas


alot-doc_0.7-1.log.gz
Description: application/gzip

Bug#905191: libecm1-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: libecm1-dev
Version: 7.0.4+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  stretch -> buster

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m29.3s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libecm1-dev/AUTHORS (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/AUTHORS (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/NEWS.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/NEWS.gz (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/README.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/README.gz (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/README.lib.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/README.lib.gz (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/changelog.Debian.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/changelog.Debian.gz (libecm1-dev-common)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/changelog.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/changelog.gz (libecm1-dev-common)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/copyright (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/copyright (libecm1-dev-common)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/examples (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/examples (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/examples/Makefile (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/examples/Makefile (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/examples/ecmfactor.c (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/examples/ecmfactor.c (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common


cheers,

Andreas


libecm1-dev_7.0.4+ds-2.log.gz
Description: application/gzip

Processed: cryptsetup-initramfs: fails to install, remove, distupgrade, and install again

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + cryptsetup
Bug #905188 [cryptsetup-initramfs] cryptsetup-initramfs: fails to install, 
remove, distupgrade, and install again
Added indication that 905188 affects cryptsetup

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

Bug#905188: cryptsetup-initramfs: fails to install, remove, distupgrade, and install again

[Andreas Beckmann]

Package: cryptsetup-initramfs
Version: 2:2.0.3-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + cryptsetup

Hi,

during a test with piuparts I noticed your package cryptsetup failed to
install (in 'stretch'), remove (but not purge), distupgrade to 'buster',
and install again.
Before the second installation the package is in config-files-remaining
state. The configuration is remaining from the last version that was
successfully configured - which is from the previous release.

The problem shows up in cryptsetup-initramfs, which prompts about a
deleted conffile, which was not deleted by the user, but probably by a
buggy script in the old package.

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...):

  Setting up initramfs-tools-core (0.131) ...
  Setting up initramfs-tools (0.131) ...
  update-initramfs: deferring update (trigger activated)
  Setting up cryptsetup-initramfs (2:2.0.3-6) ...
  
  Configuration file '/etc/cryptsetup-initramfs/conf-hook'
   ==> Deleted (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** conf-hook (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package 
cryptsetup-initramfs (--configure):
   end of file on stdin at conffile prompt
  dpkg: dependency problems prevent configuration of cryptsetup:
   cryptsetup depends on cryptsetup-initramfs (>= 2:2.0.3-1); however:
Package cryptsetup-initramfs is not configured yet.
  
  dpkg: error processing package cryptsetup (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.27-5) ...
  Processing triggers for initramfs-tools (0.131) ...
  Errors were encountered while processing:
   cryptsetup-initramfs
   cryptsetup


cheers,

Andreas


cryptsetup_2:2.0.3-6.log.gz
Description: application/gzip

Bug#905185: Bug #905185 in libreoffice marked as pending

[Rene Engelhard]

Control: tag -1 pending

Hello,

Bug #905185 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/commit/cb6e12b34ac225685ff17017cc6116184d02061d


add Breaks/Replaces: libreoffice-common (<< 1:6.1.0~alpha1-1) to 
libreoffice-help-common (closes: #905185)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/905185

Processed: Bug #905185 in libreoffice marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #905185 [libreoffice-help-common] libreoffice-help-common: missing 
Breaks+Replaces: libreoffice-common (<< 1:6.1.0~alpha1-1)
Added tag(s) pending.

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

Bug#905186: uim-qt5-immodule: missing Breaks+Replaces: uim-qt5 (<< 1:1.8.6+gh20161003.0.d63dadd-5~exp1)

[Andreas Beckmann]

Package: uim-qt5-immodule
Version: 1:1.8.8-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package uim-qt5-immodule:amd64.
  Preparing to unpack .../32-uim-qt5-immodule_1%3a1.8.8-2_amd64.deb ...
  Unpacking uim-qt5-immodule:amd64 (1:1.8.8-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-sqVbwc/32-uim-qt5-immodule_1%3a1.8.8-2_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libuimplatforminputcontextplugin.so',
 which is also in package uim-qt5 1:1.8.6+gh20161003.0.d63dadd-2
  Preparing to unpack .../33-uim-qt5_1%3a1.8.8-2_amd64.deb ...
  Unpacking uim-qt5 (1:1.8.8-2) over (1:1.8.6+gh20161003.0.d63dadd-2) ...

The other *-immodule packages might have similar problems.


cheers,

Andreas


task-japanese-desktop_3.44.log.gz
Description: application/gzip

Bug#905185: libreoffice-help-common: missing Breaks+Replaces: libreoffice-common (<< 1:6.1.0~alpha1-1)

[Andreas Beckmann]

Package: libreoffice-help-common
Version: 1:6.1.0~rc2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libreoffice-help-common.
  Preparing to unpack .../02-libreoffice-help-common_1%3a6.1.0~rc2-3_all.deb ...
  Unpacking libreoffice-help-common (1:6.1.0~rc2-3) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-a0UQpU/02-libreoffice-help-common_1%3a6.1.0~rc2-3_all.deb 
(--unpack):
   trying to overwrite '/usr/share/libreoffice/help/idxcaption.xsl', which is 
also in package libreoffice-common 1:5.2.7-1+deb9u4
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

If I parsed the changelog correctly, libreoffice-help-common was
added in 1:6.1.0~alpha1-1


cheers,

Andreas


libreoffice-help-ca_1:6.1.0~rc2-3.log.gz
Description: application/gzip

Bug#905184: upgrade of 389-ds-base fails if /var/lib/dirsrv is on different partition as /etc

[Jan Kowalsky]

Package: 389-ds-base
Version: 1.3.5.17-2
Severity: serious

Upgrade to newer version of 389-ds-base fails with dpkg configuration
error on postinstall script /var/lib/dpkg/info/389-ds-base.postinst

After getting full log of postinstall I saw:

[18/08/01:10:33:37] - [Setup] Info Could not rename config file
'/etc/dirsrv/slapd-INSTANCE/slapd-collations.conf' to
'/var/lib/dirsrv/slapd-INSTANCE/bak.bak/slapd-collations.conf'.  Error:
Invalid cross-device link

This is caused by line 24:

setup-ds -l $OUT -u -s General.UpdateMode=offline > $OUT 2>&1

calling this directly we got the same failure.

The reason is that the script tries to make a backup of configuration
files in /var/lib/dirsrv/INSTANCE/bak.bak:


# these files are obsolete, or we want to replace
# them with newer versions
my @toremove = qw(slapd-collations.conf);

# make a backup directory to store the deleted config file, then
# don't really delete it, just move it to that directory
my $mode = (stat($inf->{slapd}->{config_dir}))[2];
my $bakdir = $inf->{slapd}->{bak_dir} . ".bak";
if (! -d $bakdir) {
$! = 0; # clear
mkdir $bakdir, $mode;
if ($!) {
return ('error_creating_directory', $bakdir, $!);
}
}

my @errs;
for my $file (@toremove) {
my $oldname = $inf->{slapd}->{config_dir} . "/" . $file;
next if (! -f $oldname); # does not exist - skip - already (re)moved
my $newname = "$bakdir/$file";
$! = 0; # clear
rename $oldname, $newname;
if ($!) {
push @errs, ["error_renaming_config", $oldname, $newname, $!];
}
}


According to
https://www.unix.com/shell-programming-and-scripting/27747-perl-rename-failed.html
the perl rename call can cause this error.

My workaround was to create the directories in /etc and make symlinks in
/var/lib/dirsrv/...

  mkdir /etc/dirsrv/slapd-INSTANCE/bak
  ln -s /etc/dirsrv/slapd-INSTANCE/bak /var/lib/dirsrv/slapd-INSTANCE/bak
  mkdir /etc/dirsrv/slapd-INSTANCE/bak.bak
  ln -s /etc/dirsrv/slapd-INSTANCE/bak.bak
/var/lib/dirsrv/slapd-INSTANCE/bak.bak


Upgrade succeeded now.

I originally encountered this problem while upgrading 389-ds-base on
jessie from 1.3.3.5-4 to 1.3.3.5-4+deb8u1. Since upgrade scripts didn't
change this should be still valid for the actual version.

Bug#905183: openstack-dashboard: dependency problems upgrading from stretch to buster

[Andreas Beckmann]

Package: openstack-dashboard
Version: 3:13.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails.

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

  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) python3-django-horizon:amd64 < none -> 3:13.0.1-1 @un uN Ib 
>
  Broken python3-django-horizon:amd64 Conflicts on 
python-django-openstack-auth:amd64 < 2.4.1-2 -> 3.5.0-2 @ii umU >
Considering python-django-openstack-auth:amd64 0 as a solution to 
python3-django-horizon:amd64 0
Holding Back python3-django-horizon:amd64 rather than change 
python-django-openstack-auth:amd64
  Investigating (1) openstack-dashboard:amd64 < 3:10.0.1-1 -> 3:13.0.1-1 @ii 
umU Ib >
  Broken openstack-dashboard:amd64 Depends on python3-django-horizon:amd64 < 
none | 3:13.0.1-1 @un uH > (= 3:13.0.1-1)
Considering python3-django-horizon:amd64 0 as a solution to 
openstack-dashboard:amd64 0
Holding Back openstack-dashboard:amd64 rather than change 
python3-django-horizon:amd64
  Investigating (2) python-django:amd64 < 1:1.10.7-2+deb9u1 -> 1:1.11.14-1 @ii 
umU Ib >
  Broken python-django:amd64 Breaks on openstack-dashboard:amd64 < 3:10.0.1-1 | 
3:13.0.1-1 @ii umH > (< 3:12)
Considering openstack-dashboard:amd64 0 as a solution to 
python-django:amd64 11
Upgrading openstack-dashboard:amd64 due to Breaks field in 
python-django:amd64
  Investigating (2) openstack-dashboard:amd64 < 3:10.0.1-1 -> 3:13.0.1-1 @ii 
umU Ib >
  Broken openstack-dashboard:amd64 Depends on python3-django-horizon:amd64 < 
none | 3:13.0.1-1 @un uH > (= 3:13.0.1-1)
Considering python3-django-horizon:amd64 0 as a solution to 
openstack-dashboard:amd64 0
Holding Back openstack-dashboard:amd64 rather than change 
python3-django-horizon:amd64
  Investigating (3) python-django:amd64 < 1:1.10.7-2+deb9u1 -> 1:1.11.14-1 @ii 
umU Ib >
  Broken python-django:amd64 Breaks on openstack-dashboard:amd64 < 3:10.0.1-1 | 
3:13.0.1-1 @ii umH > (< 3:12)
Considering openstack-dashboard:amd64 0 as a solution to 
python-django:amd64 11
Upgrading openstack-dashboard:amd64 due to Breaks field in 
python-django:amd64
  Investigating (3) openstack-dashboard:amd64 < 3:10.0.1-1 -> 3:13.0.1-1 @ii 
umU Ib >
  Broken openstack-dashboard:amd64 Depends on python3-django-horizon:amd64 < 
none | 3:13.0.1-1 @un uH > (= 3:13.0.1-1)
Considering python3-django-horizon:amd64 0 as a solution to 
openstack-dashboard:amd64 0
Holding Back openstack-dashboard:amd64 rather than change 
python3-django-horizon:amd64
...
  Investigating (9) python-django:amd64 < 1:1.10.7-2+deb9u1 -> 1:1.11.14-1 @ii 
umU Ib >
  Broken python-django:amd64 Breaks on openstack-dashboard:amd64 < 3:10.0.1-1 | 
3:13.0.1-1 @ii umH > (< 3:12)
Considering openstack-dashboard:amd64 0 as a solution to 
python-django:amd64 11
Upgrading openstack-dashboard:amd64 due to Breaks field in 
python-django:amd64
  Investigating (9) openstack-dashboard:amd64 < 3:10.0.1-1 -> 3:13.0.1-1 @ii 
umU Ib >
  Broken openstack-dashboard:amd64 Depends on python3-django-horizon:amd64 < 
none | 3:13.0.1-1 @un uH > (= 3:13.0.1-1)
Considering python3-django-horizon:amd64 0 as a solution to 
openstack-dashboard:amd64 0
Holding Back openstack-dashboard:amd64 rather than change 
python3-django-horizon:amd64
  Done
  
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   fonts-roboto-fontface : Breaks: openstack-dashboard (< 3:12) but 3:10.0.1-1 
is to be installed
   python-django : Breaks: openstack-dashboard (< 3:12) but 3:10.0.1-1 is to be 
installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.


The problem seems to come from the conflict against
python-django-openstack-auth, but that package is still available
in buster and therefore apt is quite reluctant to remove a package
that is not obsolete, but upgradable.

cheers,


Andreas


openstack-dashboard_3:13.0.1-1.log.gz
Description: application/gzip

Bug#905182: zhcon-data,zhcon: Missing Breaks + Replaces causes error on upgrade

[Boyuan Yang]

Package: zhcon
Severity: serious
Version: 1:0.2.6-13
X-Debbugs-CC: f...@debian.org
Justification: File conflict

正在选中未选择的软件包 zhcon-data。
正准备解包 .../4-zhcon-data_1%3a0.2.6-13_all.deb  ...
正在解包 zhcon-data (1:0.2.6-13) ...
dpkg: 处理归档 /tmp/apt-dpkg-install-FgGkRR/4-zhcon-data_1%3a0.2.6-13_all.deb
(--unpack)时出错：
 正试图覆盖 /usr/share/zhcon/font/asc12.bpsf，它同时被包含于软件包 zhcon 1:0.2.6-12
dpkg-deb: 错误: 粘贴 subprocess was killed by signal (断开的管道)
正准备解包 .../5-zhcon_1%3a0.2.6-13_amd64.deb  ...
正在将 zhcon (1:0.2.6-13) 解包到 (1:0.2.6-12) 上 ...
在处理时有错误发生：
 /tmp/apt-dpkg-install-FgGkRR/4-zhcon-data_1%3a0.2.6-13_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

--
Regards,
Boyuan Yang

Bug#905180: libmoe-dev: missing Breaks+Replaces: libmoe1.5 (<< 1.5.8-3)

[Andreas Beckmann]

Package: libmoe-dev
Version: 1.5.8-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Unpacking libmoe-dev (1.5.8-3) over (1.5.8-2+b1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libmoe-dev_1.5.8-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/libmoe.so', which is also in package libmoe1.5 
1.5.8-2+b1
  Preparing to unpack .../libmoe1.5_1.5.8-3_amd64.deb ...
  Unpacking libmoe1.5 (1.5.8-3) over (1.5.8-2+b1) ...
  Preparing to unpack .../multiarch-support_2.27-5_amd64.deb ...
  Unpacking multiarch-support (2.27-5) over (2.24-11+deb9u3) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libmoe-dev_1.5.8-3_amd64.deb


cheers,

Andreas


libmoe-dev_1.5.8-3.log.gz
Description: application/gzip

Bug#905179: apticron: prompting due to modified conffiles which were not modified by the user: /etc/apticron/apticron.conf

[Andreas Beckmann]

Package: apticron
Version: 1.2.0
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/#behavior,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

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

  Setting up apticron (1.2.0) ...
  
  Configuration file '/etc/apticron/apticron.conf'
   ==> File on system created by you or by a script.
   ==> File also in package provided by package maintainer.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** apticron.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package 
apticron (--configure):
   end of file on stdin at conffile prompt
  Setting up libgssapi-krb5-2:amd64 (1.16-2) ...
  Processing triggers for libc-bin (2.27-5) ...
  Errors were encountered while processing:
   apticron


cheers,

Andreas


apticron_1.2.0.log.gz
Description: application/gzip

Bug#905178: apt-cacher: prompting due to modified conffiles which were not modified by the user: /etc/default/apt-cacher

[Andreas Beckmann]

Package: apt-cacher
Version: 1.7.18
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/#behavior,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

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

  Setting up apt-cacher (1.7.18) ...
  Installing new version of config file /etc/apt-cacher/apt-cacher.conf ...
  
  Configuration file '/etc/default/apt-cacher'
   ==> File on system created by you or by a script.
   ==> File also in package provided by package maintainer.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** apt-cacher (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package 
apt-cacher (--configure):
   end of file on stdin at conffile prompt
  Processing triggers for libc-bin (2.27-5) ...
  Processing triggers for ca-certificates (20170717) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  done.
  Errors were encountered while processing:
   apt-cacher


cheers,

Andreas


apt-cacher_1.7.18.log.gz
Description: application/gzip

Bug#905177: bind9: prompting due to modified conffiles which were not modified by the user: /etc/bind/named.conf.options

[Andreas Beckmann]

Package: bind9
Version: 1:9.11.4+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/#behavior,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

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

  Setting up bind9 (1:9.11.4+dfsg-2) ...
  Installing new version of config file /etc/apparmor.d/usr.sbin.named ...
  Installing new version of config file /etc/bind/bind.keys ...
  
  Configuration file '/etc/bind/named.conf.options'
   ==> File on system created by you or by a script.
   ==> File also in package provided by package maintainer.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** named.conf.options (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing 
package bind9 (--configure):
   end of file on stdin at conffile prompt
  Processing triggers for libc-bin (2.27-5) ...
  Errors were encountered while processing:
   bind9


cheers,

Andreas


bind9_1:9.11.4+dfsg-2.log.gz
Description: application/gzip

Bug#904357: marked as done (python3-pysnmp4: fails to install with python 3.7)

[Debian Bug Tracking System]

Your message dated Wed, 01 Aug 2018 09:50:34 +
with message-id 
and subject line Bug#904357: fixed in python-pysnmp4 4.4.3-2
has caused the Debian Bug report #904357,
regarding python3-pysnmp4: fails to install with python 3.7
to be marked as done.

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

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


-- 
904357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pysnmp4
Version: 4.4.3-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-pysnmp4 (4.4.3-1) ...
File "/usr/lib/python3/dist-packages/pysnmp/carrier/asyncio/dgram/base.py", 
line 86
  self._lport = asyncio.async(c)
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/pysnmp/carrier/asyncio/dispatch.py", 
line 72
  self.loopingcall = asyncio.async(self.handle_timeout())
 ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-pysnmp4 (--configure):
   installed python3-pysnmp4 package post-installation script subprocess 
returned error exit status 1


"async" has become a reserved keyword in python 3.7


cheers,

Andreas


ceilometer-common=1%10.0.0-5.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-pysnmp4
Source-Version: 4.4.3-2

We believe that the bug you reported is fixed in the latest version of
python-pysnmp4, 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.
Michal Arbet  (supplier of updated python-pysnmp4 
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: Tue, 31 Jul 2018 12:59:43 +0300
Source: python-pysnmp4
Binary: python-pysnmp4 python3-pysnmp4 python-pysnmp4-doc
Architecture: source
Version: 4.4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Michal Arbet 
Description:
 python-pysnmp4 - Python SNMP library for agents and managers (Python 2 module)
 python-pysnmp4-doc - Python SNMP library for agents and managers (unstable 
branch)
 python3-pysnmp4 - Python SNMP library for agents and managers (Python 3 module)
Closes: 904357
Changes:
 python-pysnmp4 (4.4.3-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
 .
   [ Michal Arbet ]
   * Add 0002-Fix-py37-async-as-keyword.patch (Closes: #904357)
Checksums-Sha1:
 7b0ec9211e1bfaccab6f4ea5916278bccf03 2542 python-pysnmp4_4.4.3-2.dsc
 8972723a9bde09a472b4422ddc225e4870dc8197 6208 
python-pysnmp4_4.4.3-2.debian.tar.xz
 d78eb62c994f83c467d169b0b2ae088aec4ae82e 10035 
python-pysnmp4_4.4.3-2_amd64.buildinfo
Checksums-Sha256:
 dbd1662ceb6c652d3854e4d13b1cb319b95cf4a69a170a87cea60f2fd3ee6a5c 2542 
python-pysnmp4_4.4.3-2.dsc
 4d05058365864a2741bf4b757caeaffeccb798689503bc0c767d96d55a224c02 6208 
python-pysnmp4_4.4.3-2.debian.tar.xz
 e2401cdfa07fb6bd2bd996822109680caee6d893b3a095706b32b6d20d12492a 10035 
python-pysnmp4_4.4.3-2_amd64.buildinfo
Files:
 512637a929fbfa47e3437345f3732e9b 2542 python optional 
python-pysnmp4_4.4.3-2.dsc
 86726574c2e3a3f3b3959d7d0691c0e2 6208 python optional 
python-pysnmp4_4.4.3-2.debian.tar.xz
 5a5e238ee59b9b052bbc15496a47d86d 10035 python optional 
python-pysnmp4_4.4.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAlthf9QQHGJlcm5hdEBs
dWZmeS5jeAAKCRCVpC/oNTUl+RkaEACdlUNeJyzv2GnvvZt4I2pIXjKHIqc+BbPI
hz6SqdSbaxKWTBvqiWM30asGIb+tZyzYJbqnR+fQEje/DrjBRCRXcih6mlMc8qzc
z4HG4CilFle5KoZKiFxLpDtrJC/adPvuvm+FvelJL+3JZLxb7jB2jGwJkcuGqCsv
AmEZFnfc7Q25XDNFMpIT2DwfA8lelzHWCflQSypPtW0yOaUShPUfcToUjCL2yXJ3
YFtB++tqUpDpNPTC0c0pmIPz3lTetnGv+/8thg5FXzlawlN17WVaIdKw3dIt+B6F

Bug#905176: ganeti: fails to upgrade from 'stretch': removal of ganeti-{haskell,htools}-2.15 fails

[Andreas Beckmann]

Package: ganeti
Version: 2.16.0~rc2-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails.

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

  Selecting previously unselected package ganeti-2.16.
  Preparing to unpack .../48-ganeti-2.16_2.16.0~rc2-4_all.deb ...
  Unpacking ganeti-2.16 (2.16.0~rc2-4) ...
  Preparing to unpack .../49-ganeti_2.16.0~rc2-4_all.deb ...
  Unpacking ganeti (2.16.0~rc2-4) over (2.15.2-7+deb9u2) ...
  (Reading database ... 
(Reading database ... 7847 files and directories currently installed.)
  Removing ganeti-htools-2.15 (2.15.2-7+deb9u2) ...
  dpkg: error processing package ganeti-htools-2.15 (--remove):
   installed ganeti-htools-2.15 package pre-removal script subprocess returned 
error exit status 30
  Removing ganeti-haskell-2.15 (2.15.2-7+deb9u2) ...
  dpkg: error processing package ganeti-haskell-2.15 (--remove):
   installed ganeti-haskell-2.15 package pre-removal script subprocess returned 
error exit status 30
  dpkg: libcurl3:amd64: dependency problems, but removing anyway as you 
requested:
   ganeti-htools-2.15 depends on libcurl3 (>= 7.16.2).
   ganeti-haskell-2.15 depends on libcurl3 (>= 7.16.2).
  
  Removing libcurl3:amd64 (7.52.1-5+deb9u6) ...
  Errors were encountered while processing:
   ganeti-htools-2.15
   ganeti-haskell-2.15


cheers,

Andreas


ganeti_2.16.0~rc2-4.log.gz
Description: application/gzip

Processed: Fixed in latest upload

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 6.0.1-5
Bug #902826 [src:scilab] scilab: FTBFS on i386 - seg. fault during build
Marked as fixed in versions scilab/6.0.1-5.

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

Bug#902826: Fixed in latest upload

[Julien Puydt]

Control: fixed -1 6.0.1-5

Hi,

according to the buildd's logs, there is no problem building on i386 
anymore.


Thanks,

jpuydt on irc.debian.org

Bug#905169: marked as done (golang-github-graph-gophers-graphql-go: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Wed, 01 Aug 2018 09:03:53 +
with message-id 
and subject line Bug#905169: fixed in golang-github-graph-gophers-graphql-go 
0.0~git20180609.bb97385-2
has caused the Debian Bug report #905169,
regarding golang-github-graph-gophers-graphql-go: 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.)


-- 
905169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-graph-gophers-graphql-go
Version: 0.0~git20180609.bb97385-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Sascha Steinbiss , 
ftpmas...@debian.org

Hi,

I just ACCEPTed golang-github-graph-gophers-graphql-go from NEW but 
noticed it was missing attribution in debian/copyright for at least 
internal/validation/testdata.

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: golang-github-graph-gophers-graphql-go
Source-Version: 0.0~git20180609.bb97385-2

We believe that the bug you reported is fixed in the latest version of
golang-github-graph-gophers-graphql-go, which is due to be installed in the 
Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Sascha Steinbiss  (supplier of updated 
golang-github-graph-gophers-graphql-go 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: Wed, 01 Aug 2018 10:22:01 +0200
Source: golang-github-graph-gophers-graphql-go
Binary: golang-github-graph-gophers-graphql-go-dev
Architecture: source all
Version: 0.0~git20180609.bb97385-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Sascha Steinbiss 
Description:
 golang-github-graph-gophers-graphql-go-dev - GraphQL server with a focus on 
ease of use
Closes: 905169
Changes:
 golang-github-graph-gophers-graphql-go (0.0~git20180609.bb97385-2) unstable; 
urgency=medium
 .
   * Add separate license text for internal/validation/testdata/*
 Thanks to Chris Lamb for the hint.
 Closes: #905169
Checksums-Sha1:
 0fe6f3b6168a2dcdc2506fc4fa9c42cfb7d8df5b 2543 
golang-github-graph-gophers-graphql-go_0.0~git20180609.bb97385-2.dsc
 200387c06bdc229c8b9362828c7f0b450a2e987a 2472 
golang-github-graph-gophers-graphql-go_0.0~git20180609.bb97385-2.debian.tar.xz
 3055e30bea8518c87a471708b0201ee6530083d8 64580 
golang-github-graph-gophers-graphql-go-dev_0.0~git20180609.bb97385-2_all.deb
 c788ad6d212676cb9802c10bd701a112f36abf6c 6404 
golang-github-graph-gophers-graphql-go_0.0~git20180609.bb97385-2_amd64.buildinfo
Checksums-Sha256:
 59dec90f06610f7b6f2b81133782b3c944e5995038fa15873c2f52c83c8063ef 2543 
golang-github-graph-gophers-graphql-go_0.0~git20180609.bb97385-2.dsc
 acfce5cc164e1797dd826a4484ccec481ba57dc6b61a8583267e73da598a8629 2472 
golang-github-graph-gophers-graphql-go_0.0~git20180609.bb97385-2.debian.tar.xz
 260b7eb91767f0d11980f3f1c51909822e8e02c0e9512c2a48cd9017907676f4 64580 
golang-github-graph-gophers-graphql-go-dev_0.0~git20180609.bb97385-2_all.deb
 6136f2e3e9b5040bcf7ca894ff2c4d92fb650138dfe2198ae8357b92ba3a3314 6404 
golang-github-graph-gophers-graphql-go_0.0~git20180609.bb97385-2_amd64.buildinfo
Files:
 c4992fb1a225ed590cd3132f834f4845 2543 devel optional 
golang-github-graph-gophers-graphql-go_0.0~git20180609.bb97385-2.dsc
 6e4264110874d695d95987baf3bf5ef8 2472 devel optional 
golang-github-graph-gophers-graphql-go_0.0~git20180609.bb97385-2.debian.tar.xz
 61cde3c43e0148c335cd56fb577dc78c 64580 devel optional 
golang-github-graph-gophers-graphql-go-dev_0.0~git20180609.bb97385-2_all.deb
 840c9f2b171ed01a845be1be3173ff61 6404 devel optional 
golang-github-graph-gophers-graphql-go_0.0~git20180609.bb97385-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIyBAEBCAAdFiEEWzS6WqtVB+kDQm6F6NN64vCfSHIFAlthc/gACgkQ6NN64vCf
SHKcAQ/2Pb+HZmB4prAutxVnpYXpWN6sgWfBpcJJqeEfGhEDjekwVCRKc6ZzkwE5
npFVKaI6f9T1Z0+Yy1l18YKY1ttBxd6q8+Ih2ezy9Ukyhpr1gIgZDFSZeTOx+djm

Bug#905146: Breaks+Replaces

[kuLa]

On 2018-07-31 23:40:40, Andreas Beckmann wrote:
> > Replaces: libpqxx6 (>= 6.2)
> > Breaks:  libpqxx6 (>= 6.2)
> 
> That is what I meant.
> (Usually you would use (<< 6.2.4-3) if you moved some files, but here
> you uploaded two buggy package versions (-1 (wrong library name) and -2
> (wrong package name)) while the older versions are OK and
> co-installable; and the old package name "disappears" in -3.)
> 
> > To be honest I'm not sure if this is what we need as libpqxx-6.2.so has been
> > introduced in 6.2.4-2 and 6.2.4-3 is broken for upgrade. If I'll upload 
> > 6.2.4-4
> > then I'd expect to replace all earlier versions of 6.2,
> 
> What do you plan to change for -4?
> The renaming of the package to libpqxx-6.2 sounds like the correct
> solution to me.

This has been done in libpqxx-6.2.4-3 and changes planned are to add B+R only,
plus do the follow through on the transition and binNMUs.

> You cannot have a libpqxx6 package not shipping
> libpqxx-6.1.so . This just needs to be handled as a proper library
> transition (you already filed the corresponding bug).
> 
> > so I'd expect B+R as
> > below:
> 
> In which package?

It was meant for libpqxx-6.2 but now I see where and why it's going to be
problematic.

> > Replaces: libpqxx-6.2 (<< ${binary:Version})
> > Breaks:  libpqxx-6.2 (<< ${binary:Version})
> 
> This sounds seriously wrong. (Unless you have a very special package, or
> a very big strange mess to be cleaned up.)
> Why would you want to B+R the newly introduced package?
> Why would you want to bump the B+R every time you upload a new version?
> You need Depends: foo (= ${binary:Version}) to keep something in sync
> but for B+R there is usually a first "good" version that no longer needs
> to be replaced, so no substvar needed.
> (The exception would be a package frequently getting new upstream
> releases in stable with diverging packaging in stable and sid, where
> every upload to stable would invalidate the first "good" version in sid.
> cf. chromium)

After looking into this situation after not so bad night sleep I have to say
that I think you're correct and your explanations are also sound. Thank you for
your help.
I'm going to use B+R accordingly to what you're suggesting.
-- 

|_|0|_|  |
|_|_|0|  "Panta rei" |
|0|0|0|  kuLa    |

gpg --keyserver pgp.mit.edu --recv-keys 0x686930DD58C338B3
3DF1  A4DF  C732  4688  38BC  F121  6869  30DD  58C3  38B3


signature.asc
Description: PGP signature

Bug#903218: marked as done (python3-opengl: fails to install with python3.7 installed)

[Debian Bug Tracking System]

Your message dated Wed, 01 Aug 2018 08:48:54 +
with message-id 
and subject line Bug#903218: fixed in pyopengl 3.1.0+dfsg-2
has caused the Debian Bug report #903218,
regarding python3-opengl: fails to install with python3.7 installed
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.)


-- 
903218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-opengl
Severity: serious
thanks

```
Setting up python3-opengl (3.1.0+dfsg-1) ...
  File "/usr/lib/python3/dist-packages/OpenGL/GL/SGIX/async.py", line 58
from OpenGL.raw.GL.SGIX.async import *
^
SyntaxError: invalid syntax
```

This is serious because it's preventing install:

```
$ sudo apt install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
sh: 0: getcwd() failed: No such file or directory
sh: 0: getcwd() failed: No such file or directory
sh: 0: getcwd() failed: No such file or directory
Setting up python3-opengl (3.1.0+dfsg-1) ...
  File "/usr/lib/python3/dist-packages/OpenGL/GL/SGIX/async.py", line 58
from OpenGL.raw.GL.SGIX.async import *
^
SyntaxError: invalid syntax

dpkg: error processing package python3-opengl (--configure):
 installed python3-opengl package post-installation script subprocess
returned error exit status 1
Errors were encountered while processing:
 python3-opengl
E: Sub-process /usr/bin/dpkg returned an error code (1)
```

I think new Python 3 (3.6.6) is trying to parse that as the `async`
keyword. I have no idea why, since I can't seem to make Python
trivially emit the syntax error rather than a module import error.

   Paul

-- 
:wq
--- End Message ---
--- Begin Message ---
Source: pyopengl
Source-Version: 3.1.0+dfsg-2

We believe that the bug you reported is fixed in the latest version of
pyopengl, 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.
Picca Frédéric-Emmanuel  (supplier of updated pyopengl 
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: Wed, 01 Aug 2018 10:39:40 +0200
Source: pyopengl
Binary: python-opengl python3-opengl
Architecture: source
Version: 3.1.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Picca Frédéric-Emmanuel 
Description:
 python-opengl - Python bindings to OpenGL (Python 2)
 python3-opengl - Python bindings to OpenGL (Python 3)
Closes: 903218
Changes:
 pyopengl (3.1.0+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Picca Frédéric-Emmanuel ]
   * d/patches
 + Added 0001-renamed-modules-async-async_-for-python3.7-like-fedo.patch
 (Closes: #903218)
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/control: Remove trailing whitespaces
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
Checksums-Sha1:
 7db8ccc963960375493c011907c44e251a9948bc 2156 pyopengl_3.1.0+dfsg-2.dsc
 eef73f952c73ff12c9fbb32ba7a0a5ee23fd38a7 11352 
pyopengl_3.1.0+dfsg-2.debian.tar.xz
 3f286ee537dd0c92e7b91fa14257e2bd524c843e 7213 
pyopengl_3.1.0+dfsg-2_source.buildinfo
Checksums-Sha256:
 777e8bd1a244f9dd09193602cf60a2d988a9d05777d0ffd969e4a45e7dcf69d7 2156 
pyopengl_3.1.0+dfsg-2.dsc
 bde89e8c25f32c59db3a7ffd9dc17e4a688ae79e6d1e7c9d45e4178fc3605e96 11352 
pyopengl_3.1.0+dfsg-2.debian.tar.xz
 b7b6e082250d9538235ffe74b77399cb41622d41e8a9f0706ec0ce4ca1981ea6 7213 
pyopengl_3.1.0+dfsg-2_source.buildinfo
Files:
 405a2cf9c4f87d0344e42f394cd29ef0 2156 python optional pyopengl_3.1.0+dfsg-2.dsc
 33ebfaa1e598b8079b4dc9c23f3f5e7a 11352 python optional 
pyopengl_3.1.0+dfsg-2.debian.tar.xz
 f29f732f646bed934c890f1e58bd84ac 7213 python optional 
pyopengl_3.1.0+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#905017: LXDE: Frozen display issue

[Julien Puydt]

Hi,

Le 31/07/2018 à 17:53, Julien Puydt a écrit :

I'll have to check what happens when disabling extensions... but for now 
I have a long-running program, so I don't want to risk breaking my 
session : it will have to wait a little before I can do some tests.


I made some more tests following your advice : I'm unable to reproduce 
the problem :-(


On the one hand it means we could close the bug report... on the other 
hand, that means something wrong has managed to escape :-/


jpuydt on irc.debian.org

Processed: fix again

[Debian Bug Tracking System]

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

> notfound 905092 1.13.5+ds1-4
Bug #905092 [src:ros-ros-comm] ros-ros-comm: breaking reverse-dependencies
Ignoring request to alter found versions of bug #905092 to the same values 
previously set
> found 905092 1.13.5+ds1-5
Bug #905092 [src:ros-ros-comm] ros-ros-comm: breaking reverse-dependencies
Marked as found in versions ros-ros-comm/1.13.5+ds1-5.
> thanks
Stopping processing here.

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

Bug#905169: golang-github-graph-gophers-graphql-go: Incomplete debian/copyright?

[Sascha Steinbiss]

Hi Chris,

> I just ACCEPTed golang-github-graph-gophers-graphql-go from NEW but 
> noticed it was missing attribution in debian/copyright for at least 
> internal/validation/testdata.
> 
> This is in no way exhaustive so please check over the entire package 
> carefully and address these on your next upload.

Thanks for taking a close look that quickly. Sure enough, I will address
this issue asap.

Have a nice DebConf!

Cheers
Sascha



signature.asc
Description: OpenPGP digital signature

Bug#859831: marked as done (xmltooling: Please migrate to openssl1.1 in Buster)

[Debian Bug Tracking System]

Your message dated Wed, 01 Aug 2018 08:10:44 +
with message-id 
and subject line Bug#859831: fixed in xmltooling 3.0.2-1
has caused the Debian Bug report #859831,
regarding xmltooling: Please migrate to openssl1.1 in Buster
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.)


-- 
859831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xmltooling
Version: 1.6.0-4
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle. The bug report about
the FTBFS is #828608. The log of the FTBFS can be found at

https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/xmltooling_1.5.6-2_amd64-20160529-1555

Sebastian
--- End Message ---
--- Begin Message ---
Source: xmltooling
Source-Version: 3.0.2-1

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

Debian distribution maintenance software
pp.
Ferenc Wágner  (supplier of updated xmltooling 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: Wed, 01 Aug 2018 00:25:03 +0200
Source: xmltooling
Binary: libxmltooling8 libxmltooling-dev xmltooling-schemas libxmltooling-doc
Architecture: source amd64 all
Version: 3.0.2-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Shib Team 
Changed-By: Ferenc Wágner 
Description:
 libxmltooling-dev - C++ XML parsing library with encryption support 
(development)
 libxmltooling-doc - C++ XML parsing library with encryption support (API docs)
 libxmltooling8 - C++ XML parsing library with encryption support (runtime)
 xmltooling-schemas - XML schemas for XMLTooling
Closes: 859831
Changes:
 xmltooling (3.0.2-1) experimental; urgency=medium
 .
   * [263b9d1] New upstream release: 3.0.2
   * [6ffad35] All of our patches were included upstream
   * [dc188aa] Update Standards-Version to 4.1.5 (no changes required)
   * [1dbdaee] Switch to Debhelper compat level 11
   * [8a38bae] Stop repeating the common part of the package descriptions
   * [ec0997b] Multiarch doesn't need Pre-Depends anymore
   * [e33065c] Rename library package according to the new soversion
   * [cb6df2a] Enable building with OpenSSL 1.1 (Closes: #859831)
   * [49b8ca9] Revert "Provide a GCC 7 build with strict enough shlibs"
 The GCC7 switchover is long done, this constraint isn't needed anymore.
   * [c5f26c9] Update debian/copyright
   * [5099fb1] Shibboleth SP 3 requires XML-Security 2 and log4shib 2
   * [65857d6] We do not ship the libtool archive files.
 But upstream installs them now to support make uninstall.
   * [d5d3966] Clean up trailing whitespace in debian/changelog
   * [b4e7f10] Our headers include Boost headers
Checksums-Sha1:
 2ff96ca756725b9f88a3a724bdedeeaec7711ff3 2665 xmltooling_3.0.2-1.dsc
 2f918421316a7134a5eef699b9851a86d1a98c89 596471 xmltooling_3.0.2.orig.tar.bz2
 9c4acadf3166a84cae5659fab52267cbf2727ed9 833 xmltooling_3.0.2.orig.tar.bz2.asc
 18a3f2e487d33cad98634178487d9bb731178446 52500 xmltooling_3.0.2-1.debian.tar.xz
 819efa72ae4b187eb83bfe4ced9b6426965db9b9 78180 
libxmltooling-dev_3.0.2-1_amd64.deb
 183894bf66e3db53f7da686e2768979a284b16f1 5608288 
libxmltooling-doc_3.0.2-1_all.deb
 327190f0eb4309460a3f65bb63c13e23d4f39735 12398844 
libxmltooling8-dbgsym_3.0.2-1_amd64.deb
 66ab1658ba7eb9bca5fcfb263db23c692512af56 611012 
libxmltooling8_3.0.2-1_amd64.deb
 9146fcd9e687db9884204e0ace7bb698b21ca0b5 19992 
xmltooling-schemas_3.0.2-1_all.deb
 802822bd84a85de4525e445f36582b7e4a90e7a9 10683 
xmltooling_3.0.2-1_amd64.buildinfo
Checksums-Sha256:
 343c6d265db09ac0b119511dfeb8eb35a6a422a1bb619ffb4ee6a3e3c7a80cd2 2665 
xmltooling_3.0.2-1.dsc
 5709cf30c9d7cfc786599ac2433653fac8cc64d425781068af86019c8ce8d689 596471 
xmltooling_3.0.2.orig.tar.bz2
 ef899ca5036744808e49768da1d3060eaef156f187c288abb147a4ee308cba70 833 
xmltooling_3.0.2.orig.tar.bz2.asc
 be8edd7dd47dfe2eb210b9b81869a2bf83ebc42bfd4ea7a189d394f3ee82f9ee 52500 
xmltooling_3.0.2-1.debian.tar.xz
 

Processed: Re: Bug#905163: lftp: CVE-2018-10916: Exploit in reverse mirror job deletes cwd on source

[Debian Bug Tracking System]

Processing control commands:

> found -1 4.7.4-1
Bug #905163 [src:lftp] lftp: CVE-2018-10916: Exploit in reverse mirror job 
deletes cwd on source
Marked as found in versions lftp/4.7.4-1.

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

Bug#905163: lftp: CVE-2018-10916: Exploit in reverse mirror job deletes cwd on source

[Salvatore Bonaccorso]

Control: found -1 4.7.4-1

Hi Noel,

On Wed, Aug 01, 2018 at 05:46:55AM +0200, Salvatore Bonaccorso wrote:
> Source: lftp
> Version: 4.8.3-1
> Severity: grave
> Tags: patch security upstream
> Forwarded: https://github.com/lavv17/lftp/issues/452
> 
> Hi,
> 
> The following vulnerability was published for lftp, were in cse revers
> mirror option is used can lead on data loss on source.
> 
> CVE-2018-10916[0]:
> Exploit in reverse mirror job deletes cwd on source
> 
> 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-10916
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10916
> [1] https://github.com/lavv17/lftp/issues/452
> [2] 
> https://github.com/lavv17/lftp/commit/a27e07d90a4608ceaf928b1babb27d4d803e1992
> 
> Please adjust the affected versions in the BTS as needed.

We marked it as no-dsa for stretch, but a fix would still be great as
well for stable. Could you prepare an update for next point release
for stretch?

Regards,
Salvatore

Bug#905169: golang-github-graph-gophers-graphql-go: Incomplete debian/copyright?

[Chris Lamb]

Source: golang-github-graph-gophers-graphql-go
Version: 0.0~git20180609.bb97385-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Sascha Steinbiss , 
ftpmas...@debian.org

Hi,

I just ACCEPTed golang-github-graph-gophers-graphql-go from NEW but 
noticed it was missing attribution in debian/copyright for at least 
internal/validation/testdata.

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#897724: collectd: ftbfs with GCC-8

[Niko Tyni]

On Fri, May 04, 2018 at 12:21:07PM +, Matthias Klose wrote:
> Package: src:collectd
> Version: 5.8.0-4
> Severity: normal
> Tags: sid buster
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-8

> src/aggregation.c: In function 'agg_lookup_class_callback':
> src/aggregation.c:204:20: error: '%s' directive output may be truncated 
> writing 14 bytes into a region of size between 0 and 127 
> [-Werror=format-truncation=]
> "%s-%s", tmp_plugin, AGG_FUNC_PLACEHOLDER);

> cc1: all warnings being treated as errors

Dear maintainers,

this is one of the few remaining blockers for the Perl 5.28 transition.

I've forwarded the issue upstream at
  https://github.com/collectd/collectd/issues/2883

I see Fedora is configuring with --disable-werror, so these warnings
does not cause a build failure there. Would you consider doing that
until a solution is implemented upstream?

Thanks for your work on Debian,
-- 
Niko Tyni   nt...@debian.org

Processed: Re: ros-ros-comm: breaking reverse-dependencies

[Debian Bug Tracking System]

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

> notfound 905092 ros-ros-comm/1.13.5+ds1-5
Bug #905092 [src:ros-ros-comm] ros-ros-comm: breaking reverse-dependencies
No longer marked as found in versions ros-ros-comm/1.13.5+ds1-5.
> thanks
Stopping processing here.

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

Bug#878337: [Pkg-javascript-devel] Bug#878337: Remove the package?

[Paolo Greppi]

Il 31/07/2018 17:07, Julien Puydt ha scritto:
> Hi,
> 
> is there any hope for this package? At one point node-source-map will need to 
> be updated.
> 
> For now I have a RC bug on node-source-map to remind me not to update it too 
> fast, but it's a bit unfair : the problem doesn't stem from node-source-map 
> if node-grunt-contrib-concat is abandoned...
> 
> jpuydt on irc.debian.org

Development is abandoned, but it's actively used.
Stats from yarnpkg.com rate it in the top five downdloaded grunt-contrib-* 
modules:

grunt-contrib-watch: 1 M downloads in the last 30 days
grunt-contrib-clean 995.9 k
grunt-contrib-copy 958.5 k
grunt-contrib-uglify 870.3 k
grunt-contrib-concat 720.5 k
grunt-contrib-jshint 612 k
grunt-contrib-cssmin 560.5 k
grunt-contrib-less 373.1 k
...

Grunt itself is 2.1 M.

source-map is much more popular (79 M downloads in the last 30 days)

Paolo

Processed: Re: ros-ros-comm: breaking reverse-dependencies

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 1.13.5+ds1-4
Bug #905092 [src:ros-ros-comm] ros-ros-comm: breaking reverse-dependencies
Ignoring request to alter found versions of bug #905092 to the same values 
previously set

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

Bug#905092: ros-ros-comm: breaking reverse-dependencies

[Gianfranco Costamagna]

control: notfound -1 1.13.5+ds1-4

On Tue, 31 Jul 2018 10:02:24 +0200 Gianfranco Costamagna 
 wrote:
> Source: ros-ros-comm
> Version: 1.13.5+ds1-5
> Severity: serious
> Affects: ros-actionlib
> Affects: ros-bond-core
> Affects: ros-dynamic-reconfigure
> Affects: ros-geometry
> Affects: ros-nodelet-core
> Affects: ros-bond-core
> 
> The renaming of libroscpp-msgs-dev to libroscpp-msg-dev broke 6 ros packages, 
> can you please fixup in some way?
> 
> thanks
> 
> G.
> 
> 
> 

Bug#905165: debootstrap - fails in docker environment

[Bastian Blank]

Package: debootstrap
Version: 1.0.106
Severity: grave

debootstrap fails in docker environment completely by:

- symlinking $TARGET/proc to /proc
- running chroot $TARGET mount -t proc none /proc

The later obviously failing with a recursive symlink:

| mount: mount proc on /proc failed: Too many levels of symbolic links

I have no idea what this detection is about, but if you are going to run
chroot, you have to also mount /proc.

Regards,
Bastian

-- 
We Klingons believe as you do -- the sick should die.  Only the strong
should live.
-- Kras, "Friday's Child", stardate 3497.2