Processed: tagging 907359

[Debian Bug Tracking System]

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

> tags 907359 + buster sid
Bug #907359 [src:minify-maven-plugin] minify-maven-plugin: FTBFS in buster/sid 
(Could not resolve dependencies for project 
com.samaxes.maven:minify-maven-plugin:maven-plugin:1.7.4)
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#907362: marked as done (fwbuilder-dbg is empty)

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 07:50:18 +
with message-id 
and subject line Bug#907362: fixed in fwbuilder 5.3.7-3
has caused the Debian Bug report #907362,
regarding fwbuilder-dbg is empty
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.)


-- 
907362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fwbuilder-dbg
Version: 5.3.7-2
Severity: grave

Both fwbuilder-dbgsym (with proper contents)
and an empty fwbuilder-dbg exist:

$ dpkg -L fwbuilder-dbg
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/fwbuilder-dbg
/usr/share/doc/fwbuilder-dbg/changelog.Debian.gz
/usr/share/doc/fwbuilder-dbg/changelog.gz
/usr/share/doc/fwbuilder-dbg/copyright
$


Please drop the empty fwbuilder-dbg.
--- End Message ---
--- Begin Message ---
Source: fwbuilder
Source-Version: 5.3.7-3

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated fwbuilder 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, 27 Aug 2018 08:31:34 +0200
Source: fwbuilder
Binary: fwbuilder fwbuilder-common fwbuilder-doc
Architecture: source
Version: 5.3.7-3
Distribution: unstable
Urgency: medium
Maintainer: Sylvestre Ledru 
Changed-By: Sylvestre Ledru 
Description:
 fwbuilder  - Firewall administration tool GUI
 fwbuilder-common - Firewall administration tool GUI (common files)
 fwbuilder-doc - Firewall administration tool GUI documentation
Closes: 907362
Changes:
 fwbuilder (5.3.7-3) unstable; urgency=medium
 .
   * Remove empty fwbuilder-dbg as fwbuilder-dbgsym exists
 (Closes: #907362)
   * Standards-Version: 4.2.0
Checksums-Sha1:
 b6fd6a206e9f2f42bd81fd69d35317d88939ae2e 2107 fwbuilder_5.3.7-3.dsc
 87af4667b09ee98dfd109cab12ba5122de8a5986 11456 fwbuilder_5.3.7-3.debian.tar.xz
 44adfd9ec648f9b36fc002487e578097866926a3 11958 
fwbuilder_5.3.7-3_amd64.buildinfo
Checksums-Sha256:
 a6242398c82e861d7418083a94f0eae0c368dae4fdd04797949882484dd2652d 2107 
fwbuilder_5.3.7-3.dsc
 bcdf276b1ee488cc35ecb353f6f04072e0aa9e57700a25e44c1080e48649072b 11456 
fwbuilder_5.3.7-3.debian.tar.xz
 2881da9a8955ee4d61a4521e7c4e2a8f317e2a6ac1b28608536ce30b6e21268e 11958 
fwbuilder_5.3.7-3_amd64.buildinfo
Files:
 8354a500664715b3e66f8a96192f6287 2107 net optional fwbuilder_5.3.7-3.dsc
 a25336790e5cbceba4306961341c6746 11456 net optional 
fwbuilder_5.3.7-3.debian.tar.xz
 5c3a636db3c80991bbd056e01bb559b7 11958 net optional 
fwbuilder_5.3.7-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAluDqhgACgkQfmUo2nUv
G+HGRhAAmF5mR3YjGS37ALQUYhYl0tTsrrMg8wa7W9+Xy8PZv/W9HC8pXtQK1KYe
fCSJ7job/yBwXJTNuTFrxvTPQUrhBySfxAW9TOvRR4g2sV2LVQec5g0JEZosEOTD
hlkGJWXMlpcqeoJf5BwoJ3HWTM15olhWRz3MzSKPqKcHpxEhugVJpLr31SUXd1q4
48pdnXcHg2Hrv4oGiS5kHNN6742BmlV/gChVVZgbxJ3DJEoLzSuGfDXAJ+9pJxhi
/+Nj2UQvvUSpqGP3C/qEE5LDoDKie9mLSgi1gjDNdIowLNUPyyUCHKkYlRDfVcj7
Sp7UdKghlb7kEz5KaD0WUK5Ts7OA8T9lRPmbXCwKinoqs70/fRMPQeIcBPJhMKQh
7qHqcl2BML9BScePf4azDpVSJgOYSe0kPixDUAf7XIDZwgugfQTriVluLQN6cAMK
rOCahEHXwR0Dn6cP+Q/+jjC0YUBRPZLI+KLcoSMqGxXwA89oUuZxHIKCOTZwcpac
rkHNxa6Bg0vjfvuc42CKjOa9pbkFb85HIcz9s8/EMZXIb1bT0P+CA2iTlJBDqaxb
TgXKbETdu/WqgIvR+vQs97zjo2RCeyLKSJy2bL60g5u1i9ifD2xiFRzZ+X3aJGlj
gN3Q81jTaxCAlewpmCZiruX0dSLL2X359pT9YvhMLi50sblR6Og=
=Fk6P
-END PGP SIGNATURE End Message ---

Bug#906158: intel-microcode: Update intel-microcode to 20180807

[Darius Spitznagel]

Hello maintainers,

today I've installed intel-microcode (3.20180807a.1~bpo9+1) from 
stretch-backports to realize that firmware file "06-2c-02" is missing.

snippet from dmesg:

[  290.754628] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.754701] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.754758] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.754812] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.754866] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.754919] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.754973] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.755026] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.755079] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.755132] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.755186] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.755239] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.755292] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.755345] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.755399] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.755452] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.755506] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.79] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.755612] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.755665] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.755718] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.755772] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.755825] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)
[  290.755878] platform microcode: firmware: failed to load 
intel-ucode/06-2c-02 (-2)

After downloading firmware from Intel 
(https://downloadmirror.intel.com/28087/eng/microcode-20180807a.tgz), unpacking 
and copying file "06-2c-02" to /lib/firmware/intel-ucode and executing "echo 1 
> /sys/devices/system/cpu/microcode/reload" everything is fine.

snippet from dmesg:

[  662.432843] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.433568] microcode: updated to revision 0x1f, date = 2018-05-08
[  662.433702] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.434464] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.435062] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.435755] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.436408] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.437094] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.437767] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.438456] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.439115] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.439803] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.440465] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.441175] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.441802] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.442480] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.443098] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.443782] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.50] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.445149] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.445758] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.446698] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.447403] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.448272] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02
[  662.448936] platform microcode: firmware: direct-loading firmware 
intel-ucode/06-2c-02

System is an Intel Westmere E5645.
Please add this firmware file as soon as possible.

Kind regards
Darius



Hinweis zur DSGVO (Datenschutzgrundverordnung):
Wir verarbeiten personenbezogene

Bug#907381: python-sphinx: missing dependency on python-stemmer

[Adrian Bunk]

Package: python-sphinx
Version: 1.7.7-1
Severity: serious
Control: affects -1 src:bzr

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/bzr.html

...
sphinx-build -b html -d _build/doctrees   . _build/html
Running Sphinx v1.7.7
loading translations [es]... done
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%] index
reading sources... [ 33%] mini-tutorial/index
reading sources... [ 50%] quick-reference/index
reading sources... [ 66%] user-guide/index
reading sources... [ 83%] user-guide/index-plain
reading sources... [100%] user-guide/version_info

looking for now-outdated files... none found
pickling environment... done
checking consistency... 
/build/1st/bzr-2.7.0+bzr6622/doc/es/user-guide/index-plain.txt: WARNING: 
document isn't included in any toctree
done
preparing documents... 
Exception occurred:
  File "/usr/lib/python2.7/dist-packages/sphinx/search/es.py", line 14, in 

import Stemmer
ImportError: No module named Stemmer
The full traceback has been saved in /tmp/sphinx-err-Y1IJ0z.log, if you want to 
report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
make[3]: *** [Makefile:50: html] Error 2


python3-sphinx likely has a similar problem.

Processed: python-sphinx: missing dependency on python-stemmer

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:bzr
Bug #907381 [python-sphinx] python-sphinx: missing dependency on python-stemmer
Added indication that 907381 affects src:bzr

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

Bug#830214: node-oauth: accesses the internet during build

[Chris Lamb]

severity 830214 important
thanks

I'm lowering severity as violating a "may not" is not an RC bug as per
Policy §1.1.


Regards,

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

Bug#830215: node-redis: accesses the internet during build

[Chris Lamb]

severity 830215 important
thanks

I'm lowering severity as violating a "may not" is not an RC bug as per
Policy § 1.1.


Regards,

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

Processed: Re: node-oauth: accesses the internet during build

[Debian Bug Tracking System]

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

> severity 830214 important
Bug #830214 [src:node-oauth] node-oauth: accesses the internet during build
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: Re: node-redis: accesses the internet during build

[Debian Bug Tracking System]

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

> severity 830215 important
Bug #830215 [src:node-redis] node-redis: accesses the internet during build
Bug #842209 [src:node-redis] node-redis: accesses the internet during build
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#896226: marked as done (python-v-sim: gi.overrides.v_sim fails to import)

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 08:37:10 +
with message-id 
and subject line Bug#896226: fixed in v-sim 3.7.2-6
has caused the Debian Bug report #896226,
regarding python-v-sim: gi.overrides.v_sim fails to import
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.)


-- 
896226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896226
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-v-sim
Version: 3.7.2-5
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-v-sim importing the module gi.overrides.v_sim
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/gi/overrides/v_sim.py", line 48, in 

v_sim = modules['v_sim']
KeyError: 'v_sim'

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: v-sim
Source-Version: 3.7.2-6

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

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

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

Debian distribution maintenance software
pp.
Damien Caliste  (supplier of updated v-sim package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 26 Jul 2018 15:50:43 +0200
Source: v-sim
Binary: v-sim v-sim-common gir1.2-v-sim-1.0 v-sim-doc v-sim-plugins python-v-sim
Architecture: source amd64 all
Version: 3.7.2-6
Distribution: unstable
Urgency: low
Maintainer: Debian Science Team 

Changed-By: Damien Caliste 
Description:
 gir1.2-v-sim-1.0 - Visualize atomic structures (gir bindings)
 python-v-sim - Python bindings for V_Sim (a 3D visualization package)
 v-sim  - Visualize atomic structures
 v-sim-common - Visualize atomic structures (support files)
 v-sim-doc  - Visualize atomic structures (example files)
 v-sim-plugins - Plugins for V_Sim (a 3D visualization package)
Closes: 896226
Changes:
 v-sim (3.7.2-6) unstable; urgency=low
 .
   * Standards-Version updated to 4.2.0
   * Add Multi-Arch: foreign to v-sim-common and v-sim-doc
   * Add a Comment= entry in v_sim.desktop
   * Fix the overrides importation of Python module (Closes: #896226)
Checksums-Sha1:
 07c988d44541109f945aa7c8b5114531037fb86f 2535 v-sim_3.7.2-6.dsc
 a1cd807733ccf445d75a7aaca3df15b1b3d47b25 13792 v-sim_3.7.2-6.debian.tar.xz
 df1bcec0727ac31646a59098c72b20fa8a098d6a 59736 
gir1.2-v-sim-1.0_3.7.2-6_amd64.deb
 b529122bca3daf47b08b20a76a3c205f55f0e0dd 25176 python-v-sim_3.7.2-6_all.deb
 3e7fbce5133a53d263a3489f20de975a7849288f 229576 v-sim-common_3.7.2-6_all.deb
 e704f127910f107dd1115479daceeadfc2f12ab0 1965076 v-sim-dbgsym_3.7.2-6_amd64.deb
 e0d19fb3ebb601c20288942564b38526d431eecc 411308 v-sim-doc_3.7.2-6_all.deb
 dceb46730e82e5f12bb622e146c76a6e18d3c53d 227152 
v-sim-plugins-dbgsym_3.7.2-6_amd64.deb
 1430de96dc6a25cf4a995166379d27152009d891 1083548 
v-sim-plugins_3.7.2-6_amd64.deb
 365377e8620e0007b28ee381ab1cb4fd08f10f91 18487 v-sim_3.7.2-6_amd64.buildinfo
 2093b1393a7894e57685c487ec997540d34a6db5 671168 v-sim_3.7.2-6_amd64.deb
Checksums-Sha256:
 53845f816f823d98ffba1bc0dd634898ba9b0413b3d14a0660914edbbd5ef9cf 2535 
v-sim_3.7.2-6.dsc
 661e0ade9676adf672f3d6df718ea3f89c25c20e76748d1d04a4b0daf3abcdae 13792 
v-sim_3.7.2-6.debian.tar.xz
 8b8c6ee7042b6f2d0aad947d824b9be9f23da7fdd5fc1528098681ebafddb82c 59736 
gir1.2-v-sim-1.0_3.7.2-6_amd64.deb
 2a396cb203842850f82441bc79781908df0b0d05ad225ef462ab939a2aa13d83 25176 
python-v-sim_3.7.2-6_all.deb
 dc21a20e8878660d863ed848ceacfd6452f9379b224808ae0ed646295cc2ebe4 229576 
v-sim-common_3.7.2-6_all.deb
 5c6a3923eee28c86f1421f384ac2b15a06adc56480e46dff90653aa9bdd12308 1965076 
v-sim-dbgsym_3.7.2-6_amd64.deb
 555cead8ab73aa80ec73bf2a23473f2fe791a7e9e

Processed: closing 889053

[Debian Bug Tracking System]

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

> close 889053 1.5.19-1
Bug #889053 [gir1.2-ibus-1.0] [gir1.2-ibus-1.0] Fails to install Multi-Arch
Bug #897363 [gir1.2-ibus-1.0] gir1.2-ibus-1.0:amd64: Unqualified 
gir1.2-ibus-1.0 package name in prerm
Bug #900077 [gir1.2-ibus-1.0] gir1.2-ibus-1.0: co-installation of amd64 and 
i386 packages will cause non-recoverable error
Bug #905624 [gir1.2-ibus-1.0] Impossible to configure gir1.2-ibus-1.0:amd64, 
gir1.2-ibus-1.0:i386, libibus-1.0-dev:i386 and libsdl2-dev:i386
Ignoring request to alter fixed versions of bug #889053 to the same values 
previously set
Ignoring request to alter fixed versions of bug #897363 to the same values 
previously set
Ignoring request to alter fixed versions of bug #900077 to the same values 
previously set
Ignoring request to alter fixed versions of bug #905624 to the same values 
previously set
Bug #889053 [gir1.2-ibus-1.0] [gir1.2-ibus-1.0] Fails to install Multi-Arch
Bug #897363 [gir1.2-ibus-1.0] gir1.2-ibus-1.0:amd64: Unqualified 
gir1.2-ibus-1.0 package name in prerm
Bug #900077 [gir1.2-ibus-1.0] gir1.2-ibus-1.0: co-installation of amd64 and 
i386 packages will cause non-recoverable error
Bug #905624 [gir1.2-ibus-1.0] Impossible to configure gir1.2-ibus-1.0:amd64, 
gir1.2-ibus-1.0:i386, libibus-1.0-dev:i386 and libsdl2-dev:i386
Marked Bug as done
Marked Bug as done
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#906514: marked as done (xfce4-taskmanager: FTBFS in buster/sid (cp: cannot create regular file 'm4/intltool.m4': No such file or directory))

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 09:35:17 +
with message-id 
and subject line Bug#906514: fixed in xfce4-taskmanager 1.2.1-1
has caused the Debian Bug report #906514,
regarding xfce4-taskmanager: FTBFS in buster/sid (cp: cannot create regular 
file 'm4/intltool.m4': No such file or directory)
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.)


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

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --parallel --with autoreconf
   dh_update_autotools_config -a -O--parallel
   dh_autoreconf -a -O--parallel
xdt-autogen: It is recommended to use IT_PROG_INTLTOOL([0.35.0])
 in your configure.ac file and remove AC_PROG_INTLTOOL

 See http://bugzilla.xfce.org/show_bug.cgi?id=8930 for
 more information.

Preparing package directory /<>...
Running glib-gettextize --force --copy...
Copying file po/Makefile.in.in

Please add the files
  codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4
  progtest.m4
from the /usr/share/aclocal directory to your autoconf macro directory
or directly to your aclocal.m4 file.
You will also need config.guess and config.sub, which you can get from
ftp://ftp.gnu.org/pub/gnu/config/.

Running intltoolize --automake --copy --force
cp: cannot create regular file 'm4/intltool.m4': No such file or directory
intltoolize: cannot copy '/usr/share/aclocal/intltool.m4' to 'm4/intltool.m4'
dh_autoreconf: xdt-autogen returned exit code 1
make: *** [debian/rules:14: build-arch] Error 25
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

where you can get a full build log if you need it.

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: xfce4-taskmanager
Source-Version: 1.2.1-1

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfce4-taskmanager 
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, 27 Aug 2018 11:28:51 +0200
Source: xfce4-taskmanager
Binary: xfce4-taskmanager
Architecture: source
Version: 1.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 xfce4-taskmanager - process manager for the Xfce4 Desktop Environment
Closes: 899746 906514
Changes:
 xfce4-taskmanager (1.2.1-1) unstable; urgency=medium
 .
   * Moved the package to git on salsa.debian.org
   * Updated the maintainer address to debian-x...@lists.debian.org
 closes: #899746
   * d/gbp.conf added, following DEP-14
   * New upstream version 1.2.1
   * d/p/01_configure-kfreebsd refreshed for new upstream
   * d/rules: create m4 directory before running autoreconf
 closes: #906514
   * d/control: run wrap-and-sort
   * d/control: add build-dep on libxmu-dev
   * d/control: update standards version to 4.2.0
   * d/control: drop Lionel from Uploaders, thanks for the work
   * d/control: drop useless versions from build-deps
   * bump dh compat to 10
Checksums-Sha1:
 79136b2685634e4d9d506d56dee7ebbc81d029cf 1796 xfce4-taskmanager_1.2.1-1.dsc
 6b8292680fc3fd08b33c83c90e85bc0c8a825346 394704 
xfce4-taskmanager_1.2.1.orig.tar.bz2
 4bbd348438f4621422411fcd58c168b21fdd281c 4712 
xfce4-taskmanager_

Bug#899746: marked as done (xfce4-taskmanager: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 09:35:17 +
with message-id 
and subject line Bug#899746: fixed in xfce4-taskmanager 1.2.1-1
has caused the Debian Bug report #899746,
regarding xfce4-taskmanager: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of xfce4-taskmanager,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xfce4-taskmanager
Source-Version: 1.2.1-1

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

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

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfce4-taskmanager 
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, 27 Aug 2018 11:28:51 +0200
Source: xfce4-taskmanager
Binary: xfce4-taskmanager
Architecture: source
Version: 1.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 xfce4-taskmanager - process manager for the Xfce4 Desktop Environment
Closes: 899746 906514
Changes:
 xfce4-taskmanager (1.2.1-1) unstable; urgency=medium
 .
   * Moved the package to git on salsa.debian.org
   * Updated the maintainer address to debian-x...@lists.debian.org
 closes: #899746
   * d/gbp.conf added, following DEP-14
   * New upstream version 1.2.1
   * d/p/01_configure-kfreebsd refreshed for new upstream
   * d/rules: create m4 directory before running autoreconf
 closes: #906514
   * d/control: run wrap-and-sort
   * d/control: add build-dep on libxmu-dev
   * d/control: update standards version to 4.2.0
   * d/control: drop Lionel from Uploaders, thanks for the work
   * d/control: drop useless versions from build-deps
   * bump dh compat to 10
Checksums-Sha1:
 79136b2685634e4d9d506d56dee7ebbc81d029cf 1796 xfce4-taskmanager_1.2.1-1.dsc
 6b8292680fc3fd08b33c83c90e85bc0c8a825346 394704 
xfce4-taskmanager_1.2.1.orig.ta

Bug#889053: closing 889053

[Laurent Bigonville]

close 889053 1.5.19-1
thanks

Hi,

I can confirm that I can install gir1.2-ibus-1.0 for multiple architectures now

This is probably working now because the pycompile is not called anymore
because the explicit dependency against python is gone

Processed: tagging 889053

[Debian Bug Tracking System]

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

> tags 889053 + stretch
Bug #889053 {Done: Laurent Bigonville } [gir1.2-ibus-1.0] 
[gir1.2-ibus-1.0] Fails to install Multi-Arch
Bug #897363 {Done: Laurent Bigonville } [gir1.2-ibus-1.0] 
gir1.2-ibus-1.0:amd64: Unqualified gir1.2-ibus-1.0 package name in prerm
Bug #900077 {Done: Laurent Bigonville } [gir1.2-ibus-1.0] 
gir1.2-ibus-1.0: co-installation of amd64 and i386 packages will cause 
non-recoverable error
Bug #905624 {Done: Laurent Bigonville } [gir1.2-ibus-1.0] 
Impossible to configure gir1.2-ibus-1.0:amd64, gir1.2-ibus-1.0:i386, 
libibus-1.0-dev:i386 and libsdl2-dev:i386
Added tag(s) stretch.
Added tag(s) stretch.
Added tag(s) stretch.
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Bug#867912: marked as done (fusiondirectory: unusable after upgrade from jessie to stretch)

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 10:00:25 +
with message-id 
and subject line Bug#867912: fixed in fusiondirectory 1.2.1-1
has caused the Debian Bug report #867912,
regarding fusiondirectory: unusable after upgrade from jessie to stretch
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.)


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

