Processed: tagging 875321, tagging 925667, tagging 934709, tagging 935246, tagging 928993, tagging 935086 ...

[Debian Bug Tracking System]

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

> tags 875321 + bullseye experimental
Bug #875321 [src:openambit] QJson removal form Buster
Bug #875327 [src:openambit] QJson removal in Buster
Added tag(s) bullseye and experimental.
Added tag(s) bullseye and experimental.
> tags 925667 + experimental
Bug #925667 {Done: Boyuan Yang } [src:dde-qt-dbus-factory] 
dde-qt-dbus-factory: ftbfs with GCC-9
Added tag(s) experimental.
> tags 934709 + bullseye sid
Bug #934709 {Done: IOhannes m zmölnig (Debian/GNU) } 
[src:v4l2loopback] v4l2loopback: autopkgtest fails when there is a new version 
of linux-latest
Added tag(s) sid and bullseye.
> tags 935246 + sid bullseye
Bug #935246 [php-patchwork-utf8] Useless in Debian
Added tag(s) sid and bullseye.
> tags 928993 + experimental
Bug #928993 {Done: Boyuan Yang } [sdaps] sdaps: Please 
package the latest upstream version
Added tag(s) experimental.
> tags 935086 + sid bullseye
Bug #935086 [src:insighttoolkit4] insighttoolkit4: FTBFS with GCC-9: use of 
undeclared identifier '__builtin_is_constant_evaluated'
Added tag(s) bullseye and sid.
> tags 891993 - buster
Bug #891993 [src:syrthes] syrthes: Build-Depends on Qt4-only python-qwt5-qt4
Removed tag(s) buster.
> tags 906578 + sid bullseye
Bug #906578 [src:makehuman] [makehuman] Future Qt4 removal
Added tag(s) bullseye and sid.
> tags 932614 + sid bullseye
Bug #932614 {Done: Sandro Tosi } [src:basemap] basemap: 
pyproj upstream going to drop Python 2 support
Added tag(s) sid and bullseye.
> tags 932653 + sid bullseye
Bug #932653 {Done: Sandro Tosi } [src:overpass] 
python-overpass: Don't depend on python-geojson
Added tag(s) sid and bullseye.
> tags 935324 + sid bullseye
Bug #935324 [src:qemu] FTBFS: gluster API has changed
Added tag(s) sid and bullseye.
> tags 935290 + sid bullseye experimental
Bug #935290 [src:rakudo] rakudo: FTBFS on amd64
Added tag(s) experimental, bullseye, and sid.
> tags 858774 + sid bullseye
Bug #858774 [gr-air-modes] modes_rx: ImportError: cannot import name QtWebKit
Added tag(s) bullseye and sid.
> tags 935339 + sid bullseye
Bug #935339 [ruby-svg-graph] ruby-svg-graph: depends on ancient 'parsedate' 
Ruby core library
Added tag(s) sid and bullseye.
> tags 935272 + sid bullseye
Bug #935272 {Done: Ole Streicher } [src:astropy-healpix] 
astropy-healpix: FTBFS on amd64
Added tag(s) sid and bullseye.
> tags 935384 + sid bullseye
Bug #935384 [phpunit-git] Abandoned upstream
Added tag(s) bullseye and sid.
> tags 932668 + sid bullseye
Bug #932668 {Done: Samuel Henrique } [src:python-shodan] 
python-shodan: Don't depend on python-click-plugins
Added tag(s) bullseye and sid.
> tags 849862 + sid bullseye
Bug #849862 {Done: Debian FTP Masters } 
[kmidimon] kmidimon needs updaing to latest libdrumstick (1.0.2-1)
Added tag(s) bullseye and sid.
> tags 875086 + sid bullseye
Bug #875086 [src:paraview] [paraview] Future Qt4 removal from Buster
Added tag(s) sid and bullseye.
> tags 906564 + sid bullseye
Bug #906564 [src:buildnotify] [buildnotify] Future Qt4 removal
Added tag(s) sid and bullseye.
> found 931921 1.26.2+dfsg-10
Bug #931921 [clutter-1.0-tests] clutter's autopkgtests hang when ran with a 
libglib2.0-0 built with gcc-9
Marked as found in versions clutter-1.0/1.26.2+dfsg-10.
> tags 931921 + sid bullseye
Bug #931921 [clutter-1.0-tests] clutter's autopkgtests hang when ran with a 
libglib2.0-0 built with gcc-9
Added tag(s) bullseye and sid.
> tags 843897 + sid bullseye
Bug #843897 {Done: Gianfranco Costamagna } 
[python-pyqtgraph] Should allow pyqt5
Added tag(s) bullseye and sid.
> tags 935335 + sid bullseye
Bug #935335 [src:monkeysign] Depends on removed python-zbar
Added tag(s) bullseye and sid.
> tags 875501 + sid bullseye
Bug #875501 {Done: Debian FTP Masters } 
[src:opensesame] Qt4 removal from Buster
Added tag(s) sid and bullseye.
> tags 875500 + sid bullseye
Bug #875500 {Done: Debian FTP Masters } 
[src:seascope] Qt4 removal form Buster
Added tag(s) bullseye and sid.
> tags 935375 + sid bullseye
Bug #935375 {Done: Debian FTP Masters } 
[buffycli] buffycli: Depends on to be removed libs
Added tag(s) sid and bullseye.
> tags 935486 + sid bullseye
Bug #935486 [quicksynergy] quicksynergy: Depends on synergy which is due to be 
removed (Obsolete libs)
Added tag(s) bullseye and sid.
> tags 916195 + sid bullseye
Bug #916195 [python3-qwt] python3-qwt: make optional the python3-pyqt4 
dependency
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
843897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843897
849862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849862
858774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858774
875086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875086
875321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875321
875327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875327
875500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875500
875501: 

Bug#935570: src:pysph: License and Copyrights missing from debian/copyright

[Scott Kitterman]

Package: src:pysph
Version: 1.0~a6-1
Severity: serious
Justification: Policy 2.3

During review of your package in New, the following items were noted to
be missing from debian/copyright.  I'm filing this bug instead of
rejecting the package (since it's not a new issue in the package).
Please fix in your next upload.

Scott K

pysph/tools/fortranfile.py:
# Copyright 2008, 2009 Neil Martinsen-Burrell
#
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
# copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:

# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.

# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
# THE SOFTWARE.

pysph/tools/tests/test_interpolator.py:
# Author: Prabhu Ramachandran
# Copyright (c) 2014 Prabhu Ramachandran
# License: BSD Style.

pysph/tools/gmsh.py:
Copyright (c) 2015 Prabhu Ramachandran

pysph/sph/tests/test_simple_inlet_outlet.py:
Copyright (c) 2015, Prabhu Ramachandran
License: BSD

pysph/sph/simple_inlet_outlet.py:
# Copyright (c) 2015-2017, Prabhu Ramachandran
# License: BSD

pyzoltan/core/msstdint.h:
//
//  Copyright (c) 2006-2013 Alexander Chemeris
//
// Redistribution and use in source and binary forms, with or without
// modification, are permitted provided that the following conditions are met:
//
//   1. Redistributions of source code must retain the above copyright notice,
//  this list of conditions and the following disclaimer.
//
//   2. Redistributions in binary form must reproduce the above copyright
//  notice, this list of conditions and the following disclaimer in the
//  documentation and/or other materials provided with the distribution.
//
//   3. Neither the name of the product nor the names of its contributors may
//  be used to endorse or promote products derived from this software
//  without specific prior written permission.
//
// THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED
// WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
// MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
// EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
// PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
// OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
// WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
// OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
// ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Scott K

Bug#935568: sphinx-issuetracker: should this package be removed?

[Sandro Tosi]

Source: sphinx-issuetracker
Severity: serious

Hello,
sphinx-issuetracker is currently incompatible with python3.7:

Exception occurred:
  File 
"/build/sphinx-issuetracker-0.11/sphinxcontrib/issuetracker/__init__.py", line 
282, in connect_builtin_tracker
from sphinxcontrib.issuetracker.resolvers import BUILTIN_ISSUE_TRACKERS
  File 
"/build/sphinx-issuetracker-0.11/sphinxcontrib/issuetracker/resolvers.py", line 
138
except ImportError, e:
  ^
SyntaxError: invalid syntax


it has a very low popcon value

It has no reverse-dependencies and it's currently one of the few r-deps of
python-debianbts.

Should we just remove this package from Debian?

Thanks,
Sandro

-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#875057: marked as done ([mp3diags] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sat, 24 Aug 2019 01:35:01 +
with message-id 
and subject line Bug#875057: fixed in mp3diags 1.5.01-1
has caused the Debian Bug report #875057,
regarding [mp3diags] 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.)


-- 
875057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mp3diags
Version: 1.2.03-1
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: mp3diags
Source-Version: 1.5.01-1

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated mp3diags 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 Aug 2019 18:44:15 -0600
Source: mp3diags
Binary: mp3diags
Architecture: source
Version: 1.5.01-1
Distribution: unstable
Urgency: medium
Maintainer: Josue Ortega 
Changed-By: Josue Ortega 
Description:
 mp3diags   - find issues in MP3 files and help to solve them
Closes: 875057
Changes:
 mp3diags (1.5.01-1) unstable; urgency=medium
 .
   * New upstream release (1.5.01-1)
 - Refresh debian/patches
 - debian/rules: Update icons name at override_dh_install
 - Update binary name at installation
   * Update debian watch file
   * Update package to use Qt5. Closes: #875057
   * Update package to use debhelper-compat (= 12)
 - debian/rules: Remove unnecessary argument --parallel
   * Update Vcs-* to use salsa.debian.org.
   * Add debian/clean to remove unsafe symlink from source
   * Bump Standards-Version to 4.4.0:
 - debian/copyright: Update Format field to use https
   * Add debian/source/lintian-overrides
   * Add Debian CI tests
Checksums-Sha1:
 8782ac709079dc56209d9c01273b5d7b4d584dd7 1977 mp3diags_1.5.01-1.dsc
 eebac4ef2042b00a70e3a5f92f70d7ea1763079c 7465534 mp3diags_1.5.01.orig.tar.gz
 13dd4436678e97a344ced2b62860682814d415dc 7820 mp3diags_1.5.01-1.debian.tar.xz
 497813d77b5dfa583c95c310785179e89a645e07 10953 
mp3diags_1.5.01-1_amd64.buildinfo
Checksums-Sha256:
 5aed6886a6aeaf92dc84ea28fa4fab22a2df5411b53a1e479c566d93e046187a 1977 
mp3diags_1.5.01-1.dsc
 

Bug#899007: marked as done (bauble: Depends on unmaintained python-gdata)

[Debian Bug Tracking System]

Your message dated Sat, 24 Aug 2019 01:20:54 +
with message-id 
and subject line Bug#935508: Removed package(s) from unstable
has caused the Debian Bug report #899007,
regarding bauble: Depends on unmaintained python-gdata
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.)


-- 
899007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bauble
Version: 0.9.7-2.1
Severity: important

Dear maintainer,

Your package currently uses python-gdata, which is dead upstream and had no
upstream release since 2013. It also does not support Python 3.

The recommended alternative is using google-api-python-client [1], which is
packaged in Debian as python-googleapi.

I would like to remove python-gdata from Debian Buster, so please update
your package.

[1]: https://github.com/google/google-api-python-client

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.9.7-2.1+rm

Dear submitter,

as the package bauble has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/935508

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#874955: marked as done ([kmidimon] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sat, 24 Aug 2019 01:21:30 +
with message-id 
and subject line Bug#935541: Removed package(s) from unstable
has caused the Debian Bug report #874955,
regarding [kmidimon] 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.)


-- 
874955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kmidimon
Version: 0.7.5-3
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 ---
Version: 0.7.5-3+rm

Dear submitter,

as the package kmidimon has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/935541

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#925705: marked as done (grantlee: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Sat, 24 Aug 2019 01:23:44 +
with message-id 
and subject line Bug#935554: Removed package(s) from unstable
has caused the Debian Bug report #925705,
regarding grantlee: ftbfs with GCC-9
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.)


-- 
925705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:grantlee
Version: 0.4.0-4
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/grantlee_0.4.0-4_unstable_gcc9.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
QWARN  : TestInternationalization::testFailure(fail-03) "Unknown tag: "i18np", 
line 0, " 
QWARN  : TestInternationalization::testFailure(fail-04) "Unknown tag: "i18ncp", 
line 0, " 
PASS   : TestInternationalization::testFailure()
PASS   : TestInternationalization::cleanupTestCase()
Totals: 9 passed, 31 failed, 0 skipped
* Finished testing of TestInternationalization *

 9/11 Test #10: htmlbuildertest ..Child aborted***Exception:   
