Bug#896628: marked as done (FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive')

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2018 03:34:30 +
with message-id 
and subject line Bug#896628: fixed in pymvpa2 2.6.5-1
has caused the Debian Bug report #896628,
regarding FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'
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.)


-- 
896628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinx
Version: 1.7.2-1
Severity: serious
Control: affects -1 src:alembic src:bcfg2 src:bottleneck src:dipy src:heat 
src:julia src:mako src:prospector src:pyevolve src:pymvpa2 
src:python-cryptography src:python-expyriment src:python-numpy src:python-scipy

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/alembic.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bcfg2.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bottleneck.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dipy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/heat.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/julia.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mako.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prospector.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyevolve.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pymvpa2.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/python-cryptography.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-expyriment.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-numpy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-scipy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/sqlalchemy.html

Example (from alembic):

...
   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/build/1st/alembic-0.9.7'
sphinx-build -b html docs/build 
/build/1st/alembic-0.9.7/debian/alembic/usr/share/doc/alembic/html
Running Sphinx v1.7.2

Extension error:
Could not import extension changelog (exception: cannot import name 'Directive')
make[1]: *** [debian/rules:13: override_dh_sphinxdoc] Error 2
--- End Message ---
--- Begin Message ---
Source: pymvpa2
Source-Version: 2.6.5-1

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

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

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