Dear Maintainer,

after upgrading my fusiondirectory installation from jessie (1.0.8.2-5)
to stretch (1.0.19-1) the package has become practically unusable.
(that's after adding workarounds for #854398 and ).

e.g. trying to edit anything, i get the following on saving:
> LDAP operation failed!
>
> Object: cn=config,ou=fusiondirectory,dc=example,dc=com
>
> Error: Undefined attribute type - attribute: fdHttpHeaderAuthHeaderName
> (fdHttpHeaderAuthHeaderName: attribute type undefined, while operating
> on 'cn=config,ou=fusiondirectory,dc=iem,dc=at' using LDAP server
> 'ldaps://ldap.example.com:636')o

followed by:
> Error when saving:
> The entry cn=config,ou=fusiondirectory,dc=example,dc=com is not existing 

OR trying to manage my users (by clicking on the "Users" menu), i get
two pages of PHP code thrown in my face:
> ip) { logging::log('security', 'login', '', array(), 'main.php called
> with session which has a changed IP address.'); header ('Location:
> index.php?signout=1&message=newip'); exit; } $config =
> session::global_get('config'); /* If SSL is forced, just forward to the
> SSL enabled site */ if (($config->get_cfg_value('forcessl') == 'TRUE')
> && ($ssl != '')) { header ("Location: $ssl"); exit; }
> timezone::setDefaultTimezoneFromConfig(); /* Check for invalid sessions
> */ if (session::global_get('_LAST_PAGE_REQUEST') != '') { /* check
> FusionDirectory.conf for defined session lifetime */ $max_life =
> $config->get_cfg_value('sessionLifetime', 60 * 60 * 2); if ($max_life >
> 0) { /* get time difference between last page reload */ $request_time =
> (time() - session::global_get('_LAST_PAGE_REQUEST')); /* If page wasn't
> reloaded for more than max_life seconds * kill session */ if
> ($request_time > $max_life) { session::destroy();
> logging::log('security', 'login', '', array(), 'main.php called with
> expired session - logging out'); header ('Location:
> index.php?signout=1&message=expired'); exit; } } }
> session::global_set('_LAST_PAGE_REQUEST', time()); @DEBUG (DEBUG_CONFIG,
> __LINE__, __FUNCTION__, __FILE__, $config->data, "config"); /* Set
> template compile directory */ $smarty->compile_dir =
> $config->get_cfg_value("templateCompileDirectory", SPOOL_DIR); /* Preset
> current main base */ if (!session::global_is_set('CurrentMainBase')) {
> session::global_set('CurrentMainBase', get_base_from_people($ui->dn)); }
> initLanguage(); /* Prepare plugin list */ $plist = load_plist(); /*
> Check for register globals */ if (isset($global_check) && 

no warning has been emitted when I upgraded from jessie to stretch.
esp. no NEWS have indicated that anything could possibly go wrong.

there are some upstream notes in /usr/share/doc/fusiondirectory/docs/ about
upgrading, indicating that this will require quite a lot of
schema-changes and similar.
however, the upstream notes are very incremental (e.g. 1.0.8.1 ->
1.0.8.2) and do not make it easy to upgrade from jessie to stretch.

since fusiondirectory is a package to manage core infrastructure (like
user databases and networking devices), extra should be taken to allow
smooth upgrades between releases.

please fix this for the next point release (and please provide some
instructions for the 9.0-users on how to handle their broken
installations)

PS: thanks for packaging fusiondirectory!


-- System Information:
Debian Release: 9.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fusiondirectory depends on:
ii  apache2 [httpd] 2.4.25-3+deb9u1
ii  fusiondirectory-smarty3-acl-render  1.0.19-1
ii  gettext 0.19.8.1-2
ii  javascript-common   11
ii  libarchive-extract-perl 0.80-1
ii  libcrypt-cbc-perl   2.33-1
ii  libfile-copy-recursive-perl 0.

Bug#897729: marked as done (cpp-hocon: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 10:00:11 +
with message-id 
and subject line Bug#897729: fixed in cpp-hocon 0.1.7-1
has caused the Debian Bug report #897729,
regarding cpp-hocon: ftbfs with GCC-8
to be marked as done.

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

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


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

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

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

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/cpp-hocon_0.1.6-1_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
[ 50%] Building CXX object 
lib/CMakeFiles/libprojectsrc.dir/src/config_render_options.cc.o
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/c++  
-DBOOST_ALL_DYN_LINK -DBOOST_LOG_WITHOUT_WCHAR_T -DBOOST_SYSTEM_NO_DEPRECATED 
-DLEATHERMAN_I18N -DLEATHERMAN_LOGGING_NAMESPACE=\"puppetlabs.cpp-hocon\" 
-DLEATHERMAN_USE_LOCALES 
-DPROJECT_DIR=\"/<>/obj-x86_64-linux-gnu\" 
-DPROJECT_NAME=\"cpp-hocon\" -I/<>/lib/inc 
-I/<>/../vendor/nowide/include  -Wextra -std=c++11 -Wall -Werror 
-Wno-unused-parameter -Wno-unused-local-typedefs -Wno-unknown-pragmas 
-Wno-missing-field-initializers -Wno-maybe-uninitialized -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC   -o 
CMakeFiles/libprojectsrc.dir/src/config_render_options.cc.o -c 
/<>/lib/src/config_render_options.cc
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 52%] Building CXX object 
lib/CMakeFiles/libprojectsrc.dir/src/config_document_parser.cc.o
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/c++  
-DBOOST_ALL_DYN_LINK -DBOOST_LOG_WITHOUT_WCHAR_T -DBOOST_SYSTEM_NO_DEPRECATED 
-DLEATHERMAN_I18N -DLEATHERMAN_LOGGING_NAMESPACE=\"puppetlabs.cpp-hocon\" 
-DLEATHERMAN_USE_LOCALES 
-DPROJECT_DIR=\"/<>/obj-x86_64-linux-gnu\" 
-DPROJECT_NAME=\"cpp-hocon\" -I/<>/lib/inc 
-I/<>/../vendor/nowide/include  -Wextra -std=c++11 -Wall -Werror 
-Wno-unused-parameter -Wno-unused-local-typedefs -Wno-unknown-pragmas 
-Wno-missing-field-initializers -Wno-maybe-uninitialized -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC   -o 
CMakeFiles/libprojectsrc.dir/src/config_util.cc.o -c 
/<>/lib/src/config_util.cc
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 53%] Building CXX object 
lib/CMakeFiles/libprojectsrc.dir/src/config_document_factory.cc.o
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/c++  
-DBOOST_ALL_DYN_LINK -DBOOST_LOG_WITHOUT_WCHAR_T -DBOOST_SYSTEM_NO_DEPRECATED 
-DLEATHERMAN_I18N -DLEATHERMAN_LOGGING_NAMESPACE=\"puppetlabs.cpp-hocon\" 
-DLEATHERMAN_USE_LOCALES 
-DPROJECT_DIR=\"/<>/obj-x86_64-linux-gnu\" 
-DPROJECT_NAME=\"cpp-hocon\" -I/<>/lib/inc 
-I/<>/../vendor/nowide/include  -Wextra -std=c++11 -Wall -Werror 
-Wno-unused-parameter -Wno-unused-local-typedefs -Wno-unknown-pragmas 
-Wno-missing-field-initializers -Wno-maybe-uninitialized -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC   -o 
CMakeFiles/libprojectsrc.dir/src

Bug#906557: marked as done (ratpoison: FTBFS in buster/sid (makeinfo: command not found))

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 10:00:28 +
with message-id 
and subject line Bug#906775: fixed in hamlib 3.2-1
has caused the Debian Bug report #906775,
regarding ratpoison: FTBFS in buster/sid (makeinfo: command not found)
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.)


-- 
906775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ratpoison
Version: 1.4.8-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh_testdir
autoreconf -i
aclocal: installing 'm4/pkg.m4' from '/usr/share/aclocal/pkg.m4'
configure.ac:114: installing 'build-aux/compile'
configure.ac:24: installing 'build-aux/install-sh'
configure.ac:24: installing 'build-aux/missing'
doc/Makefile.am:20: installing 'build-aux/mdate-sh'
doc/Makefile.am:20: installing 'build-aux/texinfo.tex'
src/Makefile.am: installing 'build-aux/depcomp'
touch autoreconf-stamp
dh_testdir
./configure --build x86_64-linux-gnu \
--prefix=/usr --sysconfdir=/etc \

[... snipped ...]

make[1]: Entering directory '/<>'
Making install in src
make[2]: Entering directory '/<>/src'
make[3]: Entering directory '/<>/src'
 /bin/mkdir -p '/<>/debian/ratpoison/usr/bin'
  /usr/bin/install -c ratpoison '/<>/debian/ratpoison/usr/bin'
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>/src'
make[2]: Leaving directory '/<>/src'
Making install in doc
make[2]: Entering directory '/<>/doc'
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
rm -rf $backupdir && mkdir $backupdir && \
if (/bin/bash /<>/build-aux/missing makeinfo --version) >/dev/null 
2>&1; then \
  for f in ratpoison.info ratpoison.info-[0-9] ratpoison.info-[0-9][0-9] 
ratpoison.i[0-9] ratpoison.i[0-9][0-9]; do \
if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
  done; \
else :; fi && \
cd "$am__cwd"; \
if /bin/bash /<>/build-aux/missing makeinfo   -I . \
 -o ratpoison.info ratpoison.texi; \
then \
  rc=0; \
  CDPATH="${ZSH_VERSION+.}:" && cd .; \
else \
  rc=$?; \
  CDPATH="${ZSH_VERSION+.}:" && cd . && \
  $restore $backupdir/* `echo "./ratpoison.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
/<>/build-aux/missing: line 81: makeinfo: command not found
WARNING: 'makeinfo' is missing on your system.
 You should only need it if you modified a '.texi' file, or
 any other file indirectly affecting the aspect of the manual.
 You might want to install the Texinfo package:
 
 The spurious makeinfo call might also be the consequence of
 using a buggy 'make' (AIX, DU, IRIX), in which case you might
 want to install GNU make:
 
make[2]: *** [Makefile:358: ratpoison.info] Error 127
make[2]: Leaving directory '/<>/doc'
make[1]: *** [Makefile:413: install-recursive] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:105: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

where you can get a full build log if you need it.

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: hamlib
Source-Version: 3.2-1

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

Debian distribution maintenance software
pp.
Enrico Rossi  (supplier of updated hamlib 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 SIGNE

Bug#906426: marked as done (gnuchess: FTBFS: makeinfo: command not found (missing build-dependency on texinfo))

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 10:00:28 +
with message-id 
and subject line Bug#906775: fixed in hamlib 3.2-1
has caused the Debian Bug report #906775,
regarding gnuchess: FTBFS: makeinfo: command not found (missing 
build-dependency on texinfo)
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.)


-- 
906775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnuchess
Version: 6.2.5-1
Severity: serious
Tags: ftbfs, patch
Justification: fails to build from source (but built successfully in the past)

Hi,

Building gnuchess in a current sid chroot fails with:


Making check in doc
make[2]: Entering directory '/<>/doc'
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
rm -rf $backupdir && mkdir $backupdir && \
if (/bin/bash /<>/missing makeinfo --version) >/dev/null 2>&1; 
then \
  for f in gnuchess.info gnuchess.info-[0-9] gnuchess.info-[0-9][0-9] gnuchess.i
[0-9] gnuchess.i[0-9][0-9]; do \
if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
  done; \
else :; fi && \
cd "$am__cwd"; \
if /bin/bash /<>/missing makeinfo   -I . \
 -o gnuchess.info gnuchess.texi; \
then \
  rc=0; \
  CDPATH="${ZSH_VERSION+.}:" && cd .; \
else \
  rc=$?; \
  CDPATH="${ZSH_VERSION+.}:" && cd . && \
  $restore $backupdir/* `echo "./gnuchess.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
/<>/missing: line 81: makeinfo: command not found
WARNING: 'makeinfo' is missing on your system.
 You should only need it if you modified a '.texi' file, or
 any other file indirectly affecting the aspect of the manual.
 You might want to install the Texinfo package:
 
 The spurious makeinfo call might also be the consequence of
 using a buggy 'make' (AIX, DU, IRIX), in which case you might
 want to install GNU make:
 
make[2]: *** [Makefile:382: gnuchess.info] Error 127


Same is observed on 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnuchess.html

Adding 'texinfo' to the build dependencies fixes the problem.

Complete build log attached.


-- dam


gnuchess_amd64-2018-08-17T10:32:23Z.build.xz
Description: application/xz
--- End Message ---
--- Begin Message ---
Source: hamlib
Source-Version: 3.2-1

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

Debian distribution maintenance software
pp.
Enrico Rossi  (supplier of updated hamlib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 23 Aug 2018 15:27:16 +0200
Source: hamlib
Binary: libhamlib2 libhamlib2++c2 libhamlib-dev libhamlib++-dev libhamlib2-perl 
libhamlib2-tcl python-libhamlib2 python3-libhamlib2 libhamlib-utils 
libhamlib-doc lua-hamlib2
Architecture: source amd64 all
Version: 3.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian Hamradio Maintainers 
Changed-By: Enrico Rossi 
Description:
 libhamlib++-dev - Development C++ library to control radio transceivers and 
receive
 libhamlib-dev - Development library to control radio transceivers and receivers
 libhamlib-doc - Documentation for the hamlib radio control library
 libhamlib-utils - Utilities to support the hamlib radio control library
 libhamlib2 - Run-time library to control radio transceivers and receivers
 libhamlib2++c2 - Run-time C++ library to control radio transceivers and 
receivers
 libhamlib2-perl - Run-time perl library to control radio transceivers and 
receivers
 libhamlib2-tcl - Run-time Tcl library to control radio transceivers and 
receivers
 lua-hamlib2 - Run-time Lua library to control radio transceivers and receivers
 python-libhamlib2 - Run-time Python library to control radio transceivers and 
receive
 python3-libhamlib2 - Run-time Python3 library to control radio transceivers 
and receiv
Closes: 906775
Ch

Bug#906775: marked as done (hamlib: FTBFS in buster/sid (makeinfo: command not found))

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 10:00:28 +
with message-id 
and subject line Bug#906775: fixed in hamlib 3.2-1
has caused the Debian Bug report #906775,
regarding hamlib: FTBFS in buster/sid (makeinfo: command not found)
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.)


-- 
906775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hamlib
Version: 3.1-8
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh_testdir
dh_autoreconf
aclocal: overwriting 'macros/libtool.m4' with '/usr/share/aclocal/libtool.m4'
aclocal: overwriting 'macros/ltoptions.m4' with 
'/usr/share/aclocal/ltoptions.m4'

[... snipped ...]

libtool: warning: '../src/libhamlib.la' has not been installed in '/usr/lib'
libtool: install: /usr/bin/install -c .libs/rotctld 
/<>/debian/tmp/usr/bin/rotctld
 /bin/mkdir -p '/<>/debian/tmp/usr/share/man/man1'
 /usr/bin/install -c -m 644 ../../tests/rigctl.1 ../../tests/rigctld.1 
../../tests/rigmem.1 ../../tests/rigsmtr.1 ../../tests/rigswr.1 
../../tests/rotctl.1 ../../tests/rotctld.1 
'/<>/debian/tmp/usr/share/man/man1'
make[3]: Leaving directory '/<>/build-2.7/tests'
make[2]: Leaving directory '/<>/build-2.7/tests'
Making install in doc
make[2]: Entering directory '/<>/build-2.7/doc'
Updating ../../doc/version.texi
make[3]: Entering directory '/<>/build-2.7/doc'
make[3]: Nothing to be done for 'install-exec-am'.
rm -rf hamlib.htp
if /bin/bash /<>/build-aux/missing makeinfo --html --no-headers 
--no-split  -I ../../doc \
 -o hamlib.htp ../../doc/hamlib.texi; \
then \
  rm -rf hamlib.html && mv hamlib.htp hamlib.html; \
else \
  rm -rf hamlib.htp; exit 1; \
fi
/<>/build-aux/missing: line 81: makeinfo: command not found
WARNING: 'makeinfo' is missing on your system.
 You should only need it if you modified a '.texi' file, or
 any other file indirectly affecting the aspect of the manual.
 You might want to install the Texinfo package:
 
 The spurious makeinfo call might also be the consequence of
 using a buggy 'make' (AIX, DU, IRIX), in which case you might
 want to install GNU make:
 
make[3]: *** [Makefile:499: hamlib.html] Error 1
make[3]: Leaving directory '/<>/build-2.7/doc'
make[2]: *** [Makefile:700: install-am] Error 2
make[2]: Leaving directory '/<>/build-2.7/doc'
make[1]: *** [Makefile:577: install-recursive] Error 1
make[1]: Leaving directory '/<>/build-2.7'
make: *** [debian/rules:64: install-base] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

where you can get a full build log if you need it.

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: hamlib
Source-Version: 3.2-1

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

Debian distribution maintenance software
pp.
Enrico Rossi  (supplier of updated hamlib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 23 Aug 2018 15:27:16 +0200
Source: hamlib
Binary: libhamlib2 libhamlib2++c2 libhamlib-dev libhamlib++-dev libhamlib2-perl 
libhamlib2-tcl python-libhamlib2 python3-libhamlib2 libhamlib-utils 
libhamlib-doc lua-hamlib2
Architecture: source amd64 all
Version: 3.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian Hamradio Maintainers 
Changed-By: Enrico Rossi 
Descr

Bug#906774: marked as done (dico: FTBFS in buster/sid (makeinfo: command not found))

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 10:00:28 +
with message-id 
and subject line Bug#906775: fixed in hamlib 3.2-1
has caused the Debian Bug report #906775,
regarding dico: FTBFS in buster/sid (makeinfo: command not found)
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.)


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

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2
   dh_update_autotools_config -i
   dh_autoreconf -i
Copying file m4/glibc2.m4
Copying file m4/intdiv0.m4

[... snipped ...]

Making check in doc
make[3]: Entering directory '/<>/doc'
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
rm -rf $backupdir && mkdir $backupdir && \
if (/bin/bash /<>/build-aux/missing makeinfo --version) >/dev/null 
2>&1; then \
  for f in dico.info dico.info-[0-9] dico.info-[0-9][0-9] dico.i[0-9] 
dico.i[0-9][0-9]; do \
if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
  done; \
else :; fi && \
cd "$am__cwd"; \
if /bin/bash /<>/build-aux/missing makeinfo -I ../imprimatur -D 
DISTRIB  -I . \
 -o dico.info dico.texi; \
then \
  rc=0; \
  CDPATH="${ZSH_VERSION+.}:" && cd .; \
else \
  rc=$?; \
  CDPATH="${ZSH_VERSION+.}:" && cd . && \
  $restore $backupdir/* `echo "./dico.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
/<>/build-aux/missing: line 81: makeinfo: command not found
WARNING: 'makeinfo' is missing on your system.
 You should only need it if you modified a '.texi' file, or
 any other file indirectly affecting the aspect of the manual.
 You might want to install the Texinfo package:
 
 The spurious makeinfo call might also be the consequence of
 using a buggy 'make' (AIX, DU, IRIX), in which case you might
 want to install GNU make:
 
make[3]: *** [Makefile:1263: dico.info] Error 127
make[3]: Leaving directory '/<>/doc'
make[2]: *** [Makefile:1294: check-recursive] Error 1
make[2]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:60: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:14: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

where you can get a full build log if you need it.

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: hamlib
Source-Version: 3.2-1

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

Debian distribution maintenance software
pp.
Enrico Rossi  (supplier of updated hamlib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 23 Aug 2018 15:27:16 +0200
Source: hamlib
Binary: libhamlib2 libhamlib2++c2 libhamlib-dev libhamlib++-dev libhamlib2-perl 
libhamlib2-tcl python-libhamlib2 python3-libhamlib2 libhamlib-utils 
libhamlib-doc lua-hamlib2
Architecture: source amd64 all
Version: 3.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian Hamradio Maintainers 
Changed-By: Enrico Rossi 
Description:
 libhamlib++-dev - Development C++ library to control radio transceivers and 
receive
 libhamlib-dev - Development library to control radio transceivers and receivers
 libhamlib-doc - Document

Bug#906778: marked as done (guile-gnome-platform: FTBFS in buster/sid (makeinfo: command not found))

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 10:00:28 +
with message-id 
and subject line Bug#906775: fixed in hamlib 3.2-1
has caused the Debian Bug report #906775,
regarding guile-gnome-platform: FTBFS in buster/sid (makeinfo: command not 
found)
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.)


-- 
906775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:guile-gnome-platform
Version: 2.16.4-5
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
test -x debian/rules
mkdir -p "."
CDBS WARNING:DEB_DH_INSTALL_ARGS is deprecated since 0.4.85
set -e;   mv ./build-aux/config.guess ./build-aux/config.guess.cdbs-orig; cp 
--remove-destination /usr/share/misc/config.guess ./build-aux/config.guess;
set -e;   mv ./build-aux/config.sub ./build-aux/config.sub.cdbs-orig; cp 
--remove-destination /usr/share/misc/config.sub ./build-aux/config.sub;
dh_autoreconf 
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'

[... snipped ...]

Making check in glib
make[4]: Entering directory '/<>/glib/doc/glib'
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
rm -rf $backupdir && mkdir $backupdir && \
if (/bin/bash /<>/build-aux/missing makeinfo --version) >/dev/null 
2>&1; then \
  for f in guile-gnome-glib.info guile-gnome-glib.info-[0-9] 
guile-gnome-glib.info-[0-9][0-9] guile-gnome-glib.i[0-9] 
guile-gnome-glib.i[0-9][0-9]; do \
if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
  done; \
else :; fi && \
cd "$am__cwd"; \
if /bin/bash /<>/build-aux/missing makeinfo   -I . \
 -o guile-gnome-glib.info guile-gnome-glib.texi; \
then \
  rc=0; \
  CDPATH="${ZSH_VERSION+.}:" && cd .; \
else \
  rc=$?; \
  CDPATH="${ZSH_VERSION+.}:" && cd . && \
  $restore $backupdir/* `echo "./guile-gnome-glib.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
/<>/build-aux/missing: line 81: makeinfo: command not found
WARNING: 'makeinfo' is missing on your system.
 You should only need it if you modified a '.texi' file, or
 any other file indirectly affecting the aspect of the manual.
 You might want to install the Texinfo package:
 
 The spurious makeinfo call might also be the consequence of
 using a buggy 'make' (AIX, DU, IRIX), in which case you might
 want to install GNU make:
 
make[4]: *** [Makefile:470: guile-gnome-glib.info] Error 127
make[4]: Leaving directory '/<>/glib/doc/glib'
make[3]: *** [Makefile:399: check-recursive] Error 1
make[3]: Leaving directory '/<>/glib/doc'
make[2]: *** [Makefile:513: check-recursive] Error 1
make[2]: Leaving directory '/<>/glib'
make[1]: *** [Makefile:457: check-recursive] Error 1
make[1]: Leaving directory '/<>'
make: *** [/usr/share/cdbs/1/class/makefile.mk:113: 
debian/stamp-makefile-check] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/guile-gnome-platform.html

where you can get a full build log if you need it.

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: hamlib
Source-Version: 3.2-1

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

Debian distribution maintenance software
pp.
Enrico Rossi  (supplier of updated hamlib 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 MESSA

Bug#906790: marked as done (libtasn1-6 FTBFS during arch-only: missing makeinfo)

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 10:00:28 +
with message-id 
and subject line Bug#906775: fixed in hamlib 3.2-1
has caused the Debian Bug report #906775,
regarding libtasn1-6 FTBFS during arch-only: missing makeinfo
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.)


-- 
906775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtasn1-6
Version: 4.13-3
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap

Doing an arch-only build of libtasn1-6 on amd64 fails. A build log ends
with:

| make[3]: Entering directory '/<>/doc'
| restore=: && backupdir=".am$$" && \
| am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
| rm -rf $backupdir && mkdir $backupdir && \
| if (/bin/bash /<>/build-aux/missing makeinfo --version) 
>/dev/null 2>&1; then \
|   for f in libtasn1.info libtasn1.info-[0-9] libtasn1.info-[0-9][0-9] 
libtasn1.i[0-9] libtasn1.i[0-9][0-9]; do \
| if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
|   done; \
| else :; fi && \
| cd "$am__cwd"; \
| if /bin/bash /<>/build-aux/missing makeinfo -I ../doc  -I . \
|  -o libtasn1.info libtasn1.texi; \
| then \
|   rc=0; \
|   CDPATH="${ZSH_VERSION+.}:" && cd .; \
| else \
|   rc=$?; \
|   CDPATH="${ZSH_VERSION+.}:" && cd . && \
|   $restore $backupdir/* `echo "./libtasn1.info" | sed 's|[^/]*$||'`; \
| fi; \
| rm -rf $backupdir; exit $rc
| /<>/build-aux/missing: line 81: makeinfo: command not found
| WARNING: 'makeinfo' is missing on your system.
|  You should only need it if you modified a '.texi' file, or
|  any other file indirectly affecting the aspect of the manual.
|  You might want to install the Texinfo package:
|  
|  The spurious makeinfo call might also be the consequence of
|  using a buggy 'make' (AIX, DU, IRIX), in which case you might
|  want to install GNU make:
|  
| make[3]: *** [Makefile:1097: libtasn1.info] Error 127
| make[3]: Leaving directory '/<>/doc'
| make[2]: *** [Makefile:1350: check-recursive] Error 1
| make[2]: Leaving directory '/<>/doc'
| make[1]: *** [Makefile:1027: check-recursive] Error 1
| make[1]: Leaving directory '/<>'
| dh_auto_test: make -j8 check VERBOSE=1 returned exit code 2
| make: *** [debian/rules:51: binary-arch] Error 2
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

A full build work, which is why reproducible doesn't see this issue. The
installation set does not include the texinfo package, which contains
makeinfo, and texinfo is not requested by Build-Depends. The earlier
builds on the buildds did not attempt to run makeinfo. Possibly this is
related to updating the version of autoconf?

Helmut
--- End Message ---
--- Begin Message ---
Source: hamlib
Source-Version: 3.2-1

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

Debian distribution maintenance software
pp.
Enrico Rossi  (supplier of updated hamlib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 23 Aug 2018 15:27:16 +0200
Source: hamlib
Binary: libhamlib2 libhamlib2++c2 libhamlib-dev libhamlib++-dev libhamlib2-perl 
libhamlib2-tcl python-libhamlib2 python3-libhamlib2 libhamlib-utils 
libhamlib-doc lua-hamlib2
Architecture: source amd64 all
Version: 3.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian Hamradio Maintainers 
Changed-By: Enrico Rossi 
Description:
 libhamlib++-dev - Development C++ library to control radio transceivers and 
receive
 libhamlib-dev - Development library to control radio transceivers and receivers
 libhamlib-doc - Documentation for the hamlib radio control library
 libhamlib-utils - Utilities to support the hamlib radio control library
 libhamlib2 - Run-time library to control radio transceivers and receivers
 libhamlib2++c2 - Run-time C++ library to control radio transceivers and 
receivers
 libhamlib2-perl - Run-time perl l

Processed: reopening 906426

[Debian Bug Tracking System]

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

> reopen 906426
Bug #906426 {Done: Enrico Rossi } [automake] gnuchess: 
FTBFS: makeinfo: command not found (missing build-dependency on texinfo)
Bug #906557 {Done: Enrico Rossi } [automake] ratpoison: 
FTBFS in buster/sid (makeinfo: command not found)
Bug #906774 {Done: Enrico Rossi } [automake] dico: 
FTBFS in buster/sid (makeinfo: command not found)
Bug #906775 {Done: Enrico Rossi } [automake] hamlib: 
FTBFS in buster/sid (makeinfo: command not found)
Bug #906778 {Done: Enrico Rossi } [automake] 
guile-gnome-platform: FTBFS in buster/sid (makeinfo: command not found)
Bug #906790 {Done: Enrico Rossi } [automake] libtasn1-6 
FTBFS during arch-only: missing makeinfo
'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 hamlib/3.2-1.
No longer marked as fixed in versions hamlib/3.2-1.
No longer marked as fixed in versions hamlib/3.2-1.
No longer marked as fixed in versions hamlib/3.2-1.
No longer marked as fixed in versions hamlib/3.2-1.
No longer marked as fixed in versions hamlib/3.2-1.
> thanks
Stopping processing here.

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

Processed: tagging 889053

[Debian Bug Tracking System]

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

> tags 889053 + sid buster
Bug #889053 {Done: Laurent Bigonville } [gir1.2-ibus-1.0] 
[gir1.2-ibus-1.0] Fails to install Multi-Arch
Bug #897363 {Done: Laurent Bigonville } [gir1.2-ibus-1.0] 
gir1.2-ibus-1.0:amd64: Unqualified gir1.2-ibus-1.0 package name in prerm
Bug #900077 {Done: Laurent Bigonville } [gir1.2-ibus-1.0] 
gir1.2-ibus-1.0: co-installation of amd64 and i386 packages will cause 
non-recoverable error
Bug #905624 {Done: Laurent Bigonville } [gir1.2-ibus-1.0] 
Impossible to configure gir1.2-ibus-1.0:amd64, gir1.2-ibus-1.0:i386, 
libibus-1.0-dev:i386 and libsdl2-dev:i386
Added tag(s) sid and buster.
Added tag(s) sid and buster.
Added tag(s) buster and sid.
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#906168: pyside2: diff for NMU version 5.11.0-3.1

[Sophie Brun]

Hello,

Thanks for you help.

I planned to make an upload this week when I have corrected an other bug.

I will include your patch with the different fixes.

regards
Sophie

Processed: Missing dependencies are RC

[Debian Bug Tracking System]

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

> severity 906789 serious
Bug #906789 [yapf3] missing python3-pkg-resources dependency
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#906168: pyside2: diff for NMU version 5.11.0-3.1

[Adrian Bunk]

On Mon, Aug 27, 2018 at 12:13:04PM +0200, Sophie Brun wrote:
> Hello,

Hi Sophie,

> Thanks for you help.
> 
> I planned to make an upload this week when I have corrected an other bug.
> 
> I will include your patch with the different fixes.

thanks, sounds good to me.

I've cancelled my NMU.

> regards
> Sophie

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

Processed: found 906789 in 0.15.1-1

[Debian Bug Tracking System]

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

> found 906789 0.15.1-1
Bug #906789 [yapf3] missing python3-pkg-resources dependency
Marked as found in versions yapf/0.15.1-1.
> thanks
Stopping processing here.

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

Bug#904755: closed by Ana Custura (Bug#904755: fixed in yapf 0.22.0-2)

[Adrian Bunk]

Control: reopen -1

On Sun, Aug 12, 2018 at 03:39:08PM +, Debian Bug Tracking System wrote:
>...
>  yapf (0.22.0-2) unstable; urgency=medium
>  .
>* debian/control:
>- adds missing dependency on python-pkg-resources (Closes: #904755)
>...

This isn't fixed:

Package: yapf
Version: 0.22.0-5
Depends: python:any, python-yapf (= 0.22.0-5)

Package: yapf
Version: 0.22.0-2
Depends: python:any, python-yapf (= 0.22.0-2)


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

Processed: Re: Bug#904755 closed by Ana Custura (Bug#904755: fixed in yapf 0.22.0-2)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #904755 {Done: Ana Custura } [yapf] yapf: missing 
dependency on python-pkg-resources
'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 yapf/0.22.0-2.

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

Bug#907381: python-sphinx: missing dependency on python-stemmer

[Dmitry Shachnev]

Hi Adrian!

On Mon, Aug 27, 2018 at 11:20:20AM +0300, Adrian Bunk wrote:
> Package: python-sphinx
> Version: 1.7.7-1
> Severity: serious
> Control: affects -1 src:bzr
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/bzr.html
>
> ...
> Exception occurred:
>   File "/usr/lib/python2.7/dist-packages/sphinx/search/es.py", line 14, in 
> 
> import Stemmer
> ImportError: No module named Stemmer

I did not want to make pystemmer a hard dependency because this only affects
non-English documentation.

Indeed it is my bad that I did not check what packages will be broken with
this, but maybe you can estimate how many of them got broken now? If it is
< 10 source packages, I would rather file bugs on them.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Processed: Re: libpodofo: FTBFS in buster/sid (Error copying directory)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #906781 [src:libpodofo] libpodofo: FTBFS in buster/sid (Error copying 
directory)
Added tag(s) patch.

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

Bug#906781: libpodofo: FTBFS in buster/sid (Error copying directory)

[Juhani Numminen]

Control: tags -1 patch

On Mon, 20 Aug 2018 22:59:44 + Santiago Vila  wrote:
> Package: src:libpodofo
> Version: 0.9.5-9
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer:
> 
> I tried to build this package in buster but it failed:

> [... snipped ...]

> cd /<>/obj-x86_64-linux-gnu/test/TokenizerTest && /usr/bin/cmake 
> -E copy_directory /<>/test/TokenizerTest/objects 
> /<>/obj-x86_64-linux-gnu/test/TokenizerTest/objects
> Error copying directory from "/<>/test/TokenizerTest/objects" to 
> "/<>/obj-x86_64-linux-gnu/test/TokenizerTest/objects".

As far as I can tell, there is no directory test/TokenizerTest/objects in the
source package, and trying to copy it is possibly a copy-paste error.
This did not cause an error prior to CMake 3.12, as documented in the release 
notes:

https://cmake.org/cmake/help/v3.12/release/3.12.html
"The cmake(1) -E copy_directory tool now fails when the source directory does 
not exist. Previously it succeeded by creating an empty destination directory."

My patch removes the directory copying command from the CMakeLists.txt.


Regards,
Juhani
Description: Before CMake 3.12, trying to copy a non-existing dir didn't fail
Author: Juhani Numminen 
Bug-Debian: https://bugs.debian.org/906781
Last-Update: 2018-08-27

--- a/test/TokenizerTest/CMakeLists.txt
+++ b/test/TokenizerTest/CMakeLists.txt
@@ -2,10 +2,3 @@
 TARGET_LINK_LIBRARIES(TokenizerTest ${PODOFO_LIB} ${PODOFO_LIB_DEPENDS})
 SET_TARGET_PROPERTIES(TokenizerTest PROPERTIES COMPILE_FLAGS "${PODOFO_CFLAGS}")
 ADD_DEPENDENCIES(TokenizerTest ${PODOFO_DEPEND_TARGET})
-
-# Copy the test samples over to the build tree
-ADD_CUSTOM_COMMAND(
-TARGET TokenizerTest
-POST_BUILD
-COMMAND "${CMAKE_COMMAND}" -E copy_directory "${CMAKE_CURRENT_SOURCE_DIR}/objects" "${CMAKE_CURRENT_BINARY_DIR}/objects"
-)

Bug#906980: kmer: autopkgtest fails with segfault in testing/unstable while it passes in stable

[Liubov Chuprikova]

Hi Andreas,

On Thu, 23 Aug 2018 at 08:58 Andreas Tille  wrote:

>
> On Wed, Aug 22, 2018 at 09:42:13PM +0200, Liubov Chuprikova wrote:
> > An autopkgtest fails with segfault in testing and unstable [1].
> >
> > ```
> > /usr/bin/../lib/atac/bin/statsGenerator -a
> /tmp/autopkgtest-lxc.epng5fx9/downtmp/autopkgtest_tmp/results/EcolivsSent.atac
> > -p
> /tmp/autopkgtest-lxc.epng5fx9/downtmp/autopkgtest_tmp/results/stats/EcolivsSent
> > -g A >
> /tmp/autopkgtest-lxc.epng5fx9/downtmp/autopkgtest_tmp/results/stats/EcolivsSent.stats
> >
> > Segmentation fault
> > Failed to ganerate statistics.
> > ```
> >
> > Notably, that building and testing in stable were successful (I tested
> > it in clean chroot). JFI, I tried installing an older version of gcc on
> > testing, the one that is used in stable (4:6.3.0-4), and this eliminated
> > the segfault.
>
> Thanks for this good catch which proves how important your Outreachy
> project is for providing stable and working packages in Debian Med.
>

Now I see!


> Thanks also for verifying that older compilers seem to produce working
> code while newer don't.
>

This seemed just something to go on.

I wonder whether you feel able to do some debugging what position of
> code causes the issue.

My first shout would be to grep for
>"Failed to ganerate statistics"
> which is probably in a wrapper around some code and than use some
> debugging techniques (either you are comfortable with gdb / want to
> become comfortable with gdb or simply use some
> printf("DEBUG %s(%i): ...", __FILE__, __LINE__, ...);
> statements in the code to watch what's happening.



> It might be helpful to lower / switch off optimisation options to see
> whether some optimisation feature of some later gcc will deal
> differently with some not properly specified code part.
>

Thanks a lot for your advise! I tried debugging with grep when I had just
caught the error for the first time, but it was without result at that
moment. Turning off optimization flags, as you recommended, also did not
help. After that I made one more attemp to debug with grep and printing
some statements and finally found what it is called classical non-bug in
gcc [1].

I have just uploaded a patch. Could you please sponsor an upload?

With regards,
Liubov

[1] https://gcc.gnu.org/bugs/#nonbugs_c

Processed: Raising the severity to grave

[Debian Bug Tracking System]

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

> severity 904592 grave
Bug #904592 [predict-gsat] predict-gsat: No executable is included
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#904667: marked as done (sumo FTBFS due to a C++ error)

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 10:53:06 +
with message-id 
and subject line Bug#897872: fixed in sumo 0.32.0+dfsg1-2
has caused the Debian Bug report #897872,
regarding sumo FTBFS due to a C++ error
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.)


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

Hi,

While rebuilding packages in preparation of the json-c transition (#904418),
I discovered that sumo fails to build from source, independently of the
transition.

Please find a build log attached.


Best,

  nicoo

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

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: sumo
Source-Version: 0.32.0+dfsg1-2

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated sumo 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, 27 Aug 2018 12:28:23 +0200
Source: sumo
Binary: sumo sumo-doc sumo-tools
Architecture: source
Version: 0.32.0+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 sumo   - Simulation of Urban MObility (SUMO)
 sumo-doc   - Simulation of Urban MObility (SUMO), documentation and examples
 sumo-tools - Simulation of Urban MObility (SUMO), tools and scripts
Closes: 897872
Changes:
 sumo (0.32.0+dfsg1-2) unstable; urgency=medium
 .
   * [6b65aa2] Fix FTBFS with GCC-8. (Closes: #897872)
   * [a1ad134] Update VCS-field
   * [005fdea] Set Standards-Version to 4.2.0
Checksums-Sha1:
 2b7634451608c89bb9f1dc711c0c21de0c7a174a 2266 sumo_0.32.0+dfsg1-2.dsc
 5e72ee06e7f557bcb5824c59c30ee56eb297ea52 19668 
sumo_0.32.0+dfsg1-2.debian.tar.xz
 706462209ab2553088da79bb63b4386a96f6511c 15036 
sumo_0.32.0+dfsg1-2_source.buildinfo
Checksums-Sha256:
 dc207cf935bec53587e3d19a5863bcd302691d3a55532314596d8202a824a5a1 2266 
sumo_0.32.0+dfsg1-2.dsc
 fef737b11bb4c75341396bd7cc5a4c95d2b27cc73536cf23db767ba2460e99ec 19668 
sumo_0.32.0+dfsg1-2.debian.tar.xz
 34edece5d6138871f6206ebc1af259fdc4076dd00fddc6ef3d13ebfefcce77d1 15036 
sumo_0.32.0+dfsg1-2_source.buildinfo
Files:
 85c413bbf0cf38c390cc0e2ec1030b4d 2266 science optional sumo_0.32.0+dfsg1-2.dsc
 d25015985cf7ff17ece22047d6bc1124 19668 science optional 
sumo_0.32.0+dfsg1-2.debian.tar.xz
 7ca6c9cc51497d26f15025b85bd11573 15036 science optional 
sumo_0.32.0+dfsg1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAluD0mIACgkQ0+Fzg8+n
/wZGeBAAkKToC6Ls7KAWmHSwVmY3K/CUEzjuamgJDINtf+mw6FEN2cdRLYTewc0B
tlxJ4KkEHyrX5l8wSbm1G+iWLYKOtFbYjPMpc2Fr9/zXPX4eu4fjtMOL4mGQ2GHo
0DTki12Q9SZRw8RHwk/geW5EVqLD/UbtUVKDsV19Suud0d6zQBs9aiBIQA4HoThF
nZrVJBsnWGyh8mcqLaCKz208JCQuUmTXFonYRaJaIlt3TkSSNIFYasZJkd4XpNGl
Gx2AKnJ9fkQW8YA/BWAhmTGvNseb8Thb7r0FCiKPxGlRymHLZlZ9XyinX3PdZTIA
nQvGqp/OS/QGCLgt9kQYfEqEWxlJMiKNmyLqplp7LVuTErotIb8WN0sX2t7huYyA
nSE3jcqW2ZsCotNXzxMbcai1OQWl+PJUn4+ygdhyUcMmTLrmZF1xm9jIdOKHMZTe
Ea397WrgsUBfCWeAuHOPAU98od36yIgbCgMUOWAR2/ywgU7+JnI6ILeCN6e3lGJH
nPQU5qqz9WdIO4aSoz0Slxt3TAJ09zCmfQPoPen7PHWJSx1mFZHR+eLvZ5MvAk0A
vtjLxp7ZJ+OM0Rs2crUsL9hJ5gubu2qMh9HMiIFxAYuKtLy9rAKUo39kLL0v39lv
Cnp7OewXbd9x2tYHHy/DcltlQLNIwKFVaMt2ERNiGEnJshoP9hc=
=mZc8
-END PGP SIGNATURE End Message ---

Bug#897872: marked as done (sumo: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 10:53:06 +
with message-id 
and subject line Bug#897872: fixed in sumo 0.32.0+dfsg1-2
has caused the Debian Bug report #897872,
regarding sumo: ftbfs with GCC-8
to be marked as done.

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

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


-- 
897872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897872
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sumo
Version: 0.32.0+dfsg1-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

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

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

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/sumo_0.32.0+dfsg1-1_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
make[6]: Entering directory 
'/<>/sumo-0.32.0+dfsg1/src/microsim/lcmodels'
ranlib libmicrosimlcmodels.a
make[6]: Leaving directory 
'/<>/sumo-0.32.0+dfsg1/src/microsim/lcmodels'
Making all in logging
make[6]: Nothing to be done for 'all'.
Making all in output
make[6]: Entering directory 
'/<>/sumo-0.32.0+dfsg1/src/microsim/output'
g++ -DHAVE_CONFIG_H -I. -I../../../src  -I/<>/sumo-0.32.0+dfsg1/./src 
-I/usr/include/fox-1.6 -I/usr/include/gdal -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/local/include -I/usr/include  -Wdate-time -D_FORTIFY_SOURCE=2  
-std=c++11 -O2 -DNDEBUG -g -O2 
-fdebug-prefix-map=/<>/sumo-0.32.0+dfsg1=. -fstack-protector-strong 
-Wformat -Werror=format-security -c -o MSMeanData.o MSMeanData.cpp
In file included from /usr/include/c++/8/map:60,
 from ../../../src/microsim/MSEdgeControl.h:38,
 from MSMeanData.cpp:35:
/usr/include/c++/8/bits/stl_tree.h: In instantiation of 'class 
std::_Rb_tree, 
Named::ComparatorIdLess, std::allocator >':
/usr/include/c++/8/bits/stl_set.h:133:17:   required from 'class 
std::set'
../../../src/microsim/MSEdgeControl.h:223:48:   required from here
/usr/include/c++/8/bits/stl_tree.h:452:21: error: static assertion failed: 
comparison object must be invocable with two arguments of key type
   static_assert(__is_invocable<_Compare&, const _Key&, const _Key&>{},
 ^
make[6]: *** [Makefile:453: MSMeanData.o] Error 1
make[6]: Leaving directory '/<>/sumo-0.32.0+dfsg1/src/microsim/output'
make[6]: *** Waiting for unfinished jobs
make[6]: Entering directory 
'/<>/sumo-0.32.0+dfsg1/src/microsim/output'
g++ -DHAVE_CONFIG_H -I. -I../../../src  -I/<>/sumo-0.32.0+dfsg1/./src 
-I/usr/include/fox-1.6 -I/usr/include/gdal -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/local/include -I/usr/include  -Wdate-time -D_FORTIFY_SOURCE=2  
-std=c++11 -O2 -DNDEBUG -g -O2 
-fdebug-prefix-map=/<>/sumo-0.32.0+dfsg1=. -fstack-protector-strong 
-Wformat -Werror=format-security -c -o MSMeanData_Emissions.o 
MSMeanData_Emissions.cpp
make[6]: Leaving directory '/<>/sumo-0.32.0+dfsg1/src/microsim/output'
make[6]: Entering directory 
'/<>/sumo-0.32.0+dfsg1/src/microsim/output'
g++ -DHAVE_CONFIG_H -I. -I../../../src  -I/<>/sumo-0.32.0+dfsg1/./src 
-I/usr/include/fox-1.6 -I/usr/include/gdal -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/local/include -I/usr/include  -Wdate-time -D_FORTIFY_SOURCE=2  
-std=c++11 -O2 -DNDEBUG -g -O2 
-fdebug-prefix-map=/<>/sumo-0.32.0+dfsg1=. -fstack-protector-strong 
-Wformat -Werror=format-security -c -o MSMeanData_Harmonoise.o 
MSMeanData_Harmonoise.cpp
make[6]: Leaving directory '/<>/sumo-0.32.0+dfsg1/src/microsim/output'
make[6]: Entering directory 
'/<>/sumo-0.32.0+dfsg1/src/microsim/output'
g++ -DHAVE_CONFIG_H -I. -I../../../src  -I/<>/sumo-0.32.0+dfsg1/./src 
-I/usr/include/fox-1.6 -I/usr/include/gdal -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/local/include -I/usr/include  -Wdate-time -D_FORTI

Bug#906139: debian-policy: versioned depends on libjs-sphinxdoc unsatisfiable on stretch

[Raphael Hertzog]

Hi,

On Sat, 25 Aug 2018, Sean Whitton wrote:
> Urgh.
> 
> I am reluctantly (yet gratefully!) working on implementing Ian's
> substvar hack.

Or you could have read dh_linktree's manual page and see that you can
use "replace" instead of "deduplicate" to get a weak dependency.

$ git diff
diff --git a/debian/debian-policy-ja.linktrees 
b/debian/debian-policy-ja.linktrees
index bb8ef9b..74aef4c 100644
--- a/debian/debian-policy-ja.linktrees
+++ b/debian/debian-policy-ja.linktrees
@@ -1 +1 @@
-deduplicate /usr/share/javascript/sphinxdoc/1.0/ 
usr/share/doc/debian-policy/ja/policy.html/_static/
+replace /usr/share/javascript/sphinxdoc/1.0/ 
usr/share/doc/debian-policy/ja/policy.html/_static/
diff --git a/debian/debian-policy.linktrees b/debian/debian-policy.linktrees
index 88fadfd..ea76805 100644
--- a/debian/debian-policy.linktrees
+++ b/debian/debian-policy.linktrees
@@ -1 +1 @@
-deduplicate /usr/share/javascript/sphinxdoc/1.0/ 
usr/share/doc/debian-policy/policy.html/_static/
+replace /usr/share/javascript/sphinxdoc/1.0/ 
usr/share/doc/debian-policy/policy.html/_static/

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/


signature.asc
Description: PGP signature

Processed: block 904275 with 907239

[Debian Bug Tracking System]

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

> block 904275 with 907239
Bug #904275 [ftp.debian.org] RM: llvm-toolchain-5.0 -- ROM; Trying to limit the 
number of llvm versions in Debian
904275 was blocked by: 904279 904276 904277 904278
904275 was not blocking any bugs.
Added blocking bug(s) of 904275: 907239
> thanks
Stopping processing here.

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

Bug#896269: marked as done (python3-rebulk: rebulk fails to import)

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 11:35:15 +
with message-id 
and subject line Bug#896269: fixed in python-rebulk 0.9.0-2
has caused the Debian Bug report #896269,
regarding python3-rebulk: rebulk fails to import
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.)


-- 
896269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-rebulk
Version: 0.9.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-rebulk importing the module rebulk
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/rebulk/__init__.py", line 7, in 
from .rebulk import Rebulk
  File "/usr/lib/python3/dist-packages/rebulk/rebulk.py", line 13, in 
from .processors import ConflictSolver, PrivateRemover
  File "/usr/lib/python3/dist-packages/rebulk/processors.py", line 10, in 

from .rules import Rule, RemoveMatch
  File "/usr/lib/python3/dist-packages/rebulk/rules.py", line 14, in 
from toposort import toposort
ModuleNotFoundError: No module named 'toposort'

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: python-rebulk
Source-Version: 0.9.0-2

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

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

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-rebulk 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, 27 Aug 2018 13:08:35 +0200
Source: python-rebulk
Binary: python3-rebulk
Architecture: source all
Version: 0.9.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Description:
 python3-rebulk - Define simple search patterns in bulk to perform advanced 
matchin
Closes: 896269
Changes:
 python-rebulk (0.9.0-2) unstable; urgency=medium
 .
   * Team upload.
   * d/control: Set Vcs-* to salsa.debian.org
   * Enable autopkgtest-pkg-python testsuite
   * d/p/0001-Remove-embedded-toposort.patch:
 Add toposort into install_requires (Closes: #896269)
   * Bump debhelper compat level to 11
   * Standards version is 4.2.1 now (no changes)
   * d/copyright: Remove unused paragraph
Checksums-Sha1:
 6564e293b3b0214331fc156a9a231b8d9bf380a7 2128 python-rebulk_0.9.0-2.dsc
 f24d3cb43df6555edcfe2b487af2473e731641d6 4528 
python-rebulk_0.9.0-2.debian.tar.xz
 84054924b9024426097e4ce987feabd5e6c0cb29 6610 
python-rebulk_0.9.0-2_amd64.buildinfo
 7541ed2ef208f18b8a600308345bf7d6a9428cb8 36532 python3-rebulk_0.9.0-2_all.deb
Checksums-Sha256:
 93d8a2418f2aa4f7109c9f55d6d9169d6a0962aba53e4fa0cf5b59dfd6594a0f 2128 
python-rebulk_0.9.0-2.dsc
 67bcf630375c9570381ea2e63a283aaceec8494bafd6d58fcb5f879d6819c469 4528 
python-rebulk_0.9.0-2.debian.tar.xz
 bc86ea9366e98469813211f37766762add432d0bc2d840aaaf1a521895085417 6610 
python-rebulk_0.9.0-2_amd64.buildinfo
 cd82bb6766a6ff2a70bc4620f6ae14ab2f556b05c6de758f3ad7ddeb368b69c5 36532 
python3-rebulk_0.9.0-2_all.deb
Files:
 7d4b74f1707b216bc2c3a19a2b62307f 2128 python optional python-rebulk_0.9.0-2.dsc
 28efff7b610fbeaf8d06753a464fb0a6 4528 python optional 
python-rebulk_0.9.0-2.debian.tar.xz
 a1552f889056d63004d4149de6d61b11 6610 python optional 
python-rebulk_0.9.0-2_amd64.buildinfo
 7574dd493a73e0851fde3c9e50b67639 36532 python optional 
python3-rebulk_0.9.0-2_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAluD3CkACgkQNXMSVZ0e
BksyXBAAglqqEauEgcL/wIm4Zb8Pqx0IOeXhZzvA2KXyGpdwmVD5bGyq8dFFaM3w
X3uJ87bS6gp/oz7gmFq403pi7eYc4TOQoHHO+a

Bug#892706: marked as done (guake-indicator: Depends on gconf)

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 11:34:32 +
with message-id 
and subject line Bug#892706: fixed in guake-indicator 1.4-1
has caused the Debian Bug report #892706,
regarding guake-indicator: Depends on gconf
to be marked as done.

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

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


-- 
892706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: guake-indicator
Version: 1.1-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf
Tags: sid buster

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

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

Please try to port your package away from gconf. Otherwise, please
consider requesting that your package be removed from Debian to help us
complete this goal.

References
--
https://developer.gnome.org/gio/stable/ch34.html
https://developer.gnome.org/gio/stable/GSettings.html
https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: guake-indicator
Source-Version: 1.4-1

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

Debian distribution maintenance software
pp.
Alessio Garzi  (supplier of updated guake-indicator 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, 27 Aug 2018 10:27:50 +0200
Source: guake-indicator
Binary: guake-indicator
Architecture: source
Version: 1.4-1
Distribution: unstable
Urgency: medium
Maintainer: Alessio Garzi 
Changed-By: Alessio Garzi 
Description:
 guake-indicator - Guake terminal app indicator
Closes: 829883 891093 892706 906046
Changes:
 guake-indicator (1.4-1) unstable; urgency=medium
 .
   [ Alessio Garzi ]
   * New upstream release.
   * debian/guake-indicator.1:
 + Drop man page, now shipped upstream.
   * debian/manpages:
 + Drop file. Upstream man page now installed via autotools.
   * debian/menu:
 + Drop file. Forbidden as applications has a .desktop file.
   * debian/install:
 + Remove data/gi_custom_cmd_form.glade, no custom cmd form in this upstream
   version anymore.
   * debian/control:
 + Drop from B-D: gnome-common, not needed anymore. (Closes: #829883).
 + Drop from B-D: libgconf2-dev. (Closes: #892706).
 + Drop from B-D and D: python-beautifulsoup. (Closes: #891093).
 + Replace B-D on libappindicator-dev by B-D on 
libayatana-appindicator3-dev.
   (Closes: #906046).
 .
   [ Mike Gabriel ]
   * debian/changelog: White-space cleanup.
   * debian/rules:
 + Add get-orig-source target.
 + Drop --with autotools-dev. Deprecated.
 + Enable all hardening flags.
   * debian/watch:
 + Fix URL scheme, upstream tarball now has a dash (not underscore) after
   the code project name.
   * debian/control:
 + Bump Standards-Version: to 4.2.0. No changes needed.
 + Add Vcs-*: fields. Packaging now takes place on salsa.debian.org.
 + Add B-D: dpkg-dev (>= 1.16.1.1~).
 + Drop now useless B-D on autotools-dev.
   * debian/{control,compat}: Bump DH compat level to version 11.
   * debian/copyright:
 + Use secure URI for copyright format reference.
Checksums-Sha1:
 063362c445df086f0ebf2b153e38d8f3fb56cad3 2105 guake-indicator_1.4-1.dsc
 a3c552c1a1ea8e8dd6bed0ad639a50230d1af02c 215577 guake-indicator_1.4.orig.tar.gz
 9571637e566c5f28d47c8d44a3fc923618619d86 2752 
guake-indicator_1.4-1.debian.tar.xz
 1f3bcd7ad06678dde5d83942f6da73e3eb7df95d 34313 
guake-indicator_1.4-1_source.buildinfo
Checksums-Sha256:
 9c41d588738f128bd5f7d115f8563acc671e487cd67e5096a44f09239c47288f 2105 
guake-indicator_1.4-1.dsc
 30a2b9fe488d7d651695d04d06603e95a625243e21d52df676377aa7b9218db7 215577 
guake-indicator_1.4.orig.tar.gz
 c91a1086c03a8e2221f6765ff2d3abe3fcb58a024127548e9046d4cb0951c15a 2752 
guake-indicator_1.4-1.debian.tar.xz
 2309ad6fb799a374aa81c2797a56783de5850796c6abd404ca3

Bug#906379: marked as done (libsass-python: FTBFS in buster/sid (error: 'sass_option_push_import_extension' was not declared in this scope))

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 12:05:45 +
with message-id 
and subject line Bug#906379: fixed in libsass-python 0.14.5-2
has caused the Debian Bug report #906379,
regarding libsass-python: FTBFS in buster/sid (error: 
'sass_option_push_import_extension' was not declared in this scope)
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.)


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

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dpkg-query -f '\n' -W libsass-dev|sed 's/-.*//' > .libsass-upstream-version
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
pybuild --configure --test-pytest -i python{version} -p 2.7
I: pybuild base:217: python2.7 setup.py config 
running config
pybuild --configure --test-pytest -i python{version} -p 3.6
I: pybuild base:217: python3.6 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
pybuild --build -p "2.7 3.6"
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
copying sass.py -> /<>/.pybuild/cpython3_3.6/build
copying sassc.py -> /<>/.pybuild/cpython3_3.6/build
copying sasstests.py -> /<>/.pybuild/cpython3_3.6/build
creating /<>/.pybuild/cpython3_3.6/build/sassutils
copying sassutils/distutils.py -> 
/<>/.pybuild/cpython3_3.6/build/sassutils
copying sassutils/wsgi.py -> 
/<>/.pybuild/cpython3_3.6/build/sassutils
copying sassutils/__init__.py -> 
/<>/.pybuild/cpython3_3.6/build/sassutils
copying sassutils/builder.py -> 
/<>/.pybuild/cpython3_3.6/build/sassutils
running build_ext
building '_sass' extension
creating build
creating build/temp.linux-amd64-3.6
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/python3.6m -c pysass.cpp -o build/temp.linux-amd64-3.6/pysass.o 
-fPIC -std=gnu++0x -Wall -Wno-parentheses -Werror=switch
pysass.cpp: In function 'void _add_custom_import_extensions(Sass_Options*, 
PyObject*)':
pysass.cpp:515:9: error: 'sass_option_push_import_extension' was not declared 
in this scope
 sass_option_push_import_extension(options, PyBytes_AS_STRING(ext));
 ^
pysass.cpp:515:9: note: suggested alternative: 'sass_option_set_c_importers'
 sass_option_push_import_extension(options, PyBytes_AS_STRING(ext));
 ^
 sass_option_set_c_importers
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py build 
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 13
make[1]: Leaving directory '/<>'
make: *** [debian/rules:9: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

where you can get a full build log if you need it.

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: libsass-python
Source-Version: 0.14.5-2

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

Processed: Re: golang-github-hashicorp-memberlist: FTBFS randomly (failing tests)

[Debian Bug Tracking System]

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

> retitle 906360 golang-github-hashicorp-memberlist: FTBFS randomly (failing 
> tests)
Bug #906360 [src:golang-github-hashicorp-memberlist] 
golang-github-hashicorp-memberlist: FTBFS in buster/sid (failing tests)
Changed Bug title to 'golang-github-hashicorp-memberlist: FTBFS randomly 
(failing tests)' from 'golang-github-hashicorp-memberlist: FTBFS in buster/sid 
(failing tests)'.
> severity 906360 important
Bug #906360 [src:golang-github-hashicorp-memberlist] 
golang-github-hashicorp-memberlist: FTBFS randomly (failing tests)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#906360: golang-github-hashicorp-memberlist: FTBFS randomly (failing tests)

[Santiago Vila]

retitle 906360 golang-github-hashicorp-memberlist: FTBFS randomly (failing 
tests)
severity 906360 important
thanks

This is really random. It builds most of the time but not always.

Thanks.

Bug#903523: marked as done (jaraco.itertools FTBFS with Python 3.7 as supported version)

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 13:04:48 +
with message-id 
and subject line Bug#903523: fixed in jaraco.itertools 2.0.1-2
has caused the Debian Bug report #903523,
regarding jaraco.itertools FTBFS with Python 3.7 as supported version
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.)


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

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

...
I: pybuild base:217: cd 
/build/1st/jaraco.itertools-2.0.1/.pybuild/cpython3_3.7_jaraco.itertools/build; 
python3.7 -m pytest jaraco/
= test session starts ==
platform linux -- Python 3.7.0, pytest-3.6.2, py-1.5.3, pluggy-0.6.0
rootdir: 
/build/1st/jaraco.itertools-2.0.1/.pybuild/cpython3_3.7_jaraco.itertools/build, 
inifile: pytest.ini
collected 32 items

jaraco/itertools.py ..FF..FF.F.. [100%]

=== FAILURES ===
___ [doctest] jaraco.itertools.FetchingQueue ___
146 
147 A FIFO Queue that is supplied with a function to inject more into
148 the queue if it is empty.
149 
150 >>> values = iter(range(10))
151 >>> get_value = lambda: globals()['q'].enqueue(next(values))
152 >>> q = FetchingQueue(get_value)
153 >>> [x for x in q] == list(range(10))
UNEXPECTED EXCEPTION: RuntimeError('generator raised StopIteration')
Traceback (most recent call last):

  File 
"/build/1st/jaraco.itertools-2.0.1/.pybuild/cpython3_3.7_jaraco.itertools/build/jaraco/itertools.py",
 line 175, in __iter__
yield next(self)

  File 
"/build/1st/jaraco.itertools-2.0.1/.pybuild/cpython3_3.7_jaraco.itertools/build/jaraco/itertools.py",
 line 169, in __next__
self._fetcher()

  File "", line 1, in 

StopIteration


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


Traceback (most recent call last):

  File "/usr/lib/python3.7/doctest.py", line 1329, in __run
compileflags, 1), test.globs)

  File "", line 1, in 

  File "", line 1, in 

RuntimeError: generator raised StopIteration

/build/1st/jaraco.itertools-2.0.1/.pybuild/cpython3_3.7_jaraco.itertools/build/jaraco/itertools.py:153:
 UnexpectedException
___ [doctest] jaraco.itertools.GroupbySaved 
073 element in the sequence.
074 
075 >>> truthsplit = GroupbySaved(['Test', '', 30, None], bool)
076 >>> truthsplit['x']
077 Traceback (most recent call last):
078 ...
079 KeyError: 'x'
080 >>> true_items = truthsplit[True]
081 >>> false_items = truthsplit[False]
082 >>> tuple(iter(false_items))
UNEXPECTED EXCEPTION: RuntimeError('generator raised StopIteration')
Traceback (most recent call last):

  File 
"/build/1st/jaraco.itertools-2.0.1/.pybuild/cpython3_3.7_jaraco.itertools/build/jaraco/itertools.py",
 line 175, in __iter__
yield next(self)

  File 
"/build/1st/jaraco.itertools-2.0.1/.pybuild/cpython3_3.7_jaraco.itertools/build/jaraco/itertools.py",
 line 169, in __next__
self._fetcher()

  File 
"/build/1st/jaraco.itertools-2.0.1/.pybuild/cpython3_3.7_jaraco.itertools/build/jaraco/itertools.py",
 line 115, in __fetch__
item = next(self.sequence)

StopIteration


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


Traceback (most recent call last):

  File "/usr/lib/python3.7/doctest.py", line 1329, in __run
compileflags, 1), test.globs)

  File "", line 1, in 

