Bug#777791: [PATCH] ball: ftbfs with GCC-5

[Andreas Tille]

Hi Danni,

On Tue, May 10, 2016 at 07:13:28PM +0200, Andreas Tille wrote:
> > 
> > I then rebuilt the package on a fresh sid cowbuilder, but now there's a
> > new problem (see attachment for the exact error message) near the end of
> > the build, involving a static_cast.

I can confirm that the current Git repository builds for me.

> Thanks a lot.  Your work is really appreciated.  Please also be bold and
> commit to master.  I have no time to look the next 2-3 days - but I'd
> like to see the changes in master since I see no point in deriving for
> this package what we are doing anywhere else.

Could you please add your changes to debian/changelog?  If you use

dch

it injects a separate section for your ID.

Thanks a lot for your work on this which is really appreciated

  Andreas.

-- 
http://fam-tille.de

Bug#812948: libbson-doc: contains manpages with generic names: index(3), installing(3)

[Ralf Treinen]

Hi,

libbson-doc also ships

  /usr/share/man/man3/clock.3.gz

which also exists in manpages-dev. -Ralf.

Bug#824628: golang-metrics-dev and golang-github-rcrowley-go-metrics-dev: error when trying to install together

[Ralf Treinen]

Package: golang-github-rcrowley-go-metrics-dev,golang-metrics-dev
Version: golang-github-rcrowley-go-metrics-dev/0.0~git20160226.0.eeba7bd-1
Version: golang-metrics-dev/0.0~git20150823-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-05-18
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Selecting previously unselected package bzip2.
(Reading database ... 10961 files and directories currently installed.)
Preparing to unpack .../bzip2_1.0.6-8_amd64.deb ...
Unpacking bzip2 (1.0.6-8) ...
Selecting previously unselected package xz-utils.
Preparing to unpack .../xz-utils_5.1.1alpha+20120614-2.1_amd64.deb ...
Unpacking xz-utils (5.1.1alpha+20120614-2.1) ...
Selecting previously unselected package binutils.
Preparing to unpack .../binutils_2.26-9_amd64.deb ...
Unpacking binutils (2.26-9) ...
Selecting previously unselected package libdpkg-perl.
Preparing to unpack .../libdpkg-perl_1.18.7_all.deb ...
Unpacking libdpkg-perl (1.18.7) ...
Selecting previously unselected package patch.
Preparing to unpack .../patch_2.7.5-1_amd64.deb ...
Unpacking patch (2.7.5-1) ...
Selecting previously unselected package make.
Preparing to unpack .../archives/make_4.1-9_amd64.deb ...
Unpacking make (4.1-9) ...
Selecting previously unselected package dpkg-dev.
Preparing to unpack .../dpkg-dev_1.18.7_all.deb ...
Unpacking dpkg-dev (1.18.7) ...
Selecting previously unselected package golang-src.
Preparing to unpack .../golang-src_2%3a1.6.1-2_amd64.deb ...
Unpacking golang-src (2:1.6.1-2) ...
Selecting previously unselected package golang-go.
Preparing to unpack .../golang-go_2%3a1.6.1-2_amd64.deb ...
Unpacking golang-go (2:1.6.1-2) ...
Selecting previously unselected package golang-github-stathat-go-dev.
Preparing to unpack 
.../golang-github-stathat-go-dev_0.0~git20130314.0.01d012b-1_all.deb ...
Unpacking golang-github-stathat-go-dev (0.0~git20130314.0.01d012b-1) ...
Selecting previously unselected package golang-github-rcrowley-go-metrics-dev.
Preparing to unpack 
.../golang-github-rcrowley-go-metrics-dev_0.0~git20160226.0.eeba7bd-1_all.deb 
...
Unpacking golang-github-rcrowley-go-metrics-dev (0.0~git20160226.0.eeba7bd-1) 
...
Selecting previously unselected package golang-metrics-dev.
Preparing to unpack .../golang-metrics-dev_0.0~git20150823-1_all.deb ...
Unpacking golang-metrics-dev (0.0~git20150823-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/golang-metrics-dev_0.0~git20150823-1_all.deb (--unpack):
 trying to overwrite 
'/usr/share/gocode/src/github.com/rcrowley/go-metrics/sample_test.go', which is 
also in package golang-github-rcrowley-go-metrics-dev 
0.0~git20160226.0.eeba7bd-1
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/golang-metrics-dev_0.0~git20150823-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  
/usr/share/gocode/src/github.com/rcrowley/go-metrics/cmd/metrics-bench/metrics-bench.go
  
/usr/share/gocode/src/github.com/rcrowley/go-metrics/cmd/metrics-example/metrics-example.go
  
/usr/share/gocode/src/github.com/rcrowley/go-metrics/cmd/never-read/never-read.go
  /usr/share/gocode/src/github.com/rcrowley/go-metrics/counter.go
  /usr/share/gocode/src/github.com/rcrowley/go-metrics/counter_test.go
  /usr/share/gocode/src/github.com/rcrowley/go-metrics/debug.go
  /usr/share/gocode/src/github.com/rcrowley/go-metrics/debug_test.go
  /usr/share/gocode/src/github.com/rcrowley/go-metrics/ewma.go
  /usr/share/gocode/src/github.com/rcrowley/go-metrics/ewma_test.go
  /usr/share/gocode/src/github.com/rcrowley/go-metrics/gauge.go
  /usr/share/gocode/src/github.com/rcrowley/go-metrics/gauge_float64.go
  /usr/share/gocode/src/github.com/rcrowley/go-metrics/gauge_float64_test.go
  /usr/share/gocode/src/github.com/rcrowley/go-metrics/gauge_test.go
  /usr/share/gocode/src/github.com/rcrowley/go-metrics/graphite.go
  /usr/share/gocode/src/github.com/rcrowley/go-metrics/graphite_test.go
  /usr/share/gocode/src/github.com/rcrowley/go-metrics/healthcheck.go
  /usr/share/g

Processed: reassign 824623 to cdbs, found 824623 in 0.4.133, affects 824623

[Debian Bug Tracking System]

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

> reassign 824623 cdbs
Bug #824623 {Done: Simon McVittie } [src:glib2.0] glib2.0 
FTBFS: dh_install: libglib2.0-tests missing files: 
usr/lib/glib2.0/installed-tests
Bug reassigned from package 'src:glib2.0' to 'cdbs'.
No longer marked as found in versions glib2.0/2.48.1-1.
No longer marked as fixed in versions cdbs/0.4.135.
> found 824623 0.4.133
Bug #824623 {Done: Simon McVittie } [cdbs] glib2.0 FTBFS: 
dh_install: libglib2.0-tests missing files: usr/lib/glib2.0/installed-tests
Marked as found in versions cdbs/0.4.133 and reopened.
> affects 824623 glib2.0
Bug #824623 [cdbs] glib2.0 FTBFS: dh_install: libglib2.0-tests missing files: 
usr/lib/glib2.0/installed-tests
Added indication that 824623 affects glib2.0
> thanks
Stopping processing here.

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

Bug#824623: marked as done (glib2.0 FTBFS: dh_install: libglib2.0-tests missing files: usr/lib/glib2.0/installed-tests)

[Debian Bug Tracking System]

Your message dated Wed, 18 May 2016 07:20:22 +0100
with message-id <20160518062022.ga12...@perpetual.pseudorandom.co.uk>
and subject line Re: Bug#824623: glib2.0 FTBFS: dh_install: libglib2.0-tests 
missing files: usr/lib/glib2.0/installed-tests
has caused the Debian Bug report #824623,
regarding glib2.0 FTBFS: dh_install: libglib2.0-tests missing files: 
usr/lib/glib2.0/installed-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.)


-- 
824623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glib2.0
Version: 2.48.1-1
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

Hi,