Debian distribution maintenance software
pp.
Yaroslav Halchenko  (supplier of updated pymvpa2 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: Mon, 25 Jun 2018 22:03:05 -0400
Source: pymvpa2
Binary: python-mvpa2 python-mvpa2-lib python-mvpa2-doc
Architecture: source all amd64
Version: 2.6.5-1
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian team 
Changed-By: Yaroslav Halchenko 
Description:
 python-mvpa2 - multivariate pattern analysis with Python v. 2
 python-mvpa2-doc - documentation and examples for PyMVPA v. 2
 python-mvpa2-lib - low-level implementations and bindings for PyMVPA v. 2
Closes: 896628
Changes:
 pymvpa2 (2.6.5-1) unstable; urgency=medium
 .
   * Fresh minor upstream release
   * debian/patches
 - two patches to make docs buildable (Closes: #896628)
Checksums-Sha1:
 07f8f5f061229b6bdb94c5393999484f53848deb 2411 pymvpa2_2.6.5-1.dsc
 9da828ba20ae0946172c19053ad6b610f84392f8 8154417 pymvpa2_2.6.5.orig.tar.gz
 2efbd2ab9d66475a8afa26a808c4dc853e720e3d 318760 pymvpa2_2.6.5-1.debian.tar.xz
 0409f61d395e6b3fb8f5a13b7e141b9cedf9aec0 14899 pymvpa2_2.6.5-1_amd64.buildinfo
 2bdfc8181f53989e6752d564c67ef52ed3389ae6 4262520 
python-mvpa2-doc_2.6.5-1_all.deb
 c851205c4cbecc457333961c9109e6099defeff0 90844 
python-mvpa2-lib-dbgsym_2.6.5-1_amd64.deb
 a723fe56bca0076a2ac17443be176d1096972448 51468 
python-mvpa2-lib_2.6.5-1_amd64.deb
 8e96274c11153122207d9c8b14e70d49853ef63a 5108676 python-mvpa2_2.6.5-1_all.deb
Checksums-Sha256:
 71e67d2e27b32d833307ca6ec3c91a5c2960991bad4bbd34dd6e91b5b51053c5 2411 

Bug#902465: marked as done (golang-github-armon-go-metrics: FTBFS in buster/sid (failing tests))

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2018 03:04:12 +
with message-id 
and subject line Bug#902465: fixed in golang-github-armon-go-metrics 
0.0~git20171117.6c3acc97-1
has caused the Debian Bug report #902465,
regarding golang-github-armon-go-metrics: FTBFS in buster/sid (failing tests)
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.)


-- 
902465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:golang-github-armon-go-metrics
Version: 0.0~git20170601.0.f036747-5
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/golang-github-armon-go-metrics-0.0\~git20170601.0.f036747/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/<>/golang-github-armon-go-metrics-0.0\~git20170601.0.f036747/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/armon/go-metrics github.com/armon/go-metrics/circonus 
github.com/armon/go-metrics/datadog github.com/armon/go-metrics/prometheus
github.com/armon/go-metrics
github.com/hashicorp/go-cleanhttp
github.com/hashicorp/go-retryablehttp
github.com/circonus-labs/circonus-gometrics/api
github.com/circonus-labs/circonus-gometrics/checkmgr
github.com/circonus-labs/circonusllhist
github.com/circonus-labs/circonus-gometrics

[... snipped ...]

--- PASS: TestNewStatsdSinkFromURL (0.00s)
--- PASS: TestNewStatsdSinkFromURL/address_is_populated (0.00s)
--- PASS: TestNewStatsdSinkFromURL/address_includes_port (0.00s)
=== RUN   TestStatsite_Flatten
--- PASS: TestStatsite_Flatten (0.00s)
=== RUN   TestStatsite_PushFullQueue
--- PASS: TestStatsite_PushFullQueue (0.00s)
=== RUN   TestStatsite_Conn
--- SKIP: TestStatsite_Conn (0.00s)
statsite_test.go:46: 
=== RUN   TestNewStatsiteSinkFromURL
=== RUN   TestNewStatsiteSinkFromURL/address_is_populated
=== RUN   TestNewStatsiteSinkFromURL/address_includes_port
--- PASS: TestNewStatsiteSinkFromURL (0.00s)
--- PASS: TestNewStatsiteSinkFromURL/address_is_populated (0.00s)
--- PASS: TestNewStatsiteSinkFromURL/address_includes_port (0.00s)
FAIL
FAILgithub.com/armon/go-metrics 0.230s
=== RUN   TestNewCirconusSink
--- PASS: TestNewCirconusSink (0.00s)
=== RUN   TestFlattenKey
--- PASS: TestFlattenKey (0.00s)
=== RUN   TestSetGauge
--- SKIP: TestSetGauge (0.00s)
circonus_test.go:72: 
=== RUN   TestIncrCounter
--- PASS: TestIncrCounter (0.00s)
=== RUN   TestAddSample
--- PASS: TestAddSample (0.00s)
PASS
ok  github.com/armon/go-metrics/circonus0.003s
=== RUN   TestParseKey
--- PASS: TestParseKey (0.00s)
=== RUN   TestFlattenKey
--- PASS: TestFlattenKey (0.00s)
=== RUN   TestMetricSink
--- PASS: TestMetricSink (0.00s)
=== RUN   TestTaggableMetrics
--- PASS: TestTaggableMetrics (0.00s)
PASS
ok  github.com/armon/go-metrics/datadog 0.002s
?   github.com/armon/go-metrics/prometheus  [no test files]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/armon/go-metrics github.com/armon/go-metrics/circonus 
github.com/armon/go-metrics/datadog github.com/armon/go-metrics/prometheus 
returned exit code 1
debian/rules:5: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-armon-go-metrics.html

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: golang-github-armon-go-metrics
Source-Version: 0.0~git20171117.6c3acc97-1

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

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

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

[Debian Bug Tracking System]

Your message dated Wed, 27 Jun 2018 00:37:15 +
with message-id 
and subject line Bug#899914: fixed in mp4h 1.3.1-17
has caused the Debian Bug report #899914,
regarding mp4h: Invalid maintainer address 
pkg-wml-maintain...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of mp4h,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: mp4h
Source-Version: 1.3.1-17

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

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

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated mp4h package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 27 Jun 2018 02:04:54 +0200
Source: mp4h
Binary: mp4h
Architecture: source amd64
Version: 1.3.1-17
Distribution: unstable
Urgency: medium
Maintainer: Axel Beckert 
Changed-By: Axel Beckert 
Description:
 mp4h   - Macro processor for HTML documents
Closes: 899914 901534
Changes:
 mp4h (1.3.1-17) unstable; urgency=medium
 .
   [ Axel Beckert ]
   * Update Vcs-* headers for packaging repository moving to Salsa.
   * Drop one-man-team from Maintainer field, set myself personally there
 instead. (Closes: #899914)
   * Remove trailing whitespace from ancient debian/changelog entries.
   * Declare compliance with Debian Policy 4.1.4.
 + Update debian/copyright format URL and another one to HTTPS.
   * Drop no more needed Testsuite field from debian/control.
   * Add (mostly redundant) DEP12 debian/upstream/metadata file.
   * Add patch to fix spelling error found by lintian in man page.
 .
   [ Helmut Grohne ]
   * Link libpcre dynamically. (Closes: #901534)
Checksums-Sha1:
 51867bbd9849fac76fcbd5bb3bb8e1e3a2c3324b 1940 mp4h_1.3.1-17.dsc
 bbd7b2aa72b942b37210ef947fc9fc54a21f74f9 16344 mp4h_1.3.1-17.debian.tar.xz
 cc1a7ab6836ca346d287c8b4b9ccf7a8cfcc65a7 150516 mp4h-dbgsym_1.3.1-17_amd64.deb
 9a41de9a95f0deda82679af708b2d11a876bdfdf 5940 

Bug#885038: Bug #885038 in paprefs marked as pending

[Felipe Sateler]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/pulseaudio-team/paprefs/commit/2e76ca4ea884f1470b15a9f94331b67df5c9352a


Port to GSettings and GTK-3 from GConf and GTK-2

1. Pick upstream patches that accomplish this.
2. Build-Depend on gtkmm-3
3. Adjust package dependencies for the new gsettings module

Closes: #885038
Closes: #885076



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/885038

Bug#885076: Bug #885076 in paprefs marked as pending

[Felipe Sateler]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/pulseaudio-team/paprefs/commit/2e76ca4ea884f1470b15a9f94331b67df5c9352a


Port to GSettings and GTK-3 from GConf and GTK-2

1. Pick upstream patches that accomplish this.
2. Build-Depend on gtkmm-3
3. Adjust package dependencies for the new gsettings module

Closes: #885038
Closes: #885076



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/885076

Processed: Bug #885038 in paprefs marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #885038 [src:paprefs] paprefs: Please don't (Build-)Depend on gconfmm2.6
Added tag(s) pending.

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

Processed: Bug #885076 in paprefs marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #885076 [src:paprefs] paprefs: Drop (Build-)Depends on libglademm2.4
Added tag(s) pending.

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

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

[Debian Bug Tracking System]

Your message dated Tue, 26 Jun 2018 23:49:22 +
with message-id 
and subject line Bug#899962: fixed in eperl 2.2.14-23
has caused the Debian Bug report #899962,
regarding eperl: Invalid maintainer address 
pkg-wml-maintain...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of eperl,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: eperl
Source-Version: 2.2.14-23

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

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

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated eperl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 27 Jun 2018 01:20:50 +0200
Source: eperl
Binary: eperl
Architecture: source amd64
Version: 2.2.14-23
Distribution: unstable
Urgency: medium
Maintainer: Axel Beckert 
Changed-By: Axel Beckert 
Description:
 eperl  - Embedded Perl 5 Language
Closes: 899962
Changes:
 eperl (2.2.14-23) unstable; urgency=medium
 .
   * Update Vcs-* headers for packaging repository moving to Salsa.
   * Drop one-man-team from Maintainer field, set myself personally there
 instead. (Closes: #899962)
   * Remove trailing whitespace from ancient debian/changelog entries.
   * Declare compliance with Debian Policy 4.1.4. (No changes needed.)
   * Bump debhelper compatibility level to 11.
 + Update versioned build-dependency on debhelper accordingly.
 + Update .gitignore to ignore additional build artefacts.
   * Guard a few patched files from being cleaned up by
 dh_autoreconf_clean.
   * Convert debian/copyright to machine-readable DEP5 format.
Checksums-Sha1:
 f15bc9de35bd5358cf9a4a6fb302f10b42c4889d 1833 eperl_2.2.14-23.dsc
 a590915cf091353ed8d35001b7f3ff766bb8f3ca 67380 eperl_2.2.14-23.debian.tar.xz
 903605ee31c849726f7edac7846e1e1a47125955 40940 eperl-dbgsym_2.2.14-23_amd64.deb
 a1bccfdcca128564f695953be97784b7ec727e50 5751 eperl_2.2.14-23_amd64.buildinfo

Processed: tagging 899914

[Debian Bug Tracking System]

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

> tags 899914 + pending
Bug #899914 [src:mp4h] mp4h: Invalid maintainer address 
pkg-wml-maintain...@lists.alioth.debian.org
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#902470: influxdb-python: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:influxdb-python
Version: 4.1.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython2_2.7_influxdb/build/influxdb

[... snipped ...]

SKIP: Skipping server test (INFLUXDB_PYTHON_SKIP_SERVER_TESTS)
test_create_database 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_create_user 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_create_user_admin 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_create_user_blank_password 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_create_user_blank_username 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_drop_database 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_drop_user 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_drop_user_nonexisting 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_fresh_server_no_db 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_get_list_users 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_get_list_users_empty 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_grant_privilege 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_grant_privilege_invalid 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_invalid_port_fails 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_query_fail 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_query_fail_ignore_errors 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_revoke_admin_privileges 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_revoke_privilege 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
test_revoke_privilege_invalid 
(influxdb.tests.server_tests.client_test_with_server.SimpleTests) ... SKIP: 
Skipping server tests...
SKIP: Skipping server test (INFLUXDB_PYTHON_SKIP_SERVER_TESTS)
Ensure precision is preserved when casting floats into strings. ... ok
test_make_lines (influxdb.tests.test_line_protocol.TestLineProtocol) ... ok
test_make_lines_unicode (influxdb.tests.test_line_protocol.TestLineProtocol) 
... ok
test_quote_ident (influxdb.tests.test_line_protocol.TestLineProtocol) ... ok
test_quote_literal (influxdb.tests.test_line_protocol.TestLineProtocol) ... ok
test_string_val_newline (influxdb.tests.test_line_protocol.TestLineProtocol) 
... ok
test_timezone (influxdb.tests.test_line_protocol.TestLineProtocol) ... ok

==
FAIL: test_write_points_from_dataframe_with_numeric_precision 
(influxdb.tests.dataframe_client_test.TestDataFrameClient)
--
Traceback (most recent call last):
  File "/<>/influxdb/tests/dataframe_client_test.py", line 294, in 
test_write_points_from_dataframe_with_numeric_precision
self.assertEqual(m.last_request.body, expected_default_precision)
AssertionError: 'foo,hello=there 0="1",1=1i,2=1.1 
0\nfoo,hello=there 0="2",1=2i,2=2.2 36000\n' != 
'foo,hello=there 0="1",1=1i,2=1.111 0\nfoo,hello=there 
0="2",1=2i,2=2.222 36000\n'

--
Ran 190 tests in 0.634s

FAILED (SKIP=23, failures=1)
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython2_2.7_influxdb/build; python2.7 -m nose {dir} 
--verbose
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:10: recipe for 

Bug#902471: ipywidgets: FTBFS in buster/sid (error TS2352: Type 'HTMLButtonElement' cannot be converted to type 'HTMLInputElement')

[Santiago Vila]

Package: src:ipywidgets
Version: 6.0.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
dh_auto_configure -- -d ./widgetsnbextension
I: pybuild base:217: python2.7 setup.py config 
INFO:root:setup.py entered
INFO:root:$PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
running config
I: pybuild base:217: python3.6 setup.py config 
INFO:root:setup.py entered
INFO:root:$PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
running config
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/usr/bin/make -C debian -f fakewebpack.mk all
make[2]: Entering directory '/<>/debian'
/usr/bin/make -f "fakewebpack-prep-unpacked.mk" all
make[3]: Entering directory '/<>/debian'
cd "fakewebpack-unpacked/phosphor/" && tsc --project src
mkdir -p "fakewebpack-unpacked/phosphor/styles/" && NODE_PATH=../.. 
fakewebpack-helpers/css-loader-pack.py < 
"fakewebpack-unpacked/phosphor/styles/base.css.real" > 
"fakewebpack-unpacked/phosphor/styles/base.css"
mkdir -p "fakewebpack-unpacked/phosphor/styles/" && m4 -DNODE_PATH=../.. 
-DCSS_INPUT=./base.css "fakewebpack-helpers/style-loader.js.m4" > 
"fakewebpack-unpacked/phosphor/styles/base.css?f74d"
printf "module.exports = $(cat 
"fakewebpack-unpacked/jupyter-js-widgets/package.json.real");" > 
"fakewebpack-unpacked/jupyter-js-widgets/package.json"
cd "fakewebpack-unpacked/jupyter-js-widgets/" && tsc --project src
src/widget_selection.ts(366,30): error TS2352: Type 'HTMLButtonElement' cannot 
be converted to type 'HTMLInputElement'.
  Property 'accept' is missing in type 'HTMLButtonElement'.
fakewebpack-prep-unpacked.mk:33: recipe for target 
'fakewebpack-unpacked/jupyter-js-widgets/lib.stamp' failed
make[3]: *** [fakewebpack-unpacked/jupyter-js-widgets/lib.stamp] Error 1
make[3]: Leaving directory '/<>/debian'
fakewebpack.mk:73: recipe for target 
'fakewebpack/widgetsnbextension-unpacked.stamp' failed
make[2]: *** [fakewebpack/widgetsnbextension-unpacked.stamp] Error 2
make[2]: Leaving directory '/<>/debian'
debian/rules:15: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
debian/rules:7: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902469: golang-gopkg-hlandau-easyconfig.v1: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:golang-gopkg-hlandau-easyconfig.v1
Version: 1.0.15-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" 
-asmflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -v -p 1 
gopkg.in/hlandau/easyconfig.v1 gopkg.in/hlandau/easyconfig.v1/adaptconf 
gopkg.in/hlandau/easyconfig.v1/adaptenv 
gopkg.in/hlandau/easyconfig.v1/adaptflag gopkg.in/hlandau/easyconfig.v1/cflag 
gopkg.in/hlandau/easyconfig.v1/cstruct gopkg.in/hlandau/easyconfig.v1/manual
gopkg.in/hlandau/configurable.v1
github.com/BurntSushi/toml
gopkg.in/hlandau/easyconfig.v1/cflag
gopkg.in/hlandau/svcutils.v1/exepath
gopkg.in/hlandau/easyconfig.v1/adaptconf
gopkg.in/hlandau/easyconfig.v1/adaptenv
github.com/ogier/pflag
github.com/alecthomas/units
gopkg.in/alecthomas/kingpin.v2
gopkg.in/hlandau/easyconfig.v1/adaptflag
# gopkg.in/hlandau/easyconfig.v1/adaptflag
src/gopkg.in/hlandau/easyconfig.v1/adaptflag/adaptflag.go:227:22: cannot use 
byte(r) (type byte) as type rune in argument to fl.Short
gopkg.in/hlandau/easyconfig.v1/cstruct
gopkg.in/hlandau/easyconfig.v1/manual
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" 
-asmflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -v -p 1 
gopkg.in/hlandau/easyconfig.v1 gopkg.in/hlandau/easyconfig.v1/adaptconf 
gopkg.in/hlandau/easyconfig.v1/adaptenv 
gopkg.in/hlandau/easyconfig.v1/adaptflag gopkg.in/hlandau/easyconfig.v1/cflag 
gopkg.in/hlandau/easyconfig.v1/cstruct gopkg.in/hlandau/easyconfig.v1/manual 
returned exit code 2
debian/rules:7: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-gopkg-hlandau-easyconfig.v1.html

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902468: golang-github-mwitkow-go-conntrack: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:golang-github-mwitkow-go-conntrack
Version: 0.0~git20161129.cc309e4-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
dh_auto_configure: "github.com/mwitkow/go-conntrack" is already installed. 
Please check for circular dependencies.

   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/golang-github-mwitkow-go-conntrack-0.0\~git20161129.cc309e4/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/<>/golang-github-mwitkow-go-conntrack-0.0\~git20161129.cc309e4/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/mwitkow/go-conntrack 
github.com/mwitkow/go-conntrack/connhelpers
github.com/beorn7/perks/quantile
github.com/golang/protobuf/proto
github.com/prometheus/client_model/go
github.com/matttproud/golang_protobuf_extensions/pbutil
github.com/prometheus/common/internal/bitbucket.org/ww/goautoneg
github.com/prometheus/common/model
github.com/prometheus/common/expfmt
github.com/prometheus/procfs/internal/util
github.com/prometheus/procfs/nfs
github.com/prometheus/procfs/xfs
github.com/prometheus/procfs
github.com/prometheus/client_golang/prometheus
golang.org/x/net/internal/timeseries
golang.org/x/net/trace
github.com/mwitkow/go-conntrack
github.com/mwitkow/go-conntrack/connhelpers
   dh_auto_test -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/mwitkow/go-conntrack github.com/mwitkow/go-conntrack/connhelpers
=== RUN   TestDialerWrapper
=== RUN   
TestDialerWrapper/TestDialerMetricsAreNotPreregisteredWithMonitoringOff
=== RUN   TestDialerWrapper/TestDialerMetricsArePreregistered
=== RUN   TestDialerWrapper/TestDialerRefusedFailure
=== RUN   TestDialerWrapper/TestDialerResolutionFailure
=== RUN   TestDialerWrapper/TestDialerUnderNormalConnection
=== RUN   TestDialerWrapper/TestDialerWithContextName
--- PASS: TestDialerWrapper (0.12s)
--- PASS: 
TestDialerWrapper/TestDialerMetricsAreNotPreregisteredWithMonitoringOff (0.01s)
--- PASS: TestDialerWrapper/TestDialerMetricsArePreregistered (0.02s)
--- PASS: TestDialerWrapper/TestDialerRefusedFailure (0.01s)
--- PASS: TestDialerWrapper/TestDialerResolutionFailure (0.04s)
--- PASS: TestDialerWrapper/TestDialerUnderNormalConnection (0.02s)
--- PASS: TestDialerWrapper/TestDialerWithContextName (0.01s)
dialer_test.go:186: stopped http.Server at: 127.0.0.1:46241
=== RUN   TestListenerTestSuite
=== RUN   TestListenerTestSuite/TestDialerTracingCapturedInPage
=== RUN   TestListenerTestSuite/TestMonitoringNormalConns
=== RUN   TestListenerTestSuite/TestTracingNormalComms
=== RUN   TestListenerTestSuite/TestTrackingMetricsPreregistered
--- FAIL: TestListenerTestSuite (0.05s)
--- PASS: TestListenerTestSuite/TestDialerTracingCapturedInPage (0.01s)
--- FAIL: TestListenerTestSuite/TestMonitoringNormalConns (0.01s)
listener_test.go:81: 
Error Trace:listener_test.go:81
Error:  Not equal: 
expected: 2
actual  : 1
Test:   
TestListenerTestSuite/TestMonitoringNormalConns
Messages:   the closed conn counter must be 
incremented after connection was closed
--- PASS: TestListenerTestSuite/TestTracingNormalComms (0.01s)
--- PASS: TestListenerTestSuite/TestTrackingMetricsPreregistered (0.01s)
listener_test.go:97: stopped http.Server at: 127.0.0.1:41893
FAIL
FAILgithub.com/mwitkow/go-conntrack 0.180s
?   github.com/mwitkow/go-conntrack/connhelpers [no test files]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/mwitkow/go-conntrack github.com/mwitkow/go-conntrack/connhelpers 
returned exit code 1
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-mwitkow-go-conntrack.html

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902462: flask-restful: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:flask-restful
Version: 0.3.6-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=pybuild --with=python2,python3,sphinxdoc
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild base:217: /usr/bin/python setup.py build 

[... snipped ...]

checking consistency... done
preparing documents... done
writing output... [ 11%] api
writing output... [ 22%] extending
writing output... [ 33%] fields
writing output... [ 44%] index
writing output... [ 55%] installation
writing output... [ 66%] intermediate-usage
writing output... [ 77%] quickstart
writing output... [ 88%] reqparse
writing output... [100%] testing

/<>/docs/reqparse.rst:41: WARNING: undefined label: error-messages 
(if the link has no caption the label must precede a section header)
generating indices... genindex py-modindex
writing additional pages... search
copying static files... done
copying extra files... done
dumping search index in English (code: en) ... done
dumping object inventory... done
build succeeded, 5 warnings.

The HTML pages are in _build/html.

Build finished. The HTML pages are in _build/html.
make[2]: Leaving directory '/<>/docs'
make[1]: Leaving directory '/<>'
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:217: cd 
/<>/.pybuild/cpython2_2.7_flask-restful/build; python2.7 -m nose 
tests
...E...
==
ERROR: test_fr_405 (tests.test_api.APITestCase)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython2_2.7_flask-restful/build/tests/test_api.py", 
line 787, in test_fr_405
set(['HEAD', 'OPTIONS'] + HelloWorld.methods))
TypeError: can only concatenate list (not "set") to list

--
Ran 395 tests in 0.228s

FAILED (errors=1)
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython2_2.7_flask-restful/build; python2.7 -m nose 
tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
exit code 13
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902465: golang-github-armon-go-metrics: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:golang-github-armon-go-metrics
Version: 0.0~git20170601.0.f036747-5
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/golang-github-armon-go-metrics-0.0\~git20170601.0.f036747/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/<>/golang-github-armon-go-metrics-0.0\~git20170601.0.f036747/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/armon/go-metrics github.com/armon/go-metrics/circonus 
github.com/armon/go-metrics/datadog github.com/armon/go-metrics/prometheus
github.com/armon/go-metrics
github.com/hashicorp/go-cleanhttp
github.com/hashicorp/go-retryablehttp
github.com/circonus-labs/circonus-gometrics/api
github.com/circonus-labs/circonus-gometrics/checkmgr
github.com/circonus-labs/circonusllhist
github.com/circonus-labs/circonus-gometrics

[... snipped ...]

--- PASS: TestNewStatsdSinkFromURL (0.00s)
--- PASS: TestNewStatsdSinkFromURL/address_is_populated (0.00s)
--- PASS: TestNewStatsdSinkFromURL/address_includes_port (0.00s)
=== RUN   TestStatsite_Flatten
--- PASS: TestStatsite_Flatten (0.00s)
=== RUN   TestStatsite_PushFullQueue
--- PASS: TestStatsite_PushFullQueue (0.00s)
=== RUN   TestStatsite_Conn
--- SKIP: TestStatsite_Conn (0.00s)
statsite_test.go:46: 
=== RUN   TestNewStatsiteSinkFromURL
=== RUN   TestNewStatsiteSinkFromURL/address_is_populated
=== RUN   TestNewStatsiteSinkFromURL/address_includes_port
--- PASS: TestNewStatsiteSinkFromURL (0.00s)
--- PASS: TestNewStatsiteSinkFromURL/address_is_populated (0.00s)
--- PASS: TestNewStatsiteSinkFromURL/address_includes_port (0.00s)
FAIL
FAILgithub.com/armon/go-metrics 0.230s
=== RUN   TestNewCirconusSink
--- PASS: TestNewCirconusSink (0.00s)
=== RUN   TestFlattenKey
--- PASS: TestFlattenKey (0.00s)
=== RUN   TestSetGauge
--- SKIP: TestSetGauge (0.00s)
circonus_test.go:72: 
=== RUN   TestIncrCounter
--- PASS: TestIncrCounter (0.00s)
=== RUN   TestAddSample
--- PASS: TestAddSample (0.00s)
PASS
ok  github.com/armon/go-metrics/circonus0.003s
=== RUN   TestParseKey
--- PASS: TestParseKey (0.00s)
=== RUN   TestFlattenKey
--- PASS: TestFlattenKey (0.00s)
=== RUN   TestMetricSink
--- PASS: TestMetricSink (0.00s)
=== RUN   TestTaggableMetrics
--- PASS: TestTaggableMetrics (0.00s)
PASS
ok  github.com/armon/go-metrics/datadog 0.002s
?   github.com/armon/go-metrics/prometheus  [no test files]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/armon/go-metrics github.com/armon/go-metrics/circonus 
github.com/armon/go-metrics/datadog github.com/armon/go-metrics/prometheus 
returned exit code 1
debian/rules:5: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-armon-go-metrics.html

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902466: golang-github-grpc-ecosystem-go-grpc-prometheus: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:golang-github-grpc-ecosystem-go-grpc-prometheus
Version: 1.1+git20170826.0dafe0d-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   debian/rules override_dh_auto_build
make[1]: Entering directory 
'/<>/golang-github-grpc-ecosystem-go-grpc-prometheus-1.1+git20170826.0dafe0d'
cd 
obj-x86_64-linux-gnu/src/github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto
 && \
GOPATH=obj-x86_64-linux-gnu make 
make[2]: Entering directory 
'/<>/golang-github-grpc-ecosystem-go-grpc-prometheus-1.1+git20170826.0dafe0d/obj-x86_64-linux-gnu/src/github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto'
PATH="obj-x86_64-linux-gnu/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
 protoc \
  -I. \
-Iobj-x86_64-linux-gnu/src \

[... snipped ...]

=== RUN   TestServerInterceptorSuite/TestUnaryIncrementsStarted
--- FAIL: TestServerInterceptorSuite (0.08s)
--- PASS: TestServerInterceptorSuite/TestRegisterPresetsStuff (0.02s)
--- FAIL: TestServerInterceptorSuite/TestStreamingIncrementsHandled (0.01s)
server_test.go:218: 
Error Trace:server_test.go:218
Error:  Not equal: 
expected: 1
actual  : 0
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsHandled
Messages:   grpc_server_handled_total should be 
incremented for PingList FailedPrecondition
--- FAIL: TestServerInterceptorSuite/TestStreamingIncrementsHistograms 
(0.01s)
server_test.go:186: 
Error Trace:server_test.go:186
Error:  Not equal: 
expected: 2
actual  : 3
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsHistograms
Messages:   grpc_server_handling_seconds_count 
should be incremented for PingList OK
server_test.go:193: 
Error Trace:server_test.go:193
Error:  Not equal: 
expected: 4
actual  : 3
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsHistograms
Messages:   grpc_server_handling_seconds_count 
should be incremented for PingList FailedPrecondition
--- PASS: TestServerInterceptorSuite/TestStreamingIncrementsMessageCounts 
(0.01s)
--- FAIL: TestServerInterceptorSuite/TestStreamingIncrementsStarted (0.00s)
server_test.go:168: 
Error Trace:server_test.go:168
Error:  Not equal: 
expected: 6
actual  : 5
Test:   
TestServerInterceptorSuite/TestStreamingIncrementsStarted
Messages:   grpc_server_started_total should be 
incremented for PingList
--- PASS: TestServerInterceptorSuite/TestUnaryIncrementsHandled (0.01s)
--- PASS: TestServerInterceptorSuite/TestUnaryIncrementsHistograms (0.01s)
--- PASS: TestServerInterceptorSuite/TestUnaryIncrementsStarted (0.01s)
server_test.go:86: stopped grpc.Server at: 127.0.0.1:33315
FAIL
FAILgithub.com/grpc-ecosystem/go-grpc-prometheus0.124s
?   github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto [no 
test files]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/grpc-ecosystem/go-grpc-prometheus 
github.com/grpc-ecosystem/go-grpc-prometheus/examples/testproto returned exit 
code 1
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-grpc-ecosystem-go-grpc-prometheus.html

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902467: golang-github-kardianos-osext: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:golang-github-kardianos-osext
Version: 0.0~git20170510.0.ae77be6-5
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/golang-github-kardianos-osext-0.0\~git20170510.0.ae77be6/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/<>/golang-github-kardianos-osext-0.0\~git20170510.0.ae77be6/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/kardianos/osext
github.com/kardianos/osext
   dh_auto_test -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/kardianos/osext
=== RUN   TestPrintExecutable
--- PASS: TestPrintExecutable (0.00s)
osext_test.go:32: Executable: /tmp/go-build962600465/b001/osext.test
=== RUN   TestPrintExecutableFolder
--- PASS: TestPrintExecutableFolder (0.00s)
osext_test.go:39: Executable Folder: /tmp/go-build962600465/b001
=== RUN   TestExecutableFolder
--- PASS: TestExecutableFolder (0.00s)
=== RUN   TestExecutableMatch
--- PASS: TestExecutableMatch (0.00s)
=== RUN   TestExecutableDelete
--- FAIL: TestExecutableDelete (0.00s)
osext_test.go:135: Child returned 
"/tmp/go-build962600465/b001/osext.test (deleted)", not the same file as 
"/tmp/go-build962600465/b001/osext.test"
FAIL
FAILgithub.com/kardianos/osext  0.004s
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/kardianos/osext returned exit code 1
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-kardianos-osext.html

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902464: flask-silk: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:flask-silk
Version: 0.2-12
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with=python2,python3,sphinxdoc,linktree --buildsystem pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build

[... snipped ...]

make[1]: Leaving directory '/<>'
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py test 
running test
running egg_info
writing requirements to Flask_Silk.egg-info/requires.txt
writing Flask_Silk.egg-info/PKG-INFO
writing top-level names to Flask_Silk.egg-info/top_level.txt
writing dependency_links to Flask_Silk.egg-info/dependency_links.txt
reading manifest file 'Flask_Silk.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'Flask_Silk.egg-info/SOURCES.txt'
running build_ext
Traceback (most recent call last):
  File "setup.py", line 46, in 
'Topic :: Software Development :: Libraries :: Python Modules'
  File "/usr/lib/python2.7/dist-packages/setuptools/__init__.py", line 129, in 
setup
return distutils.core.setup(**attrs)
  File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
dist.run_commands()
  File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
  File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
  File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 226, 
in run
self.run_tests()
  File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 248, 
in run_tests
exit=False,
  File "/usr/lib/python2.7/unittest/main.py", line 94, in __init__
self.parseArgs(argv)
  File "/usr/lib/python2.7/unittest/main.py", line 149, in parseArgs
self.createTests()
  File "/usr/lib/python2.7/unittest/main.py", line 158, in createTests
self.module)
  File "/usr/lib/python2.7/unittest/loader.py", line 130, in loadTestsFromNames
suites = [self.loadTestsFromName(name, module) for name in names]
  File "/usr/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName
module = __import__('.'.join(parts_copy))
  File "/<>/test.py", line 5, in 
from flask.ext.silk import Silk
ImportError: No module named ext.silk
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902454: bochs: FTBFS in buster/sid ('AmlCode' undeclared)

[Santiago Vila]

Package: src:bochs
Version: 2.6-5
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh_testdir
libtoolize -c
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './compile'
libtoolize: copying file './config.guess'
libtoolize: copying file './config.sub'
libtoolize: copying file './depcomp'
libtoolize: copying file './install-sh'
libtoolize: copying file './missing'
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in 'libltdl/m4'.
libtoolize: copying file 'libltdl/m4/libtool.m4'

[... snipped ...]


acpi-dsdt.dsl.i631: Return(0x01)
Warning  3104 -  ^ Reserved method should not 
return a value (_L0E)

acpi-dsdt.dsl.i634: Return(0x01)
Warning  3104 -  ^ Reserved method should not 
return a value (_L0F)


Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20180508
Copyright (c) 2000 - 2018 Intel Corporation

ASL Input: acpi-dsdt.dsl.i - 639 lines, 29236 bytes, 707 keywords
AML Output:acpi-dsdt.aml - 7585 bytes, 253 named objects, 454 executable 
opcodes
Hex Dump:  acpi-dsdt.hex - 71586 bytes

Compilation complete. 0 Errors, 51 Warnings, 10 Remarks, 494 Optimizations, 93 
Constants Folded
rm acpi-dsdt.dsl.i
sed -i -e's/^unsigned/const unsigned/' acpi-dsdt.hex
gcc -m32 -fno-stack-protector -O2 -Wall -c -o rombios32.o rombios32.c
rombios32.c: In function 'setup_mtrr':
rombios32.c:501:23: warning: variable 'wc' set but not used 
[-Wunused-but-set-variable]
 int i, vcnt, fix, wc;
   ^~
In file included from rombios32.c:1454:0:
acpi-dsdt.hex: At top level:
acpi-dsdt.hex:13:15: warning: extra tokens at end of #ifndef directive
 #ifndef __ACPI-DSDT_HEX__
   ^
acpi-dsdt.hex:14:15: warning: ISO C99 requires whitespace after the macro name
 #define __ACPI-DSDT_HEX__
   ^
acpi-dsdt.hex:16:25: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before '-' token
 const unsigned char acpi-dsdt_aml_code[] =
 ^
rombios32.c: In function 'acpi_bios_init':
rombios32.c:1609:20: error: 'AmlCode' undeclared (first use in this function)
 addr += sizeof(AmlCode);
^~~
rombios32.c:1609:20: note: each undeclared identifier is reported only once for 
each function it appears in
Makefile:125: recipe for target 'rombios32.o' failed
make[1]: *** [rombios32.o] Error 1
make[1]: Leaving directory '/<>/bios'
debian/rules:135: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902461: flask-oauthlib: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:flask-oauthlib
Version: 0.9.5-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating 
/<>/.pybuild/cpython3_3.6_flask-oauthlib/build/flask_oauthlib
copying flask_oauthlib/client.py -> 
/<>/.pybuild/cpython3_3.6_flask-oauthlib/build/flask_oauthlib
copying flask_oauthlib/__init__.py -> 
/<>/.pybuild/cpython3_3.6_flask-oauthlib/build/flask_oauthlib

[... snipped ...]

return load_source(name, filename, file)
  File "/usr/lib/python3.6/imp.py", line 172, in load_source
module = _load(spec)
  File "", line 684, in _load
  File "", line 665, in _load_unlocked
  File "", line 678, in exec_module
  File "", line 219, in _call_with_frames_removed
  File 
"/<>/.pybuild/cpython3_3.6_flask-oauthlib/build/tests/test_oauth2/test_refresh.py",
 line 5, in 
from .base import TestCase
  File 
"/<>/.pybuild/cpython3_3.6_flask-oauthlib/build/tests/test_oauth2/base.py",
 line 8, in 
from flask_sqlalchemy import SQLAlchemy
ModuleNotFoundError: No module named 'flask_sqlalchemy'

==
ERROR: Failure: ModuleNotFoundError (No module named 'mock')
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest
raise self.exc_val.with_traceback(self.tb)
  File "/usr/lib/python3/dist-packages/nose/loader.py", line 417, in 
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File "/usr/lib/python3.6/imp.py", line 235, in load_module
return load_source(name, filename, file)
  File "/usr/lib/python3.6/imp.py", line 172, in load_source
module = _load(spec)
  File "", line 684, in _load
  File "", line 665, in _load_unlocked
  File "", line 678, in exec_module
  File "", line 219, in _call_with_frames_removed
  File 
"/<>/.pybuild/cpython3_3.6_flask-oauthlib/build/tests/test_utils.py",
 line 4, in 
import mock
ModuleNotFoundError: No module named 'mock'

--
Ran 11 tests in 0.004s

FAILED (errors=9)
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.6_flask-oauthlib/build; python3.6 -m nose 
tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.6 returned 
exit code 13
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902457: cupt: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:cupt
Version: 2.10.1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep -Bb/ --parallel --with bash-completion
   dh_testdir -i -O-Bb/ -O--parallel
   dh_update_autotools_config -i -O-Bb/ -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -Bb/ -- -DCMAKE_BUILD_TYPE=RelWithDebInfo
cd b && cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_BUILD_TYPE=RelWithDebInfo
-- The C compiler identification is GNU 7.3.0
-- The CXX compiler identification is GNU 7.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info

[... snipped ...]

[03:42:41] tt/query/show/package-existance.t 
.. ok   92 ms ( 
0.00 usr  0.00 sys +  0.05 cusr  0.02 csys =  0.07 CPU)
[03:42:41] tt/query/show/status-of-installed-package.t 
 ok  261 ms ( 0.00 usr  
0.00 sys +  0.08 cusr  0.05 csys =  0.13 CPU)
[03:42:41] tt/query/show/version-merging/architecture.t 
... ok  129 ms ( 0.00 usr  
0.00 sys +  0.07 cusr  0.02 csys =  0.09 CPU)
[03:42:42] tt/query/show/version-merging/version-hash-release.t 
... ok  195 ms ( 0.00 usr  0.00 sys 
+  0.08 cusr  0.03 csys =  0.11 CPU)
[03:42:43] tt/query/version-string/compare.t 
.. ok 1230 ms ( 
0.02 usr  0.00 sys +  0.23 cusr  0.19 csys =  0.44 CPU)
[03:42:43] tt/query/version-string/invalid.t 
.. ok  195 ms ( 
0.00 usr  0.00 sys +  0.08 cusr  0.03 csys =  0.11 CPU)
[03:42:43] tt/query/why/basic.t 
... ok  
120 ms ( 0.01 usr  0.00 sys +  0.06 cusr  0.03 csys =  0.10 CPU)
[03:42:44] tt/query/why/endurance.t 
... ok  
955 ms ( 0.00 usr  0.00 sys +  0.68 cusr  0.21 csys =  0.89 CPU)
[03:42:44] tt/query/why/from-specific-packages.t 
.. ok  152 ms ( 
0.00 usr  0.00 sys +  0.07 cusr  0.02 csys =  0.09 CPU)
[03:42:44] tt/query/why/loop.t 
 ok 
  93 ms ( 0.00 usr  0.00 sys +  0.07 cusr  0.01 csys =  0.08 CPU)
[03:42:45] tt/query/why/priorities.t 
.. ok  
311 ms ( 0.01 usr  0.00 sys +  0.11 cusr  0.04 csys =  0.16 CPU)
[03:42:45] tt/query/why/recommends-and-suggests.t 
. ok   98 ms ( 0.00 
usr  0.00 sys +  0.06 cusr  0.02 csys =  0.08 CPU)
[03:42:45] tt/query/why/traverse-order.t 
.. ok   86 
ms ( 0.00 usr  0.00 sys +  0.06 cusr  0.02 csys =  0.08 CPU)



[03:42:45] tt/shell/basic.t 
... 
ok  217 ms ( 0.00 usr  0.01 sys +  0.11 cusr  0.04 csys =  0.16 CPU)
[03:42:45] tt/shell/cache-reload.t 
 ok 
 387 ms ( 0.01 usr  0.00 sys +  0.15 cusr  0.09 csys =  0.25 CPU)
[03:42:46] tt/shell/error-handling.t 
.. ok  
278 ms ( 0.01 usr  0.00 sys +  0.12 cusr  0.03 csys =  0.16 CPU)
[03:42:46] tt/shell/tokenising.t 
.. ok   
   178 ms ( 0.00 usr  0.00 sys +  0.10 cusr  0.04 csys =  0.14 CPU)
[03:42:46] tt/version.t 
...
 ok   94 ms ( 0.00 usr  0.01 sys +  0.06 cusr  0.02 csys =  0.09 CPU)
[03:42:46]

Test Summary Report
---
tt/query/repo-signatures/validation-errors.t
 (Wstat: 768 Tests: 9 Failed: 3)
  Failed tests:  1-2, 9
  Non-zero exit status: 3
Files=181, Tests=2072, 63 wallclock secs ( 0.87 usr  0.22 sys + 36.62 cusr  
7.04 csys = 44.75 CPU)
Result: FAIL
test/CMakeFiles/test.dir/build.make:60: recipe for target 
'test/CMakeFiles/test' failed
make[4]: *** [test/CMakeFiles/test] Error 1
make[4]: Leaving directory '/<>/b'
CMakeFiles/Makefile2:637: recipe for target 

Bug#902463: flask-script: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:flask-script
Version: 2.0.5-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython2_2.7_flask-script/build/flask_script
copying flask_script/commands.py -> 
/<>/.pybuild/cpython2_2.7_flask-script/build/flask_script
copying flask_script/_compat.py -> 
/<>/.pybuild/cpython2_2.7_flask-script/build/flask_script
copying flask_script/cli.py -> 
/<>/.pybuild/cpython2_2.7_flask-script/build/flask_script
copying flask_script/__init__.py -> 
/<>/.pybuild/cpython2_2.7_flask-script/build/flask_script
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython3_3.6_flask-script/build/flask_script
copying flask_script/commands.py -> 
/<>/.pybuild/cpython3_3.6_flask-script/build/flask_script
copying flask_script/_compat.py -> 
/<>/.pybuild/cpython3_3.6_flask-script/build/flask_script
copying flask_script/cli.py -> 
/<>/.pybuild/cpython3_3.6_flask-script/build/flask_script
copying flask_script/__init__.py -> 
/<>/.pybuild/cpython3_3.6_flask-script/build/flask_script
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
py.test tests.py
= test session starts ==
platform linux2 -- Python 2.7.15, pytest-3.3.2, py-1.5.3, pluggy-0.6.0
rootdir: /<>, inifile:
collected 0 items / 1 errors

 ERRORS 
__ ERROR collecting tests.py ___
ImportError while importing test module '/<>/tests.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
tests.py:8: in 
from flask.ext.script._compat import StringIO, text_type
E   ImportError: No module named ext.script._compat
!!! Interrupted: 1 errors during collection 
=== 1 error in 0.21 seconds 
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
debian/rules:10: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902460: flask-assets: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:flask-assets
Version: 0.12-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
copying src/flask_assets.py -> 
/<>/.pybuild/cpython3_3.6_flask-bcrypt/build
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:217: cd 
/<>/.pybuild/cpython3_3.6_flask-bcrypt/build; python3.6 -m nose 
tests

[... snipped ...]


==
ERROR: Make sure url generation works with globs.
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 381, in setUp
try_run(self.inst, ('setup', 'setUp'))
  File "/usr/lib/python3/dist-packages/nose/util.py", line 471, in try_run
return func()
  File 
"/<>/.pybuild/cpython3_3.6_flask-bcrypt/build/tests/test_integration.py",
 line 31, in setup
self.app = Flask(__name__, static_path='/app_static')
TypeError: __init__() got an unexpected keyword argument 'static_path'

==
ERROR: Test how urls are generated via the Flask static system
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 381, in setUp
try_run(self.inst, ('setup', 'setUp'))
  File "/usr/lib/python3/dist-packages/nose/util.py", line 471, in try_run
return func()
  File 
"/<>/.pybuild/cpython3_3.6_flask-bcrypt/build/tests/test_integration.py",
 line 31, in setup
self.app = Flask(__name__, static_path='/app_static')
TypeError: __init__() got an unexpected keyword argument 'static_path'

==
ERROR: Make sure the "url" and "directory" config values are
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 381, in setUp
try_run(self.inst, ('setup', 'setUp'))
  File "/usr/lib/python3/dist-packages/nose/util.py", line 471, in try_run
return func()
  File 
"/<>/.pybuild/cpython3_3.6_flask-bcrypt/build/tests/test_integration.py",
 line 153, in setup
self.app = Flask(__name__, static_path='/initapp_static')
TypeError: __init__() got an unexpected keyword argument 'static_path'

--
Ran 29 tests in 0.066s

FAILED (errors=9)
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.6_flask-bcrypt/build; python3.6 -m nose 
tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.6 returned 
exit code 13
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902456: cf-python: FTBFS in buster/sid (AttributeError: 'module' object has no attribute 'netcdftime')

[Santiago Vila]

Package: src:cf-python
Version: 1.3.2+dfsg1-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep  --with python2,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>/cf-python-1.3.2+dfsg1'
PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -E -b html docs/source 
docs/build/html
Running Sphinx v1.7.5

Configuration error:
There is a programable error in your configuration file:

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/config.py", line 161, in 
__init__
execfile_(filename, config)
  File "/usr/lib/python2.7/dist-packages/sphinx/util/pycompat.py", line 150, in 
execfile_
exec_(code, _globals)
  File "/usr/lib/python2.7/dist-packages/six.py", line 709, in exec_
exec("""exec _code_ in _globs_, _locs_""")
  File "", line 1, in 
  File "conf.py", line 340, in 
import inspect, cf
  File "/<>/cf-python-1.3.2+dfsg1/cf/__init__.py", line 81, in 

from .variable import Variable
  File "/<>/cf-python-1.3.2+dfsg1/cf/variable.py", line 21, in 

from .query  import Query
  File "/<>/cf-python-1.3.2+dfsg1/cf/query.py", line 10, in 
from .cfdatetime import Datetime, dt
  File "/<>/cf-python-1.3.2+dfsg1/cf/cfdatetime.py", line 12, in 

from .unitsimport Units
  File "/<>/cf-python-1.3.2+dfsg1/cf/units.py", line 259, in 
_netCDF4_netcdftime_utime = netCDF4.netcdftime.utime
AttributeError: 'module' object has no attribute 'netcdftime'

debian/rules:14: recipe for target 'override_dh_auto_build-indep' failed
make[1]: *** [override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>/cf-python-1.3.2+dfsg1'
debian/rules:11: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902455: ccdproc: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:ccdproc
Version: 1.3.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py

[... snipped ...]

  ccdproc/core.py:1568: RuntimeWarning: invalid value encountered in greater
crarr = (rarr > thresh)

ccdproc/tests/test_ccdproc.py::test_flat_correct_does_not_change_input
  /usr/lib/python2.7/dist-packages/astropy/units/quantity.py:641: 
RuntimeWarning: invalid value encountered in true_divide
*arrays, **kwargs)

ccdproc/tests/test_ccdproc.py::test_transform_image_does_not_change_input
  ccdproc/core.py:841: RuntimeWarning: invalid value encountered in sqrt
nccd.data = transform_func(nccd.data, **kwargs)

ccdproc/tests/test_ccdproc.py::test_wcs_project_onto_shifted_wcs
  ccdproc/core.py:921: RuntimeWarning: invalid value encountered in greater
reprojected_mask = reprojected_mask > 1e-8

ccdproc/tests/test_ccdproc.py::test_wcs_project_onto_scale_wcs
  ccdproc/core.py:921: RuntimeWarning: invalid value encountered in greater
reprojected_mask = reprojected_mask > 1e-8

docs/ccdproc/image_combination.rst
  -c:1: RuntimeWarning: divide by zero encountered in divide
  -c:1: RuntimeWarning: divide by zero encountered in divide
  -c:1: RuntimeWarning: divide by zero encountered in divide
  ccdproc/combiner.py:169: UserWarning: Warning: converting a masked element to 
nan.
self._scaling = np.array(self._scaling)
  ccdproc/combiner.py:169: UserWarning: Warning: converting a masked element to 
nan.
self._scaling = np.array(self._scaling)
  ccdproc/combiner.py:169: UserWarning: Warning: converting a masked element to 
nan.
self._scaling = np.array(self._scaling)

docs/ccdproc/image_management.rst
  ccdproc/image_collection.py:117: AstropyUserWarning: no FITS files in the 
collection.
AstropyUserWarning)
  ccdproc/image_collection.py:117: AstropyUserWarning: no FITS files in the 
