Bug#828288: marked as done (duo-unix: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 07:48:42 +
with message-id 
and subject line Bug#828288: fixed in duo-unix 1.9.19-1
has caused the Debian Bug report #828288,
regarding duo-unix: FTBFS with openssl 1.1.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.)


-- 
828288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: duo-unix
Version: 1.9.11-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/duo-unix_1.9.11-1_amd64-20160529-1415

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: duo-unix
Source-Version: 1.9.19-1

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

Debian distribution maintenance software
pp.
Kees Cook  (supplier of updated duo-unix 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, 16 Nov 2016 21:25:57 -0800
Source: duo-unix
Binary: libpam-duo login-duo libduo3 libduo-dev
Architecture: source amd64
Version: 1.9.19-1
Distribution: unstable
Urgency: medium
Maintainer: Kees Cook 
Changed-By: Kees Cook 
Description:
 libduo-dev - Duo Security development libraries and header files
 libduo3- Duo Security library
 libpam-duo - PAM module for Duo Security two-factor authentication
 login-duo  - login wrapper for Duo Security two-factor authentication
Closes: 748895 826553 828288
Changes:
 duo-unix (1.9.19-1) unstable; urgency=medium
 .
   * New upstream release (Closes: 826553).
   * control: fixed typos (Closes: 748895).
   * patches/openssl.patch: add openssl 1.1.0 support (Closes: 828288).
   * copyright: fix filename globs to use .? since .[ch] isn't supported.
   * control: bump standards version; no changes needed.
   * rules:
 - enable full hardening
 - strip rpath
Checksums-Sha1:
 3992b4cfbd5ae75df4c398e5deabb3d00fe34ad3 1956 duo-unix_1.9.19-1.dsc
 d095f005ae42703d338f9002b13f12d5a2160fcb 470432 duo-unix_1.9.19.orig.tar.gz
 157bb7d648aa4e311bebe9c736d65ca2830e2abc 8436 duo-unix_1.9.19-1.debian.tar.xz
 4246c9df64e87efd03ab2787057d13f122241d17 7772 duo-unix_1.9.19-1_amd64.buildinfo
 4cb6fc5e960272f46b87dfef01e29a1f40a702d8 8554 libduo-dev_1.9.19-1_amd64.deb
 c15b58fd20ea98e142bfffb68cc0d93c12d622b3 65030 
libduo3-dbgsym_1.9.19-1_amd64.deb
 c189078e1c2bf217b7a05ed5bbba39e00520939f 35398 libduo3_1.9.19-1_amd64.deb
 0ea95d7803d89c641045aa0b59b7ebe133214f40 13844 
libpam-duo-dbgsym_1.9.19-1_amd64.deb
 f321b624497a561e583cdeedbf2dd926df10011a 14814 libpam-duo_1.9.19-1_amd64.deb
 41690436797a0e4778fa31822425b07034f96465 12090 
login-duo-dbgsym_1.9.19-1_amd64.deb
 07f50402477747ba8b20d58f314f9f1228f597f6 15704 login-duo_1.9.19-1_amd64.deb
Checksums-Sha256:
 c8b99832a29a6a574c6212c42391ed1ff7b49fec6cf12ab34f8eceeedefb6b33 1956 
duo-unix_1.9.19-1.dsc
 2d23f9700f091da1c9113b45919203b37fac6392a9e24a666c7b0269a7571b0a 470432 
duo-unix_1.9.19.orig.tar.gz
 e12a76716d26fa7b8b882b9573058f166561da5947a31479d7f80efe403121f9 8436 
duo-unix_1.9.19-1.debian.tar.xz
 59e036ce17258b573d01ca2d020a262c68eb6eb433f652726528e367b88a0af3 7772 
duo-unix_1.9.19-1_amd64.buildinfo
 e8872e3bb7c019ce96af12d778e2cc15f0569e9a60f000a7ed9b8e487c04240b 8554 
libduo-dev_1.9.19-1_amd64.deb
 60dd4209a334ab0bcadeb3e0acedf4b0c4f2742bf8a07fdb5d7355f686a4 65030 
libduo3-dbgsym_1.9.19-1_amd64.deb
 

Bug#844486: gnuplot-qt: Mismatch between the program and library build versions with GNUTERM=wxt

[Anton Gladky]

Hi Olly,

thanks for your opinion! From my point of view, wxwidgets3.0
should be binNMUed together with all rdeps. Because even a
minor source upload of wxwidges3.0t will start this process anyway
but in uncoordinated mode.

Cheers

Anton

2016-11-17 2:36 GMT+01:00 Olly Betts :
> However, if you want to eliminate this warning message and are going to
> binNMU wxwidgets3.0 to that end, you will also need to binNMU any of its
> rdeps which haven't been built with the newer compiler ABI, or else
> you're just going to swap around which rdeps issue this warning.
>
> Cheers,
> Olly

Bug#817679: marked as done (statserial: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 03:07:01 +
with message-id 
and subject line Bug#817679: fixed in statserial 1.1-22.1
has caused the Debian Bug report #817679,
regarding statserial: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: statserial
Severity: important
Usertags: compat-4-removal

Hi,

The package statserial uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: statserial
Source-Version: 1.1-22.1

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated statserial 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Nov 2016 00:01:02 -0200
Source: statserial
Binary: statserial
Architecture: source
Version: 1.1-22.1
Distribution: unstable
Urgency: medium
Maintainer: Vince Mulhollon 
Changed-By: Joao Eriberto Mota Filho 
Description:
 statserial - Displays serial port modem status lines
Closes: 817679
Changes:
 statserial (1.1-22.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10. (Closes: #817679)
   * debian/compat: created.
   * debian/control:
   - Added a ${misc:Depends} variable to Depends field.
   - Added a Homepage field.
   - Bumped Standards-Version to 3.9.8.
   * debian/watch: created.
Checksums-Sha1:
 28c964110941d676a4db12d896fa3f7b7a8e8435 1689 statserial_1.1-22.1.dsc
 e49fbec05047ecc8ae54600a239d6d63f4583388 3414 statserial_1.1-22.1.diff.gz
Checksums-Sha256:
 132e95c85be2b229f34e026421310a144b927a972225709965745bf1e62cac2a 1689 
statserial_1.1-22.1.dsc
 36830e1a28052b921c82ecfff03c7aff5e2d7a3df85a381be61c90e0ec7da823 3414 
statserial_1.1-22.1.diff.gz
Files:
 ef16ca30156c500eabf714ebbaa504b9 1689 utils extra statserial_1.1-22.1.dsc
 672f8e44b356c2dcd3bd832530df681d 3414 utils extra statserial_1.1-22.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYH+SXAAoJEN5juccE6+nv7ssP/2XM6VZWmS20lYP1OGV32njJ
IVDTXurtEkGJ9DxFqZ3sJzEmTgaEU8d0s2kDmkt8qQGHBXN7GXSRVOcft2SMnlES
J4JJbdMi7z/7UivIMtwIarGoPMg3Zwh1jSPojn4JH0x2FpyGAUchpOB1A1daygcH
vhIgu5fdGKT/2J1LaKYRa5/6eIim9Fcj3aDB6hv3uNKhVw2QMSxk9XTBchWk7xit
gwuL6z03rB2LZhdB310T9NRqMPC7kmaAUtO9O7ziKzdpywVZ5Z9uv8Z+O/QI1B+Y
ZZ3B03mI40LXG8TQWVfvP8NN8tKPCzALSG8sWQtGBYMBLyA6BX1McrR5yK/p5ejb
+Epwx426qPFfUjvTzP7f3Ca/t+divr+RYvhy6J8UIBnbGlvjzq8EO4mI3OF7ZBSZ
IQ24JkkvrICQdDZfz0h1CLRMxn++CgTLOj8rVgj77p1+WM9dSN4GQ/gcCRAo8Mua
q1BRNPGF+skgnoYoa28UxQpG26B12fdSLbsSmmCpKBQhvRfGCN+POjBBYOmGROhI
pfKR7o1FdMrXC+RByLcx1zE7dnqfw9TBSgIc9r4gMYzrCHUKGdDWcESY8q0C1NxF
t2HqPDQb73kvMTGt/+jhbrXba/7zND9ghpq7dSmLXRbKWewDhwuxL5kdR7xjfgpX
VEb6pbgKrWRwEMaCGG5M
=xA29
-END PGP SIGNATURE End Message ---

Bug#844486: gnuplot-qt: Mismatch between the program and library build versions with GNUTERM=wxt

[Olly Betts]

On Wed, Nov 16, 2016 at 08:14:00PM +0100, Anton Gladky wrote:
> block 844486 by 844526
> thanks
> 
> wxwidget should be binnmued to fix the bug properly.

I don't believe there's actually any real bug here, let alone an RC one.

GCC makes small fixes to obscure corner cases of the C++ ABI from time
to time and (not unreasonably) bumps the ABI version each time.  It used
to be the case that GCC defaulted to the old ABI version in this case,
but more recently they seem to make the new ABI version the default
instead.

In upstream wxWidgets, if the compile-time ABI and run-time ABI don't
match, then you get an error and the app won't run, which is just not
helpful.  In Debian we reduce that error to a warning - in practice I've
never seen an actual problem due to this, but leaving the warning there
means that this at least gets flagged as a potential issue.

However, if you want to eliminate this warning message and are going to
binNMU wxwidgets3.0 to that end, you will also need to binNMU any of its
rdeps which haven't been built with the newer compiler ABI, or else
you're just going to swap around which rdeps issue this warning.

Cheers,
Olly

Bug#828412: marked as done (libsecp256k1: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 01:18:52 +
with message-id 
and subject line Bug#828412: fixed in libsecp256k1 0.1~20161026-1
has caused the Debian Bug report #828412,
regarding libsecp256k1: FTBFS with openssl 1.1.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.)


-- 
828412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsecp256k1
Version: 0.1~20160216-3
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/libsecp256k1_0.1~20160216-3_amd64-20160529-1444

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: libsecp256k1
Source-Version: 0.1~20161026-1

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated libsecp256k1 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, 17 Nov 2016 01:49:54 +0100
Source: libsecp256k1
Binary: libsecp256k1-0 libsecp256k1-dev
Architecture: source amd64
Version: 0.1~20161026-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Bitcoin Team 
Changed-By: Jonas Smedegaard 
Description:
 libsecp256k1-0 - library for EC operations on curve secp256k1
 libsecp256k1-dev - library for EC operations on curve secp256k1 - development 
header
Closes: 828412
Changes:
 libsecp256k1 (0.1~20161026-1) unstable; urgency=medium
 .
   [ upstream ]
   * Snapshot from upstream git.
 + Fix secp256k1_fe_inv_all_var parameter order.
 + Fix secp256k1_ge_set_all_gej_var parameter order.
 + Fix secp256k1_ge_set_table_gej_var parameter order.
 + Remove guarantees about memcmp-ability.
 + Fix auto-enabled static precompuatation.
 + Update scalar_4x64_impl.h.
 + Restructure nonce clearing.
 .
   [ Jonas Smedegaard ]
   * Update watch file: Use substitution string @PACKAGE@.
   * Refresh patch.
   * Simplify README.source: Skip options set in gbp.conf.
   * Update copyright info:
 + Use license shortname FSFAP (not FSFUL~generic).
 + Add another copyright holder (no new license).
   * Build-depend on libssl1.0-dev (with older libssl-dev as fallback):
 OpenSSL 1.1 not yet supported upstream.
 Closes: Bug#828412. Thanks to Kurt Roeckx.
Checksums-Sha1:
 8961775af533b79f52ece2fe622782338d9a61ff 2254 libsecp256k1_0.1~20161026-1.dsc
 4e0492382286244434d64fa956c37cff6cbf9d53 147872 
libsecp256k1_0.1~20161026.orig.tar.gz
 9c2ab3910d19926f23a4070d56f66b16702fcd71 7380 
libsecp256k1_0.1~20161026-1.debian.tar.xz
 1dd9ce48f52dfdf2f95accef385f47bf38fc1c80 77566 
libsecp256k1-0-dbgsym_0.1~20161026-1_amd64.deb
 e7f540d6f589f47cda29cd70082804abcbfab3fc 103854 
libsecp256k1-0_0.1~20161026-1_amd64.deb
 f18b447fe43d4635c57a4dbc56d05993757f 109986 
libsecp256k1-dev_0.1~20161026-1_amd64.deb
 094cf05700b9cabf47aa5d98c227443eae064798 7446 
libsecp256k1_0.1~20161026-1_amd64.buildinfo
Checksums-Sha256:
 d466479beb21dcef670107404dd228f8206a4281c9e8ac2eb175a11854446310 2254 
libsecp256k1_0.1~20161026-1.dsc
 bfc81adc5b5ece357cbc5be6ea0443e7309825c366565278900739c7f572316d 147872 
libsecp256k1_0.1~20161026.orig.tar.gz
 c59fdb8f8f0e8409a0217f87e5c6a24958d544c4fbbf96cd5d5c5fce22f0e2c4 7380 
libsecp256k1_0.1~20161026-1.debian.tar.xz
 

Processed (with 1 error): limit source to debbugs, tagging 584922, tagging 49228, tagging 800287, tagging 717967

[Debian Bug Tracking System]

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

> limit source debbugs
Limiting to bugs with field 'source' containing at least one of 'debbugs'
Limit currently set to 'source':'debbugs'

> tags 584922 + pending
Bug #584922 [debbugs] return 400 when the client sends a malformed request
Added tag(s) pending.
> tags 49228 + pending
Failed to alter tags of Bug 49228: Bug 49228 mergedwith differs from bug 
197304: (197304: '49228 322931 378108 395154 424431 504375 526049 540222') vs. 
('322931 378108 395154 424431 49228 504375 526049 540222') (197304 322931 
378108 395154 424431 504375 526049 540222 49228).

> tags 800287 + pending
Bug #800287 [src:debbugs] debbugs: Please migrate a supported debhelper compat 
level
Added tag(s) pending.
> tags 717967 + pending
Bug #717967 [debbugs-web] debbugs-web: fails to upgrade from 'sid' - trying to 
overwrite /etc/debbugs/html/server-control.html.in
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: reopening 823865

[Debian Bug Tracking System]

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

> reopen 823865
Bug #823865 {Done: Bjoern Boschman } [phpsysinfo] 
d/copyright is missing licenses for many files
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions phpsysinfo/3.2.5-3.
> thanks
Stopping processing here.

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

Bug#823865: marked as done (d/copyright is missing licenses for many files)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 01:05:07 +
with message-id 
and subject line Bug#823865: fixed in phpsysinfo 3.2.5-3
has caused the Debian Bug report #823865,
regarding d/copyright is missing licenses for many files
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.)


-- 
823865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpsysinfo
Version: 3.2.1-1
Severity: serious

Dear maintainer,

d/copyright doesn't list all license holders and has wrong copyright
for at least some files:

Please convert to machine-readable copyright file and add missing copyrights:
 + Files: * is GPLv2+, e.g. any later version and not just GPL-2
 + Files: debian/* copyright is missing (is that also GPL-2), could you try 
contacting previous maintainers and make this clear?
 + Files: js/jQuery/* licenses are missing
 + Files: js/vendor/* licenses are missing
 + Files: templates/plugin/* licenses are missing, see the originals 
https://github.com/ludo/jquery-treetable/tree/master/css
 + Files: templates/vendor/* licenses are missing

Then there's a lot of pictures in gfx/, could you please contact
upstream and clarify the licenses for the images there?  At least
gfx/images/ looks suspicious, but there are lot of other images all
around.

The rest look okay(ish), but double check it anyway please.

Cheers,
Ondrej

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: phpsysinfo
Source-Version: 3.2.5-3

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

Debian distribution maintenance software
pp.
Bjoern Boschman  (supplier of updated phpsysinfo 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, 24 Aug 2016 16:24:20 +0200
Source: phpsysinfo
Binary: phpsysinfo
Architecture: source
Version: 3.2.5-3
Distribution: unstable
Urgency: medium
Maintainer: Bjoern Boschman 
Changed-By: Bjoern Boschman 
Description:
 phpsysinfo - PHP based host information
Closes: 816766 821628 823865
Changes:
 phpsysinfo (3.2.5-3) unstable; urgency=medium
 .
   * New upstream release (Closes: #816766)
   * updated Standards-Version: 3.9.8.0
   * introduced new dependencies for php7.0 transition (Closes: #821628)
   * machine readable debian/copyright (Closes: #823865)
Checksums-Sha1:
 bb9159c5e79fac1d55849be0ef8af866932f88e1 1856 phpsysinfo_3.2.5-3.dsc
 d91fd0aba1f6596492b12495080c168cb94b059d 947527 phpsysinfo_3.2.5.orig.tar.gz
 97cb1ff8ecc1408f11c250a7e376be3bf9b740c9 5864 phpsysinfo_3.2.5-3.debian.tar.xz
Checksums-Sha256:
 f7a10e635a67b5121907e367a6451d7cc1e3fd69c8de38117e981c38527b8ae0 1856 
phpsysinfo_3.2.5-3.dsc
 580af40ab1909ee913fd507839512c1e11ab14cd296dce0fa0f34c17d8db57ba 947527 
phpsysinfo_3.2.5.orig.tar.gz
 c12f2754e84f1e68af70176d66d17e1fa756467294020f25b2e6e614521850fb 5864 
phpsysinfo_3.2.5-3.debian.tar.xz
Files:
 72061712bca453c198bb13ea22269b0b 1856 web optional phpsysinfo_3.2.5-3.dsc
 08875b31a9a7a662473d8cbe866059e7 947527 web optional 
phpsysinfo_3.2.5.orig.tar.gz
 33689020a61431e3fab8afaa8a4e64c2 5864 web optional 
phpsysinfo_3.2.5-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJYLPzVXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHwR8QAKxo/ObVbVH3E9WQFwOrl4og
V+8Psqs562FtpcG1vv3lZR5Lz38Akvz0On72m4D06EPNwhVSqLULP0NxiE5xin4o
19SK2X8n/DgapGOx7GN1qoHBB7eieirfnkwNM1nUn1cOOK5tisArmNDPFRDlhxK6
CMAmUJDQiyYJ8qQ5xTKqtDPUtgq956M3SC8oeu9OcxKaSLLhX7o/rP5nWu+Cm3Vt

Bug#843404: marked as done (haskell-swish: needs sourceful upload for ghc8 transition)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 01:05:01 +
with message-id 
and subject line Bug#843404: fixed in haskell-swish 0.9.1.7-3
has caused the Debian Bug report #843404,
regarding haskell-swish: needs sourceful upload for ghc8 transition
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.)


-- 
843404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-swish
Version: 0.9.1.7-2
Severity: serious

libghc-swish-doc needs to be rebuilt against ghc 8 so it
can become installable.
--- End Message ---
--- Begin Message ---
Source: haskell-swish
Source-Version: 0.9.1.7-3

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated haskell-swish 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, 17 Nov 2016 01:18:10 +0100
Source: haskell-swish
Binary: swish libghc-swish-dev libghc-swish-doc libghc-swish-prof
Architecture: source
Version: 0.9.1.7-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Jonas Smedegaard 
Description:
 libghc-swish-dev - semantic web toolkit - libraries
 libghc-swish-doc - semantic web toolkit - library documentation
 libghc-swish-prof - semantic web toolkit - profiling libraries
 swish  - semantic web toolkit - tools
Closes: 843404
Changes:
 haskell-swish (0.9.1.7-3) unstable; urgency=medium
 .
   * Modernize CDBS setup: Build-depend on licensecheck (not devscripts).
   * Simply doing this rebuild implies rebuilding against ghc 8.
 Closes: Bug#843404. Thanks to Clint Adams.
Checksums-Sha1:
 f258c68fa069cdf0c55a9dde3effe97e1554285f 2971 haskell-swish_0.9.1.7-3.dsc
 7e736ba898e837990add6fbaf37bb86e6a301ea7 7500 
haskell-swish_0.9.1.7-3.debian.tar.xz
Checksums-Sha256:
 a33cdfee7e982ae8817ca263b975301859ef7cfbab1d7c70541d3943f378871b 2971 
haskell-swish_0.9.1.7-3.dsc
 36c134d1b1371a951cce72564681b69c6a44e05cb599abc04134bbf991820da1 7500 
haskell-swish_0.9.1.7-3.debian.tar.xz
Files:
 033cfe97589b5eb43a035e7e9ff72897 2971 haskell optional 
haskell-swish_0.9.1.7-3.dsc
 a0d23ee05910053a45a504ec991e4a3f 7500 haskell optional 
haskell-swish_0.9.1.7-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYLP+EAAoJECx8MUbBoAEhNAYP/2yhWKHytfejpaUIQhkaHKO4
5Lt2lsV4ShYm8ohDbnXNBR+XW/GtYotHtrXzPccPeGPM+B4evNxmkyLj7tJxmBdt
NQZa/2LJJelXpGiLDSOBA9u6s2qZBVZ5HQv2kEQJgrTMapPvJCdcXZW66O9sAKxv
CifcbpQ1ZGFEyH/1etiSVJk02gM2jDUouYH94DFqhkIWtpgxXsK1o8+oavgBWmUj
P/O0sWIUNv7BzJJU5Cmj4qm2lmTaKSD1MxyUdya33jT6s0fU7xhWLfzt/5GuVmKJ
cHyvRGdLZqk86g/wxBpGmNIIcRNVsVAHz6Hdwt4gIpOgH0+7YFt3V4nmJsefRSq1
yzFAm4wilX1nMvs5+/DU4i6XWM02QXzsvXmsPmNC1QrwrlDteaRL+Ecmh/zS/13U
BiUQ79834HhXX37k7MBlttyXhE5S+vg1c9GI81gLK4aV1Ktj5CPQO2Mzq6RxQ/tF
mDLZNpH+hwJ44zma3iYaSFKYJhLge8IBvNC3FZfkjEArhjSbj7EVNXt9YmTRTABn
vCvfSnaE2FSv34m17t4qdUhEY9CujQNfcLDbaD4Ie7EraXWyVH7GKPeUZq3+y5Ak
9EXoRexbw7lqEJAZOKlvWr/hlMqqDb1MkCwZNfpa2SLVga9dZJIqydpQw0NsCVLG
pm0J7XN/gm2CMv8LKEmT
=vxnP
-END PGP SIGNATURE End Message ---

Bug#821628: marked as done (phpsysinfo: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 01:05:07 +
with message-id 
and subject line Bug#821628: fixed in phpsysinfo 3.2.5-3
has caused the Debian Bug report #821628,
regarding phpsysinfo: PHP 7.0 Transition
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.)


-- 
821628: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpsysinfo
Version: 3.2.1-1
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The phpsysinfo package currently depends on php5 php5-xsl .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: phpsysinfo -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUrKXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH/CUP/AoGnQ2NjcWex/mrXXRI2+Lx
wVBcTcODzmkSTnqJG8ORMQjaCktJeEohDCWHtTPdx3RhStBNKi8KlNytT9H9zOh4
GnMx8sDvkjH45P7jY+B944X/Unv8U6RloS3ztZxXfi/cvzd+HasIOxWbM5hgGlAZ
ntWx13m/HCrtWbLvJGfgAmRs54WLPDXbADcIjTt90jUb6XcGdhph2DaSMLvf+rYy
HG8a4/L274sBTYuy9u8XOihR/daeHx9vlIf22oueRlAa+9WSUmRzZ8hXwXRoJCIo

Processed: reopening 823865

[Debian Bug Tracking System]

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

> reopen 823865
Bug #823865 [phpsysinfo] d/copyright is missing licenses for many files
Bug 823865 is not marked as done; doing nothing.
> thanks
Stopping processing here.

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

Bug#844573: link-grammar: FTBFS (cannot find -lncurses)

[Santiago Vila]

Package: src:link-grammar
Version: 5.3.11-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2
   dh_testdir -i
   dh_update_autotools_config -i
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf --as-needed
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'

[... snipped ...]

build:

BUILD SUCCESSFUL
Total time: 1 second
make[3]: Leaving directory '/<>/bindings/java'
Making all in ocaml
make[3]: Entering directory '/<>/bindings/ocaml'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/bindings/ocaml'
Making all in python
make[3]: Entering directory '/<>/bindings/python'
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ 
-DPACKAGE_NAME=\"link-grammar\" -DPACKAGE_TARNAME=\"link-grammar\" 
-DPACKAGE_VERSION=\"5.3.11\" -DPACKAGE_STRING=\"link-grammar\ 5.3.11\" 
-DPACKAGE_BUGREPORT=\"link-gram...@googlegroups.com\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"link-grammar\" -DVERSION=\"5.3.11\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSTDC_HEADERS=1 
-DHAVE_STRNDUP=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 
-DHAVE_WORKING_VFORK=1 -DHAVE_WORKING_FORK=1 -DHAVE_PRCTL=1 
-DHAVE_LOCALE_T_IN_LOCALE_H=1 -DHAVE_MKLIT=1 -DHAVE_LIBSTDC__=1 
-DHAVE_HUNSPELL=1 -DHUNSPELL_DICT_DIR=\"/usr/share/myspell/dicts\" 
-DHAVE_EDITLINE=1 -DHAVE_WIDECHAR_EDITLINE=1 -DHAVE_REGEXEC=1 
-DHAVE_PYTHON=\"2.7\" -DHAVE_MAYBE_UNINITIALIZED=1 -I.   
-I/usr/include/python2.7 -I../.. -I../.. -Wdate-t
 ime -D_FORTIFY_SOURCE=2 -DUSE_PTHREADS=1 -DUSE_SAT_SOLVER=1  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -O3 -Wall -std=c++11 -c -o 
../../bindings/python/_clinkgrammar_la-lg_python_wrap.lo `test -f 
'../../bindings/python/lg_python_wrap.cc' || echo 
'./'`../../bindings/python/lg_python_wrap.cc
libtool: compile:  g++ -DPACKAGE_NAME=\"link-grammar\" 
-DPACKAGE_TARNAME=\"link-grammar\" -DPACKAGE_VERSION=\"5.3.11\" 
"-DPACKAGE_STRING=\"link-grammar 5.3.11\"" 
-DPACKAGE_BUGREPORT=\"link-gram...@googlegroups.com\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"link-grammar\" -DVERSION=\"5.3.11\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSTDC_HEADERS=1 
-DHAVE_STRNDUP=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 
-DHAVE_WORKING_VFORK=1 -DHAVE_WORKING_FORK=1 -DHAVE_PRCTL=1 
-DHAVE_LOCALE_T_IN_LOCALE_H=1 -DHAVE_MKLIT=1 -DHAVE_LIBSTDC__=1 
-DHAVE_HUNSPELL=1 -DHUNSPELL_DICT_DIR=\"/usr/share/myspell/dicts\" 
-DHAVE_EDITLINE=1 -DHAVE_WIDECHAR_EDITLINE=1 -DHAVE_REGEXEC=1 
-DHAVE_PYTHON=\"2.7\" -DHAVE_MAYBE_UNINITIALIZED=1 -I. -I/usr/include/python2.7 
-I../.. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -DUSE_PTHR
 EADS=1 -DUSE_SAT_SOLVER=1 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -Wall -std=c++11 
-c ../../bindings/python/lg_python_wrap.cc  -fPIC -DPIC -o 
../../bindings/python/.libs/_clinkgrammar_la-lg_python_wrap.o
/bin/bash ../../libtool  --tag=CXX   --mode=link g++  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -O3 -Wall -std=c++11 -version-info 8:11:3   -module 
-no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--as-needed -o 
_clinkgrammar.la -rpath /usr/lib/python2.7/dist-packages/linkgrammar 
../../bindings/python/_clinkgrammar_la-lg_python_wrap.lo  
../../link-grammar/liblink-grammar.la -L/usr/lib -lpython2.7 -lstdc++ 
libtool: link: g++  -fPIC -DPIC -shared -nostdlib 
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/crti.o 
/usr/lib/gcc/x86_64-linux-gnu/6/crtbeginS.o  
../../bindings/python/.libs/_clinkgrammar_la-lg_python_wrap.o   -Wl,-rpath 
-Wl,/<>/link-grammar/.libs -Wl,--as-needed 
../../link-grammar/.libs/liblink-grammar.so -L/usr/lib -lpython2.7 
-L/usr/lib/gcc/x86_64-linux-gnu/6 
-L/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu 
-L/usr/lib/gcc/x86_64-linux-gnu/6/../../../../lib -L/lib/x86_64-linux-gnu 
-L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib 
-L/usr/lib/gcc/x86_64-linux-gnu/6/../../.. -lstdc++ -lm -lc -lgcc_s 
/usr/lib/gcc/x86_64-linux-gnu/6/crtendS.o 
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/crtn.o  -g -O2 

Bug#844572: uncertainties: FTBFS randomly (FAIL: Full comparison to a Monte-Carlo calculation)

[Santiago Vila]

Package: src:uncertainties
Version: 2.4.4-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
==
FAIL: Full comparison to a Monte-Carlo calculation.
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/<>/uncertainties/test_umath.py", line 177, in 
test_monte_carlo_comparison
% (covariances_samples, covariances_this_module)
AssertionError: The covariance matrices do not coincide between the Monte-Carlo 
simulation and the direct calculation:
* Monte-Carlo:
[[  9.99611355e-05   1.34661091e-08   3.20307739e-04]
 [  1.34661091e-08   9.95636755e-07  -3.20894019e-05]
 [  3.20307739e-04  -3.20894019e-05   2.16969297e-03]]
* Direct calculation:
[[  1.e-04   0.e+00   3.17312046e-04]
 [  0.e+00   1.e-06  -3.37427446e-05]
 [  3.17312046e-04  -3.37427446e-05   2.14544216e-03]]

--
Ran 54 tests in 2.074s

FAILED (failures=1)
E: pybuild pybuild:276: test: plugin custom failed with: exit code=1: cd 
uncertainties; nosetests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
exit code 13
debian/rules:21: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:7: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This happens randomly. Sometimes it fails. Sometimes it does not.
But it's easy to trigger if the build is attempted enough times.

I attach three build logs in which this test failed.

Thanks.

uncertainties_2.4.4-1_amd64-20161107T023353Z.gz
Description: application/gzip


uncertainties_2.4.4-1_amd64-20161117T000107Z.gz
Description: application/gzip


uncertainties_2.4.4-1_amd64-20161117T000521Z.gz
Description: application/gzip

Bug#844571: uncertainties: FTBFS randomly (ERROR: Comparison between function derivatives and numerical derivatives)

[Santiago Vila]

Package: src:uncertainties
Version: 2.4.4-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
==
ERROR: Comparison between function derivatives and numerical derivatives.
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/<>/uncertainties/test_umath.py", line 40, in 
test_fixed_derivatives_math_funcs
test_uncertainties.compare_derivatives(func, numerical_derivatives)
  File "/<>/uncertainties/test_uncertainties.py", line 203, in 
compare_derivatives
fixed_deriv_value, num_deriv_value))
DerivativesDiffer: Derivative #0 of function 'cos' may be wrong: at args = 
[-0.00015531348313757576+/-0], value obtained = 0.0001553134825132, while 
numerical approximation = 0.0001439137242899.
 >> begin captured stdout << -
Testing acos at [0.3515705140294627+/-0], arg #0
Testing acosh at [1.21383500642085+/-0], arg #0
Testing asin at [0.2751865361039778+/-0], arg #0
Testing asinh at [1.848245081819893+/-0], arg #0
Testing atan at [0.5694583185549367+/-0], arg #0
Testing atan2 at [-0.4649913075928138+/-0, 0.396898674765+/-0], arg #0
Testing atan2 at [-0.4649913075928138+/-0, 0.396898674765+/-0], arg #1
Testing atanh at [0.02193641824821002+/-0], arg #0
Testing copysign at [-1.3339747776292108+/-0, 1.4083966105684347+/-0], arg #0
Testing copysign at [-1.3339747776292108+/-0, 1.4083966105684347+/-0], arg #1
Testing cos at [-0.00015531348313757576+/-0], arg #0

- >> end captured stdout << --

--
Ran 54 tests in 1.396s

FAILED (errors=1)
E: pybuild pybuild:276: test: plugin custom failed with: exit code=1: cd 
uncertainties; nosetests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
exit code 13
debian/rules:21: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:7: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This happens randomly. Sometimes it fails. Sometimes it does not.
But it's easy to trigger if the build is attempted enough times.

I attach two build logs in which this test failed.

Thanks.

uncertainties_2.4.4-1_amd64-20161112T050834Z.gz
Description: application/gzip


uncertainties_2.4.4-1_amd64-20161117T000619Z.gz
Description: application/gzip

Bug#841498: marked as done (rawtherapee: UI elements are displayed too big)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 00:19:31 +
with message-id 
and subject line Bug#841498: fixed in rawtherapee 4.2.1395-1
has caused the Debian Bug report #841498,
regarding rawtherapee: UI elements are displayed too big
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.)


-- 
841498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rawtherapee
Version: 4.2.1241-2
Severity: normal

Since the update to 4.2.1241 (thanks a lot for maintaining this package!) the 
UI is unusable. The elements of the top and right toolbar are very much 
enlarged, e.g. the name of the processing profiles is truncated by surrounding 
elements (see http://imgur.com/u2XAPHi). On a big screen this is annoying, but 
on a smaller screen it makes RT completely unusable. I also get the following 
output on the commandline:

(rawtherapee:6301): Gtk-WARNING **: Theme parsing error: 
RawTherapee.css:112:44: The style property 
GtkProgressBar:min-vertical-bar-width is deprecated and shouldn't be used 
anymore. It will be removed in a future version

(rawtherapee:6301): Gtk-WARNING **: Theme parsing error: 
RawTherapee.css:113:47: The style property 
GtkProgressBar:min-horizontal-bar-height is deprecated and shouldn't be used 
anymore. It will be removed in a future version

(rawtherapee:6301): Gtk-WARNING **: Theme parsing error: 
RawTherapee.css:175:20: The :insensitive pseudo-class is deprecated. Use 
:disabled instead.

(rawtherapee:6301): Gtk-WARNING **: Theme parsing error: 
RawTherapee.css:175:47: The :insensitive pseudo-class is deprecated. Use 
:disabled instead.

(rawtherapee:6301): Gtk-WARNING **: Theme parsing error: :1:16: Using 
Pango syntax for the font: style property is deprecated; please use CSS syntax
Error: ":1:10not a number"

I hope this is a configuration problem of my own or a packaging problem and not 
a design choice...

I use xfce as DE, in case it is relevant.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages rawtherapee depends on:
ii  libatkmm-1.6-1v52.24.2-2
ii  libbz2-1.0  1.0.6-8
ii  libc6   2.24-3
ii  libcairomm-1.0-1v5  1.12.0-1+b1
ii  libcanberra-gtk3-0  0.30-3
ii  libcanberra00.30-3
ii  libexpat1   2.2.0-1
ii  libfftw3-single33.3.5-1
ii  libgcc1 1:6.2.0-6
ii  libglib2.0-02.50.1-1
ii  libglibmm-2.4-1v5   2.50.0-1
ii  libgomp16.2.0-6
ii  libgtk-3-0  3.22.1-1
ii  libgtkmm-3.0-1v53.22.0-1
ii  libiptcdata01.0.4-4
ii  libjpeg62-turbo 1:1.5.0-1
ii  liblcms2-2  2.7-1
ii  libpangomm-1.4-1v5  2.40.1-3
ii  libpng16-16 1.6.25-2
ii  libsigc++-2.0-0v5   2.10.0-1
ii  libstdc++6  6.2.0-6
ii  libtiff54.0.6-2
ii  rawtherapee-data4.2.1241-2
ii  zlib1g  1:1.2.8.dfsg-2+b1

rawtherapee recommends no packages.

rawtherapee suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: rawtherapee
Source-Version: 4.2.1395-1

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

Debian distribution maintenance software
pp.
Philip Rinn  (supplier of updated rawtherapee 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, 16 Nov 2016 23:46:17 +0100
Source: rawtherapee
Binary: rawtherapee rawtherapee-data
Architecture: source
Version: 4.2.1395-1
Distribution: unstable
Urgency: medium
Maintainer: Philip Rinn 
Changed-By: Philip Rinn 
Description:
 rawtherapee - raw image converter and digital photo processor
 rawtherapee-data - raw image converter and 

Bug#842424: marked as done (rawtherapee: UI is too big. Tone curves are totally unusable.)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 00:19:31 +
with message-id 
and subject line Bug#841498: fixed in rawtherapee 4.2.1395-1
has caused the Debian Bug report #841498,
regarding rawtherapee: UI is too big. Tone curves are  totally unusable.
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.)


-- 
841498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rawtherapee
Version: 4.2.1241-2
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



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

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

Versions of packages rawtherapee depends on:
ii  libatkmm-1.6-1v52.24.2-2
ii  libbz2-1.0  1.0.6-8
ii  libc6   2.24-5
ii  libcairomm-1.0-1v5  1.12.0-1+b1
ii  libcanberra-gtk3-0  0.30-3
ii  libcanberra00.30-3
ii  libexpat1   2.2.0-1
ii  libfftw3-single33.3.5-1
ii  libgcc1 1:6.2.0-10
ii  libglib2.0-02.50.1-1
ii  libglibmm-2.4-1v5   2.50.0-1
ii  libgomp16.2.0-10
ii  libgtk-3-0  3.22.2-1
ii  libgtkmm-3.0-1v53.22.0-1
ii  libiptcdata01.0.4-6
ii  libjpeg62-turbo 1:1.5.1-2
ii  liblcms2-2  2.7-1
ii  libpangomm-1.4-1v5  2.40.1-3
ii  libpng16-16 1.6.26-1
ii  libsigc++-2.0-0v5   2.10.0-1
ii  libstdc++6  6.2.0-10
ii  libtiff54.0.6-2
ii  rawtherapee-data4.2.1241-2
ii  zlib1g  1:1.2.8.dfsg-2+b1

rawtherapee recommends no packages.

rawtherapee suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: rawtherapee
Source-Version: 4.2.1395-1

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

Debian distribution maintenance software
pp.
Philip Rinn  (supplier of updated rawtherapee 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, 16 Nov 2016 23:46:17 +0100
Source: rawtherapee
Binary: rawtherapee rawtherapee-data
Architecture: source
Version: 4.2.1395-1
Distribution: unstable
Urgency: medium
Maintainer: Philip Rinn 
Changed-By: Philip Rinn 
Description:
 rawtherapee - raw image converter and digital photo processor
 rawtherapee-data - raw image converter and digital photo processor (data files)
Closes: 841498
Changes:
 rawtherapee (4.2.1395-1) unstable; urgency=medium
 .
   * New upstream snapshot (closes: #841498).
   * Remove patch patch/01-fix-overflow-in-dcraw.patch:
 - It's applied upstream
   * Bump debhelper compat from 9 to 10 (no changes necessary).
   * Make build reproducible on i386.
Checksums-Sha1:
 89905fbe5685dd9645d187d4e5c4af796e6d8e8f 2189 rawtherapee_4.2.1395-1.dsc
 d7a138ce09411ec05940db1cf1ec29c905d2c020 10105692 
rawtherapee_4.2.1395.orig.tar.xz
 09947a847a6623a0042a6db76871784bf4e96145 7764 
rawtherapee_4.2.1395-1.debian.tar.xz
Checksums-Sha256:
 5de4c38573c56f2772a2762b633527605195fe3574f516e9db3644af65a803e9 2189 
rawtherapee_4.2.1395-1.dsc
 fc754c7ed72340a65a6b8ac83bf366f861610405681255120c03e0e0acef3481 10105692 
rawtherapee_4.2.1395.orig.tar.xz
 bacdca83338853d12dc46d0ba55e5ff6e2faf865462d8ec6252db9ca28f7771d 7764 
rawtherapee_4.2.1395-1.debian.tar.xz
Files:
 a960f6b80f4ba4607f516705bcf2e6f1 2189 graphics optional 
rawtherapee_4.2.1395-1.dsc
 96b5a988c554d7e07510bda124d17d66 10105692 graphics optional 
rawtherapee_4.2.1395.orig.tar.xz
 3b79eb9b570df1ae029d9f3915208737 

Bug#839666: marked as done (Fails to disable uwsgi module upon purge)

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 23:51:53 +
with message-id 
and subject line Bug#839666: fixed in uwsgi 2.0.14+20161106-1
has caused the Debian Bug report #839666,
regarding Fails to disable uwsgi module upon purge
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.)


-- 
839666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-uwsgi
Version: 2.0.12-7
Severity: critical
File: /etc/apache2/mods-available/uwsgi.load
Justification: breaks unrelated software

libapache2-mod-uwsgi provides /etc/apache2/mods-available/proxy_uwsgi.load
and /usr/lib/apache2/modules/mod_proxy_uwsgi.so and enables the module in
the postinst:
apache2_invoke enmod @@module_name@@  || exit 1
https://sources.debian.net/src/uwsgi/2.0.12-7/debian/libapache2-mod-__MODULE__.postinst.in/

However, 
https://sources.debian.net/src/uwsgi/2.0.12-7/debian/libapache2-mod-__MODULE__.prerm.in/
 seems to fail to dismod on purge:

Original log is from jessie:

$ sudo apt --purge remove  libapache2-mod-uwsgi libapache2-mod-wsgi
Removing libapache2-mod-uwsgi (2.0.7-1) ...
Purging configuration files for libapache2-mod-uwsgi (2.0.7-1) ...
Removing libapache2-mod-wsgi (4.3.0-1) ...
ERROR: Can't open /etc/apache2/mods-enabled/uwsgi.load: No such file or 
directoryModule wsgi disabled.
apache2_invoke prerm: Disable module wsgi
apache2_reload: Your configuration is broken. Not restarting Apache 2
apache2_reload: apache2: Syntax error on line 140 of /etc/apache2/apache2.conf: 
Could not open configuration file /etc/apache2/mods-enabled/uwsgi.load: No such 
file or directory
Purging configuration files for libapache2-mod-wsgi (4.3.0-1) ...
apache2_invoke postrm: Purging state for wsgi

Not restarting Apache on a server which is providing multiple hosts is
very bad, especially as apt|dpkg exits cleanly. Unless the admin is
watching the purge output directly, the reason for the server going
offline would not be obvious.

Once the problem is spotted:
$ sudo a2dismod uwsgi
$ sudo apache2ctl restart

... does allow apache to restart successfully.

Reproduced in a sid VM:
$ sudo apt install libapache2-mod-uwsgi libapache2-mod-wsgi

$ sudo apache2ctl -M|grep wsgi
AH00558: apache2: Could not reliably determine the server's fully qualified 
domain name, using 127.0.1.1. Set the 'ServerName' directive globally to 
suppress this message
 uwsgi_module (shared)
 wsgi_module (shared)
neil@debian-sid:~$ sudo apt --purge remove libapache2-mod-uwsgi 
libapache2-mod-wsgi
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libjansson4 libmatheval1 libpython2.7 libsodium18 libyaml-0-2 libzmq5
  uwsgi-core
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  libapache2-mod-uwsgi* libapache2-mod-wsgi*
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 342 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 46879 files and directories currently installed.)
Removing libapache2-mod-uwsgi (2.0.12-7) ...
Removing libapache2-mod-wsgi (4.5.7-1) ...
Module wsgi disabled.
apache2_invoke prerm: Disable module wsgi
apache2_reload: Your configuration is broken. Not restarting Apache 2
apache2_reload: apache2: Syntax error on line 140 of /etc/apache2/apache2.conf: 
Syntax error on line 1 of /etc/apache2/mods-enabled/uwsgi.load: Cannot load 
/usr/lib/apache2/modules/mod_uwsgi.so into server: 
/usr/lib/apache2/modules/mod_uwsgi.so: cannot open shared object file: No such 
file or directory
(Reading database ... 46865 files and directories currently installed.)
Removing libapache2-mod-wsgi (4.5.7-1) ...
Purging configuration files for libapache2-mod-wsgi (4.5.7-1) ...
apache2_invoke postrm: Purging state for wsgi
Removing libapache2-mod-uwsgi (2.0.12-7) ...
Purging configuration files for libapache2-mod-uwsgi (2.0.12-7) ...


$ sudo service apache2 restart
Job for apache2.service failed because the control process exited with error 
code.
See "systemctl status apache2.service" and "journalctl -xe" for details.
$ sudo service apache2 status
● apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: 
enabled)
   Active: failed (Result: exit-code) since Mon 2016-10-03 17:22:08 BST; 3s ago
  Process: 27997 ExecStop=/usr/sbin/apachectl stop (code=exited, 
status=1/FAILURE)
  Process: 28004 

Bug#828785: marked as done (uwsgi: FTBFS in testing (uwsgiconfig.py: Command not found))

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 23:51:53 +
with message-id 
and subject line Bug#828785: fixed in uwsgi 2.0.14+20161106-1
has caused the Debian Bug report #828785,
regarding uwsgi: FTBFS in testing (uwsgiconfig.py: Command not found)
to be marked as done.

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

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


-- 
828785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:uwsgi
Version: 2.0.12-7
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Severity: serious

Hello Jonas.

This package currently fails to build in stretch:


[...]
test -x debian/rules
rm -f debian/copyright_newhints
rm -f debian/cdbs-install-list debian/cdbs-package-list 
debian/stamp-copyright-check
rm -rf "debian/upstream-cruft"
rm -f debian/stamp-upstream-cruft
dh_clean 
uwsgiconfig.py -v --clean
make: uwsgiconfig.py: Command not found
debian/rules:335: recipe for target 'clean' failed
make: *** [clean] Error 127
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2


You can find a full build log here:

https://tests.reproducible-builds.org/debian/rbuild/testing/amd64/uwsgi_2.0.12-7.rbuild.log

Note: Maybe you need a versioned Build-Depends somewhere? (for a
build-dependency which did not enter testing yet).

It is a known fact that Britney does not currently take build-depends
in account for the unstable to testing migration, only ordinary
depends, but even in such case, a package in testing should not fail
in this way. It should better fail in the "Build-depends may not be met"
way.

Thanks.
--- End Message ---
--- Begin Message ---
Source: uwsgi
Source-Version: 2.0.14+20161106-1

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated uwsgi 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, 16 Nov 2016 23:45:42 +0100
Source: uwsgi
Binary: uwsgi uwsgi-dbg uwsgi-src uwsgi-core uwsgi-emperor uwsgi-plugins-all 
uwsgi-infrastructure-plugins uwsgi-app-integration-plugins 
uwsgi-mongodb-plugins uwsgi-plugin-alarm-curl uwsgi-plugin-alarm-xmpp 
uwsgi-plugin-curl-cron uwsgi-plugin-emperor-pg uwsgi-plugin-glusterfs 
uwsgi-plugin-rados uwsgi-plugin-rbthreads uwsgi-plugin-fiber uwsgi-plugin-geoip 
uwsgi-plugin-graylog2 uwsgi-plugin-gevent-python uwsgi-plugin-greenlet-python 
uwsgi-plugin-asyncio-python uwsgi-plugin-asyncio-python3 
uwsgi-plugin-tornado-python uwsgi-plugin-gccgo uwsgi-plugin-jvm-openjdk-8 
uwsgi-plugin-jwsgi-openjdk-8 uwsgi-plugin-ring-openjdk-8 
uwsgi-plugin-servlet-openjdk-8 uwsgi-plugin-ldap uwsgi-plugin-lua5.1 
uwsgi-plugin-lua5.2 uwsgi-plugin-luajit uwsgi-plugin-mono uwsgi-plugin-psgi 
uwsgi-plugin-python uwsgi-plugin-python3 uwsgi-plugin-rack-ruby2.3 
uwsgi-plugin-router-access uwsgi-plugin-sqlite3 uwsgi-plugin-v8 
uwsgi-plugin-xslt libapache2-mod-proxy-uwsgi libapache2-mod-proxy-uwsgi-dbg
 libapache2-mod-uwsgi libapache2-mod-uwsgi-dbg libapache2-mod-ruwsgi 
libapache2-mod-ruwsgi-dbg python-uwsgidecorators python3-uwsgidecorators
 uwsgi-extra
Architecture: source amd64 all
Version: 2.0.14+20161106-1
Distribution: unstable
Urgency: medium
Maintainer: uWSGI packaging team 
Changed-By: Jonas Smedegaard 
Description:
 libapache2-mod-proxy-uwsgi - uwsgi proxy module for Apache2 (mod_uwsgi)
 libapache2-mod-proxy-uwsgi-dbg - debugging symbols for Apache2 mod_proxy_uwsgi
 libapache2-mod-ruwsgi - uwsgi module for Apache2 (mod_Ruwsgi)
 libapache2-mod-ruwsgi-dbg - debugging symbols for Apache2 mod_Ruwsgi
 libapache2-mod-uwsgi - uwsgi module for Apache2 (mod_uwsgi)
 libapache2-mod-uwsgi-dbg - debugging symbols for Apache2 mod_uwsgi
 python-uwsgidecorators - module of decorators for elegant access to uWSGI API 

Bug#833055: marked as done (uwsgi: B-D mongodb-dev is no longer built by mongodb)

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 23:51:53 +
with message-id 
and subject line Bug#833055: fixed in uwsgi 2.0.14+20161106-1
has caused the Debian Bug report #833055,
regarding uwsgi: B-D mongodb-dev is no longer built by mongodb
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.)


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

Hi,

uwsgi has Build-Depends: mongodb-dev, but that package is no longer built:

mongodb (1:2.6.11-1) experimental; urgency=medium
...
  * d/control:
+ Drop the mongodb-dev binary package. The C++ client library is now
  developed separately from the mongo database server.
...
 -- Apollon Oikonomopoulos   Tue, 15 Mar 2016 14:32:18 +

Please switch to a suitable alternative (there are several mongodb
client library packages available).


Andreas
--- End Message ---
--- Begin Message ---
Source: uwsgi
Source-Version: 2.0.14+20161106-1

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated uwsgi 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, 16 Nov 2016 23:45:42 +0100
Source: uwsgi
Binary: uwsgi uwsgi-dbg uwsgi-src uwsgi-core uwsgi-emperor uwsgi-plugins-all 
uwsgi-infrastructure-plugins uwsgi-app-integration-plugins 
uwsgi-mongodb-plugins uwsgi-plugin-alarm-curl uwsgi-plugin-alarm-xmpp 
uwsgi-plugin-curl-cron uwsgi-plugin-emperor-pg uwsgi-plugin-glusterfs 
uwsgi-plugin-rados uwsgi-plugin-rbthreads uwsgi-plugin-fiber uwsgi-plugin-geoip 
uwsgi-plugin-graylog2 uwsgi-plugin-gevent-python uwsgi-plugin-greenlet-python 
uwsgi-plugin-asyncio-python uwsgi-plugin-asyncio-python3 
uwsgi-plugin-tornado-python uwsgi-plugin-gccgo uwsgi-plugin-jvm-openjdk-8 
uwsgi-plugin-jwsgi-openjdk-8 uwsgi-plugin-ring-openjdk-8 
uwsgi-plugin-servlet-openjdk-8 uwsgi-plugin-ldap uwsgi-plugin-lua5.1 
uwsgi-plugin-lua5.2 uwsgi-plugin-luajit uwsgi-plugin-mono uwsgi-plugin-psgi 
uwsgi-plugin-python uwsgi-plugin-python3 uwsgi-plugin-rack-ruby2.3 
uwsgi-plugin-router-access uwsgi-plugin-sqlite3 uwsgi-plugin-v8 
uwsgi-plugin-xslt libapache2-mod-proxy-uwsgi libapache2-mod-proxy-uwsgi-dbg
 libapache2-mod-uwsgi libapache2-mod-uwsgi-dbg libapache2-mod-ruwsgi 
libapache2-mod-ruwsgi-dbg python-uwsgidecorators python3-uwsgidecorators
 uwsgi-extra
Architecture: source amd64 all
Version: 2.0.14+20161106-1
Distribution: unstable
Urgency: medium
Maintainer: uWSGI packaging team 
Changed-By: Jonas Smedegaard 
Description:
 libapache2-mod-proxy-uwsgi - uwsgi proxy module for Apache2 (mod_uwsgi)
 libapache2-mod-proxy-uwsgi-dbg - debugging symbols for Apache2 mod_proxy_uwsgi
 libapache2-mod-ruwsgi - uwsgi module for Apache2 (mod_Ruwsgi)
 libapache2-mod-ruwsgi-dbg - debugging symbols for Apache2 mod_Ruwsgi
 libapache2-mod-uwsgi - uwsgi module for Apache2 (mod_uwsgi)
 libapache2-mod-uwsgi-dbg - debugging symbols for Apache2 mod_uwsgi
 python-uwsgidecorators - module of decorators for elegant access to uWSGI API 
(Python 2)
 python3-uwsgidecorators - module of decorators for elegant access to uWSGI API 
(Python 3)
 uwsgi  - fast, self-healing application container server
 uwsgi-app-integration-plugins - plugins for integration of uWSGI and 
application
 uwsgi-core - fast, self-healing application container server (core)
 uwsgi-dbg  - debugging symbols for uWSGI server and it's plugins
 uwsgi-emperor - fast, self-healing application container server (emperor 
scripts)
 uwsgi-extra - fast, self-healing application container server (extra files)
 uwsgi-infrastructure-plugins - infrastructure plugins for uWSGI
 uwsgi-mongodb-plugins - MongoDB/GridFS plugins for uWSGI
 uwsgi-plugin-alarm-curl - cURL alarm plugin for uWSGI
 

Bug#843405: marked as done (haskell-intern: needs sourceful upload)

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 23:48:58 +
with message-id 
and subject line Bug#843405: fixed in haskell-intern 0.9.1.4-2
has caused the Debian Bug report #843405,
regarding haskell-intern: needs sourceful upload
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.)


-- 
843405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-intern
Version: 0.9.1.4-1
Severity: serious

libghc-intern-doc needs to be rebuilt with ghc 8 so it can become
installable.
--- End Message ---
--- Begin Message ---
Source: haskell-intern
Source-Version: 0.9.1.4-2

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated haskell-intern 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, 17 Nov 2016 00:24:53 +0100
Source: haskell-intern
Binary: libghc-intern-dev libghc-intern-doc libghc-intern-prof
Architecture: source
Version: 0.9.1.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Jonas Smedegaard 
Description:
 libghc-intern-dev - hash consing for data types - libraries
 libghc-intern-doc - hash consing for data types - library documentation
 libghc-intern-prof - hash consing for data types - profiling libraries
Closes: 843405
Changes:
 haskell-intern (0.9.1.4-2) unstable; urgency=medium
 .
   * Declare compliance with Debian Policy 3.9.8.
   * Update copyright info: Extend coverage of packaging to include this
 year.
   * Relax inclusion of hlibrary.mk, to ease bootstrap of build (i.e. not
 need to install Haskell development environment outside build
 chroot).
   * Modernize CDBS setup: Build-depend on licensecheck (not devscripts).
   * Simply doing this rebuild implies rebuilding against ghc 8.
 Closes: Bug#843405. Thanks to Clint Adams.
Checksums-Sha1:
 463fc4762c70884ab71604edc9968c195df0a249 2429 haskell-intern_0.9.1.4-2.dsc
 553c46c7e2773798aa4dd846c1935485f98fb46d 4204 
haskell-intern_0.9.1.4-2.debian.tar.xz
Checksums-Sha256:
 8d9de2142c69c3eb55b20cc6e512a6e1da46c71b706a40180f2abcb1f36e33d4 2429 
haskell-intern_0.9.1.4-2.dsc
 c3ba79903feb1441797be83c31fbbfa564c8ade0e7847a89eaba10aca2edfe71 4204 
haskell-intern_0.9.1.4-2.debian.tar.xz
Files:
 61e4b67aee210f0cd3622bee1e17b1d0 2429 haskell optional 
haskell-intern_0.9.1.4-2.dsc
 948a8f28c41ffb35f060857a338f03f0 4204 haskell optional 
haskell-intern_0.9.1.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYLO+CAAoJECx8MUbBoAEhLkcP/0gb+0yLV3CDUPmOxpOLppLo
Ln704hP49W0gZycxXMW2b6xi1yv/aM5yKbwshO0JL5MHIFNJiio7Ew/sr5Rye69N
AmUAn4CIJ4S41S4i6AKdMxqKvUvF09k9DiVDPO3SlXdlI18gyjVObGfwex/kFKLr
SVetn7jwT+xCVFHQBBfDidcyXmAqkC7wFUYMqSFjk6l7+RC+G2jjwDhFrrtAoWg6
RnRPR7x7UuelVo0gdEbclIbvGHUwVnwYW5bpjcj3VZK5BaguiZOt3YhzmCA88KpY
bV0c5nkAjv2OaF2Hm9vzH/hu2HtBU8UgJhZ25xibWs18IkOkkNLO/hdZZgUJ32ht
7E+ejwPKo2u6nR7Fvb5S5SxqsdyM4xwF1G0hJms04Sk4T+pO6M90wsq22v7TXNFB
5DDjhXJ/YdsObVpMlnvzS0439s94Av80tCR2QZjq2Il84GMpjyx0+6pI1nRzN1Y2
Ach4D0MnzAvsdURUlFx0NkjOUEi1IMhIP4Hfxn9gmbX4src4g2VHK8YPorjKZr5Q
fG0cJKFY6nFGKdEGVtPgj0yMKWiZveiPkdl3yIyxm9J2IU54fvayv8OLm0TAMQDM
N1JpfX4g968mbBFJ8JHgnQ7JqgQ4/Ap9rZQHPHsgPkLpHd3qY87hq8nlEzgcnghi
q4T/jsJqvqVLnTn2mZtV
=qDvN
-END PGP SIGNATURE End Message ---

Processed: tagging 844549

[Debian Bug Tracking System]

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

> tags 844549 + pending
Bug #844549 [rootskel] network-console broken: no screen to be resumed matching 
sh
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#844549: network-console broken: no screen to be resumed matching sh

[Martin Michlmayr]

* Samuel Thibault  [2016-11-16 23:03]:
> But AIUI the intent was to have screen in ssh connections too.

I'm not sure what the intent was.  I assume you're right because Roger
didn't exclude screen from the network-console images.  Personally,
I'm not sure I see the point of screen in that case because you can
always open a second SSH connection and open a terminal, but I don't
have strong feelings either way if there's an advantage of having
screen in such cases.

> I'm also thinking that we perhaps want to add -x when resuming a
> session, so that somebody can connect trough ssh several times ?

Yes because right now I get this when I open a 2nd connection:

debug1: Sending env LC_COLLATE = C
There is a screen on:
1356.network(11/16/16 23:24:12) (Attached)

Apart from this, the patch works for me.

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#843393: marked as done (FTBFS when building architecture-independent packages only)

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 23:04:01 +
with message-id 
and subject line Bug#843393: fixed in git 1:2.10.2-3
has caused the Debian Bug report #843393,
regarding FTBFS when building architecture-independent packages only
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.)


-- 
843393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: git
Version: 1:2.10.2-2

Hi,

git fails to build from source when building architecture-indepedent
packages only because the newly introduced diffing of the license files
errors (the license files do not exist yet when building arch-indep only).

I'll send a reference to my git commit fixing it after having received
the bug number.

Regards,
Daniel
--- End Message ---
--- Begin Message ---
Source: git
Source-Version: 1:2.10.2-3

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

Debian distribution maintenance software
pp.
Anders Kaseorg  (supplier of updated git 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: SHA1

Format: 1.8
Date: Wed, 16 Nov 2016 16:12:02 -0500
Source: git
Binary: git git-man git-core git-doc git-arch git-cvs git-svn git-mediawiki 
git-email git-daemon-run git-daemon-sysvinit git-gui gitk git-el gitweb git-all
Architecture: source all amd64
Version: 1:2.10.2-3
Distribution: unstable
Urgency: medium
Maintainer: Gerrit Pape 
Changed-By: Anders Kaseorg 
Description:
 git- fast, scalable, distributed revision control system
 git-all- fast, scalable, distributed revision control system (all subpacka
 git-arch   - fast, scalable, distributed revision control system (arch interop
 git-core   - fast, scalable, distributed revision control system (obsolete)
 git-cvs- fast, scalable, distributed revision control system (cvs interope
 git-daemon-run - fast, scalable, distributed revision control system 
(git-daemon s
 git-daemon-sysvinit - fast, scalable, distributed revision control system 
(git-daemon s
 git-doc- fast, scalable, distributed revision control system (documentatio
 git-el - fast, scalable, distributed revision control system (emacs suppor
 git-email  - fast, scalable, distributed revision control system (email add-on
 git-gui- fast, scalable, distributed revision control system (GUI)
 git-man- fast, scalable, distributed revision control system (manual pages
 git-mediawiki - fast, scalable, distributed revision control system (MediaWiki 
re
 git-svn- fast, scalable, distributed revision control system (svn interope
 gitk   - fast, scalable, distributed revision control system (revision tre
 gitweb - fast, scalable, distributed revision control system (web interfac
Closes: 843393
Changes:
 git (1:2.10.2-3) unstable; urgency=medium
 .
   * debian/rules: Split override_dh_installdocs into -arch and -indep
 parts.  (Closes: #843393)
Checksums-Sha1:
 712a5a7564f09727bb08538aefaa2bfc7b48f739 2855 git_2.10.2-3.dsc
 2023975ae0061bd569b8529025428e3eca53be2e 4106108 git_2.10.2.orig.tar.xz
 eeb6f638eb5811a08a71658cb2e1abb620a6c233 511884 git_2.10.2-3.debian.tar.xz
 9daed73ff81cc6fe422b947b50d3c529b80934ce 662076 git-all_2.10.2-3_all.deb
 0cd26569b171fac47e765472f03c6bf137c88f2f 675502 git-arch_2.10.2-3_all.deb
 2cdfb6dc570d8394f5a326867a708247fdb06b72 1406 git-core_2.10.2-3_all.deb
 ca49eb95f0233455ed27736b408e014a8ea0a93e 725150 git-cvs_2.10.2-3_all.deb
 3c42c00d188ef7471bf67ae6f2de92883ad4592e 663586 git-daemon-run_2.10.2-3_all.deb
 d0dcbca276fe8fdaeddc448b3f4caa9f4830fc12 664786 
git-daemon-sysvinit_2.10.2-3_all.deb
 a9c973fac8244ff832d7e759dba1b36982b5c99d 29371820 git-dbgsym_2.10.2-3_amd64.deb
 9bf3d7230c949511164d0b7c523269299cdea370 1517644 git-doc_2.10.2-3_all.deb
 965936c868171ca052526aa7a0baf10017a9ae59 681664 git-el_2.10.2-3_all.deb
 0c74ade1e4d2887b83745fc7300e371b07a22667 683856 git-email_2.10.2-3_all.deb
 a79ca6c0187b2cb4283594ef42237f19632082f9 863646 git-gui_2.10.2-3_all.deb
 

Bug#821974: comgt: Build arch:all+arch:any but is missing build-{arch,indep} targets

[Andreas "Jimmy" Gredler]

On 11/11/2016 03:31 PM, Christoph Biedl wrote:
> Andreas "Jimmy" Gredler wrote...
> 
>> Thank you for the patch. I will review the package to see if I can
>> change it to dh-* in time or if it would be better to upload it with the
>> patch only.
> 
> Any progress on this? comgt has fallen out of testing in the meantime,
> I was glad if it could return in due course.

Hi,

The package is almost done but I'm also reviewing if the patches
mentioned in the other reports should be included or go to upstream.

Best,
Jimmy

Bug#844043: marked as done (git: FTBFS when built with dpkg-buildpackage -A (No such file or directory))

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 23:04:01 +
with message-id 
and subject line Bug#843393: fixed in git 1:2.10.2-3
has caused the Debian Bug report #843393,
regarding git: FTBFS when built with dpkg-buildpackage -A (No such file or 
directory)
to be marked as done.

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

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


-- 
843393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:git
Version: 1:2.10.2-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with apache2
   dh_testdir -i
   dh_update_autotools_config -i
   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>'
gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.2.0-10' 
--with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs 
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared 
--enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext 
--enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ 
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie 
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk 
--enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre 
--enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64 
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--enable-objc-g
 c --enable-multiarch --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix

[... snipped ...]

make[2]: Leaving directory '/<>/contrib/subtree'
make[2]: Entering directory '/<>/contrib/subtree'
xmlto -m ../../Documentation/manpage-normal.xsl man git-subtree.xml
make[2]: Leaving directory '/<>/contrib/subtree'
make[2]: Entering directory '/<>/contrib/subtree'
install -d -m 755 /<>/debian/tmp/usr/share/man/man1
install -m 644 git-subtree.1 /<>/debian/tmp/usr/share/man/man1
make[2]: Leaving directory '/<>/contrib/subtree'
make[2]: Entering directory '/<>/contrib/subtree'
asciidoc -b xhtml11 -d manpage -f ../../Documentation/asciidoc.conf \
-agit_version=2.10.2 git-subtree.txt
make[2]: Leaving directory '/<>/contrib/subtree'
make[2]: Entering directory '/<>/contrib/subtree'
install -d -m 755 /<>/debian/tmp/usr/share/doc/git/html
install -m 644 git-subtree.html 
/<>/debian/tmp/usr/share/doc/git/html
make[2]: Leaving directory '/<>/contrib/subtree'
make[1]: Entering directory '/<>'
install -m 0644 contrib/subtree/git-subtree.txt 
'/<>/debian/tmp'/html
# RelNotes are shipped in git
rm -rf '/<>/debian/tmp'/html/RelNotes
# don't include git-p4 man page
rm -f '/<>/debian/tmp'/html/git-p4.*
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install-indep
make[1]: Entering directory '/<>'
dh_install --indep
for i in git-archimport git-cvs git-p4 git-svn git-send-email gitk \
 git-gui git-citool; do \
  rm -f '/<>/debian/git'-man/usr/share/man/man1/$i*; \
done
rm -f '/<>/debian/git'-man/usr/share/man/man3/Git::SVN*.3pm
make[1]: Leaving directory '/<>'
   dh_apache2 -i
   debian/rules override_dh_installdocs
make[1]: Entering directory '/<>'
install -d -m0755 '/<>/debian/git'-core/usr/share/doc
ln -s git '/<>/debian/git'-core/usr/share/doc/git-core
dh_installdocs -X.gitignore
# These licenses are replaced with symlinks in git.links.
diff -q 
'/<>/debian/git'/usr/share/doc/git/contrib/persistent-https/LICENSE
 /usr/share/common-licenses/Apache-2.0
diff: 
/<>/debian/git/usr/share/doc/git/contrib/persistent-https/LICENSE: 
No such file or directory
debian/rules:126: recipe for target 'override_dh_installdocs' failed
make[1]: *** [override_dh_installdocs] Error 2
make[1]: Leaving directory '/<>'
debian/rules:41: recipe for target 'binary-indep' failed
make: *** 

Bug#844160: Bug#828236: [Pkg-openssl-devel] Bug#844160: openssl 1.1 and apache2

[Adrian Bunk]

On Wed, Nov 16, 2016 at 11:05:13PM +0100, Stefan Fritsch wrote:
>...
> BTW, I am pretty sure that support for enhanced master secret and chacha20 
> will appear for openssl 1.0.2 before the release of stretch+1, if only 
> because 
> redhat needs it for its long support cycles. Back-porting that to stretch in 
> a 
> year or so in a stable-point-release would IMHO be the best option.

At least for ChaCha20 there are patches available for OpenSSL 1.0.2 that 
are already being used elsewhere.

> When 
> Apache httpd 2.4 came out, I was also quite disappointed that it could not be 
> included in squeeze, but mod_perl was not ready at the time and it would not 
> have made any sense to include an inofficial forward-port of mod_perl to 2.4 
> in 
> Debian. In the same way, I don't think it is a good idea to include lots of 
> patches for openssl 1.1, with little testing.
> 
> Cheers,
> Stefan

cu
Adrian

-- 

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

Processed: block 844515

[Debian Bug Tracking System]

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

> block 844515 by 844258
Bug #844515 [packer] packer: FTBFS on s390x (go install -v -p 1 died with 
signal 4)
844515 was not blocked by any bugs.
844515 was not blocking any bugs.
Added blocking bug(s) of 844515: 844258
> thanks
Stopping processing here.

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

Bug#844515: [pkg-go] Bug#844515: packer: FTBFS on s390x (go install -v -p 1 died with signal 4)

[Daniel Stender]

... found it, #844258 (golang-go: go SIGILL on s390x)

True, zemlinsky (builder) is z10, zelenka (porterbox) z13.

Thanks for the hint,
DS

On 16.11.2016 20:05, Michael Hudson-Doyle wrote:
> This is the "golang for s390x only works on z196+, not z10" thing. The
> right fix is probably to not build golang on Debian, sadly.
> 
> On 17 November 2016 at 01:40, Daniel Stender 
> wrote:
> 
>> Package: packer
>> Version: 0.10.1+dfsg-1
>> Severity: serious
>> Justification: fails to build from source (but built successfully in the
>> past)
>>
>> Packer currently (recently 0.10.2+dfsg-1) fails to build on s390x:
>>
>> 
>>dh_auto_build -O--buildsystem=golang
>> cd obj-s390x-linux-gnu
>> go install -v -p 1
>> dh_auto_build: go install -v -p 1 died with signal 4
>> cd /<>/packer-0.10.2+dfsg
>> debian/rules:6: recipe for target 'build' failed
>> make: *** [build] Error 255
>> dpkg-buildpackage: error: debian/rules build gave error exit status 2
>> 
>>
>> This is a regression from 0.10.1+dfsg-1 [1] (the build on 2016-10-16 [2]
>> failed
>> for a dependency reason which is solved in the meanwhile, see #841605 [3]).
>>
>> [1] https://buildd.debian.org/status/logs.php?pkg=packer=s390x
>>
>> [2] https://buildd.debian.org/status/fetch.php?pkg=packer;
>> arch=s390x=0.10.1%2Bdfsg-1=1476596269
>>
>> [3] https://bugs.debian.org/841605 (packer: FTBFS: src/
>> github.com/Azure/go-autorest/autorest/azure/token.go:140: undefined:
>> jwt.MapClaims)
>>
>> I can reproduce this locally in a qemu-chroot for Sbuild, however a test
>> build on
>> the zelenka porterbox succeeded:
>>
>> 
>> {...}
>> dpkg-deb: building package 'golang-github-mitchellh-packer-dev' in
>> '../golang-github-mitchellh-packer-dev_0.10.2+dfsg-1_all.deb'.
>> dpkg-deb: building package 'packer' in '../packer_0.10.2+dfsg-1_
>> s390x.deb'.
>>  dpkg-genbuildinfo
>> dpkg-genbuildinfo: warning: File::FcntlLock not available; using flock
>> which is not NFS-safe
>>  dpkg-genchanges  >../packer_0.10.2+dfsg-1_s390x.changes
>> dpkg-genchanges: info: including full source code in upload
>>  dpkg-source --after-build packer-0.10.2+dfsg
>> dpkg-buildpackage: info: full upload (original source is included)
>> (sid_s390x-dchroot)stender@zelenka:~/sandbox/packer-0.10.2+dfsg$
>> 
>>
>> Thanks for hints,
>> DS
>>
>> -- System Information:
>> Debian Release: stretch/sid
>>   APT prefers testing
>>   APT policy: (500, 'testing'), (1, 'experimental')
>> Architecture: amd64 (x86_64)
>>
>> Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
>> Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>> Init: systemd (via /run/systemd/system)
>>
>> Versions of packages packer depends on:
>> ii  libc6  2.24-5
>>
>> Versions of packages packer recommends:
>> pn  docker.io  
>> ii  qemu   1:2.7+dfsg-3+b1
>>
>> Versions of packages packer suggests:
>> ii  ansible  2.1.1.0-1
>> pn  chef 
>>
>> -- no debconf information
>>
>> ___
>> Pkg-go-maintainers mailing list
>> pkg-go-maintain...@lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>>
> 


-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/

Bug#817478: marked as done (gkrellshoot: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 22:24:01 +
with message-id 
and subject line Bug#817478: fixed in gkrellshoot 0.4.4-2
has caused the Debian Bug report #817478,
regarding gkrellshoot: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gkrellshoot
Severity: important
Usertags: compat-4-removal

Hi,

The package gkrellshoot uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: gkrellshoot
Source-Version: 0.4.4-2

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

Debian distribution maintenance software
pp.
Andreas "Jimmy" Gredler  (supplier of updated gkrellshoot 
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: Sun, 13 Nov 2016 18:55:43 -0800
Source: gkrellshoot
Binary: gkrellshoot
Architecture: source amd64
Version: 0.4.4-2
Distribution: unstable
Urgency: medium
Maintainer: Andreas "Jimmy" Gredler 
Changed-By: Andreas "Jimmy" Gredler 
Description:
 gkrellshoot - Plugin for gkrellm to lock the screen and make screenshots
Closes: 817478
Changes:
 gkrellshoot (0.4.4-2) unstable; urgency=medium
 .
   * Changed maintainer's email address.
   * Bumped debhelper compat to 9 (Closes: #817478).
   * Enabled Debian hardening options.
   * Rewrote debian/rules to use the newer simpler format.
   * Changed Makefile to use DESTDIR variable.
   * Updated watch file to use the new format for SourceForge.
   * Bumped standards version to 3.9.8.
   * Switched to quilt 3.0 format.
Checksums-Sha1:
 8827edb4f1bc4c3bd6562fce119df3ba1558ab2f 1730 gkrellshoot_0.4.4-2.dsc
 a4d2b31585e64c4a9e8cb3bd638856ebbc471f7b 2592 gkrellshoot_0.4.4-2.debian.tar.xz
 fa0bdc86d946298235454593d33b83bccfdd0979 8975 
gkrellshoot_0.4.4-2_20161116T220613z-25ece6de.buildinfo
 3fae43adbdc098ecd5462d73e13e439dd0974d73 22586 gkrellshoot_0.4.4-2_amd64.deb
Checksums-Sha256:
 db3e7269e19e21b93ce134bc42fbd887fea8ebd4f317d9c4e7b8506bfd3f2c97 1730 
gkrellshoot_0.4.4-2.dsc
 c8da23e72e86128e3328b0da269f10f3e7f8503b26bb254112cacff92f145988 2592 
gkrellshoot_0.4.4-2.debian.tar.xz
 3cc0fe25dca10fb3fea09b1ecd8b8e06da884cc093a361517357fddcf53f1db3 8975 
gkrellshoot_0.4.4-2_20161116T220613z-25ece6de.buildinfo
 7ea752c9566e1012b0cc44004fe4f930fd1faa94013e198cf1d77d74c978d18b 22586 
gkrellshoot_0.4.4-2_amd64.deb
Files:
 a984cfdb962337f2cffb71d0f7a3c313 1730 x11 optional gkrellshoot_0.4.4-2.dsc
 d54d3bd64ed232900e65ea9233afb41d 2592 x11 optional 
gkrellshoot_0.4.4-2.debian.tar.xz
 25ece6de89baf574de82e0845e8f3a86 8975 x11 optional 
gkrellshoot_0.4.4-2_20161116T220613z-25ece6de.buildinfo
 6d37ab42ebd04527aad56ac738e85f22 22586 x11 optional 
gkrellshoot_0.4.4-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYLNjcAAoJEJaoeHK36jc3ju8QALSxx46qh8VBx3Ubu69dPK9S
hV0qMB06pcMXZ5hdf8xaE3uZmtBzBK/IKP3aO1saywApDglt2Q29Z5uKEZ+uOQnC
FC8rLxyMzreimkkPmMCRcEgpYiyHTLwFW4xhBU+9eYkXuJNmfMHzDQ9QWl6Q0mMN
kkOxLBHI8bWV1U7AuFk3QfkX0MoiyKZGxY2AwdgUSDeuOa1JNXsIEmDEYBhy4G6M
zt/E4Yx2Berde36rwuVzciorm0BenSN8QT/yKqASsFhRZC0fSv20rvPAUF08YMA9
zb+sa/5/q0qw7JhPuVnNRC7QmCpl2zOOjxiTu4rndsQy+4Dfd69frAY8+6iTt5EP
Pakr3JZXlA2llEy9yXdDhnmuYyTnL5WOa+dmFN2Da9sG4/eipDdLDJKans29Zv6l
CPbS0cSWSuK9n34Llb8BBZu4tdk/JWxZW57Lpvc2btCiwfiwR9PBLfQfEdWyJ3C/

Bug#844220: exim4: fails to install: user mail was not found

[Holger Levsen]

Hi,

On Tue, Nov 15, 2016 at 09:56:53PM +0100, Michael Biebl wrote:
> Am 15.11.2016 um 21:31 schrieb Michael Biebl:
> > On Tue, 15 Nov 2016 13:38:59 + Holger Levsen 
> > wrote:
> >> reassign 844220 usrmerge
> >> thanks
> >>
> >> Hi Marco,
> >>
> >> to summarize this bug: upon running these jenkins jobs with debootstrap
> >> from jessie-backports (which defaults to /usr-merged), several jobs
> >> testing installations in a sid chroot failed. The symptom was that there
> >> was no mail user when exim4 was configured…
> >>
> > 
> > I can't reproduce the problem.

thanks for trying and reporting here, Michael!

> > # getent passwd mail
> > mail:x:8:8:mail:/var/mail:/usr/sbin/nologin
> > 
> > works just fine in a usr-merged system.
> > 
> > I also can't reproduce the installation failure of exim4 (tried in
> > chroot created with the new debootstrap).

how strange…

> > Fwiw, the new d-i alpha8 uses the new deboostrap as well and exim4 is
> > typically installed as part of the system installation.
> > 
> > I just tried a stretch alpha8 installation. Worked fine as well.
> > 
> > Can you attach the exim4 generated config file?
> > What does
> > # getent passwd mail
> > say in your jenkins build chroot?
> > 
> 
> I have to add, that I'm running sid on this particular system and I
> created the chroots with debootstrap from sid. Not sure if that makes a
> difference.

it should not, but oh well…

> Holger, can you specify how we can re-create the exact environment that
> is used on jenkins.d.n so we have a chance of reproducing the issue.

just debootstrap+pbuilder really…

sadly I dont have much time atm to try to reproduce manually, so if
noone else can I would suggest downgrading this bug to normal and
unreproducible and maybe I'll find the time to properly debug or the bug
comes back when /usr-merged comes back as a default…


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Processed: Easy fix

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #844254 [src:libesmtp] libesmtp: FTBFS with openssl 1.1.0
Added tag(s) patch.

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

Bug#844160: Bug#828236: [Pkg-openssl-devel] Bug#844160: openssl 1.1 and apache2

[Stefan Fritsch]

Hi,

[I have trimmed the cc list a bit]

On Wednesday, 16 November 2016 20:36:49 CET Kurt Roeckx wrote:
> On Mon, Nov 14, 2016 at 03:06:44PM -0800, Russ Allbery wrote:
> > Stefan Fritsch  writes:
> > > I must admit that I did not think of php when doing that change, sorry.
> > > 
> > > On the other hand, shibboleth-sp2 also build-depends on apache2-dev and
> > > there have been some indications that shibboleth won't be switching to
> > > openssl 1.1 for stretch. See
> > > https://lists.debian.org/debian-release/2016/11/msg00024.html> 
> > It turns out that Shibboleth will be okay if Apache goes to 1.1.  The
> > Shibboleth code that goes into Apache is isolated from the OpenSSL use
> > inside Shibboleth, so we can keep building Shibboleth against 1.0 and
> > Apache can go to 1.1 and all the pieces are happy.  (The OpenSSL work is
> > done in a separate daemon, shibd, that the Apache module talks to.)
> 
> So I looked at apache2-dev to see why it depends on libssl-dev.
> The only thing I can find is that mod_ssl_openssl.h provides some
> hooks, and you actually get SSL_CTX * and SSL * in there. But
> nothing in Debian seems to include that file.

That header was created for mod_ssl_ct which provides support for certificate 
transparency. It's quite new and likely that nothing else uses the header. It 
would probably be acceptable to remove the dependency in apache2-dev on 
libssl-dev and add a caveat to the README.Debian. I could also not install the 
header, or put it into a separate new package that depends on libssl-dev. 

That would be one alternative. Another would be to switch apache2 to openssl 
1.1. I have explained why I don't want to  this. But it's not impossible. The 
release team has announced that they will decide soon if they want the 
transition to go ahead or not. I will reconsider depending on what they write.

BTW, I am pretty sure that support for enhanced master secret and chacha20 
will appear for openssl 1.0.2 before the release of stretch+1, if only because 
redhat needs it for its long support cycles. Back-porting that to stretch in a 
year or so in a stable-point-release would IMHO be the best option. When 
Apache httpd 2.4 came out, I was also quite disappointed that it could not be 
included in squeeze, but mod_perl was not ready at the time and it would not 
have made any sense to include an inofficial forward-port of mod_perl to 2.4 in 
Debian. In the same way, I don't think it is a good idea to include lots of 
patches for openssl 1.1, with little testing.

Cheers,
Stefan

Bug#844254: Easy fix

[Hilko Bengen]

Control: tag -1 patch

The problem is that the configure script is looking for the wrong symbol
in libssl. Something like this

-   AC_CHECK_LIB(ssl, SSL_library_init, [
+   AC_CHECK_LIB(ssl, SSL_new, [

causes the build to work again.

Looking for SSL_library_init seems to be a somewhat common pattern, by
the way.

Cheers,
-Hilko

Bug#844549: network-console broken: no screen to be resumed matching sh

[Samuel Thibault]

Hello,

Martin Michlmayr, on Wed 16 Nov 2016 12:07:07 -0800, wrote:
> I believe below is the right fix, i.e. start screen when screen exists and
> when we're on serial or when we're NOT on network.

But AIUI the intent was to have screen in ssh connections too.

We could have the case where d-i is first started with the serial
console, running through screen, and enable the network console, which
we'd also want to run through screen.

I'd thus say that we rather want the attached changes, to have one
screen session per terminal type.

I'm also thinking that we perhaps want to add -x when resuming a
session, so that somebody can connect trough ssh several times ?

Samuel
diff --git a/src/lib/debian-installer.d/S70menu 
b/src/lib/debian-installer.d/S70menu
index 7b35fac..2549e29 100644
--- a/src/lib/debian-installer.d/S70menu
+++ b/src/lib/debian-installer.d/S70menu
@@ -14,11 +14,11 @@ else
if [ -x "$screen_bin" -a \( "$TERM_TYPE" = network -o "$TERM_TYPE" = 
serial \) -a "$TERM" != dumb ]; then
# there's GNU/screen binary, run menu in it.
# call this script again with in GNU/screen, possibly in UTF-8 
mode
-   SCREEN_OPT=""
+   SCREEN_OPT="-S $TERM_TYPE"
[ -n "$TERM_UTF8" ] &&
SCREEN_OPT="$SCREEN_OPT -U"
-   [ -d /var/run/screen/S-root -a -e /var/run/screen/S-root/* ] &&
-   SCREEN_OPT="-r" # If GNU/screen is already 
started, just resume it
+   [ -d /var/run/screen/S-root -a -e 
/var/run/screen/S-root/*.$TERM_TYPE ] &&
+   SCREEN_OPT="-r $TERM_TYPE"  # If GNU/screen 
is already started, just resume it
set +e
$screen_bin $SCREEN_OPT sh -c 'printf "\033k%s\033\\" installer 
; /lib/debian-installer/menu'
EXIT=$?

Bug#830399: Info received (Bug#830399: Info received (python-jedi: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13))

[PICCA Frederic-Emmanuel]

looking at the upstream repository,it seems that there is plenty of py3 fixes 
since the last release 0.9.0

so maybe it would be better to not run the unit test for the python3 now.

Another solution is to take the HEAD of python-jedi, as explain by the 
upstream[1] and see if it pass the unit tests

What is your opinion ?

https://github.com/davidhalter/jedi/issues/808

Bug#844549: network-console broken: no screen to be resumed matching sh

[Martin Michlmayr]

* Ben Hutchings  [2016-11-16 21:15]:
> >     rm -f $font
> > -   if [ -x "$screen_bin" -a \( "$TERM_TYPE" = network -o "$TERM_TYPE" = 
> > serial \) -a "$TERM" != dumb ]; then
> > +   if [ -x "$screen_bin" -a \( "$TERM_TYPE" != network -o "$TERM_TYPE" = 
> > serial \) -a "$TERM" != dumb ]; then
> 
> This makes the comparison with 'serial' redundant; the condition will
> be equivalent to:
> 
> [ -x "$screen_bin" -a "$TERM_TYPE" != network -a "$TERM" != dumb ]
> 
> Is that really what we want?

Oh, good point.

I think that's what we want but I'm not sure.  Maybe Roger can
comment.  In his old code, there was also a $NETBOOT_SCREEN variable
which afaict wasn't set set anywhere.

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#835675: marked as done (seahorse-nautilus: FTBFS: conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 21:34:13 +
with message-id 
and subject line Bug#835675: fixed in seahorse-nautilus 3.11.92-1.1
has caused the Debian Bug report #835675,
regarding seahorse-nautilus: FTBFS: conftest.c:11:28: fatal error: 
ac_nonexistent.h: No such file or directory
to be marked as done.

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

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


-- 
835675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: seahorse-nautilus
Version: 3.11.92-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> gcc version 6.2.0 20160822 (Debian 6.2.0-1) 
> configure:3615: $? = 0
> configure:3604: gcc -V >&5
> gcc: error: unrecognized command line option '-V'
> gcc: fatal error: no input files
> compilation terminated.
> configure:3615: $? = 1
> configure:3604: gcc -qversion >&5
> gcc: error: unrecognized command line option '-qversion'; did you mean 
> '--version'?
> gcc: fatal error: no input files
> compilation terminated.
> configure:3615: $? = 1
> configure:3635: checking whether the C compiler works
> configure:3657: gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.c  >&5
> configure:3661: $? = 0
> configure:3709: result: yes
> configure:3712: checking for C compiler default output file name
> configure:3714: result: a.out
> configure:3720: checking for suffix of executables
> configure:3727: gcc -o conftest -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.c  >&5
> configure:3731: $? = 0
> configure:3753: result: 
> configure:3775: checking whether we are cross compiling
> configure:3783: gcc -o conftest -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.c  >&5
> configure:3787: $? = 0
> configure:3794: ./conftest
> configure:3798: $? = 0
> configure:3813: result: no
> configure:3818: checking for suffix of object files
> configure:3840: gcc -c -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3844: $? = 0
> configure:3865: result: o
> configure:3869: checking whether we are using the GNU C compiler
> configure:3888: gcc -c -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3888: $? = 0
> configure:3897: result: yes
> configure:3906: checking whether gcc accepts -g
> configure:3926: gcc -c -g -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3926: $? = 0
> configure:3967: result: yes
> configure:3984: checking for gcc option to accept ISO C89
> configure:4047: gcc  -c -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:4047: $? = 0
> configure:4060: result: none needed
> configure:4082: checking dependency style of gcc
> configure:4193: result: none
> configure:4214: checking how to run the C preprocessor
> configure:4245: gcc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
> configure:4245: $? = 0
> configure:4259: gcc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
> conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory
>  #include 
> ^
> compilation terminated.
> configure:4259: $? = 1
> configure: failed program was:
> | /* confdefs.h */
> | #define PACKAGE_NAME "seahorse-nautilus"
> | #define PACKAGE_TARNAME "seahorse-nautilus"
> | #define PACKAGE_VERSION "3.11.92"
> | #define PACKAGE_STRING "seahorse-nautilus 3.11.92"
> | #define PACKAGE_BUGREPORT 
> "http://bugzilla.gnome.org/enter_bug.cgi?product=seahorse-plugins=Nautilus;
> | #define PACKAGE_URL ""
> | #define PACKAGE "seahorse-nautilus"
> | #define VERSION "3.11.92"
> | /* end confdefs.h.  */
> | #include 
> configure:4284: result: gcc -E
> configure:4304: gcc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
> configure:4304: $? = 0
> configure:4318: gcc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
> conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory
>  #include 
>  

Bug#835702: marked as done (seahorse-nautilus: FTBFS: conftest.c:64:20: error: expected expression before ')' token)

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 21:34:13 +
with message-id 
and subject line Bug#835675: fixed in seahorse-nautilus 3.11.92-1.1
has caused the Debian Bug report #835675,
regarding seahorse-nautilus: FTBFS: conftest.c:64:20: error: expected 
expression before ')' token
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.)