RuntimeError: generator raised StopIteration

/build/1st/jaraco.itertools-2.0.1/.pybuild/cpython3_3.7_jaraco.itertools/build/jaraco/itertools.py:82:
 UnexpectedException
__ [doctest] jaraco.itertools.bisect ___
046 
047 Split a sequence into two sequences:  the first is elements that
048 return False for func(element) and the second for True for
049 func(element).
050 By default, func is ``bool``, so uses the truth value of the object.
051 
052 >>> is_odd = lambda n: n%2
053 >>> even, odd = bisect(range(5), is_odd)
054 >>> list(odd)
UNEXPECTED EXCEPTION: RuntimeError('generator raised StopIteration')
Traceback (most recent call last):

  File 
"/build/1st/jaraco.itertools-2.0.1/.pybuild/cpython3_3.7_jaraco.itertools/build/jaraco/itertools.py",
 line 175, in __iter__
yield next(self)

  File 
"/build/1st/jaraco.itertools-2.0.1/.pybuild

Bug#907392: firebird3.0-utils: tables with varchar attributes with big size cannot be backed up with gbak

[Pablo Sánchez [gmail]]

Package: firebird3.0-utils
Version: 3.0.3.32900.ds4-4
Severity: grave
Justification: renders package unusable (kind of)