collection.
AstropyUserWarning)
  ccdproc/image_collection.py:117: AstropyUserWarning: no FITS files in the 
collection.
AstropyUserWarning)

-- Docs: http://doc.pytest.org/en/latest/warnings.html
= 4 failed, 370 passed, 3 skipped, 17 warnings in 6.83 seconds =
debian/rules:16: recipe for target 'test-python2.7' failed
make[1]: *** [test-python2.7] Error 1
make[1]: Leaving directory '/<>'
debian/rules:12: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902459: faumachine: FTBFS in buster/sid (error: 'faum_dsdt' undeclared)

[Santiago Vila]

Package: src:faumachine
Version: 20180503-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh_testdir
./autogen.sh
configure.ac:140: installing 'scripts/compile'
configure.ac:142: installing 'scripts/config.guess'
configure.ac:142: installing 'scripts/config.sub'
configure.ac:20: installing 'scripts/install-sh'
configure.ac:20: installing 'scripts/missing'
chips/Makefile.am: installing 'scripts/depcomp'
lib/Makefile.am:174: warning: source file 'pattern-matcher/patternm.c' is in a 
subdirectory,
lib/Makefile.am:174: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'

[... snipped ...]

../../scripts/gcc.pl "gcc -Wchar-subscripts -Wcomment -Wformat -Wnonnull 
-Wimplicit-int -Wimplicit-function-declaration -Wimplicit -Wmain 
-Wmissing-braces -Wparentheses -Wsequence-point -Wreturn-type -Wswitch 
-Wtrigraphs -Wunused-function -Wunused-label -Wunused-variable -Wunused-value 
-Wuninitialized -Wunknown-pragmas -Wundef -Wendif-labels -Wshadow 
-Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Waggregate-return 
-Wstrict-prototypes -Wmissing-noreturn -Wnested-externs -Wunused-local-typedefs 
-Wredundant-decls -Wno-pointer-sign" -DHAVE_CONFIG_H -I. -I../..-DINIT_RM 
--sec-prefix=.init.rm -I../.. --freestanding -fno-pic -fno-PIC -fno-pie 
-fno-PIE  -fno-dse -fno-pie -no-pie -Os -fomit-frame-pointer 
-mpreferred-stack-boundary=2 --freestanding -falign-functions=15 
-I../mb_template_bios -I.. -I../../lib -DCONFIG_APM_SUPPORT 
-DCONFIG_MOUSE_SUPPORT -DCONFIG_PCI_SUPPORT -DCONFIG_PNP_SUPPORT 
-DCONFIG_SMI_SUPPORT -DCONFIG_SMP_SUPPORT -DCONFIG_ACPI_SUPPORT 
-DCONFIG_MB_GA_686DLX_SU
 PPORT -DCONFIG_INTEL_7180 -m32 -march=i386 -MT libinit_rm_a-print.o -MD -MP 
-MF .deps/libinit_rm_a-print.Tpo -c -o libinit_rm_a-print.o `test -f 
'../mb_template_bios/print.c' || echo './'`../mb_template_bios/print.c
mv -f .deps/libinit_rm_a-print.Tpo .deps/libinit_rm_a-print.Po
../../scripts/gcc.pl "gcc -Wchar-subscripts -Wcomment -Wformat -Wnonnull 
-Wimplicit-int -Wimplicit-function-declaration -Wimplicit -Wmain 
-Wmissing-braces -Wparentheses -Wsequence-point -Wreturn-type -Wswitch 
-Wtrigraphs -Wunused-function -Wunused-label -Wunused-variable -Wunused-value 
-Wuninitialized -Wunknown-pragmas -Wundef -Wendif-labels -Wshadow 
-Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Waggregate-return 
-Wstrict-prototypes -Wmissing-noreturn -Wnested-externs -Wunused-local-typedefs 
-Wredundant-decls -Wno-pointer-sign" -DHAVE_CONFIG_H -I. -I../..-DINIT_RM 
--sec-prefix=.init.rm -I../.. --freestanding -fno-pic -fno-PIC -fno-pie 
-fno-PIE  -fno-dse -fno-pie -no-pie -Os -fomit-frame-pointer 
-mpreferred-stack-boundary=2 --freestanding -falign-functions=15 
-I../mb_template_bios -I.. -I../../lib -DCONFIG_APM_SUPPORT 
-DCONFIG_MOUSE_SUPPORT -DCONFIG_PCI_SUPPORT -DCONFIG_PNP_SUPPORT 
-DCONFIG_SMI_SUPPORT -DCONFIG_SMP_SUPPORT -DCONFIG_ACPI_SUPPORT 
-DCONFIG_MB_GA_686DLX_SU
 PPORT -DCONFIG_INTEL_7180 -m32 -march=i386 -MT libinit_rm_a-vsprintf.o -MD -MP 
-MF .deps/libinit_rm_a-vsprintf.Tpo -c -o libinit_rm_a-vsprintf.o `test -f 
'../mb_template_bios/vsprintf.c' || echo './'`../mb_template_bios/vsprintf.c
mv -f .deps/libinit_rm_a-vsprintf.Tpo .deps/libinit_rm_a-vsprintf.Po
../../scripts/gcc.pl "gcc -Wchar-subscripts -Wcomment -Wformat -Wnonnull 
-Wimplicit-int -Wimplicit-function-declaration -Wimplicit -Wmain 
-Wmissing-braces -Wparentheses -Wsequence-point -Wreturn-type -Wswitch 
-Wtrigraphs -Wunused-function -Wunused-label -Wunused-variable -Wunused-value 
-Wuninitialized -Wunknown-pragmas -Wundef -Wendif-labels -Wshadow 
-Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Waggregate-return 
-Wstrict-prototypes -Wmissing-noreturn -Wnested-externs -Wunused-local-typedefs 
-Wredundant-decls -Wno-pointer-sign" -DHAVE_CONFIG_H -I. -I../..-DINIT_RM 
--sec-prefix=.init.rm -I../.. --freestanding -fno-pic -fno-PIC -fno-pie 
-fno-PIE  -fno-dse -fno-pie -no-pie -Os -fomit-frame-pointer 
-mpreferred-stack-boundary=2 --freestanding -falign-functions=15 
-I../mb_template_bios -I.. -I../../lib -DCONFIG_APM_SUPPORT 
-DCONFIG_MOUSE_SUPPORT -DCONFIG_PCI_SUPPORT -DCONFIG_PNP_SUPPORT 
-DCONFIG_SMI_SUPPORT -DCONFIG_SMP_SUPPORT -DCONFIG_ACPI_SUPPORT 
-DCONFIG_MB_GA_686DLX_SU
 PPORT -DCONFIG_INTEL_7180 -m32 -march=i386 -MT libinit_rm_a-debug.o -MD -MP 