-- 
835675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: seahorse-nautilus
Version: 3.11.92-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

seahorse-nautilus fails to build from source in unstable/amd64:

  [..]

  lt_cv_path_mainfest_tool=no
  lt_cv_prog_compiler_c_o=yes
  lt_cv_prog_compiler_pic='-fPIC -DPIC'
  lt_cv_prog_compiler_pic_works=yes
  lt_cv_prog_compiler_rtti_exceptions=no
  lt_cv_prog_compiler_static_works=yes
  lt_cv_prog_gnu_ld=yes
  lt_cv_sharedlib_from_linklib_cmd='printf %s\n'
  lt_cv_shlibpath_overrides_runpath=no
  lt_cv_sys_global_symbol_pipe='sed -n -e '\''s/^.*[ 
]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][  
]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p'\'' | sed '\''/ __gnu_lto/d'\'''
  lt_cv_sys_global_symbol_to_c_name_address='sed -n -e '\''s/^: \([^ ]*\)[ ]*$/ 
 {\"\1\", (void *) 0},/p'\'' -e '\''s/^[ABCDGIRSTW]* \([^ ]*\) \([^ ]*\)$/  
{"\2", (void *) \&\2},/p'\'''
  lt_cv_sys_global_symbol_to_c_name_address_lib_prefix='sed -n -e '\''s/^: \([^ 
]*\)[ ]*$/  {\"\1\", (void *) 0},/p'\'' -e '\''s/^[ABCDGIRSTW]* \([^ ]*\) 
\(lib[^ ]*\)$/  {"\2", (void *) \&\2},/p'\'' -e '\''s/^[ABCDGIRSTW]* \([^ ]*\) 
\([^ ]*\)$/  {"lib\2", (void *) \&\2},/p'\'''
  lt_cv_sys_global_symbol_to_cdecl='sed -n -e '\''s/^T .* \(.*\)$/extern int 
\1();/p'\'' -e '\''s/^[ABCDGIRSTW]* .* \(.*\)$/extern char \1;/p'\'''
  lt_cv_sys_max_cmd_len=1572864
  lt_cv_to_host_file_cmd=func_convert_file_noop
  lt_cv_to_tool_file_cmd=func_convert_file_noop
  pkg_cv_GTK_CFLAGS='-pthread -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include'
  pkg_cv_GTK_LIBS='-lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 
-lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0'
  
  ## - ##
  ## Output variables. ##
  ## - ##
  
  
  
  
  
  
  
  
  
  
$(INSTALL_DATA) $^ "$(DESTDIR)$(gsettingsschemadir)"; \
test -n "$(GSETTINGS_DISABLE_SCHEMAS_COMPILE)$(DESTDIR)" || 
$(GLIB_COMPILE_SCHEMAS) $(gsettingsschemadir); \
test -z "$(gsettingsschemadir)" || $(MKDIR_P) 
"$(DESTDIR)$(gsettingsschemadir)"; \
$(AM_V_GEN) glib-mkenums --comments '\'''\'' --fhead 
"" --vhead "  <@type@ 
id='\''$(gsettings_ENUM_NAMESPACE).@EnumName@'\''>" --vprod "" --vtail "  " 
--ftail "" $^ > $@.tmp && mv $@.tmp $@
$(AM_V_GEN) if test -f "$<"; then d=; else d="$(srcdir)/"; fi; 
$(GLIB_COMPILE_SCHEMAS) --strict --dry-run $(addprefix 
--schema-file=,$(gsettings__enum_file)) --schema-file=$${d}$< && touch $@
@$(NORMAL_INSTALL)
@$(NORMAL_UNINSTALL)
@list='\''$(gsettings_SCHEMAS) $(gsettings__enum_file)'\''; test -n 
"$(gsettingsschemadir)" || list=; \
cd "$(DESTDIR)$(gsettingsschemadir)" && rm -f $$files
echo " ( cd '\''$(DESTDIR)$(gsettingsschemadir)'\'' && rm -f" $$files 
")"; \
fi
files=`for p in $$list; do echo $$p; done | sed -e '\''s|^.*/||'\''`; \
if test -n "$^"; then \
rm -f $(gsettings_SCHEMAS:.xml=.valid) $(gsettings__enum_file)
test -n "$$files" || exit 0; \
test -n "$(GSETTINGS_DISABLE_SCHEMAS_COMPILE)$(DESTDIR)" || 
$(GLIB_COMPILE_SCHEMAS) $(gsettingsschemadir)
  $(gsettings__enum_file): $(gsettings_ENUM_FILES)
  %.gschema.valid: %.gschema.xml $(gsettings__enum_file)
  .PHONY : uninstall-gsettings-schemas install-gsettings-schemas 
clean-gsettings-schemas
  .SECONDARY: $(gsettings_SCHEMAS)
  ACLOCAL='${SHELL} 

Bug#830399: Info received (python-jedi: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13)

[PICCA Frederic-Emmanuel]

I just apply this patch and the import test PASS.

I took only a part of the upstream patch

but now I get this 

I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_3.5/build; 
python3.5 -m pytest test
= test session starts ==
platform linux -- Python 3.5.2+, pytest-3.0.3, py-1.4.31, pluggy-0.4.0
rootdir: /<>, inifile: pytest.ini
collected 257 items / 1 errors

 ERRORS 
 ERROR collecting .pybuild/pythonX.Y_3.5/build/test/test_integration.py 
test/conftest.py:59: in pytest_generate_tests
cases = list(run.collect_dir_tests(base_dir, test_files))
test/run.py:293: in collect_dir_tests
source = open(path).read()
/usr/lib/python3.5/encodings/ascii.py:26: in decode
return codecs.ascii_decode(input, self.errors)[0]
E   UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 331: 
ordinal not in range(128)
!!! Interrupted: 1 errors during collection 
=== 1 error in 4.38 seconds Description: 
 TODO: Put a short summary on the line above and replace this paragraph
 with a longer explanation of this change. Complete the meta-information
 with other relevant fields (see below for details). To make it easier, the
 information below has been extracted from the changelog. Adjust it or drop
 it.
 .
 python-jedi (0.9.0-1) unstable; urgency=medium
 .
   * New upstream release
   * debian/watch: use pypi.debian.net redirector
Author: Piotr Ożarowski 

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: , 
Bug: 
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded: 
Reviewed-By: 
Last-Update: 2016-11-16

--- python-jedi-0.9.0.orig/test/test_integration_import.py
+++ python-jedi-0.9.0/test/test_integration_import.py
@@ -18,22 +18,22 @@ def test_goto_definition_on_import():
 def test_complete_on_empty_import():
 assert Script("from datetime import").completions()[0].name == 'import'
 # should just list the files in the directory
-assert 10 < len(Script("from .", path='').completions()) < 30
+assert 10 < len(Script("from .", path='whatever.py').completions()) < 30
 
 # Global import
-assert len(Script("from . import", 1, 5, '').completions()) > 30
+assert len(Script("from . import", 1, 5, 'whatever.py').completions()) > 30
 # relative import
-assert 10 < len(Script("from . import", 1, 6, '').completions()) < 30
+assert 10 < len(Script("from . import", 1, 6, 'whatever.py').completions()) < 30
 
 # Global import
-assert len(Script("from . import classes", 1, 5, '').completions()) > 30
+assert len(Script("from . import classes", 1, 5, 'whatever.py').completions()) > 30
 # relative import
-assert 10 < len(Script("from . import classes", 1, 6, '').completions()) < 30
+assert 10 < len(Script("from . import classes", 1, 6, 'whatever.py').completions()) < 30
 
 wanted = set(['ImportError', 'import', 'ImportWarning'])
 assert set([c.name for c in Script("import").completions()]) == wanted
 if not is_py26:  # python 2.6 doesn't always come with a library `import*`.
-assert len(Script("import import", path='').completions()) > 0
+assert len(Script("import import", path='whatever.py').completions()) > 0
 
 # 111
 assert Script("from datetime import").completions()[0].name == 'import'

Bug#835675: [nmu] debdiff

[intrigeri]

hi,

u:
> built and tested the binary. Looks good!

Thanks! I've verified that this does fix the FTBFS, uploaded after
adding missing info to debian/changelog. Here is the corresponding
updated debdiff.

Cheers!
-- 
intrigeri

diff -Nru seahorse-nautilus-3.11.92/debian/changelog seahorse-nautilus-3.11.92/debian/changelog
--- seahorse-nautilus-3.11.92/debian/changelog	2014-09-15 21:35:21.0 +0200
+++ seahorse-nautilus-3.11.92/debian/changelog	2016-11-16 21:31:26.0 +0100
@@ -1,3 +1,13 @@
+seahorse-nautilus (3.11.92-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * gpg21.patch: new patch, fixes FTBFS by supporting GnuPG 2.1;
+Thanks to Adrian Bunk  for providing a patch.
+(Closes: #835675)
+  * Really remove add-correct-flag-for-reaping-the-progress-child.patch.
+
+ -- Ulrike Uhlig   Wed, 16 Nov 2016 21:31:26 +0100
+
 seahorse-nautilus (3.11.92-1) unstable; urgency=medium
 
   [ Clément Hermann (nodens) ]
diff -Nru seahorse-nautilus-3.11.92/debian/patches/add-correct-flag-for-reaping-the-progress-child.patch seahorse-nautilus-3.11.92/debian/patches/add-correct-flag-for-reaping-the-progress-child.patch
--- seahorse-nautilus-3.11.92/debian/patches/add-correct-flag-for-reaping-the-progress-child.patch	2014-03-23 00:20:50.0 +0100
+++ seahorse-nautilus-3.11.92/debian/patches/add-correct-flag-for-reaping-the-progress-child.patch	1970-01-01 01:00:00.0 +0100
@@ -1,26 +0,0 @@
-From: Stef Walter 
-Date: Fri, 16 Aug 2013 17:24:11 +
-Subject: Add correct flag for reaping the progress child
-Origin: https://git.gnome.org/browse/seahorse-nautilus/commit/?id=c41f07cf5785b2d755b85f20bf0546c6ce2ebb02
-
-This fixes the WARNING about ECHILD that comes from some versions
-of glib. The WARNING was removed in later versions of glib, but this
-is also a good fix.
-
-https://bugzilla.gnome.org/show_bug.cgi?id=697895

-diff --git a/tool/seahorse-tool-progress.c b/tool/seahorse-tool-progress.c
-index 613e82f..c039118 100644
 a/tool/seahorse-tool-progress.c
-+++ b/tool/seahorse-tool-progress.c
-@@ -217,7 +217,7 @@ seahorse_tool_progress_start (const gchar *title)
- argv[2] = (gchar *)title;
- argv[3] = NULL;
- 
--ret = g_spawn_async_with_pipes (NULL, argv, NULL, G_SPAWN_STDOUT_TO_DEV_NULL | G_SPAWN_SEARCH_PATH,
-+ret = g_spawn_async_with_pipes (NULL, argv, NULL, G_SPAWN_STDOUT_TO_DEV_NULL | G_SPAWN_SEARCH_PATH | G_SPAWN_DO_NOT_REAP_CHILD,
- NULL, NULL, _pid, _fd, NULL, NULL, );
- 
- if (!ret) {
---
-cgit v0.9.2
diff -Nru seahorse-nautilus-3.11.92/debian/patches/gpg21.patch seahorse-nautilus-3.11.92/debian/patches/gpg21.patch
--- seahorse-nautilus-3.11.92/debian/patches/gpg21.patch	1970-01-01 01:00:00.0 +0100
+++ seahorse-nautilus-3.11.92/debian/patches/gpg21.patch	2016-11-16 21:31:26.0 +0100
@@ -0,0 +1,29 @@
+Description: Accept GnuPG 2.1
+ This is the minimum change to fix the build,
+ upstream fixed this as part of a bigger change in 3.18
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/835675
+Forwarded: not-needed
+
+--- seahorse-nautilus-3.11.92.orig/configure.ac
 seahorse-nautilus-3.11.92/configure.ac
+@@ -57,7 +57,7 @@ AC_ARG_ENABLE(gpg-check,
+ 	DO_CHECK=$enableval, DO_CHECK=yes)
+ 
+ if test	"$DO_CHECK" = "yes"; then
+-	accepted_versions="1.2 1.4 2.0"
++	accepted_versions="1.2 1.4 2.0 2.1"
+ 	AC_PATH_PROGS(GNUPG, [gpg gpg2], no)
+ 	ok="no"
+ 	if test "$GNUPG" != "no"; then
+--- seahorse-nautilus-3.11.92.orig/configure
 seahorse-nautilus-3.11.92/configure
+@@ -14879,7 +14891,7 @@ fi
+ 
+ 
+ if test	"$DO_CHECK" = "yes"; then
+-	accepted_versions="1.2 1.4 2.0"
++	accepted_versions="1.2 1.4 2.0 2.1"
+ 	for ac_prog in gpg gpg2
+ do
+   # Extract the first word of "$ac_prog", so it can be a program name with args.
diff -Nru seahorse-nautilus-3.11.92/debian/patches/series seahorse-nautilus-3.11.92/debian/patches/series
--- seahorse-nautilus-3.11.92/debian/patches/series	2014-09-15 21:31:16.0 +0200
+++ seahorse-nautilus-3.11.92/debian/patches/series	2016-11-16 21:31:26.0 +0100
@@ -0,0 +1 @@
+gpg21.patch

Bug#835675: [nmu] debdiff

[u]

Hi,

built and tested the binary. Looks good!

Cheers!
u.
diff -Nru seahorse-nautilus-3.11.92/debian/changelog 
seahorse-nautilus-3.11.92/debian/changelog
--- seahorse-nautilus-3.11.92/debian/changelog  2014-09-15 21:35:21.0 
+0200
+++ seahorse-nautilus-3.11.92/debian/changelog  2016-11-16 21:34:02.0 
+0100
@@ -1,3 +1,10 @@
+seahorse-nautilus (3.11.92-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Really remove add-correct-flag-for-reaping-the-progress-child.patch.
+
+ -- Ulrike Uhlig   Wed, 16 Nov 2016 21:31:26 +0100
+
 seahorse-nautilus (3.11.92-1) unstable; urgency=medium
 
   [ Clément Hermann (nodens) ]
diff -Nru 
seahorse-nautilus-3.11.92/debian/patches/add-correct-flag-for-reaping-the-progress-child.patch
 
seahorse-nautilus-3.11.92/debian/patches/add-correct-flag-for-reaping-the-progress-child.patch
--- 
seahorse-nautilus-3.11.92/debian/patches/add-correct-flag-for-reaping-the-progress-child.patch
  2014-03-23 00:20:50.0 +0100
+++ 
seahorse-nautilus-3.11.92/debian/patches/add-correct-flag-for-reaping-the-progress-child.patch
  1970-01-01 01:00:00.0 +0100
@@ -1,26 +0,0 @@
-From: Stef Walter 
-Date: Fri, 16 Aug 2013 17:24:11 +
-Subject: Add correct flag for reaping the progress child
-Origin: 
https://git.gnome.org/browse/seahorse-nautilus/commit/?id=c41f07cf5785b2d755b85f20bf0546c6ce2ebb02
-
-This fixes the WARNING about ECHILD that comes from some versions
-of glib. The WARNING was removed in later versions of glib, but this
-is also a good fix.
-
-https://bugzilla.gnome.org/show_bug.cgi?id=697895

-diff --git a/tool/seahorse-tool-progress.c b/tool/seahorse-tool-progress.c
-index 613e82f..c039118 100644
 a/tool/seahorse-tool-progress.c
-+++ b/tool/seahorse-tool-progress.c
-@@ -217,7 +217,7 @@ seahorse_tool_progress_start (const gchar *title)
- argv[2] = (gchar *)title;
- argv[3] = NULL;
- 
--ret = g_spawn_async_with_pipes (NULL, argv, NULL, 
G_SPAWN_STDOUT_TO_DEV_NULL | G_SPAWN_SEARCH_PATH,
-+ret = g_spawn_async_with_pipes (NULL, argv, NULL, 
G_SPAWN_STDOUT_TO_DEV_NULL | G_SPAWN_SEARCH_PATH | G_SPAWN_DO_NOT_REAP_CHILD,
- NULL, NULL, _pid, _fd, 
NULL, NULL, );
- 
- if (!ret) {
---
-cgit v0.9.2
diff -Nru seahorse-nautilus-3.11.92/debian/patches/gpg21.patch 
seahorse-nautilus-3.11.92/debian/patches/gpg21.patch
--- seahorse-nautilus-3.11.92/debian/patches/gpg21.patch1970-01-01 
01:00:00.0 +0100
+++ seahorse-nautilus-3.11.92/debian/patches/gpg21.patch2016-11-16 
21:30:02.0 +0100
@@ -0,0 +1,29 @@
+Description: Accept GnuPG 2.1
+ This is the minimum change to fix the build,
+ upstream fixed this as part of a bigger change in 3.18
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/835675
+Forwarded: not-needed
+
+--- seahorse-nautilus-3.11.92.orig/configure.ac
 seahorse-nautilus-3.11.92/configure.ac
+@@ -57,7 +57,7 @@ AC_ARG_ENABLE(gpg-check,
+   DO_CHECK=$enableval, DO_CHECK=yes)
+ 
+ if test   "$DO_CHECK" = "yes"; then
+-  accepted_versions="1.2 1.4 2.0"
++  accepted_versions="1.2 1.4 2.0 2.1"
+   AC_PATH_PROGS(GNUPG, [gpg gpg2], no)
+   ok="no"
+   if test "$GNUPG" != "no"; then
+--- seahorse-nautilus-3.11.92.orig/configure
 seahorse-nautilus-3.11.92/configure
+@@ -14879,7 +14891,7 @@ fi
+ 
+ 
+ if test   "$DO_CHECK" = "yes"; then
+-  accepted_versions="1.2 1.4 2.0"
++  accepted_versions="1.2 1.4 2.0 2.1"
+   for ac_prog in gpg gpg2
+ do
+   # Extract the first word of "$ac_prog", so it can be a program name with 
args.
diff -Nru seahorse-nautilus-3.11.92/debian/patches/series 
seahorse-nautilus-3.11.92/debian/patches/series
--- seahorse-nautilus-3.11.92/debian/patches/series 2014-09-15 
21:31:16.0 +0200
+++ seahorse-nautilus-3.11.92/debian/patches/series 2016-11-16 
21:30:02.0 +0100
@@ -0,0 +1 @@
+gpg21.patch

Bug#844549: network-console broken: no screen to be resumed matching sh

[Ben Hutchings]

On Wed, 2016-11-16 at 12:07 -0800, Martin Michlmayr wrote:
> Package: rootskel
> Version: 1.119
> Severity: serious
> Tags: patch
> 
> Several users have reported to me that the network-console images are
> broken.
> 
> Commit ec6d3c3d79 (Move screen support) moved the screen support
> around and also changed the logic of when screen is used.
> Unfortunately, that change broke all network-console images which now
> lead to:
> 
> installer@192.168.0.102's password:
> There is no screen to be resumed matching sh.
> Connection to 192.168.0.102 closed.
> 
> This is because d-i is already running in screen on the serial console but
> it's active and can't be resumed.
> 
> I believe below is the right fix, i.e. start screen when screen exists and
> when we're on serial or when we're NOT on network.
> 
> Samuel, Roger, does that look correct?
> 
> diff --git a/src/lib/debian-installer.d/S70menu 
> b/src/lib/debian-installer.d/S70menu
> index 7b35fac..14cad7f 100644
> --- a/src/lib/debian-installer.d/S70menu
> +++ b/src/lib/debian-installer.d/S70menu
> @@ -11,7 +11,7 @@ if [ -x "$bterm" ] && [ -e "$font" ] && [ -n "$TERM_UTF8" ] 
> && [ -n "$TERM_FRAME
>   set -e
>  else
>   rm -f $font
> - if [ -x "$screen_bin" -a \( "$TERM_TYPE" = network -o "$TERM_TYPE" = 
> serial \) -a "$TERM" != dumb ]; then
> + if [ -x "$screen_bin" -a \( "$TERM_TYPE" != network -o "$TERM_TYPE" = 
> serial \) -a "$TERM" != dumb ]; then

This makes the comparison with 'serial' redundant; the condition will
be equivalent to:

[ -x "$screen_bin" -a "$TERM_TYPE" != network -a "$TERM" != dumb ]

Is that really what we want?

Ben.

>   # there's GNU/screen binary, run menu in it.
> >     # call this script again with in GNU/screen, possibly in UTF-8 
> > mode
> >     SCREEN_OPT=""
> 
-- 
Ben Hutchings
Time is nature's way of making sure that everything doesn't happen at
once.


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

Processed: Bug#837566 marked as pending

[Debian Bug Tracking System]

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

> tag 837566 pending
Bug #837566 [src:mjpegtools] mjpegtools: FTBFS with bindnow and PIE enabled
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#844558: gdcm: FTBFS on mipsel

[Adrian Bunk]

Control: reassign -1 binutils
Control: forcemerge 844357 -1
Control: affects 844357 src:gdcm

On Wed, Nov 16, 2016 at 09:38:05PM +0100, Bas Couwenberg wrote:
> Source: gdcm
> Version: 2.6.6-2
> Severity: serious
> Justification: makes the package in question unusable or mostly so
> 
> Dear Maintainer,
> 
> gdcm 2.6.6-2 FTBFS on mipsel and this seems to block the poppler
> migration to testing.
> 
> If the build cannot be fixed, please request partial removal of gdcm and
> its reverse dependencies from mipsel.

/usr/lib/mipsel-linux-gnu/libvtkRenderingOpenGL-6.3.so.6.3.0: undefined 
reference to `glLoadMatrixd'

This is #844357

> Kind Regards,
> 
> Bas

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#837566: marked as pending

[Sebastian Ramacher]

tag 837566 pending
thanks

Hello,

Bug #837566 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


http://git.debian.org/?p=pkg-multimedia/mjpegtools.git;a=commitdiff;h=bb3e442

---
commit bb3e44212c5154fc512353765d3fe018c50cee45
Author: Sebastian Ramacher 
Date:   Wed Nov 16 21:50:59 2016 +0100

Finalize changelog

diff --git a/debian/changelog b/debian/changelog
index c61b81d..022f8d1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+mjpegtools (1:2.1.0+debian-5) unstable; urgency=medium
+
+  * Team upload.
+  * debian/{control,rules,compat}: Bump dh compat to 10.
+  * debian/patches: Do not use -fno-PIC (Closes: #837566)
+  * debian/rules: Build with -Wl,--as-needed
+
+ -- Sebastian Ramacher   Wed, 16 Nov 2016 21:50:46 +0100
+
 mjpegtools (1:2.1.0+debian-4) unstable; urgency=medium
 
   * Team upload.

Bug#844558: gdcm: FTBFS on mipsel

[Bas Couwenberg]

Source: gdcm
Version: 2.6.6-2
Severity: serious
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

gdcm 2.6.6-2 FTBFS on mipsel and this seems to block the poppler
migration to testing.

If the build cannot be fixed, please request partial removal of gdcm and
its reverse dependencies from mipsel.

Kind Regards,

Bas

Processed: Merge with the other bugs

[Debian Bug Tracking System]

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

> reassign 844550 libmysqlclient-dev
Bug #844550 [src:mediatomb] mediatomb: FTBFS: g++: error: .specs: No such file 
or directory
Bug reassigned from package 'src:mediatomb' to 'libmysqlclient-dev'.
No longer marked as found in versions mediatomb/0.12.1-47-g7ab7616-1.
Ignoring request to alter fixed versions of bug #844550 to the same values 
previously set
> forcemerge 844275 844550
Bug #844275 [libmysqlclient-dev] mysql_config injects build flags which breaks 
the build for other packages
Bug #844302 [libmysqlclient-dev] libapache-mod-musicindex: FTBFS: 
x86_64-linux-gnu-gcc: error: .specs: No such file or directory
Bug #844304 [libmysqlclient-dev] python-mysqldb: FTBFS: x86_64-linux-gnu-gcc: 
error: .specs: No such file or directory
Bug #844401 [libmysqlclient-dev] redland: FTBFS: gcc: error: .specs: No such 
file or directory
Bug #844492 [libmysqlclient-dev] lua-sql: FTBFS: cc: error: .specs: No such 
file or directory
Bug #844304 [libmysqlclient-dev] python-mysqldb: FTBFS: x86_64-linux-gnu-gcc: 
error: .specs: No such file or directory
Removed indication that 844304 affects src:libapache-mod-musicindex, 
src:rsyslog, src:redland, src:python-mysqldb, and src:lua-sql
Added indication that 844304 affects 
src:python-mysqldb,src:lua-sql,src:rsyslog,src:redland,src:libapache-mod-musicindex
Removed indication that 844275 affects src:lua-sql, 
src:libapache-mod-musicindex, src:rsyslog, src:python-mysqldb, and src:redland
Added indication that 844275 affects 
src:python-mysqldb,src:lua-sql,src:rsyslog,src:redland,src:libapache-mod-musicindex
Removed indication that 844302 affects src:lua-sql, src:python-mysqldb, 
src:redland, src:libapache-mod-musicindex, and src:rsyslog
Added indication that 844302 affects 
src:python-mysqldb,src:lua-sql,src:rsyslog,src:redland,src:libapache-mod-musicindex
Removed indication that 844401 affects src:rsyslog, 
src:libapache-mod-musicindex, src:redland, src:python-mysqldb, and src:lua-sql
Added indication that 844401 affects 
src:python-mysqldb,src:lua-sql,src:rsyslog,src:redland,src:libapache-mod-musicindex
Removed indication that 844492 affects src:redland, src:python-mysqldb, 
src:libapache-mod-musicindex, src:rsyslog, and src:lua-sql
Added indication that 844492 affects 
src:python-mysqldb,src:lua-sql,src:rsyslog,src:redland,src:libapache-mod-musicindex
Bug #844550 [libmysqlclient-dev] mediatomb: FTBFS: g++: error: .specs: No such 
file or directory
Added indication that 844550 affects 
src:python-mysqldb,src:lua-sql,src:rsyslog,src:redland,src:libapache-mod-musicindex
Marked as found in versions mysql-5.7/5.7.16-1.
Bug #844302 [libmysqlclient-dev] libapache-mod-musicindex: FTBFS: 
x86_64-linux-gnu-gcc: error: .specs: No such file or directory
Bug #844401 [libmysqlclient-dev] redland: FTBFS: gcc: error: .specs: No such 
file or directory
Bug #844492 [libmysqlclient-dev] lua-sql: FTBFS: cc: error: .specs: No such 
file or directory
Merged 844275 844302 844304 844401 844492 844550
> affects 844275 src:mediatomb
Bug #844275 [libmysqlclient-dev] mysql_config injects build flags which breaks 
the build for other packages
Bug #844302 [libmysqlclient-dev] libapache-mod-musicindex: FTBFS: 
x86_64-linux-gnu-gcc: error: .specs: No such file or directory
Bug #844304 [libmysqlclient-dev] python-mysqldb: FTBFS: x86_64-linux-gnu-gcc: 
error: .specs: No such file or directory
Bug #844401 [libmysqlclient-dev] redland: FTBFS: gcc: error: .specs: No such 
file or directory
Bug #844492 [libmysqlclient-dev] lua-sql: FTBFS: cc: error: .specs: No such 
file or directory
Bug #844550 [libmysqlclient-dev] mediatomb: FTBFS: g++: error: .specs: No such 
file or directory
Added indication that 844275 affects src:mediatomb
Added indication that 844302 affects src:mediatomb
Added indication that 844304 affects src:mediatomb
Added indication that 844401 affects src:mediatomb
Added indication that 844492 affects src:mediatomb
Added indication that 844550 affects src:mediatomb
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
844275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844275
844302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844302
844304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844304
844401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844401
844492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844492
844550: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#844160: [Pkg-openssl-devel] Bug#844160: openssl 1.1 and apache2

[Kurt Roeckx]

On Wed, Nov 16, 2016 at 10:26:48PM +0200, Adrian Bunk wrote:
> On Wed, Nov 16, 2016 at 08:36:49PM +0100, Kurt Roeckx wrote:
> > On Mon, Nov 14, 2016 at 03:06:44PM -0800, Russ Allbery wrote:
> > > Stefan Fritsch  writes:
> > > 
> > > > I must admit that I did not think of php when doing that change, sorry. 
> > > 
> > > > On the other hand, shibboleth-sp2 also build-depends on apache2-dev and 
> > > > there 
> > > > have been some indications that shibboleth won't be switching to 
> > > > openssl 1.1 
> > > > for stretch. See 
> > > > https://lists.debian.org/debian-release/2016/11/msg00024.html
> > > 
> > > It turns out that Shibboleth will be okay if Apache goes to 1.1.  The
> > > Shibboleth code that goes into Apache is isolated from the OpenSSL use
> > > inside Shibboleth, so we can keep building Shibboleth against 1.0 and
> > > Apache can go to 1.1 and all the pieces are happy.  (The OpenSSL work is
> > > done in a separate daemon, shibd, that the Apache module talks to.)
> > 
> > So I looked at apache2-dev to see why it depends on libssl-dev.
> > The only thing I can find is that mod_ssl_openssl.h provides some
> > hooks, and you actually get SSL_CTX * and SSL * in there. But
> > nothing in Debian seems to include that file.
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828330#16
> 
> Where is that dependency on the same OpenSSL version coming from?

Like I just said, it exposes the SSL_CTX * and SSL *, and you need
to use them with the same version that created them.


Kurt

Bug#698527: Already fixed in oldstable

[Francesco Poli]

On Wed, 16 Nov 2016 14:07:39 +0200 Adrian Bunk wrote:

[...]
> On Sat, Oct 29, 2016 at 06:13:21PM +0200, Francesco Poli wrote:
> > On Mon, 17 Oct 2016 22:59:06 +0200 Francesco Poli wrote:
[...]
> > > ElmerGUI is included in the experimental package (elmerfem/7.0.svn.6034
> > > +dfsg-2): it's not clear to me how the OpenSSL linking issue was solved.
> > > I cannot find any explanation in the changelog: could someone please
> > > clarify?
> > > 
> > > Please let me know.
> > > Thanks for your time!
> > 
> > Ping?
> 
> Thanks a lot for noticing, and apologies for the late reply.

You're welcome. And no problems for the delay...

> 
> I completely missed that the more recent version in experimental
> is not fixed, reopening.

OK, thank you!

Please address the remaining issue (that is to say: the link with
OpenSSL).
I hope this may be done soon.

Bye and thanks for your time!


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpd8WceDH_4o.pgp
Description: PGP signature

Bug#844160: [Pkg-openssl-devel] Bug#844160: openssl 1.1 and apache2

[Adrian Bunk]

On Wed, Nov 16, 2016 at 08:36:49PM +0100, Kurt Roeckx wrote:
> On Mon, Nov 14, 2016 at 03:06:44PM -0800, Russ Allbery wrote:
> > Stefan Fritsch  writes:
> > 
> > > I must admit that I did not think of php when doing that change, sorry. 
> > 
> > > On the other hand, shibboleth-sp2 also build-depends on apache2-dev and 
> > > there 
> > > have been some indications that shibboleth won't be switching to openssl 
> > > 1.1 
> > > for stretch. See 
> > > https://lists.debian.org/debian-release/2016/11/msg00024.html
> > 
> > It turns out that Shibboleth will be okay if Apache goes to 1.1.  The
> > Shibboleth code that goes into Apache is isolated from the OpenSSL use
> > inside Shibboleth, so we can keep building Shibboleth against 1.0 and
> > Apache can go to 1.1 and all the pieces are happy.  (The OpenSSL work is
> > done in a separate daemon, shibd, that the Apache module talks to.)
> 
> So I looked at apache2-dev to see why it depends on libssl-dev.
> The only thing I can find is that mod_ssl_openssl.h provides some
> hooks, and you actually get SSL_CTX * and SSL * in there. But
> nothing in Debian seems to include that file.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828330#16

Where is that dependency on the same OpenSSL version coming from?

> Kurt

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#844550: mediatomb: FTBFS: g++: error: .specs: No such file or directory

[Chris Lamb]

Source: mediatomb
Version: 0.12.1-47-g7ab7616-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

mediatomb fails to build from source in unstable/amd64:

  […]

  LDFLAGS='-Wl,-z,relro'
  LIBEXIF_CFLAGS=''
  LIBEXIF_LDFLAGS=''
  LIBEXIF_LIBS=''
  LIBEXIF_OPTION_ENABLED=''
  LIBEXIF_OPTION_REQUESTED=''
  LIBEXIF_STATUS=''
  LIBJS_CFLAGS=''
  LIBJS_LIBS=''
  LIBJS_OPTION_ENABLED=''
  LIBJS_OPTION_REQUESTED=''
  LIBMAGIC_CFLAGS=''
  LIBMAGIC_LDFLAGS=''
  LIBMAGIC_LIBS=''
  LIBMAGIC_OPTION_ENABLED=''
  LIBMAGIC_OPTION_REQUESTED=''
  LIBMAGIC_STATUS=''
  LIBMAGIC_VERSION=''
  LIBMP4V2_CFLAGS=''
  LIBMP4V2_LDFLAGS=''
  LIBMP4V2_LIBS=''
  LIBMP4V2_OPTION_ENABLED=''
  LIBMP4V2_OPTION_REQUESTED=''
  LIBMP4V2_STATUS=''
  LIBOBJS=''
  LIBS=''
  LOG_OPTION_ENABLED=''
  LOG_OPTION_REQUESTED=''
  LTLIBOBJS=''
  LWRES_LIBS=''
  MAKEINFO='${SHELL} 
/home/lamby/temp/cdt.20161116210630.psKfUnjLkH.db.mediatomb/mediatomb-0.12.1-47-g7ab7616/configure_aux/missing
 makeinfo'
  MKDIR_P='/bin/mkdir -p'
  MRREG_SERVICE_OPTION_ENABLED='no'
  MRREG_SERVICE_OPTION_REQUESTED='no'
  MT_SEARCHPATH='/usr/local'
  MT_SEARCHPATH_HEADERS='/usr/local/include'
  MT_SEARCHPATH_LIBS='/usr/local/lib'
  MT_SEARCHPATH_PKGCONFIG='/usr/local/lib/pkgconfig'
  MT_SEARCHPATH_PROGS='/usr/local/bin'
  MYSQL_CFLAGS=''
  MYSQL_LIBS=''
  MYSQL_OPTION_ENABLED='yes'
  MYSQL_OPTION_REQUESTED='yes'
  MYSQL_STATUS=''
  MYSQL_VERSION=''
  NSL_LIBS=''
  OBJEXT='o'
  PACKAGE='mediatomb'
  PACKAGE_BUGREPORT='j...@mediatomb.cc'
  PACKAGE_NAME='MediaTomb'
  PACKAGE_STRING='MediaTomb 0.12.2'
  PACKAGE_TARNAME='mediatomb'
  PACKAGE_URL=''
  PACKAGE_VERSION='0.12.2'
  PATH_SEPARATOR=':'
  PKG_CONFIG='/usr/bin/pkg-config'
  PKG_CONFIG_LIBDIR=''
  PKG_CONFIG_PATH=''
  POW_LIB=''
  PROTOCOLINFO_EXTENSION_OPTION_ENABLED='yes'
  PROTOCOLINFO_EXTENSION_OPTION_REQUESTED='no'
  PTHREAD_CC='gcc'
  PTHREAD_CFLAGS='-pthread'
  PTHREAD_LDFLAGS=''
  PTHREAD_LIBS=''
  PTHREAD_LIB_OPTION_ENABLED='no'
  PTHREAD_LIB_OPTION_REQUESTED='no'
  PTHREAD_STATUS=''
  RANLIB='ranlib'
  RT_LDFLAGS=''
  RT_LIBS='-lrt '
  RT_STATUS='yes'
  SET_MAKE=''
  SHELL='/bin/bash'
  SQLITE3_CFLAGS=''
  SQLITE3_LIBS='-lsqlite3'
  SQLITE3_OPTION_ENABLED='yes'
  SQLITE3_OPTION_REQUESTED='yes'
  SQLITE_BACKUP_DEFAULTS_OPTION_ENABLED='no'
  SQLITE_BACKUP_DEFAULTS_OPTION_REQUESTED='no'
  STATIC_OPTION_ENABLED='no'
  STATIC_OPTION_REQUESTED='no'
  STRIP=''
  TAGLIB_CFLAGS=''
  TAGLIB_LIBS=''
  TAGLIB_OPTION_ENABLED=''
  TAGLIB_OPTION_REQUESTED=''
  TAGLIB_STATUS=''
  TAGLIB_VERSION=''
  TOMBDEBUG_OPTION_ENABLED=''
  TOMBDEBUG_OPTION_REQUESTED=''
  UPNPDEBUG_OPTION_ENABLED=''
  UPNPDEBUG_OPTION_REQUESTED=''
  VERSION='0.12.2'
  YOUTUBE_OPTION_ENABLED='yes'
  YOUTUBE_OPTION_REQUESTED='yes'
  ZLIB_CFLAGS=''
  ZLIB_LDFLAGS=''
  ZLIB_LIBS='-lz'
  ZLIB_STATUS='yes'
  ac_ct_AR='ar'
  ac_ct_CC='gcc'
  ac_ct_CXX='g++'
  acx_pthread_config=''
  am__EXEEXT_FALSE=''
  am__EXEEXT_TRUE=''
  am__fastdepCC_FALSE=''
  am__fastdepCC_TRUE='#'
  am__fastdepCXX_FALSE=''
  am__fastdepCXX_TRUE='#'
  am__include='include'
  am__isrc=''
  am__leading_dot='.'
  am__nodep=''
  am__quote=''
  am__tar='$${TAR-tar} chof - "$$tardir"'
  am__untar='$${TAR-tar} xf -'
  bindir='${exec_prefix}/bin'
  build='x86_64-pc-linux-gnu'
  build_alias='x86_64-linux-gnu'
  build_cpu='x86_64'
  build_os='linux-gnu'
  build_vendor='pc'
  datadir='${datarootdir}'
  datarootdir='${prefix}/share'
  docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
  dvidir='${docdir}'
  exec_prefix='NONE'
  host='x86_64-pc-linux-gnu'
  host_alias=''
  host_cpu='x86_64'
  host_os='linux-gnu'
  host_vendor='pc'
  htmldir='${docdir}'
  includedir='${prefix}/include'
  infodir='${prefix}/share/info'
  install_sh='${SHELL} 
/home/lamby/temp/cdt.20161116210630.psKfUnjLkH.db.mediatomb/mediatomb-0.12.1-47-g7ab7616/configure_aux/install-sh'
  libdir='${prefix}/lib/x86_64-linux-gnu'
  libexecdir='${prefix}/lib/x86_64-linux-gnu'
  localedir='${datarootdir}/locale'
  localstatedir='/var'
  mandir='${prefix}/share/man'
  mkdir_p='$(MKDIR_P)'
  mt_mysql_config='/usr/bin/mysql_config'
  mt_taglib_config=''
  oldincludedir='/usr/include'
  pdfdir='${docdir}'
  prefix='/usr'
  program_transform_name='s,x,x,'
  psdir='${docdir}'
  runstatedir='${localstatedir}/run'
  sbindir='${exec_prefix}/sbin'
  sharedstatedir='${prefix}/com'
  sysconfdir='/etc'
  target_alias=''
  
  ## --- ##
  ## confdefs.h. ##
  ## --- ##
  
  /* confdefs.h */
  #define PACKAGE_NAME "MediaTomb"
  #define PACKAGE_TARNAME "mediatomb"
  #define PACKAGE_VERSION "0.12.2"
  #define PACKAGE_STRING "MediaTomb 0.12.2"
  #define PACKAGE_BUGREPORT "j...@mediatomb.cc"
  #define PACKAGE_URL ""
  #define PACKAGE "mediatomb"
  #define VERSION "0.12.2"
  #define ATOMIC_X86_SMP 1
  #define ENABLE_SIGHUP 1
  #define EXTEND_PROTOCOLINFO 1
  #define UPNP_VERSION_STRING "0.12.2"
  

Bug#844549: network-console broken: no screen to be resumed matching sh

[Martin Michlmayr]

Package: rootskel
Version: 1.119
Severity: serious
Tags: patch

Several users have reported to me that the network-console images are
broken.

Commit ec6d3c3d79 (Move screen support) moved the screen support
around and also changed the logic of when screen is used.
Unfortunately, that change broke all network-console images which now
lead to:

installer@192.168.0.102's password:
There is no screen to be resumed matching sh.
Connection to 192.168.0.102 closed.

This is because d-i is already running in screen on the serial console but
it's active and can't be resumed.

I believe below is the right fix, i.e. start screen when screen exists and
when we're on serial or when we're NOT on network.

Samuel, Roger, does that look correct?

diff --git a/src/lib/debian-installer.d/S70menu 
b/src/lib/debian-installer.d/S70menu
index 7b35fac..14cad7f 100644
--- a/src/lib/debian-installer.d/S70menu
+++ b/src/lib/debian-installer.d/S70menu
@@ -11,7 +11,7 @@ if [ -x "$bterm" ] && [ -e "$font" ] && [ -n "$TERM_UTF8" ] 
&& [ -n "$TERM_FRAME
set -e
 else
rm -f $font
-   if [ -x "$screen_bin" -a \( "$TERM_TYPE" = network -o "$TERM_TYPE" = 
serial \) -a "$TERM" != dumb ]; then
+   if [ -x "$screen_bin" -a \( "$TERM_TYPE" != network -o "$TERM_TYPE" = 
serial \) -a "$TERM" != dumb ]; then
# there's GNU/screen binary, run menu in it.
# call this script again with in GNU/screen, possibly in UTF-8 
mode
SCREEN_OPT=""

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#844544: marked as done (chromium: Window clipped over x11 (PuTTY + XMing))

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 14:50:43 -0500
with message-id <019901d24042$b7a85fd0$26f91f70$@yahoo.com>
and subject line Fixed: not a bug
has caused the Debian Bug report #844544,
regarding chromium: Window clipped over x11 (PuTTY + XMing)
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.)


-- 
844544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 53.0.2785.143-1~deb8u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

Starting chromium in a fowarded X11 session clips the window when I
attempt to resize it. After resizing, only a quarter of chromium is
visible, the rest of the client window is black, and unresponsive to
mouse clicks.

Client is PuTTY 0.67 with XMing 7.7.07 on Windows 7 Ultimate x86_64

I expect the chromium application to size itself to the client window.

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

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

Versions of packages chromium depends on:
ii  libasound2   1.0.28-1
ii  libatk1.0-0  2.14.0-1
ii  libc62.19-18+deb8u6
ii  libcairo21.14.0-2.1+deb8u1
ii  libcups2 1.7.5-11+deb8u1
ii  libdbus-1-3  1.8.20-0+deb8u1
ii  libexpat12.1.0-6+deb8u3
ii  libfontconfig1   2.11.0-6.3+deb8u1
ii  libfreetype6 2.5.2-3+deb8u1
ii  libgcc1  1:4.9.2-10
ii  libgdk-pixbuf2.0-0   2.31.1-2+deb8u5
ii  libglib2.0-0 2.42.1-1+b1
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk2.0-0  2.24.25-3+deb8u1
ii  libjpeg62-turbo  1:1.3.1-12
ii  libnspr4 2:4.12-1+debu8u1
ii  libnss3  2:3.26-1+debu8u1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpci3  1:3.2.1-3
ii  libspeechd2  0.8-7
ii  libstdc++6   4.9.2-10
ii  libx11-6 2:1.6.2-3
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.1-2+b2
ii  libxi6   2:1.7.4-1+b2
ii  libxml2  2.9.1+dfsg1-5+deb8u3
ii  libxrandr2   2:1.4.2-1+b1
ii  libxrender1  1:0.9.8-1+b1
ii  libxslt1.1   1.1.28-2+deb8u2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+2
ii  xdg-utils1.1.0~rc1+git20111210-7.4

chromium recommends no packages.

Versions of packages chromium suggests:
pn  chromium-inspector  
pn  chromium-l10n   

-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,

  I erroneously reported in a bug in chromium.

The issue was resolved by restarting the XMing X server.

 

Thank you for your time,

  Steven G. Messervey

--- End Message ---

Bug#844160: [Pkg-openssl-devel] Bug#844160: openssl 1.1 and apache2

[Kurt Roeckx]

On Mon, Nov 14, 2016 at 03:06:44PM -0800, Russ Allbery wrote:
> Stefan Fritsch  writes:
> 
> > I must admit that I did not think of php when doing that change, sorry. 
> 
> > On the other hand, shibboleth-sp2 also build-depends on apache2-dev and 
> > there 
> > have been some indications that shibboleth won't be switching to openssl 
> > 1.1 
> > for stretch. See 
> > https://lists.debian.org/debian-release/2016/11/msg00024.html
> 
> It turns out that Shibboleth will be okay if Apache goes to 1.1.  The
> Shibboleth code that goes into Apache is isolated from the OpenSSL use
> inside Shibboleth, so we can keep building Shibboleth against 1.0 and
> Apache can go to 1.1 and all the pieces are happy.  (The OpenSSL work is
> done in a separate daemon, shibd, that the Apache module talks to.)

So I looked at apache2-dev to see why it depends on libssl-dev.
The only thing I can find is that mod_ssl_openssl.h provides some
hooks, and you actually get SSL_CTX * and SSL * in there. But
nothing in Debian seems to include that file.


Kurt

Processed: tagging 844546

[Debian Bug Tracking System]

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

> tags 844546 + upstream fixed-upstream
Bug #844546 [teeworlds] teeworlds: possible remote code execution on the client
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#844515: [pkg-go] Bug#844515: packer: FTBFS on s390x (go install -v -p 1 died with signal 4)

[Michael Hudson-Doyle]

This is the "golang for s390x only works on z196+, not z10" thing. The
right fix is probably to not build golang on Debian, sadly.

On 17 November 2016 at 01:40, Daniel Stender 
wrote:

> Package: packer
> Version: 0.10.1+dfsg-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the
> past)
>
> Packer currently (recently 0.10.2+dfsg-1) fails to build on s390x:
>
> 
>dh_auto_build -O--buildsystem=golang
> cd obj-s390x-linux-gnu
> go install -v -p 1
> dh_auto_build: go install -v -p 1 died with signal 4
> cd /<>/packer-0.10.2+dfsg
> debian/rules:6: recipe for target 'build' failed
> make: *** [build] Error 255
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> 
>
> This is a regression from 0.10.1+dfsg-1 [1] (the build on 2016-10-16 [2]
> failed
> for a dependency reason which is solved in the meanwhile, see #841605 [3]).
>
> [1] https://buildd.debian.org/status/logs.php?pkg=packer=s390x
>
> [2] https://buildd.debian.org/status/fetch.php?pkg=packer;
> arch=s390x=0.10.1%2Bdfsg-1=1476596269
>
> [3] https://bugs.debian.org/841605 (packer: FTBFS: src/
> github.com/Azure/go-autorest/autorest/azure/token.go:140: undefined:
> jwt.MapClaims)
>
> I can reproduce this locally in a qemu-chroot for Sbuild, however a test
> build on
> the zelenka porterbox succeeded:
>
> 
> {...}
> dpkg-deb: building package 'golang-github-mitchellh-packer-dev' in
> '../golang-github-mitchellh-packer-dev_0.10.2+dfsg-1_all.deb'.
> dpkg-deb: building package 'packer' in '../packer_0.10.2+dfsg-1_
> s390x.deb'.
>  dpkg-genbuildinfo
> dpkg-genbuildinfo: warning: File::FcntlLock not available; using flock
> which is not NFS-safe
>  dpkg-genchanges  >../packer_0.10.2+dfsg-1_s390x.changes
> dpkg-genchanges: info: including full source code in upload
>  dpkg-source --after-build packer-0.10.2+dfsg
> dpkg-buildpackage: info: full upload (original source is included)
> (sid_s390x-dchroot)stender@zelenka:~/sandbox/packer-0.10.2+dfsg$
> 
>
> Thanks for hints,
> DS
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (500, 'testing'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages packer depends on:
> ii  libc6  2.24-5
>
> Versions of packages packer recommends:
> pn  docker.io  
> ii  qemu   1:2.7+dfsg-3+b1
>
> Versions of packages packer suggests:
> ii  ansible  2.1.1.0-1
> pn  chef 
>
> -- no debconf information
>
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>

Bug#844546: teeworlds: possible remote code execution on the client

[Felix Geyer]

Package: teeworlds
Version: 0.6.1+dfsg-1
Severity: grave
Tags: security
Justification: user security hole

teeworlds upstream has released version 0.6.4.

https://www.teeworlds.com/?page=news=12086 says

> the security vulnerability is worse, attacker controlled memory-writes and
> possibly arbitrary code execution on the client, abusable by any server the
> client joins

The upstream fix:
https://github.com/teeworlds/teeworlds/commit/ff254722a2683867fcb3e67569ffd36226c4bc62

There doesn't seem to be a CVE assigned to this vulnerability.

Felix

Bug#844486: gnuplot-qt: Mismatch between the program and library build versions with GNUTERM=wxt

[Anton Gladky]

block 844486 by 844526
thanks

wxwidget should be binnmued to fix the bug properly.

Cheers

Anton


2016-11-16 11:11 GMT+01:00 Vincent Lefevre :
>> (Set to serious as I believe that the ABI mismatch may yield obscure
>> bugs and should be solved before the next stable release.)
>
> More generally, isn't there anything missing in the build dependency
> rules to avoid this mismatch?

Processed: Re: Bug#844486: gnuplot-qt: Mismatch between the program and library build versions with GNUTERM=wxt

[Debian Bug Tracking System]

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

> block 844486 by 844526
Bug #844486 [gnuplot-qt] gnuplot-qt: Mismatch between the program and library 
build versions with GNUTERM=wxt
844486 was not blocked by any bugs.
844486 was not blocking any bugs.
Added blocking bug(s) of 844486: 844526
> thanks
Stopping processing here.

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

Bug#832876: marked as done (snapd: FTBFS: build-dependency not installable: golang-pb-dev)

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 11:01:20 -0800
with message-id <20161116190120.ga3kx46rpczz7...@virgil.dodds.net>
and subject line Re:  snapd: FTBFS: build-dependency not installable: 
golang-pb-dev
has caused the Debian Bug report #832876,
regarding snapd: FTBFS: build-dependency not installable: golang-pb-dev
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.)


-- 
832876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: snapd
Version: 2.0.8+1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> ┌──┐
> │ Install snapd build dependencies (apt-based resolver)   
>  │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-snapd-dummy : Depends: golang-pb-dev but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/07/28/snapd_2.0.8+1_unstable.log

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

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

This was fixed in the 2.16-1 upload.

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


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

Bug#844227: FTBFS on mips*, ./.libs/libmutter-cogl.so: undefined reference to `eglQueryString'

[Michael Biebl]

Am 15.11.2016 um 14:03 schrieb Andreas Boll:
> On Mon, Nov 14, 2016 at 06:47:00PM +0100, Michael Biebl wrote:
>> Am 13.11.2016 um 19:43 schrieb Michael Biebl:
>>> Am 13.11.2016 um 18:37 schrieb Sven Joachim:
 The toolchain has also changed quite a bit in the past four weeks, with
 gcc having pie enabled by default and binutils at a bleeding edge
 snapshot.  Maybe one of those has triggered the build failure.
>>>
>>> That might well be it. Currently mutter still builds fine in stretch.
>>> The new binutils should migrate to testing soon.
>>> I can then retry the build on a mips porter machine with
>>> 2.27.51.20161108-1
>>
>> binutils 2.27.51.20161108-1 just migrated to stretch. mutter still
>> builds fine in stretch with this version. So I'd say we can cross off
>> binutils from the list of suspects.
> 
> As Sven already mentioned these symbols are still available otherwise
> Mesa would FTBFS as we strictly check those symbols in the build with
> 
> override_dh_makeshlibs:
> dh_makeshlibs -a -- -c4
> 
> Furthermore I've manually checked libegl1-mesa_12.0.4-2_mips.deb [1]
> with nm that those symbols are still exported.
> 
> Mesa could be still affected by a broken binutils. To cross out
> binutils or other toolchain bugs we would need to rebuild Mesa
> 12.0.3-3 (= version in testing) with the current toolchain and build
> mutter against this rebuild of Mesa.
> Michael, could you check this on a mips porter machine?
> 

Unfortunately I can't install arbitrary versions on the porter boxes.
All I get is either a sid or a stretch chroot.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#843988: stunnel4 segfaults (client mode)

[Peter Pentchev]

control: tag -1 + pending

On Tue, Nov 15, 2016 at 05:06:24PM +0100, gregor herrmann wrote:
> On Tue, 15 Nov 2016 13:39:21 +0100, Sebastian Andrzej Siewior wrote:
> 
> > On 2016-11-14 22:43:16 [+0100], gregor herrmann wrote:
> > > Yay, this looks good!
> > So upstream came up with the patch attached after I forwaded mine. Can
> > you please confirm whether this works or not?
> 
> Confirmed: I don't see any crashes with this patch applied.
> Thanks.

Thanks a lot to both of you!  I've added the patch to the stunnel4
Debian package repository; an upload should be forthcoming soon.
(I'll drop a note to my comaintainer and sponsor, László Böszörményi,
once I get the mentors.d.n upload notification)

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@freebsd.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Processed: Re: Bug#843988: stunnel4 segfaults (client mode)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #843988 [stunnel4] stunnel4 segfaults (client mode)
Added tag(s) pending.

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

Processed: Re: Bug#844491: linux-atm: FTBFS: time.h:9:8: error: redefinition of 'struct timespec'

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 linux-libc-dev 4.8.5-1
Bug #844491 [src:linux-atm] linux-atm: FTBFS: time.h:9:8: error: redefinition 
of 'struct timespec'
Bug reassigned from package 'src:linux-atm' to 'linux-libc-dev'.
No longer marked as found in versions linux-atm/1:2.5.1-1.6.
Ignoring request to alter fixed versions of bug #844491 to the same values 
previously set
Bug #844491 [linux-libc-dev] linux-atm: FTBFS: time.h:9:8: error: redefinition 
of 'struct timespec'
Marked as found in versions linux/4.8.5-1.
> retitle -1 linux/atm_zatm.h change breaks time.h inclusion
Bug #844491 [linux-libc-dev] linux-atm: FTBFS: time.h:9:8: error: redefinition 
of 'struct timespec'
Changed Bug title to 'linux/atm_zatm.h change breaks time.h inclusion' from 
'linux-atm: FTBFS: time.h:9:8: error: redefinition of 'struct timespec''.
> tags -1 fixed-upstream patch
Bug #844491 [linux-libc-dev] linux/atm_zatm.h change breaks time.h inclusion
Added tag(s) patch and fixed-upstream.

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

Processed: And add the missing affects

[Debian Bug Tracking System]

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

> affects 844491 src:linux-atm
Bug #844491 [linux-libc-dev] linux/atm_zatm.h change breaks time.h inclusion
Added indication that 844491 affects src:linux-atm
> thanks
Stopping processing here.

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

Bug#844491: linux-atm: FTBFS: time.h:9:8: error: redefinition of 'struct timespec'

[Adrian Bunk]

Control: reassign -1 linux-libc-dev 4.8.5-1
Control: retitle -1 linux/atm_zatm.h change breaks time.h inclusion
Control: tags -1 fixed-upstream patch

On Wed, Nov 16, 2016 at 09:46:03AM +, Chris Lamb wrote:
>...
>   In file included from /usr/include/linux/atm_zatm.h:17:0,
>from zntune.c:17:
>   /usr/include/linux/time.h:9:8: error: redefinition of 'struct timespec'
>struct timespec {
>   ^~~~
>   In file included from /usr/include/x86_64-linux-gnu/sys/select.h:45:0,
>from /usr/include/x86_64-linux-gnu/sys/types.h:219,
>from /usr/include/stdlib.h:275,
>from zntune.c:9:
>   /usr/include/time.h:120:8: note: originally defined here
>struct timespec
>...

Thanks for your report, this is a bug in the kernel userspace headers.

I've attached the fix that was applied upstream.

> Regards,

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

commit 7b5b74efcca00f15c2aec1dc7175bfe34b6ec643
Author: Mike Frysinger 
Date:   Thu Nov 10 19:08:39 2016 -0500

Revert "include/uapi/linux/atm_zatm.h: include linux/time.h"

This reverts commit cf00713a655d ("include/uapi/linux/atm_zatm.h: include
linux/time.h").

This attempted to fix userspace breakage that no longer existed when
the patch was merged.  Almost one year earlier, commit 70ba07b675b5
("atm: remove 'struct zatm_t_hist'") deleted the struct in question.

After this patch was merged, we now have to deal with people being
unable to include this header in conjunction with standard C library
headers like stdlib.h (which linux-atm does).  Example breakage:
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I./../q2931 
-I./../saal \
-I.  -DCPPFLAGS_TEST  -I../../src/include -O2 -march=native -pipe 
-g \
-frecord-gcc-switches -freport-bug -Wimplicit-function-declaration \
-Wnonnull -Wstrict-aliasing -Wparentheses -Warray-bounds \
-Wfree-nonheap-object -Wreturn-local-addr -fno-strict-aliasing 
-Wall \
-Wshadow -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -c 
zntune.c
In file included from /usr/include/linux/atm_zatm.h:17:0,
 from zntune.c:17:
/usr/include/linux/time.h:9:8: error: redefinition of ‘struct timespec’
 struct timespec {
^
In file included from /usr/include/sys/select.h:43:0,
 from /usr/include/sys/types.h:219,
 from /usr/include/stdlib.h:314,
 from zntune.c:9:
/usr/include/time.h:120:8: note: originally defined here
 struct timespec
^

Signed-off-by: Mike Frysinger 
Acked-by: Mikko Rapeli 
Signed-off-by: David S. Miller 

diff --git a/include/uapi/linux/atm_zatm.h b/include/uapi/linux/atm_zatm.h
index 5cd4d4d..9c9c6ad 100644
--- a/include/uapi/linux/atm_zatm.h
+++ b/include/uapi/linux/atm_zatm.h
@@ -14,7 +14,6 @@
 
 #include 
 #include 
-#include 
 
 #define ZATM_GETPOOL   _IOW('a',ATMIOC_SARPRV+1,struct atmif_sioc)
/* get pool statistics */

Bug#844544: chromium: Window clipped over x11 (PuTTY + XMing)

[Steven G. Messervey]

Package: chromium
Version: 53.0.2785.143-1~deb8u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

Starting chromium in a fowarded X11 session clips the window when I
attempt to resize it. After resizing, only a quarter of chromium is
visible, the rest of the client window is black, and unresponsive to
mouse clicks.

Client is PuTTY 0.67 with XMing 7.7.07 on Windows 7 Ultimate x86_64

I expect the chromium application to size itself to the client window.

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

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

Versions of packages chromium depends on:
ii  libasound2   1.0.28-1
ii  libatk1.0-0  2.14.0-1
ii  libc62.19-18+deb8u6
ii  libcairo21.14.0-2.1+deb8u1
ii  libcups2 1.7.5-11+deb8u1
ii  libdbus-1-3  1.8.20-0+deb8u1
ii  libexpat12.1.0-6+deb8u3
ii  libfontconfig1   2.11.0-6.3+deb8u1
ii  libfreetype6 2.5.2-3+deb8u1
ii  libgcc1  1:4.9.2-10
ii  libgdk-pixbuf2.0-0   2.31.1-2+deb8u5
ii  libglib2.0-0 2.42.1-1+b1
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk2.0-0  2.24.25-3+deb8u1
ii  libjpeg62-turbo  1:1.3.1-12
ii  libnspr4 2:4.12-1+debu8u1
ii  libnss3  2:3.26-1+debu8u1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpci3  1:3.2.1-3
ii  libspeechd2  0.8-7
ii  libstdc++6   4.9.2-10
ii  libx11-6 2:1.6.2-3
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.1-2+b2
ii  libxi6   2:1.7.4-1+b2
ii  libxml2  2.9.1+dfsg1-5+deb8u3
ii  libxrandr2   2:1.4.2-1+b1
ii  libxrender1  1:0.9.8-1+b1
ii  libxslt1.1   1.1.28-2+deb8u2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+2
ii  xdg-utils1.1.0~rc1+git20111210-7.4

chromium recommends no packages.

Versions of packages chromium suggests:
pn  chromium-inspector  
pn  chromium-l10n   

-- no debconf information

Bug#820693: marked as done (gdebi: Add flakes8 Build-Depends to fix FTBFS)

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 17:48:37 +
with message-id 
and subject line Bug#820693: fixed in gdebi 0.9.5.7+nmu1
has caused the Debian Bug report #820693,
regarding gdebi: Add flakes8 Build-Depends to fix FTBFS
to be marked as done.

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

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


-- 
820693: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gdebi
Version: 0.9.5.7
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

pyflakes has been split with /usr/bin scripts in separate binary
packages for Python 2 and 3.  This causes gdebi to FTBFS because it
can't find pyflakes3.  A simple addition of pyflakes3 to Build-Depends
will fix the problem.

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

Kernel: Linux 4.4.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gdebi depends on:
ii  gdebi-core0.9.5.7
ii  gir1.2-gtk-3.03.18.9-1
ii  gir1.2-vte-2.91   0.44.0-1
ii  gksu  2.0.2-9
ii  gnome-icon-theme  3.12.0-1
ii  python3-gi3.18.2-2+b1
pn  python3:any   

Versions of packages gdebi recommends:
ii  libgtk2-perl  2:1.2498-1
ii  lintian   2.5.43
ii  shared-mime-info  1.5-2

gdebi suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXC6bWAAoJEBJutWOnSwa/ywsQAKvowRpvQSl487SAPF56T2Cp
O4H+8LTeI3WUHN1LFyDLUCt/JJrKqC4+hkGQhtMmwhXbdNmefCQVFkMhRpWZp9lQ
2ulm6UWZs9SxHxxGYzemCo4zS5TnWMonbeBYiO9pddTkur/7G/F8L0joRGYcxN6z
7vbdPKPrN48wbH8HWFDBst4SV5OuEBvnOyhpdyOEFJ9yQLD84ufsArYLSfarkaYc
kdDerD0WR0E042u8P8WgxaJY3dT668ZBQqF28mdnCP/Ym9p+h43pvuXmN1qm6s1z
Uh8KGmx8FLxGzStEyrgd5cW628zYI/sM7ZROQe2nLTl/79VPBRaTqQbDeLQp43Sc
o5jV+3bngeJ6pqak1oWx91yD/e/q40nZODn32TVNcWVvW+WwfAOjfUbneL7BaxKY
uArSauKiiSgbBjUXlFGyAMPzWn085VgRLtfgcwtRVq8qPozMiLtTVPU1My64xTS/
3ZccAMaMYpLKZ8+dfUTMLKDcd4QauajifiaEraL0GUiweUJhtj/SUBWtGmHFaY2C
o8tAmXpogKhLri//GqxIzuNiZVsJTtuFWcnOKwDiVK+YN7e97NBeCKHWusmT0RRe
yZfnrBxKAQRTWtfKuYoJq+b/arg+N6YrE0N2Ogz/rXFQQThfbeoVKBzNkw87DgwB
E3vCtKArWB7OvNH88EfM
=uCXP
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: gdebi
Source-Version: 0.9.5.7+nmu1

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

Debian distribution maintenance software
pp.
Jonathan Wiltshire  (supplier of updated gdebi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Nov 2016 17:04:19 +
Source: gdebi
Binary: gdebi-core gdebi gdebi-kde
Architecture: source all
Version: 0.9.5.7+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Ubuntu Developers 
Changed-By: Jonathan Wiltshire 
Description:
 gdebi  - simple tool to view and install deb files - GNOME GUI
 gdebi-core - simple tool to install deb files
 gdebi-kde  - simple tool to install deb files - KDE GUI
Closes: 820693
Changes:
 gdebi (0.9.5.7+nmu1) unstable; urgency=medium
 .
   [ Petter Reinholdtsen ]
   * Non-maintainer upload.
   * Fix build dependencies, add pyflakes3 needed after package split
 (Closes: #820693).
Checksums-Sha1:
 5e972b4566bae89a5d9fc31adf7bea6f44dd7cc8 1778 gdebi_0.9.5.7+nmu1.dsc
 088f2335cc64c8414995b1d8d2897ee9ccac47ea 190892 gdebi_0.9.5.7+nmu1.tar.xz
 ec23d9175e2ba1bf31696a373f599ed733097e7c 133588 gdebi-core_0.9.5.7+nmu1_all.deb
 7b7eaa077a03ece330e213fc8b683dece86878cf 29356 gdebi-kde_0.9.5.7+nmu1_all.deb
 bb4f37f01af95144f10f41e18b4312b89d078879 11371 
gdebi_0.9.5.7+nmu1_2016T170918z-27c8a3c2.buildinfo
 85987672761e1f1525127931fceb2064a2c29064 40378 gdebi_0.9.5.7+nmu1_all.deb
Checksums-Sha256:
 9f7a6984ed35064dcf2dc3900e154d05c36ac5cbfebb38365cfa43b5d32cb703 1778 
gdebi_0.9.5.7+nmu1.dsc
 

Bug#844538: libdbd-mysql-perl: FTBFS on some architectures

[Salvatore Bonaccorso]

Source: libdbd-mysql-perl
Version: 4.039-1
Severity: serious
Justification: FTBFS on some release architectures

Hi

libdbd-mysql-perl FTBFS on some architectures, namely mips and s390x
for the release architectures:

https://buildd.debian.org/status/package.php?p=libdbd-mysql-perl

https://buildd.debian.org/status/fetch.php?pkg=libdbd-mysql-perl=mips=4.039-1=1479285659
https://buildd.debian.org/status/fetch.php?pkg=libdbd-mysql-perl=s390x=4.039-1=1479285790

Regards,
Salvatore

Bug#844139: python-django: FTBFS: Tests failures

[Raphael Hertzog]

Hi,

On Sat, 12 Nov 2016, Scott Kitterman wrote:
> > This failure happens on a CPU with TSX extensions available, but is not
> > reproducible on a machine without them. 

I can't reproduce this either on my machine. But I have other failures
(see below).

Lucas, can you see if you reproduce your problem with this small
patch:
--- a/debian/rules
+++ b/debian/rules
@@ -23,7 +23,7 @@ override_dh_auto_test:
 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
set -e; cd tests && for python in $$(pyversions -s) $$(py3versions -s); 
do \
echo "——— Running tests with $$python ———"; \
-   LC_ALL=C.UTF-8 PYTHONPATH=.. $$python ./runtests.py 
--verbosity=2; \
+   LC_ALL=C.UTF-8 PYTHONPATH=.. $$python ./runtests.py 
--verbosity=2 --parallel=4; \
done
 endif
 
My failures:
==
ERROR: test_command_help (i18n.test_compilation.ExcludedLocaleCompilationTests)
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 320, in run
self.setUp()
  File "/<>/tests/i18n/test_compilation.py", line 124, in setUp
shutil.copytree('canned_locale', 'locale')
  File "/usr/lib/python2.7/shutil.py", line 177, in copytree
os.makedirs(dst)
  File "/usr/lib/python2.7/os.py", line 157, in makedirs
mkdir(name, mode)
OSError: [Errno 17] File exists: 'locale'

==
ERROR: test_multiple_locales_excluded 
(i18n.test_compilation.ExcludedLocaleCompilationTests)
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 320, in run
self.setUp()
  File "/<>/tests/i18n/test_compilation.py", line 124, in setUp
shutil.copytree('canned_locale', 'locale')
  File "/usr/lib/python2.7/shutil.py", line 177, in copytree
os.makedirs(dst)
  File "/usr/lib/python2.7/os.py", line 157, in makedirs
mkdir(name, mode)
OSError: [Errno 17] File exists: 'locale'

==
ERROR: test_multiple_locales_excluded_with_locale 
(i18n.test_compilation.ExcludedLocaleCompilationTests)
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 320, in run
self.setUp()
  File "/<>/tests/i18n/test_compilation.py", line 124, in setUp
shutil.copytree('canned_locale', 'locale')
  File "/usr/lib/python2.7/shutil.py", line 177, in copytree
os.makedirs(dst)
  File "/usr/lib/python2.7/os.py", line 157, in makedirs
mkdir(name, mode)
OSError: [Errno 17] File exists: 'locale'

==
ERROR: test_one_locale_excluded 
(i18n.test_compilation.ExcludedLocaleCompilationTests)
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 320, in run
self.setUp()
  File "/<>/tests/i18n/test_compilation.py", line 124, in setUp
shutil.copytree('canned_locale', 'locale')
  File "/usr/lib/python2.7/shutil.py", line 177, in copytree
os.makedirs(dst)
  File "/usr/lib/python2.7/os.py", line 157, in makedirs
mkdir(name, mode)
OSError: [Errno 17] File exists: 'locale'

==
ERROR: test_one_locale_excluded_with_locale 
(i18n.test_compilation.ExcludedLocaleCompilationTests)
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 320, in run
self.setUp()
  File "/<>/tests/i18n/test_compilation.py", line 124, in setUp
shutil.copytree('canned_locale', 'locale')
  File "/usr/lib/python2.7/shutil.py", line 177, in copytree
os.makedirs(dst)
  File "/usr/lib/python2.7/os.py", line 157, in makedirs
mkdir(name, mode)
OSError: [Errno 17] File exists: 'locale'

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

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

Bug#844458: bootstrap-base: if debootstrap_script is unset, DEBOOTSTRAP_SCRIPT is set to a directory, breaking the install

[Philip Hands]

Cyril Brulebois  writes:

> Control: severity -1 serious
> Control: tag -1 - d-i
>
> Philip Hands  (2016-11-16):
>> Package: bootstrap-base
>> Version: 1.166
>> Severity: important
>> Tags: d-i patch
>> 
>> While testing the daily images, I get this:
>> 
>>   
>> https://jenkins.debian.net/view/lvc/job/lvc_debian-testing-daily/516/artifact/results//00:03:05___gui___minimal___VT__.png
>
> Screenshots don't make it easy/possible to search inside bug reports (and
> mails), and triage bug reports, so it would be nice to include messages
> directly there.

My apologies -- I became over-excited by the fact that this bug was
found by cucumber running on jenkins.debian.net (which is a first!).
I was effectively trying to give it credit.

For posterity (and because at some point that screenshot will probably
get deleted) it said:

=-=-=-=-
  /Base system installation error/

  The debootstrap program exited with an error (return code 127)

  Check /var/log/syslog or see virtual console 4 for details.
=-=-=-=-

(looking at syslog didn't actually shed a great deal of light though,
since it referenced a line number that didn't really indicate the cause
of the problem, or even the file where the error had occured, so rather
than quote all that, I just jumped straight to fixing the bug.  That
being the case, the screenshot was really only there as evidence that
there was a problem, rather than being very useful for diagnosis)

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#833216: marked as done (fluid-soundfont: Uses obsolete compressor for .deb data.tar member)

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 16:49:52 +
with message-id 
and subject line Bug#833216: fixed in fluid-soundfont 3.1-5.1
has caused the Debian Bug report #833216,
regarding fluid-soundfont: Uses obsolete compressor for .deb data.tar member
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.)


-- 
833216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fluid-soundfont
Source-Version: 3.1-5
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-obsolete-deb-data-tar-compressor

Hi!

This source package builds one or more binary packages using the
deprecated compressor bzip2. The default has been xz for a while now
which should usually compress better than bzip2. If instead you'd like
speed then switch to use gzip.

Using a deprecated compressor when building binary packages will
become an error in the near future. Please update the packages.

See also .

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: fluid-soundfont
Source-Version: 3.1-5.1

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

Debian distribution maintenance software
pp.
Jonathan Wiltshire  (supplier of updated fluid-soundfont 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Nov 2016 15:58:00 +
Source: fluid-soundfont
Binary: fluid-soundfont-gm fluid-soundfont-gs
Architecture: source all
Version: 3.1-5.1
Distribution: unstable
Urgency: medium
Maintainer: Toby Smithe 
Changed-By: Jonathan Wiltshire 
Description:
 fluid-soundfont-gm - Fluid (R3) General MIDI SoundFont (GM)
 fluid-soundfont-gs - Fluid (R3) General MIDI SoundFont (GS)
Closes: 833216
Changes:
 fluid-soundfont (3.1-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Do not specify bzip2 compressor to dh_builddeb
 (Closes: #833216)
Checksums-Sha1:
 1a2236a6b6a9b49fa775a413e5260ba6cff9acd8 1746 fluid-soundfont_3.1-5.1.dsc
 8d04d03c6ec8f28a5ab9713aabda24dce5da5d0e 21344 fluid-soundfont_3.1-5.1.diff.gz
 3a6961d27c4e62672b98ff127cb6aff774c6aa8f 119627278 
fluid-soundfont-gm_3.1-5.1_all.deb
 db5976d2ed868890d570dca632864cbf0a7e6bf9 2474010 
fluid-soundfont-gs_3.1-5.1_all.deb
 585aa4447cffe594b43fb2c22a84c01e5a441c49 4669 
fluid-soundfont_3.1-5.1_2016T160103z-f2e19fb4.buildinfo
Checksums-Sha256:
 4a4753a35b18f5acbb584e7adc20a68de7091271a46ce75c44615209102c0445 1746 
fluid-soundfont_3.1-5.1.dsc
 307fd3f7f71384c102f4c10e39de4216af59c974308fd153187b253923180cf7 21344 
fluid-soundfont_3.1-5.1.diff.gz
 401b4100020ce5dfecb1d93922f545b93dec1c9f02d274834e0c4f35d032 119627278 
fluid-soundfont-gm_3.1-5.1_all.deb
 bb1fe8e5f1c531e19a0278214b11b39ceabc7fe96d75f2aade0316aaae2ce809 2474010 
fluid-soundfont-gs_3.1-5.1_all.deb
 d4950c785be23cb5aff92c862543a5d38f58362dd13e3d7e007ef4111b0e903a 4669 
fluid-soundfont_3.1-5.1_2016T160103z-f2e19fb4.buildinfo
Files:
 0f0644e5b7b165f74b2fd83cbd4c556f 1746 sound optional 
fluid-soundfont_3.1-5.1.dsc
 fe80bcda601873168d27779013c3c42f 21344 sound optional 
fluid-soundfont_3.1-5.1.diff.gz
 188c4d2bc5613b551a56a4e377d6e67c 119627278 sound optional 
fluid-soundfont-gm_3.1-5.1_all.deb
 1b8c3118b182c60121d883b8f5cda9ba 2474010 sound optional 
fluid-soundfont-gs_3.1-5.1_all.deb
 f2e19fb4a9e14d1884a51d0615279758 4669 sound optional 
fluid-soundfont_3.1-5.1_2016T160103z-f2e19fb4.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYJevkAAoJEETTKrX6JvjJkdcQALRVFN5Pgjh4rQ2Tz336WgDn
z5EYvNHnEgCosepsuLOpzdonC1oW5IhLqtXiQGwSlenRfnYRFwMl/THQKfIIYI5F
9zQeny8mE15lChz8MzP/zPfo+k27ExSW9D6zy827thSdvq4SugzbquTxgvAD50Vl
ZYhHiJ+74fDJTTfHWlydAjY/m6duY2mNv9dFut5ypyCsFhzF58z5qD9o2C6wmCjf
PAi7tybzbF+nHt0lM8HewhRMxREDrcrd5VtRpEZCy7O17EyMJdRcF1fcx+Dps5c3
pbAP6uE1ZwAyZjstZryb/kpzhvHF3Jgii/NoGn5ypzLWeT+6f5UpO9gA4wfhvVpC
hiNQBJBtgbKi/h9LSmJYzbsGwg18Y7zw7yp2FEQqVEux5vbjg2xrS6Q+0JMjPl2S

Bug#844393: blhc still uses dpkg architecture triplets

[Jari Aalto]

On 2016-11-16 12:46, Simon Ruderich wrote:
| On Tue, Nov 15, 2016 at 08:47:41AM +0100, Johannes Schauer wrote:
| > Hi,
| >
| > recently, dpkg switched from the triplettable to architecture
| > quadruplets. When now trying to run blhc with the new libdpkg-perl, one
| > will get:
| >
| > Undefined subroutine ::Arch::debarch_to_debtriplet called at 
/usr/bin/blhc line 1032.
| 
| Hello,
| 
| Fixed in bf41976 [1].
| 
| Jari, could you please cherry-pick this commit and apply it to
| the Debian package.

Will do, thanks Simon.

Jari

Bug#844533: d-feet: FTBFS: tests/tests.py:105:1: E305 expected 2 blank lines after class or function definition, found 1

[Chris Lamb]

Source: d-feet
Version: 0.3.11-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

d-feet fails to build from source in unstable/amd64:

  […]

  pep8 --max-line-length=99 --ignore=E123,E402 
--exclude='.svn,CVS,.bzr,.hg,.git,__pycache__,.#*' ../../src/
  ../../src/tests/tests.py:105:1: E305 expected 2 blank lines after class or 
function definition, found 1
  Makefile:820: recipe for target 'check-local' failed
  make[5]: *** [check-local] Error 1
  make[5]: Leaving directory 
'/home/lamby/temp/cdt.20161116173756.dheYweAuB8.db.d-feet/d-feet-0.3.11/src/tests'
  Makefile:698: recipe for target 'check-am' failed
  make[4]: *** [check-am] Error 2
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20161116173756.dheYweAuB8.db.d-feet/d-feet-0.3.11/src/tests'
  Makefile:445: recipe for target 'check-recursive' failed
  make[3]: *** [check-recursive] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20161116173756.dheYweAuB8.db.d-feet/d-feet-0.3.11/src'
  Makefile:389: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20161116173756.dheYweAuB8.db.d-feet/d-feet-0.3.11'
  debian/rules:9: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20161116173756.dheYweAuB8.db.d-feet/d-feet-0.3.11'
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 2

  […]

The full build log is attached.


Regards,

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


d-feet.0.3.11-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#844534: uftp: FTBFS: encrypt_openssl.c:352:20: error: storage size of 'ctx' isn't known

[Chris Lamb]

Source: uftp
Version: 4.9.2-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

uftp fails to build from source in unstable/amd64:

  […]

make -j1
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20161116173956.JevpBpJbR0.db.uftp/uftp-4.9.2'
  cc -g -Wall -Wextra -Wno-unused-parameter -Wno-sign-compare -Wformat=2 
-Wwrite-strings -Wpointer-arith -Wcast-qual -Wshadow 
-Wno-missing-field-initializers -Wstrict-prototypes -Winline 
-Wbad-function-cast -DHAS_GETIFADDRS   -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161116173956.JevpBpJbR0.db.uftp/uftp-4.9.2=.
 -fstack-protector-strong -Wformat -Werror=format-security `getconf LFS_CFLAGS` 
 -c uftp_common.c
  uftp_common.c: In function 'multicast_join':
  uftp_common.c:1636:17: warning: 'level' may be used uninitialized in this 
function [-Wmaybe-uninitialized]
   if (setsockopt(s, level, MCAST_JOIN_GROUP,
   ^~
   (char *), sizeof(greq)) == -1) {
   
  uftp_common.c: In function 'multicast_leave':
  uftp_common.c:1700:21: warning: 'level' may be used uninitialized in this 
function [-Wmaybe-uninitialized]
   if (setsockopt(s, level, MCAST_LEAVE_SOURCE_GROUP,
   ^~
   (char *), sizeof(gsreq)) == -1) {
   ~~
  cc -g -Wall -Wextra -Wno-unused-parameter -Wno-sign-compare -Wformat=2 
-Wwrite-strings -Wpointer-arith -Wcast-qual -Wshadow 
-Wno-missing-field-initializers -Wstrict-prototypes -Winline 
-Wbad-function-cast -DHAS_GETIFADDRS   -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161116173956.JevpBpJbR0.db.uftp/uftp-4.9.2=.
 -fstack-protector-strong -Wformat -Werror=format-security `getconf LFS_CFLAGS` 
 -c encrypt_openssl.c
  encrypt_openssl.c: In function 'encrypt_block':
  encrypt_openssl.c:352:20: error: storage size of 'ctx' isn't known
   EVP_CIPHER_CTX ctx;
  ^~~
  encrypt_openssl.c:352:20: warning: unused variable 'ctx' [-Wunused-variable]
  encrypt_openssl.c: In function 'decrypt_block':
  encrypt_openssl.c:456:20: error: storage size of 'ctx' isn't known
   EVP_CIPHER_CTX ctx;
  ^~~
  encrypt_openssl.c:456:20: warning: unused variable 'ctx' [-Wunused-variable]
  encrypt_openssl.c: In function 'hash':
  encrypt_openssl.c:572:16: error: storage size of 'hashctx' isn't known
   EVP_MD_CTX hashctx;
  ^~~
  encrypt_openssl.c:582:9: warning: implicit declaration of function 
'EVP_MD_CTX_cleanup' [-Wimplicit-function-declaration]
   EVP_MD_CTX_cleanup();
   ^~
  encrypt_openssl.c:572:16: warning: unused variable 'hashctx' 
[-Wunused-variable]
   EVP_MD_CTX hashctx;
  ^~~
  In file included from /usr/include/openssl/asn1.h:24:0,
   from /usr/include/openssl/objects.h:916,
   from /usr/include/openssl/evp.h:27,
   from encrypt_openssl.c:39:
  encrypt_openssl.c: In function 'create_ECDSA_sig':
  encrypt_openssl.c:793:36: error: dereferencing pointer to incomplete type 
'ECDSA_SIG {aka struct ECDSA_SIG_st}'
   sval = rval + BN_num_bytes(_sig->r);
  ^
  encrypt_openssl.c: In function 'import_RSA_key':
  encrypt_openssl.c:926:16: error: dereferencing pointer to incomplete type 
'RSA {aka struct rsa_st}'
   if (((*rsa)->e = BN_bin2bn((const unsigned char *)>exponent,
  ^~
  In file included from /usr/include/openssl/asn1.h:24:0,
   from /usr/include/openssl/objects.h:916,
   from /usr/include/openssl/evp.h:27,
   from encrypt_openssl.c:39:
  encrypt_openssl.c: In function 'export_RSA_key':
  encrypt_openssl.c:954:25: error: dereferencing pointer to incomplete type 
'RSA {aka struct rsa_st}'
   if (BN_num_bytes(rsa->e) > sizeof(bin_exponent)) {
   ^
  encrypt_openssl.c: In function 'gen_RSA_key':
  encrypt_openssl.c:1078:5: warning: 'RSA_generate_key' is deprecated 
[-Wdeprecated-declarations]
   if ((rsa = RSA_generate_key(bits ? bits : DEF_RSA_LEN,
   ^~
  In file included from /usr/include/openssl/rsa.h:13:0,
   from encrypt_openssl.c:43:
  /usr/include/openssl/rsa.h:193:1: note: declared here
   DEPRECATEDIN_0_9_8(RSA *RSA_generate_key(int bits, unsigned long e, void
   ^
  makefile:195: recipe for target 'encrypt_openssl.o' failed
  make[1]: *** [encrypt_openssl.o] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20161116173956.JevpBpJbR0.db.uftp/uftp-4.9.2'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:7: recipe for target 'build' failed
  make: *** 

Bug#833211: marked as done (dvd+rw-tools: Uses obsolete compressor for .deb data.tar member)

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 15:48:40 +
with message-id 
and subject line Bug#833211: fixed in dvd+rw-tools 7.1-11.1
has caused the Debian Bug report #833211,
regarding dvd+rw-tools: Uses obsolete compressor for .deb data.tar member
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.)


-- 
833211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dvd+rw-tools
Source-Version: 7.1-11
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-obsolete-deb-data-tar-compressor

Hi!

This source package builds one or more binary packages using the
deprecated compressor bzip2. The default has been xz for a while now
which should usually compress better than bzip2. If instead you'd like
speed then switch to use gzip.

Using a deprecated compressor when building binary packages will
become an error in the near future. Please update the packages.

See also .

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: dvd+rw-tools
Source-Version: 7.1-11.1

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

Debian distribution maintenance software
pp.
Jonathan Wiltshire  (supplier of updated dvd+rw-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Nov 2016 15:11:36 +
Source: dvd+rw-tools
Binary: growisofs dvd+rw-tools dvd+rw-tools-dbg
Architecture: source amd64
Version: 7.1-11.1
Distribution: unstable
Urgency: medium
Maintainer: Optical Media Tools Team 

Changed-By: Jonathan Wiltshire 
Description:
 dvd+rw-tools - DVD+-RW/R tools
 dvd+rw-tools-dbg - DVD+-RW/R tools (debug)
 growisofs  - DVD+-RW/R recorder
Closes: 833211
Changes:
 dvd+rw-tools (7.1-11.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Do not specify bzip2 compressor to dh_builddeb
 (Closes: #833211)
Checksums-Sha1:
 9c35b079413794b5bdfce8e0e7e1e6c075fb593c 2164 dvd+rw-tools_7.1-11.1.dsc
 d7d16bf0b3a16c7d863ebcd9cbdec6ef29d21346 24447 
dvd+rw-tools_7.1-11.1.debian.tar.bz2
 0739e5ac92abd1bf38b62bc8cff64f9c03aedca1 22180 
dvd+rw-tools-dbg_7.1-11.1_amd64.deb
 87c2c5311b3420e83eb13744b5dacebb2a4eb3d2 4888 
dvd+rw-tools_7.1-11.1_2016T151250z-cc0e06bf.buildinfo
 ad1d814d8979a0eb738b6aac0ade56c2758cde18 86148 dvd+rw-tools_7.1-11.1_amd64.deb
 b5498316a6ec832eb36c1a9ef7619a7d02ee1a69 69804 growisofs_7.1-11.1_amd64.deb
Checksums-Sha256:
 ac9f763ba6b739f65b5f0b6acd7e91fd78192e8246a1b10ef0fe81c13fdc1be2 2164 
dvd+rw-tools_7.1-11.1.dsc
 83d4045e931c712b41ba73102501d45b716a25c5b88905b119f6ff694c561e4e 24447 
dvd+rw-tools_7.1-11.1.debian.tar.bz2
 206424d38c5f718a8fd5a279ab8d2283b082b5fba43b7ee6f4bc5bd38dbf2dc8 22180 
dvd+rw-tools-dbg_7.1-11.1_amd64.deb
 76f73c72ecc99d8fcb037ddac79d1ebac224c521a92d62319009ec34f634d7e2 4888 
dvd+rw-tools_7.1-11.1_2016T151250z-cc0e06bf.buildinfo
 92f3685bf88d4e3a4f88b36ffe0730db5820dde1ba5f188a9476cc09f69b4977 86148 
dvd+rw-tools_7.1-11.1_amd64.deb
 1da97938e1afc8a154fefc007ddae9edc89ec0c304be214717f9d20d2eb3d7b3 69804 
growisofs_7.1-11.1_amd64.deb
Files:
 df15d18c2626142144aff1bd59607d7b 2164 video optional dvd+rw-tools_7.1-11.1.dsc
 9c385bf21e1058e863c8b61beb73ecd2 24447 video optional 
dvd+rw-tools_7.1-11.1.debian.tar.bz2
 7e696a2e1e78041295fc2930e44e2654 22180 debug extra 
dvd+rw-tools-dbg_7.1-11.1_amd64.deb
 cc0e06bf5b1d0d27d604eecaeec73625 4888 video optional 
dvd+rw-tools_7.1-11.1_2016T151250z-cc0e06bf.buildinfo
 9206fc32e3dec6b519971771fa5fde0f 86148 video optional 
dvd+rw-tools_7.1-11.1_amd64.deb
 201a02d07a4c86171f0cb4dcce8bb720 69804 video optional 
growisofs_7.1-11.1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYJeBxAAoJEETTKrX6JvjJYLoQAIFNj1Ltppv2rLDCEFitxbID
ZuaHC6lV24WuAliuz+3etK7qlzGgu+MqC1mSgpWRao7T2PIJLGi4l+tPK2FkYJJD
PcivjZlJWY3vVzWZDssKjloYZ2la2fYq8Tgn5dpL2f06Qd2TDLuDC9wCFEkF63it

Bug#828241: marked as done (atheme-services: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 15:33:40 +
with message-id 
and subject line Bug#828241: fixed in atheme-services 7.2.7-1
has caused the Debian Bug report #828241,
regarding atheme-services: FTBFS with openssl 1.1.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.)


-- 
828241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: atheme-services
Version: 7.0.7-2
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/atheme-services_7.0.7-2_amd64-20160529-1405

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: atheme-services
Source-Version: 7.2.7-1

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

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated atheme-services 
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, 16 Nov 2016 09:59:17 -0500
Source: atheme-services
Binary: atheme-services
Architecture: source amd64
Version: 7.2.7-1
Distribution: unstable
Urgency: medium
Maintainer: Antoine Beaupré 
Changed-By: Antoine Beaupré 
Description:
 atheme-services - modular IRC services daemon
Closes: 818947 828241
Changes:
 atheme-services (7.2.7-1) unstable; urgency=medium
 .
   * new upstream release
   * stop using overlay, upstream seems to have cleaned up their thing
   * fix watch file
   * add missing lsb-base dependency
   * update standards version, no change
   * silence lintian warnings about libathemecore
   * new patches to fix FTBFS with OpenSSL 1.1.0 (Closes: #828241):
 * openssl-1.1.0-5480943.patch
 * openssl-1.1.0-b04f18e.patch
   * remove patches factored in upstream:
 * reproducible-f4cd16d.patch (Closes: #818947)
 * CVE-2014-9773.patch
 * CVE-2016-4478.patch
Checksums-Sha1:
 6668c488c48bf402d42c4d1e8e6d232d00354f4f 2071 atheme-services_7.2.7-1.dsc
 2eb7969382d3dbe4239b6521c6bebe5ad7ec0f06 1181086 
atheme-services_7.2.7.orig.tar.bz2
 8ab3f5b32a4583631d916d5fee7ce0a223e79330 11868 
atheme-services_7.2.7-1.debian.tar.xz
 ef3770b625e72098a2d2f70ecc98e4ecd887c0ba 6202902 
atheme-services-dbgsym_7.2.7-1_amd64.deb
 e78e3c5727d584d895940250a4d2c51c6c95d341 4888 
atheme-services_7.2.7-1_20161116T151241z-b6056ed7.buildinfo
 fd70e710d793a870c60cbe3341ca79af16875845 981346 
atheme-services_7.2.7-1_amd64.deb
Checksums-Sha256:
 057e95fdad1931dea2e57a1a1349bc161f5191893cf50d3c251988ba4ab5fc74 2071 
atheme-services_7.2.7-1.dsc
 64159a5aef905f0a15f35c7dd2bf1b140d918290488e9b6762fd85fd1bfafd94 1181086 
atheme-services_7.2.7.orig.tar.bz2
 815f2eac212dac9b78e71ded24eb32ec7385c25da12f89c248e8ad6c114cee45 11868 
atheme-services_7.2.7-1.debian.tar.xz
 71dd4c474112410f6760f3d6772900fa05525270497ba95b22ec903275449d5a 6202902 
atheme-services-dbgsym_7.2.7-1_amd64.deb
 c01231f77442cf5b7792686528ae95c93b7b1b1921a8f8f62c25d821be1faa20 4888 
atheme-services_7.2.7-1_20161116T151241z-b6056ed7.buildinfo
 fbec2caf1c85887c8fe18b90989ae417e9102b851fe121febde4a36fa1a1bfb0 981346 
atheme-services_7.2.7-1_amd64.deb
Files:
 dba53f690748ccf8fb929755b76a56ce 2071 net optional atheme-services_7.2.7-1.dsc
 90750946f5f9633fcaa85368835ea7ac 1181086 net optional 
atheme-services_7.2.7.orig.tar.bz2
 530fc4cd5144ef3180f8acc2ef2cb70f 11868 net optional 

Bug#839468: marked as done (pgloader: FTBFS: error opening #P"/etc/localtime": No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 15:07:12 +
with message-id 
and subject line Bug#839468: fixed in pgloader 3.3.1+dfsg-2
has caused the Debian Bug report #839468,
regarding pgloader: FTBFS:   error opening #P"/etc/localtime": No such file or 
directory
to be marked as done.

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

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


-- 
839468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pgloader
Version: 3.3.1+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/pgloader-3.3.1+dfsg'
> make[2]: 'docs' is up to date.
> make[2]: Leaving directory '/<>/pgloader-3.3.1+dfsg'
> mkdir -p build/bin
> mkdir -p /<>/pgloader-3.3.1+dfsg/debian/home
> buildapp --require sb-posix \
>  --require sb-bsd-sockets   \
>  --load /usr/share/common-lisp/source/cl-asdf/build/asdf.lisp 
> \
>  --asdf-path .  \
>  --asdf-tree /usr/share/common-lisp/systems \
>  --load-system asdf-finalizers\
>  --load-system asdf-system-connections\
>  --load-system pgloader   \
>  --load src/hooks.lisp  \
>  --entry pgloader:main  \
>  --dynamic-space-size 4096   \
>  --compress-core  \
>  --output build/bin/pgloader
> ; compiling file "/usr/share/common-lisp/source/cl-asdf/build/asdf.lisp" 
> (written 06 APR 2016 10:27:19 AM):
> 
> ; 
> /<>/pgloader-3.3.1+dfsg/debian/home/.cache/common-lisp/sbcl-1.3.8.debian-linux-x64/usr/share/common-lisp/source/cl-asdf/build/asdf-TMP.fasl
>  written
> ; compilation finished in 0:00:04.509
> ;; loading file #P"/usr/share/common-lisp/source/cl-asdf/build/asdf.lisp"
> ;; loading system "asdf-finalizers"
> ;; loading system "asdf-system-connections"
> ;; loading system "pgloader"
> Fatal SIMPLE-FILE-ERROR:
>   error opening #P"/etc/localtime": No such file or directory
> debian/rules:31: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/01/pgloader_3.3.1+dfsg-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated pgloader 
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, 03 Nov 2016 14:32:28 +0100
Source: pgloader
Binary: pgloader cl-pgloader
Architecture: source
Version: 3.3.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Dimitri 

Bug#833196: marked as done (libpcl1: Uses obsolete Source-Version substvar)

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 15:05:58 +
with message-id 
and subject line Bug#833196: fixed in libpcl1 1.6-1.1
has caused the Debian Bug report #833196,
regarding libpcl1: Uses obsolete Source-Version substvar
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.)


-- 
833196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpcl1
Source-Version: 1.6-1
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-obsolete-source-version-substvar

Hi!

This source package uses the ${Source-Version} substvar variable
deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced
the substvars binary:Version and source:Version which can be used
instead.

Using this deprecated substvar will become an error in the near
future. Please update the package.

See also .

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: libpcl1
Source-Version: 1.6-1.1

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated libpcl1 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Nov 2016 13:23:45 +
Source: libpcl1
Binary: libpcl1-dev libpcl1
Architecture: source amd64
Version: 1.6-1.1
Distribution: unstable
Urgency: medium
Maintainer: Damián Viano 
Changed-By: Chris Lamb 
Description:
 libpcl1- Portable Coroutine Library (PCL)
 libpcl1-dev - Portable Coroutine Library (PCL), development files
Closes: 833196
Changes:
 libpcl1 (1.6-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Move from obsolete Source-Version substvar to binary:Version.
 (Closes: #833196)
Checksums-Sha1:
 546a25a06ed77d4eda3c38332891101a581ec0ff 1688 libpcl1_1.6-1.1.dsc
 cbf38299404eb0496f727f1c797262bb90a859f5 335028 libpcl1_1.6.orig.tar.gz
 fefeacab6042d2bb6954ce2e47c18129fb40e55a 21241 libpcl1_1.6-1.1.diff.gz
 18d8500dd14ef45043288a307f038c02a6cae91c 6416 libpcl1-dbgsym_1.6-1.1_amd64.deb
 3e9c60b3d3f0945cd71b8065ca11702fa6010a6d 11374 libpcl1-dev_1.6-1.1_amd64.deb
 3d8ad0f52a28900a2419ac1330054f5ac97d6827 4753 
libpcl1_1.6-1.1_2016T132508z-edef7c4b.buildinfo
 faba1b89dba32514f130730b3fddb2d9e13f3289 4970 libpcl1_1.6-1.1_amd64.deb
Checksums-Sha256:
 9f398eaa78bdd3f6818782e9528a8758b66452601bb9f9704788cf321b19ef23 1688 
libpcl1_1.6-1.1.dsc
 556834057845ad4413e9e2b629d559b431001ded40d64f607fdeaf4a7b570602 335028 
libpcl1_1.6.orig.tar.gz
 c8483026ed6190e91eff4f457a86e10c7865d82f1c54c6c14d27a1ad77fbe976 21241 
libpcl1_1.6-1.1.diff.gz
 810cc5667b3c73940e24629b0a72c48abbe4e0d8f07af179ccd59632b893c542 6416 
libpcl1-dbgsym_1.6-1.1_amd64.deb
 92c2860df22dba1df60358c93a1e6626e108d5f44e233adc7ee5ececf21560b9 11374 
libpcl1-dev_1.6-1.1_amd64.deb
 e7a5082280be8df26d6137e5c0a5383be11eac4bcbf3472669007107fdc94f4c 4753 
libpcl1_1.6-1.1_2016T132508z-edef7c4b.buildinfo
 e7803104c563c6e4637d22d90f192da702b08b1b6ed116c8fa5bf3f7eb3f3007 4970 
libpcl1_1.6-1.1_amd64.deb
Files:
 337318dc573111fc3571dfd4a63db5e1 1688 libs optional libpcl1_1.6-1.1.dsc
 67f63b02e94ab1775f26bc5463817f09 335028 libs optional libpcl1_1.6.orig.tar.gz
 ab02092363c2bcc7f88008729dcde5cb 21241 libs optional libpcl1_1.6-1.1.diff.gz
 a51ac109624c057b64503836e4b096a9 6416 debug extra 
libpcl1-dbgsym_1.6-1.1_amd64.deb
 c5afddb7d419ec335f46ae31ed4894c6 11374 libdevel optional 
libpcl1-dev_1.6-1.1_amd64.deb
 edef7c4b92a56373796ba63812b4ea7d 4753 libs optional 
libpcl1_1.6-1.1_2016T132508z-edef7c4b.buildinfo
 e92d8b1884ccd0b2f63ec80da71aa670 4970 libs optional libpcl1_1.6-1.1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAlglyMoACgkQHpU+J9Qx
HlhlvBAAoscmReApw55otNXmQBp+rgOMb7KSiGoeoW/3Fn+q2zBaeE2Ez9kQrz7m
bEDB7rF1CH9dR/mJKxRSmnKaLNW+qxDU762WELSRLojVAuKn+8aMMU71WlE2MPgu

Bug#833195: marked as done (libident: Uses obsolete Source-Version substvar)

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 15:05:34 +
with message-id 
and subject line Bug#833195: fixed in libident 0.22-3.1
has caused the Debian Bug report #833195,
regarding libident: Uses obsolete Source-Version substvar
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.)


-- 
833195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libident
Source-Version: 0.22-3
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-obsolete-source-version-substvar

Hi!

This source package uses the ${Source-Version} substvar variable
deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced
the substvars binary:Version and source:Version which can be used
instead.

Using this deprecated substvar will become an error in the near
future. Please update the package.

See also .

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: libident
Source-Version: 0.22-3.1

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated libident package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Nov 2016 13:19:51 +
Source: libident
Binary: libident libident-dev
Architecture: source amd64
Version: 0.22-3.1
Distribution: unstable
Urgency: medium
Maintainer: Paul Slootman 
Changed-By: Chris Lamb 
Description:
 libident   - simple RFC1413 client library - runtime
 libident-dev - simple RFC1413 client library - development
Closes: 833195
Changes:
 libident (0.22-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Move from obsolete Source-Version substvar to binary:Version.
 (Closes: #833195)
Checksums-Sha1:
 138397900a6e3f681731af21581d877ab7ce3f7b 1659 libident_0.22-3.1.dsc
 cf70a9600880085c333d4e8623ece8056a196cc6 10716 libident_0.22.orig.tar.gz
 9273db1b76d70c144246be0b7d773d5e99a436e8 9525 libident_0.22-3.1.diff.gz
 62675c06d8c68582e0365cf4b4af2562810277c6 8614 libident-dev_0.22-3.1_amd64.deb
 d77d0fb3c286cf5167e4ade5f0ddbd90fb83ba44 3637 
libident_0.22-3.1_2016T132259z-3964d6f9.buildinfo
 c681bb0b54718fbc949c69fc083ee47d41d9d039 12592 libident_0.22-3.1_amd64.deb
Checksums-Sha256:
 fbc0a8f94276803f32bdd91ee6ca2a45eb5e9403e81b22dc14befbcf972482a4 1659 
libident_0.22-3.1.dsc
 04c3cc5287849c97305eb2e1aae7efbc96f622d02b3fd4274ed4647d0ccb0aa3 10716 
libident_0.22.orig.tar.gz
 1248d92998145c04e77d557e01723835e06adb08c93606f74b2b6bae7b7d4078 9525 
libident_0.22-3.1.diff.gz
 cb30a2f98f1806ed1fa1f773c7d2d17736e228f0412d4fc09e2ed516959f9d69 8614 
libident-dev_0.22-3.1_amd64.deb
 00bfa5723f7335df83ea8722bf0672133cf4a0bad18016bb47199d3d984e2897 3637 
libident_0.22-3.1_2016T132259z-3964d6f9.buildinfo
 4182c59293fc13fb5e0d5035f145207d54f2aa6ed19f9a764ef35f097fd09960 12592 
libident_0.22-3.1_amd64.deb
Files:
 f06fdc755cea6669ae8e85bcee82c215 1659 libs important libident_0.22-3.1.dsc
 218b6706e574ca5b41a0a675cf1860eb 10716 libs important libident_0.22.orig.tar.gz
 f147abcaea2385e6a4425be84a9722e1 9525 libs important libident_0.22-3.1.diff.gz
 4ea369775606e9122e219f3d6824a3e1 8614 libdevel optional 
libident-dev_0.22-3.1_amd64.deb
 3964d6f9b4cee2447c3a17cf9598e7d4 3637 libs important 
libident_0.22-3.1_2016T132259z-3964d6f9.buildinfo
 367395ab16338ef38df5405f59795b44 12592 libs important 
libident_0.22-3.1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAlglyNIACgkQHpU+J9Qx
HlgQghAApSUurueG1HCjDE+9lEIiB7geR4WsBzWVx2RmJZDgYSHeSbDbZhy0rW4n
mQHcMxzpbA+CANdnCeQoBJ5EjxWPFFPScjvPIOZnJqoUFE6z191KpRM2E5OnaNku
a05y98zvB8oy3vgwM6O0QG3sS5Ozdu3lnNHj6TsX6Y8y6cHBtoLjm2J36Mqj90Et
xaNs2u2x5vOJqMGMDr7LpHdByAOgptCXH2kBH0R/p3NM5Q2yDEnRk9zp3iDfVQIc
MolpH2JylRxLSOIyt/v0pgViTunpldY+inHBrEk1O7iYqbhzAqr1aqQD6fjpnjIu
yCX9txoCncMM//eSlBWvL6oVPhRcq8HPsWRBJ+5bQn3oolG0WZUjyT5M4N0nVuqs

Bug#833202: marked as done (pygopherd: Uses obsolete Source-Version substvar)

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 15:07:19 +
with message-id 
and subject line Bug#833202: fixed in pygopherd 2.0.18.4+nmu1
has caused the Debian Bug report #833202,
regarding pygopherd: Uses obsolete Source-Version substvar
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.)


-- 
833202: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygopherd
Source-Version: 2.0.18.4
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-obsolete-source-version-substvar

Hi!

This source package uses the ${Source-Version} substvar variable
deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced
the substvars binary:Version and source:Version which can be used
instead.

Using this deprecated substvar will become an error in the near
future. Please update the package.

See also .

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: pygopherd
Source-Version: 2.0.18.4+nmu1

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated pygopherd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Nov 2016 13:23:52 +
Source: pygopherd
Binary: pygopherd pygfarm
Architecture: source all
Version: 2.0.18.4+nmu1
Distribution: unstable
Urgency: medium
Maintainer: John Goerzen 
Changed-By: Chris Lamb 
Description:
 pygfarm- Collection of add-on modules for Pygopherd
 pygopherd  - Modular Multiprotocol Gopher/HTTP/WAP Server in Python
Closes: 833202
Changes:
 pygopherd (2.0.18.4+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Move from obsolete Source-Version substvar ${source:Version}.
 (Closes: #833202)
Checksums-Sha1:
 0c7feab1cc2e1d057160fb5c6b2c661dcfb1ab04 1690 pygopherd_2.0.18.4+nmu1.dsc
 b789d54a6588100843229d0a42521b670fa12c04 274050 pygopherd_2.0.18.4+nmu1.tar.gz
 a5ef5cc7bee4814ee8c477f248bb83834180a47a 7612 pygfarm_2.0.18.4+nmu1_all.deb
 308ac6edc5364bf431df6605e5474a54dff57ae7 5113 
pygopherd_2.0.18.4+nmu1_2016T132714z-bce2a0d4.buildinfo
 c22f5b4d7e8ccac57c9459bf3f5dea1250a50be5 217850 pygopherd_2.0.18.4+nmu1_all.deb
Checksums-Sha256:
 97039fd54997b04442c178fa5e902e69d69aab4a98f034300a223aaace870270 1690 
pygopherd_2.0.18.4+nmu1.dsc
 bb282008f432b9e3dfb99741ed0f47dbfde43e3d58f659e1169d542d0b609af6 274050 
pygopherd_2.0.18.4+nmu1.tar.gz
 9cb4eee0fb702ac55ec98381751b2a92b25edbba727d3b9dac379de082e4042c 7612 
pygfarm_2.0.18.4+nmu1_all.deb
 2aa838f9a4c00b6e158a06002f19bd01f52c5746d6dcd94e8632084ed7a06855 5113 
pygopherd_2.0.18.4+nmu1_2016T132714z-bce2a0d4.buildinfo
 c52afd921f8af801e370a12259162c7353ac1f472e2c68bda679e7f39dd4065a 217850 
pygopherd_2.0.18.4+nmu1_all.deb
Files:
 bb6bb9e388c4b7be5122edbf247e6e85 1690 net optional pygopherd_2.0.18.4+nmu1.dsc
 c5e0bc0f8fc040c46a42b13fbccfee43 274050 net optional 
pygopherd_2.0.18.4+nmu1.tar.gz
 9f542c648a388830f85d7e50e2a89513 7612 net optional 
pygfarm_2.0.18.4+nmu1_all.deb
 bce2a0d421bb23c4fe108d67b556ee1f 5113 net optional 
pygopherd_2.0.18.4+nmu1_2016T132714z-bce2a0d4.buildinfo
 3eff9b335562d9bacd8099c8c15ef477 217850 net optional 
pygopherd_2.0.18.4+nmu1_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAlglyMMACgkQHpU+J9Qx
HlgLRhAAtkngFEJHQ4qOCM9rXfoSS7em0WCIzmFAck/z3Cus1Nz9c5LOpcQXzE79
8ERNfawgACDuJfcYfys7qQU5kf8OeRwbv69GRI/jHnZ9SAlLG2mChcTggKApL/dx
LYvzQsXo9iANYopvxqARZJlrB/mfURA/bEltwsQmGbovalDeoyVt1cR68JlOkul0
piQf7wbNzwz//TmBVQrSkqvXolv8LSUCsNKGWbnOqCzqwJZh+Hp+zzUPbRFG7ucv
Qr1SKopELNhUWEyOKvip6oiTLQXk6kQ13x37mS8nxuPrq6VtFQwaRqG3d2Y3MhWg
YjVKwdF5/1SNhYuqOROApwGr4in18tHu1Kvpn05yk9GAwerVoeaUwLmEoWRgnS4i
JJCaAqxz1pKGFhT0gLERjCfkPTE4PVLtVT1818DBydW8B94R7KqHGeJ7LRZMfm+L
o89MDfirJs51sCvH1+h2NOLR2HUfBOPCMbDZWXsQIG38hy0cvNMA8QWWir94ndfU

Bug#844458: bootstrap-base: if debootstrap_script is unset, DEBOOTSTRAP_SCRIPT is set to a directory, breaking the install

[Philip Hands]

Philip Hands  writes:

> Tianon Gravi  writes:
>
>> On 15 November 2016 at 15:36, Philip Hands  wrote:
>>> This seems to have resulted from the recent change to bootstrap-base to
>>> allow the script to be specified only as the codename, but which is not
>>> checking whether the debconf variable is actually set.
>>>
>>> This commit should therefore fix the problem:
>>>
>>>   http://deb.li/iUtYi
>>>
>>> I've applied that change to a broken image by hand, and it does solve the 
>>> problem.
>>
>> Doh, sorry I missed this edge case!
>>
>> For what it's worth, the proposed change looks legit to me. :)
>
> Glad yo like it, but on re-examination, I'm not so sure -- should the
> concatenated path not also be checked to see if it exists?

So, the previous code was:

  db_get base-installer/debootstrap_script
  DEBOOTSTRAP_SCRIPT="$RET"
  if [ ! -e /usr/share/debootstrap/scripts/"$DEBOOTSTRAP_SCRIPT" ]; then
error "debootstrap script '$DEBOOTSTRAP_SCRIPT' doesn't exist"
  fi

which throws an error if base-installer/debootstrap_script is set to a
path that does not exist, but does not throw an error if it is unset (as
long as the /usr/share/debootstrap/scripts/ directory exists).

It seems to me that the commit message for a8b68f8e should have been
"Allow absolute paths ..." because the code already dealt with
codenames, since it was already checking for the existence of:

  /usr/share/debootstrap/scripts/"$DEBOOTSTRAP_SCRIPT"

Looking at the debootstrap code, if this is unset, then there is no $4
so we're going to get the script set to "$DEBOOTSTRAP_DIR/scripts/$1"
(where $1 is the suite), possibly with .$VARIANT added if set.  This
seems to be the default behaviour.

If the debconf variable was set to an absolute path, then I guess the
old code would break, since it unconditionally prefixed the path before
checking for existence.  If it were set to the suite name, then the test
in bootstrap-base.postinst would pass, but debootstrap would then have a
suite name as the script, so the:

  if [ ! -e "$SCRIPT" ]; then

test would fail, so I'm guessing this code never worked.  Is that
actually right?

In light of all that, I think that this commit actually does the right
thing, and is rather more obvious than my previous attempt:

  http://deb.li/3IOXc

(but I still need to test it...)

Cheers, Phil.

P.S. I used the   if ... && [ "$RET" ]   style test because it's
also in use for the variant setting, and in the unlikely event that
base-installer/debootstrap_script were unset, it would still do the
right thing, rather than throwing an error becuase of the set -e.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#840853: qemu 2.7 requires linuxboot_dma.bin but does not provide or depend on it

[Vincent Danjean]

Package: qemu-system-x86
Version: 1:2.7+dfsg-3+b1
Followup-For: Bug #840853

  Hi,

  Contrary to what the debian/changelog says, this bug has not been fixed yet.
In fact, looking at the git repo, the fix has just been commited by
the maintainer on 2016-11-09, ie *after* the 2.7+dfsg-3 version.
  It would be very pleasant if the jessie backport package could be remade
with this fix.
  For information, I just uploaded to jessie-backport a backported version
of seabios 1.9.3-2 (ie 1.9.3-2~bpo8+1)

  Regards,
Vincent

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

Kernel: Linux 4.8.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages qemu-system-x86 depends on:
ii  ipxe-qemu   1.0.0+git-20150424.a25a16d-1
ii  libaio1 0.3.110-3
ii  libasound2  1.1.2-1
ii  libbluetooth3   5.43-1
ii  libbrlapi0.65.4-2
ii  libc6   2.24-5
ii  libcacard0  1:2.5.0-2
ii  libfdt1 1.4.0+dfsg-2
ii  libgcc1 1:6.2.0-10
ii  libglib2.0-02.50.2-1
ii  libgnutls30 3.5.6-2
ii  libjpeg62-turbo 1:1.5.1-2
ii  libncurses5 6.0+20160917-1
ii  libnettle6  3.3-1
ii  libpixman-1-0   0.34.0-1
ii  libpng16-16 1.6.26-1
ii  libpulse0   9.0-5
ii  libsasl2-2  2.1.27~72-g88d82a3+dfsg-1
ii  libsdl1.2debian 1.2.15+dfsg1-4
ii  libseccomp2 2.3.1-2
ii  libspice-server10.12.8-1
ii  libtinfo5   6.0+20160917-1
ii  libusb-1.0-02:1.0.21-1
ii  libusbredirparser1  0.7.1-1
ii  libuuid12.29-1
ii  libvdeplug2 2.3.2+r586-2+b1
ii  libx11-62:1.6.3-1
ii  libxen-4.8  4.8.0~rc3-1
ii  libxenstore3.0  4.8.0~rc3-1
ii  qemu-system-common  1:2.7+dfsg-3+b1
ii  seabios 1.9.3-2
ii  zlib1g  1:1.2.8.dfsg-2+b3

Versions of packages qemu-system-x86 recommends:
ii  qemu-utils  1:2.7+dfsg-3+b1

Versions of packages qemu-system-x86 suggests:
ii  kmod  23-1
pn  ovmf  
pn  qemu-block-extra  
pn  samba 
pn  sgabios   
ii  vde2  2.3.2+r586-2+b1

-- no debconf information

Processed: notfixed 840853 in 1:2.7+dfsg-2

[Debian Bug Tracking System]

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

> notfixed 840853 1:2.7+dfsg-2
Bug #840853 {Done: Michael Tokarev } [qemu] qemu 2.7 requires 
linuxboot_dma.bin but does not provide or depend on it
Bug #841953 {Done: Michael Tokarev } [qemu] libvirt0: 
virt-install generates "No bootable device" error when using --location option
Bug #841974 {Done: Michael Tokarev } [qemu] libguestfs-tools: 
Appliance get stuck
No longer marked as fixed in versions qemu/1:2.7+dfsg-2.
No longer marked as fixed in versions qemu/1:2.7+dfsg-2.
No longer marked as fixed in versions qemu/1:2.7+dfsg-2.
> thanks
Stopping processing here.

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

Bug#826653: Pending fixes for bugs in the shiro package

[pkg-java-maintainers]

tag 826653 + pending
thanks

Some bugs in the shiro package are closed in revision
0c7b865f067809d1314205edcfb425165a6502fe in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/shiro.git/commit/?id=0c7b865

Commit message:

Marked CVE-2016-4437 as fixed (Closes: #826653)

Processed: Pending fixes for bugs in the shiro package

[Debian Bug Tracking System]

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

> tag 826653 + pending
Bug #826653 {Done: tony mancill } [src:shiro] CVE-2016-4437
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#806273: use grub-mount as the sole source of partition probes (disable kernel readonly mounts)

[Emmanuel Kasper]

changes since v1:
 * do not fallback on dangerous read only kernel mounts if grub-mount is
missing, just exit with error



>From 34a2c247fa08d4e01aa08b5b75977c66d71df4f8 Mon Sep 17 00:00:00 2001
From: Emmanuel Kasper 
Date: Tue, 15 Nov 2016 14:52:23 +0100
Subject: [PATCH v2] use grub-mount as the sole source of partition probes
 (disable kernel readonly mounts)

the read only kernel mounts of os-probes caused various data corruption in virtual machines
and exported block devices due to the following chain of event:

 1. os-prober tries to mount via grub-mount each block device as seen from /sys/block
 2. in case of iscsi exported block devices or virtualization environment, such
 a block device could be a whole disk image with a partition table
 3. since grub-mount expects a filesystem superblock but encounters a partition table
 it fails and then give hand to
 4. kernel read only mounts, calling the function ro_partition
 5. the ro_partition function sets the block device readonly via blockdev --setro
 6. a number of kernel mounts are attempted via various kernel modules
 7. the block device is set to readwrite

now when I/O happened on the iscsi initiator or virtual machines between 5-7
the blocks cannot be flushed to the block device since it has been
locked  by os-prober. This causes a filesystem error and the filesystem to be
remounted read only.

since grub-mount is now available on all the platforms debian supports
we assume we can disable the risky behaviour without losing too much os-prober functionnality

grub-mount has also now support for all filesystems which the kernel knows,
the exception being QNX
---
 debian/control   |  2 +-
 os-probes/common/50mounted-tests | 27 +++
 2 files changed, 12 insertions(+), 17 deletions(-)

diff --git a/debian/control b/debian/control
index 10459bd..ac307f5 100644
--- a/debian/control
+++ b/debian/control
@@ -22,7 +22,7 @@ Package: os-prober
 Architecture: any
 Section: utils
 Priority: extra
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, grub-common
 Description: utility to detect other OSes on a set of drives
  This package detects other OSes available on a system and outputs the
  results in a generic machine-readable format.
diff --git a/os-probes/common/50mounted-tests b/os-probes/common/50mounted-tests
index 561163b..8e1c87f 100755
--- a/os-probes/common/50mounted-tests
+++ b/os-probes/common/50mounted-tests
@@ -47,25 +47,20 @@ fi
 
 mounted=
 if type grub-mount >/dev/null 2>&1 && \
-   type grub-probe >/dev/null 2>&1 && \
-   grub-mount "$partition" "$tmpmnt" 2>/dev/null; then
-	mounted=1
-	type="$(grub-probe -d "$partition" -t fs)" || true
-	if [ "$type" ]; then
-		debug "mounted using GRUB $type filesystem driver"
-	else
-		debug "mounted using GRUB, but unknown filesystem?"
+   type grub-probe >/dev/null 2>&1; then
+	if grub-mount "$partition" "$tmpmnt" 2>/dev/null; then
+		mounted=1
+		type="$(grub-probe -d "$partition" -t fs)" || true
+		if [ "$type" ]; then
+			debug "mounted using GRUB $type filesystem driver"
+		else
+			debug "mounted using GRUB, but unknown filesystem?"
 		type=fuseblk
+		fi
 	fi
 else
-	ro_partition "$partition"
-	for type in $types $delaytypes; do
-		if mount -o ro -t "$type" "$partition" "$tmpmnt" 2>/dev/null; then
-			debug "mounted as $type filesystem"
-			mounted=1
-			break
-		fi
-	done
+	echo "Cannot find grub-mount (Try installing grub-common)" >&2
+	exit 1
 fi
 
 if [ "$mounted" ]; then
-- 
2.1.4

Bug#844523: Debian xserver freeze

[Carmelo C]

Package: xserver-xorg
Version: 1:7.7+7
Severity: critical
Tags: security
Justification: breaks the whole system

For some time I noticed that browsing with firefox on the site: twitter or
google maps, it happens that the system freezes and I have to unplug the
laptop
from the switch. The problem also occurs when I open gimp and applying
contrast, saturation or adjusting the levels of an image, the system
freezes.
log attached refers to Xorg.1.log file
[   506.152]
X.Org X Server 1.16.4
Release Date: 2014-12-20
[   506.152] X Protocol Version 11, Revision 0
[   506.152] Build Operating System: Linux 3.2.0-4-amd64 i686 Debian
[   506.152] Current Operating System: Linux debian 3.16.0-4-686-pae #1 SMP
Debian 3.16.7-ckt11-1+deb8u6 (2015-11-09) i686
[   506.152] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-686-pae
root=UUID=ec43167a-ee14-44c5-aee3-0301bf529f95 ro radeon.dpm=1
[   506.152] Build Date: 11 February 2015  01:14:26AM
[   506.152] xorg-server 2:1.16.4-1 (http://www.debian.org/support)
[   506.152] Current version of pixman: 0.32.6
[   506.153]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   506.153] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   506.153] (==) Log file: "/var/log/Xorg.1.log", Time: Fri Nov 27 16:58:11
2015
[   506.153] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   506.153] (==) No Layout section.  Using the first Screen section.
[   506.153] (==) No screen section available. Using defaults.
[   506.153] (**) |-->Screen "Default Screen Section" (0)
[   506.153] (**) |   |-->Monitor ""
[   506.154] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   506.154] (==) Automatically adding devices
[   506.154] (==) Automatically enabling devices
[   506.154] (==) Automatically adding GPU devices
[   506.154] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   506.154]Entry deleted from font path.
[   506.154] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[   506.154] (==) ModulePath set to "/usr/lib/xorg/modules"
[   506.154] (II) The server relies on udev to provide the list of input
devices.
If no devices become available, reconfigure udev or disable
AutoAddDevices.
[   506.154] (II) Loader magic: 0xb7773700
[   506.154] (II) Module ABI versions:
[   506.154]X.Org ANSI C Emulation: 0.4
[   506.154]X.Org Video Driver: 18.0
[   506.154]X.Org XInput driver : 21.0
[   506.154]X.Org Server Extension : 8.0
[   506.154] (II) xfree86: Adding drm device (/dev/dri/card0)
[   506.156] (--) PCI:*(0:1:0:0) 1002:95c4:1028:029f rev 0, Mem @
0xd000/268435456, 0xfc00/65536, I/O @ 0x2000/256, BIOS @
0x/131072
[   506.156] (II) LoadModule: "glx"
[   506.156] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   506.158] (II) Module glx: vendor="X.Org Foundation"
[   506.158]compiled for 1.16.4, module version = 1.0.0
[   506.158]ABI class: X.Org Server Extension, version 8.0
[   506.158] (==) AIGLX enabled
[   506.158] (==) Matched ati as autoconfigured driver 0
[   506.158] (==) Matched ati as autoconfigured driver 1
[   506.158] (==) Matched modesetting as autoconfigured driver 2
[   506.158] (==) Matched fbdev as autoconfigured driver 3
[   506.158] (==) Matched vesa as autoconfigured driver 4
[   506.158] (==) Assigned the driver to the xf86ConfigLayout
[   506.158] (II) LoadModule: "ati"
[   506.158] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[   506.158] (II) Module ati: vendor="X.Org Foundation"
[   506.158]compiled for 1.16.1, module version = 7.5.0
[   506.158]Module class: X.Org Video Driver
[   506.158]ABI class: X.Org Video Driver, version 18.0
[   506.158] (II) LoadModule: "radeon"
[   506.158] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[   506.158] (II) Module radeon: vendor="X.Org Foundation"
[   506.158]compiled for 1.16.1, module version = 7.5.0
[   506.158]Module class: X.Org Video Driver
[   506.158]ABI class: X.Org Video Driver, version 18.0
[   506.158] (II) LoadModule: "modesetting"
[   506.158] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[   506.158] (II) Module modesetting: vendor="X.Org Foundation"
[   506.159]compiled for 1.16.4, module version = 0.9.0
[   506.159]Module class: X.Org Video Driver
[   506.159]ABI class: X.Org Video Driver, version 18.0
[   506.159] (II) LoadModule: "fbdev"
[   506.159] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[   506.159] (II) Module fbdev: 

Processed: Re: Bug#844458: bootstrap-base: if debootstrap_script is unset, DEBOOTSTRAP_SCRIPT is set to a directory, breaking the install

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #844458 [bootstrap-base] bootstrap-base: if debootstrap_script is unset, 
DEBOOTSTRAP_SCRIPT is set to a directory, breaking the install
Severity set to 'serious' from 'important'
> tag -1 - d-i
Bug #844458 [bootstrap-base] bootstrap-base: if debootstrap_script is unset, 
DEBOOTSTRAP_SCRIPT is set to a directory, breaking the install
Removed tag(s) d-i.

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

Bug#840554: Fixes from 2.9.4+dfsg1-2.1 / 2.8.0+dfsg1-7+wheezy7

[Thorsten Glaser]

On Wed, 16 Nov 2016, Salvatore Bonaccorso wrote:

> FWIW, from security-team side I was planning to work on those after
> 2.9.4+dfsg1-2.1 was now exposed enought in unstable first (unless

OK, thank you.

> I have it though not yet finalized.

No worries.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Bug#840553: Bug#840554: Fixes from 2.9.4+dfsg1-2.1 / 2.8.0+dfsg1-7+wheezy7

[Salvatore Bonaccorso]

Hi,

On Wed, Nov 16, 2016 at 02:54:54PM +0100, Thorsten Glaser wrote:
> Hello Aron,
> 
> are you going to upload these fixes for jessie, too?
> Do you need assistance?

FWIW, from security-team side I was planning to work on those after
2.9.4+dfsg1-2.1 was now exposed enought in unstable first (unless
Around wwanted to take over).

I have it though not yet finalized.

Regards,
Salvatore

Bug#828241: atheme-services: FTBFS with openssl 1.1.0

[Antoine Beaupré]

Control: forwarded 828241 https://github.com/atheme/atheme/issues/528

On 2016-11-10 05:03:17, Adrian Bunk wrote:
> On Mon, Aug 01, 2016 at 07:18:38PM -0400, Antoine Beaupré wrote:
>> On 2016-06-26 06:21:03, Kurt Roeckx wrote:
>> > OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
>> > OpenSSL this package fail to build.  A log of that build can be found at:
>> > https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/atheme-services_7.0.7-2_amd64-20160529-1405
>> >
>> > On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various 
>> > of the
>> > reasons why it might fail.  There are also updated man pages at
>> > https://www.openssl.org/docs/manmaster/ that should contain useful 
>> > information.
>> >
>> > There is a libssl-dev package available in experimental that contains a 
>> > recent
>> > snapshot, I suggest you try building against that to see if everything 
>> > works.
>> >
>> > If you have problems making things work, feel free to contact us.
>> 
>> Hi!
>> 
>> I have just uploaded 7.2.6 to sid. Hopefully I didn't mess *that* up but
>> since it is a more recent, I wonder if this bug will just be fixed on
>> its own. Are rebuilds done regularly?
>> 
>> I do not have time right now to investigate this further, but let me
>> know if I do need to run a rebuild on my own.
>
> 7.2.6-1 fails to build in unstable with OpenSSL 1.1.0:
>
> pbkdf2.c: In function 'PKCS5_PBKDF2_HMAC':
> pbkdf2.c:47:11: error: storage size of 'hctx' isn't known
>   HMAC_CTX hctx;
>^~~~
> pbkdf2.c:51:2: error: implicit declaration of function 'HMAC_CTX_init' 
> [-Werror=implicit-function-declaration]
>   HMAC_CTX_init();
>   ^
> pbkdf2.c:87:2: error: implicit declaration of function 
> 'HMAC_CTX_cleanup' [-Werror=implicit-function-declaration]
>   HMAC_CTX_cleanup();
>   ^~~~

With 7.2.7 too, unfortunately. I have forwarded this upstream.

Patches would be welcome of course.

A.

-- 
Dr. King’s major assumption was that if you are nonviolent, if you
suffer, your opponent will see your suffering and will be moved to
change his heart. He only made one fallacious assumption: In order for
nonviolence to work, your opponent must have a conscience. The United
States has none.- Stokely Carmichael

Processed: Re: Bug#828241: atheme-services: FTBFS with openssl 1.1.0

[Debian Bug Tracking System]

Processing control commands:

> forwarded 828241 https://github.com/atheme/atheme/issues/528
Bug #828241 [src:atheme-services] atheme-services: FTBFS with openssl 1.1.0
Set Bug forwarded-to-address to 'https://github.com/atheme/atheme/issues/528'.

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

Processed: fixed 843627 4.0-1

[Debian Bug Tracking System]

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

> fixed 843627 4.0-1
Bug #843627 {Done: Javi Merino } [src:mercurial] mercurial 
fails it's tests on armhf
Marked as fixed in versions mercurial/4.0-1.
> thanks
Stopping processing here.

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

Bug#840553: Fixes from 2.9.4+dfsg1-2.1 / 2.8.0+dfsg1-7+wheezy7

[Thorsten Glaser]

Hello Aron,

are you going to upload these fixes for jessie, too?
Do you need assistance?

Thanks,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Bug#844501: alsa-firmware-loaders: udev rule causes race condition which blocks us-122 initialisation (with fix!)

[Jaime T]

On 16 November 2016 at 10:50, jaimet  wrote:
> My udev-fu is very weak, but after stumbling around with "udevadm
> monitor" for a bit, I replaced that udev rule line with:
>
> SUBSYSTEM=="sound", ACTION=="add", KERNEL=="hwC2D0", 
> RUN+="/lib/udev/tascam_fpga"

It now appears that my udev-fu is even weaker than I thought: "hwC2D0"
is obviously an "arbitrary-card-ordering-dependent" reference which
breaks if my sound cards are discovered in a different order. A much
better alternative (that is *not* order-dependent) is:

SUBSYSTEM=="sound", ACTION=="add", ATTR{id}=="USX2Y",
RUN+="/lib/udev/tascam_fpga"

Apologies for the noise. J :-)

Bug#843627: marked as done (mercurial fails it's tests on armhf)

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 13:20:46 +
with message-id 

and subject line mercurial tests now passing on armhf
has caused the Debian Bug report #843627,
regarding mercurial fails it's tests on armhf
to be marked as done.

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

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


-- 
843627: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mercurial
Version: 4.0-1
Severity: serious
Tags: sid stretch

according to
https://buildd.debian.org/status/package.php?p=mercurial

Failed test-largefiles-update.t: output changed
# Ran 474 tests, 51 skipped, 0 warned, 1 failed.
python hash seed: 630897662
# Cleaning up HGTMP /tmp/hgtests.LhS4fT
Makefile:110: recipe for target 'tests' failed
make[2]: *** [tests] Error 1
make[2]: Leaving directory '/«PKGBUILDDIR»'
dh_auto_test: make -j1 check TESTFLAGS=--verbose --timeout 1440 --jobs 4
--blacklist /«PKGBUILDDIR»/debian/mercurial.test_blacklist returned exit code 2
debian/rules:42: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:8: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
--- End Message ---
--- Begin Message ---
According to [0], "Ran 474 tests, 51 skipped, 0 warned, 0 failed."

[0] 
https://buildd.debian.org/status/fetch.php?pkg=mercurial=armhf=4.0-1=1479115599

Thanks,
Javi--- End Message ---

Bug#817465: marked as done (fusesmb: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Wed, 16 Nov 2016 13:19:01 +
with message-id 
and subject line Bug#817465: fixed in fusesmb 0.8.7-1.4
has caused the Debian Bug report #817465,
regarding fusesmb: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fusesmb
Severity: important
Usertags: compat-4-removal

Hi,

The package fusesmb uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: fusesmb
Source-Version: 0.8.7-1.4

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated fusesmb 
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: Sun, 06 Nov 2016 10:06:15 -0200
Source: fusesmb
Binary: fusesmb
Architecture: source
Version: 0.8.7-1.4
Distribution: unstable
Urgency: medium
Maintainer: Samuel Mimram 
Changed-By: Joao Eriberto Mota Filho 
Description:
 fusesmb- filesystem client based on the SMB file transfer protocol
Closes: 817465
Changes:
 fusesmb (0.8.7-1.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bumped DH level to 10. (Closes: #817465)
   * debian/control:
   - Added a ${misc:Depends} variable.
   - Bumped Standards-Version to 3.9.8.
   * Run wrap-and-sort.
Checksums-Sha1:
 938c13e95c44093e3a1a76dae26ec513ddd7bca0 1698 fusesmb_0.8.7-1.4.dsc
 d33eda5b8ef2915026799e92ae1958de6e3c4002 24025 fusesmb_0.8.7-1.4.diff.gz
Checksums-Sha256:
 7c8f2e97e32f4de72f3f7a33ecc702740209bad961a31cb35b1635c3e772da42 1698 
fusesmb_0.8.7-1.4.dsc
 fc356c97e2ea0122f9ce4552a463262e1ddd3f475c7b611ed143c7d34be5cc9e 24025 
fusesmb_0.8.7-1.4.diff.gz
Files:
 2aa398bec32b3a6e30b5aa82ad0a2c54 1698 utils optional fusesmb_0.8.7-1.4.dsc
 ee194df714a578181427ccb46e439f09 24025 utils optional fusesmb_0.8.7-1.4.diff.gz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYHyErAAoJEN5juccE6+nvQA8P/2/f8EC6bWeBbi7jhhg89/sO
5mwHXp5Aam5RotO+IAmWs/7HCkr7poyYw54BTrgKRTDiqGo4bKQtpI0aJaR+dDSp
Ss1MeZRRZENQEnOw9nvbSiVfcOqFbCBcL3oAqPU7rzucBTZswEvQOuaokRM2cxxA
oZlXobnxV39XQmQo4Nh8UPxTs0H+9MLFA7yX7VohHyRvGMsfMifd9z9h1d7vc/By
QGDr7Qwe7yfAj34ktfUQbPRk31uS+iJJbjneNqx8c9Fh+siA/3OWmWHCYBBbVWgF
XA7jHyv2LqKOCH/dFvRyizsVAKpHEBCo4+H02DEyNg4X0cxyqtkR2tKE4S7T7b2A
ZflexfSMdV7es/uIJXtUCEkGEhba/GWGcFQTLf2m/AIMlejU1172DMS9dngXFVd4
YXyUYcqs5U6IqoTKcOwF16b1DZx/nmAq0ShqNeuBhJb2MSaRa4l+9ThaK5zxvwqa
OGu675rwTH1rUaGG4GT6ff5JK9Fp0DmB89QOjHN//chnso5TNqGx8aBKI/riRRua
YEvP1jwW8NaYfgWgWsAYT4SDeMAQEdLH71j5+4bPxiNkyWgidP6+yo0GFr3TQMq8
67k7ZjGI5O8KuhHCJiT9SkDd7AiXA8eKo6TTheiim/S34efZyyXrE1asYuUf7jSr
77tyY0Jo5Cy4GL8pYtMf
=o8Pc
-END PGP SIGNATURE End Message ---

Processed: Re: Building with OpenSSL 1.0.2 is sufficient for stretch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #828231 [src:alpine] alpine: FTBFS with openssl 1.1.0
Added tag(s) patch.

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

Bug#828231: Building with OpenSSL 1.0.2 is sufficient for stretch

[Adrian Bunk]

Control: tags -1 patch

On Wed, Nov 16, 2016 at 01:40:08PM +0100, Sebastian Andrzej Siewior wrote:
> Control: tags -1 - patch
> 
> On 2016-11-10 12:31:00 [+0200], Adrian Bunk wrote:
> > 
> > Not a perfect solution but sufficient for stretch is the following 
> > change to use OpenSSL 1.0.2:
> > 
> > --- debian/control.old  2016-11-10 10:20:58.0 +
> > +++ debian/control  2016-11-10 10:21:32.0 +
> > @@ -5,7 +5,7 @@
> >  Uploaders: Andreas Tille , Luke Faraone 
> > ,
> >   Unit 193 
> >  Build-Depends: debhelper (>= 9), libldap2-dev, libpam0g-dev, 
> > libncurses-dev,
> > - libssl-dev, dh-autoreconf, ca-certificates, automake, autoconf, libtool, 
> > libkrb5-dev,
> > + libssl1.0-dev, dh-autoreconf, ca-certificates, automake, autoconf, 
> > libtool, libkrb5-dev,
> >   aspell, dpkg-dev (>= 1.16.1~)
> >  Standards-Version: 3.9.6
> >  Vcs-Browser: http://anonscm.debian.org/cgit/collab-maint/alpine.git
> 
> Adrian, seriously?

Yes.

> This is not a patch. While you are technically
> correct to describe this is a patch - it is not.

My patch does fix the RC issue for stretch.

> The issue reported here (not building against openssl 1.1.0) is not
> solved by this. Tagging this as patch makes people think that there is
> indeed a patch which is not the case.

The RC FTBFS issue is fixed for stretch with my patch.

> If the maintainer decides to stick with openssl 1.0.2 for the Stretch
> release I assume he is able to do the change himself

Considering that some of these patches have been uploaded with
"thanks Adrian Bunk" in the changelog, it seems maintainers
actually appreciate my efforts in helping their packages to
stay in stretch.

> and lowering the
> severity to important rather than closing this bug.

My tag applies to making the package non-RC-buggy for stretch.

Tracking two different issues in one bug is never a good idea,
but if you want to do it this way please don't interfere with
making the package non-RC-buggy for stretch.

> Please also untag any other patch tag in other bugs should they contain
> only this kind of a patch.

If you remove patch tags, I will add them back.

> Sebastian

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