1- create database, and insert on column (using raspbian)

SQL> create database '/srv/data/debian-test.fdb'
CON> user 'SYSDBA'
CON> password 'masterkey'
CON> page_size 8192
CON> default character set iso8859_1;
SQL> commit ;
SQL> exit ;

2- create a table with a big size varchar and insert data into it .
CREATE TABLE TEST
(
  ID INTEGER,
  VC VARCHAR(32765)
);

INSERT INTO TABLE1 (ID, TEXT) VALUES ('1', 'abcdef123456');

3- backup database

root@raspberrypi:/srv/data# gbak -b -v  -user SYSDBA -password masterkey
/srv/data/debian-test.fdb /srv/data/debian-test.fbk
gbak:readied database /srv/data/debian-test.fdb for backup
gbak:creating file /srv/data/debian-test.fbk
gbak:starting transaction
gbak:database /srv/data/debian-test.fdb has a page size of 8192 bytes.
gbak:writing domains
gbak:writing domain RDB$1
gbak:writing domain RDB$2
gbak:writing shadow files
gbak:writing character sets
gbak:writing collations
gbak:writing tables
gbak:writing table TABLE1
gbak: writing column ID
gbak: writing column TEXT
gbak:writing types
gbak:writing filters
gbak:writing id generators
gbak:writing exceptions
gbak:writing functions
gbak:writing stored procedures
gbak:writing packages
gbak:writing data for table TABLE1
gbak: ERROR:message length error (encountered -32758, expected 32778)
gbak: ERROR:gds_$receive failed
gbak:Exiting before completion due to errors