-MF .deps/libinit_rm_a-debug.Tpo -c -o libinit_rm_a-debug.o `test -f 
'../mb_template_bios/debug.c' || echo './'`../mb_template_bios/debug.c
mv -f .deps/libinit_rm_a-debug.Tpo .deps/libinit_rm_a-debug.Po
../../scripts/gcc.pl "gcc -Wchar-subscripts -Wcomment -Wformat -Wnonnull 
-Wimplicit-int -Wimplicit-function-declaration -Wimplicit -Wmain 
-Wmissing-braces -Wparentheses 

Bug#902458: django-countries: FTBFS in buster/sid ("BAD" is not a valid choice)

[Santiago Vila]

Package: src:django-countries
Version: 5.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py

[... snipped ...]

copying django_countries/ioc_data.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries
copying django_countries/__init__.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries
creating 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/test_fields.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/test_widgets.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/test_tags.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/custom_countries.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/test_countries.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/test_settings.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/settings.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/models.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/test_drf.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/forms.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/test_admin_filters.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
copying django_countries/tests/__init__.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/tests
creating 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/templatetags
copying django_countries/templatetags/__init__.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/templatetags
copying django_countries/templatetags/countries.py -> 
/<>/.pybuild/cpython3_3.6_django-countries/build/django_countries/templatetags
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
set -e; \
for python in python2.7 python3.6; do \
  PYTHONPATH="." DJANGO_SETTINGS_MODULE=django_countries.tests.settings $python 
/usr/bin/django-admin test django_countries.tests;\
done
..F.
==
FAIL: test_multi_deserialize_invalid (django_countries.tests.test_drf.TestDRF)
--
Traceback (most recent call last):
  File "/<>/django_countries/tests/test_drf.py", line 147, in 
test_multi_deserialize_invalid
['"BAD" is not a valid choice.'])
AssertionError: {1: [ErrorDetail(string=u'"BAD" is not a valid choice.', 
code=u'invalid_choice')]} != [u'"BAD" is not a valid choice.']

--
Ran 144 tests in 0.442s

FAILED (failures=1)
Creating test database for alias 'default'...
System check identified no issues (0 silenced).
Destroying test database for alias 'default'...
debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:10: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902453: aff4: FTBFS in buster/sid

[Santiago Vila]

Package: src:aff4
Version: 0.24.post1-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep  --with autoreconf,python2 --parallel
   dh_update_autotools_config -i -O--parallel
   dh_autoreconf -i -O--parallel
configure.ac:104: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2601: _AC_COMPILE_IFELSE is expanded from...
../../lib/autoconf/general.m4:2617: AC_COMPILE_IFELSE is expanded from...
m4/uriparser.m4:1: URIPARSER_CHECK is expanded from...
configure.ac:104: the top level
configure.ac:104: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2601: _AC_COMPILE_IFELSE is expanded from...

[... snipped ...]

## --- ##
## confdefs.h. ##
## --- ##

/* confdefs.h */
#define PACKAGE_NAME "AFF4"
#define PACKAGE_TARNAME "aff4"
#define PACKAGE_VERSION "0.1"
#define PACKAGE_STRING "AFF4 0.1"
#define PACKAGE_BUGREPORT "aff4-us...@googlegroups.com"
#define PACKAGE_URL "http://www.aff4.org/;
#define PACKAGE "aff4"
#define VERSION "0.1"
#define HAVE_LIBRAPTOR2 1
#define HAVE_LIBUUID 1
#define HAVE_LIBZ 1
#define HAVE_LIBGLOG 1
#define HAVE_LIBSNAPPY 1
#define HAVE_LIBPTHREAD 1
#define STDC_HEADERS 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_MEMORY_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define HAVE_FCNTL_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_UNISTD_H 1
#define SIZEOF_OFF_T 8
#define SIZEOF_SIZE_T 8
#define HAVE_DLFCN_H 1
#define LT_OBJDIR ".libs/"

configure: exit 1
dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking returned exit code 1
debian/rules:14: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory '/<>'
debian/rules:7: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

Bug#902452: Kamailio TLS module in Debian Stretch is unusable

[Pali Rohár]

Package: kamailio-tls-modules
Version: 4.4.4-2+deb9u1
Severity: grave

After installation of kamailio-tls-modules package on Debian Stretch and
enabling TLS support in kamailio.cfg via #!define WITH_TLS I'm just
getting following fatal error (in syslog):

Jun 27 00:19:57 pali /usr/sbin/kamailio[15055]: : tls [tls_init.c:651]: 
init_tls_h(): ERROR: tls: init_tls_h: openssl compile options mismatch: library 
has kerberos support disabled and Kamailio tls enabled (unstable 
configuration)#012 (tls_force_run in kamailio.cfg will override this check)
Jun 27 00:19:57 pali /usr/sbin/kamailio[15055]: CRITICAL:  [main.c:2592]: 
main(): could not initialize tls, exiting...

And kamailio refuse to start.

Therefore current version of kamailio-tls-modules package in Debian
Stretch is unusable as TLS support which it provides cannot be enabled.

It looks like this package needs to be (re)compiled against correct
version of openssl with correct configure options or it needs to runtime
depends on correct version of openssl libraries.

As package currently does not work at all, I'm marking this issue with
severity grave.

-- 
Pali Rohár
pali.ro...@gmail.com


signature.asc
Description: PGP signature

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

[Debian Bug Tracking System]

Your message dated Tue, 26 Jun 2018 22:20:05 +
with message-id 
and subject line Bug#899691: fixed in slice 1.3.8-14
has caused the Debian Bug report #899691,
regarding slice: Invalid maintainer address 
pkg-wml-maintain...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of slice,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: slice
Source-Version: 1.3.8-14

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

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

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated slice 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: Tue, 26 Jun 2018 23:59:12 +0200
Source: slice
Binary: slice
Architecture: source all
Version: 1.3.8-14
Distribution: unstable
Urgency: medium
Maintainer: Axel Beckert 
Changed-By: Axel Beckert 
Description:
 slice  - Extract out pre-defined slices of an ASCII file
Closes: 899691
Changes:
 slice (1.3.8-14) unstable; urgency=medium
 .
   * Update Vcs-* headers for packaging repository moving to Salsa.
   * Drop one-man-team from Maintainer field, set myself personally there
 instead. (Closes: #899691)
   * Declare compliance with Debian Policy 4.1.4.
 + Update debian/copyright format URL to HTTPS.
   * Switch Homepage header to HTTPS. Thanks DUCK for the hint!
   * Drop no more needed Testsuite field from debian/control.
   * Bump debhelper compatibility level to 11.
 + Update versioned build-dependency on debhelper accordingly.
 + Update .gitignore to ignore additional build artefacts.
   * Add (mostly redundant) DEP12 debian/upstream/metadata file.
Checksums-Sha1:
 aced651bbd5ecdcdd74e112d0082cb6a54f50b58 1897 slice_1.3.8-14.dsc
 e906579d6a6f012491c5f5fb3ecc0c8cea11715a 7008 slice_1.3.8-14.debian.tar.xz
 62e9a7da99968a6276b152d5dd4cc7fc885675a6 24632 slice_1.3.8-14_all.deb
 6d998c6f9744ccdc0b4dd1efde7675c6ef7cbab9 5490 

Bug#899124: fa-solid-900.ttf symlinked as fontawesome-webfont.ttf

[Alexis Murzeau]

Le 26/06/2018 à 04:13, vasudev-debian a écrit :
> I'll have a look. if possible clone from team repo and raise a pr on it.
> 

I've created 3 PR at [0], one for each branch (in this order: upstream,
pristine-tar and master).
The 5.0.10+really4.7.0~dfsg orig tar I imported is the same as the one
used for 4.7.0~dfsg.
Debian/watch file tracks the v4 branch (ignoring v5.*)
I've also added a autopkgtest test to ensure symlinks are not broken.

[0] https://salsa.debian.org/fonts-team/fonts-font-awesome/merge_requests

Le 26/06/2018 à 09:26, Sean Whitton a écrit :
>
> The git history is up to you but resetting the changelog seems like a
> really bad idea -- it is confusing to see that there are uploads to the
> archive that are not present in the changelog.
>
> I think you should at least retain d/changelog, even if you reset
> everything else (personally, I would keep all the git history).
>

I finally kept the full changelog and git history, to not lie the past
:) if someone wonders what happened.
Thanks for your advices.

-- 
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F



signature.asc
Description: OpenPGP digital signature

Processed: tagging 899962

[Debian Bug Tracking System]

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

> tags 899962 + pending
Bug #899962 [src:eperl] eperl: Invalid maintainer address 
pkg-wml-maintain...@lists.alioth.debian.org
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 899691

[Debian Bug Tracking System]

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

> tags 899691 + pending
Bug #899691 [src:slice] slice: Invalid maintainer address 
pkg-wml-maintain...@lists.alioth.debian.org
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#901952: new info

[Tomasz Buchert]

Control: reassign 901952 tar 1.30+dfsg-1

On 26/06/18 20:23, Tomasz Buchert wrote:
> On 20/06/18 21:18, Hans-Christoph Steiner wrote:
> >
> > [...]
>
> This seems to be a regression caused by tar.
>
> I can successfully checkout the tarball, but with the version tar_1.29b-2.
> When I install tar_1.30+dfsg-1, I cannot checkout anymore.
>
> I guess we'll need to find the real cause in tar then.

I believe I have a repro case extracted from this bug report showing
that #897653 was not actually fixed. It can be downloaded from:
http://ivyzdokx5queplps.onion/repro.tar.xz

It has a number of files generated with tar 1.30, with all
combinations of reproducibility related flags and none of them
reproduces the tarball produced by the version 1.29.

I'm reassigning this to tar.


signature.asc
Description: PGP signature

Processed: Re: new info

[Debian Bug Tracking System]

Processing control commands:

> reassign 901952 tar 1.30+dfsg-1
Bug #901952 [pristine-tar] xdelta: expected from file 
(/tmp/pristine-tar.SljdkfANnj/recreatetarball) of length 7557120 bytes
Bug reassigned from package 'pristine-tar' to 'tar'.
No longer marked as found in versions pristine-tar/1.44.
No longer marked as fixed in versions pristine-tar/1.38.
Bug #901952 [tar] xdelta: expected from file 
(/tmp/pristine-tar.SljdkfANnj/recreatetarball) of length 7557120 bytes
Marked as found in versions tar/1.30+dfsg-1.

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

Bug#900248: nvidia-driver: update to 390.59 breaks direct rendering

[Luca Boccassi]

On Sun, 2018-06-24 at 11:49 +0200, floris wrote:
> > 
> > What about the following 
> > /etc/nvidia/current/nvidia-drm-outputclass.conf
> > 
> > ---
> > Section "Files"
> > ModulePath "/usr/lib/xorg/modules/linux"
> > ModulePath "/usr/lib/xorg/modules"
> > EndSection
> > 
> > Section "OutputClass"
> > Identifier "nvidia"
> > MatchDriver"nvidia-drm"
> > Driver "nvidia"
> > EndSection
> > ---
> > 
> > That seems to work for stable ... what about sid?
> > 
> > 
> > Andreas
> 
> Hmmm, this should work, but the NVidia glx module will always be
> loaded 
> for all screens by the xserver. This will break a multiseat system
> with 
> multiple gpu vendors and maybe other glvnd dispatch goodness.

Tried this with nonglvnd + optimus + bumblebee and it works fine as far
as I can see

> Is the following situation a possibility?
> 
> Stable -> nvidia-driver (up to version 390.xx in backports),
> compatible 
> with all versions of the xserver
>   This version is shipped with a separate Files section in 
> nvidia-drm-outputclass.conf
>   If xserver 1.20 is in backports, this version can be upgraded to
> match 
> the new Testing/Sid version
> 
> Testing and Sid -> nvidia-legacy-390xx-driver, xserver > 1.20
>  -> nvidia-driver (version > 396.xx), xserver > 1.20
>   These versions will have the ModulePath option in the OutputClass 
> section. (and we can drop the glx-alternative system)
> ---
> Floris

-- 
Kind regards,
Luca Boccassi

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

Bug#902410: redis: CVE-2018-12326

[Chris Lamb]

Hi security-team,

Not sure why but in an automatic update of data/CVE/list,
CVE-2018-12326 was marked as being fixed in DSA-4230-1. However, this
only fixes CVE-2018-11218 & CVE-2018-11219.

As I understand it, this therefore means we need to do the following:

 a) Release 3:3.2.6-3+deb9u2 with the additional change for
CVE-2018-12326?

 b) Update the CVE list manually?

 --- a/data/CVE/list
 +++ b/data/CVE/list
 @@ -1461,7 +1461,6 @@ CVE-2018-12327 (Stack-based buffer overflow in ntpq 
and ntpdc of NTP version 4.2
 NOTE: 
https://gist.github.com/fakhrizulkifli/9b58ed8e0354e8deee50b0eebd1c011f
 NOTE: Negligible security impact
  CVE-2018-12326 (Buffer overflow in redis-cli of Redis before 4.0.10 and 
5.x before 5.0 ...)
 -   {DSA-4230-1}
 - redis 5:4.0.10-1 (bug #902410)
 NOTE: 
https://gist.github.com/fakhrizulkifli/f831f40ec6cde4f744c552503d8698f0
 NOTE: 
https://github.com/antirez/redis/commit/9fdcc15962f9ff4baebe6fdd947816f43f730d50

 c) ... & ensure that this doesn't clobber the 3:3.2.6-3+deb9u2 upload in
stretch-proposed-updates (what happens in this case out of
interest?)


Best wishes,

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

Bug#902448: timidity: Breaks: timidity-daemon (>= 2.14.0-1~) but 2.14.0-5 is to be installed

[Sven Joachim]

Package: timidity
Version: 2.14.0-5
Severity: serious

In this version, timidity-daemon has become uninstallable:

,
| $ LANG=C aptitude -s install timidity-daemon
| The following packages will be upgraded: 
|   timidity{b} timidity-daemon 
| The following packages are RECOMMENDED but will NOT be installed:
|   fluid-soundfont-gm 
| 2 packages upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
| Need to get 676 kB of archives. After unpacking 49.2 kB will be used.
| The following packages have unmet dependencies:
|  timidity : Breaks: timidity-daemon (>= 2.14.0-1~) but 2.14.0-5 is to be 
installed
| The following actions will resolve these dependencies:
| 
|  Keep the following packages at their current version:
| 1) timidity [2.14.0-4 (now)]  
| 2) timidity-daemon [2.14.0-4 (now)]   
| 
| 
| 
| Accept this solution? [Y/n/q/?] q
| Abandoning all efforts to resolve these dependencies.
| Abort.
`

Most likely you meant to break timidity-daemon (<= 2.14.0-1~) rather
than (>= 2.14.0-1~).


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

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

Bug#902185:

[Kyle Edwards]

On 06/26/2018 04:45 PM, Christopher Obbard wrote:

A reinstall of Debian on my main PC seemed to fix it.


I was able to fix it by booting into a recovery shell and running:

$ apt-get install systemd

which updates systemd to the latest version. I then ran

$ apt-get install

to finish reconfiguring udev.

YMMV.


My laptop boots to the WM but with no keyboard/mouse.


This is because udev is failing to start. A text-based recovery console 
will still work, and udev will work properly again once systemd is fully 
upgraded.



This is a grave bug.


Agreed.

Bug#902185:

[Christopher Obbard]

this has happened to me on both my laptop and pc when doing an upgrade.

A reinstall of Debian on my main PC seemed to fix it.

My laptop boots to the WM but with no keyboard/mouse.

This is a grave bug.

Bug#902445: libclojure-java: Upgrading fails in preinst

[Adrian Bunk]

Package: libclojure-java
Version: 1.9.0-4
Severity: serious

On 1.9.0-2 -> 1.9.0-4 upgrade:

Preparing to unpack .../00-libclojure-java_1.9.0-4_all.deb ...
update-alternatives: error: no alternatives for clojure
dpkg: error processing archive 
/tmp/apt-dpkg-install-Z53q9V/00-libclojure-java_1.9.0-4_all.deb (--unpack):
 new libclojure-java package pre-installation script subprocess returned error 
exit status 2

Bug#902439: libpython3.7-testsuite: fails during install

[Paul Gevers]

Package: libpython3.7-testsuite
Version: 3.7.0~rc1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear Python maintainers,

python3.7 is blocked¹ from migration to testing because it fails its
piuparts (and autopkgtest) test with the error below. This happens
during package installation.

Please fix libpython3.7-testsuite.

Paul

¹ https://qa.debian.org/excuses.php?package=python3.7

https://piuparts.debian.org/sid/fail/libpython3.7-testsuite_3.7.0~rc1-3.log

  Preparing to unpack .../libpython3.7-testsuite_3.7.0~rc1-3_all.deb ...
  Unpacking libpython3.7-testsuite (3.7.0~rc1-3) ...
  Setting up libpython3.7-testsuite (3.7.0~rc1-3) ...
File "/usr/lib/python3.7/idlelib/idle_test/template.py", line 3
  from idlelib import
^
  SyntaxError: invalid syntax

  dpkg: error processing package libpython3.7-testsuite (--configure):
   installed libpython3.7-testsuite package post-installation script
subprocess returned error exit status 1
  Errors were encountered while processing:
   libpython3.7-testsuite





signature.asc
Description: OpenPGP digital signature

Bug#901377: marked as done (skimage: FTBFS and Debci failure with NumPy 1.14)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jun 2018 18:35:55 +
with message-id 
and subject line Bug#901377: fixed in skimage 0.14.0-1
has caused the Debian Bug report #901377,
regarding skimage: FTBFS and Debci failure with NumPy 1.14
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.)


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

Source: skimage
Version: 0.13.1-3
Severity: serious
Tags: ftbfs
User: debian...@lists.debian.org
Usertags: needs-update

Hi Maintainer

Since the recent upload of python-numpy on 2018-05-05, skimage has been 
failing its autopkgtests [1] and has now also started to FTBFS in 
unstable [2] with several errors similar to the following:


==
ERROR: skimage.io.tests.test_mpl_imshow.test_uint8
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in 
runTest

self.test(*self.arg)
  File 
"/build/1st/skimage-0.13.1/debian/tmp/usr/lib/python2.7/dist-packages/skimage/io/tests/test_mpl_imshow.py", 
line 48, in test_uint8

ax_im = io.imshow(im8)
  File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__
self.gen.next()
  File 
"/build/1st/skimage-0.13.1/debian/tmp/usr/lib/python2.7/dist-packages/skimage/_shared/_warnings.py", 
line 121, in expected_warnings

raise ValueError('Unexpected warning: %s' % str(warn.message))
ValueError: Unexpected warning: Conversion of the second argument of 
issubdtype from `float` to `np.floating` is deprecated. In future, it 
will be treated as `np.float64 == np.dtype(float).type`.

 >> begin captured logging << 
matplotlib.font_manager: DEBUG: findfont: Matching 
:family=sans-serif:style=normal:variant=normal:weight=normal:stretch=normal:size=10.0 
to DejaVu Sans 
(u'/usr/share/matplotlib/mpl-data/fonts/ttf/DejaVuSans.ttf') with score 
of 0.05

- >> end captured logging << -

Regards
Graham


[1] https://ci.debian.net/packages/s/skimage/unstable/amd64/
[2] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/skimage.html
--- End Message ---
--- Begin Message ---
Source: skimage
Source-Version: 0.14.0-1

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

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

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

Debian distribution maintenance software
pp.
Yaroslav Halchenko  (supplier of updated skimage 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: Mon, 25 Jun 2018 12:26:51 -0400
Source: skimage
Binary: python-skimage python3-skimage python-skimage-doc python-skimage-lib 
python3-skimage-lib
Architecture: source all amd64
Version: 0.14.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Yaroslav Halchenko 
Description:
 python-skimage - Python modules for image processing
 python-skimage-doc - Documentation and examples for scikit-image
 python-skimage-lib - Optimized low-level algorithms for scikit-image
 python3-skimage - Python 3 modules for image processing
 python3-skimage-lib - Optimized low-level algorithms for Python 3 scikit-image
Closes: 901377
Changes:
 skimage (0.14.0-1) unstable; urgency=medium
 .
   * Fresh upstream release
 - should resolve FTBFS due to incompatibility with NumPy 1.14
   (Closes: #901377)
   * d/patches
 - refreshed patches skipping on some archs.  Use testing.skipif instead
   of explicit import of skipif into the namespace
 - removed remove_deprecated_box-forced.patch - was CPed from upstream
 - added 0001-BF-perform-computation-serially-with-a-warning-if-da.patch
   to make skimage not crash whenever dask is not available
 - added deb_no_dask_in_setup to not demand dask at setup.py leve since
   not available for python2 in Debian
   * d/tests,control
 - upstream uses pytest instead of nose now
   * d/control
 - recommend and b-depend on 

Bug#901952: new info

[Tomasz Buchert]

On 20/06/18 21:18, Hans-Christoph Steiner wrote:
>
> [...]

This seems to be a regression caused by tar.

I can successfully checkout the tarball, but with the version tar_1.29b-2.
When I install tar_1.30+dfsg-1, I cannot checkout anymore.

I guess we'll need to find the real cause in tar then.


signature.asc
Description: PGP signature

Bug#902185: (no subject)

[Kyle Edwards]

This bug broke my Sid instance, I had to use a recovery shell to 
manually upgrade systemd because udev wouldn't start. This is a 
system-breaking bug.

Processed: your mail

[Debian Bug Tracking System]

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

> severity 902401 normal
Bug #902401 [src:gfsview] gfsview: missing source: debian/Makefile.in
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#902401: gfsview: missing source: debian/Makefile.in

[Anton Gladky]

severity -1 normal

Hello Helmut,

thank you for bug report. Makefile.in was needed for some reasons.
If it will be removed, not sure the package will compile, needs to be
checked. Anyway, the file is in a human-readable format, though generated.
I do not think there are some legal problems with it. Thus I have
reduced the bug`s severity.

