Bug#805195: marked as done (debdry: FTBFS: ImportError: No module named 'apt_pkg')

[Debian Bug Tracking System]

Your message dated Tue, 25 Oct 2016 04:24:33 +
with message-id 
and subject line Bug#805195: fixed in debdry 0.2.2-1
has caused the Debian Bug report #805195,
regarding debdry: FTBFS: ImportError: No module named 'apt_pkg'
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.)


-- 
805195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debdry
Version: 0.2.1-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:


==
ERROR: test.test_control (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: test.test_control
Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/loader.py", line 428, in _find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python3.5/unittest/loader.py", line 369, in 
_get_module_from_name
__import__(name)
  File "/debdry-0.2.1/.pybuild/pythonX.Y_3.5/build/test/test_control.py", line 
2, in 
from debdrylib.tree import Control
  File "/debdry-0.2.1/.pybuild/pythonX.Y_3.5/build/debdrylib/tree.py", line 7, 
in 
import apt_pkg
ImportError: No module named 'apt_pkg'


...

--
Ran 3 tests in 0.000s

FAILED (errors=3)
E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: cd 
/debdry-0.2.1/.pybuild/pythonX.Y_3.5/build; python3.5 -m unittest discover -v 
dh_auto_test: pybuild --test -i python{version} -p 3.5 3.4 --dir . returned 
exit code 13

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/debdry.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: debdry
Source-Version: 0.2.2-1

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

Debian distribution maintenance software
pp.
Paul Wise  (supplier of updated debdry package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 25 Oct 2016 09:19:23 +0800
Source: debdry
Binary: debdry
Architecture: source
Version: 0.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Paul Wise 
Description:
 debdry - Semi-assisted automatic Debian packaging
Closes: 780254 805195
Changes:
 debdry (0.2.2-1) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Antonio Terceiro ]
   * git-debdry-build: switch from `git-buildpackage` to `gbp buildpackage`
 .
   [ Paul Wise ]
   * Fix minor typo in the package description (Closes: #780254)
   * Use canonical links to anonscm.d.o repos
   * Add python3-apt to X-Debdry-Build-Depends (Closes: #805195)
   * Set Maintainer to orphaned (See: #813203)
   * Pass --git-ignore-new to gbp
Checksums-Sha1:
 6f16c74ffbd9d72a0097aca47c91d8cb540b960e 1872 debdry_0.2.2-1.dsc
 ffcdfd4d3c7511fb66903b222db35cf4cddeeb91 28248 debdry_0.2.2.orig.tar.gz
 bfc6621df4f52129f0d08edcd8c1b49fa85509ac 2796 debdry_0.2.2-1.debian.tar.xz
Checksums-Sha256:
 dd6c3e0cbbe9a44e212daa276cd3634a7c92336ca11b3c24c2c7fd56d18edaab 1872 
debdry_0.2.2-1.dsc
 c3c2343474f42e5db298bdb8d99c05113c1e8311bfaf016dd2f442571bdf2b26 28248 
debdry_0.2.2.orig.tar.gz
 4ec56dada8a2d3e9b4acaace7005faa9bac296087a8d72a86fa661ec7679a6b7 2796 
debdry_0.2.2-1.debian.tar.xz
Files:
 813fcd2cc087db4647eb4e608aa73aad 1872 devel optional debdry_0.2.2-1.dsc
 89dfb5f2fe643a4c153a539152443287 28248 devel optional debdry_0.2.2.orig.tar.gz
 8dafab015fd59a2108ac6ef776e18245 2796 devel optional 
debdry_0.2.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#841578: marked as done (gap-float: FTBFS: configure: error: library fplll not found. Using --with-fplll, specify its location, "extern" to compile it locally, or "no" to disable it.)

[Debian Bug Tracking System]

Your message dated Tue, 25 Oct 2016 03:15:38 +0100
with message-id 
and subject line gap-float: FTBFS: false assertion
has caused the Debian Bug report #841578,
regarding gap-float: FTBFS: configure: error: library fplll not found. Using 
--with-fplll, specify its location, "extern" to compile it locally, or "no" to 
disable it.
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.)


-- 
841578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gap-float
Version: 0.7.4+ds-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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):
> checking for mpfi_sqrt in -lmpfi... yes
> checking for mpc.h... yes
> checking for mpc_sqrt in -lmpc... yes
> checking for fplll.h... yes
> checking for lllReduction in -lfplll... no
> configure: error: library fplll not found. Using --with-fplll, specify its 
> location, "extern" to compile it locally, or "no" to disable it.
>   "tail -v -n +0 config.log"

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/21/gap-float_0.7.4+ds-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 ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

It appears that the last package builds well.
Jerome
-BEGIN PGP SIGNATURE-

iQQcBAEBCgAGBQJYDsBKAAoJED+SGaZ/NsaLIMIf/2eWQOJoheXuR3WwyL9eVfyI
KG6shz663v47xMo6wdwzOUZRs2tQwbnTo0hEeVrapbrObRo+wHOJbSAPDXpebiL7
YpCs8xDSpBzfbRD0n9xkWYCl8Yt92jEsznD1uv/gYaUy0Gud9oeIOYdxOkFO49Bf
3KUWYuhze3+kzxiNs7Z7aOdQLbVqmCehrSLKqwxtO0bYERQGz8l1ecJqmUe5rv+5
mvkBz4AiDdgTxSBL6KX8ZLRLviCgRTgTGOjoX5Ydj2muSmdrxFpjMCClSgGB0Un/
uMO0cv1++KnOhNkaQiasUIncD5u/qkUuk32cscy9uG8w1AxHVS1apQJHnVC9N+si
mDN2auTYHWxBJLMeBHdLE0dtz2wesNCFBNHD6T3IKaAah2e7Dgjw0/fg5K/MSvmC
UP9lljk3XaRHB5tOsJbqxNlPuODkofvBS4Z6/Sqy0rYZ7TchKaNGCrU/kT3etNo+
C2MtyIvQdV12ufr6mS4Kl4QSg9i7/dshkPWSjv+jLf7zbpqJRxEfBbRc5cMbNHhC
qi24s4pRmzVBoFVFM7dG+ayRRs8IWI5if9rSeBOaI4Q9HMf586LyLHZwtBp0LGk0
a8EnKfXdS08mCLgNcLJ0uI/R/gD3jzGnjKzcIxSj9mmtWTztXLbp0eM9Wvptxqkp
sU+p7jgrOaK6WDORd1DVZ1JiYfdimi6kk1ET0n8L4c3I96zyyzJQFmEez+X2AD92
LMbTNnVKmvcrg2Vujpw/TGyU83PC1NtRv96eG9lKwkrN/3D9UKQkDH46BVIaqASY
M0SU4Fw68d2BnmKCaHEf4e/dYGtxbgnnNeN5JGmaX0pFGkMYKlg8mMJ2S4m2w+i2
rF264cdl1lFpKeLVBQ4psi3mzV6DJDGHknU3F9KgmP1f4VA68YgE65+UobVBOLdj
jFC3mnVCxQmDQ6n2iyLmj3l1isXInO0WPEYwUrBiPHga+jAPQXKWhPj58P0PRw3T
TYmFqV9nrdYv4S+3acoY0hLCr0AvQczucZrJeFHLWllXCoEpwCfyg7mxbvWqblxp
JN7uKaYT6J2IzEafUVOzjKjmeCX8i1HLh7HHDvkQEY481AILHR5EzWYj3UlLB3Cn
WdeY1bcymEqbElOVJ6+EYmaMJqPWo5dvynhRBIq/NHkPzIWHH8ZrsXBsZDfy6kDY
6cMb4wnL8fPC3TrK0yd8ySUcu3TeL82rx/AnSnjOzVwtiFuxDHZszcoA3fifEIGt
6AmmY45vFxjj4NbyQk/WEOPkeZXNOZHxcHkPhb2m4DX31+6qKJiSNoNk5Zep38WN
xmmrwVXjCkxwQBH9pIY+WjM2YmPmXK4Vf+kmuNPGuXAwq/HW2k07sTg0/PDjqps=
=hGes
-END PGP SIGNATURE End Message ---

Processed (with 1 error): forcibly merging 840853 841060

[Debian Bug Tracking System]

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

> forcemerge 840853 841060
Bug #840853 [qemu] qemu 2.7 requires linuxboot_dma.bin but does not provide or 
depend on it
Bug #841974 [qemu] libguestfs-tools: Appliance get stuck
Unable to merge bugs because:
package of #841060 is 'qemu-system-x86' not 'qemu'
Failed to forcibly merge 840853: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: fun with sudden pie

[Debian Bug Tracking System]

Processing control commands:

> severity 712228 serious
Bug #712228 {Done: Sven Bartscher } [ghc] Hardening flag 
-pie breaks compilation with GHC
Severity set to 'serious' from 'important'

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

Bug#816759: marked as done (minissdpd: CVE-2016-3178 CVE-2016-3179)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2016 23:01:32 +
with message-id 
and subject line Bug#816759: fixed in minissdpd 1.2.20130907-3.2
has caused the Debian Bug report #816759,
regarding minissdpd: CVE-2016-3178 CVE-2016-3179
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.)


-- 
816759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: minissdpd
Version: 1.2.20130907-3
Justification: renders package unusable
Severity: grave
Tags: security patch

Dear Maintainer,

The following bug report provides the technical description and bug fixes
and has been extracted from the detailed security advisory
at http://speirofr.appspot.com/files/advisory/SPADV-2016-02.md

Best,

Vulnerability details
=

The minissdpd daemon (version: 1.2.20130907-3) contains a
improper validation of array index vulnerability (CWE-129)
when processing requests sent to the Unix socket at /var/run/minissdpd.sock
the Unix socket can be accessed by an unprivileged user to send invalid
request causes an out-of-bounds memory access that crashes the minissdpd
daemon.

Technical Details
=

The vulnerability can be triggered by a local unprivileged user performs
the following request:

$ echo -en '\x04\x01\x60\x8f\xff\xff\xff\x7f\x0a' | nc.openbsd -U
/var/run/minissdpd.sock

The request is processed by the processRequest() function at minissdpd.c
which identifies the request of type=4, and performs the parsing of the
"new service" request, the decoding of the length of the usn field
performed at
line 663, sets l = 0x, with p = buf+4, and n = 9, the negative
length
l=-1 passes the check at line 664 with (buf+4-1) < (buf + 9), continuing
with
the allocation of the usn field at line 673, that initialises newserv->usn =
malloc(0), where in the case of Linux malloc(3) the allocator returns a
pointer
that can be later passed to free().  The line 668 attempts to copy
0x
bytes from the message pointer p to newserv->usn, that causes the daemon to
perform an out-of-bound memory access writing outside the allocated buffer.

~~~
663 DECODELENGTH_CHECKLIMIT(l, p, buf + n);
664 if(p+l > buf+n) {
665 syslog(LOG_WARNING, "bad request (length encoding)");
666 goto error;
667 }
...
673 newserv->usn = malloc(l + 1);
674 if(!newserv->usn) {
675 syslog(LOG_ERR, "cannot allocate memory");
676 goto error;
677 }
668 memcpy(newserv->usn, p, l);
~~~

The problem is the incorrect validation on the length returned by the
DECODELENGTH_CHECKLIMIT macro at line 664, that does not consider negative
length values. The fix of the length has already been applied to the
upstream
minissdpd repository see [2], the bug happens at multiple locations after
the
DECODELENGTH_CHECKLIMIT macro that also need to be fixed:

~~~
  DECODELENGTH_CHECKLIMIT(l, p, buf + n);
- if(p+l > buf+n) {
+ if(l > (unsigned)(buf+n-p)) {
 syslog(LOG_ERR, "cannot allocate memory");
 goto error;
  }
~~~

After performing the corrections of the length check the minissdpd daemon
properly detects the invalid negative values and performs error handling.
However, the error handling code at line 753 attempts to free the undefined
memory contents that newserv = malloc() allocated at line 642.

~~~
753 if(newserv) {
754 free(newserv->st);
755 free(newserv->usn);
756 free(newserv->server);
757 free(newserv->location);
758 free(newserv);
759 newserv = NULL;
760 }
~~~

The issue is corrected by applying initialising the contents of the newserv
to zero [3].
That causes free() to correctly operate when freeing the uninitialised
struct fields.

~~~
642 newserv = malloc(sizeof(struct service));
643 if(!newserv) {
644 syslog(LOG_ERR, "cannot allocate memory");
645 goto error;
646 }
+   memset(newserv, 0, sizeof(struct service));
~~~

Solution


Apply the proposed fixes, contained in the patch below.

~~~
>From 2f6746a0c00872b977cc81452d77463aa39609e7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Salva=20Peir=C3=B3?= 
Date: Fri, 4 Mar 2016 12:38:18 +0100
Subject: [PATCH] Fix minissdpd.c handling of request with negative length

---
 minissdpd.c | 9 +
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/minissdpd.c b/minissdpd.c
index 520a6c5..1cd079e 100644

Bug#840847: marked as done (freezegun: FTBFS under some timezones (eg. GMT-14))

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2016 22:52:05 +
with message-id 
and subject line Bug#840847: fixed in freezegun 0.3.7-1
has caused the Debian Bug report #840847,
regarding freezegun: FTBFS under some timezones (eg. GMT-14)
to be marked as done.

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

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


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

Dear Maintainer,

freezegun fails to build from source in logs/unstable undersome timezones (eg. 
TZ="/usr/share/zoneinfo/Etc/GMT-14"):

  [..]

  ==
  FAIL: tests.test_class_import.test_import_localtime
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
  self.test(*self.arg)
File "/build-2nd/freezegun-0.3.6/freezegun/api.py", line 449, in wrapper
  result = func(*args, **kwargs)
File "/build-2nd/freezegun-0.3.6/tests/test_class_import.py", line 83, in 
test_import_localtime
  assert struct.tm_mday == 14
  AssertionError: 
  time.struct_time(tm_year=2012, tm_mon=1, tm_mday=15, tm_hour=2, tm_min=0, 
tm_sec=0, tm_wday=6, tm_yday=15, tm_isdst=-1) = fake_localtime_function()
  assert time.struct_time(tm_year=2012, tm_mon=1, tm_mday=15, tm_hour=2, 
tm_min=0, tm_sec=0, tm_wday=6, tm_yday=15, tm_isdst=-1).tm_year == 2012
  assert time.struct_time(tm_year=2012, tm_mon=1, tm_mday=15, tm_hour=2, 
tm_min=0, tm_sec=0, tm_wday=6, tm_yday=15, tm_isdst=-1).tm_mon == 1
  >>  assert time.struct_time(tm_year=2012, tm_mon=1, tm_mday=15, tm_hour=2, 
tm_min=0, tm_sec=0, tm_wday=6, tm_yday=15, tm_isdst=-1).tm_mday == 14

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/debian/logs/unstable/amd64/freezegun_0.3.6-1.build2.log.gz

(Note the use of fake_localtime, which is going to vary under such extreme
timezones.)




Regards,

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


freezegun.0.3.6-1.logs.unstable.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: freezegun
Source-Version: 0.3.7-1

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

Debian distribution maintenance software
pp.
Federico Ceratto  (supplier of updated freezegun package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 25 Oct 2016 11:05:01 +1400
Source: freezegun
Binary: python-freezegun python3-freezegun
Architecture: source all
Version: 0.3.7-1
Distribution: unstable
Urgency: medium
Maintainer: Federico Ceratto 
Changed-By: Federico Ceratto 
Description:
 python-freezegun - Python library to mock the datetime module in unit testing
 python3-freezegun - Python3 library to mock the datetime module in unit testing
Closes: 840847
Changes:
 freezegun (0.3.7-1) unstable; urgency=medium
 .
   * New upstream release
   * Fix test_import_localtime test (Closes: #840847)
Checksums-Sha1:
 c72859d5bf2fd182c270cf434cd312b60023040e 2156 freezegun_0.3.7-1.dsc
 e48810ee031f742569c131ab8372ddbd6e44ebc8 15771 freezegun_0.3.7.orig.tar.gz
 cbfefd8541da1e353363911aed7905326898f22b 2416 freezegun_0.3.7-1.debian.tar.xz
 4777c8326863424935ff301de3ba745195a513ed 7864 python-freezegun_0.3.7-1_all.deb
 28f3c1ccb4305176f64554726d8d9c44b8042196 6572 python3-freezegun_0.3.7-1_all.deb
Checksums-Sha256:
 0c6e1103567842e45dfdfce021689ff034b9bad03e4cd88c1c36f117d753b6ce 2156 
freezegun_0.3.7-1.dsc
 1ca8e4833f50ab908398d92900865832d3d409f7ae2ede32c153966d404f8192 15771 
freezegun_0.3.7.orig.tar.gz
 

Bug#840546: marked as done (KMail: HTML injection in plain text viewer)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2016 22:32:11 +
with message-id 
and subject line Bug#840546: fixed in kdepimlibs 4:4.14.2-2+deb8u1
has caused the Debian Bug report #840546,
regarding KMail: HTML injection in plain text viewer
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.)


-- 
840546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kdepimlibs
Version: 4:4.4.5-2
Severity: grave
Tags: security patch upstream
Justification: user security hole

KDE Project Security Advisory
=

Title:  KMail: HTML injection in plain text viewer
Risk Rating:Important
CVE:CVE-2016-7966
Platforms:  All
Versions:   kmail >= 4.4.0
Author: Andre Heinecke 
Date:   6 October 2016

Overview


Through a malicious URL that contained a quote character it
was possible to inject HTML code in KMail's plain text viewer.
Due to the parser used on the URL it was not possible to include
the equal sign (=) or a space into the injected HTML, which greatly
reduces the available HTML functionality. Although it is possible
to include an HTML comment indicator to hide content.

Impact
==

An unauthenticated attacker can send out mails with malicious content
that breaks KMail's plain text HTML escape logic. Due to the limitations
of the provided HTML in itself it might not be serious. But as a way
to break out of KMail's restricted Plain text mode this might open
the way to the exploitation of other vulnerabilities in the HTML viewer
code, which is disabled by default.

Workaround
==

None.

Solution


For KDE Frameworks based releases of KMail apply the following patch to
kcoreaddons:
https://quickgit.kde.org/?p=kcoreaddons.git=commitdiff=96e562d9138c100498da38e4c5b4091a226dde12

For kdelibs4 based releases apply the following patch:
https://quickgit.kde.org/?p=kdepimlibs.git=commitdiff=176fee25ca79145ab5c8e2275d248f1a46a8d8cf

Credits
===

Thanks to Roland Tapken for reporting this issue, Andre Heinecke from
Intevation GmbH for analysing the problems and Laurent Montel for
fixing this issue.
From: Montel Laurent 
Date: Fri, 30 Sep 2016 13:55:35 +
Subject: Backport avoid to transform as a url when we have a quote
X-Git-Url: http://quickgit.kde.org/?p=kdepimlibs.git=commitdiff=176fee25ca79145ab5c8e2275d248f1a46a8d8cf
---
Backport avoid to transform as a url when we have a quote
---


--- a/kpimutils/linklocator.cpp
+++ b/kpimutils/linklocator.cpp
@@ -94,6 +94,12 @@
 }
 
 QString LinkLocator::getUrl()
+{
+return getUrlAndCheckValidHref();
+}
+
+
+QString LinkLocator::getUrlAndCheckValidHref(bool *badurl)
 {
   QString url;
   if ( atUrl() ) {
@@ -129,13 +135,26 @@
 
 url.reserve( maxUrlLen() );  // avoid allocs
 int start = mPos;
+bool previousCharIsADoubleQuote = false;
 while ( ( mPos < (int)mText.length() ) &&
 ( mText[mPos].isPrint() || mText[mPos].isSpace() ) &&
 ( ( afterUrl.isNull() && !mText[mPos].isSpace() ) ||
   ( !afterUrl.isNull() && mText[mPos] != afterUrl ) ) ) {
   if ( !mText[mPos].isSpace() ) {   // skip whitespace
-url.append( mText[mPos] );
-if ( url.length() > maxUrlLen() ) {
+  if (mText[mPos] == QLatin1Char('>') && previousCharIsADoubleQuote) {
+  //it's an invalid url
+  if (badurl) {
+  *badurl = true;
+  }
+  return QString();
+  }
+  if (mText[mPos] == QLatin1Char('"')) {
+  previousCharIsADoubleQuote = true;
+  } else {
+  previousCharIsADoubleQuote = false;
+  }
+  url.append( mText[mPos] );
+  if ( url.length() > maxUrlLen() ) {
   break;
 }
   }
@@ -367,7 +386,12 @@
 } else {
   const int start = locator.mPos;
   if ( !( flags & IgnoreUrls ) ) {
-str = locator.getUrl();
+bool badUrl = false;
+str = locator.getUrlAndCheckValidHref();
+if (badUrl) {
+return locator.mText;
+}
+
 if ( !str.isEmpty() ) {
   QString hyperlink;
   if ( str.left( 4 ) == QLatin1String("www.") ) {

--- a/kpimutils/linklocator.h
+++ b/kpimutils/linklocator.h
@@ -107,6 +107,7 @@
   @return The URL at the current scan position, or an empty string.
 */
 QString getUrl();
+QString getUrlAndCheckValidHref(bool *badurl = 0);
 
 /**
   

Bug#816759: minissdpd: CVE-2016-3178 CVE-2016-3179

[James Cowgill]

Control: tags -1 pending

Hi,

I have uploaded the attached NMU to fix this bug. It was mostly based on
the fix already present in wheezy-lts (the CVE patches are identical).
I've done some basic testing of the patches and it fixes the buffer
overflow which can be triggered as described earlier in the bugreport.

I'll see what I can do about fixing this in jessie as well.

Thanks,
James
diff -Nru minissdpd-1.2.20130907/debian/changelog 
minissdpd-1.2.20130907/debian/changelog
--- minissdpd-1.2.20130907/debian/changelog 2016-07-13 19:12:39.0 
+0100
+++ minissdpd-1.2.20130907/debian/changelog 2016-10-24 08:54:59.0 
+0100
@@ -1,3 +1,15 @@
+minissdpd (1.2.20130907-3.2) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Fix CVE-2016-3178 and CVE-2016-3179. (Closes: #816759)
+The minissdpd daemon contains a improper validation of array index
+vulnerability (CWE-129) when processing requests sent to the Unix
+socket at /var/run/minissdpd.sock the Unix socket can be accessed
+by an unprivileged user to send invalid request causes an
+out-of-bounds memory access that crashes the minissdpd daemon.
+
+ -- James Cowgill   Mon, 24 Oct 2016 08:54:59 +0100
+
 minissdpd (1.2.20130907-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru minissdpd-1.2.20130907/debian/patches/CVE-2016-3178.patch 
minissdpd-1.2.20130907/debian/patches/CVE-2016-3178.patch
--- minissdpd-1.2.20130907/debian/patches/CVE-2016-3178.patch   1970-01-01 
01:00:00.0 +0100
+++ minissdpd-1.2.20130907/debian/patches/CVE-2016-3178.patch   2016-10-24 
08:54:59.0 +0100
@@ -0,0 +1,95 @@
+Description: Fix CVE-2016-3178
+ buffer overflow while handling negative length request
+Author: Salva Peiró 
+Origin: upstream, 
https://github.com/miniupnp/miniupnp/commit/b238cade9a173c6f751a34acf8ccff838a62aa47
+Bug-Debian: https://bugs.debian.org/816759
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/minissdpd.c
 b/minissdpd.c
+@@ -555,7 +555,7 @@ void processRequest(struct reqelem * req
+   type = buf[0];
+   p = buf + 1;
+   DECODELENGTH_CHECKLIMIT(l, p, buf + n);
+-  if(p+l > buf+n) {
++  if(l > (unsigned)(buf+n-p)) {
+   syslog(LOG_WARNING, "bad request (length encoding)");
+   goto error;
+   }
+@@ -661,7 +661,7 @@ void processRequest(struct reqelem * req
+   goto error;
+   }
+   DECODELENGTH_CHECKLIMIT(l, p, buf + n);
+-  if(p+l > buf+n) {
++  if(l > (unsigned)(buf+n-p)) {
+   syslog(LOG_WARNING, "bad request (length encoding)");
+   goto error;
+   }
+@@ -679,7 +679,7 @@ void processRequest(struct reqelem * req
+   newserv->usn[l] = '\0';
+   p += l;
+   DECODELENGTH_CHECKLIMIT(l, p, buf + n);
+-  if(p+l > buf+n) {
++  if(l > (unsigned)(buf+n-p)) {
+   syslog(LOG_WARNING, "bad request (length encoding)");
+   goto error;
+   }
+@@ -697,7 +697,7 @@ void processRequest(struct reqelem * req
+   newserv->server[l] = '\0';
+   p += l;
+   DECODELENGTH_CHECKLIMIT(l, p, buf + n);
+-  if(p+l > buf+n) {
++  if(l > (unsigned)(buf+n-p)) {
+   syslog(LOG_WARNING, "bad request (length encoding)");
+   goto error;
+   }
+--- a/testminissdpd.c
 b/testminissdpd.c
+@@ -45,6 +45,23 @@ void printresponse(const unsigned char *
+ #define SENDCOMMAND(command, size) write(s, command, size); \
+   printf("Command written type=%u\n", (unsigned)command[0]);
+ 
++int connect_unix_socket(const char * sockpath)
++{
++  int s;
++  struct sockaddr_un addr;
++
++  s = socket(AF_UNIX, SOCK_STREAM, 0);
++  addr.sun_family = AF_UNIX;
++  strncpy(addr.sun_path, sockpath, sizeof(addr.sun_path));
++  if(connect(s, (struct sockaddr *), sizeof(struct sockaddr_un)) < 
0) {
++  fprintf(stderr, "connecting to %s : ", addr.sun_path);
++  perror("connect");
++  exit(1);
++  }
++  printf("Connected to %s\n", addr.sun_path);
++  return s;
++}
++
+ /* test program for minissdpd */
+ int
+ main(int argc, char * * argv)
+@@ -52,6 +69,7 @@ main(int argc, char * * argv)
+   char command1[] = 
"\x01\x00urn:schemas-upnp-org:device:InternetGatewayDevice";
+   char command2[] = 
"\x02\x00uuid:fc4ec57e-b051-11db-88f8-0060085db3f6::upnp:rootdevice";
+   char command3[] = { 0x03, 0x00 };
++const char bad_command4[] = { 0x04, 0x01, 0x60, 0x8f, 0xff, 0xff, 
0xff, 0x7f};
+   struct sockaddr_un addr;
+   int s;
+   int i;
+@@ -89,6 +107,15 @@ main(int argc, char * * argv)
+   n = read(s, buf, sizeof(buf));
+   printf("Response received %d bytes\n", (int)n);

Bug#841977: libomxil-bellagio0: binaries shipped in shared library package

[Andreas Cadhalpun]

Package: libomxil-bellagio0
Version: 0.9.3-3
Severity: serious
Justification: Debian Policy section 8.2

Dear Maintainer,

libomxil-bellagio0 includes binaries and manual pages:
 * /usr/bin/omxregister-bellagio
 * /usr/bin/omxregister-bellagio-0
 * /usr/share/man/man1/omxregister-bellagio.1.gz
 * /usr/share/man/man1/omxregister-bellagio-0.1.gz

These filenames are not versioned. After a soname bump, the new
library package will thus conflict with libomxil-bellagio0.
Such behavior is forbidden by Debian Policy section 8.2:
"If your package contains files whose names do not change with each
change in the library shared object version, you must not put them
in the shared library package. Otherwise, several versions of the
shared library cannot be installed at the same time without filename
clashes, making upgrades and transitions unnecessarily difficult."

Also libomxil-bellagio0 runs omxregister-bellagio upon installation,
which means it is not installable on a foreign architecture.

Best regards,
Andreas

Processed: affects 841974

[Debian Bug Tracking System]

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

> affects 841974 python-guestfs libguestfs-tools
Bug #841974 [qemu] libguestfs-tools: Appliance get stuck
Bug #840853 [qemu] qemu 2.7 requires linuxboot_dma.bin but does not provide or 
depend on it
Added indication that 841974 affects python-guestfs and libguestfs-tools
Added indication that 840853 affects python-guestfs and libguestfs-tools
> thanks
Stopping processing here.

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

Processed: Bug#816759: minissdpd: CVE-2016-3178 CVE-2016-3179

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #816759 [minissdpd] minissdpd: CVE-2016-3178 CVE-2016-3179
Added tag(s) pending.

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

Processed: Re: Bug#841974: libguestfs-tools: Appliance get stuck

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 qemu
Bug #841974 [libguestfs-tools] libguestfs-tools: Appliance get stuck
Bug reassigned from package 'libguestfs-tools' to 'qemu'.
No longer marked as found in versions libguestfs/1:1.32.7-1.
Ignoring request to alter fixed versions of bug #841974 to the same values 
previously set
> forcemerge -1 840853
Bug #841974 [qemu] libguestfs-tools: Appliance get stuck
Bug #841974 [qemu] libguestfs-tools: Appliance get stuck
Marked as found in versions qemu/1:2.7+dfsg-1.
Bug #840853 [qemu] qemu 2.7 requires linuxboot_dma.bin but does not provide or 
depend on it
Severity set to 'grave' from 'serious'
Removed indication that 840853 affects python-guestfs
Merged 840853 841974

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

Bug#841974: libguestfs-tools: Appliance get stuck

[Hilko Bengen]

Control: reassign -1 qemu
Control: forcemerge -1 840853

* Laurent Bigonville:

> When running libguestfs-test-tool (and also from virt-manager) the
> appliance get stuck at some point.

Thank you for diagnosing the bug. You are right, linuxboot_dma.bin is
missing, this is a problem in qemu.

Cheers,
-Hilko

Processed: Re: Bug#841961: nmu: ocaml_4.02.3-7

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 841938 -1
Bug #841938 [release.debian.org] nmu: ocaml_4.02.3-7
Bug #841961 [release.debian.org] nmu: ocaml_4.02.3-7
837359 was blocked by: 837350 841938
837359 was not blocking any bugs.
Added blocking bug(s) of 837359: 841961
837659 was blocked by: 841938 837350
837659 was not blocking any bugs.
Added blocking bug(s) of 837659: 841961
841961 was not blocked by any bugs.
841961 was blocking: 837359 837659
Added blocking bug(s) of 841961: 837350
841961 was blocked by: 837350
841961 was blocking: 837359 837659
Added blocking bug(s) of 841961: 841921
Merged 841938 841961

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

Bug#841974: libguestfs-tools: Appliance get stuck

[Laurent Bigonville]

Package: libguestfs-tools
Version: 1:1.32.7-1+b2
Severity: grave
Justification: renders package unusable

Hi,

When running libguestfs-test-tool (and also from virt-manager) the
appliance get stuck at some point.

The first problem seems that there is no explicit dependency against
sgabios.

After installing sgabios, the appliance complains about "No bootable
device."

On my machine I've a linuxboot.bin file (from sgabios package) but this
is not enough apparently, if I'm creating a linuxboot_dma.bin symlink
to that file in /usr/share/seabios then the appliance starts as
expected (see the 3rd attached log file).

Laurent Bigonville

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

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

Versions of packages libguestfs-tools depends on:
ii  curl   7.50.1-1
ii  libatk1.0-02.22.0-1
ii  libc6  2.24-5
ii  libcairo2  1.14.6-1+b1
ii  libconfig9 1.5-0.2
ii  libfontconfig1 2.11.0-6.7
ii  libfreetype6   2.6.3-3+b1
ii  libfuse2   2.9.7-1
ii  libgdk-pixbuf2.0-0 2.36.0-1
ii  libglib2.0-0   2.50.1-1
ii  libgtk2.0-02.24.31-1
ii  libguestfs-perl1:1.32.7-1+b2
ii  libguestfs01:1.32.7-1+b2
ii  libintl-perl   1.26-2
ii  liblzma5   5.2.2-1.2
ii  libncurses56.0+20160917-1
ii  libpango-1.0-0 1.40.3-2
ii  libpangocairo-1.0-01.40.3-2
ii  libpangoft2-1.0-0  1.40.3-2
ii  libpcre3   2:8.39-2
ii  libreadline7   7.0-1
ii  libstring-shellquote-perl  1.03-1.2
ii  libsys-virt-perl   2.3.0-1
ii  libtinfo5  6.0+20160917-1
ii  libvirt0   2.3.0-3
ii  libwin-hivex-perl  1.3.13-2+b2
ii  libxml22.9.4+dfsg1-2
ii  libyajl2   2.1.0-2

Versions of packages libguestfs-tools recommends:
ii  gnupg  2.1.15-4

libguestfs-tools suggests no packages.

-- no debconf information
 
 *IMPORTANT NOTICE
 *
 * When reporting bugs, include the COMPLETE, UNEDITED
 * output below in your bug report.
 *
 
PATH=/usr/local/bin:/usr/bin:/bin:/usr/games
SELinux: sh: 1: getenforce: not found
guestfs_get_append: (null)
guestfs_get_autosync: 1
guestfs_get_backend: direct
guestfs_get_backend_settings: []
guestfs_get_cachedir: /var/tmp
guestfs_get_direct: 0
guestfs_get_hv: /usr/bin/qemu-system-x86_64
guestfs_get_memsize: 500
guestfs_get_network: 0
guestfs_get_path: /usr/lib/x86_64-linux-gnu/guestfs
guestfs_get_pgroup: 0
guestfs_get_program: libguestfs-test-tool
guestfs_get_recovery_proc: 1
guestfs_get_selinux: 0
guestfs_get_smp: 1
guestfs_get_tmpdir: /tmp
guestfs_get_trace: 0
guestfs_get_verbose: 1
host_cpu: x86_64
Launching appliance, timeout set to 600 seconds.
libguestfs: launch: program=libguestfs-test-tool
libguestfs: launch: version=1.32.7
libguestfs: launch: backend registered: unix
libguestfs: launch: backend registered: uml
libguestfs: launch: backend registered: libvirt
libguestfs: launch: backend registered: direct
libguestfs: launch: backend=direct
libguestfs: launch: tmpdir=/tmp/libguestfsCF9TMu
libguestfs: launch: umask=0022
libguestfs: launch: euid=1000
libguestfs: [0ms] begin building supermin appliance
libguestfs: [0ms] run supermin
libguestfs: command: run: /usr/bin/supermin
libguestfs: command: run: \ --build
libguestfs: command: run: \ --verbose
libguestfs: command: run: \ --if-newer
libguestfs: command: run: \ --lock /var/tmp/.guestfs-1000/lock
libguestfs: command: run: \ --copy-kernel
libguestfs: command: run: \ -f ext2
libguestfs: command: run: \ --host-cpu x86_64
libguestfs: command: run: \ /usr/lib/x86_64-linux-gnu/guestfs/supermin.d
libguestfs: command: run: \ -o /var/tmp/.guestfs-1000/appliance.d
supermin: version: 5.1.16
supermin: package handler: debian/dpkg
supermin: acquiring lock on /var/tmp/.guestfs-1000/lock
supermin: if-newer: output does not need rebuilding
libguestfs: [7ms] finished building supermin appliance
libguestfs: [7ms] begin testing qemu features
libguestfs: command: run: /usr/bin/qemu-system-x86_64
libguestfs: command: run: \ -display none
libguestfs: command: run: \ -help
libguestfs: command: run: /usr/bin/qemu-system-x86_64
libguestfs: command: run: \ -display none
libguestfs: command: run: \ -version
libguestfs: qemu version 2.7
libguestfs: command: run: /usr/bin/qemu-system-x86_64
libguestfs: command: run: \ 

Bug#841947: [pkg-boost-devel] Bug#841947: libboost-*1.61-dev: Please build static libs with -fPIC

[Gilles Filippini]

Control: block -1 by 841956

Steve M. Robbins a écrit le 24/10/2016 à 20:28 :
> My understanding is that you have to first build boost with the
> pie-enabled compiler chain, then build your package with the new
> boost.
> 
> c.f. https://wiki.ubuntu.com/SecurityTeam/PIE
> 
> 
> Note that using -fPIC on static libs is against current Debian Policy.

You're right. I've just tested building psi4 against a fresh build of
boost1.61, and it works. I've submitted a binnmu request accordingly.

Thanks,

_g.

> 
> On Mon, Oct 24, 2016 at 08:19:13PM +0200, Gilles Filippini wrote:
>> Source: boost1.61
>> Version: 1.61.0+dfsg-3
>> Severity: serious
>> Justification: make other packages FTBFS
>>
> Hi,
> 
> When rebuilding the psi4 package on amd6', it FTBFS with:
> 
> [100%] Linking CXX executable ../../../bin/psi4
> cd /<>/builddir/src/bin/psi4 && /usr/bin/cmake -E 
> cmake_link_script CMakeFiles/psi4.dir/link.txt --verbose=1
> /usr/bin/c++   -DRESTRICT=__restrict__ -Xlinker -export-dynamic -fPIC 
> -std=c++11 -fopenmp -O2 -g -DNDEBUG   
> CMakeFiles/psi4_objlib.dir/export_psio.cc.o 
> CMakeFiles/psi4_objlib.dir/export_mints.cc.o 
> CMakeFiles/psi4_objlib.dir/psi_stop.cc.o 
> CMakeFiles/psi4_objlib.dir/export_functional.cc.o 
> CMakeFiles/psi4_objlib.dir/export_oeprop.cc.o 
> CMakeFiles/psi4_objlib.dir/export_plugins.cc.o 
> CMakeFiles/psi4_objlib.dir/export_blas_lapack.cc.o 
> CMakeFiles/psi4_objlib.dir/export_benchmarks.cc.o 
> CMakeFiles/psi4_objlib.dir/export_efp.cc.o 
> CMakeFiles/psi4_objlib.dir/export_cubeprop.cc.o 
> CMakeFiles/psi4_objlib.dir/clean.cc.o 
> CMakeFiles/psi4_objlib.dir/create_new_plugin.cc.o 
> CMakeFiles/psi4_objlib.dir/script.cc.o 
> CMakeFiles/psi4_objlib.dir/set_memory.cc.o 
> CMakeFiles/psi4_objlib.dir/read_options.cc.o 
> CMakeFiles/psi4_objlib.dir/export_libparallel.cc.o 
> CMakeFiles/versioned_code.dir/version.cc.o 
> CMakeFiles/versioned_code.dir/python.cc.o 
> CMakeFiles/versioned_code.dir/psi_start.cc.o CMakeFiles/versioned_code.dir
>  /psi4.cc.o  -o ../../../bin/psi4 -rdynamic -lutil -lm -lrt -ldl -lpython2.7 
> -Wl,--whole-archive ../../../lib/libadc.a ../../../lib/libccdensity.a 
> ../../../lib/libccenergy.a ../../../lib/libcceom.a ../../../lib/libcchbar.a 
> ../../../lib/libcclambda.a ../../../lib/libccresponse.a 
> ../../../lib/libccsort.a ../../../lib/libcctransort.a 
> ../../../lib/libcctriples.a ../../../lib/libdcft.a ../../../lib/libdetci.a 
> ../../../lib/libdfmp2.a ../../../lib/libdfocc.a ../../../lib/libefp.a 
> ../../../lib/libfindif.a ../../../lib/libfisapt.a ../../../lib/libfnocc.a 
> ../../../lib/libmcscf.a ../../../lib/libmints_wrapper.a 
> ../../../lib/libmrcc.a ../../../lib/libocc.a ../../../lib/liboptking.a 
> ../../../lib/libpsimrcc.a ../../../lib/libsapt.a ../../../lib/libscf.a 
> ../../../lib/libscfgrad.a ../../../lib/libthermo.a ../../../lib/libtransqt2.a 
> ../../../lib/libdmrg.a ../../../lib/lib3index.a ../../../lib/libciomr.a 
> ../../../lib/libdiis.a ../../../lib/libdisp.a ../../../lib/libdpd.a 
> ../../../lib/libefp_solver.a .
>  ./../../lib/libfock.a ../../../lib/libfunctional.a -Wl,--whole-archive 
> ../../../lib/libiwl.a -Wl,--no-whole-archive ../../../lib/libmints.a 
> ../../../lib/libmoinfo.a ../../../lib/liboptions.a ../../../lib/libparallel.a 
> ../../../lib/libparallel2.a ../../../lib/libplugin.a 
> ../../../lib/libsapt_solver.a ../../../lib/libscf_solver.a 
> ../../../lib/libthce.a ../../../lib/libtrans.a ../../../lib/libpsi4util.a 
> ../../../lib/libpsio.a ../../../lib/libPsiUtil.a ../../../lib/libqt.a 
> ../../../lib/libcubeprop.a ../../../lib/libinterface_libefp.a 
> -Wl,--no-whole-archive -Wl,-Bstatic -lboost_filesystem -lboost_python 
> -lboost_regex -lboost_serialization -lboost_system -lboost_timer 
> -lboost_chrono -lboost_thread -lboost_date_time -lboost_atomic -Wl,-Bdynamic 
> -lpthread -llapack -lblas -lpython2.7 -lblas -llapack -lint -lderiv -lutil 
> -ldl -lrt -lm /usr/lib/x86_64-linux-gnu/libchemps2.so -lchemps2 
> /usr/lib/x86_64-linux-gnu/hdf5/serial/lib/libhdf5.so -lsz -lz -lpthread -lm 
> -lpython2.7 -ldl -Wl,-rpath,/usr/l
>  ib/x86_64-linux-gnu/hdf5/serial/lib 
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_filesystem.a(operations.o):
>  relocation R_X86_64_32S against symbol 
> `_ZN5boost6detail15sp_counted_base7destroyEv' can not be used when making a 
> shared object; recompile with -fPIC
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_filesystem.a(path.o):
>  relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making 
> a shared object; recompile with -fPIC
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python.a(list.o):
>  relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making 
> a shared object; recompile with -fPIC
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python.a(dict.o):
>  relocation R_X86_64_32 against `.rodata.str1.1' can 

Processed: Re: [pkg-boost-devel] Bug#841947: libboost-*1.61-dev: Please build static libs with -fPIC

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 841956
Bug #841947 [src:boost1.61] libboost-*1.61-dev: Please build static libs with 
-fPIC
841947 was not blocked by any bugs.
841947 was not blocking any bugs.
Added blocking bug(s) of 841947: 841956

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

Bug#841607: mydumper: FTBFS: dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/

[Mateusz Kijowski]

Hi,


The relevant part seems to be:

CMake Error: The following variables are used in this project, but
they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the
CMake files:
MYSQL_LIBRARIES_atomic
linked by target "mydumper" in directory /<>
linked by target "myloader" in directory /<>

-- Configuring incomplete, errors occurred!

It turns out that mysql_config returns as a necessary lib on amd64 in
sid. libatomic1 package is properly installed as a dependancy, but it
installs atomic.so.1 library symlink which isn't detected by cmake. I
am not sure if this is the desired behaviour, but I would assume so,
since atomic.so (which seems to be required for cmake detection to
work) is part of libgcc-{5,6}-dev packages. So possible solutions are:

a) patch cmake/modules/FindMySQL.cmake to find atomic.so.1
b) add proper libgcc-{5,6}-dev package dependancy

I am not quite sure how to determine which libgcc-dev version I should
use, also I think that this dependancy is not required on i386 (and
possibly other architectures as well). Will update this bug after I
find some more info.

Bug#840428: Forwarded

[Bastien ROUCARIÈS]

control: forwarded -1 https://github.com/ImageMagick/PythonMagick/issues/5



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

Processed: Forwarded

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/ImageMagick/PythonMagick/issues/5
Bug #840428 [src:pythonmagick] pyhonmagick: FTBS with newer experimental 
version of imagemagick
Set Bug forwarded-to-address to 
'https://github.com/ImageMagick/PythonMagick/issues/5'.

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

Bug#841551: marked as done (emacs25: FTBFS: segmentation fault)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2016 19:20:23 +
with message-id 
and subject line Bug#841551: fixed in emacs25 25.1+1-2
has caused the Debian Bug report #841551,
regarding emacs25: FTBFS: segmentation fault
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.)


-- 
841551: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs25
Version: 25.1+1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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[4]: Entering directory '/<>/emacs25-25.1+1/debian/build-x/lisp'
> make[4]: Leaving directory '/<>/emacs25-25.1+1/debian/build-x/lisp'
> ./temacs --batch --load loadup bootstrap
> Error in GnuTLS initialization: ASN1 parser: Generic parsing error.
> Loading loadup.el (source)...
> Using load-path (/<>/emacs25-25.1+1/debian/build-x/lisp 
> /<>/emacs25-25.1+1/debian/build-x/lisp/emacs-lisp 
> /<>/emacs25-25.1+1/debian/build-x/lisp/language 
> /<>/emacs25-25.1+1/debian/build-x/lisp/international 
> /<>/emacs25-25.1+1/debian/build-x/lisp/textmodes 
> /<>/emacs25-25.1+1/debian/build-x/lisp/vc)
> Loading emacs-lisp/byte-run (source)...
> Loading emacs-lisp/backquote (source)...
> Loading subr (source)...
> Loading version (source)...
> Loading widget (source)...
> Loading custom (source)...
> Loading emacs-lisp/map-ynp (source)...
> Loading international/mule (source)...
> Loading international/mule-conf (source)...
> Loading env (source)...
> Loading format (source)...
> Loading bindings (source)...
> Loading window (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/files.el (source)...
> Loading 
> /<>/emacs25-25.1+1/debian/build-x/lisp/emacs-lisp/macroexp.el 
> (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/emacs-lisp/pcase.el 
> (source)...
> Loading 
> /<>/emacs25-25.1+1/debian/build-x/lisp/emacs-lisp/macroexp.el 
> (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/cus-face.el 
> (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/faces.el (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/button.el (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/ldefs-boot.el 
> (source)...
> Loading 
> /<>/emacs25-25.1+1/debian/build-x/lisp/emacs-lisp/nadvice.el 
> (source)...
> Loading 
> /<>/emacs25-25.1+1/debian/build-x/lisp/emacs-lisp/cl-preloaded.el 
> (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/minibuffer.el 
> (source)...
> ../lisp/minibuffer.el: `with-wrapper-hook' is an obsolete macro (as of 24.4); 
> use a -function variable modified by `add-function'.
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/abbrev.el (source)...
> ../lisp/abbrev.el: `with-wrapper-hook' is an obsolete macro (as of 24.4); use 
> a -function variable modified by `add-function'.
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/simple.el (source)...
> ../lisp/simple.el: `with-wrapper-hook' is an obsolete macro (as of 24.4); use 
> a -function variable modified by `add-function'.
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/help.el (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/jka-cmpr-hook.el 
> (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/epa-hook.el 
> (source)...
> Loading 
> /<>/emacs25-25.1+1/debian/build-x/lisp/international/mule-cmds.el 
> (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/case-table.el 
> (source)...
> Loading 
> /<>/emacs25-25.1+1/debian/build-x/lisp/international/characters.el 
> (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/composite.el 
> (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/language/chinese.el 
> (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/language/cyrillic.el 
> (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/language/indian.el 
> (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/language/sinhala.el 
> (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/language/english.el 
> (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/language/ethiopic.el 
> (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/language/european.el 
> (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/language/czech.el 
> (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/language/slovak.el 
> (source)...
> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/language/romanian.el 
> 

Bug#840701: marked as done (emacs25: FTBFS: tests fail or time out)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2016 19:20:23 +
with message-id 
and subject line Bug#841551: fixed in emacs25 25.1+1-2
has caused the Debian Bug report #841551,
regarding emacs25: FTBFS: tests fail or time out
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.)


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

Automated builds of emacs25 on Linux encountered test failures (and a
hang on arm64), as detailed at

https://buildd.debian.org/status/logs.php?pkg=emacs25=25.1%2B1-1

Could you please take a look?

(Non-Linux builds failed for another reason, which I'll report separately
in a moment.)

Thanks!

FYI, even though emacs25 is new, I'm classifying this bug as a regression
because I strongly suspect it would also strike binNMUs on amd64.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Source: emacs25
Source-Version: 25.1+1-2

We believe that the bug you reported is fixed in the latest version of
emacs25, 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.
Rob Browning  (supplier of updated emacs25 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, 24 Oct 2016 13:10:40 -0500
Source: emacs25
Binary: emacs25-lucid emacs25-lucid-dbg emacs25-nox emacs25-nox-dbg emacs25 
emacs25-dbg emacs25-bin-common emacs25-common emacs25-el
Architecture: source amd64 all
Version: 25.1+1-2
Distribution: unstable
Urgency: medium
Maintainer: Rob Browning 
Changed-By: Rob Browning 
Description:
 emacs25- GNU Emacs editor (with GTK+ GUI support)
 emacs25-bin-common - GNU Emacs editor's shared, architecture dependent files
 emacs25-common - GNU Emacs editor's shared, architecture independent 
infrastructur
 emacs25-dbg - Debugging symbols for emacs25
 emacs25-el - GNU Emacs LISP (.el) files
 emacs25-lucid - GNU Emacs editor (with Lucid GUI support)
 emacs25-lucid-dbg - Debugging symbols for emacs25-lucid
 emacs25-nox - GNU Emacs editor (without GUI support)
 emacs25-nox-dbg - Debugging symbols for emacs25-nox
Closes: 841551 841687
Changes:
 emacs25 (25.1+1-2) unstable; urgency=medium
 .
   * Respect DEB_BUILD_OPTIONS=nocheck.  Thanks to David Bremner for
 reporting the issue.
 .
   * Don't dh_auto_clean, and run dh_clean first.  Since we don't build
 in the source tree, we shouldn't clean there either, and let
 dh_clean take care of its bits before we stomp around.
 .
   * Install emacs.appdata.xml as emacs25.appdata.xml.
 .
   * Drop emacs23 icons to avoid future path conflicts.  Thanks to
 Tatsuya Kinoshita for reporting the problem. (Closes: 841687)
 .
   * Fix fix for package-test gpg-agent cleanup race.  Specify
 --no-autostart so that we don't start an agent if one wasn't
 already running when we're requesting shutdown, and delete the
 test dir with "rm -rf" to avoid being affected by vanishing
 sockets (sockets that gpg-agent may be deleting in parallel).
 .
   * Add gnupg-agent build-dep for package-test.
 .
   * Don't segfault if gcc expects -nopie instead of -no-pie.  Thanks
 to Lucas Nussbaum and Aaron M. Ucko for reporting the problem, and
 Sven Joachim for tracking down the upstream patch. (Closes:
 841551)
Checksums-Sha1:
 c8de1bdb65bac187b010d3d4e75c72b05bc782e2 2775 emacs25_25.1+1-2.dsc
 85921b98269b7678605c5a57750f8a5a0982d6cf 49752 emacs25_25.1+1-2.debian.tar.xz
 6d7017c679dbee6a4bb997b16805e2e937e4ec47 281372 
emacs25-bin-common-dbgsym_25.1+1-2_amd64.deb
 64e470321247a02abb3c4414c9bd7ccc89007aae 145854 
emacs25-bin-common_25.1+1-2_amd64.deb
 e4f8e984e025942f7a95184447ccbd7bab341160 13057024 
emacs25-common_25.1+1-2_all.deb
 892ec940d5ff87c06cbaad2b4c5ec1a3f7b80119 

Processed: Fixing the cernlib FTBFS will also rebuild the static libraries

[Debian Bug Tracking System]

Processing control commands:

> reassign 837711 src:cernlib
Bug #837711 [libmathlib2-dev] libmathlib2-dev: Please build libmathlib.a with 
-fPIC
Bug reassigned from package 'libmathlib2-dev' to 'src:cernlib'.
No longer marked as found in versions libmathlib2-dev/20061220+dfsg3-3.
Ignoring request to alter fixed versions of bug #837711 to the same values 
previously set
> forcemerge -1 837711
Bug #837657 [src:cernlib] cernlib: FTBFS with bindnow and PIE enabled
Bug #837711 [src:cernlib] libmathlib2-dev: Please build libmathlib.a with -fPIC
Removed indication that 837711 affects src:paw and paw
Marked as found in versions cernlib/20061220+dfsg3-4.2.
Merged 837657 837711
> affects -1 src:paw
Bug #837657 [src:cernlib] cernlib: FTBFS with bindnow and PIE enabled
Bug #837711 [src:cernlib] libmathlib2-dev: Please build libmathlib.a with -fPIC
Added indication that 837657 affects src:paw
Added indication that 837711 affects src:paw

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

Bug#837657: Fixing the cernlib FTBFS will also rebuild the static libraries

[Adrian Bunk]

Control: reassign 837711 src:cernlib
Control: forcemerge -1 837711
Control: affects -1 src:paw

Fixing the cernlib FTBFS will also rebuild the static libraries
with PIE, and a binNMU is anyways not possible before the FTBFS
is fixed.

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: closing 833735

[Debian Bug Tracking System]

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

> close 833735 8:6.9.5.7+dfsg-1
Bug #833735 {Done: Bastien Roucariès } 
[src:imagemagick] Coder path transversal
The source 'imagemagick' and version '8:6.9.5.7+dfsg-1' do not appear to match 
any binary packages
Marked as fixed in versions imagemagick/8:6.9.5.7+dfsg-1.
Bug #833735 {Done: Bastien Roucariès } 
[src:imagemagick] Coder path transversal
Bug 833735 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#833735: closing 833735

[Salvatore Bonaccorso]

close 833735 8:6.9.5.7+dfsg-1
thanks

Bug#841947: [pkg-boost-devel] Bug#841947: libboost-*1.61-dev: Please build static libs with -fPIC

[Steve M. Robbins]

My understanding is that you have to first build boost with the
pie-enabled compiler chain, then build your package with the new
boost.

c.f. https://wiki.ubuntu.com/SecurityTeam/PIE


Note that using -fPIC on static libs is against current Debian Policy.

-Steve


On Mon, Oct 24, 2016 at 08:19:13PM +0200, Gilles Filippini wrote:
> Source: boost1.61
> Version: 1.61.0+dfsg-3
> Severity: serious
> Justification: make other packages FTBFS
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Hi,
> 
> When rebuilding the psi4 package on amd6', it FTBFS with:
> 
> [100%] Linking CXX executable ../../../bin/psi4
> cd /<>/builddir/src/bin/psi4 && /usr/bin/cmake -E 
> cmake_link_script CMakeFiles/psi4.dir/link.txt --verbose=1
> /usr/bin/c++   -DRESTRICT=__restrict__ -Xlinker -export-dynamic -fPIC 
> -std=c++11 -fopenmp -O2 -g -DNDEBUG   
> CMakeFiles/psi4_objlib.dir/export_psio.cc.o 
> CMakeFiles/psi4_objlib.dir/export_mints.cc.o 
> CMakeFiles/psi4_objlib.dir/psi_stop.cc.o 
> CMakeFiles/psi4_objlib.dir/export_functional.cc.o 
> CMakeFiles/psi4_objlib.dir/export_oeprop.cc.o 
> CMakeFiles/psi4_objlib.dir/export_plugins.cc.o 
> CMakeFiles/psi4_objlib.dir/export_blas_lapack.cc.o 
> CMakeFiles/psi4_objlib.dir/export_benchmarks.cc.o 
> CMakeFiles/psi4_objlib.dir/export_efp.cc.o 
> CMakeFiles/psi4_objlib.dir/export_cubeprop.cc.o 
> CMakeFiles/psi4_objlib.dir/clean.cc.o 
> CMakeFiles/psi4_objlib.dir/create_new_plugin.cc.o 
> CMakeFiles/psi4_objlib.dir/script.cc.o 
> CMakeFiles/psi4_objlib.dir/set_memory.cc.o 
> CMakeFiles/psi4_objlib.dir/read_options.cc.o 
> CMakeFiles/psi4_objlib.dir/export_libparallel.cc.o 
> CMakeFiles/versioned_code.dir/version.cc.o 
> CMakeFiles/versioned_code.dir/python.cc.o 
> CMakeFiles/versioned_code.dir/psi_start.cc.o CMakeFiles/versioned_code.dir
>  /psi4.cc.o  -o ../../../bin/psi4 -rdynamic -lutil -lm -lrt -ldl -lpython2.7 
> -Wl,--whole-archive ../../../lib/libadc.a ../../../lib/libccdensity.a 
> ../../../lib/libccenergy.a ../../../lib/libcceom.a ../../../lib/libcchbar.a 
> ../../../lib/libcclambda.a ../../../lib/libccresponse.a 
> ../../../lib/libccsort.a ../../../lib/libcctransort.a 
> ../../../lib/libcctriples.a ../../../lib/libdcft.a ../../../lib/libdetci.a 
> ../../../lib/libdfmp2.a ../../../lib/libdfocc.a ../../../lib/libefp.a 
> ../../../lib/libfindif.a ../../../lib/libfisapt.a ../../../lib/libfnocc.a 
> ../../../lib/libmcscf.a ../../../lib/libmints_wrapper.a 
> ../../../lib/libmrcc.a ../../../lib/libocc.a ../../../lib/liboptking.a 
> ../../../lib/libpsimrcc.a ../../../lib/libsapt.a ../../../lib/libscf.a 
> ../../../lib/libscfgrad.a ../../../lib/libthermo.a ../../../lib/libtransqt2.a 
> ../../../lib/libdmrg.a ../../../lib/lib3index.a ../../../lib/libciomr.a 
> ../../../lib/libdiis.a ../../../lib/libdisp.a ../../../lib/libdpd.a 
> ../../../lib/libefp_solver.a .
>  ./../../lib/libfock.a ../../../lib/libfunctional.a -Wl,--whole-archive 
> ../../../lib/libiwl.a -Wl,--no-whole-archive ../../../lib/libmints.a 
> ../../../lib/libmoinfo.a ../../../lib/liboptions.a ../../../lib/libparallel.a 
> ../../../lib/libparallel2.a ../../../lib/libplugin.a 
> ../../../lib/libsapt_solver.a ../../../lib/libscf_solver.a 
> ../../../lib/libthce.a ../../../lib/libtrans.a ../../../lib/libpsi4util.a 
> ../../../lib/libpsio.a ../../../lib/libPsiUtil.a ../../../lib/libqt.a 
> ../../../lib/libcubeprop.a ../../../lib/libinterface_libefp.a 
> -Wl,--no-whole-archive -Wl,-Bstatic -lboost_filesystem -lboost_python 
> -lboost_regex -lboost_serialization -lboost_system -lboost_timer 
> -lboost_chrono -lboost_thread -lboost_date_time -lboost_atomic -Wl,-Bdynamic 
> -lpthread -llapack -lblas -lpython2.7 -lblas -llapack -lint -lderiv -lutil 
> -ldl -lrt -lm /usr/lib/x86_64-linux-gnu/libchemps2.so -lchemps2 
> /usr/lib/x86_64-linux-gnu/hdf5/serial/lib/libhdf5.so -lsz -lz -lpthread -lm 
> -lpython2.7 -ldl -Wl,-rpath,/usr/l
>  ib/x86_64-linux-gnu/hdf5/serial/lib 
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_filesystem.a(operations.o):
>  relocation R_X86_64_32S against symbol 
> `_ZN5boost6detail15sp_counted_base7destroyEv' can not be used when making a 
> shared object; recompile with -fPIC
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_filesystem.a(path.o):
>  relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making 
> a shared object; recompile with -fPIC
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python.a(list.o):
>  relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making 
> a shared object; recompile with -fPIC
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python.a(dict.o):
>  relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making 
> a shared object; recompile with -fPIC
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python.a(tuple.o):
>  relocation R_X86_64_32 

Processed: nmu: madness_0.10-8

[Debian Bug Tracking System]

Processing control commands:

> block 837699 by -1
Bug #837699 [src:madness] libmadness-dev: Please build libMAD*.a with -fPIC
837699 was not blocked by any bugs.
837699 was not blocking any bugs.
Added blocking bug(s) of 837699: 841948

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

Bug#837699: Only a binNMU should be required

[Adrian Bunk]

Control: retitle -1 madness needs PIE binNMU

A binNMU should be sufficient to fix this, and is already requested.

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: Only a binNMU should be required

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 madness needs PIE binNMU
Bug #837699 [src:madness] libmadness-dev: Please build libMAD*.a with -fPIC
Changed Bug title to 'madness needs PIE binNMU' from 'libmadness-dev: Please 
build libMAD*.a with -fPIC'.

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

Processed: emacs25: merge segfault bugs

[Debian Bug Tracking System]

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

> merge 840701 841551
Bug #840701 [src:emacs25] emacs25: FTBFS: tests fail or time out
Bug #840701 [src:emacs25] emacs25: FTBFS: tests fail or time out
Added tag(s) stretch and sid.
Bug #841551 [src:emacs25] emacs25: FTBFS: segmentation fault
Merged 840701 841551
> thanks
Stopping processing here.

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

Bug#837686: Only a binNMU should be required

[Adrian Bunk]

Control: retitle -1 libint needs PIE binNMU

A binNMU should be sufficient to fix this, and is already requested.

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: Also execute the commands

[Debian Bug Tracking System]

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

> reassign 811996 src:ptlib
Bug #811996 [ptlib] ptlib: FTBFS with GCC 6: call overloaded is ambiguous
Bug reassigned from package 'ptlib' to 'src:ptlib'.
No longer marked as found in versions 2.10.11~dfsg-2.
Ignoring request to alter fixed versions of bug #811996 to the same values 
previously set
> reassign 837577 src:ptlib
Bug #837577 [src:t38modem] t38modem: FTBFS with bindnow and PIE enabled
Bug reassigned from package 'src:t38modem' to 'src:ptlib'.
No longer marked as found in versions t38modem/2.0.0-4.
Ignoring request to alter fixed versions of bug #837577 to the same values 
previously set
> forcemerge 811996 837577
Bug #811996 [src:ptlib] ptlib: FTBFS with GCC 6: call overloaded is ambiguous
Bug #837577 [src:ptlib] t38modem: FTBFS with bindnow and PIE enabled
Merged 811996 837577
> affects 811996 src:t38modem
Bug #811996 [src:ptlib] ptlib: FTBFS with GCC 6: call overloaded is ambiguous
Bug #837577 [src:ptlib] t38modem: FTBFS with bindnow and PIE enabled
Added indication that 811996 affects src:t38modem
Added indication that 837577 affects src:t38modem
> thanks
Stopping processing here.

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

Processed (with 1 error): Retrying the merge

[Debian Bug Tracking System]

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

> merge 837359 837659
Bug #837359 [src:ocaml] ocaml needs PIE binNMU
Unable to merge bugs because:
blockedby of #837659 is '841938 837350' not '837350 841938'
affects of #837659 is 
'camlp5,ara,ocaml-data-notation,tyxml,js-of-ocaml,ocamlgraph,ocamlmod,ocurl,dose3,ocaml-fileutils,why3,atdgen,ben,ocaml-zarith,ocaml-re,alt-ergo,pcre-ocaml,mingw-ocaml,findlib,supermin,optcomp,ocaml-expect,scilab,marionnet,approx,extlib,sexplib310,misery,variantslib,pagodacf,type-conv,janest-core-extended,camlimages,oasis,caml-crush,ocsigenserver,advi,obus,gmetadom,ocaml-batteries,fieldslib,coccinelle,jsonm,lambda-term,laby,ocaml-sqlite3,janest-core-kernel,janest-core,nss-passwords,ocaml-sqlexpr,ocamlgsl,virt-top,camomile,ocaml-textutils,orpie,cryptokit,enumerate,libguestfs,cppo,omake,ocamldsort,ocaml-base64,ocamlnet,mtasc,ocaml-csv,ppx-sexp-conv,confluence,camlmix,postgresql-ocaml,pipebang,yojson,uuidm,utop,monotone-viz,coinst,spamoracle,xml-light,custom-printf,xmlm,coq,ocamlcreal,ocamlrss,pdfsandwich,biniou,comparelib,botch,pa-test,ocaml-estring,menhir,wyrd,ocaml-res,galax,ocaml-gettext,pa-ounit,ocaml-benchmark,ocaml-ipaddr,cduce,pa-bench,ocaml-atd,ppx-core,ocaml-extunix,ocaml-melt,mlgmp,liquidsoap,pa-structural-sexp,haxe,zed,ppx-type-conv,ocaml-reins,ocaml-re2,freetennis,kalzium,opam,ocamlviz,herelib,ocamlbricks,ocp-indent,ocaml-libvirt,typerep,js-build-tools,mlpost,perl4caml,cudf,unison,ppx-driver,prooftree,eliom,ocaml-deriving-ocsigen,matita,ounit,caml2html,geneweb,pgocaml,ppx-optcomp,dochelp,ocaml-usb,ppx-deriving,bin-prot'
 not 
'camlimages,ocaml-re,ben,coccinelle,prooftree,janest-core-extended,unison,ocamlbricks,obus,src:hivex,fieldslib,orpie,ocamlmod,uuidm,confluence,ppx-core,ocp-indent,ocamlgraph,mingw-ocaml,ocaml-expect,xml-light,ocaml-libvirt,haxe,mtasc,cppo,ocsigenserver,cryptokit,coinst,pa-bench,mlpost,janest-core,ocaml-usb,utop,camlp5,pdfsandwich,ocaml-benchmark,approx,cduce,comparelib,marionnet,wyrd,enumerate,virt-top,matita,alt-ergo,atdgen,ppx-deriving,ocaml-re2,caml2html,ppx-optcomp,pa-ounit,ocaml-base64,ocamlgsl,spamoracle,typerep,variantslib,monotone-viz,ocamlcreal,caml-crush,yojson,extlib,ocaml-ipaddr,mlgmp,geneweb,ocaml-csv,ocaml-zarith,js-of-ocaml,ocamlnet,menhir,ppx-driver,biniou,dochelp,gmetadom,zed,ocaml-estring,cudf,ocaml-textutils,ocamlrss,ocaml-res,botch,js-build-tools,why3,ocaml-melt,type-conv,pipebang,ocaml-atd,omake,kalzium,dose3,ocaml-data-notation,pagodacf,perl4caml,xmlm,tyxml,opam,herelib,galax,advi,pa-test,pcre-ocaml,postgresql-ocaml,oasis,coq,findlib,supermin,ocaml-deriving-ocsigen,ppx-type-conv,nss-passwords,sexplib310,janest-core-kernel,libguestfs,ocaml-reins,ocaml-batteries,ocaml-sqlexpr,ocamlviz,ocamldsort,laby,camomile,ocaml-fileutils,ocaml-sqlite3,liquidsoap,jsonm,lambda-term,ocurl,ocaml-gettext,custom-printf,optcomp,freetennis,ounit,misery,pgocaml,ara,ppx-sexp-conv,camlmix,pa-structural-sexp,eliom,scilab,ocaml-extunix,bin-prot'
Failed to merge 837359: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#841947: libboost-*1.61-dev: Please build static libs with -fPIC

[Gilles Filippini]

Source: boost1.61
Version: 1.61.0+dfsg-3
Severity: serious
Justification: make other packages FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

When rebuilding the psi4 package on amd6', it FTBFS with:

[100%] Linking CXX executable ../../../bin/psi4
cd /<>/builddir/src/bin/psi4 && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/psi4.dir/link.txt --verbose=1
/usr/bin/c++   -DRESTRICT=__restrict__ -Xlinker -export-dynamic -fPIC 
-std=c++11 -fopenmp -O2 -g -DNDEBUG   
CMakeFiles/psi4_objlib.dir/export_psio.cc.o 
CMakeFiles/psi4_objlib.dir/export_mints.cc.o 
CMakeFiles/psi4_objlib.dir/psi_stop.cc.o 
CMakeFiles/psi4_objlib.dir/export_functional.cc.o 
CMakeFiles/psi4_objlib.dir/export_oeprop.cc.o 
CMakeFiles/psi4_objlib.dir/export_plugins.cc.o 
CMakeFiles/psi4_objlib.dir/export_blas_lapack.cc.o 
CMakeFiles/psi4_objlib.dir/export_benchmarks.cc.o 
CMakeFiles/psi4_objlib.dir/export_efp.cc.o 
CMakeFiles/psi4_objlib.dir/export_cubeprop.cc.o 
CMakeFiles/psi4_objlib.dir/clean.cc.o 
CMakeFiles/psi4_objlib.dir/create_new_plugin.cc.o 
CMakeFiles/psi4_objlib.dir/script.cc.o 
CMakeFiles/psi4_objlib.dir/set_memory.cc.o 
CMakeFiles/psi4_objlib.dir/read_options.cc.o 
CMakeFiles/psi4_objlib.dir/export_libparallel.cc.o 
CMakeFiles/versioned_code.dir/version.cc.o 
CMakeFiles/versioned_code.dir/python.cc.o 
CMakeFiles/versioned_code.dir/psi_start.cc.o CMakeFiles/versioned_code.dir
 /psi4.cc.o  -o ../../../bin/psi4 -rdynamic -lutil -lm -lrt -ldl -lpython2.7 
-Wl,--whole-archive ../../../lib/libadc.a ../../../lib/libccdensity.a 
../../../lib/libccenergy.a ../../../lib/libcceom.a ../../../lib/libcchbar.a 
../../../lib/libcclambda.a ../../../lib/libccresponse.a 
../../../lib/libccsort.a ../../../lib/libcctransort.a 
../../../lib/libcctriples.a ../../../lib/libdcft.a ../../../lib/libdetci.a 
../../../lib/libdfmp2.a ../../../lib/libdfocc.a ../../../lib/libefp.a 
../../../lib/libfindif.a ../../../lib/libfisapt.a ../../../lib/libfnocc.a 
../../../lib/libmcscf.a ../../../lib/libmints_wrapper.a ../../../lib/libmrcc.a 
../../../lib/libocc.a ../../../lib/liboptking.a ../../../lib/libpsimrcc.a 
../../../lib/libsapt.a ../../../lib/libscf.a ../../../lib/libscfgrad.a 
../../../lib/libthermo.a ../../../lib/libtransqt2.a ../../../lib/libdmrg.a 
../../../lib/lib3index.a ../../../lib/libciomr.a ../../../lib/libdiis.a 
../../../lib/libdisp.a ../../../lib/libdpd.a ../../../lib/libefp_solver.a .
 ./../../lib/libfock.a ../../../lib/libfunctional.a -Wl,--whole-archive 
../../../lib/libiwl.a -Wl,--no-whole-archive ../../../lib/libmints.a 
../../../lib/libmoinfo.a ../../../lib/liboptions.a ../../../lib/libparallel.a 
../../../lib/libparallel2.a ../../../lib/libplugin.a 
../../../lib/libsapt_solver.a ../../../lib/libscf_solver.a 
../../../lib/libthce.a ../../../lib/libtrans.a ../../../lib/libpsi4util.a 
../../../lib/libpsio.a ../../../lib/libPsiUtil.a ../../../lib/libqt.a 
../../../lib/libcubeprop.a ../../../lib/libinterface_libefp.a 
-Wl,--no-whole-archive -Wl,-Bstatic -lboost_filesystem -lboost_python 
-lboost_regex -lboost_serialization -lboost_system -lboost_timer -lboost_chrono 
-lboost_thread -lboost_date_time -lboost_atomic -Wl,-Bdynamic -lpthread 
-llapack -lblas -lpython2.7 -lblas -llapack -lint -lderiv -lutil -ldl -lrt -lm 
/usr/lib/x86_64-linux-gnu/libchemps2.so -lchemps2 
/usr/lib/x86_64-linux-gnu/hdf5/serial/lib/libhdf5.so -lsz -lz -lpthread -lm 
-lpython2.7 -ldl -Wl,-rpath,/usr/l
 ib/x86_64-linux-gnu/hdf5/serial/lib 
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_filesystem.a(operations.o):
 relocation R_X86_64_32S against symbol 
`_ZN5boost6detail15sp_counted_base7destroyEv' can not be used when making a 
shared object; recompile with -fPIC
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_filesystem.a(path.o):
 relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a 
shared object; recompile with -fPIC
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python.a(list.o):
 relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a 
shared object; recompile with -fPIC
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python.a(dict.o):
 relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a 
shared object; recompile with -fPIC
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python.a(tuple.o):
 relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a 
shared object; recompile with -fPIC
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python.a(str.o):
 relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a 
shared object; recompile with -fPIC
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libboost_python.a(from_python.o):
 relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a 
shared object; 

Processed: Only a binNMU should be required

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libint needs PIE binNMU
Bug #837686 [libint-dev] libint-dev: Please build static libraries with -fPIC
Changed Bug title to 'libint needs PIE binNMU' from 'libint-dev: Please build 
static libraries with -fPIC'.

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

Processed (with 1 error): Retrying the merge

[Debian Bug Tracking System]

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

> forcemerge 837659 837359
Bug #837659 [src:ocaml] hivex: FTBFS with bindnow and PIE enabled
Bug #837359 [src:ocaml] ocaml needs PIE binNMU
Removed indication that 837359 affects libguestfs, ocaml-benchmark, coinst, 
ocaml-melt, ocsigenserver, ppx-driver, ppx-type-conv, ocamlnet, camlimages, 
matita, oasis, unison, galax, ocaml-zarith, dose3, ocaml-fileutils, ppx-core, 
ocp-indent, comparelib, bin-prot, pa-bench, ounit, ocaml-sqlite3, monotone-viz, 
janest-core-kernel, typerep, ocaml-libvirt, cppo, herelib, xml-light, omake, 
lambda-term, ocurl, jsonm, enumerate, pdfsandwich, variantslib, ocaml-ipaddr, 
js-build-tools, pgocaml, marionnet, spamoracle, confluence, wyrd, mlpost, 
ocaml-extunix, advi, janest-core, ocaml-re, pipebang, ocamlgsl, ocaml-re2, 
cduce, camomile, ocamlmod, cryptokit, ocamlrss, ppx-deriving, botch, cudf, 
pa-test, nss-passwords, ocamlviz, ocamlbricks, tyxml, ocaml-data-notation, 
ocamlcreal, type-conv, geneweb, ocaml-textutils, virt-top, ocaml-expect, 
ocaml-csv, js-of-ocaml, why3, xmlm, ocaml-sqlexpr, uuidm, 
ocaml-deriving-ocsigen, ocaml-batteries, pagodacf, pa-structural-sexp, 
sexplib310, liquidsoap, eliom, kalzium, mingw-ocaml, perl4caml, opam, scilab, 
mlgmp, orpie, menhir, camlp5, coq, alt-ergo, ocaml-estring, supermin, 
postgresql-ocaml, mtasc, ocamlgraph, ocamldsort, approx, ben, gmetadom, 
camlmix, ppx-sexp-conv, ocaml-atd, custom-printf, ocaml-res, 
janest-core-extended, laby, ocaml-gettext, caml2html, atdgen, optcomp, 
caml-crush, utop, biniou, pcre-ocaml, freetennis, src:hivex, fieldslib, 
ocaml-reins, ppx-optcomp, ara, prooftree, misery, obus, haxe, yojson, extlib, 
findlib, zed, coccinelle, pa-ounit, ocaml-usb, dochelp, and ocaml-base64
Added indication that 837359 affects 
camlp5,ara,ocaml-data-notation,tyxml,js-of-ocaml,ocamlgraph,ocamlmod,ocurl,dose3,ocaml-fileutils,why3,atdgen,ben,ocaml-zarith,ocaml-re,alt-ergo,pcre-ocaml,mingw-ocaml,findlib,supermin,optcomp,ocaml-expect,scilab,marionnet,approx,extlib,sexplib310,misery,variantslib,pagodacf,type-conv,janest-core-extended,camlimages,oasis,caml-crush,ocsigenserver,advi,obus,gmetadom,ocaml-batteries,fieldslib,coccinelle,jsonm,lambda-term,laby,ocaml-sqlite3,janest-core-kernel,janest-core,nss-passwords,ocaml-sqlexpr,ocamlgsl,virt-top,camomile,ocaml-textutils,orpie,cryptokit,enumerate,libguestfs,cppo,omake,ocamldsort,ocaml-base64,ocamlnet,mtasc,ocaml-csv,ppx-sexp-conv,confluence,camlmix,postgresql-ocaml,pipebang,yojson,uuidm,utop,monotone-viz,coinst,spamoracle,xml-light,custom-printf,xmlm,coq,ocamlcreal,ocamlrss,pdfsandwich,biniou,comparelib,botch,pa-test,ocaml-estring,menhir,wyrd,ocaml-res,galax,ocaml-gettext,pa-ounit,ocaml-benchmark,ocaml-ipaddr,cduce,pa-bench,ocaml-atd,ppx-core,ocaml-extunix,ocaml-melt,mlgmp,liquidsoap,pa-structural-sexp,haxe,zed,ppx-type-conv,ocaml-reins,ocaml-re2,freetennis,kalzium,opam,ocamlviz,herelib,ocamlbricks,ocp-indent,ocaml-libvirt,typerep,js-build-tools,mlpost,perl4caml,cudf,unison,ppx-driver,prooftree,eliom,ocaml-deriving-ocsigen,matita,ounit,caml2html,geneweb,pgocaml,ppx-optcomp,dochelp,ocaml-usb,ppx-deriving,bin-prot
Bug #837359 [src:ocaml] ocaml needs PIE binNMU
Unable to complete merge on previous attempt; trying again (retry: 2)
Bug #837359 [src:ocaml] ocaml needs PIE binNMU
Unable to complete merge on previous attempt; trying again (retry: 3)
Bug #837359 [src:ocaml] ocaml needs PIE binNMU
After four attempts, the following changes were unable to be made:
blockedby of #837359 is '837350 841938' not '841938 837350'
Failed to forcibly merge 837659: Unable to modify bugs so they could be merged.

> thanks
Stopping processing here.

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

Processed: nmu: libint_1.1.6-2

[Debian Bug Tracking System]

Processing control commands:

> block 837686 by -1
Bug #837686 [libint-dev] libint-dev: Please build static libraries with -fPIC
837686 was not blocked by any bugs.
837686 was not blocking any bugs.
Added blocking bug(s) of 837686: 841946

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

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

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2016 18:04:49 +
with message-id 
and subject line Bug#806107: fixed in signond 8.59-1
has caused the Debian Bug report #806107,
regarding signond: 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.)


-- 
806107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:signond
Version: 8.57+20150423-3
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 fakeroot debian/rules binary-indep
/usr/bin/make -f debian/rules dhmk_run_build-indep_commands 
DHMK_TARGET="build-indep"
make[1]: Entering directory '/<>/signond-8.57+20150423'
dh_testdir  # [-i]
# Running override target (override_dh_auto_build)
test -z "`ls debian/*.debhelper.log 2>/dev/null`" || sed -i 
'/^override_dh_auto_build[[:space:]]/d' debian/*.debhelper.log
/usr/bin/make -f debian/rules override_dh_auto_build 
DH_INTERNAL_OVERRIDE="dh_auto_build"  # [-i]
make[2]: Entering directory '/<>/signond-8.57+20150423'
QT_SELECT=qt4 dh_auto_build -Bbuild/qt4
make -j1
make[3]: Entering directory '/<>/signond-8.57+20150423/build/qt4'
cd lib/ && make -f Makefile 
make[4]: Entering directory '/<>/signond-8.57+20150423/build/qt4/lib'
cd signond/ && make -f Makefile 
make[5]: Entering directory 
'/<>/signond-8.57+20150423/build/qt4/lib/signond'
cd SignOn/ && make -f Makefile 
make[6]: Entering directory 
'/<>/signond-8.57+20150423/build/qt4/lib/signond/SignOn'
make -f Makefile.SignOnExtension 
make[7]: Entering directory 
'/<>/signond-8.57+20150423/build/qt4/lib/signond/SignOn'
make[7]: Nothing to be done for 'first'.
make[7]: Leaving directory 
'/<>/signond-8.57+20150423/build/qt4/lib/signond/SignOn'
make[6]: Leaving directory 
'/<>/signond-8.57+20150423/build/qt4/lib/signond/SignOn'

[... snipped ...]

dh_auto_install -Bbuild/qt4 -plibsignon-qt-dev
dh_auto_install: No packages to build.
mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake/SignOnQt 
debian/tmp/usr/lib/x86_64-linux-gnu/cmake/SignOnQt4
mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/cmake/SignOnQt': No such 
file or directory
debian/rules:39: recipe for target 'override_dh_auto_install' failed
make[2]: *** [override_dh_auto_install] Error 1
make[2]: Leaving directory '/<>/signond-8.57+20150423'
/usr/share/pkg-kde-tools/qt-kde-team/2/dhmk.mk:97: recipe for target 
'pre_install-indep_dh_auto_install' failed
make[1]: *** [pre_install-indep_dh_auto_install] Error 2
make[1]: Leaving directory '/<>/signond-8.57+20150423'
/usr/share/pkg-kde-tools/qt-kde-team/2/dhmk.mk:110: recipe for target 
'debian/dhmk_install-indep' failed
make: *** [debian/dhmk_install-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one, but I can give some general hints:

* If all the arch-independent packages are dummy transitional packages
released with jessie, the easy fix is to drop them now.
 
* If not, debian/rules should be modified so that the binary-indep
target works in all cases, even when binary-arch is not used (this is
what the "Architecture: all" autobuilder does). For that:

* If you are using debhelper, you might want to use options -a and -i
for dh_* commands so that they do not act on packages they do not
have to act.

* Also, if you are using dh, the (independently) optional targets
override_dh_foo-arch and override_dh_foo-indep (for several values
of "foo") may be useful to write a debian/rules which behaves exactly
as desired.


After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B"
work properly, this package will be suitable to be uploaded in
source-only form if you wish (you might want to try it).

Thanks.
--- End Message ---
--- Begin Message ---
Source: signond
Source-Version: 8.59-1

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

Processed (with 1 error): This is the same bug

[Debian Bug Tracking System]

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

> reassign 837659 src:ocaml
Bug #837659 [ocaml-nox] hivex: FTBFS with bindnow and PIE enabled
Bug reassigned from package 'ocaml-nox' to 'src:ocaml'.
Ignoring request to alter found versions of bug #837659 to the same values 
previously set
Ignoring request to alter fixed versions of bug #837659 to the same values 
previously set
> forcemerge 837359 837659
Bug #837359 [src:ocaml] ocaml needs PIE binNMU
Bug #837659 [src:ocaml] hivex: FTBFS with bindnow and PIE enabled
837659 was not blocked by any bugs.
837659 was not blocking any bugs.
Added blocking bug(s) of 837659: 841938
837659 was blocked by: 841938
837659 was not blocking any bugs.
Added blocking bug(s) of 837659: 837350
Removed indication that 837659 affects src:hivex
Added indication that 837659 affects 
camlp5,ara,ocaml-data-notation,tyxml,js-of-ocaml,ocamlgraph,ocamlmod,ocurl,dose3,ocaml-fileutils,why3,atdgen,ben,ocaml-zarith,ocaml-re,alt-ergo,pcre-ocaml,mingw-ocaml,findlib,supermin,optcomp,ocaml-expect,scilab,marionnet,approx,extlib,sexplib310,misery,variantslib,pagodacf,type-conv,janest-core-extended,camlimages,oasis,caml-crush,ocsigenserver,advi,obus,gmetadom,ocaml-batteries,fieldslib,coccinelle,jsonm,lambda-term,laby,ocaml-sqlite3,janest-core-kernel,janest-core,nss-passwords,ocaml-sqlexpr,ocamlgsl,virt-top,camomile,ocaml-textutils,orpie,cryptokit,enumerate,libguestfs,cppo,omake,ocamldsort,ocaml-base64,ocamlnet,mtasc,ocaml-csv,ppx-sexp-conv,confluence,camlmix,postgresql-ocaml,pipebang,yojson,uuidm,utop,monotone-viz,coinst,spamoracle,xml-light,custom-printf,xmlm,coq,ocamlcreal,ocamlrss,pdfsandwich,biniou,comparelib,botch,pa-test,ocaml-estring,menhir,wyrd,ocaml-res,galax,ocaml-gettext,pa-ounit,ocaml-benchmark,ocaml-ipaddr,cduce,pa-bench,ocaml-atd,ppx-core,ocaml-extunix,ocaml-melt,mlgmp,liquidsoap,pa-structural-sexp,haxe,zed,ppx-type-conv,ocaml-reins,ocaml-re2,freetennis,kalzium,opam,ocamlviz,herelib,ocamlbricks,ocp-indent,ocaml-libvirt,typerep,js-build-tools,mlpost,perl4caml,cudf,unison,ppx-driver,prooftree,eliom,ocaml-deriving-ocsigen,matita,ounit,caml2html,geneweb,pgocaml,ppx-optcomp,dochelp,ocaml-usb,ppx-deriving,bin-prot
Marked as found in versions ocaml/4.02.3-7.
Bug #837659 [src:ocaml] hivex: FTBFS with bindnow and PIE enabled
Unable to complete merge on previous attempt; trying again (retry: 2)
Bug #837659 [src:ocaml] hivex: FTBFS with bindnow and PIE enabled
Unable to complete merge on previous attempt; trying again (retry: 3)
Bug #837659 [src:ocaml] hivex: FTBFS with bindnow and PIE enabled
After four attempts, the following changes were unable to be made:
blockedby of #837659 is '841938 837350' not '837350 841938'
Failed to forcibly merge 837359: Unable to modify bugs so they could be merged.

> affects 837359 src:hivex
Bug #837359 [src:ocaml] ocaml needs PIE binNMU
Added indication that 837359 affects src:hivex
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> severity 841741 grave
Bug #841741 [grub-common] grub-probe fails to find GRUB drive
Severity set to 'grave' from 'normal'
> retitle 841741 grub-probe fails to find GRUB drive, makes system unbootable
Bug #841741 [grub-common] grub-probe fails to find GRUB drive
Changed Bug title to 'grub-probe fails to find GRUB drive, makes system 
unbootable' from 'grub-probe fails to find GRUB drive'.
>
End of message, stopping processing here.

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

Bug#811996: Fixing the ptlib FTBFS will also fix the t38modem FTBFS

[Adrian Bunk]

reassign 811996 src:ptlib
reassign 837577 src:ptlib
forcemerge 811996 837577
affects 811996 src:t38modem
thanks

Strictly speaking the ptlib build failure is unrelated to the t38modem 
build failure, but a ptlib binNMU is not possible due to the ptlib
FTBFS, and any new ptlib upload will automatically be built with PIE.

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#811068: libgda5: Patch to disable the failing tests

[Santiago Vila]

Dear GNOME maintainers:

Based on the comments by Andreas in the rygel bug, I could understand
your desire to do the "right thing" and fix the failing tests, but it
surely would take time and effort, and nobody can really force you to do that.

If you decide to disable the tests, I'm attaching a patch to make it easy.
I've actually tested it (by diffing build logs), and it does what it
says it does.

Thanks a lot.
diff -Nru libgda5-5.2.4/debian/changelog libgda5-5.2.4/debian/changelog
--- libgda5-5.2.4/debian/changelog  2016-09-23 10:22:18.0 +0200
+++ libgda5-5.2.4/debian/changelog  2016-10-24 16:35:54.0 +0200
@@ -1,3 +1,10 @@
+libgda5 (5.2.4-3) unstable; urgency=medium
+
+  * Disable check_data_proxy and check_vcnc, as they fail randomly
+and make the package to FTBFS (Closes: #811068, #839444).
+
+ -- Andreas Henriksson   Mon, 24 Oct 2016 16:35:54 +0200
+
 libgda5 (5.2.4-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru libgda5-5.2.4/debian/patches/disable-randomly-failing-tests.patch 
libgda5-5.2.4/debian/patches/disable-randomly-failing-tests.patch
--- libgda5-5.2.4/debian/patches/disable-randomly-failing-tests.patch   
1970-01-01 01:00:00.0 +0100
+++ libgda5-5.2.4/debian/patches/disable-randomly-failing-tests.patch   
2016-10-24 16:34:01.0 +0200
@@ -0,0 +1,16 @@
+From: Santiago Vila 
+Subject: Disable check_data_proxy and check_vcnc, known to fail randomly, 
until we know why they fail
+Bug-Debian: https://bugs.debian.org/811068
+Bug-Debian: https://bugs.debian.org/839444
+
+--- libgda5-5.2.4.orig/tests/data-models/Makefile.am
 libgda5-5.2.4/tests/data-models/Makefile.am
+@@ -9,7 +9,7 @@ AM_CPPFLAGS = \
+ 
+ TESTS_ENVIRONMENT = GDA_TOP_SRC_DIR="$(abs_top_srcdir)" 
GDA_TOP_BUILD_DIR="$(abs_top_builddir)"
+ check_PROGRAMS = check_model_import check_virtual check_data_proxy 
check_model_copy check_pmodel check_empty_rs check_model_errors check_vcnc 
check_pivot
+-TESTS = check_model_import check_virtual check_data_proxy check_model_copy 
check_pmodel check_empty_rs check_model_errors check_vcnc check_pivot
++TESTS = check_model_import check_virtual check_model_copy check_pmodel 
check_empty_rs check_model_errors check_pivot
+ 
+ common_sources = \
+   ../test-errors.h \
diff -Nru libgda5-5.2.4/debian/patches/series 
libgda5-5.2.4/debian/patches/series
--- libgda5-5.2.4/debian/patches/series 2016-09-23 09:56:32.0 +0200
+++ libgda5-5.2.4/debian/patches/series 2016-10-24 16:32:41.0 +0200
@@ -1,2 +1,3 @@
 01-link-sqlite-provider-against-sqlite3.patch
 Accept-SQLITE_INDEX_CONSTRAINT_LIKE-from-sqlite.patch
+disable-randomly-failing-tests.patch

Bug#841883: linux-image-4.7.0-1-686: cannot boot with 4.7.8-1, stuck at loading initrd

[Francesco Poli]

On Mon, 24 Oct 2016 14:14:18 +0800 sharuzzaman wrote:

[...]
> with previous version of linux-image-4.7.0-1-686, I'm able to boot my laptop 
> with no issue.
> 
> yesterday, I update the kernel to version 4.7.8-1 from debian repository 
> using aptitude upgrade, then after reboot, the laptop is not able to boot up
> 
> the screeen just went blank and blinking cursor shown after loading initrd 
> ramdisk
> 
> I rebooted the laptop and select kernel 4.6, and the laptop boots up just fine
> 
> I have run update-initramfs for kernel 4.7, but still not able to boot after 
> that
> 
> I also have run aptitude reinstall for kernel 4.7, but still not able to boot 
> after that
> 
> I'm sure this is not a problem with my laptop, but something is wrong with 
> the kernel and/or initrd image

Hello,
I am another user bitten by the same bug on an i386 machine (but
everything seems to be fine on amd64 machines).
I experience the same exact misbehavior (version 4.7.8-1 fails to boot:
stuck while loading initrd); I have tried the same things to no avail.

I have currently altered GRUB_DEFAULT in /etc/default/grub, in order to
force the machine to automatically boot the previous kernel version
(4.6.4-1).

I hope the bug may be fixed soon.
Thanks to the Debian Kernel Team for any help they may provide.


-- 
 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


pgpnuff9ZAXEH.pgp
Description: PGP signature

Processed: Patch from Ubuntu for the sbcl PIE FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #837576 [src:sbcl] sbcl: FTBFS with bindnow and PIE enabled
Added tag(s) patch.

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

Bug#837576: Patch from Ubuntu for the sbcl PIE FTBFS

[Adrian Bunk]

Control: tags -1 +patch

The patch I found in Ubuntu for this bug is attached,

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

Author: Steve Beattie 
Subject: make -no-pie arguments consistent with upstream GCC
Bug: https://bugs.launchpad.net/ubuntu/+source/sbcl/+bug/1576871

SBCL fails to build when gcc is configure to
generate Position Independent Binaries. The runtime
configs for SBCL in sbcl/src/runtime/Config.x86-linux and
sbcl/src/runtime/Config.x86-64-linux attempt to take this into account
via detecting and adding the -nopie flag.

However, upstream gcc has standardized on the -no-pie flag (note
embedded hyphen):

  https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/doc/invoke.texi;h=515d948ce710a2fba98c586ea2efa05d4cf60979;hb=HEAD#l10620

as of upstream commit:

  https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=e9abca4f4a48fa8b1fd9778f6a3cd748e099e3bb

This causes SBCL to FTBFS in Ubuntu 16.10 on amd64 where -pie is
enabled by default in gcc.

Signed-off-by: Steve Beattie 
---
 src/runtime/Config.x86-64-linux |6 +++---
 src/runtime/Config.x86-linux|6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)

Index: b/src/runtime/Config.x86-64-linux
===
--- a/src/runtime/Config.x86-64-linux
+++ b/src/runtime/Config.x86-64-linux
@@ -47,10 +47,10 @@ CFLAGS += -fno-omit-frame-pointer
 GC_SRC = gencgc.c
 
 # Hardened GCC enables PIE by default
-ifneq ($(shell $(CC) -dumpspecs 2>/dev/null | grep -e nopie),)
+ifneq ($(shell $(CC) -dumpspecs 2>/dev/null | grep -e no-pie),)
 CFLAGS += -fno-pie
-LINKFLAGS += -nopie
-LDFLAGS += -nopie
+LINKFLAGS += -no-pie
+LDFLAGS += -no-pie
 endif
 
 # Nothing to do for after-grovel-headers.
Index: b/src/runtime/Config.x86-linux
===
--- a/src/runtime/Config.x86-linux
+++ b/src/runtime/Config.x86-linux
@@ -43,10 +43,10 @@ ifdef LISP_FEATURE_SB_CORE_COMPRESSION
 endif
 
 # Hardened GCC enables PIE by default
-ifneq ($(shell $(CC) -dumpspecs 2>/dev/null | grep -e nopie),)
+ifneq ($(shell $(CC) -dumpspecs 2>/dev/null | grep -e no-pie'),)
 CFLAGS += -fno-pie
-LINKFLAGS += -nopie
-LDFLAGS += -nopie
+LINKFLAGS += -no-pie
+LDFLAGS += -no-pie
 endif
 
 GC_SRC = gencgc.c

Processed: [bts-link] source package python-pyhsm

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package python-pyhsm
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #834066 (http://bugs.debian.org/834066)
> # Bug title: python-pyhsm: ships 
> /usr/lib/python2.7/dist-packages/test/__init__.py
> #  * https://github.com/Yubico/python-pyhsm/issues/11
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 834066 + fixed-upstream
Bug #834066 [python-pyhsm] python-pyhsm: ships 
/usr/lib/python2.7/dist-packages/test/__init__.py
Added tag(s) fixed-upstream.
> usertags 834066 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 834066 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: Only a binNMU should be required

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 psicode needs PIE binNMU
Bug #837569 [libpsi3-dev] libpsi3-dev Please build static libraries with -fPIC
Changed Bug title to 'psicode needs PIE binNMU' from 'libpsi3-dev Please build 
static libraries with -fPIC'.

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

Bug#841721: marked as done (lxqt-l10n: Debian changelog is incomplete)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2016 17:24:43 +
with message-id 
and subject line Bug#841721: fixed in lxqt-l10n 0.11.0-19-g717bd7e-5
has caused the Debian Bug report #841721,
regarding lxqt-l10n: Debian changelog is incomplete
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.)


-- 
841721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lxqt-l10n
Version: 0.11.0-19-g717bd7e-3
Severity: serious

https://tracker.debian.org/media/packages/l/lxqt-l10n/changelog-0.11.0-19-g717bd7e-3

There are versions missing that are part of the history of
this version.

Please do not ever remove items from the Debian changelog.

One effect of this bad practice is that version tracking thinks that
#824825 is still present in the version in unstable, which would
ensure that your package will not be part of stretch.

Please add the missing changelog items (at least 0.11.0-19-g717bd7e-1
and 0.11.0-19-g717bd7e-2) back to the Debian changelog.
--- End Message ---
--- Begin Message ---
Source: lxqt-l10n
Source-Version: 0.11.0-19-g717bd7e-5

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 24 Oct 2016 18:18:04 +0200
Source: lxqt-l10n
Binary: compton-conf-l10n libfm-qt-l10n liblxqt-l10n lximage-qt-l10n 
lxqt-about-l10n lxqt-admin-l10n lxqt-config-l10n lxqt-globalkeys-l10n 
lxqt-notificationd-l10n lxqt-openssh-askpass-l10n lxqt-panel-l10n 
lxqt-policykit-l10n lxqt-powermanagement-l10n lxqt-runner-l10n 
lxqt-session-l10n lxqt-sudo-l10n obconf-qt-l10n pavucontrol-qt-l10n 
pcmanfm-qt-l10n qterminal-l10n
Architecture: source
Version: 0.11.0-19-g717bd7e-5
Distribution: unstable
Urgency: medium
Maintainer: LXQt Packaging Team 
Changed-By: Alf Gaida 
Description:
 compton-conf-l10n - Language package for compton-conf
 libfm-qt-l10n - Language package for libfm-qt
 liblxqt-l10n - Language package for liblxqt
 lximage-qt-l10n - Language-package for lximage-qt
 lxqt-about-l10n - Language package for lxqt-about
 lxqt-admin-l10n - Language package for lxqt-admin
 lxqt-config-l10n - Language package for lxqt-config
 lxqt-globalkeys-l10n - Language package for lxqt-globalkeys
 lxqt-notificationd-l10n - Language package for lxqt-notificationd
 lxqt-openssh-askpass-l10n - Language package for lxqt-openssh-askpass
 lxqt-panel-l10n - Language package for lxqt-panel
 lxqt-policykit-l10n - Language package for lxqt-policykit
 lxqt-powermanagement-l10n - Language package for lxqt-powermanagement
 lxqt-runner-l10n - Language package for lxqt-runner
 lxqt-session-l10n - Language package for lxqt-session
 lxqt-sudo-l10n - Language package for lxqt-sudo
 obconf-qt-l10n - Language package for obconf-qt
 pavucontrol-qt-l10n - Language package for pavucontrol-qt
 pcmanfm-qt-l10n - Language package for pcmanfm-qt
 qterminal-l10n - Language package for qterminal
Closes: 841721
Changes:
 lxqt-l10n (0.11.0-19-g717bd7e-5) unstable; urgency=medium
 .
   * Really close 841721 ((Closes: #841721)
   * Follow the multiarch hinter and mark the l10n-packages foreign
Checksums-Sha1:
 6b89cafe815688fb68d171c87438b7bfa7986fe0 3153 
lxqt-l10n_0.11.0-19-g717bd7e-5.dsc
 9f9729265a40a7f9c932fb20d691ca3241759cca 6112 
lxqt-l10n_0.11.0-19-g717bd7e-5.debian.tar.xz
Checksums-Sha256:
 1d2b30f166cdef74a64eabd6d8a8cca8b4934bd3f3afe6c8cd2c241ce92d2052 3153 
lxqt-l10n_0.11.0-19-g717bd7e-5.dsc
 2d34343019fb96e5f42a7430055fbfb002c4991fb436f29e2a12ad359c193581 6112 
lxqt-l10n_0.11.0-19-g717bd7e-5.debian.tar.xz
Files:
 9771d47da62849b681f59ed82f731dc5 3153 utils optional 
lxqt-l10n_0.11.0-19-g717bd7e-5.dsc
 ee40ea3402ed1f9593e220de74e0fa55 6112 utils optional 
lxqt-l10n_0.11.0-19-g717bd7e-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

Processed: nmu: psicode_3.4.0-6

[Debian Bug Tracking System]

Processing control commands:

> block 837569 by -1
Bug #837569 [libpsi3-dev] libpsi3-dev Please build static libraries with -fPIC
837569 was not blocked by any bugs.
837569 was not blocking any bugs.
Added blocking bug(s) of 837569: 841942

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

Bug#837569: Only a binNMU should be required

[Adrian Bunk]

Control: retitle -1 psicode needs PIE binNMU

A binNMU should be sufficient to fix this, and is already requested.

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#837567: Only a binNMU should be required

[Adrian Bunk]

Control: retitle -1 mlton needs PIE binNMU

A binNMU should be sufficient to fix this, and already requested.

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: nmu: mlton_20100608-5.1

[Debian Bug Tracking System]

Processing control commands:

> block 837567 by -1
Bug #837567 [src:mlton] mlton: FTBFS with bindnow and PIE enabled
837567 was not blocked by any bugs.
837567 was not blocking any bugs.
Added blocking bug(s) of 837567: 841941

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

Processed: Only a binNMU should be required

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 mlton needs PIE binNMU
Bug #837567 [src:mlton] mlton: FTBFS with bindnow and PIE enabled
Changed Bug title to 'mlton needs PIE binNMU' from 'mlton: FTBFS with bindnow 
and PIE enabled'.

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

Processed: Reassign with correct syntax

[Debian Bug Tracking System]

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

> reassign 837456 src:ocamlgraph
Bug #837456 [src:frama-c] ocamlgraph needs PIE binNMU
Bug reassigned from package 'src:frama-c' to 'src:ocamlgraph'.
No longer marked as found in versions frama-c/20151002+magnesium+dfsg-1.
Ignoring request to alter fixed versions of bug #837456 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: Mark as forwarded

[Debian Bug Tracking System]

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

> forwarded 837480 https://github.com/constabulary/gb/issues/607
Bug #837480 [src:gb] gb: FTBFS with bindnow and PIE enabled
Set Bug forwarded-to-address to 'https://github.com/constabulary/gb/issues/607'.
> thanks
Stopping processing here.

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

Bug#837456: ocamlgraph needs PIE binNMU

[Adrian Bunk]

Control: rassagn -1 src:ocamlgraph
Control: affects -1 src:frama-c
Control: retitle -1 ocamlgraph needs PIE binNMU

A binNMU is sufficient to fix this, and already requested.

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 (with 1 error): ocamlgraph needs PIE binNMU

[Debian Bug Tracking System]

Processing control commands:

> rassagn -1 src:ocamlgraph
Unknown command or malformed arguments to command.

> affects -1 src:frama-c
Bug #837456 [src:frama-c] frama-c: FTBFS with bindnow and PIE enabled
Added indication that 837456 affects src:frama-c
> retitle -1 ocamlgraph needs PIE binNMU
Bug #837456 [src:frama-c] frama-c: FTBFS with bindnow and PIE enabled
Changed Bug title to 'ocamlgraph needs PIE binNMU' from 'frama-c: FTBFS with 
bindnow and PIE enabled'.

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

Processed: nmu: ocamlgraph_1.8.6-1

[Debian Bug Tracking System]

Processing control commands:

> block 837456 by -1
Bug #837456 [src:frama-c] frama-c: FTBFS with bindnow and PIE enabled
837456 was not blocked by any bugs.
837456 was not blocking any bugs.
Added blocking bug(s) of 837456: 841939

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

Processed: lucene-solr: Network tests are performed using public IP instead of 127.0.0.1

[Debian Bug Tracking System]

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

> retitle 840827 lucene-solr: Network tests are performed using public IP 
> instead of 127.0.0.1
Bug #840827 [src:lucene-solr] lucene-solr: FTBFS (failing tests, no route to 
host)
Changed Bug title to 'lucene-solr: Network tests are performed using public IP 
instead of 127.0.0.1' from 'lucene-solr: FTBFS (failing tests, no route to 
host)'.
> severity 840827 normal
Bug #840827 [src:lucene-solr] lucene-solr: Network tests are performed using 
public IP instead of 127.0.0.1
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#840827: lucene-solr: Network tests are performed using public IP instead of 127.0.0.1

[Santiago Vila]

retitle 840827 lucene-solr: Network tests are performed using public IP instead 
of 127.0.0.1
severity 840827 normal
thanks

On Mon, Oct 24, 2016 at 05:08:39PM +0200, Emmanuel Bourg wrote:

> I got a look at this issue and it seems the failing tests are setting up
> a local RMI server but the subsequent connections do not work.
> 
> I don't know why it fails with your machines but if I'm not mistaken
> local connections are allowed during the build.
> 
> Is the IP you redacted the one from the machine building the package, or
> another machine on your network?

Big ooops! Sorry. That was why it failed.

Not all my machines have a fixed IP, and I made the mistake of putting
the public IP of the day in /etc/hosts instead of 127.0.1.1.

I've triggered rebuilds on the machines where it previously failed and
now it does not fail, so there is no FTBFS bug anymore.



But I have still to "redact" the build logs in case the tests fail.

Would not be better to do the tests by connecting to localhost or
127.0.0.1 instead of the machine name?

I think this would even simplify the code, as you could use always
"localhost" instead of having to guess the real hostname first.


Thanks a lot.

Bug#837454: Patch from Ubuntu for the flint-arb PIE FTBFS

[Adrian Bunk]

Control: tags -1 +patch

The patch I found in Ubuntu for this bug is attached,

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

Description: invoke cc with just -r to fix FTBFS with PIE enabled
Author: Logan Rosen 
Forwarded: no
Last-Update: 2016-05-07 
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/Makefile.subdirs
+++ b/Makefile.subdirs
@@ -52,7 +52,7 @@
 	$(QUIET_CC) $(CC) $(CFLAGS) $(INCS) -c $< -o $@ -MMD -MP -MF "$(BUILD_DIR)/$(MOD_DIR)_$*.d" -MT "$(BUILD_DIR)/$(MOD_DIR)_$*.d" -MT "$@"
 
 $(MOD_LOBJ): $(LOBJS)
-	$(QUIET_CC) $(CC) $(ABI_FLAG) -Wl,-r $^ -o $@ -nostdlib
+	$(QUIET_CC) $(CC) $(ABI_FLAG) -r $^ -o $@ -nostdlib
 
 -include $(LOBJS:.lo=.d)
 

Processed: Patch from Ubuntu for the flint-arb PIE FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #837454 [src:flint-arb] flint-arb: FTBFS with bindnow and PIE enabled
Added tag(s) patch.

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

Processed: Re: Bug#841709: [uscan] missing package parameter at call of debian/repack.sh

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #841709 [devscripts] [uscan] missing package parameter at call of 
debian/repack.sh
Severity set to 'normal' from 'grave'

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

Bug#841709: [uscan] missing package parameter at call of debian/repack.sh

[Osamu Aoki]

control: severity -1 normal

Hi,

On Sat, Oct 22, 2016 at 04:19:29PM +0200, Jörg Frings-Fürst wrote:
> Package: devscripts
> Version: 2.16.8
> Severity: grave
^ Please read the policy.
> at download a new release with uscan the repack failed.
> 
> At the call of debian/repack.sh the parameter $3 is missing:

Ok.  Please show me your debian/watch file.

If you are using uscan with version=4 watch file, $3 should not be there.

Please describe exact way for me to reproduce your problem.

Osamu

Processed: Also block the binNMU requests

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 841921 837350
Bug #841938 [release.debian.org] nmu: ocaml_4.02.3-7
841938 was not blocked by any bugs.
841938 was blocking: 837359
Added blocking bug(s) of 841938: 837350 and 841921

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

Bug#837359: Only a binNMU is required

[Adrian Bunk]

Control: retitle -1 ocaml needs PIE binNMU
Control: tags -1 -patch

A binNMU is sufficient to fix this, and already requested.

Policy does not permit building static libraries with PIC unless
there is a special reason.

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: Only a binNMU is required

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 ocaml needs PIE binNMU
Bug #837359 [src:ocaml] ocaml: Please build libasmrun.a and libcamlrun.a with 
-fPIC
Changed Bug title to 'ocaml needs PIE binNMU' from 'ocaml: Please build 
libasmrun.a and libcamlrun.a with -fPIC'.
> tags -1 -patch
Bug #837359 [src:ocaml] ocaml needs PIE binNMU
Removed tag(s) patch.

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

Processed: nmu: ocaml_4.02.3-7

[Debian Bug Tracking System]

Processing control commands:

> block 837359 by -1
Bug #837359 [src:ocaml] ocaml: Please build libasmrun.a and libcamlrun.a with 
-fPIC
837359 was blocked by: 837350
837359 was not blocking any bugs.
Added blocking bug(s) of 837359: 841938

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

Bug#840847: (no subject)

[Barry Warsaw]

Any chance this fix can get uploaded soon-ish?  gtimelog build depends on it
so it's marked for autoremoval because of this bug.  Thanks!

Bug#840827: lucene-solr: FTBFS (failing tests, no route to host)

[Emmanuel Bourg]

Hi Santiago,

I got a look at this issue and it seems the failing tests are setting up
a local RMI server but the subsequent connections do not work.

I don't know why it fails with your machines but if I'm not mistaken
local connections are allowed during the build.

Is the IP you redacted the one from the machine building the package, or
another machine on your network?

Is it possible that the tests hit a TCP connection limit on the host?

Emmanuel Bourg

Processed: libctl binnmu blocks 837568

[Debian Bug Tracking System]

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

> block 837568 by 841929
Bug #837568 {Done: Thorsten Alteholz } [libctl-dev] 
libctl-dev: Please build libctlgeom.a with -fPIC
837568 was not blocked by any bugs.
837568 was not blocking any bugs.
Added blocking bug(s) of 837568: 841929
> thanks
Stopping processing here.

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

Processed: Only a binNMU is required

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 jack-audio-connection-kit needs PIE binNMU
Bug #837423 [src:jack-audio-connection-kit] jack-audio-connection-kit: Please 
build libjack.a with -fPIC
Changed Bug title to 'jack-audio-connection-kit needs PIE binNMU' from 
'jack-audio-connection-kit: Please build libjack.a with -fPIC'.
> tags -1 -patch
Bug #837423 [src:jack-audio-connection-kit] jack-audio-connection-kit needs PIE 
binNMU
Removed tag(s) patch.

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

Bug#837423: Only a binNMU is required

[Adrian Bunk]

Control: retitle -1 jack-audio-connection-kit needs PIE binNMU
Control: tags -1 -patch

A binNMU is sufficient to fix this, and already requested.

Building static libraries with PIC is not permitted by policy.

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: nmu: jack-audio-connection-kit_1:0.125.0-1+b1

[Debian Bug Tracking System]

Processing control commands:

> block 837423 by -1
Bug #837423 [src:jack-audio-connection-kit] jack-audio-connection-kit: Please 
build libjack.a with -fPIC
837423 was not blocked by any bugs.
837423 was not blocking any bugs.
Added blocking bug(s) of 837423: 841930

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

Processed: No patch required

[Debian Bug Tracking System]

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

> tags 837350 -patch
Bug #837350 [src:binutils] binutils needs PIE binNMU
Removed tag(s) patch.
> tags 837445 -patch
Bug #837445 [src:check] check needs PIE binNMU
Bug #841757 [src:check] check needs PIE binNMU
Removed tag(s) patch.
Removed tag(s) patch.
> thanks
Stopping processing here.

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

Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*

[Pietro Battiston]

Il giorno lun, 24/10/2016 alle 16.28 +0200, IOhannes m zmölnig
(Debian/GNU) ha scritto:
> 
> On 2016-10-24 13:48, Pietro Battiston wrote:
> > 
> > Il giorno lun, 24/10/2016 alle 12.06 +0200, Fabian Greffrath ha
> > scritto:
> > > 
> > > It's just a wild guess, but this
> > > 
> > > Pietro Battiston wrote:
> > > > 
> > > > 
> > > > Package: ardour
> > > > Version: 1:5.4.0~dfsg-1
> > > [...]
> > > > 
> > > > 
> > > > ii  ardour-data   1:4.2~dfsg-5
> > > 
> > > just doesn't seem corect to me!
> > > 
> > 
> > Oooohhh...
> > right.
> > This explains everything.
> > 
> > Package "ardour" should probably depend on the same exact version
> > of
> > package "ardour-data".
> 
> this is the fix i uploaded today with 1:5.4.0~dfsg-2

Yep, I replied before seeing it!

Thank you very much,

Pietro

Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*

[Debian/GNU]

On 2016-10-24 13:48, Pietro Battiston wrote:
> Il giorno lun, 24/10/2016 alle 12.06 +0200, Fabian Greffrath ha
> scritto:
>> It's just a wild guess, but this
>>
>> Pietro Battiston wrote:
>>>
>>> Package: ardour
>>> Version: 1:5.4.0~dfsg-1
>> [...]
>>>
>>> ii  ardour-data   1:4.2~dfsg-5
>>
>> just doesn't seem corect to me!
>>
> 
> Oooohhh...
> right.
> This explains everything.
> 
> Package "ardour" should probably depend on the same exact version of
> package "ardour-data".

this is the fix i uploaded today with 1:5.4.0~dfsg-2

fgasdr
IOhannes

Processed: Only a binNMU is required for binutils

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 binutils needs PIE binNMU
Bug #837350 [src:binutils] binutils: Please build libbfd.a with -fPIC
Changed Bug title to 'binutils needs PIE binNMU' from 'binutils: Please build 
libbfd.a with -fPIC'.

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

Bug#837445: Only a binNMU is required

[Adrian Bunk]

Control: retitle -1 check needs PIE binNMU

A binNMU is sufficient to fix this, and already requested.

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: Only a binNMU is required

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 check needs PIE binNMU
Bug #837445 [src:check] check: Please build libcheck.a with -fPIC
Bug #841757 [src:check] mpc: FTBFS: relocation R_X86_64_32S against `.rodata' 
can not be used when making a shared object; recompile with -fPIC
Changed Bug title to 'check needs PIE binNMU' from 'check: Please build 
libcheck.a with -fPIC'.
Changed Bug title to 'check needs PIE binNMU' from 'mpc: FTBFS: relocation 
R_X86_64_32S against `.rodata' can not be used when making a shared object; 
recompile with -fPIC'.

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

Bug#837823: fprintd: diff for NMU version 0.6.0-2.1

[gustavo panizzo (gfa)]

Previous patch has urgency=medium, this patch has
urgency=low.
I plan to upload this patch

Apologizes for the noise

-- 
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: https://keybase.io/gfa
diff -Nru fprintd-0.6.0/debian/changelog fprintd-0.6.0/debian/changelog
--- fprintd-0.6.0/debian/changelog	2016-06-09 03:32:03.0 +0800
+++ fprintd-0.6.0/debian/changelog	2016-10-24 20:40:42.0 +0800
@@ -1,3 +1,11 @@
+fprintd (0.6.0-2.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Add intltool to build-dep, preparing for the deprecation of gnome-common,
+Fixes FTBFS. (Closes: #837823).
+
+ -- gustavo panizzo   Mon, 24 Oct 2016 20:40:42 +0800
+
 fprintd (0.6.0-2) unstable; urgency=medium
 
   [ Santiago Vila ]
diff -Nru fprintd-0.6.0/debian/control fprintd-0.6.0/debian/control
--- fprintd-0.6.0/debian/control	2016-06-09 03:31:31.0 +0800
+++ fprintd-0.6.0/debian/control	2016-10-24 20:33:56.0 +0800
@@ -9,6 +9,7 @@
  libdbus-glib-1-dev,
  libpolkit-gobject-1-dev,
  gtk-doc-tools,
+ intltool,
  libpam0g-dev
 Standards-Version: 3.9.8
 Homepage: http://www.freedesktop.org/wiki/Software/fprint/fprintd


signature.asc
Description: PGP signature

Processed: nmu: check_0.10.0-3

[Debian Bug Tracking System]

Processing control commands:

> block 837445 by -1
Bug #837445 [src:check] check: Please build libcheck.a with -fPIC
Bug #841757 [src:check] mpc: FTBFS: relocation R_X86_64_32S against `.rodata' 
can not be used when making a shared object; recompile with -fPIC
837445 was not blocked by any bugs.
837445 was not blocking any bugs.
Added blocking bug(s) of 837445: 841927
841757 was not blocked by any bugs.
841757 was not blocking any bugs.
Added blocking bug(s) of 841757: 841927

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

Bug#837350: Only a binNMU is required for binutils

[Adrian Bunk]

Control: retitle -1 binutils needs PIE binNMU

A binNMU is sufficient to fix this, and already requested.

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: fprintd: diff for NMU version 0.6.0-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 837823 + patch
Bug #837823 [src:fprintd] fprintd: FTBFS due to undeclared build dependencies
Added tag(s) patch.
> tags 837823 + pending
Bug #837823 [src:fprintd] fprintd: FTBFS due to undeclared build dependencies
Added tag(s) pending.

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

Bug#837823: fprintd: diff for NMU version 0.6.0-2.1

[gustavo panizzo (gfa)]

Control: tags 837823 + patch
Control: tags 837823 + pending

Dear maintainer,

I've prepared an NMU for fprintd (versioned as 0.6.0-2.1)

I'm looking for and sponsor, then I'll upload it to DELAYED/5.

Please feel free to tell me if I should delay it longer.

After the package reach the archive I'll upload to the git repo

Regards.

-- 
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: https://keybase.io/gfa
diff -Nru fprintd-0.6.0/debian/changelog fprintd-0.6.0/debian/changelog
--- fprintd-0.6.0/debian/changelog	2016-06-09 03:32:03.0 +0800
+++ fprintd-0.6.0/debian/changelog	2016-10-24 20:40:42.0 +0800
@@ -1,3 +1,11 @@
+fprintd (0.6.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add intltool to build-dep, preparing for the deprecation of gnome-common,
+Fixes FTBFS. (Closes: #837823).
+
+ -- gustavo panizzo   Mon, 24 Oct 2016 20:40:42 +0800
+
 fprintd (0.6.0-2) unstable; urgency=medium
 
   [ Santiago Vila ]
diff -Nru fprintd-0.6.0/debian/control fprintd-0.6.0/debian/control
--- fprintd-0.6.0/debian/control	2016-06-09 03:31:31.0 +0800
+++ fprintd-0.6.0/debian/control	2016-10-24 20:33:56.0 +0800
@@ -9,6 +9,7 @@
  libdbus-glib-1-dev,
  libpolkit-gobject-1-dev,
  gtk-doc-tools,
+ intltool,
  libpam0g-dev
 Standards-Version: 3.9.8
 Homepage: http://www.freedesktop.org/wiki/Software/fprint/fprintd


signature.asc
Description: PGP signature

Processed: your mail

[Debian Bug Tracking System]

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

> tag 841691 + pending
Bug #841691 [sabnzbdplus] sabnzbdplus: uninstallable with libjs-jquery 3.1.1-1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#841098: not fixed in rygel 0.32.1-1

[Santiago Vila]

On Mon, Oct 24, 2016 at 01:45:24PM +0200, Andreas Henriksson wrote:

> If you're strongly attached to (cluttering up my maintainer view and)
> tracking every issue in the debian bug tracking system (I'd instead
> recommend you use the upstream bug tracker), then I'd welcome
> a bug report with severity minor. Minor is in my opinion the correct
> severity for such an issue.

I'm only attached to ensuring that Debian packages build ok and
without failures (release policy), so I have to decline your
suggestion to use the upstream bug tracker, as that will not make
the Debian package to build ok 100% of the time again.

If you think this is not RC, you can always ask for permission to use
sarge-ignore here (you could ask in the same report if it's ok for
them to disable the test).

IMO, disabling the test would be just a way to follow release policy,
which says "packages must build without failures".

If you plan to downgrade instead, please consider these two bugs as well:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839444
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811068

The three bugs are FTBFS which happen randomly. The package usually
builds fine in the official autobuilders (but not always), and the
FTBFS problem could be avoided trivially by disabling one or more
tests.

It would be really strange to downgrade one of those bugs and not the
others. Before doing so, please try to reach a consensus inside the
GNOME team about what should be done with all those bugs.

Thanks.

Processed: nmu: binutils_2.27-9

[Debian Bug Tracking System]

Processing control commands:

> block 837350 by -1
Bug #837350 [src:binutils] binutils: Please build libbfd.a with -fPIC
837350 was not blocked by any bugs.
837350 was blocking: 837359
Added blocking bug(s) of 837350: 841921

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

Processed (with 1 error): Re: Bug#841736: lilypond in Testing?

[Debian Bug Tracking System]

Processing control commands:

> forcemerge -1 746005
Bug #841736 [lilypond] lilypond in Testing?
Bug #746005 [lilypond] lilypond: please migrate to guile-2.0
Unset Bug forwarded-to-address
Severity set to 'normal' from 'serious'
Failed to forcibly merge 841736: Not altering archived bugs; see unarchive.


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

Bug#838112: marked as done (uctodata: fails to upgrade from 'jessie' - trying to overwrite /etc/ucto/es.abr)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2016 12:54:34 +
with message-id 
and subject line Bug#838112: fixed in uctodata 0.2-1
has caused the Debian Bug report #838112,
regarding uctodata: fails to upgrade from 'jessie' - trying to overwrite 
/etc/ucto/es.abr
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.)


-- 
838112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: uctodata
Version: 0.1.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package uctodata.
  Preparing to unpack .../uctodata_0.1.1-1_all.deb ...
  Unpacking uctodata (0.1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/uctodata_0.1.1-1_all.deb (--unpack):
   trying to overwrite '/etc/ucto/es.abr', which is also in package ucto 
0.5.3-3.1+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/uctodata_0.1.1-1_all.deb


cheers,

Andreas


ucto=0.5.3-3.1+b1_uctodata=0.1.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: uctodata
Source-Version: 0.2-1

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

Debian distribution maintenance software
pp.
Maarten van Gompel  (supplier of updated uctodata package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Oct 2016 14:25:00 +0200
Source: uctodata
Binary: uctodata
Architecture: source
Version: 0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Maarten van Gompel 
Description:
 uctodata   - Data files for Ucto
Closes: 838112
Changes:
 uctodata (0.2-1) unstable; urgency=medium
 .
   * New upstream
   * debian/control: cleanup, whitespace
   * debian/control: bumped compat level/debhelper to 10,
 fixed Vcs-git, pointed to wrong package
   * debian/control: Added replaces+breaks for older
 pre-split ucto versions (Closes: #838112),
 thanks to Andreas Beckmann
   * debian/control: added Multi-Arch: foreign
   * debian/copyright: ordering fixes, symlink fix
   * d/uctodata.lintian-overrides: obsolete, removed
(Thanks to Mattia Rizzolo for pointing out most of the above)
Checksums-Sha1:
 4adf1e36ca8986236e38d778a4c6dcc712fd358e 1988 uctodata_0.2-1.dsc
 85962f9be81741db8f2540224f07d2d6aa508ebf 88991 uctodata_0.2.orig.tar.gz
 664f51e781b9650884b6868c443792c03af72722 2172 uctodata_0.2-1.debian.tar.xz
Checksums-Sha256:
 79adbc024585322202dbb75aa153d3c422ffb8a478e8e08501856d71110d23c3 1988 
uctodata_0.2-1.dsc
 5ab98efefdee0f2afce0af4c96247c3f49b07ea4e5ee2930bb22d311b3a747a1 88991 
uctodata_0.2.orig.tar.gz
 e727d39e937db467e7cc5f8034dbb64f5e5ccf7910d5f194225dda328155d99e 2172 
uctodata_0.2-1.debian.tar.xz
Files:
 afedb70c5d3c6e827f3c59eefcd57351 1988 science extra uctodata_0.2-1.dsc
 0aad6fa5afe5b4d3255a2e9c7ddb14b1 88991 science extra uctodata_0.2.orig.tar.gz
 36eb04f122c6f3d619182f7e478fa493 2172 science extra 
uctodata_0.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYDf17AAoJEAgWueGMdiutgWgQAKgAxF4ZkyhzejDdQwRD5tOu
vy4Spupixy+0sg/pEpNK84I6ch0WjdPgys8Uz7uArgcRvJA7OS5ijncWSZuEyK0/
Tv+krh7AahZsz1gOHsDKV4uIg8Hhwo5mvOW5kPnD0HtctqyjqSCIYqDM2YGYAL/u
2Ybb32li2tDlK96svlDoT0ikhcI+w37RTb44C/96NPyXA5v+bTeatPJ04c35t/WM
8Oryi7aQc6ELz9sS+n19iTTUCx1wovd2jCF/JII4r4H8d2QaUynAf63fiWWMYQdA
lwG4BK5XrEW/9KD6XM5LZ3fZxugdp0w5OpY6AGMi0GqO8nLp+T7qXey4Ob58/0cN
Lds5vGpIwMGSdKPCsQ3DbMqOcbs5vzrL3yvtyWlgtGMI6I1P2iJGLm2Sh4u0AqNC

Bug#841511: python-bitbucket-api, python-bitbucket: error when trying to install together

[David Villa]

I think python-bitbucket can be removed. Its functionality is quite limited.

Regards

El vie., 21 oct. 2016 a las 18:28, ChangZhuo Chen ()
escribió:

> On Fri, Oct 21, 2016 at 11:42:03AM +0200, Andreas Beckmann wrote:
> > This is a serious bug as it makes installation fail, and violates
> > sections 7.6.1 and 10.1 of the policy. An optimal solution would
> > consist in only one of the packages installing that file, and renaming
> > or removing the file in the other package. Depending on the
> > circumstances you might also consider Replace relations or file
> > diversions. If the conflicting situation cannot be resolved then, as a
> > last resort, the two packages have to declare a mutual
> > Conflict. Please take into account that Replaces, Conflicts and
> > diversions should only be used when packages provide different
> > implementations for the same functionality.
>
> I has checked the code, and these two packages provide very different
> implementation of bitbucket API. So I think the solution is mutual
> Conflict.
>
> Another solution is removing python-bitbucket-api since I only need
> python3-bitbucket-api for git-repo (#840371), and it is Python3 only.
> Not sure if that is a good solution, but it can solve the problem too.
>
>
> --
> ChangZhuo Chen (陳昌倬) 
> Debian Developer (https://nm.debian.org/public/person/czchen)
> Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D
>   BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B
>

Bug#812532: files with the same name installed in / and /usr

[Mark Brown]

On Sun, Oct 23, 2016 at 02:06:29AM +0200, Marco d'Itri wrote:
> On Oct 23, Mark Brown  wrote:

> > I'd have expected to at least have seen something going round saying
> > that the transition was mostly complete and that there were only a few
> > packages blocking it prior to just dumping a new version of deboostrap
> > in unstable and rendering everything instabuggy.  Most similar

> I did this in *february* for the other packages, but not this one since 
> you had recently suggested that it was not ready anyway.

Telling other package maintainers doesn't help me know that this is a
transition that's actually happening, and one of the things that would
tell me that there might be some sense of urgency would be an indication
that the transition was actually happening.  I do remember you asking me
about my plans to fix it but there was no context that this was anything
more than a "hey, it'd be nice sometime".  For things like this even if
people aren't working on something now if there's a bigger picture it's
good to tell people about it, something like "OK, but please note that
we're actively working on this transition and expect it to be done for
stretch" would've really helped here in avoiding surprise with sudden RC
bugs out of nowhere.

> > I didn't ask for help because I just don't care about this transition,
> > in part because as I indicated there's no way to really use yp-tools at
> > present so it's the least of anyone's worries so when I'm spending time

> Maybe then the package should not be in testing anyway?

It's not impossible that someone could use it, it's just not as useful
as it could be.


signature.asc
Description: PGP signature

Processed: Re: alfa: build-depends on libcfitsio3-dev

[Debian Bug Tracking System]

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

> severity 841658 serious
Bug #841658 [alfa] alfa: build-depends on libcfitsio3-dev
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#840974: samtools: FTBFS: configure.ac:69: error: macro PKG_CHECK_EXISTS is not defined; is a m4 file missing?

[Sascha Steinbiss]

Hi.

[...]
>> Thanks. This has fixed the problem for me. Is this solution OK for
everyone?
>
> Fine for me

OK, I'll upload later.

Cheers
Sascha

Processed: Re: xnetcardconfig: does not work with ruby-gnome2 3.0.9-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - experimental
Bug #840698 [xnetcardconfig] xnetcardconfig: does not work with ruby-gnome2 
3.0.9-1
Ignoring request to alter tags of bug #840698 to the same tags previously set

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

Bug#840698: xnetcardconfig: does not work with ruby-gnome2 3.0.9-1

[dai]

Control: tags -1 - experimental

I uploaded ruby-gnome2 3.0.9-2 to unstable.
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature

Processed: Re: Bug#841906: neutron: FTBFS randomly (failing tests)

[Debian Bug Tracking System]

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

> retitle 841906 neutron: FTBFS randomly (failing tests)
Bug #841906 [src:neutron] neutron: FTBFS (failing tests)
Changed Bug title to 'neutron: FTBFS randomly (failing tests)' from 'neutron: 
FTBFS (failing tests)'.
>
End of message, stopping processing here.

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

Bug#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*

[Pietro Battiston]

Il giorno lun, 24/10/2016 alle 12.06 +0200, Fabian Greffrath ha
scritto:
> It's just a wild guess, but this
> 
> Pietro Battiston wrote:
> > 
> > Package: ardour
> > Version: 1:5.4.0~dfsg-1
> [...]
> > 
> > ii  ardour-data   1:4.2~dfsg-5
> 
> just doesn't seem corect to me!
> 

Oooohhh...
right.
This explains everything.

Package "ardour" should probably depend on the same exact version of
package "ardour-data".

Pietro

Bug#841098: not fixed in rygel 0.32.1-1

[Andreas Henriksson]

Hello Santiago Vila.

Thanks for the backtrace, it's helpful.

On Fri, Oct 21, 2016 at 01:16:20PM +0200, Santiago Vila wrote:
> The package FTBFS (sometimes) because rygel-media-engine-test segfaults.
> 
> Here is a backtrace:
> 
> (gdb) bt
> #0  0x7f1a1a4b3fdf in raise () from /lib/x86_64-linux-gnu/libc.so.6
> #1  0x7f1a1a4b540a in abort () from /lib/x86_64-linux-gnu/libc.so.6
> #2  0x7f1a1af8a4f5 in g_assertion_message () from 
> /lib/x86_64-linux-gnu/libglib-2.0.so.0

This is not a segfault though, but an assertion failure.

> #3  0x7f1a1af8a58a in g_assertion_message_expr () from 
> /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #4  0x55597c5578bd in __lambda19_ (_data3_=) at 
> rygel-media-engine-test.c:2035
[...]

^^^ hint on where the failing assertion can be found.

(Please note that the source is vala so you'll need to translate this to
the applicable lambda in the vala source.)

> #5  ___lambda19__gsource_func (self=0x7f19f4001410) at 
> rygel-media-engine-test.c:2047
> #6  0x7f1a1af6368a in g_main_context_dispatch () from 
> /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #7  0x7f1a1af63a40 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #8  0x7f1a1af63d62 in g_main_loop_run () from 
> /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #9  0x55597c559688 in rygel_data_source_test_test_stop_start 
> (error=0x7ffe67fae238, self=0x55597df7e4e0)
> at rygel-media-engine-test.c:2116
> #10 rygel_data_source_test_run (self=0x55597df7e4e0) at 
> rygel-media-engine-test.c:2717
> #11 0x55597c55a310 in rygel_data_source_test_main (args=, 
> args_length1=)
> at rygel-media-engine-test.c:2996
> #12 0x7f1a1a4a12b1 in __libc_start_main () from 
> /lib/x86_64-linux-gnu/libc.so.6
> #13 0x55597c556f4a in _start ()
> 
> It could be, of course, that my autobuilder is misconfigured, but the
> same segfault happened several times in buildd.debian.org in the past.

You're more than welcome to dive deep into this issue. Patches are
always welcome.

Claiming this is RC is a bit over the top though. If you're only out
to ride the policy train without actually wanting to debug it yourself
then I'll be forced to simply disable the testsuite. In my opinion
the testsuite exists to raise the quality of what we produce and
to *save* us time. If it becomes to time-consuming to maintain I'll
do without it. Disabling failing tests-suites is something I know
from personal experience that several release team members have
a strong opinion against. Disabling it for a extremely rare occational
failure is something I imagine they would be even more opposed to.

If you're strongly attached to (cluttering up my maintainer view and)
tracking every issue in the debian bug tracking system (I'd instead
recommend you use the upstream bug tracker), then I'd welcome
a bug report with severity minor. Minor is in my opinion the correct
severity for such an issue.

Regards,
Andreas Henriksson