Processed: severity of 910255 is serious

[Debian Bug Tracking System]

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

> severity 910255 serious
Bug #910255 [libsane-common] libsane-common: error upgrading libsane-common 
(1.0.27-2) over (1.0.25-4.1)
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: tagging 909851, bug 909851 is forwarded to https://github.com/mesonbuild/meson/pull/4308

[Debian Bug Tracking System]

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

> tags 909851 + upstream
Bug #909851 [meson] meson fails: AttributeError: 'list' object has no attribute 
'absolute_path'
Added tag(s) upstream.
> forwarded 909851 https://github.com/mesonbuild/meson/pull/4308
Bug #909851 [meson] meson fails: AttributeError: 'list' object has no attribute 
'absolute_path'
Set Bug forwarded-to-address to 'https://github.com/mesonbuild/meson/pull/4308'.
> thanks
Stopping processing here.

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

Bug#893651: marked as done (isso FTBFS with node-almond 0.3.3+dfsg-1)

[Debian Bug Tracking System]

Your message dated Thu, 04 Oct 2018 05:20:04 +
with message-id 
and subject line Bug#893651: fixed in isso 0.10.6+git20181001+dfsg-1
has caused the Debian Bug report #893651,
regarding isso FTBFS with node-almond 0.3.3+dfsg-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.)


-- 
893651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893651
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: isso
Version: 0.10.6+git20170928+dfsg-1
Severity: serious

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

...
mkdir -p man/man1/ man/man5
mv man/isso.1 man/man1/isso.1
mv man/isso.conf.5 man/man5/isso.conf.5
node /usr/lib/nodejs/requirejs/r.js -o isso/js/build.embed.js 
out=isso/js/embed.min.js
Error: Error: ERROR: module path does not exist: /usr/lib/nodejs/almond.js for 
module named: /usr/lib/nodejs/almond.js. Path is relative to: 
/build/1st/isso-0.10.6+git20170928+dfsg
at /usr/lib/nodejs/requirejs/r.js:25979:35

make[2]: *** [Makefile:42: isso/js/embed.min.js] Error 1
--- End Message ---
--- Begin Message ---
Source: isso
Source-Version: 0.10.6+git20181001+dfsg-1

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Sep 2018 00:31:31 +0100
Source: isso
Binary: isso
Architecture: source
Version: 0.10.6+git20181001+dfsg-1
Distribution: unstable
Urgency: high
Maintainer: Jelmer Vernooij 
Changed-By: Jelmer Vernooij 
Description:
 isso   - lightweight web-based commenting system
Closes: 893651
Changes:
 isso (0.10.6+git20181001+dfsg-1) unstable; urgency=high
 .
   [ ghost ]
   * Fix FTBFS. Closes: #893651
   * New upstream snapshot.
   * Use python3.
   * Restore bleach as html5lib is not working.
   * Use libjs-jquery and libjs-underscore for doc pages.
 .
   [ Jelmer Vernooij ]
   * Remove Federico from uploaders, per his request.
   * Point Vcs-* URLs at salsa.
   * Actually run nose tests during package build.
Checksums-Sha1:
 4685bb6347a9423bca9a20a2cf646bc1d56c55ac 2128 
isso_0.10.6+git20181001+dfsg-1.dsc
 02842ec350c05fe2ac3bdcfc730650df8d5a06ef 163297 
isso_0.10.6+git20181001+dfsg.orig.tar.gz
 82b5cb3b396f5b7a30026a60a0ab272b392a8325 10028 
isso_0.10.6+git20181001+dfsg-1.debian.tar.xz
 6ff6343809e5edfbc7e9505433b6292e46d9 9861 
isso_0.10.6+git20181001+dfsg-1_source.buildinfo
Checksums-Sha256:
 676d4128a1fafb06c0f90f7560496303cae264d9ff57d6b961ca56e86d0ed462 2128 
isso_0.10.6+git20181001+dfsg-1.dsc
 4ec01465093193854c377c5ff5c3e87603ace3930cf49858d96ca9382fee62a6 163297 
isso_0.10.6+git20181001+dfsg.orig.tar.gz
 66b93391af9aaeb950d3e5cdb9a1ed57becf8276ae11d97f49e3177009925da9 10028 
isso_0.10.6+git20181001+dfsg-1.debian.tar.xz
 fe805ada77039c42e2017107567708c0c4539b41aaf792b1d0c4ff616f41a50a 9861 
isso_0.10.6+git20181001+dfsg-1_source.buildinfo
Files:
 80afba716a52dad9c3c7ad258f9e6d0a 2128 python optional 
isso_0.10.6+git20181001+dfsg-1.dsc
 4b14e1428862c514e960a4e0ec825265 163297 python optional 
isso_0.10.6+git20181001+dfsg.orig.tar.gz
 691d7270304f63380096497a939d1000 10028 python optional 
isso_0.10.6+git20181001+dfsg-1.debian.tar.xz
 c4b5fcf1aacc0839228a01cf1643924e 9861 python optional 
isso_0.10.6+git20181001+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAlu1nEoSHGplbG1lckBk
ZWJpYW4ub3JnAAoJEFecFg1MniPoOlUP/2eEZRhVU6Amcpn2thFtq/zYObGUsIfy
tATbxfgXLWvb7nar9BkJFkUQ9i3YL2sTE9FU3T69mZwRfmoy8j7P9Qwe/cC3Si4M
lpTlz8Ygvk1PXTXzoXEM6ByflzaMBl4ZchU6wv8HZqZmHZ65Z07fMc6hsAy5syki
d6qIKp9F6XKncwBCB3gKNoHYBmOGVbEVa3H7XOaaRZPWjVur6ZqSkupPqx4bXfYE
WQNXNdzQyCcF32UqgURt4uMUXgX1ahbAgkSAUoWAEdxSlLgc2lLRbXitc0iu2BWI
ClBy8CH+4Xjm/eM7l88zMHhRzOJhSZQiymrUf0XJQhAjL1Py44wXNNbedcDwPFuT
D6UG9w4exkrki+CKYNMJZti/zCt5QmhMSEw0NO2biX0Ejh08q2qTkcxVSB7MtRMM
h72bq7Nnwf63Qo+7p7RE84GputvyuaDlT4fm5ijP87fHKHoxwT5VX1eLDU2bngDT
zzCu5jfFWuiifrcQquVHd544dwW5Nq043I/jkC1jgmEnLlLEy6wEL5SQV5n8xjYo
XCDkoieEcep1cdU37yLJ8njZR

Bug#898705: android-platform-libcore 8.1 upload to unstable?

[tony mancill]

Hello,

I maintain a package that depends on libandroid-json-java that will soon
to be evicted from testing due to the FTBFS bug (898705) filed against
src:android-platform-libcore.  Would it be possible for you to upload
the newer package in experimental to unstable?  If not, would it be
possible to update the 7.0.0+r33 based package?

Thank you,
tony


signature.asc
Description: PGP signature

Bug#910258: debmake-doc parallel FTBFS

[Helmut Grohne]

Source: debmake-doc
Version: 1.11-1
Severity: serious
Tags: ftbfs

debmake-doc randomly fails to build from source when performing a
parallel build (difficult to trigger). The issue lies in test case
debhello-3.0. Its Makefile says:

| all: data/hello.desktop po/ja.mo
|
| data/hello.desktop po/ja.mo:
|   $(MAKE)  -C po all

My build log has this:

| make[1]: Entering directory 
'/<>/debhello-3.0-pkg1/test/debhello-3.0'
| 
| make  -C po all
| 
| make  -C po all
| 
| make[2]: Entering directory 
'/<>/debhello-3.0-pkg1/test/debhello-3.0/po'


So making all in debhello-3.0 causes two $(MAKE) -C po all to be spawned
simultaneously. Now the po Makefile runs xgettext to update
debhello.pot.  Running two xgettext at the same time on the same output
file causes bad things to happen and the later msgmerge calls notice
that:

| msgmerge -U ja.po debhello.pot
| 
| msgmerge -U ja.po debhello.pot
| 
| debhello.pot:37: duplicate message definition...
| 
| debhello.pot:23: ...this is the location of the first definition
| 
| debhello.pot:42: duplicate message definition...
| 
| debhello.pot:28: ...this is the location of the first definition
| 
| msgmerge: found 2 fatal errors
| 
| make[2]: *** [Makefile:10: ja.po] Error 1
| 
| make[2]: Leaving directory 
'/<>/debhello-3.0-pkg1/test/debhello-3.0/po'
| 
| make[1]: *** [Makefile:6: data/hello.desktop] Error 2
| 
| make[1]: *** Waiting for unfinished jobs
| 
| debhello.pot:37: duplicate message definition...
| 
| debhello.pot:23: ...this is the location of the first definition
| 
| debhello.pot:42: duplicate message definition...
| 
| debhello.pot:28: ...this is the location of the first definition
| 
| msgmerge: found 2 fatal errors
| 
| make[2]: *** [Makefile:10: ja.po] Error 1
| 
| make[2]: Leaving directory 
'/<>/debhello-3.0-pkg1/test/debhello-3.0/po'

Helmut

Processed: affects 898705

[Debian Bug Tracking System]

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

> affects 898705 zabbix
Bug #898705 {Done: Saif Abdul Cassim } 
[src:android-platform-libcore] android-platform-libcore FTBFS with debhelper v11
Added indication that 898705 affects zabbix
> thanks
Stopping processing here.

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

Bug#905180: marked as done (libmoe-dev: missing Breaks+Replaces: libmoe1.5 (<< 1.5.8-3))

[Debian Bug Tracking System]

Your message dated Thu, 04 Oct 2018 02:42:45 +
with message-id 
and subject line Bug#905180: fixed in libmoe 1.5.8-5
has caused the Debian Bug report #905180,
regarding libmoe-dev: missing Breaks+Replaces: libmoe1.5 (<< 1.5.8-3)
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.)


