Bug#887924: slurm-drmaa FTBFS with slurm-llnl 17.11.2-1

[Steve Langasek]

Looking closer, I see:

configure:12821: checking for usable SLURM libraries/headers
configure:12842: gcc -o conftest -pedantic -ansi -g -O2 -fdebug-prefix-map=/tmp/
slurm-drmaa-1.0.7=. -fstack-protector-strong -Wformat -Werror=format-security -p
thread -D_REENTRANT -D_THREAD_SAFE -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -D_G
NU_SOURCE -I/usr/include/slurm/ -Wl,-Bsymbolic-functions -Wl,-z,relro -L/usr/lib
/libslurm.so conftest.c -pthread  -lslurm  >&5
conftest.c:23:11: fatal error: slurm/slurm.h: No such file or directory
  #include "slurm/slurm.h"
   ^~~
compilation terminated.

But the libslurm-dev package doesn't provide such a path:

$ dpkg -L libslurm-dev | grep usr/include
/usr/include
/usr/include/slurm-wlm
/usr/include/slurm-wlm/slurm.h
/usr/include/slurm-wlm/slurm_errno.h
/usr/include/slurm-wlm/smd_ns.h
/usr/include/slurm-wlm/spank.h
$

Certainly, /usr/include/slurm/slurm/slurm.h (as implied by the combination
of configure options with m4/ax_slurm.m4) does not exist.

It's possible this is a bug in both slurm-llnl and slurm-drmaa.

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


signature.asc
Description: PGP signature

Processed: Re: Bug#889689: pytest-arraydiff: Incomplete debian/copyright?

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #889689 [src:pytest-arraydiff] pytest-arraydiff: Incomplete 
debian/copyright?
Warning: Unknown package 'src:pytest-arraydiff'
Added tag(s) moreinfo.
Warning: Unknown package 'src:pytest-arraydiff'

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

Bug#889689: pytest-arraydiff: Incomplete debian/copyright?

[Ole Streicher]

Control: tags -1 moreinfo

Hi Chris,

thank you for the review of pytest-arraydiff!

On 05.02.2018 22:33, Chris Lamb wrote:
> I just ACCEPTed pytest-arraydiff from NEW but noticed it was missing 
> attribution in debian/copyright for at least src/jsonrpc-version-macros.h.

Hmm, there is no file src/jsonrpc-version-macros.h in the
pytest-arraydiff source? Are you sure you filed the bug against the
correct package?

Best regards

Ole

$ ls -lR
.:
insgesamt 56
-rw-r--r-- 1 ole ole  218 Feb  5 08:34 CHANGES.md
drwxr-xr-x 5 ole ole 4096 Feb  5 08:34 debian
-rw-r--r-- 1 ole ole 1448 Feb  5 08:34 LICENSE
-rw-r--r-- 1 ole ole  113 Feb  5 08:34 MANIFEST.in
-rw-r--r-- 1 ole ole 9567 Feb  5 08:34 PKG-INFO
drwxr-xr-x 3 ole ole 4096 Feb  5 08:34 pytest_arraydiff
drwxr-xr-x 2 ole ole 4096 Feb  5 08:34 pytest_arraydiff.egg-info
-rw-r--r-- 1 ole ole 7156 Feb  5 08:34 README.rst
-rw-r--r-- 1 ole ole   59 Feb  5 08:34 setup.cfg
-rwxr-xr-x 1 ole ole 1370 Feb  5 08:34 setup.py
drwxr-xr-x 3 ole ole 4096 Feb  5 08:34 tests

./debian:
insgesamt 36
-rw-r--r-- 1 ole ole  160 Feb  5 08:34 changelog
-rw-r--r-- 1 ole ole3 Feb  5 08:34 compat
-rw-r--r-- 1 ole ole 1193 Feb  5 08:34 control
-rw-r--r-- 1 ole ole 1615 Feb  5 08:34 copyright
drwxr-xr-x 2 ole ole 4096 Feb  5 08:34 patches
-rwxr-xr-x 1 ole ole  118 Feb  5 08:34 rules
drwxr-xr-x 2 ole ole 4096 Feb  5 08:34 source
drwxr-xr-x 2 ole ole 4096 Feb  5 08:34 tests
-rw-r--r-- 1 ole ole  157 Feb  5 08:34 watch

./debian/patches:
insgesamt 8
-rw-r--r-- 1 ole ole   38 Feb  5 08:34 series
-rw-r--r-- 1 ole ole 2601 Feb  5 08:34 Use-Python-3-version-of-py.test.patch

./debian/source:
insgesamt 4
-rw-r--r-- 1 ole ole 12 Feb  5 08:34 format

./debian/tests:
insgesamt 4
-rw-r--r-- 1 ole ole 34 Feb  5 08:34 control

./pytest_arraydiff:
insgesamt 20
-rwxr-xr-x 1 ole ole20 Feb  5 08:34 __init__.py
-rwxr-xr-x 1 ole ole 11576 Feb  5 08:34 plugin.py
drwxr-xr-x 2 ole ole  4096 Feb  5 08:34 __pycache__

./pytest_arraydiff/__pycache__:
insgesamt 0

./pytest_arraydiff.egg-info:
insgesamt 32
-rw-r--r-- 1 ole ole1 Feb  5 08:34 dependency_links.txt
-rw-r--r-- 1 ole ole   55 Feb  5 08:34 entry_points.txt
-rw-r--r-- 1 ole ole 9567 Feb  5 08:34 PKG-INFO
-rw-r--r-- 1 ole ole   17 Feb  5 08:34 requires.txt
-rw-r--r-- 1 ole ole  635 Feb  5 08:34 SOURCES.txt
-rw-r--r-- 1 ole ole   17 Feb  5 08:34 top_level.txt

./tests:
insgesamt 12
drwxr-xr-x 2 ole ole 4096 Feb  5 08:34 baseline
-rw-r--r-- 1 ole ole 4128 Feb  5 08:34 test_pytest_arraydiff.py

./tests/baseline:
insgesamt 40
-rw-r--r-- 1 ole ole 5760 Feb  5 08:34 test_succeeds_class.fits
-rw-r--r-- 1 ole ole   35 Feb  5 08:34 test_succeeds_func_default.txt
-rw-r--r-- 1 ole ole 5760 Feb  5 08:34 test_succeeds_func_fits.fits
-rw-r--r-- 1 ole ole 5760 Feb  5 08:34 test_succeeds_func_fits_hdu.fits
-rw-r--r-- 1 ole ole   35 Feb  5 08:34 test_succeeds_func_text.txt
-rw-r--r-- 1 ole ole 5760 Feb  5 08:34 test_tolerance.fits

Bug#882017: solution available upstream

[Christian Ehrhardt]

I tried to pick the patch mentioned before and it is ok, but not enough.
In addition Debian needs the changes in [1] to build correctly again.

[1]: https://github.com/MagicStack/asyncpg/issues/256

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd

Bug#889701: comet-ms: unsatisfiable build dependency

[Steve Langasek]

Source: comet-ms
Version: 2017012-1
Severity: serious

Hi Filippo,

The comet-ms package in Debian unstable is unbuildable on all architectures,
because it build-depends on libmstoolkit-dev (>= 82) but the most recent
version of libmstoolkit which has been uploaded to the archive is
77.0.0-1.1.  If this newer version is required, please upload it to Debian
(I see you are the maintainer of both packages); otherwise, please relax the
build-dependency.

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


signature.asc
Description: PGP signature

Processed: found 889698 in 2:3.35-1

[Debian Bug Tracking System]

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

> found 889698 2:3.35-1
Bug #889698 [nss] nss 3.35 now defaults to SQL database, broke 
certmonger/mod_nss/dogtag/freeipa
There is no source info for the package 'nss' at version '2:3.35-1' with 
architecture ''
Unable to make a source version for version '2:3.35-1'
Marked as found in versions 2:3.35-1.
> thanks
Stopping processing here.

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

Bug#889698: nss 3.35 now defaults to SQL database, broke certmonger/mod_nss/dogtag/freeipa

[Timo Aaltonen]

Package: nss
Severity: grave

Hi, please revert this commit which switched the default certificate database 
format to SQL:

https://github.com/nss-dev/nss/commit/33b114e38278c4ffbb6b244a0ebc9910e5245cd3

Several packages are not ready for it yet, including but likely not limited to:

certmonger
libapache2-mod-nss
dogtag-pki
freeipa

respective upstreams are working on it but getting everything merged will take 
a month or two.


-- 
t

Bug#888089: Really serious?

[Ondřej Surý]

Thanks for understanding. If you are to switch to embedded botan 1.10 before 
upstream sorts this out, you probably ought to upgrade the embedded version to 
latest upstream (1.10.17).

I think Christian has already filled RM bug: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889675

Ondřej 
--
Ondřej Surý 

> On 5 Feb 2018, at 21:08, Lisandro Damián Nicanor Pérez Meyer 
>  wrote:
> 
>> On 5 February 2018 at 16:54, Ondřej Surý  wrote:
>> We want to remove botan1.10 from testing, so yes, this warrants a serious 
>> severity, and it has only three r-depends:
>> 
>> 1. monotone is dead (last upstream release 2011), we shouldn’t keep zombies 
>> in Debian
>> 
>> 2. ovito is leaf package and ranked very low in popcon
>> 
>> 3. qtcreator is a leaf package[a] and ranked high in popcon
>> 
>> So I think it’s quite appropriate to fill serious bug instantly, as it 
>> doesn’t affect half of the archive, but just two (one) package.
>> 
>> From quickly skimming the Botan usage in qtcreator, I think it might be 
>> quite easy to use botan 2.x in QtCreator.  It’s just only a matter of 
>> somebody packaging it (and afaik our conversation will reset the auto-RM 
>> timer)...
> 
> ACK then. I think you should really go and file the RoM bug then, I
> can make qtcreator fall back to it's embedded version for the
> meantime.
> 
> I asked qtcreator's upstreams and so far I did not receive a reply on
> this. we want to avoid a delta with them as much as possible.

Processed: fixed 889450 in 1.3-1

[Debian Bug Tracking System]

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

> fixed 889450 1.3-1
Bug #889450 [src:django-anymail] django-anymail: CVE-2018-6596: Security issue 
with timing attack on WEBHOOK_AUTHORIZATION
Marked as fixed in versions django-anymail/1.3-1.
> thanks
Stopping processing here.

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

Processed: reopening 889450

[Debian Bug Tracking System]

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

> reopen 889450
Bug #889450 {Done: Scott Kitterman } [src:django-anymail] 
django-anymail: CVE-2018-6596: Security issue with timing attack on 
WEBHOOK_AUTHORIZATION
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions django-anymail/1.3-1.
> thanks
Stopping processing here.

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

Bug#888567: marked as done (gnome-tweaks: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Tue, 06 Feb 2018 04:04:44 +
with message-id 
and subject line Bug#888567: fixed in gnome-tweaks 3.27.90-1
has caused the Debian Bug report #888567,
regarding gnome-tweaks: Incomplete debian/copyright?
to be marked as done.

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

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


-- 
888567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-tweaks
Version: 3.27.4-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Jeremy Bicha 

Hi!

I just ACCEPTed gnome-tweaks from NEW but noticed it was missing 
attribution in debian/copyright for at least, Cosimo Cecchi,
Canonical, Red Hat, etc. etc. :)

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: gnome-tweaks
Source-Version: 3.27.90-1

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated gnome-tweaks package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 05 Feb 2018 22:48:07 -0500
Source: gnome-tweaks
Binary: gnome-tweaks gnome-tweak-tool
Architecture: source
Version: 3.27.90-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 gnome-tweak-tool - adjust advanced settings for GNOME - transitional package
 gnome-tweaks - tool to adjust advanced configuration settings for GNOME
Closes: 888567
Changes:
 gnome-tweaks (3.27.90-1) unstable; urgency=medium
 .
   * New upstream development release
   * Add install-desktop-panel.patch:
 - Install Desktop panel as long as we still offer Nautilus 3.26
   * Update debian/copyright (Closes: #888567)
Checksums-Sha1:
 b64ae3a25a22ca7a10f365fe2715a9acc6d97b92 2089 gnome-tweaks_3.27.90-1.dsc
 4d5cd3d9fe8ce5e5e4d8e1800bbf9642122eeb25 262604 
gnome-tweaks_3.27.90.orig.tar.xz
 a4a99758dc2fd1d59471b9bbc31b81253ae47341 6132 
gnome-tweaks_3.27.90-1.debian.tar.xz
 f5e08d03c360b7327676f701cb6b3db1320788f4 9189 
gnome-tweaks_3.27.90-1_source.buildinfo
Checksums-Sha256:
 c669f63b793229e30e9f923fcc0618294ee8dfaf28a5bb07ac235959e0fc984b 2089 
gnome-tweaks_3.27.90-1.dsc
 d90f5dbf3b511a117f06eab17dadb1d33ae0eb36387747b24a78150a7fee2f98 262604 
gnome-tweaks_3.27.90.orig.tar.xz
 95490172e499de7fb67c16b46e87bf9376cf5525efc0333c6e26545ab9e83478 6132 
gnome-tweaks_3.27.90-1.debian.tar.xz
 c332408caa8a179b5f5c56d292a9764ffef6a31e5d175a38b345139aed1b1c53 9189 
gnome-tweaks_3.27.90-1_source.buildinfo
Files:
 72aa8a9434f231e02c39a9d467f3dea5 2089 gnome optional gnome-tweaks_3.27.90-1.dsc
 cdecd4ed98e435ad673ef3e8ea5a8368 262604 gnome optional 
gnome-tweaks_3.27.90.orig.tar.xz
 5a7b752568e0ed437b594568cf44f278 6132 gnome optional 
gnome-tweaks_3.27.90-1.debian.tar.xz
 c7f0d6e04ddeb280db85724eb8648512 9189 gnome optional 
gnome-tweaks_3.27.90-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJaeSW4AAoJEOZsd1rr/mx9d18P/2Dj8FA9vUwufM0Wf4PRQHbk
ZthvHl3IvdTdz32yinPOwI5nc4jY6TuVr1W/ekveQ7ZDa15lgqjm65PCLUSarH47
PlCRPDDMOATcFc3pjMLykIizh+ZhOPEsBRlExkJhajUM46uGAQg8fOSK9huA5ht/
1UAlngEGL2SppMZTt0lavc9ZMHUzpqVDlzyjbhzs8uz0z3TInTZH+4OsIAddUjBb
bYBoLQbCYPPAV91VddEt+UnbEt8fy2Gy8o645nwc9n/fqdzhsHSBkNR9mRZNBD0C
x988vJeeDgaWwTFTDbNVMt2Whliznp19fhEc66jLdH12lGZEycrmcPYHwuVy99el
AAtMIX9ClE1lgMVRPsBw4Jzc10JnH+jWQyznvz2oQR8Y42bUNS25Y3ZEed6rGNVH
PmATyLCwlybwn2WfsCKx2yYjNumZMs5Y4CZIzTxnG0yxEutNd2nP7YdSJRnjhIre
uDmDgsdDSkwzNpVkePLVR5OrG5LaS/d+rNdXf8FfjOBe4qe4kX5goLEpc4Z/v/Pd
lOIDlahJhbKrHBQvb+u9RIOb/VGrsQn1ysClXqsVacEV/UhAUuZI293Due6TnqNB
33qPJoaII/x4zHy/AVnvBPeH/EZpY7Yci7p+/N6xZM7e8uOzDV1Ym6xy/sv6Zt/l
1aB5S3Mm/IvYcD2rDIMD
=swmA
-END PGP SIGNATURE End Message ---

Processed: tagging 888194

[Debian Bug Tracking System]

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

> tags 888194 + fixed-upstream
Bug #888194 [src:ruby-safe-yaml] ruby-safe-yaml: FTBFS on ruby2.5: 
uninitialized constant SafeYAML::Parse::Date::DateTime
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: bug 888194 is forwarded to https://github.com/dtao/safe_yaml/issues/80

[Debian Bug Tracking System]

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

> forwarded 888194 https://github.com/dtao/safe_yaml/issues/80
Bug #888194 [src:ruby-safe-yaml] ruby-safe-yaml: FTBFS on ruby2.5: 
uninitialized constant SafeYAML::Parse::Date::DateTime
Set Bug forwarded-to-address to 'https://github.com/dtao/safe_yaml/issues/80'.
> thanks
Stopping processing here.

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

Processed: tagging 889510

[Debian Bug Tracking System]

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

> tags 889510 + pending
Bug #889510 [src:ruby-rspec] ruby-rspec: FTBFS with ruby2.5
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 888194

[Debian Bug Tracking System]

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

> tags 888194 + upstream
Bug #888194 [src:ruby-safe-yaml] ruby-safe-yaml: FTBFS on ruby2.5: 
uninitialized constant SafeYAML::Parse::Date::DateTime
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#886944: python3-regex: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Nicholas D Steeves]

Hi Andreas and Sandro,

On Thu, Jan 11, 2018 at 05:04:13PM +0100, Andreas Beckmann wrote:
> Followup-For: Bug #886944
> Control: affects -1 + python-regex-dbg
> 
> Hi,
> 
> similar issue in python-regex-dbg:
> 
> 0m33.5s ERROR: FAIL: silently overwrites files via directory symlinks:
>   /usr/share/doc/python-regex-dbg/Features.html (python-regex-dbg) != 
> /usr/share/doc/python-regex/Features.html (python-regex)
> /usr/share/doc/python-regex-dbg -> python-regex
>   /usr/share/doc/python-regex-dbg/Features.rst.gz (python-regex-dbg) != 
> /usr/share/doc/python-regex/Features.rst.gz (python-regex)
> /usr/share/doc/python-regex-dbg -> python-regex
>   /usr/share/doc/python-regex-dbg/README (python-regex-dbg) != 
> /usr/share/doc/python-regex/README (python-regex)
> /usr/share/doc/python-regex-dbg -> python-regex
>   /usr/share/doc/python-regex-dbg/UnicodeProperties.txt.gz (python-regex-dbg) 
> != /usr/share/doc/python-regex/UnicodeProperties.txt.gz (python-regex)
> /usr/share/doc/python-regex-dbg -> python-regex
>   /usr/share/doc/python-regex-dbg/changelog.Debian.gz (python-regex-dbg) != 
> /usr/share/doc/python-regex/changelog.Debian.gz (python-regex)
> /usr/share/doc/python-regex-dbg -> python-regex
>   /usr/share/doc/python-regex-dbg/copyright (python-regex-dbg) != 
> /usr/share/doc/python-regex/copyright (python-regex)
> /usr/share/doc/python-regex-dbg -> python-regex
> 
> and probably python3-regex-dbg as well, although that does not get
> tested by piuparts as long as python3-regex fails.
> 
> 
> Andreas

I'll attempt to fix this evening, because if calibre is removed from
testing than my planned backport will be in jeopardy.  If I succeed
I'll prepare an NMU, but in any case I'll reply to this bug with my
results.

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#888930: marked as done (libgltf FTBFS with libglm-dev 0.9.9~a2-1)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 21:35:30 +
with message-id 
and subject line Bug#888930: fixed in libgltf 0.1.0-3
has caused the Debian Bug report #888930,
regarding libgltf  FTBFS with libglm-dev 0.9.9~a2-1
to be marked as done.

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

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


-- 
888930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgltf
Version: 0.1.0-2
Severity: serious

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

...
checking epoxy/gl.h usability... yes
checking epoxy/gl.h presence... yes
checking for epoxy/gl.h... yes
checking glm/glm.hpp usability... yes
checking glm/glm.hpp presence... yes
checking for glm/glm.hpp... yes
checking glm/gtc/matrix_inverse.hpp usability... yes
checking glm/gtc/matrix_inverse.hpp presence... yes
checking for glm/gtc/matrix_inverse.hpp... yes
checking glm/gtc/matrix_transform.hpp usability... yes
checking glm/gtc/matrix_transform.hpp presence... yes
checking for glm/gtc/matrix_transform.hpp... yes
checking glm/gtc/quaternion.hpp usability... yes
checking glm/gtc/quaternion.hpp presence... yes
checking for glm/gtc/quaternion.hpp... yes
checking glm/gtc/type_ptr.hpp usability... yes
checking glm/gtc/type_ptr.hpp presence... yes
checking for glm/gtc/type_ptr.hpp... yes
checking glm/gtx/quaternion.hpp usability... no
checking glm/gtx/quaternion.hpp presence... no
checking for glm/gtx/quaternion.hpp... no
configure: error: Required glm headers not found. Install glm >= 0.9.0.0
--- End Message ---
--- Begin Message ---
Source: libgltf
Source-Version: 0.1.0-3

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

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

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libgltf 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, 05 Feb 2018 21:05:03 +
Source: libgltf
Binary: libgltf-dev libgltf-0.1-1
Architecture: source amd64
Version: 0.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Rene Engelhard 
Description:
 libgltf-0.1-1 - Library for rendering glTF models
 libgltf-dev - Library for rendering glTF models -- development
Closes: 888930
Changes:
 libgltf (0.1.0-3) unstable; urgency=medium
 .
   * fix build with glm 0.9.9 by defining -DGLM_ENABLE_EXPERIMENTAL in
 GLM_CFLAGS (closes: #888930)
   * set Maintainer to Debian QA Group 
Checksums-Sha1:
 c0d10f2ee82a5495f79e365d8a3b02bf2412d6b0 1913 libgltf_0.1.0-3.dsc
 ad61e192c89903fb5e790b123c14bfd44208a73b 8852 libgltf_0.1.0-3.debian.tar.xz
 8cfd0ef3e99c0eb132efe8965628f2880e9844d1 1331412 
libgltf-0.1-1-dbgsym_0.1.0-3_amd64.deb
 9a835cffd1f6caddc610038abae08d10ce54e5c8 136360 libgltf-0.1-1_0.1.0-3_amd64.deb
 91e3cd4e5dccbc5dc87f37868cf2fb8b79e3fd6d 144248 libgltf-dev_0.1.0-3_amd64.deb
 50e7c261fefe8dcc647cdd4615e3633d9cdb4a0c 6336 libgltf_0.1.0-3_amd64.buildinfo
Checksums-Sha256:
 a921a8aecf4a2f4f28c6c6348ad2504996609e1da034ded561eae3f4ee511fc5 1913 
libgltf_0.1.0-3.dsc
 17b3058eb158c324effe463b746284d83160c64937cf559efc3dcac1a6cd84b0 8852 
libgltf_0.1.0-3.debian.tar.xz
 a759afc91ca05d31ab96d0cbde80e51263f9fda129c40c56fbba6f61c57de530 1331412 
libgltf-0.1-1-dbgsym_0.1.0-3_amd64.deb
 d980e9eb984993a6311228ed2ed2beb1072e68e500e230130f51dd057884be1c 136360 
libgltf-0.1-1_0.1.0-3_amd64.deb
 f7b5a9ec371b60f569444e2073406e521589dd99a6bd02106b5a42de0ec7288f 144248 
libgltf-dev_0.1.0-3_amd64.deb
 7acf203611b65d35e6485203abf4f2bb34e9d256dd50abd80a4aa581a6c724f5 6336 
libgltf_0.1.0-3_amd64.buildinfo
Files:
 d978d4e0d443d3a4876bd042d8198bf6 1913 libs optional libgltf_0.1.0-3.dsc
 1e8a553308f5e0a1e86dff94248d151b 8852 libs optional 
libgltf_0.1.0-3.debian.tar.xz
 b5d07762d47b996d4ab0a586ae1c7664 1331412 debug optional 
libgltf-0.1-1-dbgsym_0.1.0-3_amd64.deb
 c38b59dc64294bcbd7ee8ae6ad10ddba 136360 libs optional 
libgltf-0.1-1_0.1.0-3_amd64.deb
 

Processed: php-db pull request

[Debian Bug Tracking System]

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

> forwarded 889532 https://github.com/pear/DB/pull/5
Bug #889532 [src:php-db] php-db FTBFS with PHP 7.2
Set Bug forwarded-to-address to 'https://github.com/pear/DB/pull/5'.
>
End of message, stopping processing here.

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

Bug#889689: pytest-arraydiff: Incomplete debian/copyright?

[Chris Lamb]

Source: pytest-arraydiff
Version: 0.2-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Ole Streicher 

Hi,

I just ACCEPTed pytest-arraydiff from NEW but noticed it was missing 
attribution in debian/copyright for at least src/jsonrpc-version-macros.h.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

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

Bug#880318: marked as done (mongo-java-driver: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 21:12:27 +
with message-id 
and subject line Bug#880318: fixed in mongo-java-driver 3.6.2-1
has caused the Debian Bug report #880318,
regarding mongo-java-driver: FTBFS: Test failures
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.)


-- 
880318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mongo-java-driver
Version: 3.3.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20171030 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):
>   at 
> org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
>   at 
> org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
>   at 
> org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:72)
>   at 
> org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
>   at 
> org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
>   at 
> org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:50)
>   at 
> org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:293)
>   at 
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
>   at 
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at java.lang.Thread.run(Thread.java:748)
> 
> dh_auto_build: gradle --info --console plain --offline --stacktrace 
> --no-daemon --refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
> -Duser.name=debian -Ddebian.package=mongo-java-driver -Dfile.encoding=UTF-8 
> check -x :bson:checkstyleMain -x :bson:checkstyleTest -x 
> driver:checkstyleMain -x driver:checkstyleTest -x 
> driver-core:compileTestGroovy -x driver:compileTestGroovy -x 
> driver-async:checkstyleMain -x driver-async:checkstyleTest -x 
> driver-async:compileTestGroovy -x driver-core:checkstyleMain -x 
> driver-core:checkstyleTest returned exit code 1
> Cleanup
> debian/rules:9: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/10/30/mongo-java-driver_3.3.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: mongo-java-driver
Source-Version: 3.6.2-1

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated mongo-java-driver 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 05 Feb 2018 21:20:02 +0100
Source: mongo-java-driver
Binary: libmongodb-java
Architecture: source
Version: 3.6.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libmongodb-java - MongoDB Java Driver
Closes: 880318
Changes:
 mongo-java-driver (3.6.2-1) unstable; urgency=medium
 .
   * Team upload.
   [ Christopher Hoskin ]
   * Update patches
 .
   [ Markus Koschany ]
   * New upstream version 3.6.2.
   

