Bug#841128: marked as done (aws-shell: FTBFS (ImportError: No module named 'setuptools'))

[Debian Bug Tracking System]

Your message dated Tue, 18 Oct 2016 04:27:17 +
with message-id 
and subject line Bug#841128: fixed in aws-shell 0.1.1-2
has caused the Debian Bug report #841128,
regarding aws-shell: FTBFS (ImportError: No module named 'setuptools')
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.)


-- 
841128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:aws-shell
Version: 0.1.1-1
Severity: serious

Dear maintainer:

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


[...]
dpkg-buildpackage: info: source package aws-shell
dpkg-buildpackage: info: source version 0.1.1-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by TANIGUCHI Takaki 
 dpkg-source --before-build aws-shell-0.1.1
 fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
   dh_testdir -O--buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:184: python3.5 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 5, in 
from setuptools import setup, find_packages
ImportError: No module named 'setuptools'
E: pybuild pybuild:276: clean: plugin distutils failed with: exit code=1: 
python3.5 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p 3.5 returned exit code 13
debian/rules:7: recipe for target 'clean' failed
make: *** [clean] Error 25
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2


[ Now that the package is in the archive, please consider uploading
  this package in source-only form. That should help avoid failures
  like this one ].

Thanks.
--- End Message ---
--- Begin Message ---
Source: aws-shell
Source-Version: 0.1.1-2

We believe that the bug you reported is fixed in the latest version of
aws-shell, 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.
TANIGUCHI Takaki  (supplier of updated aws-shell 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, 18 Oct 2016 11:30:27 +0900
Source: aws-shell
Binary: aws-shell
Architecture: source all
Version: 0.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: TANIGUCHI Takaki 
Changed-By: TANIGUCHI Takaki 
Description:
 aws-shell  - Interactive productivity booster for the AWS CLI
Closes: 841128
Changes:
 aws-shell (0.1.1-2) unstable; urgency=medium
 .
   * debian/control: Add python3-setuptoolt to B-D. (Closes: #841128)
Checksums-Sha1:
 ced602bec2c97b49b2cc8a34d644f15dd3d86d43 2136 aws-shell_0.1.1-2.dsc
 55764fce705f58a6e6136d1ecb87763863b59217 1900 aws-shell_0.1.1-2.debian.tar.xz
 f44c15788dba1e39aab0c114265911e08ebc5793 33724 aws-shell_0.1.1-2_all.deb
Checksums-Sha256:
 adb1c2f5bf6dcff786364ebca12bed50664c88c4a528495ceec3637d50e598b5 2136 
aws-shell_0.1.1-2.dsc
 96894c457f0725e1c412e709bdf326d1444f5aeb15150c70a2d7fb9ba83baad5 1900 
aws-shell_0.1.1-2.debian.tar.xz
 d7e0fb384e4dfb0eedfb4db30e645e3d821ede10bb4cb2f00b8714e0530976d8 33724 
aws-shell_0.1.1-2_all.deb
Files:
 e6fd6caa810cd79f49824780bb83278c 2136 admin optional aws-shell_0.1.1-2.dsc
 ee47db4bb08399e7e9b71525569b2922 1900 admin optional 
aws-shell_0.1.1-2.debian.tar.xz
 31375f6b49187db2fb09c163d7780724 33724 admin optional aws-shell_0.1.1-2_all.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYBYl+AAoJEMwUn2wopeJXvsYP/j1J6/hzuduBIRbZG4eWNXEX
YljsvNHPJwT/0ix5jqhyDs+OsrseechJKSUB7WHGsUACnP9IY6v+KAAPtnvH2Rg1
0RDN0oZ1d88Ng2Y7DqEAvl9wqFgLaXnNsxk7jKkNzSMcx1Mf77IrOo3Ep/0J5Y98
dfzxP5ODBlUNiDhKbfwXx0NZcGeg84w61BJEuN/y2ZogW0QSvlbJmln9lAEXOSNv
D4aZ99VoZR7JQYa/jpbtKv0++QsY7/4Tt4SQjBttA83msXscLCjh+dXztc1REQqr
L6gTnLX1Nb3tugMKyoZ8DhAF2SLLt7P+v6F/4ewQ8Prot+JKHTZtMpnxLAKA2as2

Bug#840711: marked as done (golang-github-appc-docker2aci: CVE-2016-8579)

[Debian Bug Tracking System]

Your message dated Tue, 18 Oct 2016 02:26:27 +
with message-id 
and subject line Bug#838300: fixed in golang-github-appc-docker2aci 
0.12.3+dfsg-2
has caused the Debian Bug report #840711,
regarding golang-github-appc-docker2aci: CVE-2016-8579
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.)


-- 
840711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-appc-docker2aci
Version: 0.12.0+dfsg-1
Severity: grave
Tags: security upstream patch
Forwarded: https://github.com/appc/docker2aci/issues/203

Hi,

the following vulnerability was published for golang-github-appc-docker2aci.

CVE-2016-8579[0]:
infinite loop in deps walking

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-8579
[1] https://github.com/appc/docker2aci/issues/203
[2] 
https://github.com/lucab/docker2aci/commit/54331ec7020e102935c31096f336d31f6400064f

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: golang-github-appc-docker2aci
Source-Version:  0.12.3+dfsg-2

Marking as closed by hand, because I screwed up the changelog.  )-:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 18 Oct 2016 09:09:26 +1100
Source: golang-github-appc-docker2aci
Binary: golang-github-appc-docker2aci-dev docker2aci
Architecture: source amd64 all
Version: 0.12.3+dfsg-2
Distribution: unstable
Urgency: high
Maintainer: Debian Go Packaging Team 

Changed-By: Tim Potter 
Description:
 docker2aci - CLI tool to convert Docker images to ACIs
 golang-github-appc-docker2aci-dev - library to convert Docker images to ACIs