glib2.0 FTBFS again. A few days ago, cdbs was responsible (#824083) for
that. Now I cannot tell, but I wouldn't rule that out either and
therefore put Jonas into Cc. Either way, glib2.0 didn't change so the
cause is to be found in some other package. The earliest occurrence of
this issue (in a cross build setting) was observed at 2016-05-17 23:10
UTC. I am attaching a native build log for amd64. The relevant excerpt
is:

| dh_install -plibglib2.0-tests --sourcedir=debian/install/deb -X.la
| dh_install: Cannot find (any matches for) "usr/lib/glib2.0/installed-tests" 
(tried in "debian/install/deb" and "debian/tmp")
| dh_install: libglib2.0-tests missing files: usr/lib/glib2.0/installed-tests
| dh_install: missing files, aborting
| /usr/share/cdbs/1/rules/debhelper.mk:240: recipe for target 
'binary-install/libglib2.0-tests' failed
| make: *** [binary-install/libglib2.0-tests] Error 255
| dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit 
status 2

Those are actually installed as ".../usr/lib/glib2/installed-tests".

Hope this helps

Helmut


glib2.0_2.48.1-1_amd64-20160518-0557.build.xz
Description: application/xz
--- End Message ---
--- Begin Message ---
Package: cdbs
Version: 0.4.135
Control: reassign 824623 cdbs
Control: affects 824623 src:glib2.0
Control: found 824623 0.4.133

On Wed, 18 May 2016 at 06:21:15 +0200, Helmut Grohne wrote:
> glib2.0 FTBFS again. A few days ago, cdbs was responsible (#824083) for
> that. Now I cannot tell, but I wouldn't rule that out either and
> therefore put Jonas into Cc. Either way, glib2.0 didn't change so the
> cause is to be found in some other package.
...
> | dh_install: Cannot find (any matches for) "usr/lib/glib2.0/installed-tests" 
> (tried in "debian/install/deb" and "debian/tmp")
...
> Those are actually installed as ".../usr/lib/glib2/installed-tests".

The expectation is that they will be in ${libexecdir}/installed-tests, and
previously we had libexecdir=/usr/lib/${source_package}, i.e. glib2.0.

>From your build log:

--libexecdir="\${prefix}/lib/glib2"

This is not as expected.

glib2.0 doesn't explicitly specify libexecdir, so this must have come from
cdbs. autotools-vars.mk.in says:

DEB_CONFIGURE_LIBEXECDIR ?= "\$${prefix}/lib/$(DEB_SOURCE_PACKAGE)"

and

--libexecdir=$(DEB_CONFIGURE_LIBEXECDIR) \

>From the log, cdbs was version 0.4.133:

Get:59 http://proxy:/debian sid/main amd64 cdbs all 0.4.133 [79.4 kB]

It seems this is what was fixed in 0.4.135:

-DEB_SOURCE_PACKAGE := $(shell grep -Pom1 '^Source:\s*\K\w*' debian/control)
+DEB_SOURCE_PACKAGE := $(shell grep -Pom1 '^Source:\s*\K[^\s]*' 
debian/control)

as demonstrated by:

$ echo "Source: glib2.0" | grep -Pom1 '^Source:\s*\K\w*'
glib2
$ echo "Source: glib2.0" | grep -Pom1 '^Source:\s*\K[^\s]*'
glib2.0

(I'm not sure why cdbs doesn't use dpkg-parsechangelog here, like dpkg's
pkg-info.mk does.)

Regards,
S--- End Message ---

Bug#824623: glib2.0 FTBFS: dh_install: libglib2.0-tests missing files: usr/lib/glib2.0/installed-tests

[Helmut Grohne]

Source: glib2.0
Version: 2.48.1-1
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

Hi,

glib2.0 FTBFS again. A few days ago, cdbs was responsible (#824083) for
that. Now I cannot tell, but I wouldn't rule that out either and
therefore put Jonas into Cc. Either way, glib2.0 didn't change so the
cause is to be found in some other package. The earliest occurrence of
this issue (in a cross build setting) was observed at 2016-05-17 23:10
UTC. I am attaching a native build log for amd64. The relevant excerpt
is:

| dh_install -plibglib2.0-tests --sourcedir=debian/install/deb -X.la
| dh_install: Cannot find (any matches for) "usr/lib/glib2.0/installed-tests" 
(tried in "debian/install/deb" and "debian/tmp")
| dh_install: libglib2.0-tests missing files: usr/lib/glib2.0/installed-tests
| dh_install: missing files, aborting
| /usr/share/cdbs/1/rules/debhelper.mk:240: recipe for target 
'binary-install/libglib2.0-tests' failed
| make: *** [binary-install/libglib2.0-tests] Error 255
| dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit 
status 2

Those are actually installed as ".../usr/lib/glib2/installed-tests".

Hope this helps

Helmut


glib2.0_2.48.1-1_amd64-20160518-0557.build.xz
Description: application/xz

Processed: reassign 823962 to boxer-data, affects 823962

[Debian Bug Tracking System]

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

> reassign 823962 boxer-data 8
Bug #823962 [parl-desktop-strict] parl-desktop-strict: not installable in sid
Bug reassigned from package 'parl-desktop-strict' to 'boxer-data'.
No longer marked as found in versions debian-parl/1.9.2.
Ignoring request to alter fixed versions of bug #823962 to the same values 
previously set
Bug #823962 [boxer-data] parl-desktop-strict: not installable in sid
Marked as found in versions boxer-data/8.
> affects 823962 parl-desktop-strict
Bug #823962 [boxer-data] parl-desktop-strict: not installable in sid
Added indication that 823962 affects parl-desktop-strict
> thanks
Stopping processing here.

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

Bug#801046: git: "Out of memory, malloc failed" cloning certain repos

[PICCORO McKAY Lenz]

the problem its that versions in wheeze stable are not fixed!

what about it?

-- 
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com

Bug#824605: marked as done (kfreebsd-10: CVE-2016-1887: Incorrect argument handling in sendmsg(2))

[Debian Bug Tracking System]

Your message dated Wed, 18 May 2016 00:19:59 +
with message-id 
and subject line Bug#824605: fixed in kfreebsd-10 10.1~svn274115-4+kbsd8u4
has caused the Debian Bug report #824605,
regarding kfreebsd-10: CVE-2016-1887: Incorrect argument handling in sendmsg(2)
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.)


-- 
824605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kfreebsd-10
Version: 10.1~svn274115-4+kbsd8u3
Severity: grave
Tags: security

https://security.FreeBSD.org/advisories/FreeBSD-SA-16:19.sendmsg.asc

Incorrect argument handling in the socket code allows malicious local
user to overwrite large portion of the kernel memory.

This affects 10.1 in sid and jessie;  10.3 and 11.1 in experimental.
It was not reported to affect 9.0.

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

Kernel: kFreeBSD 10.1-0-amd64
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Source: kfreebsd-10
Source-Version: 10.1~svn274115-4+kbsd8u4

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

Debian distribution maintenance software
pp.
Steven Chamberlain  (supplier of updated kfreebsd-10 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 17 May 2016 22:44:13 +
Source: kfreebsd-10
Binary: kfreebsd-source-10.1 kfreebsd-headers-10.1-0 
kfreebsd-image-10.1-0-amd64 kfreebsd-image-10-amd64 
kfreebsd-headers-10.1-0-amd64 kfreebsd-headers-10-amd64 
kernel-image-10.1-0-amd64-di nic-modules-10.1-0-amd64-di 
nic-wireless-modules-10.1-0-amd64-di nic-shared-modules-10.1-0-amd64-di 
serial-modules-10.1-0-amd64-di usb-serial-modules-10.1-0-amd64-di 
ppp-modules-10.1-0-amd64-di cdrom-modules-10.1-0-amd64-di 
scsi-core-modules-10.1-0-amd64-di scsi-modules-10.1-0-amd64-di 
scsi-extra-modules-10.1-0-amd64-di plip-modules-10.1-0-amd64-di 
floppy-modules-10.1-0-amd64-di loop-modules-10.1-0-amd64-di 
ipv6-modules-10.1-0-amd64-di nls-core-modules-10.1-0-amd64-di 
ext2-modules-10.1-0-amd64-di isofs-modules-10.1-0-amd64-di 
reiserfs-modules-10.1-0-amd64-di fat-modules-10.1-0-amd64-di 
zfs-modules-10.1-0-amd64-di nfs-modules-10.1-0-amd64-di 
nullfs-modules-10.1-0-amd64-di md-modules-10.1-0-amd64-di 
parport-modules-10.1-0-amd64-di nic-usb-modules-10.1-0-amd64-di
 sata-modules-10.1-0-amd64-di acpi-modules-10.1-0-amd64-di 
i2c-modules-10.1-0-amd64-di crypto-modules-10.1-0-amd64-di 
crypto-dm-modules-10.1-0-amd64-di mmc-core-modules-10.1-0-amd64-di 
mmc-modules-10.1-0-amd64-di sound-modules-10.1-0-amd64-di 
zlib-modules-10.1-0-amd64-di kfreebsd-image-10.1-0-486 kfreebsd-image-10-486 
kfreebsd-headers-10.1-0-486 kfreebsd-headers-10-486 kfreebsd-image-10.1-0-686 
kfreebsd-image-10-686 kfreebsd-headers-10.1-0-686 kfreebsd-headers-10-686 
kfreebsd-image-10.1-0-xen kfreebsd-image-10-xen kfreebsd-headers-10.1-0-xen 
kfreebsd-headers-10-xen kernel-image-10.1-0-486-di nic-modules-10.1-0-486-di 
nic-wireless-modules-10.1-0-486-di nic-shared-modules-10.1-0-486-di 
serial-modules-10.1-0-486-di usb-serial-modules-10.1-0-486-di 
ppp-modules-10.1-0-486-di cdrom-modules-10.1-0-486-di 
scsi-core-modules-10.1-0-486-di scsi-modules-10.1-0-486-di 
scsi-extra-modules-10.1-0-486-di plip-modules-10.1-0-486-di 
floppy-modules-10.1-0-486-di
 loop-modules-10.1-0-486-di ipv6-modules-10.1-0-486-di 
nls-core-modules-10.1-0-486-di ext2-modules-10.1-0-486-di 
isofs-modules-10.1-0-486-di reiserfs-modules-10.1-0-486-di 
fat-modules-10.1-0-486-di zfs-modules-10.1-0-486-di nfs-modules-10.1-0-486-di 
nullfs-modules-10.1-0-486-di md-modules-10.1-0-486-di 
parport-modules-10.1-0-486-di nic-usb-modules-10.1-0-486-di 
sata-modules-10.1-0-486-di acpi-modules-10.1-0-486-di i2c-modules-10.1-0-486-di 
crypto-modules-10.1-0-486-di crypto-dm-modules-10.1-0-486-di 
mmc-core-modules-10.1-

Bug#821898: marked as done (opendkim: incompatible SSL versions)

[Debian Bug Tracking System]

Your message dated Wed, 18 May 2016 00:20:28 +
with message-id 
and subject line Bug#821898: fixed in opendkim 2.11.0~alpha-2
has caused the Debian Bug report #821898,
regarding opendkim: incompatible SSL versions
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.)


-- 
821898: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: opendkim
Version: 2.10.3-3+b1
Severity: grave
Justification: renders package unusable

During an upgrade:

[...]
update-initramfs: Generating /boot/initrd.img-4.2.0-1-amd64
Errors were encountered while processing:
 opendkim
==  How can you help?  (doc: https://wiki.debian.org/how-can-i-help ) ==

-  Show old opportunities as well as new ones: how-can-i-help --old  -
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up opendkim (2.10.3-3+b1) ...
Starting OpenDKIM: opendkim: incompatible SSL versions (library = 0x01000203f, 
filter = 01000204f)
invoke-rc.d: initscript opendkim, action "start" failed.
dpkg: error processing package opendkim (--configure):
 subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
 opendkim

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

Kernel: Linux 4.0.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages opendkim depends on:
ii  adduser  3.114
ii  dns-root-data2015052300+h+1
ii  init-system-helpers  1.29
ii  libbsd0  0.7.0-2
ii  libc62.22-7
ii  libdb5.3 5.3.28-11
ii  libldap-2.4-22.4.42+dfsg-2
ii  liblua5.1-0  5.1.5-8
ii  libmemcached11   1.0.18-4
ii  libmemcachedutil21.0.18-4
ii  libmilter1.0.1   8.14.9-4
ii  libopendbx1  1.4.6-9
ii  libopendkim102.10.3-3
ii  librbl1  2.10.3-3
ii  libssl1.0.2  1.0.2g-1
ii  libunbound2  1.4.22-3
ii  libvbr2  2.10.3-3
ii  lsb-base 9.20150917

opendkim recommends no packages.

Versions of packages opendkim suggests:
ii  opendkim-tools  2.10.3-3+b1
pn  unbound 

-- Configuration Files:
/etc/dkimkeys/README.PrivateKeys [Errno 13] Permission denied: 
u'/etc/dkimkeys/README.PrivateKeys'

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: opendkim
Source-Version: 2.11.0~alpha-2

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated opendkim 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, 17 May 2016 20:03:01 -0400
Source: opendkim
Binary: opendkim opendkim-tools libopendkim11 libopendkim-dev libvbr2 
libvbr-dev librbl1 librbl-dev
Architecture: source amd64
Version: 2.11.0~alpha-2
Distribution: experimental
Urgency: medium
Maintainer: Scott Kitterman 
Changed-By: Scott Kitterman 
Description:
 libopendkim-dev - Headers and development libraries for the OpenDKIM library
 libopendkim11 - Library for signing and verifying DomainKeys Identified Mail 
sign
 librbl-dev - Headers/development libraries for the OpenDKIM RBL library
 librbl1- Library to support a DKIM based RBL system
 libvbr-dev - Headers and development libraries for the OpenDKIM VBR library
 libvbr2- Library for RFC 5518 Vouch By Reference (VBR)
 opendkim   - Milter implementation of DomainKeys Identified Mail
 opendkim-tools - Set of command line tools for OpenDKIM
Closes: 821898
Changes:
 opendkim (2.11.0~alpha-2) experimental; urgency=medium
 .
   * Update debian/copyright to reflect change of copyright holder to The
 Trusted Domain Project
   * Update experimental to match changes in unstable (2.10.3-4)
 - Tighten opendkim depend version on 

Bug#824604: marked as done (kfreebsd-10: CVE-2016-1886: Buffer overflow in keyboard driver)

[Debian Bug Tracking System]

Your message dated Wed, 18 May 2016 00:19:59 +
with message-id 
and subject line Bug#824604: fixed in kfreebsd-10 10.1~svn274115-4+kbsd8u4
has caused the Debian Bug report #824604,
regarding kfreebsd-10: CVE-2016-1886: Buffer overflow in keyboard driver
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.)


-- 
824604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kfreebsd-10
Version: 10.1~svn274115-4+kbsd8u3
Severity: grave
Tags: security

https://security.FreeBSD.org/advisories/FreeBSD-SA-16:18.atkbd.asc

Incorrect signedness comparison in the ioctl(2) handler allows a
malicious local user to overwrite a portion of the kernel memory.

This affects 10.1 in sid and jessie;  9.0 in wheezy;
10.3 and 11.1 in experimental.

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

Kernel: kFreeBSD 10.1-0-amd64
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Source: kfreebsd-10
Source-Version: 10.1~svn274115-4+kbsd8u4

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

Debian distribution maintenance software
pp.
Steven Chamberlain  (supplier of updated kfreebsd-10 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 17 May 2016 22:44:13 +
Source: kfreebsd-10
Binary: kfreebsd-source-10.1 kfreebsd-headers-10.1-0 
kfreebsd-image-10.1-0-amd64 kfreebsd-image-10-amd64 
kfreebsd-headers-10.1-0-amd64 kfreebsd-headers-10-amd64 
kernel-image-10.1-0-amd64-di nic-modules-10.1-0-amd64-di 
nic-wireless-modules-10.1-0-amd64-di nic-shared-modules-10.1-0-amd64-di 
serial-modules-10.1-0-amd64-di usb-serial-modules-10.1-0-amd64-di 
ppp-modules-10.1-0-amd64-di cdrom-modules-10.1-0-amd64-di 
scsi-core-modules-10.1-0-amd64-di scsi-modules-10.1-0-amd64-di 
scsi-extra-modules-10.1-0-amd64-di plip-modules-10.1-0-amd64-di 
floppy-modules-10.1-0-amd64-di loop-modules-10.1-0-amd64-di 
ipv6-modules-10.1-0-amd64-di nls-core-modules-10.1-0-amd64-di 
ext2-modules-10.1-0-amd64-di isofs-modules-10.1-0-amd64-di 
reiserfs-modules-10.1-0-amd64-di fat-modules-10.1-0-amd64-di 
zfs-modules-10.1-0-amd64-di nfs-modules-10.1-0-amd64-di 
nullfs-modules-10.1-0-amd64-di md-modules-10.1-0-amd64-di 
parport-modules-10.1-0-amd64-di nic-usb-modules-10.1-0-amd64-di
 sata-modules-10.1-0-amd64-di acpi-modules-10.1-0-amd64-di 
i2c-modules-10.1-0-amd64-di crypto-modules-10.1-0-amd64-di 
crypto-dm-modules-10.1-0-amd64-di mmc-core-modules-10.1-0-amd64-di 
mmc-modules-10.1-0-amd64-di sound-modules-10.1-0-amd64-di 
zlib-modules-10.1-0-amd64-di kfreebsd-image-10.1-0-486 kfreebsd-image-10-486 
kfreebsd-headers-10.1-0-486 kfreebsd-headers-10-486 kfreebsd-image-10.1-0-686 
kfreebsd-image-10-686 kfreebsd-headers-10.1-0-686 kfreebsd-headers-10-686 
kfreebsd-image-10.1-0-xen kfreebsd-image-10-xen kfreebsd-headers-10.1-0-xen 
kfreebsd-headers-10-xen kernel-image-10.1-0-486-di nic-modules-10.1-0-486-di 
nic-wireless-modules-10.1-0-486-di nic-shared-modules-10.1-0-486-di 
serial-modules-10.1-0-486-di usb-serial-modules-10.1-0-486-di 
ppp-modules-10.1-0-486-di cdrom-modules-10.1-0-486-di 
scsi-core-modules-10.1-0-486-di scsi-modules-10.1-0-486-di 
scsi-extra-modules-10.1-0-486-di plip-modules-10.1-0-486-di 
floppy-modules-10.1-0-486-di
 loop-modules-10.1-0-486-di ipv6-modules-10.1-0-486-di 
nls-core-modules-10.1-0-486-di ext2-modules-10.1-0-486-di 
isofs-modules-10.1-0-486-di reiserfs-modules-10.1-0-486-di 
fat-modules-10.1-0-486-di zfs-modules-10.1-0-486-di nfs-modules-10.1-0-486-di 
nullfs-modules-10.1-0-486-di md-modules-10.1-0-486-di 
parport-modules-10.1-0-486-di nic-usb-modules-10.1-0-486-di 
sata-modules-10.1-0-486-di acpi-modules-10.1-0-486-di i2c-modules-10.1-0-486-di 
crypto-modules-10.1-0-486-di crypto-dm-modules-10.1-0-486-di 
mmc-core-modules-10.1-0-486-di mmc-modules-1

Bug#824585: marked as done (libgnomekbd: FTBFS: find: 'doc': No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 17 May 2016 23:49:25 +
with message-id 
and subject line Bug#824585: fixed in cdbs 0.4.134
has caused the Debian Bug report #824585,
regarding libgnomekbd: FTBFS: find: 'doc': No such file or directory
to be marked as done.

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

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


-- 
824585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgnomekbd
Version: 3.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,

libgnomekbd fails to build from source in unstable/amd64:

  [..]

  Preparing to unpack .../libxklavier16_5.2.1-1_amd64.deb ...
  Unpacking libxklavier16 (5.2.1-1) ...
  Selecting previously unselected package libxml2-dev:amd64.
  Preparing to unpack .../libxml2-dev_2.9.3+dfsg1-1_amd64.deb ...
  Unpacking libxml2-dev:amd64 (2.9.3+dfsg1-1) ...
  Selecting previously unselected package gir1.2-xkl-1.0.
  Preparing to unpack .../gir1.2-xkl-1.0_5.2.1-1_amd64.deb ...
  Unpacking gir1.2-xkl-1.0 (5.2.1-1) ...
  Selecting previously unselected package libxklavier-dev.
  Preparing to unpack .../libxklavier-dev_5.2.1-1_amd64.deb ...
  Unpacking libxklavier-dev (5.2.1-1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for libc-bin (2.22-9) ...
  Processing triggers for libglib2.0-0:amd64 (2.48.1-1) ...
  Processing triggers for systemd (229-6) ...
  Setting up cdbs (0.4.132) ...
  Setting up libgirepository-1.0-1:amd64 (1.48.0-2) ...
  Setting up gir1.2-glib-2.0:amd64 (1.48.0-2) ...
  Setting up libpng16-16:amd64 (1.6.21-5) ...
  Setting up libfreetype6:amd64 (2.6.3-3+b1) ...
  Setting up ucf (3.0036) ...
  Setting up fonts-dejavu-core (2.35-1) ...
  Setting up fontconfig-config (2.11.0-6.4) ...
  Setting up libfontconfig1:amd64 (2.11.0-6.4) ...
  Setting up libpixman-1-0:amd64 (0.33.6-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libxcb1:amd64 (1.11.1-1) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libx11-6:amd64 (2:1.6.3-1) ...
  Setting up libxcb-render0:amd64 (1.11.1-1) ...
  Setting up libxcb-shm0:amd64 (1.11.1-1) ...
  Setting up libxext6:amd64 (2:1.3.3-1) ...
  Setting up libxrender1:amd64 (1:0.9.9-2) ...
  Setting up libcairo2:amd64 (1.14.6-1+b1) ...
  Setting up libcairo-gobject2:amd64 (1.14.6-1+b1) ...
  Setting up gir1.2-freedesktop:amd64 (1.48.0-2) ...
  Setting up autoconf-archive (20150925-1) ...
  Setting up pkg-config (0.29-4) ...
  Setting up openssl (1.0.2h-1) ...
  Setting up ca-certificates (20160104) ...
  Setting up libencode-locale-perl (1.05-1) ...
  Setting up libhttp-date-perl (6.02-1) ...
  Setting up libfile-listing-perl (6.04-1) ...
  Setting up libhtml-tree-perl (5.03-2) ...
  Setting up libio-html-perl (1.001-1) ...
  Setting up liblwp-mediatypes-perl (6.02-1) ...
  Setting up libhttp-message-perl (6.11-1) ...
  Setting up libhttp-cookies-perl (6.01-1) ...
  Setting up libhttp-negotiate-perl (6.00-2) ...
  Setting up libnet-http-perl (6.09-1) ...
  Setting up libwww-robotrules-perl (6.01-1) ...
  Setting up gnome-pkg-tools (0.19.7) ...
  Setting up python-markupsafe (0.23-2+b2) ...
  Setting up python-mako (1.0.4+ds1-1) ...
  Setting up gobject-introspection (1.48.0-2) ...
  Setting up libatk1.0-data (2.20.0-1) ...
  Setting up libatk1.0-0:amd64 (2.20.0-1) ...
  Setting up gir1.2-atk-1.0 (2.20.0-1) ...
  Setting up libelf1:amd64 (0.165-3) ...
  Setting up libglib2.0-data (2.48.1-1) ...
  Setting up libglib2.0-bin (2.48.1-1) ...
  Setting up libpcre16-3:amd64 (2:8.38-3.1) ...
  Setting up libpcre32-3:amd64 (2:8.38-3.1) ...
  Setting up libpcrecpp0v5:amd64 (2:8.38-3.1) ...
  Setting up libpcre3-dev:amd64 (2:8.38-3.1) ...
  Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
  Setting up libglib2.0-dev (2.48.1-1) ...
  Setting up libatk1.0-dev (2.20.0-1) ...
  Setting up libffi-dev:amd64 (3.2.1-4) ...
  Setting up libgirepository1.0-dev (1.48.0-2) ...
  Setting up libdconf1:amd64 (0.26.0-1) ...
  Setting up dconf-service (0.26.0-1) ...
  Setting up dconf-gsettings-backend:amd64 (0.26.0-1) ...
  Setting up hicolor-icon-theme (0.13-1) ...
  Setting up libdbus-1-3:amd64 (1.10.8-1) ...
  Setting up libatspi2.0-0:amd64 (2.20.1-1) ...
  Setting up libatk-bridge2.0-0:amd64 (2.20.1-1) ...
  Setting up libepoxy0:amd64 (1.3.1-1) ...
  Setting up libjpeg62-turbo:amd64 (1:1.4.2-2) ...
  Setting up libjbig0:amd64 (2.1-3.1) ...
  Setting up libtiff5:amd64 (4.0.6-1)

Processed: reassign 823101 to ftp.debian.org, severity of 823101 is normal ...

[Debian Bug Tracking System]

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

> reassign 823101 ftp.debian.org
Bug #823101 [src:python-geoclue] python-geoclue: geoclue is scheduled for 
removal - switch to geoclue2
Bug reassigned from package 'src:python-geoclue' to 'ftp.debian.org'.
No longer marked as found in versions python-geoclue/0.1.0-4.
Ignoring request to alter fixed versions of bug #823101 to the same values 
previously set
> severity 823101 normal
Bug #823101 [ftp.debian.org] python-geoclue: geoclue is scheduled for removal - 
switch to geoclue2
Severity set to 'normal' from 'serious'
> retitle 823101 RM: python-geoclue -- ROM; obsolete
Bug #823101 [ftp.debian.org] python-geoclue: geoclue is scheduled for removal - 
switch to geoclue2
Changed Bug title to 'RM: python-geoclue -- ROM; obsolete' from 
'python-geoclue: geoclue is scheduled for removal - switch to geoclue2'.
> thanks
Stopping processing here.

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

Bug#824605: kfreebsd-10: CVE-2016-1887: Incorrect argument handling in sendmsg(2)

[Steven Chamberlain]

Package: src:kfreebsd-10
Version: 10.1~svn274115-4+kbsd8u3
Severity: grave
Tags: security

https://security.FreeBSD.org/advisories/FreeBSD-SA-16:19.sendmsg.asc

Incorrect argument handling in the socket code allows malicious local
user to overwrite large portion of the kernel memory.

This affects 10.1 in sid and jessie;  10.3 and 11.1 in experimental.
It was not reported to affect 9.0.

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

Kernel: kFreeBSD 10.1-0-amd64
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#824604: kfreebsd-10: CVE-2016-1886: Buffer overflow in keyboard driver

[Steven Chamberlain]

Package: src:kfreebsd-10
Version: 10.1~svn274115-4+kbsd8u3
Severity: grave
Tags: security

https://security.FreeBSD.org/advisories/FreeBSD-SA-16:18.atkbd.asc

Incorrect signedness comparison in the ioctl(2) handler allows a
malicious local user to overwrite a portion of the kernel memory.

This affects 10.1 in sid and jessie;  9.0 in wheezy;
10.3 and 11.1 in experimental.

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

Kernel: kFreeBSD 10.1-0-amd64
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#824587: marked as done (objenesis: Missing parent pom)

[Debian Bug Tracking System]

Your message dated Tue, 17 May 2016 22:32:59 +
with message-id 
and subject line Bug#824587: fixed in objenesis 2.3-2
has caused the Debian Bug report #824587,
regarding objenesis: Missing parent pom
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.)


-- 
824587: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: stapler
Version: 1.242-2
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,

stapler fails to build from source in unstable/amd64:

  [..]

  Adding debian:Staat_der_Nederlanden_Root_CA_-_G2.pem
  Adding debian:Staat_der_Nederlanden_Root_CA_-_G3.pem
  Adding debian:Starfield_Class_2_CA.pem
  Adding debian:Starfield_Root_Certificate_Authority_-_G2.pem
  Adding debian:Starfield_Services_Root_Certificate_Authority_-_G2.pem
  Adding debian:StartCom_Certification_Authority.pem
  Adding debian:StartCom_Certification_Authority_2.pem
  Adding debian:StartCom_Certification_Authority_G2.pem
  Adding debian:SwissSign_Gold_CA_-_G2.pem
  Adding debian:SwissSign_Platinum_CA_-_G2.pem
  Adding debian:SwissSign_Silver_CA_-_G2.pem
  Adding debian:Swisscom_Root_CA_1.pem
  Adding debian:Swisscom_Root_CA_2.pem
  Adding debian:Swisscom_Root_EV_CA_2.pem
  Adding debian:T-TeleSec_GlobalRoot_Class_2.pem
  Adding debian:T-TeleSec_GlobalRoot_Class_3.pem
  Adding debian:TC_TrustCenter_Class_3_CA_II.pem
  Adding debian:TURKTRUST_Certificate_Services_Provider_Root_2007.pem
  Adding debian:TWCA_Global_Root_CA.pem
  Adding debian:TWCA_Root_Certification_Authority.pem
  Adding debian:Taiwan_GRCA.pem
  Adding debian:TeliaSonera_Root_CA_v1.pem
  Adding debian:Trustis_FPS_Root_CA.pem
  Adding debian:TÜBİTAK_UEKAE_Kök_Sertifika_Hizmet_Sağlayıcısı_-_Sürüm_3.pem
  Adding debian:TÜRKTRUST_Elektronik_Sertifika_Hizmet_Sağlayıcısı_H5.pem
  Adding debian:TÜRKTRUST_Elektronik_Sertifika_Hizmet_Sağlayıcısı_H6.pem
  Adding debian:USERTrust_ECC_Certification_Authority.pem
  Adding debian:USERTrust_RSA_Certification_Authority.pem
  Adding debian:UTN_USERFirst_Email_Root_CA.pem
  Adding debian:UTN_USERFirst_Hardware_Root_CA.pem
  Adding debian:VeriSign_Class_3_Public_Primary_Certification_Authority_-_G4.pem
  Adding debian:VeriSign_Class_3_Public_Primary_Certification_Authority_-_G5.pem
  Adding debian:VeriSign_Universal_Root_Certification_Authority.pem
  Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority.pem
  Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority_-_G2.pem
  Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority_-_G3.pem
  Adding debian:Verisign_Class_2_Public_Primary_Certification_Authority_-_G2.pem
  Adding debian:Verisign_Class_2_Public_Primary_Certification_Authority_-_G3.pem
  Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority.pem
  Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority_-_G2.pem
  Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority_-_G3.pem
  Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority_2.pem
  Adding debian:Visa_eCommerce_Root.pem
  Adding debian:WellsSecure_Public_Root_Certificate_Authority.pem
  Adding debian:WoSign.pem
  Adding debian:WoSign_China.pem
  Adding debian:XRamp_Global_CA_Root.pem
  Adding debian:certSIGN_ROOT_CA.pem
  Adding debian:ePKI_Root_Certification_Authority.pem
  Adding debian:thawte_Primary_Root_CA.pem
  Adding debian:thawte_Primary_Root_CA_-_G2.pem
  Adding debian:thawte_Primary_Root_CA_-_G3.pem
  done.
  done.
  Setting up openjdk-8-jre-headless:amd64 (8u91-b14-2) ...
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/rmid to 
provide /usr/bin/rmid (rmid) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java to 
provide /usr/bin/java (java) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/keytool 
to provide /usr/bin/keytool (keytool) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/jjs to 
provide /usr/bin/jjs (jjs) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/pack200 
to provide /usr/bin/pack200 (pack200) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/rmiregistry to provide 
/usr/bin/rmiregistry (rmiregistry) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/unpack200 to provide 
/usr/bin/unpack200 

Bug#824550: marked as done (gr-air-modes build-depends on zeromq which is going to be removed)

[Debian Bug Tracking System]

Your message dated Tue, 17 May 2016 22:21:12 +
with message-id 
and subject line Bug#824550: fixed in gr-air-modes 0.0.2.65e5bd1-1
has caused the Debian Bug report #824550,
regarding gr-air-modes build-depends on zeromq which is going to be removed
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.)


-- 
824550: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
source: gr-air-modes
version: 0.0.1.514414f-5
severity: serious
control: block 818998 by -1

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818998

Please work towards removing the build-dependency on zeromq.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: gr-air-modes
Source-Version: 0.0.2.65e5bd1-1

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated gr-air-modes 
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, 17 May 2016 16:41:50 -0400
Source: gr-air-modes
Binary: gr-air-modes libair-modes0
Architecture: source amd64
Version: 0.0.2.65e5bd1-1
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Description:
 gr-air-modes - Gnuradio Mode-S/ADS-B radio
 libair-modes0 - Gnuradio Mode-S/ADS-B radio - library
Closes: 824550
Changes:
 gr-air-modes (0.0.2.65e5bd1-1) unstable; urgency=medium
 .
   * New upstream git describe --tags is 3.6-65-g65e5bd1
   * really fix build-depends (Closes: #824550)
Checksums-Sha1:
 d2721f252b93284b516f1b09294071ef3c3a1adf 2435 gr-air-modes_0.0.2.65e5bd1-1.dsc
 ca02c6f425eb9523bf8c618337f8cba43e5b19e9 132228 
gr-air-modes_0.0.2.65e5bd1.orig.tar.xz
 6a429b81c9a1e887b4655c450f98f07c5859d06e 6476 
gr-air-modes_0.0.2.65e5bd1-1.debian.tar.xz
 5b59e56dba9a91af247ab1152e49d9c66428aeb4 427962 
gr-air-modes-dbgsym_0.0.2.65e5bd1-1_amd64.deb
 f266351003d7f9732e830c0a99ccc5735b452166 112094 
gr-air-modes_0.0.2.65e5bd1-1_amd64.deb
 c9c6c81d3a3be344d046204872932d9dca990bc4 471680 
libair-modes0-dbgsym_0.0.2.65e5bd1-1_amd64.deb
 f3d6e5da0b800fe8cc1146c6ecf75db95aa2943d 32786 
libair-modes0_0.0.2.65e5bd1-1_amd64.deb
Checksums-Sha256:
 21af35b66b1ee2ef48f01de34de86bf7fa6cebbda9a9d387429d726bed5ccd64 2435 
gr-air-modes_0.0.2.65e5bd1-1.dsc
 12be82fff566779f95f6c877f42290e373bda619bb6fa3cd4ddde7973e007423 132228 
gr-air-modes_0.0.2.65e5bd1.orig.tar.xz
 6d867b6ba4217424d0b905d4337471c6612706cb3b12e917ba770838d17d2a72 6476 
gr-air-modes_0.0.2.65e5bd1-1.debian.tar.xz
 bdfbb0d871f18c39300a66613d9856f34e8f757f23a619f11497a05ac57dfc0e 427962 
gr-air-modes-dbgsym_0.0.2.65e5bd1-1_amd64.deb
 b96bc258c3e01b77c04523b12b4edc370dde2fcd0eb3ce9c2b09a0aa8588cfb6 112094 
gr-air-modes_0.0.2.65e5bd1-1_amd64.deb
 091e8162dde0804407fa45b7cd8481c15eebcb4646902876acb407f83b7dbba3 471680 
libair-modes0-dbgsym_0.0.2.65e5bd1-1_amd64.deb
 052630ca21b8d94474842a4d51bb773236309d610e45e6941f9653514f4714a5 32786 
libair-modes0_0.0.2.65e5bd1-1_amd64.deb
Files:
 0669c43c89a26007f1d7cabc3b399761 2435 libdevel optional 
gr-air-modes_0.0.2.65e5bd1-1.dsc
 d1459709ce1d5a957e0f72d4435095bd 132228 libdevel optional 
gr-air-modes_0.0.2.65e5bd1.orig.tar.xz
 38d768514c6647a5bc1d0fdb6645c0b5 6476 libdevel optional 
gr-air-modes_0.0.2.65e5bd1-1.debian.tar.xz
 155b2c5c130aba38401ae39059f84c60 427962 debug extra 
gr-air-modes-dbgsym_0.0.2.65e5bd1-1_amd64.deb
 7d7edc1fb170c31675e1e26fbd804359 112094 libdevel optional 
gr-air-modes_0.0.2.65e5bd1-1_amd64.deb
 5f075ac9d28fdb34243d18b0795b01a4 471680 debug extra 
libair-modes0-dbgsym_0.0.2.65e5bd1-1_amd64.deb
 1615b3c88632130a2e515b25053d8810 32786 libdevel optional 
li

Bug#824584: marked as done (libetonyek: FTBFS: configure: error: Package requirements (mdds) were not met)

[Debian Bug Tracking System]

Your message dated Tue, 17 May 2016 22:22:12 +
with message-id 
and subject line Bug#824584: fixed in libetonyek 0.1.6-2
has caused the Debian Bug report #824584,
regarding libetonyek: FTBFS: configure: error: Package requirements (mdds) were 
not met
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.)


-- 
824584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libetonyek
Version: 0.1.6-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,

libetonyek fails to build from source in unstable/amd64:

  [..]

  ac_cv_prog_CPP='gcc -E'
  ac_cv_prog_CXXCPP='g++ -E'
  ac_cv_prog_ac_ct_AR=ar
  ac_cv_prog_ac_ct_CC=gcc
  ac_cv_prog_ac_ct_CXX=g++
  ac_cv_prog_ac_ct_OBJDUMP=objdump
  ac_cv_prog_ac_ct_RANLIB=ranlib
  ac_cv_prog_ac_ct_STRIP=strip
  ac_cv_prog_cc_c89=
  ac_cv_prog_cc_g=yes
  ac_cv_prog_cxx_g=yes
  ac_cv_prog_make_make_set=yes
  am_cv_CC_dependencies_compiler_type=none
  am_cv_CXX_dependencies_compiler_type=none
  am_cv_ar_interface=ar
  am_cv_make_support_nested_variables=yes
  am_cv_prog_cc_c_o=yes
  lt_cv_ar_at_file=@
  lt_cv_archive_cmds_need_lc=no
  lt_cv_deplibs_check_method=pass_all
  lt_cv_file_magic_cmd='$MAGIC_CMD'
  lt_cv_file_magic_test_file=
  lt_cv_ld_reload_flag=-r
  lt_cv_nm_interface='BSD nm'
  lt_cv_objdir=.libs
  lt_cv_path_LD=/usr/bin/ld
  lt_cv_path_LDCXX='/usr/bin/ld -m elf_x86_64'
  lt_cv_path_NM='/usr/bin/nm -B'
  lt_cv_path_mainfest_tool=no
  lt_cv_prog_compiler_c_o=yes
  lt_cv_prog_compiler_c_o_CXX=yes
  lt_cv_prog_compiler_pic='-fPIC -DPIC'
  lt_cv_prog_compiler_pic_CXX='-fPIC -DPIC'
  lt_cv_prog_compiler_pic_works=yes
  lt_cv_prog_compiler_pic_works_CXX=yes
  lt_cv_prog_compiler_rtti_exceptions=no
  lt_cv_prog_compiler_static_works=yes
  lt_cv_prog_compiler_static_works_CXX=yes
  lt_cv_prog_gnu_ld=yes
  lt_cv_prog_gnu_ldcxx=yes
  lt_cv_sharedlib_from_linklib_cmd='printf %s\n'
  lt_cv_shlibpath_overrides_runpath=no
  lt_cv_sys_global_symbol_pipe='sed -n -e '\''s/^.*[ 
]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][  
]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p'\'' | sed '\''/ __gnu_lto/d'\'''
  lt_cv_sys_global_symbol_to_c_name_address='sed -n -e '\''s/^: \(.*\) .*$/  
{"\1", (void *) 0},/p'\'' -e '\''s/^[ABCDGIRSTW][ABCDGIRSTW]* .* \(.*\)$/  
{"\1", (void *) \&\1},/p'\'''
  lt_cv_sys_global_symbol_to_c_name_address_lib_prefix='sed -n -e '\''s/^: 
\(.*\) .*$/  {"\1", (void *) 0},/p'\'' -e '\''s/^[ABCDGIRSTW][ABCDGIRSTW]* .* 
\(lib.*\)$/  {"\1", (void *) \&\1},/p'\'' -e '\''s/^[ABCDGIRSTW][ABCDGIRSTW]* 
.* \(.*\)$/  {"lib\1", (void *) \&\1},/p'\'''
  lt_cv_sys_global_symbol_to_cdecl='sed -n -e '\''s/^T .* \(.*\)$/extern int 
\1();/p'\'' -e '\''s/^[ABCDGIRSTW][ABCDGIRSTW]* .* \(.*\)$/extern char 
\1;/p'\'''
  lt_cv_sys_global_symbol_to_import=
  lt_cv_sys_max_cmd_len=1572864
  lt_cv_to_host_file_cmd=func_convert_file_noop
  lt_cv_to_tool_file_cmd=func_convert_file_noop
  lt_cv_truncate_bin='/bin/dd bs=4096 count=1'
  pkg_cv_LANGTAG_CFLAGS='-I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include'
  pkg_cv_LANGTAG_LIBS='-llangtag -lglib-2.0'
  pkg_cv_REVENGE_CFLAGS=-I/usr/include/librevenge-0.0
  pkg_cv_REVENGE_LIBS=-lrevenge-0.0
  pkg_cv_XML_CFLAGS=-I/usr/include/libxml2
  pkg_cv_XML_LIBS=-lxml2
  pkg_cv_ZLIB_CFLAGS=
  pkg_cv_ZLIB_LIBS=-lz
  
  ## - ##
  ## Output variables. ##
  ## - ##
  
  ACLOCAL='${SHELL} 
/home/lamby/temp/cdt.20160517194831.Q0Esm8f53Q.libetonyek/libetonyek-0.1.6/missing
 aclocal-1.15'
  AMDEPBACKSLASH=''
  AMDEP_FALSE=''
  AMDEP_TRUE='#'
  AMTAR='$${TAR-tar}'
  AM_BACKSLASH='\'
  AM_DEFAULT_V='$(AM_DEFAULT_VERBOSITY)'
  AM_DEFAULT_VERBOSITY='1'
  AM_V='$(V)'
  AR='ar'
  AS='as'
  AUTOCONF='${SHELL} 
/home/lamby/temp/cdt.20160517194831.Q0Esm8f53Q.libetonyek/libetonyek-0.1.6/missing
 autoconf'
  AUTOHEADER='${SHELL} 
/home/lamby/temp/cdt.20160517194831.Q0Esm8f53Q.libetonyek/libetonyek-0.1.6/missing
 autoheader'
  AUTOMAKE='${SHELL} 
/home/lamby/temp/cdt.20160517194831.Q0Esm8f53Q.libetonyek/libetonyek-0.1.6/missing
 automake-1.15'
  AWK='mawk'
  BOOST_CFLAGS=''
  CC='gcc'
  CCDEPMODE='depmode=none'
  CFLAGS='-g -O2 -fstack-protector-strong -Wformat -Werror=format-security'
  CPP='gcc -E'
  CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2'
  CPPUNIT_CFLAGS=''
  CPPUNIT_LIBS=''
  CXX='g++'
  CXXCPP='g++ -E'
  CXXDEPMODE='depmode=none'
  CXXFLAGS='-g -O2 -fstack-protector-strong -Wformat -Werror=form

Bug#824596: wicd: FTBFS: KeyError: 'LANG'

[Sebastian Ramacher]

Source: wicd
Version: 1.7.4+tb2-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch

wicd currently fails to build:
| running compile_translations
| Traceback (most recent call last):
|   File "setup.py", line 708, in 
| data_files = data,
|   File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
| dist.run_commands()
|   File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
| self.run_command(cmd)
|   File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
| cmd_obj.run()
|   File "setup.py", line 68, in run
| _build.run(self)
|   File "/usr/lib/python2.7/distutils/command/build.py", line 128, in run
| self.run_command(cmd_name)
|   File "/usr/lib/python2.7/distutils/cmd.py", line 326, in run_command
| self.distribution.run_command(command)
|   File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
| cmd_obj.run()
|   File "setup.py", line 624, in run
| oldlang = os.environ['LANG']
|   File "/usr/lib/python2.7/UserDict.py", line 40, in __getitem__
| raise KeyError(key)
| KeyError: 'LANG'
| dh_auto_build: python setup.py build --force returned exit code 1

For a full build log see
https://people.debian.org/~sramacher/logs/wicd_1.7.4+tb2-1_amd64-20160517-2208.log

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#824595: cinder: FTBFS: FAIL: cinder.tests.unit.test_volume.ConsistencyGroupTestCase.test_create_delete_cgsnapshot

[Sebastian Ramacher]

chment': [], 'availability_zone': 
u'fake_az', 'tenant_id': '7f265bd4-3a85-465e-a899-5dc4854a86d3', 'created_at': 
'2016-05-17T20:58:41.257605+00:00', 'volume_id': 
'd2734803-8032-4cfd-bf0b-cbbd22bc37a3', 'volume_type': None, 'host': u'rigel', 
'replication_driver_data': None, 'replication_status': u'disabled', 
'snapshot_id': None, 'replication_extended_status': None, 'user_id': 
'c853ca26-e8ea-4797-8a52-ee124a013d0e', 'metadata': [], 'launched_at': 
'2016-05-17T20:58:41.257605', 'size': 1}, 'event_type': 'volume.create.start'}, 
{'priority': 'INFO', 'publisher_id': u'volume.rigel', 'payload': {'status': 
u'available', 'display_name': u'test_volume', 'volume_attachment': [], 
'availability_zone': u'fake_az', 'tenant_id': 
'7f265bd4-3a85-465e-a899-5dc4854a86d3', 'created_at': 
'2016-05-17T20:58:41.257605+00:00', 'volume_id': 
'd2734803-8032-4cfd-bf0b-cbbd22bc37a3', 'volume_type': None, 'host': u'rigel', 
'replication_driver_data': None, 'replication_status': u'disabled', 
'snapshot_id': None, 'replication_extended_status': None, 'user_id': 
'c853ca26-e8ea-4797-8a52-ee124a013d0e', 'metadata': [], 'launched_at': 
'2016-05-17T20:58:41.257605+00:00', 'size': 1}, 'event_type': 
'volume.create.end'}]
|
|
| --
| Ran 8010 tests in 482.671s
|
| FAILED (failures=1, skipped=6)
| make[1]: *** [override_dh_auto_test] Error 1

