Bug#908555: marked as done (pydicom build depends on the removed python-gdcm)

[Debian Bug Tracking System]

Your message dated Sat, 24 Nov 2018 03:49:31 +
with message-id 
and subject line Bug#908555: fixed in pydicom 1.2.1-1
has caused the Debian Bug report #908555,
regarding pydicom build depends on the removed python-gdcm
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.)


-- 
908555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pydicom
Version: 1.1.0-2
Severity: serious
Tags: ftbfs

The following packages have unmet dependencies:
 builddeps:pydicom : Depends: python-gdcm but it is not going to be installed
--- End Message ---
--- Begin Message ---
Source: pydicom
Source-Version: 1.2.1-1

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

Debian distribution maintenance software
pp.
Yaroslav Halchenko  (supplier of updated pydicom package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 23 Nov 2018 17:32:08 -0500
Source: pydicom
Binary: python-pydicom python3-pydicom python-pydicom-doc python-dicom 
python3-dicom
Architecture: source all
Version: 1.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Yaroslav Halchenko 
Description:
 python-dicom - transitional package for python-pydicom
 python-pydicom - DICOM medical file reading and writing (Python 2)
 python-pydicom-doc - DICOM medical file reading and writing (documentation)
 python3-dicom - transitional package for python3-pydicom
 python3-pydicom - DICOM medical file reading and writing (Python 3)
Closes: 908555
Changes:
 pydicom (1.2.1-1) unstable; urgency=medium
 .
   * New upstream release
   * Added debian/gbp.conf to point that we use "debian" branch, not master
 and also we use pristine-tar
   * debian/control
 - Removed gdcm from B-Depends and moved under Suggests since it is an
   optional dependency (Closes: #908555)
   * debian/patches
 - refreshed and upstreamed ones removed/disabled
Checksums-Sha1:
 ffe92c3785d02988f87dbfb040a4a6dada0e0c2d 2444 pydicom_1.2.1-1.dsc
 5601d4b4e510d242cbd56fdb40b7628f3aa2f0bb 7041066 pydicom_1.2.1.orig.tar.gz
 e5886612703a7caeb7679ed6acbfb6b698a9e9da 6228 pydicom_1.2.1-1.debian.tar.xz
 bf1e6aface673a8f04ee2838d09868c5578b1a21 10253 pydicom_1.2.1-1_amd64.buildinfo
 0f95d445deda6e8796e253ed4c18a503eacd6e87 4696 python-dicom_1.2.1-1_all.deb
 0f1fa3f857840bbcdf2bffe20f47a15cab480c7e 347024 
python-pydicom-doc_1.2.1-1_all.deb
 9c28d31c1f23b2394ab43e0bea3faec67280b040 4396516 python-pydicom_1.2.1-1_all.deb
 42b645ee1d429b55a20717d233d6aafe43f83ab2 4704 python3-dicom_1.2.1-1_all.deb
 0f7671d028e1b89890ef7df59a28bfa67470c59b 4396608 
python3-pydicom_1.2.1-1_all.deb
Checksums-Sha256:
 c353e1904f5961a538b0a385e31021be9f1a0d82aaa757d7e8819c7791b57b05 2444 
pydicom_1.2.1-1.dsc
 adb92a855619fdd86bed413213d1d1db97d763dd65ea008ede6dad876a28c91c 7041066 
pydicom_1.2.1.orig.tar.gz
 b5203425fe9b07ee7a660fdf45df308a863f8168f8e68c160d21b0a03d0b4c8d 6228 
pydicom_1.2.1-1.debian.tar.xz
 d512a1698088569fd3732ae47dc948b471d3a27cd6694e4a9fe95cd5bb8e5514 10253 
pydicom_1.2.1-1_amd64.buildinfo
 f649699a251230f21829e4d94eca0feb5f1703f438f90fc5ba54280db906a6f6 4696 
python-dicom_1.2.1-1_all.deb
 e4824c32e55bb943c3030db90e636966ef20a6ef5576250c1c287d85fafafcf0 347024 
python-pydicom-doc_1.2.1-1_all.deb
 1b3ae05572b1ce364e334f4c77259ef9c71a995c82755b5cbc89801a74fdf180 4396516 
python-pydicom_1.2.1-1_all.deb
 85733c5cbda324e7ed52318f497c367966cb7ba844fdbb03b3801882217791eb 4704 
python3-dicom_1.2.1-1_all.deb
 448cb88aba2fbdf6faa046f84aebc08f7101a0b1ff14647dd012c53bf83a853c 4396608 
python3-pydicom_1.2.1-1_all.deb
Files:
 6449f24a2a91be4f8879cca8674ef406 2444 python optional pydicom_1.2.1-1.dsc
 2f21c96fe0e7dd2a20983b3a665aa366 7041066 python optional 
pydicom_1.2.1.orig.tar.gz
 03ad71d9d33cc0a226aa96526486d07f 6228 python optional 
pydicom_1.2.1-1.debian.tar.xz
 a6c538e6178acdaaa806ca2052ab038b 10253 python optional 
pydicom_1.2.1-1_amd64.buildinfo
 78b836d112bc724ff3522ec8c5433645 4696 oldlibs optional 
python-dicom_1.2.1-1_all.deb
 

Processed: Re: Bug #913014: e3 (all binaries): immediate segmentation fault

[Debian Bug Tracking System]

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

> tags 913014 + patch
Bug #913014 [e3] e3 (all binaries): immediate segmentation fault
Added tag(s) patch.
> quit
Stopping processing here.

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

Bug#881565: marked as done (python-acoustid: incompatible with python3 (fix availble upstream))

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 23:58:02 +
with message-id 
and subject line Bug#881565: fixed in pyacoustid 1.1.5-1
has caused the Debian Bug report #881565,
regarding python-acoustid: incompatible with python3 (fix availble upstream)
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.)


-- 
881565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-acoustid
Version: 1.1.2-2
Severity: important

Dear Maintainer,

The current version of python-acoustid doesn't work with Python 3.
Specifically the submit() function to submit fingerprints is broken:
https://github.com/beetbox/pyacoustid/pull/33

There is a fix available upstream in the 1.1.5 release. Could you please
update the Debian packaging to include this fix?

Thanks,
James


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

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

Versions of packages python3-acoustid depends on:
ii  libchromaprint11.4.2-1
ii  python33.6.3-2
pn  python3-audioread  
ii  python3-requests   2.18.1-1

python3-acoustid recommends no packages.

python3-acoustid suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pyacoustid
Source-Version: 1.1.5-1

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated pyacoustid package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 23 Nov 2018 18:24:26 -0500
Source: pyacoustid
Binary: python-acoustid python3-acoustid
Architecture: source all
Version: 1.1.5-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Description:
 python-acoustid - Acoustid interface implementation and Chromaprint bindings
 python3-acoustid - Acoustid interface implementation and Chromaprint bindings 
(Pytho
Closes: 878623 881565 889775
Changes:
 pyacoustid (1.1.5-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/changelog: Remove trailing whitespaces
   * Convert git repository from git-dpm to gbp layout
 .
   [ Sandro Tosi ]
   * New maintainer; Closes: 889775
   * New upstream release; Closes: #878623, #881565
   * debian/control
 - bump Standards-Version to 4.2.1 (no changes needed)
Checksums-Sha1:
 69b6309c7e9b91f6169d9faaa790702d21a42b7d 2109 pyacoustid_1.1.5-1.dsc
 90d70ff4162367ad5418842a272c42ae68a18adf 11846 pyacoustid_1.1.5.orig.tar.gz
 dbedccc63b055efa0b5566da901fa76e0d1658b7 2908 pyacoustid_1.1.5-1.debian.tar.xz
 d8f10e9dcac1269832dbe0428372f9a231deee74 7847 
pyacoustid_1.1.5-1_amd64.buildinfo
 4e66ab508e5144fb785cb76502521d5192af85a0 15476 python-acoustid_1.1.5-1_all.deb
 2236e317b13fd5abfc116d2058a2d95b2507a3cb 11892 python3-acoustid_1.1.5-1_all.deb
Checksums-Sha256:
 6a1d5078e5e08bc40c4d7f534e652968f3cb4731d192d90fff008ba0a4c5ecb0 2109 
pyacoustid_1.1.5-1.dsc
 efb6337a470c9301a108a539af7b775678ff67aa63944e9e04ce4216676cc777 11846 
pyacoustid_1.1.5.orig.tar.gz
 7ceb5e74331aa9947d5d526843429e8843fe6839823355f4a3b489fd1c05a676 2908 
pyacoustid_1.1.5-1.debian.tar.xz
 bebdb50eb7d201115bc53c1a6f9e031c6c2eafe778820ba47bf0c069f837de5c 7847 
pyacoustid_1.1.5-1_amd64.buildinfo
 9e82082de881b1a43a137e23f756bea011fd45fec7718c6c66498920ef3a2af8 15476 
python-acoustid_1.1.5-1_all.deb
 3b1fee05baf3f7d53ac27ab902c391df14408857a57900d432461b0b96eba889 11892 
python3-acoustid_1.1.5-1_all.deb
Files:
 5ec5a58b5d0e63eae355251c690c491b 2109 python optional pyacoustid_1.1.5-1.dsc
 036a4754343d1f9c894004c82d8309bd 11846 python optional 
pyacoustid_1.1.5.orig.tar.gz
 6abc6b87189902394cef9c474f19d2c9 

Bug#881566: marked as done (python-acoustid: incompatible/broken on Python 3 (fix available upstream))

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 23:58:02 +
with message-id 
and subject line Bug#881565: fixed in pyacoustid 1.1.5-1
has caused the Debian Bug report #881565,
regarding python-acoustid: incompatible/broken on Python 3 (fix available 
upstream)
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.)


-- 
881565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-acoustid
Version: 1.1.2-2
Severity: important

Dear Maintainer,

The current version of python-acoustid doesn't work with Python 3.
Specifically the submit() function to submit fingerprints is broken:
https://github.com/beetbox/pyacoustid/pull/33

There is a fix available upstream in the 1.1.5 release. Could you please
update the Debian packaging to include this fix?

Thanks,
James


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

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

Versions of packages python3-acoustid depends on:
ii  libchromaprint11.4.2-1
ii  python33.6.3-2
pn  python3-audioread  
ii  python3-requests   2.18.1-1

python3-acoustid recommends no packages.

python3-acoustid suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pyacoustid
Source-Version: 1.1.5-1

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated pyacoustid package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 23 Nov 2018 18:24:26 -0500
Source: pyacoustid
Binary: python-acoustid python3-acoustid
Architecture: source all
Version: 1.1.5-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Description:
 python-acoustid - Acoustid interface implementation and Chromaprint bindings
 python3-acoustid - Acoustid interface implementation and Chromaprint bindings 
(Pytho
Closes: 878623 881565 889775
Changes:
 pyacoustid (1.1.5-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/changelog: Remove trailing whitespaces
   * Convert git repository from git-dpm to gbp layout
 .
   [ Sandro Tosi ]
   * New maintainer; Closes: 889775
   * New upstream release; Closes: #878623, #881565
   * debian/control
 - bump Standards-Version to 4.2.1 (no changes needed)
Checksums-Sha1:
 69b6309c7e9b91f6169d9faaa790702d21a42b7d 2109 pyacoustid_1.1.5-1.dsc
 90d70ff4162367ad5418842a272c42ae68a18adf 11846 pyacoustid_1.1.5.orig.tar.gz
 dbedccc63b055efa0b5566da901fa76e0d1658b7 2908 pyacoustid_1.1.5-1.debian.tar.xz
 d8f10e9dcac1269832dbe0428372f9a231deee74 7847 
pyacoustid_1.1.5-1_amd64.buildinfo
 4e66ab508e5144fb785cb76502521d5192af85a0 15476 python-acoustid_1.1.5-1_all.deb
 2236e317b13fd5abfc116d2058a2d95b2507a3cb 11892 python3-acoustid_1.1.5-1_all.deb
Checksums-Sha256:
 6a1d5078e5e08bc40c4d7f534e652968f3cb4731d192d90fff008ba0a4c5ecb0 2109 
pyacoustid_1.1.5-1.dsc
 efb6337a470c9301a108a539af7b775678ff67aa63944e9e04ce4216676cc777 11846 
pyacoustid_1.1.5.orig.tar.gz
 7ceb5e74331aa9947d5d526843429e8843fe6839823355f4a3b489fd1c05a676 2908 
pyacoustid_1.1.5-1.debian.tar.xz
 bebdb50eb7d201115bc53c1a6f9e031c6c2eafe778820ba47bf0c069f837de5c 7847 
pyacoustid_1.1.5-1_amd64.buildinfo
 9e82082de881b1a43a137e23f756bea011fd45fec7718c6c66498920ef3a2af8 15476 
python-acoustid_1.1.5-1_all.deb
 3b1fee05baf3f7d53ac27ab902c391df14408857a57900d432461b0b96eba889 11892 
python3-acoustid_1.1.5-1_all.deb
Files:
 5ec5a58b5d0e63eae355251c690c491b 2109 python optional pyacoustid_1.1.5-1.dsc
 036a4754343d1f9c894004c82d8309bd 11846 python optional 
pyacoustid_1.1.5.orig.tar.gz
 

Processed: Bug #881565 in pyacoustid marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #881565 [python3-acoustid] python-acoustid: incompatible with python3 (fix 
availble upstream)
Bug #881566 [python3-acoustid] python-acoustid: incompatible/broken on Python 3 
(fix available upstream)
Added tag(s) pending.
Added tag(s) pending.

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

Bug#881565: Bug #881565 in pyacoustid marked as pending

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #881565 in pyacoustid reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/pyacoustid/commit/19e05f4452d89f7267dd1ee2baf6bc8e5b502ecb


New upstream release; Closes: #878623, #881565



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/881565

Processed: your mail

[Debian Bug Tracking System]

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

> block 914450 by 914448
Bug #914450 [ftp.debian.org] RM: lucene2 -- ROM; Obsolete, no longer used
914450 was not blocked by any bugs.
914450 was not blocking any bugs.
Added blocking bug(s) of 914450: 914448
> block 914452 by 914448
Bug #914452 [ftp.debian.org] RM: asm3 -- ROM; Obsolete, no longer used
914452 was not blocked by any bugs.
914452 was not blocking any bugs.
Added blocking bug(s) of 914452: 914448
> block 914463 by 914450
Bug #914463 [ftp.debian.org] RM: icu4j-4.2 -- ROM; Obsolete, no longer used
914463 was not blocked by any bugs.
914463 was not blocking any bugs.
Added blocking bug(s) of 914463: 914450
> block 914466 by 914448
Bug #914466 [ftp.debian.org] RM: icu4j-49 -- ROM; Obsolete, no longer used
914466 was not blocked by any bugs.
914466 was not blocking any bugs.
Added blocking bug(s) of 914466: 914448
> block 914467 by 914448
Bug #914467 [ftp.debian.org] RM: swt-gtk -- ROM; No longer used, superseded by 
swt4-gtk
914467 was not blocked by any bugs.
914467 was not blocking any bugs.
Added blocking bug(s) of 914467: 914448
> block 914467 by 912216
Bug #914467 [ftp.debian.org] RM: swt-gtk -- ROM; No longer used, superseded by 
swt4-gtk
914467 was blocked by: 914448
914467 was not blocking any bugs.
Added blocking bug(s) of 914467: 912216
>
End of message, stopping processing here.

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

Bug#899796: marked as done (input-pad: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 22:10:46 +
with message-id 
and subject line Bug#899796: fixed in input-pad 1.0.3-2
has caused the Debian Bug report #899796,
regarding input-pad: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of input-pad,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: input-pad
Source-Version: 1.0.3-2

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated input-pad package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 23 Nov 2018 11:21:35 -0500
Source: input-pad
Binary: gir1.2-input-pad-1.0 input-pad libinput-pad-dev libinput-pad-xtest 
libinput-pad1 python-input-pad
Architecture: source
Version: 1.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Description:
 gir1.2-input-pad-1.0 - On-screen Input Pad to Send Characters with Mouse - 
introspection
 input-pad  - On-screen Input Pad to Send Characters with Mouse
 libinput-pad-dev - On-screen Input Pad to Send Characters with Mouse - dev
 libinput-pad-xtest - On-screen Input Pad to Send Characters with Mouse - xtest
 libinput-pad1 - On-screen Input Pad to Send Characters with Mouse - libs
 python-input-pad - On-screen Input Pad to Send Characters with Mouse - python
Closes: 841804 899796
Changes:
 input-pad (1.0.3-2) unstable; urgency=medium
 .
   * Team upload.
   * debian:
 + Apply "wrap-and-sort -abst".
 + Bump debhelper compat to v11.
   * debian/control:
 + Remove LI Daobing from uploaders list. (Closes: #841804)
 + Update maintainer address and use Debian Input Method Team.
   (Closes: #899796)
 + Bump Standards-Version to 4.2.1.
 + Update homepage and use the project on GitHub.
 + Update Vcs-* fields and use git 

Bug#914496: gitlab-shell: Fail on gitlab-shell on git push

[David L]

Package: gitlab-shell
Version: 8.3.3+dfsg-1
Severity: grave
Justification: renders package unusable


Doing a git push on a repository connected to gitlab, I receive this error:

BloudFire:repository maqui$ git push origin
/usr/share/gitlab-shell/bin/gitlab-shell:10:in `require_relative': cannot load 
such file -- /usr/share/gitlab-shell/bin/gitlab_init (LoadError)
from /usr/share/gitlab-shell/bin/gitlab-shell:10:in `'
fatal: No se pudo leer del repositorio remoto.

Testing on gitlab server, the file gitlab_init does not exist on this 
repository. They are a gitlab_init.rb on /usr/lib/ruby/vendor_ruby folder.


With this fail, gitlab is unusable, because I cannot commit to the repository 
or download from it.


Thanks,


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

Kernel: Linux 4.9.23--grs-ipv6-64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=locale: Cannot set LC_CTYPE 
to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968), LANGUAGE=en_GB:en (charmap=locale: Cannot set LC_CTYPE to 
default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab-shell depends on:
ii  libc6  2.27-8
ii  ruby   1:2.5.1

gitlab-shell recommends no packages.

gitlab-shell suggests no packages.

-- debconf-show failed

Bug#911266: marked as done (mosquitto: CVE-2017-7653)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 21:39:29 +
with message-id 
and subject line Bug#911266: fixed in mosquitto 1.5.4-1
has caused the Debian Bug report #911266,
regarding mosquitto: CVE-2017-7653
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.)


-- 
911266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mosquitto
Version: 1.4.10-1
Severity: grave
Tags: patch security upstream
Forwarded: https://bugs.eclipse.org/bugs/show_bug.cgi?id=532113

Hi,

The following vulnerability was published for mosquitto. Planned to be
fixed in a DSA, and needs to be fixed for buster as reason for the RC
severity filling.

CVE-2017-7653[0]:
| The Eclipse Mosquitto broker up to version 1.4.15 does not reject
| strings that are not valid UTF-8. A malicious client could cause other
| clients that do reject invalid UTF-8 strings to disconnect themselves
| from the broker by sending a topic string which is not valid UTF-8,
| and so cause a denial of service for the clients.

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-2017-7653
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7653
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=532113
[2] 
https://github.com/eclipse/mosquitto/commit/729a09310a7a56fbe5933b70b4588049da1a42b4

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: mosquitto
Source-Version: 1.5.4-1

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

Debian distribution maintenance software
pp.
Roger A. Light  (supplier of updated mosquitto 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, 08 Nov 2018 13:34:59 +
Source: mosquitto
Binary: mosquitto mosquitto-dev libmosquitto1 libmosquitto-dev libmosquittopp1 
libmosquittopp-dev mosquitto-clients
Architecture: source
Version: 1.5.4-1
Distribution: unstable
Urgency: medium
Maintainer: Roger A. Light 
Changed-By: Roger A. Light 
Description:
 libmosquitto-dev - MQTT version 3.1/3.1.1 client library, development files
 libmosquitto1 - MQTT version 3.1/3.1.1 client library
 libmosquittopp-dev - MQTT version 3.1 client C++ library, development files
 libmosquittopp1 - MQTT version 3.1/3.1.1 client C++ library
 mosquitto  - MQTT version 3.1/3.1.1 compatible message broker
 mosquitto-clients - Mosquitto command line MQTT clients
 mosquitto-dev - Development files for Mosquitto
Closes: 901424 911104 911265 911266
Changes:
 mosquitto (1.5.4-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #911104).
 - Fixes CVE-2017-7654 (Closes: #911265)
 - Fixes CVE-2017-7653 (Closes: #911266)
   * Remove no longer needed patches. Some are integrated into upstream, others
 have been replaced with changes in rules.
 - async_dns.patch
 - build-timestamp.patch
 - disable-in-tree-uthash.patch
 - enable-libwrap.patch
 - enable-websockets.patch
 - fix-prefix.patch
 - hurd-errno.patch
 - libdir.patch
 - nostrip.patch
   * Copyright fix - src/uthash.h -> src/deps/uthash.h
   * Update symbols files with new additions.
   * Remove debian/mosquitto.prerm
 - Calls to invoke-rc.d to stop mosquitto will be inserted automagically by
   debhelper.
   * Stop removing the mosquitto user in postrm.
 - This is not safe since there might still be logs (and other files?)
   around owned by the uid, so we don't want it reused for a new user.
   * Add build dependency on libsystemd-dev.
   * Enable systemd build support.
   * Ship the mosquitto.service file (with sd-notify support)
   * Drop -dbg packages and do -dbgsym migration.
   * libmosquito{,pp}-dev: ship libmosquitto{,pp}.pc respectively.
   * Remove unused build dependency on python-all. (Closes: #901424).
   * Bump standards version to 4.2.1, no changes needed.
   * Bumped dh compat level to 11.
   * Add 

Bug#911265: marked as done (mosquitto: CVE-2017-7654)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 21:39:29 +
with message-id 
and subject line Bug#911265: fixed in mosquitto 1.5.4-1
has caused the Debian Bug report #911265,
regarding mosquitto: CVE-2017-7654
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.)


-- 
911265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mosquitto
Version: 1.4.10-1
Severity: grave
Tags: patch security upstream
Forwarded: https://bugs.eclipse.org/bugs/show_bug.cgi?id=533493

Hi,

The following vulnerability was published for mosquitto.

Filling with RC severity as it will be fixed in a DSA, and needs to be
fixed before buster release in unstable/testing as well.

CVE-2017-7654[0]:
| In Eclipse Mosquitto 1.4.15 and earlier, a Memory Leak vulnerability
| was found within the Mosquitto Broker. Unauthenticated clients can
| send crafted CONNECT packets which could cause a denial of service in
| the Mosquitto Broker.

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-2017-7654
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7654
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=533493
[2] 
https://github.com/eclipse/mosquitto/commit/51ec5601c2ec523bf2973fdc1eca77335eafb8de

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: mosquitto
Source-Version: 1.5.4-1

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

Debian distribution maintenance software
pp.
Roger A. Light  (supplier of updated mosquitto 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, 08 Nov 2018 13:34:59 +
Source: mosquitto
Binary: mosquitto mosquitto-dev libmosquitto1 libmosquitto-dev libmosquittopp1 
libmosquittopp-dev mosquitto-clients
Architecture: source
Version: 1.5.4-1
Distribution: unstable
Urgency: medium
Maintainer: Roger A. Light 
Changed-By: Roger A. Light 
Description:
 libmosquitto-dev - MQTT version 3.1/3.1.1 client library, development files
 libmosquitto1 - MQTT version 3.1/3.1.1 client library
 libmosquittopp-dev - MQTT version 3.1 client C++ library, development files
 libmosquittopp1 - MQTT version 3.1/3.1.1 client C++ library
 mosquitto  - MQTT version 3.1/3.1.1 compatible message broker
 mosquitto-clients - Mosquitto command line MQTT clients
 mosquitto-dev - Development files for Mosquitto
Closes: 901424 911104 911265 911266
Changes:
 mosquitto (1.5.4-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #911104).
 - Fixes CVE-2017-7654 (Closes: #911265)
 - Fixes CVE-2017-7653 (Closes: #911266)
   * Remove no longer needed patches. Some are integrated into upstream, others
 have been replaced with changes in rules.
 - async_dns.patch
 - build-timestamp.patch
 - disable-in-tree-uthash.patch
 - enable-libwrap.patch
 - enable-websockets.patch
 - fix-prefix.patch
 - hurd-errno.patch
 - libdir.patch
 - nostrip.patch
   * Copyright fix - src/uthash.h -> src/deps/uthash.h
   * Update symbols files with new additions.
   * Remove debian/mosquitto.prerm
 - Calls to invoke-rc.d to stop mosquitto will be inserted automagically by
   debhelper.
   * Stop removing the mosquitto user in postrm.
 - This is not safe since there might still be logs (and other files?)
   around owned by the uid, so we don't want it reused for a new user.
   * Add build dependency on libsystemd-dev.
   * Enable systemd build support.
   * Ship the mosquitto.service file (with sd-notify support)
   * Drop -dbg packages and do -dbgsym migration.
   * libmosquito{,pp}-dev: ship libmosquitto{,pp}.pc respectively.
   * Remove unused build dependency on python-all. (Closes: #901424).
   * Bump standards version to 4.2.1, no changes needed.
   * Bumped dh compat level to 11.
   * Add upstream/metadata.
Checksums-Sha1:
 828c141c592f5b79fce2a22b2c01b75185719471 

Bug#874962: marked as done ([knights] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 21:38:22 +
with message-id 
and subject line Bug#874962: fixed in knights 18.11.80-1
has caused the Debian Bug report #874962,
regarding [knights] Future Qt4 removal from 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.)


-- 
874962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: knights
Version: 2.5.0-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: knights
Source-Version: 18.11.80-1

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated knights package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 23 Nov 2018 22:20:19 +0100
Source: knights
Binary: knights
Architecture: source
Version: 18.11.80-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Description:
 knights- chess interface for the KDE Platform
Closes: 874962
Changes:
 knights (18.11.80-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream development release: (Closes: #874962) (LP: #1757703)
 - now part of KDE Applications, so adopt its versioning
   * Switch Vcs-* fields to salsa.debian.org.
   * Remove knights-dbg in favour of the -dbgsym package
 - stop forcing --destdir for dh_auto_install, as there is only one binary
   now
   * Bump the debhelper compatibility to 11:
 - bump the debhelper build dependency to 11~
 - bump compat to 11
 - remove --parallel for dh, as now done by default
   * Drop the Debian-provided knights man page, as knights does not really have
 command line options.
   * Remove trailing whitespaces in changelog, and control.
   * Remove empty line at the end of changelog.
   * Bump Standards-Version to 4.2.1, no changes required.
   * Add a watch file.
   * Add the upstream GPG signing key.
   * Update the build dependencies following the port to Frameworks:
 - remove kdelibs5-dev, and libkdegames-dev
 - add extra-cmake-modules, qtbase5-dev, libqt5svg5-dev,
   libqt5texttospeech5-dev, libkf5configwidgets-dev, 

Bug#914495: linux-image-4.18.0-3-amd64: does not boot here

[TS]

Package: src:linux
Version: 4.18.20-1
Severity: critical
Justification: breaks the whole system

Dear Maintainers,

linux-image-4.18.0-3-amd64 does not boot on this computer.
After grub shortly cursor is blinking upper left (when usually the initrd is
deflating and systemd starts).
After that nothing happens.
HDD LED does not signalling activity.
Display stays dark, no messages appear with
GRUB_CMDLINE_LINUX_DEFAULT="quiet consoleblank=0 systemd.show_status=1"
set.

initrd has been rebuild manually before rebooting with
dpkg-reconfigure linux-image-...

as i get used to.

Booting linux-image-4.18.0-2-amd64 instead solves the issue.

Since the issue happens very early in boot process debugging is quit difficult.
Assistance with further debugging is required if you need additional 
informations.



kind regards,

 Thilo


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: TOSHIBA
product_name: Satellite L300
product_version: PSLB8E-12T018GR
chassis_vendor: Chassis Manufacturer
chassis_version: Chassis Version
bios_vendor: INSYDE
bios_version: 1.80
board_vendor: TOSHIBA
board_name: Portable PC
board_version: Base Board Version

** Network interface configuration:


auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0




iface ethernet inet static
network 192.168.10.0
gateway 192.168.10.1
broadcast   192.168.10.255
netmask 255.255.255.0
dns-nameservers 127.0.0.1

allow-hotplug eth0
iface eth0 inet static inherits ethernet
address 192.168.10.4


** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory
Controller Hub [8086:2a40] (rev 07)
Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Memory
Controller Hub [1179:ff66]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping-
SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series
Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA
controller])
Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset 
Integrated
Graphics Controller [1179:ff67]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping-
SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset
Integrated Graphics Controller [8086:2a43] (rev 07)
Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset 
Integrated
Graphics Controller [1179:ff67]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping-
SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #4 [8086:2937] (rev 03) (prog-if 00 [UHCI])
Subsystem: Toshiba America Info Systems 82801I (ICH9 Family) USB UHCI
Controller [1179:ff66]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping-
SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd

00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #5 [8086:2938] (rev 03) (prog-if 00 [UHCI])
Subsystem: Toshiba America Info Systems 82801I (ICH9 Family) USB UHCI
Controller [1179:ff66]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping-
SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd

00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI
Controller #2 [8086:293c] (rev 03) (prog-if 20 [EHCI])
Subsystem: Toshiba America Info Systems 82801I (ICH9 Family) USB2 EHCI
Controller [1179:ff66]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping-
SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio
Controller [8086:293e] (rev 03)
Subsystem: Toshiba America Info Systems 82801I (ICH9 Family) HD Audio
Controller [1179:ff66]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping-
SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: 

Bug#914262: marked as done (Segfaults on "Write Output" if more than 8 keysyms per key are present)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 21:33:35 +
with message-id 
and subject line Bug#914262: fixed in xkeycaps 2.47-4.1+deb9u1
has caused the Debian Bug report #914262,
regarding Segfaults on "Write Output" if more than 8 keysyms per key are present
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.)


-- 
914262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xkeycaps
Version: 2.47-4.1
Severity: grave
Tags: stretch patch

The code only deals with 8 names per key, but unfortunately doesn't expose that
number as a constant that is easily changed. Clip to 8 so we don't segfault.

 Program received signal SIGSEGV, Segmentation fault.
 strlen () at ../sysdeps/x86_64/strlen.S:106
 106   ../sysdeps/x86_64/strlen.S: Datei oder Verzeichnis nicht gefunden.
 (gdb) bt
 #0  strlen () at ../sysdeps/x86_64/strlen.S:106
 #1  0x76a2fa45 in __GI__IO_fputs (
 str=str@entry=0x7fff000a ,
 fp=fp@entry=0x559f6da0) at iofputs.c:33
 #2  0x555dc2a4 in fprintf (__fmt=0x555e49e1 "%s", 
__stream=)
 at /usr/include/x86_64-linux-gnu/bits/stdio2.h:97
 #3  button_write (button=, client_data=,
 call_data=) at commands.c:629
 #4  0x77944aad in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6
 #5  0x77944f15 in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6
 #6  0x77945bdd in _XtTranslateEvent () from 
/usr/lib/x86_64-linux-gnu/libXt.so.6
 #7  0x7791def2 in XtDispatchEventToWidget () from 
/usr/lib/x86_64-linux-gnu/libXt.so.6
 #8  0x7791e8dd in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6
 #9  0x7791e9b9 in XtDispatchEvent () from 
/usr/lib/x86_64-linux-gnu/libXt.so.6
 #10 0x555d2d96 in xkeycaps_main_loop (app=0x559a81a0, 
keyboard=)
 at xkeycaps.c:232
 #11 main (argc=, argv=) at xkeycaps.c:355
 (gdb) f 3
 #3  button_write (button=, client_data=,
 call_data=) at commands.c:629
 629 fprintf (out, "%s", differences[i].names[j]);
 (gdb) p i
 $1 = 1
 (gdb) p j
 $2 = 9
 (gdb) p differences
 $3 = {{key = 0x55a0dde0, count = 3, names = {0x76e13fc6 
<_XkeyTable+134> "Escape",
   0x555e4448 "NoSymbol", 0x76e13fc6 <_XkeyTable+134> "Escape", 0x0,
   0x1d7 ,
   0x1000 ,
   0x8 ,
   0x5a42ab91 }}, {key = 
0x55a0dfa0,
 count = 10, names = {0x76e144be <_XkeyTable+1406> "F1",
   0x76e144be <_XkeyTable+1406> "F1", 0x76e144be <_XkeyTable+1406> 
"F1",
   0x76e144be <_XkeyTable+1406> "F1", 0x76e144be <_XkeyTable+1406> 
"F1",
   0x76e144be <_XkeyTable+1406> "F1",
   0x76e1dfaf <_XkeyTable+41071> "XF86Switch_VT_1",
   0x76e144be <_XkeyTable+1406> "F1"}}, {key = 0x55a0e160, count = 
10, names = {
   0x76e144c7 <_XkeyTable+1415> "F2", 0x76e144c7 <_XkeyTable+1415> 
"F2",
   0x76e144c7 <_XkeyTable+1415> "F2", 0x76e144c7 <_XkeyTable+1415> 
"F2",
   0x76e144c7 <_XkeyTable+1415> "F2", 0x76e144c7 <_XkeyTable+1415> 
"F2",
   0x76e1dfc5 <_XkeyTable+41093> "XF86Switch_VT_2",
   0x76e144c7 <_XkeyTable+1415> "F2"}},

--- a/commands.c
+++ b/commands.c
@@ -440,6 +440,7 @@ button_write (button, client_data, call_
 keysyms = XGetKeyboardMapping (XtDisplay (widget),
key->key.keycode,
1, );
+if (count > 8) count = 8; /* FIXME: we are only prepared for 8 
names per key, clip here */
 if (! keysyms) count = 0;
 all [all_count].key = key;
 for (; count > 0; count--)


Christoph
--- End Message ---
--- Begin Message ---
Source: xkeycaps
Source-Version: 2.47-4.1+deb9u1

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated xkeycaps 
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, 21 Nov 2018 09:47:46 +0100
Source: xkeycaps

Processed: libfclib0: hard codes library dependency

[Debian Bug Tracking System]

Processing control commands:

> block 913837 by -1
Bug #913837 [release.debian.org] transition: hdf5
913837 was not blocked by any bugs.
913837 was not blocking any bugs.
Added blocking bug(s) of 913837: 914493

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

Bug#910431: marked as done (qemu: CVE-2018-10839: integer overflow leads to buffer overflow issue)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 21:32:54 +
with message-id 
and subject line Bug#910431: fixed in qemu 1:2.8+dfsg-6+deb9u5
has caused the Debian Bug report #910431,
regarding qemu: CVE-2018-10839: integer overflow leads to buffer overflow issue
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.)


-- 
910431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu
Version: 1:2.12+dfsg-3
Severity: important
Tags: security upstream
Forwarded: https://lists.gnu.org/archive/html/qemu-devel/2018-09/msg03273.html
Control: found -1 1:2.8+dfsg-1

Hi,

The following vulnerability was published for qemu.

CVE-2018-10839[0]:
ne2000: integer overflow leads to buffer overflow issue

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-10839
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10839
[1] https://lists.gnu.org/archive/html/qemu-devel/2018-09/msg03273.html

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:2.8+dfsg-6+deb9u5

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

Debian distribution maintenance software
pp.
Moritz Mühlenhoff  (supplier of updated qemu 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, 08 Nov 2018 16:41:45 +0100
Source: qemu
Binary: qemu qemu-system qemu-block-extra qemu-system-common qemu-system-misc 
qemu-system-arm qemu-system-mips qemu-system-ppc qemu-system-sparc 
qemu-system-x86 qemu-user qemu-user-static qemu-user-binfmt qemu-utils 
qemu-guest-agent qemu-kvm
Architecture: source amd64
Version: 1:2.8+dfsg-6+deb9u5
Distribution: stretch-security
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: Moritz Mühlenhoff 
Description:
 qemu   - fast processor emulator
 qemu-block-extra - extra block backend modules for qemu-system and qemu-utils
 qemu-guest-agent - Guest-side qemu-system agent
 qemu-kvm   - QEMU Full virtualization on x86 hardware
 qemu-system - QEMU full system emulation binaries
 qemu-system-arm - QEMU full system emulation binaries (arm)
 qemu-system-common - QEMU full system emulation binaries (common files)
 qemu-system-mips - QEMU full system emulation binaries (mips)
 qemu-system-misc - QEMU full system emulation binaries (miscellaneous)
 qemu-system-ppc - QEMU full system emulation binaries (ppc)
 qemu-system-sparc - QEMU full system emulation binaries (sparc)
 qemu-system-x86 - QEMU full system emulation binaries (x86)
 qemu-user  - QEMU user mode emulation binaries
 qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user
 qemu-user-static - QEMU user mode emulation binaries (static version)
 qemu-utils - QEMU utilities
Closes: 908682 910431 911468 911469
Changes:
 qemu (1:2.8+dfsg-6+deb9u5) stretch-security; urgency=medium
 .
   * Backport SSBD support (Closes: #908682)
   * CVE-2018-10839 (Closes: #910431)
   * CVE-2018-17962 (Closes: #911468)
   * CVE-2018-17963 (Closes: #911469)
Checksums-Sha1:
 51d9a6ab1938acf80d1c4dda5eccbbbacb196cca 5904 qemu_2.8+dfsg-6+deb9u5.dsc
 43e41704d1befe6ff21fe4c460974938fd1a9d1c 153452 
qemu_2.8+dfsg-6+deb9u5.debian.tar.xz
 2bb046d38c6d176249b9faba8578ee458ce2e012 276060 
qemu-block-extra-dbgsym_2.8+dfsg-6+deb9u5_amd64.deb
 15061b0a968f84e910391246697ffa138adebc86 105362 
qemu-block-extra_2.8+dfsg-6+deb9u5_amd64.deb
 4c29681c0248affe9784649493869a7a6b1b1c00 771368 
qemu-guest-agent-dbgsym_2.8+dfsg-6+deb9u5_amd64.deb
 48d4cd0816ed6560f73e2df2b436a37ee2f7d3fe 314908 
qemu-guest-agent_2.8+dfsg-6+deb9u5_amd64.deb
 dc30f657ff3fae27899a50d65e0ffbeca0429fce 66802 
qemu-kvm_2.8+dfsg-6+deb9u5_amd64.deb
 710b232915152ba891b7fb06ab69c73a94514c8c 33553014 
qemu-system-arm-dbgsym_2.8+dfsg-6+deb9u5_amd64.deb
 26ba135064c64507e1f6aa94fefa161b0720436a 5246398 
qemu-system-arm_2.8+dfsg-6+deb9u5_amd64.deb
 

Bug#914493: libfclib0: hard codes library dependency

[Mattia Rizzolo]

Package: libfclib0
Version: 3.0.0+dfsg-1
Severity: serious
Control: block 913837 by -1

Dear maintainer,

your source package has this:

Package: libfclib0
Architecture: any
Multi-Arch: same
Section: libs
Depends: ${misc:Depends},
 ${shlibs:Depends},
 libhdf5-100,
 libsuitesparse-dev (>= 1:5.1.2)

This is no good in at least two ways:

 * you hardcode a depdency on libhdf5-100, which made me notice this,
   since now there is a transition going on to libhdf5-103.  the shlibs
   mechanism finds the depedency just fine (and if it didn't it would be
   a different bug in this package anyway), so please just plain drop
   this.
 * there is a depedency on a development package.  That's plain
   worrisome, why would you need that??  I suppose you just wanted a
   depdency on suitparse, and the shlibs mechanism perfectly finds
   libcxsparse3 already, so there shouldn't be any need for that, I
   hope.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#911175: marked as done (ghostscript: CVE-2018-18284: 1Policy operator gives access to .forceput)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 21:32:28 +
with message-id 
and subject line Bug#911175: fixed in ghostscript 9.25~dfsg-0+deb9u1
has caused the Debian Bug report #911175,
regarding ghostscript: CVE-2018-18284: 1Policy operator gives access to 
.forceput
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.)


-- 
911175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ghostscript
Version: 9.20~dfsg-1
Severity: grave
Tags: patch security upstream
Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=699963

Hi,

The following vulnerability was published for ghostscript.

CVE-2018-18284[0]:
1Policy operator gives access to .forceput

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-18284
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-18284
[1] https://bugs.ghostscript.com/show_bug.cgi?id=699963
[2] https://bugs.chromium.org/p/project-zero/issues/detail?id=1696
[3] 
http://git.ghostscript.com/?p=ghostpdl.git;h=8d19fdf63f91f50466b08f23e2d93d37a4c5ea0b

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: ghostscript
Source-Version: 9.25~dfsg-0+deb9u1

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated ghostscript 
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, 08 Nov 2018 16:06:47 +0100
Source: ghostscript
Binary: ghostscript ghostscript-x ghostscript-doc libgs9 libgs9-common 
libgs-dev ghostscript-dbg
Architecture: source
Version: 9.25~dfsg-0+deb9u1
Distribution: stretch-security
Urgency: high
Maintainer: Debian Printing Team 
Changed-By: Salvatore Bonaccorso 
Closes: 909076 909929 910758 911175
Description: 
 ghostscript - interpreter for the PostScript language and for PDF
 ghostscript-dbg - interpreter for the PostScript language and for PDF - Debug 
symbo
 ghostscript-doc - interpreter for the PostScript language and for PDF - 
Documentati
 ghostscript-x - interpreter for the PostScript language and for PDF - X11 
support
 libgs-dev  - interpreter for the PostScript language and for PDF - Development
 libgs9 - interpreter for the PostScript language and for PDF - Library
 libgs9-common - interpreter for the PostScript language and for PDF - common 
file
Changes:
 ghostscript (9.25~dfsg-0+deb9u1) stretch-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * New upstream version 9.25~dfsg
 + Fixes regression using ps2ascii after fix for CVE-2018-17183
   (Closes: #909076)
 + status operator honour SAFER option (CVE-2018-11645)
   * Drop patches applied upstream
   * Rebase 2001_docdir_fix_for_debian.patch for 9.25
   * Rebase 2010_add_build_timestamp_setting.patch for 9.25
   * Add patches cherry-picked upstream to fix execution issues.
 + Implement .currentoutputdevice operator
 + Change "executeonly" to throw typecheck on gstatetype and
   devicetype objects
 + Undefine some additional internal operators.
 + Fix handling of .needinput if used from interpreter
 + Ensure all errors are included from initialization
 + setundercolorremoval memory corruption
 + copydevice fails after stack device copies invalidated
 + add operand checking to .setnativefontmapbuilt
 + add object type check for AES key
 + Add parameter type checking on .bigstring
 + zparse_dsc_comments can crash with invalid dsc_state
 + Catch errors in setpagesize, .setpagesize and setpagedevice and
   cleanup
 + Catch errors and cleanup stack on statusdict page size definitions
 + Add parameter checking in setresolution
 + device subclass open_device call must return child code
 + fix DSC comment parsing in pdfwrite
 + Check all uses of dict_find* to ensure 0 return 

Bug#911468: marked as done (qemu: CVE-2018-17962: pcnet: integer overflow leads to buffer overflow)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 21:32:54 +
with message-id 
and subject line Bug#911468: fixed in qemu 1:2.8+dfsg-6+deb9u5
has caused the Debian Bug report #911468,
regarding qemu: CVE-2018-17962: pcnet: integer overflow leads to buffer overflow
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.)


-- 
911468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu
Version: 1:2.12+dfsg-3
Severity: important
Tags: security upstream

Hi,

The following vulnerability was published for qemu.

CVE-2018-17962[0]:
| Qemu has a Buffer Overflow in pcnet_receive in hw/net/pcnet.c because
| an incorrect integer data type is used.

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-17962
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17962
[1] https://lists.gnu.org/archive/html/qemu-devel/2018-09/msg03268.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:2.8+dfsg-6+deb9u5

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

Debian distribution maintenance software
pp.
Moritz Mühlenhoff  (supplier of updated qemu 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, 08 Nov 2018 16:41:45 +0100
Source: qemu
Binary: qemu qemu-system qemu-block-extra qemu-system-common qemu-system-misc 
qemu-system-arm qemu-system-mips qemu-system-ppc qemu-system-sparc 
qemu-system-x86 qemu-user qemu-user-static qemu-user-binfmt qemu-utils 
qemu-guest-agent qemu-kvm
Architecture: source amd64
Version: 1:2.8+dfsg-6+deb9u5
Distribution: stretch-security
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: Moritz Mühlenhoff 
Description:
 qemu   - fast processor emulator
 qemu-block-extra - extra block backend modules for qemu-system and qemu-utils
 qemu-guest-agent - Guest-side qemu-system agent
 qemu-kvm   - QEMU Full virtualization on x86 hardware
 qemu-system - QEMU full system emulation binaries
 qemu-system-arm - QEMU full system emulation binaries (arm)
 qemu-system-common - QEMU full system emulation binaries (common files)
 qemu-system-mips - QEMU full system emulation binaries (mips)
 qemu-system-misc - QEMU full system emulation binaries (miscellaneous)
 qemu-system-ppc - QEMU full system emulation binaries (ppc)
 qemu-system-sparc - QEMU full system emulation binaries (sparc)
 qemu-system-x86 - QEMU full system emulation binaries (x86)
 qemu-user  - QEMU user mode emulation binaries
 qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user
 qemu-user-static - QEMU user mode emulation binaries (static version)
 qemu-utils - QEMU utilities
Closes: 908682 910431 911468 911469
Changes:
 qemu (1:2.8+dfsg-6+deb9u5) stretch-security; urgency=medium
 .
   * Backport SSBD support (Closes: #908682)
   * CVE-2018-10839 (Closes: #910431)
   * CVE-2018-17962 (Closes: #911468)
   * CVE-2018-17963 (Closes: #911469)
Checksums-Sha1:
 51d9a6ab1938acf80d1c4dda5eccbbbacb196cca 5904 qemu_2.8+dfsg-6+deb9u5.dsc
 43e41704d1befe6ff21fe4c460974938fd1a9d1c 153452 
qemu_2.8+dfsg-6+deb9u5.debian.tar.xz
 2bb046d38c6d176249b9faba8578ee458ce2e012 276060 
qemu-block-extra-dbgsym_2.8+dfsg-6+deb9u5_amd64.deb
 15061b0a968f84e910391246697ffa138adebc86 105362 
qemu-block-extra_2.8+dfsg-6+deb9u5_amd64.deb
 4c29681c0248affe9784649493869a7a6b1b1c00 771368 
qemu-guest-agent-dbgsym_2.8+dfsg-6+deb9u5_amd64.deb
 48d4cd0816ed6560f73e2df2b436a37ee2f7d3fe 314908 
qemu-guest-agent_2.8+dfsg-6+deb9u5_amd64.deb
 dc30f657ff3fae27899a50d65e0ffbeca0429fce 66802 
qemu-kvm_2.8+dfsg-6+deb9u5_amd64.deb
 710b232915152ba891b7fb06ab69c73a94514c8c 33553014 
qemu-system-arm-dbgsym_2.8+dfsg-6+deb9u5_amd64.deb
 26ba135064c64507e1f6aa94fefa161b0720436a 5246398 
qemu-system-arm_2.8+dfsg-6+deb9u5_amd64.deb
 

Bug#908682: marked as done (qemu: (CVE-2018-3639 SSB) qemu should be able to pass the ssbd cpu flag)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 21:32:54 +
with message-id 
and subject line Bug#908682: fixed in qemu 1:2.8+dfsg-6+deb9u5
has caused the Debian Bug report #908682,
regarding qemu: (CVE-2018-3639 SSB) qemu should be able to pass the ssbd cpu 
flag
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.)


-- 
908682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu
Version: 1:2.8+dfsg-6+deb9u4
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

To mitigate (CVE-2018-3639 SSB) qemu should pass the ssbd cpu flag and patches 
were made public in May 
"https://lists.gnu.org/archive/html/qemu-devel/2018-05/msg04795.html;

Is there a reason why the qemu stretch package still doesn't have this patch ?

Best regards,
Azad
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:2.8+dfsg-6+deb9u5

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

Debian distribution maintenance software
pp.
Moritz Mühlenhoff  (supplier of updated qemu 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, 08 Nov 2018 16:41:45 +0100
Source: qemu
Binary: qemu qemu-system qemu-block-extra qemu-system-common qemu-system-misc 
qemu-system-arm qemu-system-mips qemu-system-ppc qemu-system-sparc 
qemu-system-x86 qemu-user qemu-user-static qemu-user-binfmt qemu-utils 
qemu-guest-agent qemu-kvm
Architecture: source amd64
Version: 1:2.8+dfsg-6+deb9u5
Distribution: stretch-security
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: Moritz Mühlenhoff 
Description:
 qemu   - fast processor emulator
 qemu-block-extra - extra block backend modules for qemu-system and qemu-utils
 qemu-guest-agent - Guest-side qemu-system agent
 qemu-kvm   - QEMU Full virtualization on x86 hardware
 qemu-system - QEMU full system emulation binaries
 qemu-system-arm - QEMU full system emulation binaries (arm)
 qemu-system-common - QEMU full system emulation binaries (common files)
 qemu-system-mips - QEMU full system emulation binaries (mips)
 qemu-system-misc - QEMU full system emulation binaries (miscellaneous)
 qemu-system-ppc - QEMU full system emulation binaries (ppc)
 qemu-system-sparc - QEMU full system emulation binaries (sparc)
 qemu-system-x86 - QEMU full system emulation binaries (x86)
 qemu-user  - QEMU user mode emulation binaries
 qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user
 qemu-user-static - QEMU user mode emulation binaries (static version)
 qemu-utils - QEMU utilities
Closes: 908682 910431 911468 911469
Changes:
 qemu (1:2.8+dfsg-6+deb9u5) stretch-security; urgency=medium
 .
   * Backport SSBD support (Closes: #908682)
   * CVE-2018-10839 (Closes: #910431)
   * CVE-2018-17962 (Closes: #911468)
   * CVE-2018-17963 (Closes: #911469)
Checksums-Sha1:
 51d9a6ab1938acf80d1c4dda5eccbbbacb196cca 5904 qemu_2.8+dfsg-6+deb9u5.dsc
 43e41704d1befe6ff21fe4c460974938fd1a9d1c 153452 
qemu_2.8+dfsg-6+deb9u5.debian.tar.xz
 2bb046d38c6d176249b9faba8578ee458ce2e012 276060 
qemu-block-extra-dbgsym_2.8+dfsg-6+deb9u5_amd64.deb
 15061b0a968f84e910391246697ffa138adebc86 105362 
qemu-block-extra_2.8+dfsg-6+deb9u5_amd64.deb
 4c29681c0248affe9784649493869a7a6b1b1c00 771368 
qemu-guest-agent-dbgsym_2.8+dfsg-6+deb9u5_amd64.deb
 48d4cd0816ed6560f73e2df2b436a37ee2f7d3fe 314908 
qemu-guest-agent_2.8+dfsg-6+deb9u5_amd64.deb
 dc30f657ff3fae27899a50d65e0ffbeca0429fce 66802 
qemu-kvm_2.8+dfsg-6+deb9u5_amd64.deb
 710b232915152ba891b7fb06ab69c73a94514c8c 33553014 
qemu-system-arm-dbgsym_2.8+dfsg-6+deb9u5_amd64.deb
 26ba135064c64507e1f6aa94fefa161b0720436a 5246398 
qemu-system-arm_2.8+dfsg-6+deb9u5_amd64.deb
 dae8fa6d5c94b1463d58a925d78279e857d10641 329706 
qemu-system-common-dbgsym_2.8+dfsg-6+deb9u5_amd64.deb
 3ca4b1bab999da34a81934783465006e361c6405 501926 
qemu-system-common_2.8+dfsg-6+deb9u5_amd64.deb
 9e12e831caf035ad458b41209461708ed66d4f46 57946296 
qemu-system-mips-dbgsym_2.8+dfsg-6+deb9u5_amd64.deb
 3f96cdeb30073fcb5d32ab78410293292d471961 

Bug#909076: marked as done (ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 21:32:27 +
with message-id 
and subject line Bug#909076: fixed in ghostscript 9.25~dfsg-0+deb9u1
has caused the Debian Bug report #909076,
regarding ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--
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.)


-- 
909076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ghostscript
Version: 9.20~dfsg-3.2+deb9u5
Severity: serious
X-Debbugs-CC: t...@security.debian.org, Moritz Mühlenhoff , 
reproducible-bui...@lists.alioth.debian.org
Control: affects -1 diffoscope

Dear maintainer,

after the latest ghostscript security update, ps2ascii started to crash:

|% ps2ascii 
/build/diffoscope-101~bpo9+1/.pybuild/pythonX.Y_3.5/build/tests/data/test1.ps
|Error: /typecheck in --.bind--
|Operand stack:
|   --nostringval--   false   setshared   true   --dict:30/32(L)--   typecheck  
 --nostringval--   currentglobal   .currentglobal
|Execution stack:
|   %interp_exit   .runexec2   --nostringval--   --nostringval--   
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--   
--nostringval--   false   1   %stopped_push   1998   2   3   %oparray_pop   
1997   2   3   %oparray_pop   1981   2   3   %oparray_pop   1868   2   3   
%oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   
--nostringval--   --nostringval--   2   %stopped_push   --nostringval--   2009  
 3   3   %oparray_pop   --nostringval--   --nostringval--   
--dict:1267/1684(G)--   --nostringval--   1936   %dict_continue   
--nostringval--   1974   9   4   %oparray_pop   --nostringval--
|Dictionary stack:
|   --dict:1267/1684(G)--   --dict:0/20(G)--   --dict:81/200(L)--   
--dict:1267/1684(G)--
|Current allocation mode is global
|Current file position is 44643
|GPL Ghostscript 9.20: Unrecoverable error, exit code 1


Downgrading to 9.20~dfsg-3.2+deb9u4 shows the problem is limited to the
latest update:

|% ps2ascii 
/build/diffoscope-101~bpo9+1/.pybuild/pythonX.Y_3.5/build/tests/data/test1.ps
|
|
|Today's date: February 28, 2016
|
|1


This also causes diffoscope (both 78 in stretch and whatever is in
stretch-backports at the moment) to FTBFS.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ghostscript
Source-Version: 9.25~dfsg-0+deb9u1

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated ghostscript 
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, 08 Nov 2018 16:06:47 +0100
Source: ghostscript
Binary: ghostscript ghostscript-x ghostscript-doc libgs9 libgs9-common 
libgs-dev ghostscript-dbg
Architecture: source
Version: 9.25~dfsg-0+deb9u1
Distribution: stretch-security
Urgency: high
Maintainer: Debian Printing Team 
Changed-By: Salvatore Bonaccorso 
Closes: 909076 909929 910758 911175
Description: 
 ghostscript - interpreter for the PostScript language and for PDF
 ghostscript-dbg - interpreter for the PostScript language and for PDF - Debug 
symbo
 ghostscript-doc - interpreter for the PostScript language and for PDF - 
Documentati
 ghostscript-x - interpreter for the PostScript language and for PDF - X11 
support
 libgs-dev  - interpreter for the PostScript language and for PDF - Development
 libgs9 - interpreter for the PostScript language and for PDF - Library
 libgs9-common - interpreter for the PostScript language and for PDF - common 
file
Changes:
 ghostscript (9.25~dfsg-0+deb9u1) stretch-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * New upstream version 

Bug#911469: marked as done (qemu: CVE-2018-17963: net: ignore packets with large size)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 21:32:54 +
with message-id 
and subject line Bug#911469: fixed in qemu 1:2.8+dfsg-6+deb9u5
has caused the Debian Bug report #911469,
regarding qemu: CVE-2018-17963: net: ignore packets with large size
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.)


-- 
911469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu
Version: 1:2.12+dfsg-3
Severity: important
Tags: security upstream

Hi,

The following vulnerability was published for qemu.

CVE-2018-17963[0]:
| qemu_deliver_packet_iov in net/net.c in Qemu accepts packet sizes
| greater than INT_MAX, which allows attackers to cause a denial of
| service or possibly have unspecified other impact.

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-17963
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17963
[1] https://lists.gnu.org/archive/html/qemu-devel/2018-09/msg03267.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:2.8+dfsg-6+deb9u5

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

Debian distribution maintenance software
pp.
Moritz Mühlenhoff  (supplier of updated qemu 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, 08 Nov 2018 16:41:45 +0100
Source: qemu
Binary: qemu qemu-system qemu-block-extra qemu-system-common qemu-system-misc 
qemu-system-arm qemu-system-mips qemu-system-ppc qemu-system-sparc 
qemu-system-x86 qemu-user qemu-user-static qemu-user-binfmt qemu-utils 
qemu-guest-agent qemu-kvm
Architecture: source amd64
Version: 1:2.8+dfsg-6+deb9u5
Distribution: stretch-security
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: Moritz Mühlenhoff 
Description:
 qemu   - fast processor emulator
 qemu-block-extra - extra block backend modules for qemu-system and qemu-utils
 qemu-guest-agent - Guest-side qemu-system agent
 qemu-kvm   - QEMU Full virtualization on x86 hardware
 qemu-system - QEMU full system emulation binaries
 qemu-system-arm - QEMU full system emulation binaries (arm)
 qemu-system-common - QEMU full system emulation binaries (common files)
 qemu-system-mips - QEMU full system emulation binaries (mips)
 qemu-system-misc - QEMU full system emulation binaries (miscellaneous)
 qemu-system-ppc - QEMU full system emulation binaries (ppc)
 qemu-system-sparc - QEMU full system emulation binaries (sparc)
 qemu-system-x86 - QEMU full system emulation binaries (x86)
 qemu-user  - QEMU user mode emulation binaries
 qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user
 qemu-user-static - QEMU user mode emulation binaries (static version)
 qemu-utils - QEMU utilities
Closes: 908682 910431 911468 911469
Changes:
 qemu (1:2.8+dfsg-6+deb9u5) stretch-security; urgency=medium
 .
   * Backport SSBD support (Closes: #908682)
   * CVE-2018-10839 (Closes: #910431)
   * CVE-2018-17962 (Closes: #911468)
   * CVE-2018-17963 (Closes: #911469)
Checksums-Sha1:
 51d9a6ab1938acf80d1c4dda5eccbbbacb196cca 5904 qemu_2.8+dfsg-6+deb9u5.dsc
 43e41704d1befe6ff21fe4c460974938fd1a9d1c 153452 
qemu_2.8+dfsg-6+deb9u5.debian.tar.xz
 2bb046d38c6d176249b9faba8578ee458ce2e012 276060 
qemu-block-extra-dbgsym_2.8+dfsg-6+deb9u5_amd64.deb
 15061b0a968f84e910391246697ffa138adebc86 105362 
qemu-block-extra_2.8+dfsg-6+deb9u5_amd64.deb
 4c29681c0248affe9784649493869a7a6b1b1c00 771368 
qemu-guest-agent-dbgsym_2.8+dfsg-6+deb9u5_amd64.deb
 48d4cd0816ed6560f73e2df2b436a37ee2f7d3fe 314908 
qemu-guest-agent_2.8+dfsg-6+deb9u5_amd64.deb
 dc30f657ff3fae27899a50d65e0ffbeca0429fce 66802 
qemu-kvm_2.8+dfsg-6+deb9u5_amd64.deb
 710b232915152ba891b7fb06ab69c73a94514c8c 33553014 
qemu-system-arm-dbgsym_2.8+dfsg-6+deb9u5_amd64.deb
 26ba135064c64507e1f6aa94fefa161b0720436a 5246398 

Bug#911084: Bug #911084: sagemath crashes as cantor backend

[Bernhard Übelacker]

Dear Maintainer, hello Kinky Nekoboi,
just tried to reproduce this issue and there is really a crash.

In a minimal buster amd64 qemu VM,
with installed cantor and cantor-backend-sage packages.

Then follow these steps:
- start cantor
- select Sage backend
- enter in the field below the "Session 1" tab marked with ">>>":
plot(cos, (-5,5))
- press "Evaluate Worksheet"




The actual crash happens in cantor_sagebackend.so.
There the version of sagemath is tried to be retrieved by
executing "/usr/bin/sage -v".

Unfortunately this outputs just an error message, therefore
is nothing read from stdinput. In the console the output
"found version:  ()" from line 472 is visible.
This empty line is processed then by a regular expression
and that is expected to return results on index 1 and 2.


benutzer@debian:~$ /usr/bin/sage -v
/usr/bin/sage: line 16: /src/bin/sage-version.sh: No such file or directory


(gdb) list sagesession.cpp:462,500
462 bool SageSession::updateSageVersion()
463 {
464 QProcess get_sage_version;
465 
get_sage_version.setProgram(SageSettings::self()->path().toLocalFile());
466 
get_sage_version.setArguments(QStringList()<&2
else
. "$0-env" >&2
fi
...



Attached patch moves the sourcing of sage-env above the call to sage_version.
With that applied cantor successfully can draw and show that plot command.
But I really cannot estimate what else that could break elsewhere.



I think both issues deserve to be tracked separately:
- cantor_sagebackend.so should be more robust against the output of 
/usr/bin/sage
- /usr/bin/sage should report its version


Kind regards,
Bernhard


(gdb) bt
#0  0x7f97c94617ac in QString::toIntegral_helper (base=10, ok=0x0, 
len=, data=) at 
../../include/QtCore/../../src/corelib/tools/qstring.h:895
#1  QString::toInt (this=, ok=ok@entry=0x0, base=base@entry=10) 
at tools/qstring.cpp:7078
#2  0x7f97c005007d in SageSession::updateSageVersion() () at 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:115
#3  0x7f97c00503f1 in SageSession::login() () at 
./src/backends/sage/sagesession.cpp:119
#4  0x7f97b0042621 in Worksheet::loginToSession 
(this=this@entry=0x55b0052087f0) at ./src/worksheet.cpp:93
#5  0x7f97b0042c10 in Worksheet::evaluate() () at ./src/worksheet.cpp:457
#6  0x7f97b00387d2 in CantorPart::evaluateOrInterrupt() () at 
./src/cantor_part.cpp:529
#7  0x7f97b00767ed in CantorPart::qt_static_metacall (_o=, 
_id=, _a=, _c=) at 
./obj-x86_64-linux-gnu/src/cantorpart_autogen/EWIEGA46WW/moc_cantor_part.cpp:207
#8  0x7f97c95bb28b in QMetaObject::activate(QObject*, int, int, void**) () 
at kernel/qobject.cpp:3771
#9  0x7f97c95bb8a7 in QMetaObject::activate 
(sender=sender@entry=0x55b00525e970, m=m@entry=0x7f97ca3d1840 
, local_signal_index=local_signal_index@entry=1, 
argv=argv@entry=0x7ffdca3ab9d0) at kernel/qobject.cpp:3633
#10 0x7f97c9f01ee2 in QAction::triggered (this=this@entry=0x55b00525e970, 
_t1=) at .moc/moc_qaction.cpp:376
#11 0x7f97c9f044f0 in QAction::activate (this=0x55b00525e970, 
event=) at kernel/qaction.cpp:1166
#12 0x7f97c9fefc8d in QAbstractButtonPrivate::click (this=0x55b0053538b0) 
at widgets/qabstractbutton.cpp:397
#13 0x7f97c9fefec5 in QAbstractButton::mouseReleaseEvent 
(this=0x55b0053533a0, e=0x7ffdca3abea0) at widgets/qabstractbutton.cpp:1011
#14 0x7f97ca0d9c0a in QToolButton::mouseReleaseEvent (this=, 
e=) at widgets/qtoolbutton.cpp:622
#15 0x7f97c9f467c8 in QWidget::event (this=0x55b0053533a0, 
event=0x7ffdca3abea0) at kernel/qwidget.cpp:8925
#16 0x7f97c9ff1103 in QAbstractButton::event 
(this=this@entry=0x55b0053533a0, e=e@entry=0x7ffdca3abea0) at 
widgets/qabstractbutton.cpp:968
#17 0x7f97ca0d9cb3 in QToolButton::event (this=0x55b0053533a0, 
event=0x7ffdca3abea0) at widgets/qtoolbutton.cpp:985
#18 0x7f97c9f08491 in QApplicationPrivate::notify_helper 
(this=this@entry=0x55b004f5e380, receiver=receiver@entry=0x55b0053533a0, 
e=e@entry=0x7ffdca3abea0) at kernel/qapplication.cpp:3727
#19 0x7f97c9f0fd18 in QApplication::notify(QObject*, QEvent*) () at 
kernel/qapplication.cpp:3203
#20 0x7f97c9592039 in QCoreApplication::notifyInternal2(QObject*, QEvent*) 
() at 
../../include/QtCore/5.11.2/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:307
#21 0x7f97c9f0f019 in QCoreApplication::sendEvent (event=, 
receiver=) at 
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234
#22 QApplicationPrivate::sendMouseEvent 
(receiver=receiver@entry=0x55b0053533a0, event=event@entry=0x7ffdca3abea0, 
alienWidget=alienWidget@entry=0x55b0053533a0, nativeWidget=0x55b004fa5610, 
buttonDown=buttonDown@entry=0x7f97ca400870 , 
lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:2695
#23 0x7f97c9f61304 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () at 
/usr/include/c++/8/bits/atomic_base.h:390
#24 0x7f97c9f63e8e in 

Bug#914347: marked as done (vtk7: FTBFS against python 3.7.1 (now the default for python3))

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 21:05:14 +
with message-id 
and subject line Bug#914347: fixed in vtk7 7.1.1+dfsg1-10
has caused the Debian Bug report #914347,
regarding vtk7: FTBFS against python 3.7.1 (now the default for python3)
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.)


-- 
914347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vtk7
Version: 7.1.1+dfsg1-9
Severity: serious
Justification: FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

Python 3.7.1 is now the default for python3 [1], and vtk7 FTBFS [2] against 
this version:

/<>/vtk7-7.1.1+dfsg1/Wrapping/PythonCore/vtkPythonArgs.cxx: In 
instantiation of 'bool vtkPythonGetStringValue(PyObject*, T*&, const char*) 
[with T = char; PyObject = _object]':
/<>/vtk7-7.1.1+dfsg1/Wrapping/PythonCore/vtkPythonArgs.cxx:287:66:   
required from here
/<>/vtk7-7.1.1+dfsg1/Wrapping/PythonCore/vtkPythonArgs.cxx:105:25: 
error: invalid conversion from 'const char*' to 'char*' [-fpermissive]
 a = PyUnicode_AsUTF8(o);
 ^~~

[1] 
https://tracker.debian.org/news/1004786/accepted-python3-defaults-371-2-source-into-unstable/
[2] 
https://buildd.debian.org/status/fetch.php?pkg=vtk7=amd64=7.1.1%2Bdfsg1-9%2Bb1=1542847447=0
 

Thanks,

_g.

- -- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAlv2tzgACgkQ7+hsbH/+
z4OytAgAnzaibDNKJjCUMSEdLLY/L4zEQOkxGkTc8EYN084aU8ndQK1XP/M9HVdO
lI47VlRGLJzPsUlpzH0/nLvD/0Z+TQZuibZMlq6unZSXqwmCcMmS6mEiOGqOL+yO
u6TyPeTfBpGRsnFycY7RT/1VbfcyHsxRLd9ipTf9/3OWU+DxmWjm0xCnzuJjfUa4
rQdv8BrEQbPHH3WWHNZkhCvbJ7nQSfLB2HQwwbt1FLlZS6o/QByGb64KLS1yfg3p
MBZ3Ct5oAQ6NX87BGu1tiYeM6E5OKggKYWyAzbZrziMojIMqiteNjcQSDV7pq7b6
iCtv/bUAFc2AhRywKQ5fSu+dGdyPAA==
=ohUZ
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: vtk7
Source-Version: 7.1.1+dfsg1-10

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

Debian distribution maintenance software
pp.
Gert Wollny  (supplier of updated vtk7 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 23 Nov 2018 21:02:42 +0100
Source: vtk7
Binary: libvtk7-dev libvtk7-qt-dev libvtk7.1 libvtk7.1-qt libvtk7-jni 
libvtk7-java python3-vtk7 tcl-vtk7 vtk7 vtk7-doc vtk7-examples
Architecture: source
Version: 7.1.1+dfsg1-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Gert Wollny 
Description:
 libvtk7-dev - VTK header files
 libvtk7-java - Visualization Toolkit - A high level 3D visualization library - 
j
 libvtk7-jni - Visualization Toolkit - A high level 3D visualization library - j
 libvtk7-qt-dev - VTK header files, containing Qt files
 libvtk7.1  - VTK libraries
 libvtk7.1-qt - VTK libraries, Qt files
 python3-vtk7 - Python bindings for VTK
 tcl-vtk7   - Tcl bindings for VTK
 vtk7   - Binaries for VTK7
 vtk7-doc   - VTK class reference documentation
 vtk7-examples - VTK examples
Closes: 911793 914347
Changes:
 vtk7 (7.1.1+dfsg1-10) unstable; urgency=medium
 .
   * d/rules: Correctly set BuildAllModules, Closes: #911793
   * d/p/110: fix build with python 3.7.1, Closes:  #914347
   * d/p/111: Correct shebangs and add patch description
Checksums-Sha1:
 7f9dfe332fd7b2cd94c2cb76c708cd1d1a8803de 4063 vtk7_7.1.1+dfsg1-10.dsc
 918744f6c26c46ba9d658ae7426e96f74c008ec5 26040 
vtk7_7.1.1+dfsg1-10.debian.tar.xz
 9598cac74609e5b6f4a78cea3e728c63903cac28 32000 
vtk7_7.1.1+dfsg1-10_source.buildinfo
Checksums-Sha256:
 e9360c110d9993489cb0c8772d8953247d2d8c66351e90d8dfd9c9c80fc9b749 4063 
vtk7_7.1.1+dfsg1-10.dsc
 de676b7038562757cec75aec3f44db006f23651fda77ffbd561068a98197083c 26040 

Bug#911793: marked as done (Don't drop some libvtkRendering* libraries)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 21:05:14 +
with message-id 
and subject line Bug#911793: fixed in vtk7 7.1.1+dfsg1-10
has caused the Debian Bug report #911793,
regarding Don't drop some libvtkRendering* libraries
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.)


-- 
911793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: camitk
Version: 4.1.2-2
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of camitk the autopkgtest of camitk fails in
testing when that autopkgtest is run with the binary packages of camitk
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
camitk from testing4.1.2-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. As the
autopkgtest of the same version in unstable is passing, it may be caused
by a missing *versioned* (test) dependency.

Currently this regression is contributing to the delay of the migration
to testing [1]. Can you please investigate the situation and fix it? If
needed, please change the bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=camitk

https://ci.debian.net/data/autopkgtest/testing/amd64/c/camitk/1201581/log.gz

autopkgtest [04:42:59]: test config-test.sh: [---
== checking camitk configuration ==
= Testing installed version =
= Temporary directory created /tmp/camitk-test-tmp.8KqRtk4hlS =
= Check OS =
= Uname is Linux = OS is Linux =
= Configuring xvfb =
PID of Xvfb: 7451
= Checking camitk-config =
[OK]
= Get CamiTK configuration =
/tmp/autopkgtest-lxc.73ftktc1/downtmp/build.Rkn/src/debian/tests/config-test.sh:
line 148:  7453 Segmentation fault  $camitkConfig --config 2>
/dev/null > ./config-output
unlink: No such file or directory
unlink /tmp/camitk-test-tmp.8KqRtk4hlS//Xvfb_screen0 failed, Invalid
argumentautopkgtest [04:43:00]: test config-test.sh:
---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: vtk7
Source-Version: 7.1.1+dfsg1-10

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

Debian distribution maintenance software
pp.
Gert Wollny  (supplier of updated vtk7 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 23 Nov 2018 21:02:42 +0100
Source: vtk7
Binary: libvtk7-dev libvtk7-qt-dev libvtk7.1 libvtk7.1-qt libvtk7-jni 
libvtk7-java python3-vtk7 tcl-vtk7 vtk7 vtk7-doc vtk7-examples
Architecture: source
Version: 7.1.1+dfsg1-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Gert Wollny 
Description:
 libvtk7-dev - VTK header files
 libvtk7-java - Visualization Toolkit - A high level 3D visualization library - 
j
 libvtk7-jni - Visualization Toolkit - A high level 3D visualization library - j
 libvtk7-qt-dev - VTK header files, containing Qt files
 libvtk7.1  - VTK libraries
 libvtk7.1-qt - VTK libraries, Qt files
 python3-vtk7 - Python bindings for VTK
 tcl-vtk7   - Tcl bindings for VTK
 vtk7   - Binaries for VTK7
 vtk7-doc   - VTK class reference documentation
 vtk7-examples - VTK examples
Closes: 911793 914347
Changes:
 vtk7 (7.1.1+dfsg1-10) unstable; urgency=medium
 .
   * d/rules: Correctly set BuildAllModules, Closes: #911793
   * d/p/110: fix build with python 3.7.1, Closes:  #914347
   * d/p/111: Correct shebangs and add patch description
Checksums-Sha1:
 7f9dfe332fd7b2cd94c2cb76c708cd1d1a8803de 4063 vtk7_7.1.1+dfsg1-10.dsc
 918744f6c26c46ba9d658ae7426e96f74c008ec5 26040 
vtk7_7.1.1+dfsg1-10.debian.tar.xz
 9598cac74609e5b6f4a78cea3e728c63903cac28 32000 

Bug#906057: linphone: Linphone "cannot start transport on port 5060, maybe this port is already used" although it is not.

[W. Martin Borgert]

I use linphone on stretch as my one and only telephone.
So far, I did not encounter this problem.
I suggest to downgrade this issue to "important",
because it seems to affect only few users.

Bug#911793: Bug#914483: Control: reassign -1 src:gdcm 2.8.7-2

[Gert Wollny]

Am Freitag, den 23.11.2018, 20:14 +0100 schrieb Mattia Rizzolo:
> Hi,
> 
> so, if you don't particularly mind, I'm happy to just take the least
> and fix all the involved packages here, so src:vtk7 
I just uploaded vtk7, I knew where to look because I did the changes
that made the libraries go away, and the python thing was not so
difficult after all. 

> and src:gdcm (and rebuilding fw4spl).  At the very least, I'm going
> to rename libvtkgdcm2.8 to something else; thinking about
> libvtkgdcm2.8a (libvtk7gdcm2.8 would be somewhat against policy, as
> it wouldn't match the SONAME anymore, and I don't really like to
> change a library's SONAME without coordingation with upstream).
Thanks, btw: Mathieu (who proposed the libvtk7gdcm) is actually
upstream.

> I'd hope the "both vtk6 and vtk7 were loaded in memory" is not so
> relevant... after all they are different libraries, they shouldn't
> mess with each other that much (there chances of it, but…).
The problem is that vtk6 and vtk7 share many symbols, so linking both
into the same executable is likely to create problems.

[...]

> Gert: you mention you gave up on symbols, but at least in gdcm's
> changelog I don't see anything about that.  Had you had troubles
> there as well?
TBH I never tried with gdcm, I think I started to upload the package
when it was already at version 2.4 and I didn't even note that there is
a script for the symbols there (which points at 2.2). 

When I started packaging some of my software (mia) that has lots of
templates I just noted that getting symbols right there is kind of an
infinite task because each arch would need its own file because of
templates that on 64 bit use some types that are not available, and
were not instanciated on 32 bit systems. Maybe the tools are better
now, but at that time (2012) it was all kind of wired.

> What I would welcome your help with is explaining the camitk FTBFS on
> i386.
Just had as peek, my guess is that this will help: 

ifeq ($(DEB_BUILD_ARCH),i386)
  export DEB_CXXFLAGS_MAINT_APPEND=-ffloat-store
endif

The same was needed for ITK because they write tests with floating
point values apparently comparing with high accuracy, and on i386
optimizations can lead to the used of intermediate 80 bit floating
point values that then result in test failures because the references
were tuned for 64 bit floating point values. Adding above flag makes
sure that intermediate results are not keps in these 80 bit FPU
registers. 

Best,
Gert

Bug#914487: chromium: nonfree unrar code

[Legimet]

Package: chromium
Version: 70.0.3538.67-2
Severity: serious
Justification: Policy 2.1

Chromium contains nonfree code from unrar, located at third_party/unrar.

Bug#910348: marked as done (linux-headers-4.19.0-rc6-amd64: File scripts/subarch.include is missing)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 19:50:49 +
with message-id 
and subject line Bug#910348: fixed in linux 4.18.20-2
has caused the Debian Bug report #910348,
regarding linux-headers-4.19.0-rc6-amd64: File scripts/subarch.include is 
missing
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.)


-- 
910348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-headers-4.19.0-rc6-amd64
Version: 4.19~rc6-1~exp1
Severity: normal

Dear Maintainer,

I try to recompile the virtualbox kernel module. But this did not happen. The
log file told me that:
DKMS make.log for virtualbox-5.2.18 for kernel 4.19.0-rc6-amd64 (x86_64)
Fri  5 Oct 08:05:30 CEST 2018
make: Entering directory '/usr/src/linux-headers-4.19.0-rc6-amd64'
/usr/src/linux-headers-4.19.0-rc6-common/Makefile:302: scripts/subarch.include:
No such file or directory
make[2]: *** No rule to make target 'scripts/subarch.include'.  Stop.
make[2]: *** Waiting for unfinished jobs
make[1]: *** [Makefile:146: sub-make] Error 2
make: *** [Makefile:8: all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.19.0-rc6-amd64'

After install the file scripts/subarch.include it works.

It is new in rc5

Links:
https://fossies.org/diffs/linux/4.19-rc4_vs_4.19-rc5/Makefile-diff.html
https://patchwork.kernel.org/patch/10601895/






-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (710, 'unstable'), (660, 'testing'), (600, 'stable'), (510, 
'experimental'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages linux-headers-4.19.0-rc6-amd64 depends on:
ii  linux-compiler-gcc-8-x86 4.19~rc6-1~exp1
ii  linux-headers-4.19.0-rc6-common  4.19~rc6-1~exp1
ii  linux-kbuild-4.194.19~rc6-1~exp1

linux-headers-4.19.0-rc6-amd64 recommends no packages.

linux-headers-4.19.0-rc6-amd64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.18.20-2

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

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

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 23 Nov 2018 19:15:55 +
Source: linux
Binary: linux-source-4.18 linux-support-4.18.0-3 linux-doc-4.18 linux-cpupower 
libcpupower1 libcpupower-dev usbip hyperv-daemons lockdep liblockdep4.18 
liblockdep-dev linux-kbuild-4.18 linux-perf-4.18 linux-bootwrapper-4.18.0-3 
linux-headers-4.18.0-3-common linux-headers-4.18.0-3-common-rt linux-libc-dev 
linux-headers-4.18.0-3-all linux-headers-4.18.0-3-all-alpha linux-config-4.18 
kernel-image-4.18.0-3-alpha-generic-di nic-modules-4.18.0-3-alpha-generic-di 
nic-wireless-modules-4.18.0-3-alpha-generic-di 
nic-shared-modules-4.18.0-3-alpha-generic-di 
serial-modules-4.18.0-3-alpha-generic-di 
usb-serial-modules-4.18.0-3-alpha-generic-di 
ppp-modules-4.18.0-3-alpha-generic-di pata-modules-4.18.0-3-alpha-generic-di 
cdrom-core-modules-4.18.0-3-alpha-generic-di 
scsi-core-modules-4.18.0-3-alpha-generic-di 
scsi-modules-4.18.0-3-alpha-generic-di loop-modules-4.18.0-3-alpha-generic-di 
btrfs-modules-4.18.0-3-alpha-generic-di ext4-modules-4.18.0-3-alpha-generic-di
 isofs-modules-4.18.0-3-alpha-generic-di jfs-modules-4.18.0-3-alpha-generic-di 
xfs-modules-4.18.0-3-alpha-generic-di fat-modules-4.18.0-3-alpha-generic-di 
md-modules-4.18.0-3-alpha-generic-di 
multipath-modules-4.18.0-3-alpha-generic-di 
usb-modules-4.18.0-3-alpha-generic-di 
usb-storage-modules-4.18.0-3-alpha-generic-di 
input-modules-4.18.0-3-alpha-generic-di event-modules-4.18.0-3-alpha-generic-di 

Bug#914431: marked as done (linux-headers-4.18.0-3-common: missing file referred in Makefile)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 19:50:49 +
with message-id 
and subject line Bug#910348: fixed in linux 4.18.20-2
has caused the Debian Bug report #910348,
regarding linux-headers-4.18.0-3-common: missing file referred in Makefile
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.)


-- 
910348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-headers-4.18.0-3-common
Version: 4.18.20-1
Severity: normal

Dear Maintainer,

a module couldn't be compiled by dkms with this specific kernel (for
information, it was the wireguard module). The compilation failed indicating
that it couldn't find the file "scripts/subarch.include", as referred in line
301 of /usr/src/linux-headers-4.18.0-3-common/Makefile (it is a "include
scripts/subarch.include"). This file is indeed absent from my system.

As a test, I simply tried to comment this include line. It happened that this
was sufficient for compiling the wireguard module. I suppose that the
subarch.include file is missing (or fails to be generated), even if it appears
that is was not necessary in my case.

I report this bug for linux-headers-4.18.0-3-common as it seemed to be the
place where lies the bug (at least for me), but it may actually be a wireguard
bug.

Thank you,
Cordially,
Raphael



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

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.18.20-2

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

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

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 23 Nov 2018 19:15:55 +
Source: linux
Binary: linux-source-4.18 linux-support-4.18.0-3 linux-doc-4.18 linux-cpupower 
libcpupower1 libcpupower-dev usbip hyperv-daemons lockdep liblockdep4.18 
liblockdep-dev linux-kbuild-4.18 linux-perf-4.18 linux-bootwrapper-4.18.0-3 
linux-headers-4.18.0-3-common linux-headers-4.18.0-3-common-rt linux-libc-dev 
linux-headers-4.18.0-3-all linux-headers-4.18.0-3-all-alpha linux-config-4.18 
kernel-image-4.18.0-3-alpha-generic-di nic-modules-4.18.0-3-alpha-generic-di 
nic-wireless-modules-4.18.0-3-alpha-generic-di 
nic-shared-modules-4.18.0-3-alpha-generic-di 
serial-modules-4.18.0-3-alpha-generic-di 
usb-serial-modules-4.18.0-3-alpha-generic-di 
ppp-modules-4.18.0-3-alpha-generic-di pata-modules-4.18.0-3-alpha-generic-di 
cdrom-core-modules-4.18.0-3-alpha-generic-di 
scsi-core-modules-4.18.0-3-alpha-generic-di 
scsi-modules-4.18.0-3-alpha-generic-di loop-modules-4.18.0-3-alpha-generic-di 
btrfs-modules-4.18.0-3-alpha-generic-di ext4-modules-4.18.0-3-alpha-generic-di
 isofs-modules-4.18.0-3-alpha-generic-di jfs-modules-4.18.0-3-alpha-generic-di 
xfs-modules-4.18.0-3-alpha-generic-di fat-modules-4.18.0-3-alpha-generic-di 
md-modules-4.18.0-3-alpha-generic-di 
multipath-modules-4.18.0-3-alpha-generic-di 
usb-modules-4.18.0-3-alpha-generic-di 
usb-storage-modules-4.18.0-3-alpha-generic-di 
input-modules-4.18.0-3-alpha-generic-di event-modules-4.18.0-3-alpha-generic-di 
mouse-modules-4.18.0-3-alpha-generic-di 
nic-pcmcia-modules-4.18.0-3-alpha-generic-di 
pcmcia-modules-4.18.0-3-alpha-generic-di 
nic-usb-modules-4.18.0-3-alpha-generic-di 
sata-modules-4.18.0-3-alpha-generic-di i2c-modules-4.18.0-3-alpha-generic-di 
crc-modules-4.18.0-3-alpha-generic-di crypto-modules-4.18.0-3-alpha-generic-di 
crypto-dm-modules-4.18.0-3-alpha-generic-di 
ata-modules-4.18.0-3-alpha-generic-di nbd-modules-4.18.0-3-alpha-generic-di 

Bug#914420: marked as done (python-pytest: Breaks many Python 2 test suites)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 19:23:50 +
with message-id 
and subject line Bug#914420: fixed in pytest 3.10.1-1
has caused the Debian Bug report #914420,
regarding python-pytest: Breaks many Python 2 test suites
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.)


-- 
914420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pytest
Version: 3.9.3-2
Severity: serious
Affects: python-astropy, python-ccdproc, astropy-healpix, python-drizzle

Dear maintainer,

many astronomy Python packages rely on pytest for build and CI tests.
The Python 2 tests are now broken with the new version of pytest, since
the tests are not found anymore, and the test returns with exit code 5.
Depending on the build time tests, this may also cause FTBFS of some
packages.

Python 3 tests are not affected.

Best

Ole
--- End Message ---
--- Begin Message ---
Source: pytest
Source-Version: 3.10.1-1

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 23 Nov 2018 18:59:56 +0100
Source: pytest
Binary: pypy-pytest python-pytest python-pytest-doc python3-pytest
Architecture: source
Version: 3.10.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Description:
 pypy-pytest - Simple, powerful testing in PyPy
 python-pytest - Simple, powerful testing in Python
 python-pytest-doc - Simple, powerful testing in Python - Documentation
 python3-pytest - Simple, powerful testing in Python3
Closes: 914420
Changes:
 pytest (3.10.1-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #914420)
Checksums-Sha1:
 5678986f5bb03dd6b3542829e5b80a2e8b333bee 3194 pytest_3.10.1-1.dsc
 f5f26c444b347d1dca23f7bd6815f4c79baba1cb 892420 pytest_3.10.1.orig.tar.gz
 55effc231389eeb5f61ff8bb92868bb004213c7d 10600 pytest_3.10.1-1.debian.tar.xz
 576705b56248d9f042c82ad30f2ec1383e5dad06 10701 pytest_3.10.1-1_amd64.buildinfo
Checksums-Sha256:
 616b295af2f87e56f41468a2b73cda08e4c5d5766ee625acb47c7adc645a5df5 3194 
pytest_3.10.1-1.dsc
 e246cf173c01169b9617fc07264b7b1316e78d7a650055235d6d897bc80d9660 892420 
pytest_3.10.1.orig.tar.gz
 7f450bf453d94c61dd9b16e1aead18ac199a9aeccdcd6347c16af649918fab0b 10600 
pytest_3.10.1-1.debian.tar.xz
 af8b01af586c1e2689ff8c865bb0af4d85d573b93f61680b18eb74234b9bf7c1 10701 
pytest_3.10.1-1_amd64.buildinfo
Files:
 ff6c403c0e4a094429f116ae7466b029 3194 python optional pytest_3.10.1-1.dsc
 9afbcf5a86d4fea46024eb65994e7e69 892420 python optional 
pytest_3.10.1.orig.tar.gz
 31c1b3260b0733ca6e839637e6d5c33a 10600 python optional 
pytest_3.10.1-1.debian.tar.xz
 7a15e1ab66de170a80311142a0126885 10701 python optional 
pytest_3.10.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAlv4SiYACgkQNXMSVZ0e
BkvRWhAApvp9Oq0hN57eCufDsWIrRkbX8yiR6YFsK2B4E05ijiUJc4Cl5By/RLRK
RkRjzHXkEvq9ZEjKmRHMxUokfOZXJMv0dEk6Tf4ysrwMe1J7Ubhxe2NeCXdHNCs3
dvZUFqb3V3uHECt24tBbLFOt6rVEqXVF1G44rOsR2yNARRPvaU9mmlFqSIO2/Ewy
Hbz/JZ77JGs9qfIRzD9mf32b5QoFKew2z0EuwKUkJ8d8JziHOCooAVIQxOa2aY6T
dAnh+OEYv6jrDC+AYmvixA6Myg5E+7E5pI+eggs64TA/t1WW5pwuXZ8CrQoyGxPH
trI/X/xBPsk9lhB11rhQi6t+URsumvffnvMj1nxC0VzFZzpHxWMyH09d5xrvp07U
mEf7I5p1pVH0M3r/1TUxcKDgThxqqqOAshLfkXDnP2fyQ7nSHRDK4vwEHxUJU6AW
JGF3p37a4V2bilexfJafpGp/TCutZKq4nKioAvdvhgXfP3Rpcd9iN2rDpATcgORe
qGBVhKKQa5B20EcOoq6QgtvkpjosVb6mmnu5iMTZBzBmzg5OldpgYkoH9HooyLi4
8nHMZZs2XB5VlI9BvazTakhSdMhQccGtl5cDxlDnpBcGoo0+oysX2ZmoHq3J0HkB
3/JlzJ5dWTcedDTiTn1tvmTPH1ArnqR8O8+LJLc9nu4gBqzNs04=
=BSPv
-END PGP SIGNATURE End Message ---

Bug#914483: Control: reassign -1 src:gdcm 2.8.7-2

[Mattia Rizzolo]

Hi,

so, if you don't particularly mind, I'm happy to just take the least and
fix all the involved packages here, so src:vtk7 and src:gdcm (and
rebuilding fw4spl).  At the very least, I'm going to rename
libvtkgdcm2.8 to something else; thinking about libvtkgdcm2.8a
(libvtk7gdcm2.8 would be somewhat against policy, as it wouldn't match
the SONAME anymore, and I don't really like to change a library's SONAME
without coordingation with upstream).


On Fri, Nov 23, 2018 at 04:30:16PM +0100, Emmanuel Promayon wrote:
> So I suppose the problem is in vtk7

nah, that's just an unrelated breakage for which a patch is even already
available..

> 1) gdcm 2.8.7-2 moved to python3 (probably because a move from python2 to
> python3 was required) which I think triggered the choice of moving from vtk6
> to vtk7 (which probably made more sense, as I presume vtk6 is also on its
> way out of buster).

My gut feeling is that the culprit is more the vtk6→vtk7 change rathe
than the py2→py3, but it's not relevant.

> 2) When gdcm 2.8.7-2 arrived in sid, it generated a SegFaults during  camitk
> 4.1.2-1 as camitk 4.1.2-1 was still based on vtk6, and loading any camitk
> executable meant that both vtk6 and vtk7 were loaded in memory.

I'd hope the "both vtk6 and vtk7 were loaded in memory" is not so
relevant... after all they are different libraries, they shouldn't mess
with each other that much (there chances of it, but…).

> 4) gdcm 2.8.7-5 then fixed the double dependency to vtk6 and vtk7 but camitk
> 4.1.2-2 was not rebuilt against it, therefore generating the initial error
> that triggered bug #911793

the camitk that is currently in unstable is built against gdcm 2.8.7-5,
which should have been a fine version.  So does camitk really segfault
with the current libvtkgdcm2.8?

> 5) vtk7 (which was updated in the meantime) seems to have now some missing
> libraries and as hdf5 is broken as well camitk 4.1.2-2 can not be rebuilt
> yet

It needs a rebuild against hdf5, blocked by
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914347 but a patch is
already available, so..

> On a side discussion:
> Does the fact that I moved the dependency of camitk from vtk6 in 4.1.2-1 to
> vtk7 in 4.1.2-2 might generate another ABI break? If this is the case, I
> will take any advice regarding how to specify this properly!

I will check this out.

> I will also welcome any information/documentation about how to track the
> symbol.

TBH, I got kinda tired at writing stuff about how to properly deal with
symbols every now and then, so I'll probably just go ahead and commit
something.


Gert: you mention you gave up on symbols, but at least in gdcm's
changelog I don't see anything about that.  Had you had troubles there
as well?


What I would welcome your help with is explaining the camitk FTBFS on
i386.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#911793: gdcm: ABI break

[Mattia Rizzolo]

Control: clone -1 -2
Control: reassign -2 src:gdcm 2.8.7-2
Control: retitle -2 gdcm: ABI break
Control: found -1 7.1.1+dfsg1-8

On Fri, Nov 23, 2018 at 01:44:26PM +0100, Gert Wollny wrote:
> Control: reassign -1 vtk7 
> Control: retitle -1 Don't drop some libvtkRendering* libraries
> 
> I don't think that this is a problem with gdcm, both camitk-imp and
> camitk-config don't even list any gdcm library with ldd, but they both
> list 
> 
>   libvtkRenderingFreeTypeFontConfig-7.1.so.7.1 => not found
>   libvtkRenderingMatplotlib-7.1.so.7.1 => not found

libcaitk4 generates a dependency on libvtkgdcm2.8, so I guess something
links there anyway.

And there has been an ABI break on gdcm, please don't hide it.

> So my guess it that I botchered vtk7 when I tried to fix the missing
> armhf/armel build and somehow managed to exclude these libraries from
> the package, and since camitk was build against an vtk7 package version
> is has these libraries in the link list. 
> 
> I'll see what I can do to get this fixed, but vtk7 now has also a
> python related bug and these are usually ugly to fix, so it may take
> some time (especially since this is really not my field of work
> anymore).

I can try take care of this if you'd like.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: Re: Bug#911793: gdcm: ABI break

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #911793 [vtk7] Don't drop some libvtkRendering* libraries
Bug 911793 cloned as bug 914483
909120 was blocked by: 914482 911793
909120 was not blocking any bugs.
Added blocking bug(s) of 909120: 914483
> reassign -2 src:gdcm 2.8.7-2
Bug #914483 [vtk7] Don't drop some libvtkRendering* libraries
Bug reassigned from package 'vtk7' to 'src:gdcm'.
No longer marked as found in versions vtk7/7.1.1+dfsg1-8.
Ignoring request to alter fixed versions of bug #914483 to the same values 
previously set
Bug #914483 [src:gdcm] Don't drop some libvtkRendering* libraries
Marked as found in versions gdcm/2.8.7-2.
> retitle -2 gdcm: ABI break
Bug #914483 [src:gdcm] Don't drop some libvtkRendering* libraries
Changed Bug title to 'gdcm: ABI break' from 'Don't drop some libvtkRendering* 
libraries'.
> found -1 7.1.1+dfsg1-8
Bug #911793 [vtk7] Don't drop some libvtkRendering* libraries
Ignoring request to alter found versions of bug #911793 to the same values 
previously set

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

Processed: Re: Bug#911793: gdcm: ABI break

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #911793 [vtk7] Don't drop some libvtkRendering* libraries
Bug 911793 cloned as bug 914482
909120 was blocked by: 911793
909120 was not blocking any bugs.
Added blocking bug(s) of 909120: 914482
> reassign -2 src:gdcm 2.8.7-2
Bug #914482 [vtk7] Don't drop some libvtkRendering* libraries
Bug reassigned from package 'vtk7' to 'src:gdcm'.
Ignoring request to alter found versions of bug #914482 to the same values 
previously set
Ignoring request to alter fixed versions of bug #914482 to the same values 
previously set
Bug #914482 [src:gdcm] Don't drop some libvtkRendering* libraries
Marked as found in versions gdcm/2.8.7-2.
> retitle -2 gdcm: ABI break
Bug #914482 [src:gdcm] Don't drop some libvtkRendering* libraries
Changed Bug title to 'gdcm: ABI break' from 'Don't drop some libvtkRendering* 
libraries'.
> found -1 7.1.1+dfsg1-8
Bug #911793 [vtk7] Don't drop some libvtkRendering* libraries
Marked as found in versions vtk7/7.1.1+dfsg1-8.

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

Bug#914420: Bug #914420 in pytest marked as pending

[Ondřej Nový]

Control: tag -1 pending

Hello,

Bug #914420 in pytest reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/pytest/commit/8b96653f3411e55336b274763a74fdf3058d40ec


New upstream release (Closes: #914420)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/914420

Processed: Bug #914420 in pytest marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #914420 [python-pytest] python-pytest: Breaks many Python 2 test suites
Added tag(s) pending.

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

Bug#914378: marked as done (with Python 3.7: RuntimeError: generator raised StopIteration)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 18:21:19 +
with message-id 
and subject line Bug#914378: fixed in python-pygraphviz 1.5-1
has caused the Debian Bug report #914378,
regarding with Python 3.7: RuntimeError: generator raised StopIteration
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.)


-- 
914378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pygraphviz
Version: 1.4~rc1-1+b2
Severity: grave
Tags: patch
Justification: renders package unusable

Hi,

steps to reproduce:

$ python3 --version
Python 3.7.1
$ python3 -c 'import pygraphviz; A=pygraphviz.AGraph(); A.graph_attr.keys()'
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1743, in 
iteritems
ah = gv.agnxtattr(self.handle, self.type, ah)
StopIteration: agnxtattr

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

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1733, in keys
return list(self.__iter__())
  File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1736, in 
__iter__
for (k, v) in self.iteritems():
RuntimeError: generator raised StopIteration

This problem does not happen with snapshot 20181121T102052Z but does
happen with snapshot 20181121T232318Z. There is only one change between
chroots made from these two snapshots, the following packages have been
upgraded from version 3.6.7-1 to 3.7.1-1:

libpython3-stdlib, libpython3.6-minimal, libpython3.6-stdlib, python3,
python3-minimal, python3.6, python3.6-minimal

Thus I conclude that this problem was introduced because of the upgrade
of Python from 3.6 to 3.7.

Upstream has a fix here:

https://github.com/pygraphviz/pygraphviz/commit/b5df022700669ae496f65d20dd9cd387d6af948e

I backported that commit on top of the version of python-pygraphviz from
Debian unstable. Please find the patch attached.

I see that this package did not see an upload since January 2017. If you
are okay with me NMU-ing the package for this fix, then please tell me.

Alternatively, this bug can also be fixed by packaging the latest
upstream version 1.5 of pygraphviz which includes the above commit.

Thanks!

cheers, josch
diff -Nru python-pygraphviz-1.4~rc1/debian/changelog 
python-pygraphviz-1.4~rc1/debian/changelog
--- python-pygraphviz-1.4~rc1/debian/changelog  2017-01-08 21:03:20.0 
+0100
+++ python-pygraphviz-1.4~rc1/debian/changelog  2018-11-22 19:31:03.0 
+0100
@@ -1,3 +1,10 @@
+python-pygraphviz (1.4~rc1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix StopIteration with Python 3.7
+
+ -- Johannes 'josch' Schauer   Thu, 22 Nov 2018 19:31:03 
+0100
+
 python-pygraphviz (1.4~rc1-1) unstable; urgency=medium
 
   * New upstream release candidate
diff -Nru 
python-pygraphviz-1.4~rc1/debian/patches/catch_stopiterations_created_by_c_code 
python-pygraphviz-1.4~rc1/debian/patches/catch_stopiterations_created_by_c_code
--- 
python-pygraphviz-1.4~rc1/debian/patches/catch_stopiterations_created_by_c_code 
1970-01-01 01:00:00.0 +0100
+++ 
python-pygraphviz-1.4~rc1/debian/patches/catch_stopiterations_created_by_c_code 
2018-11-22 19:30:55.0 +0100
@@ -0,0 +1,174 @@
+From b5df022700669ae496f65d20dd9cd387d6af948e Mon Sep 17 00:00:00 2001
+From: Dan Schult 
+Date: Thu, 2 Aug 2018 21:32:47 -0400
+Subject: [PATCH] catch StopIterations created by C code
+
+--- a/pygraphviz/agraph.py
 b/pygraphviz/agraph.py
+@@ -374,8 +374,10 @@ class AGraph(object):
+ nh = gv.agfstnode(self.handle)
+ while nh is not None:
+ yield Node(self, nh=nh)
+-nh = gv.agnxtnode(self.handle, nh)
+-raise StopIteration
++try:
++nh = gv.agnxtnode(self.handle, nh)
++except StopIteration:
++return
+ 
+ iternodes = nodes_iter
+ 
+@@ -597,8 +599,10 @@ class AGraph(object):
+ yield Node(self, t)
+ else:
+ yield Node(self, s)
+-eh = gv.agnxtedge(self.handle, eh, nh)
+-raise StopIteration
++try:
++eh = gv.agnxtedge(self.handle, eh, nh)
++except StopIteration:
++return
+ 
+ def neighbors(self, n):
+ """Return a list of the nodes attached to n."""
+@@ -627,8 +631,14 @@ class AGraph(object):
+ yield (e[0], e[1], e.name)
+ else:
+ yield e
+-   

Bug#914378: Bug #914378 in python-pygraphviz marked as pending

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #914378 in python-pygraphviz reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/python-pygraphviz/commit/f56783a35994207b2619d103f1c576c659749508


New upstream release; Closes: #914378



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/914378

Processed: Bug #914378 in python-pygraphviz marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #914378 [src:python-pygraphviz] with Python 3.7: RuntimeError: generator 
raised StopIteration
Added tag(s) pending.

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

Bug#914457: marked as done (icingacli: any command issued to icingacli rise an exception)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 18:05:44 +
with message-id 
and subject line Bug#914457: fixed in icingaweb2 2.6.2-2
has caused the Debian Bug report #914457,
regarding icingacli: any command issued to icingacli rise an exception
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.)


-- 
914457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: icingacli
Version: 2.6.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

an example: 

icingacli --help

Fatal error: Uncaught ErrorException: "continue" targeting switch is equivalent 
to "break". Did you mean to use "continue 2"? in 
/usr/share/php/Icinga/File/Ini/IniParser.php:67
Stack trace:
#0 /usr/share/php/Icinga/Application/ClassLoader.php(303): 
Icinga\Application\ApplicationBootstrap->Icinga\Application\{closure}(2, 
'"continue" targ...', '/usr/share/php/...', 67, Array)
#1 /usr/share/php/Icinga/Application/ClassLoader.php(303): require()
#2 [internal function]: 
Icinga\Application\ClassLoader->loadClass('Icinga\\File\\Ini...')
#3 /usr/share/php/Icinga/Application/Config.php(326): 
spl_autoload_call('Icinga\\File\\Ini...')
#4 /usr/share/php/Icinga/Application/Config.php(397): 
Icinga\Application\Config::fromIni('/etc/icingaweb2...')
#5 /usr/share/php/Icinga/Application/ApplicationBootstrap.php(522): 
Icinga\Application\Config::app()
#6 /usr/share/php/Icinga/Application/Cli.php(39): 
Icinga\Application\ApplicationBootstrap->loadConfig()
#7 /usr/share/php/Icinga/Application/ApplicationBootstrap.php(369): 
Icinga\Application\Cl in /usr/share/php/Icinga/File/Ini/IniParser.php on line 67


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

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

Versions of packages icingacli depends on:
ii  adduser 3.118
ii  php-icinga  2.6.1-1

Versions of packages icingacli recommends:
ii  php7.2-cli [php-cli]  7.2.9-1
ii  php7.3-cli [php-cli]  7.3.0~rc4-1

Versions of packages icingacli suggests:
ii  icingaweb2-module-monitoring  2.6.1-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: icingaweb2
Source-Version: 2.6.2-2

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated icingaweb2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 23 Nov 2018 18:36:14 +0100
Source: icingaweb2
Binary: icingaweb2 icingaweb2-common icingaweb2-module-monitoring 
icingaweb2-module-doc php-icinga icingacli
Architecture: source all
Version: 2.6.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Nagios Maintainer Group 

Changed-By: Bas Couwenberg 
Description:
 icingacli  - simple CLI tool for Icingaweb2 and its modules
 icingaweb2 - simple and responsive web interface for Icinga
 icingaweb2-common - simple and responsive web interface for Icinga - common 
files
 icingaweb2-module-doc - simple and responsive web interface for Icinga - 
documentation mo
 icingaweb2-module-monitoring - simple and responsive web interface for Icinga 
- monitoring modul
 php-icinga - PHP library to communicate with and use Icinga
Closes: 914457
Changes:
 icingaweb2 (2.6.2-2) unstable; urgency=medium
 .
   * Team upload.
   * Add patch to fix Uncaught ErrorException with PHP 7.3.
 (closes: #914457)
Checksums-Sha1:
 e993afa2a9bab200a79b8c8c14a49a6bc29f724e 2357 icingaweb2_2.6.2-2.dsc
 0b26e1f33b71af0f4cefa639cd82c027684565a1 12628 icingaweb2_2.6.2-2.debian.tar.xz
 76f2d041095f3f867c19b5269fcfbd85d7c639d9 29284 icingacli_2.6.2-2_all.deb
 70c18d59edacf9db129be1d6b47955ac7ea1bc75 363796 
icingaweb2-common_2.6.2-2_all.deb
 eb670e3e5247e2cfdd5f5580a9c7d3da246eef23 44892 

Bug#914356: marked as done (dlt-daemon: FTBFS (ld: cannot find -lpthreads))

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 17:50:34 +
with message-id 
and subject line Bug#914356: fixed in dlt-daemon 2.17.0-2
has caused the Debian Bug report #914356,
regarding dlt-daemon: FTBFS (ld: cannot find -lpthreads)
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.)


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

Dear maintainer:

I tried to build this package but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure --  -DWITH_SYSTEMD=ON -DWITH_SYSTEMD_JOURNAL=ON 
-DCMAKE_LIBRARY_PATH=x86_64-linux-gnu
install -d obj-x86_64-linux-gnu
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DWITH_SYSTEMD=ON -DWITH_SYSTEMD_JOURNAL=ON 
-DCMAKE_LIBRARY_PATH=x86_64-linux-gnu ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info

[... snipped ...]

#endif
}

Determining if the function pthread_create exists in the pthreads failed with 
the following output:
Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_2df6a/fast"
make[2]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_2df6a.dir/build.make 
CMakeFiles/cmTC_2df6a.dir/build
make[3]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_2df6a.dir/CheckFunctionExists.c.o
/usr/bin/cc   -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create   -o 
CMakeFiles/cmTC_2df6a.dir/CheckFunctionExists.c.o   -c 
/usr/share/cmake-3.12/Modules/CheckFunctionExists.c
Linking C executable cmTC_2df6a
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_2df6a.dir/link.txt 
--verbose=1
/usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create  -Wl,-z,relro  
-rdynamic CMakeFiles/cmTC_2df6a.dir/CheckFunctionExists.c.o  -o cmTC_2df6a 
-lpthreads 
/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status
make[3]: *** [CMakeFiles/cmTC_2df6a.dir/build.make:87: cmTC_2df6a] Error 1
make[3]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: *** [Makefile:121: cmTC_2df6a/fast] Error 2
make[2]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'


Determining if the function floor exists failed with the following output:
Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_3de1c/fast"
make[2]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_3de1c.dir/build.make 
CMakeFiles/cmTC_3de1c.dir/build
make[3]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_3de1c.dir/CheckFunctionExists.c.o
/usr/bin/cc  -I/<>/systemd/3rdparty  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu99 
-DCHECK_FUNCTION_EXISTS=floor   -o 
CMakeFiles/cmTC_3de1c.dir/CheckFunctionExists.c.o   -c 
/usr/share/cmake-3.12/Modules/CheckFunctionExists.c
: warning: conflicting types for built-in function 'floor' 
[-Wbuiltin-declaration-mismatch]
/usr/share/cmake-3.12/Modules/CheckFunctionExists.c:7:3: note: in expansion of 
macro 'CHECK_FUNCTION_EXISTS'
   CHECK_FUNCTION_EXISTS(void);
   ^
Linking C executable cmTC_3de1c
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_3de1c.dir/link.txt 
--verbose=1
/usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=gnu99 -DCHECK_FUNCTION_EXISTS=floor  -Wl,-z,relro  
-rdynamic 

Bug#911793: Control: reassign -1 src:gdcm 2.8.7-2

[Gert Wollny]

Hello, 

Am Freitag, den 23.11.2018, 16:30 +0100 schrieb Emmanuel Promayon:
> Dear all
> 
> Thank to Paul for your answers about the autoremoval and explanation 
> about the ABI problem. It seems that Adrian Bunk's triage message in 
> 909120 (added blocking bug(s) of 909120: 911793) did push the 
> autoremoval for another month (thanks to Adrian as well, as that's 
> exactly what is happening).
> 
> Thank you to Mattia for finding the ABI problem and to Matthieu for
> his comments.
> 
> Thank you to Gert for the explanation about vtk7 (by the way do you
> have any idea about the possible future introduction of vtk8 or
> vtk9?).
The problem is that I moved to a different work which is rather
unrelated to using VTK, so my personal interest there is quite limited.
There was also some discussion of actually using paraview as a vehicle
to also bring in the VTK libraries, because paraview has them bundled
and it seems to be difficult to unbundle them.   


> You are right about camitk-imp and camitk-config: they are not
> linked 
> with gdcm. When camitk-imp or camitk-config are run they load some 
> plugins (e.g. the dicom plugin) that itself is linked with gdcm.
> Running ldd on one of the pluging get the similar missing vtk
> symbols and so. So I suppose the problem is in vtk7
I found the problem with the missing libraries, it was indeed something
I messed up when I removed the QT dependency on armhf/armel. 

> 
>  From what I can understand (sorry in advance for any approximation
> or  stating the obvious):
> 1) gdcm 2.8.7-2 moved to python3 (probably because a move from
> python2 to python3 was required) which I think triggered the choice
> of moving from vtk6 to vtk7 (which probably made more sense, as I
> presume vtk6 is  also on its way out of buster).
AFAIK vtk6 doesn't support python3 at all, and the general idea is to
at least minimize the use of vtk6, only provide the libraries, but let
vtk7+ provide the language bindings.  

It will not be possible to remove it completely because of the switch
to OpenGL 3.2 in vtk7 which breaks a number of reverse dependecies
(ginkgocadx and maybe also itksnap).

> 2) When gdcm 2.8.7-2 arrived in sid, it generated a SegFaults
> during camitk 4.1.2-1 as camitk 4.1.2-1 was still based on vtk6, and
> loading  any camitk executable meant that both vtk6 and vtk7 were
> loaded in memory.
This is where I messed up a bit, because I didn't expect that vtkgdcm
would export symbols from vtk, and I didn't check the reverse
dependencies because I was only focused on python3 (and there
inveselius), but this is independend from camitk pulling in two
versions of vtkm, even if vtkgdcm would not export VTK symbols then
this would still have been a problem.

> 3) camitk 4.1.2-2 introduced a patch so that it only depends on vtk7 
> (and like gdcm 2.8.7 without changing the upstream source version).
> 4) gdcm 2.8.7-5 then fixed the double dependency to vtk6 and vtk7
> but camitk 4.1.2-2 was not rebuilt against it, therefore generating
> the initial error that triggered bug #911793
> 5) vtk7 (which was updated in the meantime) seems to have now some 
> missing libraries and as hdf5 is broken as well camitk 4.1.2-2 can
> not be rebuilt yet
I'm noit so sure about the inbetween parts, but the last step is
correct. I just have to check the pytjon problem, and then I should be
able to upload a new vtk7 version. 

> 
> Let me know if there is anything I can do to help.
> 
> On a side discussion:
> Does the fact that I moved the dependency of camitk from vtk6 in
> 4.1.2-1  to vtk7 in 4.1.2-2 might generate another ABI break? 
AFAICS camitk is a leaf package, so there shouldn't be any ABI break
possible.

> If this is the  case, I will take any advice regarding how to specify
> this properly! I will also welcome any information/documentation
> about how to track the symbol.
I tried to tdo this once, but with C++ libraries and templates it was
not quite streightforward, so I gave up on it. 

Best, 
Gert 

Bug#914457: [Pkg-nagios-devel] Bug#914457: icingacli: any command issued to icingacli rise an exception

[Sebastiaan Couwenberg]

Control: tags -1 upstream pending

This issue is caused by PHP 7.3, see:

 https://bugs.php.net/bug.php?id=76753

I've added a patch to fix the issues in the icingaweb2 code, and a new
upload to unstable will follow shortly.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: Re: [Pkg-nagios-devel] Bug#914457: icingacli: any command issued to icingacli rise an exception

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream pending
Bug #914457 [icingacli] icingacli: any command issued to icingacli rise an 
exception
Added tag(s) upstream and pending.

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

Bug#913645: Oldstable also affected

[Carsten Schoenert]

Hello Bastian,

Am 20.11.18 um 17:44 schrieb Bastian Neuburger:
> Hi,
> 
>> I have however not yet tested what happens if you start thunderbird 
>> aftter the upgrade and close it right away (i.e. not trying to sign 
>> anything but also not entering the master password). I will try to test 
>> this later but now I need a working mail client.
>>
> 
> I also tested this variant now:
> 
> 1. Have berkeley DB based profile that works fine with thunderbird 52 in 
> Jessie
> 2. Upgrade thunderbird
> 3. Start thunderbird
> 4. Close it without doing anything (I am not prompted for the master 
> password)
> 5. Start thunderbird again
> 
> Expected results:
> Either key3.db is still there or I am getting prompted for a master 
> password during step 4.
> 
> Actual results:
> Everything under "Your certificates" and "People" in the Certificate 
> Manager gone, all saved passwords gone.
> 
> So the problem we encountered did not only wipe private keys, but also 
> certificates of other people I already corresponded with AND stored 
> passwords.

thanks for testing this, I'm unable to this as I don't use any of these
features.

> How should reporting with upstream be handled? Should I take care of it 
> myself or would you like to forward it?

I'd prefer if you could do the interaction with upstream as I only would
act as a man in the middle. And I haven't much time to work on
Thunderbird now.
Please give a note back about the upstream bug number so we can add a
forwarding to this issue. Thanks!

-- 
Regards
Carsten Schoenert

Bug#913163: (Security) bugs in pdns in stretch

[Chris Hofstaedtler]

* Moritz Mühlenhoff  [181123 14:09]:
> On Sat, Nov 10, 2018 at 04:34:48PM +0100, Chris Hofstaedtler wrote:
> > Hi everyone,
> > 
> > thanks for reporting bugs against pdns in stretch.
> > I intend to upload a new version to stretch to fix those bugs, but I
> > cannot test all involved components personally. Please give this
> > version a shot:
> 
> @Chris: Was there any test feedback so far?

Xan Charbonnet has tested it and gave a positive response (mostly
for #889798 I'd imagine).

Some more feedback wouldn't hurt.

Cheers,
Chris

Bug#913810: marked as done (bzr binary-all FTBFS: ERROR: bzrlib.tests.blackbox.test_too_much.SFTPTestsAbsolute.test_push)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 17:19:35 +
with message-id 
and subject line Bug#913810: fixed in bzr 2.7.0+bzr6622-15
has caused the Debian Bug report #913810,
regarding bzr binary-all FTBFS: ERROR: 
bzrlib.tests.blackbox.test_too_much.SFTPTestsAbsolute.test_push
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.)


-- 
913810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bzr
Version: 2.7.0+bzr6622-14
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=bzr=all=2.7.0%2Bbzr6622-14=1542144694=0

...
==
ERROR: bzrlib.tests.blackbox.test_too_much.SFTPTestsAbsolute.test_push
--
Traceback (most recent call last):
testtools.testresult.real._StringException: lost connection during test 
'bzrlib.tests.blackbox.test_too_much.SFTPTestsAbsolute.test_push'
--
Ran 21773 tests in 636.774s

FAILED (errors=1, known_failure_count=60)
2104 tests skipped
make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: bzr
Source-Version: 2.7.0+bzr6622-15

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated bzr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 23 Nov 2018 16:41:56 +
Source: bzr
Binary: bzr python-bzrlib python-bzrlib-dbg python-bzrlib.tests bzr-doc
Architecture: source
Version: 2.7.0+bzr6622-15
Distribution: unstable
Urgency: medium
Maintainer: Debian Bazaar Maintainers 
Changed-By: Jelmer Vernooij 
Description:
 bzr- easy to use distributed version control system
 bzr-doc- easy to use distributed version control system (documentation)
 python-bzrlib - distributed version control system - python library
 python-bzrlib-dbg - distributed version control system - debug extension
 python-bzrlib.tests - distributed version control system - testsuite
Closes: 913810
Changes:
 bzr (2.7.0+bzr6622-15) unstable; urgency=medium
 .
   * Use secure URI in Homepage field.
   * Add 30_test_too_much: Disable flaky test_too_much tests. Closes:
 #913810
Checksums-Sha1:
 7bb780c804da3e35a90729768734f6921a902109 2923 bzr_2.7.0+bzr6622-15.dsc
 1684592ffbbfbd701f3dcdbaed983257bbc76769 92936 
bzr_2.7.0+bzr6622-15.debian.tar.xz
 252556fcb576cb4943ba9a656d1ae34addcfd18d 9958 
bzr_2.7.0+bzr6622-15_amd64.buildinfo
Checksums-Sha256:
 ce3ad2a536c52343f06d7393a7f76ef3855bc91daa596e9e8e895bf289d2e43d 2923 
bzr_2.7.0+bzr6622-15.dsc
 d2198b93059cc9d37c551f7bfda19a199c18f4c9c6104a8c40ccd6d0c65e6fd3 92936 
bzr_2.7.0+bzr6622-15.debian.tar.xz
 2c705a9d9d4dc2d9eb51652262d79cd3ad10dba3be2c77e2f3007f97f2af0db2 9958 
bzr_2.7.0+bzr6622-15_amd64.buildinfo
Files:
 36703c6373f43e8f80e6007bac648f28 2923 vcs optional bzr_2.7.0+bzr6622-15.dsc
 c6350455296927712e017107d5ec0033 92936 vcs optional 
bzr_2.7.0+bzr6622-15.debian.tar.xz
 ab159b1e97a4acee62dd5fe28402b905 9958 vcs optional 
bzr_2.7.0+bzr6622-15_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAlv4MF4SHGplbG1lckBk
ZWJpYW4ub3JnAAoJEFecFg1MniPo1woP/RhorQd7jMzcWSbhiN9+xzGmEEO2BIQu
Q3LMtZI1d4g/BVUV4FbRmPDBcX+7FeROMVko/vOkEHhxeAf5o0e3NfAleoymn3yf
brBYzZfBeV9RzNpgdv5kJR4KXOIoBRGCj1a1z1T11Gps4GLewGAhGMv2vU5sE/r2
IjhjG0FC9HHKnakEpssCrJRjyVSHqz7RBfcU59N0qcdo3gSfl5765kIz9I1+UG+8
OKM3bbwKvmz8CAv58vT7Vqqu9s0VJthxyiqX0+zHBryYRUX8QjxA/e6zxXkDVJx8
nddPQuRDT1RO7k9DD8a1KmCDhhg/d4Y622zk1gjbFCNmX6ASNhrW4JAdjrC80caf
1D00X58KLXPmbCPpZ+CkkgSKzGEhdNNdGCne7LaPwQ0/7eIVOrTLDxf8DzfaOY7u
BYfSElGSBydW3FwFw/Cgx0Jt7FHI+Tq3VdZ8KY4hyCTW+mebG/LIvzs0CBsNmEey
5H5lOZYqHqTzzVY9P/k/n4T8JhFIC9XvoowiqTujN1AK99LCYbLv8B8Q+x343xrk
ql5rIpLxaf3afsj6hoLJBpssqBC7keE7Qg6AlBAmHyBoYECWHLbc34Y4oPvB/YkO
pyslLmwBYPXm15kBn6i6uJoQMZtUoUMd8W+LqJWXI2ybddKUyF7OMQs3NWepEY3e

Processed: Re: mmdebstrap: cannot install apt under fakechroot or proot

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #909637 [mmdebstrap] mmdebstrap: cannot install apt under fakechroot or 
proot
Severity set to 'important' from 'grave'

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

Bug#909637: mmdebstrap: cannot install apt under fakechroot or proot

[Johannes Schauer]

Control: severity -1 important

On Wed, 26 Sep 2018 06:36:44 +0200 Johannes 'josch' Schauer  
wrote:
> Apt uses 'mv' in its post inst. 'mv' from coreutils uses the renameat2
> systemcall. The renameat2 systemcall is not supported by fakechroot or
> proot.

downgrade severity to non-RC level because since 0.3.0-1, mmdebstrap warns the
user if they try to run it on a system where fakechroot and/or proot are unable
to use mv(1).


signature.asc
Description: signature

Bug#914386: marked as done (fritzing FTBFS: arch-only build)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 17:48:15 +0100
with message-id <20181123164815.GA13740@localhost>
and subject line bug fixed
has caused the Debian Bug report #914386,
regarding fritzing FTBFS: arch-only build
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.)


-- 
914386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fritzing
Version: 0.9.3b+dfsg-6
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap

While trying to cross build fritzing, I noticed that it fails to build
from source natively. An arch-only build fails:

| find /<>/fritzing-0.9.3b+dfsg/debian/fritzing-data/ -type d -empty 
-delete
| find: '/<>/fritzing-0.9.3b+dfsg/debian/fritzing-data/': No such 
file or directory
| make[1]: *** [debian/rules:28: override_dh_install] Error 1
| make[1]: Leaving directory '/<>/fritzing-0.9.3b+dfsg'
| make: *** [debian/rules:12: binary-arch] Error 2

This happens on the official buildds as well:

https://buildd.debian.org/status/fetch.php?pkg=fritzing=arm64=0.9.3b%2Bdfsg-6=1542881203=0
https://buildd.debian.org/status/fetch.php?pkg=fritzing=armel=0.9.3b%2Bdfsg-6=1542884524=0
https://buildd.debian.org/status/fetch.php?pkg=fritzing=armhf=0.9.3b%2Bdfsg-6=1542882060=0

Looks like you need to conditionalize that command to arch:all builds.

Helmut
--- End Message ---
--- Begin Message ---
The new release fritzing/0.9.3b+dfsg-7 has been built on various
architectures successfully.

-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: PGP signature
--- End Message ---

Bug#914462: node-rollup-plugin-alias: Fails to build, unsatsifiable Build-Depends

[Jeremy Bicha]

Source: node-rollup-plugin-alias
Version: 1.3.1-2
Severity: serious
Tags: ftbfs
X-Debbugs-CC: prav...@debian.org

node-rollup-plugin-alias can't build from source because it
Build-Depends on node-babel-preset-es2015-loose-rollup which is not in
Debian.

Thanks,
Jeremy Bicha

Bug#914457: icingacli: any command issued to icingacli rise an exception

[Max]

Package: icingacli
Version: 2.6.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

an example: 

icingacli --help

Fatal error: Uncaught ErrorException: "continue" targeting switch is equivalent 
to "break". Did you mean to use "continue 2"? in 
/usr/share/php/Icinga/File/Ini/IniParser.php:67
Stack trace:
#0 /usr/share/php/Icinga/Application/ClassLoader.php(303): 
Icinga\Application\ApplicationBootstrap->Icinga\Application\{closure}(2, 
'"continue" targ...', '/usr/share/php/...', 67, Array)
#1 /usr/share/php/Icinga/Application/ClassLoader.php(303): require()
#2 [internal function]: 
Icinga\Application\ClassLoader->loadClass('Icinga\\File\\Ini...')
#3 /usr/share/php/Icinga/Application/Config.php(326): 
spl_autoload_call('Icinga\\File\\Ini...')
#4 /usr/share/php/Icinga/Application/Config.php(397): 
Icinga\Application\Config::fromIni('/etc/icingaweb2...')
#5 /usr/share/php/Icinga/Application/ApplicationBootstrap.php(522): 
Icinga\Application\Config::app()
#6 /usr/share/php/Icinga/Application/Cli.php(39): 
Icinga\Application\ApplicationBootstrap->loadConfig()
#7 /usr/share/php/Icinga/Application/ApplicationBootstrap.php(369): 
Icinga\Application\Cl in /usr/share/php/Icinga/File/Ini/IniParser.php on line 67


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

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

Versions of packages icingacli depends on:
ii  adduser 3.118
ii  php-icinga  2.6.1-1

Versions of packages icingacli recommends:
ii  php7.2-cli [php-cli]  7.2.9-1
ii  php7.3-cli [php-cli]  7.3.0~rc4-1

Versions of packages icingacli suggests:
ii  icingaweb2-module-monitoring  2.6.1-1

-- no debconf information

Bug#914245: marked as done (h5py: FTBFS against hdf5 1.10.4 now in unstable)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 15:34:17 +
with message-id 
and subject line Bug#914245: fixed in h5py 2.8.0-2
has caused the Debian Bug report #914245,
regarding h5py: FTBFS against hdf5 1.10.4 now 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.)


-- 
914245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: h5py
Version: 2.8.0-1
Severity: serious
Tags: patch
Justification: FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

h5py FTBFS against hdf5 1.10.4 now transitioning into unstable:
==
ERROR: test_force_swmr_mode_on_raises 
(h5py.tests.hl.test_dataset_swmr.TestDatasetSwmrRead)
Verify when reading a file cannot be forcibly switched to swmr mode.
- --
Traceback (most recent call last):
  File "h5py/tests/hl/test_dataset_swmr.py", line 75, in 
test_force_swmr_mode_on_raises
self.f.swmr_mode = True
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
  File "h5py/_hl/files.py", line 268, in swmr_mode
self.id.start_swmr_write()
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
  File "h5py/h5f.pyx", line 510, in h5py.h5f.FileID.start_swmr_write
TypeError: Unable to convert file format (no write intent on file)

==
ERROR: test_exc (h5py.tests.old.test_group.TestLen)
len() on closed group gives ValueError
- --
Traceback (most recent call last):
  File "h5py/tests/old/test_group.py", line 302, in test_exc
len(self.f)
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
  File "h5py/_hl/group.py", line 318, in __len__
return self.id.get_num_objs()
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
  File "h5py/h5g.pyx", line 331, in h5py.h5g.GroupID.get_num_objs
TypeError: Not a location id (invalid object ID)

This is due to some changes introduced in hdf5 1.10.3. Please find attached
a patch backported from upstream repository.

Thanks,

_g.

- -- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAlv0eYsACgkQ7+hsbH/+
z4M1CQf/eNEpNVS++J7s9+9ydFCjv2PDDc7JOooChlJYhIfMFKe/aN6yUEWb6+qc
7bbk5Xx6oR+KU2OptDa9liUzSkvczzPB0KhGVpBOUSYKea3+g2ydCMf6m8KRJSPl
kecdlpOS+sOzzt9dxYqhzXIYk8qBduSu8eAjMx1iMYwr4HWELTm4zQ2YQXf1CGI3
bWzVI8K6iqOIQgfjpi+Jari3SWKtQ4vEHBAU50epHJsfnOibF4Fdlc5eqk76m6x7
43+LUAYJ4UAvbtXySh2g7lf/qEEcG4g3U+q0ARyJB6RwO1jXhRokoDPVYmVuiZox
7Oi9wDkmHDzhqmhg+QabZRXQZbrI4A==
=JQqV
-END PGP SIGNATURE-
diff -Nru h5py-2.8.0/debian/changelog h5py-2.8.0/debian/changelog
--- h5py-2.8.0/debian/changelog 2018-08-04 18:54:06.0 +0200
+++ h5py-2.8.0/debian/changelog 2018-10-14 22:52:25.0 +0200
@@ -1,3 +1,10 @@
+h5py (2.8.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * New patch hdf5-1.10.3-support.patch: fix FTBFS against HDF5 1.10.3
+
+ -- Gilles Filippini   Sun, 14 Oct 2018 22:52:25 +0200
+
 h5py (2.8.0-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru h5py-2.8.0/debian/patches/hdf5-1.10.3-support.patch 
h5py-2.8.0/debian/patches/hdf5-1.10.3-support.patch
--- h5py-2.8.0/debian/patches/hdf5-1.10.3-support.patch 1970-01-01 
01:00:00.0 +0100
+++ h5py-2.8.0/debian/patches/hdf5-1.10.3-support.patch 2018-10-14 
22:52:25.0 +0200
@@ -0,0 +1,32 @@
+Description: backport upstream patch to fix FTBFS against HDF5 1.10.3
+
+From 6653c65e8c8d024bbcf50315a1c5201487632322 Mon Sep 17 00:00:00 2001
+From: Thomas A Caswell 
+Date: Thu, 11 Oct 2018 23:39:29 -0400
+Subject: [PATCH] FIX: adjust mapping of hdf5 error codes -> python error codes
+
+This is to account for changes to hdf5 between 1.10.2 and 1.10.3.
+
+Closes #1088
+---
+ h5py/_errors.pyx | 7 

Bug#911793: Control: reassign -1 src:gdcm 2.8.7-2

[Emmanuel Promayon]

Dear all

Thank to Paul for your answers about the autoremoval and explanation 
about the ABI problem. It seems that Adrian Bunk's triage message in 
909120 (added blocking bug(s) of 909120: 911793) did push the 
autoremoval for another month (thanks to Adrian as well, as that's 
exactly what is happening).


Thank you to Mattia for finding the ABI problem and to Matthieu for his 
comments.


Thank you to Gert for the explanation about vtk7 (by the way do you have 
any idea about the possible future introduction of vtk8 or vtk9?).
You are right about camitk-imp and camitk-config: they are not linked 
with gdcm. When camitk-imp or camitk-config are run they load some 
plugins (e.g. the dicom plugin) that itself is linked with gdcm.
Running ldd on one of the pluging get the similar missing vtk symbols 
and so.

So I suppose the problem is in vtk7

From what I can understand (sorry in advance for any approximation or 
stating the obvious):
1) gdcm 2.8.7-2 moved to python3 (probably because a move from python2 
to python3 was required) which I think triggered the choice of moving 
from vtk6 to vtk7 (which probably made more sense, as I presume vtk6 is 
also on its way out of buster).
2) When gdcm 2.8.7-2 arrived in sid, it generated a SegFaults during  
camitk 4.1.2-1 as camitk 4.1.2-1 was still based on vtk6, and loading 
any camitk executable meant that both vtk6 and vtk7 were loaded in memory.
3) camitk 4.1.2-2 introduced a patch so that it only depends on vtk7 
(and like gdcm 2.8.7 without changing the upstream source version).
4) gdcm 2.8.7-5 then fixed the double dependency to vtk6 and vtk7 but 
camitk 4.1.2-2 was not rebuilt against it, therefore generating the 
initial error that triggered bug #911793
5) vtk7 (which was updated in the meantime) seems to have now some 
missing libraries and as hdf5 is broken as well camitk 4.1.2-2 can not 
be rebuilt yet


Let me know if there is anything I can do to help.

On a side discussion:
Does the fact that I moved the dependency of camitk from vtk6 in 4.1.2-1 
to vtk7 in 4.1.2-2 might generate another ABI break? If this is the 
case, I will take any advice regarding how to specify this properly!
I will also welcome any information/documentation about how to track the 
symbol.


Best regards
Emmanuel

Bug#914449: haskell-blogliterately: FTBFS with ghc-8.4

[Ilias Tsitsimpis]

Source: haskell-blogliterately
Version: 0.8.6.2-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://github.com/byorgey/BlogLiterately/issues/40

Fails to build with ghc-8.4.3 with the following error:

src/Text/BlogLiterately/Options.hs:136:10: error:
* No instance for (Semigroup BlogLiterately)
arising from the superclasses of an instance declaration
* In the instance declaration for `Monoid BlogLiterately'
|
136 | instance Monoid BlogLiterately where
|  ^

-- 
Ilias

Bug#885638: gbonds: Please drop Build-Depends on rarian-compat

[Richard Laager]

On 11/23/18 7:38 AM, Jeremy Bicha wrote:
> gbonds is now 1 of the last 2 packages keeping rarian in Debian
> Unstable. Do you think you'll be able to review these patches soon?

Yes. I've been busy with a new baby at home, but I intend to get to
these very soon.

-- 
Richard

Processed: limit source to linux, reassign 910348 to src:linux, reassign 914431 to src:linux ..., closing 910348

[Debian Bug Tracking System]

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

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

> reassign 910348 src:linux 4.19~rc6-1~exp1
Bug #910348 {Done: Ben Hutchings } [linux-kbuild-4.19] 
linux-headers-4.19.0-rc6-amd64: File scripts/subarch.include is missing
Bug reassigned from package 'linux-kbuild-4.19' to 'src:linux'.
No longer marked as found in versions linux/4.19~rc6-1~exp1 and linux/4.18.20-1.
No longer marked as fixed in versions linux-signed-i386/4.19~rc7+1~exp1, 
linux-signed-amd64/4.19~rc7+1~exp1, linux-signed-arm64/4.19~rc7+1~exp1, and 
linux/4.19~rc7-1~exp1.
Bug #910348 {Done: Ben Hutchings } [src:linux] 
linux-headers-4.19.0-rc6-amd64: File scripts/subarch.include is missing
Marked as found in versions linux/4.19~rc6-1~exp1.
> reassign 914431 src:linux 4.18.20-1
Bug #914431 [linux-headers-4.18.0-3-common] linux-headers-4.18.0-3-common: 
missing file referred in Makefile
Bug reassigned from package 'linux-headers-4.18.0-3-common' to 'src:linux'.
No longer marked as found in versions linux/4.18.20-1.
Ignoring request to alter fixed versions of bug #914431 to the same values 
previously set
Bug #914431 [src:linux] linux-headers-4.18.0-3-common: missing file referred in 
Makefile
Marked as found in versions linux/4.18.20-1.
> forcemerge 910348 914431
Bug #910348 {Done: Ben Hutchings } [src:linux] 
linux-headers-4.19.0-rc6-amd64: File scripts/subarch.include is missing
Bug #910348 {Done: Ben Hutchings } [src:linux] 
linux-headers-4.19.0-rc6-amd64: File scripts/subarch.include is missing
Marked as found in versions linux/4.18.20-1.
Bug #914431 [src:linux] linux-headers-4.18.0-3-common: missing file referred in 
Makefile
Severity set to 'serious' from 'normal'
Marked Bug as done
Marked as found in versions linux/4.19~rc6-1~exp1.
Merged 910348 914431
> close 910348 4.19~rc7-1~exp1
Bug #910348 {Done: Ben Hutchings } [src:linux] 
linux-headers-4.19.0-rc6-amd64: File scripts/subarch.include is missing
Bug #914431 {Done: Ben Hutchings } [src:linux] 
linux-headers-4.18.0-3-common: missing file referred in Makefile
Marked as fixed in versions linux/4.19~rc7-1~exp1.
Marked as fixed in versions linux/4.19~rc7-1~exp1.
Bug #910348 {Done: Ben Hutchings } [src:linux] 
linux-headers-4.19.0-rc6-amd64: File scripts/subarch.include is missing
Bug #914431 {Done: Ben Hutchings } [src:linux] 
linux-headers-4.18.0-3-common: missing file referred in Makefile
Bug 910348 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#914440: photocollage: ValueError: Namespace Gtk not available

[Robert Pommrich]

Package: photocollage
Version: 1.4.3-2
Severity: grave

Dear Maintainer,

I get the following error, when I try to start photocollage.

$ photocollage
Traceback (most recent call last):
  File "/usr/bin/photocollage", line 21, in 
from photocollage import gtkgui
  File "/usr/lib/python3/dist-packages/photocollage/gtkgui.py", line 28, in 

gi.require_version('Gtk', '3.0')  # noqa
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 118, in 
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Gtk not available

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

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

Versions of packages photocollage depends on:
ii  python3   3.5.3-1
ii  python3-gi-cairo  3.22.0-2
ii  python3-pil   4.0.0-4
ii  python3-six   1.10.0-3

photocollage recommends no packages.

photocollage suggests no packages.

-- no debconf information


Best regards,
Robert Pommrich

Bug#885638: gbonds: Please drop Build-Depends on rarian-compat

[Jeremy Bicha]

Richard,

gbonds is now 1 of the last 2 packages keeping rarian in Debian
Unstable. Do you think you'll be able to review these patches soon?

Thanks,
Jeremy Bicha

Bug#914420: [Python-modules-team] Bug#914420: Bug#914420: python-pytest: Breaks many Python 2 test suites

[Ondrej Novy]

Hi,

pá 23. 11. 2018 v 13:21 odesílatel Ole Streicher 
napsal:

> By reading the upstream changelog, I could not find a cause what should
> cause the incompatibility. Also, the logs now all contain a warning like
>

me either. :(


> /usr/lib/python2.7/dist-packages/_pytest/cacheprovider.py:58
>   /usr/lib/python2.7/dist-packages/_pytest/cacheprovider.py:58:
> PytestWarning: could not create cache path
> /usr/lib/python2.7/dist-packages/aplpy/.pytest_cache/v/cache/nodeids
> PytestWarning(fmt.format(**args) if args else fmt), self._config
>
> which is not present in the Python 3 runs (and also not with pytest
> 3.6.4) -- this shows that probably something goes wrong when using
> pytest/Python2 on installed packages.
>

good point. I will dig into this.


> For python-m3u8, the CI test is a simple m3u8.loads() call that does not
> invoke pytest at all.
>

package build, not CI test :]

-- 
Best regards
 Ondřej Nový

Email: n...@ondrej.org
PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B

Bug#913163: (Security) bugs in pdns in stretch

[Moritz Mühlenhoff]

On Sat, Nov 10, 2018 at 04:34:48PM +0100, Chris Hofstaedtler wrote:
> Hi everyone,
> 
> thanks for reporting bugs against pdns in stretch.
> I intend to upload a new version to stretch to fix those bugs, but I
> cannot test all involved components personally. Please give this
> version a shot:

@Chris: Was there any test feedback so far?

If noone uses pdns on stretch, we can just as well remove it in the
next point release or block it out of buster.

If you do use, please give it a shot and test the update provided by Chris.

Cheers,
Moritz

Bug#911793: gdcm: ABI break

[Gert Wollny]

Control: reassign -1 vtk7 
Control: retitle -1 Don't drop some libvtkRendering* libraries

I don't think that this is a problem with gdcm, both camitk-imp and
camitk-config don't even list any gdcm library with ldd, but they both
list 

  libvtkRenderingFreeTypeFontConfig-7.1.so.7.1 => not found
  libvtkRenderingMatplotlib-7.1.so.7.1 => not found

So my guess it that I botchered vtk7 when I tried to fix the missing
armhf/armel build and somehow managed to exclude these libraries from
the package, and since camitk was build against an vtk7 package version
is has these libraries in the link list. 

I'll see what I can do to get this fixed, but vtk7 now has also a
python related bug and these are usually ugly to fix, so it may take
some time (especially since this is really not my field of work
anymore).

Best,
Gert

Processed: Re: gdcm: ABI break

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 vtk7
Bug #911793 [src:gdcm] gdcm: ABI break
Bug reassigned from package 'src:gdcm' to 'vtk7'.
No longer marked as found in versions gdcm/2.8.7-2.
Ignoring request to alter fixed versions of bug #911793 to the same values 
previously set
> retitle -1 Don't drop some libvtkRendering* libraries
Bug #911793 [vtk7] gdcm: ABI break
Changed Bug title to 'Don't drop some libvtkRendering* libraries' from 'gdcm: 
ABI break'.

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

Bug#914435: haskell-finite-field: Missing build-dependency on singletons

[Ilias Tsitsimpis]

Source: haskell-finite-field
Version: 0.8.0
Severity: serious
Justification: fails to build from source

This package is not part of LTS. Do we want to continue maintaining it?
If so, we will have to package singletons.

-- 
Ilias

Bug#914143: marked as done (soundscaperenderer FTBFS on armel/armhf)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 12:36:35 +
with message-id 
and subject line Bug#914143: fixed in soundscaperenderer 0.5.0~dfsg-3
has caused the Debian Bug report #914143,
regarding soundscaperenderer FTBFS on armel/armhf
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.)


-- 
914143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: soundscaperenderer
Version: 0.5.0~dfsg-1
Severity: serious
Tags: ftbfs

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

...
checking for QT... yes
checking GL/glu.h usability... no
checking GL/glu.h presence... no
checking for GL/glu.h... no
checking OpenGL/glu.h usability... no
checking OpenGL/glu.h presence... no
checking for OpenGL/glu.h... no
checking for library containing gluNewQuadric... no
checking for library containing glSelectBuffer... no
configure: error: --enable-gui (graphical user interface (using Qt)) requested 
but not available!
make: *** [/usr/share/cdbs/1/class/autotools.mk:46: debian/stamp-autotools/qt] 
Error 1


The root cause is that on armel/armhf
Qt5 is compiled with OpenGL ES instead of OpenGL.

Ideally it should be fixed to build and work with OpenGL ES,
but if this is not easily possible only soundscaperenderer-nox
should be built for armel and armhf.
--- End Message ---
--- Begin Message ---
Source: soundscaperenderer
Source-Version: 0.5.0~dfsg-3

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
soundscaperenderer 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, 20 Nov 2018 11:07:41 +0100
Source: soundscaperenderer
Binary: soundscaperenderer-nox soundscaperenderer soundscaperenderer-common
Architecture: source
Version: 0.5.0~dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Description:
 soundscaperenderer - tool for real-time spatial audio reproduction
 soundscaperenderer-common - tool for real-time spatial audio reproduction 
(common-files)
 soundscaperenderer-nox - tool for real-time spatial audio reproduction 
(without X support)
Closes: 914143
Changes:
 soundscaperenderer (0.5.0~dfsg-3) unstable; urgency=medium
 .
   * Don't build Qt-packages on armel/armhf (Closes: #914143)
   * B-D on non-virtual libqt5opengl5-dev package
Checksums-Sha1:
 3a85a9cd7a07f9687ec4f9ca9c35c8283bc0f37d 2535 
soundscaperenderer_0.5.0~dfsg-3.dsc
 74abe66dca40df980d9dbea0b7c3a0ef1ef3d42e 11680 
soundscaperenderer_0.5.0~dfsg-3.debian.tar.xz
 28849981b9775bdfc7b9c023e05cddbce9ae6f11 15786 
soundscaperenderer_0.5.0~dfsg-3_amd64.buildinfo
Checksums-Sha256:
 53fcf85bc822e3896c41bd4dfad183cf48e3047754512f4f4bb97657833e0701 2535 
soundscaperenderer_0.5.0~dfsg-3.dsc
 8ee2e01309c8518769bb152e38f5e6592665e3782d6556eef7237e0795b88f25 11680 
soundscaperenderer_0.5.0~dfsg-3.debian.tar.xz
 2565ee30e5417a7399400da58b2cedbfb22d4cb152e13a248cab28cb74fff96f 15786 
soundscaperenderer_0.5.0~dfsg-3_amd64.buildinfo
Files:
 0e0924c3442d232be1d962c838da309e 2535 sound optional 
soundscaperenderer_0.5.0~dfsg-3.dsc
 6c12669fa24ad3f5a84b4a0b0bd635b2 11680 sound optional 
soundscaperenderer_0.5.0~dfsg-3.debian.tar.xz
 4b1a3311f171035096fdee5cc42b0b4f 15786 sound optional 
soundscaperenderer_0.5.0~dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAlv34Q4ACgkQtlAZxH96
NvjybA//W7FZPOYBFEzO8BublWI7jpZnoDmCv2yim4nE6r57FeGg/A9ruTSX+2JT
xdQ0Z6N1MydjE2uGAYy1mW88cynUZ/I4ez4Y+Y5M/f4jOkIGOycvDk/ixqxQFRWY
JEpJ9blKsEB3AlwguCY9uTe/UB4ZOwTgl5J9dC1qxe5adSamKXlbUdb7XeeruuMz
LY5+KuYhqIuiSLylhIc2yd+s1u8TUECqEJc9VlpcU2Vd1Fq3ZjdqUqvUhNw+pVFL
13QRAaqJXEsqw+hLjRzW+1paVdO4xdvYO6DU+tJRq13jCHWvWIqQTqVAzlLlSqY9
LlNichMSET5rNzbgLmp+M3St/db+e8CPEytYAOF2Gw4JDL8z5Ta4YGu3hWB1tFud
u8VFwGaqPKEfHOB9QKktPzwRzaC592U+g+X8/sUmqmERot8kdCJbXlN3OD1GH9+e

Processed: summary 911278 Package is no longer maintained; requested removal.

[Debian Bug Tracking System]

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

> summary 911278 Package is no longer maintained; requested removal.
Summary recorded from message bug 911278 message 
> thanks
Stopping processing here.

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

Processed: Split 911371 into two bugs for two separate tasks

[Debian Bug Tracking System]

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

> clone 911371 -1
Bug #911371 [src:antlr4] antlr4: package v4.7.1 and include Cpp 
libraries/headers
Bug 911371 cloned as bug 914434
894359 was blocked by: 911371
894359 was not blocking any bugs.
Added blocking bug(s) of 894359: 914434
902798 was blocked by: 911371
902798 was not blocking any bugs.
Added blocking bug(s) of 902798: 914434
914434 was blocked by: 911302
914434 was blocking: 894359 902798
Ignoring request to alter blocking bugs of bug #914434 to the same blocks 
previously set
> retitle 911371 antlr4: package v4.7.1
Bug #911371 [src:antlr4] antlr4: package v4.7.1 and include Cpp 
libraries/headers
Changed Bug title to 'antlr4: package v4.7.1' from 'antlr4: package v4.7.1 and 
include Cpp libraries/headers'.
> retitle -1 antlr4: package Cpp libraries/headers
Bug #914434 [src:antlr4] antlr4: package v4.7.1 and include Cpp 
libraries/headers
Changed Bug title to 'antlr4: package Cpp libraries/headers' from 'antlr4: 
package v4.7.1 and include Cpp libraries/headers'.
> unblock 894359 by -1
Bug #894359 [src:beast2-mcmc] beast2-mcmc build depends on openjdk-8-jdk
894359 was blocked by: 911371 914434
894359 was not blocking any bugs.
Removed blocking bug(s) of 894359: 914434
> thanks
Stopping processing here.

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

Processed: Reassign 914417 to javahelper instead of src:javahelper

[Debian Bug Tracking System]

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

> reassign 914417 javahelper
Bug #914417 [src:javahelper] libjide-oss-java package does not install a 
jide-oss.jar file when built from source
Warning: Unknown package 'src:javahelper'
Bug reassigned from package 'src:javahelper' to 'javahelper'.
Ignoring request to alter found versions of bug #914417 to the same values 
previously set
Ignoring request to alter fixed versions of bug #914417 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#914420: [Python-modules-team] Bug#914420: python-pytest: Breaks many Python 2 test suites

[Ole Streicher]

Hi Ondrey,

newer astropy (>= 3.x) is limited to Python 3.x, and the problem appears
only with Python 2.7. The "python-astropy" package mentioned in the
Affects field of the bug is the stable (but supported) version 2.0.x,
which is (now) Python-2 only. The other packages mentioned there support
both Python branches, and there only Python 2 is affected.

By reading the upstream changelog, I could not find a cause what should
cause the incompatibility. Also, the logs now all contain a warning like

/usr/lib/python2.7/dist-packages/_pytest/cacheprovider.py:58
  /usr/lib/python2.7/dist-packages/_pytest/cacheprovider.py:58:
PytestWarning: could not create cache path
/usr/lib/python2.7/dist-packages/aplpy/.pytest_cache/v/cache/nodeids
PytestWarning(fmt.format(**args) if args else fmt), self._config

which is not present in the Python 3 runs (and also not with pytest
3.6.4) -- this shows that probably something goes wrong when using
pytest/Python2 on installed packages.

For python-m3u8, the CI test is a simple m3u8.loads() call that does not
invoke pytest at all.

Best

Ole

Processed: Re: Bug#914417: libjide-oss-java package does not install a jide-oss.jar file when built from source

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:javahelper
Bug #914417 [src:libjide-oss-java] libjide-oss-java package does not install a 
jide-oss.jar file when built from source
Bug reassigned from package 'src:libjide-oss-java' to 'src:javahelper'.
Warning: Unknown package 'src:javahelper'
Warning: Unknown package 'src:javahelper'
No longer marked as found in versions libjide-oss-java/3.7.4+dfsg-1.
Warning: Unknown package 'src:javahelper'
Warning: Unknown package 'src:javahelper'
Ignoring request to alter fixed versions of bug #914417 to the same values 
previously set
Warning: Unknown package 'src:javahelper'

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

Bug#914417: libjide-oss-java package does not install a jide-oss.jar file when built from source

[Markus Koschany]

Control: reassign -1 src:javahelper

Am 23.11.18 um 09:48 schrieb Matthias Klose:
> Package: src:libjide-oss-java
> Version: 3.7.4+dfsg-1
> Severity: serious
> Tags: sid buster
> 
> Seen at
> https://bugs.launchpad.net/ubuntu/+source/starjava-ttools/+bug/1804773
> 
> verified that a rebuild in unstable doesn't include the unversioned jar 
> symlink
> either.

This looks like a javahelper regression to me. I use a jlibs file, so
probably there is something wrong with jh_installlibs.

From the manual:

If the jars built by upstream already contain the version number, this
will be stripped before installing.
jh_installlibs will also try to strip the upstream version number of any
ds or dfsg suffix. Other version-mangling options or explicit version
numbers can also be provided.

I have not changed the format in years and always had a line with a
version number in *.jlibs

jide-oss-3.7.4.jar




signature.asc
Description: OpenPGP digital signature

Bug#914420: [Python-modules-team] Bug#914420: python-pytest: Breaks many Python 2 test suites

[Ondrej Novy]

Hi Ole,

this looks like bug in astropy and other packages. They are just not
compatible with newer pytest.

For example astropy upstream uses pytest 3.9 and/or 3.10 for testing code,
see
https://github.com/astropy/astropy/commit/3e34e7c450ebd982978423d8774ef6953832f610

I tried to build simple package python-m3u8, which uses pytest for py2 and
py3 and it build+test fine with newer pytest.

Thanks.

-- 
Best regards
 Ondřej Nový

Email: n...@ondrej.org
PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B

Bug#866653: RFS: thawab 4.1-1 [UPDATE]

[Jeremy Bicha]

As-Salaam Alaikum,

In order for thawab to get into Testing, we need to fix othman.

I believe othman's problem was that a source-only upload was done but
the package is non-free.

Please read this section and send the email. Please CC me on the email.
https://www.debian.org/doc/manuals/developers-reference/ch05.html#non-free-buildd

In the email, I think it would be helpful if you include a link to the
git commit where you added the autobuild line to debian/control.

thawab and hijra have the same issue so please follow the steps for
those 2 packages also.


Thank you,
Jeremy Bicha

Bug#911793: Control: reassign -1 src:gdcm 2.8.7-2

[Mattia Rizzolo]

On Fri, Nov 23, 2018 at 12:22:23PM +0100, Mathieu Malaterre wrote:
> > Also, before doing that somebody should check all the other binaries,
> > and verify they didn't change their ABI either.
> 
> Which binaries ? Those build from src:gdcm ?

Yup.  I didn't check libgdcm2.8, it should be checked.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#911793: Control: reassign -1 src:gdcm 2.8.7-2

[Mathieu Malaterre]

On Fri, Nov 23, 2018 at 12:04 PM Mattia Rizzolo  wrote:
>
> On Fri, Nov 23, 2018 at 11:41:10AM +0100, Mathieu Malaterre wrote:
> > As you've noticed the ABI breakage occur in between two minor uploads
> > -1 and -2. So I suspect this may confuse reader that bug be reported
> > against src:gdcm, since obviously not a single line change could have
> > occurred in between two minor uploads.
>
> I don't understand this sentence of yours.
> The debian revision in a version doesn't convey any particular meaning
> about the "dimension" of the changes.  In fact going from 2.8.7-1 to
> 2.8.7-2 could techinically ship a completely different upstream tarball
> with completely different code in it, still you would call that a "minor
> upload"?
>
> So everything could have happened in between.

https://www.debian.org/doc/debian-policy/ch-controlfields.html#version

[...]debian_revision This part of the version number specifies the
version of the Debian package based on the upstream version. [...]

In any case, the upstream source did not change a bit in between
uploads of those two debian_version.

> > Trying to read the changelog of 2.8.7-2 I only find reference to py3
> > changes, however digging a bit in the d/control Deps I can see a
> > switch from vtk6 to vtk7:
> >
> > https://salsa.debian.org/med-team/gdcm/commit/616785342cdfc6747125a3f505af0b985d4d8fee
> >
> > Since libvtkgdcm2.8 is a c++ project, I suspect that any change of any
> > inherited c++ class will change the ABI. I would suggest that
> > libvtkgdcm2.8 be removed, and a new binary package libvtk7gdcm2.8 be
> > uploaded instead.
>
> Please also read the rest of my email, that's what I deduced and
> recomended as well (apart from suggesting a particular name for the
> binary).

[...]
Also, I don't know what triggered this, if it was the py3 change or
the vtk change (most likely).
[...]

So my point was simply to remove this potential confusion. That is all.

> Also, before doing that somebody should check all the other binaries,
> and verify they didn't change their ABI either.

Which binaries ? Those build from src:gdcm ?

> BTW, it bothers me quite a lot that such a big change as moving from
> VTK6 to VTK7 has not been mentioned in the changelog at all.

True. Hence the confusion, which my email tried to remove.

> --
> regards,
> Mattia Rizzolo
>
> GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
> more about me:  https://mapreri.org : :'  :
> Launchpad user: https://launchpad.net/~mapreri  `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Bug#911793: Control: reassign -1 src:gdcm 2.8.7-2

[Mattia Rizzolo]

On Fri, Nov 23, 2018 at 11:41:10AM +0100, Mathieu Malaterre wrote:
> As you've noticed the ABI breakage occur in between two minor uploads
> -1 and -2. So I suspect this may confuse reader that bug be reported
> against src:gdcm, since obviously not a single line change could have
> occurred in between two minor uploads.

I don't understand this sentence of yours.
The debian revision in a version doesn't convey any particular meaning
about the "dimension" of the changes.  In fact going from 2.8.7-1 to
2.8.7-2 could techinically ship a completely different upstream tarball
with completely different code in it, still you would call that a "minor
upload"?

So everything could have happened in between.

> Trying to read the changelog of 2.8.7-2 I only find reference to py3
> changes, however digging a bit in the d/control Deps I can see a
> switch from vtk6 to vtk7:
> 
> https://salsa.debian.org/med-team/gdcm/commit/616785342cdfc6747125a3f505af0b985d4d8fee
> 
> Since libvtkgdcm2.8 is a c++ project, I suspect that any change of any
> inherited c++ class will change the ABI. I would suggest that
> libvtkgdcm2.8 be removed, and a new binary package libvtk7gdcm2.8 be
> uploaded instead.

Please also read the rest of my email, that's what I deduced and
recomended as well (apart from suggesting a particular name for the
binary).

Also, before doing that somebody should check all the other binaries,
and verify they didn't change their ABI either.


BTW, it bothers me quite a lot that such a big change as moving from
VTK6 to VTK7 has not been mentioned in the changelog at all.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#911793: Control: reassign -1 src:gdcm 2.8.7-2

[Mathieu Malaterre]

> This is a diff of a .symbols file I generated from libvtkgdcm2.8
> versions 2.8.7-1 and 2.8.7-2.

Thanks Mattia for tracking this issue !

As you've noticed the ABI breakage occur in between two minor uploads
-1 and -2. So I suspect this may confuse reader that bug be reported
against src:gdcm, since obviously not a single line change could have
occurred in between two minor uploads.

Trying to read the changelog of 2.8.7-2 I only find reference to py3
changes, however digging a bit in the d/control Deps I can see a
switch from vtk6 to vtk7:

https://salsa.debian.org/med-team/gdcm/commit/616785342cdfc6747125a3f505af0b985d4d8fee

Since libvtkgdcm2.8 is a c++ project, I suspect that any change of any
inherited c++ class will change the ABI. I would suggest that
libvtkgdcm2.8 be removed, and a new binary package libvtk7gdcm2.8 be
uploaded instead.

Processed: Re: [Debian-med-packaging] Bug#911793: autopkgtest regression: Segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:gdcm 2.8.7-2
Bug #911793 [src:camitk] camitk: autopkgtest regression: Segmentation fault
Bug reassigned from package 'src:camitk' to 'src:gdcm'.
No longer marked as found in versions camitk/4.1.2-2.
Ignoring request to alter fixed versions of bug #911793 to the same values 
previously set
Bug #911793 [src:gdcm] camitk: autopkgtest regression: Segmentation fault
Marked as found in versions gdcm/2.8.7-2.
> severity -1 serious
Bug #911793 [src:gdcm] camitk: autopkgtest regression: Segmentation fault
Severity set to 'serious' from 'normal'
> retitle -1 gdcm: ABI break
Bug #911793 [src:gdcm] camitk: autopkgtest regression: Segmentation fault
Changed Bug title to 'gdcm: ABI break' from 'camitk: autopkgtest regression: 
Segmentation fault'.
> affects -1 camitk
Bug #911793 [src:gdcm] gdcm: ABI break
Added indication that 911793 affects camitk

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

Bug#914062: marked as done (pyexiv2 FTBFS with boost 1.67)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 09:23:13 +
with message-id 
and subject line Bug#914062: fixed in pyexiv2 0.3.2-9
has caused the Debian Bug report #914062,
regarding pyexiv2 FTBFS with boost 1.67
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.)


-- 
914062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyexiv2
Version: 0.3.2-8
Severity: serious
Tags: ftbfs buster sid

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

...
g++ -o build/libexiv2python.so -Wl,-z,relro -shared build/exiv2wrapper.os 
build/exiv2wrapper_python.os -lboost_python-py27 -lexiv2
/bin/ld: cannot find -lboost_python-py27
collect2: error: ld returned 1 exit status
scons: *** [build/libexiv2python.so] Error 1


The Ubuntu diff seems to contain a fix.
--- End Message ---
--- Begin Message ---
Source: pyexiv2
Source-Version: 0.3.2-9

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

Debian distribution maintenance software
pp.
Michal Čihař  (supplier of updated pyexiv2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 23 Nov 2018 09:21:23 +0100
Source: pyexiv2
Binary: python-pyexiv2 python-pyexiv2-doc
Architecture: source
Version: 0.3.2-9
Distribution: unstable
Urgency: medium
Maintainer: Michal Čihař 
Changed-By: Michal Čihař 
Description:
 python-pyexiv2 - Python binding to Exiv2
 python-pyexiv2-doc - Documentation for Python binding to Exiv2
Closes: 914062
Changes:
 pyexiv2 (0.3.2-9) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Fixed VCS URL (https)
   * d/control: Set Vcs-* to salsa.debian.org
   * d/control: Remove trailing whitespaces
   * d/rules: Remove trailing whitespaces
   * d/control: Remove ancient X-Python-Version field
   * Convert git repository from git-dpm to gbp layout
 .
   [ Michal Čihař ]
   * Fix boost python library name (Closes: #914062).
   * d/control: Cleanup by cme.
   * Use dh_sphinxdoc.
   * Fix doc-base definition for text files.
Checksums-Sha1:
 33c96083325c574d5db9bc2b9f5fab909da7d254 2087 pyexiv2_0.3.2-9.dsc
 4276ac13661812e4e5e98694bfa5bb3bed3008d9 5052 pyexiv2_0.3.2-9.debian.tar.xz
 7b6dc38b810a23939dfc5fe642a3529800f81d9a 8757 pyexiv2_0.3.2-9_amd64.buildinfo
Checksums-Sha256:
 3051e00ffca167a4557d960fef8930f25792012d129b4e8dd3d91d0a6751c6dd 2087 
pyexiv2_0.3.2-9.dsc
 4dcf65f62497f31766930edd91bbfc9eda2cc47b141f2c2b321ca3999a9829c9 5052 
pyexiv2_0.3.2-9.debian.tar.xz
 61b376efa3e892e12112871105b93ac8d5c3e7241dafcc688218c411152efcf6 8757 
pyexiv2_0.3.2-9_amd64.buildinfo
Files:
 c5829e05055429fc5256f6068d388c9e 2087 python optional pyexiv2_0.3.2-9.dsc
 1c346c78451af41190ac6af9aa2b8088 5052 python optional 
pyexiv2_0.3.2-9.debian.tar.xz
 c83bde471f7c298c37c42e237748bb5c 8757 python optional 
pyexiv2_0.3.2-9_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEh+Zzr4P2w6DDRMjD9KoinU1YwkUFAlv3uNMACgkQ9KoinU1Y
wkWESA/+K9oPmbQfQT43VJtvpNzrzhltAt8s48rGE2cBsz3TbVUeI22KiVr3HwEI
siVcR55qat7GKA5oyUiq80vZgS00RL6WMsSpMpWkJW4cMRsGFClCLJaczPEKi0j2
6V4sprWZpy2XhZfv8R74dW56v6kQrlcxLWV/ZctSXBILYjg8TI/G0Ii7CIbejenG
ovuGpheaSyuKYG9JDkCSPq3SLH+6sCYAsXawR4PV2XWbLUK5aAOFE/uKmbjAYzVc
HuIYH7UN9/fW5HCZ8U00fq02yo+J7jHkjvjOESKUblR+gLYeK1Ad/ulYUt7hpbSX
Wg9IzIWr5OCaJ3GpQERiNpiwweSGsdsY9UkJi1P2PcK1UQlazRpp8cECK/65kdaV
0v/QBQWDyxLDT9Tp8dbjv5LbccpxQF+srKN6W3PDk18z+dmIjrHwkGbs6ReRUW0l
CMlJInFOiUYcn7injyUFXsSYxs58mw4mSI2pv0pjStpNiyEzgewd77DM6oirhlgI
FVz87ax8gquhn45ejGgILdcWHcKU18hKrESaUPX4B/71iJgcEcuwc9TRMD+fMhM6
VQebNBO0tBL5tRnMUCDYhYzdo5W3HSMu5cnwi95rsiETU+jR2UX98TzuXkF6bAa3
RLuuxhcwne0F9qaNeF0YxNqTdpwtDA9dYctXoDak9zSQ12otfAw=
=SmZx
-END PGP SIGNATURE End Message ---

Bug#914420: python-pytest: Breaks many Python 2 test suites

[Ole Streicher]

Package: python-pytest
Version: 3.9.3-2
Severity: serious
Affects: python-astropy, python-ccdproc, astropy-healpix, python-drizzle

Dear maintainer,

many astronomy Python packages rely on pytest for build and CI tests.
The Python 2 tests are now broken with the new version of pytest, since
the tests are not found anymore, and the test returns with exit code 5.
Depending on the build time tests, this may also cause FTBFS of some
packages.

Python 3 tests are not affected.

Best

Ole

Bug#914419: debhelper mustn't set pass V to make

[Adrian Bunk]

Package: debhelper
Version: 11.5.2
Severity: serious

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

...
dh clean --with autoreconf
   dh_auto_clean
make V=1 -j16 clean
make[1]: Entering directory '/build/1st/apcupsd-3.14.14'
1find . -depth \
  \( -name  -o -name  -o -name \*.a \) \
  -exec  "  CLEAN" \{\} \; -exec  \{\} \;
/bin/sh: 1: 1find: not found
make[1]: *** [autoconf/targets.mak:98: clean] Error 127


https://sources.debian.org/src/apcupsd/3.14.14-2/autoconf/targets.mak/#L98


Using V=1 for getting verbose build output is a relatively
recent convention followed by some software.

It is not something that is safe to use everywhere.

Bug#914175: lightning is not installable after binNMUs

[Pascal Legrand]

Same problem here.
No more lightning after upgrading thunderbird to 1:60.3.0-1+b1

--
Pascal

Processed: closing 914003

[Debian Bug Tracking System]

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

> close 914003 2.15.0-2
Bug #914003 [src:ruby-guard] ruby-guard FTBFS: test failure
Marked as fixed in versions ruby-guard/2.15.0-2.
Bug #914003 [src:ruby-guard] ruby-guard FTBFS: test failure
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#914417: libjide-oss-java package does not install a jide-oss.jar file when built from source

[Matthias Klose]

Package: src:libjide-oss-java
Version: 3.7.4+dfsg-1
Severity: serious
Tags: sid buster

Seen at
https://bugs.launchpad.net/ubuntu/+source/starjava-ttools/+bug/1804773

verified that a rebuild in unstable doesn't include the unversioned jar symlink
either.

Bug#868551: File conflict between redis-server-dbgsym and redis-tools-dbgsym

[Chris Lamb]

tags 868551 + wontfix
thanks

Hi Adrian,

> > > … is too invasive for a stable update. The version in stable is a
> > > little outdated anyway, and the backport is recommended anyway…
[…]
> No disagreement from me.

Thanks. Tagging as wontfix accordingly.


Regards,

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

Processed: Re: Bug#868551: File conflict between redis-server-dbgsym and redis-tools-dbgsym

[Debian Bug Tracking System]

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

> tags 868551 + wontfix
Bug #868551 {Done: Chris Lamb } [src:redis] File conflict 
between redis-server-dbgsym and redis-tools-dbgsym
Added tag(s) wontfix.
> thanks
Stopping processing here.

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

Processed: Bug #914062 in pyexiv2 marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #914062 [src:pyexiv2] pyexiv2 FTBFS with boost 1.67
Added tag(s) pending.

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

Bug#914062: Bug #914062 in pyexiv2 marked as pending

[Michal Čihař]

Control: tag -1 pending

Hello,

Bug #914062 in pyexiv2 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/pyexiv2/commit/8f7e8b67466a4e453a51e5a74e45eb5174cd9ac0


Fix boost python library name (Closes: #914062).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/914062

Bug#866653: RFS: thawab 4.1-1 [UPDATE]

[أحمد المحمودي]

Fixed

Please sponsor the upload of the updated package thawab.

Last changelog entry is:
thawab (4.1-1) unstable; urgency=medium

  [ Shanavas M ]
  * New upstream release
  * Fix debian/patches/private-pkg.diff

  [ أحمد المحمودي (Ahmed El-Mahmoudy) ]
  * Change priority to optional
  * Add webkit2.diff patch to port to Webkit2 (Closes: #866653)
  * Update Vcs-* URIs
  * Removed X-Python-Version field, not needed anymore
  * Update standards version to 4.2.1, no changes needed
  * Bumped compat level to 11
  * Switch to secure copyright format URL
  * Update copyright years


The package has the following lintian issues:
I: thawab source: missing-explanation-for-contrib-or-non-free-package
I: thawab source: testsuite-autopkgtest-missing
P: thawab source: debian-watch-does-not-check-gpg-signature
I: thawab: desktop-entry-lacks-keywords-entry 
usr/share/applications/thawab.desktop
X: thawab: dependency-on-python-version-marked-for-end-of-life (Depends: python)

The package is on: g...@salsa.debian.org:islamic-team/thawab.git


-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Bug#914411: maven-javadoc-plugin FTBFS: unreported exception java.io.IOException; must be caught or declared to be thrown

[Adrian Bunk]

Source: maven-javadoc-plugin
Version: 3.0.1-1
Severity: serious
Tags: ftbfs

Some recent change in unstable makes maven-javadoc-plugin FTBFS:

https://tests.reproducible-builds.org/debian/history/maven-javadoc-plugin.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/maven-javadoc-plugin.html

...
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project maven-javadoc-plugin: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/maven-javadoc-plugin-3.0.1/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java:[1181,34]
 unreported exception java.io.IOException; must be caught or declared to be 
thrown
[ERROR] 
/build/1st/maven-javadoc-plugin-3.0.1/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java:[1183,34]
 unreported exception java.io.IOException; must be caught or declared to be 
thrown
[ERROR] 
/build/1st/maven-javadoc-plugin-3.0.1/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java:[1184,34]
 unreported exception java.io.IOException; must be caught or declared to be 
thrown
[ERROR] 
/build/1st/maven-javadoc-plugin-3.0.1/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java:[1185,34]
 unreported exception java.io.IOException; must be caught or declared to be 
thrown
[ERROR] 
/build/1st/maven-javadoc-plugin-3.0.1/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java:[1186,34]
 unreported exception java.io.IOException; must be caught or declared to be 
thrown
[ERROR] 
/build/1st/maven-javadoc-plugin-3.0.1/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java:[1187,34]
 unreported exception java.io.IOException; must be caught or declared to be 
thrown
[ERROR] 
/build/1st/maven-javadoc-plugin-3.0.1/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java:[1188,34]
 unreported exception java.io.IOException; must be caught or declared to be 
thrown
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/maven-javadoc-plugin-3.0.1 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/maven-javadoc-plugin-3.0.1/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/maven-javadoc-plugin-3.0.1/debian 
-Dmaven.repo.local=/build/1st/maven-javadoc-plugin-3.0.1/debian/maven-repo 
--batch-mode package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned 
exit code 1
make: *** [debian/rules:4: build] Error 2

Bug#914054: marked as done (calamares FTBFS with boost 1.67)

[Debian Bug Tracking System]

Your message dated Fri, 23 Nov 2018 09:01:27 +0200
with message-id <8c28f96e-1775-1154-3136-6937298d5...@debian.org>
and subject line Fixed
has caused the Debian Bug report #914054,
regarding calamares FTBFS with boost 1.67
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.)


-- 
914054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: calamares
Version: 3.2.2-1
Severity: serious
Tags: ftbfs

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

...
cd /<>/obj-x86_64-linux-gnu/src/libcalamares && /usr/bin/c++  
-DDLLEXPORT_PRO -DPYTHONQT_USE_RELEASE_PYTHON_FALLBACK -DQT_CORE_LIB 
-DQT_NO_DEBUG -DQT_SHARED -DQT_SHAREDPOINTER_TRACK_POINTERS 
-DQT_STRICT_ITERATORS -Dcalamares_EXPORTS 
-I/<>/obj-x86_64-linux-gnu/src/libcalamares/calamares_autogen/include
 -I/<>/src -I/<>/src/libcalamares 
-I/<>/src/libcalamaresui 
-I/<>/obj-x86_64-linux-gnu/src 
-I/<>/obj-x86_64-linux-gnu/src/libcalamares 
-I/<>/obj-x86_64-linux-gnu/src/libcalamaresui 
-I/usr/include/python3.6m -I/usr/include/PythonQt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,--no-undefined 
-Wl,--fatal-warnings -Wnon-virtual-dtor -Woverloaded-virtual 
-Werror=return-type -fdiagnostics-color=auto -fPIC   -fPIC -std=gnu++14 -o 
CMakeFiles/calamares.dir/GlobalStorage.cpp.o -c 
/<>/src/libcalamares/GlobalStorage.cpp
In file included from /usr/include/yaml-cpp/node/iterator.h:13,
 from /usr/include/yaml-cpp/node/impl.h:11,
 from /usr/include/yaml-cpp/yaml.h:17,
 from /<>/src/modules/test_conf.cpp:29:
/usr/include/yaml-cpp/node/detail/iterator.h: In member function 'void 
YAML::detail::iterator_base::increment()':
/usr/include/yaml-cpp/node/detail/iterator.h:48:54: error: 'next' is not a 
member of 'boost'
   void increment() { this->base_reference() = boost::next(this->base()); }
  ^~~~
/usr/include/yaml-cpp/node/detail/iterator.h:48:54: note: suggested 
alternatives:
In file included from /usr/include/c++/8/bits/stl_algobase.h:66,
 from /usr/include/c++/8/bits/char_traits.h:39,
 from /usr/include/c++/8/ios:40,
 from /usr/include/c++/8/ostream:38,
 from /usr/include/c++/8/iostream:39,
 from /<>/src/modules/test_conf.cpp:27:
/usr/include/c++/8/bits/stl_iterator_base_funcs.h:213:5: note:   'std::next'
 next(_InputIterator __x, typename
 ^~~~
In file included from /usr/include/boost/mpl/next.hpp:17,
 from /usr/include/boost/mpl/bind.hpp:25,
 from /usr/include/boost/mpl/lambda.hpp:18,
 from /usr/include/boost/mpl/apply.hpp:25,
 from /usr/include/boost/iterator/iterator_facade.hpp:36,
 from /usr/include/yaml-cpp/node/detail/node_iterator.h:12,
 from /usr/include/yaml-cpp/node/detail/iterator.h:12,
 from /usr/include/yaml-cpp/node/iterator.h:13,
 from /usr/include/yaml-cpp/node/impl.h:11,
 from /usr/include/yaml-cpp/yaml.h:17,
 from /<>/src/modules/test_conf.cpp:29:
/usr/include/boost/mpl/next_prior.hpp:29:8: note:   'boost::mpl::next'
 struct next
^~~~
make[3]: *** [src/modules/CMakeFiles/test_conf.dir/build.make:66: 
src/modules/CMakeFiles/test_conf.dir/test_conf.cpp.o] Error 1
--- End Message ---
--- Begin Message ---
Fixed by rebuilding against newer version of yamlk-cpp that was recently
uploaded in unstable.--- End Message ---

Bug#914410: ruby-validate-url FTBFS: test failure

[Adrian Bunk]

Source: ruby-validate-url
Version: 1.0.2+git-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=ruby-validate-url=all=1.0.2%2Bgit-1=1542891743=0

...
┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=. 
GEM_PATH=debian/ruby-validate-url/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation

An error occurred while loading 
/<>/ruby-validate-url-1.0.2+git/spec/validate_url_spec.rb.
Failure/Error: require 'active_record'

LoadError:
  cannot load such file -- active_record
# /<>/ruby-validate-url-1.0.2+git/spec/spec_helper.rb:7:in `'
# /<>/ruby-validate-url-1.0.2+git/spec/validate_url_spec.rb:2:in 
`'
No examples found.

Finished in 0.00031 seconds (files took 0.18346 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples

/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/<>/ruby-validate-url-1.0.2\+git/debian/ruby-validate-url returned 
exit code 1
make: *** [debian/rules:7: binary-indep] Error 1