0.02 sec
* Start testing of TestHtmlOutput *
Config: Using QTest library 4.8.7, Qt 4.8.7
PASS   : TestHtmlOutput::initTestCase()
PASS   : TestHtmlOutput::testSingleFormat()
htmlbuildertest_exec: malloc.c:2852: mremap_chunk: Assertion `((size + offset) 
& (GLRO (dl_pagesize) - 1)) == 0' failed.

10/11 Test #11: plainmarkupbuildertest ...Child aborted***Exception:   
0.02 sec
* Start testing of TestPlainMarkupOutput *
Config: Using QTest library 4.8.7, Qt 4.8.7
PASS   : TestPlainMarkupOutput::initTestCase()
PASS   : TestPlainMarkupOutput::testSingleFormat()
plainmarkupbuildertest_exec: malloc.c:2852: mremap_chunk: Assertion `((size + 
offset) & (GLRO (dl_pagesize) - 1)) == 0' failed.

11/11 Test  #7: testgenerictypes .***Failed0.04 sec
* Start testing of TestGenericTypes *
Config: Using QTest library 4.8.7, Qt 4.8.7
PASS   : TestGenericTypes::initTestCase()
PASS   : TestGenericTypes::testGenericClassType()
PASS   : TestGenericTypes::testSequentialContainer_Variant()
PASS   : TestGenericTypes::testAssociativeContainer_Variant()
PASS   : TestGenericTypes::testSequentialContainer_Type()
PASS   : TestGenericTypes::testAssociativeContainer_Type()
PASS   : TestGenericTypes::testSharedPointer()
PASS   : TestGenericTypes::testThirdPartySharedPointer()
FAIL!  : TestGenericTypes::testNestedContainers() Compared values are not the 
same
   Actual (result): (M ([0, ] : (L ),([1, ] : (L ),),(M ([0, ] : (L ),([1, ] : 
(L ),),
   Expected (expectedResult): (M (0 : (L (V 1,2,),(V 3,4,),),(1 : (L (V 
5,6,),(V 7,8,),),),(M (0 : (L (V 9,10,),(V 11,12,),),(1 : (L (V 13,14,),(V 
15,16,),),),
   Loc: [/<>/templates/tests/testgenerictypes.cpp(688)]
PASS   : TestGenericTypes::testCustomQObjectDerived()
QWARN  : TestGenericTypes::testUnregistered() Don't know how to handle metatype 
UnregisteredType 
QWARN  : TestGenericTypes::testUnregistered() Don't know how to handle metatype 
for list UnregisteredType 
QWARN  : TestGenericTypes::testUnregistered() No toList function for metatype 
RegisteredNotListType 
QWARN  : TestGenericTypes::testUnregistered() No lookup function for metatype 
UnregisteredType 
PASS   : TestGenericTypes::testUnregistered()
PASS   : 

Bug#874908: marked as done ([grantlee] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sat, 24 Aug 2019 01:23:44 +
with message-id 
and subject line Bug#935554: Removed package(s) from unstable
has caused the Debian Bug report #874908,
regarding [grantlee] 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.)


-- 
874908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: grantlee
Version: 0.4.0-4
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 ---
Version: 0.4.0-4+rm

Dear submitter,

as the package grantlee has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/935554

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#849862: marked as done (kmidimon needs updaing to latest libdrumstick (1.0.2-1))

[Debian Bug Tracking System]

Your message dated Sat, 24 Aug 2019 01:21:30 +
with message-id 
and subject line Bug#935541: Removed package(s) from unstable
has caused the Debian Bug report #849862,
regarding kmidimon needs updaing to latest libdrumstick (1.0.2-1)
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.)


-- 
849862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kmidimon
Version: 0.7.5-3
Severity: wishlist

Dear Maintainer,

I am looking to join in with the maintenance of the libdrumstick suite of
packages (vmpk, kmetronome etc.). Libdrumstick 1.0.2-1 is currently sitting in
experimental, waiting for a transition slot. Unfortunately, we missed the date
of the transition freeze for Debian Stretch, so it will have to wait for
Buster.

Kmidimon is the only remaining reverse dependency of libdrumstick in Debian
that does not build with the latest version in experimental. Discussions with
the upstream maintainer suggest that it will be upgraded (including migration
to the latest Qt5 libraries) in early 2017.



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 0.7.5-3+rm

Dear submitter,

as the package kmidimon has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/935541

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#935563: astropy 3.2.1 breaks sunpy

[Steve Langasek]

Source: astropy
Version: 3.2.1-1
Severity: serious
Justification: autopkgtest regressions block migration
Affects: sunpy/0.9.6-2
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan autopkgtest

Hi Ole,

The sunpy autopkgtests fail with new astropy 3.2.1-1, and considering the
failing autopkgtest is one specifically intended to test an error-prone
astropy transformation (according to the comments), this looks to me like it
may be a genuine regression in astropy that's caught by sunpy:

[...]
=== FAILURES ===
 test_hgs_hcrs _

def test_hgs_hcrs():
# This test checks the HGS->HCRS transformation by transforming from 
HGS to
# HeliocentricTrueEcliptic (HTE).  It will fail if there are errors in 
Astropy's
# HCRS->ICRS or ICRS->HTE transformations.

# Use published HGS coordinates in the Astronomical Almanac (2013), 
pages C6-C7
obstime = Time('2013-01-28')
earth_hgs = SkyCoord(0*u.deg, -5.73*u.deg, 0.9848139*u.AU, 
frame=HeliographicStonyhurst,
 obstime=obstime)

# Transform to HTE at observation-time equinox
earth_hte = 
earth_hgs.transform_to(HeliocentricTrueEcliptic(equinox=obstime))

# Validate against published values from the Astronomical Almanac 
(2013), page C6 per page E2
# The dominant source of inaccuracy is the limited precision of the 
published B0 used above
>   assert quantity_allclose(earth_hte.lon, Angle('308d13m30.51s') - 
> 180*u.deg, atol=5*u.arcsec)
E   assert False
E+  where False = quantity_allclose(, 
( - (180 * Unit("deg"))), atol=(5 * Unit("arcsec")))
E+where  = .lon
E+and= Angle('308d13m30.51s')
E+and   Unit("deg") = u.deg
E+and   Unit("arcsec") = u.arcsec

/usr/lib/python3/dist-packages/sunpy/coordinates/tests/test_transformations.py:146:
 AssertionError
[...]

(https://ci.debian.net/data/autopkgtest/testing/amd64/s/sunpy/2801123/log.gz)

Opening a bug so that this is documented in the BTS (and so it can be
reassigned if I'm wrong about which package is to blame).

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#935562: goobook raises exception about google-auth-httplib2

[Matthew Moore]

Package: goobook
Version: 3.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Running goobook results in a traceback:

Traceback (most recent call last):
  File "/usr/bin/goobook", line 6, in 
from pkg_resources import load_entry_point
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3250, 
in 
@_call_aside
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3234, 
in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3263, 
in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 583, in 
_build_master
ws.require(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 900, in 
require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 786, in 
resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'google-auth-httplib2>=0.0.3' 
distribution was not found and is required by google-api-python-client

--

The correct dependencies are installed, and it seems like the versions are
correct, so I'm not sure why the exception is being raised.


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

Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to C.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
C.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages goobook depends on:
ii  python3   3.7.3-1
ii  python3-googleapi 1.7.11-2
ii  python3-oauth2client  4.1.2-4
ii  python3-simplejson3.16.0-2

goobook recommends no packages.

goobook suggests no packages.

-- no debconf information

Bug#935015: datalad: diff for NMU version 0.11.6-1.1

[Sandro Tosi]

Control: tags 935015 + patch
Control: tags 935015 + pending


Dear maintainer,

I've prepared an NMU for datalad (versioned as 0.11.6-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

This drops python2, and switch to python3 (freeing the latest rdep of
python-tqdm)

Regards.

diff -Nru datalad-0.11.6/debian/changelog datalad-0.11.6/debian/changelog
--- datalad-0.11.6/debian/changelog	2019-07-29 12:07:25.0 -0400
+++ datalad-0.11.6/debian/changelog	2019-08-23 17:41:08.0 -0400
@@ -1,3 +1,11 @@
+datalad (0.11.6-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support and switch to python 3; patches by Steve Langasek;
+Closes: #935015
+
+ -- Sandro Tosi   Fri, 23 Aug 2019 17:41:08 -0400
+
 datalad (0.11.6-1) unstable; urgency=medium
 
   * Fresh upstream release
diff -Nru datalad-0.11.6/debian/control datalad-0.11.6/debian/control
--- datalad-0.11.6/debian/control	2019-07-29 12:07:25.0 -0400
+++ datalad-0.11.6/debian/control	2019-08-23 17:40:59.0 -0400
@@ -11,39 +11,6 @@
  git-annex (>= 6.20180913~) | git-annex-standalone (>= 6.20180913~),
  help2man,
  patool,
- python-all,
- python-appdirs,
- python-argcomplete,
- python-boto,
- python-dateutil,
- python-exif,
- python-fasteners,
- python-iso8601,
- python-jsmin,
- python-git (>= 2.1.6~),
- python-github,
- python-html5lib,
- python-httpretty,
- python-humanize,
- python-keyrings.alt | python-keyring (<=8),
- python-keyring,
- python-secretstorage | python-keyring (<<9.2),
- python-nose (>= 1.3.7-2) | python-libxmp,
- python-lzma,
- python-mock,
- python-msgpack,
- python-mutagen,
- python-nose,
- python-pil,
- python-pyperclip,
- python-requests,
- python-setuptools,
- python-simplejson,
- python-six (>= 1.8.0~),
- python-tqdm,
- python-whoosh,
- python-vcr,
- python-wrapt,
  python3-all,
  python3-appdirs,
  python3-argcomplete,
@@ -89,7 +56,7 @@
  python3-datalad (= ${binary:Version}),
  python3-argcomplete,
  ${misc:Depends},
- ${python:Depends}
+ ${python3:Depends}
 Suggests:
  datalad-containers,
  datalad-crawler,
@@ -113,69 +80,6 @@
  This package provides the command line tools.  Install without
  Recommends if you need only core functionality.
 
-Package: python-datalad
-Architecture: all
-Section: python
-Provides: ${python:Provides}
-Depends:
- git-annex (>= 6.20180913~) | git-annex-standalone (>= 6.20180913~),
- patool,
- python-appdirs,
- python-fasteners,
- python-git (>= 2.1.6~),
- python-humanize,
- python-iso8601,
- python-keyrings.alt | python-keyring (<=8),
- python-secretstorage,
- python-keyring,
- python-mock,
- python-msgpack,
- python-pil,
- python-requests,
- python-simplejson,
- python-six (>= 1.8.0~),
- python-tqdm,
- python-wrapt,
- ${misc:Depends},
- ${python:Depends}
-Recommends:
- python-exif,
- python-github,
- python-jsmin,
- python-html5lib,
- python-httpretty,
- python-libxmp,
- python-lzma,
- python-mutagen,
- python-nose,
- python-pyperclip,
- python-requests-ftp,
- python-vcr,
- python-whoosh,
-Suggests:
- python-duecredit,
- python-bs4,
- python-numpy,
-Description: data files management and distribution platform
- DataLad is a data management and distribution platform providing
- access to a wide range of data resources already available online.
- Using git-annex as its backend for data logistics it provides following
- facilities built-in or available through additional extensions
- .
-  - command line and Python interfaces for manipulation of collections of
-datasets (install, uninstall, update, publish, save, etc.) and
-	separate files/directories (add, get)
-  - extract, aggregate, and search through various sources of metadata
-(xmp, EXIF, etc; install datalad-neuroimaging for DICOM, BIDS, NIfTI
-support)
-  - crawl web sites to automatically prepare and update git-annex
-repositories with content from online websites, S3, etc (install
-datalad-crawler)
- .
- This package installs the module for Python 2, and Recommends install
- all dependencies necessary for searching and managing datasets, publishing,
- and testing.  If you need base functionality, install without Recommends.
-
 Package: python3-datalad
 Architecture: all
 Section: python
diff -Nru datalad-0.11.6/debian/patches/python3.patch datalad-0.11.6/debian/patches/python3.patch
--- datalad-0.11.6/debian/patches/python3.patch	1969-12-31 19:00:00.0 -0500
+++ datalad-0.11.6/debian/patches/python3.patch	2019-08-23 17:41:01.0 -0400
@@ -0,0 +1,77 @@
+Description: use python3 interpreter, not python
+ datalad will automatically try to run .py scripts it's been given under
+ 'python' but that is python2 and no longer guaranteed to be available by
+ default.  Dispatch these instead to python3.
+Author: Steve Langasek 
+Last-Modified: 2019-08-17
+
+Index: datalad-0.11.6/datalad/interface/run_procedure.py
+===
+--- 

Processed: datalad: diff for NMU version 0.11.6-1.1 (this is the real upload)

[Debian Bug Tracking System]

Processing control commands:

> tags 935015 + patch
Bug #935015 [src:datalad] datalad: please drop python-datalad (python 2 removal 
effort)
Added tag(s) patch.
> tags 935015 + pending
Bug #935015 [src:datalad] datalad: please drop python-datalad (python 2 removal 
effort)
Added tag(s) pending.

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

Processed: datalad: diff for NMU version 0.11.6-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 935015 + patch
Bug #935015 [src:datalad] datalad: please drop python-datalad (python 2 removal 
effort)
Ignoring request to alter tags of bug #935015 to the same tags previously set
> tags 935015 + pending
Bug #935015 [src:datalad] datalad: please drop python-datalad (python 2 removal 
effort)
Ignoring request to alter tags of bug #935015 to the same tags previously set

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

Bug#935015: datalad: diff for NMU version 0.11.6-1.1 (this is the real upload)

[Sandro Tosi]

Control: tags 935015 + patch
Control: tags 935015 + pending


Dear maintainer,

I've prepared an NMU for datalad (versioned as 0.11.6-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru datalad-0.11.6/debian/changelog datalad-0.11.6/debian/changelog
--- datalad-0.11.6/debian/changelog	2019-07-29 12:07:25.0 -0400
+++ datalad-0.11.6/debian/changelog	2019-08-23 17:58:36.0 -0400
@@ -1,3 +1,11 @@
+datalad (0.11.6-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support and switch to python 3; patches by Steve Langasek;
+Closes: #935015
+
+ -- Sandro Tosi   Fri, 23 Aug 2019 17:58:36 -0400
+
 datalad (0.11.6-1) unstable; urgency=medium
 
   * Fresh upstream release
diff -Nru datalad-0.11.6/debian/control datalad-0.11.6/debian/control
--- datalad-0.11.6/debian/control	2019-07-29 12:07:25.0 -0400
+++ datalad-0.11.6/debian/control	2019-08-23 17:40:59.0 -0400
@@ -11,39 +11,6 @@
  git-annex (>= 6.20180913~) | git-annex-standalone (>= 6.20180913~),
  help2man,
  patool,
- python-all,
- python-appdirs,
- python-argcomplete,
- python-boto,
- python-dateutil,
- python-exif,
- python-fasteners,
- python-iso8601,
- python-jsmin,
- python-git (>= 2.1.6~),
- python-github,
- python-html5lib,
- python-httpretty,
- python-humanize,
- python-keyrings.alt | python-keyring (<=8),
- python-keyring,
- python-secretstorage | python-keyring (<<9.2),
- python-nose (>= 1.3.7-2) | python-libxmp,
- python-lzma,
- python-mock,
- python-msgpack,
- python-mutagen,
- python-nose,
- python-pil,
- python-pyperclip,
- python-requests,
- python-setuptools,
- python-simplejson,
- python-six (>= 1.8.0~),
- python-tqdm,
- python-whoosh,
- python-vcr,
- python-wrapt,
  python3-all,
  python3-appdirs,
  python3-argcomplete,
@@ -89,7 +56,7 @@
  python3-datalad (= ${binary:Version}),
  python3-argcomplete,
  ${misc:Depends},
- ${python:Depends}
+ ${python3:Depends}
 Suggests:
  datalad-containers,
  datalad-crawler,
@@ -113,69 +80,6 @@
  This package provides the command line tools.  Install without
  Recommends if you need only core functionality.
 
-Package: python-datalad
-Architecture: all
-Section: python
-Provides: ${python:Provides}
-Depends:
- git-annex (>= 6.20180913~) | git-annex-standalone (>= 6.20180913~),
- patool,
- python-appdirs,
- python-fasteners,
- python-git (>= 2.1.6~),
- python-humanize,
- python-iso8601,
- python-keyrings.alt | python-keyring (<=8),
- python-secretstorage,
- python-keyring,
- python-mock,
- python-msgpack,
- python-pil,
- python-requests,
- python-simplejson,
- python-six (>= 1.8.0~),
- python-tqdm,
- python-wrapt,
- ${misc:Depends},
- ${python:Depends}
-Recommends:
- python-exif,
- python-github,
- python-jsmin,
- python-html5lib,
- python-httpretty,
- python-libxmp,
- python-lzma,
- python-mutagen,
- python-nose,
- python-pyperclip,
- python-requests-ftp,
- python-vcr,
- python-whoosh,
-Suggests:
- python-duecredit,
- python-bs4,
- python-numpy,
-Description: data files management and distribution platform
- DataLad is a data management and distribution platform providing
- access to a wide range of data resources already available online.
- Using git-annex as its backend for data logistics it provides following
- facilities built-in or available through additional extensions
- .
-  - command line and Python interfaces for manipulation of collections of
-datasets (install, uninstall, update, publish, save, etc.) and
-	separate files/directories (add, get)
-  - extract, aggregate, and search through various sources of metadata
-(xmp, EXIF, etc; install datalad-neuroimaging for DICOM, BIDS, NIfTI
-support)
-  - crawl web sites to automatically prepare and update git-annex
-repositories with content from online websites, S3, etc (install
-datalad-crawler)
- .
- This package installs the module for Python 2, and Recommends install
- all dependencies necessary for searching and managing datasets, publishing,
- and testing.  If you need base functionality, install without Recommends.
-
 Package: python3-datalad
 Architecture: all
 Section: python
diff -Nru datalad-0.11.6/debian/patches/python3.patch datalad-0.11.6/debian/patches/python3.patch
--- datalad-0.11.6/debian/patches/python3.patch	1969-12-31 19:00:00.0 -0500
+++ datalad-0.11.6/debian/patches/python3.patch	2019-08-23 17:41:01.0 -0400
@@ -0,0 +1,77 @@
+Description: use python3 interpreter, not python
+ datalad will automatically try to run .py scripts it's been given under
+ 'python' but that is python2 and no longer guaranteed to be available by
+ default.  Dispatch these instead to python3.
+Author: Steve Langasek 
+Last-Modified: 2019-08-17
+
+Index: datalad-0.11.6/datalad/interface/run_procedure.py
+===
+--- datalad-0.11.6.orig/datalad/interface/run_procedure.py
 datalad-0.11.6/datalad/interface/run_procedure.py
+@@ -189,7 +189,7 

Bug#875054: marked as done ([noblenote] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sat, 24 Aug 2019 00:20:42 +0200
with message-id <20190823222042.GA9356@pisco.westfalen.local>
and subject line Re: [noblenote] Future Qt4 removal from Buster
has caused the Debian Bug report #875054,
regarding [noblenote] 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.)


-- 
875054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: noblenote
Version: 1.0.8-1
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 ---
Version: 1.2.0-1

On Sat, Sep 09, 2017 at 10:12:32PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: noblenote
> Version: 1.0.8-1
> 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:

For some reason it's not listed in the debian/changelog and doesn't have
a Closes: entry, but the 1.2.0-1 upload switched to Qt5.

Cheers,
Moritz--- End Message ---

Bug#875134: [qemuctl] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sun, Sep 10, 2017 at 01:24:39PM +0300, Antti Järvinen wrote:
> Lisandro Damián Nicanor Pérez Meyer writes:
>  > 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.
> 
> Upstream has been contacted with help request ; qemuctl relies on
> application embedding feature and its semantics are fairly different in qt5
> and I could not craft working set of patches myself.

Upstream seems dead, there's no release after 2011 or did you get a reply?

Let's remove it from the archive then.

Cheers,
Moritz

Bug#874867: [fbreader] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

Hi Eugene,

> This is what I plan to do if nobody steps and as new Debian and/or
> upstream maintainer:
> 
> 1. When Qt4 is removed from Debian, libzlui-qt4 (Qt4 back-end for fbreader) 
> will
> go away. Fbreader will remain usable with libzlui-gtk (GTK2 back-end).

The time has come now, please drop the Qt4 backend (or remove the package 
altogether)

Cheers,
Moritz

Bug#874823: [ams] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

Lisandro Damián Nicanor Pérez Meyer wrote:
 Source: ams
> Version: 2.1.1-1.1
> 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.

The current git version on Sourceforge defaults to Qt5.

Cheers,
Moritz

Bug#935556: command-not-found: fails to use it (see below)

[MC2]

Package: command-not-found
Version: 18.04.5-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

It is impossible to run update-command-not-found. When typing a name of package 
not installed, gere's the output :

Could not find the database of available applications, run 
update-command-not-found as root to fix this
Sorry, command-not-found has crashed! Please file a bug report at:
http://www.debian.org/Bugs/Reporting
Please include the following information with the report:

command-not-found version: 0.3
Python version: 3.7.3 final 0
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 10 (buster)
Release:10
Codename:   buster
Exception information:

local variable 'cnf' referenced before assignment
Traceback (most recent call last):
  File "/usr/share/command-not-found/CommandNotFound/util.py", line 23, in 
crash_guard
callback()
  File "/usr/lib/command-not-found", line 93, in main
if not cnf.advise(args[0], options.ignore_installed) and not 
options.no_failure_msg:
UnboundLocalError: local variable 'cnf' referenced before assignment


-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 10 (buster)
Release:10
Codename:   buster
Architecture: armv7l

Kernel: Linux 4.19.66-v7+ (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=ANSI_X3.4-1968) 
(ignored: LC_ALL set to C), LANGUAGE=en_GB.UTF-8 (charmap=ANSI_X3.4-1968) 
(ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages command-not-found depends on:
ii  apt-file 3.2.2
ii  lsb-release  10.2019051400+rpi1
ii  python3  3.7.3-1
ii  python3-apt  1.8.4

command-not-found recommends no packages.

Versions of packages command-not-found suggests:
pn  snapd  

-- no debconf information

Bug#874908: [grantlee] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

El vie., 23 ago. 2019 18:18, Moritz Mühlenhoff  escribió:

> On Sun, Jul 07, 2019 at 11:40:59AM -0300, Lisandro Damián Nicanor Pérez
> Meyer wrote:
> > Hi Moritz!
> >
> > On Fri, 5 Jul 2019 at 15:33, Moritz Mühlenhoff  wrote:
> > >
> > > On Sat, Sep 09, 2017 at 09:05:49PM +0200, Lisandro Damián Nicanor
> Pérez Meyer wrote:
> > > > Source: grantlee
> > > > Version: 0.4.0-4
> > > > Severity: wishlist
> > > > User: debian-qt-...@lists.debian.org
> > > > Usertags: qt4-removal
> > >
> > > The changelog mentions that as of 5.0.0 upstream switched to Qt5.
> >
> > Currently the archive has both versions. The Qt4 one will get removed
> > once it has no rdeps or Qt4 is finally ditched.
>
> With the removal of kdepim4 there are no reverse dependencies left,
> so I've just filed a removal request.
>

Thanks *a lot* for all your help with this!

>

Bug#875057: [mp3diags] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sat, Sep 09, 2017 at 10:12:07PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: mp3diags
> Version: 1.2.03-1
> 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.

Hi Josue,
the current upstream web site is https://github.com/mciobanu/mp3diags/
and release https://github.com/mciobanu/mp3diags/releases/tag/1.5.01
should support Qt5 now:
https://github.com/mciobanu/mp3diags/commit/45db02b4670bb6c10e07d80524dc4c1f54d3678f

Are you planning to upgrade the package (given that the last upload was over 
three
years ago) or shall we remove it from the archive?

Cheers,
Moritz

Bug#874852: [dgedit] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sat, Sep 09, 2017 at 09:03:46PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: dgedit
> Version: 0~git20160401-1
> 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

Per this upstream commit current releases should support Qt5:

-
commit e21e14223b6d87b29221b29488d1b09895912527
Author: Bent Bisballe Nyeng 
Date:   Wed Mar 21 20:46:24 2018 +0100

DGEdit is now officially a Qt5 project.
-

Cheers,
Moritz

Bug#874931: [karlyriceditor] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

Lisandro Damián Nicanor Pérez Meyer wrote:
> Source: karlyriceditor
> 
> 
> 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

Hi Martin,
current upstream releases (after 2.2) should support Qt5. The last upload by you
was in March 2016, if you're no longer interested in karlyriceditor, we can
also remove it.

Cheers,
Moritz

Bug#874908: [grantlee] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sun, Jul 07, 2019 at 11:40:59AM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Hi Moritz!
> 
> On Fri, 5 Jul 2019 at 15:33, Moritz Mühlenhoff  wrote:
> >
> > On Sat, Sep 09, 2017 at 09:05:49PM +0200, Lisandro Damián Nicanor Pérez 
> > Meyer wrote:
> > > Source: grantlee
> > > Version: 0.4.0-4
> > > Severity: wishlist
> > > User: debian-qt-...@lists.debian.org
> > > Usertags: qt4-removal
> >
> > The changelog mentions that as of 5.0.0 upstream switched to Qt5.
> 
> Currently the archive has both versions. The Qt4 one will get removed
> once it has no rdeps or Qt4 is finally ditched.

With the removal of kdepim4 there are no reverse dependencies left,
so I've just filed a removal request.

Cheers,
Moritz

Bug#935552: nomad: FTBFS

[Steve Langasek]

Source: nomad
Version: 0.8.7+dfsg1-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

The nomad package fails to build in Debian unstable (and in Ubuntu devel):

[...]
dh_auto_build -v
build cache is disabled by GOCACHE=off, but required as of Go 1.12
cd _build && go generate -v
can't load package: package .: no Go files in /tmp/nomad-0.8.7+dfsg1/_build
dh_auto_build: cd _build && go generate -v returned exit code 1
make[1]: *** [debian/rules:37: override_dh_auto_build] Error 255
[...]

It appears that removing the 'GOCACHE=off' line from debian/rules is
sufficient to fix this failure.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#830726: xtrlock: CVE-2016-10894: xtrlock does not block multitouch events

[Antoine Amarilli]

Hi Chris,

On Thu, Aug 22, 2019 at 11:12:52AM -0700, Chris Lamb wrote:
> > > Whilst I've fixed that bit at least, the new attached patch doesn't
> > > grab devices that are renabled via "xinput enable" although we do
> > > successfully detect that "edge" event now.
> > 
> > Cool! I'm not sure whether this other edge case is important -- are
> > there situations where an attacker in front of a locked computer could
> > manage to pull this off?
> 
> An attacker being able to run xinput? No we should not care about that
> but I was _only_ using that to *emulate* your example of plugging in a
> USB multitouch device, not caring about that particular vector per se.

OK makes sense.

> Unfortunately, it turns out my touchpad is a PCI device and I can't
> thus follow the exact same testcase as you (ie. via the "authorized")
> file. Not only that when I try and emulate it using "rmmod i2c_hid &&
> sleep 5 && modprobe i2c_hid" I cannot reproduce that the device is not
> regrabbed.
> 
> I wonder; could you try the patch I attached previously and see
> whether that actually works for USB devices?

OK, so I tried the patch. Initially, I got an X bad value error, but it
can apparently be fixed by initializing xi_major and xi_minor to 2. This
was done in your previous patch, is required according to man
XIQueryVersion, and appears to fix the issue.

The new patch is slightly better than the older one in that it would
seem to re-grab devices when they appear after xtrlock has been run.
This is the case both when making them disappear and reappear with
/sys/bus/usb/devices/*/authorized, and when doing the same with xinput
enable/disable. Playing with the devices after they have appeared no
longer moves the mouse pointer, whereas it did with the first patch that
you proposed.

In the case of xinput (but not the authorized file), when one plays with
the touchscreen *while* "xinput enable" runs, then I got the mouse
pointer to move to the location I was pressing on the touchscreen,
suggesting the possibility of a timing attack. In the case of the
authorized file (or when not doing either of these two things), the
mouse pointer never moves when the touchscreen is interacted with.

However, but there's still a more serious problem, which is also pretty
weird. If I do:

 (sleep 10 ; xinput 9 disable; sleep 10 ; xinput 9 enable)&
 xtrlock

Then:

- For the 10 first seconds, playing with the touchscreen does nothing
  (because it is correctly grabbed)

- For the next 10 seconds, playing with the touchscreen does nothing
  (because it is disabled)

- Then, the touchscreen seems to be "grabbed" in the sense that playing
  with the touchscreen no longer moves the mouse pointer. (Again, this
  was not true with the first version of the patch, so there's an
  improvement now.) However, the touchscreen is not "correctly" grabbed
  because I can still work around the grab using multiple fingers (i.e.,
  press somewhere, then interact with chromium). This is exactly like
  the bug I reported in the original xtrlock, with the only difference
  that the mouse pointer does not move while I do it.

So the regrab doesn't actually solve things. What is even weirder is
that this problem with the screen not being "correctly" grabbed will
persist on future xtrlock runs: if I close xtrlock by typing the correct
password, and run xtrlock again (without messing around with xinput this
time), then the touchscreen will again not be "correctly" grabbed:
playing with it does not move the mouse pointer, but I can still work
around the grab using multiple fingers. I can exit/restart xtrlock
multiple times and the problem persists.

The problem is only solved when I do an "xinput disable" and "xinput
enable" of the input while xtrlock is *not* running. Then, if I run
xtrlock afterwards, then the output is correctly grabbed and I cannot
work around it.

I'm sorry that this a bit complicated to describe... I'm not familiar at
all with what's going on, but it is as if, when the input appears while
xtrlock is running, then its attempt to grab it not only fails to work
properly (though it still prevents the mouse pointer from moving), but
also put the input in a weird state that will also make further grabs
fail to work properly, until running xinput enable/disable outside of
xtrlock puts it back in a sane state.

[The exact same behavior seems to occur if I replace xinput
enable/disable with the corresponding play with the authorized file.]

Can you reproduce this pretty weird behavior? Does it make any sense to
you?

On Thu, Aug 22, 2019 at 11:39:47PM +0100, Matthew Vernon wrote:
> I think we may be in danger of Trying Too Hard here - xtrlock and similar
> are already vulnerable to some attacks (e.g. Ctrl-Alt-F1 could get you to do
> tty which might have a login session on).

I agree we shouldn't try excessively hard, but what you describe here
isn't really an xtrlock vulnerability: xtrlock is about locking the X
display, not TTYs. Security-conscious users 

Bug#935548: libxml-security-java: CVE-2019-12400

[Salvatore Bonaccorso]

Source: libxml-security-java
Version: 2.0.10-2
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for libxml-security-java.

CVE-2019-12400[0]:
|Apache Santuario potentially loads XML parsing code from an
|untrusted source

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-12400
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12400
[1] http://santuario.apache.org/secadv.data/CVE-2019-12400.asc

Regards,
Salvatore

Processed: Re: Bug#916195: python3-qwt: make optional the python3-pyqt4 dependency

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #916195 [python3-qwt] python3-qwt: make optional the python3-pyqt4 
dependency
Severity set to 'serious' from 'important'

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

Processed: Blocking 876905 by 935547

[Debian Bug Tracking System]

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

> block 876905 by 935547
Bug #876905 [src:qtwebkit] qtwebkit should not be released with buster
876905 was blocked by: 784479
876905 was not blocking any bugs.
Added blocking bug(s) of 876905: 935547
> thanks
Stopping processing here.

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

Bug#935547: python-ghost: Qt4 WebKit removal

[Dmitry Shachnev]

On Fri, Aug 23, 2019 at 10:58:54PM +0300, Dmitry Shachnev wrote:
> Upstream has ported the package to Qt5 and PySide2 [2]. Unfortunately,
> in Debian the PySide2 package is built without WebKit support. If you are
> interested, we can fix this. Also you can try to use PyQt5 which has
> mostly compatible API and is built without WebKit support.

This should have been “... and is built *with* WebKit support”. Sorry.

https://packages.debian.org/sid/python3-pyqt5.qtwebkit

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#932299: closed by Vincent Danjean (Bug#932299: fixed in owfs 3.2p3+dfsg1-3)

[Vincent Danjean]

  Hi,

Le 05/08/2019 à 14:06, Bernhard Schmidt a écrit :
> On Thu, Jul 25, 2019 at 10:54:04AM +, Debian Bug Tracking System wrote:
> 
> Hi Vincent,
> 
>> This is an automatic notification regarding your Bug report
>> which was filed against the src:owfs package:
>>
>> #932299: owfs: FTBFS: relocation R_X86_64_32 against symbol `_Py_NoneStruct' 
>> can not be used
>>
>> It has been closed by Vincent Danjean .
> 
> It won't migrate to testing because it was not a source-only upload. See 
> 
> https://lists.debian.org/debian-release/2019/07/msg00053.html 
> 
> second paragraph.
> 
> Could you perform a source-only upload?

  Many thanks for the advise. I was on holidays for 3 weeks, so I just
saw your message. A source-only upload is on the way.

  Regards,
Vincent

> Thanks,
> Bernhard
> 


-- 
Vincent Danjean   GPG key ID 0xD17897FA vdanj...@debian.org
GPG key fingerprint: 621E 3509 654D D77C 43F5  CA4A F6AE F2AF D178 97FA
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo:  deb http://people.debian.org/~vdanjean/debian unstable main

Bug#935547: python-ghost: Qt4 WebKit removal

[Dmitry Shachnev]

Source: python-ghost
Version: 0.2.3-2
Severity: serious
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal qt4-removal

Dear Maintainer,

As announced four years ago [1], we want to remove Qt 4.x WebKit from
archive. Unfortunately we failed to remove it from Stretch or from Buster,
but now time has come and it will not be part of Bullseye.

Your package relies on Qt 4.x WebKit and uses it via pyside. Pyside is
scheduled for autoremoval from testing and your package will be removed
transitively.

However, I am asking you to also get rid of Qt 4.x WebKit dependency in sid,
or request the removal of this package.

Upstream has ported the package to Qt5 and PySide2 [2]. Unfortunately,
in Debian the PySide2 package is built without WebKit support. If you are
interested, we can fix this. Also you can try to use PyQt5 which has
mostly compatible API and is built without WebKit support.

[1]: https://lists.debian.org/debian-devel-announce/2015/05/msg1.html
[2]: https://github.com/jeanphix/Ghost.py/commit/12edc074b529141c

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#875238: marked as done ([vmpk] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Fri, 23 Aug 2019 19:51:59 +
with message-id 
and subject line Bug#875238: fixed in vmpk 0.7.1-1
has caused the Debian Bug report #875238,
regarding [vmpk] 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.)


-- 
875238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vmpk
Version: 0.4.0-3
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: vmpk
Source-Version: 0.7.1-1

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated vmpk 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 Aug 2019 21:34:23 +0200
Source: vmpk
Architecture: source
Version: 0.7.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Closes: 758046 797535 870355 875238
Changes:
 vmpk (0.7.1-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ross Gammon ]
   * New upstream release
   * New maintainer (Closes: #797535)
   * Embedded copy of RiMidi no longer included (Closes: #758046)
   * Update to QT5 dependencies (Closes: #870355, #875238)
   * Unapply patches from source
   * Build depend on latest libdrumstick for new RT library
   * Add myself as uploaders
   * Use latest secure & canonical Vcs URIs
   * Drop old build options & add bindnow hardening option
   * Update copyrights & move to copyright format 1.0
   * Switch to Debian Multimedia Team maintenance
 .
   [ Sebastian Ramacher ]
   * debian/control:
 - Bump debhelper compat to 12.
 - Set Priority to optional.
 - Bump Standards-Version.
   * debian/rules: Force cmake build system.
Checksums-Sha1:
 6de7bb21b7b5c58ba1499ef660483f72c4ce840c 2061 vmpk_0.7.1-1.dsc
 1e4dcd3a6258351dcd6c0a25a9223c03278ae22e 623509 vmpk_0.7.1.orig.tar.gz
 6f35371a96ad9ad62c0c344c415568f463d27325 3556 vmpk_0.7.1-1.debian.tar.xz
Checksums-Sha256:
 2a6f7453c68778937e3558ff11e42cfafa633ba601ec2a161c14a33233c5d8e8 2061 
vmpk_0.7.1-1.dsc
 4afe1ad486c7463df95f5697dfb3551cfbbda22c8b89561832f37011101af2a6 623509 

Bug#935453: libconfig-model-tkui-perl breaks libconfig-model-itself-perl autopkgtest

[gregor herrmann]

On Fri, 23 Aug 2019 18:56:36 +0200, Dominique Dumont wrote:

> ok 3 - Read all models from wr_root/load_write_itself/lib/Config/Model/models
> Configuration item 'application:fstab model' has a wrong value:
>   reference type does not know 'Fstab'. Expected 'Itself::Application' or 
> 'Itself::CargoElement' or 'Itself::Class' or 'Itself::CommonElement' or 
> 'Itself::CommonElement::Assert' or 'Itself::CommonElement::WarnIfMatch' or 
> 'Itself::ComputedValue' or 'Itself::ConfigAccept' or 
> 'Itself::ConfigReadWrite' 
> or 'Itself::ConfigReadWrite::DefaultLayer' or 'Itself::Element' or 
> 'Itself::MigratedValue' or 'Itself::Model' or 'Itself::NonWarpableElement' or 
> 'Itself::WarpOnlyElement' or 'Itself::WarpValue' or 
> 'Itself::WarpableCargoElement' or 'Itself::WarpableElement'
> # Tests were run but no plan was declared and done_testing() was not seen.
> # Looks like your test exited with 2 just after 3.
> Dubious, test returned 2 (wstat 512, 0x200)
> 
> This looks like cme is able to find the file /usr/share/perl5/Config/Model/
> system.d/fstab , but is not able to load /usr/share/perl5/Config/Model/models/
> Fstab.pl. Even though both files are provided by libconfig-model-perl. 
> 
> Given that I cannot reproduce this issue on my system, I guess that the setup 
> of perl library in autopkgtest is different than the default setup.  I need 
> to 
> check how these files are found.

In can reproduce it in my autopkgtest setup.

I'm not really sure what exactly happens, but what makes the
difference is the existence of blib/ (i.e. running perl Build.PL;
./Build before the tests).

Background: the smoke test in autopkgtests-pkg-perl copies (by
default only t/, in our case, because of
debian/tests/pkg-perl/smoke-files) t/ and data/ to an empty temporary
directory and runs prove there.

But the empty directory is not even necessary. In the source tree (in
my case in an schroot chroot after the failed autopkgtest but that
shouldn't matter):
- `prove --verbose t/load_write_itself.t' fails with the error above

- perl Build.PL ; ./Build
- and now `prove --verbose t/load_write_itself.t' succeeds

- ./Build realclean; perl Build.PL
- prove fails

- ./Build
- prove succeeds

- ./Build realclean ; perl Build.PL ; ./Build ; rm -r blib
- prove fails


Somewhere in the tests, they look into blib/ and fail otherwise …


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Bettina Wegner: Ach, wenn ich doch als Mann auf diese Welt gekommen 
wär


signature.asc
Description: Digital Signature

Processed:

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #921694 [src:mdk4] mdk4: FTBFS randomly when built in parallel (undefined 
reference to `getFrequencyFromChannel')
Severity set to 'normal' from 'serious'

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

Bug#921694:

[Samuel Henrique]

Control: severity -1 normal

Lowering the severity back to normal now as it's safe to migrate to Testing
now, I forwarded this to upstream but could not reproduce on my machine.

I think this may be some isolated case, anyway we have until the bullseye
to confirm that and mdk4 will probably change a lot meanwhile.

-- 
Samuel Henrique 

Bug#932668: marked as done (python-shodan: Don't depend on python-click-plugins)

[Debian Bug Tracking System]

Your message dated Fri, 23 Aug 2019 18:34:58 +
with message-id 
and subject line Bug#932668: fixed in python-shodan 1.15.0-2
has caused the Debian Bug report #932668,
regarding python-shodan: Don't depend on python-click-plugins
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.)


-- 
932668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-shodan
Version: 1.11.1-1
Severity: important
User: debian-...@lists.debian.org
Usertags: python-click-plugins

Dear Maintainer,

The python-click-plugins package is going to be removed due to the
Python 2 EOL.

Your package should stop (build) depending on python-click-plugins.

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: python-shodan
Source-Version: 1.15.0-2

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

Debian distribution maintenance software
pp.
Samuel Henrique  (supplier of updated python-shodan 
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 Aug 2019 19:04:39 +0100
Source: python-shodan
Binary: python-shodan-doc python3-shodan
Architecture: source all
Version: 1.15.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 
Changed-By: Samuel Henrique 
Description:
 python-shodan-doc - Official Python library for Shodan (common documentation)
 python3-shodan - Official Python library for Shodan (Python 3)
Closes: 932668
Changes:
 python-shodan (1.15.0-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat.
 .
   [ Samuel Henrique ]
   * Drop python2 package (closes: #932668)
   * d/python-shodan-doc.doc-base: fix path of index.html
Checksums-Sha1:
 87e6e604fc61dca3ac725947ebeb0c4d4c45e0c1 2191 python-shodan_1.15.0-2.dsc
 78e47e7df7de945489acedeb3d37de502bb20186 3572 
python-shodan_1.15.0-2.debian.tar.xz
 9b0152a0daf9f4753b84a5c6dd9ce07cdc667c70 41396 
python-shodan-doc_1.15.0-2_all.deb
 cc3424ee6b43d78ce6ab2bb25f5e76ea1ed1bed6 7834 
python-shodan_1.15.0-2_amd64.buildinfo
 bb31f5ea68a0c44bfbe7dbf95d20e9912db61b96 33732 python3-shodan_1.15.0-2_all.deb
Checksums-Sha256:
 c980bf6d30dd7efdbe6a10628ca5c1df07a361cb3925c80b62f880d311c9b8a2 2191 
python-shodan_1.15.0-2.dsc
 d8665d74d32a71da1e0728d44c72827c5f5ccafec1598e4ace2b7193b05126cc 3572 
python-shodan_1.15.0-2.debian.tar.xz
 aadb90d346422d1e5c07a075e780a732bb2731f6c962a9680ae96b15b3e21fe1 41396 
python-shodan-doc_1.15.0-2_all.deb
 04db7868b53da001e534471f41c4c229f55fe8965d61bb2d578e11352114930f 7834 
python-shodan_1.15.0-2_amd64.buildinfo
 3a8726e4c888fe1f77aeaa8551bfe80d1b334bf7553f34afc0d87e0a92d124d4 33732 
python3-shodan_1.15.0-2_all.deb
Files:
 9b2afac74b96231b4f12dd2d640bf8b2 2191 python optional 
python-shodan_1.15.0-2.dsc
 8f3160401de3fa28ede0ccf5288fdcf5 3572 python optional 
python-shodan_1.15.0-2.debian.tar.xz
 dcc004dcfce1cb3596b915e2b7070278 41396 doc optional 
python-shodan-doc_1.15.0-2_all.deb
 c9f6e0d1a5257685e86d313ddf6bbb61 7834 python optional 
python-shodan_1.15.0-2_amd64.buildinfo
 d93d0670b3298b9ac4f0f2a5f754c17d 33732 python optional 
python3-shodan_1.15.0-2_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEBdtqg34QX0sdAsVfu6n6rcz7RwcFAl1gLn4ACgkQu6n6rcz7
RwdbJA/+MKxTzIJJb6GSOz2mkVbAjjT4KksHtQqsMa823+RB9ZDX2JmeTTbNavgD
1OT+INj83UbzUI6RamtQ8YpqRThPHIKj3Wds6vSLIbPuuH+EFAuQChdIIaVw7N4x
2KBNTX+5G8Uv3ZLxrWLDoYVPIlZ0mtU2UJWOK+zIuiMxjMrrY2WbTKktiOR/0ACY
zT62WaRb645Ncjrg74/07xnbX7Kiw+VbIL+6+3a0ffgs3BU0hySYoaUK9hj2Vkcg
v3zbYL5sf8gd4BPFGadGLMIpKb9f0L+ygXjsHRpD1lDnwwylgz7B2zwJLHAb6ZOo
KSpY7QTYZjSRfLJi+ltPjDdijEmAxWCS6Tqu1dWWAf0LzHiK2UmYupmdwFHABKDG
qf+gM3fs4fteWSwZ7ozdII3Lo2W3PKzjg48cXTOeFHY+Qep9aAz0aiPxS+7cuo0u
SrmdWs4HiNjh4Nzyc+NuUv4i6HobFZKpPB2hxPla+o4tXeJO6yJP86Qd9xwsm+xo
VjHBa7EMdZyyZpNgyEOx26kfodBOXA4fii6EzR6mFd7ZdP/nLaDom9lud9TQG2eq
m7Jq3rwfRiUCfcPtAAb/5Sf9/G73zwz+5F7HIlB3yJQYEYNI4dqOEHpb63n7v4Hd
uzD7ZyeSQi6zH4Ntp/kyU6S9BiclnvN0NzVSKFEWKhLqxAVfcb4=
=c2mO
-END PGP SIGNATURE End Message ---

Processed: tagging 914441 ...

[Debian Bug Tracking System]

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

> tags 914441 + patch
Bug #914441 [kamoso] kamoso: no user interface is shown: qrc:/qml/Main.qml:7 
module "org.kde.kirigami" is not installed
Added tag(s) patch.
> forwarded 914441 
> https://salsa.debian.org/qt-kde-team/kde/kamoso/merge_requests/1
Bug #914441 [kamoso] kamoso: no user interface is shown: qrc:/qml/Main.qml:7 
module "org.kde.kirigami" is not installed
Set Bug forwarded-to-address to 
'https://salsa.debian.org/qt-kde-team/kde/kamoso/merge_requests/1'.
> thanks
Stopping processing here.

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

Processed: unarchiving 866980, reopening 866980

[Debian Bug Tracking System]

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

> unarchive 866980
Bug #866980 {Done: Debian FTP Masters } 
[biomaj-watcher] biomaj-watcher: fails to upgrade from 'jessie': Exception in 
thread "main" java.lang.UnsupportedClassVersionError: WatcherConfigurator : 
Unsupported major.minor version 52.0
Unarchived Bug 866980
> reopen 866980
Bug #866980 {Done: Debian FTP Masters } 
[biomaj-watcher] biomaj-watcher: fails to upgrade from 'jessie': Exception in 
thread "main" java.lang.UnsupportedClassVersionError: WatcherConfigurator : 
Unsupported major.minor version 52.0
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.2.2-6+rm.
> thanks
Stopping processing here.

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

Bug#935453: libconfig-model-tkui-perl breaks libconfig-model-itself-perl autopkgtest

[Dominique Dumont]

On jeudi 22 août 2019 20:31:52 CEST you wrote:
> Can you please investigate the situation and reassign the
> bug to the right package?

Sure.

The change done in libconfig-model-tkui-perl 1.370 did break libconfig-model-
itself-perl 2.016 (the API change are backward compatible, the class 
inheritance, less so :-( )

I've released libconfig-model-itself-perl 2.018 with a change that fixes the 
tests with libconfig-model-tkui-perl 1.370 (but probably break with 1.369).

The log from auotpkgtest [1] in  the setup that should work shows this error:

ok 3 - Read all models from wr_root/load_write_itself/lib/Config/Model/models
Configuration item 'application:fstab model' has a wrong value:
reference type does not know 'Fstab'. Expected 'Itself::Application' or 
'Itself::CargoElement' or 'Itself::Class' or 'Itself::CommonElement' or 
'Itself::CommonElement::Assert' or 'Itself::CommonElement::WarnIfMatch' or 
'Itself::ComputedValue' or 'Itself::ConfigAccept' or 'Itself::ConfigReadWrite' 
or 'Itself::ConfigReadWrite::DefaultLayer' or 'Itself::Element' or 
'Itself::MigratedValue' or 'Itself::Model' or 'Itself::NonWarpableElement' or 
'Itself::WarpOnlyElement' or 'Itself::WarpValue' or 
'Itself::WarpableCargoElement' or 'Itself::WarpableElement'
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 2 just after 3.
Dubious, test returned 2 (wstat 512, 0x200)

This looks like cme is able to find the file /usr/share/perl5/Config/Model/
system.d/fstab , but is not able to load /usr/share/perl5/Config/Model/models/
Fstab.pl. Even though both files are provided by libconfig-model-perl. 

Given that I cannot reproduce this issue on my system, I guess that the setup 
of perl library in autopkgtest is different than the default setup.  I need to 
check how these files are found.

In any case the root cause for the failure of libconfig-model-itself-perl 2.018 
with libconfig-model-tkui-perl 1.370  is not the regression brought by 
libconfig-model-tkui-perl 1.370


All the best

[1] 
https://ci.debian.net/data/autopkgtest/unstable/amd64/libc/libconfig-model-itself-perl/2796602/log.gz
> 
> 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=libconfig-model-tkui-perl
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/libc/libconfig-model-it
> self-perl/2794069/log.gz
> 
> not ok 3 - edit is in test mode
> #   Failed test 'edit is in test mode'
> #   at t/cme-meta-edit.t line 34.
> #   'Reading model from /usr/share/perl5/Config/Model
> # '
> # doesn't match '(?^:Test mode: quit)'
> 1..3
> # Looks like you failed 1 test of 3.
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/3 subtests
> t/cme-meta-plugin.t 
> Prototype mismatch: sub CORE::GLOBAL::exit: none vs (;$) at
> /usr/lib/x86_64-linux-gnu/perl5/5.28/Tk.pm line 415.
> ok 1 - compiled
> not ok 2 - threw no exceptions
> #   Failed test 'threw no exceptions'
> #   at t/cme-meta-plugin.t line 52.
> #  got: 'Can't call method "fetch_element" on an undefined value
> at /usr/share/perl5/Config/Model/Itself/TkEditUI.pm line 80.
> #  at /usr/lib/x86_64-linux-gnu/perl5/5.28/Tk/Widget.pm line 203.
> # '
> # expected: undef
> ok 3 - edit plugin and quit
> not ok 4 - edit plugin is in test mode
> #   Failed test 'edit plugin is in test mode'
> #   at t/cme-meta-plugin.t line 57.
> #   'Preparing plugin my-plugin for model Fstab found in
> /usr/share/perl5/Config/Model
> # Use -dev option to create a plugin for a local model (i.e. in
> wr_test/plugin-ui)
> # '
> # doesn't match '(?^:Test mode: save and quit)'
> not ok 5 - check content of
> wr_test/plugin-ui/models/Fstab.d/my-plugin/Fstab/CommonOptions.pl
> #   Failed test 'check content of
> wr_test/plugin-ui/models/Fstab.d/my-plugin/Fstab/CommonOptions.pl'
> #   at t/cme-meta-plugin.t line 59.
> # Could not open file
> wr_test/plugin-ui/models/Fstab.d/my-plugin/Fstab/CommonOptions.pl: No
> such file or directory
> 1..5
> # Looks like you failed 3 tests of 5.
> 
> [...]
> 
> Test Summary Report
> ---
> t/cme-meta-edit.t(Wstat: 256 Tests: 3 Failed: 1)
>   Failed test:  3
>   Non-zero exit status: 1
> t/cme-meta-plugin.t  (Wstat: 768 Tests: 5 Failed: 3)
>   Failed tests:  2, 4-5
>   Non-zero exit status: 3
> t/itself-editor.t(Wstat: 6400 Tests: 6 Failed: 0)
>   Non-zero exit status: 25
>   Parse errors: No plan found in TAP output
> Files=11, Tests=85, 162 wallclock secs ( 0.07 usr  0.02 sys + 158.99
> cusr  2.99 csys = 162.07 CPU)
> Result: FAIL
> autopkgtest [17:14:40]: test autodep8-perl-build-deps:
> ---]


-- 

Bug#935269: marked as done (trilinos: FTBFS on mips64el)

[Debian Bug Tracking System]

Your message dated Fri, 23 Aug 2019 16:08:06 +
with message-id 
and subject line Bug#935269: fixed in trilinos 12.12.1-8
has caused the Debian Bug report #935269,
regarding trilinos: FTBFS on mips64el
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.)


-- 
935269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:trilinos
version: 12.12.1-7
severity: serious
tags: ftbfs

Hi,

The latest version of trilinos in unstable fails on mips64el:

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

After 2 failed attempts on the buildd, a maintainer build was uploaded.
Packages need to build on buildds. If it doesn't build on mips64el, the binary
should be removed there (and in that case the build should probably be
disabled on mips64el because it takes a very long time).

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: trilinos
Source-Version: 12.12.1-8

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated trilinos 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 Aug 2019 14:24:44 +
Source: trilinos
Architecture: source
Version: 12.12.1-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Graham Inggs 
Closes: 835406 848770 868523 881873 935269
Changes:
 trilinos (12.12.1-8) unstable; urgency=medium
 .
   * Switch to debhelper 12
   * Set Rules-Requires-Root: no
   * Update debian/watch
   * Restrict build architectures to those that are successful
 (Closes: #835406, #881873, #935269)
   * Fix Phalanx tests with GCC 7.2 and re-enable them (Closes: #868523)
   * Re-enable Isorropia, ShyLUCore and Teko tests (Closes: #848770)
   * Bump Standards-Version to 4.4.0, no changes
Checksums-Sha1:
 b9c81cb16d1c7b14d10089a2fd11ba83cb20ee75 11805 trilinos_12.12.1-8.dsc
 d7d474c99c598db1ff9ebeaaf09e288cc0292eb5 19884 trilinos_12.12.1-8.debian.tar.xz
Checksums-Sha256:
 b620e77a206cffade486c64870dd4a92e21f0232cc47ce03f28913a5a6cd8d5c 11805 
trilinos_12.12.1-8.dsc
 61a183c168ce0819e5c37b5c503bff47510cd08fc998d480666a8f0e62f3a078 19884 
trilinos_12.12.1-8.debian.tar.xz
Files:
 f07a8dffa6fb750ac601b0a547eca7ae 11805 science optional trilinos_12.12.1-8.dsc
 3921fcfdb3cf716bac9465c7cb834e3b 19884 science optional 
trilinos_12.12.1-8.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl1f/e8ACgkQr8/sjmac
4cLY6hAAxS9GPryEAfK4EkyOXMs9V/pecCUBgtCZPFwTuWmsIgIoHx8GhUh75x+v
jZBzjeXr01vJxbZdzOMB7+TdomLfJ5okF9dbJMzG43ryLhSAdaMTYGo7O4/monYk
lzwzicSrxerbO03R6V8+TvgyvRUprqMQFhYUWHCScuyE9EmNULJaOvcPlntRjM7q
ZdhR2REFhK8iZcEkOcVNK6zPW8HTnw2m70sll88LUWGc5yEbHpu6WD/5AVHQwueX
FQV16adQwDUrMDsObv6fiFgR2iRKsMgTZAZgxCLwy18B2yZ2c+KjaLvmRsFvNF1k
452qogCq1GWajOnDdXPfEJr+g9qZ+W7azTCxP2a92pDatYmxcMyn4JBacyB0uQdY
+9OUdYstHUkM20C8Tyj+15KrHL7XhvtELZ+yGFKC3yD35bfy2mhLH5SjbZIILD5l
RsFQPXHkagG3lz3z3Urr758rK7zZitAe5/i3WcjhedlHfnAJvhZs67j+FVAaufPp
QzNU7icVLueOlt9OZrEMLPVVXBfzk7fdV9RRBF7yiX6bB47LDeAK4/sIweE5sH4e
q96nBLiU581ZMXBcsN7JhB5ej/mY2KFYovlsu4cF6gT19DwxKS2RUWOaeDCg06hV
KBPDpTA0mukW4z9MeUNzk+RtiQ0FMNPcFzHJfcafFqbucz7Ft6g=
=t433
-END PGP SIGNATURE End Message ---

Processed: bug 925689 is forwarded to https://github.com/hsnr-gamera/gamera/issues/25

[Debian Bug Tracking System]

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

> forwarded 925689 https://github.com/hsnr-gamera/gamera/issues/25
Bug #925689 [src:gamera] gamera: ftbfs with GCC-9
Set Bug forwarded-to-address to 
'https://github.com/hsnr-gamera/gamera/issues/25'.
> thanks
Stopping processing here.

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

Processed: severity of 935490 is important

[Debian Bug Tracking System]

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

> severity 935490 important
Bug #935490 [debian-installer] debian-installer: Mouse and keyboard freezes at 
first screen, choose language
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#934905: libaqbanking35: libaqbanking not ready for PSD2, will not work after 14 September 2019

[Matthias Merz]

Dear Micha,

I tried for myself yesterday. I built upstream tarball 5.8.1 using your
libaqbanking_5.7.8-3.debian.tar.xz. I needed the following changes in
exported symbols to successfully build a debian package:


cat diff_libaqbanking35.symbols
83,84d82
<  AB_AccountType_fromChar@Base 5.8.1
<  AB_AccountType_toChar@Base 5.8.1
485,488d482
<  AB_Banking_RuntimeConfig_GetCharValue@Base 5.8.1
<  AB_Banking_RuntimeConfig_GetIntValue@Base 5.8.1
<  AB_Banking_RuntimeConfig_SetCharValue@Base 5.8.1
<  AB_Banking_RuntimeConfig_SetIntValue@Base 5.8.1
1499a1494
> #MISSING: 5.5.1# AB_Transaction_GetCreditorIdentifier@Base 4.2.3+svn.r1797
1522a1518
> #MISSING: 5.5.1# AB_Transaction_GetMandateReference@Base 4.2.3+svn.r1797
1621a1618
> #MISSING: 5.5.1# AB_Transaction_SetCreditorIdentifier@Base 4.2.3+svn.r1797
1644a1642
> #MISSING: 5.5.1# AB_Transaction_SetMandateReference@Base 4.2.3+svn.r1797


But I can't tell whether this may pose problems with debian policy to
remove symbols from a package? As far as I understand the gnucash git
commit100ef2a01d, version 5.7.9 should also contain the necessary code
to pass the registration information. - online browseable at
https://github.com/Gnucash/gnucash/commit/100ef2a01decda3ed54cf7204ae38bfd8766521d


Unfortunately, gnucash even in unstable (and any released version AFAIK)
does not yet contain the necessary registration code. But I was able to
get rid of the HBCI warnings when building a debian package from the git
maint branch against libaqbanking 5.8.1. See gnucash bugreport #935503 -
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935503

Maybe his can help to create a stable-backport, o even stable-updates
package?


Yours
Matthias Merz

-- 
Ovfg QH arhtvrevt. :)


smime.p7s
Description: S/MIME cryptographic signature

Bug#925780: marked as done (monero: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Fri, 23 Aug 2019 10:39:10 +
with message-id 
and subject line Bug#925780: fixed in monero 0.14.1.2-1
has caused the Debian Bug report #925780,
regarding monero: ftbfs with GCC-9
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.)


-- 
925780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:monero
Version: 0.13.0.4-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/monero_0.13.0.4-2_unstable_gcc9.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
make[2]: *** [CMakeFiles/Makefile2:3374: 
src/device/CMakeFiles/obj_device.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs
[ 19%] Building CXX object 
src/cryptonote_basic/CMakeFiles/obj_cryptonote_basic.dir/difficulty.cpp.o
cd /<>/obj-x86_64-linux-gnu/src/cryptonote_basic && /usr/bin/c++  
-DAUTO_INITIALIZE_EASYLOGGINGPP -DBLOCKCHAIN_DB=DB_LMDB 
-DDEFAULT_DB_TYPE=\"lmdb\" -DHAVE_EXPLICIT_BZERO -DHAVE_HIDAPI -DHAVE_READLINE 
-DHAVE_STRPTIME -DPER_BLOCK_CHECKPOINT 
-I/<>/external/rapidjson/include 
-I/<>/external/easylogging++ -I/<>/src 
-I/<>/contrib/epee/include -I/<>/external 
-I/<>/obj-x86_64-linux-gnu/translations 
-I/<>/external/db_drivers/liblmdb -I/usr/include/hidapi  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DNO_AES  
-fno-strict-aliasing -std=c++11 -D_GNU_SOURCE   -Wall -Wextra -Wpointer-arith 
-Wundef -Wvla -Wwrite-strings -Wno-error=extra 
-Wno-error=deprecated-declarations -Wno-unused-parameter -Wno-unused-variable 
-Wno-error=unused-variable -Wno-error=undef -Wno-error=uninitialized 
-Wlogical-op -Wno-error=ma
 ybe-uninitialized -Wno-error=cpp -Wno-reorder -Wno-missing-field-initializers  
-fPIC  -Wformat -Wformat-security -fstack-protector -fstack-protector-strong 
-fcf-protection=full -fstack-clash-protection -mmitigate-rop 
-fno-strict-aliasing   -Werror -o 
CMakeFiles/obj_cryptonote_basic.dir/difficulty.cpp.o -c 
/<>/src/cryptonote_basic/difficulty.cpp
c++: warning: switch '-mmitigate-rop' is no longer supported
[ 19%] Building CXX object 
src/cryptonote_basic/CMakeFiles/obj_cryptonote_basic.dir/hardfork.cpp.o
cd /<>/obj-x86_64-linux-gnu/src/cryptonote_basic && /usr/bin/c++  
-DAUTO_INITIALIZE_EASYLOGGINGPP -DBLOCKCHAIN_DB=DB_LMDB 
-DDEFAULT_DB_TYPE=\"lmdb\" -DHAVE_EXPLICIT_BZERO -DHAVE_HIDAPI -DHAVE_READLINE 
-DHAVE_STRPTIME -DPER_BLOCK_CHECKPOINT 
-I/<>/external/rapidjson/include 
-I/<>/external/easylogging++ -I/<>/src 
-I/<>/contrib/epee/include -I/<>/external 
-I/<>/obj-x86_64-linux-gnu/translations 
-I/<>/external/db_drivers/liblmdb -I/usr/include/hidapi  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DNO_AES  
-fno-strict-aliasing -std=c++11 -D_GNU_SOURCE   -Wall -Wextra -Wpointer-arith 
-Wundef -Wvla -Wwrite-strings -Wno-error=extra 
-Wno-error=deprecated-declarations -Wno-unused-parameter -Wno-unused-variable 
-Wno-error=unused-variable -Wno-error=undef -Wno-error=uninitialized 
-Wlogical-op -Wno-error=ma
 ybe-uninitialized -Wno-error=cpp -Wno-reorder -Wno-missing-field-initializers  
-fPIC  -Wformat -Wformat-security -fstack-protector -fstack-protector-strong 

Bug#910455: marked as done (bitcoin FTBFS on 32bit: test failure)

[Debian Bug Tracking System]

Your message dated Fri, 23 Aug 2019 10:35:09 +
with message-id 
and subject line Bug#910455: fixed in bitcoin 0.18.1~dfsg-1
has caused the Debian Bug report #910455,
regarding bitcoin FTBFS on 32bit: test failure
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.)


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

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

...
make[5]: Leaving directory '/<>/src'
Running tests: compress_tests from test/compress_tests.cpp
test/test_bitcoin -l test_suite -t "`cat test/compress_tests.cpp | grep -E 
"(BOOST_FIXTURE_TEST_SUITE\\(|BOOST_AUTO_TEST_SUITE\\()" | cut -d '(' -f 2 | 
cut -d ',' -f 1 | cut -d ')' -f 1`" > test/compress_tests.cpp.log 2>&1 || (cat 
test/compress_tests.cpp.log && false)
Running tests: crypto_tests from test/crypto_tests.cpp
test/test_bitcoin -l test_suite -t "`cat test/crypto_tests.cpp | grep -E 
"(BOOST_FIXTURE_TEST_SUITE\\(|BOOST_AUTO_TEST_SUITE\\()" | cut -d '(' -f 2 | 
cut -d ',' -f 1 | cut -d ')' -f 1`" > test/crypto_tests.cpp.log 2>&1 || (cat 
test/crypto_tests.cpp.log && false)
Running tests: cuckoocache_tests from test/cuckoocache_tests.cpp
test/test_bitcoin -l test_suite -t "`cat test/cuckoocache_tests.cpp | grep -E 
"(BOOST_FIXTURE_TEST_SUITE\\(|BOOST_AUTO_TEST_SUITE\\()" | cut -d '(' -f 2 | 
cut -d ',' -f 1 | cut -d ')' -f 1`" > test/cuckoocache_tests.cpp.log 2>&1 || 
(cat test/cuckoocache_tests.cpp.log && false)
Running tests: denialofservice_tests from test/denialofservice_tests.cpp
test/test_bitcoin -l test_suite -t "`cat test/denialofservice_tests.cpp | grep 
-E "(BOOST_FIXTURE_TEST_SUITE\\(|BOOST_AUTO_TEST_SUITE\\()" | cut -d '(' -f 2 | 
cut -d ',' -f 1 | cut -d ')' -f 1`" > test/denialofservice_tests.cpp.log 2>&1 
|| (cat test/denialofservice_tests.cpp.log && false)
Running tests: descriptor_tests from test/descriptor_tests.cpp
test/test_bitcoin -l test_suite -t "`cat test/descriptor_tests.cpp | grep -E 
"(BOOST_FIXTURE_TEST_SUITE\\(|BOOST_AUTO_TEST_SUITE\\()" | cut -d '(' -f 2 | 
cut -d ',' -f 1 | cut -d ')' -f 1`" > test/descriptor_tests.cpp.log 2>&1 || 
(cat test/descriptor_tests.cpp.log && false)
Running tests: getarg_tests from test/getarg_tests.cpp
test/test_bitcoin -l test_suite -t "`cat test/getarg_tests.cpp | grep -E 
"(BOOST_FIXTURE_TEST_SUITE\\(|BOOST_AUTO_TEST_SUITE\\()" | cut -d '(' -f 2 | 
cut -d ',' -f 1 | cut -d ')' -f 1`" > test/getarg_tests.cpp.log 2>&1 || (cat 
test/getarg_tests.cpp.log && false)
Running tests: hash_tests from test/hash_tests.cpp
test/test_bitcoin -l test_suite -t "`cat test/hash_tests.cpp | grep -E 
"(BOOST_FIXTURE_TEST_SUITE\\(|BOOST_AUTO_TEST_SUITE\\()" | cut -d '(' -f 2 | 
cut -d ',' -f 1 | cut -d ')' -f 1`" > test/hash_tests.cpp.log 2>&1 || (cat 
test/hash_tests.cpp.log && false)
Running tests: key_io_tests from test/key_io_tests.cpp
test/test_bitcoin -l test_suite -t "`cat test/key_io_tests.cpp | grep -E 
"(BOOST_FIXTURE_TEST_SUITE\\(|BOOST_AUTO_TEST_SUITE\\()" | cut -d '(' -f 2 | 
cut -d ',' -f 1 | cut -d ')' -f 1`" > test/key_io_tests.cpp.log 2>&1 || (cat 
test/key_io_tests.cpp.log && false)
Running 11 test cases...
Entering test module "Bitcoin Test Suite"
test/crypto_tests.cpp(23): Entering test suite "crypto_tests"
test/crypto_tests.cpp(217): Entering test case "ripemd160_testvectors"
test/crypto_tests.cpp(217): Leaving test case "ripemd160_testvectors"; testing 
time: 346645us
test/crypto_tests.cpp(233): Entering test case "sha1_testvectors"
test/crypto_tests.cpp(233): Leaving test case "sha1_testvectors"; testing time: 
555499us
test/crypto_tests.cpp(249): Entering test case "sha256_testvectors"
test/crypto_tests.cpp(249): Leaving test case "sha256_testvectors"; testing 
time: 550873us
test/crypto_tests.cpp(271): Entering test case "sha512_testvectors"
test/crypto_tests.cpp(271): Leaving test case "sha512_testvectors"; testing 
time: 1591096us
test/crypto_tests.cpp(308): Entering test case "hmac_sha256_testvectors"
test/crypto_tests.cpp(308): Leaving test case "hmac_sha256_testvectors"; 
testing time: 46886us
test/crypto_tests.cpp(361): Entering test case "hmac_sha512_testvectors"
test/crypto_tests.cpp(361): Leaving test case "hmac_sha512_testvectors"; 
testing time: 62095us
test/crypto_tests.cpp(429): Entering test case "aes_testvectors"
test/crypto_tests.cpp(429): Leaving test case "aes_testvectors"; testing time: 
39761us
test/crypto_tests.cpp(445): Entering test case "aes_cbc_testvectors"
test/crypto_tests.cpp(445): 

Bug#934861: marked as done (python-yubico-tools not installable, broken dependency)

[Debian Bug Tracking System]

Your message dated Fri, 23 Aug 2019 09:54:59 +
with message-id 
and subject line Bug#934861: fixed in python-yubico 1.3.2-2.2
has caused the Debian Bug report #934861,
regarding python-yubico-tools not installable, broken dependency
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.)


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

Package: python-yubico-tools
Version: 1.3.2-2.1
Severity: important

The python-yubico-tools package in sid cannot be installed.  The recent 
NMU of the python-yubico added "X-Python-Version: >= 2.8" to the 
debian/control, which resulted in a bogus binary dependency on 
python:any (>= 2.8~).


The current Python packaging policy manual says that these fields are 
obsolete and can be removed now that only Python 2.7 is supported[1].


[1] 
https://www.debian.org/doc/packaging-manuals/python-policy/module_packages.html#specifying_versions

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

Kernel: Linux 5.0.0-trunk-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python-yubico-tools depends on:
ii  libpython2.7-stdlib [python-argparse]  2.7.16-3
ii  python 2.7.16-1
ii  python-yubico  1.3.2-2.2~prerelease

python-yubico-tools recommends no packages.

python-yubico-tools suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-yubico
Source-Version: 1.3.2-2.2

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
python-yubico 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 Aug 2019 10:45:57 +0200
Source: python-yubico
Binary: python-yubico python-yubico-tools python3-yubico
Architecture: source
Version: 1.3.2-2.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Authentication Maintainers 

Changed-By: Gianfranco Costamagna 
Description:
 python-yubico - Python2 library for talking to Yubico YubiKeys
 python-yubico-tools - Tools for Yubico YubiKeys
 python3-yubico - Python3 library for talking to Yubico YubiKeys
Closes: 934861
Changes:
 python-yubico (1.3.2-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix some lintian warnings, e.g. duplicate long description
   * Fix nocheck not honoured in dh_auto_test
   * Fix copyright non in secure mode
   * Bump std-version to 4.4.0
   * Bump compat level to 12
 .
   [ Darsey Litzenberger  ]
   * Fixup previous upload Closes: #934861
Checksums-Sha1:
 6cfc01076f61e9a0d42984ad2592b174c612b985 2355 python-yubico_1.3.2-2.2.dsc
 157201345e5044cd5dfe3d2340584c89434ffe76 8284 
python-yubico_1.3.2-2.2.debian.tar.xz
 d2573f9efaf003186ea04c53daadecea164e76dd 8097 
python-yubico_1.3.2-2.2_source.buildinfo
Checksums-Sha256:
 1b77ed7a417e4d862e744d149d8de7ce50f48ff0386641c0f6571d0d26baced0 2355 
python-yubico_1.3.2-2.2.dsc
 82b686115a7a08af09c465097f99abe6b6e66c6f69dc6ee1b4b9bd238daa1629 8284 
python-yubico_1.3.2-2.2.debian.tar.xz
 6006ee5c16452a8050d8a8e6f52e4645bb88a91aeced5c3cef21aac573af8382 8097 
python-yubico_1.3.2-2.2_source.buildinfo
Files:
 34537bbb2653c2090a84473d34cf26f0 2355 python optional 
python-yubico_1.3.2-2.2.dsc
 613d0dfc2ff5b72f8e6d5f4c08e7076f 8284 python optional 
python-yubico_1.3.2-2.2.debian.tar.xz
 f149bc7396221572467aaa99cc773293 8097 python optional 
python-yubico_1.3.2-2.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl1fqgMACgkQ808JdE6f

Processed: Re: wireless-tools: ftbfs with GCC-9

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #925857 [src:wireless-tools] wireless-tools: ftbfs with GCC-9
Added tag(s) patch.

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

Bug#925857: wireless-tools: ftbfs with GCC-9

[Reiner Herrmann]

Control: tags -1 + patch

Hi,

the attached patch fixes the FTBFS with gcc9 by moving
the linked libraries to the end of the commandline.

Regards,
  Reiner
diff -Nru wireless-tools-30~pre9/debian/patches/gcc9.patch wireless-tools-30~pre9/debian/patches/gcc9.patch
--- wireless-tools-30~pre9/debian/patches/gcc9.patch	1970-01-01 01:00:00.0 +0100
+++ wireless-tools-30~pre9/debian/patches/gcc9.patch	2019-08-23 11:43:45.0 +0200
@@ -0,0 +1,15 @@
+Author: Reiner Herrmann 
+Description: Fix build with gcc9 by moving linked libraries to the end
+Bug-Debian: https://bugs.debian.org/925857
+
+--- a/Makefile
 b/Makefile
+@@ -150,7 +150,7 @@
+ 
+ # Compilation of the dynamic library
+ $(DYNAMIC): $(OBJS:.o=.so)
+-	$(CC) -shared -o $@ -Wl,-soname,$@ $(STRIPFLAGS) $(LIBS) $(LDFLAGS) -lc $^
++	$(CC) -shared -o $@ -Wl,-soname,$@ $(STRIPFLAGS) $(LDFLAGS) $^ -lc $(LIBS)
+ 
+ # Compilation of the static library
+ $(STATIC): $(OBJS:.o=.so)
diff -Nru wireless-tools-30~pre9/debian/patches/series wireless-tools-30~pre9/debian/patches/series
--- wireless-tools-30~pre9/debian/patches/series	2018-06-05 21:29:11.0 +0200
+++ wireless-tools-30~pre9/debian/patches/series	2019-08-23 11:43:45.0 +0200
@@ -5,3 +5,4 @@
 add-import-type-to-udev-rules
 fix-typos
 improve-make-install
+gcc9.patch


signature.asc
Description: PGP signature

Processed: tagging 935359

[Debian Bug Tracking System]

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

> tags 935359 + pending
Bug #935359 [src:znc] znc: Missing copyright attributions
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#934861: python-yubico-tools not installable, broken dependency

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #934861 [python-yubico-tools] python-yubico-tools not installable, broken 
dependency
Severity set to 'serious' from 'important'
> tags -1 patch pending
Bug #934861 [python-yubico-tools] python-yubico-tools not installable, broken 
dependency
Added tag(s) pending.

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

Bug#935496: Fails to install: Invalid action '-p'

[Michael Biebl]

Package: fuse
Version: 2.9.9-1
Severity: serious

Trying to run apt (re)install fuse results in

$ sudo apt install --reinstall fuse
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 72.3 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ftp.debian.org/debian sid/main amd64 fuse amd64 2.9.9-1 [72.3 kB]
Fetched 72.3 kB in 0s (219 kB/s)
[master ba9ff87] saving uncommitted changes in /etc prior to apt run
 Author: Michael Biebl 
 1 file changed, 5 insertions(+), 5 deletions(-)
(Reading database ... 389058 files and directories currently installed.)
Preparing to unpack .../fuse_2.9.9-1_amd64.deb ...
Unpacking fuse (2.9.9-1) over (2.9.9-1) ...
Setting up fuse (2.9.9-1) ...
dpkg: error processing package fuse (--configure):
 installed fuse package post-installation script subprocess returned error exit 
status 1
Processing triggers for man-db (2.8.6.1-1) ...
Errors were encountered while processing:
 fuse
E: Sub-process /usr/bin/dpkg returned an error code (1)

Looking at the postinst code, the faulty line is
udevadm test --action -p  $(udevadm info -q path -n /dev/fuse) > /dev/null 2>&1

Running that yields
# udevadm test --action -p /devices/virtual/misc/fuse
Invalid action '-p'



I'm not exactly sure what this code is supposed to achieve.
Since fuse no longer ships its own udev rules, maybe it can be dropped
altogether?

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

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

Versions of packages fuse depends on:
ii  adduser   3.118
ii  libc6 2.28-10
ii  libfuse2  2.9.9-1
ii  mount 2.34-0.1
ii  sed   4.7-1

fuse recommends no packages.

fuse suggests no packages.

-- Configuration Files:
/etc/fuse.conf [Errno 13] Keine Berechtigung: '/etc/fuse.conf'

-- no debconf information

Bug#933529: marked as done (gnome-control-center: segfaults on selecting Details -> Overview (info-overview) panel)

[Debian Bug Tracking System]

Your message dated Fri, 23 Aug 2019 07:57:02 +
with message-id 
and subject line Bug#933529: fixed in gnome-control-center 1:3.30.3-2~deb10u1
has caused the Debian Bug report #933529,
regarding gnome-control-center: segfaults on selecting Details -> Overview 
(info-overview) panel
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.)


-- 
933529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-control-center
Version: 1:3.30.3-1
Severity: grave

Suddenly gnome-control-center starts to immediatly segfaults on start.
This happens for me on 2 devices (of 2 tested).

One note about "suddenly": When that started to happen, it first
normally started and then crashed once I tried to enter a submenu
(I think it was "Devices", because I wanted to change timezone settings)
Since then, the crashes are immediate. (Maybe it remembered the last
settings-tab?) 

I've installed the dbgyms, and running it under gdb produces that
backtrace:

tobi@rivendell:~/tmp/gnome-control-center-3.30.3$ gdb gnome-control-center

Reading symbols from gnome-control-center...
Reading symbols from 
/usr/lib/debug/.build-id/8e/05293cc612ba05838d87b656b29337b2329ab0.debug...
(gdb) r
Starting program: /usr/bin/gnome-control-center 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffea2b5700 (LWP 4346)]
[New Thread 0x7fffe9ab4700 (LWP 4347)]
[New Thread 0x7fffe9270700 (LWP 4348)]
[New Thread 0x7fffe8a6f700 (LWP 4349)]
[New Thread 0x7fffdae49700 (LWP 4350)]
[Detaching after fork from child process 4352]

Thread 1 "gnome-control-c" received signal SIGSEGV, Segmentation fault.
__GI___libc_free (mem=0x1) at malloc.c:3093
3093malloc.c: No such file or directory.

(gdb) bt
#0  0x75c3c9bd in __GI___libc_free (mem=0x1) at malloc.c:3093
#1  0x77e865e5 in g_unix_mount_free () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#2  0x555d8e50 in get_primary_disc_info_start (self=0x5606c480)
at ../panels/info/cc-info-overview-panel.c:539
#3  0x555d9bc7 in get_primary_disc_info (self=0x5606c480)
at ../panels/info/cc-info-overview-panel.c:593
#4  0x555d9bc7 in info_overview_panel_setup_overview 
(self=0x5606c480)
at ../panels/info/cc-info-overview-panel.c:794
#5  0x555d9bc7 in cc_info_overview_panel_init (self=0x5606c480)
at ../panels/info/cc-info-overview-panel.c:910
#6  0x77d992f7 in g_type_create_instance () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x77d7b738 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x77d7d5c4 in g_object_new_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x77d7d8f9 in g_object_new () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x555ace19 in cc_panel_loader_load_by_name
(shell=, name=, parameters=) 
at ../shell/cc-panel-loader.c:248
#11 0x555b05c1 in activate_panel
(gicon=, visibility=, name=0x56248d50 
"About", parameters=0x0, id=0x56096ac0 "info-overview", 
self=0x55fc0460) at ../shell/cc-window.c:184
#12 0x555b05c1 in set_active_panel_from_id
(shell=0x55fc0460, start_id=, parameters=0x0, 
add_to_history=1, error=)
at ../shell/cc-window.c:395
#13 0x77d78b97 in g_cclosure_marshal_VOID__STRINGv () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x77d760c6 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x77d9257d in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x77d92b6f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x555aee06 in row_activated_cb (listbox=0x560747a0, 
row=0x55fd4810, self=0x5606c1f0)
at ../shell/cc-panel-list.c:567
#18 0x77d791ff in g_cclosure_marshal_VOID__OBJECTv () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#19 0x77d760c6 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#20 0x77d9257d in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#21 0x77d92b6f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#22 0x77d760c6 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#23 0x77d9257d in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#24 0x77d93046 in g_signal_emit_by_name () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#25 

Bug#935037: marked as done (nginx: CVE-2019-9511 CVE-2019-9513 CVE-2019-9516)

[Debian Bug Tracking System]

Your message dated Fri, 23 Aug 2019 07:57:04 +
with message-id 
and subject line Bug#935037: fixed in nginx 1.14.2-2+deb10u1
has caused the Debian Bug report #935037,
regarding nginx: CVE-2019-9511 CVE-2019-9513 CVE-2019-9516
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.)


-- 
935037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nginx
Version: 1.14.2-2
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 1.10.3-1+deb9u2
Control: found -1 1.10.3-1

Hi,

The following vulnerabilities were published for nginx.

CVE-2019-9511[0]:
| Some HTTP/2 implementations are vulnerable to window size manipulation
| and stream prioritization manipulation, potentially leading to a
| denial of service. The attacker requests a large amount of data from a
| specified resource over multiple streams. They manipulate window size
| and stream priority to force the server to queue the data in 1-byte
| chunks. Depending on how efficiently this data is queued, this can
| consume excess CPU, memory, or both.


CVE-2019-9513[1]:
| Some HTTP/2 implementations are vulnerable to resource loops,
| potentially leading to a denial of service. The attacker creates
| multiple request streams and continually shuffles the priority of the
| streams in a way that causes substantial churn to the priority tree.
| This can consume excess CPU.


CVE-2019-9516[2]:
| Some HTTP/2 implementations are vulnerable to a header leak,
| potentially leading to a denial of service. The attacker sends a
| stream of headers with a 0-length header name and 0-length header
| value, optionally Huffman encoded into 1-byte or greater headers. Some
| implementations allocate memory for these headers and keep the
| allocation alive until the session dies. This can consume excess
| memory.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-9511
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9511

https://github.com/nginx/nginx/commit/a987f81dd19210bc30b62591db331e31d3d74089
[1] https://security-tracker.debian.org/tracker/CVE-2019-9513
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9513

https://github.com/nginx/nginx/commit/5ae726912654da10a9a81b2c8436829f3e94f69f
[2] https://security-tracker.debian.org/tracker/CVE-2019-9516
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9516

https://github.com/nginx/nginx/commit/6dfbc8b1c2116f362bb871efebbf9df576738e89
[3] 
https://www.nginx.com/blog/nginx-updates-mitigate-august-2019-http-2-vulnerabilities/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: nginx
Source-Version: 1.14.2-2+deb10u1

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

Debian distribution maintenance software
pp.
Christos Trochalakis  (supplier of updated nginx 
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 Aug 2019 11:22:25 EEST
Source: nginx
Architecture: source
Version: 1.14.2-2+deb10u1
Distribution: buster-security
Urgency: high
Maintainer: Debian Nginx Maintainers 

Changed-By: Christos Trochalakis 
Closes: 935037
Changes:
 nginx (1.14.2-2+deb10u1) buster-security; urgency=high
 .
   * Backport upstream fixes for 3 CVEs (Closes: #935037)
 Those fixes affect Nginx HTTP/2 implementation, which might cause
 excessive memory consumption and CPU 

Processed: block 932545 with 932543

[Debian Bug Tracking System]

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

> block 932545 with 932543
Bug #932545 [ftp.debian.org] RM: python-xmlbuilder -- ROM; No upstream, python 
2 only
932545 was not blocked by any bugs.
932545 was not blocking any bugs.
Added blocking bug(s) of 932545: 932543
> thanks
Stopping processing here.

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

Processed: forcibly merging 932542 932197

[Debian Bug Tracking System]

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

> forcemerge 932542 932197
Bug #932542 [src:nipype] Please switch to Python 3
Bug #932197 [src:nipype] Please switch to Python 3
Severity set to 'serious' from 'important'
Marked as found in versions nipype/1.1.8-1.
Added tag(s) sid, bullseye, and experimental.
Bug #932542 [src:nipype] Please switch to Python 3
Marked as found in versions nipype/1.1.9-1.
Merged 932197 932542
> thanks
Stopping processing here.

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

Bug#875207: [tipp10] Future Qt4 removal from Buster

[Christoph Martin]

Hi Moritz,

Am 22.08.19 um 21:47 schrieb Moritz Mühlenhoff:

> tipp10 seems to be dead upstream (not surprising given that it seems to be
> based on an old diploma thesis)
> 
> Are you planning to port it to Qt5 yourself? Otherwise we should remove it
> from the archive.

I'd like to try to port it to qt5. I also try to get some help from more
experienced qt5 developpers or maintainers.

If it is to much work or to difficult we have to drop the package.

Christoph



signature.asc
Description: OpenPGP digital signature

Bug#935490: debian-installer: Mouse and keyboard freezes at first screen, choose language

[Marcus]

Package: debian-installer
Version: Debian 10 buster
Severity: critical
Tags: d-i
Justification: breaks the whole system

Dear Maintainer,

Installing from USB stick on a supermicro server.
Tested with netintall, full local install and firmware install iso. All of them 
have the same behavior.
At first try came up to where the installer ask for non-free firmware. Went to 
fetch them and when I came back mouse and keyboard was frozen.
Tested a number of times and with different iso images with the same result. 
The mouse and keyboard freezes on first screen where you choose install 
language.
Server only have urb3 ports, and the BIOS were set to usb2 support enabled and 
usb3 auto. Tested to change settings but no difference.
Tried to install Debian 9.9 and that worked well without any freeze.
Might be related to bug report: #728226
debian-installer: Install freezes for up to 70 seconds in isolinux

Thanks
Marcus


-- System Information:
Debian Release: 10