For a full build log see
https://people.debian.org/~sramacher/logs/cinder_8.0.0-2_amd64-20160517-2148.log

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#824593: python-reno: FTBFS due to missing B-D on git

[Sebastian Ramacher]

| FAIL: reno.tests.test_scanner.UniqueIdTest.test_legacy
| reno.tests.test_scanner.UniqueIdTest.test_legacy
| --
| _StringException: Empty attachments:
|   pythonlogging:''
|   stderr
|   stdout
|
| Traceback (most recent call last):
|   File "reno/tests/test_scanner.py", line 186, in setUp
| self._git_setup()
|   File "reno/tests/test_scanner.py", line 124, in _git_setup
| self._run_git('init', '.')
|   File "reno/tests/test_scanner.py", line 119, in _run_git
| cwd=self.reporoot,
|   File "reno/utils.py", line 44, in check_output
| raw = subprocess.check_output(*args, **kwds)
|   File "/usr/lib/python2.7/subprocess.py", line 567, in check_output
| process = Popen(stdout=PIPE, *popenargs, **kwargs)
|   File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
| errread, errwrite)
|   File "/usr/lib/python2.7/subprocess.py", line 1340, in _execute_child
| raise child_exception
| OSError: [Errno 2] No such file or directory
|
|
| ==
| FAIL: reno.tests.test_scanner.UniqueIdTest.test_modern
| reno.tests.test_scanner.UniqueIdTest.test_modern
| --
| _StringException: Empty attachments:
|   pythonlogging:''
|   stderr
|   stdout
|
| Traceback (most recent call last):
|   File "reno/tests/test_scanner.py", line 186, in setUp
| self._git_setup()
|   File "reno/tests/test_scanner.py", line 124, in _git_setup
| self._run_git('init', '.')
|   File "reno/tests/test_scanner.py", line 119, in _run_git
| cwd=self.reporoot,
|   File "reno/utils.py", line 44, in check_output
| raw = subprocess.check_output(*args, **kwds)
|   File "/usr/lib/python2.7/subprocess.py", line 567, in check_output
| process = Popen(stdout=PIPE, *popenargs, **kwargs)
|   File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
| errread, errwrite)
|   File "/usr/lib/python2.7/subprocess.py", line 1340, in _execute_child
| raise child_exception
| OSError: [Errno 2] No such file or directory
|
|
| --
| Ran 27 tests in 7.392s
|
| FAILED (failures=22)
| make[1]: *** [override_dh_auto_test] Error 1

See
https://people.debian.org/~sramacher/logs/python-reno_1.3.0-2_amd64-20160517-.log
for a full build log.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#824566: (no subject)