Note that if I create db on amd64 and restore on raspberrypi, I get the
same error .
But if create db on amd64 and restore on amd64 there is no error and data
is there.
I use buster now, but on v2.5 on stretch had the same problem. After
posting on
firebrid-support , I was suggested to post here.

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

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

Versions of packages firebird3.0-utils depends on:
ii  firebird3.0-common  3.0.3.32900.ds4-4
ii  firebird3.0-common-doc  3.0.3.32900.ds4-4
ii  libc6   2.27-5+rpi1
ii  libedit23.1-20180525-1
ii  libfbclient23.0.3.32900.ds4-4
ii  libgcc1 1:8.1.0-12+rpi1
ii  libncurses6 6.1+20180714-1
ii  libstdc++6  8.1.0-12+rpi1
ii  libtinfo6   6.1+20180714-1
ii  libtommath1 1.0.1-1

Versions of packages firebird3.0-utils recommends:
ii  firebird3.0-server-core  3.0.3.32900.ds4-4

Versions of packages firebird3.0-utils suggests:
pn  firebird3.0-doc 
ii  firebird3.0-server  3.0.3.32900.ds4-4

-- no debconf information
Regards

Pablo Sánchez

Bug#906139: debian-policy: versioned depends on libjs-sphinxdoc unsatisfiable on stretch

[Sean Whitton]

Hello Raphael,

On Mon 27 Aug 2018 at 12:58PM +0200, Raphael Hertzog wrote:

> Or you could have read dh_linktree's manual page and see that you can
> use "replace" instead of "deduplicate" to get a weak dependency.

I did read this -- unfortunately, though, it would not help make
debian-policy installable on stretch, which was the original bug
reporter's problem.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Processed: automake-1.16: diff for NMU version 1:1.16.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 906426 + pending
Bug #906426 [automake] gnuchess: FTBFS: makeinfo: command not found (missing 
build-dependency on texinfo)
Bug #906557 [automake] ratpoison: FTBFS in buster/sid (makeinfo: command not 
found)
Bug #906774 [automake] dico: FTBFS in buster/sid (makeinfo: command not found)
Bug #906775 [automake] hamlib: FTBFS in buster/sid (makeinfo: command not found)
Bug #906778 [automake] guile-gnome-platform: FTBFS in buster/sid (makeinfo: 
command not found)
Bug #906790 [automake] libtasn1-6 FTBFS during arch-only: missing makeinfo
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.

-- 
906426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906426
906557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906557
906774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906774
906775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906775
906778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906778
906790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#906426: automake-1.16: diff for NMU version 1:1.16.1-1.1

[Adrian Bunk]

Control: tags 906426 + pending

Dear maintainer,

I've prepared an NMU for automake-1.16 (versioned as 1:1.16.1-1.1) and 
uploaded it to DELAYED/5. Please feel free to tell me if I should cancel it.

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