-- 
905180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmoe-dev
Version: 1.5.8-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Unpacking libmoe-dev (1.5.8-3) over (1.5.8-2+b1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libmoe-dev_1.5.8-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/libmoe.so', which is also in package libmoe1.5 
1.5.8-2+b1
  Preparing to unpack .../libmoe1.5_1.5.8-3_amd64.deb ...
  Unpacking libmoe1.5 (1.5.8-3) over (1.5.8-2+b1) ...
  Preparing to unpack .../multiarch-support_2.27-5_amd64.deb ...
  Unpacking multiarch-support (2.27-5) over (2.24-11+deb9u3) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libmoe-dev_1.5.8-3_amd64.deb


cheers,

Andreas


libmoe-dev_1.5.8-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libmoe
Source-Version: 1.5.8-5

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

Debian distribution maintenance software
pp.
TANIGUCHI Takaki  (supplier of updated libmoe 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, 04 Oct 2018 11:24:26 +0900
Source: libmoe
Binary: libmoe-dev libmoe1.5
Architecture: source amd64
Version: 1.5.8-5
Distribution: unstable
Urgency: medium
Maintainer: TANIGUCHI Takaki 
Changed-By: TANIGUCHI Takaki 
Description:
 libmoe-dev - library to handle multiple octets character encoding scheme (deve
 libmoe1.5  - library to handle multiple octets character encoding scheme
Closes: 905180
Changes:
 libmoe (1.5.8-5) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces
   * d/control: Remove trailing whitespaces
   * d/rules: Remove trailing whitespaces
   * d/control: Fix wrong Vcs-*
 .
   [ TANIGUCHI Takaki ]
   * d/control: Fix package name on Breaks and Replaces. (Closes: #905180)
   * Bump Stanrads-Version to 4.2.1
Checksums-Sha1:
 ff9f7969547a91ba9dc44016330400f76741af81 1821 libmoe_1.5.8-5.dsc
 e2fb369a780bb9bbcc9b85ac0f442cfb702fec11 3236 libmoe_1.5.8-5.debian.tar.xz
 13899e48ec08f2c66f820c935e44079466c511dc 15364 libmoe-dev_1.5.8-5_amd64.deb
 491bc166ff2716b91d9b61e0bcbe17024d7471ef 179660 
libmoe1.5-dbgsym_1.5.8-5_amd64.deb
 5b11102fdf6dfd476ad1734d9fbb1984c831ba97 452648 libmoe1.5_1.5.8-5_amd64.deb
 ba7b97321d8ad723be37011b1a9cddb2ed2eeede 7092 libmoe_1.5.8-5_amd64.buildinfo
Checksums-Sha256:
 51b4373ff1263242f7db12a49f86ce38c32c8912fd895b89d21edf1ed080265f 1821 
libmoe_1.5.8-5.dsc
 c01a83192ada0aff67592edac90547a4448185375ce54c3cfbad69158d088617 3236 
libmoe_1.5.8-5.debian.tar.xz
 ff5dffe394ae5c43ad2b44673fd68762b8381a6905ab55c37571510697de9411 15364 
libmoe-dev_1.5.8-5_amd64.deb
 9e682dbdff2f8571fedac2a305cd52e9f58a8e147d2ceb34932c2a2e6b94c7ff 179660 
libmoe1.5-dbgsym_1.5.8-5_amd64.deb
 5d1b350d3ad06413d5d1843cdcb37eb74b991ee2d1f8f0c3fb343fd64576f750 452648 
libmoe1.5_1.5.8-5_amd64.deb
 7588614aa30215077f6cd2b6fee543afe99b13c013f4553db10055d16c675d32 7092 
libmoe_1.5.8-5_amd64.buildinfo
Files:
 089ab17a65d393ffb494a93771102f30 1821 libdevel optional libmoe_1.5.8-5.dsc
 43ca831a4eadb807dd8ef2a315b3c594 3236 libdevel optional 
libmoe_1.5.8-5.debian.tar.xz
 64a7f083904182b8f94728912aa5e6c2 15364 libdevel optional 
libmoe-dev_1.5.8-5_

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 906147 https://github.com/zeroSteiner/smoke-zephyr/issues/4
Bug #906147 [src:python-smoke-zephyr] python-smoke-zephyr ftbfs (failing tests)
Warning: Unknown package 'src:python-smoke-zephyr'
Set Bug forwarded-to-address to 
'https://github.com/zeroSteiner/smoke-zephyr/issues/4'.
Warning: Unknown package 'src:python-smoke-zephyr'
> thanks
Stopping processing here.

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

Bug#906147:

[Samuel Henrique]

Control: forwarded !
https://github.com/zeroSteiner/smoke-zephyr/issues/4#issuecomment-426854295
thanks

Upstream is aware of it

-- 
Samuel Henrique 

Bug#909971: marked as done (remove unneeded dependency on backports.ssl-match-hostname)

[Debian Bug Tracking System]

Your message dated Thu, 04 Oct 2018 01:34:53 +
with message-id 
and subject line Bug#909971: fixed in libcloud 2.3.0-3
has caused the Debian Bug report #909971,
regarding remove unneeded dependency on backports.ssl-match-hostname
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.)


-- 
909971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:backports.ssl-match-hostname
Version: 3.5.0.1-1
Severity: important
Tags: sid buster

The python3 and python2 versions already have that fix (and had it in stretch
too).  This package should  be removed for the buster release.
--- End Message ---
--- Begin Message ---
Source: libcloud
Source-Version: 2.3.0-3

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

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

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

Debian distribution maintenance software
pp.
Andrew Starr-Bochicchio  (supplier of updated libcloud package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 03 Oct 2018 21:14:23 -0400
Source: libcloud
Binary: python-libcloud python3-libcloud
Architecture: source all
Version: 2.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrew Starr-Bochicchio 
Description:
 python-libcloud - unified Python interface into the cloud
 python3-libcloud - unified Python interface into the cloud (Python3 version)
Closes: 909971
Changes:
 libcloud (2.3.0-3) unstable; urgency=medium
 .
   * d/control: Remove unneeded dependency on
 backports.ssl-match-hostname (Closes: #909971).
   * d/control: Bump Standards-Version to 4.2.1.
   * d/docs: Install NOTICE file.
Checksums-Sha1:
 de98e12c04a8342d1e222e8b26cf63eebd50b907 2663 libcloud_2.3.0-3.dsc
 c4a7ee50bd1cddfa1d6e6045444b76119c3bf0cb 8384 libcloud_2.3.0-3.debian.tar.xz
 6bebcecf183cb13c658e300bacc5ee0441ba4ba6 9338 libcloud_2.3.0-3_amd64.buildinfo
 ebf93b418f3abcaf165fe33908bcc0426f3e7c1a 1307032 
python-libcloud_2.3.0-3_all.deb
 19e51fabf65f5fe1f44ea49bd2731ca0343912e3 1290532 
python3-libcloud_2.3.0-3_all.deb
Checksums-Sha256:
 5367f3628fbc49f99e9b3083c027b2c969cbaa444807d23ff01a7b80c1ecad38 2663 
libcloud_2.3.0-3.dsc
 a32f4b272d3ced2a059cd773547eafb68de52224fdb786e6eb8ad5a3bbb94ab5 8384 
libcloud_2.3.0-3.debian.tar.xz
 920be1952e64bcead8bca5a84704b04c192441c3d338e6e5fbbf2bcb20a5f5b1 9338 
libcloud_2.3.0-3_amd64.buildinfo
 315e860d5e17404847cf5339c82006ae6a7740ae5c480470c87b21b659d8b6d8 1307032 
python-libcloud_2.3.0-3_all.deb
 e40496630676bff862c08cd9fc37dd638afc7355a8a88bc5b0d7f90a9d05c561 1290532 
python3-libcloud_2.3.0-3_all.deb
Files:
 977b63734fcab00b69f0dffe0b1f2c2e 2663 python optional libcloud_2.3.0-3.dsc
 acff127c4d6e4aa4dddf9e695f7bbc93 8384 python optional 
libcloud_2.3.0-3.debian.tar.xz
 f2211324b29e79185c69dedbc09e4a0c 9338 python optional 
libcloud_2.3.0-3_amd64.buildinfo
 40f5b31ed8d357059e088ecfd32f7a25 1307032 python optional 
python-libcloud_2.3.0-3_all.deb
 ce50535bf29a1b170d244e0ddbb113b2 1290532 python optional 
python3-libcloud_2.3.0-3_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEbrIj19ceZ6U8k6faO1biu9U/3LEFAlu1a4sACgkQO1biu9U/
3LG3qQ//eqC8BjtEBPBchgz0jsDUWy5YDNaC8KYdN/FpsDvB9vdh/Qt+bn3chq0X
8d7P3gcnlEOoyL3x0WwZt28FUWUgNDufUmHHljHJAcdSBKmpOWiTwiuyQCKRAzqL
SGMCVTrZd4CPmNGiTWW9C6AFqE1r+GqC6KNhgwwmT/ZVjZ385n4MBtwZ3vO1aoID
778Y/ySzpnKKj/U0unAn430waj7jCRHDSmdU1Qhpq+HZuHpbho1CWk8pyBcBHyvm
+MSGw7Tocmi5FTL3HvpvfSbH+8Cff/BVRoVHizlHyT12k6q8tJfLQ80x2/02QwHk
ZRCaa9lMeeTtgsdC+q54C9M1rpnSzCrSjlp+WHJ0jIlUdIHTJRkicQrBxTMZPeNB
czN/lOXid27FpX6oC2TCIP0+0g0khSKmYGS/Z049cyyVmEOyzsB6qehfyWnSdNTw
y2pjdQ9Bwzh/PFAz9x11VmyKqJcNuEQtK5XN3crEaMl3P1CF+0lgiV48oIGIzy7U
7rWJhcWr2f6UQdF65275jNfY9Es1ilhSe939X5afmYUGajQplwaLw5ZdzoIekWU3
BW/lLif94bv9BOjsSTLu77eGvbafFpJW5yGENMCFqRMo1BFA3JNCblnd8R47UIve
i60qqPYnd2IgJEfojQ9v17xz4MrgEVnDzpz2qi/U8wwZw7VR/YQ=
=kfsW
-END PGP SIGNATURE End Message ---

Processed: Bug #909971 in libcloud marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #909971 [libcloud] remove unneeded dependency on 
backports.ssl-match-hostname
Added tag(s) pending.

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

Bug#909971: Bug #909971 in libcloud marked as pending

[Andrew Starr-Bochicchio]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/libcloud/commit/e344d530eacbe358ac9bfe7ceba60266afe14c43


d/control: Remove unneeded dependency on backports.ssl-match-hostname (Closes: 
#909971).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/909971

Bug#910233: libsvn-{dev,java}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[James McCoy]

On Wed, Oct 03, 2018 at 07:49:35PM +0200, Andreas Beckmann wrote:
> an upgrade test with piuparts revealed that your package installs files
> over existing symlinks and possibly overwrites files owned by other
> packages. This usually means an old version of the package shipped a
> symlink but that was later replaced by a real (and non-empty)
> directory. This kind of overwriting another package's files cannot be
> detected by dpkg.
> 
> Note that dpkg intentionally does not replace directories with symlinks
> and vice versa, you need the maintainer scripts to do this.
> See in particular the end of point 4 in
> https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade
> 
> It is recommended to use the dpkg-maintscript-helper commands
> 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
> to perform the conversion, ideally using d/$PACKAGE.maintscript.

This is exactly what I did:

https://salsa.debian.org/jamessan/subversion/commit/d5e5e1c5c61b072974de5e0803deed669530e48c
https://salsa.debian.org/jamessan/subversion/commit/af236dd6de6239dff820d480206b4c92b8287be2

Confused,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#910249: marked as done (Bumping up encryption to AES-256 by default)

[Debian Bug Tracking System]

Your message dated Wed, 3 Oct 2018 20:45:38 -0400
with message-id 

and subject line Re: Bug#910249: Bumping up encryption to AES-256 by default
has caused the Debian Bug report #910249,
regarding Bumping up encryption to AES-256 by default
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.)


-- 
910249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-disk-utility
Version: all
Severity: serious

Hi. I noticed Gnome Disks uses AES-128 by default instead of AES-256
like Debian does out of the box. Having 256 bit symmetric keys is good
practice for long term security especially in a coming era of quantum
computers. (Whether they materialize or not is deabatble but why not
have a sufficient margin if it's easy enough?) It is also the
recommended level by NIST.


This is verified by running:

# cryptsetup luksDump --debug 

AES in XTS mode uses a keysize double its bit size (512 in this case)
since with XTS the key is split in 2 so you actually get AES with
256-bit keys.

A partition created by Gnome Disks shows it's only using MK size 256
instead of the expected 512. Please modify the source to pass 512 bit
size to cryptsetup.


For more details and original research by me see:

https://www.whonix.org/wiki/Full_Disk_Encryption_and_Encrypted_Images#Protection_Against_Powerful_Adversaries
--- End Message ---
--- Begin Message ---
On Wed, Oct 3, 2018 at 8:43 PM procmem  wrote:
> Thanks for pointing me to the code and upstream bugtracker :) I've
> opened a ticket on GNOME here:
>
> https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/103
>
> Feel free to close the ticket here because it's not related to you guys.--- End Message ---

Bug#910249: Bumping up encryption to AES-256 by default

[procmem]

Jeremy Bicha:
> On Wed, Oct 3, 2018 at 6:36 PM procmem  wrote:
>> Package: gnome-disk-utility
>> Version: all
>> Severity: serious
>>
>> Hi. I noticed Gnome Disks uses AES-128 by default instead of AES-256
>> like Debian does out of the box. Having 256 bit symmetric keys is good
>> practice for long term security especially in a coming era of quantum
>> computers. (Whether they materialize or not is deabatble but why not
>> have a sufficient margin if it's easy enough?) It is also the
>> recommended level by NIST.
> 
> Please report this issue to the GNOME Disks developers:
> https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues
> 
> From what I can tell, Disks uses udisks2 which uses libblockdev. The
> libblockdev default is 256 bits.
> 
> https://github.com/storaged-project/libblockdev/blob/master/src/plugins/crypto.h#L39
> 
> So I'm not sure if the libblockdev default should be changed or if
> that's something that GNOME Disks is supposed to handle itself.
> 
> Thanks,
> Jeremy Bicha
> 

Thanks for pointing me to the code and upstream bugtracker :) I've
opened a ticket on GNOME here:

https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/103

Feel free to close the ticket here because it's not related to you guys.

Bug#906147: python-smoke-zephyr ftbfs (failing tests)

[Samuel Henrique]

Hello Matthias,

Thanks for reporting it, I think I will have to check with upstream about this.

> Please also make it clear which Python version is used during the tests.

I didn't understand this part, what do you mean exactly by making the
version clear? Feel free to point me to examples or docs if
appropriate.

Thanks,

-- 
Samuel Henrique 

Bug#910249: Bumping up encryption to AES-256 by default

[Jeremy Bicha]

On Wed, Oct 3, 2018 at 6:36 PM procmem  wrote:
> Package: gnome-disk-utility
> Version: all
> Severity: serious
>
> Hi. I noticed Gnome Disks uses AES-128 by default instead of AES-256
> like Debian does out of the box. Having 256 bit symmetric keys is good
> practice for long term security especially in a coming era of quantum
> computers. (Whether they materialize or not is deabatble but why not
> have a sufficient margin if it's easy enough?) It is also the
> recommended level by NIST.

Please report this issue to the GNOME Disks developers:
https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues

>From what I can tell, Disks uses udisks2 which uses libblockdev. The
libblockdev default is 256 bits.

https://github.com/storaged-project/libblockdev/blob/master/src/plugins/crypto.h#L39

So I'm not sure if the libblockdev default should be changed or if
that's something that GNOME Disks is supposed to handle itself.

Thanks,
Jeremy Bicha

Bug#897883: marked as done (varconf: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Wed, 03 Oct 2018 23:13:55 +
with message-id 
and subject line Bug#897883: fixed in varconf 1.0.1-6
has caused the Debian Bug report #897883,
regarding varconf: 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.)


-- 
897883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:varconf
Version: 1.0.1-5
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/varconf_1.0.1-5_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

[...]
- 
_ZNK7varconf7VarBasecvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev@Base
 0.6.7
+#MISSING: 1.0.1-5# 
_ZNK7varconf7VarBasecvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev@Base
 0.6.7
  
_ZNK7varconf7VarBasecvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcv@Base
 1.0.1-4~
  _ZNK7varconf7VarBasecvbEv@Base 0.6.7
  _ZNK7varconf7VarBasecvdEv@Base 0.6.7
@@ -89,31 +89,35 @@
  _ZNK7varconf8VarArray7is_boolEv@Base 0.6.7
  _ZNK7varconf8VarArray9is_doubleEv@Base 0.6.7
  _ZNK7varconf8VarArray9is_stringEv@Base 0.6.7
- 
_ZNK7varconf8VarArraycvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev@Base
 0.6.7
+#MISSING: 1.0.1-5# 
_ZNK7varconf8VarArraycvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev@Base
 0.6.7
  
_ZNK7varconf8VarArraycvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcv@Base
 1.0.1-4~
  _ZNK7varconf8VarArraycvbEv@Base 0.6.7
  _ZNK7varconf8VarArraycvdEv@Base 0.6.7
  _ZNK7varconf8VarArraycviEv@Base 0.6.7
  
(optional=inline)_ZNKSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N7varconf8VariableEESt10_Select1stISA_ESt4lessIS5_ESaISA_EE4findERS7_@Base
 0.6.7
  
(optional=inline)_ZNKSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_St3mapIS5_N7varconf8VariableESt4lessIS5_ESaIS6_IS7_SA_St10_Select1stISG_ESC_SaISG_EE4findERS7_@Base
 0.6.7
- (optional=inline)_ZNSt12_Vector_baseIN7varconf8VariableESaIS1_EED1Ev@Base 
0.6.7
- (optional=inline)_ZNSt12_Vector_baseIN7varconf8VariableESaIS1_EED2Ev@Base 
0.6.7
+#MISSING: 1.0.1-5# 
(optional=inline)_ZNSt12_Vector_baseIN7varconf8VariableESaIS1_EED1Ev@Base 0.6.7
+#MISSING: 1.0.1-5# 
(optional=inline)_ZNSt12_Vector_baseIN7varconf8VariableESaIS1_EED2Ev@Base 0.6.7
  (regex)_ZNSt6vectorIN7varconf8VariableESaIS1_EE17_M_default_appendE[mj]@Base 
1.0.1
+ 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base
 1.0.1-5
+ 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag@Base
 1.0.1-5
  
(optional=inline)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N7varconf8VariableEESt10_Select1stISA_ESt4lessIS5_ESaISA_EE11equal_rangeERS7_@Base
 0.6.7
+ 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N7varconf8VariableEESt10_Select1stISA_ESt4lessIS5_ESaISA_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESL_IJESt17_Rb_tree_iteratorISA_ESt23_Rb_tree_const_iteratorISA_EDpOT_@Base
 1.0.1-5
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N7varconf8VariableEESt10_Select1stISA_ESt4lessIS5_ESaISA_EE24_M_get_insert_unique_posERS7_@Base
 0.6.7
  
(optional=inline)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N7varconf8VariableEESt10_Select1stISA_ESt4lessIS5_ESaISA_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISA_ERS7_@Base
 0.6.7
  
_ZNSt8

Bug#909602: [Pkg-mailman-hackers] Bug#909602: mailmanclient causes python3-mailman-hyperkitty and mailman3-web to fail to install in buster

[Pierre-Elliott Bécue]

Le mercredi 26 septembre 2018 à 20:32:47+0200, Paul Gevers a écrit :
> Hi
> 
> On Tue, 25 Sep 2018 21:33:18 +0200 Paul Gevers  wrote:
> > If the right binary package(s) from mailmanclient would have had a
> > versioned Breaks on the broken versions of mailman3-web and
> > python3-mailman-hyperkitty this could have been prevented.
> 
> I forgot, and thus forgot to mention, that it is possible that a (test)
> dependency is missing that is pulled in via dependencies. I couldn't
> spot yet which package that would be. If the dependency is available in
> buster, the bug can quickly and simply be fixed by a new upload of
> mailmanclient.

Hi,

Would you prefer if we push a fix or if we wait for mailman-hyperkitty
migration?

Cheers,

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#908827: mesa: Fails to build on Stretch, missing min build dep

[Stuart Young]

Commit has made it into the queue for 18.2.2.

On Thu, 27 Sep 2018 at 18:12, Stuart Young  wrote:

> This was an upstream issue due to new work in the vulkan driver that uses
> newer libxcb functions (only in 1.13+).
>
> For Mesa 18.2.1, the following upstream commit resolves the build issue:
>  dd333c66bdcb11c0d7c5 "vulkan: Disable randr lease for libxcb < 1.13"
>
> Hopefully this should make it into Mesa 18.2.2 shortly.
>
> --
> Stuart Young (aka Cefiar)
>


-- 
Stuart Young (aka Cefiar)

Bug#910249: Bumping up encryption to AES-256 by default

[procmem]

Package: gnome-disk-utility
Version: all
Severity: serious

Hi. I noticed Gnome Disks uses AES-128 by default instead of AES-256
like Debian does out of the box. Having 256 bit symmetric keys is good
practice for long term security especially in a coming era of quantum
computers. (Whether they materialize or not is deabatble but why not
have a sufficient margin if it's easy enough?) It is also the
recommended level by NIST.


This is verified by running:

# cryptsetup luksDump --debug 

AES in XTS mode uses a keysize double its bit size (512 in this case)
since with XTS the key is split in 2 so you actually get AES with
256-bit keys.

A partition created by Gnome Disks shows it's only using MK size 256
instead of the expected 512. Please modify the source to pass 512 bit
size to cryptsetup.


For more details and original research by me see:

https://www.whonix.org/wiki/Full_Disk_Encryption_and_Encrypted_Images#Protection_Against_Powerful_Adversaries

Bug#910248: kmymoney: KMyMoney needs to be recompiled against KDE PIM 18.08.

[Sandro Knauß]

Source: kmymoney
Version: 5.0.1-2
Severity: serious
Control: block 909288 by -1

Hey,

KDE PIM 18.08 changes ABI, so KMyMoney needs to recompiled against the
new version. But as KMyMoney 5.0.1 is currently in experimental, this
can't be done via the normal transition (so far as I unserstand.

hefee

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

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

Processed: kmymoney: KMyMoney needs to be recompiled against KDE PIM 18.08.

[Debian Bug Tracking System]

Processing control commands:

> block 909288 by -1
Bug #909288 [release.debian.org] transition: kdepim 18.08
909288 was blocked by: 908869
909288 was not blocking any bugs.
Added blocking bug(s) of 909288: 910248

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

Processed: Re: [Epoptes] Bug#910216: epoptes-client: removed shipped file: /etc/network/if-up.d/epoptes-client

[Debian Bug Tracking System]

Processing control commands:

> tags 910216 pending
Bug #910216 [epoptes-client] epoptes-client: removed shipped file: 
/etc/network/if-up.d/epoptes-client
Added tag(s) pending.

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

Bug#910216: [Epoptes] Bug#910216: epoptes-client: removed shipped file: /etc/network/if-up.d/epoptes-client

[Vagrant Cascadian]

Control: tags 910216 pending

On 2018-10-03, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package removes files that
> it has shipped.
>
> From the attached log (scroll to the bottom...):
>
> 1m6.1s ERROR: FAIL: debsums reports modifications inside the chroot:
>   debsums: missing file /etc/network/if-up.d/epoptes-client (from 
> epoptes-client package)
>
> This was observed after a stretch->buster upgrade.

Fix committed to git, though I haven't yet tested it:

  
https://github.com/Epoptes/epoptes/commit/593f413e7edb718c2b5622fea17d2587468cd43a


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#909214: marked as done (mailman-hyperkitty FTBFS: FAIL: test_archive_message_unserializable (mailman_hyperkitty.tests.test_archiver.ArchiverTestCase))

[Debian Bug Tracking System]

Your message dated Wed, 03 Oct 2018 22:07:03 +
with message-id 
and subject line Bug#909214: fixed in mailman-hyperkitty 1.1.0-9
has caused the Debian Bug report #909214,
regarding mailman-hyperkitty FTBFS: FAIL: test_archive_message_unserializable 
(mailman_hyperkitty.tests.test_archiver.ArchiverTestCase)
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.)


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

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

...
FAIL: test_archive_message_unserializable 
(mailman_hyperkitty.tests.test_archiver.ArchiverTestCase)
--
Traceback (most recent call last):
  File 
"/build/1st/mailman-hyperkitty-1.1.0/mailman_hyperkitty/tests/test_archiver.py",
 line 357, in test_archive_message_unserializable
self.assertEqual(logger.error.call_count, 1)
AssertionError: 2 != 1

--
Ran 14 tests in 0.982s

FAILED (failures=1)
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: 
python3.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit code 
13
make: *** [debian/rules:6: build] Error 25
--- End Message ---
--- Begin Message ---
Source: mailman-hyperkitty
Source-Version: 1.1.0-9

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

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

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

Debian distribution maintenance software
pp.
Pierre-Elliott Bécue  (supplier of updated mailman-hyperkitty 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 03 Oct 2018 14:26:30 +0200
Source: mailman-hyperkitty
Binary: python3-mailman-hyperkitty
Architecture: source
Version: 1.1.0-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Mailman Team 
Changed-By: Pierre-Elliott Bécue 
Description:
 python3-mailman-hyperkitty - Mailman3 plugin to archive emails with HyperKitty
Closes: 909214
Changes:
 mailman-hyperkitty (1.1.0-9) unstable; urgency=medium
 .
   * d/patches:
 - Add patch 0002 to disable a test that doesn't work properly in Python3
   (Closes: #909214)
   * d/control:
 - Change my email address as uploader of the package.
Checksums-Sha1:
 cead57a5a7a771c25f5476c3376c3afe21412fc3 2314 mailman-hyperkitty_1.1.0-9.dsc
 755a1c82022afa1cd534aa1dd25f2243d364cfc4 38712 
mailman-hyperkitty_1.1.0-9.debian.tar.xz
 3712f3def1a4d8db0e4b196d3b7f19bc65781fb9 8698 
mailman-hyperkitty_1.1.0-9_amd64.buildinfo
Checksums-Sha256:
 a3b0f058e52f5edd22afac615e25df3da5b360d806a249c3401efb1333b8b1f4 2314 
mailman-hyperkitty_1.1.0-9.dsc
 ac31070ea4ac5e3e10a7ac55f3ea7429ccde845be45bcb17f7a86e8cfd56ae1e 38712 
mailman-hyperkitty_1.1.0-9.debian.tar.xz
 25357ddf28d5aa5f25392ad5a3c6d936d8997c4be6a791046d469f7422583226 8698 
mailman-hyperkitty_1.1.0-9_amd64.buildinfo
Files:
 b45b98b19b4d8e6a1a6f9889fe2d0ad1 2314 python optional 
mailman-hyperkitty_1.1.0-9.dsc
 f6a8d12dfefc0f2c75d796468ea1b011 38712 python optional 
mailman-hyperkitty_1.1.0-9.debian.tar.xz
 820c51305283beeec7f95a5c92405daa 8698 python optional 
mailman-hyperkitty_1.1.0-9_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEESYqTBWsFJgT6y8ijKb+g0HkpCsoFAlu1OUMACgkQKb+g0Hkp
Csov0g//avnTlLxMKbl+gLqiQpEFmEG4L6rP4JH6EOI9FgByT3ayAeabuSCN1ygs
UuY0q67bTnW1GmDrUg5eechQhf79CsReyJb1Iq3ior3Ndw+tVmFzOGcJk0mSyzgZ
nVF4s83A/+v3SzeyYTaKokFBRsgozbucDyHfGlAGt045aDLYLEGcnvFpqDodVk4i
UcWoSff5BpRyR8B90z+GvRc4o0g76LEwH9av+mqU4Lr329e3BrArasRmVf7wh4wU
rigPqZbFeysUlwYIZFS7l+hM8lc2jFfhn6GeWthF/C/eQRnz6RBBZHRxIO+G0Q+J
Ymv6GNyW0shxKOU+WIoyaRoRnpp72kUK4JcotI+7fEGHG/V10tqobgM2Bh07hKfz
HtjWO2A3lbaepxQUz1FHnhtdJKSl+RLeVxrBPh9Ma6efQrLWR/mKeMxf353C+OWS
6BBn5Vk3Av0TVWHS4c3XnU5jWknz7n/uuTfmjdNP07ejMh0JiwP+SulyJSQU7rOW
hBdYVzNUwgBOrcGPifkWEThe95a3LGyoSTKtl8ukQthnC+QZDeQooXj0Asb0eKpY
w0KnmxS8kxea90/uXt1I1yL8MI/fjfCS+uK9yyFeCZ70e5U4gDUC4QseQIV

Bug#907788: marked as done ("dh key too small" since openssl upgrade)

[Debian Bug Tracking System]

Your message dated Wed, 3 Oct 2018 22:55:30 +0100
with message-id <20181003215530.GA30589@pinky.flat11.house>
and subject line Re: Bug#907788: "dh key too small" since openssl upgrade
has caused the Debian Bug report #907788,
regarding "dh key too small" since openssl upgrade
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.)


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

Package: curl
Version: 7.61.0-1

Since openssl upgrade to 1.1.1~~pre9-1, curl is not able anymore to do 
requests to some sites. For example:


% curl https://www.credit-cooperatif.coop/
curl: (35) error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small

It used to work with curl, and it still works with wget (which uses gnutls).

I suspect it's related to #907015.
--- End Message ---
--- Begin Message ---
On Sat, Sep 29, 2018 at 06:33:02PM +0200, Sebastian Andrzej Siewior wrote:
> control: unblock 907015 by 907788
> 
> On 2018-09-02 09:59:11 [+0200], VA wrote:
> > Since openssl upgrade to 1.1.1~~pre9-1, curl is not able anymore to do
> > requests to some sites. For example:
> > 
> > % curl https://www.credit-cooperatif.coop/
> > curl: (35) error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small
> > 
> > It used to work with curl, and it still works with wget (which uses gnutls).
> > 
> > I suspect it's related to #907015.
> 
> I would close that if I were the curl maintainer. The remote site in the
> example uses a small DH key [0]. If you can't get owner to upgrade the
> site and want still to access the site I suggest to remove
>   CipherString = DEFAULT@SECLEVEL=2
> from /etc/ssl/openssl.cnf.
> 
> [0] https://www.ssllabs.com/ssltest/analyze.html?d=www.credit-cooperatif.coop


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

Bug#896759: [gui-ufw] FTBFS and no maintainer activity since 2016

[Samuel Henrique]

Hello Everyone, I'm not sure if I should have CC'ed everyone, sorry if
I shouldn't.

Today a Brazilian user was asking help installing gufw on Testing, he
said it was only on unstable and stable, I decided to have a look and
discovered:

* The last upload was a NMU on 2017-05-13
* The last maintainer upload was on 2016-11-06
* Package currently has an very easy fix FTBFS bug opened since April this year
* One of the maintainers (Devid) is still maintaining the package on
Ubuntu and doing uploads
* Deivid had to get sponsor for their uploads on Debian

I would really like to see the status of the package be the same as of
on Ubuntu, being up to date and without bugs.

Deivid and Miriam, are you still willing to maintain the package? I
can see that Deivid already have DM permission on some packages, you
could get one for gui-fw, or at least I could sponsor your uploads (if
Miriam stopped doing so).

In the last case, I could have a look and put the package up to date
with Ubuntu's.

Thanks for your consideration.
-- 
Samuel Henrique 

Bug#905481: marked as done (mediastreamer2: FTBFS with GCC-8)

[Debian Bug Tracking System]

Your message dated Wed, 03 Oct 2018 21:41:49 +
with message-id 
and subject line Bug#905481: fixed in mediastreamer2 1:2.16.1-3
has caused the Debian Bug report #905481,
regarding mediastreamer2: 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.)


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

Hi,

mediastreamer2 FTBFS since GCC-8 became the default compiler:

[ 38%] Building C object 
src/CMakeFiles/mediastreamer_voip-static.dir/voip/audiostream.c.o
cd /build/mediastreamer2-2.16.1/obj-x86_64-linux-gnu/src && /usr/bin/cc 
-DBCTBX_STATIC -DBZRTP_STATIC -DHAVE_CONFIG_H -DMS2_EXPORTS -DMS2_FILTERS 
-DMS2_INTERNAL -DMS2_STATIC -DORTP_STATIC -DVIDEO_ENABLED -D_TRUE_TIME 
-I/build/mediastreamer2-2.16.1/include 
-I/build/mediastreamer2-2.16.1/src/audiofilters 
-I/build/mediastreamer2-2.16.1/src/utils 
-I/build/mediastreamer2-2.16.1/src/voip 
-I/build/mediastreamer2-2.16.1/obj-x86_64-linux-gnu 
-I/build/mediastreamer2-2.16.1/obj-x86_64-linux-gnu/src -I/usr/include/libxml2 
-I/usr/include/x86_64-linux-gnu  -g -O2 
-fdebug-prefix-map=/build/mediastreamer2-2.16.1=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-Wall 
-Wuninitialized -Wno-format-truncation -Werror -Wextra -Wno-unused-parameter 
-fno-strict-aliasing -Wno-missing-field-initializers 
-Wdeclaration-after-statement -Wstrict-prototypes -Wno-error=strict-prototypes 
-o CMakeFiles/mediastreamer_voip-static.dir/voip/audiostream.c.o   -c 
/build/mediastreamer2-2.16.1/src/voip/audiostream.c
/build/mediastreamer2-2.16.1/src/voip/audiostream.c: In function 
'audio_stream_start_from_io':
/build/mediastreamer2-2.16.1/src/voip/audiostream.c:816:52: error: cast between 
incompatible function types from 'void (*)(RtpSession *, uint32_t,  void *)' 
{aka 'void (*)(struct _RtpSession *, unsigned int,  void *)'} to 'void 
(*)(struct _RtpSession *, void *, void *, void *)' [-Werror=cast-function-type]
  
rtp_session_signal_connect(rtps,"telephone-event",(RtpCallback)on_dtmf_received,stream);
^
/build/mediastreamer2-2.16.1/src/voip/audiostream.c:817:57: error: cast between 
incompatible function types from 'bool_t (*)(RtpSession *, void *)' {aka 
'unsigned char (*)(struct _RtpSession *, void *)'} to 'void (*)(struct 
_RtpSession *, void *, void *, void *)' [-Werror=cast-function-type]
  
rtp_session_signal_connect(rtps,"payload_type_changed",(RtpCallback)audio_stream_payload_type_changed,stream);
 ^
/build/mediastreamer2-2.16.1/src/voip/audiostream.c: In function 
'audio_stream_stop':
/build/mediastreamer2-2.16.1/src/voip/audiostream.c:1783:94: error: cast 
between incompatible function types from 'void (*)(RtpSession *, uint32_t,  
void *)' {aka 'void (*)(struct _RtpSession *, unsigned int,  void *)'} to 'void 
(*)(struct _RtpSession *, void *, void *, void *)' [-Werror=cast-function-type]
  
rtp_session_signal_disconnect_by_callback(stream->ms.sessions.rtp_session,"telephone-event",(RtpCallback)on_dtmf_received);

  ^
/build/mediastreamer2-2.16.1/src/voip/audiostream.c:1784:99: error: cast 
between incompatible function types from 'bool_t (*)(RtpSession *, void *)' 
{aka 'unsigned char (*)(struct _RtpSession *, void *)'} to 'void (*)(struct 
_RtpSession *, void *, void *, void *)' [-Werror=cast-function-type]
  
rtp_session_signal_disconnect_by_callback(stream->ms.sessions.rtp_session,"payload_type_changed",(RtpCallback)audio_stream_payload_type_changed);

   ^

This seems to be caused by compiling with error and the new compiler
series emitting more diagnostics.


Andreas


mediastreamer2_1%2.16.1-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: mediastreamer2
Source-Version: 1:2.16.1-3

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

Bug#910206: marked as done (libpbbam-dev: missing Breaks+Replaces: libpbbam (<< 0.18))

[Debian Bug Tracking System]

Your message dated Wed, 03 Oct 2018 21:42:23 +
with message-id 
and subject line Bug#910206: fixed in pbbam 0.18.0+dfsg-2
has caused the Debian Bug report #910206,
regarding libpbbam-dev: missing Breaks+Replaces: libpbbam (<< 0.18)
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.)


-- 
910206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpbbam-dev
Version: 0.18.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../8-libpbbam-dev_0.18.0+dfsg-1_amd64.deb ...
  Unpacking libpbbam-dev (0.18.0+dfsg-1) over (0.7.4+ds-1+b1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-IoLOpc/8-libpbbam-dev_0.18.0+dfsg-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libpbbam.so', which is also 
in package libpbbam:amd64 0.7.4+ds-1+b1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-IoLOpc/8-libpbbam-dev_0.18.0+dfsg-1_amd64.deb


cheers,

Andreas


libpbbam-dev_0.18.0+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pbbam
Source-Version: 0.18.0+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated pbbam package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 03 Oct 2018 22:24:56 +0200
Source: pbbam
Binary: pbbamtools libpbbam0.18.0 libpbbam-dev
Architecture: source
Version: 0.18.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libpbbam-dev - Pacific Biosciences binary alignment/map (BAM) library (headers)
 libpbbam0.18.0 - Pacific Biosciences binary alignment/map (BAM) library
 pbbamtools - processing Pacific Biosciences binary alignment/map files
Closes: 910206
Changes:
 pbbam (0.18.0+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * Missing Breaks+Replaces: libpbbam (<< 0.18)
 Closes: #910206
   * No needs-recommends restrictions, just Test-Depends: samtools
Checksums-Sha1:
 6e5c7c769717ee568a84ec5a9731037109a06087 2308 pbbam_0.18.0+dfsg-2.dsc
 431bac00e17ec1fb8b5019f5648f12e226d446d6 6944 pbbam_0.18.0+dfsg-2.debian.tar.xz
Checksums-Sha256:
 39fe56701d0a0b5168d38bc8a2f4d07775a614ca39d3b860e17c278ac409e48b 2308 
pbbam_0.18.0+dfsg-2.dsc
 31fa0d48262b9a0045e63ba87322bdce223e8dc6db47b8c6b2452ec6971c970b 6944 
pbbam_0.18.0+dfsg-2.debian.tar.xz
Files:
 f27ac2df56e156672ca58b6234ebcd15 2308 science optional pbbam_0.18.0+dfsg-2.dsc
 085f653157e471237a4e6dcf5dec8431 6944 science optional 
pbbam_0.18.0+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlu1KK8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEamg//SGKKSX3qc/so3Tgci6grvt39/F/PchSS
Pac+gYzZ1Mn4nwUS2lNrnx2S5UilNzsoX/b3AgfkhBjlOahalewkpTdmkXRN4m78
SWez8Ww+p1yK1zzQ0GKUbYkS4g7cFGpaAXWKV/F1Ks/qp55AJBm4h0fc1SPvY4YG
vs53E57d6edxi8xO/nnjyb4s4v9E3nnXIKcu+Dy0KYJFZQT9zU7uicMSMaBTKPoJ
BUaY3fMrkDnHbjaFPye71b2WhyOv3jjyk8lIfSipWquDXU/Dve3DS/IpgWjrpyjg
5JU+zST+ZBWJdM27iQwwJTasA+cbRu6Dj2GDcOjzjrADTnEBYIsPlDDDJNKaWNHR
MKapdDwey7NCVSuzLd7n5CwwqqVUK/ENY56R3xCnsbKZyL5ta9sti8E0It+1mfP6
MTdLTVwW7TvInO8XtU1Ut/QIukCTaENyh7g/Y/uytj3RBI9ynJTL67px4x6pCypq
df3ku3nzuokkReIfyVTE1iUzpmO+S0YOWPtORUcZVPhyfS062YPBdjJVSsuqh1HW
WyoKA9ujmUvgEgu3Vid+yepAHc0W1JGoLV7yHHUirCq4P7VaK3U8tEfBAUebAWCn
gZPK8y8GpI3NI1/h7+hk70rQbdX76rlwjMJFWDvspVNw8AepLu+U7ipIc6+0l+L1
qB6O6fL+pKE=
=KPkN
-END PGP SIGNATURE End Message ---

Bug#910230: marked as done (libactivation-java: missing Breaks+Replaces: glassfish-activation)

[Debian Bug Tracking System]

Your message dated Wed, 03 Oct 2018 21:39:18 +
with message-id 
and subject line Bug#910230: fixed in javabeans-activation-framework 1.2.0-2
has caused the Debian Bug report #910230,
regarding libactivation-java: missing Breaks+Replaces: glassfish-activation
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.)


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

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie' to 'stretch' to 'buster'.
It installed fine in 'jessie', and upgraded to 'stretch' successfully,
but then the upgrade to 'buster' failed.

In case the package was not part of an intermediate stable release,
the version from the preceding stable release was kept installed.

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

  Selecting previously unselected package libactivation-java.
  Preparing to unpack .../23-libactivation-java_1.2.0-1_all.deb ...
  Unpacking libactivation-java (1.2.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-pUdXjX/23-libactivation-java_1.2.0-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/maven-repo/javax/activation/activation/debian/activation-debian.pom',
 which is also in package glassfish-activation 1:2.1.1-b31g+dfsg1-2


cheers,

Andreas


libstax-ex-java_1.7.8-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: javabeans-activation-framework
Source-Version: 1.2.0-2

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated 
javabeans-activation-framework package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 03 Oct 2018 22:51:36 +0200
Source: javabeans-activation-framework
Binary: libactivation-java
Architecture: source
Version: 1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libactivation-java - JavaBeans Activation Framework
Closes: 910230
Changes:
 javabeans-activation-framework (1.2.0-2) unstable; urgency=medium
 .
   * libactivation-java breaks/replaces glassfish-activation from Jessie
 (Closes: #910230)
   * Standards-Version updated to 4.2.1
   * Switch to debhelper level 11
   * Use salsa.debian.org Vcs-* URLs
Checksums-Sha1:
 2e56c5e31a7704eb393271955b3b78506bfed862 2297 
javabeans-activation-framework_1.2.0-2.dsc
 1bc38df58c8dc8878de8bda7a3120e5030c7fec1 9216 
javabeans-activation-framework_1.2.0-2.debian.tar.xz
 d7c8e46b102c186a55efad67443844203f9c 15926 
javabeans-activation-framework_1.2.0-2_source.buildinfo
Checksums-Sha256:
 8623a905044cb70d0054365702188d1d240c8ff2146b9bd788cb30e97da1ca93 2297 
javabeans-activation-framework_1.2.0-2.dsc
 23091cb26022198a9d96bbf6e73c72cdf13f2df14df112fa8aff09ab85965df9 9216 
javabeans-activation-framework_1.2.0-2.debian.tar.xz
 183785d09093f5d51772fbce0722a52261feddb0d2fa4c4f5f41ae5bc54a266f 15926 
javabeans-activation-framework_1.2.0-2_source.buildinfo
Files:
 299f2f6c0cefdfc0ff386238c84b807a 2297 java optional 
javabeans-activation-framework_1.2.0-2.dsc
 60a646e14bc1657332ba4178a71fe798 9216 java optional 
javabeans-activation-framework_1.2.0-2.debian.tar.xz
 ba5a6c202005bee3ce4d5e68ae1ac2e2 15926 java optional 
javabeans-activation-framework_1.2.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlu1LaASHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsRUMQALzAtVhA0sYiwcpojqznFnhpk1j/ZVW8
dLY7Y5Gj8nPA7leaY5gCTTfXjEopTqqJnWcAckG7Ju8XX03mLaZ3+QQG2yTZJrbK
xMOGSyTJawMB0Q6riAKmjh4ktUxJqVhOKyzk/xoxuyUYt+guxiND7X9dLUOilpQu
OLO14IsBp7QVf7JRLRzDK19LoKPLJRSLf9hzAXpsF2UH4fO7gfZ2asJh3Bb9OojF
irjGJIWE3O1aLieG8luHatf0NH7v/14C+3iTXmRRNjP1q22aOSstBcWZPICdyttQ
wAuk0RWd6ksMbPwcEPST5z0Rb93XiOLSOgzvAPLbw7hNmOD1GiepboYEYCOFtCgW
2otUjI3XI22q1QuFFTeYjw/0

Bug#910230: Bug #910230 in javabeans-activation-framework marked as pending

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/javabeans-activation-framework/commit/7c0faf9be3b17795ab6073e2975601cbb2dbe96a


libactivation-java breaks/replaces glassfish-activation from Jessie (Closes: 
#910230)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/910230

Processed: Bug #910230 in javabeans-activation-framework marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #910230 [libactivation-java] libactivation-java: missing Breaks+Replaces: 
glassfish-activation
Added tag(s) pending.

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

Bug#906358: marked as done (gimp-help: FTBFS in buster/sid (You must have automake 1.10 or newer installed))

[Debian Bug Tracking System]

Your message dated Wed, 03 Oct 2018 20:43:07 +
with message-id 
and subject line Bug#906358: fixed in gimp-help 2.8.2-0.2
has caused the Debian Bug report #906358,
regarding gimp-help: FTBFS in buster/sid (You must have automake 1.10 or newer 
installed)
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.)


-- 
906358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gimp-help
Version: 2.8.2-0.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=autoreconf #--builddirectory=build 
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -i
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf ./autogen.sh
dh_autoreconf: Compatibility levels before 9 are deprecated (level 7 in use)
Looking for latest automake version ... 
  You must have automake 1.10 or newer installed to compile gimp-help-2.
  Download the appropriate package for your distribution,
  or get the source tarball at ftp://ftp.gnu.org/pub/gnu/automake/

Please install/upgrade the missing tools and call me again.

dh_autoreconf: ./autogen.sh returned exit code 1
make[1]: *** [debian/rules:19: override_dh_autoreconf] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:13: 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/gimp-help.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: gimp-help
Source-Version: 2.8.2-0.2

We believe that the bug you reported is fixed in the latest version of
gimp-help, 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.
Adrian Bunk  (supplier of updated gimp-help package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Sep 2018 21:21:52 +0300
Source: gimp-help
Binary: gimp-help-common gimp-help-ca gimp-help-de gimp-help-el gimp-help-en 
gimp-help-es gimp-help-fr gimp-help-it gimp-help-ja gimp-help-ko gimp-help-nl 
gimp-help-nn gimp-help-pt gimp-help-ru gimp-help-sl gimp-help-sv
Architecture: source
Version: 2.8.2-0.2
Distribution: unstable
Urgency: medium
Maintainer: Ari Pollak 
Changed-By: Adrian Bunk 
Description:
 gimp-help-ca - Documentation for the GIMP (Catalan)
 gimp-help-common - Data files for the GIMP documentation
 gimp-help-de - Documentation for the GIMP (German)
 gimp-help-el - Documentation for the GIMP (Greek)
 gimp-help-en - Documentation for the GIMP (English)
 gimp-help-es - Documentation for the GIMP (Spanish)
 gimp-help-fr - Documentation for the GIMP (French)
 gimp-help-it - Documentation for the GIMP (Italian)
 gimp-help-ja - Documentation for the GIMP (Japanese)
 gimp-help-ko - Documentation for the GIMP (Korean)
 gimp-help-nl - Documentation for the GIMP (Dutch)
 gimp-help-nn - Documentation for the GIMP (Norwegian)
 gimp-help-pt - Documentation for the GIMP (Portuguese)
 gimp-help-ru - Documentation for the GIMP (Russian)
 gimp-help-sl - Documentation for the GIMP (Slovenian)
 gimp-help-sv - Documentation for the GIMP (Swedish)
Closes: 906358
Changes:
 gimp-help (2.8.2-0.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add upstream fix for FTBFS with automake 1.16,
 thanks to Juhani Numminen. (Closes: #906358)
Checksums-Sha1:
 baab31dd63b660db638df307a87bc8df6272308c 2720 gimp-help_2.8.2-0.2.dsc
 09f8d4857a8b495bbc24e81b409c256796c6ed82 

Bug#897743: marked as done (eris: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Wed, 03 Oct 2018 20:39:48 +
with message-id 
and subject line Bug#897743: fixed in eris 1.3.23-7
has caused the Debian Bug report #897743,
regarding eris: 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.)


-- 
897743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:eris
Version: 1.3.23-6
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/eris_1.3.23-6_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

[...]
+ 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6AvatarEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESM_IJESt17_Rb_tree_iteratorISB_ESt23_Rb_tree_const_iteratorISB_EDpOT_@Base
 1.3.23-6
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6AvatarEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE24_M_get_insert_unique_posERS7_@Base
 1.3.23
  
(optional=certain_64b_arches)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6AvatarEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISB_ERS7_@Base
 1.3.23
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6AvatarEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE8_M_eraseEPSt13_Rb_tree_nodeISB_E@Base
 1.3.23
  
(optional=certain_64b_arches)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6EntityEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE11equal_rangeERS7_@Base
 1.3.23
+ 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6EntityEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESM_IJESt17_Rb_tree_iteratorISB_ESt23_Rb_tree_const_iteratorISB_EDpOT_@Base
 1.3.23-6
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6EntityEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE24_M_get_insert_unique_posERS7_@Base
 1.3.23
  
(optional=certain_64b_arches)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6EntityEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISB_ERS7_@Base
 1.3.23
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6EntityEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE8_M_eraseEPSt13_Rb_tree_nodeISB_E@Base
 1.3.23
+ 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESM_IJESt17_Rb_tree_iteratorISB_ESt23_Rb_tree_const_iteratorISB_EDpOT_@Base
 1.3.23-6
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE24_M_get_insert_unique_posERS7_@Base
 1.3.23
  
(optional=certain_64b_arches)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISB_ERS7_@Base
 1.3.23
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE4findERS7_@Base
 1.3.23
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonE

Bug#909539: dds: test failures on multiple Ubuntu architectures

[Helmut Grohne]

On Wed, Oct 03, 2018 at 10:01:58PM +0200, Christoph Berg wrote:
> It is parsing the `free` output to probe available memory. The code is
> utterly wrong since free had been changed to output only two lines
> instead of three, so it looks at the amount of swap available. I
> haven't checked, but my guess is that on systems without swap, you'll
> get the above error.

I confirm that the system where it fails lacks swap and that my local
system where it succeeds does have swap. Your hypothesis fully matches
my observations.

Helmut

Bug#909352: Was severity serious intended?

[Marcin Owsiany]

śr., 3 paź 2018, 21:49 użytkownik Adrian Bunk  napisał:

> On Wed, Oct 03, 2018 at 09:14:15PM +0200, Marcin Owsiany wrote:
> > Maybe I'm missing something, but what was the reason for filing #909352
> as
> > serious? Looking at #892016 it does not seem like it was the cause of the
> > segfault? Or was it?
>
> No.
>
> > If not, then getting rid of squeak-plugins-scratch sounds more like a
> > wishlist cleanup request to me than a serious bug.
>
> "package is completely useless" tends to be treated as RC.
>

I'm not sure I agree, since having reverse-dependencies seems to prove the
contrary.


> > All the more that
> > removing squeak-plugins-scratch from testing will cause scratch to be
> > removed, which is not a great outcome for those using it.
> >
> > Can you please provide a rationale or downgrade the severity?
>
> Downgrading the severity wouldn't make sense.
>
> If it is intentional that squeak-plugins-scratch provides only plugins
> that are already in squeak-vm, then this bug should be closed with an
> explanation why this is intentional.
>
> If it is not intentional that squeak-plugins-scratch provides only
> plugins that are already in squeak-vm and it is no longer needed,
> then fixing the two reverse dependencies is trivial.
>

Right, but it still requires work, which nobody volunteered to do so far,
so one could argue that a high severity is a disservice for our users in
the short term...

Anyway, thank you for the explanation.


Marcin

Bug#909539: dds: test failures on multiple Ubuntu architectures

[Christoph Berg]

Re: Helmut Grohne 2018-10-03 <20181003191607.ga11...@alf.mars>
> > make[2]: Leaving directory '/<>/examples'
> > LD_LIBRARY_PATH=src examples/DealerPar
> > Memory::GetPtr: 0 vs. 0
> 
> I got exactly this with sbuild in unstable/amd64 with a stretch kernel
> on a haswell cpu. On another system (with less cores), I could not
> reproduce it at all. Still I think that two independent submitters are
> enough to call this a real ftbfs.

It is parsing the `free` output to probe available memory. The code is
utterly wrong since free had been changed to output only two lines
instead of three, so it looks at the amount of swap available. I
haven't checked, but my guess is that on systems without swap, you'll
get the above error.

I tried using a more sensible mechanism via sysconf(), but I'm not
sure yet which number is the correct one to use. (Probably
_SC_PHYS_PAGES rather than _SC_AVPHYS_PAGES.)

Christoph

Bug#909352: Was severity serious intended?

[Adrian Bunk]

On Wed, Oct 03, 2018 at 09:14:15PM +0200, Marcin Owsiany wrote:
> Maybe I'm missing something, but what was the reason for filing #909352 as
> serious? Looking at #892016 it does not seem like it was the cause of the
> segfault? Or was it?

No.

> If not, then getting rid of squeak-plugins-scratch sounds more like a
> wishlist cleanup request to me than a serious bug.

"package is completely useless" tends to be treated as RC.

> All the more that
> removing squeak-plugins-scratch from testing will cause scratch to be
> removed, which is not a great outcome for those using it.
> 
> Can you please provide a rationale or downgrade the severity?

Downgrading the severity wouldn't make sense.

If it is intentional that squeak-plugins-scratch provides only plugins 
that are already in squeak-vm, then this bug should be closed with an
explanation why this is intentional.

If it is not intentional that squeak-plugins-scratch provides only 
plugins that are already in squeak-vm and it is no longer needed,
then fixing the two reverse dependencies is trivial.

> Marcin

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#910182: cloud-init FTBFS: tests fail

[Thomas Goirand]

On 10/3/18 1:44 PM, Helmut Grohne wrote:
> Source: cloud-init
> Version: 0.7.9-5
> Severity: serious
> Tags: ftbfs
> 
> Building cloud-init in unstable on amd64 fails in sbuild. The build ends
> with:

That's kind of fine, as I'm planning for uploading the version which is
currently in Experimental next week.

Cheers,

Thomas Goirand (zigo)

Processed: Re: Bug#909539: dds: test failures on multiple Ubuntu architectures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + ftbfs
Bug #909539 [src:dds] dds: test failures on multiple Ubuntu architectures
Added tag(s) ftbfs.
> severity -1 serious
Bug #909539 [src:dds] dds: test failures on multiple Ubuntu architectures
Severity set to 'serious' from 'normal'

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

Bug#909352: Was severity serious intended?

[Marcin Owsiany]

Maybe I'm missing something, but what was the reason for filing #909352 as
serious? Looking at #892016 it does not seem like it was the cause of the
segfault? Or was it?

If not, then getting rid of squeak-plugins-scratch sounds more like a
wishlist cleanup request to me than a serious bug. All the more that
removing squeak-plugins-scratch from testing will cause scratch to be
removed, which is not a great outcome for those using it.

Can you please provide a rationale or downgrade the severity?

Marcin

Bug#908580: marked as done (ibus-table-createdb fails with nonexisting $HOME)

[Debian Bug Tracking System]

Your message dated Wed, 03 Oct 2018 15:12:24 -0400
with message-id <6f6782d6f470e09ee68f6030d230978180cb506d.ca...@gmail.com>
and subject line Properly close bug #908580
has caused the Debian Bug report #908580,
regarding ibus-table-createdb fails with nonexisting $HOME
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.)


-- 
908580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ibus-table
Version: 1.9.21-1
Severity: serious
Control: affects -1 src:ibus-table-others

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ibus-table-others.html

...
/usr/bin/ibus-table-createdb  -n compose.db -s compose.txt
Traceback (most recent call last):
  File "/usr/share/ibus-table/engine/tabcreatedb.py", line 455, in 
main()
  File "/usr/share/ibus-table/engine/tabcreatedb.py", line 175, in main
create_database=True)
  File "/usr/share/ibus-table/engine/tabsqlitedb.py", line 262, in __init__
import ibus_table_location
  File "/usr/share/ibus-table/engine/ibus_table_location.py", line 102, in 

__module_init = __ModuleInitializer()
  File "/usr/share/ibus-table/engine/ibus_table_location.py", line 96, in 
__init__
_init()
  File "/usr/share/ibus-table/engine/ibus_table_location.py", line 76, in _init
os.makedirs(IBUS_TABLE_LOCATION['data_home'])
  File "/usr/lib/python3.6/os.py", line 210, in makedirs
makedirs(head, mode, exist_ok)
  File "/usr/lib/python3.6/os.py", line 210, in makedirs
makedirs(head, mode, exist_ok)
  File "/usr/lib/python3.6/os.py", line 210, in makedirs
makedirs(head, mode, exist_ok)
  File "/usr/lib/python3.6/os.py", line 220, in makedirs
mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: '/nonexistent'
make[2]: *** [Makefile:519: compose.db] Error 1


This can be reproduced with:

# works
$ HOME=/tmp /usr/bin/ibus-table-createdb -n compose.db -s compose.txt

# fails
$ HOME=/doesnotexist /usr/bin/ibus-table-createdb -n compose.db -s compose.txt
--- End Message ---
--- Begin Message ---
Version: 1.9.21-2

Thanks,
Boyuan Yang--- End Message ---

Bug#910242: samba-libs: missing Breaks+Replaces: libndr-standard0

[Andreas Beckmann]

Package: samba-libs
Version: 2:4.8.5+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy' to 'jessie' to 'stretch' to 'buster'.
Its successor installed fine in 'wheezy', and upgraded to 'jessie' and 'stretch'
successfully,
but then the upgrade to 'buster' failed,
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package samba-libs:amd64.
  Preparing to unpack .../29-samba-libs_2%3a4.8.5+dfsg-1_amd64.deb ...
  Unpacking samba-libs:amd64 (2:4.8.5+dfsg-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-sgTROH/29-samba-libs_2%3a4.8.5+dfsg-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libndr-krb5pac.so.0.0.1', 
which is also in package libndr-standard0:amd64 4.0.0~beta2+dfsg1-3.2+deb7u2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)


libndr-standard0 was last seen in oldoldstable.


cheers,

Andreas


samba4-testsuite_None.log.gz
Description: application/gzip

Bug#905180: libmoe-dev: missing Breaks+Replaces: libmoe1.5 (<< 1.5.8-3)

[Andreas Beckmann]

Followup-For: Bug #905180

Hi,

you added Breaks and Replaces against
  libmoe (<< 1.5.8-3)
but this needs to be
  libmoe1.5 (<< 1.5.8-3)


Andreas

Processed: found 910199 in 1.13.1-7

[Debian Bug Tracking System]

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

> found 910199 1.13.1-7
Bug #910199 [python3-adios] python3-adios: fails to install: 
python3-adios.postinst: Syntax error: "(" unexpected
Marked as found in versions adios/1.13.1-7.
> thanks
Stopping processing here.

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

Processed: severity of 910199 is serious

[Debian Bug Tracking System]

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

> severity 910199 serious
Bug #910199 [python3-adios] python3-adios: fails to install: 
python3-adios.postinst: Syntax error: "(" unexpected
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: Re: Bug#910128: bash-completion parallel FTBFS

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/scop/bash-completion/issues/212
Bug #910128 [src:bash-completion] bash-completion parallel FTBFS
Set Bug forwarded-to-address to 
'https://github.com/scop/bash-completion/issues/212'.
> tags -1 fixed-upstream patch
Bug #910128 [src:bash-completion] bash-completion parallel FTBFS
Added tag(s) fixed-upstream and patch.

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

Bug#910128: bash-completion parallel FTBFS

[Adrian Bunk]

Control: forwarded -1 https://github.com/scop/bash-completion/issues/212
Control: tags -1 fixed-upstream patch

On Wed, Oct 03, 2018 at 07:33:34AM +0200, Helmut Grohne wrote:
>...
> Notably, the completion directory is created after adding symlinks into
> it. Looking at the generated completions/Makefile, one can see the
> cause: The symlinks target creates the symlinks and depends on
> $(targetdir), but there is no target for $(targetdir). Instead, the
> completion directory is created by install-bashcompDATA and these
> targets are fully independent. install-data-am depends on
> install-bashcompDATA and install-data-local. The latter depends on
> symlinks. We'd need a dependency from symlinks on install-bashcompDATA,
> but I have no clue how to add that in completions/Makefile.am.

https://github.com/scop/bash-completion/commit/ee6b37ad7ff5b309cbb9b886a871252abd9398fa

> Hope this helps anyway
> 
> Helmut

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#910234: python-minimal: add Conflicts against python-central

[Andreas Beckmann]

Package: python-minimal
Version: 2.7.15-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that packages using
python-central (last seen in oldstable) may have been kept installed
over all distupgrade steps to buster. But these packages cannot be
uninstalled any longer, since pycentral errors out with

  ValueError: /usr/bin/python does not match the python default version.
  It must be reset to point to python2.7

since the /usr/bin/python symlink points to python2 instead of python2.7

Let's ensure that these cruft packages get removed on upgrades from
stretch to buster (before the new python-minimal is unpacked) by adding 
  Conflicts: python-central
to python-minimal.


An upgrade log from python-irclib showing this problem is attached.


Thanks

Andreas


python-irclib_None.log.gz
Description: application/gzip

Bug#910233: libsvn-{dev,java}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: libsvn-dev,libsvn-java
Version: 1.10.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  wheezy -> jessie -> stretch -> buster

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

1m32.4s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libsvn-dev/changelog.Debian.gz (libsvn-dev:amd64) != 
/usr/share/doc/libsvn1/changelog.Debian.gz (libsvn1:amd64)
/usr/share/doc/libsvn-dev -> /usr/share/doc/libsvn1
  /usr/share/doc/libsvn-dev/changelog.gz (libsvn-dev:amd64) != 
/usr/share/doc/libsvn1/changelog.gz (libsvn1:amd64)
/usr/share/doc/libsvn-dev -> /usr/share/doc/libsvn1
  /usr/share/doc/libsvn-dev/copyright (libsvn-dev:amd64) != 
/usr/share/doc/libsvn1/copyright (libsvn1:amd64)
/usr/share/doc/libsvn-dev -> /usr/share/doc/libsvn1

1m37.7s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libsvn-java/changelog.Debian.gz (libsvn-java) != 
/usr/share/doc/libsvn1/changelog.Debian.gz (libsvn1:amd64)
/usr/share/doc/libsvn-java -> /usr/share/doc/libsvn1
  /usr/share/doc/libsvn-java/changelog.gz (libsvn-java) != 
/usr/share/doc/libsvn1/changelog.gz (libsvn1:amd64)
/usr/share/doc/libsvn-java -> /usr/share/doc/libsvn1
  /usr/share/doc/libsvn-java/copyright (libsvn-java) != 
/usr/share/doc/libsvn1/copyright (libsvn1:amd64)
/usr/share/doc/libsvn-java -> /usr/share/doc/libsvn1


Even if it was forgotten to properly handle this transition
in jessie, it is not too late to finally clean this up for buster.


cheers,

Andreas


libsvn-dev_1.10.2-1.log.gz
Description: application/gzip

Processed: add ftbfs tag

[Debian Bug Tracking System]

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

> tags 806100 + ftbfs
Bug #806100 [src:pyviennacl] pyviennacl: FTBFS when built with 
dpkg-buildpackage -A (No such file or directory)
Added tag(s) ftbfs.
> tags 806127 + ftbfs
Bug #806127 [src:zope2.13] zope2.13: FTBFS when built with dpkg-buildpackage -A 
(No such file or directory)
Added tag(s) ftbfs.
> tags 806624 + ftbfs
Bug #806624 [src:ikvm] ikvm: FTBFS when built with dpkg-buildpackage -A (mkdir: 
File exists)
Added tag(s) ftbfs.
> tags 806873 + ftbfs
Bug #806873 [src:roboptim-core] roboptim-core: FTBFS when built with 
dpkg-buildpackage -A (24 tests failed out of 24)
Added tag(s) ftbfs.
> tags 813015 + ftbfs
Bug #813015 [src:mlpy] mlpy: FTBFS: error: unbalanced parenthesis
Added tag(s) ftbfs.
> tags 817126 + ftbfs
Bug #817126 [src:grafana] grafana: FTBFS when built with dpkg-buildpackage -A 
(unable to chdir to _build)
Added tag(s) ftbfs.
> tags 817810 + ftbfs
Bug #817810 [src:emscripten] emscripten: FTBFS when built with 
dpkg-buildpackage -A (ln: failed to create symbolic link)
Added tag(s) ftbfs.
> tags 828429 + ftbfs
Bug #828429 [src:mailavenger] mailavenger: FTBFS with openssl 1.1.0
Added tag(s) ftbfs.
> tags 828481 + ftbfs
Bug #828481 [src:ori] ori: FTBFS with openssl 1.1.0
Added tag(s) ftbfs.
> tags 828483 + ftbfs
Bug #828483 [src:osslsigncode] osslsigncode: FTBFS with openssl 1.1.0
Added tag(s) ftbfs.
> tags 831925 + ftbfs
Bug #831925 [src:docbook2odf] docbook2odf: FTBFS with dpkg-buildpackage -A: 
dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
distribute
Added tag(s) ftbfs.
> tags 831939 + ftbfs
Bug #831939 [src:jailer] jailer: FTBFS with dpkg-buildpackage -A: 
dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
distribute
Added tag(s) ftbfs.
> tags 831952 + ftbfs
Bug #831952 [src:thp] thp: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: 
error: binary build with no binary artifacts found; cannot distribute
Added tag(s) ftbfs.
> tags 834917 + ftbfs
Bug #834917 [src:python-async] python-async: FTBFS on single CPU machines
Added tag(s) ftbfs.
> tags 836934 + ftbfs
Bug #836934 [src:frobtads] frobtads: FTBFS with GCC 6: error: exception cleanup 
for this placement new selects non-placement operator delete
Added tag(s) ftbfs.
> tags 837361 + ftbfs
Bug #837361 [src:fsl] fsl: FTBFS with GCC 6: error: no match for 'operator>' 
(operand types are 'std::ifstream' and 'int')
Added tag(s) ftbfs.
> tags 839374 + ftbfs
Bug #839374 [src:kcov] kcov: FTBFS: ld: final link failed: Nonrepresentable 
section on output
Added tag(s) ftbfs.
> tags 839432 + ftbfs
Bug #839432 [src:libmonitoring-availability-perl] 
libmonitoring-availability-perl: FTBFS: Tests failures
Added tag(s) ftbfs.
> tags 844145 + ftbfs
Bug #844145 [src:elektra] elektra: FTBFS: kdberrors.h:489:0: error: invalid 
storage class for function 'elektraSetErrorf8'
Added tag(s) ftbfs.
> tags 849574 + ftbfs
Bug #849574 [src:gtkdataboxmm] gtkdataboxmm: FTBFS when built with 
dpkg-buildpackage -A (Makefile error)
Added tag(s) ftbfs.
> tags 851048 + ftbfs
Bug #851048 [src:dipy] dipy: FTBFS: x86_64-linux-gnu-gcc: error: /arch:SSE2: No 
such file or directory
Added tag(s) ftbfs.
> tags 852913 + ftbfs
Bug #852913 [src:ocaml-re2] ocaml-re2: FTBFS: unsatisfiable build-dependencies: 
libcore-ocaml-dev, libpa-test-camlp4-dev, libbin-prot-camlp4-dev, 
libsexplib-camlp4-dev
Added tag(s) ftbfs.
> tags 868918 + ftbfs
Bug #868918 [src:pymc] pymc: FTBFS: ld: cannot find -lcblas
Added tag(s) ftbfs.
> tags 868920 + ftbfs
Bug #868920 [src:arora] arora: FTBFS: 
../../src/network/cookiejar/cookiejar.cpp:81:12: error: ambiguous overload for 
'operator<<' (operand types are 'QDataStream' and 'const unsigned int')
Added tag(s) ftbfs.
> tags 868928 + ftbfs
Bug #868928 [src:dmtcp] dmtcp: FTBFS: pidwrappers.h:191:20: error: 
'__WAIT_STATUS' was not declared in this scope
Added tag(s) ftbfs.
> tags 868929 + ftbfs
Bug #868929 [src:kfreebsd-10] kfreebsd-10: FTBFS: 
../../../compat/ia32/ia32_genassym.c:1:0: error: code model kernel does not 
support PIC mode
Added tag(s) ftbfs.
> tags 868970 + ftbfs
Bug #868970 [src:rcs-blame] rcs-blame: FTBFS: ./lib/argp.h:587: multiple 
definition of `argp_usage'
Added tag(s) ftbfs.
> tags 868971 + ftbfs
Bug #868971 [src:python-feather-format] python-feather-format: FTBFS: 
feather/ext.cpp:28:20: fatal error: Python.h: No such file or directory
Added tag(s) ftbfs.
> tags 868974 + ftbfs
Bug #868974 [src:roboptim-core] roboptim-core: FTBFS: terminal-color.hh:40:13: 
error: no match for 'operator==' (operand types are 'std::ostream {aka 
std::basic_ostream}' and 'std::ostream {aka std::basic_ostream}')
Added tag(s) ftbfs.
> tags 871215 + ftbfs
Bug #871215 [src:frobtads] frobtads: FTBFS with GCC-7: error: ISO C++ forbids 
comparison between pointer and integer
Added tag(s) ftbfs.
> tags 872635 + ftbfs
Bug #872635 [src:util-linux] util-linux: FTBFS on armel: test failure
Added tag(s) ftbfs.
> tags 873993 + ftbfs
Bug #873993 [src:munin] FTBFS w

Bug#902753: marked as done (fflas-ffpack FTBFS on 32bit big endian: test failure)

[Debian Bug Tracking System]

Your message dated Wed, 03 Oct 2018 17:19:17 +
with message-id 
and subject line Bug#902753: fixed in fflas-ffpack 2.3.2-3
has caused the Debian Bug report #902753,
regarding fflas-ffpack FTBFS on 32bit big endian: test failure
to be marked as done.

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

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


-- 
902753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fflas-ffpack
Version: 2.3.2-1~exp1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=fflas-ffpack&suite=sid

...
Checking Modular, RecInt::ruint<8>> modulo 
137086259543411796519661122363958397351 ... FAIL
alpha   :1, beta   : 0
m   :10, k   : 37
ldA :49, incX : 1, incY : 8
Error Y[0]=1992134205620791178773468912365171 
D[0]=33516737080336839904404042326759926523
Error Y[1]=19012610462383539819047065227639652127 
D[1]=33027539844715459854001461431663776355
Error Y[2]=36275471608480693956989447364591853611 
D[2]=71305711375164665192185413746827937790
Error Y[3]=16802259068307208301092687002429463235 
D[3]=111805956383619924708206385812549612197
Error Y[4]=37497646901470143638708872110055354636 
D[4]=10851073192729426488164756656238986655
Error Y[5]=111941573376661391371080194781913260186 
D[5]=87502874614680165651743215857944944321
Error Y[6]=24854382304849165236729549431699250443 
D[6]=100589182556177209784894408578247046121
Error Y[7]=64877439080209582754648837426698863426 
D[7]=75580908271244353910959300344839680750
Error Y[8]=77890500635456927145236262383571288034 
D[8]=84739061027717235821509912345371008426
Error Y[9]=68356228138285939741967710419270414124 
D[9]=13534641280687414727768176760958703984
XX
FAILED 
FAIL test-fgemv (exit status: 1)


Testsuite summary for FFLAS-FFPACK 2.3.2

# TOTAL: 31
# PASS:  29
# SKIP:  0
# XFAIL: 0
# FAIL:  2
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to ffpack-de...@googlegroups.com

make[5]: *** [Makefile:1513: test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Source: fflas-ffpack
Source-Version: 2.3.2-3

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

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

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

Debian distribution maintenance software
pp.
Doug Torrance  (supplier of updated fflas-ffpack 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 02 Oct 2018 20:19:30 -0400
Source: fflas-ffpack
Binary: fflas-ffpack fflas-ffpack-common fflas-ffpack-user-doc 
fflas-ffpack-dev-doc
Architecture: source
Version: 2.3.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Doug Torrance 
Description:
 fflas-ffpack - Finite field linear algebra subroutines/package
 fflas-ffpack-common - Finite field linear algebra subroutines/package - common 
files
 fflas-ffpack-dev-doc - FFLAS-FFPACK Developer Documentation
 fflas-ffpack-user-doc - FFLAS-FFPACK User Documentation
Closes: 902753 907010
Changes:
 fflas-ffpack (2.3.2-3) unstable; urgency=medium
 .
   * debian/compat
 - Bump debhelper compatibility level to 11.
   * debian/control
 - Bump versioned dependency on debhelper to >= 11.
 - Bump Standards-Version to 4.2.1.
   * debian/copyright
 - Remove paragraph for fflas-ffpack/utils/print-utils.h; file no longer
   exists.
   * debian/docs
 - Remove nonexistent NEWS.
   * debian/fflas-ffpack-*-doc.doc-base
 - Update paths to documentation.
   * debian/fflas-ffpack-*-doc.docs
 - Install documentation subdirectories instead of files within these
   subdirectories.  Since both documentation packages now install to
   /usr/share/fflas-ffpack, we do not want any file conflicts.
   * debian/fflas-ffpack-*-doc.lintian-overrides
 - Remove files; as of v2.5.57, lintian no longer warn

Bug#907010: marked as done (fflas-ffpack: baseline violation on i386)

[Debian Bug Tracking System]

Your message dated Wed, 03 Oct 2018 17:19:17 +
with message-id 
and subject line Bug#907010: fixed in fflas-ffpack 2.3.2-3
has caused the Debian Bug report #907010,
regarding fflas-ffpack: baseline violation on i386
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.)


-- 
907010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fflas-ffpack
Version: 2.3.2-1~exp3
Severity: serious

SSE is not part of the i386 baseline.
--- End Message ---
--- Begin Message ---
Source: fflas-ffpack
Source-Version: 2.3.2-3

We believe that the bug you reported is fixed in the latest version of
fflas-ffpack, 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.
Doug Torrance  (supplier of updated fflas-ffpack 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 02 Oct 2018 20:19:30 -0400
Source: fflas-ffpack
Binary: fflas-ffpack fflas-ffpack-common fflas-ffpack-user-doc 
fflas-ffpack-dev-doc
Architecture: source
Version: 2.3.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Doug Torrance 
Description:
 fflas-ffpack - Finite field linear algebra subroutines/package
 fflas-ffpack-common - Finite field linear algebra subroutines/package - common 
files
 fflas-ffpack-dev-doc - FFLAS-FFPACK Developer Documentation
 fflas-ffpack-user-doc - FFLAS-FFPACK User Documentation
Closes: 902753 907010
Changes:
 fflas-ffpack (2.3.2-3) unstable; urgency=medium
 .
   * debian/compat
 - Bump debhelper compatibility level to 11.
   * debian/control
 - Bump versioned dependency on debhelper to >= 11.
 - Bump Standards-Version to 4.2.1.
   * debian/copyright
 - Remove paragraph for fflas-ffpack/utils/print-utils.h; file no longer
   exists.
   * debian/docs
 - Remove nonexistent NEWS.
   * debian/fflas-ffpack-*-doc.doc-base
 - Update paths to documentation.
   * debian/fflas-ffpack-*-doc.docs
 - Install documentation subdirectories instead of files within these
   subdirectories.  Since both documentation packages now install to
   /usr/share/fflas-ffpack, we do not want any file conflicts.
   * debian/fflas-ffpack-*-doc.lintian-overrides
 - Remove files; as of v2.5.57, lintian no longer warns when there are
   embedded jQuery libraries for Doxygen.
   * debian/patches/do-not-cp-INSTALL-or-COPYING.patch
 - Rename patch from do-not-fail-cp-INSTALL.patch.  We also do not copy
   COPYING as the extra copies resulted in extra-license-file lintian
   warnings.
   * debian/patches/fix-fgemm-check-tests.patch
 - New patch replacing skip-fgemm-check-tests.patch; fix for failing tests
   from upstream git.
   * debian/patches/fix-file-path-in-doc.patch
 - Remove patch; no longer necessary as our documentation directory
   structure matches upstream's.
   * debian/rules
 - Disable SSE and SSE2 on i386 (Closes: #907010).
 - Skip failing tests on big-endian 32-bit architectures (Closes: #902753).
 - New override_dh_installdocs target; install all docs to
   /usr/share/doc/fflas-ffpack as suggested in Debian Policy section 12.3.
   * debian/upstream/metadata
 - New DEP-12 file with citation information.
Checksums-Sha1:
 1e2af99a683d5bef30565d602cf497e21b734735 2490 fflas-ffpack_2.3.2-3.dsc
 f380dfd5bc7483cdbf3ac7889b724466566a052e 6968 
fflas-ffpack_2.3.2-3.debian.tar.xz
 7c3bc6c15544cd7e5735bac8ffdc97d0ff0809a8 6025 
fflas-ffpack_2.3.2-3_source.buildinfo
Checksums-Sha256:
 7001035930c3c105435a8f4ed4ea3d5ccbd257716fe97b9e854549805e5d7fd8 2490 
fflas-ffpack_2.3.2-3.dsc
 0c2b0ada24221c461bbd364f296c5c272eb7b99830877b2b774ed440700eba94 6968 
fflas-ffpack_2.3.2-3.debian.tar.xz
 9ed0d12c56de0873c6745a58ace45bb5e70a1b90a34712376a26404573deee91 6025 
fflas-ffpack_2.3.2-3_source.buildinfo
Files:
 dfe2018e0d34a77edd3c3ca4f57e1533 2490 math optional fflas-ffpack_2.3.2-3.dsc
 8b03c9a2ed83d46fff2e56596c23b9ce 6968 math optional 
fflas-ffpack_2.3.2-3.debian.tar.xz
 eb6308d2c1f2f0e37980a1ed34641077 6025 math option

Bug#910230: libactivation-java: missing Breaks+Replaces: glassfish-activation

[Andreas Beckmann]

Package: libactivation-java
Version: 1.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie' to 'stretch' to 'buster'.
It installed fine in 'jessie', and upgraded to 'stretch' successfully,
but then the upgrade to 'buster' failed.

In case the package was not part of an intermediate stable release,
the version from the preceding stable release was kept installed.

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

  Selecting previously unselected package libactivation-java.
  Preparing to unpack .../23-libactivation-java_1.2.0-1_all.deb ...
  Unpacking libactivation-java (1.2.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-pUdXjX/23-libactivation-java_1.2.0-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/maven-repo/javax/activation/activation/debian/activation-debian.pom',
 which is also in package glassfish-activation 1:2.1.1-b31g+dfsg1-2


cheers,

Andreas


libstax-ex-java_1.7.8-2.log.gz
Description: application/gzip

Bug#910229: python-gitlab: File conflict with ruby-gitlab

[Jeremy Bicha]

Source: python-gitlab
Version: 1:1.6.0-1
Severity: serious
Affects: src:ruby-gitlab

Both ruby-gitlab and gitlab-cli ship /usr/bin/gitlab and
/usr/share/man/man1/gitlab.1.gz

This is a violation of the first paragraph of Debian Policy § 10.1

https://www.debian.org/doc/debian-policy/ch-files.html

I suggest that both packages rename their scripts. How about
ruby-gitlab and python-gitlab?

Thanks,
Jeremy Bicha

Bug#910228: ruby-gitlab: file conflict with gitlab-cli

[Jeremy Bicha]

Source: ruby-gitlab
Version: 4.5.00-1
Severity: serious
Affects: src:python-gitlab
X-Debbugs-CC: bou...@debian.org, sop...@freexian.com

Both ruby-gitlab and gitlab-cli ship /usr/bin/gitlab and
/usr/share/man/man1/gitlab.1.gz

This is a violation of the first paragraph of Debian Policy § 10.1

https://www.debian.org/doc/debian-policy/ch-files.html

I suggest that both packages rename their scripts. How about
ruby-gitlab and python-gitlab?

Thanks,
Jeremy Bicha

Processed (with 2 errors): user debian...@lists.debian.org, usertagging 910008, reassign 910008 to libghc-mtl-dev ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 910008 piuparts
There were no usertags set.
Usertags are now: piuparts.
> reassign 910008 libghc-mtl-dev 2.2.2-2
Bug #910008 [src:haskell-mtl] haskell-mtl: Package libghc-mtl-dev not 
co-installable with ghc due to file conflicts
Bug reassigned from package 'src:haskell-mtl' to 'libghc-mtl-dev'.
No longer marked as found in versions haskell-mtl/2.2.2-2.
Ignoring request to alter fixed versions of bug #910008 to the same values 
previously set
Bug #910008 [libghc-mtl-dev] haskell-mtl: Package libghc-mtl-dev not 
co-installable with ghc due to file conflicts
Marked as found in versions haskell-mtl/2.2.2-2.
> reassign 910119 python3-paste,python-paste 2.0.3+dfsg-7
Unknown command or malformed arguments to command.
> retitle 910119 python{,3}-paste: broken symlink: 
> /usr/lib/python{2.7,3}/dist-packages/paste/evalexception/media/MochiKit.packed.js
Bug #910119 [python3-paste] python3-paste: broken symlink: 
/usr/lib/python3/dist-packages/paste/evalexception/media/MochiKit.packed.js -> 
../../../../../../share/javascript/mochikit/MochiKit.js
Changed Bug title to 'python{,3}-paste: broken symlink: 
/usr/lib/python{2.7,3}/dist-packages/paste/evalexception/media/MochiKit.packed.js'
 from 'python3-paste: broken symlink: 
/usr/lib/python3/dist-packages/paste/evalexception/media/MochiKit.packed.js -> 
../../../../../../share/javascript/mochikit/MochiKit.js'.
> found 904509 gcc-x86-64-linux-gnux32/4:8.1.0-1
Bug #904509 [gcc-x86-64-linux-gnux32] gcc-x86-64-linux-gnux32: broken symlink: 
/usr/share/doc/cpp-x86_64-linux-gnux32/README.Bugs -> 
../gcc-8-x86_64-linux-gnux32-base/README.Bugs
The source gcc-x86-64-linux-gnux32 and version 4:8.1.0-1 do not appear to match 
any binary packages
Marked as found in versions gcc-x86-64-linux-gnux32/4:8.1.0-1.
> found 905209 2.40.1-4
Bug #905209 [libgraphviz-dev] libgraphviz-dev: broken symlinks: 
/usr/lib/tcl8.6/graphviz/lib*.so -> lib*.so.0.0.0
Marked as found in versions graphviz/2.40.1-4.
> found 872238 2.5.11-1
Bug #872238 [cyrus-murder] cyrus-murder: broken symlink: 
/usr/lib/cyrus/bin/mupdatetest -> imtest
Marked as found in versions cyrus-imapd/2.5.11-1.
> unarchive 857522
Bug #857522 {Done: Ondřej Surý } [libbind-export-dev] 
libbind-export-dev: broken symlinks: 
/usr/lib/x86_64-linux-gnu/liblwres-export.so -> 
/lib/x86_64-linux-gnu/liblwres-export.so.141, 
/usr/lib/x86_64-linux-gnu/libbind9.so -> libbind9.so.140.0.10
Unarchived Bug 857522
> found 857522 1:9.11.4.P2+dfsg-3
Bug #857522 {Done: Ondřej Surý } [libbind-export-dev] 
libbind-export-dev: broken symlinks: 
/usr/lib/x86_64-linux-gnu/liblwres-export.so -> 
/lib/x86_64-linux-gnu/liblwres-export.so.141, 
/usr/lib/x86_64-linux-gnu/libbind9.so -> libbind9.so.140.0.10
Marked as found in versions bind9/1:9.11.4.P2+dfsg-3 and reopened.
> usertags 887687 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 857680 + llvm-8-examples
Bug #857680 [llvm-3.8-examples] llvm-3.8-examples: broken symlinks: 
/usr/share/doc/llvm-3.8-examples/Makefile.* -> 
../../../lib/llvm-3.8/build/Makefile.*
Added indication that 857680 affects llvm-8-examples
> found 857680 llvm-8-examples/1:8~svn343154-1
Bug #857680 [llvm-3.8-examples] llvm-3.8-examples: broken symlinks: 
/usr/share/doc/llvm-3.8-examples/Makefile.* -> 
../../../lib/llvm-3.8/build/Makefile.*
The source llvm-8-examples and version 1:8~svn343154-1 do not appear to match 
any binary packages
Marked as found in versions llvm-8-examples/1:8~svn343154-1.
> found 857680 llvm-7-examples/1:7-3
Bug #857680 [llvm-3.8-examples] llvm-3.8-examples: broken symlinks: 
/usr/share/doc/llvm-3.8-examples/Makefile.* -> 
../../../lib/llvm-3.8/build/Makefile.*
The source llvm-7-examples and version 1:7-3 do not appear to match any binary 
packages
Marked as found in versions llvm-7-examples/1:7-3.
> found 857680 llvm-6.0-examples/1:6.0.1-9
Bug #857680 [llvm-3.8-examples] llvm-3.8-examples: broken symlinks: 
/usr/share/doc/llvm-3.8-examples/Makefile.* -> 
../../../lib/llvm-3.8/build/Makefile.*
The source llvm-6.0-examples and version 1:6.0.1-9 do not appear to match any 
binary packages
Marked as found in versions llvm-6.0-examples/1:6.0.1-9.
> found 857680 llvm-4.0-examples/1:4.0.1-10
Bug #857680 [llvm-3.8-examples] llvm-3.8-examples: broken symlinks: 
/usr/share/doc/llvm-3.8-examples/Makefile.* -> 
../../../lib/llvm-3.8/build/Makefile.*
The source llvm-4.0-examples and version 1:4.0.1-10 do not appear to match any 
binary packages
Ignoring request to alter found versions of bug #857680 to the same values 
previously set
> affects 907875 + libvirtodbc0
Bug #907875 [virtuoso-opensource-7-bin,virtuoso-opensource-7-common] 
virtuoso-opensource-7-{bin,common}: missing Breaks+Replaces: 
virtuoso-opensource-6.1-{bin,common}
Added indication that 907875 affects libvirtodbc0
> affects 906110 + freecad
Bug #906110 [freecad-common,free

Bug#910226: expeyes-web: fails to upgrade from 'stretch': Exception: cannot get content of python3-expeyes

[Andreas Beckmann]

Package: expeyes-web
Version: 4.4.4+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails.

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

  Setting up expeyes-web (4.4.4+dfsg-1) ...
  dpkg-query: package 'python3-expeyes' is not installed
  Use dpkg --info (= dpkg-deb --info) to examine archive files,
  and dpkg --contents (= dpkg-deb --contents) to list their contents.
  Traceback (most recent call last):
File "/usr/bin/py3compile", line 290, in 
  main()
File "/usr/bin/py3compile", line 270, in main
  options.force, options.optimize, e_patterns)
File "/usr/bin/py3compile", line 154, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/py3compile", line 106, in filter_files
  for fn in files:
File "/usr/share/python3/debpython/files.py", line 71, in filter_public
  for fn in files:
File "/usr/share/python3/debpython/files.py", line 53, in from_package
  raise Exception("cannot get content of %s" % package_name)
  Exception: cannot get content of python3-expeyes
  dpkg: error processing package expeyes-web (--configure):
   installed expeyes-web package post-installation script subprocess returned 
error exit status 1


There seems to be a manually added py3compile call in the postinst
which does not look like it was intended for this package.


cheers,

Andreas


expeyes-web_4.4.4+dfsg-1.log.gz
Description: application/gzip

Processed: openstack-dashboard: fails to upgrade from stretch with python-ironic-ui installed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + python-ironic-ui
Bug #910225 [openstack-dashboard] openstack-dashboard: fails to upgrade from 
stretch with python-ironic-ui installed
Added indication that 910225 affects python-ironic-ui

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

Bug#906826: xul-ext-spdy-indicator no longer works with firefox-esr 60

[Dmitry Smirnov]

On Thursday, 4 October 2018 1:20:42 AM AEST Moritz Mühlenhoff wrote:
> On Tue, Aug 21, 2018 at 06:56:13PM +0300, Adrian Bunk wrote:
> > Package: xul-ext-spdy-indicator
> > Version: 2.2-1
> > Severity: serious
> > 
> > XUL addons are no longer supported.
> 
> Dmitry,
> shall we remove it from the archive?

Sure. There is a successor web-extension but I can't allocate time to package 
it yet:

  https://github.com/bsiegel/http2-indicator



> SPDY itself is deprecated as well.

Extension detects HTTP/2 as well.

-- 
Cheers,
 Dmitry Smirnov.

---

Men can only be happy when they do not assume that the object of life is
happiness.
-- George Orwell


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

Bug#910222: opam: copyright file missing after upgrade (policy 12.5)

[Andreas Beckmann]

Package: opam
Version: 2.0.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

  stretch -> buster

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

0m52.3s ERROR: WARN: Inadequate results from running adequate!
  opam: missing-copyright-file /usr/share/doc/opam/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/opam/copyright
  # ls -lad /usr/share/doc/opam
  drwxr-xr-x 2 root root 40 Sep 24 12:23 /usr/share/doc/opam
  # ls -la /usr/share/doc/opam/
  total 0
  drwxr-xr-x   2 root root   40 Sep 24 12:23 .
  drwxr-xr-x 137 root root 3440 Sep 24 12:23 ..


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


opam_2.0.0-4.log.gz
Description: application/gzip

Bug#881971: fixed in lightbeam 2.1.0-1

[Dmitry Smirnov]

On Thursday, 4 October 2018 1:19:56 AM AEST Moritz Mühlenhoff wrote:
> On Wed, Jul 25, 2018 at 04:19:18AM +, Dmitry Smirnov wrote:
> >* New upstream release [February 2018].
> >
> >  + WebExtensions version (Closes: #881971).
> 
> lightbeam is also broken in stretch, do you plan to update it
> there or should it be removed from stable?

Unfortunately I have no capacity to take care of it in Stretch...

Removal remains an option unless a team member prepares an upload...

-- 
Cheers,
 Dmitry Smirnov.

---

A man does what he must - in spite of personal consequences, in spite of
obstacles and dangers and pressures - and that is the basis of all human
morality.
-- Winston Churchill


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

Bug#910220: libdmtx-dev: copyright file missing after upgrade (policy 12.5)

[Andreas Beckmann]

Package: libdmtx-dev
Version: 0.7.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

  stretch -> buster

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

0m25.9s ERROR: WARN: Inadequate results from running adequate!
  libdmtx-dev:amd64: missing-copyright-file /usr/share/doc/libdmtx-dev/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/libdmtx-dev/copyright
  # ls -lad /usr/share/doc/libdmtx-dev
  drwxr-xr-x 2 root root 40 Aug 19 07:34 /usr/share/doc/libdmtx-dev
  # ls -la /usr/share/doc/libdmtx-dev/
  total 0
  drwxr-xr-x  2 root root   40 Aug 19 07:34 .
  drwxr-xr-x 91 root root 1940 Aug 19 07:34 ..


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


libdmtx-dev_0.7.5-1.log.gz
Description: application/gzip

Bug#910219: libdeps-renderer-dot-perl: copyright file missing after upgrade (policy 12.5)

[Andreas Beckmann]

Package: libdeps-renderer-dot-perl
Version: 0.13-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

  stretch -> buster

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

0m42.9s ERROR: WARN: Inadequate results from running adequate!
  libdeps-renderer-dot-perl: missing-copyright-file 
/usr/share/doc/libdeps-renderer-dot-perl/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/libdeps-renderer-dot-perl/copyright
  # ls -lad /usr/share/doc/libdeps-renderer-dot-perl
  drwxr-xr-x 2 root root 40 Aug  2 13:53 
/usr/share/doc/libdeps-renderer-dot-perl
  # ls -la /usr/share/doc/libdeps-renderer-dot-perl/
  total 0
  drwxr-xr-x   2 root root   40 Aug  2 13:53 .
  drwxr-xr-x 153 root root 3180 Aug  2 13:53 ..


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


libdeps-renderer-dot-perl_0.13-3.log.gz
Description: application/gzip

Bug#910218: libapache2-mod-proxy-uwsgi: copyright file missing after upgrade (policy 12.5)

[Andreas Beckmann]

Package: libapache2-mod-proxy-uwsgi
Version: 2.4.34-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

  stretch -> buster

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

0m43.3s ERROR: WARN: Inadequate results from running adequate!
  libapache2-mod-proxy-uwsgi: missing-copyright-file 
/usr/share/doc/libapache2-mod-proxy-uwsgi/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/libapache2-mod-proxy-uwsgi/copyright
  # ls -lad /usr/share/doc/libapache2-mod-proxy-uwsgi
  drwxr-xr-x 2 root root 40 Aug  2 15:26 
/usr/share/doc/libapache2-mod-proxy-uwsgi
  # ls -la /usr/share/doc/libapache2-mod-proxy-uwsgi/
  total 0
  drwxr-xr-x   2 root root   40 Aug  2 15:26 .
  drwxr-xr-x 140 root root 2940 Aug  2 15:26 ..

Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


libapache2-mod-proxy-uwsgi_2.4.34-1.log.gz
Description: application/gzip

Processed: tagging 909460

[Debian Bug Tracking System]

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

> tags 909460 + pending
Bug #909460 [src:bacula] Trouble with the sqlite3 upgrade path
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#910217: apparmor: removed shipped file: /var/cache/apparmor/CACHEDIR.TAG

[Andreas Beckmann]

Package: apparmor
Version: 2.13-8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package removes files that
it has shipped.

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

0m35.9s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /var/cache/apparmor/CACHEDIR.TAG (from apparmor package)


This was observed after a stretch->buster upgrade.


cheers,

Andreas


apparmor_2.13-8.log.gz
Description: application/gzip

Bug#910216: epoptes-client: removed shipped file: /etc/network/if-up.d/epoptes-client

[Andreas Beckmann]

Package: epoptes-client
Version: 1.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package removes files that
it has shipped.

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

1m6.1s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /etc/network/if-up.d/epoptes-client (from 
epoptes-client package)

This was observed after a stretch->buster upgrade.


cheers,

Andreas


epoptes-client_1.0.0-1.log.gz
Description: application/gzip

Bug#906609: fixed in gnucash 1:3.3-1

[Dmitry Smirnov]

On Thursday, 4 October 2018 1:01:12 AM AEST Bernhard Übelacker wrote:
> Hello Dimitry,
> I saw that a version 3.3-1 got uploaded so I had a look at the build
> logs,

Thank you for checking build logs.


> but found some of them failing with this error:
> 
> /<>/libgnucash/engine/gnc-timezone.cpp:55:22: error:
> operator '!' has no right operand
>  #if ! WORDS_BIGENDIAN
>   ^
> 
> I fear this happens because just the part of my patch in debian/rules
> made it into this release.
> 
> Unfortunately for this to work the tiny second change in the upstream
> file common/config.h.cmake.in is also important:
> 
> -#cmakedefine WORDS_BIGENDIAN
> +#cmakedefine WORDS_BIGENDIAN 1

I know, I know - I've noticed it too and committed the patch already:

  https://salsa.debian.org/debian/gnucash/commit/e0c54914

It was entirely my fault to miss that but I'm not uploading the fix yet due 
to unrelated FTBFS on i386 that I hope to address when upstream fixes it:

  https://bugs.gnucash.org/show_bug.cgi?id=796878

-- 
Regards,
 Dmitry Smirnov.

---

If liberty means anything at all, it means the right to tell people what
they do not want to hear.
-- George Orwell


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

Bug#910215: murano-agent: prompting due to modified conffiles which were not modified by the user: /etc/murano-agent/muranoagent.conf

[Andreas Beckmann]

Package: murano-agent
Version: 1:3.5.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/ch-files.html#behavior,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

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

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

  Setting up murano-agent (1:3.5.1-2) ...
  Installing new version of config file /etc/init.d/murano-agent ...
  
  Configuration file '/etc/murano-agent/muranoagent.conf'
   ==> File on system created by you or by a script.
   ==> File also in package provided by package maintainer.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** muranoagent.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing 
package murano-agent (--configure):
   end of file on stdin at conffile prompt
  Processing triggers for libc-bin (2.27-6) ...
  Errors were encountered while processing:
   murano-agent


cheers,

Andreas


murano-agent_1:3.5.1-2.log.gz
Description: application/gzip

Bug#910214: softflowd: prompting due to modified conffiles which were not modified by the user: /etc/softflowd/default.conf

[Andreas Beckmann]

Package: softflowd
Version: 0.9.9-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/ch-files.html#behavior,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

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

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

  Setting up softflowd (0.9.9-4) ...
  Installing new version of config file /etc/init.d/softflowd ...
  
  Configuration file '/etc/softflowd/default.conf'
   ==> File on system created by you or by a script.
   ==> File also in package provided by package maintainer.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** default.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package 
softflowd (--configure):
   end of file on stdin at conffile prompt
  Errors were encountered while processing:
   softflowd


cheers,

Andreas


softflowd_0.9.9-4.log.gz
Description: application/gzip

Bug#906826: xul-ext-spdy-indicator no longer works with firefox-esr 60

[Moritz Mühlenhoff]

On Tue, Aug 21, 2018 at 06:56:13PM +0300, Adrian Bunk wrote:
> Package: xul-ext-spdy-indicator
> Version: 2.2-1
> Severity: serious
> 
> XUL addons are no longer supported.

Dmitry,
shall we remove it from the archive? SPDY itself is deprecated as well.

Cheers,
Moritz

Bug#882287: xul-ext-noscript: new upstream version

[Moritz Mühlenhoff]

On Mon, Sep 17, 2018 at 01:13:18PM +0400, Jerome BENOIT wrote:
> Please consider to the new upstream version 10
> given that the current version of noscript provided in Stretch
> does not work with  firefox-esr 60.2 recently brought in Stretch.

What's the plan for noscript in stretch? Is a backport of the
web extension planned for stretch or should it be removed in the
next point release? (This was also require a backport of dh_webext
to stretch it seems).

Cheers,
Moritz

Bug#909719: marked as done (dpkg breaks devscripts autopkgtest due to syntax/behavior change)

[Debian Bug Tracking System]

Your message dated Wed, 03 Oct 2018 15:19:13 +
with message-id 
and subject line Bug#909719: fixed in devscripts 2.18.5
has caused the Debian Bug report #909719,
regarding dpkg breaks devscripts autopkgtest due to syntax/behavior change
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.)


-- 
909719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dpkg, devscripts
Control: found -1 dpkg/1.19.1
Control: found -1 devscripts/2.18.4
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of dpkg the autopkgtest of devscripts fails in
testing when that autopkgtest is run with the binary packages of dpkg
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
dpkg   from testing1.19.1
devscripts from testing2.18.4
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report. If I read the
output correctly, devscripts need to be updated to changed behavior of
dpkg and dpkg probably should add a versioned Breaks on devscripts
before it is fixed.

Currently this regression is contributing to the delay of the migration
of dpkg to testing [1]. Due to the nature of this issue, I filed this
bug report against both packages. Can you please investigate the
situation and reassign the bug to the right package or clone it if my
judgment above was correct? If needed, please change the bug's severity.

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

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
dpkg/1.19.1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=dpkg

https://ci.debian.net/data/autopkgtest/testing/amd64/d/devscripts/1062173/log.gz

ASSERT:standard output of debuild --no-conf --no-lintian
--preserve-envvar=PATH --preserve-envvar=PERL5LIB
--preserve-envvar=DEBFULLNAME --preserve-envvar=DEBEMAIL
--preserve-envvar=GNUPGHOME --set-envvar=NO_PKG_MANGLE=1 -k'uscan test
key (no secret) ' matches
/tmp/autopkgtest-lxc.de2hfc_n/downtmp/build.dwK/src/test/package_lifecycle/debuild.txt\n
expected:<0> but was:<1>
6c6
<  dpkg-source --before-build .
---
>  dpkg-source --before-build test
10c10
<  dpkg-source -b .
---
>  dpkg-source -b test
22c22
<  dpkg-source --after-build .
---
>  dpkg-source --after-build test
test_dscverify
test_dscextractControl
test_dscextractChangelog
test_debchange
test_list_unreleased
test_debuild2
ASSERT:standard output of debuild --no-conf --no-lintian
--preserve-envvar=PATH --preserve-envvar=PERL5LIB
--preserve-envvar=DEBFULLNAME --preserve-envvar=DEBEMAIL
--preserve-envvar=GNUPGHOME --set-envvar=NO_PKG_MANGLE=1 -k'uscan test
key (no secret) ' matches
/tmp/autopkgtest-lxc.de2hfc_n/downtmp/build.dwK/src/test/package_lifecycle/debuild.txt\n
expected:<0> but was:<1>
6c6
<  dpkg-source --before-build .
---
>  dpkg-source --before-build test
10c10
<  dpkg-source -b .
---
>  dpkg-source -b test
22c22
<  dpkg-source --after-build .
---
>  dpkg-source --after-build test
test_debuild_forcesign
ASSERT:standard output of debuild --no-conf --no-lintian
--preserve-envvar=PATH --preserve-envvar=PERL5LIB
--preserve-envvar=DEBFULLNAME --preserve-envvar=DEBEMAIL
--preserve-envvar=GNUPGHOME --set-envvar=NO_PKG_MANGLE=1 --force-sign
-k'uscan test key (no secret) ' matches
/tmp/autopkgtest-lxc.de2hfc_n/downtmp/build.dwK/src/test/package_lifecycle/debuild.txt\n
expected:<0> but was:<1>
6c6
<  dpkg-source --before-build .
---
>  dpkg-source --before-build test
10c10
<  dpkg-source -b .
---
>  dpkg-source -b test
22c22
<  dpkg-source --after-build .
---
>  dpkg-source --after-build test
test_debdiff

Ran 9 tests.

FAILED (failures=3)



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: devscripts
Source-Version: 2.18.5

We believe that the bug you reported is fixed in the latest version of
devscripts, 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 b

Bug#881894: xul-ext-cookie-monster: dead upstream, broken in FF57

[Moritz Mühlenhoff]

On Thu, Nov 16, 2017 at 06:21:56AM +0100, Christoph Anton Mitterer wrote:
> Package: xul-ext-cookie-monster
> Version: 1.3.0.5-1
> Severity: normal
> 
> 
> 
> Hi.
> 
> Seems this addon is dead upstream (at least:
> https://addons.mozilla.org/en-US/firefox/addon/cookie-monster/
> says "This add-on has been removed by its author.").
> 
> Also it won't work with FF >57 anymore.

Let's remove it from the archive?

Cheers,
Moritz

Bug#906859: xul-ext-dom-inspector no longer works with firefox-esr 60

[Moritz Mühlenhoff]

On Sat, Sep 08, 2018 at 03:12:40PM +0800, Paul Wise wrote:
> On Tue, 21 Aug 2018 21:11:16 +0300 Adrian Bunk wrote:
> 
> > Package: xul-ext-dom-inspector
> > 
> > XUL addons are no longer supported.
> 
> The native Firefox developer tools are almost a replacement,
> so I think this package can just be removed from Debian.

David, agreed to remove?

Cheers,
Moritz

Bug#906843: xul-ext-custom-tab-width no longer works with firefox-esr 60

[Moritz Mühlenhoff]

On Tue, Aug 21, 2018 at 08:04:57PM +0300, Adrian Bunk wrote:
> Package: xul-ext-custom-tab-width
> Version: 1.1-1
> Severity: serious
> 
> XUL addons are no longer supported.

This is dead upstream and broken even in ESR, let's remove it
from the archive?

Cheers,
Moritz

Bug#881971: fixed in lightbeam 2.1.0-1

[Moritz Mühlenhoff]

On Wed, Jul 25, 2018 at 04:19:18AM +, Dmitry Smirnov wrote:
>* New upstream release [February 2018].
>  + WebExtensions version (Closes: #881971).

lightbeam is also broken in stretch, do you plan to update it
there or should it be removed from stable?

Cheers,
Moritz

Bug#906832: xul-ext-kwallet5 no longer works with firefox-esr 60

[Moritz Mühlenhoff]

On Tue, Aug 21, 2018 at 07:53:52PM +0300, Adrian Bunk wrote:
> On Tue, Aug 21, 2018 at 07:11:59PM +0300, Adrian Bunk wrote:
> > Package: xul-ext-kwallet5
> > Version: 1.0-2
> > Severity: serious
> > 
> > XUL addons are no longer supported.
> 
> If it is confirmed that this package works with thunderbird 60,
> it might be an option to change the dependency to only thunderbird.

addons.thunderbird.net only lists it as compatible to versions
up to 49.

Shall we remove xul-ext-kwallet5 from the archive?

Cheers,
Moritz

Bug#865305: Does not work with firefox 54

[Moritz Mühlenhoff]

On Tue, Jun 20, 2017 at 02:30:11PM +0200, Javier Barroso wrote:
> Package: xul-ext-pentadactyl
> Version: 1.2~r20170308-1
> Severity: important
> 
> Maybe add a README if the package can work with firefox 54 (seems that
> multiprocess have to be disable).
> Not sure if would be good idea to add vimperator to debian again [
> seems like there are more activity on its repo ]

This is dead upstream and now fully broken in stable and unstable,
let's remove it from the archive?

Cheers,
Moritz

Bug#910212: fusiondirectory: fails to upgrade from 'stretch': pre-installation script subprocess returned error exit status 30

[Andreas Beckmann]

Package: fusiondirectory
Version: 1.2.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails.

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

  Preparing to unpack .../17-fusiondirectory_1.2.2-3_all.deb ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-3pYVnF/17-fusiondirectory_1.2.2-3_all.deb (--unpack):
   new fusiondirectory package pre-installation script subprocess returned 
error exit status 30

This looks like a debconf question not being asked under

  DEBIAN_FRONTEND=noninteractive


cheers,

Andreas


fusiondirectory_1.2.2-3.log.gz
Description: application/gzip

Bug#910158: marked as done (libpmix-dev: broken symlink: /usr/lib/x86_64-linux-gnu/pmix/lib/libpmix.so -> libpmix.so.2.2.0)

[Debian Bug Tracking System]

Your message dated Wed, 03 Oct 2018 15:08:30 +
with message-id 
and subject line Bug#910158: fixed in pmix 3.0.2-2
has caused the Debian Bug report #910158,
regarding libpmix-dev: broken symlink: 
/usr/lib/x86_64-linux-gnu/pmix/lib/libpmix.so -> libpmix.so.2.2.0
to be marked as done.

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

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


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

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m30.1s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/pmix/lib/libpmix.so -> libpmix.so.2.2.0 
(libpmix-dev:amd64)


The library filename is currently

  libpmix.so.2.2.2

But you may bette rtarget the SONAME with the symlink:

  libpmix.so.2


cheers,

Andreas


libpmix-dev_3.0.2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pmix
Source-Version: 3.0.2-2

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

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

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated pmix package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 03 Oct 2018 15:22:05 +0100
Source: pmix
Binary: libpmix-dev libpmi-pmix-dev libpmi1-pmix libpmi2-pmix libpmix2
Architecture: source amd64
Version: 3.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libpmi-pmix-dev - Development files for the PMI library (OpenMPI )
 libpmi1-pmix - OpenMPI implementation of the PMI v1 library
 libpmi2-pmix - OpenMPI implementation of the PMI v2 library
 libpmix-dev - Development files for the PMI Exascale library
 libpmix2   - Process Management Interface (Exascale) library
Closes: 910158
Changes:
 pmix (3.0.2-2) unstable; urgency=medium
 .
   * Fix broken symlink (lib version change). Closes: #910158
Checksums-Sha1:
 1564f7109feed4b1b04370a7ade004f95b867054 2140 pmix_3.0.2-2.dsc
 33166f8d8c4c9c8897ea25909aa1b44f5928fe44 7284 pmix_3.0.2-2.debian.tar.xz
 a412ee7294a835c7c0e61332b14a743c507bb7b9 454052 
libpmi-pmix-dev_3.0.2-2_amd64.deb
 50b82dc291608d4a7a48722ad08a850efe697baa 1498456 
libpmi1-pmix-dbgsym_3.0.2-2_amd64.deb
 eb649716c61169fcf12dc52b368bf2fe8753acf7 278536 libpmi1-pmix_3.0.2-2_amd64.deb
 0c1e8ca463eec5694ee50aa678fb03f911d765ef 1504416 
libpmi2-pmix-dbgsym_3.0.2-2_amd64.deb
 9ee18f01df777fe297455e4b13e16b8bfc7ccef2 281548 libpmi2-pmix_3.0.2-2_amd64.deb
 b0796f4d4f2c4ef784bf839141ba98a001ff4081 521016 libpmix-dev_3.0.2-2_amd64.deb
 13adf7fbce75fda59c142bda20e6655722dc0e3e 2474044 
libpmix2-dbgsym_3.0.2-2_amd64.deb
 b8e1d8809a5d092b957d0f5b263672fd556fc74d 409480 libpmix2_3.0.2-2_amd64.deb
 8f261ecc16134d7dc0e675d81c4afbeb5bfdb4d8 7925 pmix_3.0.2-2_amd64.buildinfo
Checksums-Sha256:
 761e929fad38de28743b77f6f31f16730053872e7b7d418bd27a28fc4837e93b 2140 
pmix_3.0.2-2.dsc
 6f24895c72b54bff75c213a5f6b57a0467d4a6c30a7aeab386cc4d224419821c 7284 
pmix_3.0.2-2.debian.tar.xz
 823b7699f535ed65f7e918bc7b7871f2399104dd43646c4811250febbcc61ecd 454052 
libpmi-pmix-dev_3.0.2-2_amd64.deb
 6abcfed9b156fb05bd01a5eb27fb09a5d3d454ac1b9e5117e1ef829132c8aa05 1498456 
libpmi1-pmix-dbgsym_3.0.2-2_amd64.deb
 ab1398b44276b78ea1293ed71f5c15eca98da25b320727f73a83e5b01572f352 278536 
libpmi1-pmix_3.0.2-2_amd64.deb
 30d9ede4a2ff60c2b24f0798cb9393cffac50213d0318c814f9946b66b6f4760 1504416 
libpmi2-pmix-dbgsym_3.0.2-2_amd64.deb
 de8eee1ab35c2b6a6916755d4e21e9a4b7103b243d40552ee89916fad003af37 281548 
libpmi2-pmix_3.0.2-2_amd64.deb
 02196a70ec5300c006b92a56ecf6a740ee9e0f568217e3002a15e68054419c06 521016 
libpmix-dev_3.0.2-2_amd64.deb
 62feac989c926746d5206fa0b12312a5e3ab021a91528966a52392361ec76eb0 2474044 
libpmix2-dbgsym_3.0.2-2_amd64.deb
 12b54551d32312025e8b6c49b150294e1e795dfa0ede82c054a93cbe7ff55fe1 409480 
libpmix2_3.0.2-2_amd64.deb
 a11b4b17362bc78b42dc1

Bug#910211: python-werkzeug-doc: unhandled symlink to directory conversion: /usr/share/doc/python-werkzeug/examples

[Andreas Beckmann]

Package: python-werkzeug-doc
Version: 0.14.1+dfsg1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  stretch -> sid

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m26.7s INFO: dirname part contains a symlink:
  /usr/share/doc/python-werkzeug/examples/README (python-werkzeug-doc) != 
/usr/share/doc/python-werkzeug-doc/examples/README (?)
/usr/share/doc/python-werkzeug/examples -> ../python-werkzeug-doc/examples
  /usr/share/doc/python-werkzeug/examples/contrib (python-werkzeug-doc) != 
/usr/share/doc/python-werkzeug-doc/examples/contrib (?)
/usr/share/doc/python-werkzeug/examples -> ../python-werkzeug-doc/examples
  /usr/share/doc/python-werkzeug/examples/contrib/README (python-werkzeug-doc) 
!= /usr/share/doc/python-werkzeug-doc/examples/contrib/README (?)
/usr/share/doc/python-werkzeug/examples -> ../python-werkzeug-doc/examples
  /usr/share/doc/python-werkzeug/examples/contrib/securecookie.py 
(python-werkzeug-doc) != 
/usr/share/doc/python-werkzeug-doc/examples/contrib/securecookie.py (?)
/usr/share/doc/python-werkzeug/examples -> ../python-werkzeug-doc/examples
  /usr/share/doc/python-werkzeug/examples/contrib/sessions.py 
(python-werkzeug-doc) != 
/usr/share/doc/python-werkzeug-doc/examples/contrib/sessions.py (?)
/usr/share/doc/python-werkzeug/examples -> ../python-werkzeug-doc/examples
  /usr/share/doc/python-werkzeug/examples/cookieauth.py (python-werkzeug-doc) 
!= /usr/share/doc/python-werkzeug-doc/examples/cookieauth.py (?)
/usr/share/doc/python-werkzeug/examples -> ../python-werkzeug-doc/examples
  /usr/share/doc/python-werkzeug/examples/coolmagic (python-werkzeug-doc) != 
/usr/share/doc/python-werkzeug-doc/examples/coolmagic (?)
/usr/share/doc/python-werkzeug/examples -> ../python-werkzeug-doc/examples
  /usr/share/doc/python-werkzeug/examples/coolmagic/__init__.py 
(python-werkzeug-doc) != 
/usr/share/doc/python-werkzeug-doc/examples/coolmagic/__init__.py (?)
/usr/share/doc/python-werkzeug/examples -> ../python-werkzeug-doc/examples
  /usr/share/doc/python-werkzeug/examples/coolmagic/application.py 
(python-werkzeug-doc) != 
/usr/share/doc/python-werkzeug-doc/examples/coolmagic/application.py (?)
/usr/share/doc/python-werkzeug/examples -> ../python-werkzeug-doc/examples
  /usr/share/doc/python-werkzeug/examples/coolmagic/helpers.py 
(python-werkzeug-doc) != 
/usr/share/doc/python-werkzeug-doc/examples/coolmagic/helpers.py (?)
/usr/share/doc/python-werkzeug/examples -> ../python-werkzeug-doc/examples
  /usr/share/doc/python-werkzeug/examples/coolmagic/public 
(python-werkzeug-doc) != 
/usr/share/doc/python-werkzeug-doc/examples/coolmagic/public (?)
/usr/share/doc/python-werkzeug/examples -> ../python-werkzeug-doc/examples
  /usr/share/doc/python-werkzeug/examples/coolmagic/public/style.css 
(python-werkzeug-doc) != 
/usr/share/doc/python-werkzeug-doc/examples/coolmagic/public/style.css (?)
/usr/share/doc/python-werkzeug/examples -> ../python-werkzeug-doc/examples
  /usr/share/doc/python-werkzeug/examples/coolmagic/templates 
(python-werkzeug-doc) != 
/usr/share/doc/python-werkzeug-doc/examples/coolmagic/templates (?)
/usr/share/doc/python-werkzeug/examples -> ../python-werkzeug-doc/examples
  /usr/share/doc/python-werkzeug/examples/coolmagic/templates/layout.html 
(python-werkzeug-doc) != 
/usr/share/doc/python-werkzeug-doc/examples/coolmagic/templates/layout.html (?)
/usr/share/doc/python-werkzeug/examples -> ../python-we

Bug#906609: fixed in gnucash 1:3.3-1

[Bernhard Übelacker]

Hello Dimitry,
I saw that a version 3.3-1 got uploaded so I had a look at the build
logs, but found some of them failing with this error:

/<>/libgnucash/engine/gnc-timezone.cpp:55:22: error:
operator '!' has no right operand
 #if ! WORDS_BIGENDIAN
  ^

I fear this happens because just the part of my patch in debian/rules
made it into this release.

Unfortunately for this to work the tiny second change in the upstream
file common/config.h.cmake.in is also important:

-#cmakedefine WORDS_BIGENDIAN
+#cmakedefine WORDS_BIGENDIAN 1


Kind regards,
Bernhard

Bug#910208: Crash at encoding change

[Egmont Koblinger]

Package: libvte-2.91-0
Version: 0.54.0-1
Severity: grave

Open gnome-terminal, and use its Terminal -> Set Character Encoding
menu to switch to another encoding. Switch back, then again to
something different.

gnome-terminal crashes.

Mainstream vte 0.54.1 fixes this issue. Could you please upgrade (or
at least cherry-pick this fix)?

Thanks,
egmont

Processed: linux-headers-4.18.0-*: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + linux-headers-4.18.0-1-amd64
Bug #910207 [src:linux] linux-headers-4.18.0-*: unhandled symlink to directory 
conversion: /usr/share/doc/PACKAGE
Added indication that 910207 affects linux-headers-4.18.0-1-amd64

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

Bug#910207: linux-headers-4.18.0-*: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Source: linux
Version: 4.18.8-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + linux-headers-4.18.0-1-amd64

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:


For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m31.8s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/linux-headers-4.18.0-1-amd64/changelog.Debian.gz 
(linux-headers-4.18.0-1-amd64) != 
/usr/share/doc/linux-headers-4.18.0-1-common/changelog.Debian.gz 
(linux-headers-4.18.0-1-common)
/usr/share/doc/linux-headers-4.18.0-1-amd64 -> linux-headers-4.18.0-1-common
  /usr/share/doc/linux-headers-4.18.0-1-amd64/copyright 
(linux-headers-4.18.0-1-amd64) != 
/usr/share/doc/linux-headers-4.18.0-1-common/copyright 
(linux-headers-4.18.0-1-common)
/usr/share/doc/linux-headers-4.18.0-1-amd64 -> linux-headers-4.18.0-1-common

This seems to happen in all linux-headers-VERSION-ABI-FLAVOR packages.

(This will probably resolve automatically with the next ABI bump.)


cheers,

Andreas


linux-headers-4.18.0-1-amd64_4.18.8-1.log.gz
Description: application/gzip

Bug#910206: libpbbam-dev: missing Breaks+Replaces: libpbbam (<< 0.18)

[Andreas Beckmann]

Package: libpbbam-dev
Version: 0.18.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../8-libpbbam-dev_0.18.0+dfsg-1_amd64.deb ...
  Unpacking libpbbam-dev (0.18.0+dfsg-1) over (0.7.4+ds-1+b1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-IoLOpc/8-libpbbam-dev_0.18.0+dfsg-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libpbbam.so', which is also 
in package libpbbam:amd64 0.7.4+ds-1+b1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-IoLOpc/8-libpbbam-dev_0.18.0+dfsg-1_amd64.deb


cheers,

Andreas


libpbbam-dev_0.18.0+dfsg-1.log.gz
Description: application/gzip

Bug#910205: libadios-bin: fails to remove: update-alternatives: error: no alternatives for adios

[Andreas Beckmann]

Package: libadios-bin
Version: 1.13.1-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to remove.

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

  Removing libadios-bin (1.13.1-7) ...
  update-alternatives: error: no alternatives for adios
  dpkg: error processing package libadios-bin (--remove):
   installed libadios-bin package pre-removal script subprocess returned error 
exit status 2


cheers,

Andreas


libadios-bin_1.13.1-7.log.gz
Description: application/gzip

Bug#908681: libsane1: nothing provides libsane so xsane uninstallable

[Agustin Martin]

On Wed, Oct 03, 2018 at 10:25:31AM +1300, Ben Caradoc-Davies wrote:
> The removal of "Provides: libsane" in libsane1 1.0.27-2 makes xsane
> uninstallable because nothing provides libsane.

Hi all,

I am aware that keeping "libsane" name with "Provides: libsane1" is under
consideration. 

In case that is not finally decided and current status is preserved, should
not sane-backends provide a libsane transitional package? Something like

Package: libsane
Section: oldlibs
Priority: extra
Architecture: all
Depends:
 libsane1,
 ${misc:Depends}
Description: Transitional package for easier upgrade to libsane1
 This is a dummy transitional package to smooth upgrade to libsane1.
 .
 It can be safely removed afterwards.

Regards,

-- 
Agustin

Bug#906388: nipy: FTBFS in buster/sid (failing tests)

[Yaroslav Halchenko]

update:
- uploaded sympy 1.3 which resolves sympy bug
- running by upstream the resolution for the other failed test:
  https://github.com/nipy/nipy/pull/445

and will upload fixed up package tomorrow


On Tue, 02 Oct 2018, Yaroslav Halchenko wrote:

> FWIW, two of the errors are caused by a bug in sympy which was fixed in
> 1.3 .  I am preparing sympy 1.3 although didn't check yet if it would
> fix it in nipy tests (not clear why it wasn't triggered before)

> On Fri, 17 Aug 2018, Santiago Vila wrote:

> > Package: src:nipy
> > Version: 0.4.2-1
> > Severity: serious
> > Tags: ftbfs

> > Dear maintainer:

> > I tried to build this package in buster but it failed:
-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik


signature.asc
Description: PGP signature

Bug#909974: backports.ssl-match-hostname should be removed for buster

[Ivo De Decker]

Hi,

On 10/02/2018 09:22 PM, Felipe Sateler wrote:

Hi Matthias, Ivo,

On Sun, 30 Sep 2018 22:59:26 +0200 Ivo De Decker > wrote:

 > clone 869896 -1
 > retitle -1 remove unneeded dependency on backports.ssl-match-hostname
 > block 869896 by -1
 > clone -1 -2 -3 -4 -5
 > reassign -1 libcloud
 > reassign -2 python-docker
 > reassign -3 websocket-client
 > reassign -4 docker-compose
 > reassign -5 sagemath
 > thanks

Next time, please CC the affected packages, otherwise it's easy to miss.


Good point. Sorry about that!

Thanks for the quick fix.

Ivo

Bug#910202: libghc-parsec3-dev: ships /var/lib/ghc/package.conf.d/parsec-3.1.13.0.conf which is now also in ghc

[Andreas Beckmann]

Package: libghc-parsec3-dev
Version: 3.1.13.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package libghc-parsec3-dev.
  (Reading database ... 
(Reading database ... 10244 files and directories currently installed.)
  Preparing to unpack .../libghc-parsec3-dev_3.1.13.0-3_amd64.deb ...
  Unpacking libghc-parsec3-dev (3.1.13.0-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libghc-parsec3-dev_3.1.13.0-3_amd64.deb (--unpack):
   trying to overwrite '/var/lib/ghc/package.conf.d/parsec-3.1.13.0.conf', 
which is also in package ghc 8.4.3+dfsg1-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libghc-parsec3-dev_3.1.13.0-3_amd64.deb


cheers,

Andreas


libghc-parsec3-dev_3.1.13.0-3.log.gz
Description: application/gzip

Processed: clone 907751

[Debian Bug Tracking System]

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

> clone 907751 -1
Bug #907751 [ftp.debian.org] RM: vmdebootstrap -- ROM; upstream discontinued, 
obsolete, better options exist
Bug 907751 cloned as bug 910201
> reassign -1 vmdebootstrap
Bug #910201 [ftp.debian.org] RM: vmdebootstrap -- ROM; upstream discontinued, 
obsolete, better options exist
Bug reassigned from package 'ftp.debian.org' to 'vmdebootstrap'.
Ignoring request to alter found versions of bug #910201 to the same values 
previously set
Ignoring request to alter fixed versions of bug #910201 to the same values 
previously set
> severity -1 serious
Bug #910201 [vmdebootstrap] RM: vmdebootstrap -- ROM; upstream discontinued, 
obsolete, better options exist
Severity set to 'serious' from 'normal'
> retitle -1 vmdebootstrap should not be in buster
Bug #910201 [vmdebootstrap] RM: vmdebootstrap -- ROM; upstream discontinued, 
obsolete, better options exist
Changed Bug title to 'vmdebootstrap should not be in buster' from 'RM: 
vmdebootstrap -- ROM; upstream discontinued, obsolete, better options exist'.
> thanks
Stopping processing here.

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

Processed: tagging 909286

[Debian Bug Tracking System]

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

> tags 909286 - newcomer
Bug #909286 [firefox] firefox: "The bookmarks and history system will not be 
functional" message always
Removed tag(s) newcomer.
> thanks
Stopping processing here.

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

Bug#907953: marked as done (network-manager-strongswan FTBFS with glib 2.58)

[Debian Bug Tracking System]

Your message dated Wed, 03 Oct 2018 13:49:47 +
with message-id 
and subject line Bug#907953: fixed in network-manager-strongswan 1.4.4-2
has caused the Debian Bug report #907953,
regarding network-manager-strongswan FTBFS with glib 2.58
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.)


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/network-manager-strongswan.html

...
nm-strongswan.c: In function 'strongswan_plugin_ui_widget_class_init':
nm-strongswan.c:647:2: error: 'g_type_class_add_private' is deprecated 
[-Werror=deprecated-declarations]
  g_type_class_add_private (req_class, sizeof 
(StrongswanPluginUiWidgetPrivate));
  ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-3.0/gdk/gdkapplaunchcontext.h:28,
 from /usr/include/gtk-3.0/gdk/gdk.h:32,
 from /usr/include/gtk-3.0/gtk/gtk.h:30,
 from nm-strongswan.c:28:
/usr/include/glib-2.0/gobject/gtype.h:1303:10: note: declared here
 void g_type_class_add_private   (gpointerg_class,
  ^~~~
cc1: all warnings being treated as errors
make[3]: *** [Makefile:568: libnm_vpn_plugin_strongswan_la-nm-strongswan.lo] 
Error 1
--- End Message ---
--- Begin Message ---
Source: network-manager-strongswan
Source-Version: 1.4.4-2

We believe that the bug you reported is fixed in the latest version of
network-manager-strongswan, 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.
Harald Dunkel  (supplier of updated network-manager-strongswan 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 03 Oct 2018 11:33:28 +0200
Source: network-manager-strongswan
Binary: network-manager-strongswan
Architecture: source
Version: 1.4.4-2
Distribution: unstable
Urgency: medium
Maintainer: Harald Dunkel 
Changed-By: Harald Dunkel 
Description:
 network-manager-strongswan - network management framework (strongSwan plugin)
Closes: 907953
Changes:
 network-manager-strongswan (1.4.4-2) unstable; urgency=medium
 .
   * ignore deprecated api in libglib2.0-dev 2.58.1-2, until upstream
 fixes https://wiki.strongswan.org/issues/2765 (Closes: #907953)
Checksums-Sha1:
 54aa272867d677c925593945c98e690b4249928c 1863 
network-manager-strongswan_1.4.4-2.dsc
 3cb7e465feb914e42d81e513b0d0c75012257c49 3284 
network-manager-strongswan_1.4.4-2.debian.tar.xz
Checksums-Sha256:
 a7f618729ad332b0db5dca62cc7be04213709e053b39351883b05b91102817b1 1863 
network-manager-strongswan_1.4.4-2.dsc
 0b35cbd82af80a6e0283b386bd3729614662f63797d8b2387a2b6ece9b449e74 3284 
network-manager-strongswan_1.4.4-2.debian.tar.xz
Files:
 5ff518bbc69ae68d4efa35afa063471d 1863 net extra 
network-manager-strongswan_1.4.4-2.dsc
 3d97e64381799599a69411d2a5da4c78 3284 net extra 
network-manager-strongswan_1.4.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEVZrkbC1rbTJl58uh4+M5I0i1DTkFAlu0xQsACgkQ4+M5I0i1
DTm0pAgAhV1WlAX/y657AC9+vv1VjplQLiX/HHccmbjW2FfvjR7aNuoTlesgQV77
8ggiNHrU5/tNxV/iTFxTt5K9Zc/lBXyTlUv9ORK2iw4L4sr/1rp3yCt3QBQaXDuA
9JmaMRkm5hNfZhyiCiaWehM32k6jbi/mMtcYHOMP7s5v+r0g/wWcPpq/2bX1erVJ
xFK99hlTn3cAcXo/H2W5wi3e5p4gCOOYQkhc5v1ntyAIlLsWeH/xxOg4vNfqDzbv
5V40yjyrMPfnxwiSgaDSBy0ngNmbpnDaNTVdwDcf6Y2TNMq+SRah9pXVXDfxZOcz
0jjTvyZ5TmEfM++MA6r1B+fREWfmzw==
=YLRh
-END PGP SIGNATURE End Message ---

Bug#857299: Package builds again

[Helmut Grohne]

On Wed, Oct 03, 2018 at 02:37:23PM +0200, Frédéric Bonnard wrote:
> does this bug still appear for rebootstrap ?
> How can I simply reproduce it within rebootstrap ?
> Building inside sbuild works.

This is/was a native problem. It was filed against the natively built
ppc64el package (noticed as a side effect of my rebootstrap work). If it
is fixed there, just close the bug.

Helmut

Bug#907953: network-manager-strongswan FTBFS with glib 2.58

[Ian Jackson]

Harald Dunkel writes ("Re: network-manager-strongswan FTBFS with glib 2.58"):
> I have created a new source package. It just disables the error message.
> When upstream releases a fixed version, this patch can be removed again.
> 
> Ian, would you mind to sponsor an upload? I have signed the new tag
> debian/1.4.4-2.

Done, thanks.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#906050: marked as done (python-plplot-qt lost its generated python dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 03 Oct 2018 13:34:41 +
with message-id 
and subject line Bug#906050: fixed in plplot 5.13.0+dfsg-9
has caused the Debian Bug report #906050,
regarding python-plplot-qt lost its generated 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.)


-- 
906050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-plplot-qt
Version: 5.13.0+dfsg-8
Severity: serious
Tags: patch

Fix:

--- debian/control.old  2018-08-13 14:34:30.282538085 +
+++ debian/control  2018-08-13 14:35:06.738537738 +
@@ -449,9 +449,9 @@
 Depends: plplot-driver-qt (= ${binary:Version}),
  python-plplot (= ${binary:Version}),
  ${misc:Depends},
- ${python2:Depends},
+ ${python:Depends},
  ${shlibs:Depends}
-Provides: ${python2:Provides}
+Provides: ${python:Provides}
 Description: Scientific plotting library (Python 2 Qt GUI)
  PLplot is relatively small, portable, freely distributable, and is rich
  enough to satisfy most users.  It has a wide range of plot types including
--- End Message ---
--- Begin Message ---
Source: plplot
Source-Version: 5.13.0+dfsg-9

We believe that the bug you reported is fixed in the latest version of
plplot, 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.
Ole Streicher  (supplier of updated plplot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 03 Oct 2018 14:16:29 +0200
Source: plplot
Binary: libplplot-dev libplplot15 libplplotcxx13 libplplotfortran0 
libplplot-java libcsironn0 libcsirocsa0 libqsastime0 libqsastime-dev 
plplot-driver-xwin plplot-driver-wxwidgets libplplotwxwidgets1 plplot-tcl 
plplot-tcl-bin plplot-tcl-dev plplot-driver-cairo plplot-driver-qt libplplotqt2 
python-plplot python-plplot-qt python3-plplot python3-plplot-qt octave-plplot 
libplplotada2 libplplot-ada-dev plplot-doc libplplot-ocaml libplplot-ocaml-dev 
libplplot-lua
Architecture: source
Version: 5.13.0+dfsg-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Ole Streicher 
Description:
 libcsirocsa0 - Scientific plotting library (CSIRO csa library)
 libcsironn0 - Scientific plotting library (CSIRO nn library)
 libplplot-ada-dev - Ada support for PLplot, a plotting library (development 
files)
 libplplot-dev - Scientific plotting library (development files)
 libplplot-java - Scientific plotting library (Java bindings)
 libplplot-lua - Scientific plotting library (Lua bindings)
 libplplot-ocaml - OCaml bindings for the scientific plotting library
 libplplot-ocaml-dev - OCaml support for the PLplot plotting library 
(development files)
 libplplot15 - Scientific plotting library
 libplplotada2 - Ada support for PLplot, a plotting library
 libplplotcxx13 - Scientific plotting library (C++ binding)
 libplplotfortran0 - Scientific plotting library (fortran bindings)
 libplplotqt2 - Scientific plotting library (Qt bindings)
 libplplotwxwidgets1 - Scientific plotting library (wxWidgets bindings)
 libqsastime-dev - Time format conversion library (development files)
 libqsastime0 - Time format conversion library
 octave-plplot - Octave support for PLplot, a plotting library
 plplot-doc - Documentation for PLplot, a plotting library
 plplot-driver-cairo - Scientific plotting library (Cairo driver)
 plplot-driver-qt - Scientific plotting library (Qt driver)
 plplot-driver-wxwidgets - Scientific plotting library (wxWidgets driver)
 plplot-driver-xwin - Scientific plotting library (X11 driver)
 plplot-tcl - Tcl/Tk support for PLplot, a plotting library
 plplot-tcl-bin - Tcl/Tk tools for PLplot, a plotting library
 plplot-tcl-dev - Tcl/Tk development support for PLplot, a plotting library
 python-plplot - Python 2 support for PLplot, a plotting library
 python-plplot-qt - Scientific plotting library (Python 2 Qt GUI)
 python3-plplot - Python 3 support for PLplot, a plotting library
 python3-plplot-qt - Scientific plotting library (Python 3 Qt GUI)
Closes: 893413 901920 906050
Changes:
 plplot (