Processed: retitle 889688 to gweled crashes when rsvg reports an error

[Debian Bug Tracking System]

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

> retitle 889688 gweled crashes when rsvg reports an error
Bug #889688 [gweled] rsvg_pixbuf_from_file_at_size broken in recent librsvg2-2
Changed Bug title to 'gweled crashes when rsvg reports an error' from 
'rsvg_pixbuf_from_file_at_size broken in recent librsvg2-2'.
> thanks
Stopping processing here.

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

Bug#866448: marked as done (openshot: depends on obsolete python-imaging (replace with python3-pil or python-pil))

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 21:12:39 +
with message-id 
and subject line Bug#866448: fixed in openshot-qt 2.4.1-2
has caused the Debian Bug report #866448,
regarding openshot: depends on obsolete python-imaging (replace with 
python3-pil or python-pil)
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.)


-- 
866448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openshot
Version: 1.4.3-1.2
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.
--- End Message ---
--- Begin Message ---
Source: openshot-qt
Source-Version: 2.4.1-2

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated openshot-qt 
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, 05 Feb 2018 21:41:12 +0100
Source: openshot-qt
Binary: openshot-qt openshot-qt-doc openshot openshot-doc
Architecture: source
Version: 2.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Dr. Tobias Quathamer 
Description:
 openshot   - create and edit videos and movies (transitional package)
 openshot-doc - documentation for openshot-qt (transitional package)
 openshot-qt - create and edit videos and movies
 openshot-qt-doc - documentation for openshot-qt