diff -Nru automake-1.16-1.16.1/debian/changelog automake-1.16-1.16.1/debian/changelog
--- automake-1.16-1.16.1/debian/changelog	2018-07-18 23:49:47.0 +0300
+++ automake-1.16-1.16.1/debian/changelog	2018-08-27 16:40:12.0 +0300
@@ -1,3 +1,11 @@
+automake-1.16 (1:1.16.1-1.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Remove 0008-SOURCE_DATE_EPOCH-support-for-mdate-sh.patch which
+broke mdate-sh, thanks to Andreas Metzler. (Closes: #906426)
+
+ -- Adrian Bunk   Mon, 27 Aug 2018 16:40:12 +0300
+
 automake-1.16 (1:1.16.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru automake-1.16-1.16.1/debian/patches/series automake-1.16-1.16.1/debian/patches/series
--- automake-1.16-1.16.1/debian/patches/series	2018-07-18 23:49:47.0 +0300
+++ automake-1.16-1.16.1/debian/patches/series	2018-08-27 16:40:06.0 +0300
@@ -1,4 +1,4 @@
 0001-texi-rename.patch
 0005-Disable-t-check12.sh-and-t-check12-w.sh.patch
 0006-Drop-SHELL.patch
-0008-SOURCE_DATE_EPOCH-support-for-mdate-sh.patch
+#0008-SOURCE_DATE_EPOCH-support-for-mdate-sh.patch

Processed: abinit: new upstream release 8.8.4

[Debian Bug Tracking System]

Processing control commands:

> block 897696 by -1
Bug #897696 [src:abinit] abinit: ftbfs with GCC-8
897696 was not blocked by any bugs.
897696 was not blocking any bugs.
Added blocking bug(s) of 897696: 907395
> block -1 by 578829
Bug #907395 [src:abinit] abinit: new upstream release 8.8.4
907395 was not blocked by any bugs.
907395 was blocking: 897696
Added blocking bug(s) of 907395: 578829

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

Bug#907171: prometheus FTBFS:

[Martín Ferrari]

Adrian,

On 24/08/18 13:47, Adrian Bunk wrote:

> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prometheus.html
> 
> ...
> panic: Can't start web handler:listen tcp :9090: bind: address already in use

This is a known problem when running the autopkgtests, becasue the
installed package starts the daemon and then the tests fail when trying
to use the same port; but this is not a FTBFS: the build daemons do not
fail to build from source. I think you should lower the severity.

-- 
Martín Ferrari (Tincho)

Bug#906616: marked as done (form builds with -march=native)

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 14:41:57 +
with message-id 
and subject line Bug#906616: fixed in form 4.2.0+git20180528-2
has caused the Debian Bug report #906616,
regarding form builds with -march=native
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.)


-- 
906616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: form
Version: 4.2.0+git20180528-1
Severity: serious

march=native must not be used since the resulting code will only run
on machines compatible with whatever buildd built the package.
--- End Message ---
--- Begin Message ---
Source: form
Source-Version: 4.2.0+git20180528-2

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

Debian distribution maintenance software
pp.
Gürkan Myczko  (supplier of updated form 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, 27 Aug 2018 15:24:16 +0200
Source: form
Binary: form form-doc
Architecture: source
Version: 4.2.0+git20180528-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Gürkan Myczko 
Description:
 form   - Symbolic manipulation system
 form-doc   - Documentation for symbolic manipulation system
Closes: 906616
Changes:
 form (4.2.0+git20180528-2) unstable; urgency=medium
 .
   * Update homepage.
   * Omit -march support. (Closes: #906616)
   * Bump debhelper version to 11.
   * Bump standards version to 4.2.1.
Checksums-Sha1:
 c2a0ac25ef093ee8beb2e25e13fc52dc5190c49c 1975 form_4.2.0+git20180528-2.dsc
 d6e1de1f011aab31d9803da5592044bc6db05c23 3832 
form_4.2.0+git20180528-2.debian.tar.xz
 400e6eeada7820d81cf36f45bd5fd92dd0bf8bfb 5570 
form_4.2.0+git20180528-2_source.buildinfo
Checksums-Sha256:
 2d7cfd44b442c10b5a3245ba50ec22a473fa047b8537d72fb8755ecad78e2153 1975 
form_4.2.0+git20180528-2.dsc
 1b967c18806ae171c602e27d71230d889f0375bcc3c8405058b009c4bb8603be 3832 
form_4.2.0+git20180528-2.debian.tar.xz
 4912dcf26cbb9edf41d6b8ab95b51b48d75796d7c8edf74d09395427f4996128 5570 
form_4.2.0+git20180528-2_source.buildinfo
Files:
 99036033bc9abcdb0bca2410787c6859 1975 science optional 
form_4.2.0+git20180528-2.dsc
 e42ec652a3c9a5ed91e7db103eb45122 3832 science optional 
form_4.2.0+git20180528-2.debian.tar.xz
 3bd72f7d5e48eafd3f396f9ad94eecb2 5570 science optional 
form_4.2.0+git20180528-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAluECYkACgkQweDZLphv
fH7Lng/8DmDCct9daElb8N/C6qUJFtQF8TgGO/k3cb+IOrbv0HI6KsTwwQK168/4
czZZk6vcgsABXyISMm2z5cdPGMVKKXR9TA/3DkeZKcfKNAKbCd/TZXrTNQfAPgoa
l/P977B23LXldT9WpG+AoMdYIde1SNP7sclDPenOkA6rj7lOQpqn8ZH1tmlORGu3
1Pb4rS/jgvy/ZavBHWGQo2OMhG04fat+iFT3w7O/Yfc1gNvSRkenj0DBef6pU6Ay
Rz4Uf78PqNqd42hOsfkmUXA+MilM5srbks4PShzth0iAOrCSitwIjaU4hucQDZrJ
gCtdbUbumt5S0iWypwi3zlt0K/gGSfZRuju23qmfoTpi2m+PS3clybDTv1BVt44m
tbt7X7nBV/vYRfOaxYjYqk1kJmmEhAcppUK/IdA+dpvVZCym3e5UFfpsdgGWCnmP
ONg/z/XNLTsRoa4GWtNspg9rh/6ZkATjRZwNS/ucT9xPKLwMAE1la62iR3Mieg9B
MQY3ZaKb8HnwJaIig2yxxRzaChNdTMWtq3JyflgBbjdpi+X5lp6mUjY7GkNnc6gK
Jo8HeGg7aP/LmXjVeaC/cVpS4KRNkl93flPcUW94k4lFmtGqNJ5hk/zhFFYSaNQN
AEyHbMnZ4MZqJor7QD6c8zD6sjAyrDwG+EAgQcHKKigMWRPZYNs=
=cqvg
-END PGP SIGNATURE End Message ---

Bug#906764: recoll: FTBFS in buster/sid (invalid use of incomplete type 'class QAbstractItemView')

[Kartik Mistry]

On Fri, Aug 24, 2018 at 4:15 PM Jean-Francois Dockes  wrote:
> The attached patch should clear the problem.

Thank you! I'll upload package today.

--
Kartik Mistry | કાર્તિક મિસ્ત્રી
kartikm.wordpress.com

Bug#897696: tag 897696 as fixed-upstream

[Andrius Merkys]

|control: tags 897696 + fixed-upstream Hello, the bug indeed seems to be fixed 
at least in 8.8.4, which builds in sid on amd64. Andrius |

-- 
Andrius Merkys
Vilnius University Institute of Biotechnology, Saulėtekio al. 7, room V325
LT-10257 Vilnius, Lithuania

Processed: tag 897696 as fixed-upstream

[Debian Bug Tracking System]

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

> tags 897696 + fixed-upstream
Bug #897696 [src:abinit] abinit: ftbfs with GCC-8
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: Re: Bug#906980: kmer: autopkgtest fails with segfault in testing/unstable while it passes in stable

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #906980 [kmer] kmer: autopkgtest fails with segfault in testing/unstable 
while it passes in stable
Added tag(s) pending.

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

Bug#906980: kmer: autopkgtest fails with segfault in testing/unstable while it passes in stable

[Andreas Tille]

Control: tags -1 pending

Hi Liubov,

On Mon, Aug 27, 2018 at 12:36:22PM +0200, Liubov Chuprikova wrote:
> > > it in clean chroot). JFI, I tried installing an older version of gcc on
> > > testing, the one that is used in stable (4:6.3.0-4), and this eliminated
> > > the segfault.
> >
> > Thanks for this good catch which proves how important your Outreachy
> > project is for providing stable and working packages in Debian Med.
> 
> Now I see!

:-)
 
> Thanks a lot for your advise! I tried debugging with grep when I had just
> caught the error for the first time, but it was without result at that
> moment. Turning off optimization flags, as you recommended, also did not
> help. After that I made one more attemp to debug with grep and printing
> some statements and finally found what it is called classical non-bug in
> gcc [1].

Ah, finally a pretty simple solution for a quite hidden problem.
BTW, I wonder whether there are tools that would warn about issues
described in[1] - I think there are good means to detect this
automatically.

Would you please forward this solution to upstream?  May be once you
contact upstream asking for a versioned release for download would be a
good idea.
 
> I have just uploaded a patch. Could you please sponsor an upload?

I did.  Unfortunately I created quite some mess in the Git repository.
I was traveling yesterday, found a patch for bug #907007 and uploaded
without further checking.  To make things worse I forgot to push my
changes due to bad bandwidth.  I tried hard to get your commits right
again to keep some sensible history.  I hope its not so confusing - at
least the resulting code in debian/ dir is correct ...

Please note that I moved the data file into a separate package
kmer-examples to avoid duplication of the data files and enable users
installing the code without the data.  Thus the package needs to pass
the new queue (hope this will happen soon).

Thanks a lot for you fine work.  I think this issue is something you
can be really proud about since your work uncovered an issue and you
finally was able to fix it.  I really hope you will be able to
continue this work even if GSoC is close to finished.  May be, if you
have time you could continue a bit.  I'd be very happy about this.

Kind regards and thanks again

  Andreas.

 
> [1] https://gcc.gnu.org/bugs/#nonbugs_c

-- 
http://fam-tille.de

Bug#907171: prometheus FTBFS:

[Santiago Vila]

On Mon, 27 Aug 2018, Martín Ferrari wrote:

> Adrian,
> 
> On 24/08/18 13:47, Adrian Bunk wrote:
> 
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prometheus.html
> > 
> > ...
> > panic: Can't start web handler:listen tcp :9090: bind: address already in 
> > use
> 
> This is a known problem when running the autopkgtests, becasue the
> installed package starts the daemon and then the tests fail when trying
> to use the same port; but this is not a FTBFS: the build daemons do not
> fail to build from source. I think you should lower the severity.

Tincho, if we go that route we would be applying a definition for FTBFS
which would be different from everybody else.

A FTBFS could be defined as a non-zero exit status from
dpkg-buildpackage. If you include the test suite as part of the build,
then a failure in the test suite will naturally mean a FTBFS bug, for
all purposes.

If, as you explain, the tests are not suitable to be run after
dh_auto_build, then it follows that they should be disabled from the
package build, because we don't want dpkg-buildpackage to exit with
error. In such case, just an empty debian/rules target like this:

override_dh_auto_test:

would do the trick.

(But of course disabling only the failing tests would be better).

Thanks.

Bug#906377: marked as done (libpgjava: FTBFS in buster/sid)

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 15:20:23 +
with message-id 
and subject line Bug#906377: fixed in libpgjava 42.2.4-2
has caused the Debian Bug report #906377,
regarding libpgjava: FTBFS in buster/sid
to be marked as done.

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

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


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

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
mh_patchpoms -plibpostgresql-jdbc-java --debian-build 
--keep-pom-version --maven-repo=/<>/debian/maven-repo
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- package
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-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 
-DskipTests -Dnotimestamp=true -Dlocale=en_US
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations

[... snipped ...]

[WARNING] ^
[WARNING] 
/<>/pgjdbc/target/gen-src/org/postgresql/sspi/NTDSAPIWrapper.java:11:
 error: package com.sun.jna.ptr does not exist
[WARNING] import com.sun.jna.ptr.IntByReference;
[WARNING] ^
[WARNING] 
/<>/pgjdbc/target/gen-src/org/postgresql/osgi/PGDataSourceFactory.java:17:
 error: package org.osgi.service.jdbc does not exist
[WARNING] import org.osgi.service.jdbc.DataSourceFactory;
[WARNING] ^
[WARNING] 
/<>/pgjdbc/target/gen-src/org/postgresql/osgi/PGBundleActivator.java:10:
 error: package org.osgi.framework does not exist
[WARNING] import org.osgi.framework.BundleActivator;
[WARNING] ^
[WARNING] 
/<>/pgjdbc/target/gen-src/org/postgresql/osgi/PGBundleActivator.java:11:
 error: package org.osgi.framework does not exist
[WARNING] import org.osgi.framework.BundleContext;
[WARNING] ^
[WARNING] 
/<>/pgjdbc/target/gen-src/org/postgresql/osgi/PGBundleActivator.java:12:
 error: package org.osgi.framework does not exist
[WARNING] import org.osgi.framework.ServiceRegistration;
[WARNING] ^
[WARNING] 
/<>/pgjdbc/target/gen-src/org/postgresql/osgi/PGBundleActivator.java:13:
 error: package org.osgi.service.jdbc does not exist
[WARNING] import org.osgi.service.jdbc.DataSourceFactory;
[WARNING] ^
[WARNING] javadoc: warning - You have not specified the version of HTML to use.
[WARNING] The default is currently HTML 4.01, but this will change to HTML5
[WARNING] in a future release. To suppress this warning, please specify the
[WARNING] version of HTML used in your documentation comments and to be
[WARNING] generated by this doclet, using the -html4 or -html5 options.
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] PostgreSQL JDBC Driver - JDBC 4.2 .. FAILURE [ 13.441 s]
[INFO] PostgreSQL JDBC Driver aggregate 42.2.4  SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 14.969 s
[INFO] Finished at: 2018-08-14T05:28:00Z
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc (default-cli) on 
project postgresql: An error has occurred in Javadoc report generation: Project 
contains Javadoc Warnings -> [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

Processed: bug 906781 is forwarded to https://sourceforge.net/p/podofo/tickets/29/

[Debian Bug Tracking System]

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

> forwarded 906781 https://sourceforge.net/p/podofo/tickets/29/
Bug #906781 [src:libpodofo] libpodofo: FTBFS in buster/sid (Error copying 
directory)
Set Bug forwarded-to-address to 'https://sourceforge.net/p/podofo/tickets/29/'.
> thanks
Stopping processing here.

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

Bug#907055: marked as done (erlang-p1-tls FTBFS with OpenSSL 1.1.1)

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 15:19:19 +
with message-id 
and subject line Bug#907055: fixed in erlang-p1-tls 1.0.23-2
has caused the Debian Bug report #907055,
regarding erlang-p1-tls FTBFS with OpenSSL 1.1.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.)


-- 
907055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-p1-tls
Version: 1.0.23-1
Severity: serious
Tags: ftbfs
Control: block 907015 by -1

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/erlang-p1-tls.html

...
 EUnit 
module 'fast_tls_sup'
module 'fast_tls_app'
module 'p1_sha'
  p1_sha: load_nif_test...[0.013 s] ok
  p1_sha: sha1_test...ok
  p1_sha: sha224_test...ok
  p1_sha: sha256_test...ok
  p1_sha: sha384_test...ok
  p1_sha: sha512_test...ok
  p1_sha: to_hexlist_test...ok
  [done in 0.035 s]
module 'fast_tls'
  fast_tls: load_nif_test...[0.002 s] ok
  fast_tls: transmission_test...*failed*
in function fast_tls:'-transmission_test/0-fun-1-'/1 (src/fast_tls.erl, line 
511)
**error:{assertEqual,[{module,fast_tls},
  {line,511},
  {expression,"<< \"abcdefghi\" >>"},
  {expected,<<>>},
  {value,<<"abcdefghi">>}]}
  output:<<"">>

  fast_tls: not_compatible_protocol_options_test...[1.014 s] ok
  [done in 3.044 s]
===
  Failed: 1.  Skipped: 0.  Passed: 9.
Cover analysis: /build/1st/erlang-p1-tls-1.0.23/.eunit/index.html
Coverdata export: /build/1st/erlang-p1-tls-1.0.23/.eunit/cover.coverdata
DEBUG: Reconstruct rebar []
DEBUG: Reconstruct crypto [{fips_mode,false}]
DEBUG: Reconstruct kernel [{error_logger,tty}]
DEBUG: Reconstruct stdlib []
DEBUG: No processes to kill
ERROR: One or more eunit tests failed.
ERROR: eunit failed while processing /build/1st/erlang-p1-tls-1.0.23: 
rebar_abort
make[1]: *** [/usr/share/dh-rebar/make/dh-rebar.Makefile:138: rebar_eunit] 
Error 1
--- End Message ---
--- Begin Message ---
Source: erlang-p1-tls
Source-Version: 1.0.23-2

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

Debian distribution maintenance software
pp.
Philipp Huebner  (supplier of updated erlang-p1-tls 
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, 27 Aug 2018 16:50:14 +0200
Source: erlang-p1-tls
Binary: erlang-p1-tls
Architecture: source amd64
Version: 1.0.23-2
Distribution: unstable
Urgency: medium
Maintainer: Ejabberd Packaging Team 
Changed-By: Philipp Huebner 
Description:
 erlang-p1-tls - native TLS / SSL driver for Erlang / Elixir
Closes: 907055
Changes:
 erlang-p1-tls (1.0.23-2) unstable; urgency=medium
 .
   * Added support for OpenSSL 1.1.1 (Closes: #907055)
   * Updated Standards-Version: 4.2.0 (no changes needed)
Checksums-Sha1:
 cefed68ce70a674eee942e8ca2a2a3bcb31e68a8 2124 erlang-p1-tls_1.0.23-2.dsc
 1631d7a7f57f4fdb01eac0e442b1bf6d2c81a17c 9540 
erlang-p1-tls_1.0.23-2.debian.tar.xz
 4d7dd3aa20555c50058f9388edf29c01e0d89a87 37688 
erlang-p1-tls-dbgsym_1.0.23-2_amd64.deb
 d647fca693c505228dc7ed8537305dc1f8dee6e2 9738 
erlang-p1-tls_1.0.23-2_amd64.buildinfo
 21050cf0cc8f45a0c70b629156ee99bfa22cf3e7 43136 erlang-p1-tls_1.0.23-2_amd64.deb
Checksums-Sha256:
 ce166a4632bbb8645df1fd59a1364ca9710ebb90bee5fdc3387689b16f9899c5 2124 
erlang-p1-tls_1.0.23-2.dsc
 0b4d226bf2a4cb7f01e99fa468c8f2f50f29c9ec34c9619b2c7cdde264dc4612 9540 
erlang-p1-tls_1.0.23-2.debian.tar.xz
 6abd246461db95808159b84ef03e8de6f8538b8e8d0c71ffba111c721b6f9912 37688 
erlang-p1-tls-dbgsym_1.0.23-2_amd64.deb
 6825f5c6932e2cd96709d1b84d6c9312fcf94d30b7bbb8cd3ccfb12b181e12bc 9738 
erlang-p1-tls_1.0.23-2_amd64.buildinfo
 b0cef68520f1b8743ac0f8d23cd9d74009a08ee4bf4948fddd90d0201cd0af38 43136 
erlang-p1-tls_1.0.23-2_amd64.deb
Files:
 63bd13b52fb8719fd6c3cd8f9f94bdb4 2124 libs optional erlang-p1-tls_1.0.23-2.dsc
 b6a5bf7b274f12991ffe817e2bf0a16f 9540 libs optional 
erlang-p1-tls_1.0.23-2.debian.tar.xz
 91a7be3bf31e16f18dcb437a1211ca

Bug#906781: marked as done (libpodofo: FTBFS in buster/sid (Error copying directory))

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 15:34:42 +
with message-id 
and subject line Bug#906781: fixed in libpodofo 0.9.5-10
has caused the Debian Bug report #906781,
regarding libpodofo: FTBFS in buster/sid (Error copying directory)
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.)


-- 
906781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libpodofo
Version: 0.9.5-9
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules binary-arch
dh binary-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
-DWANT_FONTCONFIG:BOOL=TRUE \
-DWANT_BOOST:BOOL=1 \
-DPODOFO_BUILD_SHARED:BOOL=TRUE \
-DPODOFO_BUILD_STATIC:BOOL=FALSE \

install -d obj-x86_64-linux-gnu
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DWANT_FONTCONFIG:BOOL=TRUE -DWANT_BOOST:BOOL=1 
-DPODOFO_BUILD_SHARED:BOOL=TRUE -DPODOFO_BUILD_STATIC:BOOL=FALSE ..

[... snipped ...]

make -f test/ParserTest/CMakeFiles/ParserTest.dir/build.make 
test/ParserTest/CMakeFiles/ParserTest.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 53%] Building CXX object 
test/ParserTest/CMakeFiles/ParserTest.dir/ParserTest.cpp.o
cd /<>/obj-x86_64-linux-gnu/test/ParserTest && /usr/bin/c++   
-I/<>/obj-x86_64-linux-gnu -I/<> 
-I/usr/include/x86_64-linux-gnu -I/usr/include/cppunit -I/usr/include/lua5.1 
-I/<>/src -I/usr/include/freetype2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-Woverloaded-virtual -Wswitch-enum -Wcast-qual -Wwrite-strings 
-Wredundant-decls -Wreorder -Wno-deprecated-declarations   -W -o 
CMakeFiles/ParserTest.dir/ParserTest.cpp.o -c 
/<>/test/ParserTest/ParserTest.cpp
[ 54%] Linking CXX executable ParserTest
cd /<>/obj-x86_64-linux-gnu/test/ParserTest && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/ParserTest.dir/link.txt --verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Woverloaded-virtual -Wswitch-enum -Wcast-qual 
-Wwrite-strings -Wredundant-decls -Wreorder -Wno-deprecated-declarations  
-Wl,-z,relro -Wl,-z,now -rdynamic CMakeFiles/ParserTest.dir/ParserTest.cpp.o  
-o ParserTest  -L/<>/obj-x86_64-linux-gnu/src 
-Wl,-rpath,/<>/obj-x86_64-linux-gnu/src -lpodofo -lfontconfig 
-lfreetype -lz -lidn -lcrypto -lcrypto -ljpeg -lpthread -lfreetype -lpng -lz 
-ltiff -lidn -lcrypto -lcrypto -ljpeg -lpthread -lfreetype -lpng -ltiff 
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[ 54%] Built target ParserTest
make -f test/SignatureTest/CMakeFiles/SignatureTest.dir/build.make 
test/SignatureTest/CMakeFiles/SignatureTest.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/test/SignatureTest 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/test/SignatureTest 
/<>/obj-x86_64-linux-gnu/test/SignatureTest/CMakeFiles/SignatureTest.dir/DependInfo.cmake
 --color=
Scanning dependencies of target SignatureTest
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f test/SignatureTest/CMakeFiles/SignatureTest.dir/build.make 
test/SignatureTest/CMakeFiles/SignatureTest.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 54%] Building CXX object 
test/SignatureTest/CMakeFiles/SignatureTest.dir/SignTest.cpp.o
cd /<>/obj-x86_64-linux-gnu/test/SignatureTest && /usr/bin/c++   
-I/<>/obj-x86_64-linux-gnu -I/<> 
-I/usr/include/x86_64-linux-gnu -I/usr/include/cppunit -I/usr/include/lua5.1 
-I/<>/src -I/usr/include/freetype2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-Woverloaded-virtual -Wswitch-enum -Wcast-qual -Wwrite-strings 
-Wredundant-decls -Wreorder -Wno-deprecated-declarations   -W -o 
CMakeFiles/SignatureTest.dir/SignTest.cpp.o -c 
/<>/test/SignatureTest/SignTest.cpp
[ 55%] Linking CXX executable SignatureTest
cd /<>/o

Bug#907403: opam-installer: missing Replaces: opam-doc (<< 2.0.0-1)

[Adrian Bunk]

Package: opam-installer
Version: 2.0.0-1
Severity: serious