[Barry Warsaw]

I don't know how to use targetcli.  I tried the simple command you gave in
your bug report, but that failed for other reasons (some kind of input file is
missing).

In any case, I just uploaded pyparsing 2.1.4+dfsg1-1 which has a number of bug
fixes.  Please try that.  If it works for you, great!  Please close this bug.

If it still doesn't work for you, please provide a reproducible test case.

Bug#824587: objenesis: Missing parent pom

[Emmanuel Bourg]

Le 17/05/2016 à 21:52, Markus Koschany a écrit :

> Hmm, they don't ship a parent pom in 2.3 anymore. I will see if I can
> simply reuse the old one.

The project still has a parent pom though:

https://github.com/easymock/objenesis/blob/2.3/pom.xml

I suggest using the GitHub tag archive as the upstream tarball for the
next updates and reverting to maven-debian-helper.

Bug#824587: objenesis: Missing parent pom

[Markus Koschany]

Am 17.05.2016 um 21:38 schrieb Emmanuel Bourg:
> Control: retitle -1 objenesis: Missing parent pom
> Control: reassign -1 objenesis 2.3-1
> Control: affects -1 stapler wagon2
> 
> Thank you for the report Chris. This error is caused by objenesis/2.3-1,
> the parent pom is missing in the update. It affects all reverse
> dependencies using Maven.
> 

Hmm, they don't ship a parent pom in 2.3 anymore. I will see if I can
simply reuse the old one.

Markus




signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#824587: stapler: FTBFS: Could not resolve dependencies for project org.kohsuke.stapler:stapler:jar

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 objenesis: Missing parent pom
Bug #824587 [src:stapler] stapler: FTBFS: Could not resolve dependencies for 
project org.kohsuke.stapler:stapler:jar
Changed Bug title to 'objenesis: Missing parent pom' from 'stapler: FTBFS: 
Could not resolve dependencies for project org.kohsuke.stapler:stapler:jar'.
> reassign -1 objenesis 2.3-1
Bug #824587 [src:stapler] objenesis: Missing parent pom
Bug reassigned from package 'src:stapler' to 'objenesis'.
No longer marked as found in versions stapler/1.242-2.
Ignoring request to alter fixed versions of bug #824587 to the same values 
previously set
Bug #824587 [objenesis] objenesis: Missing parent pom
There is no source info for the package 'objenesis' at version '2.3-1' with 
architecture ''
Unable to make a source version for version '2.3-1'
Marked as found in versions 2.3-1.
> affects -1 stapler wagon2
Bug #824587 [objenesis] objenesis: Missing parent pom
Added indication that 824587 affects stapler and wagon2

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

Bug#824587: stapler: FTBFS: Could not resolve dependencies for project org.kohsuke.stapler:stapler:jar

[Emmanuel Bourg]

Control: retitle -1 objenesis: Missing parent pom
Control: reassign -1 objenesis 2.3-1
Control: affects -1 stapler wagon2

Thank you for the report Chris. This error is caused by objenesis/2.3-1,
the parent pom is missing in the update. It affects all reverse
dependencies using Maven.

Processed: affects 824585

[Debian Bug Tracking System]

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

> affects 824585 src:libgnomekbd
Bug #824585 [cdbs] libgnomekbd: FTBFS: find: 'doc': No such file or directory
Added indication that 824585 affects src:libgnomekbd
> thanks
Stopping processing here.

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

Bug#824585: libgnomekbd: FTBFS: find: 'doc': No such file or directory

[Michael Biebl]

Control: reassign -1 cdbs 0.4.132

Hi Chris,

thanks for your bug report. This is a regression in cdbs, thus reassigning.

Am 17.05.2016 um 21:04 schrieb Chris Lamb:
>   dpkg-buildpackage: info: source package libgnomekbd
>   dpkg-buildpackage: info: source version 3.6.0-1
>   dpkg-buildpackage: info: source distribution unstable
>   dpkg-buildpackage: info: source changed by Andreas Henriksson 
> 
>dpkg-source --before-build libgnomekbd-3.6.0
>   dpkg-buildpackage: info: host architecture amd64
>fakeroot debian/rules clean
>   test -x debian/rules
>   rm -f debian/stamp-makefile-build debian/stamp-makefile-install
>   GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL=1 /usr/bin/make  -C .  -k distclean
>   make[1]: Entering directory 
> '/home/lamby/temp/cdt.20160517194917.GNZtBMxNGo.libgnomekbd/libgnomekbd-3.6.0'
>   make[1]: *** No rule to make target 'distclean'.
>   make[1]: Leaving directory 
> '/home/lamby/temp/cdt.20160517194917.GNZtBMxNGo.libgnomekbd/libgnomekbd-3.6.0'
>   /usr/share/cdbs/1/class/makefile.mk:88: recipe for target 'makefile-clean' 
> failed
>   make: [makefile-clean] Error 2 (ignored)
>   rm -f debian/stamp-autotools
>   rmdir --ignore-fail-on-non-empty .
>   rmdir: failed to remove '.': Invalid argument
>   /usr/share/cdbs/1/class/autotools.mk:65: recipe for target 'makefile-clean' 
> failed
>   make: [makefile-clean] Error 1 (ignored)
>   for i in ./config.guess ./config.sub  ; do \
>   if test -e $i.cdbs-orig ; then \
>   mv $i.cdbs-orig $i ; \
>   fi ; \
>   done
>   if test -e debian/autoreconf.before; then \
>   dh_autoreconf_clean ; \
>   fi
>   dh_clean 
>   rm -f debian/copyright_newhints; 
>   rm -f debian/cdbs-install-list debian/cdbs-package-list 
> debian/stamp-copyright-check
>   rm -rf "debian/upstream-cruft"
>   rm -f debian/stamp-upstream-cruft
>   rm -f debian/stamp-autotools-files
>   cd "." && rm -f intltool-extract intltool-merge intltool-update 
> po/.intltool-merge-cache
>   find doc -name '*.omf.out' -type f -delete
>   find: 'doc': No such file or directory
>   /usr/share/cdbs/1/class/gnome.mk:38: recipe for target 'clean' failed
>   make: *** [clean] Error 1
> 



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



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#824585: libgnomekbd: FTBFS: find: 'doc': No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 cdbs 0.4.132
Bug #824585 [src:libgnomekbd] libgnomekbd: FTBFS: find: 'doc': No such file or 
directory
Bug reassigned from package 'src:libgnomekbd' to 'cdbs'.
No longer marked as found in versions libgnomekbd/3.6.0-1.
Ignoring request to alter fixed versions of bug #824585 to the same values 
previously set
Bug #824585 [cdbs] libgnomekbd: FTBFS: find: 'doc': No such file or directory
Marked as found in versions cdbs/0.4.132.

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

Bug#823750: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1553360

[Bastien ROUCARIES]

Not a concern after previous patches

Bug#824586: networkmanager-qt: FTBFS: dh_makeshlibs: failing due to earlier errors

[Chris Lamb]

Source: networkmanager-qt
Version: 5.16.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,