There are also no problems with the license of all files including debian/*
files. I never (or extremely rarely) put the license of debian-files explicitly
because according to Debian Social Contract (2):

> "We will give back to the free software community"

So all of my work (mostly in debian/*) is compatible with upstream
license by default.

Anyway, thanks for double check the package. If you want, feel free
to join as the package maintainer, because the package is "semi-orphaned".
The only maintainer listed in the "Uploaders-filed" is the upstream author
and is not too much active in Debian.

Best regards

Anton


2018-06-26 6:16 GMT+02:00 Helmut Grohne :
> Source: gfsview
> Version: 20121130+dfsg-5
> Severity: serious
> Justification: missing source
>
> While trying to fix gfsview, I noticed that the source of gfsview is
> incomplete. debian/Makefile.in is quite obviously generated from
> debian/Makefile.am, but debian/Makefile.am is missing. I'm not sure what
> this file is used for. Potentially, just deleting it is sufficient.
>
> Looking further debian/copyright assigns the copyright of debian/* to
> the National Institute of Water and Atmospheric Research. According to
> debian/changelog and the git logs, Anton Gladky should somehow be
> visible in debian/copyright unless he specifically assigns his
> copyright. This seems strange at least.
>
> Given these findings, I suggest doing a NEW-like review by ftp masters.
>
> Helmut
>
> --
> debian-science-maintainers mailing list
> debian-science-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 895235 https://gitlab.gnome.org/GNOME/pango/issues/301
Bug #895235 [libpango1.0-dev] "pkg-config --libs pango" incorrectly contains 
-lfribidi
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/pango/issues/301'.
> thanks
Stopping processing here.

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

Bug#902424: closed by Apollon Oikonomopoulos (Bug#902424: fixed in mongo-cxx-driver-legacy 1.1.3-2)

[Santiago Vila]

Thanks for fixing this so quickly!

I forgot to say that there is a simple way to avoid this kind of bugs
to propagate to testing: you can upload in source only form by doing
"dpkg-buildpackage -S". Give it a try some day.

Thanks.

Bug#902424: marked as done (mongo-cxx-driver-legacy: FTBFS when built with dpkg-buildpackage -A)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jun 2018 15:34:45 +
with message-id 
and subject line Bug#902424: fixed in mongo-cxx-driver-legacy 1.1.3-2
has caused the Debian Bug report #902424,
regarding mongo-cxx-driver-legacy: FTBFS when built with dpkg-buildpackage -A
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.)


-- 
902424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mongo-cxx-driver-legacy
Version: 1.1.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
install -d debian/.debhelper/bucket/files
cp -an --reflink=auto 
src/third_party/gtest-1.7.0/build-aux/config.guess 
debian/.debhelper/bucket/files/9be3de218833c076786b919dc34aab691611f4cd73316e7705f2673e2c41921b.tmp
mv 
debian/.debhelper/bucket/files/9be3de218833c076786b919dc34aab691611f4cd73316e7705f2673e2c41921b.tmp
 
debian/.debhelper/bucket/files/9be3de218833c076786b919dc34aab691611f4cd73316e7705f2673e2c41921b
cp -f /usr/share/misc/config.guess 
./src/third_party/gtest-1.7.0/build-aux/config.guess
cp -an --reflink=auto src/third_party/gtest-1.7.0/build-aux/config.sub 
debian/.debhelper/bucket/files/e308ae7f7f524bd790f8d4457c7c0a30f84034dd0b7d4388daca24275db4.tmp
mv 
debian/.debhelper/bucket/files/e308ae7f7f524bd790f8d4457c7c0a30f84034dd0b7d4388daca24275db4.tmp
 
debian/.debhelper/bucket/files/e308ae7f7f524bd790f8d4457c7c0a30f84034dd0b7d4388daca24275db4
cp -f /usr/share/misc/config.sub 
./src/third_party/gtest-1.7.0/build-aux/config.sub
   dh_autoreconf -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
# Backup directories contained sources that should not be used.

[... snipped ...]

Chmod("tmp/include/mongo/util/time_support.h", 0644)
Creating 'build/linux2/c++11_on/ssl/mongo/version.h'
Install file: "build/linux2/c++11_on/ssl/mongo/version.h" as 
"tmp/include/mongo/version.h"
Chmod("tmp/include/mongo/version.h", 0644)
scons: done building targets.
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
install -d debian/.debhelper/generated/libmongoclient-dev
install -d debian/.debhelper/generated/libmongoclient0
install -d debian/.debhelper/generated/mongodb-dev
# Move generated header files to the arch-specific include path
install -d 
"/<>/debian/libmongoclient-dev/usr/include/${DEB_HOST_MULTIARCH}/mongo"
mv /<>/debian/libmongoclient-dev/usr/include/mongo/config.h \
/<>/debian/libmongoclient-dev/usr/include/mongo/version.h \

"/<>/debian/libmongoclient-dev/usr/include/${DEB_HOST_MULTIARCH}/mongo"
mv: cannot stat 
'/<>/debian/libmongoclient-dev/usr/include/mongo/config.h': No 
such file or directory
mv: cannot stat 
'/<>/debian/libmongoclient-dev/usr/include/mongo/version.h': No 
such file or directory
debian/rules:59: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<>'
debian/rules:9: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


Hint: Try splitting override_dh_install into override_dh_install-indep
and override_dh_install-arch.

Thanks.
--- End Message ---
--- Begin Message ---
Source: mongo-cxx-driver-legacy
Source-Version: 1.1.3-2

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

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated 
mongo-cxx-driver-legacy 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, 26 Jun 2018 17:52:57 

Processed: Re: Bug#902421: wicd-daemon: silently keeps and uses obsolete, possibly insecure config in /etc/wicd/wireless-settings.conf

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #902421 [wicd-daemon] wicd-daemon: silently keeps and uses obsolete, 
possibly insecure config in /etc/wicd/wireless-settings.conf
Severity set to 'normal' from 'grave'
> tag -1 + moreinfo
Bug #902421 [wicd-daemon] wicd-daemon: silently keeps and uses obsolete, 
possibly insecure config in /etc/wicd/wireless-settings.conf
Added tag(s) moreinfo.

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

Bug#902421: wicd-daemon: silently keeps and uses obsolete, possibly insecure config in /etc/wicd/wireless-settings.conf

[Axel Beckert]

Control: severity -1 normal
Control: tag -1 + moreinfo

Hi Vincent,

Vincent Lefevre wrote:
> Severity: grave
> Tags: security
> Justification: user security hole
> 
> I'm using eduroam, and instead of keeping only one config associated
> with it (e.g. [essid:eduroam]), wicd creates many of them in
> /etc/wicd/wireless-settings.conf (based on the bssid instead of the
> essid,

Yes, this is by design.

Are you aware that you need to explicitly configure if a configuration
needs to be solely based on the ESSID? It's called "use these settings
for all wifis with this ESSID" or similar.

And IMNSHO it's a security feature and not a bug that wicd does use
only the BSSID by default. That way credentials can't be leaked to to
rogue access points which share the same ESSID (which is easy to do).

> even though wicd seems to ignore the bssid when searching for
> a matching config),

If you set that flag, of course it does.

> and when one updates the eduroam config, some old configs are not
> updated, and wicd can randomly use them later.

In which case did this happen? With an ESSID where you had the "use
these settings for all wifis with this ESSID" flag set or not? In the
latter case it should update all of them (or only keep one and remove
the remaining ones with the same ESSID), in the former it shouldn't.
(→ moreinfo)

Downgrading to the default severity at least until the specific
settings under which this happened, are clarified.

> I noticed that after a password update: I got a connection failure
> due to an old config with an old password. But there's the same issue
> with the certificate (ca_cert field). In my case, some old configs
> that became insecure after a security hole was found in the protocol
> were still used by wicd, which could yield a leak of my password.

Am I right that you say that it's not an outdated password which might
be leaked, but the current password which is sent in an insecure way,
like WEP instead of WPA? (But then I wonder: Why is the WPA password
sent via WEP? IIRC WICD stores them per encryption method. And I don't
think that sending no more valid passwords is a security threat that
validates RC severity.)

Once again: This depends a lot on your settings (see above) and
depending on your settings. It should not happen with the setting "use
these settings for all wifis with this ESSID", but it is expected to
happen (and a security feature) if that flag is not set.

> Note: The UI just presents the essid, so that the user will generally
> not know what's going on.

Which UI? WICD has several UIs (Gtk, Curses, CLI) and you filed that
bug report against wicd-daemon. (→ moreinfo, too)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#901377: ping (was: Re: skimage: FTBFS and Debci failure with NumPy 1.14)

[Yaroslav Halchenko]

FWIW -- about to upload, cosmetics now

On Mon, 25 Jun 2018, Graham Inggs wrote:

> On 25 June 2018 at 18:21, Yaroslav Halchenko  wrote:
> > I am loosely involved and highly interested ;-)  If someone could help
> > maintaining it, I would appreciate.

> > meanwhile since there were no other activity regarding this issue, I
> > will look into updating it for 0.14.0

> In case you didn't receive Lumin's earlier reply:

> On 25 June 2018 at 13:45, Lumin  wrote:
> > I'm working on this. It would take days for me to finish it
> > due to my final terms... But I think it doesn't matter because
> > we still have a month until AUTORM.

> > https://salsa.debian.org/lumin-guest/skimage/commits/master


-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#902281: libgsl23: ABI breakage due to removed symbols

[Niko Tyni]

On Tue, Jun 26, 2018 at 08:37:58AM -0500, Dirk Eddelbuettel wrote:
> On 26 June 2018 at 10:12, Niko Tyni wrote:

> | For the record, the Perl GSL bindings package libmath-gsl-perl (can be
> | made to) work without the deprecated symbols too. It just needs a rebuild,
> | and forcing that rebuild (and the associated dependency metadata updates)
> | is the main point of SONAME bumps. 
> | 
> | So please don't feel obliged to carry those symbols forever because of us.
> 
> I like to be similar to upstream, so consider this to be a simple but
> forceful nudge towards that rebuild on your side.

The way to remove symbols from a shared library in Debian (or otherwise
change its ABI in an incompatible way) is to upload a version with SONAME
bumped to experimental, check that reverse dependencies still build,
file bugs if they don't, and when everything is ready enough ask for a
transition slot from the release team. They will then handle the rebuilds.

The libmath-gsl-perl package does need a bit of work to become source
compatible with the removal of the deprecated functions. We're already
handling that in #901807 now that this issue brought it to our attention.

> Do we know if any other packages depending on GSL use these?

codesearch.debian.net does give some hits for at least
gsl_sf_legendre_array_size and gsl_linalg_hessenberg. I didn't check
whether they are false positives.

Test rebuilds with the new library version need to be done anyway and
should pinpoint any such issues.

Hope this helps,
-- 
Niko

Bug#901807: libmath-gsl-perl: incompatible with GSL >= 2.5

[Niko Tyni]

On Tue, Jun 26, 2018 at 10:25:06AM +0300, Niko Tyni wrote:

> It looks like the deprecated symbols will be reinstated for now.
> Not sure if we still want to disable them on our side. Probably not.

The gsl maintainer seems keen to remove those symbols in a (near?) future
SONAME bump. Probably best to disable them now on our side after all so
we can handle any resulting fallout sooner.
-- 
Niko

Processed: bug 900051 is forwarded to https://github.com/bestpractical/gnupg-interface/pull/1

[Debian Bug Tracking System]

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

> # commented on the existing PR
> forwarded 900051 https://github.com/bestpractical/gnupg-interface/pull/1
Bug #900051 [libgnupg-interface-perl] libgnupg-interface-perl: 
t/get_public_keys.t fails with gnupg2/2.2.7-1
Set Bug forwarded-to-address to 
'https://github.com/bestpractical/gnupg-interface/pull/1'.
> thanks
Stopping processing here.

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

Bug#902281: libgsl23: ABI breakage due to removed symbols

[Dirk Eddelbuettel]

On 26 June 2018 at 10:12, Niko Tyni wrote:
| On Mon, Jun 25, 2018 at 06:37:21AM -0500, Dirk Eddelbuettel wrote:
|  
| > I seem to have confused myself. I have new 2.5-2 packages which should carry
| > the deprecated symbols, brought back for our use in the eg the Perl GSL 
package.
|  
| Thanks! I can confirm that libmath-gsl-perl works fine again with
| libgsl23_2.5+dfsg-2 from experimental. Please upload the fix to unstable
| too :)

Yes, done between you writing this and me reading it -- experimental was an
oversight left over from when I thought I needed a transition.  Now in
unstable too and this bug you filed is closed by now.
 
| For the record, the Perl GSL bindings package libmath-gsl-perl (can be
| made to) work without the deprecated symbols too. It just needs a rebuild,
| and forcing that rebuild (and the associated dependency metadata updates)
| is the main point of SONAME bumps. 
| 
| So please don't feel obliged to carry those symbols forever because of us.

I like to be similar to upstream, so consider this to be a simple but
forceful nudge towards that rebuild on your side.

Do we know if any other packages depending on GSL use these?
 
| Any user code compiled against libgsl23 and using those symbols would
| of course be similarly affected, and the SONAME bump makes that visible,
| which is preferable to silent breakage at runtime.
| 
| > You have really helpful on this -- much appreciated.
| 
| My pleasure!

Thanks again,  Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#902424: mongo-cxx-driver-legacy: FTBFS when built with dpkg-buildpackage -A

[Santiago Vila]

Package: src:mongo-cxx-driver-legacy
Version: 1.1.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
install -d debian/.debhelper/bucket/files
cp -an --reflink=auto 
src/third_party/gtest-1.7.0/build-aux/config.guess 
debian/.debhelper/bucket/files/9be3de218833c076786b919dc34aab691611f4cd73316e7705f2673e2c41921b.tmp
mv 
debian/.debhelper/bucket/files/9be3de218833c076786b919dc34aab691611f4cd73316e7705f2673e2c41921b.tmp
 
debian/.debhelper/bucket/files/9be3de218833c076786b919dc34aab691611f4cd73316e7705f2673e2c41921b
cp -f /usr/share/misc/config.guess 
./src/third_party/gtest-1.7.0/build-aux/config.guess
cp -an --reflink=auto src/third_party/gtest-1.7.0/build-aux/config.sub 
debian/.debhelper/bucket/files/e308ae7f7f524bd790f8d4457c7c0a30f84034dd0b7d4388daca24275db4.tmp
mv 
debian/.debhelper/bucket/files/e308ae7f7f524bd790f8d4457c7c0a30f84034dd0b7d4388daca24275db4.tmp
 
debian/.debhelper/bucket/files/e308ae7f7f524bd790f8d4457c7c0a30f84034dd0b7d4388daca24275db4
cp -f /usr/share/misc/config.sub 
./src/third_party/gtest-1.7.0/build-aux/config.sub
   dh_autoreconf -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
# Backup directories contained sources that should not be used.

[... snipped ...]

Chmod("tmp/include/mongo/util/time_support.h", 0644)
Creating 'build/linux2/c++11_on/ssl/mongo/version.h'
Install file: "build/linux2/c++11_on/ssl/mongo/version.h" as 
"tmp/include/mongo/version.h"
Chmod("tmp/include/mongo/version.h", 0644)
scons: done building targets.
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
install -d debian/.debhelper/generated/libmongoclient-dev
install -d debian/.debhelper/generated/libmongoclient0
install -d debian/.debhelper/generated/mongodb-dev
# Move generated header files to the arch-specific include path
install -d 
"/<>/debian/libmongoclient-dev/usr/include/${DEB_HOST_MULTIARCH}/mongo"
mv /<>/debian/libmongoclient-dev/usr/include/mongo/config.h \
/<>/debian/libmongoclient-dev/usr/include/mongo/version.h \

"/<>/debian/libmongoclient-dev/usr/include/${DEB_HOST_MULTIARCH}/mongo"
mv: cannot stat 
'/<>/debian/libmongoclient-dev/usr/include/mongo/config.h': No 
such file or directory
mv: cannot stat 
'/<>/debian/libmongoclient-dev/usr/include/mongo/version.h': No 
such file or directory
debian/rules:59: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<>'
debian/rules:9: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


Hint: Try splitting override_dh_install into override_dh_install-indep
and override_dh_install-arch.

Thanks.

Bug#902421: wicd-daemon: silently keeps and uses obsolete, possibly insecure config in /etc/wicd/wireless-settings.conf

[Vincent Lefevre]

Package: wicd-daemon
Version: 1.7.4+tb2-6
Severity: grave
Tags: security
Justification: user security hole

I'm using eduroam, and instead of keeping only one config associated
with it (e.g. [essid:eduroam]), wicd creates many of them in
/etc/wicd/wireless-settings.conf (based on the bssid instead of the
essid, even though wicd seems to ignore the bssid when searching for
a matching config), and when one updates the eduroam config, some
old configs are not updated, and wicd can randomly use them later.

I noticed that after a password update: I got a connection failure
due to an old config with an old password. But there's the same issue
with the certificate (ca_cert field). In my case, some old configs
that became insecure after a security hole was found in the protocol
were still used by wicd, which could yield a leak of my password.

Note: The UI just presents the essid, so that the user will generally
not know what's going on.

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

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

Versions of packages wicd-daemon depends on:
ii  adduser   3.117
ii  dbus  1.12.8-3
ii  debconf   1.5.67
ii  iputils-ping  3:20161105-1
ii  isc-dhcp-client   4.3.5-4
ii  lsb-base  9.20170808
ii  psmisc23.1-1+b1
ii  python2.7.15-3
ii  python-dbus   1.2.8-2
ii  python-gobject-2  2.28.6-13+b1
ii  python-wicd   1.7.4+tb2-6
ii  wireless-tools30~pre9-12+b1
ii  wpasupplicant 2:2.6-17

Versions of packages wicd-daemon recommends:
ii  rfkill 2.32-0.1
ii  wicd-curses [wicd-client]  1.7.4+tb2-6
ii  wicd-gtk [wicd-client] 1.7.4+tb2-6

Versions of packages wicd-daemon suggests:
pn  pm-utils  

Versions of packages wicd depends on:
ii  wicd-curses [wicd-client]  1.7.4+tb2-6
ii  wicd-gtk [wicd-client] 1.7.4+tb2-6

Versions of packages wicd-gtk depends on:
ii  python 2.7.15-3
ii  python-glade2  2.24.0-5.1+b1
ii  python-gtk22.24.0-5.1+b1

Versions of packages wicd-gtk recommends:
ii  menu   2.1.47+b1
ii  policykit-10.105-20
ii  python-notify  0.1.1-4

Versions of packages wicd-curses depends on:
ii  python2.7.15-3
ii  python-urwid  2.0.1-2

Versions of packages wicd-curses recommends:
ii  sudo  1.8.23-1

Versions of packages python-wicd depends on:
ii  net-tools  1.60+git20161116.90da8a0-2
ii  python 2.7.15-3

Versions of packages python-wicd suggests:
ii  ethtool   1:4.16-1
ii  iproute2  4.16.0-4

-- Configuration Files:
/etc/wicd/encryption/templates/active changed [not included]

-- debconf information:
* wicd/users:

Bug#896921: [Pkg-salt-team] Bug#896921: Salt / tornado incompatibility - new upstream release is out with a fix

[Benjamin Drung]

Am Montag, den 25.06.2018, 17:05 +0100 schrieb Shish:
> Looks like 2018.3.1 is out, and the version installed from upstream's
> personal repository no longer has the bug :)
> 
> Specifically, I'm using
> http://repo.saltstack.com/apt/debian/9/amd64/latest/pool/main/s/salt/
> on Buster

The difference between the upstream package and the package in Debian
is that Debian's package uses Python 3 instead of Python 2. Sadly,
tornado 5 is still not supported in salt 2018.3.1 if Python 3 is used.

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
10405 Berlin

Email: benjamin.dr...@profitbricks.com
URL: https://www.profitbricks.de

Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 125506 B
Geschäftsführer: Achim Weiss, Matthias Steinberg, Christoph Steffens

Bug#886048: marked as done (plasma-pa: Depends on gconf)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jun 2018 12:09:21 +
with message-id 
and subject line Bug#886048: fixed in plasma-pa 4:5.13.1-1
has caused the Debian Bug report #886048,
regarding plasma-pa: Depends on gconf
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.)


-- 
886048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plasma-pa
Version: 4:5.10.5-2
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf
Tags: sid buster

Your package depends or build-depends on gconf, but gconf will be
removed from Debian soon.

gconf's last release was about 5 years ago. It has been replaced by
gsettings (provided in Debian by source glib2.0 )

I assume this depends on pulseaudio.

References
--
https://developer.gnome.org/gio/stable/ch34.html
https://developer.gnome.org/gio/stable/GSettings.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: plasma-pa
Source-Version: 4:5.13.1-1

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

Debian distribution maintenance software
pp.
Maximiliano Curia  (supplier of updated plasma-pa 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: Tue, 26 Jun 2018 13:43:20 +0200
Source: plasma-pa
Binary: plasma-pa
Architecture: source
Version: 4:5.13.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Maximiliano Curia 
Description:
 plasma-pa  - Plasma 5 Volume controller
Closes: 886048
Changes:
 plasma-pa (4:5.13.1-1) unstable; urgency=medium
 .
   * New upstream release (5.13.1).
   * Make GConf optional dependency
   * Build without gconf.
 Thanks to Martin Steigerwald for following this, and David Rosca for the 
patch
 (Closes: 886048)
   * Release to unstable
Checksums-Sha1:
 7d6bdd9a63c107cf91efd110c3dc702e49a43af0 2593 plasma-pa_5.13.1-1.dsc
 138d6a63ab7e4f804f3c12b556a9dad936a183fe 89980 plasma-pa_5.13.1.orig.tar.xz
 352cf28430e2d3a3fd8905245131a47a813eeaf5 774 plasma-pa_5.13.1.orig.tar.xz.asc
 c59c29bd02b3e825fab3df547b2af454719b6eae 11868 plasma-pa_5.13.1-1.debian.tar.xz
 2e2859a61417f5e169fb3461b9c22d88a573571e 25694 
plasma-pa_5.13.1-1_source.buildinfo
Checksums-Sha256:
 f8caf17fa1bb51e685fff888c0880338c345961b76a6c305c7c3a21bebf0b0e6 2593 
plasma-pa_5.13.1-1.dsc
 871f02eff33389851581fa29e9ad94de3764356ecfc755a1bc471f2c60eeb362 89980 
plasma-pa_5.13.1.orig.tar.xz
 46e69f7ee6b5540d6b5d992bb669dc653c5a4b35cc5ec505a4951e8178984c9f 774 
plasma-pa_5.13.1.orig.tar.xz.asc
 70e3877f950a4195010257138f0f7811f95c4cc5848b5a180d08df923e8df6ca 11868 
plasma-pa_5.13.1-1.debian.tar.xz
 1eb4aada29c8ef452aecd106b73f7d202edc90e55a7a461416a1a97c19bfe151 25694 
plasma-pa_5.13.1-1_source.buildinfo
Files:
 f4b801526a668675af195354addab2b9 2593 kde optional plasma-pa_5.13.1-1.dsc
 480578bfe139552f2e94b9dfb99693cf 89980 kde optional 
plasma-pa_5.13.1.orig.tar.xz
 a77c2ac5dc3a019785f62be4412c62a6 774 kde optional 
plasma-pa_5.13.1.orig.tar.xz.asc
 b95fe43376849ac58bdc83be72de1fd2 11868 kde optional 
plasma-pa_5.13.1-1.debian.tar.xz
 cf08eb0e76cf514fe82ce69bfa94086f 25694 kde optional 
plasma-pa_5.13.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE+JIdOnQEyG4RNSIVxxl2mbKbIyoFAlsyKTwACgkQxxl2mbKb
IyoBmg/+Lu4r9wddCzsl1IKU1gkn6IHy6g67fXkC/OzhmYazIbxZ3H+miiuKIPK+
fVWvkQiA8L19hxDYAkB4g+B7R7GnQiAkm4pr5LY5ujL+XM9ocA/MOqlG6Gxwc0tn
/vR9ZLUEAY7EqR/ItGfLMYCJBJnryMS6mUoYfJ6XV+buUNZtKaFwpFRcn0CSVXDh
RXPsfDkYDviJwUgllrfG46HgVencaQfSb33MQrM1XHJ5TVlSmCsYgFeKI/ZYusev
R0sEVIjXQwYDOKy0yyXx5ZD0DMy1L44lyJsDyQPtyFFuCMd54YQlxC45iTu2QeHh
KFlfBQW4OHxgp6PfKQFdCefpgUoyu4pErS2fsoDEVz3/5TUW3z0TvL065Gst3xNf
qwoXjqn7GMQ2aKJhscRdWrOQNUwHqeiv9BUWb9skKThNzvdXfA6QYugA1fQycgQa
ChvcQ1YbJp24KX0s4Qsua7IOnYUhLTi/LrvUGK65ZaZagTxo9WLuWh+6C3Os2hJ+
INcjGeEUwh/XJWqxpxpc1HLoSzsrmsXFLWey6sQG4oDeGTs93vcHACwDdmg4ifnb
PDAxkNGmS3KnxEhDI2Wo7+v4O4nE7dqvlPg5qMAjkroHKVO0IOeTAkg+qhPw7gHy

Bug#900177: marked as done (rifiuti does not trap errors from gcc)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jun 2018 12:10:11 +
with message-id 
and subject line Bug#900177: fixed in rifiuti 20040505-2
has caused the Debian Bug report #900177,
regarding rifiuti does not trap errors from gcc
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.)


-- 
900177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rifiuti
Version: 20040505-1
Severity: serious
Justification: policy 4.6

The install target in src/Makefile chains commands with ";" and thus
does not abort on an error. This violates Debian policy section 4.6.

Helmut
--- End Message ---
--- Begin Message ---
Source: rifiuti
Source-Version: 20040505-2

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

Debian distribution maintenance software
pp.
Lorenzo "Palinuro" Faletra  (supplier of updated 
rifiuti package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 27 May 2018 21:42:32 +0200
Source: rifiuti
Binary: rifiuti
Architecture: source
Version: 20040505-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Lorenzo "Palinuro" Faletra 
Description:
 rifiuti- MS Windows recycle bin analysis tool
Closes: 900177
Changes:
 rifiuti (20040505-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Lorenzo "Palinuro" Faletra ]
   * Fix upstream Makefile. (Closes: #900177)
   * debian/compat
 - Bump DH level to 10.
   * debian/control:
   - Bump Standards-Version to 4.1.4.1.
   * debian/watch:
   - Bump version 4.
   * use https where possible in d/*.
   * Add debian/gbp.conf for dep-14 compliance.
 .
   [ Raphaël Hertzog ]
   * Update Vcs-* fields for the move to salsa.
Checksums-Sha1:
 d60cff750a8f5a650a75c392a48d4514dbf1389f 1658 rifiuti_20040505-2.dsc
 e9bf1912460d47a147a1ae111089b21766dd2140 4288 rifiuti_20040505-2.debian.tar.xz
 46bc31e76235a22f9fcb0ada461c7928a7ae2b85 5805 
rifiuti_20040505-2_source.buildinfo
Checksums-Sha256:
 6278a9a34d0d020baef41a5bc75642d13f34eed158f5b0ae2e7971bd7a992ca0 1658 
rifiuti_20040505-2.dsc
 f96d2301fcebd61bb5f44c919dcc814000efc9b73bea5c54a4493fa3dff83270 4288 
rifiuti_20040505-2.debian.tar.xz
 cd7755d27b0400ce6894b948cdaca20db877baae970971be7950e34749cfa57a 5805 
rifiuti_20040505-2_source.buildinfo
Files:
 877adc37032005d009bd41f599936d5b 1658 utils optional rifiuti_20040505-2.dsc
 ca62498ed3ea5942614395f5e1ac0886 4288 utils optional 
rifiuti_20040505-2.debian.tar.xz
 90f314829fb04e7549603772c470ff98 5805 utils optional 
rifiuti_20040505-2_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Signed by Raphael Hertzog

iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAlsyKWoACgkQA4gdq+vC
mrnv5Af9FpBJNvx2PV85bCeZL6Dt4NyKxdI5rzyPvvcTyEujHxSp5+4dTP7E1X6k
apaFXhIHvOn2RCkSGgEQn35fvfaHi2+X0vI39HCZDvPblsDmuDcN7niHjSv3gHSM
XZ5SPQdIJwdZKSnCxXUi6ab0a24rr3H0qxL/Ma6AJ6bdSTEBkT35V8vGmoJQutSP
gRGUMD5rPkTRaFatoBVYYzgI67fn4KoJhYSS4QmPkChqMDW7h3AgByeN4afg4+ZH
MOjAjR01Or5o9ldgwvTHqH2+rZBkzHmmkP93HaAZ6Thjck8EhF4zjoHxAa1sHZHb
usMfVCe0ZNsc/SUs+ardQRVWl55LlA==
=gom5
-END PGP SIGNATURE End Message ---

Bug#900302: FTBFS: bitrot

[Gianfranco Costamagna]

On Mon, 28 May 2018 18:10:07 + Clint Adams  wrote:
> Source: gitit
> Version: 0.12.2.1-1
> Severity: serious
> 
> gitit needs patching for newer dependencies (feed in particular)
> 
> 

feed patch is here
https://github.com/jgm/gitit/commit/e08643b8b353b0c9fc659ec323996e850ee9f52b#diff-d855f9af32d4eb5a6bd4d7167892dd79

now we need new pandoc to work.

I'm attaching the "feed" work, and the upstream cherry-picks)

G.


gitit_0.12.2.1+dfsg-4.debian.tar.xz
Description: application/xz

Bug#900485: [Debian-med-packaging] Bug#900485: python-pbcore: FTBFS and Debci failure with NumPy 1.14

[Afif Elghraoui]

On June 26, 2018 3:45:49 AM EDT, Andreas Tille  wrote:
>On Mon, Jun 25, 2018 at 09:52:50AM -0400, Afif Elghraoui wrote:
>> I think we can give 1.5.0 a try, but it might have the same problem.
>
>Since it builds successfully I've just uploaded.
> 

Ok

>> >  (And what do you think about watch mode=git?)
>> 
>> I don't know much about it, but I don't have any strong preference
>here.
>
>It might serve as a sensible solution for all upstreams using Git
>without proper release tagging.  I guess the pbcore example will
>explain
>what to do.
> 
>BTW, I remembered to late that you are not happy about the cme
>formatting.  I just fired up cme for Vcs-fields, Standards-Version etc.
>I hope you don't mind - feel free to revert to your prefered formatting
>and I hope I will not forget if I touch some of your packages in
>future.
>

Don't worry about this.

>
>PS: I'm currently checking pbseqlib since now upstream has tagged a
>release but there are some hdf5 issues which prevent me from
>uploading.  Please let me know if you want me to revert the cme
>formatting to its previous shape.
>

No need to revert anything.

regards
Afif

Bug#902281: marked as done (libgsl23: ABI breakage due to removed symbols)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jun 2018 10:50:48 +
with message-id 
and subject line Bug#902281: fixed in gsl 2.5+dfsg-3
has caused the Debian Bug report #902281,
regarding libgsl23: ABI breakage due to removed symbols
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.)


-- 
902281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgsl23
Version: 2.5+dfsg-1
Severity: serious

libgsl23 changed it's ABI without an SONAME bump in 2.5+dfsg-1.

Missing symbols:

% diff -u <(objdump -T libgsl.so.23-buster| cut -c50-) <(objdump -T 
libgsl.so.23-sid| cut -c50-)|grep ^-
--- /proc/self/fd/132018-06-23 18:24:03.211641309 +0300
-Basegsl_sf_legendre_Plm_deriv_array
-Basegsl_sf_legendre_Plm_array
-Basegsl_sf_legendre_sphPlm_array
-Basegsl_sf_legendre_array_size
-Basegsl_multifit_fdfsolver_dif_fdf
-Basegsl_sf_coupling_6j_INCORRECT
-Basegsl_linalg_hessenberg
-Basegsl_sf_coupling_6j_INCORRECT_e
-Basegsl_sf_legendre_sphPlm_deriv_array

This broke at least libmath-gsl-perl, which now fails
due to missing symbols.

  https://ci.debian.net/packages/libm/libmath-gsl-perl/unstable/amd64/

  # perl -e 'use Math::GSL::Linalg'
  Can't load 
'/usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Math/GSL/Linalg/Linalg.so' for 
module Math::GSL::Linalg: 
/usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Math/GSL/Linalg/Linalg.so: undefined 
symbol: gsl_linalg_hessenberg at 
/usr/lib/x86_64-linux-gnu/perl/5.26/DynaLoader.pm line 187.
   at /usr/lib/x86_64-linux-gnu/perl5/5.26/Math/GSL/Linalg.pm line 11.
  Compilation failed in require at -e line 1.
  BEGIN failed--compilation aborted at -e line 1.
  
  # perl -e 'use Math::GSL::SF'
  Can't load '/usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Math/GSL/SF/SF.so' for 
module Math::GSL::SF: 
/usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Math/GSL/SF/SF.so: undefined symbol: 
gsl_sf_coupling_6j_INCORRECT_e at 
/usr/lib/x86_64-linux-gnu/perl/5.26/DynaLoader.pm line 187.
   at /usr/lib/x86_64-linux-gnu/perl5/5.26/Math/GSL/SF.pm line 11.
  Compilation failed in require at -e line 1.
  BEGIN failed--compilation aborted at -e line 1.

Please reinstate the symbols or bump the SONAME (which would normally
require a proper library transition.)
-- 
Niko Tyni nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: gsl
Source-Version: 2.5+dfsg-3

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

Debian distribution maintenance software
pp.
Dirk Eddelbuettel  (supplier of updated gsl 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, 26 Jun 2018 05:09:48 -0500
Source: gsl
Binary: libgsl23 libgslcblas0 libgsl-dev gsl-bin libgsl-dbg libgsl-prof
Architecture: source amd64
Version: 2.5+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel 
Changed-By: Dirk Eddelbuettel 
Description:
 gsl-bin- GNU Scientific Library (GSL) -- binary package
 libgsl-dbg - GNU Scientific Library (GSL) -- debug symbols package
 libgsl-dev - GNU Scientific Library (GSL) -- development package
 libgsl-prof - GNU Scientific Library (GSL) -- profiling symbols package
 libgsl23   - GNU Scientific Library (GSL) -- library package
 libgslcblas0 - GNU Scientific Library (GSL) -- blas library package
Closes: 902281
Changes:
 gsl (2.5+dfsg-3) unstable; urgency=medium
 .
   * Rebuilding for unstable
 .
   * debian/patches/series: Reactivate 'dont-disable-deprecated' to provide
 otherwise deprecated symbols for the Perl GSL package (Closes: #902281)
Checksums-Sha1:
 1ca62d5aa25b009782784299acdcb78582877097 2069 gsl_2.5+dfsg-3.dsc
 6b49359f23217739635b3dd784eac232f3229c5f 18780 gsl_2.5+dfsg-3.debian.tar.xz
 2e89f286f7d29910e8365ba59a6674f9d0988671 29304 gsl-bin_2.5+dfsg-3_amd64.deb
 b313217f6f0dbdda3e4ccd36dc470323a3d726e7 6063 gsl_2.5+dfsg-3_amd64.buildinfo
 3ee96ae9fed4d7a3cd73d1cf9f406b7a08237ce9 2538008 
libgsl-dbg_2.5+dfsg-3_amd64.deb
 5c0b469677d66c3dc28ef8c2f93d6117cac4 1057748 

Bug#886048: Bug#902181: Bug#886048: plasma-pa: Depends on gconf

[Martin Steigerwald]

Martin Steigerwald - 26.06.18, 12:04:
> I still have no clear idea at what functionality will break by doing
> so. Asked so on kde-distro-packagers list. I now also asked on
> upstream bug report again:
> 
> https://bugs.kde.org/show_bug.cgi?id=386665#c18

Here is the functionality that will break:

From David Rosca:
> Two checkboxes under Advanced tab in KCM:
> 
> * Add virtual output device for simultaneous output on all local sound
> cards 
> * Automatically switch all running streams when a new output
> becomes available

Those will be now hidden when building without GConf.

From Christophe Giboudeaux:
> Virtual devices. The openSUSE maintainers for pulseaudio tried
> removing the gconf plugin and it made my virtual card to have sound
> both on my speakers & USB card disappear.

To me it seems like it is dropping gconf support for *now* and readding 
gsettings support back in with Plasma 5.14. There may be some users who 
use virtual devices, but I bet most users won´t. And those may still be 
able to use paprefs as a interim solution.

Upstream patch for dropping gconf support, by David Rosca:

https://phabricator.kde.org/D13734

Thanks,
-- 
Martin

Bug#886048: Bug#902181: Bug#886048: plasma-pa: Depends on gconf

[Martin Steigerwald]

Martin Steigerwald - 25.06.18, 17:39:
> Felipe Sateler - 25.06.18, 16:41:
> > > With Debian's pulseaudio 12.0 upload, pulseaudio has removed
> > > pulseaudio- module-gconf in favour of pulseaudio-module-gsettings,
> > > which would break current plasma-pa.
> > 
> > Indeed. While pulseaudio can build a gconf or a gsettings backend,
> > building both is not advisable and would lead to confusion, as
> > changes would not be synchronized between the modules. Therefore I
> > have removed the gconf module.
> > 
> > The only reverse dependencies are plasma-pa and paprefs. paprefs is
> > already fixed upstream and I'm only waiting on a release to upload
> > to debian. That would leave plasma-pa to be fixed.
> 
> Please also see upstream bug report:
> 
> [plasma-pa] [Bug 386665] Drop dependency on pulseaudio-gconf?
> https://bugs.kde.org/386665
> 
> I hope that upstream provides a fix soon.

A port before Plasma 5.14 is unlikely:

https://bugs.kde.org/show_bug.cgi?id=386665#c17

So seems to me that building without gconf module support is the best  
option for now. See:

https://bugs.kde.org/show_bug.cgi?id=386665#c16

=> 

https://build.opensuse.org/package/view_file/
home:cfeck:branches:KDE:Unstable:Frameworks/plasma5-pa/plasma-pa.diff?
expand=1

I still have no clear idea at what functionality will break by doing so. 
Asked so on kde-distro-packagers list. I now also asked on upstream bug 
report again:

https://bugs.kde.org/show_bug.cgi?id=386665#c18

Thanks,
-- 
Martin

Bug#894213: No clue yet for building snakemake since there are two dirs in .pybuild

[Andreas Tille]

Hi,

meanwhile I upgraded snakemake to latest upstream in Salsa[1].  I keep
on having trouble with building it:


...
Building DAG of jobs...
Using shell: /bin/bash
Job counts:
count   jobs
1   1
1
Finished job 0.
1 of 1 steps (100%) done
Complete log: 
/tmp/tmp3rl_vn12/.snakemake/log/2018-06-26T092103.652823.snakemake.log
.E
==
ERROR: Failure: Exception (snakemake not in PATH. For testing, install 
snakemake with 'pip install -e .'. You should do this in a separate environment 
(via conda or virtualenv).)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest
raise self.exc_val.with_traceback(self.tb)
  File "/usr/lib/python3/dist-packages/nose/loader.py", line 417, in 
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File "/usr/lib/python3.6/imp.py", line 235, in load_module
return load_source(name, filename, file)
  File "/usr/lib/python3.6/imp.py", line 172, in load_source
module = _load(spec)
  File "", line 684, in _load
  File "", line 665, in _load_unlocked
  File "", line 678, in exec_module
  File "", line 219, in _call_with_frames_removed
  File 
"/build/snakemake-5.1.5/.pybuild/cpython3_3.6_snakemake/build/tests/tests.py", 
line 22, in 
raise Exception("snakemake not in PATH. For testing, install snakemake with 
"
Exception: snakemake not in PATH. For testing, install snakemake with 'pip 
install -e .'. You should do this in a separate environment (via conda or 
virtualenv).

--
Ran 4 tests in 0.227s

FAILED (errors=1)
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: cd 
/build/snakemake-5.1.5/.pybuild/cpython3_3.6_snakemake/build; python3.6 -m nose 
tests



I think the cause of the issue is that there are two dirs in .pybuild:


# ls -l /build/snakemake-5.1.5/.pybuild
total 8
drwxr-xr-x 3 pbuilder pbuilder 4096 Jun 26 09:20 cpython3_3.6
drwxr-xr-x 3 pbuilder pbuilder 4096 Jun 26 09:20 cpython3_3.6_snakemake


and the latter contains all the installed files while the former is
empty.  How can I prevent this?

Kind regards

Andreas.


[1] https://salsa.debian.org/med-team/snakemake

-- 
http://fam-tille.de

Bug#897521: marked as done (haskell-servant-server: FTBFS: Could not find module `Build_doctests')

[Debian Bug Tracking System]

Your message dated Tue, 26 Jun 2018 09:49:18 +
with message-id 
and subject line Bug#897521: fixed in haskell-servant-server 0.13.0.1-1
has caused the Debian Bug report #897521,
regarding haskell-servant-server: FTBFS: Could not find module 
`Build_doctests'
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.)


-- 
897521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-servant-server
Version: 0.13-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> . /usr/share/haskell-devscripts/Dh_Haskell.sh && \
> make_setup_recipe
> Running ghc --make Setup.lhs -o debian/hlibrary.setup
> 
> Setup.lhs:19:2: error:
>  warning: #warning You are configuring this package without cabal-doctest 
> installed. The doctests test-suite will not work as a result. To fix this, 
> install cabal-doctest before configuring. [-Wcpp]
>  #warning You are configuring this package without cabal-doctest 
> installed. \
>   ^~~
>|
> 19 | #warning You are configuring this package without cabal-doctest 
> installed. \
>|  ^
> [1 of 1] Compiling Main ( Setup.lhs, Setup.o )
> Linking debian/hlibrary.setup ...
> . /usr/share/haskell-devscripts/Dh_Haskell.sh && \
> configure_recipe
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/servant-server-0.13/ 
> --datasubdir=servant-server 
> --htmldir=/usr/share/doc/libghc-servant-server-doc/html/ 
> --enable-library-profiling --enable-tests
> Configuring servant-server-0.13...
> Dependency QuickCheck >=2.10.1 && <2.12: using QuickCheck-2.10.1
> Dependency aeson >=1.2.3.0 && <1.3: using aeson-1.2.4.0
> Dependency attoparsec >=0.13.2.0 && <0.14: using attoparsec-0.13.2.2
> Dependency base >=4.7 && <4.11: using base-4.10.1.0
> Dependency base-compat >=0.9.3 && <0.10: using base-compat-0.9.3
> Dependency base64-bytestring >=1.0.0.1 && <1.1: using
> base64-bytestring-1.0.0.1
> Dependency bytestring >=0.10.4.0 && <0.11: using bytestring-0.10.8.2
> Dependency containers >=0.5.5.1 && <0.6: using containers-0.5.10.2
> Dependency directory >=1.2.1.0 && <1.4: using directory-1.3.0.2
> Dependency doctest >=0.13.0 && <0.14: using doctest-0.13.0
> Dependency exceptions >=0.8.3 && <0.9: using exceptions-0.8.3
> Dependency filepath >=1.3.0.2 && <1.5: using filepath-1.4.1.2
> Dependency hspec >=2.4.4 && <2.5: using hspec-2.4.8
> Dependency hspec-wai ==0.9.*: using hspec-wai-0.9.0
> Dependency http-api-data >=0.3.7.1 && <0.4: using http-api-data-0.3.7.2
> Dependency http-media >=0.7.1.1 && <0.8: using http-media-0.7.1.2
> Dependency http-types ==0.12.*: using http-types-0.12.1
> Dependency monad-control >=1.0.0.4 && <1.1: using monad-control-1.0.2.3
> Dependency mtl >=2.1 && <2.3: using mtl-2.2.2
> Dependency network >=2.6.3.2 && <2.7: using network-2.6.3.5
> Dependency network-uri >=2.6.1.0 && <2.7: using network-uri-2.6.1.0
> Dependency parsec >=3.1.11 && <3.2: using parsec-3.1.13.0
> Dependency resourcet >=1.1.9 && <1.3: using resourcet-1.2.0
> Dependency safe >=0.3.15 && <0.4: using safe-0.3.17
> Dependency servant ==0.13.*: using servant-0.13.0.1
> Dependency servant-server -any: using servant-server-0.13
> Dependency should-not-typecheck >=2.1.0 && <2.2: using
> should-not-typecheck-2.1.0
> Dependency split >=0.2.3.2 && <0.3: using split-0.2.3.3
> Dependency string-conversions >=0.4.0.1 && <0.5: using
> string-conversions-0.4.0.1
> Dependency system-filepath ==0.4.*: using system-filepath-0.4.14
> Dependency tagged >=0.8.5 && <0.9: using tagged-0.8.5
> Dependency temporary >=1.2.0.3 && <1.3: using temporary-1.2.1.1
> Dependency text >=1.2.3.0 && <1.3: using text-1.2.3.0
> Dependency transformers >=0.3.0.0 && <0.6: using transformers-0.5.2.0
> Dependency transformers-base >=0.4.4 && <0.5: using transformers-base-0.4.4
> Dependency transformers-compat >=0.5.1 && <0.6: using
> transformers-compat-0.5.1.4
> Dependency wai >=3.2.1.1 && <3.3: using wai-3.2.1.2
> Dependency wai-app-static 

Bug#899021: libembperl-perl: FTBFS with Perl 5.27, unmaintained upstream

[Axel Beckert]

Hi,

gregor herrmann wrote:
> > Is there an APT repo where I can get all the build-dependencies
> > necessary to debug this?
> 
> Yup, at the same server. Details and key at the start page of
> http://perl.debian.net/

Ah, sorry, was probably to tired yesterday to try the most obvious
thing. :-) Anyway, thanks for that hint!

Will try to dig into it, but might take a few days until I get to it.

Niko Tyni wrote:
> Indeed. Alternatively, I believe locally rebuilding
> 
> libhtml-parser-perl
> libnet-ssleay-perl
> libbsd-resource-perl
> libapache2-mod-perl2

I'm not really keen on having to rebuild mod_perl. And I remembered
from previous Perl version bumps that such a repo exists. :-)

> against 5.28 should suffice.

Hrm, aptitude inside pbuilder wanted to remove at least 8 packages
when I wanted to upgrade perl to 5.28, so it might be a few more...
Then again, the remaining four packages might have been some arch:all
packages with arch:any dependencies...

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 902410 3:3.2.6-3+deb9u1
Bug #902410 [redis] redis: CVE-2018-12326
There is no source info for the package 'redis' at version '3:3.2.6-3+deb9u1' 
with architecture ''
Unable to make a source version for version '3:3.2.6-3+deb9u1'
Marked as fixed in versions 3:3.2.6-3+deb9u1.
> thanks
Stopping processing here.

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

Bug#792205: marked as done (fusioninventory-agent: modifies conffiles (policy 10.7.3): /etc/fusioninventory/agent.cfg)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jun 2018 10:31:35 +0200 (CEST)
with message-id <651086950.3755701.1530001895186.javamail.zim...@teclib.com>
and subject line Re: fusioninventory-agent: modifies conffiles (policy 10.7.3): 
/etc/fusioninventory/agent.cfg
has caused the Debian Bug report #792205,
regarding fusioninventory-agent: modifies conffiles (policy 10.7.3): 
/etc/fusioninventory/agent.cfg
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.)


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

Hi,

during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files

10.7.3: "[...] The easy way to achieve this behavior is to make the
configuration file a conffile. [...] This implies that the default
version will be part of the package distribution, and must not be
modified by the maintainer scripts during installation (or at any
other time)."

Note that once a package ships a modified version of that conffile,
dpkg will prompt the user for an action how to handle the upgrade of
this modified conffile (that was not modified by the user).

Further in 10.7.3: "[...] must not ask unnecessary questions
(particularly during upgrades) [...]"

If a configuration file is customized by a maintainer script after
having asked some debconf questions, it may not be marked as a
conffile. Instead a template could be installed in /usr/share and used
by the postinst script to fill in the custom values and create (or
update) the configuration file (preserving any user modifications!).
This file must be removed during postrm purge.
ucf(1) may help with these tasks.
See also https://wiki.debian.org/DpkgConffileHandling

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

debsums reports modification of the following files,
from the attached log (scroll to the bottom...):

4m54.9s ERROR: FAIL: debsums reports modifications inside the chroot:
  /etc/fusioninventory/agent.cfg

  
This problem was observed after an squeeze -> wheezy -> jessie -> stretch
upgrade.


cheers,

Andreas


fusioninventory-agent_1:2.3.16-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 1:2.3.16-1

Hi,

I'm the upstream maintainer.

As I said before, ucf is used since 2.3.10. So the problem shouldn't occur in 
later releases.

So this bug should be closed.

Cheers,

Guillaume Bougard 
Ingénieur R 
gboug...@teclib.com 

TECLIB' Montpellier 
3 rue Doria, 
34000 Montpellier, France --- End Message ---

Bug#902410: redis: CVE-2018-12326

[Chris Lamb]

Package: redis
Version: 2:2.8.17-1+deb8u5
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for redis.

CVE-2018-12326[0]:
| Buffer overflow in redis-cli of Redis before 4.0.10 and 5.x before 5.0
| RC3 allows an attacker to achieve code execution and escalate to higher
| privileges via a crafted command line. NOTE: It is unclear whether
| there are any common situations in which redis-cli is used with, for
| example, a -h (aka hostname) argument 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-2018-12326
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12326


Regards,

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

Bug#900834: marked as done (perl: CVE-2018-12015: Archive::Tar: directory traversal)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jun 2018 08:18:09 +
with message-id 
and subject line Bug#900834: fixed in perl 5.28.0-1
has caused the Debian Bug report #900834,
regarding perl: CVE-2018-12015: Archive::Tar: directory traversal
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.)


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

Source: perl
Version: 5.26.2-5
Tags: security

By default, the Archive::Tar module doesn't allow extracting files 
outside the current working directory. However, you can bypass this 
secure extraction mode easily by putting a symlink and a regular file 
with the same name into the tarball.


I've attached proof of concept tarball, which makes Archive::Tar create 
/tmp/moo, regardless of what the current working directory is:


  $ tar -tvvf traversal.tar.gz
  lrwxrwxrwx root/root 0 2018-06-05 18:55 moo -> /tmp/moo
  -rw-r--r-- root/root 4 2018-06-05 18:55 moo

  $ pwd
  /home/jwilk

  $ ls /tmp/moo
  ls: cannot access '/tmp/moo': No such file or directory

  $ perl -MArchive::Tar -e 'Archive::Tar->extract_archive("traversal.tar.gz")'

  $ ls /tmp/moo
  /tmp/moo

--
Jakub Wilk


traversal.tar.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: perl
Source-Version: 5.28.0-1

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

Debian distribution maintenance software
pp.
Niko Tyni  (supplier of updated perl 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: Mon, 25 Jun 2018 22:20:16 +0300
Source: perl
Binary: perl-base perl-doc perl-debug libperl5.28 libperl-dev perl-modules-5.28 
perl
Architecture: source
Version: 5.28.0-1
Distribution: experimental
Urgency: medium
Maintainer: Niko Tyni 
Changed-By: Niko Tyni 
Description:
 libperl-dev - Perl library: development files
 libperl5.28 - shared Perl library
 perl   - Larry Wall's Practical Extraction and Report Language
 perl-base  - minimal Perl system
 perl-debug - debug-enabled Perl interpreter
 perl-doc   - Perl documentation
 perl-modules-5.28 - Core Perl modules
Closes: 900834
Changes:
 perl (5.28.0-1) experimental; urgency=medium
 .
   [ Dominic Hargreaves ]
   * Merge 5.26.2-6 from unstable
 - [SECURITY] CVE-2018-12015: fix directory traversal vulnerability
   in Archive-Tar (Closes: #900834)
 .
   [ Niko Tyni ]
   * Add an autopkgtest check that trivially embeds Perl in C.
   * Import new upstream major release.
Checksums-Sha1:
 4de68cb29e14d3fd4bb4df4a6bbc6c8c01671d6b 2810 perl_5.28.0-1.dsc
 21339f5f1bcacbaed5cdfe97368eacbc5e55da35 411944 
perl_5.28.0.orig-regen-configure.tar.xz
 c0e9e7a0dea97ec9816687d865fd461a99ef185c 12410536 perl_5.28.0.orig.tar.xz
 f69e2f6d929af8f8509857a8462373ababe05033 158260 perl_5.28.0-1.debian.tar.xz
 66ccc15f8cdb38e2b3ad50d2e94de64cf2a6a3ae 4729 perl_5.28.0-1_source.buildinfo
Checksums-Sha256:
 226d942fbe976325a81bdd7e870dd24788abdf8c13dd372624eb3522e16095be 2810 
perl_5.28.0-1.dsc
 5873b81af4514d3910ab1a8267b15ff8c0e2100dbae4edfd10b65ef72cd31ef8 411944 
perl_5.28.0.orig-regen-configure.tar.xz
 059b3cb69970d8c8c5964caced0335b4af34ac990c8e61f7e3f90cd1c2d11e49 12410536 
perl_5.28.0.orig.tar.xz
 a587795bbaaec31d0dbfa84b2d2f130bc47d8926823de8afb5141904df892a61 158260 
perl_5.28.0-1.debian.tar.xz
 c000ae91b48aeb9923ae38398ab8b2e6e8a9c4368d3b6c7bf4f77498ed3f1f29 4729 
perl_5.28.0-1_source.buildinfo
Files:
 7148eff8c8fbf5f8410b3ac475cd435e 2810 perl standard perl_5.28.0-1.dsc
 fbf2e774fdcc55c92afe713db38e5e25 411944 perl standard 
perl_5.28.0.orig-regen-configure.tar.xz
 f3245183c0a08f65e94a995af08e 12410536 perl standard perl_5.28.0.orig.tar.xz
 433f0df9d2640f50ee6a801c03f11d4c 158260 perl standard 
perl_5.28.0-1.debian.tar.xz
 d89e67cbcff53286c4ed087c4aefc229 4729 perl standard 
perl_5.28.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEdqKOQsmBHZHoj7peLsD/s7cwGx8FAlsx6q4RHG50eW5pQGRl
Ymlhbi5vcmcACgkQLsD/s7cwGx8QHRAAw2TmhU/MC8l+aMkt0xCzyTi1FV9xwzDV

Bug#902409: grep-excuses: uses YAML::Syck in a unsafe way

[Ansgar Burchardt]

Package: devscripts
Version: 2.18.3
Severity: grave
File: /usr/bin/grep-excuses
Tags: patch security

grep-excuses uses YAML::Syck without telling YAML::Syck to not bless
objects which might lead to running code the author of grep-excuses
might not have intended to run.

The attached patch tells grep-excuses to tell YAML::Syck to not point
a loaded gun towards your foot (even though this might be against the
UNIX philosophy of shooting on feet).

See also #862475.

Ansgar
--- scripts/grep-excuses.pl 2018-03-06 15:42:39.0 +0100
+++ /usr/bin/grep-excuses   2018-06-26 09:57:34.499148292 +0200
@@ -32,6 +32,8 @@
 
 eval {
require YAML::Syck;
+   no warnings 'once';
+   $YAML::Syck::LoadBlessed = 0;
 };
 
 if ($@) {

Bug#899004: marked as done (gnome-shell: crash on attempt to lock)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jun 2018 08:56:10 +0100
with message-id <20180626075610.ga3...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#899004: gnome-shell: crash on attempt to lock
has caused the Debian Bug report #899004,
regarding gnome-shell: crash on attempt to lock
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.)


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

Dear Maintainer,

gnome-shell crashes when I press meta+L to lock the session. After the third
failed attempt, it crashes and also suspends the computer.

A backtrace follows:

#0  0x770c14f4 in g_hash_table_iter_init
(iter=iter@entry=0x7ffef010, hash_table=0x10004) at
../../../../glib/ghash.c:769
#1  0x72909042 in nm_ip_address_dup (address=) at libnm-
core/nm-setting-ip-config.c:388
#2  0x773aaecb in g_boxed_copy (boxed_type=93825030200288,
src_boxed=src_boxed@entry=0x563791e0) at ../../../../gobject/gboxed.c:343
#3  0x7609f540 in gjs_boxed_from_c_struct(JSContext*, GIStructInfo*,
void*, GjsBoxedCreationFlags) (context=context@entry=0x55dd7a00,
info=info@entry=0x57aec540, gboxed=0x563791e0, flags=)
at gi/boxed.cpp:1235
#4  0x7609b194 in gjs_value_from_g_argument(JSContext*,
JS::MutableHandleValue, GITypeInfo*, GArgument*, bool)
(context=context@entry=0x55dd7a00, value_p=...,
type_info=type_info@entry=0x58331ca0, arg=arg@entry=0x7ffef4b8,
copy_structs=copy_structs@entry=true) at gi/arg.cpp:2909
#5  0x7609bf33 in gjs_array_from_carray_internal(JSContext*,
JS::MutableHandleValue, GITypeInfo*, guint, gpointer)
(context=context@entry=0x55dd7a00, value_p=..., value_p@entry=...,
param_info=param_info@entry=0x58331ca0, length=1, array=) at
gi/arg.cpp:2346
#6  0x7609a446 in gjs_array_from_boxed_array (arg=0x7ffef998,
param_info=0x58331ca0, array_type=, value_p=...,
context=0x55dd7a00) at gi/arg.cpp:2462
#7  0x7609a446 in gjs_value_from_g_argument(JSContext*,
JS::MutableHandleValue, GITypeInfo*, GArgument*, bool)
(context=context@entry=0x55dd7a00, value_p=...,
type_info=type_info@entry=0x7ffef9c0, arg=arg@entry=0x7ffef998,
copy_structs=copy_structs@entry=true) at gi/arg.cpp:3012
#8  0x760a677e in gjs_invoke_c_function(JSContext*, Function*,
JS::HandleObject, JS::HandleValueArray const&,
mozilla::Maybe >, GIArgument*)
(context=context@entry=0x55dd7a00, function=function@entry=0x576f0b00,
obj=...,
obj@entry=..., args=..., js_rval=..., r_value=r_value@entry=0x0) at
gi/function.cpp:1147
#9  0x760a6a24 in function_call(JSContext*, unsigned int, JS::Value*)
(context=context@entry=0x55dd7a00, js_argc=0, vp=0x55f14d50)
at gi/function.cpp:1406
#10 0x7fffed039fdc in js::CallJSNative(JSContext*, bool (*)(JSContext*,
unsigned int, JS::Value*), JS::CallArgs const&) (args=...,
native=0x760a68c0 ,
cx=0x55dd7a00) at ./js/src/jscntxtinlines.h:239
#11 0x7fffed039fdc in js::InternalCallOrConstruct(JSContext*, JS::CallArgs
const&, js::MaybeConstruct) (cx=0x55dd7a00, args=...,
construct=js::NO_CONSTRUCT) at ./js/src/vm/Interpreter.cpp:447
#12 0x7fffed02d087 in js::CallFromStack(JSContext*, JS::CallArgs const&)
(args=..., cx=) at ./js/src/vm/Interpreter.cpp:510
#13 0x7fffed02d087 in Interpret(JSContext*, js::RunState&)
(cx=0x55dd7a00, state=...) at ./js/src/vm/Interpreter.cpp:2922
#14 0x7fffed039846 in js::RunScript(JSContext*, js::RunState&)
(cx=cx@entry=0x55dd7a00, state=...) at ./js/src/vm/Interpreter.cpp:405
#15 0x7fffed039e1f in js::InternalCallOrConstruct(JSContext*, JS::CallArgs
const&, js::MaybeConstruct) (cx=cx@entry=0x55dd7a00, args=...,
construct=construct@entry=js::NO_CONSTRUCT) at ./js/src/vm/Interpreter.cpp:477
#16 0x7fffed03a099 in InternalCall(JSContext*, js::AnyInvokeArgs const&)
(cx=cx@entry=0x55dd7a00, args=...) at ./js/src/vm/Interpreter.cpp:504
#17 0x7fffed03a0f9 in js::Call(JSContext*, JS::Handle,
JS::Handle, js::AnyInvokeArgs const&, JS::MutableHandle)
(cx=cx@entry=0x55dd7a00, fval=..., fval@entry=..., thisv=...,
thisv@entry=..., args=..., rval=rval@entry=...) at
./js/src/vm/Interpreter.cpp:523
#18 0x7fffece2c079 in js::jit::InvokeFunction(JSContext*,
JS::Handle, bool, unsigned int, JS::Value*,
JS::MutableHandle) (cx=0x55dd7a00, obj=...,
constructing=, argc=, argv=0x7fff06c0,
rval=...) at ./js/src/jit/VMFunctions.cpp:114

Bug#900485: [Debian-med-packaging] Bug#900485: python-pbcore: FTBFS and Debci failure with NumPy 1.14

[Andreas Tille]

On Mon, Jun 25, 2018 at 09:52:50AM -0400, Afif Elghraoui wrote:
> I think we can give 1.5.0 a try, but it might have the same problem.

Since it builds successfully I've just uploaded.
 
> >  (And what do you think about watch mode=git?)
> 
> I don't know much about it, but I don't have any strong preference here.

It might serve as a sensible solution for all upstreams using Git
without proper release tagging.  I guess the pbcore example will explain
what to do.
 
BTW, I remembered to late that you are not happy about the cme
formatting.  I just fired up cme for Vcs-fields, Standards-Version etc.
I hope you don't mind - feel free to revert to your prefered formatting
and I hope I will not forget if I touch some of your packages in future.

Kind regards

Andreas.

PS: I'm currently checking pbseqlib since now upstream has tagged a
release but there are some hdf5 issues which prevent me from
uploading.  Please let me know if you want me to revert the cme
formatting to its previous shape.

-- 
http://fam-tille.de

Bug#901807: libmath-gsl-perl: incompatible with GSL >= 2.5

[Niko Tyni]

On Sun, Jun 24, 2018 at 04:02:06PM +0200, gregor herrmann wrote:

> -my $ver2func = do(catfile(qw/inc ver2func/));
> +my $ver2func = do('./' . catfile(qw/inc ver2func/));

Yeah, that's better than -I. (hardcoding '/' as the directory separator is
a bit ugly but works for us, and I see catfile is rather eager to remove
'./' if it sees it.)

>  sub is_release {
> -return -e '.git' ? 0 : 1;
> +return 0;
>  }

I think I was testing all the time with inside a git checkout,
that probably explains it. Happy if that's enough to trigger
the rebuild. Not sure if it still looks at file mtime stamps
and would need an explicit clean first?

> > The latter one may not turn out to be
> > necessary if the deprecated functions get reinstated with #902281.
> 
> Ack.

It looks like the deprecated symbols will be reinstated for now.
Not sure if we still want to disable them on our side. Probably not.

In any case, I think we should still do a swig rebuild every
time as part of the normal package build.
 
> I've pushed your and my patches, but I'd rather have another
> doublecheck before uploading.

Looks good to me, thanks!
-- 
Niko

Bug#899124: fa-solid-900.ttf symlinked as fontawesome-webfont.ttf

[Sean Whitton]

Hello Alexis,

On Tue, Jun 26 2018, Alexis Murzeau wrote:

> I've updated my personal repo [0] to use the version
> 5.0.10+really4.7.0~dfsg-1.  I've reset the changelog and everything to
> debian/4.7.0~dfsg-3 tag and then cherry-picking relevant commits in
> 5.0.10-x:
>   * Change maintainer email address to debian-fonts@l.d.o.
>   * Drop Friendica Maintainers team from uploaders list.
>   * Mark package compliance with Debian policy 4.1.4.
>   * Use salsa URL in Vcs-* fields.
>
> And then update the package version and watch file.  I've branched out
> from the debian/4.7.0_dfsg-3 tag but that's a non forward master
> branch move. I'm not sure how to handle this here, but v5 related
> change don't seems relevant for the v4 package to me as everything is
> just reverted.

The git history is up to you but resetting the changelog seems like a
really bad idea -- it is confusing to see that there are uploads to the
archive that are not present in the changelog.

I think you should at least retain d/changelog, even if you reset
everything else (personally, I would keep all the git history).

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#902281: libgsl23: ABI breakage due to removed symbols

[Niko Tyni]

On Mon, Jun 25, 2018 at 06:37:21AM -0500, Dirk Eddelbuettel wrote:
 
> I seem to have confused myself. I have new 2.5-2 packages which should carry
> the deprecated symbols, brought back for our use in the eg the Perl GSL 
> package.
 
Thanks! I can confirm that libmath-gsl-perl works fine again with
libgsl23_2.5+dfsg-2 from experimental. Please upload the fix to unstable
too :)

For the record, the Perl GSL bindings package libmath-gsl-perl (can be
made to) work without the deprecated symbols too. It just needs a rebuild,
and forcing that rebuild (and the associated dependency metadata updates)
is the main point of SONAME bumps. 

So please don't feel obliged to carry those symbols forever because of us.

Any user code compiled against libgsl23 and using those symbols would
of course be similarly affected, and the SONAME bump makes that visible,
which is preferable to silent breakage at runtime.

> You have really helpful on this -- much appreciated.

My pleasure!
-- 
Niko

Processed: bug 901823 is forwarded to https://github.com/mjambon/atd/issues/140

[Debian Bug Tracking System]

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

> forwarded 901823 https://github.com/mjambon/atd/issues/140
Bug #901823 [src:ocaml-atd] ocaml-atd FTBFS on i386: tests failure
Set Bug forwarded-to-address to 'https://github.com/mjambon/atd/issues/140'.
> thanks
Stopping processing here.

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

Bug#899021: libembperl-perl: FTBFS with Perl 5.27, unmaintained upstream

[Niko Tyni]

On Tue, Jun 26, 2018 at 08:23:54AM +0200, gregor herrmann wrote:
> On Tue, 26 Jun 2018 04:24:59 +0200, Axel Beckert wrote:
> 
> > Dominic Hargreaves wrote:
> > > The upstream version of this package has not worked since 5.18, and we
> > > have had to apply several fixes in Debian since. The build has now
> > > broken again with Perl 5.27:
> > > 
> > > http://perl.debian.net/rebuild-logs/perl-5.27-throwaway/libembperl-perl_2.5.0-11/libembperl-perl_2.5.0-11_amd64-2018-05-18T08:09:28Z.build
> > 
> > Is there an APT repo where I can get all the build-dependencies
> > necessary to debug this?
> 
> Yup, at the same server. Details and key at the start page of
> http://perl.debian.net/

Indeed. Alternatively, I believe locally rebuilding

libhtml-parser-perl
libnet-ssleay-perl
libbsd-resource-perl
libapache2-mod-perl2

against 5.28 should suffice.

> gregor, hoping that all build-deps for _this_ package are included
> but so far this has worked flawlessly for me

The system is pretty well automated nowadays (thanks Dom!) and shouldn't
lag behind sid for more than half a day at most.
-- 
Niko

Bug#900485: marked as done (python-pbcore: FTBFS and Debci failure with NumPy 1.14)

[Debian Bug Tracking System]

Your message dated Tue, 26 Jun 2018 06:49:03 +
with message-id 
and subject line Bug#900485: fixed in python-pbcore 
1.5.0+git20180606.43fcd9d+dfsg-1
has caused the Debian Bug report #900485,
regarding python-pbcore: FTBFS and Debci failure with NumPy 1.14
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.)


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

Source: python-pbcore
Version: 1.2.11+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: needs-update

Hi Maintainer

Since the recent upload of python-numpy on 2018-05-05, python-pbcore has 
been failing its autopkgtests [1] and has now also started to FTBFS in 
unstable [2] with several errors similar to the following:


FAIL: test_referenceInfo (test_pbdataset.TestDataSet)
--
Traceback (most recent call last):
  File "/build/1st/python-pbcore-1.2.11+dfsg/tests/test_pbdataset.py", 
line 1407, in test_referenceInfo

"(27, 27, 'E.faecalis.1', 'E.faecalis.1', 1482, "
AssertionError: "(27, 27, 'E.faecalis.1', 'E.faecalis.1', 1482, 
'a1a59c267ac1341e5a12bce7a7d37bcb', 0, 0)" != "(27, 27, 'E.faecalis.1', 
'E.faecalis.1', 1482, 'a1a59c267ac1341e5a12bce7a7d37bcb', 0L, 0L)"

 >> begin captured logging << 
pbcore.io.dataset.DataSetIO: DEBUG: Opening ReadSet resources
pbcore.io.dataset.DataSetIO: DEBUG: Done opening resources
pbcore.io.dataset.DataSetIO: DEBUG: Updating counts
pbcore.io.dataset.DataSetIO: DEBUG: Populating index
pbcore.io.dataset.DataSetIO: DEBUG: Processing resource indices
pbcore.io.dataset.DataSetIO: DEBUG: Filtering reference entries
pbcore.io.dataset.DataSetIO: DEBUG: Done populating index

Regards
Graham


[1] https://ci.debian.net/packages/p/python-pbcore/unstable/amd64/
[2] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-pbcore.html
--- End Message ---
--- Begin Message ---
Source: python-pbcore
Source-Version: 1.5.0+git20180606.43fcd9d+dfsg-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-pbcore 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, 26 Jun 2018 08:13:42 +0200
Source: python-pbcore
Binary: python-pbcore python-pbcore-doc
Architecture: source
Version: 1.5.0+git20180606.43fcd9d+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 python-pbcore - Python library for processing PacBio data files
 python-pbcore-doc - Python library for processing PacBio data files 
(documentation)
Closes: 900485
Changes:
 python-pbcore (1.5.0+git20180606.43fcd9d+dfsg-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Afif Elghraoui ]
   * New upstream version (git f3bcf3a)
   * Updated patches
   * Added tests dependency on python-coverage
   * d/control: use build profile declarations
 .
   [ Andreas Tille ]
   * New upstream version
 Closes: #900485
   * Relax test constraint which is rather a rounding issue
   * d/watch: mode=git
   * cme fix dpkg-control
  - Point Vcs-fields to Salsa
  - Standards-Version: 4.1.4
  - Sequence of fields
  - Formatting
   * debhelper 11
   * remove outdated X-Python-Version
   * d/rules: Drop get-orig-source target
Checksums-Sha1:
 6bd638889e43d6e37dbfa2c1f852d33c49a9a9df 2505 
python-pbcore_1.5.0+git20180606.43fcd9d+dfsg-1.dsc
 3abdd9ba1d600d34ccb7a5eccfe949dce0bc4bac 9138120 
python-pbcore_1.5.0+git20180606.43fcd9d+dfsg.orig.tar.xz
 c3eb6eabe0d0637358588f15220f42b634bc845f 6900 
python-pbcore_1.5.0+git20180606.43fcd9d+dfsg-1.debian.tar.xz
Checksums-Sha256:
 58af670c6d226c283a705ae684dfa5f7b475d279347314e0c167a9bf1a821943 2505 
python-pbcore_1.5.0+git20180606.43fcd9d+dfsg-1.dsc
 3856f1b5c3bd161680ba41b12c053ad2a9dc8eab73710e0d68a92746cef7428b 9138120 

Bug#899021: libembperl-perl: FTBFS with Perl 5.27, unmaintained upstream

[gregor herrmann]

On Tue, 26 Jun 2018 04:24:59 +0200, Axel Beckert wrote:

> Dominic Hargreaves wrote:
> > The upstream version of this package has not worked since 5.18, and we
> > have had to apply several fixes in Debian since. The build has now
> > broken again with Perl 5.27:
> > 
> > http://perl.debian.net/rebuild-logs/perl-5.27-throwaway/libembperl-perl_2.5.0-11/libembperl-perl_2.5.0-11_amd64-2018-05-18T08:09:28Z.build
> 
> Is there an APT repo where I can get all the build-dependencies
> necessary to debug this?

Yup, at the same server. Details and key at the start page of
http://perl.debian.net/
 

Cheers,
gregor, hoping that all build-deps for _this_ package are included
but so far this has worked flawlessly for me

-- 
 .''`.  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
   `-   BOFH excuse #344:  Network failure - call NBC 

Bug#901218: closed by Laszlo Boszormenyi (GCS) (Bug#901218: fixed in grpc 1.13.0~pre2-1)

[GCS]

On Tue, Jun 26, 2018 at 2:45 AM Andreas Beckmann  wrote:
> and now we have the same problem with libgpr2-dev ... I assume
> you want to add a conflict against that, too.
> (Even if a conflict between two unrelated packages is not really
> the right solution here (one might want to link against both libraries),
> I don't see a better one here for now).
 Exactly. Upstream developers need to discuss this and one project
need to rename its library.
Maybe Nicolas has some connections with GNAT upstream and when
informed, they can discuss this library name collision with Google.

Regards,
Laszlo/GCS

Processed: tagging 902352

[Debian Bug Tracking System]

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

> tags 902352 + pending
Bug #902352 [src:dict-gcide] dict-gcide: Build-Depends on cruft package: libmaa3
Added tag(s) pending.
> thanks
Stopping processing here.

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