Unpacking opam-installer (2.0.0-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-KfKgI6/4-opam-installer_2.0.0-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man1/opam-installer.1.gz', which is also 
in package opam-docs 1.2.2-7

Bug#907404: klibc FTBFS on i386: ld: discarded output section: `.got.plt'

[Adrian Bunk]

Source: klibc
Version: 2.0.4-14
Severity: serious
Tags: ftbfs

Some recent change in unstable makes klibc FTBFS on i386:

https://tests.reproducible-builds.org/debian/history/klibc.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/klibc.html

...
  ld -m elf_i386 -o usr/kinit/ipconfig/static/ipconfig  
usr/klibc/arch/i386/crt0.o --start-group  usr/kinit/ipconfig/main.o 
usr/kinit/ipconfig/netdev.o usr/kinit/ipconfig/packet.o 
usr/kinit/ipconfig/dhcp_proto.o usr/kinit/ipconfig/bootp_proto.o  
usr/klibc/libc.a /usr/lib/gcc/i686-linux-gnu/8/libgcc.a --end-group ; cp -f 
usr/kinit/ipconfig/static/ipconfig usr/kinit/ipconfig/static/ipconfig.g ; strip 
--strip-all -R .comment -R .note --strip-all -R .comment -R .note --strip-all 
-R .comment -R .note usr/kinit/ipconfig/static/ipconfig
  ld -m elf_i386 -o usr/kinit/ipconfig/shared/ipconfig  -e main 
usr/klibc/interp.o --start-group  usr/kinit/ipconfig/main.o 
usr/kinit/ipconfig/netdev.o usr/kinit/ipconfig/packet.o 
usr/kinit/ipconfig/dhcp_proto.o usr/kinit/ipconfig/bootp_proto.o  -R 
usr/klibc/libc.so /usr/lib/gcc/i686-linux-gnu/8/libgcc.a --end-group ; cp -f 
usr/kinit/ipconfig/shared/ipconfig usr/kinit/ipconfig/shared/ipconfig.g ; strip 
--strip-all -R .comment -R .note --strip-all -R .comment -R .note --strip-all 
-R .comment -R .note usr/kinit/ipconfig/shared/ipconfig
ld: discarded output section: `.got.plt'
make[5]: *** [/build/1st/klibc-2.0.4/scripts/Kbuild.klibc:357: 
usr/kinit/ipconfig/shared/ipconfig] Error 1

Bug#907171: prometheus FTBFS:

[Adrian Bunk]

On Mon, Aug 27, 2018 at 03:27:07PM +0100, Martín Ferrari wrote:
> Adrian,

Hi Martín,

> On 24/08/18 13:47, Adrian Bunk wrote:
> 
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prometheus.html
> > 
> > ...
> > panic: Can't start web handler:listen tcp :9090: bind: address already in 
> > use
> 
> This is a known problem when running the autopkgtests, becasue the
> installed package starts the daemon and then the tests fail when trying
> to use the same port; but this is not a FTBFS: the build daemons do not
> fail to build from source. I think you should lower the severity.

I am not talking about autopkgtests, I am talking about a FTBFS I was
able to reproduce locally.

But retrying a few more times, this might actually be a flaky test?

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

Bug#907171: prometheus FTBFS:

[Martín Ferrari]

Santiago,

On 27/08/18 16:00, Santiago Vila wrote:

>> This is a known problem when running the autopkgtests, becasue the
>> installed package starts the daemon and then the tests fail when trying
>> to use the same port; but this is not a FTBFS: the build daemons do not
>> fail to build from source. I think you should lower the severity.
> 
> Tincho, if we go that route we would be applying a definition for FTBFS
> which would be different from everybody else.

> A FTBFS could be defined as a non-zero exit status from
> dpkg-buildpackage. If you include the test suite as part of the build,
> then a failure in the test suite will naturally mean a FTBFS bug, for
> all purposes.

Yes, but this is not what is happening: the build only fails if
prometheus is already running in the machine, which is the case for
autopkgtest, but not for a normal build. I plan to fix this, but I need
to find a general fix for all go packages that include a daemon.

Look at the buildd logs, there are no failures (except i386, which is
known not to work):
https://buildd.debian.org/status/package.php?p=prometheus

> If, as you explain, the tests are not suitable to be run after
> dh_auto_build, then it follows that they should be disabled from the
> package build, because we don't want dpkg-buildpackage to exit with
> error. In such case, just an empty debian/rules target like this:
If you run dpkg-buildpackage in a clean chroot, it does not fail: I have
just checked again; so this bug is not RC. There are a few other go
packages that fail autopkgtests for the exact same reason, please do not
open FTBFS bugs without actually trying to build the package.

-- 
Martín Ferrari (Tincho)

Bug#907171: prometheus FTBFS:

[Martín Ferrari]

On 27/08/18 16:51, Adrian Bunk wrote:

>>> panic: Can't start web handler:listen tcp :9090: bind: address
already in use

> I am not talking about autopkgtests, I am talking about a FTBFS I was
> able to reproduce locally.
> 
> But retrying a few more times, this might actually be a flaky test?

I have not seen this error before, I can only imagine you had some old
process lying around, or somehow the port was still in use? Otherwise,
it must be some concurrency issue, but as I said, I have not been able
to reproduce this.

-- 
Martín Ferrari (Tincho)

Bug#907407: openmpi: arpack builds on i386 and armhf time out

[Graham Inggs]

Source: openmpi
Version: 3.1.1.real-6
Severity: serious

Hi Alastair

Recent reproducible builds of arpack have timed out on i386 [1] and
armhf [2].  From the dates of previous builds, it appears that builds
against openmpi 3.1.1.real-4 were successful.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/history/i386/arpack.html
[2] https://tests.reproducible-builds.org/debian/history/armhf/arpack.html

Processed: gemma autopkgtest fails: cannot stat '/usr/share/doc/gemma-doc/example/*'

[Debian Bug Tracking System]

Processing control commands:

> block 904854 by -1
Bug #904854 {Done: Andreas Tille } [src:gemma] gemma ftbfs in 
unstable (test failures and libquadmath not available on all architectures)
Warning: Unknown package 'src:gemma'
904854 was not blocked by any bugs.
904854 was not blocking any bugs.
Added blocking bug(s) of 904854: 907406
Warning: Unknown package 'src:gemma'
Warning: Unknown package 'src:gemma'

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

Bug#907171: prometheus FTBFS:

[Adrian Bunk]

On Mon, Aug 27, 2018 at 04:57:49PM +0100, Martín Ferrari wrote:
> On 27/08/18 16:51, Adrian Bunk wrote:
> 
> >>> panic: Can't start web handler:listen tcp :9090: bind: address
> already in use
> 
> > I am not talking about autopkgtests, I am talking about a FTBFS I was
> > able to reproduce locally.
> > 
> > But retrying a few more times, this might actually be a flaky test?
> 
> I have not seen this error before, I can only imagine you had some old
> process lying around, or somehow the port was still in use? Otherwise,
> it must be some concurrency issue, but as I said, I have not been able
> to reproduce this.

How often did you try?

I would say the probability to hit is somewhere around 50%:
https://tests.reproducible-builds.org/debian/history/prometheus.html

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

Bug#906349: [Pkg-pascal-devel] Bug#906349: Bug#906349: Bug#906349: doublecmd: FTBFS in buster/sid (tries to write in /usr)

[Abou Al Montacir]

Hi Graham,

On Thu, 2018-08-23 at 15:33 +0200, Graham Inggs wrote:
> Hi Abou
> 
> On 17/08/2018 18:37, Graham Inggs wrote:
> > Abou, do you have an opinion on whether this is a bug in lazarus, or
> > does the doublecmd packaging need to be fixed?
I just returned back from vacation, let me check this.
> The same problem occurs in ddrescueview, reported in #906458.
Seems strange
> I found it was introduced by the changes to debian/rules in this commit 
> 'Stop adding manually compiled flag from packages' [1].
That one was proposed to solve a lazarus IDE rebuild issue. I don't like it as I
tend to think that units shall be compiled only once and not every time. However
the way upstream sees Lazarus distribution is  the opposite. I don't see a
better way to fix it.
> Both doublecmd and ddrescueview build successfully if lazarus-src is 
> added as a build-dependency.
This means that we are missing some PPU/LPK files to be distributed or maybe we
are trying to recompile some units and missing some include files.
One needs to add -va and look carefully to the log file.
>   Is this change in behaviour intentional? 
Somewhat as it was fixing bug#898310
> Should I make these changes to doublecmd and ddrescueview, or is this a 
> bug in lazarus?
Maybe we shall think more about this change. Removing the manually flag leads to
a deeper question: Do we need to distribute LCL units in binary form if they
will get recompiled anyway?
> Regards
> Graham
> 
> 
> [1] 
> https://salsa.debian.org/pascal-team/lazarus/commit/eb89bf37af1b42215811c132fd
> fc919f19126952

-- 
Cheers,
Abou Al Montacir

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

Processed: openmpi: arpack builds on i386 and armhf time out

[Debian Bug Tracking System]

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

> affects 907407 + src:arpack
Bug #907407 [src:openmpi] openmpi: arpack builds on i386 and armhf time out
Added indication that 907407 affects src:arpack
> thanks
Stopping processing here.

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

Bug#906158: intel-microcode: Update intel-microcode to 20180807

[Henrique de Moraes Holschuh]

On Mon, 27 Aug 2018, Darius Spitznagel wrote:
> today I've installed intel-microcode (3.20180807a.1~bpo9+1) from 
> stretch-backports to realize that firmware file "06-2c-02" is missing.

Refer to bug #907402
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907402

-- 
  Henrique Holschuh

Processed: bug 907231 is forwarded to https://cgit.kde.org/ktp-contact-list.git/commit/?id=7110886 ...

[Debian Bug Tracking System]

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

> forwarded 907231 https://cgit.kde.org/ktp-contact-list.git/commit/?id=7110886
Bug #907231 [src:ktp-contact-list] ktp-contact-list: FTBFS with Qt 5.11
Set Bug forwarded-to-address to 
'https://cgit.kde.org/ktp-contact-list.git/commit/?id=7110886'.
> tags 907231 + fixed-upstream patch
Bug #907231 [src:ktp-contact-list] ktp-contact-list: FTBFS with Qt 5.11
Added tag(s) patch and fixed-upstream.
> thanks
Stopping processing here.

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

Processed: bug 907229 is forwarded to https://cgit.kde.org/kdesvn.git/commit/?id=f4ec3ee, tagging 907229

[Debian Bug Tracking System]

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

> forwarded 907229 https://cgit.kde.org/kdesvn.git/commit/?id=f4ec3ee
Bug #907229 [src:kdesvn] kdesvn: FTBFS with Qt 5.11
Set Bug forwarded-to-address to 
'https://cgit.kde.org/kdesvn.git/commit/?id=f4ec3ee'.
> tags 907229 + fixed-upstream patch
Bug #907229 [src:kdesvn] kdesvn: FTBFS with Qt 5.11
Added tag(s) fixed-upstream and patch.
> thanks
Stopping processing here.

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

Processed: bug 907228 is forwarded to https://cgit.kde.org/kaffeine.git/commit/?id=06b78c5, tagging 907228

[Debian Bug Tracking System]

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

> forwarded 907228 https://cgit.kde.org/kaffeine.git/commit/?id=06b78c5
Bug #907228 [src:kaffeine] kaffeine: FTBFS with Qt 5.11
Set Bug forwarded-to-address to 
'https://cgit.kde.org/kaffeine.git/commit/?id=06b78c5'.
> tags 907228 + fixed-upstream patch
Bug #907228 [src:kaffeine] kaffeine: FTBFS with Qt 5.11
Added tag(s) fixed-upstream and patch.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package cyrus-imapd

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package cyrus-imapd
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #863520 (http://bugs.debian.org/863520)
> # Bug title: cyrus-imapd version 2.5.10-3 Fatal error with SSL
> #  * https://github.com/cyrusimap/cyrus-imapd/issues/1872
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 863520 + fixed-upstream
Bug #863520 [cyrus-imapd] cyrus-imapd version 2.5.10-3 Fatal error with SSL
Added tag(s) fixed-upstream.
> usertags 863520 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#907226: cutesdr: FTBFS with Qt 5.11

[Reiner Herrmann]

Control: tags -1 + patch

Hi,

the attached patch fixes the FTBFS by including the missing header.

Regards,
  Reiner
diff -Nru cutesdr-1.20/debian/patches/qt5.11.patch cutesdr-1.20/debian/patches/qt5.11.patch
--- cutesdr-1.20/debian/patches/qt5.11.patch	1970-01-01 01:00:00.0 +0100
+++ cutesdr-1.20/debian/patches/qt5.11.patch	2018-05-21 06:26:20.0 +0200
@@ -0,0 +1,14 @@
+Author: Reiner Herrmann 
+Description: Fix build failure with Qt 5.11 by including missing header
+Bug-Debian: https://bugs.debian.org/907226
+
+--- a/gui/ipeditwidget.h
 b/gui/ipeditwidget.h
+@@ -9,6 +9,7 @@
+ #define IPEDITWIDGET_H
+ 
+ #include 
++#include 
+ #include "ui_ipeditframe.h"
+ 
+ class CIPEditWidget : public QFrame
diff -Nru cutesdr-1.20/debian/patches/series cutesdr-1.20/debian/patches/series
--- cutesdr-1.20/debian/patches/series	2018-05-21 06:26:20.0 +0200
+++ cutesdr-1.20/debian/patches/series	2018-05-21 06:26:20.0 +0200
@@ -7,3 +7,4 @@
 file-send-for-unix
 fsk-radio-button-for-unix
 siqs-ftdi1
+qt5.11.patch


signature.asc
Description: PGP signature

Processed: Re: cutesdr: FTBFS with Qt 5.11

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #907226 [src:cutesdr] cutesdr: FTBFS with Qt 5.11
Added tag(s) patch.

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

Processed: bug 907162 is forwarded to https://github.com/KDE/step/commit/f045cfa, tagging 907162

[Debian Bug Tracking System]

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

> forwarded 907162 https://github.com/KDE/step/commit/f045cfa
Bug #907162 [src:step] step: FTBFS in buster/sid (invalid use of incomplete 
type 'class QItemSelectionModel')
Set Bug forwarded-to-address to 'https://github.com/KDE/step/commit/f045cfa'.
> tags 907162 + patch fixed-upstream
Bug #907162 [src:step] step: FTBFS in buster/sid (invalid use of incomplete 
type 'class QItemSelectionModel')
Added tag(s) patch and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#903525: marked as done (python3-dropbox fails to install with Python 3.7 as supported version)

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 17:53:29 +
with message-id 
and subject line Bug#903525: fixed in python-dropbox 9.0.0-1
has caused the Debian Bug report #903525,
regarding python3-dropbox fails to install with Python 3.7 as supported version
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.)


-- 
903525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-dropbox
Version: 8.7.1-1
Severity: grave
Control: block 902788 by -1

Setting up python3-dropbox (8.7.1-1) ...
  File "/usr/lib/python3/dist-packages/dropbox/base.py", line 10
async,
^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/dropbox/base_team.py", line 10
async,
^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/dropbox/files.py", line 21
async,
^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/dropbox/sharing.py", line 21
async,
^
SyntaxError: invalid syntax

  File "/usr/lib/python3/dist-packages/dropbox/team.py", line 17
async,
^
SyntaxError: invalid syntax

dpkg: error processing package python3-dropbox (--configure):
 installed python3-dropbox package post-installation script subprocess returned 
--- End Message ---
--- Begin Message ---
Source: python-dropbox
Source-Version: 9.0.0-1

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

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

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

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated python-dropbox 
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, 27 Aug 2018 19:25:58 +0200
Source: python-dropbox
Binary: python3-dropbox
Architecture: source all
Version: 9.0.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Description:
 python3-dropbox - Official Dropbox API Client (Python3 version)
Closes: 903525
Changes:
 python-dropbox (9.0.0-1) unstable; urgency=low
 .
   [ Ondřej Nový ]
   * d/control: Remove ancient X-Python3-Version field
 .
   [ Michael Fladischer ]
   * New upstream release (Closes: #903525).
   * Set d/watch to use github release tarballs.
   * Clean up files in dropbox.egg-info/ to allow two builds in a row.
   * Bump Standards-Version to 4.2.1.
Checksums-Sha1:
 cee6f766d9cfcde0c73782ea0104fe360ac64e6e 1777 python-dropbox_9.0.0-1.dsc
 c3e6a22cc454f3f9c28b7842aafcf6b064082fe3 1042611 
python-dropbox_9.0.0.orig.tar.gz
 ad1bb8895dbb2f2277244ea306be4b72a91a977c 2564 
python-dropbox_9.0.0-1.debian.tar.xz
 cacc34cfaf15e4244b2563de6231f0b7e0559d86 6990 
python-dropbox_9.0.0-1_amd64.buildinfo
 f61824114da418eddca7b206fcf06c998ed79ae5 336436 python3-dropbox_9.0.0-1_all.deb
Checksums-Sha256:
 3999650412a9418d7fd85abdcb3a0c10f601bb085eaca84247f5d2293cf92951 1777 
python-dropbox_9.0.0-1.dsc
 2ea1def06b34903add26f66d1b9f204410a708630004d2e6be011799cc442376 1042611 
python-dropbox_9.0.0.orig.tar.gz
 b3b57adbb2c2bf5e68998bf84e531676fe40c58c186aedf7a2b3239659079420 2564 
python-dropbox_9.0.0-1.debian.tar.xz
 5edd3306eca4419ea1d87861d2b69160fe2cd78b05c4aacdd1e2a2f67b1be734 6990 
python-dropbox_9.0.0-1_amd64.buildinfo
 f7ba63e5ccd6cd5a6d42a45025f5588030c04131fdb0005dfaea474162aa0f66 336436 
python3-dropbox_9.0.0-1_all.deb
Files:
 dff5c69828f6de4a7af3ad7b200da1a4 1777 python optional 
python-dropbox_9.0.0-1.dsc
 d32d5e798b635ea8ef151c5a0d137ff6 1042611 python optional 
python-dropbox_9.0.0.orig.tar.gz
 03f53e09802215e37cbc86c9cab9865b 2564 python optional 
python-dropbox_9.0.0-1.debian.tar.xz
 63baa6b65986ec66e7a236f3f5e6afb5 6990 python optional 
python-dropbox_9.0.0-1_amd64.buildinfo
 9c18c87abcd5de896ee4693a9dc70851 336436 python optional 
python3-dropbox_9.0.0-1_all.deb

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAluENUgACgkQ/9PIi5l9
0WqRBgf/fzniWFd/Yaq+GPI2pwaOpuT3hgEy8Vr2CNxz5plIYmFshCXwqhBbPZJk
d36eDHMr5wfcDQ0q9njWNNUFYlZ136mzjqwNfHlMPLEohzVC40RuqU2RxrJFzmIx
NQtfS6hagwf/Jh8xUZivDfhhsZWAFrsBAi/OIYJ7W6L5DCSgvvBY0gnTfeCPd

Processed: bug 907161 is forwarded to https://github.com/rncbc/qtractor/commit/b49da1c, tagging 907161

[Debian Bug Tracking System]

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

> forwarded 907161 https://github.com/rncbc/qtractor/commit/b49da1c
Bug #907161 [src:qtractor] qtractor: FTBFS in buster/sid (incomplete type 
'QAction' used in nested name specifier)
Set Bug forwarded-to-address to 
'https://github.com/rncbc/qtractor/commit/b49da1c'.
> tags 907161 + patch fixed-upstream
Bug #907161 [src:qtractor] qtractor: FTBFS in buster/sid (incomplete type 
'QAction' used in nested name specifier)
Added tag(s) fixed-upstream and patch.
> thanks
Stopping processing here.

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

Bug#907411: pcsx2 FTBFS with gcc 8

[Adrian Bunk]

Source: pcsx2
Version: 1.4.0+dfsg-2
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/pcsx2.html

...
In file included from /usr/lib/gcc/i686-linux-gnu/8/include/x86intrin.h:74,
 from 
/build/1st/pcsx2-1.4.0+dfsg/common/src/x86emitter/cpudetect.cpp:19:
/usr/lib/gcc/i686-linux-gnu/8/include/xsaveintrin.h:60:1: error: ambiguating 
new declaration of 'long long int _xgetbv(unsigned int)'
 _xgetbv (unsigned int __A)
 ^~~
In file included from /build/1st/pcsx2-1.4.0+dfsg/common/include/Pcsx2Defs.h:31,
 from 
/build/1st/pcsx2-1.4.0+dfsg/common/src/x86emitter/PrecompiledHeader.h:23,
 from 
/build/1st/pcsx2-1.4.0+dfsg/common/src/x86emitter/cpudetect.cpp:16:
/build/1st/pcsx2-1.4.0+dfsg/common/include/intrin_x86.h:107:69: note: old 
declaration 'long long unsigned int _xgetbv(unsigned int)'
 static __inline__ __attribute__((always_inline)) unsigned long long 
_xgetbv(unsigned int index)
 ^~~

Bug#907171: prometheus FTBFS:

[Martín Ferrari]

On 27/08/18 17:08, Adrian Bunk wrote:

> How often did you try?
> 
> I would say the probability to hit is somewhere around 50%:
> https://tests.reproducible-builds.org/debian/history/prometheus.html

I just tried 20 builds, while using desktop applications that put some
extra strain on tHE CPU, and none failed..


-- 
Martín Ferrari (Tincho)

Bug#869951: marked as done (webdis: FTBFS with libevent 2.1.x)

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 18:22:11 +
with message-id 
and subject line Bug#869951: fixed in webdis 0.1.4+dfsg-1
has caused the Debian Bug report #869951,
regarding webdis: FTBFS with libevent 2.1.x
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.)


-- 
869951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: webdis
Version: 0.1.2+dfsg-2
Severity: important
User: rbal...@ubuntu.com
Usertags: libevent-20170726


Dear Maintainer,

During test rebuilds for the upcoming libevent transition [1] your package found
to be failing to build [2] with libevent-dev 2.1.8-stable-2 from experimental:

...
Ran 22 tests in 0.015s

OK
python tests/limits.py
..
--
Ran 2 tests in 64.121s

OK
./tests/pubsub -p 48262

1 %
2 %
E: Build killed with signal TERM after 150 minutes of inactivity

Build finished at 2017-06-29T10:01:37Z
...

Cheers,
Balint

[1] https://release.debian.org/transitions/html/auto-libevent.html
[2] 
https://people.debian.org/~rbalint/build-logs/libevent-20170726/webdis_0.1.2+dfsg-2

-- 
Balint Reczey
Debian & Ubuntu Developer
--- End Message ---
--- Begin Message ---
Source: webdis
Source-Version: 0.1.4+dfsg-1

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

Debian distribution maintenance software
pp.
Andrii Senkovych  (supplier of updated webdis package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 Aug 2018 15:30:36 +0300
Source: webdis
Binary: webdis
Architecture: source
Version: 0.1.4+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Andrii Senkovych 
Changed-By: Andrii Senkovych 
Description:
 webdis - simple web server providing an HTTP interface to Redis
Closes: 869951 901555
Changes:
 webdis (0.1.4+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 0.1.4+dfsg
   * d/control, d/copyright: update maintainers email and proper name spelling.
   * Raise compat level to 11.
   * d/control: remove explicit *-dbg package definition.
   * d/control: bump Standards-Version to 4.2.0.
   * d/control: update Vcs-* fields to point to salsa.d.o.
   * d/control: add Rules-Requires-Root header set to no.
   * d/control: add direct build dependency on pkg-config.
   * d/webdis.install: no need to explicitly install webdis binary.
   * d/rules: remove DESTDIR and CONFDIR vars setup by hand.
   * d/rules: avoid installing webdis.prod.json from upstream.
   * d/control, d/rules: remove trailing whitespace.
   * d/control: remote unnecessary Testsuite header.
   * d/copyright: use https protocol.
   * Add systemd service configuration.
   * d/patches/fix-test-new-libevent.patch: fix pubsub test when compiled w/
 libevent 2.1.x. (Closes: #869951, #901555)
   * d/rules: use /usr/share/dpkg/buildflags.mk to populate build flags.
   * Fix lintian typo check
Checksums-Sha1:
 1025d1cc501528de06afbd59815f6b4a2efd2077 2129 webdis_0.1.4+dfsg-1.dsc
 8593d8422586ce42db8c873c3df0a816ce5673fc 59571 webdis_0.1.4+dfsg.orig.tar.gz
 2fcae1408db46363f748843437f2e1c1436de883 12296 
webdis_0.1.4+dfsg-1.debian.tar.xz
 49ee9ddaac518347bae817ce977be7b9c7143f58 7100 
webdis_0.1.4+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 baf84e17234ca11a6bc98b5a978c91e8450fafd30cc41d78e543c204cd09cc89 2129 
webdis_0.1.4+dfsg-1.dsc
 8e606ea67f9dbd6b7e2d2c7d9fda3b7249dd1aa0e56ad125ae1d061365ea29c2 59571 
webdis_0.1.4+dfsg.orig.tar.gz
 f22b0653dc327baf484bf6abd8f4060d1e23159ca2ed50553ed30afe68392014 12296 
webdis_0.1.4+dfsg-1.debian.tar.xz
 73b11a9fae6d3dac6b28cef73e682e7d442c5a8be4abbf17830a44a935095ec1 7100 
webdis_0.1.4+dfsg-1_amd64.buildinfo
Files:
 81487426ff3a81bc173a0be49181f5d1 2129 web optional webdis_0.1.4+dfsg-1.dsc
 3e2927e3b332ea60e660d1a3fde0ffe2 59571 web optional 
webdis_0.1.4+dfsg.orig.tar.gz
 3afe4868812bafd78d06de4bc9adf23e 12296 web optional 
webdis_0.1.4+dfsg-1.debian.tar.xz
 07e6e29b0c58078c1f2dcbcd

Processed: Re: affects 907015

[Debian Bug Tracking System]

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

> affects 907015 - libio-socket-ssl-perl -
Bug #907015 [src:openssl] openssl version 1.1.1 breaks multiple reverse 
dependencies; versioned Breaks needed
Removed indication that 907015 affects libio-socket-ssl-perl and -
> thanks
Stopping processing here.

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

Bug#907411: pcsx2 FTBFS with gcc 8

[Juhani Numminen]

On Mon, 27 Aug 2018 20:55:56 +0300 Adrian Bunk  wrote:
> Source: pcsx2
> Version: 1.4.0+dfsg-2
> Severity: serious
> Tags: ftbfs
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/pcsx2.html
> 
> ...
> In file included from /usr/lib/gcc/i686-linux-gnu/8/include/x86intrin.h:74,
>  from 
> /build/1st/pcsx2-1.4.0+dfsg/common/src/x86emitter/cpudetect.cpp:19:
> /usr/lib/gcc/i686-linux-gnu/8/include/xsaveintrin.h:60:1: error: ambiguating 
> new declaration of 'long long int _xgetbv(unsigned int)'
>  _xgetbv (unsigned int __A)
>  ^~~
> In file included from 
> /build/1st/pcsx2-1.4.0+dfsg/common/include/Pcsx2Defs.h:31,
>  from 
> /build/1st/pcsx2-1.4.0+dfsg/common/src/x86emitter/PrecompiledHeader.h:23,
>  from 
> /build/1st/pcsx2-1.4.0+dfsg/common/src/x86emitter/cpudetect.cpp:16:
> /build/1st/pcsx2-1.4.0+dfsg/common/include/intrin_x86.h:107:69: note: old 
> declaration 'long long unsigned int _xgetbv(unsigned int)'
>  static __inline__ __attribute__((always_inline)) unsigned long long 
> _xgetbv(unsigned int index)

This might be relevant:

"common: Use GCC's _xgetbv definition from GCC 8.2 onwards
The _xgetbv bug was fixed, so avoid using our own definition (again)."
https://github.com/PCSX2/pcsx2/commit/e8ed18febaa046a3383a4b960517372a5bc554d1


Regards,
Juhani

Bug#907414: twitter-bootstrap3: CVE-2018-14040 CVE-2018-14041 CVE-2018-14042

[Antoine Beaupre]

Package: twitter-bootstrap3
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for twitter-bootstrap3.

CVE-2018-14040[0]:
| In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent
| attribute.

CVE-2018-14041[1]:
| In Bootstrap before 4.1.2, XSS is possible in the data-target property
| of scrollspy.

CVE-2018-14042[2]:
| In Bootstrap before 4.1.2, XSS is possible in the data-container
| property of tooltip.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-14040
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14040
[1] https://security-tracker.debian.org/tracker/CVE-2018-14041
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14041
[2] https://security-tracker.debian.org/tracker/CVE-2018-14042
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14042

Please adjust the affected versions in the BTS as needed.

-- 


signature.asc
Description: PGP signature

Bug#907332: ghostscript has a new code execution issue, even when used with -dSAFER

[Jonas Smedegaard]

Quoting Salvatore Bonaccorso (2018-08-26 21:55:14)
> Hi,
> 
> On Sun, Aug 26, 2018 at 06:08:58PM +0100, Nicolas Braud-Santoni wrote:
> > Tavis Ormandy disclosed a new ghoscript security issue, leading directly to 
> > code
> > execution:  http://openwall.com/lists/oss-security/2018/08/21/2
> 
> There are actually several issues, see the whole thread. For now since
> you filled this bug will track all those with this bug entry. Proper
> evaluation though is still pending (and Moritz is taking care of
> strech, adding this note to dsa-needed file ("needs some research on
> issues found by Tavis").
> 
> See
> 
> https://www.kb.cert.org/vuls/id/332928
> 
> the current set of fixes:
> 
> http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=b575e1ec
> http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=8e9ce501
> http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=241d9111
> http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=c432131c
> http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=e01e77a3
> http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=0edd3d6c
> http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=a054156d
> http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=0d390118
> http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=c3476dde
> http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=b326a716
> http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=78911a01
> http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=5516c614

Also http://git.ghostscript.com/?p=ghostpdl.git;h=0b6cd19


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#906230: marked as done (insighttoolkit4-python: missing python dependencies)

[Debian Bug Tracking System]

Your message dated Mon, 27 Aug 2018 18:34:35 +
with message-id 
and subject line Bug#906230: fixed in insighttoolkit4 4.12.2-dfsg1-3
has caused the Debian Bug report #906230,
regarding insighttoolkit4-python: missing python dependencies
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.)


-- 
906230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: insighttoolkit4-python
Version: 4.10.1-dfsg1-1.1
Severity: serious
Tags: patch

Fix:

--- debian/control.in.old   2018-08-13 12:46:42.486599767 +
+++ debian/control.in   2018-08-14 08:11:49.018243996 +
@@ -21,6 +21,7 @@
 libminc-dev, 
 libnifti-dev, 
 libhdf5-dev, 
+dh-python,
 python-all-dev
 #  libvtk6-dev -- only needed if we enable one of the following modules:
 # VtkGlue, LevelSetsv4Visualization
@@ -90,7 +91,7 @@
 Package: insighttoolkit@VER_MAJOR@-python 
 Section: python 
 Architecture: amd64 i386
-Depends: ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}, ${python:Depends}
 Conflicts: insighttoolkit-python
 Replaces: insighttoolkit-python
 Description: Image processing toolkit for registration and segmentation - 
Python bindings
--- debian/control.old  2018-08-12 22:39:53.179084322 +
+++ debian/control  2018-08-14 08:11:37.626244105 +
@@ -21,6 +21,7 @@
libminc-dev, 
 libnifti-dev, 
libhdf5-dev, 
+   dh-python,
python-all-dev
 #  libvtk6-dev -- only needed if we enable one of the following modules:
 # VtkGlue, LevelSetsv4Visualization
@@ -90,7 +91,7 @@
 Package: insighttoolkit4-python 
 Section: python 
 Architecture: amd64 i386
-Depends: ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}, ${python:Depends}
 Conflicts: insighttoolkit-python
 Replaces: insighttoolkit-python
 Description: Image processing toolkit for registration and segmentation - 
Python bindings
--- debian/rules.old2018-08-12 22:39:54.667084308 +
+++ debian/rules2018-08-13 12:48:11.170598921 +
@@ -81,7 +81,7 @@
 
 
 %:
-   dh $@ --builddir=BUILD --parallel
+   dh $@ --builddir=BUILD --parallel --with python2
 
 override_dh_auto_configure-indep:
 
--- End Message ---
--- Begin Message ---
Source: insighttoolkit4
Source-Version: 4.12.2-dfsg1-3

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

Debian distribution maintenance software
pp.
Gert Wollny  (supplier of updated insighttoolkit4 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, 27 Aug 2018 20:18:54 +0200
Source: insighttoolkit4
Binary: libinsighttoolkit4.12 libinsighttoolkit4-dev insighttoolkit4-examples 
insighttoolkit4-python
Architecture: source
Version: 4.12.2-dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gert Wollny 
Description:
 insighttoolkit4-examples - Image processing toolkit for registration and 
segmentation - exam
 insighttoolkit4-python - Image processing toolkit for registration and 
segmentation - Pyth
 libinsighttoolkit4-dev - Image processing toolkit for registration and 
segmentation - deve
 libinsighttoolkit4.12 - Image processing toolkit for registration and 
segmentation - runt
Closes: 906230
Changes:
 insighttoolkit4 (4.12.2-dfsg1-3) unstable; urgency=medium
 .
   * d/control*, d/rules: Fix python dependencies, Closes: #906230
Checksums-Sha1:
 bae1c06abfc2f06c986d3ac817b37d86b5e93ad9 2988 
insighttoolkit4_4.12.2-dfsg1-3.dsc
 fcbe5946293238737113ad37d264046f7b38b346 26072 
insighttoolkit4_4.12.2-dfsg1-3.debian.tar.xz
 c2b1337e6c99de4e8e62857889da3cdcc1c93646 10500 
insighttoolkit4_4.12.2-dfsg1-3_source.buildinfo
Checksums-Sha256:
 c03fc667445720263e86cd595dc41f3fe88a6e8ff90d18a7facea8e50a3b87de 2988 
insighttoolkit4_4.12.2-dfsg1-3.dsc
 62b1d1c1f593cfc298010abe58680617cebc947e81b9fa8877032f39553e0786 26072 
insighttoolkit4_4.12.2-dfsg1-3.debian.tar.xz
 b93fc2103439ab1d78bda66b82d58467a78dccf6e003504d076b703e44fee84

Bug#907417: libmems: Wrong library Provides for libraries with different ABI

[Steve Langasek]

Package: libmems
Version: 1.6.0+4725-7
Severity: grave
Tags: patch
Justification: renders package unusable
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu cosmic ubuntu-patch

Dear Andreas,

The latest libmems package builds a libmems1 binary package which declares
'Provides: libmems-1.6-1v5'.  This is completely wrong.  The libmems1
package ships libMems.so.1, and the libmems-1.6-1v5 package shipped
libMems-1.6.so.1.  Declaring Provides: in this way breaks all
reverse-dependencies that were built against previous SONAME (i.e.,
progressivemauve 1.2.0+4713-2 in stable).

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libmems-1.6.0+4725/debian/control libmems-1.6.0+4725/debian/control
--- libmems-1.6.0+4725/debian/control   2018-07-26 23:11:01.0 -0700
+++ libmems-1.6.0+4725/debian/control   2018-08-27 11:54:14.0 -0700
@@ -43,12 +43,6 @@
 Depends: ${shlibs:Depends},
  ${misc:Depends}
 Pre-Depends: ${misc:Pre-Depends}
-Conflicts: libmems-1.6-1,
-   libmems-1.6-1v5
-Provides: libmems-1.6-1,
-  libmems-1.6-1v5
-Replaces: libmems-1.6-1,
-  libmems-1.6-1v5
 Description: library to support DNA string matching and comparative genomics
  libMems is a freely available software development library to support DNA
  string matching and comparative genomics. Among other things, libMems

Processed: Re%3A vala-panel FTBFS%3A CMake Error at util%2FCMakeLists.txt%3A40 %28set_target_properties%29

[Debian Bug Tracking System]

Processing control commands:

> close -1
Bug #906633 [src:vala-panel] vala-panel FTBFS: CMake Error at 
util/CMakeLists.txt:40 (set_target_properties)
Marked Bug as done
> fixed -1 0.4.61+repack1-1
Bug #906633 {Done: Mike Gabriel } 
[src:vala-panel] vala-panel FTBFS: CMake Error at util/CMakeLists.txt:40 
(set_target_properties)
Marked as fixed in versions vala-panel/0.4.61+repack1-1.

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

Bug#906633: Re%3A vala-panel FTBFS%3A CMake Error at util%2FCMakeLists.txt%3A40 %28set_target_properties%29

[Mike Gabriel]

Control: close -1
Control: fixed -1 0.4.61+repack1-1

Hi Adrian,

On Sun, 19 Aug 2018 02:44:35 +0300 Adrian Bunk  wrote:
> Source: vala-panel
> Version: 0.3.75-2
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=vala-panel
> 
> ...
> CMake Error at util/CMakeLists.txt:40 (set_target_properties):
>   set_target_properties called with incorrect number of arguments.
> 
> 
> CMake Error at util/gtk/CMakeLists.txt:31 (set_target_properties):
>   set_target_properties called with incorrect number of arguments.
> 
> 
> XMLLINT not set and xmllint not found in path; skipping xml preprocessing.
> CMake Error at ui/applets-new/CMakeLists.txt:14 (set_target_properties):
>   set_target_properties called with incorrect number of arguments.
> 
> 
> CMake Error at ui/c-lib/CMakeLists.txt:22 (set_target_properties):
>   set_target_properties called with incorrect number of arguments.
> 
> 
> XMLLINT not set and xmllint not found in path; skipping xml preprocessing.
> CMake Error at ui/CMakeLists.txt:69 (set_target_properties):
>   set_target_properties called with incorrect number of arguments.
> 
> 

This main FTBFS issue has been solved by upload of vala-panel 0.4.61+repack1-1.

Mike
-- 
Sent from my Fairphone (powered by SailfishOS)

Processed: openmpi: elpa ftbfs on at least armel, mips64el, ppc64el

[Debian Bug Tracking System]

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

> reassign 905418 src:openmpi 3.1.1.real-6
Bug #905418 [src:elpa] elpa ftbfs on at least armel, mips64el, ppc64el
Bug reassigned from package 'src:elpa' to 'src:openmpi'.
No longer marked as found in versions elpa/2016.05.001-6.
Ignoring request to alter fixed versions of bug #905418 to the same values 
previously set
Bug #905418 [src:openmpi] elpa ftbfs on at least armel, mips64el, ppc64el
Marked as found in versions openmpi/3.1.1.real-6.
> thanks
Stopping processing here.

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

Bug#907422: python-yaml-dbg is empty

[Adrian Bunk]

Package: python-yaml-dbg
Version: 3.12-1
Severity: serious
Tags: buster sid

$ dpkg -L python-yaml-dbg
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/python-yaml-dbg
$


It seems bogus that python{,3}-yaml-dbgsym are built
in addition to python{,3}-yaml-dbg.

Bug#907420: rt4-standalone is empty

[Adrian Bunk]

Package: rt4-standalone
Version: 4.4.1-3
Severity: serious

$ dpkg -L rt4-standalone
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/rt4-standalone
/usr/share/doc/rt4-standalone/NEWS.Debian.gz
/usr/share/doc/rt4-standalone/changelog.Debian.gz
/usr/share/doc/rt4-standalone/copyright
$

Processed: openmpi: elpa builds hang on multiple architectures

[Debian Bug Tracking System]

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

> affects 905418 + src:elpa
Bug #905418 [src:openmpi] elpa ftbfs on at least armel, mips64el, ppc64el
Added indication that 905418 affects src:elpa
> retitle 905418 openmpi: elpa builds hang on multiple architectures
Bug #905418 [src:openmpi] elpa ftbfs on at least armel, mips64el, ppc64el
Changed Bug title to 'openmpi: elpa builds hang on multiple architectures' from 
'elpa ftbfs on at least armel, mips64el, ppc64el'.
> thanks
Stopping processing here.

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

Processed: gphoto2-cffi: diff for NMU version 0.3~a1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 896238 + patch
Bug #896238 [python3-gphoto2cffi] python3-gphoto2cffi: gphoto2cffi fails to 
import
Added tag(s) patch.
> tags 896238 + pending
Bug #896238 [python3-gphoto2cffi] python3-gphoto2cffi: gphoto2cffi fails to 
import
Added tag(s) pending.

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

Bug#905418: openmpi: elpa builds hang on multiple architectures

[Graham Inggs]

Hi Alastair

Elpa seems to be another package with builds timing out.
Confirmed on reproducible builders for i386 [1] and armhf [2].

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/history/i386/elpa.html
[2] https://tests.reproducible-builds.org/debian/history/armhf/elpa.html