networkmanager-qt fails to build from source in unstable/amd64:

  [..]

  for doc in `cd 
/home/lamby/temp/cdt.20160517195048.VlRK3bUjME.networkmanager-qt/networkmanager-qt-5.16.0/debian/tmp/usr/share/doc/kde/HTML/en;
 find . -name index.docbook`; do \
  pkg=${doc%/index.docbook}; pkg=${pkg#./}; \
  echo Building $pkg HTML docs...; \
  mkdir -p 
/home/lamby/temp/cdt.20160517195048.VlRK3bUjME.networkmanager-qt/networkmanager-qt-5.16.0/debian/networkmanager-qt-doc-html/usr/share/doc/kde/HTML/en/$pkg;
 \
  cd 
/home/lamby/temp/cdt.20160517195048.VlRK3bUjME.networkmanager-qt/networkmanager-qt-5.16.0/debian/networkmanager-qt-doc-html/usr/share/doc/kde/HTML/en/$pkg;
 \
  meinproc5 
/home/lamby/temp/cdt.20160517195048.VlRK3bUjME.networkmanager-qt/networkmanager-qt-5.16.0/debian/tmp/usr/share/doc/kde/HTML/en/$pkg/index.docbook;
 \
  done; \
  for pkg in  ; do \
  rm -rf 
/home/lamby/temp/cdt.20160517195048.VlRK3bUjME.networkmanager-qt/networkmanager-qt-5.16.0/debian/networkmanager-qt-doc-html/usr/share/doc/kde/HTML/en/$pkg;
 \
  done; \
  fi
  dh_movelibkdeinit  
  dh_installdocs  
  dh_installchangelogs  
  dh_installexamples  
  dh_installman  
  dh_installcatalogs  
  dh_installcron  
  dh_installdebconf  
  dh_installemacsen  
  dh_installifupdown  
  dh_installinfo  
  dh_installinit  
  dh_installmenu  
  dh_installmime  
  dh_installmodules  
  dh_installlogcheck  
  dh_installlogrotate  
  dh_installpam  
  dh_installppp  
  dh_installudev  
  dh_installwm  
  dh_installxfonts  
  dh_bugfiles  
  dh_lintian  
  dh_gconf  
  dh_icons  
  dh_perl  
  dh_usrlocal  
  dh_link  
  dh_compress '-X.dcl' '-X.docbook' '-X-license' '-X.tag' '-X.sty' '-X.el'  
  dh_fixperms  
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160517195048.VlRK3bUjME.networkmanager-qt/networkmanager-qt-5.16.0'
  # "install" target is done
  /usr/bin/make -f debian/rules dhmk_run_binary_commands DHMK_TARGET="binary"
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160517195048.VlRK3bUjME.networkmanager-qt/networkmanager-qt-5.16.0'
  # Running override target (override_dh_strip)
  test -z "`ls debian/*.debhelper.log 2>/dev/null`" || sed -i 
'/^override_dh_strip[[:space:]]/d' debian/*.debhelper.log
  /usr/bin/make -f debian/rules override_dh_strip 
DH_INTERNAL_OVERRIDE="dh_strip"  
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160517195048.VlRK3bUjME.networkmanager-qt/networkmanager-qt-5.16.0'
  dh_strip  --dbg-package=libkf5networkmanagerqt6-dbg
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160517195048.VlRK3bUjME.networkmanager-qt/networkmanager-qt-5.16.0'
  dh_makeshlibs '-Xusr/lib/libkdeinit5_*'  
  dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
  dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
  dpkg-gensymbols: warning: debian/libkf5networkmanagerqt6/DEBIAN/symbols 
doesn't match completely debian/libkf5networkmanagerqt6.symbols
  --- debian/libkf5networkmanagerqt6.symbols 
(libkf5networkmanagerqt6_5.16.0-1_amd64)
  +++ dpkg-gensymbols_KeSnE 2016-05-17 19:54:36.067411476 +0100
  @@ -286,24 +286,24 @@
_ZN14NetworkManager11VlanSettingD0Ev@Base 5.1.1+git20141203.0020+15.04
_ZN14NetworkManager11VlanSettingD1Ev@Base 5.1.1+git20141203.0020+15.04
_ZN14NetworkManager11VlanSettingD2Ev@Base 5.1.1+git20141203.0020+15.04
  - _ZN14NetworkManager11WimaxDevice11bsidChangedERK7QString@Base 
5.1.1+git20141203.0020+15.04
  - _ZN14NetworkManager11WimaxDevice11cinrChangedEi@Base 
5.1.1+git20141203.0020+15.04
  - _ZN14NetworkManager11WimaxDevice11nspAppearedERK7QString@Base 
5.1.1+git20141203.0020+15.04
  - _ZN14NetworkManager11WimaxDevice11qt_metacallEN11QMetaObject4CallEiPPv@Base 
5.1.1+git20141203.0020+15.04
  - _ZN14NetworkManager11WimaxDevice11qt_metacastEPKc@Base 
5.1.1+git20141203.0020+15.04
  - _ZN14NetworkManager11WimaxDevice11rssiChangedEi@Base 
5.1.1+git20141203.0020+15.04
  - _ZN14NetworkManager11WimaxDevice14bitRateChangedEi@Base 
5.1.1+git20141203.0020+15.04
  - _ZN14NetworkManager11WimaxDevice14nspDisappearedERK7QString@Base 
5.1.1+git20141203.0020+15.04
  - _ZN14NetworkManager11WimaxDevice14txPowerChangedEi@Base 
5.1.1+git20141203.0020+15.04
  - _ZN14NetworkManager11WimaxDevice16activeNspChangedERK7QString@Base 
5.1.1+git20141203.0020+15.04
  - _ZN14NetworkManager11WimaxDevice16staticMetaObjectE@Base 
5.1.1+git20141203.0020+15.04
  - _ZN14NetworkManager11WimaxDevice22centerFrequencyChangedEj@Base 
5.1.1+git20141203.0020+15.04
  - _ZN14NetworkManager11WimaxDevice22hardwareAddressChangedERK7QString@Base 
5.1.1+git20141203.0020+15.04
  - _ZN14NetworkManager11WimaxDeviceC1ERK7QStringP7QO

Bug#824585: libgnomekbd: FTBFS: find: 'doc': No such file or directory

[Chris Lamb]

Source: libgnomekbd
Version: 3.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,

libgnomekbd fails to build from source in unstable/amd64:

  [..]

  Preparing to unpack .../libxklavier16_5.2.1-1_amd64.deb ...
  Unpacking libxklavier16 (5.2.1-1) ...
  Selecting previously unselected package libxml2-dev:amd64.
  Preparing to unpack .../libxml2-dev_2.9.3+dfsg1-1_amd64.deb ...
  Unpacking libxml2-dev:amd64 (2.9.3+dfsg1-1) ...
  Selecting previously unselected package gir1.2-xkl-1.0.
  Preparing to unpack .../gir1.2-xkl-1.0_5.2.1-1_amd64.deb ...
  Unpacking gir1.2-xkl-1.0 (5.2.1-1) ...
  Selecting previously unselected package libxklavier-dev.
  Preparing to unpack .../libxklavier-dev_5.2.1-1_amd64.deb ...
  Unpacking libxklavier-dev (5.2.1-1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for libc-bin (2.22-9) ...
  Processing triggers for libglib2.0-0:amd64 (2.48.1-1) ...
  Processing triggers for systemd (229-6) ...
  Setting up cdbs (0.4.132) ...
  Setting up libgirepository-1.0-1:amd64 (1.48.0-2) ...
  Setting up gir1.2-glib-2.0:amd64 (1.48.0-2) ...
  Setting up libpng16-16:amd64 (1.6.21-5) ...
  Setting up libfreetype6:amd64 (2.6.3-3+b1) ...
  Setting up ucf (3.0036) ...
  Setting up fonts-dejavu-core (2.35-1) ...
  Setting up fontconfig-config (2.11.0-6.4) ...
  Setting up libfontconfig1:amd64 (2.11.0-6.4) ...
  Setting up libpixman-1-0:amd64 (0.33.6-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libxcb1:amd64 (1.11.1-1) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libx11-6:amd64 (2:1.6.3-1) ...
  Setting up libxcb-render0:amd64 (1.11.1-1) ...
  Setting up libxcb-shm0:amd64 (1.11.1-1) ...
  Setting up libxext6:amd64 (2:1.3.3-1) ...
  Setting up libxrender1:amd64 (1:0.9.9-2) ...
  Setting up libcairo2:amd64 (1.14.6-1+b1) ...
  Setting up libcairo-gobject2:amd64 (1.14.6-1+b1) ...
  Setting up gir1.2-freedesktop:amd64 (1.48.0-2) ...
  Setting up autoconf-archive (20150925-1) ...
  Setting up pkg-config (0.29-4) ...
  Setting up openssl (1.0.2h-1) ...
  Setting up ca-certificates (20160104) ...
  Setting up libencode-locale-perl (1.05-1) ...
  Setting up libhttp-date-perl (6.02-1) ...
  Setting up libfile-listing-perl (6.04-1) ...
  Setting up libhtml-tree-perl (5.03-2) ...
  Setting up libio-html-perl (1.001-1) ...
  Setting up liblwp-mediatypes-perl (6.02-1) ...
  Setting up libhttp-message-perl (6.11-1) ...
  Setting up libhttp-cookies-perl (6.01-1) ...
  Setting up libhttp-negotiate-perl (6.00-2) ...
  Setting up libnet-http-perl (6.09-1) ...
  Setting up libwww-robotrules-perl (6.01-1) ...
  Setting up gnome-pkg-tools (0.19.7) ...
  Setting up python-markupsafe (0.23-2+b2) ...
  Setting up python-mako (1.0.4+ds1-1) ...
  Setting up gobject-introspection (1.48.0-2) ...
  Setting up libatk1.0-data (2.20.0-1) ...
  Setting up libatk1.0-0:amd64 (2.20.0-1) ...
  Setting up gir1.2-atk-1.0 (2.20.0-1) ...
  Setting up libelf1:amd64 (0.165-3) ...
  Setting up libglib2.0-data (2.48.1-1) ...
  Setting up libglib2.0-bin (2.48.1-1) ...
  Setting up libpcre16-3:amd64 (2:8.38-3.1) ...
  Setting up libpcre32-3:amd64 (2:8.38-3.1) ...
  Setting up libpcrecpp0v5:amd64 (2:8.38-3.1) ...
  Setting up libpcre3-dev:amd64 (2:8.38-3.1) ...
  Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
  Setting up libglib2.0-dev (2.48.1-1) ...
  Setting up libatk1.0-dev (2.20.0-1) ...
  Setting up libffi-dev:amd64 (3.2.1-4) ...
  Setting up libgirepository1.0-dev (1.48.0-2) ...
  Setting up libdconf1:amd64 (0.26.0-1) ...
  Setting up dconf-service (0.26.0-1) ...
  Setting up dconf-gsettings-backend:amd64 (0.26.0-1) ...
  Setting up hicolor-icon-theme (0.13-1) ...
  Setting up libdbus-1-3:amd64 (1.10.8-1) ...
  Setting up libatspi2.0-0:amd64 (2.20.1-1) ...
  Setting up libatk-bridge2.0-0:amd64 (2.20.1-1) ...
  Setting up libepoxy0:amd64 (1.3.1-1) ...
  Setting up libjpeg62-turbo:amd64 (1:1.4.2-2) ...
  Setting up libjbig0:amd64 (2.1-3.1) ...
  Setting up libtiff5:amd64 (4.0.6-1) ...
  Setting up shared-mime-info (1.6-1) ...
  Setting up libgdk-pixbuf2.0-common (2.34.0-1) ...
  Setting up libgdk-pixbuf2.0-0:amd64 (2.34.0-1) ...
  Setting up fontconfig (2.11.0-6.4) ...
  Regenerating fonts cache... done.
  Setting up libthai-data (0.1.24-2) ...
  Setting up libdatrie1:amd64 (0.2.10-2) ...
  Setting up libthai0:amd64 (0.1.24-2) ...
  Setting up libpango-1.0-0:amd64 (1.40.1-1) ...
  Setting up libgraphite2-3:amd64 (1.3.8-1) ...
  Setting up libharfbuzz0b:amd64 (1.2.6-2) ...
  Setting up libpangoft2-1.0-0:amd64 (1.40.1-1) ...
  Setting up libpangocairo-1.0-0:amd64 (1.40.1-1) ...
  Setting up libwayland-client0:amd64 (1.10.0-2) ...
  Setting up libwayland-cursor0:amd64 (1.10.0-2) ...
  Setting up libdrm2:amd64 (2.4.68-1) ...
  Setting up libwayland-server0:amd64 (1.10.0-2) ...
  Setting 

Bug#824587: stapler: FTBFS: Could not resolve dependencies for project org.kohsuke.stapler:stapler:jar

[Chris Lamb]

Source: stapler
Version: 1.242-2
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,

stapler fails to build from source in unstable/amd64:

  [..]

  Adding debian:Staat_der_Nederlanden_Root_CA_-_G2.pem
  Adding debian:Staat_der_Nederlanden_Root_CA_-_G3.pem
  Adding debian:Starfield_Class_2_CA.pem
  Adding debian:Starfield_Root_Certificate_Authority_-_G2.pem
  Adding debian:Starfield_Services_Root_Certificate_Authority_-_G2.pem
  Adding debian:StartCom_Certification_Authority.pem
  Adding debian:StartCom_Certification_Authority_2.pem
  Adding debian:StartCom_Certification_Authority_G2.pem
  Adding debian:SwissSign_Gold_CA_-_G2.pem
  Adding debian:SwissSign_Platinum_CA_-_G2.pem
  Adding debian:SwissSign_Silver_CA_-_G2.pem
  Adding debian:Swisscom_Root_CA_1.pem
  Adding debian:Swisscom_Root_CA_2.pem
  Adding debian:Swisscom_Root_EV_CA_2.pem
  Adding debian:T-TeleSec_GlobalRoot_Class_2.pem
  Adding debian:T-TeleSec_GlobalRoot_Class_3.pem
  Adding debian:TC_TrustCenter_Class_3_CA_II.pem
  Adding debian:TURKTRUST_Certificate_Services_Provider_Root_2007.pem
  Adding debian:TWCA_Global_Root_CA.pem
  Adding debian:TWCA_Root_Certification_Authority.pem
  Adding debian:Taiwan_GRCA.pem
  Adding debian:TeliaSonera_Root_CA_v1.pem
  Adding debian:Trustis_FPS_Root_CA.pem
  Adding debian:TÜBİTAK_UEKAE_Kök_Sertifika_Hizmet_Sağlayıcısı_-_Sürüm_3.pem
  Adding debian:TÜRKTRUST_Elektronik_Sertifika_Hizmet_Sağlayıcısı_H5.pem
  Adding debian:TÜRKTRUST_Elektronik_Sertifika_Hizmet_Sağlayıcısı_H6.pem
  Adding debian:USERTrust_ECC_Certification_Authority.pem
  Adding debian:USERTrust_RSA_Certification_Authority.pem
  Adding debian:UTN_USERFirst_Email_Root_CA.pem
  Adding debian:UTN_USERFirst_Hardware_Root_CA.pem
  Adding debian:VeriSign_Class_3_Public_Primary_Certification_Authority_-_G4.pem
  Adding debian:VeriSign_Class_3_Public_Primary_Certification_Authority_-_G5.pem
  Adding debian:VeriSign_Universal_Root_Certification_Authority.pem
  Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority.pem
  Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority_-_G2.pem
  Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority_-_G3.pem
  Adding debian:Verisign_Class_2_Public_Primary_Certification_Authority_-_G2.pem
  Adding debian:Verisign_Class_2_Public_Primary_Certification_Authority_-_G3.pem
  Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority.pem
  Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority_-_G2.pem
  Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority_-_G3.pem
  Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority_2.pem
  Adding debian:Visa_eCommerce_Root.pem
  Adding debian:WellsSecure_Public_Root_Certificate_Authority.pem
  Adding debian:WoSign.pem
  Adding debian:WoSign_China.pem
  Adding debian:XRamp_Global_CA_Root.pem
  Adding debian:certSIGN_ROOT_CA.pem
  Adding debian:ePKI_Root_Certification_Authority.pem
  Adding debian:thawte_Primary_Root_CA.pem
  Adding debian:thawte_Primary_Root_CA_-_G2.pem
  Adding debian:thawte_Primary_Root_CA_-_G3.pem
  done.
  done.
  Setting up openjdk-8-jre-headless:amd64 (8u91-b14-2) ...
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/rmid to 
provide /usr/bin/rmid (rmid) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java to 
provide /usr/bin/java (java) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/keytool 
to provide /usr/bin/keytool (keytool) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/jjs to 
provide /usr/bin/jjs (jjs) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/pack200 
to provide /usr/bin/pack200 (pack200) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/rmiregistry to provide 
/usr/bin/rmiregistry (rmiregistry) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/unpack200 to provide 
/usr/bin/unpack200 (unpack200) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/orbd to 
provide /usr/bin/orbd (orbd) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/servertool to provide 
/usr/bin/servertool (servertool) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/tnameserv to provide 
/usr/bin/tnameserv (tnameserv) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jexec to 
provide /usr/bin/jexec (jexec) in auto mode
  Setting up default-jre-headless (2:1.8-57) ...
  Setting up openjdk-8-jre:amd64 (8u91-b14-2) ...
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/policytool to provide 
/usr/bin/policytool (policytool) in auto mode
  

Bug#824584: libetonyek: FTBFS: configure: error: Package requirements (mdds) were not met

[Chris Lamb]

Source: libetonyek
Version: 0.1.6-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,

libetonyek fails to build from source in unstable/amd64:

  [..]

  ac_cv_prog_CPP='gcc -E'
  ac_cv_prog_CXXCPP='g++ -E'
  ac_cv_prog_ac_ct_AR=ar
  ac_cv_prog_ac_ct_CC=gcc
  ac_cv_prog_ac_ct_CXX=g++
  ac_cv_prog_ac_ct_OBJDUMP=objdump
  ac_cv_prog_ac_ct_RANLIB=ranlib
  ac_cv_prog_ac_ct_STRIP=strip
  ac_cv_prog_cc_c89=
  ac_cv_prog_cc_g=yes
  ac_cv_prog_cxx_g=yes
  ac_cv_prog_make_make_set=yes
  am_cv_CC_dependencies_compiler_type=none
  am_cv_CXX_dependencies_compiler_type=none
  am_cv_ar_interface=ar
  am_cv_make_support_nested_variables=yes
  am_cv_prog_cc_c_o=yes
  lt_cv_ar_at_file=@
  lt_cv_archive_cmds_need_lc=no
  lt_cv_deplibs_check_method=pass_all
  lt_cv_file_magic_cmd='$MAGIC_CMD'
  lt_cv_file_magic_test_file=
  lt_cv_ld_reload_flag=-r
  lt_cv_nm_interface='BSD nm'
  lt_cv_objdir=.libs
  lt_cv_path_LD=/usr/bin/ld
  lt_cv_path_LDCXX='/usr/bin/ld -m elf_x86_64'
  lt_cv_path_NM='/usr/bin/nm -B'
  lt_cv_path_mainfest_tool=no
  lt_cv_prog_compiler_c_o=yes
  lt_cv_prog_compiler_c_o_CXX=yes
  lt_cv_prog_compiler_pic='-fPIC -DPIC'
  lt_cv_prog_compiler_pic_CXX='-fPIC -DPIC'
  lt_cv_prog_compiler_pic_works=yes
  lt_cv_prog_compiler_pic_works_CXX=yes
  lt_cv_prog_compiler_rtti_exceptions=no
  lt_cv_prog_compiler_static_works=yes
  lt_cv_prog_compiler_static_works_CXX=yes
  lt_cv_prog_gnu_ld=yes
  lt_cv_prog_gnu_ldcxx=yes
  lt_cv_sharedlib_from_linklib_cmd='printf %s\n'
  lt_cv_shlibpath_overrides_runpath=no
  lt_cv_sys_global_symbol_pipe='sed -n -e '\''s/^.*[ 
]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][  
]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p'\'' | sed '\''/ __gnu_lto/d'\'''
  lt_cv_sys_global_symbol_to_c_name_address='sed -n -e '\''s/^: \(.*\) .*$/  
{"\1", (void *) 0},/p'\'' -e '\''s/^[ABCDGIRSTW][ABCDGIRSTW]* .* \(.*\)$/  
{"\1", (void *) \&\1},/p'\'''
  lt_cv_sys_global_symbol_to_c_name_address_lib_prefix='sed -n -e '\''s/^: 
\(.*\) .*$/  {"\1", (void *) 0},/p'\'' -e '\''s/^[ABCDGIRSTW][ABCDGIRSTW]* .* 
\(lib.*\)$/  {"\1", (void *) \&\1},/p'\'' -e '\''s/^[ABCDGIRSTW][ABCDGIRSTW]* 
.* \(.*\)$/  {"lib\1", (void *) \&\1},/p'\'''
  lt_cv_sys_global_symbol_to_cdecl='sed -n -e '\''s/^T .* \(.*\)$/extern int 
\1();/p'\'' -e '\''s/^[ABCDGIRSTW][ABCDGIRSTW]* .* \(.*\)$/extern char 
\1;/p'\'''
  lt_cv_sys_global_symbol_to_import=
  lt_cv_sys_max_cmd_len=1572864
  lt_cv_to_host_file_cmd=func_convert_file_noop
  lt_cv_to_tool_file_cmd=func_convert_file_noop
  lt_cv_truncate_bin='/bin/dd bs=4096 count=1'
  pkg_cv_LANGTAG_CFLAGS='-I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include'
  pkg_cv_LANGTAG_LIBS='-llangtag -lglib-2.0'
  pkg_cv_REVENGE_CFLAGS=-I/usr/include/librevenge-0.0
  pkg_cv_REVENGE_LIBS=-lrevenge-0.0
  pkg_cv_XML_CFLAGS=-I/usr/include/libxml2
  pkg_cv_XML_LIBS=-lxml2
  pkg_cv_ZLIB_CFLAGS=
  pkg_cv_ZLIB_LIBS=-lz
  
  ## - ##
  ## Output variables. ##
  ## - ##
  
  ACLOCAL='${SHELL} 
/home/lamby/temp/cdt.20160517194831.Q0Esm8f53Q.libetonyek/libetonyek-0.1.6/missing
 aclocal-1.15'
  AMDEPBACKSLASH=''
  AMDEP_FALSE=''
  AMDEP_TRUE='#'
  AMTAR='$${TAR-tar}'
  AM_BACKSLASH='\'
  AM_DEFAULT_V='$(AM_DEFAULT_VERBOSITY)'
  AM_DEFAULT_VERBOSITY='1'
  AM_V='$(V)'
  AR='ar'
  AS='as'
  AUTOCONF='${SHELL} 
/home/lamby/temp/cdt.20160517194831.Q0Esm8f53Q.libetonyek/libetonyek-0.1.6/missing
 autoconf'
  AUTOHEADER='${SHELL} 
/home/lamby/temp/cdt.20160517194831.Q0Esm8f53Q.libetonyek/libetonyek-0.1.6/missing
 autoheader'
  AUTOMAKE='${SHELL} 
/home/lamby/temp/cdt.20160517194831.Q0Esm8f53Q.libetonyek/libetonyek-0.1.6/missing
 automake-1.15'
  AWK='mawk'
  BOOST_CFLAGS=''
  CC='gcc'
  CCDEPMODE='depmode=none'
  CFLAGS='-g -O2 -fstack-protector-strong -Wformat -Werror=format-security'
  CPP='gcc -E'
  CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2'
  CPPUNIT_CFLAGS=''
  CPPUNIT_LIBS=''
  CXX='g++'
  CXXCPP='g++ -E'
  CXXDEPMODE='depmode=none'
  CXXFLAGS='-g -O2 -fstack-protector-strong -Wformat -Werror=format-security'
  CYGPATH_W='echo'
  DEBUG_CXXFLAGS=''
  DEFS=''
  DEPDIR='.deps'
  DLLTOOL='false'
  DOXYGEN=''
  DSYMUTIL=''
  DUMPBIN=''
  ECHO_C=''
  ECHO_N='-n'
  ECHO_T=''
  EGREP='/bin/grep -E'
  ETONYEK_MAJOR_VERSION=''
  ETONYEK_MICRO_VERSION=''
  ETONYEK_MINOR_VERSION=''
  EXEEXT=''
  FGREP='/bin/grep -F'
  GLM_CFLAGS=''
  GPERF='${SHELL} 
/home/lamby/temp/cdt.20160517194831.Q0Esm8f53Q.libetonyek/libetonyek-0.1.6/missing
 gperf'
  GREP='/bin/grep'
  HAVE_CXX11=''
  INSTALL_DATA='${INSTALL} -m 644'
  INSTALL_PROGRAM='${INSTALL}'
  INSTALL_SCRIPT='${INSTALL}'
  INSTALL_STRIP_PROGRAM='$(install_sh) -c -s'
  KEY2RAW_WIN32_RESOURCE=''
  KEY2TEXT_WIN32_RESOURCE=''
  KEY2XHTML_WIN32_RESOURCE=''
  KN_VERSION=''
  LANGTAG_CFLAGS='-I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include'
  LANGTAG_LIBS='-llangtag -lglib-2.0

Bug#824581: supercollider: FTBFS on various arches: errors in oscpack_build.cpp

[James Cowgill]

Source: supercollider
Version: 1:3.7.0~repack-1
Severity: serious

Hi,

supercollider FTBFS on every arch except for amd64, i386, armhf and
mipsel.

The build fails during the compile of oscpack_build.cpp with one of
these errors. The first error appears on 64-bit arches only.

===

[ 30%] Building CXX object 
external_libraries/CMakeFiles/oscpack.dir/oscpack_build.cpp.o
cd "/«PKGBUILDDIR»/obj-alpha-linux-gnu/external_libraries" && /usr/bin/g++   
-DBOOST_CHRONO_HEADER_ONLY -DBOOST_NO_AUTO_PTR 
-DSC_DATA_DIR=\"/usr/share/SuperCollider\" 
-I"/«PKGBUILDDIR»/external_libraries/boost"  -g -O2 -Wformat 
-Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -O2 -g 
-DNDEBUG   -fschedule-insns2 -fomit-frame-pointer -Wreturn-type -pthread 
-fvisibility=hidden -o CMakeFiles/oscpack.dir/oscpack_build.cpp.o -c 
"/«PKGBUILDDIR»/external_libraries/oscpack_build.cpp"
In file included from /«PKGBUILDDIR»/external_libraries/oscpack_build.cpp:13:0:
/«PKGBUILDDIR»/external_libraries/oscpack_1_1_0/osc/OscReceivedElements.cpp: In 
function 'osc::uint32 osc::RoundUp4(osc::uint32)':
/«PKGBUILDDIR»/external_libraries/oscpack_1_1_0/osc/OscReceivedElements.cpp:87:22:
 error: redefinition of 'osc::uint32 osc::RoundUp4(osc::uint32)'
 static inline uint32 RoundUp4( uint32 x ) 
  ^
In file included from /«PKGBUILDDIR»/external_libraries/oscpack_build.cpp:11:0:
/«PKGBUILDDIR»/external_libraries/oscpack_1_1_0/osc/OscOutboundPacketStream.cpp:149:27:
 note: 'std::size_t osc::RoundUp4(std::size_t)' previously defined here
 static inline std::size_t RoundUp4( std::size_t x ) 
   ^
external_libraries/CMakeFiles/oscpack.dir/build.make:65: recipe for target 
'external_libraries/CMakeFiles/oscpack.dir/oscpack_build.cpp.o' failed
make[3]: *** [external_libraries/CMakeFiles/oscpack.dir/oscpack_build.cpp.o] 
Error 1

===

[ 30%] Building CXX object 
external_libraries/CMakeFiles/oscpack.dir/oscpack_build.cpp.o
cd "/«PKGBUILDDIR»/obj-mips-linux-gnu/external_libraries" && /usr/bin/g++   
-DBOOST_CHRONO_HEADER_ONLY -DBOOST_NO_AUTO_PTR 
-DSC_DATA_DIR=\"/usr/share/SuperCollider\" 
-I"/«PKGBUILDDIR»/external_libraries/boost"  -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
-std=c++11 -O2 -g -DNDEBUG   -fschedule-insns2 -fomit-frame-pointer 
-Wreturn-type -pthread -fvisibility=hidden -o 
CMakeFiles/oscpack.dir/oscpack_build.cpp.o -c 
"/«PKGBUILDDIR»/external_libraries/oscpack_build.cpp"
In file included from /«PKGBUILDDIR»/external_libraries/oscpack_build.cpp:13:0:
/«PKGBUILDDIR»/external_libraries/oscpack_1_1_0/osc/OscReceivedElements.cpp: In 
member function 'osc::int32 osc::ReceivedMessageArgument::AsInt32Unchecked() 
const':
/«PKGBUILDDIR»/external_libraries/oscpack_1_1_0/osc/OscReceivedElements.cpp:252:18:
 error: 'argument_' was not declared in this scope
  return *(int32*)argument_;
  ^
/«PKGBUILDDIR»/external_libraries/oscpack_1_1_0/osc/OscReceivedElements.cpp: In 
member function 'float osc::ReceivedMessageArgument::AsFloatUnchecked() const':
/«PKGBUILDDIR»/external_libraries/oscpack_1_1_0/osc/OscReceivedElements.cpp:283:18:
 error: 'argument_' was not declared in this scope
  return *(float*)argument_;
  ^
/«PKGBUILDDIR»/external_libraries/oscpack_1_1_0/osc/OscReceivedElements.cpp: In 
member function 'double osc::ReceivedMessageArgument::AsDoubleUnchecked() 
const':
/«PKGBUILDDIR»/external_libraries/oscpack_1_1_0/osc/OscReceivedElements.cpp:403:19:
 error: 'argument_' was not declared in this scope
  return *(double*)argument_;
   ^
external_libraries/CMakeFiles/oscpack.dir/build.make:65: recipe for target 
'external_libraries/CMakeFiles/oscpack.dir/oscpack_build.cpp.o' failed

===

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

Thanks,
James

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

Bug#823750: Fix a SIGABRT in pdb file handling

[Bastien ROUCARIES]

Fix a SIGABRT in pdb file handling

bug: https://github.com/ImageMagick/ImageMagick/issues/148
bug-ubuntu:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1556273
origin: upstream,
https://github.com/ImageMagick/ImageMagick/commit/53c1dcd34bed85181b901bfce1a2322f85a59472
bug-debian:  https://bugs.debian.org/823750

Bug#823750: Fix an out of bound access in pdb file handling

[Bastien ROUCARIES]

bug: https://github.com/ImageMagick/ImageMagick/issues/143
origin: upstream,
https://github.com/ImageMagick/ImageMagick/commit/424d40ebfcde48bb872eba75179d3d73704fdf1f
bug-ubuntu:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1553366
bug-debian:  https://bugs.debian.org/823750

Bug#822397: collectd FTBFS: configure: error: "Some plugins are missing dependencies

[Jean-Michel Vourgère]

Ben Hutching uploaded linux 4.5.4-1 that fixes this issue this morning.
See https://bugs.debian.org/822396

Build is under way...
https://buildd.debian.org/status/package.php?p=linux&suite=unstable

collected no longer FTBFS here.

Bug#823916: marked as done (pypy: FTBFS on s390x)

[Debian Bug Tracking System]

Your message dated Tue, 17 May 2016 17:51:45 +
with message-id 
and subject line Bug#823916: fixed in pypy 5.1.2+dfsg-1
has caused the Debian Bug report #823916,
regarding pypy: FTBFS on s390x
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.)


-- 
823916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pypy
Version: 5.1+dfsg-1
Severity: serious

Your package failed to build on s390x.

=== 390 failed, 12 skipped in 43.08 seconds 
pypy/goal/pypy-c -u pypy/test_all.py \
   --resultlog=build-tests/pypy-c.log \
   pypy/module/pypyjit/test_pypy_c || true
Illegal instruction

Logs at:

https://buildd.debian.org/status/logs.php?pkg=pypy&ver=5.1%2Bdfsg-1&arch=s390x

Emilio
--- End Message ---
--- Begin Message ---
Source: pypy
Source-Version: 5.1.2+dfsg-1

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

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

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated pypy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 17 May 2016 19:31:56 +0200
Source: pypy
Binary: pypy pypy-tk python-pypy.sandbox pypy-lib pypy-lib-testsuite pypy-doc 
pypy-dev
Architecture: source
Version: 5.1.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Stefano Rivera 
Changed-By: Stefano Rivera 
Description:
 pypy   - fast alternative implementation of Python - PyPy interpreter
 pypy-dev   - header files for PyPy (an alternative Python interpreter)
 pypy-doc   - developer Documentation for PyPy (an alternative Python interpret
 pypy-lib   - standard library for PyPy (an alternative Python interpreter)
 pypy-lib-testsuite - standard library test suite for PyPy (an alternative 
Python inter
 pypy-tk- Tkinter module for PyPy (an alternative Python interpreter)
 python-pypy.sandbox - sandboxed PyPy interpreter
Closes: 823916
Changes:
 pypy (5.1.2+dfsg-1) unstable; urgency=medium
 .
   * New upstream release.
   * Refresh s390x-march.
   * Drop other s390x patches, superseded upstream.
   * Build with cpython on s390x, until we've got a JIT bootstrapped (builds
 timing out, without it). (Closes: #823916)
   * britney now supports versioned Provides, so generate them in pydist.
Checksums-Sha1:
 0158ae50735371e5059e0a960dd303c37bc547e0 2343 pypy_5.1.2+dfsg-1.dsc
 998ac0bc78f29428d129482f9f0b28ad6b910593 11847320 pypy_5.1.2+dfsg.orig.tar.xz
 561393c7862a06fe7d55ba84c004b3ac0c5c54a4 64712 pypy_5.1.2+dfsg-1.debian.tar.xz
Checksums-Sha256:
 98becd93bf91dea1d7ef89fd15352981be45b260d495423800901735f944a20d 2343 
pypy_5.1.2+dfsg-1.dsc
 c6953ded53d78ddc6bce9d452fb29cb43387219231cdfbe79d822708cf2e5ecd 11847320 
pypy_5.1.2+dfsg.orig.tar.xz
 888cd1a3287a28a5cc66a8f4a365b613f6275c46ed43ab7d9e5e6b0e68ed23cd 64712 
pypy_5.1.2+dfsg-1.debian.tar.xz
Files:
 2927a8294ef64fe5c581f18251082073 2343 python extra pypy_5.1.2+dfsg-1.dsc
 51debb385636911e4cde764d95f71e1d 11847320 python extra 
pypy_5.1.2+dfsg.orig.tar.xz
 9e1366e72b2c8f956d7c749d7d8e1fe7 64712 python extra 
pypy_5.1.2+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCgAGBQJXO1XIAAoJEOrxkryqPw9R+0IH/jjeOj1I+BxnWVPqpAScc7h6
RxExLzaboxW2pXjthAUALdFbzu99H1Vhe/NtH3jV90mWlXRKnNBwl3UyjvPecOjm
YJ/XNNzIkqg1CdmkycFMcFA3iS1kvWDQ/qecP9p6Js54p/wsZJ/37yoxDpDawENt
MRwbYw2K3Wg7xMdiAbFKG0iLbVdqyIf1KkJZry+JLK1W0wnmhq78QcPE2SveiKLA
VaA3j9wx12fK9GY/RGa3YlWPRvqWlJemYL8YU1HVREtuA0nb96Yu7Z5RUDjt7yzX
oe1DgbgbOV87gn00BBf1btUoJDD1JkFbBls2GFeHWFa0rZQyz9hIHldIbuOuUSo=
=tJlW
-END PGP SIGNATURE End Message ---

Bug#823750: Already fixed

[Bastien ROUCARIES]

https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1553366

Bug#823750: Fix an out of bound in mat file handling

[Bastien ROUCARIES]

Origin: upstream,
https://github.com/ImageMagick/ImageMagick/commit/1bc1fd0ff8c555841c78829217ac81fa0598255d
bug-ubuntu:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1545183
bug-debian: https://bugs.debian.org/823750
Bug:https://github.com/ImageMagick/ImageMagick/issues/131

Bug#822529: gdm3: retries to often / to fast on errors

[Michael Biebl]

Control: tags -1 moreinfo

On Fri, 6 May 2016 16:52:33 +0200 Laurent Bigonville 
wrote:
> Do you think it's a regression from 3.18? TBH, I think I already saw 
> this behavior in the past.

Tobias, can you please answer this question, i.e. try 3.18 from testing
and see if that shows the same behaviour.

Atm, this bug blocks gdm3 and a lot of other important GNOME 3.20 from
entering testing.

Michael


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



signature.asc
Description: OpenPGP digital signature

Processed: Re: gdm3: retries to often / to fast on errors

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #822529 [gdm3] gdm3: retries to often / to fast on errors
Added tag(s) moreinfo.

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

Bug#819096: Frequent hangs/crashes when changing network configuration

[Michael Biebl]

Control: severity -1 important

Hi Ben

On Fri, 25 Mar 2016 08:50:04 + Simon McVittie  wrote:
> On Wed, 23 Mar 2016 at 15:48:33 +, Ben Hutchings wrote:
> > If I change the network configuration through the right hand menu in
> > GNOME Shell it may hang for 10 seconds or (apparently) indefinitely.
> 
> Do you get the same thing in 3.18.1-1 from testing? If you do, please
> mark this bug as found there so it doesn't have to block migration.
> 
> If you can provide some more specific steps-to-reproduce (something like
> "be on wifi, switch to mobile broadband, switch back to wifi"), or a
> rough idea of what proportion of the time those steps will trigger this
> bug, that would probably also be useful information.

Since we didn't have any further feedback and I can't seem to reproduce
the issue, I'm downgrading the severity (for now).
Otherwise this bug blocks gnome-shell and other important updates to
enter testing.

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



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#819096: Frequent hangs/crashes when changing network configuration

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #819096 [gnome-shell] Frequent hangs/crashes when changing network 
configuration
Severity set to 'important' from 'serious'

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

Bug#824455: marked as done (missing license in debian/copyright)

[Debian Bug Tracking System]

Your message dated Tue, 17 May 2016 16:21:21 +
with message-id 
and subject line Bug#824455: fixed in irstlm 6.00.05-2
has caused the Debian Bug report #824455,
regarding missing license in debian/copyright
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.)


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

Package: irstlm
Version: 6.00.05-1
Severity: serious
User: alteh...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks

Dear Maintainer,

please add the missing license of:
 irstlm-6.00.05/doc/mdframed.sty
to your debian/copyright.

Thanks!
  Thorsten
--- End Message ---
--- Begin Message ---
Source: irstlm
Source-Version: 6.00.05-2

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

Debian distribution maintenance software
pp.
Giulio Paci  (supplier of updated irstlm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 17 May 2016 09:45:14 +0200
Source: irstlm
Binary: irstlm libirstlm-dev libirstlm1
Architecture: source
Version: 6.00.05-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Giulio Paci 
Description:
 irstlm - IRST Language Modeling Toolkit
 libirstlm-dev - IRST Language Modeling Toolkit - development files
 libirstlm1 - IRST Language Modeling Toolkit - runtime library
Closes: 824455
Changes:
 irstlm (6.00.05-2) unstable; urgency=medium
 .
   * Add missing LPPL license to copyright.
 Closes: #824455
   * Add path command to irstlm wrapper script.
   * Change maintainer to Debian Science Maintainers
 
   * Updated Vcs-* fields in control.
 The repository has been moved to debian-science.
Checksums-Sha1:
 bfcc750d9fc4c1f6d9374d141f466809b63475f0 2258 irstlm_6.00.05-2.dsc
 1b9d384c504a3016190d9458f46047009f384049 21068 irstlm_6.00.05-2.debian.tar.xz
Checksums-Sha256:
 30bb05c7d80a00893c2fe7725836a6cb175e131840b1ac88ad7ebc4b54da9ab6 2258 
irstlm_6.00.05-2.dsc
 60bddc641ed286b5e97dd339d94a5ee8f918ee46f0bc58b124789e65ca4ba1bc 21068 
irstlm_6.00.05-2.debian.tar.xz
Files:
 ce8d1d67d4fa06da22779e17613a2fb9 2258 science optional irstlm_6.00.05-2.dsc
 cb507ebc7e6769f9edf1dbb233164cee 21068 science optional 
irstlm_6.00.05-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXOyajAAoJEEsEP825REVAoR8QAIumYHJ6EJgP0OUwLoxn2HEY
5hEhk9PwrkmasaDL02mpbKcbdI/m2muVBQcBFxTa9dujFPzOR9clLwYM132hrRXs
IJbQFK4p0cpXE9M1TxtvS0bjXRSsrtphC91WRpu7h3C+bMY2lce3gWd2GTKyAIVG
JAbydek0UeqyO2fmr7LqhetQ4JKT2QSSwBbTLEgvAbixUaIHD4L/eHCp+M8kJwDb
BSjdDoCF32Kzgmws0jceDuT5MSWKdxNcDVeCJINaBQTAk7wc6LWKgms7HAu2NBWh
+nSey+F4ml1izSIcAX9Tn89U0RYGvgcvcXbR7TogOF4lS9ZXSgquvw3UTiALyjf/
vLLWNVFzYRcu/deqQTjysgSv//H3bRymiiKIc10VjbH34ThSv7V6TclAUJcf6Keo
5PPlw5ZtU9hgNXFpNTx0gp98KdorOB+10+00f08uit6eFWvRSG6Cyomsp4Ph6RxV
Zwiier/IiuqpDxcnpf5AgqkzTvBWwgQitkhLmMSngzQ7oOZkN0Od6tZCiHjbvOkL
6jDdtifIUvj+8sXyOR3AmNt7ohE+DNWqoxP7y9wmJHe9a9/+KPvV9ZDaqt+6TrXw
Bw/G8TWXBOHAaNyLWWigxE6NKEgTPsIj9Cl2xh4jqSGj72LUffnPmb1tLE4u1rOq
zJWfnVYDC98bRSkF8+np
=25Ya
-END PGP SIGNATURE End Message ---

Bug#823318: marked as done (giada: contains non-free Steinberg ASIO library)

[Debian Bug Tracking System]

Your message dated Tue, 17 May 2016 16:20:19 +
with message-id 
and subject line Bug#823318: fixed in giada 0.12.1~dfsg1-1
has caused the Debian Bug report #823318,
regarding giada: contains non-free Steinberg ASIO library
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.)


-- 
823318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: giada
Version: 0.11.2~dfsg-1
Severity: serious

Hi,

giada contains a bundled copy of the Steinberg ASIO library headers in
src/deps/rtaudio-mod/include. These files are under very strict
licensing terms which can be found here (you have to download the SDK
and open the PDF):
http://www.steinberg.net/en/company/developers.html

The term "Licensed Software Developer Kit" appears to cover all the
code:

1.1
The object of this agreement consists of the Steinberg ASIO (Audio
Stream I/O) Software Development Kit version 2.3, respectively any
preview version of this Kit, comprising of documentation, example code,
and several ASIO examples. These are described hereinafter as the
"Licensed Software Developer Kit".

The license goes on to include other terms which seem to prohibit
modification or redistribution in most cases:

2.3
The Licensee has no permission to sell, license, give-away and/or
distribute the Licensed Software Developer Kit or parts of it for the
use as software developer kit in any way, for example, integrated in
any framework application, on any medium, including the Internet, to
any other person, including sub-licensors of the Licensee or companies
where the Licensee has any involvement. This includes re-working this
specification, or reverse-engineering any products based upon this
specification.

2.4
In case the Licensed Software Developer Kit is modified, it shall not
be published, sold or distributed without agreement of Steinberg.
Furthermore, the naming of the Licensed Software Developer Kit shall
not include “ASIO 2.3 SDK” or any combination containing the VST brand
without permission of Steinberg.

Thanks,
James

signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: giada
Source-Version: 0.12.1~dfsg1-1

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

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

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
giada 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, 17 May 2016 15:54:31 +0200
Source: giada
Binary: giada
Architecture: source
Version: 0.12.1~dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: IOhannes m zmölnig (Debian/GNU) 
Description:
 giada  - Hardcore Loop Machine
Closes: 823318
Changes:
 giada (0.12.1~dfsg1-1) unstable; urgency=medium
 .
   * Imported Upstream version 0.12.1~dfsg1
 * Dropped embedded copy of non-free ASIO SDK in rtaudio-mod
   that had accidentally crept in with 0.11.0 (Closes: #823318)
   * Dropped patches applied upstream.
   * Dropped references to JUCE
   * Bumped to standards version 3.9.8
Checksums-Sha1:
 11736f8f1734d937325639681cd462393c930268 2238 giada_0.12.1~dfsg1-1.dsc
 8c3e2635bdf2570944bb1dccf114ea0b6cd244c5 409154 giada_0.12.1~dfsg1.orig.tar.gz
 8615e377018b08422da9b0b792281853d2939100 9368 
giada_0.12.1~dfsg1-1.debian.tar.xz
Checksums-Sha256:
 1f2841b6826fe7aef75009698a7f701745b692c73e92e8e068a7506a18390baf 2238 
giada_0.12.1~dfsg1-1.dsc
 5368afa3f008a5e6952dce3c0ebc7b314cdb4df198830d1891ea2eb8b2f362cc 409154 
giada_0.12.1~dfsg1.orig.tar.gz
 9bfb2094c651cb4c7304eb52b380938687795017681bae6f33c18a389f05526a 9368 
giada_0.12.1~dfsg1-1.debian.tar.xz
Files:
 f90079fee75e673700bb5ace5a1977b4 2238 sound optional giada_0.12.1~dfsg1-1.dsc
 2abb28ab0e3e700a442b6152d497f72a 409154 sound optional 
giada_0.12.1~dfsg1.orig.tar.gz
 89ab2ee3cb9d5c6737cfcf2d6f14f2cf 9368 sound optional 
giada_0.12.1~dfsg1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXOyRdAAoJELZQG

Processed: tagging 815409, found 815409 in 2.6+dfsg-1

[Debian Bug Tracking System]

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

> tags 815409 + confirmed
Bug #815409 [qemu] qemu-img create -f qcow2 ... segfaults on mips
Added tag(s) confirmed.
> found 815409 2.6+dfsg-1
Bug #815409 [qemu] qemu-img create -f qcow2 ... segfaults on mips
There is no source info for the package 'qemu' at version '2.6+dfsg-1' with 
architecture ''
Unable to make a source version for version '2.6+dfsg-1'
Marked as found in versions 2.6+dfsg-1.
> thanks
Stopping processing here.

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

Bug#824566: python-pyparsing: targetcli 'saveconfig' command does not work

[Kouichi ONO]

Package: python-pyparsing
Version: 2.1.1+dfsg1-1
Severity: serious

Dear Maintainer,

'saveconfig' command of targetcli (in targetcli package) does not work with
python-pyparsing_2.1.1+dfsg1-1_all.deb package.
downgrade to python-pyparsing_2.0.3+dfsg1-1_all.deb fixes problem.

# targetcli / saveconfig
Save configuration? [Y/n]:
Performing backup of startup configuration: 
/var/target/backup-2016-05-18_00:16:59.lio
Saving new startup configuration
Traceback (most recent call last):
  File "/usr/bin/targetcli", line 89, in 
main()
  File "/usr/bin/targetcli", line 78, in main
shell.run_cmdline(" ".join(sys.argv[1:]))
  File "/usr/lib/python2.7/dist-packages/configshell/shell.py", line 934, in 
run_cmdline
self._execute_command(path, command, pparams, kparams)
  File "/usr/lib/python2.7/dist-packages/configshell/shell.py", line 909, in 
_execute_command
result = target.execute_command(command, pparams, kparams)
  File "/usr/lib/python2.7/dist-packages/targetcli/ui_node.py", line 104, in 
execute_command
pparams, kparams)
  File "/usr/lib/python2.7/dist-packages/configshell/node.py", line 1416, in 
execute_command
result = method(*pparams, **kparams)
  File "/usr/lib/python2.7/dist-packages/targetcli/ui_node.py", line 123, in 
ui_command_saveconfig
CliConfig.save_running_config()
  File "/usr/lib/python2.7/dist-packages/targetcli/cli_config.py", line 64, in 
save_running_config
config = Config()
  File "/usr/lib/python2.7/dist-packages/rtslib/config.py", line 133, in 
__init__
self._load_policy()
  File "/usr/lib/python2.7/dist-packages/rtslib/config.py", line 144, in 
_load_policy
parse_tree = self._policy_parser.parse_file(filepath)
  File "/usr/lib/python2.7/dist-packages/rtslib/config_parser.py", line 144, in 
parse_file
return self._parser.parseFile(filepath, parseAll=True).asList()
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 1555, in parseFile
return self.parseString(file_contents, parseAll)
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 1162, in 
parseString
loc, tokens = self._parse( instring, 0 )
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 1028, in 
_parseNoCache
loc,tokens = self.parseImpl( instring, preloc, doActions )
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 2888, in parseImpl
return super(ZeroOrMore, self).parseImpl(instring, loc, doActions)
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 2841, in parseImpl
loc, tokens = self_expr_parse( instring, loc, doActions, callPreParse=False 
)
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 1028, in 
_parseNoCache
loc,tokens = self.parseImpl( instring, preloc, doActions )
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 2719, in parseImpl
return self.expr._parse( instring, loc, doActions, callPreParse=False )
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 1028, in 
_parseNoCache
loc,tokens = self.parseImpl( instring, preloc, doActions )
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 2719, in parseImpl
return self.expr._parse( instring, loc, doActions, callPreParse=False )
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 1028, in 
_parseNoCache
loc,tokens = self.parseImpl( instring, preloc, doActions )
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 2462, in parseImpl
loc, exprtokens = e._parse( instring, loc, doActions )
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 1028, in 
_parseNoCache
loc,tokens = self.parseImpl( instring, preloc, doActions )
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 2576, in parseImpl
ret = e._parse( instring, loc, doActions )
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 1028, in 
_parseNoCache
loc,tokens = self.parseImpl( instring, preloc, doActions )
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 2462, in parseImpl
loc, exprtokens = e._parse( instring, loc, doActions )
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 1028, in 
_parseNoCache
loc,tokens = self.parseImpl( instring, preloc, doActions )
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 2924, in parseImpl
loc, tokens = self.expr._parse( instring, loc, doActions, 
callPreParse=False )
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 1028, in 
_parseNoCache
loc,tokens = self.parseImpl( instring, preloc, doActions )
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 2576, in parseImpl
ret = e._parse( instring, loc, doActions )
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 1028, in 
_parseNoCache
loc,tokens = self.parseImpl( instring, preloc, doActions )
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 2719, in parseImpl
return self.expr._parse( instring, loc, doActions, callPreParse=False )
  File "/usr/lib/python2.7/dist-packages/pyparsing.py", line 1028, in

Bug#823916: fixed in pypy 5.1.1+dfsg-2

[Stefano Rivera]

Hi Emilio (2016.05.17_17:22:58_+0200)
> On Thu, 12 May 2016 22:34:17 + Stefano Rivera  wrote:
> >  pypy (5.1.1+dfsg-2) unstable; urgency=medium
> >  .
> >* Cherry-pick upstream s390x patches, that should (amongst other things) 
> > get
> >  us building on s390x, again. (Closes: #823916)
> 
> You might have noticed it, but in case you missed it, this wasn't sufficient 
> and
> failed to build again.

Different problem. It's just timing out.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Processed: Re: Bug#823916: fixed in pypy 5.1.1+dfsg-2

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #823916 {Done: Stefano Rivera } [src:pypy] pypy: FTBFS 
on s390x
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions pypy/5.1.1+dfsg-2.

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

Bug#823916: fixed in pypy 5.1.1+dfsg-2

[Emilio Pozuelo Monfort]

Control: reopen -1

On Thu, 12 May 2016 22:34:17 + Stefano Rivera  wrote:
>  pypy (5.1.1+dfsg-2) unstable; urgency=medium
>  .
>* Cherry-pick upstream s390x patches, that should (amongst other things) 
> get
>  us building on s390x, again. (Closes: #823916)

You might have noticed it, but in case you missed it, this wasn't sufficient and
failed to build again.

Cheers,
Emilio

Bug#823748: tar: illegal hardware instruction breaks apt-get upgrade

[Lee Garrett]

On 17/05/16 14:21, Vlad Orlov wrote:
> Hi,
> 
> This doesn't happen even in VirtualBox working on a host with an old Core 2 
> Duo
> (both host and guest Debian installations are 64-bit). The upgrade went fine.

This is because your CPU architecture is not 32 bit, and not i586 or lower.
I'm sure if you set that by hand, you will be able to reproduce that.

Processed: tagging 822369

[Debian Bug Tracking System]

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

> tags 822369 - pending
Bug #822369 [xfsprogs] xfsprogs: FTBFS: error: redefinition of 'struct fsxattr'
Bug #822470 [xfsprogs] qemu: FTBFS: error: redefinition of 'struct fsxattr'
Removed tag(s) pending.
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Bug#814316: New Flash player is available -- fixes a security issue

[Bastian Triller]

Package: flashplugin-nonfree
Version: 1:3.6.1+b1
Followup-For: Bug #814316

Dear Maintainer,

Flash Player version installed on this system  : 11.2.202.616
Flash Player version available on upstream site: 11.2.202.621
flash-mozilla.so - auto mode
  link best version is /usr/lib/flashplugin-nonfree/libflashplayer.so
  link currently points to /usr/lib/flashplugin-nonfree/libflashplayer.so
  link flash-mozilla.so is /usr/lib/mozilla/plugins/flash-mozilla.so
/usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50



-- Package-specific info:
Debian version: stretch/sid
Architecture: amd64
Package version: 1:3.6.1+b1
Adobe Flash Player version: LNX 11,2,202,616
MD5 checksums:
160a01dd00527304e5291e65eb0c65e2  
/var/cache/flashplugin-nonfree/get-upstream-version.pl
18271ef4389464f5236e415a8f140872  
/var/cache/flashplugin-nonfree/install_flash_player_11_linux.x86_64.tar.gz
cb4968ab3f52b73a05590ecd87a83bd5  
/usr/lib/flashplugin-nonfree/libflashplayer.so
Alternatives:
flash-mozilla.so - auto mode
  link best version is /usr/lib/flashplugin-nonfree/libflashplayer.so
  link currently points to 
/usr/lib/flashplugin-nonfree/libflashplayer.so
  link flash-mozilla.so is /usr/lib/mozilla/plugins/flash-mozilla.so
/usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50
lrwxrwxrwx 1 root root 34 Aug 18  2015 
/usr/lib/mozilla/plugins/flash-mozilla.so -> /etc/alternatives/flash-mozilla.so
/usr/lib/mozilla/plugins/flash-mozilla.so: symbolic link to 
/etc/alternatives/flash-mozilla.so

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

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

Versions of packages flashplugin-nonfree depends on:
ii  binutils   2.26-9
ii  ca-certificates20160104
ii  debconf [debconf-2.0]  1.5.59
ii  gnupg  1.4.20-6
ii  libatk1.0-02.20.0-1
ii  libcairo2  1.14.6-1+b1
ii  libcurl3-gnutls7.47.0-1
ii  libfontconfig1 2.11.0-6.4
ii  libfreetype6   2.6.3-3+b1
ii  libgcc11:6.1.1-3
ii  libglib2.0-0   2.48.1-1
ii  libgtk2.0-02.24.30-1.1
ii  libnspr4   2:4.12-2
ii  libnss32:3.23-2
ii  libpango1.0-0  1.40.1-1
ii  libstdc++6 6.1.1-3
ii  libx11-6   2:1.6.3-1
ii  libxext6   2:1.3.3-1
ii  libxt6 1:1.1.5-1
ii  wget   1.17.1-2

flashplugin-nonfree recommends no packages.

Versions of packages flashplugin-nonfree suggests:
ii  fonts-dejavu   2.35-1
pn  hal
pn  iceweasel  
pn  konqueror-nsplugins
ii  ttf-mscorefonts-installer  3.6
pn  ttf-xfree86-nonfree

-- no debconf information

Processed: tagging 822369, tagging 823588, tagging 813698, tagging 807006, tagging 823830, tagging 813193 ...

[Debian Bug Tracking System]

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

> tags 822369 + pending
Bug #822369 [xfsprogs] xfsprogs: FTBFS: error: redefinition of 'struct fsxattr'
Bug #822470 [xfsprogs] qemu: FTBFS: error: redefinition of 'struct fsxattr'
Added tag(s) pending.
Added tag(s) pending.
> tags 823588 + pending
Bug #823588 [src:qemu] qemu: FTBFS: xfs_fs.h:42:8: error: redefinition of 
'struct fsxattr'
Added tag(s) pending.
> tags 813698 + pending
Bug #813698 [qemu-user-static] qemu-user-static: qemu-ppc64le-static segfaults 
in ppc64el chroot
Added tag(s) pending.
> tags 807006 + pending
Bug #807006 [qemu] qemu: FTBFS on sparc64 due to incompatible linker parameters
Added tag(s) pending.
> tags 823830 + pending
Bug #823830 [src:qemu] qemu: CVE-2016-3710 CVE-2016-3712
Added tag(s) pending.
> tags 813193 + pending
Bug #813193 [src:qemu] CVE-2016-2198: usb: ehci null pointer dereference in 
ehci_caps_write
Added tag(s) pending.
> tags 813194 + pending
Bug #813194 [src:qemu] CVE-2016-2197: ide: ahci null pointer dereference when 
using FIS CLB engines
Added tag(s) pending.
> tags 815008 + pending
Bug #815008 [src:qemu] qemu: CVE-2016-2392: usb: null pointer dereference in 
remote NDIS control message handling
Added tag(s) pending.
> tags 815009 + pending
Bug #815009 [src:qemu] qemu: CVE-2016-2391: usb: multiple eof_timers in ohci 
leads to null pointer dereference
Added tag(s) pending.
> tags 815680 + pending
Bug #815680 [src:qemu] qemu: CVE-2016-2538: usb: integer overflow in remote 
NDIS control message handling
Added tag(s) pending.
> tags 821038 + pending
Bug #821038 [src:qemu] qemu: CVE-2016-4001: net: buffer overflow in 
stellaris_enet emulator
Added tag(s) pending.
> tags 822344 + pending
Bug #822344 [src:qemu] qemu: CVE-2016-4037: usb: Infinite loop vulnerability in 
usb_ehci using siTD process
Added tag(s) pending.
> tags 817181 + pending
Bug #817181 [src:qemu] qemu: CVE-2016-2841: net: ne2000: infinite loop in 
ne2000_receive
Added tag(s) pending.
> tags 817182 + pending
Bug #817182 [src:qemu] qemu: CVE-2016-2857: net: out of bounds read in 
net_checksum_calculate
Added tag(s) pending.
> tags 817183 + pending
Bug #817183 [src:qemu] qemu: CVE-2016-2858: rng-random: arbitrary stack based 
allocation leading to corruption
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
807006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807006
813193: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813193
813194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813194
813698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813698
815008: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815008
815009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815009
815680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815680
817181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817181
817182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817182
817183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817183
821038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821038
822344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822344
822369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822369
822470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822470
823588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823588
823830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#814316: New Flash player is available -- fixes a security issue

[Bastian Triller]

Package: flashplugin-nonfree
Version: 1:3.6.1+b1
Followup-For: Bug #814316

Dear Maintainer,

please update to new upstream version, which fixes CVE-2016-4117 [1].

Thank you.


[1] https://helpx.adobe.com/security/products/flash-player/apsa16-02.html



-- Package-specific info:
Debian version: stretch/sid
Architecture: amd64
Package version: 1:3.6.1+b1
Adobe Flash Player version: LNX 11,2,202,616
MD5 checksums:
160a01dd00527304e5291e65eb0c65e2  
/var/cache/flashplugin-nonfree/get-upstream-version.pl
18271ef4389464f5236e415a8f140872  
/var/cache/flashplugin-nonfree/install_flash_player_11_linux.x86_64.tar.gz
cb4968ab3f52b73a05590ecd87a83bd5  
/usr/lib/flashplugin-nonfree/libflashplayer.so
Alternatives:
flash-mozilla.so - auto mode
  link best version is /usr/lib/flashplugin-nonfree/libflashplayer.so
  link currently points to 
/usr/lib/flashplugin-nonfree/libflashplayer.so
  link flash-mozilla.so is /usr/lib/mozilla/plugins/flash-mozilla.so
/usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50
lrwxrwxrwx 1 root root 34 Aug 18  2015 
/usr/lib/mozilla/plugins/flash-mozilla.so -> /etc/alternatives/flash-mozilla.so
/usr/lib/mozilla/plugins/flash-mozilla.so: symbolic link to 
/etc/alternatives/flash-mozilla.so

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

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

Versions of packages flashplugin-nonfree depends on:
ii  binutils   2.26-9
ii  ca-certificates20160104
ii  debconf [debconf-2.0]  1.5.59
ii  gnupg  1.4.20-6
ii  libatk1.0-02.20.0-1
ii  libcairo2  1.14.6-1+b1
ii  libcurl3-gnutls7.47.0-1
ii  libfontconfig1 2.11.0-6.4
ii  libfreetype6   2.6.3-3+b1
ii  libgcc11:6.1.1-3
ii  libglib2.0-0   2.48.1-1
ii  libgtk2.0-02.24.30-1.1
ii  libnspr4   2:4.12-2
ii  libnss32:3.23-2
ii  libpango1.0-0  1.40.1-1
ii  libstdc++6 6.1.1-3
ii  libx11-6   2:1.6.3-1
ii  libxext6   2:1.3.3-1
ii  libxt6 1:1.1.5-1
ii  wget   1.17.1-2

flashplugin-nonfree recommends no packages.

Versions of packages flashplugin-nonfree suggests:
ii  fonts-dejavu   2.35-1
pn  hal
pn  iceweasel  
pn  konqueror-nsplugins
ii  ttf-mscorefonts-installer  3.6
pn  ttf-xfree86-nonfree

-- no debconf information

Bug#824560: elpa-ebib: fails to install:

[Andreas Beckmann]

Package: elpa-ebib
Version: 2.5.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package elpa-ebib.
  (Reading database ... 
(Reading database ... 19618 files and directories currently installed.)
  Preparing to unpack .../elpa-ebib_2.5.4-1_all.deb ...
  Unpacking elpa-ebib (2.5.4-1) ...
  Setting up elpa-ebib (2.5.4-1) ...
  Install emacsen-common for emacs24
  emacsen-common: Handling install of emacsen flavor emacs24
  Wrote /etc/emacs24/site-start.d/00debian-vars.elc
  Wrote /usr/share/emacs24/site-lisp/debian-startup.elc
  Install elpa-parsebib for emacs24
  install/parsebib-1.0: Handling install of emacsen flavor emacs24
  install/parsebib-1.0: byte-compiling for emacs24
  Install elpa-ebib for emacs24
  install/ebib-2.5: Handling install of emacsen flavor emacs24
  install/ebib-2.5: byte-compiling for emacs24
  Loading 00debian-vars...
  
  In toplevel form:
  ebib-db.el:43:1:Error: Cannot open load file: No such file or directory, dash
  
  In toplevel form:
  ebib-filters.el:46:1:Error: Cannot open load file: No such file or directory, 
dash
  
  In toplevel form:
  ebib-keywords.el:43:1:Error: Cannot open load file: No such file or 
directory, dash
  Wrote /usr/share/emacs24/site-lisp/elpa/ebib-2.5/ebib-pkg.elc
  
  In toplevel form:
  ebib-utils.el:44:1:Error: Cannot open load file: No such file or directory, 
dash
  
  In toplevel form:
  ebib.el:54:1:Error: Cannot open load file: No such file or directory, dash
  ERROR: install script from elpa-ebib package failed
  dpkg: error processing package elpa-ebib (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   elpa-ebib


cheers,

Andreas


elpa-ebib_2.5.4-1.log.gz
Description: application/gzip

Bug#824553: marked as done (qemu-nbd: devices for partitions are not created)

[Debian Bug Tracking System]

Your message dated Tue, 17 May 2016 16:22:48 +0300
with message-id <573b1b28.5040...@msgid.tls.msk.ru>
and subject line Re: Bug#824553: qemu-nbd: devices for partitions are not 
created
has caused the Debian Bug report #824553,
regarding qemu-nbd: devices for partitions are not created
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.)


-- 
824553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu-utils
Version: 1:2.5+dfsg-5+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

In debian testing weekly build from 2016-04-18 qemu-nbd worked fine, and in 
build from 2016-04-25 it stopped working.

Steps to reproduce:

  qemu-img create -f qcow2 myimg.qcow2 10G
  qemu-system-x86_64 -enable-kvm -hda myimg.qcow2 -cdrom 
debian-testing-amd64-DVD-1.iso -m 256 -boot d
  sudo modprobe nbd max_part=16 # this works OK - /dev/nbd0,1,... devices are 
created
  sudo qemu-nbd -c /dev/nbd0 newcd-qemu.qcow2

Result: there are no /dev/nbd0p* devices.

Maybe this will be useful: when I run "sudo qemu-nbd -c /dev/nbd0 
newcd-qemu.qcow2" again, it prints this:
  /build/qemu-gfZfcR/qemu-2.5+dfsg/nbd.c:nbd_init():L723: Failed to set NBD 
socket
  /build/qemu-gfZfcR/qemu-2.5+dfsg/nbd.c:nbd_receive_request():L857: read failed
But still, no /dev/nbd0p* devices appear.

I did everything absolutely the same as I always did before, but this time it 
did not work.


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

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

Versions of packages qemu-utils depends on:
ii  libaio1   0.3.110-2
ii  libc6 2.22-7
ii  libgcc1   1:5.3.1-14
ii  libglib2.0-0  2.48.0-1
ii  libgnutls30   3.4.10-4
ii  libnettle63.2-1
ii  libuuid1  2.28-1
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages qemu-utils recommends:
ii  sharutils  1:4.15.2-1

Versions of packages qemu-utils suggests:
ii  debootstrap   1.0.80
pn  qemu-block-extra  

-- no debconf information
--- End Message ---
--- Begin Message ---
17.05.2016 15:34, Igor Liferenko wrote:
> Package: qemu-utils
> Version: 1:2.5+dfsg-5+b1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> In debian testing weekly build from 2016-04-18 qemu-nbd worked fine, and in 
> build from 2016-04-25 it stopped working.

It never worked the way you outlined below.

First of all, qemu-nbd does not care about partitions or any other
details of disk images.  The only possible explanation of the
"change" you see between two builds (which are built from the
same source!) is that qemu-nbd stopped working for some reason,
returning wrong data to read requests or failing read requests.
This, ofcourse, will prevent many other things from working,
including reading partition tables within qemu-system-x86_64
guests (as it uses the same code) and other things, and including
qemu-nbd for unpartitioned images.

Second, nbd devices are never made partitionable by kernel by
default.  One has to use other tools, such as kpartx, to enable
partitions for nbd devices.  Nothing changed in qemu about that,
and nothing can ever be changed.

And third, grave, renders package unusable, is way over-estimation,
I use qemu-nbd here quite often, for unpartitioned images too.
And it works quite well for partitioned images, both builds you
mentioned.

So closing the bugreport now.

Thanks,

/mjt

> Steps to reproduce:
> 
>   qemu-img create -f qcow2 myimg.qcow2 10G
>   qemu-system-x86_64 -enable-kvm -hda myimg.qcow2 -cdrom 
> debian-testing-amd64-DVD-1.iso -m 256 -boot d
>   sudo modprobe nbd max_part=16 # this works OK - /dev/nbd0,1,... devices are 
> created
>   sudo qemu-nbd -c /dev/nbd0 newcd-qemu.qcow2
> 
> Result: there are no /dev/nbd0p* devices.
> 
> Maybe this will be useful: when I run "sudo qemu-nbd -c /dev/nbd0 
> newcd-qemu.qcow2" again, it prints this:
>   /build/qemu-gfZfcR/qemu-2.5+dfsg/nbd.c:nbd_init():L723: Failed to set NBD 
> socket
>   /build/qemu-gfZfcR/qemu-2.5+dfsg/nbd.c:nbd_receive_request():L857: read 
> failed
> But still, no /dev/nbd0p* devices appear.
> 
> I did everything absolutely the same as I always did before, but this time it 
> did not work.
> 
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_

Bug#823748: tar: illegal hardware instruction breaks apt-get upgrade

[Vlad Orlov]

Hi,

This doesn't happen even in VirtualBox working on a host with an old Core 2 Duo
(both host and guest Debian installations are 64-bit). The upgrade went fine.

Bug#824553: qemu-nbd: devices for partitions are not created

[Igor Liferenko]

Package: qemu-utils
Version: 1:2.5+dfsg-5+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

In debian testing weekly build from 2016-04-18 qemu-nbd worked fine, and in 
build from 2016-04-25 it stopped working.

Steps to reproduce:

  qemu-img create -f qcow2 myimg.qcow2 10G
  qemu-system-x86_64 -enable-kvm -hda myimg.qcow2 -cdrom 
debian-testing-amd64-DVD-1.iso -m 256 -boot d
  sudo modprobe nbd max_part=16 # this works OK - /dev/nbd0,1,... devices are 
created
  sudo qemu-nbd -c /dev/nbd0 newcd-qemu.qcow2

Result: there are no /dev/nbd0p* devices.

Maybe this will be useful: when I run "sudo qemu-nbd -c /dev/nbd0 
newcd-qemu.qcow2" again, it prints this:
  /build/qemu-gfZfcR/qemu-2.5+dfsg/nbd.c:nbd_init():L723: Failed to set NBD 
socket
  /build/qemu-gfZfcR/qemu-2.5+dfsg/nbd.c:nbd_receive_request():L857: read failed
But still, no /dev/nbd0p* devices appear.

I did everything absolutely the same as I always did before, but this time it 
did not work.


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

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

Versions of packages qemu-utils depends on:
ii  libaio1   0.3.110-2
ii  libc6 2.22-7
ii  libgcc1   1:5.3.1-14
ii  libglib2.0-0  2.48.0-1
ii  libgnutls30   3.4.10-4
ii  libnettle63.2-1
ii  libuuid1  2.28-1
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages qemu-utils recommends:
ii  sharutils  1:4.15.2-1

Versions of packages qemu-utils suggests:
ii  debootstrap   1.0.80
pn  qemu-block-extra  

-- no debconf information

Bug#824550: gr-air-modes build-depends on zeromq which is going to be removed

[Mattia Rizzolo]

source: gr-air-modes
version: 0.0.1.514414f-5
severity: serious
control: block 818998 by -1

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818998

Please work towards removing the build-dependency on zeromq.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: gr-air-modes build-depends on zeromq which is going to be removed

[Debian Bug Tracking System]

Processing control commands:

> block 818998 by -1
Bug #818998 [ftp.debian.org] RM: zeromq -- RoQA; old, superseeded by zeromq3
818998 was blocked by: 818222
818998 was not blocking any bugs.
Added blocking bug(s) of 818998: 824550

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

Bug#784316: Please upgrade to hoauth2

[Mattia Rizzolo]

On Sat, May 23, 2015 at 04:37:44PM -0500, John Goerzen wrote:
> I am super busy right now (taking flying lessons) and will not likely
> have the chance to look at this soon, unfortunately.  I would happily
> accept patches if anybody else has the time to do so.

I wonder, anything happened in the last year?

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#824547: node-css-parse: don't ship in stretch

[Mattia Rizzolo]

Source: node-css-parse
Version: 1.7.0+dfsg-1
Severity: serious

node-css-parse removal has been requested in
https://bugs.debian.org/764944 but can't be processed yet due to rdeps.

Filing this bug so that node-css-parse get out of stretch in the
meantime.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#821576: marked as done (php-geshi: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Tue, 17 May 2016 11:34:01 +
with message-id 
and subject line Bug#821576: fixed in geshi 1.0.8.11-2.1
has caused the Debian Bug report #821576,
regarding php-geshi: PHP 7.0 Transition
to be marked as done.

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

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


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

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

The php-geshi package currently depends on php5 php5-cli .

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

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

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

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

  4. dh_php5 is now dh_php

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

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

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

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

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

So what you need to do:

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

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

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

RM: php-geshi -- ROM; doesn't support PHP 7.0

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

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

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

Cheers, Ondrej

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

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

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUqjXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHRvgP/2pFotSA+UTBU3ZD9gs9hHWe
AVJYwQ/afWbrxsIFIbS6keKm1vtkUv5a8o8syKTBt4NP5LUqvNfp5S7uz1k6HTyu
hqivYTc7alHqgkOkoTNmF80cJj0FymH2ZL2hGJw/PHanrhgpj2GVVstVKgmAlwFx
OBco+2ylLXFUIXUckBhjwWWXatJr61lo7U3Jp31BqgP+2bn1ZKPmh7YYcTuF7T6w
1EF2ExBPuXb62PMlUqLY2NxI75vCWznt0Tc1uX07t4KPwW0oneoIBY7wRWO/tMUc
dZhXHsXmtfall5clDsy/8BWnTS9aW51MrD1kUpg5XUXwszqvFs

Bug#822755: marked as done (kcalc: When launching it nothing happens)

[Debian Bug Tracking System]

Your message dated Tue, 17 May 2016 11:20:51 +
with message-id 
and subject line Bug#822755: fixed in kcalc 4:16.04.1-1
has caused the Debian Bug report #822755,
regarding kcalc: When launching it nothing happens
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.)


-- 
822755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kcalc
Version: 4:15.12.1-1
Severity: grave
Justification: renders package unusable

If you launch it, nothing happens. Even launching in konsole
produce no trace at all.

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

Kernel: Linux 4.4.8 (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 kcalc depends on:
ii  libc6 2.23-0experimental2
ii  libgcc1   1:6.0.1-2
ii  libgmp10  2:6.1.0+dfsg-2
ii  libkf5configcore5 5.19.0-1
ii  libkf5configgui5  5.19.0-1
ii  libkf5configwidgets5  5.19.0-1
ii  libkf5coreaddons5 5.19.0-1
ii  libkf5guiaddons5  5.19.0-1
ii  libkf5i18n5   5.19.0-1
ii  libkf5notifications5  5.19.0-1
ii  libkf5widgetsaddons5  5.19.0-1
ii  libkf5xmlgui5 5.19.0-1
ii  libqt5core5a  5.6.0+dfsg-2
ii  libqt5gui55.6.0+dfsg-2
ii  libqt5widgets55.6.0+dfsg-2
ii  libqt5xml55.6.0+dfsg-2
ii  libstdc++66.0.1-2

kcalc recommends no packages.

kcalc suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: kcalc
Source-Version: 4:16.04.1-1

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

Debian distribution maintenance software
pp.
Maximiliano Curia  (supplier of updated kcalc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 17 May 2016 12:41:05 +0200
Source: kcalc
Binary: kcalc
Architecture: source
Version: 4:16.04.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Maximiliano Curia 
Description:
 kcalc  - simple and scientific calculator
Closes: 822755
Changes:
 kcalc (4:16.04.1-1) unstable; urgency=medium
 .
   [ Automatic packaging ]
   * Bump Standards-Version to 3.9.8
 .
   [ Maximiliano Curia ]
   * New upstream release (15.12.2).
   * New upstream release (16.04.1). (Closes: #822755) Thanks to Eric Valette
 for following this upstream.
   * Add upstream metadata (DEP-12)
   * debian/control: Update Vcs-Browser and Vcs-Git fields
   * Add new libkdeinit5_kcalc lintian-override
Checksums-Sha1:
 4dae5a3ed9824737e6123a9d4daac7bf81094e5b 2354 kcalc_16.04.1-1.dsc
 e1ca79ecae6f54b35c151ff1b127912dc267d01f 83564 kcalc_16.04.1.orig.tar.xz
 22b99060bd34212dff903c5234738731fc1ffdf2 3700 kcalc_16.04.1-1.debian.tar.xz
Checksums-Sha256:
 e52516b0fbefb72b56e2d235b469f50f982096807b10791a0f61ad4a819bd8ec 2354 
kcalc_16.04.1-1.dsc
 ddbf18748c2869d955b255bca9dc7372695bd923b9addd62e26f3a42978d8df2 83564 
kcalc_16.04.1.orig.tar.xz
 0d8c6f727fff54977b98d04bbe0c16b842f710b6a181f41db7ff3d8eb6e3a3b6 3700 
kcalc_16.04.1-1.debian.tar.xz
Files:
 51d46754369b16018d7ae594100f9a48 2354 math optional kcalc_16.04.1-1.dsc
 9200ffe5d8fb71627cbba99de0542741 83564 math optional kcalc_16.04.1.orig.tar.xz
 6f93d35b60f93913295027ba29b045f8 3700 math optional 
kcalc_16.04.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJXOvoEAAoJEMcZdpmymyMqb7cQAJoqkSrKcwCBhaaDGGZ0mHcU
7GoD/TyrQ9ALhbTrjlkUOIToVQuXWpskvnF0xECEpiASA/9/Hjf9WwSS+9Dl2Qd7
orlTnCrg+xbmJKPCDkh12rDU9gV6R7L5wt81ri5nTOnQDb+FWT9PdSlZTK5rVLxM
aayvB74nnImx9AswZTOobaxepgFzlVKzi4HFmpVqtsWH8+QfvJUTQmoltz8IwPih
7DdrAqLhJHmc75pKH9JA4SXbd8IDsDhnHJNA/Vs+Ny0ejB6kMkjjhShfnfNHmSrq
i5pZvWr08tKdvAh/GWoGuHwJrT9aMbLLmZUwmo8COBnSYJn8T9oKPqbxFHzDVZKF
LVq2BGYU2GNBoBuk/O49bi2HiTNQIq/L7FejCB1T8UXPsvTkYlxNRZdVOZ5I7tBp
n9pOEZW9rYYNaJgGE3n+n7d

Bug#821576: php-geshi: PHP 7.0 Transition

[Tanguy Ortolo]

I will try to fix this with an NMU.

--
 ,--.
: /` )   Tanguy Ortolo  
| `-'Debian Developer   
 \_


signature.asc
Description: Digital signature

Processed: Re: Bug#817186: Boobank reveals hidden password

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://symlink.me/issues/945
Bug #817186 [weboob] Boobank reveals hidden password
Set Bug forwarded-to-address to 'https://symlink.me/issues/945'.
> tag -1 patch fixed-upstream
Bug #817186 [weboob] Boobank reveals hidden password
Added tag(s) fixed-upstream and patch.
> severity -1 important
Bug #817186 [weboob] Boobank reveals hidden password
Severity set to 'important' from 'serious'

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

Bug#817186: Boobank reveals hidden password

[Cyril Brulebois]

Control: forwarded -1 https://symlink.me/issues/945
Control: tag -1 patch fixed-upstream
Control: severity -1 important

Hi Bertrand,

Just passing by, wondering about weboob's state and why it isn't in
testing, I've just noticed this RC bug.

Bertrand Marc  (2016-03-08):
> Package: weboob
> version: 1.1-1
> Severity: serious
> 
> Dear developper,
> 
> In the case you configure two backends with boobank, storing the login
> but asking for the password (see attached configuration), boobank
> reveals the second password.
> 
> when you call list, the display is messed up as both backends require a
> password on the same line. To login with success, you need to enter the
> first password (hidden), then validate, and enter the second password
> (not hidden anymore).

I've just checked with upstream, it seems this is already fixed in git
after 1.1 (but no 1.2 release yet); they seem to consider the current
severity a bit too high, so I'm adjusting it along with setting various
tags.


KiBi.


signature.asc
Description: Digital signature

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> archive 803550
Bug #803550 [rsem] rsem: uninstallable on architectures without bowtie
Bug 803550 cannot be archived
> fixed 803550 1.2.30+dfsg-1
Bug #803550 [rsem] rsem: uninstallable on architectures without bowtie
Marked as fixed in versions rsem/1.2.30+dfsg-1.
> thanks
Stopping processing here.

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

Bug#803550: marked as done (rsem: uninstallable on architectures without bowtie)

[Debian Bug Tracking System]

Your message dated Tue, 17 May 2016 11:41:15 +0200
with message-id 

and subject line 
has caused the Debian Bug report #803550,
regarding rsem: uninstallable on architectures without bowtie
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.)


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

Hi,

during a test with piuparts I noticed your package is not
installable in sid on most architectures:

rsem/i386 unsatisfiable Depends: bowtie | bowtie2
rsem/armel unsatisfiable Depends: bowtie | bowtie2
rsem/armhf unsatisfiable Depends: bowtie | bowtie2
rsem/mips unsatisfiable Depends: bowtie | bowtie2
rsem/mipsel unsatisfiable Depends: bowtie | bowtie2
rsem/powerpc unsatisfiable Depends: bowtie | bowtie2
rsem/s390x unsatisfiable Depends: bowtie | bowtie2

since bowtie/bowtie2 is only available on a restricted set of
architectures. This will prevent its migration to testing.


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
This was fixed in 1.2.30+dfsg-1

-- 
Michael R. Crusoe  michael.cru...@gmail.com
Community Engineer Common Workflow Language project
https://impactstory.org/u/-0002-2961-9670   +32 (0) 2 808 25 58
+1 480 627 9108
--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 805678 https://github.com/pchanial/pyoperators/issues/23
Bug #805678 [src:pyoperators] pyoperators: FTBFS: NameError: global name 
'FFTW_DEFAULT_NUM_THREADS' is not defined
Set Bug forwarded-to-address to 
'https://github.com/pchanial/pyoperators/issues/23'.
>
End of message, stopping processing here.

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

Bug#824426: FTBFS against libical2

[Tino Keitel]

On Tue, May 17, 2016 at 09:14:39 +0200, Tino Keitel wrote:

> absolutely. Actually, I have 1.6.1 packages ready for upload.

Sorry, 1.5.1 packages of cause [1].

It's not pushed to the git repository[2] yet, just send me a notice if
someone wants to look into it.

Regards,
Tino

[1] http://tikei.de/debian/syncevolution/

[2] http://anonscm.debian.org/cgit/collab-maint/syncevolution.git

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 820701 https://github.com/Shark-ML/Shark/issues/63
Bug #820701 [src:shark] shark: FTBFS on various architectures - testsuite 
failures
Set Bug forwarded-to-address to 'https://github.com/Shark-ML/Shark/issues/63'.
>
End of message, stopping processing here.

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

Bug#824426: FTBFS against libical2

[Tino Keitel]

On Tue, May 17, 2016 at 09:08:17 +0200, Patrick Ohly wrote:

[...]

> OTOH, Debian itself is still on an old, pre-release version. Tino, do
> you still have plans for getting SyncEvolution updated in Debian?

Hi,

absolutely. Actually, I have 1.6.1 packages ready for upload. I just
wanted to do some more testing regarding SyncML and CalDAV/CardDAV, but
got stuck in too much RL. I'd be glad if someone could do some testing
and confirm that nothing breaks.

Regards,
Tino

Bug#824426: FTBFS against libical2

[Patrick Ohly]

On Mon, 2016-05-16 at 10:59 +0200, Andreas Henriksson wrote:
> Hello!
> 
> Some information below which might be useful
> 
> On Sun, May 15, 2016 at 09:37:24PM +0200, Michael Biebl wrote:
> > Source: syncevolution
> > Version: 1.4.99.4-5
> > Severity: serious
> > 
> > Hi,
> > 
> > during the libical transition [1], your package syncevolution was
> > rebuilt and it now FTBFS:
> [...]
> > src/syncevo/.libs/libsyncevolution.so: undefined reference to
> > `ical_tzid_prefix'
> [...]
> 
> I've quickly looked into this issue since it was discovered
> (sorry I missed spotting it before the transition started).
> 
> The global variable referenced above is indeed gone (in general
> libical seems to be moving away from global variables in 2.0.0
> in favour of accessor methods). The new accessor function to
> get the value is called icaltimezone_tzid_prefix(). See:
> http://sources.debian.net/src/libical/2.0.0-0.4/src/libical/icaltimezone.c/?hl=150#L150
> 
> I looked upstream but there seemed to be very little activity in recent time.

There hasn't been much demand for new features lately, so I consider
SyncEvolution fairly stable and in maintenance now. However, making it
compile on newer systems certainly counts as "maintenance" - I'll look
into it.

The problem for me upstream nowadays is mostly around continuing to
provide pre-compiled binaries for different distros. I got stuck on that
the last time I tried preparing a new release, because distros have
diverged in quite a few relevant libraries now (libical, EDS, even
libopenobex). Perhaps I should just give up on that front.

OTOH, Debian itself is still on an old, pre-release version. Tino, do
you still have plans for getting SyncEvolution updated in Debian?

> The libical2 transition has already been done in fedora so for comparison
> they're patching their syncevolution, see:
> http://pkgs.fedoraproject.org/cgit/rpms/syncevolution.git/tree/syncevolution-1.5.1-libical2.patch
> 
> IMNSHO the fedora patch is an ugly hack since duplicating the information
> instead of using accessor method isn't nice IMO. OTOH I've looked at
> syncevolutions usage of the global variable and if we're going to replace
> it we see it in two places. The one failing the build above + in the
> syncevolution homebrew/duplicated evolution(-data-server?) API.
> That one looks too scary to touch for me who has no way to test this
> so I sympathize with fedoras patch and maybe it's better to go that
> route. Also, the get accessor seems to be missing from the libical2.symbols
> for some reason so might need fixes on the libical side to be properly
> exported

That scary code is needed only when compiling upstream binaries that
must work with different EDS versions. For Debian it might be enough to
just call the accessor method.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.

Bug#823830: qemu: CVE-2016-3710 CVE-2016-3712

[Cristian Aires]

thx

On Tue, May 17, 2016 at 3:40 AM, Geert Stappers 
wrote:

> On Mon, May 16, 2016 at 05:04:29PM -0300, Cristian Aires wrote:
> > On Mon, 09 May 2016 14:22:37 +0200 Salvatore Bonaccorso wrote:
> > >
> > > For further information see:
> > >
> > > [0] https://security-tracker.debian.org/tracker/CVE-2016-3710
> > > [1] https://security-tracker.debian.org/tracker/CVE-2016-3712
> > > [2] http://xenbits.xen.org/xsa/advisory-179.html
> > >
> >
> > All types of video models are affected?
> >
>
> In [2] is a section vulnerable systems, which answers your question.
>
>
> Groeten
> Geert Stappers
>
> P.S.
> Visit https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823830
> to see the noise that is generated by top quoting.
>
> Please reply below the text.
> So make reading in the discussion order possible.
> Thanks.
>



-- 

*Cristian Aires*
Infraestrutura
(51) 3301.1432 - (51) 9994.3218
www.Under.com.br