Closes: 705928 725095 785562 814734 866448 879778
Changes:
 openshot-qt (2.4.1-2) unstable; urgency=medium
 .
   * Switch Vcs-URLs to salsa.d.o
   * Use debhelper v11
   * Update d/copyright
   * Update Standards-Version to 4.1.3, no changes needed
   * Add transitional packages for openshot and openshot-doc.
 This should ensure an upgrade path after upstream's
 renaming of the application. (Closes: #879778)
 Also, it should fix a lot of bugs in the openshot package:
 - No longer depend on deprecated python-pygoocanvas. (Closes: #785562)
 - No longer depend on obsolete python-imaging. (Closes: #866448)
 - Update to latest upstream version. (Closes: #814734)
 - Remove dependency on rarian-compat for openshot-doc. (Closes: #725095)
 - Do not ship embedded copy of python-gdata. (Closes: #705928)
Checksums-Sha1:
 98042d1af6a361110dbe140ac984908de57b05ec 2258 openshot-qt_2.4.1-2.dsc
 2b740fc6cf4361e876d67c457d30c29fb7ff5cd3 208048 
openshot-qt_2.4.1-2.debian.tar.xz
 e8d66a57da95a66fccc167bfac55dd89899ee618 7583 
openshot-qt_2.4.1-2_amd64.buildinfo
Checksums-Sha256:
 e7ce8aeacc289eee578d34dba2b4c1264c117eaefca1895bdff6bca5341af5f9 2258 
openshot-qt_2.4.1-2.dsc
 d765d88e4c3932d382b7f36407d2f24cbaa1df1e9c99915613efac623bbf332f 208048 
openshot-qt_2.4.1-2.debian.tar.xz
 e077d51fac071d5d6df7cbd9aa1c7579121cbc4b57a5fa9b7314b896740288a4 7583 
openshot-qt_2.4.1-2_amd64.buildinfo
Files:
 84fa3c6d119fa79177767a1b8444b5cf 2258 video optional openshot-qt_2.4.1-2.dsc
 acb6f8e09fe7e14ffaa1e67337125ea3 208048 video optional 
openshot-qt_2.4.1-2.debian.tar.xz
 458f25fd1eb7f36f60a705bc4c386b5a 7583 video optional 
openshot-qt_2.4.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlp4wtwACgkQEwLx8Dbr
6xk9wQ//UNs0qv/axXYhX5P7MOsqMFTiVk+xSIPGJiJERDLHOH7MHtY2F04wgP2v
ODTjRxWIZtbZIo3XDMFJj5HOwKx8sh0IKIKe9eKBlKUcF/vZZ3YEJDN5kZDKL4CD
IH9/WwIKWuI1wV+7N+ew88xzPVLvqNY/rp6LqmoJz/AGIJrnkXLIpaD25nNC8Vff
GenhHl7YN8oWxJ7JHhjcfjrdhHhGLJHEXQHTY/Z+wQxaKmMIHNJXpbo2JhHVS8tL

Bug#785562: marked as done (openshot: python-pygoocanvas deprecated)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 21:12:39 +
with message-id 
and subject line Bug#785562: fixed in openshot-qt 2.4.1-2
has caused the Debian Bug report #785562,
regarding openshot: python-pygoocanvas deprecated
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.)


-- 
785562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openshot
Version: 1.4.3-1.1
Severity: important

Dear Maintainer,

The latest version of goocanvas (2.0.2) has been sitting in experimental for
some time. Now that Jessie has been released, I am looking at all the reverse
dependencies to see what would be required to start the transition.

Python-pygoocanvas is one of the reverse dependencies that blocks the
transition. It has been deprecated upstream, and all software projects using
pygoocanvas are encouraged to port their applications to use the GObject
Introspection library provided in the latest goocanvas package and to move away
from GTK+2 to GTK+3.

Are there any plans to switch to gir1.2-goocanvas-2.0?

Regards,

Ross



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

Kernel: Linux 3.16.0-37-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: openshot-qt
Source-Version: 2.4.1-2

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated openshot-qt 
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, 05 Feb 2018 21:41:12 +0100
Source: openshot-qt
Binary: openshot-qt openshot-qt-doc openshot openshot-doc
Architecture: source
Version: 2.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Dr. Tobias Quathamer 
Description:
 openshot   - create and edit videos and movies (transitional package)
 openshot-doc - documentation for openshot-qt (transitional package)
 openshot-qt - create and edit videos and movies
 openshot-qt-doc - documentation for openshot-qt
Closes: 705928 725095 785562 814734 866448 879778
Changes:
 openshot-qt (2.4.1-2) unstable; urgency=medium
 .
   * Switch Vcs-URLs to salsa.d.o
   * Use debhelper v11
   * Update d/copyright
   * Update Standards-Version to 4.1.3, no changes needed
   * Add transitional packages for openshot and openshot-doc.
 This should ensure an upgrade path after upstream's
 renaming of the application. (Closes: #879778)
 Also, it should fix a lot of bugs in the openshot package:
 - No longer depend on deprecated python-pygoocanvas. (Closes: #785562)
 - No longer depend on obsolete python-imaging. (Closes: #866448)
 - Update to latest upstream version. (Closes: #814734)
 - Remove dependency on rarian-compat for openshot-doc. (Closes: #725095)
 - Do not ship embedded copy of python-gdata. (Closes: #705928)
Checksums-Sha1:
 98042d1af6a361110dbe140ac984908de57b05ec 2258 openshot-qt_2.4.1-2.dsc
 2b740fc6cf4361e876d67c457d30c29fb7ff5cd3 208048 
openshot-qt_2.4.1-2.debian.tar.xz
 e8d66a57da95a66fccc167bfac55dd89899ee618 7583 
openshot-qt_2.4.1-2_amd64.buildinfo
Checksums-Sha256:
 e7ce8aeacc289eee578d34dba2b4c1264c117eaefca1895bdff6bca5341af5f9 2258 
openshot-qt_2.4.1-2.dsc
 d765d88e4c3932d382b7f36407d2f24cbaa1df1e9c99915613efac623bbf332f 208048 
openshot-qt_2.4.1-2.debian.tar.xz
 e077d51fac071d5d6df7cbd9aa1c7579121cbc4b57a5fa9b7314b896740288a4 7583 
openshot-qt_2.4.1-2_amd64.buildinfo
Files:
 84fa3c6d119fa79177767a1b8444b5cf 2258 video optional openshot-qt_2.4.1-2.dsc
 acb6f8e09fe7e14ffaa1e67337125ea3 208048 video optional 

Processed: Re: Bug#886833: [gweled] Not compatable with recent gtk

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #886833 [librsvg2-2] rsvg_pixbuf_from_file_at_size broken in recent 
librsvg2-2
Bug 886833 cloned as bug 889688
> reassign -2 gweled
Bug #889688 [librsvg2-2] rsvg_pixbuf_from_file_at_size broken in recent 
librsvg2-2
Bug reassigned from package 'librsvg2-2' to 'gweled'.
No longer marked as found in versions librsvg/2.40.20-2.
Ignoring request to alter fixed versions of bug #889688 to the same values 
previously set
> found -2 0.9.1-4
Bug #889688 [gweled] rsvg_pixbuf_from_file_at_size broken in recent librsvg2-2
Marked as found in versions gweled/0.9.1-4.

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

Bug#886833: [gweled] Not compatable with recent gtk

[Stephen Kitt]

Control: clone -1 -2
Control: reassign -2 gweled
Control: found -2 0.9.1-4

On Mon, 5 Feb 2018 09:51:08 +0100, Stephen Kitt  wrote:
> This can be fixed from gweled by prepending “file:/”, but that seems like a
> brittle fix since rsvg_pixbuf_from_file_at_size() supposedly expects a
> filename — although providing a URI also works fine in librsvg2-2 2.40.16 so
> who knows.

gweled needs a number of other fixes for its error handling here anyway, so
I’m cloning this bug so we can track that too.

Regards,

Stephen


pgpVARXbzEEXq.pgp
Description: OpenPGP digital signature

Bug#889558: qtcreator: (Build-)Depends on obsolete libbotan1.10-dev

[Lisandro Damián Nicanor Pérez Meyer]

forwarded 889558 https://bugreports.qt.io/browse/QTCREATORBUG-19745
thanks

It seems that qt creator is the only real package preventing the botan 
removal, so please go ahead with it. I'll make qtcreator use it's internal 
copy for the moment being.

Kinds regards, Lisandro.


-- 
You are the Doc, Doc!
  Marty McFly To Dr. Emmett Brown, Back to the Future III

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


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

Bug#888089: Really serious?

[Lisandro Damián Nicanor Pérez Meyer]

On 5 February 2018 at 16:54, Ondřej Surý  wrote:
> We want to remove botan1.10 from testing, so yes, this warrants a serious 
> severity, and it has only three r-depends:
>
> 1. monotone is dead (last upstream release 2011), we shouldn’t keep zombies 
> in Debian
>
> 2. ovito is leaf package and ranked very low in popcon
>
> 3. qtcreator is a leaf package[a] and ranked high in popcon
>
> So I think it’s quite appropriate to fill serious bug instantly, as it 
> doesn’t affect half of the archive, but just two (one) package.
>
> From quickly skimming the Botan usage in qtcreator, I think it might be quite 
> easy to use botan 2.x in QtCreator.  It’s just only a matter of somebody 
> packaging it (and afaik our conversation will reset the auto-RM timer)...

ACK then. I think you should really go and file the RoM bug then, I
can make qtcreator fall back to it's embedded version for the
meantime.

I asked qtcreator's upstreams and so far I did not receive a reply on
this. we want to avoid a delta with them as much as possible.

Bug#888089: Really serious?

[Ondřej Surý]

We want to remove botan1.10 from testing, so yes, this warrants a serious 
severity, and it has only three r-depends:

1. monotone is dead (last upstream release 2011), we shouldn’t keep zombies in 
Debian

2. ovito is leaf package and ranked very low in popcon

3. qtcreator is a leaf package[a] and ranked high in popcon

So I think it’s quite appropriate to fill serious bug instantly, as it doesn’t 
affect half of the archive, but just two (one) package.

From quickly skimming the Botan usage in qtcreator, I think it might be quite 
easy to use botan 2.x in QtCreator.  It’s just only a matter of somebody 
packaging it (and afaik our conversation will reset the auto-RM timer)...

~~~

a:
Checking reverse dependencies...
# Broken Build-Depends:
gcompris-qt: qtcreator

O.
--
Ondřej Surý
ond...@sury.org

> On 5 Feb 2018, at 20:20, Lisandro Damián Nicanor Pérez Meyer 
>  wrote:
> 
> The fact that botan is going to loose support doesn't makes this an instant 
> RC 
> bug. Not the fact that you want to remove it.
> 
> You should really consider raising the rdepends bugs to severity serious once 
> the RoM bug for botan has been filed.
> 
> -- 
> 20:57  * m4rgin4l patento el proceso de invencion
> 20:57 < m4rgin4l> de aqui en mas cualquier inventor me tiene que pagar
> regalias por inventar algo
> 20:57  * m4rgin4l tiene la patente pendiente del metodo cientifico
> 
> Lisandro Damián Nicanor Pérez Meyer
> http://perezmeyer.com.ar/
> http://perezmeyer.blogspot.com/

Bug#888297: closed by Robert Luberda <rob...@debian.org> (Bug#888297: fixed in p7zip 16.02+dfsg-5)

[Robert Luberda]

Antoine Beaupré writes:

Hi,

>> The check for cur against kNumItems is missing, not sure this can
>> cause any further problem.
> 
> I concur: the original researcher explicitly sent me a patch that checks
> the `cur` counter as well.

Thanks, I'm just uploading -6 with updated patch.

Regards,
robert

Bug#889293: src:alot: Please drop "Use file-magic instead of python-magic" patch, alot will FTBFS soon

[Christoph Biedl]

Christoph Biedl wrote...

> Also, I've prepared a NMU as attached but found alot fails to build on
> some (non-release) archs and like to investigate first. Feel free to go
> ahead, though.

No worries, this turned out to be a schroot configuration issue.

So I uploaded the NMU to DELAYED/7, diff debdiff as in the previous
message. Please feel free to tell me if I should delay it longer.

Regards,

Christoph


signature.asc
Description: PGP signature

Bug#888089: Really serious?

[Lisandro Damián Nicanor Pérez Meyer]

The fact that botan is going to loose support doesn't makes this an instant RC 
bug. Not the fact that you want to remove it.

You should really consider raising the rdepends bugs to severity serious once 
the RoM bug for botan has been filed.

-- 
20:57  * m4rgin4l patento el proceso de invencion
20:57 < m4rgin4l> de aqui en mas cualquier inventor me tiene que pagar
regalias por inventar algo
20:57  * m4rgin4l tiene la patente pendiente del metodo cientifico

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


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

Bug#889558: qtcreator: (Build-)Depends on obsolete libbotan1.10-dev

[Lisandro Damián Nicanor Pérez Meyer]

severity 889558 important
thanks

El domingo, 4 de febrero de 2018 11:25:37 -03 Christian Hofstaedtler escribió:
> Package: qtcreator
> Version: 4.5.0-2
> Severity: serious
> 
> Dear Maintainer,
> 
> your package qtcreator (build-)depends on botan1.10, which itself is
> obsolete. Upstream will end security support at the end of 2018, so it
> must not be part of buster.
> 
> Please drop the libbotan1.10-dev build dependency.

The fact that a lib will loose support does not make it insta RC. You can 
raise the severity once the removal bug for libbotab1.10 is filed.


-- 
Bebe a bordo (pero con moderación)

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


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

Bug#888930: Bug #888930 in libgltf marked as pending

[rene]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/libgltf/commit/5cab72f7dad82afc48723c901980fd9e3a3eb7a9


fix build with glm 0.9.9 by defining -DGLM_ENABLE_EXPERIMENTAL in GLM_CFLAGS 
(closes: #888930)



(this message was generated automatically)
-- 
Greetings

Processed: Bug #888930 in libgltf marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #888930 [src:libgltf] libgltf  FTBFS with libglm-dev 0.9.9~a2-1
Added tag(s) pending.

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

Bug#889615: marked as done (python-tifffile: broken autopkgtest, broken package)

[Debian Bug Tracking System]

Your message dated Mon, 5 Feb 2018 11:11:48 -0800
with message-id <20180205191148.hbjhq4n3kwfnj...@virgil.dodds.net>
and subject line Re: Bug#889623 closed by Andreas Tille  
(Bug#889623: fixed in tifffile 20170929-1)
has caused the Debian Bug report #889615,
regarding python-tifffile: broken autopkgtest, broken package
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.)


-- 
889615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tifffile
Version: 20170914-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic autopkgtest

Dear Andreas,

Since the upload of tifffile 20170914-1, the autopkgtests for this package
hav been consistently failing in both Debian and Ubuntu.  While the test
failure is (unfortunately) not considered a blocker for Debian testing,
autopkgtest regressions are blockers for Ubuntu releases.

The failure shows that the module simply fails a python import test,
indicating that the package has missing dependencies; therefore I am marking
this bug 'serious'.

autopkgtest [19:30:42]: test python-import: [---
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.1pxu7uus/downtmp/build.LXT/src/debian/tests/python-import",
 line 5, in 
import tifffile
  File "/usr/lib/python2.7/dist-packages/tifffile.py", line 313, in 
import enum
ImportError: No module named enum
autopkgtest [19:30:42]: test python-import: ---]
autopkgtest [19:30:42]: test python-import:  - - - - - - - - - - results - - - 
- - - - - - -
python-importFAIL non-zero exit status 1

  https://ci.debian.net/packages/t/tifffile/unstable/amd64/

After installing the python-enum34 package, the autopkgtest still fails with
another import error about concurrent.futures (package:
python-concurrent.futures).

And if all of these undeclared dependencies are installed, the test still
fails:

$ ./debian/tests/python-import 
2017.09.14
Traceback (most recent call last):
  File "./debian/tests/python-import", line 16, in 
for page in tif:
TypeError: 'TiffFile' object is not iterable
$

This part looks like it might be a bug in the test rather than the package,
but without being familiar with the package it's hard for me to know.

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Control: reopen 889623
Version: 20170929-1

Looks like the wrong bug was referenced in the changelog; closing the right
one and reopening.


On Mon, Feb 05, 2018 at 01:27:11PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:kraken package:
> 
> #889623: kraken: failing autopkgtest, possibly broken package
> 
> It has been closed by Andreas Tille .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Andreas Tille 
>  by
> replying to this email.
> 
> 
> -- 
> 889623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889623
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> Date: Mon, 05 Feb 2018 13:24:25 +
> From: Andreas Tille 
> To: 889623-cl...@bugs.debian.org
> Subject: Bug#889623: fixed in tifffile 20170929-1
> 
> Source: tifffile
> Source-Version: 20170929-1
> 
> We believe that the bug you reported is fixed in the latest version of
> tifffile, 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 889...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Andreas Tille  (supplier of updated tifffile 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)
> 
> 
> 

Bug#889646: marked as done (knot-resolver: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 19:05:16 +
with message-id 
and subject line Bug#889646: fixed in knot-resolver 2.0.0-2
has caused the Debian Bug report #889646,
regarding knot-resolver: Incomplete debian/copyright?
to be marked as done.

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

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


-- 
889646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: knot-resolver
Version: 2.0.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Daniel Kahn Gillmor 

Hi,

I just ACCEPTed knot-resolver from NEW but noticed it was missing 
attribution in debian/copyright for at least the faketime, libswrap
and lmdb code copies.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: knot-resolver
Source-Version: 2.0.0-2

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated knot-resolver 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 05 Feb 2018 13:46:25 -0500
Source: knot-resolver
Binary: knot-resolver knot-resolver-module-http knot-resolver-doc libkres5 
libkres-dev
Architecture: source
Version: 2.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: knot-resolver packagers 
Changed-By: Daniel Kahn Gillmor 
Description:
 knot-resolver - caching, DNSSEC-validating DNS resolver
 knot-resolver-doc - Documentation for Knot Resolver
 knot-resolver-module-http - HTTP/2 module for Knot Resolver
 libkres-dev - caching, DNSSEC-validating DNS resolver (shared library developme
 libkres5   - caching, DNSSEC-validating DNS resolver (shared library)
Closes: 889646
Changes:
 knot-resolver (2.0.0-2) unstable; urgency=medium
 .
   * Simplify /etc/default/kresd
   * drop preinst special case for versions < 1.1.0-2
   * postinst: create the knot-resolver user at configure time
   * initscript knows path to /usr/lib/tmpfiles.d/knot-resolver.conf
   * Overhaul systemd integration.
   * d/copyright: include more contributed subprojects (Closes: #889646)
Checksums-Sha1:
 8832b828b62eef7da0ef719c41c98010749dede8 2851 knot-resolver_2.0.0-2.dsc
 9594f150820e6b51c346863098c02b8529d4ad8b 400476 
knot-resolver_2.0.0-2.debian.tar.xz
 e4534ee1a6d65c0a6b915d3abf35ca9ad8403b99 10929 
knot-resolver_2.0.0-2_amd64.buildinfo
Checksums-Sha256:
 715e72172a91511e128ab39a79df2eef673efe506a5e38e76c3644ad8d8b8175 2851 
knot-resolver_2.0.0-2.dsc
 af508ba406cab21c200f4186fdfd1aaafcc81426b92817f893a566d8009ecc41 400476 
knot-resolver_2.0.0-2.debian.tar.xz
 946908e89b31ec06a71420e5fb324495c8068181377fec941c9cfec4d50a229a 10929 
knot-resolver_2.0.0-2_amd64.buildinfo
Files:
 a1408407fdbf761c52e7e22f55ca8640 2851 net optional knot-resolver_2.0.0-2.dsc
 0b363ccde30331c58b6d548686fc3846 400476 net optional 
knot-resolver_2.0.0-2.debian.tar.xz
 28ec96d2b3dc1e6923f71b9df7f2c9bf 10929 net optional 
knot-resolver_2.0.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEzicvlOwymaWlnoHjyu+ogyFnUzMFAlp4pu8ACgkQyu+ogyFn
UzPZ5w//cEZw1bENWWG4bDBckmkEhzIY5e/4U5vW6S4/K4NB6blpzJj5tyxpeoxA
7KhyTR1cMWXZgFMkajaGP8CkJY3cNzp+BpnbKFvUcxhy87yi9efCa3dGei2MXOkh
7T8YUoaPkDN5nAwgrOWQqVCDjVb1fNkW2Z4XC00UVzmJB1GEUGN/JaYdA2Tr/cnT
9hGviIBdrGq4BdCorpO1VqRRl2YL67cuKS+FPqAEuoMnCtxxVesMP82pV+T1Fuq+
g/n9CQHnkDlADfuhyJyLkIcDZJCrWOQ50W3M0R6MBEKyf1V46Zo38GVU0s3H8Dnt
/ySf1G/qBaeiIkG4k9yof2cjzTGub4vfaRsJakRQIBqjLdCPHvwlZ2YOIUP3VvCk
bcl+7/wru5iYCEIA8si+ejWbqRyGezNU6kPdwMD/lpR2gaI05vhHFlUD1le5A2s1
G4tEUPgifmmxsMXXubR06LW+ih4pR8PANYr+69ljEPkFK2SHv95DUSIo6GcmRjKk
Q+YWIIEo3COiFM+dD+KJDpJVjeo4jp9/O3y0noyynvEzpcpsu9v143MQHEX800cU

Bug#888598: marked as done (cpputest: FTBFS with debhelper/11.1 due to empty build target)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 18:34:55 +
with message-id 
and subject line Bug#888598: fixed in cpputest 3.8-6
has caused the Debian Bug report #888598,
regarding cpputest: FTBFS with debhelper/11.1 due to empty build target
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.)


-- 
888598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpputest
Version: 3.8-5
Severity: serious
Tags: patch

Hi,

The cpputest package FTBFS with debhelper/11.1 as it has an
empty build target.  This is caused by debhelper had a bug in its
handling of "explicitly defined rules targets" that has now been
fixed.

Previously, this happened to work because dpkg-buildpackage would
invoke "debian/rules build" (which would be a no-op) followed by
"fakeroot debian/rules binary".  During the binary target, dh's
suboptimal handling would run the build commands.


The solution is trivial but less pretty; explicitly define "build"
with the same content as the "%:" target (or rename the "build" folder
and drop the ".PHONY" target).  I have attached a patch for this.

(There is also a bonus patch for a missing "set -e")


More details can be found in:
 * #886901 comment #35
 * #887688 comment #37
 * #880840

Apologies for the inconvenience.

Thanks,
~Niels
>From 7a82e9dd46d8ca621f2b76636497b82cc19cc8df Mon Sep 17 00:00:00 2001
From: Niels Thykier 
Date: Sat, 27 Jan 2018 15:31:16 +
Subject: [PATCH] Avoid empty build target

The dh sequencer as of debhelper/11.1 is stricter with this in order
to solve #880840 (where debhelper would fail to handle such targets
correctly).

Signed-off-by: Niels Thykier 
---
 debian/rules | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/debian/rules b/debian/rules
index e62f756..ee8ed94 100755
--- a/debian/rules
+++ b/debian/rules
@@ -3,6 +3,12 @@
 %:
dh $@ --with autoreconf
 
+# The build target must not be empty.  Sadly because of how make
+# works, we have do duplicate the target in this case.
+build:
+   dh $@ --with autoreconf
+
+
 override_dh_auto_configure:
dh_auto_configure -- --disable-silent-rules
 
-- 
2.15.1

--- End Message ---
--- Begin Message ---
Source: cpputest
Source-Version: 3.8-6

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

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

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

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated cpputest package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 05 Feb 2018 18:56:17 +0100
Source: cpputest
Binary: cpputest libcpputest-dev
Architecture: source
Version: 3.8-6
Distribution: unstable
Urgency: medium
Maintainer: Raphaël Hertzog 
Changed-By: Raphaël Hertzog 
Description:
 cpputest   - C/C++ based unit test framework — main package
 libcpputest-dev - C/C++ based unit test framework — headers and static 
libraries
Closes: 888598
Changes:
 cpputest (3.8-6) unstable; urgency=medium
 .
   * Add explicit "build" target in debian/rules due to the existence of a
 "build" directory in the upstream files. Closes: #888598
   * Switch to debhelper 11.
   * Bump Standards-Version to 4.1.3.
   * Do not run test suite if DEB_BUILD_OPTIONS contains nocheck.
Checksums-Sha1:
 3a8a91762bb8e29d25cd2c368c7c4c0bd87d3a73 1648 cpputest_3.8-6.dsc
 9c9ef8e6b012dde350731fd0719c98898ef58d55 5144 cpputest_3.8-6.debian.tar.xz
 aeeeb521b8cd4a2a302cc947f342f4814edb5361 5471 cpputest_3.8-6_source.buildinfo
Checksums-Sha256:
 0e646d6cc0cdd97ccf4475f1070e10d3401e207c1486cbb5890eb73cd88ddbef 1648 
cpputest_3.8-6.dsc
 3027a84c80735817d426c7aacc29a8a1c2ddf167cbbae06bc5ba2213e796b8bd 5144 
cpputest_3.8-6.debian.tar.xz
 4daa7d1c912fbf3ca964e8dcbdf36c8cdcb52dc9672a074c094736c1905eba77 5471 
cpputest_3.8-6_source.buildinfo
Files:
 5f95385fc236ba7debf40b3604f623a4 1648 devel optional cpputest_3.8-6.dsc
 5455e042fe3014033aa97b75bee69dad 5144 devel optional 

Processed: found 889187 in 0.17.6-1

[Debian Bug Tracking System]

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

> found 889187 0.17.6-1
Bug #889187 {Done: Andreas Metzler } [src:e17] e17-dbg is 
empty
Marked as found in versions e17/0.17.6-1.
> thanks
Stopping processing here.

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

Bug#880888: maven-enforcer FTBFS with libmaven-dependency-tree-java 3.0.1-1

[Markus Koschany]

So apparently in libmaven-dependency-tree-java 3.0.1-1 the devs decided
to rename the word tree to graph...There were some other issues though
and I was not sure how to proceed. I had a look at the Fedora package
and they patched maven-enforcer to work with Maven 3 but they also added
a dependency on maven-transfer-artifact. Maybe it might help to resolve
this bug.

https://src.fedoraproject.org/cgit/rpms/maven-enforcer.git/tree/0001-Port-to-Maven-3-API.patch

Processed: block 889675 with 889556 889557 889558

[Debian Bug Tracking System]

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

> block 889675 with 889556 889557 889558
Bug #889675 [ftp.debian.org] RM: botan1.10 -- ROM; obsolete
889675 was not blocked by any bugs.
889675 was not blocking any bugs.
Added blocking bug(s) of 889675: 889557, 889558, and 889556
> thanks
Stopping processing here.

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

Bug#882017: solution available upstream

[Christian Ehrhardt]

Hi,
I debugged the same case on Ubuntu and
  
eventually found [1].
The fix itself is [2] and would according to my tests unblock this issue.

There is also a 0.14 now, but the fix is not included in there yet.

[1]: https://github.com/MagicStack/asyncpg/issues/250
[2]: 
https://github.com/MagicStack/asyncpg/commit/05dce25f15090ae8ebfb7ba2f67a0edc60cd915a

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd

Processed: Add affects

[Debian Bug Tracking System]

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

> affects 889187 e17-dbg
Bug #889187 {Done: Andreas Metzler } [src:e17] e17-dbg is 
empty
Added indication that 889187 affects e17-dbg
> thanks
Stopping processing here.

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

Bug#889558: qtcreator: (Build-)Depends on obsolete libbotan1.10-dev

[Lisandro Damián Nicanor Pérez Meyer]

Tip: should not be RC until you file the Rom bug to remove it.

On 5 February 2018 at 13:22, Lisandro Damián Nicanor Pérez Meyer
 wrote:
> Hi Christian!
>
> On 4 February 2018 at 11:25, Christian Hofstaedtler  wrote:
>> Package: qtcreator
>> Version: 4.5.0-2
>> Severity: serious
>>
>> Dear Maintainer,
>>
>> your package qtcreator (build-)depends on botan1.10, which itself is
>> obsolete. Upstream will end security support at the end of 2018, so it
>> must not be part of buster.
>>
>> Please drop the libbotan1.10-dev build dependency.
>
> That's just fine, but creating an instant-rc bug for this is a little
> too hurried. You should really consider making this at most normal and
> increase severities with time.
>
> Cheers, Lisandro.
>
> --
> Lisandro Damián Nicanor Pérez Meyer
> http://perezmeyer.com.ar/
> http://perezmeyer.blogspot.com/



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

Bug#889558: qtcreator: (Build-)Depends on obsolete libbotan1.10-dev

[Lisandro Damián Nicanor Pérez Meyer]

On 5 February 2018 at 13:23, Lisandro Damián Nicanor Pérez Meyer
 wrote:
> Tip: should not be RC until you file the Rom bug to remove it.

On a second thought that's maybe the other extreme.

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

Bug#889558: qtcreator: (Build-)Depends on obsolete libbotan1.10-dev

[Lisandro Damián Nicanor Pérez Meyer]

Hi Christian!

On 4 February 2018 at 11:25, Christian Hofstaedtler  wrote:
> Package: qtcreator
> Version: 4.5.0-2
> Severity: serious
>
> Dear Maintainer,
>
> your package qtcreator (build-)depends on botan1.10, which itself is
> obsolete. Upstream will end security support at the end of 2018, so it
> must not be part of buster.
>
> Please drop the libbotan1.10-dev build dependency.

That's just fine, but creating an instant-rc bug for this is a little
too hurried. You should really consider making this at most normal and
increase severities with time.

Cheers, Lisandro.

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

Bug#889627: marked as done (firebird3.0 FTBFS on most architectures: crash in self-build binaries during the build)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 16:05:17 +
with message-id 
and subject line Bug#889627: fixed in firebird3.0 3.0.3.32900.ds4-2
has caused the Debian Bug report #889627,
regarding firebird3.0 FTBFS on most architectures: crash in self-build binaries 
during the build
to be marked as done.

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

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


-- 
889627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: firebird3.0
Version: 3.0.3.32900.ds4-1
Severity: serious

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

Symptoms are slightly varying, e.g. on arm64:

...
/usr/bin/make gpre
make[4]: Entering directory '/<>/gen'
rm -f metadata.fdb
/<>/gen/Release/firebird/bin/isql -q -i 
/<>/src/dbs/metadata.sql
free(): invalid size
Makefile:323: recipe for target 'metadata.fdb' failed
make[4]: *** [metadata.fdb] Aborted
--- End Message ---
--- Begin Message ---
Source: firebird3.0
Source-Version: 3.0.3.32900.ds4-2

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

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated firebird3.0 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, 05 Feb 2018 15:50:05 +
Source: firebird3.0
Binary: firebird3.0-server-core firebird3.0-server firebird3.0-utils 
libfbclient2 libib-util firebird3.0-common firebird-dev firebird3.0-examples 
firebird3.0-doc firebird3.0-common-doc
Architecture: source
Version: 3.0.3.32900.ds4-2
Distribution: unstable
Urgency: medium
Maintainer: Damyan Ivanov 
Changed-By: Damyan Ivanov 
Closes: 889627
Description: 
 firebird3.0-common - common files for firebird 3.0 server, client and utilities
 firebird3.0-common-doc - copyright, licensing and changelogs of firebird3.0
 firebird3.0-doc - Documentation files for firebird database version 3.0
 firebird3.0-examples - Examples for Firebird database
 firebird3.0-server-core - Firebird engine core
 firebird3.0-server - Firebird Server - an RDBMS based on InterBase 6.0 code
 firebird3.0-utils - Firebird command line utilities
 firebird-dev - Development files for Firebird
 libfbclient2 - Firebird client library
 libib-util - Firebird UDF support library
Changes:
 firebird3.0 (3.0.3.32900.ds4-2) unstable; urgency=medium
 .
   * add c++-std.patch, adding --std=gnu++03 to several build prefix files
 Closes: #889627
Checksums-Sha1: 
 c35565b86e04c33280d65967e3536f87dd084aec 2704 firebird3.0_3.0.3.32900.ds4-2.dsc
 6834aae33165ea431f3889a15068f99b39d5690a 96776 
firebird3.0_3.0.3.32900.ds4-2.debian.tar.xz
Checksums-Sha256: 
 8ad98d41c8e4d7d6e1b224138c5f4ffde43fa75db7d2db40787028ccf2097039 2704 
firebird3.0_3.0.3.32900.ds4-2.dsc
 b3c500698d6fb7438c9d6863c2510fc842eae921ad3ba0689c3148428f8a8031 96776 
firebird3.0_3.0.3.32900.ds4-2.debian.tar.xz
Files: 
 a52d6bb6acd049d62a9a1e737751f7e1 2704 database optional 
firebird3.0_3.0.3.32900.ds4-2.dsc
 3180164a7a12339fdd2cbf32dafde48c 96776 database optional 
firebird3.0_3.0.3.32900.ds4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErqDETssFbpNjDZ0z276dTZnSoAQFAlp4f+IACgkQ276dTZnS
oAQd/Q//Z30We9GnZurUFV2GGHIDTDGrTAFwEojzqAt6YBGGITMCw7MBBVrjgRpe
GHJj/B4MCcNyZqKosXJey8yXE0CaZOJ45H5boJUILDo/PWkJEQiGtoJK2DV+E+Y4
PjDh8txMXkAcQQmgMeS5FI7i0PyWcOTonEp2WOQfxuG9AEEOfJ3X29O71YHEmB1e
reSBoOqMno8W3woID6yZfQ51Xg5eqEXkLIQ0Vh9N7sSW5DDuXRpFSU3uoNA4UexD
f91xQuntvaMIXD3ROGZW+fl6VMl7hnzYNVsYkiLzLN/M5FvO/5AlC2L36xkaNUFY
2oMtPgsq/3TStVg2D1aJFLFF0+f4Ht31x02jq9VRRPmeN5u8LIdbMNTUeaL1NX7m
iJNZ10Wsk2U4ebpSTXzGk9DGy889Ejsj7G8vRKzswmtiMogO9M0shmVG7GEHGsqH
nmFewXxwSfoii5oo/CpfAbpMjN89kJts95WGcX602ucKxJ9mYz/sSqAE1dGu/9jk
olxCOHtbOpMny6R8gcNAmv3RRBtSHJ8p7fmIBO7ZttITesv7Z1k7oygB/FQlFht+
xyH0ArYfhpSHLAceyasGz3IYU8YsQfmkfahhJOCkEhCvRMmR1Q+VPCDgTxjjjDf2
kZOKkri1f0RvukSHMhwLmjtbflhZoD3JuWVAWT90KPOMxAbKPKA=
=c1d6
-END PGP SIGNATURE End Message ---

Processed: Proper command for the affects

[Debian Bug Tracking System]

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

> affects 888459 src:flint-arb
Bug #888459 {Done: Adrian Bunk } [libmpfr6] flint-arb's tests 
fail on 32bit archs using mpfr 4.0.0
Added indication that 888459 affects src:flint-arb
> thanks
Stopping processing here.

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

Processed: Re: Bug#888422 closed by Matthias Klose <d...@debian.org> (Bug#888422: fixed in mpfr4 4.0.0-6)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #888422 {Done: Matthias Klose } [libmpfr6] Mixing libmpfr4 
and libmpfr6 doesn't work well
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions mpfr4/4.0.0-6.

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

Bug#888422: closed by Matthias Klose <d...@debian.org> (Bug#888422: fixed in mpfr4 4.0.0-6)

[Adrian Bunk]

Control: reopen -1

On Tue, Jan 30, 2018 at 09:24:09AM +, Debian Bug Tracking System wrote:
>...
>  mpfr4 (4.0.0-6) unstable; urgency=medium
>...
>* libmpfr6: Break libmpc3 (<< 1.1.0-1~). Closes: #888422.
>...

Looking at #888911 and the fact that this FTBFS on armhf disappeared 
after everything switched to libmpfr6 [1], libmpc3 really seems to be 
just one out of many affected packages here and the Breaks should 
actually be against libmpfr4.

cu
Adrian

[1] https://tests.reproducible-builds.org/debian/history/giac.html

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#888459: marked as done (flint-arb's tests fail on 32bit archs using mpfr 4.0.0)

[Debian Bug Tracking System]

Your message dated Mon, 5 Feb 2018 17:58:30 +0200
with message-id <20180205155830.GX3126@localhost>
and subject line Fixed in 4.0.1~rc2-1
has caused the Debian Bug report #888459,
regarding flint-arb's tests fail on 32bit archs using mpfr 4.0.0
to be marked as done.

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

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


-- 
888459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:flint-arb
Version: 2.11.1-2
Severity: serious
Tags: sid buster

as seen on
https://release.debian.org/transitions/html/auto-mpfr4.html
https://buildd.debian.org/status/package.php?p=flint-arb

the testsuite fails on all 32bit architectures.

cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -I/<>
-I/usr/local/include -I/usr/local/include -I/usr/include test/t-sqrt.c -o
../build/arf/test/t-sqrt -L/<> -L/usr/local/lib -L/usr/local/lib
-L/usr/lib -lflint-arb -lflint -lmpfr -lgmp -lm -lpthread  -MMD -MP -MF
../build/arf/test/t-sqrt.d -MT "../build/arf/test/t-sqrt" -MT
"../build/arf/test/t-sqrt.d"
flooraddmul_uiPASS
cmpabs_2exp_siPASS
addset_round_uirootPASS
add_siPASS
mulPASS
set_fmpqPASS
submul_uiPASS
mul_siPASS
abs_bound_lt_2exp_siPASS
sub_siPASS
get_dPASS
addmul_fmpzPASS
add_uiPASS
frexpPASS
rsqrtPASS
subPASS
cmpabsPASS
set_fmprPASS
set_round_fmpzPASS
mul_uiPASS
abs_bound_lt_2exp_fmpzPASS
sub_uiPASS
set_fmpz_2expPASS
complex_sqrPASS
complex_mulPASS
abs_bound_le_2exp_fmpzPASS
submul_fmpzPASS
divFAIL (aliasing 4)!
prec = 352, rnd = 4

x =
(4586997233048136541430758450064474100387735230759824291973833691816938709832156080645343570059119116156929
* 2^-154742412678922490659733883)

y =
(51814976846671518298238808760042830604686502339620382299366747655022166929406808804341858227567903870767891933265103849315791036770763130077955430384829058539908460614800988509303528381975119100503701824233100229972596599113543202092890645352456600459286399836135725531911334505568114757105479020098464557517116791851426250751
* 2^-154742431125385089392575577)

v =
(2135987036418233318920600437589210504846524088997312026086185915310372929010612927677735486095361
* 2^-154742412678922490659733852)

r1 = 1, r2 = 1
../Makefile.subdirs:84: recipe for target '../build/arf/test/t-div_RUN' failed
make[3]: *** [../build/arf/test/t-div_RUN] Aborted
make[3]: *** Waiting for unfinished jobs
PASS
PASS
PASS
make[3]: Leaving directory '/<>/arf'
Makefile:179: recipe for target 'check' failed
make[2]: *** [check] Error 2
make[2]: Leaving directory '/<>'
--- End Message ---
--- Begin Message ---
Version: 4.0.1~rc2-1

Fixed in 4.0.1~rc2-1:
https://buildd.debian.org/status/package.php?p=flint-arb

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#888558: marked as done (python-backports.tempfile: ships file with generic name: /usr/lib/python2.7/dist-packages/backports/__init__.py)

[Debian Bug Tracking System]

Your message dated Mon, 5 Feb 2018 16:57:11 +0100
with message-id <20180205155711.ycverg5ew2kqh...@an3as.eu>
and subject line Closed in 1.0-2
has caused the Debian Bug report #888558,
regarding python-backports.tempfile: ships file with generic name: 
/usr/lib/python2.7/dist-packages/backports/__init__.py
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.)


-- 
888558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-backports.tempfile
Version: 1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other packages files.

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

  Selecting previously unselected package python-backports.tempfile.
  Preparing to unpack .../python-backports.tempfile_1.0-1_all.deb ...
  Unpacking python-backports.tempfile (1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-backports.tempfile_1.0-1_all.deb (--unpack):
   trying to overwrite 
'/usr/lib/python2.7/dist-packages/backports/__init__.py', which is also in 
package python-backports-shutil-get-terminal-size 1.0.0-3
  Errors were encountered while processing:
   /var/cache/apt/archives/python-backports.tempfile_1.0-1_all.deb

I don't think Breaks+Replaces is the correct approach to handle this very
generic file name.


cheers,

Andreas


python-backports-shutil-get-terminal-size=1.0.0-3_python-backports.tempfile=1.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Hi,

this bug was closed in


python-backports.tempfile (1.0-2) unstable; urgency=medium

  * Fix namespace
  * Build-Depends: python*-backports.weakref

 -- Andreas Tille   Fri, 26 Jan 2018 19:11:29 +0100


so even before the bug was filed and thus not closed in changelog.

Kind regards

   Andreas.--- End Message ---

Processed (with 1 error): Move to the package where the bug was

[Debian Bug Tracking System]

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

> reassign 888459 libmpfr6 4.0.0-7
Bug #888459 {Done: Matthias Klose } [src:flint-arb] 
flint-arb's tests fail on 32bit archs using mpfr 4.0.0
Bug reassigned from package 'src:flint-arb' to 'libmpfr6'.
No longer marked as found in versions flint-arb/2.11.1-2.
No longer marked as fixed in versions 2.11.1-2+b1.
Bug #888459 {Done: Matthias Klose } [libmpfr6] flint-arb's 
tests fail on 32bit archs using mpfr 4.0.0
Marked as found in versions mpfr4/4.0.0-7.
> affects -1 src:flint-arb
Failed to mark -1 as affecting package(s): The 'bug' parameter ("-1") to 
Debbugs::Control::affects did not pass regex check
.

> thanks
Stopping processing here.

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

Bug#888459: marked as done (flint-arb's tests fail on 32bit archs using mpfr 4.0.0)

[Debian Bug Tracking System]

Your message dated Mon, 5 Feb 2018 16:54:34 +0100
with message-id 
and subject line Re: flint-arb's tests fail on 32bit archs using mpfr 4.0.0
has caused the Debian Bug report #888459,
regarding flint-arb's tests fail on 32bit archs using mpfr 4.0.0
to be marked as done.

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

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


-- 
888459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:flint-arb
Version: 2.11.1-2
Severity: serious
Tags: sid buster

as seen on
https://release.debian.org/transitions/html/auto-mpfr4.html
https://buildd.debian.org/status/package.php?p=flint-arb

the testsuite fails on all 32bit architectures.

cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -I/<>
-I/usr/local/include -I/usr/local/include -I/usr/include test/t-sqrt.c -o
../build/arf/test/t-sqrt -L/<> -L/usr/local/lib -L/usr/local/lib
-L/usr/lib -lflint-arb -lflint -lmpfr -lgmp -lm -lpthread  -MMD -MP -MF
../build/arf/test/t-sqrt.d -MT "../build/arf/test/t-sqrt" -MT
"../build/arf/test/t-sqrt.d"
flooraddmul_uiPASS
cmpabs_2exp_siPASS
addset_round_uirootPASS
add_siPASS
mulPASS
set_fmpqPASS
submul_uiPASS
mul_siPASS
abs_bound_lt_2exp_siPASS
sub_siPASS
get_dPASS
addmul_fmpzPASS
add_uiPASS
frexpPASS
rsqrtPASS
subPASS
cmpabsPASS
set_fmprPASS
set_round_fmpzPASS
mul_uiPASS
abs_bound_lt_2exp_fmpzPASS
sub_uiPASS
set_fmpz_2expPASS
complex_sqrPASS
complex_mulPASS
abs_bound_le_2exp_fmpzPASS
submul_fmpzPASS
divFAIL (aliasing 4)!
prec = 352, rnd = 4

x =
(4586997233048136541430758450064474100387735230759824291973833691816938709832156080645343570059119116156929
* 2^-154742412678922490659733883)

y =
(51814976846671518298238808760042830604686502339620382299366747655022166929406808804341858227567903870767891933265103849315791036770763130077955430384829058539908460614800988509303528381975119100503701824233100229972596599113543202092890645352456600459286399836135725531911334505568114757105479020098464557517116791851426250751
* 2^-154742431125385089392575577)

v =
(2135987036418233318920600437589210504846524088997312026086185915310372929010612927677735486095361
* 2^-154742412678922490659733852)

r1 = 1, r2 = 1
../Makefile.subdirs:84: recipe for target '../build/arf/test/t-div_RUN' failed
make[3]: *** [../build/arf/test/t-div_RUN] Aborted
make[3]: *** Waiting for unfinished jobs
PASS
PASS
PASS
make[3]: Leaving directory '/<>/arf'
Makefile:179: recipe for target 'check' failed
make[2]: *** [check] Error 2
make[2]: Leaving directory '/<>'
--- End Message ---
--- Begin Message ---
Version: 2.11.1-2+b1

now fixed with a rebuild using mpfr4 4.0.1 rc2--- End Message ---

Bug#889672: gcompris-qt: Missing dependency

[Ignacio Losiggio]

Package: gcompris-qt
Version: 0.81-1
Severity: serious
Justification: Policy 3.5

Dear Maintainer, the package gcompris-qt has at least a missing
dependency on `qml-module-qtquick-controls`.

When i tried to execute it without that dependency this was the output:

>alumno@huayra:~/conectar/paquetes/result/huayra/torbellino/amd64$
gcompris-qt
>exeCount set to:  2
>QQmlApplicationEngine failed to load component
>qrc:/gcompris/src/core/main.qml:22 module "QtQuick.Controls" is not
installed
>
>Error: Your root item has to be a Window.

-- System Information:
Distributor ID: Huayra
Description: Huayra 3.3 (sud)
Release: 3.3
Codename: sud
Architecture: x86_64

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

Versions of packages gcompris-qt depends on:
ii  gcompris-qt-data   0.81-1
ii  libc6  2.24-11+deb9u1
ii  libgcc11:6.3.0-18
ii  libqt5core5a   5.7.1+dfsg-3+b1
ii  libqt5gui5 5.7.1+dfsg-3+b1
ii  libqt5network5 5.7.1+dfsg-3+b1
ii  libqt5qml5 5.7.1-2+b2
ii  libqt5quick5   5.7.1-2+b2
ii  libqt5sensors5 5.7.1~20161021-2
ii  libqt5widgets5 5.7.1+dfsg-3+b1
ii  libstdc++6 6.3.0-18
ii  qml-module-qtgraphicaleffects  5.7.1~20161021-3
ii  qml-module-qtmultimedia5.7.1~20161021-2
ii  qml-module-qtquick-particles2  5.7.1-2+b2

Versions of packages gcompris-qt recommends:
pn  libqt5multimedia5-plugins  

gcompris-qt suggests no packages.

-- no debconf information

Processed: found 889131 in 5.11.4-1, reassign 889187 to src:e17, fixed 889187 in 0.21.2-2

[Debian Bug Tracking System]

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

> found 889131 5.11.4-1
Bug #889131 [src:plasma-discover] plasma-discover FTBFS with 
libpackagekitqt5-dev 1.0.1-1
Marked as found in versions plasma-discover/5.11.4-1.
> reassign 889187 src:e17 0.17.6-1.1
Bug #889187 {Done: Andreas Metzler } [e17-dbg] e17-dbg is 
empty
Bug reassigned from package 'e17-dbg' to 'src:e17'.
No longer marked as found in versions e17/0.17.6-1.1.
No longer marked as fixed in versions 0.21.2-2.
Bug #889187 {Done: Andreas Metzler } [src:e17] e17-dbg is 
empty
Marked as found in versions e17/0.17.6-1.1.
> fixed 889187 0.21.2-2
Bug #889187 {Done: Andreas Metzler } [src:e17] e17-dbg is 
empty
Marked as fixed in versions e17/0.21.2-2.
> thanks
Stopping processing here.

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

Bug#889645: marked as done (pd-moonlib: architecture baseline violation on amd64/i386/armel/armhf)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 15:28:12 +
with message-id 
and subject line Bug#889645: fixed in pd-moonlib 0.3.6-3
has caused the Debian Bug report #889645,
regarding pd-moonlib: architecture baseline violation on amd64/i386/armel/armhf
to be marked as done.

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

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


-- 
889645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pd-moonlib
Version: 0.3.6-2
Severity: serious

There is no SSE3 in the amd64 port baseline.
There is no SSE in the i386 port baseline.
There is no VFP in the armel port baseline.
There aren't 32 FPU registers in the armhf port baseline.

Please be more careful when doing "Simplified & unified d/rules".
--- End Message ---
--- Begin Message ---
Source: pd-moonlib
Source-Version: 0.3.6-3

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
pd-moonlib 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, 05 Feb 2018 14:42:53 +0100
Source: pd-moonlib
Binary: pd-moonlib
Architecture: source
Version: 0.3.6-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Description:
 pd-moonlib - library of Pd objects related to GUI control
Closes: 889645
Changes:
 pd-moonlib (0.3.6-3) unstable; urgency=medium
 .
   * Switched to system-provided Makefile.pdlibbuilder (Closes: #889645)
 * Pass build-flags to all 'make' invocations
Checksums-Sha1:
 7de65ccc61495fb4585daaae068836900734e144 2054 pd-moonlib_0.3.6-3.dsc
 ddc2dc9aef114de21ac4ad4246b34ed5f596b86a 4832 pd-moonlib_0.3.6-3.debian.tar.xz
 0ff5e96089f8fc8961ce6a1294000aef07e83714 5573 
pd-moonlib_0.3.6-3_amd64.buildinfo
Checksums-Sha256:
 b665cdfce5b1fef5fa464cebcc3ae8b62150aee1ee0e40983b3ef52e88931c3a 2054 
pd-moonlib_0.3.6-3.dsc
 648aa7370d4c0ee059271aa900c9f347db4d4d89e505f4aca91dca43979b2fe4 4832 
pd-moonlib_0.3.6-3.debian.tar.xz
 e5cd04a0f0212cc582d05327eae99ee1360ff0cb881c38fd2e4461f35ddd0750 5573 
pd-moonlib_0.3.6-3_amd64.buildinfo
Files:
 37636d18ebf193385b4604fdbdc19516 2054 sound optional pd-moonlib_0.3.6-3.dsc
 26bcf72bd11e2b2e9d90cf7d7d4972ba 4832 sound optional 
pd-moonlib_0.3.6-3.debian.tar.xz
 cce0fae2b8ca51d0832da578d7742bbd 5573 sound optional 
pd-moonlib_0.3.6-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAlp4YPcACgkQtlAZxH96
NvhzPA//XptHWDJ42QOGUGHfr6cZa8WapSqj8l/MOpp0MewwdzeadTX0p9zT2AZd
3xlFFHpOFSqhOE0ggrpr5OikWTHJoKSX08Bm2T8q2KaGPm3wMHpu1IMGT/r4IYnS
f+guS9FuyxRf+vvl6CaHxGoleKEP5m9i1GNzZH9VCfvmKZTz9RCdqM1Apj1tYjhT
pS1g3T3C2+vR5LJT7iEL6tNpVOc8vHJ/fUkwtAbKmzKu+iQisO+8G9AuYBLoSi4G
GqYmFdjY3y1k8vUxtrlbxq4mLc36Z56X31uDUmnTh5PBFxDLfzh07+LSGJ3TiyNO
wKyJmnH1CZqWcW67pAwIHViBrTnd4TYJ0jMpeHex4nuZiQimFX6miDSfIwh9PRSn
yFPI+lHIYrlIvZkxQUYpM+yH7U7f2tu3Lspgq0L10rm3vgIugie0de+fssvGmh24
/f6H8iOe1z6hzKiLjLWNdm+Y6SjBY2ScALbvg19kzuPsVucEG8So3LdRHwUUFX43
ej+CgfVMsE/UdeEJPFFWwSMGEqwEBs1dJHm9IaQLVKw6G7E1BN0NbGHEtrno8Mx/
kQK1MSpGGKaAwcUsFv149ZwblnFNRPKdrGxxpS5Bgje8FThMquC+C3wqnJ1vRemI
KBXZpL7aPwc8F7WxdKUS4xkoauLvn+FGnzPOa4/5SZIzPG1VglU=
=ybef
-END PGP SIGNATURE End Message ---

Bug#889005: marked as done (mm3d FTBFS on armel/armhf: error: OpenGL (with GLU) is required)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 15:27:04 +
with message-id 
and subject line Bug#889005: fixed in mm3d 1.3.9-2
has caused the Debian Bug report #889005,
regarding mm3d FTBFS on armel/armhf: error: OpenGL (with GLU) is required
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.)


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

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

...
checking for OpenGL... yes
checking for Qt... yes:
QT_CXXFLAGS=-I/usr/include/arm-linux-gnueabi/qt5
QT_DIR=
QT_LIBS=-L/usr/lib/arm-linux-gnueabi/qt5 -lQt5Core -lQt5Gui -lQt5Widgets 
-lQt5OpenGL -lQt5Network 
QT_UIC=/usr/lib/arm-linux-gnueabi/qt5/bin/uic
QT_MOC=/usr/lib/arm-linux-gnueabi/qt5/bin/moc
QT_LRELEASE=/usr/lib/arm-linux-gnueabi/qt5/bin/lrelease
checking correct functioning of Qt installation... success
checking Qt OpenGL... success
checking for x11 fonts... no
checking for gettimeofday... yes

configure: error: OpenGL (with GLU) is required.


Ideally it should be made working when Qt is using
OpenGL ES, but if that is not possible please:
- change the build dependency from libqt5opengl5-dev
  to libqt5opengl5-desktop-dev, and
- submit a bug against ftp.debian.org asking for the
  removal of the old armel+armhf binaries from unstable
--- End Message ---
--- Begin Message ---
Source: mm3d
Source-Version: 1.3.9-2

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

Debian distribution maintenance software
pp.
Gürkan Myczko  (supplier of updated mm3d package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 05 Feb 2018 14:25:31 +0100
Source: mm3d
Binary: mm3d
Architecture: source
Version: 1.3.9-2
Distribution: unstable
Urgency: medium
Maintainer: Gürkan Myczko 
Changed-By: Gürkan Myczko 
Description:
 mm3d   - OpenGL based 3D model editor
Closes: 515140 517564 889005
Changes:
 mm3d (1.3.9-2) unstable; urgency=medium
 .
   * debian/copyright: improved.
   * debian/rules: profiling turned off. (Closes: #517564, #515140)
   * debian/control: update build-deps. (Closes: #889005)
Checksums-Sha1:
 51887dee9b53b4afad00d6a3bca7de5ed9bdebe7 1813 mm3d_1.3.9-2.dsc
 1e70440fe226f7a732d07cbc89065c5b8b6f0e21 3684 mm3d_1.3.9-2.debian.tar.xz
 1dfd757c15aca1090154cd79979d30e7e424ec52 5341 mm3d_1.3.9-2_source.buildinfo
Checksums-Sha256:
 7fc69ebf565b188d613889de88460676bd05fc81baf7f350c77634c6f0888951 1813 
mm3d_1.3.9-2.dsc
 0bdd272e146ef24c60d356b5d508ae70cfed738ecb0e20fe3d22c3e6a2b04967 3684 
mm3d_1.3.9-2.debian.tar.xz
 c6efd6246f1dbd8f4ff0d5d5b837c212811ccc44470635276071586fbedd4286 5341 
mm3d_1.3.9-2_source.buildinfo
Files:
 ba4fa8e9e89f88b771bcb3b5c9be963b 1813 graphics optional mm3d_1.3.9-2.dsc
 e197700422b448b48fb0191b1157d503 3684 graphics optional 
mm3d_1.3.9-2.debian.tar.xz
 b7895f87540093c76fc4748cbaa490a8 5341 graphics optional 
mm3d_1.3.9-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlp4ZPsACgkQweDZLphv
fH5emA//VBIKxPPP1el9XVGmjecdAFwx++4P0di9zMUOChLCACGf2aerjGL0XZHc
vWB6EpBVyJv+7SQEy+I3rbDa6bOOCcfs/t/HZDEQqmBsrSoha3BwY6MO2gg1UB9h
QcEPwvTHDLGHwVo/TjNMPkgg3h8kmkbfyUirDN6GU96GxpblfLC2s7B6uJdWrDDN
OlMM6xkTs2GqhKrG3yptc0Sk9qUAHGbYAF7LKxpfw/48Ts/oMaxTGXWrzf0l9/Rg
kVTdqhR+9V1reiIOTKO1ydLo1rO4yiogWVhh0jZdVw4LXvkQL7CshXunQGtda4GX
pTYnwUm9wVyk/oSoPij/Z7Ge23DFXaBGiMf4Fgx0IcG2oXfjmBkB3YUvB6u6aAyW
873oQWZEdku8HfTUhhv+BWoR3Q9B2Qz6MCg6WDLPLRlu2bjCU+RxTmq3J7322Chl
bbwOmW2fah/hMii25jUWhni8tbrMp4cSLLq630kZ8ha1cDiv1eiMgF4utX6pL0KP
AXPL2OMeDnLm5Jw9PfaJEx3PHGDtUVS1mX+/EzScZ4Zrm0GA5fECXihqcMEanx5h
L5rVbWTQ5IxbvhnoVpIxK1FwsTB2KN7Sg2ET0gzID565uT7SFV/dE6p2FXHHZuhW
KuKwGHgM7DYtd4HP0mtxwVIdMvWhEiz7O4HOwTu3I28mINarJgg=
=+47C
-END PGP SIGNATURE End Message ---

Bug#880793: marked as done (pymvpa2 FTBFS on mips64el: ValueError: array is too big; `arr.size * arr.dtype.itemsize` is larger than the maximum possible size.)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 15:28:42 +
with message-id 
and subject line Bug#880793: fixed in pymvpa2 2.6.4-2
has caused the Debian Bug report #880793,
regarding pymvpa2 FTBFS on mips64el: ValueError: array is too big; `arr.size * 
arr.dtype.itemsize` is larger than the maximum possible size.
to be marked as done.

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

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


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

https://buildd.debian.org/status/fetch.php?pkg=pymvpa2=mips64el=2.6.3-1=1509746580=0

...
==
ERROR: mvpa2.tests.test_misc_scatter.test_plot_scatter
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/tests/test_misc_scatter.py",
 line 56, in test_plot_scatter
fig = plot_scatter(data2d, mask=mask)
  File 
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/mvpa2/misc/plot/scatter.py",
 line 398, in plot_scatter
binsx = np.arange(minx, maxx + binwidthx, binwidthx)
ValueError: array is too big; `arr.size * arr.dtype.itemsize` is larger than 
the maximum possible size.

--
Ran 574 tests in 3879.450s

FAILED (SKIP=22, errors=1)
debian/rules:45: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1
--- End Message ---
--- Begin Message ---
Source: pymvpa2
Source-Version: 2.6.4-2

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 880...@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: Wed, 31 Jan 2018 11:09:23 -0500
Source: pymvpa2
Binary: python-mvpa2 python-mvpa2-lib python-mvpa2-doc
Architecture: source all amd64
Version: 2.6.4-2
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: 880793
Changes:
 pymvpa2 (2.6.4-2) unstable; urgency=medium
 .
   * patches to fortify scatter code and tests against degenerate cases which
 reveal themselves on exotic platforms (Now should really Closes: #880793).
 ref: https://github.com/numpy/numpy/issues/10496
Checksums-Sha1:
 3678c0d99fcddb3c0629644ef070c7b3542fd2ef 2402 pymvpa2_2.6.4-2.dsc
 002469125bdf3dc1dd62d3505db34cc04de78f14 317956 pymvpa2_2.6.4-2.debian.tar.xz
 18305e30282d8a2a2ea2f14cc8a48a0572f95317 13585 pymvpa2_2.6.4-2_amd64.buildinfo
 8e92a8ef21588877f12ca7a1f8799dee52e03637 4257764 
python-mvpa2-doc_2.6.4-2_all.deb
 5bf3229bcd0e0e47ce518e028648140ced2d209f 90972 
python-mvpa2-lib-dbgsym_2.6.4-2_amd64.deb
 9ea9cda89cca9926d4451386198d7735dd82e5a0 51272 
python-mvpa2-lib_2.6.4-2_amd64.deb
 8839df057c6a1459499967f2d3ecac7c50310632 5101520 python-mvpa2_2.6.4-2_all.deb
Checksums-Sha256:
 02596438293fc4795aed1f1254e71682e4504feeaba416db331796855655bd9a 2402 
pymvpa2_2.6.4-2.dsc
 0bd10b81472a3cdb7c40e0ed7043a72e3286b3cdcb58e25e318284f5d86c6cac 317956 
pymvpa2_2.6.4-2.debian.tar.xz
 133e1906adaa283654178912f3c5b918d091ae35b518f602e714c3ea568c95e6 13585 
pymvpa2_2.6.4-2_amd64.buildinfo
 8ef2dbe705e6f59579202b846b6edf20f8eeb4edd8708c719c440406c61ebada 4257764 
python-mvpa2-doc_2.6.4-2_all.deb
 056a6cc69816772c1e7c9f09a5d4c68f2db638dd92e452120725018ecd9c4690 90972 
python-mvpa2-lib-dbgsym_2.6.4-2_amd64.deb
 21ae3a6b2c250bd8710f051f13c48542bfed77d06fe359372b4393a190e1e80f 51272 

Bug#888452: marked as done (389-ds-base: CVE-2017-15134: Remote DoS via search filters in slapi_filter_sprintf in slapd/util.c)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 15:21:00 +
with message-id 
and subject line Bug#888452: fixed in 389-ds-base 1.3.7.9-1
has caused the Debian Bug report #888452,
regarding 389-ds-base: CVE-2017-15134: Remote DoS via search filters in 
slapi_filter_sprintf in slapd/util.c
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.)


-- 
888452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: 389-ds-base
Version: 1.3.7.8-4
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerability was published for 389-ds-base.

CVE-2017-15134[0]:
Remote DoS via search filters in slapi_filter_sprintf in slapd/util.c

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-15134
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15134
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1531573

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: 389-ds-base
Source-Version: 1.3.7.9-1

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

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

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated 389-ds-base 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, 05 Feb 2018 16:25:09 +0200
Source: 389-ds-base
Binary: 389-ds 389-ds-base-libs 389-ds-base-dev 389-ds-base python3-lib389 
python3-dirsrvtests
Architecture: source
Version: 1.3.7.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian 389ds Team 

Changed-By: Timo Aaltonen 
Description:
 389-ds - 389 Directory Server suite - metapackage
 389-ds-base - 389 Directory Server suite - server
 389-ds-base-dev - 389 Directory Server suite - development files
 389-ds-base-libs - 389 Directory Server suite - libraries
 python3-dirsrvtests - Python3 module for 389 Directory Server Continuous 
Integration te
 python3-lib389 - Python3 module for accessing and configuring the 389 
Directory Se
Closes: 888451 888452
Changes:
 389-ds-base (1.3.7.9-1) unstable; urgency=medium
 .
   * New upstream release.
 - CVE-2017-15134 (Closes: #888452)
   * patches: Fix CVE-2017-15135. (Closes: #888451)
   * tests: Add some debug output.
Checksums-Sha1:
 d6057d4029733987b58726d2086437d6612f2ece 2737 389-ds-base_1.3.7.9-1.dsc
 a3b49138c588c8389e547622ea62fa77e7f0005b 3573617 
389-ds-base_1.3.7.9.orig.tar.bz2
 efbccfd6e1b62487cfbde401335f08402e68bbb6 23664 
389-ds-base_1.3.7.9-1.debian.tar.xz
Checksums-Sha256:
 744149e318639702c9d55b6167901a72d0bb81904b1d7a3de60afbd0d097106f 2737 
389-ds-base_1.3.7.9-1.dsc
 fe9e7bee67ff6ce8b41d7e7c74dae79bd69711bcb488fe8c226e218357331e37 3573617 
389-ds-base_1.3.7.9.orig.tar.bz2
 7dcce3f6c1be57cb16f839cd60f2c61f3daa133e33e0e178a3643f23cf383198 23664 
389-ds-base_1.3.7.9-1.debian.tar.xz
Files:
 e7bd5b53d457f0c8067b9a316ac653e0 2737 net optional 389-ds-base_1.3.7.9-1.dsc
 1f40ad0aec80cc2b084a2914d2dd6370 3573617 net optional 
389-ds-base_1.3.7.9.orig.tar.bz2
 50979bbacef1c4705e2a93584cf9177e 23664 net optional 
389-ds-base_1.3.7.9-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJaeGpRAAoJEMtwMWWoiYTcS7gP/jfcYJZcOxm95mEy03tQd+v8
wmSR2+vWQbHz+8Vl3HZZtepB1lDKu0YdvYKVGtJxdSNcZ3FSzhZT+rXrEb4cqWue
MYD1Y2njzK7GWrOXIE8Lx/wC4vFhzdsApxX0FVgpsW6HPGdB0ebG06c9gx1aK/Ol
nB+6WjgNOCp1FlqiypNhjzhDMKuLz9/hpNSL5VNVRXTeVdB8Lw9/0K47XMEKpYY6
9YnfnT1LgynPJHBanwPwUdK3NeEtpDgjKADAlfy7ozLndVA7ka2BjKYXZ7zBFHCt
YxQOBI6fp5QpiYjo7M5XTYxCobeQdmt9GhNajVrPvI9xFKEZJVqoYwEphsMvjEJZ
m4C5Ih646c9A6yA7HeZx54lpdUbAMwrb8DcMRS7lgAqwIEHQdgTt+ubPSyCfMy3c
nWlyBkYxTui/AL+i+lo7UooNGGbosQCsO7n+q2g3T0+MIAzV0gCEhEGvptLrIjjW
yWDJGp1j7Nl22A82/3bsYnUK/a5jhmJvaCdiivFr6QnVcrfRtXZY6CBErMlYbyEv

Bug#888451: marked as done (389-ds-base: CVE-2017-15135: Authentication bypass due to lack of size check in slapi_ct_memcmp function in ch_malloc.c)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 15:21:00 +
with message-id 
and subject line Bug#888451: fixed in 389-ds-base 1.3.7.9-1
has caused the Debian Bug report #888451,
regarding 389-ds-base: CVE-2017-15135: Authentication bypass due to lack of 
size check in slapi_ct_memcmp function in ch_malloc.c
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.)


-- 
888451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: 389-ds-base
Version: 1.3.7.8-4
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerability was published for 389-ds-base.

CVE-2017-15135[0]:
| It was found that 389-ds-base since 1.3.6.1 up to and including
| 1.4.0.3 did not always handle internal hash comparison operations
| correctly during the authentication process. A remote, unauthenticated
| attacker could potentially use this flaw to bypass the authentication
| process under very rare and specific circumstances.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-15135
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15135
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1525628

Please adjust the affected versions in the BTS as needed, the issue
was introduced after the CVE-2016-5405 fix it is said, needs to be
verfied which suites are affected, at least stretch seems so. So far I
only looked at sid source.

Regards,
Salvatore
>From 872c98cd1b5059a4b76e3707d92f1445663db83d Mon Sep 17 00:00:00 2001
From: William Brown 
Date: Thu, 18 Jan 2018 11:27:58 +1000
Subject: [PATCH] Ticket bz1525628 - invalid password migration causes unauth
 bind

Bug Description:  Slapi_ct_memcmp expects both inputs to be
at LEAST size n. If they are not, we only compared UP to n.

Invalid migrations of passwords (IE {CRYPT}XX) would create
a pw which is just salt and no hash. ct_memcmp would then
only verify the salt bits and would allow the authentication.

This relies on an administrative mistake both of allowing
password migration (nsslapd-allow-hashed-passwords) and then
subsequently migrating an INVALID password to the server.

Fix Description:  slapi_ct_memcmp now access n1, n2 size
and will FAIL if they are not the same, but will still compare
n bytes, where n is the "longest" memory, to the first byte
of the other to prevent length disclosure of the shorter
value (generally the mis-migrated password)

https://bugzilla.redhat.com/show_bug.cgi?id=1525628

Author: wibrown

Review by: ???
---
 .../bz1525628_ct_memcmp_invalid_hash_test.py   | 56 ++
 ldap/servers/plugins/pwdstorage/clear_pwd.c|  4 +-
 ldap/servers/plugins/pwdstorage/crypt_pwd.c|  4 +-
 ldap/servers/plugins/pwdstorage/md5_pwd.c  |  4 +-
 ldap/servers/plugins/pwdstorage/sha_pwd.c  |  4 +-
 ldap/servers/plugins/pwdstorage/smd5_pwd.c |  2 +-
 ldap/servers/slapd/ch_malloc.c | 36 --
 ldap/servers/slapd/slapi-plugin.h  |  2 +-
 8 files changed, 97 insertions(+), 15 deletions(-)
 create mode 100644 
dirsrvtests/tests/suites/password/bz1525628_ct_memcmp_invalid_hash_test.py

diff --git 
a/dirsrvtests/tests/suites/password/bz1525628_ct_memcmp_invalid_hash_test.py 
b/dirsrvtests/tests/suites/password/bz1525628_ct_memcmp_invalid_hash_test.py
new file mode 100644
index 000..2f38384
--- /dev/null
+++ b/dirsrvtests/tests/suites/password/bz1525628_ct_memcmp_invalid_hash_test.py
@@ -0,0 +1,56 @@
+# --- BEGIN COPYRIGHT BLOCK ---
+# Copyright (C) 2018 Red Hat, Inc.
+# All rights reserved.
+#
+# License: GPL (version 3 or any later version).
+# See LICENSE for details.
+# --- END COPYRIGHT BLOCK ---
+#
+
+import ldap
+import pytest
+import logging
+from lib389.topologies import topology_st
+from lib389._constants import PASSWORD, DEFAULT_SUFFIX
+
+from lib389.idm.user import UserAccounts, TEST_USER_PROPERTIES
+
+logging.getLogger(__name__).setLevel(logging.DEBUG)
+log = logging.getLogger(__name__)
+
+def test_invalid_hash_fails(topology_st):
+"""When given a malformed hash from userpassword migration
+slapi_ct_memcmp would check only to the length of the shorter
+field. This affects some values where it would ONLY verify
+the salt is valid, and thus would allow any password to bind.
+
+:id: 8131c029-7147-47db-8d03-ec5db2a01cfb
+:setup: Standalone 

Bug#884548: seqan2: FTBFS: several tests fail

[Michael Crusoe]

On Sat, 16 Dec 2017 16:40:11 +0100 Andreas Beckmann  wrote:
> Source: seqan2
> Version: 2.3.2.000platform-issues8-6f85721+dfsg-2
> Severity: serious
> Justification: fails to build from source (but built successfully in the
past)
>
> Hi,
>
> seqan2 FTBFS on most platforms with failing unittests:
>
> https://buildd.debian.org/status/package.php?p=seqan2=experimental
>
> on amd64:
>
> The following tests FAILED:
> 257 - test_demo_tutorial_journaled_set_solution_online_search_finder
(Failed)
> 382 - app_test_razers (Failed)
> 383 - app_test_razers3 (Failed)
> 384 - app_test_razers3_sequential (Failed)
>
>
> Andreas
>

Thank you Andreas,
This long series of experimental builds were produced in cooperation with
upstream to fix all these failing tests. AMD64 is fixed as
of 2.4.0~rc2+dfsg-1.

If someone wants to assist upstream with the remaining failing tests I
would invite them to present themselves at
https://github.com/seqan/seqan/issues/2245

Processed: Bug #889629 in pd-iemutils marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #889629 [src:pd-iemutils] pd-iemutils binary-all FTBFS: 
debian/*//usr/lib/pd/extra': No such file or directory
Added tag(s) pending.

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

Bug#889645: Bug #889645 in pd-moonlib marked as pending

[umlaeute]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/pd/pd-moonlib/commit/d52ee771fb40cf2a454041d3d84c405c7f0c6d94


Switched to system-provided Makefile.pdlibbuilder

Closes: #889645



(this message was generated automatically)
-- 
Greetings

Processed: Bug #889645 in pd-moonlib marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #889645 [pd-moonlib] pd-moonlib: architecture baseline violation on 
amd64/i386/armel/armhf
Added tag(s) pending.

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

Bug#889629: Bug #889629 in pd-iemutils marked as pending

[umlaeute]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/pd/pd-iemutils/commit/a068cdfa0e64054934e1a1f2ed0ff85c23cfc751


Don't fail if building arch:all

Closes: #889629



(this message was generated automatically)
-- 
Greetings

Bug#865588: marked as done (djangorestframework FTBFS with Django 1.11: ERROR collecting tests/test_fields.py)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 13:51:02 +
with message-id 
and subject line Bug#865588: fixed in djangorestframework 3.7.7-1
has caused the Debian Bug report #865588,
regarding djangorestframework FTBFS with Django 1.11: ERROR collecting 
tests/test_fields.py
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.)


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

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

...
dh_auto_test
dh_auto_test: Compatibility levels before 9 are deprecated (level 8 in use)
I: pybuild base:184: python2.7 /build/1st/djangorestframework-3.4.0/runtests.py 
--nolint
= test session starts ==
platform linux2 -- Python 2.7.13, pytest-3.0.6, py-1.4.34, pluggy-0.4.0
rootdir: /build/1st/djangorestframework-3.4.0, inifile: tox.ini
plugins: django-2.9.1
collected 599 items / 1 errors

 ERRORS 
 ERROR collecting tests/test_fields.py _
tests/test_fields.py:992: in 
class TestDateTimeField(FieldValues):
tests/test_fields.py:997: in TestDateTimeField
'2001-01-01 13:00': datetime.datetime(2001, 1, 1, 13, 00, 
tzinfo=timezone.UTC()),
E   AttributeError: 'module' object has no attribute 'UTC'
!!! Interrupted: 1 errors during collection 
=== 1 error in 2.06 seconds 
E: pybuild pybuild:283: test: plugin custom failed with: exit code=2: python2.7 
/build/1st/djangorestframework-3.4.0/runtests.py --nolint
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
debian/rules:19: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
--- End Message ---
--- Begin Message ---
Source: djangorestframework
Source-Version: 3.7.7-1

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

Debian distribution maintenance software
pp.
Pierre-Elliott Bécue  (supplier of updated djangorestframework 
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: Sat, 03 Feb 2018 16:31:01 +0100
Source: djangorestframework
Binary: python-djangorestframework python-djangorestframework-doc 
python3-djangorestframework
Architecture: source
Version: 3.7.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Pierre-Elliott Bécue 
Description:
 python-djangorestframework - Web APIs for Django, made easy
 python-djangorestframework-doc - Web APIs for Django, made easy (documentation)
 python3-djangorestframework - Web APIs for Django, made easy for Python3
Closes: 865588 880558
Changes:
 djangorestframework (3.7.7-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream version: 3.7.7. (Closes: #865588, #880558)
   * Add d/patches/0003 to fix a lot of privacy breaches
   * d/contrib/docs/img/whole-structure.jpg added
   * d/control:
 - dh dependency to 11
 - Add missing build dependency on python3?-coreapi
 - Tidy all dependencies and versions
 - Add dependencies on javascript/fonts libraries to fit d/rules needs
   * d/compat to 11
   * d/copyright:
 - Use https link for copyright format
 - Updates of years, and adding the contrib/ image
   * d/rules:
 - Add rules to remove embedded contents that are packaged and link to the
   packaged ones.
 - Add upstream's changelog to the packages
   * d/python-djangorestframework-doc.doc-base:
 - Fixes file paths since d/compat is to 11
   * d/missing-sources:
 - Removes jquery 1.11.3
 - Add missing sources, and cleans a lintian error that is not fixable.

Bug#884023: Test case

[Teus Benschop]

Testing a new version of Bibledit, one with another icon file, ran into a
problem: There is a segmentation fault in libwegkit2gtk-4.

The bug has now been forwarded to that package in Debian.

A minimal case demonstrating the crash was referred to in that forwarded
bug. See https://github.com/bibletime/bibletime/issues/122 for extra
information.

It is hoped that the crash can be resolved in this minimal test case, and
then resolved in Bibledit too.

To build that minimal test case, the following packages are needed:

$ apt install build-essential autoconf automake autoconf-archive git zip
pkgconf libcurl4-openssl-dev libssl-dev libatspi2.0-dev libgtk-3-dev
libwebkit2gtk-3.0-dev libwebkit2gtk-4.0-dev

Bug#889663: FTBFS: Unable to load the SpatiaLite library extension

[Antonio Terceiro]

Source: djangorestframework-gis
Version: 0.12-1
Severity: serious
Justification: fails to build from source

dh_auto_test -- --system=custom --test-args="{interpreter} ./runtests.py"
I: pybuild base:184: python2.7 ./runtests.py
Creating test database for alias 'default'...
Traceback (most recent call last):
  File "./runtests.py", line 15, in 
execute_from_command_line(args)
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 364, in execute_from_command_line
utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 356, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File 
"/usr/lib/python2.7/dist-packages/django/core/management/commands/test.py", 
line 29, in run_from_argv
super(Command, self).run_from_argv(argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 
283, in run_from_argv
self.execute(*args, **cmd_options)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 
330, in execute
output = self.handle(*args, **options)
  File 
"/usr/lib/python2.7/dist-packages/django/core/management/commands/test.py", 
line 62, in handle
failures = test_runner.run_tests(test_labels)
  File "/usr/lib/python2.7/dist-packages/django/test/runner.py", line 601, in 
run_tests
old_config = self.setup_databases()
  File "/usr/lib/python2.7/dist-packages/django/test/runner.py", line 546, in 
setup_databases
self.parallel, **kwargs
  File "/usr/lib/python2.7/dist-packages/django/test/utils.py", line 187, in 
setup_databases
serialize=connection.settings_dict.get('TEST', {}).get('SERIALIZE', True),
  File "/usr/lib/python2.7/dist-packages/django/db/backends/base/creation.py", 
line 69, in create_test_db
run_syncdb=True,
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 131, in call_command
return command.execute(*args, **defaults)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 
330, in execute
output = self.handle(*args, **options)
  File 
"/usr/lib/python2.7/dist-packages/django/core/management/commands/migrate.py", 
line 81, in handle
connection.prepare_database()
  File 
"/usr/lib/python2.7/dist-packages/django/contrib/gis/db/backends/spatialite/base.py",
 line 72, in prepare_database
with self.cursor() as cursor:
  File "/usr/lib/python2.7/dist-packages/django/db/backends/base/base.py", line 
254, in cursor
return self._cursor()
  File "/usr/lib/python2.7/dist-packages/django/db/backends/base/base.py", line 
229, in _cursor
self.ensure_connection()
  File "/usr/lib/python2.7/dist-packages/django/db/backends/base/base.py", line 
213, in ensure_connection
self.connect()
  File "/usr/lib/python2.7/dist-packages/django/db/backends/base/base.py", line 
189, in connect
self.connection = self.get_new_connection(conn_params)
  File 
"/usr/lib/python2.7/dist-packages/django/contrib/gis/db/backends/spatialite/base.py",
 line 65, in get_new_connection
six.reraise(ImproperlyConfigured, ImproperlyConfigured(new_msg), 
sys.exc_info()[2])
  File 
"/usr/lib/python2.7/dist-packages/django/contrib/gis/db/backends/spatialite/base.py",
 line 60, in get_new_connection
cur.execute("SELECT load_extension(%s)", (self.spatialite_lib,))
  File "/usr/lib/python2.7/dist-packages/django/db/backends/sqlite3/base.py", 
line 328, in execute
return Database.Cursor.execute(self, query, params)
django.core.exceptions.ImproperlyConfigured: Unable to load the SpatiaLite 
library extension "mod_spatialite" because: mod_spatialite: cannot open shared 
object file: No such file or directory
E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: python2.7 
./runtests.py
dh_auto_test: pybuild --test -i python{version} -p 2.7 --system=custom 
"--test-args={interpreter} ./runtests.py" returned exit code 13
debian/rules:12: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:9: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


[...]

+--+
| Summary  |
+--+

Build Architecture: amd64
Build Type: full
Build-Space: 660
Build-Time: 3
Distribution: unstable
Fail-Stage: build
Host Architecture: amd64
Install-Time: 20
Job: djangorestframework-gis
Machine Architecture: amd64
Package: djangorestframework-gis
Package-Time: 27
Source-Version: 0.12-1
Space: 660
Status: attempted
Version: 0.12-1



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

Processed: Crash in webkit forwarded

[Debian Bug Tracking System]

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

> forwarded 884023 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889659
Bug #884023 [src:bibledit] bibledit: Installs same file as bibledit-gtk
Set Bug forwarded-to-address to 
'https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889659'.
> thanks
Stopping processing here.

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

Bug#853640: marked as done (reptyr: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 13:23:52 +
with message-id 
and subject line Bug#853640: fixed in reptyr 0.6.2-1.1
has caused the Debian Bug report #853640,
regarding reptyr: ftbfs with GCC-7
to be marked as done.

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

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


-- 
853640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:reptyr
Version: 0.6.2-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/reptyr_0.6.2-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
dh_auto_clean: Compatibility levels before 9 are deprecated (level 7 in use)
make -j1 clean
make[1]: Entering directory '/<>'
rm -f reptyr reptyr.o reallocarray.o attach.o platform/linux/linux_ptrace.o 
platform/linux/linux.o test/victim.o test/victim
make[1]: Leaving directory '/<>'
   dh_clean
dh_clean: Compatibility levels before 9 are deprecated (level 7 in use)
 dpkg-source -b reptyr-0.6.2
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building reptyr using existing ./reptyr_0.6.2.orig.tar.gz
dpkg-source: info: building reptyr in reptyr_0.6.2-1.debian.tar.xz
dpkg-source: info: building reptyr in reptyr_0.6.2-1.dsc
 debian/rules build
dh build
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_testdir
   dh_update_autotools_config
   dh_auto_configure
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" 
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" FCFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong" FFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong" GCJFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong" 
LDFLAGS="-Wl,-z,relro" OBJCFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" OBJCXXFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" 
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
make -j1 "CFLAGS=-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" 
"CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2" "CXXFLAGS=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" "FCFLAGS=-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong" "FFLAGS=-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong" "GCJFLAGS=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong" 
LDFLAGS=-Wl,-z,relro "OBJCFLAGS=-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" "OBJCXXFLAGS=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security"
make[2]: Entering directory '/<>'
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Werror -D_GNU_SOURCE -g -Wdate-time 
-D_FORTIFY_SOURCE=2  -c -o reptyr.o reptyr.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Werror -D_GNU_SOURCE -g -Wdate-time 
-D_FORTIFY_SOURCE=2  -c -o reallocarray.o reallocarray.c
cc -g -O2 

Bug#884023: Crash in webkit bug forwarded

[Teus Benschop]

forwarded 884023 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889659
forwarded 884023 889659

thanks

Bug#889608: man-db: man(1) dumps core (AppArmor involved)

[Colin Watson]

On Mon, Feb 05, 2018 at 08:20:54AM +0100, intrigeri wrote:
> intrigeri:
> > A) drop the child profiles (groff, filter), merge their rules into the
> >main /usr/bin/man profile, and use ix instead of Cx; these rules
> >are not particularly scary so this doesn't seem crazy an option
> 
> I had a closer look and what's scary is not the rules that can be
> found in the child profiles, it's the fact that if we drop the child
> profiles, all processes run by man will have full access to the
> filesystem:
> 
>   # The purpose of this profile isn't to confine man itself (that might be
>   # nice in the future, but is tricky since it's quite configurable), but to
>   # confine the processes it calls that parse untrusted data.
>   /** mrixwlk,
> 
> … i.e. the /usr/bin/man profile would be mostly useless. So let's
> forget about option A and instead choose between:
> 
> > B) remove the AppArmor profile entirely and rely on seccomp instead
> > C) don't enable "no new privs" and rely on AppArmor instead
> 
> I think B is fine given all the non-AppArmor hardening efforts Colin
> has been putting into man-db recently.

I posted to intregeri's merge request about this, but just to have it in
the BTS:

  Thanks - I'm sure this would work, but I don't want to take this
  approach.  My intent was to use both seccomp and AppArmor for the
  groff-related subprocesses (which seems to work fine with older
  kernels, though maybe my testing is inadequate): seccomp serves to
  confine most of the space of possible system calls they might make,
  while AppArmor restricts the parts of the filesystem they can use
  (which seccomp can't do).

  I'm hoping that it's still possible to use both, but I clearly need to
  do more testing on recent Debian kernels.  However, for now, a much
  less invasive workaround is to disable the seccomp filtering, which
  doesn't require complicated maintainer script code.  I'll go ahead and
  do that.

The two things I intend to try are:

  1) stack the child profile on the parent one, so that the kernel knows
 it's a reduction in privilege (I can't get the syntax for this to
 work, but am asking around with AppArmor experts at work)
  2) failing that, link man with libapparmor and do the profile
 transitions manually with aa_change_profile before putting the
 seccomp filter in place (I'd prefer to avoid this, but it's an
 option)

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

Processed: bug 886833 is forwarded to https://gitlab.gnome.org/GNOME/librsvg/issues/198

[Debian Bug Tracking System]

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

> forwarded 886833 https://gitlab.gnome.org/GNOME/librsvg/issues/198
Bug #886833 [librsvg2-2] rsvg_pixbuf_from_file_at_size broken in recent 
librsvg2-2
Changed Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/librsvg/issues/198' from 
'https://bugs.launchpad.net/debian/+source/gweled/+bug/1741664'.
> thanks
Stopping processing here.

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

Bug#886833: [gweled] Not compatable with recent gtk

[Stephen Kitt]

Hi Simon,

On Mon, Feb 05, 2018 at 12:36:06PM +0100, Simon McVittie wrote:
> On Sun, 04 Feb 2018 at 16:16:14 +0200, Juhani Numminen wrote:
> > (gweled:2987): GLib-WARNING **: GError set over the top of a previous 
> > GError or uninitialized memory.
> > This indicates a bug in someone's code. You must ensure an error is NULL 
> > before it's set.
> > The overwriting error message was: Operation not supported
> 
> Regardless of whether there's been an incompatible behaviour change,
> this warning indicates a bug in either gweled or a library that it
> uses. GErrors are like exceptions; after calling some function that
> fails, you must either propagate the error to your caller, or clear the
> error indicator (usually with g_clear_error()) to indicate that it has
> been handled.
> 
> G_DEBUG=fatal-warnings is sometimes useful to pin down the cause for
> warnings like this by turning them into fatal errors that leave a core
> dump.

Yes, thanks, I was aware of that ;-). There are a number of problems
in gweled around the troublesome RSVG call, notably forgetting to
initialise the error pointer to NULL, and then calling g_free on it,
which crashes gweled when an error actually occurs...

I’m fixing all that in gweled, which will still leave the RSVG
regression.

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#888170: marked as done (ruby-redcloth: FTBFS on ruby2.5: undefined method `load_documents' for Psych:Module)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 12:52:55 +
with message-id 
and subject line Bug#888170: fixed in ruby-redcloth 4.3.2-3
has caused the Debian Bug report #888170,
regarding ruby-redcloth: FTBFS on ruby2.5: undefined method `load_documents' 
for Psych:Module
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.)


-- 
888170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-redcloth
Version: 4.3.2-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:

Finished in 1.43 seconds (files took 0.86964 seconds to load)
5797 examples, 0 failures

/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

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

RUBYLIB=/build/ruby-redcloth-4.3.2/debian/ruby-redcloth/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.5.0:/build/ruby-redcloth-4.3.2/debian/ruby-redcloth/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-redcloth/usr/share/rubygems-integration/2.5.0:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation
/build/ruby-redcloth-4.3.2/spec/spec_helper.rb:29:in `block in fixtures': 
undefined method `load_documents' for Psych:Module (NoMethodError)
Did you mean?  load_stream
from /build/ruby-redcloth-4.3.2/spec/spec_helper.rb:26:in `each'
from /build/ruby-redcloth-4.3.2/spec/spec_helper.rb:26:in `fixtures'
from /build/ruby-redcloth-4.3.2/spec/spec_helper.rb:9:in 
`examples_from_yaml'
from 
/build/ruby-redcloth-4.3.2/spec/formatters/class_filtered_html_spec.rb:4:in 
`block in '
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:385:in 
`module_exec'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:385:in 
`subclass'
from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:258:in 
`block in define_example_group_method'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:43:in `block in 
expose_example_group_alias'
from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:84:in `block (2 
levels) in expose_example_group_alias_globally'
from 
/build/ruby-redcloth-4.3.2/spec/formatters/class_filtered_html_spec.rb:3:in 
`'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in 
`load'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in 
`block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in 
`each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in 
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:100:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:86:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
from /usr/bin/rspec:4:in `'
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-redcloth-4.3.2/debian/ruby-redcloth returned exit code 1
make: *** [binary] Error 1
debian/rules:15: recipe for target 'binary' failed
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-redcloth.log

Please fix it!

Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Source: ruby-redcloth
Source-Version: 4.3.2-3

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

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

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

Bug#881815: marked as done (wagon2: missing build dependency on libplexus-classworlds2-java)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 12:44:34 +
with message-id 
and subject line Bug#881815: fixed in wagon2 2.12-4
has caused the Debian Bug report #881815,
regarding wagon2: missing build dependency on libplexus-classworlds2-java
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.)


-- 
881815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wagon2
Version: 2.12-3
Severity: serious

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

...
[WARNING] The POM for org.codehaus.plexus:plexus-classworlds:jar:2.x is 
missing, no dependency information available
[WARNING] The artifact org.codehaus.plexus:plexus-container-default:jar:1.5.5 
has been relocated to org.codehaus.plexus:plexus-container-default:jar:debian
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Maven Wagon . SUCCESS [  0.599 s]
[INFO] Apache Maven Wagon :: API .. SUCCESS [  3.703 s]
[INFO] Apache Maven Wagon :: Provider Test  SUCCESS [  1.455 s]
[INFO] Apache Maven Wagon :: Providers  SUCCESS [  0.027 s]
[INFO] Apache Maven Wagon :: Providers :: File Provider ... SUCCESS [  0.293 s]
[INFO] Apache Maven Wagon :: Providers :: FTP Provider  SUCCESS [  0.430 s]
[INFO] Apache Maven Wagon :: Providers :: HTTP Shared Library SUCCESS [  0.228 
s]
[INFO] Apache Maven Wagon :: Test Compatibility Kits .. SUCCESS [  0.006 s]
[INFO] Apache Maven Wagon :: HTTP Test Compatibility Kit .. FAILURE [  0.016 s]
[INFO] Apache Maven Wagon :: Providers :: HTTP Provider ... SKIPPED
[INFO] Apache Maven Wagon :: Providers :: Lightweight HTTP Provider SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 7.167 s
[INFO] Finished at: 2018-12-17T19:20:44-12:00
[INFO] Final Memory: 25M/594M
[INFO] 
[ERROR] Failed to execute goal on project wagon-tck-http: Could not resolve 
dependencies for project org.apache.maven.wagon:wagon-tck-http:jar:2.12: Cannot 
access central (https://repo.maven.apache.org/maven2) in offline mode and the 
artifact org.codehaus.plexus:plexus-classworlds:jar:2.x has not been downloaded 
from it before. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :wagon-tck-http
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/wagon2-2.12 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/wagon2-2.12/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/wagon2-2.12/debian 
-Dmaven.repo.local=/build/1st/wagon2-2.12/debian/maven-repo --batch-mode 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
debian/rules:9: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: wagon2
Source-Version: 2.12-4

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

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

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated wagon2 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 

Bug#884207: marked as done (byte-buddy FTBFS: Execution default-cli of goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed. NullPointerException)

[Debian Bug Tracking System]

Your message dated Mon, 5 Feb 2018 13:31:39 +0100
with message-id <94de8c07-88dc-030e-4f19-2a0d07387...@debian.org>
and subject line Re: Bug#884207: byte-buddy FTBFS: Execution default-cli of 
goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed. 
NullPointerException
has caused the Debian Bug report #884207,
regarding byte-buddy FTBFS: Execution default-cli of goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed. 
NullPointerException
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.)


-- 
884207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: byte-buddy
Version: 1.7.9-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=byte-buddy=all=1.7.9-1=1513081592=0

...
[INFO] Reactor Summary:
[INFO] 
[INFO] Byte Buddy (parent)  SUCCESS [  0.981 s]
[INFO] Byte Buddy (with dependencies) . SUCCESS [ 50.736 s]
[INFO] Byte Buddy (without dependencies) .. SUCCESS [  2.047 s]
[INFO] Byte Buddy (Maven plugin) .. FAILURE [  2.197 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 56.584 s
[INFO] Finished at: 2017-12-12T12:26:27Z
[INFO] Final Memory: 37M/722M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (default-cli) on 
project byte-buddy-maven-plugin: Execution default-cli of goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed. 
NullPointerException -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :byte-buddy-maven-plugin
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US 
returned exit code 1
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
--- End Message ---
--- Begin Message ---
On Wed, 13 Dec 2017 09:31:13 +0100 Emmanuel Bourg  wrote:
> Thank you Adrian. This is caused by a regression in
> maven-javadoc-plugin/3.0.0. Other packages are probably affected.
> 
> https://issues.apache.org/jira/browse/MJAVADOC-504

I have just successfully rebuilt the package. Apparently Emmanuel fixed
this in maven-javadoc-plugin in version 3.0.0-2. I'm going to close this
bug report now.

Markus--- End Message ---

Bug#884508: marked as done (byte-buddy: FTBFS)

[Debian Bug Tracking System]

Your message dated Mon, 5 Feb 2018 13:31:39 +0100
with message-id <94de8c07-88dc-030e-4f19-2a0d07387...@debian.org>
and subject line Re: Bug#884207: byte-buddy FTBFS: Execution default-cli of 
goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed. 
NullPointerException
has caused the Debian Bug report #884207,
regarding byte-buddy: FTBFS
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.)


-- 
884207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: byte-buddy
Version: 1.7.9-1
Severity: serious
Justification: fails to build from source

Hi,

the recent upload of byte-buddy did FTBFS on the arch:all buildd:

https://buildd.debian.org/status/fetch.php?pkg=byte-buddy=all=1.7.9-1=1513081592=0

   dh_auto_configure -i
mh_patchpoms -plibbyte-buddy-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
[ERROR] Cannot find parent dependency 
net.bytebuddy:byte-buddy-parent:pom:debian, use --no-parent option to resolve 
this issue or install the parent POM in the Maven repository
   dh_auto_build -i
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[...]
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (default-cli) on 
project byte-buddy-maven-plugin: Execution default-cli of goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed. 
NullPointerException -> [Help 1]


Andreas
--- End Message ---
--- Begin Message ---
On Wed, 13 Dec 2017 09:31:13 +0100 Emmanuel Bourg  wrote:
> Thank you Adrian. This is caused by a regression in
> maven-javadoc-plugin/3.0.0. Other packages are probably affected.
> 
> https://issues.apache.org/jira/browse/MJAVADOC-504

I have just successfully rebuilt the package. Apparently Emmanuel fixed
this in maven-javadoc-plugin in version 3.0.0-2. I'm going to close this
bug report now.

Markus--- End Message ---

Bug#889645: architecture baseline violation on ia64

[Jason Duerstock]

Additionally, the inclusion of ia64 is wrong here:

https://sources.debian.org/src/pd-moonlib/0.3.6-2/Makefile.pdlibbuilder/#L424

as is evidenced in this build log:

https://buildd.debian.org/status/fetch.php?pkg=pd-moonlib=ia64=0.3.6-2=1517784204=0

Bug#889615: python-tifffile: broken autopkgtest, broken package

[Sascha Steinbiss]

Hi again,

[...]
>> I wonder whether you have an idea how this can be fixed.
>
> Unfortunately I'm a bit swamped with work and (more so) RL stuff at the
> moment... maybe this has time until the sprint later this week?

Actually this was rather easy to address. I pushed some code that should
fix it.

Cheers
Sascha

Bug#886833: [gweled] Not compatable with recent gtk

[Simon McVittie]

On Sun, 04 Feb 2018 at 16:16:14 +0200, Juhani Numminen wrote:
> (gweled:2987): GLib-WARNING **: GError set over the top of a previous GError 
> or uninitialized memory.
> This indicates a bug in someone's code. You must ensure an error is NULL 
> before it's set.
> The overwriting error message was: Operation not supported

Regardless of whether there's been an incompatible behaviour change,
this warning indicates a bug in either gweled or a library that it
uses. GErrors are like exceptions; after calling some function that
fails, you must either propagate the error to your caller, or clear the
error indicator (usually with g_clear_error()) to indicate that it has
been handled.

G_DEBUG=fatal-warnings is sometimes useful to pin down the cause for
warnings like this by turning them into fatal errors that leave a core
dump.

smcv

Processed: Add found version, remove obsolete tag

[Debian Bug Tracking System]

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

> found 886833 2.40.20-2
Bug #886833 [librsvg2-2] rsvg_pixbuf_from_file_at_size broken in recent 
librsvg2-2
Marked as found in versions librsvg/2.40.20-2.
> tags 886833 - moreinfo
Bug #886833 [librsvg2-2] rsvg_pixbuf_from_file_at_size broken in recent 
librsvg2-2
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#889615: python-tifffile: broken autopkgtest, broken package

[Sascha Steinbiss]

Hi Andreas,

>> $ ./debian/tests/python-import 
>> 2017.09.14
>> Traceback (most recent call last):
>>   File "./debian/tests/python-import", line 16, in 
>> for page in tif:
>> TypeError: 'TiffFile' object is not iterable
>> $
>>
>> This part looks like it might be a bug in the test rather than the package,
>> but without being familiar with the package it's hard for me to know.
> 
> I cared for the missing dependencied (+ upgrade to latest upstream) in
> Git.  I can confirm that the remaining issue above persists.  Sascha,
> since you wrote the test, I wonder whether you have an idea how this can
> be fixed.

Unfortunately I'm a bit swamped with work and (more so) RL stuff at the
moment... maybe this has time until the sprint later this week?
Will look at it though.

Cheers
Sascha

Bug#889626: man-db FTBFS on ppc64el: error: invalid application of 'sizeof' to incomplete type 'struct termios'

[Colin Watson]

On Mon, Feb 05, 2018 at 09:06:15AM +0200, Adrian Bunk wrote:
> ...
> ../../../lib/sandbox.c: In function 'make_seccomp_filter':
> ../../../lib/sandbox.c:435:50: error: invalid application of 'sizeof' to 
> incomplete type 'struct termios'
>SC_ALLOW_ARG_1 ("ioctl", SCMP_A1 (SCMP_CMP_EQ, TCGETS));
>   ^
> ../../../lib/sandbox.c:183:53: note: in definition of macro 'SC_ALLOW_ARG_1'
>if (seccomp_rule_add (ctx, SCMP_ACT_ALLOW, nr, 1, cmp1) < 0) \
>  ^~~~

Thanks.  I've disabled seccomp for now for other reasons, which deals
with this build failure, but I've also fixed the architecture-specific
problem here for the next upstream release:

  
https://git.savannah.gnu.org/cgit/man-db.git/commit/?id=13d37b21fe591b84558cd84701a6930b158b5904

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

Bug#889608: marked as done (man-db: man(1) dumps core (AppArmor involved))

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 10:36:45 +
with message-id 
and subject line Bug#889608: fixed in man-db 2.8.0-2
has caused the Debian Bug report #889608,
regarding man-db: man(1) dumps core (AppArmor involved)
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.)


-- 
889608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: man-db
Version: 2.8.0-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Since the upgrade to 2.8.0-1, man(1) is not really cooperative:

%man man

output in pager:
man: /usr/lib/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE: Bad system 
call (core dumped)

% man --debug man

full output in the console:

ruid=1000, euid=6
rgid=1000, egid=12
drop_effective_privs()
++priv_drop_count = 1
>From the config file /etc/manpath.config:

Mandatory mandir `/usr/man'.
Mandatory mandir `/usr/share/man'.
Mandatory mandir `/usr/local/share/man'.
Path `/bin' mapped to mandir `/usr/share/man'.
Path `/usr/bin' mapped to mandir `/usr/share/man'.
Path `/sbin' mapped to mandir `/usr/share/man'.
Path `/usr/sbin' mapped to mandir `/usr/share/man'.
Path `/usr/local/bin' mapped to mandir `/usr/local/man'.
Path `/usr/local/bin' mapped to mandir `/usr/local/share/man'.
Path `/usr/local/sbin' mapped to mandir `/usr/local/man'.
Path `/usr/local/sbin' mapped to mandir `/usr/local/share/man'.
Path `/usr/X11R6/bin' mapped to mandir `/usr/X11R6/man'.
Path `/usr/bin/X11' mapped to mandir `/usr/X11R6/man'.
Path `/usr/games' mapped to mandir `/usr/share/man'.
Path `/opt/bin' mapped to mandir `/opt/man'.
Path `/opt/sbin' mapped to mandir `/opt/man'.
Global mandir `/usr/man', catdir `/var/cache/man/fsstnd'.
Global mandir `/usr/share/man', catdir `/var/cache/man'.
Global mandir `/usr/local/man', catdir `/var/cache/man/oldlocal'.
Global mandir `/usr/local/share/man', catdir `/var/cache/man/local'.
Global mandir `/usr/X11R6/man', catdir `/var/cache/man/X11R6'.
Global mandir `/opt/man', catdir `/var/cache/man/opt'.
Added section `1'.
Added section `n'.
Added section `l'.
Added section `8'.
Added section `3'.
Added section `2'.
Added section `3posix'.
Added section `3pm'.
Added section `3perl'.
Added section `3am'.
Added section `5'.
Added section `4'.
Added section `9'.
Added section `6'.
Added section `7'.
`/usr/man'  `'  `1'
`/usr/share/man'`'  `1'
`/usr/local/share/man'  `'  `1'
`/bin'  `/usr/share/man'`0'
`/usr/bin'  `/usr/share/man'`0'
`/sbin' `/usr/share/man'`0'
`/usr/sbin' `/usr/share/man'`0'
`/usr/local/bin'`/usr/local/man'`0'
`/usr/local/bin'`/usr/local/share/man'  `0'
`/usr/local/sbin'   `/usr/local/man'`0'
`/usr/local/sbin'   `/usr/local/share/man'  `0'
`/usr/X11R6/bin'`/usr/X11R6/man'`0'
`/usr/bin/X11'  `/usr/X11R6/man'`0'
`/usr/games'`/usr/share/man'`0'
`/opt/bin'  `/opt/man'  `0'
`/opt/sbin' `/opt/man'  `0'
`/usr/man'  `/var/cache/man/fsstnd' `-1'
`/usr/share/man'`/var/cache/man'`-1'
`/usr/local/man'`/var/cache/man/oldlocal'   `-1'
`/usr/local/share/man'  `/var/cache/man/local'  `-1'
`/usr/X11R6/man'`/var/cache/man/X11R6'  `-1'
`/opt/man'  `/var/cache/man/opt'`-1'
`1' `'  `-5'
`n' `'  `-5'
`l' `'  `-5'
`8' `'  `-5'
`3' `'  `-5'
`2' `'  `-5'
`3posix'`'  `-5'
`3pm'   `'  `-5'
`3perl' `'  `-5'
`3am'   `'  `-5'
`5' `'  `-5'
`4' `'  `-5'
`9' `'  `-5'
`6' `'  `-5'
`7' `'  `-5'
is a tty
real user = 1000; effective user = 6

using most as pager

path directory /home/gregoa/bin is not in the config file
and doesn't have ../man, man, ../share/man, or share/man subdirectories

path directory /usr/lib/ccache is not in the config file
and doesn't have ../man, man, ../share/man, or share/man subdirectories

path directory /usr/local/bin is in the config file
warning: /usr/local/man: No such file or directory
warning: /usr/local/share/man: No such file or directory

path directory /usr/bin is in the config file
adding /usr/share/man to manpath

path directory /bin is in the config file
/usr/share/man is already in the manpath

path directory /usr/local/games is not in the config file
and doesn't have ../man, man, ../share/man, or share/man subdirectories

path directory /usr/games is in the config file
/usr/share/man is already in the manpath

adding mandatory man 

Bug#889617: marked as done (man-db: all man pages fail to display with "command exited with status 4")

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 10:36:45 +
with message-id 
and subject line Bug#889608: fixed in man-db 2.8.0-2
has caused the Debian Bug report #889608,
regarding man-db: all man pages fail to display with "command exited with 
status 4"
to be marked as done.

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

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


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

Dear Maintainer,

under man-db 2.8.0-1 amd64 all man pages fail to display with:

$ man man
man: command exited with status 4: /usr/lib/man-db/zsoelim | /usr/lib/man-
db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e UTF-8 | tbl |
nroff -mandoc -rLL=184n -rLT=184n -Tutf8

(Where "all" means all those I tested including "man", "ls", "tar", "git
commit".)

Workaround is to downgrade man-db to 2.7.6.1-4+b1.

Kind regards,
Ben.



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

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

Versions of packages man-db depends on:
ii  bsdmainutils   11.1.2
ii  debconf [debconf-2.0]  1.5.65
ii  dpkg   1.19.0.5
ii  groff-base 1.22.3-9
ii  libc6  2.26-6
ii  libgdbm5   1.14.1-2
ii  libpipeline1   1.5.0-1
ii  libseccomp22.3.1-2.1
ii  zlib1g 1:1.2.8.dfsg-5

man-db recommends no packages.

Versions of packages man-db suggests:
ii  apparmor2.12-2
ii  firefox [www-browser]   58.0.1-1
ii  google-chrome-stable [www-browser]  64.0.3282.140-1
pn  groff   
ii  less487-0.1

-- debconf information:
  man-db/auto-update: true
  man-db/install-setuid: false
--- End Message ---
--- Begin Message ---
Source: man-db
Source-Version: 2.8.0-2

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

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated man-db 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, 05 Feb 2018 10:09:57 +
Source: man-db
Binary: man-db
Architecture: source
Version: 2.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Colin Watson 
Changed-By: Colin Watson 
Description:
 man-db - on-line manual pager
Closes: 889608 889626
Changes:
 man-db (2.8.0-2) unstable; urgency=medium
 .
   * Build without seccomp for now, until I work out how to make it play well
 with AppArmor on recent kernels (closes: #889608, #889626).
Checksums-Sha1:
 896b5209d3f24d84646768d2732d28c6ec4580e3 2173 man-db_2.8.0-2.dsc
 5084d163e10a9e98a00999b3f237d8cf76967a0c 259040 man-db_2.8.0-2.debian.tar.xz
 f930a9281a5768a4ae62933a5e8ffedd0ecb5ea2 6955 man-db_2.8.0-2_source.buildinfo
Checksums-Sha256:
 9b44996df46064fb7238c42947a95146c5f5293cf0112020f44d1e79ecd8a391 2173 
man-db_2.8.0-2.dsc
 6538670c33a9bd8c5b9d56fc1213de85bfb844761033683155c1eb10526f1eb5 259040 
man-db_2.8.0-2.debian.tar.xz
 273072bcecd9369b39bf3c6d4b7feff4902872c2c235a4f1f7a3d7cf06ceacac 6955 
man-db_2.8.0-2_source.buildinfo
Files:
 3ee750ae4dc859bc7767f22b29281253 2173 doc important man-db_2.8.0-2.dsc
 ee468b8639a49bd124a9af452f30bb94 259040 doc important 
man-db_2.8.0-2.debian.tar.xz
 9106c9c51b0780a80320e2184b596553 6955 doc important 
man-db_2.8.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAlp4LmEACgkQOTWH2X2G
UAsWtw//ZCDItQY58/l+1MYRk7kcU8HSWaLZ3a1n3sBS3FrmmeHlUHBwFPLjGnpF
+R/78MqYzd8ozc7nWoEIyqlwU4IEwVIj0HXjEx8ZEbEcJ5l+8gAP0xID0In7lMl3

Bug#889626: marked as done (man-db FTBFS on ppc64el: error: invalid application of 'sizeof' to incomplete type 'struct termios')

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 10:36:45 +
with message-id 
and subject line Bug#889626: fixed in man-db 2.8.0-2
has caused the Debian Bug report #889626,
regarding man-db FTBFS on ppc64el: error: invalid application of 'sizeof' to 
incomplete type 'struct termios'
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.)


-- 
889626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: man-db
Version: 2.8.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=man-db=ppc64el=2.8.0-1=1517768128=0

...
../../../lib/sandbox.c: In function 'make_seccomp_filter':
../../../lib/sandbox.c:435:50: error: invalid application of 'sizeof' to 
incomplete type 'struct termios'
   SC_ALLOW_ARG_1 ("ioctl", SCMP_A1 (SCMP_CMP_EQ, TCGETS));
  ^
../../../lib/sandbox.c:183:53: note: in definition of macro 'SC_ALLOW_ARG_1'
   if (seccomp_rule_add (ctx, SCMP_ACT_ALLOW, nr, 1, cmp1) < 0) \
 ^~~~
Makefile:1662: recipe for target 'libman_la-sandbox.lo' failed
make[3]: *** [libman_la-sandbox.lo] Error 1
--- End Message ---
--- Begin Message ---
Source: man-db
Source-Version: 2.8.0-2

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

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated man-db 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, 05 Feb 2018 10:09:57 +
Source: man-db
Binary: man-db
Architecture: source
Version: 2.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Colin Watson 
Changed-By: Colin Watson 
Description:
 man-db - on-line manual pager
Closes: 889608 889626
Changes:
 man-db (2.8.0-2) unstable; urgency=medium
 .
   * Build without seccomp for now, until I work out how to make it play well
 with AppArmor on recent kernels (closes: #889608, #889626).
Checksums-Sha1:
 896b5209d3f24d84646768d2732d28c6ec4580e3 2173 man-db_2.8.0-2.dsc
 5084d163e10a9e98a00999b3f237d8cf76967a0c 259040 man-db_2.8.0-2.debian.tar.xz
 f930a9281a5768a4ae62933a5e8ffedd0ecb5ea2 6955 man-db_2.8.0-2_source.buildinfo
Checksums-Sha256:
 9b44996df46064fb7238c42947a95146c5f5293cf0112020f44d1e79ecd8a391 2173 
man-db_2.8.0-2.dsc
 6538670c33a9bd8c5b9d56fc1213de85bfb844761033683155c1eb10526f1eb5 259040 
man-db_2.8.0-2.debian.tar.xz
 273072bcecd9369b39bf3c6d4b7feff4902872c2c235a4f1f7a3d7cf06ceacac 6955 
man-db_2.8.0-2_source.buildinfo
Files:
 3ee750ae4dc859bc7767f22b29281253 2173 doc important man-db_2.8.0-2.dsc
 ee468b8639a49bd124a9af452f30bb94 259040 doc important 
man-db_2.8.0-2.debian.tar.xz
 9106c9c51b0780a80320e2184b596553 6955 doc important 
man-db_2.8.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAlp4LmEACgkQOTWH2X2G
UAsWtw//ZCDItQY58/l+1MYRk7kcU8HSWaLZ3a1n3sBS3FrmmeHlUHBwFPLjGnpF
+R/78MqYzd8ozc7nWoEIyqlwU4IEwVIj0HXjEx8ZEbEcJ5l+8gAP0xID0In7lMl3
GG82m+S9xdnFd4E9eIoOe2wkFlYfbCpoOBxGXyaR32InxB0JUhz7Xwf95cZY/0Oo
gY6iE7NjkO8TVpKpkZ8nY3Q585LnDzns0adEt9muJD+iJkQghDWJPMqgVNySIbOd
AIDOdx5FOytab5vZ8L+rq7w10ZY6spxfJpX5QkCr99ic6mYq354REMR0DxFHYGq4
YSSfyelBnTCGvelIMZk5eqeVesVd1ZXC6nHEudI04GY3EqJyv9gHSGqB8ZSq3r5q
/6aBgm4XPJHTADMhMjTX1WZ5tObsTdGFiegMnN76NYDJPVX5xloAbzzAx+BpLRfV
63xDFBkUpstw5TlaZcgO+GztyJ2w37LbSILftpblH7el68bD6hwciGMrfdlvjCS1
lrJyoHISnr5Sje950twjhfFenxAMhcoCntd7ChvJGFfTup0rGbsCmDrtf+eaKm+K
DunrGF1xlJoNo8KF2s0DvUcpIwBlrifN/Zt6f4vwuOPnj/q0L/vXNal11O6074aO
fbKxegnkYiJ2d0xXwqqJfNHiR/c9RQ0vh6r7wwABVKr0L8qytWY=
=W+pF
-END PGP SIGNATURE End Message ---

Processed: tagging 888168

[Debian Bug Tracking System]

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

> tags 888168 + upstream
Bug #888168 [src:ruby-redcarpet] ruby-redcarpet: FTBFS on ruby2.5: incompatible 
library version
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: bug 888168 is forwarded to https://github.com/vmg/redcarpet/issues/644

[Debian Bug Tracking System]

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

> forwarded 888168 https://github.com/vmg/redcarpet/issues/644
Bug #888168 [src:ruby-redcarpet] ruby-redcarpet: FTBFS on ruby2.5: incompatible 
library version
Set Bug forwarded-to-address to 'https://github.com/vmg/redcarpet/issues/644'.
> thanks
Stopping processing here.

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

Bug#889608: Bug #889608 in man-db marked as pending

[cjwatson]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/man-db/commit/d31cb825ad3716ac3812dfb693a0aefadc121b46


Build without seccomp for now, until I work out how to make it play well with 
AppArmor on recent kernels (closes: #889608, #889626).



(this message was generated automatically)
-- 
Greetings

Processed: Bug #889626 in man-db marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #889626 [src:man-db] man-db FTBFS on ppc64el: error: invalid application of 
'sizeof' to incomplete type 'struct termios'
Added tag(s) pending.

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

Processed: Bug #889608 in man-db marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #889608 [man-db] man-db: man(1) dumps core (AppArmor involved)
Bug #889617 [man-db] man-db: all man pages fail to display with "command exited 
with status 4"
Added tag(s) pending.
Added tag(s) pending.

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

Bug#889626: Bug #889626 in man-db marked as pending

[cjwatson]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/man-db/commit/d31cb825ad3716ac3812dfb693a0aefadc121b46


Build without seccomp for now, until I work out how to make it play well with 
AppArmor on recent kernels (closes: #889608, #889626).



(this message was generated automatically)
-- 
Greetings

Bug#889502: marked as done (cypari2: FTBFS on several architectures)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 10:06:37 +
with message-id 
and subject line Bug#889502: fixed in cypari2 1.1.4-1
has caused the Debian Bug report #889502,
regarding cypari2: FTBFS on several architectures
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.)


-- 
889502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cypari2
Version: 1.1.3-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

cypari2/experimental FTBFS on several architectures:
https://buildd.debian.org/status/package.php?p=cypari2=experimental

I can reproduce this in pbuilder on i386, but not on amd64 (where it
also built successfully on the buildd).

Excerpt from
https://buildd.debian.org/status/fetch.php?pkg=cypari2=i386=1.1.3-3=1516945955=0

make[2]: Entering directory '/<>/docs'
Running Sphinx v1.6.6
making output directory...
loading pickled environment... not yet created
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 6 source files that are out of date
updating environment: 6 added, 0 changed, 0 removed
reading sources... [ 16%] closure
reading sources... [ 33%] convert
reading sources... [ 50%] gen
reading sources... [ 66%] handle_error
reading sources... [ 83%] index
reading sources... [100%] pari_instance

/<>/docs/source/closure.rst:1: WARNING: autodoc: failed to import 
module u'cypari2.closure'; the following exception was raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 658, in 
import_object
__import__(self.modname)
ImportError: No module named cypari2.closure
/<>/docs/source/convert.rst:1: WARNING: autodoc: failed to import 
module u'cypari2.convert'; the following exception was raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 658, in 
import_object
__import__(self.modname)
ImportError: No module named cypari2.convert
/<>/docs/source/gen.rst:1: WARNING: autodoc: failed to import 
module u'cypari2.gen'; the following exception was raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 658, in 
import_object
__import__(self.modname)
ImportError: No module named cypari2.gen
/<>/docs/source/handle_error.rst:1: WARNING: autodoc: failed to 
import module u'cypari2.handle_error'; the following exception was raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 658, in 
import_object
__import__(self.modname)
ImportError: No module named cypari2.handle_error
/<>/docs/source/pari_instance.rst:1: WARNING: autodoc: failed to 
import module u'cypari2.pari_instance'; the following exception was raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 658, in 
import_object
__import__(self.modname)
ImportError: No module named cypari2.pari_instance
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done


Andreas
--- End Message ---
--- Begin Message ---
Source: cypari2
Source-Version: 1.1.4-1

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated cypari2 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, 05 Feb 2018 10:21:58 +0100
Source: cypari2
Binary: python-cypari2 python3-cypari2 python-cypari2-doc
Architecture: source
Version: 1.1.4-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tobias Hansen 
Description:
 python-cypari2 - Python interface to PARI -- Python 2
 python-cypari2-doc - Python interface to PARI -- documentation
 python3-cypari2 - 

Bug#889073: Permission denied on /run/munin/munin-node.pid

[Sven Hartge]

Hello!

Just for your information:

This is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889144 and
https://github.com/systemd/systemd/issues/8085

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature

Bug#889646: knot-resolver: Incomplete debian/copyright?

[Chris Lamb]

Source: knot-resolver
Version: 2.0.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Daniel Kahn Gillmor 

Hi,

I just ACCEPTed knot-resolver from NEW but noticed it was missing 
attribution in debian/copyright for at least the faketime, libswrap
and lmdb code copies.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

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

Bug#889645: pd-moonlib: architecture baseline violation on amd64/i386/armel/armhf

[Adrian Bunk]

Package: pd-moonlib
Version: 0.3.6-2
Severity: serious

There is no SSE3 in the amd64 port baseline.
There is no SSE in the i386 port baseline.
There is no VFP in the armel port baseline.
There aren't 32 FPU registers in the armhf port baseline.

Please be more careful when doing "Simplified & unified d/rules".

Bug#889642: jdeb FTBFS: [ERROR] testClearSign(org.vafer.jdeb.signing.PGPSignerTestCase)

[Adrian Bunk]

Source: jdeb
Version: 1.6-1
Severity: serious

Some recent change in unstable makes jdeb FTBFS:

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

...
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running org.vafer.jdeb.maven.DataTestCase
[INFO] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.851 s 
- in org.vafer.jdeb.maven.DataTestCase
[INFO] Running org.vafer.jdeb.DebMakerTestCase
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.682 s 
- in org.vafer.jdeb.DebMakerTestCase
[INFO] Running org.vafer.jdeb.DataBuilderTestCase
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.14 s - 
in org.vafer.jdeb.DataBuilderTestCase
[INFO] Running org.vafer.jdeb.ant.AntSelectorTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.043 s 
- in org.vafer.jdeb.ant.AntSelectorTestCase
[INFO] Running org.vafer.jdeb.ant.DebAntTaskTestCase
[INFO] Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.86 s 
- in org.vafer.jdeb.ant.DebAntTaskTestCase
[INFO] Running org.vafer.jdeb.producers.DataProducerFilesTestCase
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.467 s 
- in org.vafer.jdeb.producers.DataProducerFilesTestCase
[INFO] Running org.vafer.jdeb.producers.DataProducerPathTemplateTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in 
org.vafer.jdeb.producers.DataProducerPathTemplateTestCase
[INFO] Running org.vafer.jdeb.signing.PGPSignerTestCase
[ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.58 s 
<<< FAILURE! - in org.vafer.jdeb.signing.PGPSignerTestCase
[ERROR] testClearSign(org.vafer.jdeb.signing.PGPSignerTestCase)  Time elapsed: 
0.58 s  <<< FAILURE!
org.junit.ComparisonFailure: 
expected:<...-
Version: BCPG v1.5[8]

??...> but was:<...-
Version: BCPG v1.5[9]

??...>
at 
org.vafer.jdeb.signing.PGPSignerTestCase.testClearSign(PGPSignerTestCase.java:68)

[INFO] Running org.vafer.jdeb.signing.DebMakerTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.199 s 
- in org.vafer.jdeb.signing.DebMakerTestCase
[INFO] Running org.vafer.jdeb.debian.ChangesFileTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s 
- in org.vafer.jdeb.debian.ChangesFileTestCase
[INFO] Running org.vafer.jdeb.debian.PackageControlFileTestCase
[INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 s 
- in org.vafer.jdeb.debian.PackageControlFileTestCase
[INFO] Running org.vafer.jdeb.debian.ControlFieldTestCase
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in 
org.vafer.jdeb.debian.ControlFieldTestCase
[INFO] Running org.vafer.jdeb.mapping.LsMapperTestCase
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s 
- in org.vafer.jdeb.mapping.LsMapperTestCase
[INFO] Running org.vafer.jdeb.changes.TextfileChangesProviderTestCase
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 s 
- in org.vafer.jdeb.changes.TextfileChangesProviderTestCase
[INFO] Running org.vafer.jdeb.utils.FilteredFileTestCase
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 s 
- in org.vafer.jdeb.utils.FilteredFileTestCase
[INFO] Running org.vafer.jdeb.utils.UtilsTestCase
[INFO] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.055 s 
- in org.vafer.jdeb.utils.UtilsTestCase
[INFO] Running org.vafer.jdeb.utils.InformationInputStreamTestCase
[INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 s 
- in org.vafer.jdeb.utils.InformationInputStreamTestCase
[INFO] 
[INFO] Results:
[INFO] 
[ERROR] Failures: 
[ERROR]   
PGPSignerTestCase.testClearSign:68->Assert.assertEquals:144->Assert.assertEquals:115
 expected:<...-
Version: BCPG v1.5[8]

??...> but was:<...-
Version: BCPG v1.5[9]

??...>
[INFO] 
[ERROR] Tests run: 77, Failures: 1, Errors: 0, Skipped: 0
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 25.945 s
[INFO] Finished at: 2018-02-04T09:20:28-12:00
[INFO] Final Memory: 26M/905M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
project jdeb: There are test failures.
[ERROR] 
[ERROR] Please refer to /build/1st/jdeb-1.6/target/surefire-reports for the 
individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
[date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 

Bug#889606: marked as done (mupen64plus-video-glide64mk2: uninstallable in sid: virtual package libtxc-dxtn0 is no longer provided)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 09:08:26 +
with message-id 
and subject line Bug#889606: fixed in mupen64plus-video-glide64mk2 2.5-5
has caused the Debian Bug report #889606,
regarding mupen64plus-video-glide64mk2: uninstallable in sid: virtual package 
libtxc-dxtn0 is no longer provided
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.)


-- 
889606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mupen64plus-video-glide64mk2
Version: 2.5-4
Severity: serious
Tags: sid buster
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

The following packages have unmet dependencies:
 mupen64plus-video-glide64mk2 : Depends: libtxc-dxtn0 but it is not installable

libtxc-dxtn0 was provided by libtxc-dxtn-s2tc which has been
removed from sid.


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: mupen64plus-video-glide64mk2
Source-Version: 2.5-5

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

Debian distribution maintenance software
pp.
Sven Eckelmann  (supplier of updated 
mupen64plus-video-glide64mk2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 05 Feb 2018 08:37:04 +0100
Source: mupen64plus-video-glide64mk2
Binary: mupen64plus-video-glide64mk2
Architecture: source amd64
Version: 2.5-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Sven Eckelmann 
Description:
 mupen64plus-video-glide64mk2 - Glide64Mk2 high-level graphics emulation for 
mupen64plus
Closes: 889606
Changes:
 mupen64plus-video-glide64mk2 (2.5-5) unstable; urgency=medium
 .
   * debian/control
 - Change Vcs-Git to https://
 - update to debhelper 10
 - Switch to salsa URLs for Vcs-*
   * Sort debian control files with `wrap-and-sort -abst`
   * Upgraded to policy 4.1.3, no changes required
   * debian/copyright:
 - Update copyright years
   * debian/rules
 - Remove ddeb migration conflict against pre-stretch package
 - Disable usage of libtxc-dxtn0 which is no longer available
   (Closes: #889606)
Checksums-Sha1:
 ab088e8dbe465d8bf7ba9b52b0ab3e560ba31e14 2419 
mupen64plus-video-glide64mk2_2.5-5.dsc
 249a77690f1c015ba7988e8408ac968975c86b66 13284 
mupen64plus-video-glide64mk2_2.5-5.debian.tar.xz
 42a2293f1903448f58ae1fc8f1c38b11226053ea 760112 
mupen64plus-video-glide64mk2-dbgsym_2.5-5_amd64.deb
 5c37986d2f837dff331870e342d0aa191a26797c 11246 
mupen64plus-video-glide64mk2_2.5-5_amd64.buildinfo
 698fc9cc334c6197487f14aafa8a0c933ecb86ea 334484 
mupen64plus-video-glide64mk2_2.5-5_amd64.deb
Checksums-Sha256:
 59a790f678ba9712339604a031eecb459b32b505b2a80b37cd26ca41a685fada 2419 
mupen64plus-video-glide64mk2_2.5-5.dsc
 1ed87d4e2f5a4f3260ea9c1302f2b216b865e43d754d9398b4117d431e2f6b3c 13284 
mupen64plus-video-glide64mk2_2.5-5.debian.tar.xz
 ca4feb6080563dbc589beb7448a9b643ca5ecf5e41e54e7b81f2f1f5e94b 760112 
mupen64plus-video-glide64mk2-dbgsym_2.5-5_amd64.deb
 3f49859bb26cc0f8f704b77bed98806abbde4838489e107caa5307e074eb8d76 11246 
mupen64plus-video-glide64mk2_2.5-5_amd64.buildinfo
 db189176a71a809d0f3fc6b942c7a78af5693c13b2c5d3c714f7a9bb787901a8 334484 
mupen64plus-video-glide64mk2_2.5-5_amd64.deb
Files:
 6e5636dc69a9a6eb25f75ccc57196642 2419 games optional 
mupen64plus-video-glide64mk2_2.5-5.dsc
 eff1ca92bc64ad6ecfb7e46a0d699481 13284 games optional 
mupen64plus-video-glide64mk2_2.5-5.debian.tar.xz
 05c64ef9cd3ad0598ed279e8a532f02d 760112 debug optional 
mupen64plus-video-glide64mk2-dbgsym_2.5-5_amd64.deb
 fd32f2b3829d267b99916bd0855b35bf 11246 games optional 
mupen64plus-video-glide64mk2_2.5-5_amd64.buildinfo
 b66b055734b32b6541453d3a43eed360 334484 games optional 
mupen64plus-video-glide64mk2_2.5-5_amd64.deb

-BEGIN PGP SIGNATURE-

Bug#889560: marked as done (trilinos: cmake files seem to be missing)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 09:09:45 +
with message-id 
and subject line Bug#889560: fixed in trilinos 12.12.1-4
has caused the Debian Bug report #889560,
regarding trilinos: cmake files seem to be missing
to be marked as done.

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

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


-- 
889560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trilinos
Version: 12.12.1-3
Severity: serious
Control: affects -1 src:deal.ii

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

...
-- Include /build/1st/deal.ii-8.4.2/cmake/configure/configure_2_trilinos.cmake
CMake Error at /usr/lib/x86_64-linux-gnu/cmake/ROL/ROLConfig.cmake:174 
(INCLUDE):
  INCLUDE could not find load file:

/usr/lib/x86_64-linux-gnu/cmake/ROL/../MiniTensor/MiniTensorConfig.cmake
Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/Piro/PiroConfig.cmake:143 (INCLUDE)
  /usr/lib/x86_64-linux-gnu/cmake/Trilinos/TrilinosConfig.cmake:146 (INCLUDE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/modules/FindTRILINOS.cmake:40 (FIND_PACKAGE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/configure/configure_2_trilinos.cmake:22 (FIND_PACKAGE)
  obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/macro_configure_feature.tmp:1 
(FEATURE_TRILINOS_FIND_EXTERNAL)
  cmake/macros/macro_configure_feature.cmake:76 (INCLUDE)
  cmake/macros/macro_configure_feature.cmake:240 (RUN_COMMAND)
  cmake/configure/configure_2_trilinos.cmake:220 (CONFIGURE_FEATURE)
  cmake/macros/macro_verbose_include.cmake:19 (INCLUDE)
  CMakeLists.txt:119 (VERBOSE_INCLUDE)


CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Piro/PiroConfig.cmake:145 
(INCLUDE):
  INCLUDE could not find load file:

/usr/lib/x86_64-linux-gnu/cmake/Piro/../Tempus/TempusConfig.cmake
Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/Trilinos/TrilinosConfig.cmake:146 (INCLUDE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/modules/FindTRILINOS.cmake:40 (FIND_PACKAGE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/configure/configure_2_trilinos.cmake:22 (FIND_PACKAGE)
  obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/macro_configure_feature.tmp:1 
(FEATURE_TRILINOS_FIND_EXTERNAL)
  cmake/macros/macro_configure_feature.cmake:76 (INCLUDE)
  cmake/macros/macro_configure_feature.cmake:240 (RUN_COMMAND)
  cmake/configure/configure_2_trilinos.cmake:220 (CONFIGURE_FEATURE)
  cmake/macros/macro_verbose_include.cmake:19 (INCLUDE)
  CMakeLists.txt:119 (VERBOSE_INCLUDE)


CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Piro/PiroConfig.cmake:181 
(INCLUDE):
  INCLUDE could not find load file:

/usr/lib/x86_64-linux-gnu/cmake/Piro/../MiniTensor/MiniTensorConfig.cmake
Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/Trilinos/TrilinosConfig.cmake:146 (INCLUDE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/modules/FindTRILINOS.cmake:40 (FIND_PACKAGE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/configure/configure_2_trilinos.cmake:22 (FIND_PACKAGE)
  obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/macro_configure_feature.tmp:1 
(FEATURE_TRILINOS_FIND_EXTERNAL)
  cmake/macros/macro_configure_feature.cmake:76 (INCLUDE)
  cmake/macros/macro_configure_feature.cmake:240 (RUN_COMMAND)
  cmake/configure/configure_2_trilinos.cmake:220 (CONFIGURE_FEATURE)
  cmake/macros/macro_verbose_include.cmake:19 (INCLUDE)
  CMakeLists.txt:119 (VERBOSE_INCLUDE)


CMake Warning at 
/usr/lib/x86_64-linux-gnu/cmake/Trilinos/TrilinosConfig.cmake:156 (MESSAGE):
  Component "Tempus" NOT found.
Call Stack (most recent call first):
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/modules/FindTRILINOS.cmake:40 (FIND_PACKAGE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/configure/configure_2_trilinos.cmake:22 (FIND_PACKAGE)
  obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/macro_configure_feature.tmp:1 
(FEATURE_TRILINOS_FIND_EXTERNAL)
  cmake/macros/macro_configure_feature.cmake:76 (INCLUDE)
  cmake/macros/macro_configure_feature.cmake:240 (RUN_COMMAND)
  cmake/configure/configure_2_trilinos.cmake:220 (CONFIGURE_FEATURE)
  cmake/macros/macro_verbose_include.cmake:19 (INCLUDE)
  CMakeLists.txt:119 (VERBOSE_INCLUDE)


CMake Warning at 
/usr/lib/x86_64-linux-gnu/cmake/Trilinos/TrilinosConfig.cmake:156 (MESSAGE):
  Component "Domi" NOT found.
Call Stack (most recent call first):
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)