Changes:
 golang-github-appc-docker2aci (0.12.3+dfsg-2) unstable; urgency=high
 .
   * Fix infinite loop in deps walking, CVE-2016-8579. (Closes #840711).
Checksums-Sha1:
 fe6ea2fbb74122b8d811762ef6b298c56c73f8a4 2523 
golang-github-appc-docker2aci_0.12.3+dfsg-2.dsc
 3e92f8fc24e69613168cf98fa2a31b2e6f02db15 35656 
golang-github-appc-docker2aci_0.12.3+dfsg.orig.tar.xz
 f75010ac56a5f05dad140a71bf776ff413965746 3240 
golang-github-appc-docker2aci_0.12.3+dfsg-2.debian.tar.xz
 d2466ea5eb2615a80c9bb1e4e0866be8c63e18f5 1398420 
docker2aci_0.12.3+dfsg-2_amd64.deb
 c8b5195a5a5957cfce72e0337fc9019c5a112b01 28712 
golang-github-appc-docker2aci-dev_0.12.3+dfsg-2_all.deb
Checksums-Sha256:
 b3c4b9ee86a8f937301953844e881e2830cd51d30e3850e02f2155b694c3146b 2523 
golang-github-appc-docker2aci_0.12.3+dfsg-2.dsc
 49d9869d25a9bab4187ca070e77a23a8d20d39b92cdb24b8b4b45df0e1549aa5 35656 
golang-github-appc-docker2aci_0.12.3+dfsg.orig.tar.xz
 8168069f7267b546513db34af625dd5f17c743d704c92233057c7842132445fa 3240 
golang-github-appc-docker2aci_0.12.3+dfsg-2.debian.tar.xz
 9513b2116f16f277a1a66fb45c54ef7f0f3cca793070c30e733cacb348ee0e8c 1398420 
docker2aci_0.12.3+dfsg-2_amd64.deb
 f6a82e6e4e24b242e534aabb2bc3dd44ce1317fae02fc963830609d0478906f8 28712 
golang-github-appc-docker2aci-dev_0.12.3+dfsg-2_all.deb
Files:
 c0ce393b80ea8a8c4b532afdf32a8335 2523 devel extra 
golang-github-appc-docker2aci_0.12.3+dfsg-2.dsc
 e9b4bf8b201f78017e70c52a9e693b79 35656 devel extra 
golang-github-appc-docker2aci_0.12.3+dfsg.orig.tar.xz
 507c63c047d98ed8af76cbeca74b71c3 3240 devel extra 
golang-github-appc-docker2aci_0.12.3+dfsg-2.debian.tar.xz
 5b2ee5d96f74e36ba77ccffab2f59fc9 1398420 devel extra 
docker2aci_0.12.3+dfsg-2_amd64.deb
 f4973b710d4f5d3cf86739d41db6ab63 28712 devel extra 
golang-github-appc-docker2aci-dev_0.12.3+dfsg-2_all.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYBU/WAAoJELJMpj9uu+hNOA4QAMS++qIX1f1NgUdcZulFLs/i
K/WiluRhQcVGMMqA9+NRHa21MC67q97+Aovy7DsJbjCo/40jWwfLISmedzNW5rOc
10ox9KAYkt3/h/SlZNjHsPw7wHPmyWiy4NQEjXD/+gYZg15zQG2gcG3AeVUnZSyK
vSpJQktOAu4Ukj2/KwrG87jZ6SQN8erusP+zxN1oGfDGIGG1HPS8eII5B882jVkT
cdU/qOOFFtTR6mMFuPUcHsvPQcQFUD34bWqLFHBRvu0TrUaYuYH0mptBkM6udYGg
HCHfaxumwPSFv5fQkQ95b85H3P1SNSMmPIDPYQLQ70tuAhkVXvx9atfjgpenzBmF
Ge7yRCHbRSNsdXqhydzISugs5Xj5SO8sBF/y7E7Uy04u+SWliLt2M0fyrYMk05rP
oAdD/ctmblfk63jb9LXPRCslVEKZQeZWUCaJKl5dOUe9VmSGgmbvnEufMa3djHbG
O2hzZQnhhv2B08AIPCeLS1BNx+u+LcnwqiWewOUxsnQC/1LT2hjxyP26tkqlb+Y/
re7HrhNi9BP+jcG8g2RmBhur4wG+F5KJ5mNEwxTaVA2N/ygurYoWyXMeeYsfBrZ1
IY4KSDQ+ZlY9YD2XWqH0Edb0P+XFTMIHiDkofyb+Y2VfrbO1sP9vboxukNQTmEBn
0GZ+8uiwjccEJXwzVQgV
=EpjT
-END PGP SIGNATURE-



signature.asc
Description: Message signed with OpenPGP using GPGMail
--- 

Processed: Re: axi-cache: xapian.FeatureUnavailableError: Flint backend no longer supported

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #839982 [apt-xapian-index] axi-cache: xapian.FeatureUnavailableError: Flint 
backend no longer supported
Severity set to 'important' from 'serious'

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

Bug#839982: axi-cache: xapian.FeatureUnavailableError: Flint backend no longer supported

[Paul Wise]

Control: severity -1 important

On Fri, 2016-10-07 at 11:15 +0800, Paul Wise wrote:

> axi-cache search no longer works because of the recent python-xapian upgrade:

This is easily worked around by just running an update as root:

$ sudo update-apt-xapian-index
Reading ...
...
Rebuilding Xapian index: done.
$ axi-cache search apt xapian index
6 results found.
Results 1-6:
100% apt-xapian-index - maintenance and search tools for a Xapian index of 
Debian packages
90% libept1.5.0 - High-level library for managing Debian package information
90% libept-dev - High-level library for managing Debian package information
81% debtags - Debian Package Tags support tools
72% muon - package manager for KDE
60% apprecommender - Application recommender for Debian (and derivatives)
Did you mean: api xapian index ?
More terms: debtags packages debian popcon information sources queried
More tags: suite::debian use::searching works-with::software:package 
implemented-in::c++ devel::debian admin::package-management 
interface::commandline

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#841079: marked as pending

[W . Martin Borgert]

tag 841079 pending
thanks

Hello,

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


http://git.debian.org/?p=python-modules/packages/python-pyftpdlib.git;a=commitdiff;h=012b0b5

---
commit 012b0b577eaa2cc60f50ada0d119949578430169
Author: W. Martin Borgert 
Date:   Tue Oct 18 00:56:45 2016 +

prepare 1.5.1-2

diff --git a/debian/changelog b/debian/changelog
index bd8b669..d694fda 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,9 @@
-python-pyftpdlib (1.5.1-2) UNRELEASED; urgency=medium
+python-pyftpdlib (1.5.1-2) unstable; urgency=medium
 
-  [ W. Martin Borgert 2016-10-18 ]
-  * Build-Depend on python-openssl/python3-openssl.
+  * Build-Depend on python{,3}-openssl/python3-openssl and python{,3}-mock.
+  * Run tests from source dir. (Closes: #841079) hopefully
 
- -- W. Martin Borgert   Tue, 18 Oct 2016 00:09:44 +
+ -- W. Martin Borgert   Tue, 18 Oct 2016 00:55:20 +
 
 python-pyftpdlib (1.5.1-1) unstable; urgency=medium
 

Processed: Bug#841079 marked as pending

[Debian Bug Tracking System]

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

> tag 841079 pending
Bug #841079 [src:python-pyftpdlib] python-pyftpdlib: FTBFS (make install fails)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#841144: base: kernel BUG at linux-4.7.5/fs/ocfs2/alloc.c:1514!

[root]

Package: base
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

Two-host virtualization cluster with DRBD mirrored volume and OCFS2 filesystem.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Simply writing data to the volume exposed a kernel bug in OCFS2.

   * What was the outcome of this action?

Oct 17 09:57:38 vhost002 kernel: [ cut here ]
Oct 17 09:57:38 vhost002 kernel: kernel BUG at 
/build/linux-rAvIHq/linux-4.7.5/fs/ocfs2/alloc.c:1514!
Oct 17 09:57:38 vhost002 kernel: invalid opcode:  [#1] SMP
Oct 17 09:57:38 vhost002 kernel: Modules linked in: vhost_net vhost macvtap 
macvlan tun ocfs2 quota_tree cfg80211 rfkill iptable_filter ip_tables x_tables 
nfsd auth_rpcgss nfs_acl nfs lockd grace fscache ocfs2_dlmfs ocfs2_stack_o2cb 
sunrpc ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs bridge stp llc 
bonding ipmi_watchdog intel_rapl sb_edac edac_core x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel hmac drbg ansi_cprng igb iTCO_wdt ast iTCO_vendor_support 
mxm_wmi ttm evdev drm_kms_helper aesni_intel drm aes_x86_64 lrw xhci_pci 
gf128mul glue_helper xhci_hcd ablk_helper cryptd ehci_pci dca ehci_hcd e1000e 
i2c_algo_bit pcspkr usbcore ptp mei_me lpc_ich i2c_i801 sg mei shpchp mfd_core 
usb_common pps_core fjes wmi ipmi_si ipmi_poweroff ipmi_devintf
Oct 17 09:57:38 vhost002 kernel:  ipmi_msghandler tpm_tis tpm acpi_power_meter 
acpi_pad button fuse drbd lru_cache libcrc32c crc32c_generic autofs4 ext4 crc16 
jbd2 mbcache dm_mod md_mod sd_mod ahci libahci libata crc32c_intel scsi_mod
Oct 17 09:57:38 vhost002 kernel: CPU: 7 PID: 17663 Comm: qemu-system-x86 Not 
tainted 4.7.0-0.bpo.1-amd64 #1 Debian 4.7.5-1~bpo8+2
Oct 17 09:57:38 vhost002 kernel: Hardware name: To Be Filled By O.E.M. To Be 
Filled By O.E.M./EPC612D4I, BIOS P2.10 03/31/2016
Oct 17 09:57:38 vhost002 kernel: task: 8802547d9040 ti: 88025764 
task.ti: 88025764
Oct 17 09:57:38 vhost002 kernel: RIP: 0010:[]  
[] ocfs2_grow_tree+0x6f1/0x770 [ocfs2]
Oct 17 09:57:38 vhost002 kernel: RSP: 0018:880257643618  EFLAGS: 00010246
Oct 17 09:57:38 vhost002 kernel: RAX:  RBX: 000d 
RCX: 880257643790
Oct 17 09:57:38 vhost002 kernel: RDX: 8802576436bc RSI: 880257643968 
RDI: 8801803473f0
Oct 17 09:57:38 vhost002 kernel: RBP: 880257643678 R08:  
R09: 00390ce8
Oct 17 09:57:38 vhost002 kernel: R10: 02a15008 R11: 880257d9a030 
R12: 0001
Oct 17 09:57:38 vhost002 kernel: R13: 880257643828 R14: 8802622020c0 
R15: 0002
Oct 17 09:57:38 vhost002 kernel: FS:  7f718f75d700() 
GS:88103f3c() knlGS:
Oct 17 09:57:38 vhost002 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Oct 17 09:57:38 vhost002 kernel: CR2: 7f7ba6591e4c CR3: 0002825db000 
CR4: 001426e0
Oct 17 09:57:38 vhost002 kernel: Stack:
Oct 17 09:57:38 vhost002 kernel:  880257643728 880257643728 
c0a612a5 88025da1a880
Oct 17 09:57:38 vhost002 kernel:  8801803fd340 b2c2fd37 
8a1a0f55 000d
Oct 17 09:57:38 vhost002 kernel:  0001 880257643828 
880257643968 88025da1a880
Oct 17 09:57:38 vhost002 kernel: Call Trace:
Oct 17 09:57:38 vhost002 kernel:  [] ? 
ocfs2_set_buffer_uptodate+0x35/0x4a0 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [] ? 
__find_get_block+0xa7/0x110
Oct 17 09:57:38 vhost002 kernel:  [] ? 
ocfs2_split_and_insert+0x307/0x490 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [] ? 
ocfs2_split_extent+0x3ed/0x560 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [] ? 
ocfs2_change_extent_flag+0x273/0x450 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [] ? 
ocfs2_mark_extent_written+0x110/0x1d0 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [] ? 
ocfs2_dio_end_io_write+0x44d/0x600 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [] ? 
ocfs2_allocate_extend_trans+0x180/0x180 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [] ? 
ocfs2_dio_end_io+0x3b/0x60 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [] ? dio_complete+0x64/0x160
Oct 17 09:57:38 vhost002 kernel:  [] ? 
do_blockdev_direct_IO+0x1f5a/0x2350
Oct 17 09:57:38 vhost002 kernel:  [] ? 
ocfs2_write_end_nolock+0x560/0x560 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [] ? 
ocfs2_direct_IO+0x84/0x90 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [] ? 
generic_file_direct_write+0xb3/0x180
Oct 17 09:57:38 vhost002 kernel:  [] ? 
__generic_file_write_iter+0xb6/0x1e0
Oct 17 09:57:38 vhost002 kernel:  [] ? 
ocfs2_file_write_iter+0x44d/0xae0 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [] ? hrtimer_init+0xf0/0xf0
Oct 17 09:57:38 vhost002 kernel:  [] ? 
do_iter_readv_writev+0xb0/0x130
Oct 17 09:57:38 vhost002 kernel:  [] ? 
do_readv_writev+0x1a2/0x240
Oct 17 09:57:38 vhost002 kernel:  [] ? 
ocfs2_check_range_for_refcount+0x130/0x130 [ocfs2]
Oct 17 

Bug#800291: jade: Please migrate a supported debhelper compat level

[Neil Roeth]

Thanks, Tobias.

I have finished filing bugs against all packages with reverse
dependencies on jade and sp.  All are blockers on the tracking bugs.  I
will follow up and/or NMU as necessary.

On 10/16/2016 05:26 AM, Tobias Frost wrote:
> Hi Neil,
>
> sorry for the late reply... Been busy recenently.
>
> Am Sonntag, den 25.09.2016, 12:32 -0400 schrieb Neil Roeth:
>> Hi, Tobi,
>>
>> The removal of jade, sp and openjade1.3 is coming
>> along.   Openjade1.3
>> is done, it was actually removed from testing but there were no more
>> dependencies on it.  I was focusing recently on the sp binary
>> package,
>> and most of those dependencies have been switched to opensp.  Jade is
>> next.
>>
>> There are tracking bugs already, 811310 and 811312.
> ok
>
>> Aboot and iputils have bugs with patches open to change sp to opensp.
>>
>> Can you explain the output below?  I guess "dak rm jade" means remove
>> jade, while the -n means not to actually do it (no act).  What does
>> -R
>> mean?  Does the command apply to the jade source package or the
>> binary
>> package?  I'm guessing source since sp appears in the list and it is
>> a
>> binary package built from the jade source package.
> The command checks what would happen if you remove jade from the
> archives, a convenient way to check reverse dependencies you have on
> jade.
>
>> Thanks.
>>
>> On 09/25/2016 07:04 AM, Tobias Frost wrote:
>>> Hi Neil,
>>>
>>> how is the removal going?
>>> I was wondering if there should be a dedicated bug to track the
>>> status
>>> of the progess? What do you think? 
>>>
>>>
>>> A "dak rm -Rn jade" yields to:
>>>
>>>
>>> # Broken Depends:
>>> xmldiff: xmldiff-xmlrev
>>>
>>> # Broken Build-Depends:
>>> aboot: sp
>>> alex: jade
>>> datapacker: jade
>>> dejagnu: jade
>>> gnome-packagekit: sp
>>> gstreamer1.0: jade (>= 1.2.1)
>>> iputils: sp
>>> kannel: jade
>>> libetpan: jade
>>> lprng-doc: jade
>>> mozart: sp
>>> pyepl: jade
>>> scons-doc: jade
>>>
>>>
>>> --
>>> tobi 
>>>
>>> On Thu, 29 Oct 2015 21:00:50 -0400 Neil Roeth 
>>> wrote:
 I intend to remove this package from Debian rather than update
>>> it.  The
 Debian packages openjade/opensp can be used instead. I will file
 bugs
 against any packages that depend on jade and give them some time
 to
>>> be
 updated before I file the actual removal bug for jade.
  
 -- 
 Neil Roeth
  
  
  
>>
>>
>>


-- 
Neil Roeth

Bug#839767: ncmpcpp fails to start due to undefined symbol in binary

[Matteo Cypriani]

Control: severity -1 important
Control: tag -1 + upstream
Control: forwarded -1 https://github.com/taglib/taglib/issues/757

Le mercredi 12 octobre 2016, 14:33:36 EDT Christoph Egger a écrit :
> Control: reopen -1
> Control: reassign -1 libtag1v5
> Control: found -1 1.11+dfsg.1-0.1
> 
> Christoph Egger  writes:
> > Which is exactly what happened in unstable ~1 day ago as part of the
> > transition. So this seems to be a totally normal unstable disturbance
> > and not a bug.
> 
> Actually missing symbol seems to indicate libtag missed a soname bump?
> (And the problem was hidden by an unrelated binnmu later).

Indeed, WCharByteOrder was removed between taglib 1.9 and 1.11, as well as 
several other symbols, but the so version was changed only from 1.14.0 to 
1.16.0. I reported the problem upstream, but this is not an easy matter, as we 
can't just decide to bump the soname in Debian without a green light from 
upstream.

Matteo

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

Processed: Re: Bug#839767: ncmpcpp fails to start due to undefined symbol in binary

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #839767 [libtag1v5] ncmpcpp fails to start due to undefined symbol in binary
Severity set to 'important' from 'grave'
> tag -1 + upstream
Bug #839767 [libtag1v5] ncmpcpp fails to start due to undefined symbol in binary
Added tag(s) upstream.
> forwarded -1 https://github.com/taglib/taglib/issues/757
Bug #839767 [libtag1v5] ncmpcpp fails to start due to undefined symbol in binary
Set Bug forwarded-to-address to 'https://github.com/taglib/taglib/issues/757'.

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

Bug#841124: FTBFS on amd64

[Kurt Roeckx]

On Mon, Oct 17, 2016 at 11:20:07PM +0100, James Clarke wrote:
> This was fixed upstream by [1]. I intend to perform another NMU to fix
> this; please let me know if you disagree.

Go ahead. There is no need to upload this via delayed, I was
suprised your previous upload was.


Kurt

Bug#817493: marked as done (hebcal: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2016 22:36:26 +
with message-id 
and subject line Bug#817493: fixed in hebcal 3.5-2.1
has caused the Debian Bug report #817493,
regarding hebcal: Removal of debhelper compat 4
to be marked as done.

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

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


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

Hi,

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

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

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

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: hebcal
Source-Version: 3.5-2.1

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

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

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

Debian distribution maintenance software
pp.
Paulo Henrique de Lima Santana (phls)  (supplier of 
updated hebcal package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 07 Oct 2016 16:01:47 -0300
Source: hebcal
Binary: hebcal
Architecture: source
Version: 3.5-2.1
Distribution: unstable
Urgency: medium
Maintainer: Shaya Potter 
Changed-By: Paulo Henrique de Lima Santana (phls) 
Description:
 hebcal - A Perpetual Jewish Calendar
Closes: 817493
Changes:
 hebcal (3.5-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Updated DH to level 10. (Closes: #817493)
   * debian/control:
   - Bumped Standards-Version to 3.9.8.
   - Added Homepage field.
   * debian/watch: created.
Checksums-Sha1:
 262011ef63da67dd85bce2943fcb2a7d50731e3f 1644 hebcal_3.5-2.1.dsc
 1257d1bc6ee3ca3ed4158aca50eb76d38cb61a44 2599 hebcal_3.5-2.1.diff.gz
Checksums-Sha256:
 5f91b3d9c6c17e1dd8222d33309fd4ac33318828c67844c4d5dbd28c93bab14e 1644 
hebcal_3.5-2.1.dsc
 d91e77e08ccbe2d30ec1e84aeee091f476e2132bd2eff78732b923301fe029a9 2599 
hebcal_3.5-2.1.diff.gz
Files:
 3db9abfced5cf21ace29e8d1683bc59d 1644 utils optional hebcal_3.5-2.1.dsc
 e152b005ea3a56694bb04a0e87947461 2599 utils optional hebcal_3.5-2.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX+BSlAAoJEN5juccE6+nvz30P/jpFSMxagVx/7C4dH8vbv2OB
KQTi4X+MDivqymLqCnb056swAenClaC/FRYgS0y+6r69FNrZc4htt8t3eCnT08+y
Ugd6QtnnJYPiY5z1pp3sKtnTOMGP8LSTTNmsrKmyB9A3dRVHmJ3B4c99EZs8h/8i
ad5QXLJqYcHWHx3Nm+44ckD0pQ0u+pt6kNn/fHdqkyUxHJQFsLXY73L5O5JGyVoN
XB3Nr1aYLvSxCgyEAV7bGxMsSeZaXmAakJyw6ps3kpfKfZN1eXAFWrlO8ZrSj6FA
GW3JgeW4tSEuz4QYL0PXQHKz40zx+bDL5wfkVjM1xJ9q3GGxJ7JUO8Ws0c+eE4TK
34+R9uoAYE9y7+dMI+XPLwGH5Iw4ncu66bbmpgbj2k30JSltYoTtghhKLG3X5yRY
ngaZ0fT11KdKpAwUIpg+baaO8Xyhh7AGbp3zgpnTnQb6szvqWf7BZAXbKaqh9mTs
5LZ/vs50mRFox0EBexYsUgSmUwxJ4xW2nWFucya22EeInu5pC62aRGLj75VEvbq7
bRNei2zvPOry9xp5XHSdf38ZgivODfeqEgzKjXfOvRiQH+Isk8/jE68DF1HOaElG
j8HXCPnUa5t6//PiuXn75YfKaaTwwPQ5Ajf+RmFCZsT7Pkm814QGE+BGzKhb5RVe
vM7OdBYlC5u3NtwFWeNn
=lcz8
-END PGP SIGNATURE End Message ---

Processed: bandwidthcalc: diff for NMU version 0.2-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 817372 + patch
Bug #817372 [src:bandwidthcalc] bandwidthcalc: Removal of debhelper compat 4
Added tag(s) patch.
> tags 817372 + pending
Bug #817372 [src:bandwidthcalc] bandwidthcalc: Removal of debhelper compat 4
Added tag(s) pending.

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

Bug#817372: bandwidthcalc: diff for NMU version 0.2-1.1

[fike]

Control: tags 817372 + patch
Control: tags 817372 + pending

Dear maintainer,

I've prepared an NMU for bandwidthcalc (versioned as 0.2-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u bandwidthcalc-0.2/debian/changelog bandwidthcalc-0.2/debian/changelog
--- bandwidthcalc-0.2/debian/changelog
+++ bandwidthcalc-0.2/debian/changelog
@@ -1,3 +1,15 @@
+bandwidthcalc (0.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Updated DH level to 10. (Closes: #817372)
+  * debian/control:
+- Bumped Standards-Version to 3.9.8
+  * debian/copyright:
+- Fixed license link.
+  * Run wrap-and-sort.
+
+ -- Fernando Ike   Sat, 15 Oct 2016 22:58:05 -0300
+
 bandwidthcalc (0.2-1) unstable; urgency=low
 
   * New Upstream Version
diff -u bandwidthcalc-0.2/debian/compat bandwidthcalc-0.2/debian/compat
--- bandwidthcalc-0.2/debian/compat
+++ bandwidthcalc-0.2/debian/compat
@@ -1 +1 @@
-4
+10
diff -u bandwidthcalc-0.2/debian/control bandwidthcalc-0.2/debian/control
--- bandwidthcalc-0.2/debian/control
+++ bandwidthcalc-0.2/debian/control
@@ -2,13 +2,21 @@
 Section: x11
 Priority: optional
 Maintainer: Christoph Goehre 
-Build-Depends: debhelper (>= 4.0.0), autotools-dev, libatk1.0-dev, 
libglib2.0-dev (>= 2.6), libgtk2.0-dev (>= 2.6), libpango1.0-dev
+Build-Depends:
+ autotools-dev,
+ debhelper (>= 10),
+ libatk1.0-dev,
+ libglib2.0-dev (>= 2.6),
+ libgtk2.0-dev (>= 2.6),
+ libpango1.0-dev,
 DM-Upload-Allowed: yes
-Standards-Version: 3.8.0
+Standards-Version: 3.9.8
 
 Package: bandwidthcalc
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends:
+ ${misc:Depends},
+ ${shlibs:Depends},
 Description: file transfer time calculator written in GTK+
  Given the available bandwidth, bandwidthcalc determines how long it will take
  to transfer a file of a given size. You can specify the available bandwidth in
diff -u bandwidthcalc-0.2/debian/copyright bandwidthcalc-0.2/debian/copyright
--- bandwidthcalc-0.2/debian/copyright
+++ bandwidthcalc-0.2/debian/copyright
@@ -25,2 +25 @@
-Public License can be found in `/usr/share/common-licenses/GPL'.
-
+Public License can be found in `/usr/share/common-licenses/GPL-2'.

Processed: your mail

[Debian Bug Tracking System]

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

> tag 840711 +pending
Bug #840711 [src:golang-github-appc-docker2aci] golang-github-appc-docker2aci: 
CVE-2016-8579
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#841124: FTBFS on amd64

[James Clarke]

Control: tags -1 patch fixed-upstream

On Mon, Oct 17, 2016 at 08:40:21PM +0100, James Clarke wrote:
> Source: elfutils
> Version: 0.166-2.1
> Severity: serious
>
> Hi,
> My NMU (#832584) FTBFS on amd64[1]. However, the only changes were
> adding Build-Depends on sparc64, and 0.166-2 itself FTBFS in a clean
> amd64 chroot (log attached), so it seems the more recent dependencies
> are problematic.
>
> Important part of the (buildd) log:
>
> > FAIL: run-backtrace-native.sh
> > =
> >
> > 0x7fa73d9dc000  0x7fa73dd76000  /lib/x86_64-linux-gnu/libc-2.24.so
> > 0x7fa73dd7a000  0x7fa73df93000  /lib/x86_64-linux-gnu/libpthread-2.24.so
> > 0x7fa73df97000  0x7fa73e1bb000  /lib/x86_64-linux-gnu/ld-2.24.so
> > 0x7fa73e1bc000  0x7fa73e3bf000  / PKGBUILDDIR /tests/backtrace-child
> > 0x7ffe5aaf5000  0x7ffe5aaf7000  [vdso: 16415]
> > TID 16415:
> > # 0 0x7fa73dd8afdf  raise
> > # 1 0x7fa73e1bcad5 - 1  main
> > # 2 0x7fa73d9fc2b1 - 1  __libc_start_main
> > # 3 0x7fa73e1bcc0a - 1  _start
> > TID 16416:
> > # 0 0x7fa73dd8afdf  raise
> > # 1 0x7fa73e1bcd6b - 1  sigusr2
> > # 2 0x7fa73da0f040  (null)
> > # 3 0x7fa73e1bce70  jmp
> > # 4 0xa8428197 - 1  (null)
> > backtrace: backtrace.c:128: callback_verify: Assertion `symname != NULL
> > && strcmp (symname, "stdarg") == 0' failed.
> > ./test-subr.sh: line 84: 16412 Aborted
> > LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
> > $VALGRIND_CMD "$@"
> > # 1 0x7fa73e1bcad5 - 1  main
> > backtrace-child: neither empty nor just out of DWARF
> > FAIL run-backtrace-native.sh (exit status: 1)
>
> Regards,
> James
>
> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=elfutils=amd64=0.166-2.1=1476727320

This was fixed upstream by [1]. I intend to perform another NMU to fix
this; please let me know if you disagree.

Regards,
James

[1] 
https://git.fedorahosted.org/cgit/elfutils.git/commit/?id=9008499a5276c45b37bc0adb47e7ad227e6ba2a9


signature.asc
Description: PGP signature

Processed: Re: Bug#841124: FTBFS on amd64

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch fixed-upstream
Bug #841124 [src:elfutils] FTBFS on amd64
Added tag(s) fixed-upstream and patch.

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

Bug#837281: [PKG-Openstack-devel] Bug#837281: manila-ui: FTBFS: compressor.exceptions.OfflineGenerationError: No template loaders defined. You must set TEMPLATE_LOADERS in your settings or set 'loader

[Santiago Vila]

On Thu, 13 Oct 2016, Thomas Goirand wrote:

> On 10/12/2016 10:56 PM, Santiago Vila wrote:
> > found 837281 2.5.1-0
> > thanks
> > 
> > I can still reproduce the error reported by Lucas in this version.
> > 
> > I attach a build log for 2.5.1-0.
> > 
> > I think this could be a bug in openstack-dashboard, one of the
> > build-depends. If this is really the case, please use reassign and
> > affects so that we can see the bug in the page for src:manila-ui and
> > this way we avoid filing duplicate bugs.
> 
> [...]
>
> Though technically, I don't think this bug should stay open. There's no
> bug in manila-ui, only in Horizon 9, which was already filled in the BTS
> and fixed by the upload of version 10. If you know a way to express this
> in the BTS, let me know, [...]

I explained the way to express this in the BTS in my previous message.
(See the text I quoted above).

I will repeat it with a little bit more of detail:

If this is not a bug in manila-ui but in some other package, then please
reassign this bug to some-other-package and then send this to the
control address:

affects 837281 src:manila-ui

(You can "reassign" and "affects" in the same message, of course).

The "affects" command will make this bug to appear in the bug page for
manila-ui, because it's the real reason for the FTBFS. This should
help everybody to see that this is really a bug in some-other-package
and at the same time it will help people like me (who build packages
in testing) to avoid filing duplicate bugs against manila-ui.

Thanks.

Bug#841134: amarok: FTBFS (cmake error)

[Santiago Vila]

Package: src:amarok
Version: 2.8.0-5
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with kde --parallel
   dh_testdir -i -O--parallel
   dh_update_autotools_config -i -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -Skde -- -DCMAKE_USE_RELATIVE_PATHS=ON 
-DKDE4_BUILD_TESTS=false
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_BUILD_TYPE=Debian 
-DCMAKE_USE_RELATIVE_PATHS=ON -DKDE4_BUILD_TESTS=false
-- The C compiler identification is GNU 6.2.0
-- The CXX compiler identification is GNU 6.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info

[... snipped ...]

Feature record: CXX_FEATURE:0cxx_inline_namespaces
Feature record: CXX_FEATURE:0cxx_lambdas
Feature record: CXX_FEATURE:0cxx_lambda_init_captures
Feature record: CXX_FEATURE:0cxx_local_type_template_args
Feature record: CXX_FEATURE:0cxx_long_long_type
Feature record: CXX_FEATURE:0cxx_noexcept
Feature record: CXX_FEATURE:0cxx_nonstatic_member_init
Feature record: CXX_FEATURE:0cxx_nullptr
Feature record: CXX_FEATURE:0cxx_override
Feature record: CXX_FEATURE:0cxx_range_for
Feature record: CXX_FEATURE:0cxx_raw_string_literals
Feature record: CXX_FEATURE:0cxx_reference_qualified_functions
Feature record: CXX_FEATURE:0cxx_relaxed_constexpr
Feature record: CXX_FEATURE:0cxx_return_type_deduction
Feature record: CXX_FEATURE:0cxx_right_angle_brackets
Feature record: CXX_FEATURE:0cxx_rvalue_references
Feature record: CXX_FEATURE:0cxx_sizeof_member
Feature record: CXX_FEATURE:0cxx_static_assert
Feature record: CXX_FEATURE:0cxx_strong_enums
Feature record: CXX_FEATURE:1cxx_template_template_parameters
Feature record: CXX_FEATURE:0cxx_thread_local
Feature record: CXX_FEATURE:0cxx_trailing_return_types
Feature record: CXX_FEATURE:0cxx_unicode_literals
Feature record: CXX_FEATURE:0cxx_uniform_initialization
Feature record: CXX_FEATURE:0cxx_unrestricted_unions
Feature record: CXX_FEATURE:0cxx_user_literals
Feature record: CXX_FEATURE:0cxx_variable_templates
Feature record: CXX_FEATURE:0cxx_variadic_macros
Feature record: CXX_FEATURE:0cxx_variadic_templates
Determining if the function dlopen exists in the dl passed with the following 
output:
Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_9bc6d/fast"
make[2]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_9bc6d.dir/build.make 
CMakeFiles/cmTC_9bc6d.dir/build
make[3]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_9bc6d.dir/CheckFunctionExists.c.o
/usr/bin/cc-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -DCHECK_FUNCTION_EXISTS=dlopen   -o 
CMakeFiles/cmTC_9bc6d.dir/CheckFunctionExists.c.o   -c 
/usr/share/cmake-3.6/Modules/CheckFunctionExists.c
Linking C executable cmTC_9bc6d
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_9bc6d.dir/link.txt 
--verbose=1
/usr/bin/cc  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -DCHECK_FUNCTION_EXISTS=dlopen   -Wl,-z,relro  
CMakeFiles/cmTC_9bc6d.dir/CheckFunctionExists.c.o  -o cmTC_9bc6d -rdynamic -ldl 
make[3]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'


dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_BUILD_TYPE=Debian -DCMAKE_USE_RELATIVE_PATHS=ON 
-DKDE4_BUILD_TESTS=false returned exit code 1
debian/rules:11: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
debian/rules:27: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

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

Thanks.

Processed: pending #840825: libtag1-dev: missing header files

[Debian Bug Tracking System]

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

> tag 840825 + pending
Bug #840825 [libtag1-dev] libtag1-dev: missing header files
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#841133: ruby-gruff: FTBFS: Tests hang after segmentation fault

[Chris Lamb]

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

Dear Maintainer,

ruby-gruff fails to build from source in unstable/amd64:

  […]

  /usr/lib/ruby/vendor_ruby/test/unit/ui/testrunnermediator.rb:65:in `run_suite'
  /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:53:in `run'
  /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:124:in `run_test'
  /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:53:in `run'
  /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:124:in `run_test'
  /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:53:in `run'
  /usr/lib/ruby/vendor_ruby/test/unit/testsuite.rb:124:in `run_test'
  /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:467:in `run'
  /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:467:in `catch'
  /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:468:in `block in run'
  /usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:283:in `run_setup'
  /usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:248:in `run_fixture'
  /usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:267:in `block in 
create_fixtures_runner'
  /usr/lib/ruby/vendor_ruby/test/unit/fixture.rb:267:in `block in 
create_fixtures_runner'
  /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:470:in `block (2 levels) in 
run'
  /usr/lib/ruby/vendor_ruby/test/unit/testcase.rb:744:in `run_test'
  
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/test/test_bezier.rb:14:in
 `test_bezier'
  
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/test/test_bezier.rb:14:in
 `new'
  
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/lib/gruff/base.rb:230:in
 `initialize'
  
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/lib/gruff/base.rb:968:in
 `reset_themes'
  
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/lib/gruff/base.rb:968:in
 `new'
  
/home/lamby/temp/cdt.20161017230027.J3bkHcnItG.db.ruby-gruff/ruby-gruff-0.6.0/lib/gruff/base.rb:968:in
 `initialize'
  
  -- Machine register context 
   RIP: 0x7f59938d0249 RBP: 0x RSP: 0x7ffd0ad90bd0
   RAX: 0x RBX: 0x01ee7510 RCX: 0x0021
   RDX: 0x RDI: 0x7f5993bf1b00 RSI: 0x
R8: 0x01ee7520  R9: 0x41a0 R10: 0x
   R11: 0x R12: 0x7f5993bf1b58 R13: 0x7f5993bf1b18
   R14: 0x01ee7510 R15: 0x7f5993bf1b00 EFL: 0x00010246
  

  […]

The full build log is attached.


Regards,

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


ruby-gruff.0.6.0-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#840691: libgs9: security update DSA-3691-1 breaks zathura, evince, ... in jessie

[Francesco Poli]

On Mon, 17 Oct 2016 06:52:25 +0200 Salvatore Bonaccorso wrote:

[...]
> Only a small status update. I worked on the very same patches for
> ghostscript as well for the unstable version, to confirm I did not any
> significant mistake in the backports. The problem starts there as well
> once the patches are applied, and I suspect it actually might have
> uncovered a bug in a library which is used by evince and zathura(-ps),
> libspectre came to my mind.

So, if I understand correctly, the same bug would appear in Debian
unstable, with the security patches applied.
Hence, finding a fix is even more important.

> 
> We go no reports for other clients so far, not using that.
> 
> If you want to give the packages as well for unstable a try, I have
> uploaded to https://people.debian.org/~carnil/tmp/ghostscript/ .

I hope other people will find the time to test the packages.
I am unfortunately swamped: I won't be able to follow the debugging
closely.   :-(

[...]
> Stay tuned, and any debugging help welcome.

Many thanks for the update.
Looking forward to seeing the issue solved for the best.

Thanks a lot for your time!


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


pgpUTN9zplCZL.pgp
Description: PGP signature

Bug#841132: kid3: FTBFS: fatal error: chapterframe.h: No such file or directory

[Aurelien Jarno]

Package: kid3
Version: 3.4.2-1
Severity: serious

kid3 fails to build from source on all architectures with the following
error:

| /«PKGBUILDDIR»/src/plugins/taglibmetadata/taglibfile.cpp:119:26: fatal error: 
chapterframe.h: No such file or directory
|  #include 
|   ^
| compilation terminated.
| src/plugins/taglibmetadata/CMakeFiles/taglibmetadata.dir/build.make:93: 
recipe for target 
'src/plugins/taglibmetadata/CMakeFiles/taglibmetadata.dir/taglibfile.cpp.o' 
failed
| make[4]: *** 
[src/plugins/taglibmetadata/CMakeFiles/taglibmetadata.dir/taglibfile.cpp.o] 
Error 1

A full build log is available for example there:

https://buildd.debian.org/status/fetch.php?pkg=kid3=s390x=3.4.2-1%2Bb2=1476154044

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

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

Bug#698527: Already fixed in oldstable

[Francesco Poli]

On Sat, 15 Oct 2016 19:54:28 +0300 Adrian Bunk wrote:

> I am closing this bug since it is already fixed in oldstable.

ElmerGUI is included in the experimental package (elmerfem/7.0.svn.6034
+dfsg-2): it's not clear to me how the OpenSSL linking issue was solved.
I cannot find any explanation in the changelog: could someone please
clarify?

Please let me know.
Thanks for your time!


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


pgpPLurjMgVre.pgp
Description: PGP signature

Bug#841131: dump: FTBFS: aclocal-1.14: command not found

[Aurelien Jarno]

Package: dump
Version: 0.4b46-2
Severity: serious

dump fails to build from source on all architectures with the following
error:

| make[1]: Leaving directory '/«PKGBUILDDIR»'
|    dh_auto_build -a
|   make -j1
| make[1]: Entering directory '/«PKGBUILDDIR»'
| CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash /«PKGBUILDDIR»/missing 
aclocal-1.14 -I m4
| /«PKGBUILDDIR»/missing: line 81: aclocal-1.14: command not found
| WARNING: 'aclocal-1.14' is missing on your system.
|  You should only need it if you modified 'acinclude.m4' or
|  'configure.ac' or m4 files included by 'configure.ac'.
|  The 'aclocal' program is part of the GNU Automake package:
|  
|  It also requires GNU Autoconf, GNU m4 and Perl in order to run:
|  
|  
|  
| Makefile:405: recipe for target 'aclocal.m4' failed
| make[1]: *** [aclocal.m4] Error 127
| make[1]: Leaving directory '/«PKGBUILDDIR»'
| dh_auto_build: make -j1 returned exit code 2
| debian/rules:31: recipe for target 'build-arch' failed

You can get a full build log for example there:

https://buildd.debian.org/status/fetch.php?pkg=dump=s390x=0.4b46-2=1476009177

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

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

Bug#841128: aws-shell: FTBFS (ImportError: No module named 'setuptools')

[Santiago Vila]

Package: src:aws-shell
Version: 0.1.1-1
Severity: serious

Dear maintainer:

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


[...]
dpkg-buildpackage: info: source package aws-shell
dpkg-buildpackage: info: source version 0.1.1-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by TANIGUCHI Takaki 
 dpkg-source --before-build aws-shell-0.1.1
 fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
   dh_testdir -O--buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:184: python3.5 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 5, in 
from setuptools import setup, find_packages
ImportError: No module named 'setuptools'
E: pybuild pybuild:276: clean: plugin distutils failed with: exit code=1: 
python3.5 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p 3.5 returned exit code 13
debian/rules:7: recipe for target 'clean' failed
make: *** [clean] Error 25
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2


[ Now that the package is in the archive, please consider uploading
  this package in source-only form. That should help avoid failures
  like this one ].

Thanks.

Bug#841129: src:libjpeg-turbo: FTBFS on mips*: jsimd_mips.c:82:3: error: 'env' undeclared

[Aurelien Jarno]

Package: src:libjpeg-turbo
Version: 1:1.5.1-1
Severity: serious
Tags: patch upstream

libjpeg-turbo fails to build from source on mips* with the following
error:

| libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
-ffloat-store -c jsimd_mips_dspr2.S -fPIE -o jsimd_mips_dspr2.o >/dev/null 2>&1
| jsimd_mips.c: In function 'init_simd':
| jsimd_mips.c:82:3: error: 'env' undeclared (first use in this function)
|env = getenv("JSIMD_FORCEDSPR2");
|^~~
| jsimd_mips.c:82:3: note: each undeclared identifier is reported only once for 
each function it appears in
| Makefile:596: recipe for target 'jsimd_mips.lo' failed

The problem is that the env variable is not declared in the MIPS
specific code. The following simple patch fixes the issue:

--- libjpeg-turbo-1.5.1.orig/simd/jsimd_mips.c
+++ libjpeg-turbo-1.5.1/simd/jsimd_mips.c
@@ -63,6 +63,8 @@ parse_proc_cpuinfo(const char* search_st
 LOCAL(void)
 init_simd (void)
 {
+  char *env = NULL;
+
   if (simd_support != ~0U)
 return;

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: mips64el (mips64)

Kernel: Linux 4.7.0-1-5kc-malta
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#841124: FTBFS on amd64

[James Clarke]

Source: elfutils
Version: 0.166-2.1
Severity: serious

Hi,
My NMU (#832584) FTBFS on amd64[1]. However, the only changes were
adding Build-Depends on sparc64, and 0.166-2 itself FTBFS in a clean
amd64 chroot (log attached), so it seems the more recent dependencies
are problematic.

Important part of the (buildd) log:

> FAIL: run-backtrace-native.sh
> =
> 
> 0x7fa73d9dc000  0x7fa73dd76000  /lib/x86_64-linux-gnu/libc-2.24.so
> 0x7fa73dd7a000  0x7fa73df93000  /lib/x86_64-linux-gnu/libpthread-2.24.so
> 0x7fa73df97000  0x7fa73e1bb000  /lib/x86_64-linux-gnu/ld-2.24.so
> 0x7fa73e1bc000  0x7fa73e3bf000  / PKGBUILDDIR /tests/backtrace-child
> 0x7ffe5aaf5000  0x7ffe5aaf7000  [vdso: 16415]
> TID 16415:
> # 0 0x7fa73dd8afdf  raise
> # 1 0x7fa73e1bcad5 - 1  main
> # 2 0x7fa73d9fc2b1 - 1  __libc_start_main
> # 3 0x7fa73e1bcc0a - 1  _start
> TID 16416:
> # 0 0x7fa73dd8afdf  raise
> # 1 0x7fa73e1bcd6b - 1  sigusr2
> # 2 0x7fa73da0f040  (null)
> # 3 0x7fa73e1bce70  jmp
> # 4 0xa8428197 - 1  (null)
> backtrace: backtrace.c:128: callback_verify: Assertion `symname != NULL
> && strcmp (symname, "stdarg") == 0' failed.
> ./test-subr.sh: line 84: 16412 Aborted
> LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
> $VALGRIND_CMD "$@"
> # 1 0x7fa73e1bcad5 - 1  main
> backtrace-child: neither empty nor just out of DWARF
> FAIL run-backtrace-native.sh (exit status: 1)

Regards,
James

[1] 
https://buildd.debian.org/status/fetch.php?pkg=elfutils=amd64=0.166-2.1=1476727320
I: Copying COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.17575
I: forking: cp -al /var/cache/pbuilder/base.cow 
/var/cache/pbuilder/build/cow.17575
I: removed stale ilistfile /var/cache/pbuilder/build/cow.17575/.ilist
I: forking: chroot /var/cache/pbuilder/build/cow.17575 
cowdancer-ilistcreate /.ilist 'find . -xdev -path ./home -prune -o \( \( -type 
l -o -type f \) -a -links +1 -print0 \) | xargs -0 stat --format '%d %i ''
I: Invoking pbuilder
I: forking: pbuilder build --binary-arch --buildplace 
/var/cache/pbuilder/build/cow.17575 --buildresult /var/cache/pbuilder/result/ 
--binary-arch --no-targz --internal-chrootexec 'chroot 
/var/cache/pbuilder/build/cow.17575 cow-shell' 
/home/james/src/elfutils/elfutils_0.166-2.dsc
I: Running in no-targz mode
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Mon Oct 17 20:16:01 BST 2016
I: pbuilder-time-stamp: 1476731761
I: copying local configuration
I: mounting /proc filesystem
I: mounting /sys filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /pbuilder-repo
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Installing the build-deps
 -> Attempting to parse the build-deps
 -> Considering build-depdebhelper (>= 9)
   -> Trying to add debhelper
 -> Considering build-dep autotools-dev
   -> Trying to add autotools-dev
 -> Considering build-dep autoconf
   -> Trying to add autoconf
 -> Considering build-dep automake
   -> Trying to add automake
 -> Considering build-dep bzip2
   -> Trying to add bzip2
 -> Considering build-dep zlib1g-dev
   -> Trying to add zlib1g-dev
 -> Considering build-dep libbz2-dev
   -> Trying to add libbz2-dev
 -> Considering build-dep liblzma-dev
   -> Trying to add liblzma-dev
 -> Considering build-dep m4
   -> Trying to add m4
 -> Considering build-dep gettext
   -> Trying to add gettext
 -> Considering build-dep gawk
   -> Trying to add gawk
 -> Considering build-dep dpkg-dev (>= 1.16.1~)
   -> Trying to add dpkg-dev
 -> Considering build-dep gcc-multilib [any-amd64]
   -> Trying to add gcc-multilib
 -> Considering build-dep libc6-dbg [powerpc powerpcspe ppc64 ppc64el armel 
armhf arm64]
   -> This package is not for this architecture
 -> Considering build-dep flex
   -> Trying to add flex
 -> Considering build-dep bison
   -> Trying to add bison
 -> Installing  debhelper autotools-dev autoconf automake bzip2 zlib1g-dev 
libbz2-dev liblzma-dev m4 gettext gawk dpkg-dev gcc-multilib flex bison
Reading package lists...
Building dependency tree...
Reading state information...
bzip2 is already the newest version (1.0.6-8).
dpkg-dev is already the newest version (1.18.10).
The following additional packages will be installed:
  autopoint bsdmainutils dh-autoreconf dh-strip-nondeterminism file
  gcc-6-multilib gettext-base groff-base intltool-debian lib32asan3
  lib32atomic1 lib32cilkrts5 lib32gcc-6-dev lib32gcc1 lib32gomp1 lib32itm1
  lib32mpx2 lib32quadmath0 lib32stdc++6 lib32ubsan0 libarchive-zip-perl
  libbison-dev libbsd0 libc6-dev-i386 libc6-dev-x32 libc6-i386 libc6-x32
  libcroco3 libffi6 libfile-stripnondeterminism-perl libfl-dev libglib2.0-0
  libicu57 libmagic-mgc libmagic1 libpipeline1 libsigsegv2 libtimedate-perl
  

Bug#839138: Ceph maintainership status

[GCS]

Hi,

On Mon, Oct 17, 2016 at 8:34 PM, Adrian Bunk  wrote:
> The current status of the Ceph packages [1] does not look good.
>
> src:ceph has 3 RC bugs, from "maintainer address bounces"
> to "crashes since the latest NMU".
 I think (hope) that even if the sender get back a mail that the list
is moderated, someone may check the queue and allow mails to the
mailing list after moderation (killing spam).

> If you still intend to maintain Ceph, do the emails from the BTS
> actually reach you? If not, a list at Alioth might be a better option.
 OK, I don't remember any Ceph bugreport - but I no longer closely
monitor the packaging.

> It would also be OK if you would state that there is noone left active
> among the Ceph Maintainers, and that I can orphan the package for
> finding new maintainers.
 I've hardware issues for long and can't use it - even worse, my
computer died some days ago as the motherboard has a short circuit on
it somewhere. I'm on the way to get an other, used computer which may
be used for Ceph as well. Still, I don't want to promise I can shake
up the packaging - even if it seems I'll need a stable distributed
filesystem in the future.

I'd a discussion with Dmitry and if I understood correctly, he no
longer wants to be a close contributor - but I let him speak about his
intentions.

Regards,
Laszlo/GCS

Bug#839138: Ceph maintainership status

[Adrian Bunk]

Hi,

first of all thanks for your past work on Ceph.

The current status of the Ceph packages [1] does not look good.

src:ceph has 3 RC bugs, from "maintainer address bounces"
to "crashes since the latest NMU".

If you still intend to maintain Ceph, do the emails from the BTS 
actually reach you? If not, a list at Alioth might be a better option.

It would also be OK if you would state that there is noone left active
among the Ceph Maintainers, and that I can orphan the package for
finding new maintainers.

Regarding ceph-dkms, this is only in experimental and has an RC bug
that it doesn't work with the jessie kernel.
Is there anything left that is not in the upstream kernel?

Thanks
Adrian

[1] https://qa.debian.org/developer.php?login=ceph-maintain...@lists.ceph.com

-- 

   "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#837629: OpenRD* with debian's u-boot 2016.09

[Vagrant Cascadian]

On 2016-10-05, Vagrant Cascadian wrote:
> On 2016-10-03, Rick Thomas wrote:
>> On Oct 1, 2016, at 3:39 PM, Vagrant Cascadian  wrote:
>>> On 2016-09-17, Rick Thomas wrote:
 On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian  wrote:
...
>>> If not, I'll likely be removing OpenRD* from the packages on future
>>> uploads.
> ...
>> Sadly, it doesn’t look like it fixed the problem.  Still nothing after
>> installing the new u-boot.kwb and typing “reset”.
>>
>> let me know if there’s anything more I can do to help…
>
> If it's not fixed in 2016.11~rc1, the only thing left to try is git
> bisecting the issue...

Could also try building with a different version of gcc (e.g. the one in
jessie, or gcc-5* from sid, which may take more configuring). There may
be issues triggered by gcc-6...


live well,
  vagrant


signature.asc
Description: PGP signature

Processed: Fix for the openjdk-8-jre-dcevm FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -help
Bug #831153 [src:openjdk-8-jre-dcevm] openjdk-8-jre-dcevm: FTBFS with GCC 6: 
os.hpp:28:30: fatal error: jvmtifiles/jvmti.h: No such file or directory
Removed tag(s) help.
> tags -1 +patch
Bug #831153 [src:openjdk-8-jre-dcevm] openjdk-8-jre-dcevm: FTBFS with GCC 6: 
os.hpp:28:30: fatal error: jvmtifiles/jvmti.h: No such file or directory
Added tag(s) patch.

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

Bug#831153: Fix for the openjdk-8-jre-dcevm FTBFS

[Adrian Bunk]

Control: tags -1 -help
Control: tags -1 +patch

There are 5 different issues regarding this FTBFS and attempts to 
resolve it:

1. Changing the build dependencies doesn't change the compiler.
Adding g++-5 resulted in #835956, but when you don't tell the build
system of the software to use this compiler the default g++ is still
used.
This explains why that build dependency didn't help
(but point 2 is a better solution).

2. --std=gnu++98 fixes the C++ related build failure.

3. readdir_r() is deprecated in latest glibc.
This generates a new warning, and openjdk-8-jre-dcevm turns all warnings 
into errors by passing -Werror to the compiler.

4. Upstream uses CFLAGS instead of CXXFLAGS for C++
This is a bug somewhere in the upstream code,
using DEB_CXXFLAGS_MAINT_APPEND didn't work.

5. I didn't encounter the original build failure due to missing jvmti.h
It seems the file from openjdk-8-jdk-headless was found successfully?


The following change gave me a successful build:

--- debian/rules.old2016-10-17 15:48:31.0 +
+++ debian/rules2016-10-17 15:49:00.0 +
@@ -1,5 +1,7 @@
 #!/usr/bin/make -f
 
+export DEB_CFLAGS_MAINT_APPEND = -std=gnu++98 
-Wno-error=deprecated-declarations
+
 PACKAGE = $(shell dpkg-parsechangelog -S Source)
 
 export DISABLE_HOTSPOT_OS_VERSION_CHECK=ok




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#841012: swi-prolog: FTBFS on armel/armhf: segmentation fault during the tests

[Lev Lamberov]

Hi Emilio,


17.10.2016 02:00, Emilio Pozuelo Monfort пишет:
> Source: swi-prolog
> Version: 7.2.3+dfsg-1
> Severity: serious
>
> Your package failed to build on armel/armhf during a rebuild:
>
> make[3]: Leaving directory 
> '/«BUILDDIR»/swi-prolog-7.2.3+dfsg/packages/jpl/src/java'
> if [ -r jpltest.jar ]; then \
> 
> LD_LIBRARY_PATH="/usr/lib/jvm/java-8-openjdk-armel/jre/lib/arm/server:/usr/lib/jvm/java-8-openjdk-armel/jre/lib/arm"
>  ../swipl.sh  -q -f test_jpl.pl -g run_tests,halt -t 'halt(1)' ; \
>   else \
> echo "No jpltest.jar; maybe junit is not installed?" ; \
>   fi
> JUNIT=/usr/share/java/junit.jar JAVA=java 
> JAVA_PRELOAD=/usr/lib/jvm/java-8-openjdk-armel/jre/lib/arm/libjsig.so 
> ./test-java.sh
> Welcome to SWI-Prolog (Multi-threaded, 32 bits, Version 7.2.3)
> Copyright (c) 1990-2015 University of Amsterdam, VU Amsterdam
> SWI-Prolog comes with ABSOLUTELY NO WARRANTY. This is free software,
> and you are welcome to redistribute it under certain conditions.
> Please visit http://www.swi-prolog.org for details.
>
> For help, use ?- help(Topic). or ?- apropos(Word).
>
>
> % halt
> Segmentation fault
>
> Full logs at https://buildd.debian.org/status/package.php?p=swi-prolog

Thanks for reporting! Sometimes it happens with SWI-Prolog on
"non-mainstream" architectures. Will take a look at it.

Regards,
Lev



signature.asc
Description: OpenPGP digital signature

Bug#841111: jasper: CVE-2016-8691 CVE-2016-8692

[Salvatore Bonaccorso]

Source: jasper
Version: 1.900.1-13
Severity: grave
Tags: security upstream patch

Hi,

the following vulnerabilities were published for jasper.

CVE-2016-8692[0]:
FPE on unknown address ... jpc_dec_process_siz ... jpc_dec.c

CVE-2016-8691[1]:
FPE on unknown address ... jpc_dec_process_siz ... jpc_dec.c

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-8692
[1] https://security-tracker.debian.org/tracker/CVE-2016-8691
[2] 
https://github.com/mdadams/jasper/commit/d8c2604cd438c41ec72aff52c16ebd8183068020
[3] 
https://blogs.gentoo.org/ago/2016/10/16/jasper-two-divide-by-zero-in-jpc_dec_process_siz-jpc_dec-c/

Regards,
Salvatore

Bug#841112: jasper: CVE-2016-8690

[Salvatore Bonaccorso]

Source: jasper
Version: 1.900.1-13
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

the following vulnerability was published for jasper.

CVE-2016-8690[0]:
SEGV on unknown address ... bmp_getdata ... bmp_dec.c

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-8690
[1] 
https://blogs.gentoo.org/ago/2016/10/16/jasper-two-null-pointer-dereference-in-bmp_getdata-bmp_dec-c/

Regards,
Salvatore

Bug#841110: jasper: CVE-2016-8693

[Salvatore Bonaccorso]

Source: jasper
Version: 1.900.1-13
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for jasper.

CVE-2016-8693[0]:
attempting double-free ... mem_close ... jas_stream.c

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-8693
[1] 
https://blogs.gentoo.org/ago/2016/10/16/jasper-double-free-in-mem_close-jas_stream-c/

Regards,
Salvatore

Bug#839982: axi-cache: xapian.FeatureUnavailableError: Flint backend no longer supported

[John]

To confirm the earlier reports, I get the FeatureUnavailableError message also:

/etc/cron.weekly/apt-xapian-index:
Traceback (most recent call last):
  File "/usr/sbin/update-apt-xapian-index", line 102, in 
indexer.incrementalUpdate()
  File "/usr/lib/python2.7/dist-packages/axi/indexer.py", line 670, in 
incrementalUpd
+ate
self.updateIndex(dbpath)
  File "/usr/lib/python2.7/dist-packages/axi/indexer.py", line 629, in 
updateIndex
db = xapian.WritableDatabase(pathname, xapian.DB_CREATE_OR_OPEN)
  File "/usr/lib/python2.7/dist-packages/xapian/__init__.py", line 8619, in 
__init__
_xapian.WritableDatabase_swiginit(self, _xapian.new_WritableDatabase(*args))
xapian.FeatureUnavailableError: Flint backend no longer supported
run-parts: /etc/cron.weekly/apt-xapian-index exited with return code 1

Processed: [bts-link] source package golang-github-appc-docker2aci

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package 
> golang-github-appc-docker2aci
> # 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 #839282 (http://bugs.debian.org/839282)
> # Bug title: CVE-2016-7569
> #  * https://github.com/appc/docker2aci/issues/201
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 839282 + fixed-upstream
Bug #839282 [docker2aci] CVE-2016-7569
Added tag(s) fixed-upstream.
> usertags 839282 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 839282 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#817636: marked as done (pycmail: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2016 17:30:22 +
with message-id 
and subject line Bug#817636: fixed in pycmail 0.1.6
has caused the Debian Bug report #817636,
regarding pycmail: Removal of debhelper compat 4
to be marked as done.

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

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


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

Hi,

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

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

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

Thanks,
~Niels

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

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

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

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

Debian distribution maintenance software
pp.
Radovan Garabík  (supplier of updated pycmail 
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, 17 Oct 2016 16:20:41 +0200
Source: pycmail
Binary: pycmail
Architecture: source all
Version: 0.1.6
Distribution: unstable
Urgency: high
Maintainer: Radovan Garabík 
Changed-By: Radovan Garabík 
Description:
 pycmail- mail sorter written in Python
Closes: 817636
Changes:
 pycmail (0.1.6) unstable; urgency=high
 .
   * increase debhelper compat version (closes: #817636)
   * update URLs and addresses in the documentation
Checksums-Sha1:
 7a2ec7456f2f09a197c83cdf92b8f9f6f12e432f 1381 pycmail_0.1.6.dsc
 8de5bec20d8f598448d6ffc40c3956a0c4b4a90d 15071 pycmail_0.1.6.tar.gz
 46cc81128f611b129592522a83eef7c15c965752 18120 pycmail_0.1.6_all.deb
Checksums-Sha256:
 56da6efaf3f2ead4b368d65394d4a94719a133081c34158054647a35ac4422e7 1381 
pycmail_0.1.6.dsc
 f9615c2fb0e3a6670894e020ad2838e051b8cacc1e2ae5df246f7a5781928984 15071 
pycmail_0.1.6.tar.gz
 453ec6d9df8a345be298f79e177ff70288363ada175c346f1e5d416786f2a2ff 18120 
pycmail_0.1.6_all.deb
Files:
 a36b88642c95e0f3907c50b6099fa463 1381 mail optional pycmail_0.1.6.dsc
 a3ecacb29f63f21cc4261e235a776ce5 15071 mail optional pycmail_0.1.6.tar.gz
 e31e3bdea995f12875e02a870aa22808 18120 mail optional pycmail_0.1.6_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYBOP+AAoJEGhWpKZArz/TPDAP/3uWrKj9rUrKH490+Dwx8AbN
iIwK4DoJHlgdqe07vLy0eLeMXaPPSOyZBcMxKKhnr2BgtmZtHiHvFKWDBrJZo8Cy
vdbOe/pwYFwASaXcWg9bVPefnf9zCzXEKTcJ5qaR5GLI61LlSAqwWlvunz+NYv8A
CfrsTlcW0ctMdiCM7w3qVT0S+rveP4J5U5V0PLpKsWkKFgbFbwAJqW9sTs7Kf+Wm
agwZjdgMDtsWc7eM9d2qOl5EkCP7dDftreKHwWUjZXziqAzVeJIc8+h5BzUmamt2
fkaKY9OVYVaMgzQ0eVL34omv9YAGqbifOK9iAh5ctVcwGaWbLg9g+BjNFMlFDSuK
Lgg6OEP/w2F0ov4QwvpFssSMvf4gdz3JVxyA1F/eqS6i9Fxk8r9EqHPLXjW+flAE
fHUXMSEcjwfdbHP78r1usWo0TV9rnic9Y67K46xhdbEEaePLqAfl5ZRynAmgWTUR
8PzBfhgdi5MmBWurN9+whPsU0Btb747/p0bs0Vl3SvPJPmDiG4xsJhOTZVTzQjOy
/cpj1HTADzK8MnC/qXKW6KfR5AWgidSdbkc/gAHIv95ukpHzSEhckhqjhyXpEWpE
xeJ1usYI0RebVpc0Kr3swYiQzE1d4CkHhGLYLJIvKr8Idlsu+F82DDtK7BHyJh4+
V4QYyGwACpcwN2TMjNYh
=TSlQ
-END PGP SIGNATURE End Message ---

Bug#839795: marked as done (FTBFS, needs to be updated for liblognorm v2 and libfastjson)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2016 17:30:47 +
with message-id 
and subject line Bug#839795: fixed in sagan 1.1.2-0.1
has caused the Debian Bug report #839795,
regarding FTBFS, needs to be updated for liblognorm v2 and libfastjson
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.)


-- 
839795: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sagan
Version: 1.0.1-0.3
Severity: serious
Tags: fixed-upstream

liblognorm v2 is based on libfastjson and no longer json-c.

sagan needs to be updated accordingly. The latest upstream release 1.1.2
has support for liblognorm >= 2.0.0 and libfastjson.




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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: sagan
Source-Version: 1.1.2-0.1

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

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

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

Debian distribution maintenance software
pp.
Herbert Parentes Fortes Neto  (supplier of updated sagan 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Oct 2016 11:16:54 -0300
Source: sagan
Binary: sagan
Architecture: source amd64
Version: 1.1.2-0.1
Distribution: unstable
Urgency: medium
Maintainer: Pierre Chifflier 
Changed-By: Herbert Parentes Fortes Neto 
Description:
 sagan  - Real-time System & Event Log Monitoring System
Closes: 839795
Changes:
 sagan (1.1.2-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release. (Closes: #839795).
   * debian/control:
   - debhelper 10.
   - lsb-base package added to Depends.
   - Bump Standards-Version from 3.9.6 to 3.9.8
   - Homepage entry updated.
   * debian/copyright:
   - updated.
   - format 1.0.
   * debian/rules:
   - hardening added.
   - LDFLAGS_MAINT_APPEND added.
   * debian/patches:
   - no-bluedot-and-others.patch refreshed.
   * debian/postinst:
  - '--home /nonexistent' added.
   * debian/postrm:
  - using 'set -e' in the body of the script.
Checksums-Sha1:
 8b79b888222ebd5b4cdd571d6b5b4095d77986f5 1815 sagan_1.1.2-0.1.dsc
 cbc0f7168d23ddc7dbc706dca95a1d3664495030 585478 sagan_1.1.2.orig.tar.gz
 5955c2bc34bbfc0c10a04b437967fecb262fcb25 7836 sagan_1.1.2-0.1.debian.tar.xz
 54b41b4a01e05bf7dc53f91e7851d3a7c9ed041c 98264 sagan_1.1.2-0.1_amd64.deb
Checksums-Sha256:
 21249cc4c95a3dbbe371c7bfa7cd778d0c765fb46f9fdc9a1241c8e57e7a9083 1815 
sagan_1.1.2-0.1.dsc
 abd0d085dc25422ae61fb20f7e8c87be1da02c3f75ffe9d6a930d54717b8d9e3 585478 
sagan_1.1.2.orig.tar.gz
 d6ddbeae2d459253e1cbc538f71bde73aabef47ab56845ba64600c1394bc7f61 7836 
sagan_1.1.2-0.1.debian.tar.xz
 c96292442c8d9d16d6d1b6e32959071ea28b87fdab4a0eb476f1beb15754aa10 98264 
sagan_1.1.2-0.1_amd64.deb
Files:
 205b92506d11aaef436897d33746dd13 1815 admin extra sagan_1.1.2-0.1.dsc
 7d86591bbd7daf08c0ee9bf8c075d24e 585478 admin extra sagan_1.1.2.orig.tar.gz
 c02c532b764e999ca89bf4ea4ec508dc 7836 admin extra sagan_1.1.2-0.1.debian.tar.xz
 9ebd1acd11363e95b92c27d178993fca 98264 admin extra sagan_1.1.2-0.1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX/kBbAAoJEFUlbyisYGEamegP/iIiEDIPiBYmrvtSj+1bpDRz
qEITQcwTK1k4m21iV+tX2X3Hn5X+PmamrUMqhikGqXMSaQRwiw5ukMuFiWMwCNra
XYnMEVHykHDauFWjV0xLUypDnpIBcanwaSPesF7gcW8s0d4MAwIuBhTnzVqZgzLs
IX4NjixLjTtkCYZbbEC09NPvix9uyUnDsMPDBkzC6r7qtHV7oBtYCbn7ociKjgf2
K/1ZulVMgdYjXaM6aNSuQ41DmgcSJWXbRBT/d/2LedHjSzHMtKUoMV+QDvb/ZlUv
mBZlkBhQYMaIp5LWzYG622YszzWTyc6JmU5/qOs/KDNN+uwB3ZN1idcNYxoHB+aX
mBmNobr067iz01aNy4M2xF/GtRGTVRuwnhK6PY7cVQz6Z5O3AB92Aj3rUgNLZ3Dy
Leeju4TEVlUv63L5rIQEeDyutonlBuJEbkLOEBQ8jlAuTRk31yETZb8Tq81Yqmln

Bug#839511: marked as done (zeroinstall-injector: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2016 17:32:17 +
with message-id 
and subject line Bug#839511: fixed in zeroinstall-injector 2.12-2
has caused the Debian Bug report #839511,
regarding zeroinstall-injector: FTBFS: Tests failures
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> 
> Error 'New feed's modification time is before old version!
> Interface: http://foo/
> Old time: 2013-09-25T11:57:28Z
> New time: 2013-09-25T11:43:10Z
> Refusing update.' does not match regexp 'New feed's modification time is 
> before old version!
> Interface: http://foo/
> Old time: 2013-09-25T12:57:28Z
> New time: 2013-09-25T12:43:10Z
> Refusing update.'
> 
> --
> Ran: 295 tests in: 1.12 seconds.
> FAILED: Cases: 295 Tried: 295 Errors: 1 Failures: 0 Skip:  4 Todo: 0 
> Timeouts: 0.
> 
> Makefile:29: recipe for target 'test' failed

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

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

The full build log is available from:
   
http://aws-logs.debian.net/2016/10/01/zeroinstall-injector_2.12-1_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Thomas Leonard  (supplier of updated zeroinstall-injector 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 02 Oct 2016 12:53:59 +
Source: zeroinstall-injector
Binary: 0install 0install-core zeroinstall-injector
Architecture: source amd64 all
Version: 2.12-2
Distribution: unstable
Urgency: medium
Maintainer: Thomas Leonard 
Changed-By: Thomas Leonard 
Description:
 0install   - cross-distribution packaging system
 0install-core - cross-distribution packaging system (non-GUI parts)
 zeroinstall-injector - transitional package for 0install
Closes: 839511
Changes:
 zeroinstall-injector (2.12-2) unstable; urgency=medium
 .
   * Add missing build dep on tzdata. Closes: #839511.
Checksums-Sha1:
 29b6e7582c217276d7451444f9359729f01d0a35 2277 zeroinstall-injector_2.12-2.dsc
 9359a9744e5a3c25f63cfcab575805a1bcebe578 441288 
zeroinstall-injector_2.12.orig.tar.bz2
 4a81cad3703cfa458a402aed03a253a7b6f21c3a 13848 
zeroinstall-injector_2.12-2.debian.tar.xz
 a577efb267a348b7a8131b447f16e2c76e7f254b 339068 
0install-core-dbgsym_2.12-2_amd64.deb
 433590063b1ab11f7088cf2f44382b97f97e9140 1344406 0install-core_2.12-2_amd64.deb
 d0775c2b625735b7e0be588e75a7e105ccaf708e 129556 
0install-dbgsym_2.12-2_amd64.deb
 0c9ef100c77a6ff324073cede5e4ce62665bab71 584616 0install_2.12-2_amd64.deb
 1224c3b9b18671936d3495177d7658c45289bc97 1086 
zeroinstall-injector_2.12-2_all.deb
Checksums-Sha256:
 

Bug#841096: espresso: FTBFS (make install fails)

[Santiago Vila]

Note: It does not always fail for me.

I tried 13 times so far. It failed 11 times.

Status: failed  espresso_6.0-2_amd64-20161013T061302Z
Status: failed  espresso_6.0-2_amd64-20161013T152415Z
Status: failed  espresso_6.0-2_amd64-20161013T152515Z
Status: failed  espresso_6.0-2_amd64-20161013T222907Z
Status: failed  espresso_6.0-2_amd64-20161013T222909Z
Status: failed  espresso_6.0-2_amd64-20161013T222914Z
Status: failed  espresso_6.0-2_amd64-20161013T222916Z
Status: successful  espresso_6.0-2_amd64-20161013T222903Z
Status: failed  espresso_6.0-2_amd64-20161016T115947Z
Status: failed  espresso_6.0-2_amd64-20161017T165805Z
Status: successful  espresso_6.0-2_amd64-20161017T165810Z
Status: failed  espresso_6.0-2_amd64-20161017T165807Z
Status: failed  espresso_6.0-2_amd64-20161017T165803Z

So, it seems to be random.

Thanks.

Bug#837000: marked as done (kerberos-configs: FTBFS: Undefined subroutine ::read_config called at ./genblob line 9.)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2016 17:16:31 +
with message-id 
and subject line Bug#837000: fixed in kerberos-configs 2.5
has caused the Debian Bug report #837000,
regarding kerberos-configs: FTBFS: Undefined subroutine ::read_config 
called at ./genblob line 9.
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.)


-- 
837000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kerberos-configs
Version: 2.3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 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):
>  fakeroot debian/rules binary
> ./genblob >tmp & tmp config-blob
> Undefined subroutine ::read_config called at ./genblob line 9.
> debian/rules:17: recipe for target 'config-blob' failed
> make: *** [config-blob] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/kerberos-configs_2.3_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Sam Hartman  (supplier of updated kerberos-configs 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, 17 Oct 2016 11:08:17 -0400
Source: kerberos-configs
Binary: krb5-config
Architecture: source all
Version: 2.5
Distribution: unstable
Urgency: medium
Maintainer: Sam Hartman 
Changed-By: Sam Hartman 
Description:
 krb5-config - Configuration files for Kerberos Version 5
Closes: 741051 751972 777182 836422 837000
Changes:
 kerberos-configs (2.5) unstable; urgency=medium
 .
   * Read configuration parser out of current directory, Closes: #837000
   * New Swedish Debconf translations, Closes: #751972
   * New Brazilian Portuguese debconf translations, Thanks Diego Neves,
 Closes: #836422
   * Reproducible Builds support; sort keys in output, Closes: #777182
   * Remove outdated entries from krb5.conf, Closes: #741051
   * Update standards version (no changes)
Checksums-Sha1:
 54b4c4d7db17353317947b246b964e64184952c4 1400 kerberos-configs_2.5.dsc
 23c7fd6eb47c015c5dc4538201cd4c4fc8c142dd 26764 kerberos-configs_2.5.tar.xz
 32ec937c5b9126e7becb670f3f5004ed8bf923b3 24570 krb5-config_2.5_all.deb
Checksums-Sha256:
 67b3a58e37ad0d754618c1b9a746025872709434f8135eb2e4cb862e38b06d6a 1400 
kerberos-configs_2.5.dsc
 906c2f35e8485d6554a7f34869880d63fcd2683320e62b63983d630b9a81d24b 26764 
kerberos-configs_2.5.tar.xz
 4bfd7950634d2dd93118e89d607ea3acd598a54e58d5c4fd927bf03dd735e27a 24570 
krb5-config_2.5_all.deb
Files:
 434cf3dbce3c28f758a4b219cf6b464d 1400 net optional kerberos-configs_2.5.dsc
 1873c6950f6b5be02bed25556ee6a9fe 26764 net optional kerberos-configs_2.5.tar.xz
 49c2bbcc1745ca056419e5b5a2828bcb 24570 net optional krb5-config_2.5_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGIBAEBCAAGBQJYBOuOAAoJEHyaUfYmslafKGQLXjv6LRsxJGHYkl4AC/D0/n3f
Ba+mBjti2H1SiLEPLWm0NnyC/UPg4swMgD3m1CE+D4pt84uT3+jwg168WVbXTJpt
pugOVk8bB91LLDpoh9K5hLJ/h9jo3aULOOjEK+shoUMdJVjR17+y3j3fYu8mKQWG
r2dDiZd/D+rAFBpKUR2Xm7ungOEKSKPvemEJQNLDd8XC4/6gZ7vBM6qXsqIm+Gmp
O57l/H3ve4EbMFoXTqiBIxa18CIzxI51jBxNYuForBOTk7quLYxo4kBjyBM3Dvlg
NoJPMghrrQ4gnxXJlKB3q2Q25JU4jBpgG7DtO6VIaVffwpSazBJHE5iisy9egViE
Hk9uO7fG6IdeHje1HciGl2XZnuQQwztW3Es77Gdbns5UDJzcGB8ibV/0vuUTBn9j
2x7xpufWddQNXcOiDddisH7pE4xSETYi8O4Ln/AKhCPtPSh7i9b6KJZRZDjnajLm
JZTOC0DX5AL//38=
=ynt3

Bug#817511: marked as done (keyboards-rg: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2016 17:16:36 +
with message-id 
and subject line Bug#817511: fixed in keyboards-rg 0.3
has caused the Debian Bug report #817511,
regarding keyboards-rg: Removal of debhelper compat 4
to be marked as done.

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

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


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

Hi,

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

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

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

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: keyboards-rg
Source-Version: 0.3

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

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

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

Debian distribution maintenance software
pp.
Radovan Garabík  (supplier of updated 
keyboards-rg 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, 17 Oct 2016 14:52:51 +0200
Source: keyboards-rg
Binary: keyboards-rg
Architecture: source all
Version: 0.3
Distribution: unstable
Urgency: high
Maintainer: Radovan Garabík 
Changed-By: Radovan Garabík 
Description:
 keyboards-rg - Various keyboard layouts for X-window and linux console
Closes: 601350 817511
Changes:
 keyboards-rg (0.3) unstable; urgency=high
 .
   * increase compat level (closes: #817511), thanks to Logan Rosen
   * replace obsolete Suggests (closes: #601350)
Checksums-Sha1:
 e140c1aad53761528a0420884b7dc63f74392716 1403 keyboards-rg_0.3.dsc
 0bb3d47e7c125b9fca39db3c7ce91c34de74cdbe 16523 keyboards-rg_0.3.tar.gz
 6b9cc6fa5ddb24b70aa7b4a278f6a199a2d8e8a6 11694 keyboards-rg_0.3_all.deb
Checksums-Sha256:
 26335265de5e0e92a7b3adfbd593c7b5cb804330f453543c1458d3740a19779b 1403 
keyboards-rg_0.3.dsc
 5485e1b622f8aee0adb3d1e70ce7ae399b3ae87ebe4d7c414386645e466f4996 16523 
keyboards-rg_0.3.tar.gz
 ffe54f12f602c42e2a24ec3262167029477f8a148b00faa5be61777d03d2cfc9 11694 
keyboards-rg_0.3_all.deb
Files:
 60d2755e74cfcb621f01f586adcac633 1403 misc optional keyboards-rg_0.3.dsc
 443cfe5a94624c8820b945a9abf4ae56 16523 misc optional keyboards-rg_0.3.tar.gz
 41ede0aae3eafd768190a9f3a4aa0b12 11694 misc optional keyboards-rg_0.3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYBNRCAAoJEGhWpKZArz/TEfIP/2CPKxnQfX/YNdI7qSf/IrE/
jxH8tUIY0uGGJSFe+Cgb7AGY+elAYtSWxdmGQ54LuBfgsHB4YlMw1W9/WZ9rmgwm
QqpdKWQ5B5CFMHXV/VpVLzpmhtwH2Q77LneYdK8i3UdkKDrZURJOYKxrcuX5v2DW
tjAoJdeReOfre/yrXb/mab8Er0979wQrlRx/auDJFmbq8N1OLwk3Oruq742nn9vI
KKWHSGVBZkv19oJ+BgW68FMLx9kJKH0NBArGefL8cZOzMwLAbq2YjegzYc+o852b
YlgvTK9DkO0ZJC9jVEcej3f7NktPr3vzBPiIACB9/ejCJmezQj0mI8rDUddf3NmU
NDERkPq5h/3pzNVzzBcVev65gRU45tovL6jNAsC984eD3oVQyoESrGmxYtPHzVO6
4sKw8hX7FIXV8Stn5zGdsFr7M5+F5EGUcaBxE8E050vZrQT5wnuJstav0E3MjMsI
yhQDM3DsuF0dg2QO9x7Q+eRuYUwl8A2WeNzlfj0nJ70S9Ov/Dd8pQ4G8IbA/c/BE
m4+wDJrikoyWHtXM5WFs8okj2HvhzRAJI7gH2j+7zK9mI8tyxcBylgLA2ULJF+5D
EEqthGLfalkCgAB+EJKXEw94q5ozpBMKdvQ8kFzDhldeMkVtbgniiND/llTqMkan
AgorC7JLtpbyJlZYhMBq
=/LF/
-END PGP SIGNATURE End Message ---

Bug#841096: espresso: FTBFS (make install fails)

[Santiago Vila]

Note: A similar failure happened on the ppc64 autobuilder:

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

So I guess this is not architecture-related.

What kind of bug makes "make install" to fail?
A bug in the Makefile?

My autobuilder has a single CPU, maybe that's relevant.

Thanks.

Bug#841098: rygel: FTBFS (rygel-media-engine-test fails)

[Santiago Vila]

Package: src:rygel
Version: 0.32.0-2
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with autoreconf,gnome
   dh_testdir -i
   dh_update_autotools_config -i
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf --as-needed
Copying file m4/codeset.m4
Copying file m4/extern-inline.m4
Copying file m4/fcntl-o.m4
Copying file m4/glibc2.m4
Copying file m4/glibc21.m4
Copying file m4/intdiv0.m4

[... snipped ...]

# TOTAL: 8
# PASS:  7
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: rygel-media-engine-test
=


(lt-rygel-media-engine-test:659): GStreamer-WARNING **: Element 'filesrc4' 
already has parent
**
ERROR:rygel-media-engine-test.c:2035:__lambda19_: code should not be reached
FAIL rygel-media-engine-test (exit status: 134)


Testsuite summary for Rygel 0.32.0

# TOTAL: 8
# PASS:  7
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to http://bugzilla.gnome.org/enter_bug.cgi?product=Rygel

Makefile:1762: recipe for target 'test-suite.log' failed
make[5]: *** [test-suite.log] Error 1
make[5]: Leaving directory '/<>/tests'
Makefile:1868: recipe for target 'check-TESTS' failed
make[4]: *** [check-TESTS] Error 2
make[4]: Leaving directory '/<>/tests'
Makefile:1990: recipe for target 'check-am' failed
make[3]: *** [check-am] Error 2
make[3]: Leaving directory '/<>/tests'
Makefile:596: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory '/<>'
Makefile:887: recipe for target 'check' failed
make[1]: *** [check] Error 2
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The build was made on a QEMU/KVM virtual machine with a single CPU using sbuild.

The relevant part of the build log is included above.

If you need a full build log, just say so, I have plenty of them.

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

Thanks.

Bug#841096: espresso: FTBFS (make install fails)

[Santiago Vila]

Package: src:espresso
Version: 6.0-2
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh_auto_configure --\
--with-elpa-include=-I/usr/include/elpa/modules \
--with-elpa-lib=-lelpa
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libexecdir=\${prefix}/lib/espresso 
--disable-maintainer-mode --disable-dependency-tracking 
--with-elpa-include=-I/usr/include/elpa/modules --with-elpa-lib=-lelpa
configure: WARNING: unrecognized options: --disable-silent-rules, 
--disable-maintainer-mode, --disable-dependency-tracking
checking build system type... x86_64-pc-linux-gnu
checking ARCH... x86_64
checking setting AR... ... ar
checking setting ARFLAGS... ... ruv
checking for ifort... no
checking for pgf90... no
checking for pathf95... no

[... snipped ...]

make[3]: Leaving directory '/<>/PW/src'
( cd tools ; /usr/bin/make all || exit 1 )
make[3]: Entering directory '/<>/PW/tools'
if test -n "" ; then \
( cd ../.. ; /usr/bin/make  || exit 1 ) ; fi
mpif90 -O3 -g -x f95-cpp-input -D__GFORTRAN -D__STD_F95 -D__FFTW3 -D__MPI 
-D__SCALAPACK -D__ELPA_2016 -D__ELPA_2016 -I/<>//include 
-I../include/ -I/usr/include/elpa/modules -I../../iotk/src -I../../Modules 
-I../../FFTXlib -I../../LAXlib -I../src -I.  -c dist.f90
f951: Warning: Nonexistent include directory '../include/' 
[-Wmissing-include-dirs]
mpif90 -g -pthread -o dist.x \
dist.o ../src/libpw.a ../../Modules/libqemod.a ../../FFTXlib/libqefft.a 
../../LAXlib/libqela.a ../../clib/clib.a ../../iotk/src/libiotk.a -lelpa 
-lscalapack-openmpi -lblacs-openmpi -lblacsF77init-openmpi -llapack  -lblas  
-lfftw3  -lblas 
( cd ../../bin ; ln -fs ../PW/tools/dist.x . )
mpif90 -O3 -g -x f95-cpp-input -D__GFORTRAN -D__STD_F95 -D__FFTW3 -D__MPI 
-D__SCALAPACK -D__ELPA_2016 -D__ELPA_2016 -I/<>//include 
-I../include/ -I/usr/include/elpa/modules -I../../iotk/src -I../../Modules 
-I../../FFTXlib -I../../LAXlib -I../src -I.  -c ev_xml.f90
f951: Warning: Nonexistent include directory '../include/' 
[-Wmissing-include-dirs]
mpif90 -O3 -g -x f95-cpp-input -D__GFORTRAN -D__STD_F95 -D__FFTW3 -D__MPI 
-D__SCALAPACK -D__ELPA_2016 -D__ELPA_2016 -I/<>//include 
-I../include/ -I/usr/include/elpa/modules -I../../iotk/src -I../../Modules 
-I../../FFTXlib -I../../LAXlib -I../src -I.  -c ev.f90
f951: Warning: Nonexistent include directory '../include/' 
[-Wmissing-include-dirs]
mpif90 -g -pthread -o ev.x \
ev.o ev_xml.o ../src/libpw.a ../../Modules/libqemod.a 
../../FFTXlib/libqefft.a ../../LAXlib/libqela.a ../../clib/clib.a 
../../iotk/src/libiotk.a -lelpa -lscalapack-openmpi -lblacs-openmpi 
-lblacsF77init-openmpi -llapack  -lblas  -lfftw3  -lblas 
( cd ../../bin ; ln -fs ../PW/tools/ev.x . )
mpif90 -O3 -g -x f95-cpp-input -D__GFORTRAN -D__STD_F95 -D__FFTW3 -D__MPI 
-D__SCALAPACK -D__ELPA_2016 -D__ELPA_2016 -I/<>//include 
-I../include/ -I/usr/include/elpa/modules -I../../iotk/src -I../../Modules 
-I../../FFTXlib -I../../LAXlib -I../src -I.  -c kpoints.f90
f951: Warning: Nonexistent include directory '../include/' 
[-Wmissing-include-dirs]
mpif90 -g -pthread -o kpoints.x \
kpoints.o ../src/libpw.a ../../Modules/libqemod.a 
../../FFTXlib/libqefft.a ../../LAXlib/libqela.a ../../clib/clib.a 
../../iotk/src/libiotk.a -lelpa -lscalapack-openmpi -lblacs-openmpi 
-lblacsF77init-openmpi -llapack  -lblas  -lfftw3  -lblas 
( cd ../../bin ; ln -fs ../PW/tools/kpoints.x . )
mpif90 -O3 -g -x f95-cpp-input -D__GFORTRAN -D__STD_F95 -D__FFTW3 -D__MPI 
-D__SCALAPACK -D__ELPA_2016 -D__ELPA_2016 -I/<>//include 
-I../include/ -I/usr/include/elpa/modules -I../../iotk/src -I../../Modules 
-I../../FFTXlib -I../../LAXlib -I../src -I.  -c pwi2xsf.f90
f951: Warning: Nonexistent include directory '../include/' 
[-Wmissing-include-dirs]
mpif90 -g -pthread -o pwi2xsf.x \
pwi2xsf.o ../src/libpw.a ../../Modules/libqemod.a 
../../FFTXlib/libqefft.a ../../LAXlib/libqela.a ../../clib/clib.a 
../../iotk/src/libiotk.a -lelpa -lscalapack-openmpi -lblacs-openmpi 
-lblacsF77init-openmpi -llapack  -lblas  -lfftw3  -lblas 
( cd ../../bin ; ln -fs ../PW/tools/pwi2xsf.x . )
make[3]: Leaving directory '/<>/PW/tools'
make[2]: Leaving directory '/<>/PW'
make[1]: Leaving directory '/<>'
(cd pseudo; ../PW/src/generate_vdW_kernel_table.x)
(cd pseudo; ../PW/src/generate_rVV10_kernel_table.x)
(cd Doc; /usr/bin/make)
make[1]: Entering directory '/<>/Doc'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/<>/Doc'
 fakeroot debian/rules binary-indep
dh binary-indep --after dh_auto_test --with autotools_dev --parallel
dh: The 

Bug#840815: marked as done (acl2: FTBFS on some architectures: HARD ACL2 ERROR in ASSERT$: Assertion failed:)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2016 12:26:26 -0400
with message-id <878ttngcwd@maguirefamily.org>
and subject line Re: Bug#840815: acl2: FTBFS on some architectures: HARD ACL2 
ERROR in ASSERT$: Assertion failed:
has caused the Debian Bug report #840815,
regarding acl2: FTBFS on some architectures: HARD ACL2 ERROR in ASSERT$: 
Assertion failed:
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.)


-- 
840815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: acl2
Version: 7.2dfsg-2
Severity: serious

Hi,

Your package failed to build on mips64el, as well as in some other
(non-release) architectures. From the mips64el log:

start address -T 0xc0c0f0 ;; Finished loading #p"boot-strap-pass-2.o"
;; Loading "defpkgs.lisp"
[GC for 95 SYMBOL pages..(T=9).GC finished]
[GC for 334 CONS pages..(T=10).GC finished]
[GC for 344 CONS pages..(T=10).GC finished]
[GC for 344 CONS pages..(T=10).GC finished]
[GC for 344 CONS pages..(T=10).GC finished]
;; Finished loading "defpkgs.lisp"
[GC for 74 SFUN pages..(T=10).GC finished]


HARD ACL2 ERROR in ASSERT$:  Assertion failed:
(ASSERT$ (AND (TRUE-LISTP DIR)
  (EQ (CAR DIR) :ROOT))
 (LET* ((MSWINDOWS-DRIVE (MSWINDOWS-DRIVE # STATE))
(TMP (IF MSWINDOWS-DRIVE # "/")))
   (DOLIST (X DIR)
   (WHEN (STRINGP X) (SETQ TMP #)))
   (WHEN (STRINGP NAME)
 (SETQ TMP (CONCATENATE # TMP NAME)))
   (WHEN (STRINGP TYPE)
 (SETQ TMP (CONCATENATE # TMP "." TYPE)))
   (LET ((NAMESTRING-TMP #)
 (NAMESTRING-TRUENAME #))
(COND (# TMP) (# TMP) (T # #)
(See :DOC set-iprint to be able to see elided values in this message.)



ACL2 Error in ACL2-INTERFACE:  Evaluation aborted.  To debug see :DOC
print-gv, see :DOC trace, and see :DOC wet.


Error: 
Fast links are on: do (si::use-fast-links nil) for debugging
Signalled by INITIALIZE-ACL2.

Raw Lisp Break.
SIMPLE-ERROR: ACL2 Halted

Broken at APPLY.  Type :H for Help.
1  Return to top level. 
ACL2>>make[2]: Entering directory '/«PKGBUILDDIR»'
ACL2_WD is /«PKGBUILDDIR»
Initialization FAILED: acl2-status.txt should contain :INITIALIZED.
GNUmakefile:340: recipe for target 'check_init_ok' failed
make[2]: *** [check_init_ok] Error 1


Full logs at https://buildd.debian.org/status/package.php?p=acl2

Emilio
--- End Message ---
--- Begin Message ---
Greetings, and thanks for your report!  Fixed in -3.

Take care,

Emilio Pozuelo Monfort  writes:

> Source: acl2
> Version: 7.2dfsg-2
> Severity: serious
>
> Hi,
>
> Your package failed to build on mips64el, as well as in some other
> (non-release) architectures. From the mips64el log:
>
> start address -T 0xc0c0f0 ;; Finished loading #p"boot-strap-pass-2.o"
> ;; Loading "defpkgs.lisp"
> [GC for 95 SYMBOL pages..(T=9).GC finished]
> [GC for 334 CONS pages..(T=10).GC finished]
> [GC for 344 CONS pages..(T=10).GC finished]
> [GC for 344 CONS pages..(T=10).GC finished]
> [GC for 344 CONS pages..(T=10).GC finished]
> ;; Finished loading "defpkgs.lisp"
> [GC for 74 SFUN pages..(T=10).GC finished]
>
>
> HARD ACL2 ERROR in ASSERT$:  Assertion failed:
> (ASSERT$ (AND (TRUE-LISTP DIR)
>   (EQ (CAR DIR) :ROOT))
>  (LET* ((MSWINDOWS-DRIVE (MSWINDOWS-DRIVE # STATE))
> (TMP (IF MSWINDOWS-DRIVE # "/")))
>(DOLIST (X DIR)
>(WHEN (STRINGP X) (SETQ TMP #)))
>(WHEN (STRINGP NAME)
>  (SETQ TMP (CONCATENATE # TMP NAME)))
>(WHEN (STRINGP TYPE)
>  (SETQ TMP (CONCATENATE # TMP "." TYPE)))
>(LET ((NAMESTRING-TMP #)
>  (NAMESTRING-TRUENAME #))
> (COND (# TMP) (# TMP) (T # #)
> (See :DOC set-iprint to be able to see elided values in this message.)
>
>
>
> ACL2 Error in ACL2-INTERFACE:  Evaluation aborted.  To debug see :DOC
> print-gv, see :DOC trace, and see :DOC wet.
>
>
> Error: 
> Fast links are on: do (si::use-fast-links nil) for debugging
> Signalled by INITIALIZE-ACL2.
>
> Raw Lisp Break.
> SIMPLE-ERROR: ACL2 Halted
>
> Broken at APPLY.  Type :H for Help.
> 1  Return to top level. 
> ACL2>>make[2]: Entering directory '/«PKGBUILDDIR»'
> ACL2_WD is /«PKGBUILDDIR»
> Initialization FAILED: acl2-status.txt should contain :INITIALIZED.
> GNUmakefile:340: recipe for target 'check_init_ok' failed
> make[2]: *** [check_init_ok] Error 1
>
>
> Full logs at 

Processed: Re: python-pyftpdlib: FTBFS: Failure in test_on_incomplete_file_sent

[Debian Bug Tracking System]

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

> tags 790274 + jessie
Bug #790274 [src:python-pyftpdlib] python-pyftpdlib: FTBFS: Failure in 
test_on_incomplete_file_sent
Added tag(s) jessie.
> thanks
Stopping processing here.

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

Bug#790274: python-pyftpdlib: FTBFS: Failure in test_on_incomplete_file_sent

[Santiago Vila]

tags 790274 + jessie
thanks

Note: Before version 1.5.1-1, I was able to build this package without
problems in stretch:

Status: successful  python-pyftpdlib_1.4.0-1_amd64-20160904T035042Z
Status: successful  python-pyftpdlib_1.4.0-1_amd64-20160914T180733Z
Status: successful  python-pyftpdlib_1.4.0-1_amd64-20160925T001440Z
Status: successful  python-pyftpdlib_1.4.0-1_amd64-20161004T022548Z
Status: failed  python-pyftpdlib_1.5.1-1_amd64-20161017T064904Z
Status: failed  python-pyftpdlib_1.5.1-1_amd64-20161017T134145Z
Status: failed  python-pyftpdlib_1.5.1-1_amd64-20161017T134200Z
Status: failed  python-pyftpdlib_1.5.1-1_amd64-20161017T134203Z
Status: failed  python-pyftpdlib_1.5.1-1_amd64-20161017T134212Z

so I'm going to assume that this particular bug (#790274) is only
present in jessie.

Thanks.

Processed: Re: python-pyftpdlib: FTBFS: Failure in test_on_incomplete_file_sent

[Debian Bug Tracking System]

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

> tags 790274 - unreproducible
Bug #790274 [src:python-pyftpdlib] python-pyftpdlib: FTBFS: Failure in 
test_on_incomplete_file_sent
Removed tag(s) unreproducible.
> severity 790274 serious
Bug #790274 [src:python-pyftpdlib] python-pyftpdlib: FTBFS: Failure in 
test_on_incomplete_file_sent
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#613590: marked as done (Bus error on Sparc architecures (conntrackd))

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2016 16:49:34 +0200
with message-id 

Bug#841080: networking-l2gw: FTBFS (ImportError: No module named i18n)

[Santiago Vila]

Package: src:networking-l2gw
Version: 1:1.0.0-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python2
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   dh_auto_build -i -O--buildsystem=python_distutils
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
python setup.py build --force
running build

[... snipped ...]

  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_l2gw/tests/unit/services/l2gateway/ovsdb/test_data.py", line 
27, in 
from networking_l2gw.services.l2gateway.ovsdb import data
  File "networking_l2gw/services/l2gateway/ovsdb/data.py", line 17, in 
from neutron.i18n import _LE
ImportError: No module named i18n

Failed to import test module: 
networking_l2gw.tests.unit.services.l2gateway.test_agent_scheduler
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_l2gw/tests/unit/services/l2gateway/test_agent_scheduler.py", 
line 33, in 
from networking_l2gw.services.l2gateway import agent_scheduler
  File "networking_l2gw/services/l2gateway/agent_scheduler.py", line 24, in 

from neutron.i18n import _LE
ImportError: No module named i18n

Failed to import test module: 
networking_l2gw.tests.unit.services.l2gateway.test_plugin
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_l2gw/tests/unit/services/l2gateway/test_plugin.py", line 30, 
in 
from networking_l2gw.services.l2gateway.ovsdb import data
  File "networking_l2gw/services/l2gateway/ovsdb/data.py", line 17, in 
from neutron.i18n import _LE
ImportError: No module named i18n

--
Ran 0 tests in 0.917s

OK
+ subunit-stats
+ subunit-filter -s --no-passthrough
+ cat /tmp/tmp.WW35SUhnkj
Total tests:   0
Passed tests:  0
Failed tests:  0
Skipped tests: 0
Seen tags: 
+ rm -f /tmp/tmp.WW35SUhnkj
+ testr-python2 slowest
debian/rules:12: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 3
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

There are also build logs like this for both testing and unstable here:

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

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

Thanks.

Processed: Re: Bug#840852: please make libcpupower-dev depend on libcpupower1 (= ${binary:Version})

[Debian Bug Tracking System]

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

> tags 840852 + patch
Bug #840852 [libcpupower-dev] please make libcpupower-dev depend on 
libcpupower1 (= ${binary:Version})
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#840852: please make libcpupower-dev depend on libcpupower1 (= ${binary:Version})

[Mattia Dongili]

tags 840852 + patch
thanks

Ben,

On Sat, Oct 15, 2016 at 06:13:55PM +0300, Vlad Orlov wrote:
...
> Please make libcpupower-dev depend on libcpupower1 (= ${binary:Version}),
> like it's usually done with all the other -dev packages.

I realize the patch is trivial, but anyway here's one that is build
tested and working.

Regards
-- 
mattia
:wq!
commit 8cee65c3229f5f692ad97df9bca117ef194c9ac7
Author: Mattia Dongili 
Date:   Sun Oct 16 18:08:41 2016 -0700

libcpufreq-dev depends on its corresponding binary package

Closes: #840852
Signed-off-by: Mattia Dongili 

diff --git a/debian/changelog b/debian/changelog
index 995c950..eef97ea 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -32,6 +32,10 @@ linux (4.8.1-1~exp1) UNRELEASED; urgency=medium
   * [arm64] Enable SERIAL_8250_EXTENDED, SERIAL_8250_SHARE_IRQ and
 SERIAL_8250_BCM2835AUX, needed for Raspberry Pi 3.
 
+  [ Mattia Dongili ]
+  * make libcpufreq-dev depend on its corresponding binary package
+(Closes: #840852)
+
  -- Ben Hutchings   Sat, 01 Oct 2016 21:51:33 +0100
 
 linux (4.8~rc8-1~exp1) experimental; urgency=medium
diff --git a/debian/templates/control.tools.in b/debian/templates/control.tools.in
index 7c95172..e9318e3 100644
--- a/debian/templates/control.tools.in
+++ b/debian/templates/control.tools.in
@@ -31,7 +31,7 @@ Package: libcpupower-dev
 Build-Profiles: 
 Section: libdevel
 Architecture: linux-any
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: libcpupower1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
 Provides: libcpufreq-dev
 Conflicts: libcpufreq-dev
 Replaces: libcpufreq-dev

Bug#841079: python-pyftpdlib: FTBFS (make install fails)

[Santiago Vila]

Package: src:python-pyftpdlib
Version: 1.5.1-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config

'pyopenssl' third-party module is not installed. This means
FTPS support will be disabled. You can install it with:
'pip install pyopenssl'.
I: pybuild base:184: python3.5 setup.py config 
running config

[... snipped ...]

python setup.py build
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
creating build/lib.linux-x86_64-2.7/pyftpdlib
copying pyftpdlib/log.py -> build/lib.linux-x86_64-2.7/pyftpdlib
copying pyftpdlib/_compat.py -> build/lib.linux-x86_64-2.7/pyftpdlib
copying pyftpdlib/__main__.py -> build/lib.linux-x86_64-2.7/pyftpdlib
copying pyftpdlib/handlers.py -> build/lib.linux-x86_64-2.7/pyftpdlib
copying pyftpdlib/filesystems.py -> build/lib.linux-x86_64-2.7/pyftpdlib
copying pyftpdlib/ioloop.py -> build/lib.linux-x86_64-2.7/pyftpdlib
copying pyftpdlib/servers.py -> build/lib.linux-x86_64-2.7/pyftpdlib
copying pyftpdlib/authorizers.py -> build/lib.linux-x86_64-2.7/pyftpdlib
copying pyftpdlib/__init__.py -> build/lib.linux-x86_64-2.7/pyftpdlib
creating build/lib.linux-x86_64-2.7/pyftpdlib/test
copying pyftpdlib/test/test_authorizers.py -> 
build/lib.linux-x86_64-2.7/pyftpdlib/test
copying pyftpdlib/test/test_functional_ssl.py -> 
build/lib.linux-x86_64-2.7/pyftpdlib/test
copying pyftpdlib/test/test_ioloop.py -> 
build/lib.linux-x86_64-2.7/pyftpdlib/test
copying pyftpdlib/test/runner.py -> build/lib.linux-x86_64-2.7/pyftpdlib/test
copying pyftpdlib/test/test_functional.py -> 
build/lib.linux-x86_64-2.7/pyftpdlib/test
copying pyftpdlib/test/test_filesystems.py -> 
build/lib.linux-x86_64-2.7/pyftpdlib/test
copying pyftpdlib/test/__init__.py -> build/lib.linux-x86_64-2.7/pyftpdlib/test
copying pyftpdlib/test/test_servers.py -> 
build/lib.linux-x86_64-2.7/pyftpdlib/test
copying pyftpdlib/test/README -> build/lib.linux-x86_64-2.7/pyftpdlib/test
copying pyftpdlib/test/keycert.pem -> build/lib.linux-x86_64-2.7/pyftpdlib/test
running build_scripts
creating build/scripts-2.7
copying and adjusting scripts/ftpbench -> build/scripts-2.7
changing mode of build/scripts-2.7/ftpbench from 664 to 775

'pyopenssl' third-party module is not installed. This means
FTPS support will be disabled. You can install it with:
'pip install pyopenssl'.
python setup.py install --user;
running install
error: [Errno 13] Permission denied: '/sbuild-nonexistent'
Makefile:28: recipe for target 'install' failed
make[2]: *** [install] Error 1
make[2]: Leaving directory '/<>'
debian/rules:10: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

A similar failure may be found here:

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

While we are at it, please consider uploading in source-only form (even if the 
package
is Arch:all), so that we get pretty official build logs here:

https://buildd.debian.org/status/package.php?p=python-pyftpdlib

Thanks.

Processed: fixed 840677 in 3.6.3-2

[Debian Bug Tracking System]

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

> fixed 840677 3.6.3-2
Bug #840677 {Done: Jose Gutierrez de la Concha } 
[zeroc-icegridgui] zeroc-icegridgui: fails to upgrade from 'testing' - trying 
to overwrite /usr/bin/icegridgui
Marked as fixed in versions zeroc-ice/3.6.3-2.
> thanks
Stopping processing here.

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

Bug#840969: marked as done (nim: FTBFS: help2man: can't get `--help' info from ./bin/nimble)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2016 13:06:44 +
with message-id 
and subject line Bug#840969: fixed in nim 0.15.0-2
has caused the Debian Bug report #840969,
regarding nim: FTBFS: help2man: can't get `--help' info from ./bin/nimble
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.)


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

Dear Maintainer,

nim fails to build from source in unstable/amd64:

  […]

  CC: compiler_locals
  CC: compiler_itersgen
  CC: compiler_scriptconfig
  CC: compiler_nimconf
  CC: nimble_publish
  CC: stdlib_rdstdin
  CC: stdlib_browsers
  CC: stdlib_linenoise
  Hint:  [Link]
  Hint: operation successful (102139 lines compiled; 14.721 sec total; 
386.539MiB; Debug Build) [SuccessX]
  [NimScript] exec: 
/home/lamby/temp/cdt.20161016152612.BHlh6cTYlF.db.nim/nim-0.15.0/bin/nim c 
--noNimblePath -p:compiler -o:./bin/nimsuggest dist/nimsuggest/nimsuggest.nim
  Hint: used config file 
'/home/lamby/temp/cdt.20161016152612.BHlh6cTYlF.db.nim/nim-0.15.0/config/nim.cfg'
 [Conf]
  Hint: used config file 
'/home/lamby/temp/cdt.20161016152612.BHlh6cTYlF.db.nim/nim-0.15.0/dist/nimsuggest/nimsuggest.nim.cfg'
 [Conf]
  Hint: system [Processing]
  Hint: nimsuggest [Processing]
  Hint: strutils [Processing]
  Hint: parseutils [Processing]
  Hint: math [Processing]
  Hint: algorithm [Processing]
  Hint: os [Processing]
  Hint: times [Processing]
  Hint: posix [Processing]
  Hint: parseopt [Processing]
  Hint: sequtils [Processing]
  Hint: net [Processing]
  Hint: nativesockets [Processing]
  Hint: sets [Processing]
  Hint: hashes [Processing]
  Hint: etcpriv [Processing]
  Hint: rdstdin [Processing]
  Hint: linenoise [Processing]
  Hint: termios [Processing]
  Hint: sexp [Processing]
  Hint: lexbase [Processing]
  Hint: streams [Processing]
  Hint: unicode [Processing]
  Hint: macros [Processing]
  Hint: options [Processing]
  Hint: lists [Processing]
  Hint: strtabs [Processing]
  Hint: osproc [Processing]
  Hint: cpuinfo [Processing]
  Hint: linux [Processing]
  Hint: commands [Processing]
  Hint: msgs [Processing]
  Hint: tables [Processing]
  Hint: ropes [Processing]
  Hint: platform [Processing]
  Hint: terminal [Processing]
  Hint: nversion [Processing]
  Hint: condsyms [Processing]
  Hint: idents [Processing]
  Hint: extccomp [Processing]
  Hint: securehash [Processing]
  Hint: debuginfo [Processing]
  Hint: marshal [Processing]
  Hint: typeinfo [Processing]
  Hint: json [Processing]
  Hint: intsets [Processing]
  Hint: wordrecg [Processing]
  Hint: nimblecmd [Processing]
  Hint: modules [Processing]
  Hint: ast [Processing]
  Hint: idgen [Processing]
  Hint: astalgo [Processing]
  Hint: rodutils [Processing]
  Hint: magicsys [Processing]
  Hint: rodread [Processing]
  Hint: types [Processing]
  Hint: trees [Processing]
  Hint: lexer [Processing]
  Hint: nimlexbase [Processing]
  Hint: llstream [Processing]
  Hint: renderer [Processing]
  Hint: memfiles [Processing]
  Hint: cgendata [Processing]
  Hint: passes [Processing]
  Hint: nimsets [Processing]
  Hint: bitsets [Processing]
  Hint: syntaxes [Processing]
  Hint: parser [Processing]
  Hint: pbraces [Processing]
  Hint: filters [Processing]
  Hint: filter_tmpl [Processing]
  Hint: sigmatch [Processing]
  Hint: semdata [Processing]
  Hint: treetab [Processing]
  Hint: vmdef [Processing]
  Hint: lookups [Processing]
  Hint: prettybase [Processing]
  Hint: semtypinst [Processing]
  Hint: parampatterns [Processing]
  Hint: pretty [Processing]
  Hint: docgen [Processing]
  Hint: rstast [Processing]
  Hint: rst [Processing]
  Hint: rstgen [Processing]
  Hint: highlite [Processing]
  Hint: importer [Processing]
  Hint: sempass2 [Processing]
  Hint: guards [Processing]
  Hint: saturate [Processing]
  Hint: writetracking [Processing]
  Hint: xmltree [Processing]
  Hint: cgi [Processing]
  Hint: cookies [Processing]
  Hint: typesrenderer [Processing]
  Hint: sem [Processing]
  Hint: semfold [Processing]
  Hint: procfind [Processing]
  Hint: pragmas [Processing]
  Hint: transf [Processing]
  Hint: cgmeth [Processing]
  Hint: lambdalifting [Processing]
  Hint: lowerings [Processing]
  Hint: vm [Processing]
  Hint: vmgen [Processing]
  Hint: vmdeps [Processing]
  Hint: vmmarshal [Processing]
  Hint: evaltempl [Processing]
  

Bug#840680: dirmngr: Dirmngr not always responding

[Vincent Lefevre]

On 2016-10-14 03:12:44 +0800, Shengjing Zhu wrote:
> After upgrade to 2.1.15-4, I find dirmngr is not always responding
> which makes command like `gpg --refresh-keys` stuck.

Same problem on a machine I upgraded a few days ago.

This does not occur on a machine which I have not upgraded yet
(I saw the bug with apt-listbugs) to 2.1.15-4.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Re: Processed: Re: Bug#840298: fixed in samba 2:4.4.6+dfsg-2

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 samba/2:4.4.6+dfsg-2
Bug #840298 {Done: Mathieu Parent } [samba] 
libtevent0:i386: new version causes samba to crash
Marked as fixed in versions samba/2:4.4.6+dfsg-2.

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

Bug#840298: Processed: Re: Bug#840298: fixed in samba 2:4.4.6+dfsg-2

[Vincent Lefevre]

Control: fixed -1 samba/2:4.4.6+dfsg-2

On 2016-10-17 12:36:05 +, Debian Bug Tracking System wrote:
> Processing control commands:
> 
> > reassign -1 samba 2:4.4.5+dfsg-3
> Bug #840298 {Done: Mathieu Parent } [libtevent0] 
> libtevent0:i386: new version causes samba to crash
> Bug reassigned from package 'libtevent0' to 'samba'.
> No longer marked as found in versions tevent/0.9.31-1.
> No longer marked as fixed in versions samba/2:4.4.6+dfsg-2.

Marked as fixed in samba/2:4.4.6+dfsg-2 again.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Re: Bug#840298: fixed in samba 2:4.4.6+dfsg-2

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 samba 2:4.4.5+dfsg-3
Bug #840298 {Done: Mathieu Parent } [libtevent0] 
libtevent0:i386: new version causes samba to crash
Bug reassigned from package 'libtevent0' to 'samba'.
No longer marked as found in versions tevent/0.9.31-1.
No longer marked as fixed in versions samba/2:4.4.6+dfsg-2.
Bug #840298 {Done: Mathieu Parent } [samba] 
libtevent0:i386: new version causes samba to crash
Marked as found in versions samba/2:4.4.5+dfsg-3.

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

Bug#840298: fixed in samba 2:4.4.6+dfsg-2

[Vincent Lefevre]

Control: reassign -1 samba 2:4.4.5+dfsg-3

On 2016-10-12 06:20:46 +, Mathieu Parent wrote:
> Source: samba
> Source-Version: 2:4.4.6+dfsg-2
> 
> We believe that the bug you reported is fixed in the latest version of
> samba, which is due to be installed in the Debian FTP archive.
[...]

Reassigning to samba, otherwise apt-listbugs complains that libtevent0
is still buggy (and actually the bug was in samba anyway).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Version tracking fixes

[Debian Bug Tracking System]

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

> found 733239 1.20131021-1
Bug #733239 [dh-python] dh-python: there is no script in the new version of the 
package - giving up-Jessie
Marked as found in versions dh-python/1.20131021-1.
> notfound 797038 llvm-defaults/0.25
Bug #797038 {Done: Sylvestre Ledru } [clang] clang: needs 
to know about C++11 ABI tag
Bug #797917 {Done: Sylvestre Ledru } [clang] clang should 
use the new CXX11_ABI
No longer marked as found in versions llvm-defaults/0.25.
No longer marked as found in versions llvm-defaults/0.25.
> thanks
Stopping processing here.

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

Bug#834669: marked as done (djangorestframework-gis: FTBFS in testing (failing tests))

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2016 12:22:26 +
with message-id 
and subject line Bug#834669: fixed in djangorestframework-gis 0.10.1-2
has caused the Debian Bug report #834669,
regarding djangorestframework-gis: FTBFS in testing (failing tests)
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.)


-- 
834669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:djangorestframework-gis
Version: 0.10.1-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py

[... snipped ...]

  File "/usr/lib/python2.7/dist-packages/django/urls/resolvers.py", line 343, 
in _reverse_with_prefix
possibilities = self.reverse_dict.getlist(lookup_view)
  File "/usr/lib/python2.7/dist-packages/django/urls/resolvers.py", line 240, 
in reverse_dict
return self._reverse_dict[language_code]
KeyError: 'en-gb'

==
ERROR: test_inBBOXFilter_filtering 
(django_restframework_gis_tests.test_filters.TestRestFrameworkGisFilters)
--
Traceback (most recent call last):
  File "tests/django_restframework_gis_tests/test_filters.py", line 21, in setUp
self.location_contained_in_bbox_list_url = 
reverse('api_geojson_location_list_contained_in_bbox_filter')
  File "/usr/lib/python2.7/dist-packages/django/urls/base.py", line 91, in 
reverse
return force_text(iri_to_uri(resolver._reverse_with_prefix(view, prefix, 
*args, **kwargs)))
  File "/usr/lib/python2.7/dist-packages/django/urls/resolvers.py", line 343, 
in _reverse_with_prefix
possibilities = self.reverse_dict.getlist(lookup_view)
  File "/usr/lib/python2.7/dist-packages/django/urls/resolvers.py", line 240, 
in reverse_dict
return self._reverse_dict[language_code]
KeyError: 'en-gb'

==
ERROR: test_inBBOXFilter_filtering_none 
(django_restframework_gis_tests.test_filters.TestRestFrameworkGisFilters)
--
Traceback (most recent call last):
  File "tests/django_restframework_gis_tests/test_filters.py", line 21, in setUp
self.location_contained_in_bbox_list_url = 
reverse('api_geojson_location_list_contained_in_bbox_filter')
  File "/usr/lib/python2.7/dist-packages/django/urls/base.py", line 91, in 
reverse
return force_text(iri_to_uri(resolver._reverse_with_prefix(view, prefix, 
*args, **kwargs)))
  File "/usr/lib/python2.7/dist-packages/django/urls/resolvers.py", line 343, 
in _reverse_with_prefix
possibilities = self.reverse_dict.getlist(lookup_view)
  File "/usr/lib/python2.7/dist-packages/django/urls/resolvers.py", line 240, 
in reverse_dict
return self._reverse_dict[language_code]
KeyError: 'en-gb'

--
Ran 54 tests in 0.011s

FAILED (errors=51, skipped=3)
Creating test database for alias 'default'...
Destroying test database for alias 'default'...
E: pybuild pybuild:274: test: plugin custom failed with: exit code=1: python2.7 
./runtests.py
dh_auto_test: pybuild --test -i python{version} -p 2.7 --system=custom 
--test-args={interpreter} ./runtests.py returned exit code 13
debian/rules:12: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:9: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is 

Bug#738295: marked as done (guile-1.8-non-dfsg: FTBFS: ./gh.texi:1000: must be after '@deftypefun' to use '@deftypefunx')

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2016 15:14:42 +0300
with message-id <20161017121442.v6xe7odg2agsi...@bunk.spdns.de>
and subject line guile-1.8-non-dfsg is no longer in unstable
has caused the Debian Bug report #738295,
regarding guile-1.8-non-dfsg: FTBFS: ./gh.texi:1000: must be after 
'@deftypefun' to use '@deftypefunx'
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.)


-- 
738295: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: guile-1.8-non-dfsg
Version: 1.8.8+1-1.1
Severity: serious
Tags: patch

Hi there,

Your package guile-1.8-non-dfsg fails to build in current unstable on amd64.

(Hopefully) Relevant part of the log: 
--

make[1]: Entering directory `/«BUILDDIR»/guile-1.8-non-dfsg-1.8.8+1'
Making all in doc
make[2]: Entering directory `/«BUILDDIR»/guile-1.8-non-dfsg-1.8.8+1/doc'
Making all in ref
make[3]: Entering directory `/«BUILDDIR»/guile-1.8-non-dfsg-1.8.8+1/doc/ref'
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
rm -rf $backupdir && mkdir $backupdir && \
if (/bin/bash /«BUILDDIR»/guile-1.8-non-dfsg-1.8.8+1/missing makeinfo 
--version) >/dev/null 2>&1; then \
  for f in guile-1.8.info guile-1.8.info-[0-9] 
guile-1.8.info-[0-9][0-9] guile-1.8.i[0-9] guile-1.8.i[0-9][0-9]; do \
if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
  done; \
else :; fi && \
cd "$am__cwd"; \
if /bin/bash /«BUILDDIR»/guile-1.8-non-dfsg-1.8.8+1/missing makeinfo   
-I . \
 -o guile-1.8.info guile-1.8.texi; \
then \
  rc=0; \
  CDPATH="${ZSH_VERSION+.}:" && cd .; \
else \
  rc=$?; \
  CDPATH="${ZSH_VERSION+.}:" && cd . && \
  $restore $backupdir/* `echo "./guile-1.8.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
./gh.texi:1000: must be after `@deftypefun' to use `@deftypefunx'
./fdl.texi:411: raising the section level of @appendixsubsec which is too low
./api-utility.texi:566: warning: node `C Hooks' is next for `Hook Reference' in 
menu but not in sectioning
./api-utility.texi:674: warning: node `Hook Reference' is prev for `C Hooks' in 
menu but not in sectioning
./api-options.texi:510: warning: node next `Printing options' in menu `Debugger 
options' and in sectioning `Evaluator options' differ
./api-options.texi:533: warning: node prev `Evaluator options' in menu 
`Debugger options' and in sectioning `Printing options' differ
./api-options.texi:544: warning: node next `Evaluator trap options' in menu 
`Examples of option use' and in sectioning `Debugger options' differ
./api-options.texi:625: warning: node next `Debugger options' in menu 
`Evaluator options' and in sectioning `Examples of option use' differ
./api-options.texi:625: warning: node prev `Debugger options' in menu `Printing 
options' and in sectioning `Evaluator trap options' differ
./api-options.texi:681: warning: node prev `Examples of option use' in menu 
`Evaluator trap options' and in sectioning `Debugger options' differ
make[3]: *** [guile-1.8.info] Error 1
make[3]: Leaving directory `/«BUILDDIR»/guile-1.8-non-dfsg-1.8.8+1/doc/ref'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/«BUILDDIR»/guile-1.8-non-dfsg-1.8.8+1/doc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/«BUILDDIR»/guile-1.8-non-dfsg-1.8.8+1'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Build finished at 20140209-0047

Finished


E: Build failure (dpkg-buildpackage died)

A full buildlog is available at 
http://www.warperbbs.de/stuff/buildlogs/guile-1.8-non-dfsg_1.8.8+1-1.1_amd64.build

I'm attaching a slightly modified patch from gentoo, 
https://bugs.gentoo.org/show_bug.cgi?id=464044#c8

Thanks for your time!

Regards,
  Andreas

-- 
PGP-encrypted mails preferred
PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624
--- guile-1.8-non-dfsg-1.8.8+1.orig/doc/goops/goops.texi
+++ guile-1.8-non-dfsg-1.8.8+1/doc/goops/goops.texi
@@ -131,7 +131,7 @@ info (goops.info) and texinfo format.
 @end menu
 
 @node Running GOOPS, Methods, Getting Started, Getting Started
-@subsection Running GOOPS
+@section Running GOOPS
 
 @enumerate
 @item
--- guile-1.8-non-dfsg-1.8.8+1.orig/doc/ref/api-options.texi
+++ 

Bug#840165: fcl bug

[Jose Luis Rivero]

On 17/10/16 19:17, Jochen Sprickerhof wrote:
> * Leopold Palomo-Avellaneda  [2016-10-17 11:31]:
>> Please Jochen, could you upload it?
> 
> Will do later.
> 
> @Jose: Can you comment why you added it in
> 
> https://anonscm.debian.org/cgit/debian-science/packages/fcl.git/commit/?id=2b59789404c96e4fbc6877ef2db0adccbeb8d97b
> 

I remember to see the option while working on enabling the octomap
support and enable expecting the build system to do what the option says
(strictly enabling SSE). I did not look into the implementation sorry.

+1 on removing it.

-- 
Jose Luis Rivero 



signature.asc
Description: OpenPGP digital signature

Bug#704620: fixed in gtkglext 1.2.0-3.1

[Guillaume Chazarain]

https://packages.debian.org/testing/gliv depends on
https://packages.debian.org/testing/libgtkglext1 which depends on
https://packages.debian.org/testing/libpangox-1.0-0

This has been fixed in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709554#57.

Bug#841057: marked as done (epiphany-browser: does not retrieve saved username/passwords)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2016 13:04:32 +0200
with message-id <1476702272.5756.1.ca...@gmail.com>
and subject line Re: Bug#841057: Info received (Bug#841057: Acknowledgement 
(epiphany-browser: does not retrieve saved username/passwords))
has caused the Debian Bug report #841057,
regarding epiphany-browser: does not retrieve saved username/passwords
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.)


-- 
841057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: epiphany-browser
Version: 3.22.1-1
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

   * What led up to the situation?

  Open a webpage for which you have previously saved a user/password pair 
and set the cursor on the username field

   * What was the outcome of this action?

 Epiphany is not showing the popup on the user field with the available 
usernames. It is not obviously also autocompleting the password field.


   * What outcome did you expect instead?

 The browser should show a popup with the different usernames saved for 
that hostname. Upon selecting one, it should autocomplete the password field.


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

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

Versions of packages epiphany-browser depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.10.10-1
ii  dbus-x11 [dbus-session-bus]   1.10.12-1
ii  epiphany-browser-data 3.22.0-1
ii  gsettings-desktop-schemas 3.22.0-1
ii  iso-codes 3.67-1
ii  libavahi-client3  0.6.32-1
ii  libavahi-common3  0.6.32-1
ii  libavahi-gobject0 0.6.32-1
ii  libc6 2.23-5
ii  libcairo2 1.14.6-1+b1
ii  libgcr-base-3-1   3.20.0-2
ii  libgcr-ui-3-1 3.20.0-2
ii  libgdk-pixbuf2.0-02.35.5-1
ii  libglib2.0-0  2.50.0-1
ii  libgnome-desktop-3-12 3.21.90-3
ii  libgtk-3-03.22.0-1
ii  libjavascriptcoregtk-4.0-18   2.14.1-1
ii  libnotify40.7.6-2
ii  libpango-1.0-01.40.2-1
ii  libpangocairo-1.0-0   1.40.2-1
ii  libsecret-1-0 0.18.5-2
ii  libsoup2.4-1  2.54.0.1-2
ii  libsqlite3-0  3.12.2-1
ii  libwebkit2gtk-4.0-37  2.14.1-1
ii  libx11-6  2:1.6.3-1
ii  libxml2   2.9.3+dfsg1-1
ii  libxslt1.11.1.29-1

Versions of packages epiphany-browser recommends:
ii  browser-plugin-evince  3.21.4-1
ii  ca-certificates20160104
ii  evince 3.22.0-1
ii  yelp   3.20.1-1

epiphany-browser suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Closing then--- End Message ---

Bug#841057: Acknowledgement (epiphany-browser: does not retrieve saved username/passwords)

[Sergio Villar Senin]

O Lun, 17-10-2016 ás 09:12 +, Debian Bug Tracking System escribiu:
> Thank you for filing a new Bug report with Debian.

I think we can safely close this. The bug is only affecting
accounts.google.com. They should have changed something on the server
side because the popup is shown for some other sites where I have
multiple identities registered.

BR

Bug#841050: [debian-mysql] Bug#841050: Security fixes from the October 2016 CPU

[Lars Tangvald]

As noted in the changelog for 5.5.53 at 
https://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-53.html,
MySQL 5.5.53 contains a change that requires packaging changes and could 
potentially impact users:


By default the server will restrict the server's access for SELECT INTO 
OUTFILE and LOAD DATA operations to /var/lib/mysql-files, and requires 
the directory to be present at startup.
This behavior can be changed at build-time to either turn such access 
off completely or make it unrestricted (current behavior).


We strongly recommend keeping the default behavior to improve the 
default security, i.e. change packaging to create the mysql-files 
directory. We're not aware of any other packages that rely on this 
functionality, but there is a risk of this change disrupting user workflows.


--
Lars

On 10/17/2016 10:05 AM, Norvald H. Ryeng wrote:

Source: mysql-5.5
Version: 5.5.52-0+deb8u1
Severity: grave
Tags: security upstream fixed-upstream

The Oracle Critical Patch Update for October 2016 will be released on 
Tuesday, October 18. According to the pre-release announcement [1], it 
will contain information about CVEs fixed in MySQL 5.5.53.


The CVE numbers will be available when the CPU is released.

Regards,

Norvald H. Ryeng

[1] 
http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html


___
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

Bug#837883: marked as done (mysql-server-5.7: Please upgrade to 5.7.15+ to fix recently discovered security issues)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2016 10:37:24 +
with message-id 
and subject line Bug#837883: fixed in mysql-5.7 5.7.15-1
has caused the Debian Bug report #837883,
regarding mysql-server-5.7: Please upgrade to 5.7.15+ to fix recently 
discovered security issues
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.)


-- 
837883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mysql-server-5.7
Version: 5.7.13-1~exp1
Severity: grave
Tags: upstream security
Justification: user security hole

CVE-2016-6662

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

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

Versions of packages mysql-server-5.7 depends on:
ii  adduser3.115
ii  bsdutils   1:2.28.2-1
ii  debconf [debconf-2.0]  1.5.59
ii  init-system-helpers1.44
ii  libc6  2.24-2
ii  libgcc11:6.2.0-3
ii  libmecab2  0.996-2
ii  libstdc++6 6.2.0-3
ii  lsb-base   9.20160629
ii  mysql-client-5.7   5.7.13-1~exp1
ii  mysql-common   5.8+1.0.0
ii  mysql-server-core-5.7  5.7.13-1~exp1
ii  passwd 1:4.2-3.1
ii  perl   5.22.2-5
ii  psmisc 22.21-2.1+b1
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages mysql-server-5.7 recommends:
ii  libhtml-template-perl  2.95-2

Versions of packages mysql-server-5.7 suggests:
ii  bsd-mailx [mailx]  8.1.2-0.20160123cvs-3
ii  s-nail [mailx] 14.8.10-1
pn  tinyca 

-- debconf information:
  mysql-server-5.7/postrm_remove_databases: false
  mysql-server-5.7/start_on_boot: true
  mysql-server/no_upgrade_when_using_ndb:
  mysql-server-5.7/nis_warning:
  mysql-server-5.7/really_downgrade: false
  mysql-server/password_mismatch:
--- End Message ---
--- Begin Message ---
Source: mysql-5.7
Source-Version: 5.7.15-1

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

Debian distribution maintenance software
pp.
Lars Tangvald  (supplier of updated mysql-5.7 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Oct 2016 13:10:56 +0200
Source: mysql-5.7
Binary: libmysqlclient20 libmysqld-dev libmysqlclient-dev mysql-client-core-5.7 
mysql-client-5.7 mysql-server-core-5.7 mysql-server-5.7 mysql-server 
mysql-client mysql-testsuite mysql-testsuite-5.7 mysql-source-5.7
Architecture: source amd64 all
Version: 5.7.15-1
Distribution: unstable
Urgency: medium
Maintainer: Robie Basak 
Changed-By: Lars Tangvald 
Description:
 libmysqlclient-dev - MySQL database development files
 libmysqlclient20 - MySQL database client library
 libmysqld-dev - MySQL embedded database development files
 mysql-client - MySQL database client (metapackage depending on the latest 
versio
 mysql-client-5.7 - MySQL database client binaries
 mysql-client-core-5.7 - MySQL database core client binaries
 mysql-server - MySQL database server (metapackage depending on the latest 
versio
 mysql-server-5.7 - MySQL database server binaries and system database setup
 mysql-server-core-5.7 - MySQL database server binaries
 mysql-source-5.7 - MySQL source
 mysql-testsuite - MySQL regression tests
 mysql-testsuite-5.7 - MySQL 5.7 testsuite
Closes: 837883
Changes:
 mysql-5.7 (5.7.15-1) unstable; urgency=medium
 .
   [ Bjoern Boschman ]
   * New upstream release to fix security issues
 - CVE-2016-6662
 (Closes: #837883)
   * Removed patches that have been included upstream
 .
   [ Dieter Adriaenssens ]
   * Add DEP-12 formatted upstream metadata file
   * d/control: Fix git url typo
 .
   [ Lars Tangvald ]
   * Add working dir to perl lib path for 

Bug#841049: [debian-mysql] Bug#841049: Security fixes from the October 2016 CPU

[Lars Tangvald]

As noted in the changelog for 5.6.34 at 
https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-34.html,
5.6.34 contains a change that requires packaging changes and could 
potentially impact users:


By default the server will restrict the server's access for SELECT INTO 
OUTFILE and LOAD DATA operations to /var/lib/mysql-files, and requires 
the directory to be present at startup.
This behavior can be changed at build-time to either turn such access 
off completely or make it unrestricted (current behavior).


We strongly recommend keeping the default behavior to improve the 
default security, i.e. change packaging to create the mysql-files 
directory. We're not aware of any other packages that rely on this 
functionality, but there is a risk of this change disrupting user workflows.


--
Lars

On 10/17/2016 10:05 AM, Norvald H. Ryeng wrote:

Source: mysql-5.6
Version: 5.6.30-1
Severity: grave
Tags: security upstream fixed-upstream

The Oracle Critical Patch Update for October 2016 will be released on 
Tuesday, October 18. According to the pre-release announcement [1], it 
will contain information about CVEs fixed in MySQL 5.6.34.


The CVE numbers will be available when the CPU is released.

Regards,

Norvald H. Ryeng

[1] 
http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html


___
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

Bug#799843: googleearth-package: generated package depends on lsb-core which is not available on sid

[Graham Inggs]

Hi Alberto

Please confirm if this was fixed by the upload of lsb 9.20161016.

Regards
Graham

Processed: #840852 affects src:gnome-applets

[Debian Bug Tracking System]

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

> affects 840852 src:gnome-applets
Bug #840852 [libcpupower-dev] please make libcpupower-dev depend on 
libcpupower1 (= ${binary:Version})
Added indication that 840852 affects src:gnome-applets
> thanks
Stopping processing here.

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

Bug#840165: fcl bug

[Jochen Sprickerhof]

* Leopold Palomo-Avellaneda  [2016-10-17 11:31]:
> Please Jochen, could you upload it?

Will do later.

@Jose: Can you comment why you added it in

https://anonscm.debian.org/cgit/debian-science/packages/fcl.git/commit/?id=2b59789404c96e4fbc6877ef2db0adccbeb8d97b

Cheers Jochen


signature.asc
Description: PGP signature

Bug#837281: manila-ui: FTBFS: compressor.exceptions.OfflineGenerationError: No template loaders defined. You must set TEMPLATE_LOADERS in your settings or set 'loaders' in your TEMPLATES dictionary.

[Thomas Goirand]

Hi Andreas,

Indeed, the issue is in Horizon, which is fixed in unstable. I have
fixed the dependency of manila-ui already for this issue, but the
manila-ui package is still in Sid, not in Testing yet. Therefore,
closing the bug is the way to go, so that manila-ui from Unstable
migrates to Testing (as Horizon has already migrated to Testing).

Cheers,

Thomas Goirand (zigo)

Bug#841064: awscli: FTBFS: ImportError: No module named 's3transfer'

[Chris Lamb]

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

Dear Maintainer,

awscli fails to build from source in unstable/amd64:

  […]

  copying awscli/examples/cloudfront/list-invalidations.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/cloudfront
  copying awscli/examples/cloudfront/create-distribution.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/cloudfront
  copying awscli/examples/cloudfront/list-distributions.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/cloudfront
  copying awscli/examples/cloudfront/get-distribution.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/cloudfront
  copying awscli/examples/cloudfront/create-invalidation.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/cloudfront
  copying awscli/examples/cloudfront/get-distribution-config.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/cloudfront
  copying awscli/examples/cloudfront/update-distribution.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/cloudfront
  copying awscli/examples/cloudfront/get-invalidation.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/cloudfront
  creating 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/upload-part.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/head-bucket.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/get-bucket-lifecycle-configuration.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/list-object-versions.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/delete-bucket-tagging.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/delete-bucket-lifecycle.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/put-bucket-versioning.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/get-object.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/abort-multipart-upload.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/put-bucket-cors.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/get-bucket-policy.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/get-object-torrent.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/put-object-acl.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/put-bucket-lifecycle.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/delete-bucket-replication.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/delete-bucket-website.rst -> 
/home/lamby/temp/cdt.20161017115650.Yu8GfnJnzm.db.awscli/awscli-1.11.2/.pybuild/pythonX.Y_3.5/build/awscli/examples/s3api
  copying awscli/examples/s3api/list-parts.rst -> 

Bug#840165: fcl bug

[Leopold Palomo-Avellaneda]

I have deleted the hack to activate the SSE code. It seems that has no sense. 
Upstream clarifies in its CMakeLists: #always disable, for now.

It justs add -native as parameter to the compiler making it not generic. So 
it's better to disable.

Please Jochen, could you upload it?

Best regards,

Leopold
-- 
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

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

Bug#841057: epiphany-browser: does not retrieve saved username/passwords

[Sergio Villar Senin]

Package: epiphany-browser
Version: 3.22.1-1
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

   * What led up to the situation?

  Open a webpage for which you have previously saved a user/password pair 
and set the cursor on the username field

   * What was the outcome of this action?

 Epiphany is not showing the popup on the user field with the available 
usernames. It is not obviously also autocompleting the password field.


   * What outcome did you expect instead?

 The browser should show a popup with the different usernames saved for 
that hostname. Upon selecting one, it should autocomplete the password field.


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

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

Versions of packages epiphany-browser depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.10.10-1
ii  dbus-x11 [dbus-session-bus]   1.10.12-1
ii  epiphany-browser-data 3.22.0-1
ii  gsettings-desktop-schemas 3.22.0-1
ii  iso-codes 3.67-1
ii  libavahi-client3  0.6.32-1
ii  libavahi-common3  0.6.32-1
ii  libavahi-gobject0 0.6.32-1
ii  libc6 2.23-5
ii  libcairo2 1.14.6-1+b1
ii  libgcr-base-3-1   3.20.0-2
ii  libgcr-ui-3-1 3.20.0-2
ii  libgdk-pixbuf2.0-02.35.5-1
ii  libglib2.0-0  2.50.0-1
ii  libgnome-desktop-3-12 3.21.90-3
ii  libgtk-3-03.22.0-1
ii  libjavascriptcoregtk-4.0-18   2.14.1-1
ii  libnotify40.7.6-2
ii  libpango-1.0-01.40.2-1
ii  libpangocairo-1.0-0   1.40.2-1
ii  libsecret-1-0 0.18.5-2
ii  libsoup2.4-1  2.54.0.1-2
ii  libsqlite3-0  3.12.2-1
ii  libwebkit2gtk-4.0-37  2.14.1-1
ii  libx11-6  2:1.6.3-1
ii  libxml2   2.9.3+dfsg1-1
ii  libxslt1.11.1.29-1

Versions of packages epiphany-browser recommends:
ii  browser-plugin-evince  3.21.4-1
ii  ca-certificates20160104
ii  evince 3.22.0-1
ii  yelp   3.20.1-1

epiphany-browser suggests no packages.

-- no debconf information

Bug#841056: dvi2dvi: license requires package rename

[Jakub Wilk]

Source: dvi2dvi
Version: 2.0alpha-9.2
Severity: serious

debian/copyright reads:
3. The package name of the modified software must not be ``dvi2dvi'' or 
``dvi2dvi-'' where  is the version number.


Debian did modify the software, but our package is still called "dvi2dvi", 
contrary to the license requirements.


--
Jakub Wilk

Processed: found 841050 in 5.5.42-1

[Debian Bug Tracking System]

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

> # for the BTS graph
> found 841050 5.5.42-1
Bug #841050 [src:mysql-5.5] Security fixes from the October 2016 CPU
Ignoring request to alter found versions of bug #841050 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: found 841050 in 5.5.42-1

[Debian Bug Tracking System]

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

> found 841050 5.5.42-1
Bug #841050 [src:mysql-5.5] Security fixes from the October 2016 CPU
Marked as found in versions mysql-5.5/5.5.42-1.
> thanks
Stopping processing here.

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

Bug#841049: Security fixes from the October 2016 CPU

[Norvald H. Ryeng]

Source: mysql-5.6
Version: 5.6.30-1
Severity: grave
Tags: security upstream fixed-upstream

The Oracle Critical Patch Update for October 2016 will be released on  
Tuesday, October 18. According to the pre-release announcement [1], it  
will contain information about CVEs fixed in MySQL 5.6.34.


The CVE numbers will be available when the CPU is released.

Regards,

Norvald H. Ryeng

[1]  
http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html

Bug#841050: Security fixes from the October 2016 CPU

[Norvald H. Ryeng]

Source: mysql-5.5
Version: 5.5.52-0+deb8u1
Severity: grave
Tags: security upstream fixed-upstream

The Oracle Critical Patch Update for October 2016 will be released on  
Tuesday, October 18. According to the pre-release announcement [1], it  
will contain information about CVEs fixed in MySQL 5.5.53.


The CVE numbers will be available when the CPU is released.

Regards,

Norvald H. Ryeng

[1]  
http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html

Bug#840677: marked as done (zeroc-icegridgui: fails to upgrade from 'testing' - trying to overwrite /usr/bin/icegridgui)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2016 10:30:43 +0200
with message-id 

and subject line Re: Bug#840677: zeroc-icegridgui: fails to upgrade from 
'testing' - trying to overwrite /usr/bin/icegridgui
has caused the Debian Bug report #840677,
regarding zeroc-icegridgui: fails to upgrade from 'testing' - trying to 
overwrite /usr/bin/icegridgui
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.)


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

Hi,

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

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

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

  Selecting previously unselected package zeroc-icegridgui.
  Preparing to unpack .../15-zeroc-icegridgui_3.6.3-1_all.deb ...
  Unpacking zeroc-icegridgui (3.6.3-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-7YiD10/15-zeroc-icegridgui_3.6.3-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/icegridgui', which is also in package 
zeroc-ice-utils-java 3.6.2-stretch-51-gba6baa6-2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-7YiD10/15-zeroc-icegridgui_3.6.3-1_all.deb


cheers,

Andreas


zeroc-ice-utils-java=3.6.2-stretch-51-gba6baa6-2_zeroc-icegridgui=3.6.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
zeroc-ice-utils-java was renamed zeroc-icegridgui in 3.6.3-1 and so the
file conflict.
I have fixed the packages to handle this and tested upgrade from stretch,
things
should work fine with 3.6.3-2.

Cheers,
José

On Thu, Oct 13, 2016 at 9:05 PM, Andreas Beckmann  wrote:

> Package: zeroc-icegridgui
> Version: 3.6.3-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.
> It installed fine in 'testing', then the upgrade to 'sid' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
>
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
>
> >From the attached log (scroll to the bottom...):
>
>   Selecting previously unselected package zeroc-icegridgui.
>   Preparing to unpack .../15-zeroc-icegridgui_3.6.3-1_all.deb ...
>   Unpacking zeroc-icegridgui (3.6.3-1) ...
>   dpkg: error processing archive /tmp/apt-dpkg-install-7YiD10/
> 15-zeroc-icegridgui_3.6.3-1_all.deb (--unpack):
>trying to overwrite '/usr/bin/icegridgui', which is also in package
> zeroc-ice-utils-java 3.6.2-stretch-51-gba6baa6-2
>   dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
>   Errors were encountered while processing:
>/tmp/apt-dpkg-install-7YiD10/15-zeroc-icegridgui_3.6.3-1_all.deb
>
>
> cheers,
>
> Andreas
>
--- End Message ---

Processed: Add tag to bug 840177

[Debian Bug Tracking System]

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

> tags 840177 + patch
Bug #840177 [src:qconf] qconf: FTBFS: mkdir: cannot create directory 
'/usr/share/qconf/': Permission denied
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#840177: Set INSTALL_ROOT to fix issue

[Jan Niehusmann]

It seems like dh_auto_install used to set INSTALL_ROOT (works in
jessie), but now it doesn't, so the build fails in sid.

But it's easy to set INSTALL_ROOT, manually. Just add it to the call of
dh_auto_install in debian/rules:

--- a/debian/rules
+++ b/debian/rules
@@ -22,7 +22,7 @@ override_dh_auto_configure:
./configure --prefix=/usr
 
 override_dh_auto_install:
-   dh_auto_install
+   dh_auto_install -- INSTALL_ROOT=$(CURDIR)/debian/qconf
mv debian/qconf/usr/bin/qconf debian/qconf/usr/bin/qt-qconf


As qconf packaging is managed in git at github, I sent a pull request:
https://github.com/tehnick/qconf-debian/pull/1

Processed: severity normal

[Debian Bug Tracking System]

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

> severity 840736 normal
Bug #840736 [gnome-maps] gnome-maps: always offline cant browse any map
Severity set to 'normal' from 'grave'
> tags 840736 + unreproducible moreinfo
Bug #840736 [gnome-maps] gnome-maps: always offline cant browse any map
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Processed: tags

[Debian Bug Tracking System]

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

> tags 789885 +pending
Bug #789885 [mylvmbackup] mylvmbackup: Missing dependency on 
libfile-copy-recursive-perl
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#840853: FTBFS on amd64 - recipe for target 'quickcheck' failed

[Hilko Bengen]

The libguestfs-test-tool run ends with a timeout ("Alarm clock") after
qemu has complained about two missing files:

,
| [02004ms] /usr/bin/qemu-system-x86_64 \
| -global virtio-blk-pci.scsi=off \
| -nodefconfig \
| -enable-fips \
| -nodefaults \
| -display none \
| -machine accel=kvm:tcg \
| -cpu host \
| -m 500 \
| -no-reboot \
| -rtc driftfix=slew \
| -no-hpet \
| -global kvm-pit.lost_tick_policy=discard \
| -kernel /var/tmp/.guestfs-1000/appliance.d/kernel \
| -initrd /var/tmp/.guestfs-1000/appliance.d/initrd \
| -device virtio-scsi-pci,id=scsi \
| -drive 
file=/tmp/libguestfs52T0nj/scratch.1,cache=unsafe,format=raw,id=hd0,if=none \
| -device scsi-hd,drive=hd0 \
| -drive 
file=/var/tmp/.guestfs-1000/appliance.d/root,snapshot=on,id=appliance,cache=unsafe,if=none,format=raw
 \
| -device scsi-hd,drive=appliance \
| -device virtio-serial-pci \
| -serial stdio \
| -device sga \
| -chardev socket,path=/tmp/libguestfs52T0nj/guestfsd.sock,id=channel0 \
| -device virtserialport,chardev=channel0,name=org.libguestfs.channel.0 \
| -append 'panic=1 console=ttyS0 udevtimeout=6000 udev.event-timeout=6000 
no_timer_check acpi=off printk.time=1 cgroup_disable=memory root=/dev/sdb 
selinux=0 guestfs_verbose=1 TERM=screen'
| Could not open option rom 'linuxboot_dma.bin': No such file or directory
| Could not open option rom 'sgabios.bin': No such file or directory
| Alarm clock
`

After one installs sgabios, we at least get an error message that looks
somewhat meaningful.

,
| ...
| -append 'panic=1 console=ttyS0 udevtimeout=6000 udev.event-timeout=6000 
no_timer_check acpi=off printk.time=1 cgroup_disable=memory root=/dev/sdb 
selinux=0 guestfs_verbose=1 TERM=screen'
| Could not open option rom 'linuxboot_dma.bin': No such file or directory
| \x1b[1;256r\x1b[256;256H\x1b[6n
| Google, Inc.
| Serial Graphics Adapter 12/07/13
| SGABIOS $Id: sgabios.S 8 2010-04-22 00:03:40Z nlaredo $ (mjt@gandalf) Sat Dec 
 7 15:39:53 UTC 2013
| Term: 80x24
| 4 0
| SeaBIOS (version Debian-1.8.2-1)
| Booting from Hard Disk...
| Boot failed: not a bootable disk
| 
| Booting from Floppy...
| Boot failed: could not read the boot disk
| 
| No bootable device.
| Alarm clock
`

Cheers,
-Hilko

Processed: notfixed 837532 in mpqc3/0.0~git20160216-5

[Debian Bug Tracking System]

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

> notfixed 837532 mpqc3/0.0~git20160216-5
Bug #837532 {Done: Michael Banck } [src:libint2] mpqc3: FTBFS 
(Libint library is too old: a recent beta of 2.1.0 is required)
Bug #839361 {Done: Michael Banck } [src:libint2] mpqc3: 
FTBFS: Libint library is too old: a recent beta of 2.1.0 is required
The source mpqc3 and version 0.0~git20160216-5 do not appear to match any 
binary packages
Ignoring request to alter fixed versions of bug #837532 to the same values 
previously set
Ignoring request to alter fixed versions of bug #839361 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: notfixed 839361 in mpqc3/0.0~git20160216-5

[Debian Bug Tracking System]

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

> notfixed 839361 mpqc3/0.0~git20160216-5
Bug #839361 {Done: Michael Banck } [src:libint2] mpqc3: 
FTBFS: Libint library is too old: a recent beta of 2.1.0 is required
Bug #837532 {Done: Michael Banck } [src:libint2] mpqc3: FTBFS 
(Libint library is too old: a recent beta of 2.1.0 is required)
The source mpqc3 and version 0.0~git20160216-5 do not appear to match any 
binary packages
No longer marked as fixed in versions mpqc3/0.0~git20160216-5.
No longer marked as fixed in versions mpqc3/0.0~git20160216-5.
> thanks
Stopping processing here.

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

Processed: fixed 839361 in libint2/2.1.0-3

[Debian Bug Tracking System]

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

> fixed 839361 libint2/2.1.0-3
Bug #839361 {Done: Michael Banck } [src:libint2] mpqc3: 
FTBFS: Libint library is too old: a recent beta of 2.1.0 is required
Bug #837532 {Done: Michael Banck } [src:libint2] mpqc3: FTBFS 
(Libint library is too old: a recent beta of 2.1.0 is required)
Marked as fixed in versions libint2/2.1.0-3; no longer marked as fixed in 
versions libint2/2.1.0-3.
Marked as fixed in versions libint2/2.1.0-3; no longer marked as fixed in 
versions libint2/2.1.0-3.
> thanks
Stopping processing here.

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

Processed: fixed 837532 in libint2/2.1.0-3

[Debian Bug Tracking System]

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

> fixed 837532 libint2/2.1.0-3
Bug #837532 {Done: Michael Banck } [src:libint2] mpqc3: FTBFS 
(Libint library is too old: a recent beta of 2.1.0 is required)
Bug #839361 {Done: Michael Banck } [src:libint2] mpqc3: 
FTBFS: Libint library is too old: a recent beta of 2.1.0 is required
Marked as fixed in versions libint2/2.1.0-3.
Marked as fixed in versions libint2/2.1.0-3.
> thanks
Stopping processing here.

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

Processed: notfound 839361 in libint2/2.1.0-3

[Debian Bug Tracking System]

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

> notfound 839361 libint2/2.1.0-3
Bug #839361 {Done: Michael Banck } [src:libint2] mpqc3: 
FTBFS: Libint library is too old: a recent beta of 2.1.0 is required
Bug #837532 {Done: Michael Banck } [src:libint2] mpqc3: FTBFS 
(Libint library is too old: a recent beta of 2.1.0 is required)
Ignoring request to alter found versions of bug #839361 to the same values 
previously set
Ignoring request to alter found versions of bug #837532 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: notfound 837532 in libint2/2.1.0-3

[Debian Bug Tracking System]

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

> notfound 837532 libint2/2.1.0-3
Bug #837532 {Done: Michael Banck } [src:libint2] mpqc3: FTBFS 
(Libint library is too old: a recent beta of 2.1.0 is required)
Bug #839361 {Done: Michael Banck } [src:libint2] mpqc3: 
FTBFS: Libint library is too old: a recent beta of 2.1.0 is required
Ignoring request to alter found versions of bug #837532 to the same values 
previously set
Ignoring request to alter found versions of bug #839361 to the same values 
previously set
> thanks
Stopping processing here.

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