Bug#828929: cairocffi: FTBFS with gcc-6 and glibc 2.23

[Stefano Rivera]

Hi Jean-Christophe (2016.07.02_11:15:36_-0700)
> I don’t think it has anything to do with gcc/glibc.

I agree. I suggest doing a build with a debug python interpreter, then
you get a very helpful error message:

$ LC_ALL=C.UTF-8 xvfb-run -a --server-args="-screen 0 1024x768x24" python3-dbg 
-m pytest
 test session starts 

platform linux -- Python 3.5.2+, pytest-3.0.2, py-1.4.31, pluggy-0.3.1
rootdir: /build/cairocffi-op2T2E/cairocffi-0.7.2, inifile:
collected 44 items 

cairocffi/test_cairo.py ..
cairocffi/test_pixbuf.py 
cairocffi/test_xcb.py FF

= FAILURES 
==
__ test_xcb_pixmap 
__

xcb_conn = 

def test_xcb_pixmap(xcb_conn):
width = 10
height = 10

# create a new window
wid = create_window(xcb_conn, width, height)
# create the pixmap used to draw with cairo
pixmap = create_pixmap(xcb_conn, wid, width, height)
# create graphics context to copy pixmap on window
gc = create_gc(xcb_conn)

# create XCB surface on pixmap
root_visual = find_root_visual(xcb_conn)
>   surface = XCBSurface(xcb_conn, pixmap, root_visual, width, height)

cairocffi/test_xcb.py:128:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _

self = 
conn = , drawable = 2097153
visual = , width = 10, 
height = 10

def __init__(self, conn, drawable, visual, width, height):
c_visual = visualtype_to_c_struct(visual)

p = cairo.cairo_xcb_surface_create(
>   conn._conn, drawable, c_visual, width, height)
E   TypeError: initializer for ctype 'xcb_connection_t *' appears indeed to 
be 'xcb_connection_t *', but the types are different (check that you are not 
e.g. mixing up different ffi instances)

cairocffi/xcb.py:38: TypeError
__ test_xcb_window 
__

xcb_conn = 

@pytest.mark.xfail(cairo_version() < 11200,
   reason="Cairo version too low")
def test_xcb_window(xcb_conn):
width = 10
height = 10

# create a new window used to draw with cairo
wid = create_window(xcb_conn, width, height)

# map the window and wait for it to appear
xcb_conn.core.MapWindow(wid)
xcb_conn.flush()

start = time.time()
while time.time() < start + 10:
event = xcb_conn.wait_for_event()
if isinstance(event, xcffib.xproto.ExposeEvent):
break
else:
pytest.fail("Never received ExposeEvent")

# create XCB surface on window
root_visual = find_root_visual(xcb_conn)
>   surface = XCBSurface(xcb_conn, wid, root_visual, width, height)

cairocffi/test_xcb.py:192:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _

self = 
conn = , drawable = 2097152
visual = , width = 10, 
height = 10

def __init__(self, conn, drawable, visual, width, height):
c_visual = visualtype_to_c_struct(visual)

p = cairo.cairo_xcb_surface_create(
>   conn._conn, drawable, c_visual, width, height)
E   TypeError: initializer for ctype 'xcb_connection_t *' appears indeed to 
be 'xcb_connection_t *', but the types are different (check that you are not 
e.g. mixing up different ffi instances)

cairocffi/xcb.py:38: TypeError
 2 failed, 42 passed in 0.87 seconds 


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

Bug#836907: src:hidapi-cffi: Missing dependencies on python{3,}-cffi

[Stefano Rivera]

Package: src:hidapi-cffi
Version: 0.2.1-1
Severity: serious
Tags: patch
Justification: Policy 7.2

Upstream only declares

> setup_requires=['cffi >= 0.8']

But that's insufficient, it actually requires cffi at runtime, the first
line is:

> from cffi import FFI

It's worth noting that in Debian we split the cffi package from the
cffi-backend package. We assume that cffi packages are using the
out-of-line modes, and they only need the cffi-backend. So, when a
package declares cffi in install_requires, we generate a dependency on
the cffi-backend package.

But this package is using the in-line ABI mode (see [0] for an
explanation of the modes). So it will need an explicit dependency on
cffi, even if upstream fixes setup.py

[0]: https://cffi.readthedocs.io/en/latest/overview.html

Patch attached: dependencies.patch
Also, I noticed a bunch of things in debian/rules that pybulid can do
for you, so there's a second patch: pybulid.patch.

SR
diff -Nru hidapi-cffi-0.2.1/debian/control hidapi-cffi-0.2.1/debian/control
--- hidapi-cffi-0.2.1/debian/control	2015-06-25 13:35:38.0 -0700
+++ hidapi-cffi-0.2.1/debian/control	2016-09-06 22:04:59.0 -0700
@@ -7,14 +7,14 @@
 
 Package: python-hidapi
 Architecture: any
-Depends: ${misc:Depends}, ${python:Depends}, libhidapi-hidraw0 | libhidapi-libusb0
+Depends: ${misc:Depends}, ${python:Depends}, libhidapi-hidraw0 | libhidapi-libusb0, python-cffi (>= 0.8)
 Description: Python bindings for the HID API
  Python bindings for libhidapi for working with Human Interface Devices
  such as mouses and keyboards.
 
 Package: python3-hidapi
 Architecture: any
-Depends: ${misc:Depends}, ${python3:Depends}, libhidapi-hidraw0 | libhidapi-libusb0
+Depends: ${misc:Depends}, ${python3:Depends}, libhidapi-hidraw0 | libhidapi-libusb0, python3-cffi (>= 0.8)
 Description: Python bindings for the HID API
  Python bindings for libhidapi for working with Human Interface Devices
  such as mouses and keyboards.
diff -Nru hidapi-cffi-0.2.1/debian/clean hidapi-cffi-0.2.1/debian/clean
--- hidapi-cffi-0.2.1/debian/clean	1969-12-31 16:00:00.0 -0800
+++ hidapi-cffi-0.2.1/debian/clean	2016-09-06 22:04:59.0 -0700
@@ -0,0 +1 @@
+hidapi_cffi.egg-info/*
diff -Nru hidapi-cffi-0.2.1/debian/rules hidapi-cffi-0.2.1/debian/rules
--- hidapi-cffi-0.2.1/debian/rules	2015-06-25 13:08:50.0 -0700
+++ hidapi-cffi-0.2.1/debian/rules	2016-09-06 22:04:59.0 -0700
@@ -1,26 +1,6 @@
 #!/usr/bin/make -f
 
-# This file was automatically generated by stdeb 0.8.2 at
-# Thu, 09 Oct 2014 22:55:33 +0300
-PYTHONS:=$(shell pyversions -vr)
-PYTHON3S:=$(shell py3versions -vr)
 export PYBUILD_NAME=hidapi
+
 %:
 	dh $@ --with python2,python3 --buildsystem=pybuild
-
-override_dh_clean:
-	dh_clean -O--buildsystem=pybuild
-	rm -rf build
-	rm -rf __pycache__
-
-override_dh_install:
-	set -e ; for pyvers in $(PYTHONS); do \
-		python$$pyvers setup.py install --install-layout=deb \
-			--root $(CURDIR)/debian/python-hidapi; \
-	done
-	set -e ; for pyvers in $(PYTHON3S); do \
-		python$$pyvers setup.py install --install-layout=deb \
-			--root $(CURDIR)/debian/python3-hidapi; \
-	done
-	rm -rf $(CURDIR)/debian/python*-hidapi/usr/lib/python*/dist-packages/*.pth
-	rm -rf $(CURDIR)/debian/python*-hidapi/usr/lib/python3.*

Bug#836255: marked as done (DTBs are no longer bundled)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2016 04:48:39 +
with message-id 
and subject line Bug#836255: fixed in linux-signed 2.3
has caused the Debian Bug report #836255,
regarding DTBs are no longer bundled
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.)


-- 
836255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 4.7.0-1-armmp-lpae
Severity: important

Hi,

starting with 4.7 the DTBs are not part of the package anymore:

# dpkg -L linux-image-4.5.0-2-armmp-lpae|grep dtb|wc -l
349
# dpkg -L linux-image-4.6.0-1-armmp-lpae|grep dtb|wc -l
363
# dpkg -L linux-image-4.7.0-1-armmp-lpae|grep dtb|wc -l
0

which in return makes flash-kernel fail, and the kernel can not be
properly booted (on devices depending on flash-kernel).
--- End Message ---
--- Begin Message ---
Source: linux-signed
Source-Version: 2.3

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux-signed package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 07 Sep 2016 03:49:45 +0100
Source: linux-signed
Binary: kernel-image-4.7.0-1-amd64-di nic-modules-4.7.0-1-amd64-di 
nic-wireless-modules-4.7.0-1-amd64-di nic-shared-modules-4.7.0-1-amd64-di 
serial-modules-4.7.0-1-amd64-di usb-serial-modules-4.7.0-1-amd64-di 
ppp-modules-4.7.0-1-amd64-di pata-modules-4.7.0-1-amd64-di 
cdrom-core-modules-4.7.0-1-amd64-di firewire-core-modules-4.7.0-1-amd64-di 
scsi-core-modules-4.7.0-1-amd64-di scsi-modules-4.7.0-1-amd64-di 
loop-modules-4.7.0-1-amd64-di btrfs-modules-4.7.0-1-amd64-di 
ext4-modules-4.7.0-1-amd64-di isofs-modules-4.7.0-1-amd64-di 
jfs-modules-4.7.0-1-amd64-di ntfs-modules-4.7.0-1-amd64-di 
xfs-modules-4.7.0-1-amd64-di fat-modules-4.7.0-1-amd64-di 
md-modules-4.7.0-1-amd64-di multipath-modules-4.7.0-1-amd64-di 
usb-modules-4.7.0-1-amd64-di usb-storage-modules-4.7.0-1-amd64-di 
pcmcia-storage-modules-4.7.0-1-amd64-di fb-modules-4.7.0-1-amd64-di 
input-modules-4.7.0-1-amd64-di event-modules-4.7.0-1-amd64-di 
mouse-modules-4.7.0-1-amd64-di nic-pcmcia-modules-4.7.0-1-amd64-di
 pcmcia-modules-4.7.0-1-amd64-di nic-usb-modules-4.7.0-1-amd64-di 
sata-modules-4.7.0-1-amd64-di core-modules-4.7.0-1-amd64-di 
acpi-modules-4.7.0-1-amd64-di i2c-modules-4.7.0-1-amd64-di 
crc-modules-4.7.0-1-amd64-di crypto-modules-4.7.0-1-amd64-di 
crypto-dm-modules-4.7.0-1-amd64-di efi-modules-4.7.0-1-amd64-di 
ata-modules-4.7.0-1-amd64-di mmc-core-modules-4.7.0-1-amd64-di 
mmc-modules-4.7.0-1-amd64-di nbd-modules-4.7.0-1-amd64-di 
squashfs-modules-4.7.0-1-amd64-di speakup-modules-4.7.0-1-amd64-di 
virtio-modules-4.7.0-1-amd64-di uinput-modules-4.7.0-1-amd64-di 
sound-modules-4.7.0-1-amd64-di hyperv-modules-4.7.0-1-amd64-di 
udf-modules-4.7.0-1-amd64-di fuse-modules-4.7.0-1-amd64-di 
linux-image-4.7.0-1-amd64 kernel-image-4.7.0-1-arm64-di 
nic-modules-4.7.0-1-arm64-di nic-wireless-modules-4.7.0-1-arm64-di 
nic-shared-modules-4.7.0-1-arm64-di ppp-modules-4.7.0-1-arm64-di 
cdrom-core-modules-4.7.0-1-arm64-di scsi-core-modules-4.7.0-1-arm64-di 
scsi-modules-4.7.0-1-arm64-di
 loop-modules-4.7.0-1-arm64-di btrfs-modules-4.7.0-1-arm64-di 
ext4-modules-4.7.0-1-arm64-di isofs-modules-4.7.0-1-arm64-di 
jfs-modules-4.7.0-1-arm64-di xfs-modules-4.7.0-1-arm64-di 
fat-modules-4.7.0-1-arm64-di md-modules-4.7.0-1-arm64-di 
multipath-modules-4.7.0-1-arm64-di usb-modules-4.7.0-1-arm64-di 
usb-storage-modules-4.7.0-1-arm64-di fb-modules-4.7.0-1-arm64-di 
input-modules-4.7.0-1-arm64-di event-modules-4.7.0-1-arm64-di 
nic-usb-modules-4.7.0-1-arm64-di sata-modules-4.7.0-1-arm64-di 
core-modules-4.7.0-1-arm64-di i2c-modules-4.7.0-1-arm64-di 
crc-modules-4.7.0-1-arm64-di crypto-modules-4.7.0-1-arm64-di 
crypto-dm-modules-4.7.0-1-arm64-di efi-modules-4.7.0-1-arm64-di 
ata-modules-4.7.0-1-arm64-di mmc-modules-4.7.0-1-arm64-di 
nbd-modules-4.7.0-1-arm64-di squashfs-modules-4.7.0-1-arm64-di 

Bug#836904: Depend eatmydata is unused and undesirable on productive systems

[Jörg Frings-Fürst]

Source: vsftpd
Version: 3.0.3-6
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

since 3.0.3-6 depends vsftpd on libeatmydata.

- - eatmydata is never used in vsftd:
$ grep -r eatmy *
debian/control: libeatmydata1,
debian/changelog:  * Add libeatmydata1 in package Depends
- - the (planed) use of eatmydata causes data lose.

CU
Jörg



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

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

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXz5EHAAoJEAn4nzyModJdO1sP/289u9F7Bj8tlRRSjAYCqX59
5uo0+tRuyJh8oXgnUOxURq/0ILeXEr+c1yjyHYKSx8qLr6+rBrf7s7rxSz/PYcgr
EDpJT405lcnqwfMdJamkYHBbK65CC7KrWZJb+tBE7P9YCbrMhR9cWajovBLSxjKA
L+rbcSpd8lsYSrYCCxdEE6D8ATs0WF2I/9Gd3FcQVPgSuBgvU32oNYRS1XCZ6iU0
wkh7C8glxAYOJy/I/DyzpRYMs3ZA6/6P2HJGoXPFIY1j1f3YzcUx1LSy1QXyA4Bf
girX8uC53E8HlDQOYzFzGJPnFXZvjRMVaQjJVsxxsOGehl83pCJbW1gD90vmZ9WO
Vk9ikdtWeWlRAhYcM7AnHSmWy3JfXfdgFUFrWkVG6darU3NdYJzHLCW/1aVTbWDV
9M6zivOMJu3VpbvB8ZAQUPwsHGoDELyf1kj7qWCZOd+I9bhRaDO4IjHnnKcSy1n4
IuAMfX4q+84kgVGwBCsxT1tBt1n7tideiLobcpF/24id56Cwxld3JAP7KpYw13x/
IBSp0itHADcKim6Ne0hS01UwWmRYgbcna0OJH//DuysqtpHR9OyrK+N/ANbYe1XA
vrDWCFm22bXqVt3SzFk70iyWwCMN60e/Xjg2uz1sFbrDF3emtXJG8G0wLmIcqIty
/MoXXROgRF9ze+IdR2yh
=u2wQ
-END PGP SIGNATURE-

Bug#834833: marked as done (javassist: FTBFS too much often (failing tests))

[Debian Bug Tracking System]

Your message dated Wed, 7 Sep 2016 05:27:04 +0200
with message-id <8b0d4f20-a6f6-db68-6216-4302c8c29...@debian.org>
and subject line Re: Bug#834833: marked as done (javassist: FTBFS too much 
often (failing tests))
has caused the Debian Bug report #834833,
regarding javassist: FTBFS too much often (failing tests)
to be marked as done.

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

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


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

Dear maintainer:

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

A diff between a successful build and a failed build shows this:

--
Tests run: 376, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 20.789 sec 
<<< FAILURE! - in javassist.JvstTest
testJIRA150(javassist.JvstTest4)  Time elapsed: 0.711 sec  <<< FAILURE!
junit.framework.AssertionFailedError: 326 < 3 * 79
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at javassist.JvstTest4.testJIRA150(JvstTest4.java:666)


Results :

Failed tests: 
  javassist.JvstTest4#testJIRA150 AssertionFailedError 326 < 3 * 79

Tests run: 376, Failures: 1, Errors: 0, Skipped: 0
--

So apparently there are some tests based on performance.

If that's the case, such tests must be disabled, as it's not written
anywhere that the performance of any given autobuilder will remain
constant during the package build.

Thanks.
--- End Message ---
--- Begin Message ---
Version: 1:3.20.0-2

On Fri, 02 Sep 2016 19:59:41 -0400 Harlan Lieberman-Berg
 wrote:
> On September 2, 2016 7:27:11 PM EDT, ow...@bugs.debian.org wrote:
> >Your message dated Fri, 02 Sep 2016 23:25:14 +
> >with message-id 
> >and subject line Bug#834833: fixed in python-certbot 0.8.1-3
> >has caused the Debian Bug report #834833,
> >regarding javassist: FTBFS too much often (failing tests)
> >to be marked as done.
> >
> >This means that you claim that the problem has been dealt with.
> >If this is not the case it is now your responsibility to reopen the
> >Bug report if necessary, and/or fix the problem forthwith.
> >
> >(NB: If you are a system administrator and have no idea what this
> >message is talking about, this may indicate a serious mail system
> >misconfiguration somewhere. Please contact ow...@bugs.debian.org
> >immediately.)
> 
> reopen 834833
> notfixed 834833 0.8.1-3
> thanks
> 
> Whoops, looks like I got the bug number wrong. Sorry about that.
> -- 
> Harlan Lieberman-Berg
> ~hlieberman

Hello Harlan,

this bug was already fixed and closed. I'm going to close it again.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#833501: fixed in chromium-browser 52.0.2743.116-2

[Jean-Francois Pirus]

I can confirm it's still happening in 53.0.2785.92-2

Thread 33 "Chrome_InProcRe" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff4b7fe700 (LWP 13286)]
0x58837c85 in 
blink::LayoutObject::isDescendantOf(blink::LayoutObject const*) const ()

(gdb) bt
#0  0x58837c85 in 
blink::LayoutObject::isDescendantOf(blink::LayoutObject const*) const ()
#1  0x588b93bc in 
blink::CompositedLayerMapping::containingSquashedLayer(blink::LayoutObject 
const*, WTF::Vector const&, unsigned int) ()
#2  0x58936b8b in 
blink::CompositingLayerAssigner::getReasonsPreventingSquashing(blink::PaintLayer 
const*, blink::CompositingLayerAssigner::SquashingState const&) [clone 
.part.27] ()
#3  0x58937b0e in 
blink::CompositingLayerAssigner::assignLayersToBackingsInternal(blink::PaintLayer*, 
blink::CompositingLayerAssigner::SquashingState&, 
WTF::Vector&) ()
#4  0x58937811 in 
blink::CompositingLayerAssigner::assignLayersToBackingsInternal(blink::PaintLayer*, 
blink::CompositingLayerAssigner::SquashingState&, 
WTF::Vector&) ()
#5  0x58937811 in 
blink::CompositingLayerAssigner::assignLayersToBackingsInternal(blink::PaintLayer*, 
blink::CompositingLayerAssigner::SquashingState&, 
WTF::Vector&) ()
#6  0x58937bf1 in 
blink::CompositingLayerAssigner::assign(blink::PaintLayer*, 
WTF::Vector&) ()

#7  0x588bfc79 in blink::PaintLayerCompositor::updateIfNeeded() ()
#8  0x588c10be in 
blink::PaintLayerCompositor::updateIfNeededRecursiveInternal() ()
#9  0x588c12fc in 
blink::PaintLayerCompositor::updateIfNeededRecursive() ()
#10 0x584210b5 in 
blink::FrameView::updateLifecyclePhasesInternal(blink::DocumentLifecycle::LifecycleState) 
()
#11 0x58561b1d in 
blink::PageAnimator::updateAllLifecyclePhases(blink::LocalFrame&) ()

#12 0x578c1a5a in blink::WebViewImpl::updateAllLifecyclePhases() ()
#13 0x59b871b3 in 
content::RenderWidgetCompositor::UpdateLayerTreeHost() ()
#14 0x5a72b3d1 in 
cc::ProxyMain::BeginMainFrame(std::unique_ptr

Processed: Re: Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #834744 [src:xmlgraphics-commons] xmlgraphics-commons: FTBFS (missing 
build-depends on gnupg)
Severity set to 'normal' from 'serious'

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

Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

[Markus Koschany]

Control: severity -1 normal

On 07.09.2016 01:25, Santiago Vila wrote:
> severity 834744 serious
> tags 834744 - unreproducible
> thanks
> 
> Sorry, but missing build-dependencies are RC, and they have always been.
> 
> 
> On Mon, 22 Aug 2016, Markus Koschany wrote:
> 
>> This package builds fine in a clean cowbuilder chroot environment
> 
> No, it does not. If the chroot environment includes gnupg, then
> it's *not* a clean chroot.
> 
> To reproduce, please build in a chroot *not* having gnupg installed.
> 
> If you can't do that with cowbuilder, try sbuild.
> 
> I attach a full build log.
> 
> Please attach also your build log made with sbuild in a chroot *not*
> having gnupg installed, so that we can compare.
> 
> If you can't reproduce a bug you should ask the submitter for a way
> to reproduce it, not silently downgrade the bug and mark it as
> unreproducible without telling the submitter.
> 
> Moreover, the bug report clearly said "missing build-depends" (it is
> in the subject and it's difficult to miss) and it even included a
> patch. Are you really unable to reproduce it, or you just "don't want"
> to reproduce it?
> 
> Thanks.

I disagree with your bug severity. The build does not fail in a clean
cowbuilder environment. I'm attaching my build log as proof. This _may_
still be a bug but with a lower severity and as long as the build does
not fail in a _clean_ and commonly accepted build environment as
cowbuilder, it is not a release critical issue. Of course the release
team can still decide otherwise and feel free to contact them or the
CTTE if you continue to disagree with the maintainer's decision.
However, as I have told you before, it is not your prerogative to
overrule maintainer decisions.

You should rather work towards defining a common build environment
standard in Debian instead of filing individual bug reports against
packages that fail in _your_ specific environment. You should also
consider reassigning this bug against either cowbuilder or sbuild.

Regards,

Markus


dpkg-buildpackage: info: source package xmlgraphics-commons
dpkg-buildpackage: info: source version 2.1-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Mathieu Malaterre 
 dpkg-source --before-build xmlgraphics-commons-2.1
 fakeroot debian/rules clean
dh clean --with javahelper
   dh_testdir
   debian/rules override_dh_auto_clean
make[1]: Entering directory 
'/home/apo/src/java/build-area/xmlgraphics-commons-2.1'
# Drop any linked in deps for testing
mh_clean
rm -f lib/*.jar
dh_auto_clean
ant clean
Buildfile: /home/apo/src/java/build-area/xmlgraphics-commons-2.1/build.xml

clean:

BUILD SUCCESSFUL
Total time: 0 seconds
rm -f xmlgraphics-commons-*-bundle.jar
make[1]: Leaving directory 
'/home/apo/src/java/build-area/xmlgraphics-commons-2.1'
   jh_clean
   dh_clean
 dpkg-source -b xmlgraphics-commons-2.1
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building xmlgraphics-commons using existing 
./xmlgraphics-commons_2.1.orig.tar.gz
dpkg-source: info: building xmlgraphics-commons in 
xmlgraphics-commons_2.1-1.debian.tar.xz
dpkg-source: info: building xmlgraphics-commons in xmlgraphics-commons_2.1-1.dsc
 dpkg-genchanges --build=source >../xmlgraphics-commons_2.1-1_source.changes
dpkg-genchanges: info: including full source code in upload
 dpkg-source --after-build xmlgraphics-commons-2.1
dpkg-buildpackage: info: full upload (original source is included)
ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
 -> Copying COW directory
  forking: rm -rf /var/cache/pbuilder/build/cow.23777 
  forking: cp -al /var/cache/pbuilder/base-sid-amd64.cow 
/var/cache/pbuilder/build/cow.23777 
I: removed stale ilistfile /var/cache/pbuilder/build/cow.23777/.ilist
  forking: chroot /var/cache/pbuilder/build/cow.23777 cowdancer-ilistcreate 
/.ilist find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a 
-links +1 -print0 \) | xargs -0 stat --format '%d %i ' 
 -> Invoking pbuilder
  forking: pbuilder build --debbuildopts  --debbuildopts  --buildplace 
/var/cache/pbuilder/build/cow.23777 --buildresult /home/apo/src/java/build-area 
--extrapackages eatmydata ccache --no-targz --internal-chrootexec chroot 
/var/cache/pbuilder/build/cow.23777 cow-shell 
/home/apo/src/java/build-area/xmlgraphics-commons_2.1-1.dsc 
I: Running in no-targz mode
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Wed Sep  7 04:30:16 CEST 2016
I: pbuilder-time-stamp: 1473215416
I: copying local configuration
I: mounting /proc filesystem
I: mounting /sys filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /home/apo/reprepro
I: policy-rc.d already exists
W: no hooks of type H found -- ignoring
I: Obtaining the cached apt archive contents
I: Installing the build-deps
I: user script 

Bug#775541: NFS mounts fail at boot after Debian 8.5 upgrade

[paul . szabo]

Dear Vincent,

> Could you provide a bit more information about the package versions
> on your system?
> dpkg -l rpcbind nfs-common nfs-kernel-server systemd

psz@como:~$ dpkg -l rpcbind nfs-common nfs-kernel-server systemd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version   
Architecture  Description
+++-=-=-=-===
ii  nfs-common1:1.2.8-9 i386
  NFS support files common to client and server
ii  nfs-kernel-server 1:1.2.8-9 i386
  support for NFS kernel server
ii  rpcbind   0.2.1-6+deb8u1i386
  converts RPC program numbers into universal addresses
ii  systemd   215-17+deb8u4.psz i386
  system and service manager

The systemd packages are my "own", with my (trivial!) patches as per
https://bugs.debian.org/803013

> Also I think the output of these commands would be helpful
> systemd-analyze critical-path remote-fs-pre.target
> systemd-analyze critical-path nfs-kernel-server.service

I think you meant critical-chain:

psz@como:~$ systemd-analyze critical-chain remote-fs-pre.target
...
remote-fs-pre.target @98ms


psz@como:~$ systemd-analyze critical-chain nfs-kernel-server.service
...
nfs-kernel-server.service +223ms
  basic.target @4.819s
timers.target @4.818s
  systemd-tmpfiles-clean.timer @4.818s
sysinit.target @4.816s
  console-setup.service @4.813s +1ms
kbd.service @4.753s +58ms
  system.slice @108ms
-.slice @103ms

Cheers, Paul

Processed: Re: Bug#833930: gitk: display shot, application usability gone

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #833930 [gitk] gitk: display shot, application usability gone
Added tag(s) moreinfo.
> severity -1 normal
Bug #833930 [gitk] gitk: display shot, application usability gone
Severity set to 'normal' from 'grave'

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

Bug#833930: gitk: display shot, application usability gone

[Anders Kaseorg]

Control: tags -1 + moreinfo
Control: severity -1 normal

I tried to reproduce this by installing a fresh jessie VM in virt-manager 
with debian-live-8.5.0-amd64-xfce-desktop.iso, installing gitk, then 
upgrading the VM to stretch in two parts (apt upgrade; apt full-upgrade), 
then rebooting.  I did not observe a gitk display problem at any point 
during, between, or after these steps.

Do you have a detailed recipe for reliably reproducing this, ideally 
starting from a known state such as a live CD?

Perhaps that is hard, but at least we can distinguish between a user 
configuration issue and a system configuration issue: can you reproduce on 
the same system under a freshly created account?

Anders

Bug#775541: NFS mounts fail at boot after Debian 8.5 upgrade

[Vincent McIntyre]

Hello Paul

I read your feedback on this issue with interest.
Could you provide a bit more information about the package versions
on your system?

dpkg -l rpcbind nfs-common nfs-kernel-server systemd

Also I think the output of these commands would be helpful

systemd-analyze critical-path remote-fs-pre.target
systemd-analyze critical-path nfs-kernel-server.service

As to your question about After=rpcbind.service vs rpcbind.target,
I think rpcbind.target is correct as you're trying to express
that you want mounting remote filesystems to wait until everything
to do with getting rpcbind going is complete. But I'm far from sure.

Kind regards
Vince

Bug#832852: marked as done (gnome-keyring: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2016 01:03:33 +
with message-id 
and subject line Bug#832852: fixed in gnome-keyring 3.20.0-3
has caused the Debian Bug report #832852,
regarding gnome-keyring: FTBFS: Tests failures
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> Makefile:5960: recipe for target 'test-asn1.log' failed
> make[6]: Leaving directory '/«PKGBUILDDIR»'
> make[5]: *** [check-TESTS] Error 2
> Makefile:5939: recipe for target 'check-TESTS' failed
> make[5]: Leaving directory '/«PKGBUILDDIR»'
> make[4]: *** [check-am] Error 2
> Makefile:6593: recipe for target 'check-am' failed
> make[4]: Leaving directory '/«PKGBUILDDIR»'
> make[3]: *** [check-recursive] Error 1
> Makefile:5719: recipe for target 'check-recursive' failed
> make[3]: Leaving directory '/«PKGBUILDDIR»'
> make[2]: *** [check] Error 2
> Makefile:6596: recipe for target 'check' failed
> make[2]: Leaving directory '/«PKGBUILDDIR»'
> make[1]: *** [override_dh_auto_test] Error 2
> debian/rules:23: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/28/gnome-keyring_3.20.0-2_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated gnome-keyring package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Sep 2016 02:08:35 +0200
Source: gnome-keyring
Binary: gnome-keyring libpam-gnome-keyring
Architecture: source
Version: 3.20.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Michael Biebl 
Description:
 gnome-keyring - GNOME keyring services (daemon and tools)
 libpam-gnome-keyring - PAM module to unlock the GNOME keyring upon login
Closes: 832852 835885
Changes:
 gnome-keyring (3.20.0-3) unstable; urgency=medium
 .
   [ Jeremy Bicha ]
   * Enable parallel building and all hardening flags
   * Add debian/patches/05_skip-known-test-failures.patch:
 - Skip a few failing tests that have already been reported upstream.
   Before the switch from cdbs to dh, these tests still failed but did
   not fail the build and therefore were mostly unnoticed.
   * Explicitly Build-Depend on python for tests (Closes: #832852)
 .
   [ Dmitry Shachnev ]
   * Depend on default-dbus-session-bus | dbus-session-bus instead of
 dbus-x11 (closes: #835885).
Checksums-Sha1:
 72831049e2a5b4e11496f68f0974a15694dc6553 2497 gnome-keyring_3.20.0-3.dsc
 0a6127cb9aa0fffa3189bf476000594ea05ab7d0 17340 
gnome-keyring_3.20.0-3.debian.tar.xz
Checksums-Sha256:
 294a467db93fb3c77a7899a9aefe5da818bb3c56a36d05f7ca3022e480690b16 2497 
gnome-keyring_3.20.0-3.dsc
 8eae0325f93b59608d9939253edbc7f8ed14afdc0bb210a855217cfd1f549580 17340 
gnome-keyring_3.20.0-3.debian.tar.xz
Files:
 2ce7246e0ccc959fe8f41326fc174892 2497 gnome optional gnome-keyring_3.20.0-3.dsc
 4541a87b3888a8638d86bd532bb22053 17340 gnome optional 
gnome-keyring_3.20.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#836669: Caja crashes on my computer too.

[Laszlo KERTESZ]

I have Testing/Stretch on 2 computers, on both Caja is crashing after the
recent libgtk3 updates. I downloaded the sources and compiled it myself, it
still crashes.

dmesg:

caja[19781]: segfault at 7ffc177e3d18 ip 7fe3b627f7b6 sp
7ffc177e3d10 error 6 in libc-2.23.so[7fe3b6245000+197000]

gdb trace for the  debian repo version (it repeats):

Thread 1 "caja" received signal SIGSEGV, Segmentation fault.
__GI_strtod_l_internal (nptr=0x7f0bc0b3c21d "10",
endptr=0x7fff8baea170,
group=0, loc=0x7f0bbdd06b60 <_nl_C_locobj>) at strtod_l.c:481
481 strtod_l.c: No such file or directory.
#0  __GI_strtod_l_internal (nptr=0x7f0bc0b3c21d "10",
endptr=0x7fff8baea170, group=0, loc=0x7f0bbdd06b60 <_nl_C_locobj>)
at strtod_l.c:481
#1  0x7f0bbffc60fe in ?? ()
   from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
#2  0x7f0bbffc77a1 in pango_font_description_from_string ()
   from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
#3  0x7f0bc07f22d0 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#4  0x7f0bbf08036b in g_type_create_instance ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5  0x7f0bbf06220b in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6  0x7f0bbf06411e in g_object_new_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x7f0bbf0643c1 in g_object_new ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x7f0bc07f8656 in gtk_widget_get_style ()
   from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#9  0x55c10b82b77b in ?? ()
#10 0x55c10b82bf5b in ?? ()
#11 0x7f0bbf060010 in g_cclosure_marshal_VOID__OBJECTv ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x7f0bbf05d102 in ?? ()
 from /usr/lib/x86_64-linux-gnu/libgobject-2.0.soQuit
#0  __GI_strtod_l_internal (nptr=0x7f0bc0b3c21d "10",
endptr=0x7fff8baea170, group=0, loc=0x7f0bbdd06b60 <_nl_C_locobj>)
at strtod_l.c:481
#1  0x7f0bbffc60fe in ?? ()
   from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
#2  0x7f0bbffc77a1 in pango_font_description_from_string ()
   from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
#3  0x7f0bc07f22d0 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#4  0x7f0bbf08036b in g_type_create_instance ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5  0x7f0bbf06220b in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6  0x7f0bbf06411e in g_object_new_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x7f0bbf0643c1 in g_object_new ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x7f0bc07f8656 in gtk_widget_get_style ()
   from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#9  0x55c10b82b77b in ?? ()
#10 0x55c10b82bf5b in ?? ()
#11 0x7f0bbf060010 in g_cclosure_marshal_VOID__OBJECTv ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x7f0bbf05d102 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x7f0bbf0778dd in g_signal_emit_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x7f0bbf077fcf in g_signal_emit ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x7f0bc0af2883 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#16 0x7f0bc07f8666 in gtk_widget_get_style ()
   from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#17 0x55c10b82b77b in ?? ()
#18 0x55c10b82bf5b in ?? ()
#19 0x7f0bbf060010 in g_cclosure_marshal_VOID__OBJECTv ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#20 0x7f0bbf05d102 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#21 0x7f0bbf0778dd in g_signal_emit_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#22 0x7f0bbf077fcf in g_signal_emit ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#23 0x7f0bc0af2883 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#24 0x7f0bc07f8666 in gtk_widget_get_style ()
   from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#25 0x55c10b82b77b in ?? ()
#26 0x55c10b82bf5b in ?? ()

gdb for the version i compiled from 1.14.2-1 sources :

Thread 1 "caja" received signal SIGSEGV, Segmentation fault.
__GI_strtod_l_internal (nptr=0x75e1021d "10",
endptr=0x7f7ff420, group=0, loc=0x73025b60 <_nl_C_locobj>)
at strtod_l.c:481
481 strtod_l.c: No such file or directory.
#0  __GI_strtod_l_internal (nptr=0x75e1021d "10",
endptr=0x7f7ff420, group=0, loc=0x73025b60 <_nl_C_locobj>)
at strtod_l.c:481
#1  0x752a70fe in ?? () from
/usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
#2  0x752a87a1 in pango_font_description_from_string () from
/usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
#3  0x75ac62d0 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#4  0x7437c36b in g_type_create_instance () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5  0x7435e20b in ?? () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6  0x7436011e in 

Bug#811604: marked as done (FTBFS with GCC 6: statement indented as if it were guarded by)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2016 00:04:05 +
with message-id 
and subject line Bug#811604: fixed in crash 7.1.5-2
has caused the Debian Bug report #811604,
regarding FTBFS with GCC 6: statement indented as if it were guarded by
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.)


-- 
811604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: crash
Version: 7.1.4-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-misleading-indentation

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I. -I. -I./../include 
> -DHAVE_bfd_elf64_x86_64_vec -DHAVE_bfd_elf32_i386_vec 
> -DHAVE_bfd_elf32_x86_64_vec -DHAVE_i386linux_vec -DHAVE_i386pei_vec 
> -DHAVE_x86_64pei_vec -DHAVE_bfd_elf64_l1om_vec -DHAVE_bfd_elf64_k1om_vec 
> -DHAVE_bfd_elf64_little_generic_vec -DHAVE_bfd_elf64_big_generic_vec 
> -DHAVE_bfd_elf32_little_generic_vec -DHAVE_bfd_elf32_big_generic_vec 
> -DBINDIR=\"/usr/local/bin\" -Wdate-time -D_FORTIFY_SOURCE=2 -W -Wall 
> -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Werror -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -MT pei-i386.lo -MD 
> -MP -MF .deps/pei-i386.Tpo -c pei-i386.c -o pei-i386.o
> In file included from pei-i386.c:46:0:
> coff-i386.c: In function 'coff_i386_reloc':
> coff-i386.c:144:5: error: statement is indented as if it were guarded by... 
> [-Werror=misleading-indentation]
>  if (diff != 0)
>  ^~
> 
> coff-i386.c:135:3: note: ...this 'if' clause, but it is not
>if (reloc_entry->howto->type == R_IMAGEBASE
>^~
> 
> cc1: all warnings being treated as errors
> Makefile:1607: recipe for target 'pei-i386.lo' failed
> make[8]: *** [pei-i386.lo] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: crash
Source-Version: 7.1.5-2

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

Debian distribution maintenance software
pp.
Troy Heber  (supplier of updated crash 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, 06 Sep 2016 15:20:09 -0600
Source: crash
Binary: crash
Architecture: source amd64
Version: 7.1.5-2
Distribution: unstable
Urgency: medium
Maintainer: Troy Heber 
Changed-By: Troy Heber 
Description:
 crash  - kernel debugging utility, allowing gdb like syntax
Closes: 811604
Changes:
 crash (7.1.5-2) unstable; urgency=medium
 .
   * Forgot to close bug in the last upload (Closes: #811604)
Checksums-Sha1:
 98df0fe05f5d88539045b51b1e73d6b465f7d63f 1845 crash_7.1.5-2.dsc
 6bcb4a62b9e27a3b6cf671a7740ed1fa906cf120 100258 crash_7.1.5-2.diff.gz
 465419edc5d0e426e7089a33d086480e166191bc 13013086 
crash-dbgsym_7.1.5-2_amd64.deb
 bd98643875e4ba852e07e8c6c528a20d662a1025 2610698 crash_7.1.5-2_amd64.deb
Checksums-Sha256:
 9f70472cc0e47edd3c15ca4b602cd1164c61c2a3515e369a5e614d0f81d38994 1845 
crash_7.1.5-2.dsc
 390a119d346fc36610a5fa20344893e7f0e069b4f411d1df28bf819f1e54fd9f 100258 
crash_7.1.5-2.diff.gz
 ec24085495e3dfaea38915d3496eb1ef79580fb6c80e4dca9035395e8ada9060 13013086 
crash-dbgsym_7.1.5-2_amd64.deb
 f3050b99921a987ec99acc38618c89d9924e06bca5f999f45f031c4f07956fd6 2610698 
crash_7.1.5-2_amd64.deb
Files:
 8fdcdaec7001a64ef30f723b19e3adb6 1845 utils optional crash_7.1.5-2.dsc
 38846f032c7cabf2038901f23ea62d7e 100258 utils optional crash_7.1.5-2.diff.gz
 c79368bd89c77cc3b081d07e9a8652e9 13013086 debug extra 
crash-dbgsym_7.1.5-2_amd64.deb
 22fd13d4348b303c5a9db082c837c309 2610698 utils optional 

Bug#835708: [NMU] Re: Bug#835708: plplot: FTBFS: Tests failures

[Axel Beckert]

Dear Andrew,

Axel Beckert wrote:
> make[1]: Leaving directory 
> '/build/plplot-5.10.0+dfsg2/debian/build_tmp/bindings/qt_gui/pyqt4'
> touch install-python2.7
> touch install-python
> dh_movefiles -a --no-package=libplplot12 --no-package=libplplot-dev \
>  --no-package=python-plplot --no-package=python-plplot-qt   \
>  --no-package=libplplot-java --no-package=libplplot-ada1 \
>  --no-package=libplplot-ocaml --no-package=libplplot-lua \
>  --no-package=libplplot-d --no-package=libplplot-ada1-dev
> dh_movefiles --package=python-plplot-qt
> dh_movefiles --package=python-plplot
> dh_movefiles --package=libplplot-java
> dh_movefiles --package=libplplot-ocaml
> dh_movefiles: debian/tmp/usr/lib/ocaml/plcairo/META not found (supposed to 
> put it in libplplot-ocaml)
> debian/rules:147: recipe for target 'install-arch' failed
> make: *** [install-arch] Error 1
> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
> 2
> 
> So it seems as if the issue is somewhere in the ocaml bindings.

It seems as if the files for /usr/lib/ocaml/plcairo/ are no more built
for a reason unknown to me and independent of plplot. The remaining
libraries to be put into the libplplot-ocaml are still build.

Since /usr/lib/ocaml/plcairo/ seems to be only one part of the
libplplot-ocaml package and the remaining part looks functioning
without it, I decided to sacrifice that half of libplplot-ocaml to fix
the FTBFS and hence save all reverse dependencies from being removed
from testing. (libplplot-ocaml seems to have no reverse dependencies
not built from the plplot source package.)

After this mail, I'll upload an according fix as NMU to DELAYED/2.
Full source debdiff and libplplot-ocaml binary debdiff following. Feel
free to tell me to fast-forward or delay the upload a little bit more.

diff -Nru plplot-5.10.0+dfsg2/debian/changelog 
plplot-5.10.0+dfsg2/debian/changelog
--- plplot-5.10.0+dfsg2/debian/changelog2016-08-03 21:18:45.0 
+0200
+++ plplot-5.10.0+dfsg2/debian/changelog2016-09-07 01:29:02.0 
+0200
@@ -1,3 +1,11 @@
+plplot (5.10.0+dfsg2-0.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable installation of /usr/lib/ocaml/plcairo/ as it seems to no more
+be built. (Fixes FTBFS and hence closes: #835708)
+
+ -- Axel Beckert   Wed, 07 Sep 2016 01:29:02 +0200
+
 plplot (5.10.0+dfsg2-0.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru plplot-5.10.0+dfsg2/debian/libplplot-ocaml.files 
plplot-5.10.0+dfsg2/debian/libplplot-ocaml.files
--- plplot-5.10.0+dfsg2/debian/libplplot-ocaml.files2015-10-06 
23:58:30.0 +0200
+++ plplot-5.10.0+dfsg2/debian/libplplot-ocaml.files2016-09-07 
01:17:17.0 +0200
@@ -3,8 +3,8 @@
 usr/lib/ocaml/plplot/*.a
 usr/lib/ocaml/plplot/*.cm*
 usr/lib/ocaml/plplot/*.ml*
-usr/lib/ocaml/plcairo/META
-usr/lib/ocaml/plcairo/*.a
-usr/lib/ocaml/plcairo/*.cm*
-usr/lib/ocaml/plcairo/*.ml*
+#usr/lib/ocaml/plcairo/META
+#usr/lib/ocaml/plcairo/*.a
+#usr/lib/ocaml/plcairo/*.cm*
+#usr/lib/ocaml/plcairo/*.ml*
 usr/share/doc/libplplot-ocaml

[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in first .deb but not in second
-
-rw-r--r--  root/root   /usr/lib/ocaml/plcairo/META
-rw-r--r--  root/root   /usr/lib/ocaml/plcairo/libplcairo_stubs.a
-rw-r--r--  root/root   /usr/lib/ocaml/plcairo/plcairo.a
-rw-r--r--  root/root   /usr/lib/ocaml/plcairo/plcairo.cma
-rw-r--r--  root/root   /usr/lib/ocaml/plcairo/plcairo.cmi
-rw-r--r--  root/root   /usr/lib/ocaml/plcairo/plcairo.cmxa
-rw-r--r--  root/root   /usr/lib/ocaml/plcairo/plcairo.mli
-rw-r--r--  root/root   /usr/lib/ocaml/stublibs/dllplcairo_stubs.so

Control files: lines which differ (wdiff format)

Depends: libplplot12 (>= 5.10.0+dfsg2), ocaml-base-nox-4.02.3, libc6 (>= 
[-2.14), libcairo2 (>= 1.2.4)-] {+2.14)+}
Installed-Size: [-625-] {+531+}
Version: [-5.10.0+dfsg2-0.3-] {+5.10.0+dfsg2-0.4+}

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


signature.asc
Description: Digital signature

Processed: tagging 835708

[Debian Bug Tracking System]

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

> # NMU ahead
> tags 835708 + pending
Bug #835708 [src:plplot] plplot: FTBFS: Tests failures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: warzone2100: FTBFS when newer automake is installed

[Debian Bug Tracking System]

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

> reassign 835910 src:warzone2100
Bug #835910 [warzone2100] warzone2100: FTBFS when newer automake is installed
Bug reassigned from package 'warzone2100' to 'src:warzone2100'.
No longer marked as found in versions warzone2100/3.1.1-3.
Ignoring request to alter fixed versions of bug #835910 to the same values 
previously set
> found 835910 3.1.1-3
Bug #835910 [src:warzone2100] warzone2100: FTBFS when newer automake is 
installed
Marked as found in versions warzone2100/3.1.1-3.
> forcemerge 835910 824011
Bug #835910 [src:warzone2100] warzone2100: FTBFS when newer automake is 
installed
Bug #824011 [src:warzone2100] warzone2100: FTBFS in testing (maybe missing 
Build-Conflicts)
Severity set to 'serious' from 'normal'
Added tag(s) upstream.
Merged 824011 835910
> thanks
Stopping processing here.

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

Bug#835910: warzone2100: FTBFS when newer automake is installed

[Santiago Vila]

reassign 835910 src:warzone2100
found 835910 3.1.1-3
forcemerge 835910 824011
thanks

On Mon, 29 Aug 2016, Russell Coker wrote:

> Package: warzone2100
> Version: 3.1.1-3
> Severity: serious
> Tags: upstream patch
> Justification: fails to build from source (but built successfully in the past)
> 
> The warzone2100 build system insists on automake and aclocal version 1.11.  If
> you have 1.15 installed it won't build.

I already reported this as Bug#824011 and suggested using a Build-Conflicts.

You probably didn't see the bug because the maintainer downgraded to "normal".

Maybe I'm not the only one to think that FTBFS bugs are RC, after all.

Thanks.

Processed: Re: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

[Debian Bug Tracking System]

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

> severity 834744 serious
Bug #834744 [src:xmlgraphics-commons] xmlgraphics-commons: FTBFS (missing 
build-depends on gnupg)
Severity set to 'serious' from 'normal'
> tags 834744 - unreproducible
Bug #834744 [src:xmlgraphics-commons] xmlgraphics-commons: FTBFS (missing 
build-depends on gnupg)
Removed tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#811602: marked as done (FTBFS with GCC 6: multiple errors)

[Debian Bug Tracking System]

Your message dated Tue, 06 Sep 2016 22:36:13 +
with message-id 
and subject line Bug#811602: fixed in sword 1.7.3+dfsg-8
has caused the Debian Bug report #811602,
regarding FTBFS with GCC 6: multiple errors
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.)


-- 
811602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sword
Version: 1.7.3+dfsg-7
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-misleading-indentation gcc-6-address

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> /usr/bin/c++   -DCLUCENE2 -DCURLAVAILABLE -DCURLSFTPAVAILABLE 
> -DGLOBCONFPATH=\"/etc/sword.conf\" -DUSELUCENE -D_FTPLIB_NO_COMPAT -D_ICU_ 
> -I/<>/sword-1.7.3+dfsg/obj-x86_64-linux-gnu/include 
> -I/<>/sword-1.7.3+dfsg/include -I/usr/lib/x86_64-linux-gnu 
> -I/usr/include/x86_64-linux-gnu  -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Werror -Wno-error=deprecated-declarations 
> -Wdate-time -D_FORTIFY_SOURCE=2-fPIC -o 
> CMakeFiles/sword_static.dir/src/mgr/remotetrans.cpp.o -c 
> /<>/sword-1.7.3+dfsg/src/mgr/remotetrans.cpp
> /usr/bin/c++   -DCLUCENE2 -DCURLAVAILABLE -DCURLSFTPAVAILABLE 
> -DGLOBCONFPATH=\"/etc/sword.conf\" -DUSELUCENE -D_FTPLIB_NO_COMPAT -D_ICU_ 
> -Dsword_EXPORTS -I/<>/sword-1.7.3+dfsg/obj-x86_64-linux-gnu/include 
> -I/<>/sword-1.7.3+dfsg/include -I/usr/lib/x86_64-linux-gnu 
> -I/usr/include/x86_64-linux-gnu  -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Werror -Wno-error=deprecated-declarations 
> -Wdate-time -D_FORTIFY_SOURCE=2  -fPIC   -o 
> CMakeFiles/sword.dir/src/mgr/encfiltmgr.cpp.o -c 
> /<>/sword-1.7.3+dfsg/src/mgr/encfiltmgr.cpp
> /<>/sword-1.7.3+dfsg/src/keys/treekeyidx.cpp: In member function 
> 'virtual void sword::TreeKeyIdx::remove()':
> /<>/sword-1.7.3+dfsg/src/keys/treekeyidx.cpp:264:7: error: 
> statement is indented as if it were guarded by... 
> [-Werror=misleading-indentation]
>if (iterator.next > -1) {
>^~
> 
> /<>/sword-1.7.3+dfsg/src/keys/treekeyidx.cpp:262:6: note: ...this 
> 'while' clause, but it is not
>   while ((iterator.next != target) && (iterator.next > -1))
>   ^
> 
> /<>/sword-1.7.3+dfsg/src/keys/treekeyidx.cpp: In member function 
> 'virtual void sword::TreeKeyIdx::remove()':
> /<>/sword-1.7.3+dfsg/src/keys/treekeyidx.cpp:264:7: error: 
> statement is indented as if it were guarded by... 
> [-Werror=misleading-indentation]
>if (iterator.next > -1) {
>^~
> 
> /<>/sword-1.7.3+dfsg/src/keys/treekeyidx.cpp:262:6: note: ...this 
> 'while' clause, but it is not
>   while ((iterator.next != target) && (iterator.next > -1))
>   ^
> 
> In file included from /<>/sword-1.7.3+dfsg/include/swkey.h:28:0,
>  from /<>/sword-1.7.3+dfsg/include/treekey.h:27,
>  from /<>/sword-1.7.3+dfsg/include/treekeyidx.h:27,
>  from 
> /<>/sword-1.7.3+dfsg/src/keys/treekeyidx.cpp:24:
> /<>/sword-1.7.3+dfsg/src/keys/treekeyidx.cpp: In member function 
> 'virtual int sword::TreeKeyIdx::compare(const sword::SWKey&)':
> /<>/sword-1.7.3+dfsg/include/swobject.h:30:128: error: the compiler 
> can assume that the address of 'ikey' will always evaluate to 'true' 
> [-Werror=address]
>  #define SWDYNAMIC_CAST(className, object) (className 
> *)((object)?((object->getClass()->isAssignableFrom(#className))?object:0):0)
>   
>   ^
> 
> /<>/sword-1.7.3+dfsg/src/keys/treekeyidx.cpp:575:24: note: in 
> expansion of macro 'SWDYNAMIC_CAST'
>   TreeKeyIdx *treeKey = SWDYNAMIC_CAST(TreeKeyIdx, ());
> ^~
> 
> In file included from /<>/sword-1.7.3+dfsg/include/swkey.h:28:0,
>  from /<>/sword-1.7.3+dfsg/include/treekey.h:27,
>  from /<>/sword-1.7.3+dfsg/include/treekeyidx.h:27,
>  from 
> /<>/sword-1.7.3+dfsg/src/keys/treekeyidx.cpp:24:
> /<>/sword-1.7.3+dfsg/src/keys/treekeyidx.cpp: In member function 
> 'virtual int sword::TreeKeyIdx::compare(const 

Bug#833815: marked as done (qmhandle: FTBFS when built with dpkg-buildpackage -A (binary build with no binary artifacts))

[Debian Bug Tracking System]

Your message dated Tue, 06 Sep 2016 22:34:07 +
with message-id 
and subject line Bug#833815: fixed in qmhandle 1.3.2-2
has caused the Debian Bug report #833815,
regarding qmhandle: FTBFS when built with dpkg-buildpackage -A (binary build 
with no binary artifacts)
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.)


-- 
833815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qmhandle
Version: 1.3.2-1
User: sanv...@debian.org
Usertags: arch-all-swapped-binary-targets
Severity: serious

Dear maintainer:

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


[...]
 fakeroot debian/rules binary-indep
dh_testdir
dh_testroot
dh_clean -k
dh_clean: dh_clean -k is deprecated; use dh_prep instead
dh_installdirs
# Add here commands to install the package into debian/qmhandle.
install -m755 qmHandle debian/qmhandle/usr/bin/
mv debian/qmhandle/usr/bin/qmHandle debian/qmhandle/usr/bin/qmhandle
 dpkg-genchanges --build=all >../qmhandle_1.3.2-1_all.changes
dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
distribute
dpkg-buildpackage: error: dpkg-genchanges gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is usually a sign that the binary-arch and binary-indep targets of
debian/rules are just swapped.

Note: I'm reporting this as "serious" after getting the ok from the release
managers. See Bug #830997 for details.

Once that "dpkg-buildpackage -A" work properly, the package would be
suitable to be uploaded in source-only form if you wish.

Thanks.
--- End Message ---
--- Begin Message ---
Source: qmhandle
Source-Version: 1.3.2-2

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

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

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

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated qmhandle 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, 06 Sep 2016 21:08:30 +0100
Source: qmhandle
Binary: qmhandle
Architecture: source
Version: 1.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Santiago Vila 
Description:
 qmhandle   - tool to manage the qmail message queue
Closes: 833815
Changes:
 qmhandle (1.3.2-2) unstable; urgency=medium
 .
   * QA upload.
   * Switch to dh. Closes: #833815.
   * Switch to "3.0 (quilt)" source format.
   * Package is orphaned (Bug #738913), set maintainer to "Debian QA Group".
   * Drop copy of GPL license from the doc directory.
   * Raise debhelper compat level to 9.
Checksums-Sha1:
 f32463c8351630db472863b4dd6aad0d70ab41cb 1313 qmhandle_1.3.2-2.dsc
 edc9b731743266ddfbb6d72d65c726b2e7dc1056 1884 qmhandle_1.3.2-2.debian.tar.xz
Checksums-Sha256:
 55ed8712135dba7cbceccd431a92634ee6e12d0cd32da570ebdce9b0e2acab2a 1313 
qmhandle_1.3.2-2.dsc
 9803525ec6734dc899e66623ea097d1e62a0b58ac5f69b08b05b208e2f7c80d3 1884 
qmhandle_1.3.2-2.debian.tar.xz
Files:
 b484b71a05fdb1dd20a2fa1f84d1cb20 1313 contrib/mail optional 
qmhandle_1.3.2-2.dsc
 4206615db4fca11be7d4ba3f9a30f8e4 1884 contrib/mail optional 
qmhandle_1.3.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJXzyJjAAoJEEHOfwufG4syuSsIAJDUAZNbsFtxteI1wp0niqgS
CWwXyJyDHChBKMBlFrXbJLE17xnrTxcgyimIdfsIlICBgU2pZECiGho+Rnxve3ev
96j5MOW3NLfg91cYA2RQqHIDcB9EEIvJaYCmu6GZVNFz7jE/SHFBZjkpeBfJEYMk
qKFyBcCGCD3ekWl2MGFwXR9VygfpJBckjtxl+HRrfbdv/Jr4P0zN5ipocgL5k3be
FguctuPIiBqsWt5XABvhmwQbl1UGdeMbZuJHckD/pOcrfsHywFXZk7ZbpiAxp90L
79NH9C5eix1VFPg2pyo0A4H3vYnPqjxE3IArhVihaD/VnUPedYwelZJuGIVMVK8=
=8eEg
-END PGP SIGNATURE End Message ---

Bug#796298: tcplay: FTBFS: CMake Error at CMakeLists.txt:30 (message): Could not find the devmapper library

[Michael Prokop]

* László Böszörményi [Wed Aug 26, 2015 at 07:28:02AM +0200]:
> On Fri, Aug 21, 2015 at 10:10 AM, Chris Lamb  wrote:

> >   CMake Error at CMakeLists.txt:30 (message):
> > Could not find the devmapper library

> > From a cursory glance, devmapper.pc specifies Requires.Private librt,
> > which doesn't have a  librt.pc (which is likely correct as it's meant to
> > be linked statically? I'll leave it to you).

>  You are right in the sense that without 'Requires.private:' the
> devmapper library is found correctly. On the other hand I don't think
> static linking is mandatory as libdevmapper.so.* exists and is under
> /lib (no need to have /usr mounted, can be used in emergency shells as
> well). Can be a cmake issue? Will investigate further.

Any news here, László? I'm asking because this is an RC bug and
therefore preventing tcplay to enter Debian/stretch.

This issue was also reported towards upstream:

  https://github.com/bwalex/tc-play/issues/50

I was trying to reproduce it, though couldn't:

| -- Checking for module 'devmapper'
| --   Found devmapper, version 1.02.133

Instead if fails with:

| /usr/bin/cc  -fPIC -g -O2 -fdebug-prefix-map=/build/tcplay-1.1=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security  -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wdate-time -D_FORTIFY_SOURCE=2   
-Wl,--version-script=/build/tcplay-1.1/tcplay.map  -fPIE -pie -Wl,-z,relro 
-Wl,-z,now  -shared -Wl,-soname,libtcplay.so.1.1 -o libtcplay.so.1.1 
CMakeFiles/tcplay-so.dir/tcplay_api.c.o CMakeFiles/tcplay-so.dir/tcplay.c.o 
CMakeFiles/tcplay-so.dir/crc32.c.o CMakeFiles/tcplay-so.dir/safe_mem.c.o 
CMakeFiles/tcplay-so.dir/io.c.o CMakeFiles/tcplay-so.dir/hdr.c.o 
CMakeFiles/tcplay-so.dir/humanize.c.o CMakeFiles/tcplay-so.dir/crypto.c.o 
CMakeFiles/tcplay-so.dir/generic_xts.c.o 
CMakeFiles/tcplay-so.dir/crypto-gcrypt.c.o 
CMakeFiles/tcplay-so.dir/pbkdf2-gcrypt.c.o -ldevmapper -luuid -lgcrypt 
-lgpg-error 
| /usr/bin/ld: CMakeFiles/tcplay-so.dir/tcplay.c.o: relocation R_X86_64_PC32 
against symbol `stderr@@GLIBC_2.2.5' can not be used when making a shared 
object; recompile with -fPIC
| /usr/bin/ld: final link failed: Bad value
| collect2: error: ld returned 1 exit status

when compiling against current Debian/unstable. It looks like that's
an issue of static vs dynamic library linking. When replacing:

  set (CFLAGS_COMMON "-std=c99 -fPIE ${CFLAGS_LINUX} ${CFLAGS_WARN} 
${CFLAGS_VER}")

in CMakeLists.txt with (so adding the '-fPIC' option there):

  set (CFLAGS_COMMON "-std=c99 -fPIE -fPIC ${CFLAGS_LINUX} ${CFLAGS_WARN} 
${CFLAGS_VER}")

it indeed compiles for me.
Can you please take care of an according fixed package upload?

regards,
-mika-


signature.asc
Description: Digital signature

Bug#835980: marked as done (triggerhappy: FTBFS: evtable_SW.inc:17:8: error: array index in initializer exceeds array bounds)

[Debian Bug Tracking System]

Your message dated Tue, 06 Sep 2016 22:36:21 +
with message-id 
and subject line Bug#835980: fixed in triggerhappy 0.5.0-1
has caused the Debian Bug report #835980,
regarding triggerhappy: FTBFS: evtable_SW.inc:17:8: error: array index in 
initializer exceeds array bounds
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.)


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

triggerhappy fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  triggerhappy
   Version:  0.4.0-2
   Build architecture:   amd64
   Date: Mon, 29 Aug 2016 18:12:30 +0100
   Hostname: 664a26da6444
   Uname:Linux 664a26da6444 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 
(2016-07-18) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'triggerhappy-build-deps' in 
'../triggerhappy-build-deps_0.4.0-2_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package triggerhappy-build-deps.
  (Reading database ... 23302 files and directories currently installed.)
  Preparing to unpack triggerhappy-build-deps_0.4.0-2_all.deb ...
  Unpacking triggerhappy-build-deps (0.4.0-2) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
libsystemd-dev pkg-config
  The following NEW packages will be installed:
libsystemd-dev pkg-config
  0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 287 kB of archives.
  After this operation, 827 kB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 pkg-config amd64 
0.29-4 [62.5 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 libsystemd-dev amd64 
231-5 [224 kB]
  Fetched 287 kB in 0s (22.8 MB/s)
  Selecting previously unselected package pkg-config.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23306 files and directories currently installed.)
  Preparing to unpack .../0-pkg-config_0.29-4_amd64.deb ...
  Unpacking pkg-config (0.29-4) ...
  Selecting previously unselected package libsystemd-dev:amd64.
  Preparing to unpack .../1-libsystemd-dev_231-5_amd64.deb ...
  Unpacking libsystemd-dev:amd64 (231-5) ...
  Setting up pkg-config (0.29-4) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up libsystemd-dev:amd64 (231-5) ...
  Setting up triggerhappy-build-deps (0.4.0-2) ...
  
  
**
  ** Environment
  **
  
**
  
  

Processed: re: gearhead: FTBFS with -fdebug-prefix-map

[Debian Bug Tracking System]

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

> Severity 831797 serious
Bug #831797 [gearhead] gearhead: FTBFS with -fdebug-prefix-map
Severity set to 'serious' from 'important'
> tags 831797 +patch
Bug #831797 [gearhead] gearhead: FTBFS with -fdebug-prefix-map
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#831926: marked as done (cadubi: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute)

[Debian Bug Tracking System]

Your message dated Tue, 06 Sep 2016 22:19:42 +
with message-id 
and subject line Bug#831926: fixed in cadubi 1.3-3
has caused the Debian Bug report #831926,
regarding cadubi: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: 
binary build with no binary artifacts found; cannot distribute
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.)


-- 
831926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cadubi
Version: 1.3-2
Severity: important
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160720 qa-ftbfs qa-indep
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.  This rebuild was done by building only the architecture-independent
packages.  At the same time, a normal build succeeded, which points the
problem specifically to build-indep/binary-indep targets.


The specific error below usually happens there is a binary-indep target in
debian/rules which is either empty or does not do anything useful.

If all the arch-independent packages are dummy transitional packages released
with jessie, the easy fix is to drop them now. If not, debian/rules should be
modified so that the binary-indep target generates the architecture independent
packages (and only those).

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

I file this bug as severity: important, but Santiago Vila, who led this
effort (kudos to him), got approval from the release team to consider those
bugs RC for stretch. The severity will be increased to 'serious' shortly.
See #830997 for details.

Relevant part (hopefully):
>  fakeroot debian/rules binary-indep
> dh_testdir
> dh_testroot
> dh_clean -k
> dh_clean: dh_clean -k is deprecated; use dh_prep instead
> dh_installdirs
> # Add here commands to install the package into debian/cadubi.
> #/usr/bin/make install DESTDIR=`pwd`/debian/cadubi
> install -m755 cadubi debian/cadubi/usr/bin/
> install -m664 logo.txt help.txt debian/cadubi/usr/share/cadubi/
>  dpkg-genchanges --build=all >../cadubi_1.3-2_all.changes
> dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
> distribute

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/20/cadubi_1.3-2_unstable_archallonly.log

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

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

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

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated cadubi 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, 06 Sep 2016 21:04:00 +0100
Source: cadubi
Binary: cadubi
Architecture: source
Version: 1.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Santiago Vila 
Description:
 cadubi - Creative ASCII Drawing Utility By Ian
Closes: 831926
Changes:
 cadubi (1.3-3) unstable; urgency=medium
 .
   * QA upload.
   * Switch to dh. Closes: #831926.
   * Switch to "3.0 (quilt)" source format.
   * Package is orphaned (Bug #738912), set maintainer to "Debian QA Group".
   * Raise debhelper compat level to 9.
   * Use UTF-8 in README.Debian and copyright.
Checksums-Sha1:
 5f12baf60a581138d4b74d3a191240df053848ef 1277 cadubi_1.3-3.dsc
 4e399762f8c674fb8f992c5bdc8955c5308dfc11 5372 cadubi_1.3-3.debian.tar.xz
Checksums-Sha256:
 

Processed: Re: test-suite failures on 32bit architectures

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #826035 [src:gnome-keyring] test-suite failures on 32bit architectures
Severity set to 'important' from 'serious'

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

Bug#826035: test-suite failures on 32bit architectures

[Jeremy Bicha]

Control: severity -1 important

As discussed on IRC, I'm lowering the severity to not block the
migration of the updated package to testing. These tests have been
failing for a while now but probably no one noticed because test
failures didn't fail the build until we converted to dh. The test
failures have been reported upstream.

Thanks,
Jeremy

Bug#833501: found in 53.0.2785.92-2

[Gedalya]

fixed 833501 52.0.2743.116-2
found 833501 53.0.2785.92-2
thanks


now that we're back with gcc 6, same crashes occur with facebook, google maps 
and other sites.

This got it working for me

--- rules.orig2016-09-06 15:44:51.692191414 -0400
+++ rules2016-09-06 15:47:29.097229998 -0400
@@ -16,6 +16,10 @@
 export CFLAGS+=-fuse-ld=gold
 export CXXFLAGS+=-fuse-ld=gold
 
+# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68853
+export CFLAGS+=-fno-delete-null-pointer-checks
+export CXXFLAGS+=-fno-delete-null-pointer-checks
+
 # treat all warnings as errors
 defines=werror=
 

Processed: Bug#833501: found in 53.0.2785.92-2

[Debian Bug Tracking System]

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

> fixed 833501 52.0.2743.116-2
Bug #833501 [chromium] Aw snap while using Facebook
Bug #833506 [chromium] chromium: Crashes when browsing Google Maps
Bug #833524 [chromium] chromium: Aw Snap! after update to new in sid / even 
when purged and installed as clean
Bug #833542 [chromium] chromium: Crashes all the time after last update
Marked as fixed in versions chromium-browser/52.0.2743.116-2.
Marked as fixed in versions chromium-browser/52.0.2743.116-2.
Marked as fixed in versions chromium-browser/52.0.2743.116-2.
Marked as fixed in versions chromium-browser/52.0.2743.116-2.
> found 833501 53.0.2785.92-2
Bug #833501 [chromium] Aw snap while using Facebook
Bug #833506 [chromium] chromium: Crashes when browsing Google Maps
Bug #833524 [chromium] chromium: Aw Snap! after update to new in sid / even 
when purged and installed as clean
Bug #833542 [chromium] chromium: Crashes all the time after last update
Ignoring request to alter found versions of bug #833501 to the same values 
previously set
Ignoring request to alter found versions of bug #833506 to the same values 
previously set
Ignoring request to alter found versions of bug #833524 to the same values 
previously set
Ignoring request to alter found versions of bug #833542 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: Bug#833501: found in 53.0.2785.92-2

[Debian Bug Tracking System]

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

> unarchive 833501
Bug #833501 {Done: Michael Gilbert } [chromium] Aw snap 
while using Facebook
Bug #833506 {Done: Michael Gilbert } [chromium] chromium: 
Crashes when browsing Google Maps
Bug #833524 {Done: Michael Gilbert } [chromium] chromium: 
Aw Snap! after update to new in sid / even when purged and installed as clean
Bug #833542 {Done: Michael Gilbert } [chromium] chromium: 
Crashes all the time after last update
Unarchived Bug 833501
Unarchived Bug 833506
Unarchived Bug 833524
Unarchived Bug 833542
> reopen 833501
Bug #833501 {Done: Michael Gilbert } [chromium] Aw snap 
while using Facebook
Bug #833506 {Done: Michael Gilbert } [chromium] chromium: 
Crashes when browsing Google Maps
Bug #833524 {Done: Michael Gilbert } [chromium] chromium: 
Aw Snap! after update to new in sid / even when purged and installed as clean
Bug #833542 {Done: Michael Gilbert } [chromium] chromium: 
Crashes all the time after last update
'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 chromium-browser/52.0.2743.116-2.
No longer marked as fixed in versions chromium-browser/52.0.2743.116-2.
No longer marked as fixed in versions chromium-browser/52.0.2743.116-2.
No longer marked as fixed in versions chromium-browser/52.0.2743.116-2.
> found 833501  53.0.2785.92-2
Bug #833501 [chromium] Aw snap while using Facebook
Bug #833506 [chromium] chromium: Crashes when browsing Google Maps
Bug #833524 [chromium] chromium: Aw Snap! after update to new in sid / even 
when purged and installed as clean
Bug #833542 [chromium] chromium: Crashes all the time after last update
Marked as found in versions chromium-browser/53.0.2785.92-2.
Marked as found in versions chromium-browser/53.0.2785.92-2.
Marked as found in versions chromium-browser/53.0.2785.92-2.
Marked as found in versions chromium-browser/53.0.2785.92-2.
> thanks
Stopping processing here.

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

Bug#836706: certificate spoofing via crafted SASL messages

[Guillaume Delacour]

Please see attached the debdiff.
Also, please note that i can't upload myself to security-master as i'm
not a DD nor DM.

Le 06/09/2016 à 00:02, Guillaume Delacour a écrit :
> 
> 
> Le 05/09/2016 à 22:41, James Lu a écrit :
>> Hi,
> 
> Hi,
> 
>>
>> Just to narrow things down a bit, the relevant fix for InspIRCd 2.0 is
>> this commit
>> https://github.com/inspircd/inspircd/commit/74fafb7f11b06747f69f182ad5e3769b665eea7a
> 
> Yes, i've talked to upstream a few hours ago to include this particular
> fix to 2.0.17; upload of 2.0.23 will follow to unstable.
> 
>>
>> Best,
>> James
>>
> 

-- 
Guillaume Delacour


diff -Nru inspircd-2.0.17/debian/changelog inspircd-2.0.17/debian/changelog
--- inspircd-2.0.17/debian/changelog2016-03-22 19:31:22.0 +0100
+++ inspircd-2.0.17/debian/changelog2016-09-06 21:29:13.0 +0200
@@ -1,3 +1,10 @@
+inspircd (2.0.17-1+deb8u2) jessie-security; urgency=high
+
+  * m_sasl: don't allow AUTHENTICATE with mechanisms with a space
+(CVE-2016-7142)
+
+ -- Guillaume Delacour   Tue, 06 Sep 2016 01:58:19 +0200
+
 inspircd (2.0.17-1+deb8u1) jessie-security; urgency=high
 
   * Non-maintainer upload by the Wheezy LTS Team. 
diff -Nru inspircd-2.0.17/debian/patches/CVE-2016-7142.patch 
inspircd-2.0.17/debian/patches/CVE-2016-7142.patch
--- inspircd-2.0.17/debian/patches/CVE-2016-7142.patch  1970-01-01 
01:00:00.0 +0100
+++ inspircd-2.0.17/debian/patches/CVE-2016-7142.patch  2016-09-06 
21:29:13.0 +0200
@@ -0,0 +1,31 @@
+From 74fafb7f11b06747f69f182ad5e3769b665eea7a Mon Sep 17 00:00:00 2001
+From: Adam 
+Date: Fri, 2 Sep 2016 22:57:03 -0400
+Subject: [PATCH] m_sasl: don't allow AUTHENTICATE with mechanisms with a space
+
+---
+ src/modules/m_sasl.cpp | 4 
+ 1 file changed, 4 insertions(+)
+
+diff --git a/src/modules/m_sasl.cpp b/src/modules/m_sasl.cpp
+index 9cb5592..16a1535 100644
+--- a/src/modules/m_sasl.cpp
 b/src/modules/m_sasl.cpp
+@@ -189,6 +189,7 @@ class CommandAuthenticate : public Command
+   : Command(Creator, "AUTHENTICATE", 1), authExt(ext), cap(Cap)
+   {
+   works_before_reg = true;
++  allow_empty_last_param = false;
+   }
+ 
+   CmdResult Handle (const std::vector& parameters, User 
*user)
+@@ -199,6 +200,9 @@ class CommandAuthenticate : public Command
+   if (!cap.ext.get(user))
+   return CMD_FAILURE;
+ 
++  if (parameters[0].find(' ') != std::string::npos || 
parameters[0][0] == ':')
++  return CMD_FAILURE;
++
+   SaslAuthenticator *sasl = authExt.get(user);
+   if (!sasl)
+   authExt.set(user, new SaslAuthenticator(user, 
parameters[0]));
diff -Nru inspircd-2.0.17/debian/patches/series 
inspircd-2.0.17/debian/patches/series
--- inspircd-2.0.17/debian/patches/series   2016-03-22 19:29:23.0 
+0100
+++ inspircd-2.0.17/debian/patches/series   2016-09-06 22:55:05.0 
+0200
@@ -2,3 +2,4 @@
 01_dpkg-buildflags_support.diff
 03_gnutls_crypt_api_instead_gcrypt.diff
 CVE-2015-8702.patch
+CVE-2016-7142.patch


signature.asc
Description: OpenPGP digital signature

Bug#836888: erlang-redis-client: FTBFS: Uncaught error in rebar_core

[Chris Lamb]

Source: erlang-redis-client
Version: 1.0.8-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,

erlang-redis-client fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  erlang-redis-client
   Version:  1.0.8-2
   Build architecture:   amd64
   Date: Tue, 06 Sep 2016 21:27:54 +0100
   Hostname: ebd2af7d97c3
   Uname:Linux ebd2af7d97c3 4.7.0-1-amd64 #1 SMP Debian 4.7.2-1 
(2016-08-28) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'erlang-redis-client-build-deps' in 
'../erlang-redis-client-build-deps_1.0.8-2_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package erlang-redis-client-build-deps.
  (Reading database ... 23306 files and directories currently installed.)
  Preparing to unpack erlang-redis-client-build-deps_1.0.8-2_all.deb ...
  Unpacking erlang-redis-client-build-deps (1.0.8-2) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
dh-rebar erlang-base erlang-dev erlang-eunit erlang-mnesia
erlang-runtime-tools erlang-syntax-tools erlang-tools rebar
  Suggested packages:
erlang erlang-manpages erlang-doc
  Recommended packages:
libsctp1 erlang-crypto mercurial
  The following NEW packages will be installed:
dh-rebar erlang-base erlang-dev erlang-eunit erlang-mnesia
erlang-runtime-tools erlang-syntax-tools erlang-tools rebar
  0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 9653 kB of archives.
  After this operation, 22.0 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 erlang-base amd64 
1:19.0.5+dfsg-3 [7073 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 erlang-dev amd64 
1:19.0.5+dfsg-3 [359 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 erlang-mnesia amd64 
1:19.0.5+dfsg-3 [747 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 erlang-runtime-tools 
amd64 1:19.0.5+dfsg-3 [205 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 erlang-tools amd64 
1:19.0.5+dfsg-3 [521 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 erlang-syntax-tools 
amd64 1:19.0.5+dfsg-3 [373 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 rebar amd64 2.6.2-2 
[203 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 dh-rebar all 0.0.4 
[7298 B]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 erlang-eunit amd64 
1:19.0.5+dfsg-3 [164 kB]
  Fetched 9653 kB in 0s (95.1 MB/s)
  Selecting previously unselected package erlang-base.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23310 files and directories currently installed.)
  Preparing to unpack .../0-erlang-base_1%3a19.0.5+dfsg-3_amd64.deb ...
  Unpacking erlang-base (1:19.0.5+dfsg-3) ...
  Selecting previously unselected package erlang-dev.
  Preparing to unpack .../1-erlang-dev_1%3a19.0.5+dfsg-3_amd64.deb ...
  Unpacking erlang-dev (1:19.0.5+dfsg-3) ...
  Selecting previously unselected package erlang-mnesia.
  Preparing to unpack .../2-erlang-mnesia_1%3a19.0.5+dfsg-3_amd64.deb ...
  Unpacking erlang-mnesia (1:19.0.5+dfsg-3) ...
  Selecting previously unselected package erlang-runtime-tools.
  Preparing to unpack 

Bug#836889: sugar: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools". Stop.

[Chris Lamb]

Source: sugar
Version: 0.106.1-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,

sugar fails to build from source in unstable/amd64:

  [..]

  Setting up python-empy (3.3.2-1) ...
  Setting up libatk1.0-0:amd64 (2.21.90-2) ...
  Setting up x11proto-randr-dev (1.5.0-1) ...
  Setting up x11proto-gl-dev (1.4.17-1) ...
  Processing triggers for systemd (231-5) ...
  Setting up libpython2.7:amd64 (2.7.12-3) ...
  Setting up openssl (1.0.2h-1) ...
  Setting up libdconf1:amd64 (0.26.0-1) ...
  Setting up libfile-listing-perl (6.04-1) ...
  Setting up libexpat1-dev:amd64 (2.2.0-1) ...
  Setting up libpciaccess0:amd64 (0.13.4-1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up shared-mime-info (1.6-1) ...
  Setting up libxkbcommon0:amd64 (0.6.1-1) ...
  Setting up libhttp-message-perl (6.11-1) ...
  Setting up libpcrecpp0v5:amd64 (2:8.39-2) ...
  Setting up libpcre32-3:amd64 (2:8.39-2) ...
  Setting up libnet-http-perl (6.09-1) ...
  Setting up libpython2.7-dev:amd64 (2.7.12-3) ...
  Setting up icu-devtools (57.1-3) ...
  Setting up libdrm-radeon1:amd64 (2.4.70-1) ...
  Setting up libpcre16-3:amd64 (2:8.39-2) ...
  Setting up libcolord2:amd64 (1.3.2-1) ...
  Setting up libthai-data (0.1.25-1) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libdrm-nouveau2:amd64 (2.4.70-1) ...
  Setting up x11-common (1:7.7+16) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up ca-certificates (20160104) ...
  Setting up hicolor-icon-theme (0.15-1) ...
  Setting up libglib2.0-bin (2.49.6-1) ...
  Setting up python2.7-dev (2.7.12-3) ...
  Setting up libgraphite2-dev (1.3.8-1) ...
  Setting up wayland-protocols (1.7-1) ...
  Setting up dh-buildinfo (0.11+nmu1) ...
  Setting up libwww-robotrules-perl (6.01-1) ...
  Setting up libwayland-cursor0:amd64 (1.11.0-2) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libdbus-1-3:amd64 (1.10.10-1) ...
  Setting up liblzo2-2:amd64 (2.08-1.2) ...
  Setting up libavahi-common-data:amd64 (0.6.32-1) ...
  Setting up libhttp-negotiate-perl (6.00-2) ...
  Setting up libepoxy-dev:amd64 (1.3.1-1) ...
  Setting up libwayland-server0:amd64 (1.11.0-2) ...
  Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
  Setting up libpython-dev:amd64 (2.7.11-2) ...
  Setting up gconf2-common (3.2.6-3) ...
  
  Creating config file /etc/gconf/2/path with new version
  Setting up libdbus-1-dev:amd64 (1.10.10-1) ...
  Setting up libpcre3-dev:amd64 (2:8.39-2) ...
  Setting up gir1.2-atk-1.0 (2.21.90-2) ...
  Setting up fontconfig-config (2.11.0-6.7) ...
  Setting up libxkbcommon-dev (0.6.1-1) ...
  Setting up x11proto-core-dev (7.0.29-1) ...
  Setting up libdrm-amdgpu1:amd64 (2.4.70-1) ...
  Setting up libhttp-cookies-perl (6.01-1) ...
  Setting up libxshmfence-dev:amd64 (1.2-1) ...
  Setting up dconf-service (0.26.0-1) ...
  Setting up libdbus-glib-1-2:amd64 (0.106-1) ...
  Setting up python-dev (2.7.11-2) ...
  Setting up liblapack3 (3.6.1-2) ...
  update-alternatives: using /usr/lib/lapack/liblapack.so.3 to provide 
/usr/lib/liblapack.so.3 (liblapack.so.3) in auto mode
  Setting up libgconf-2-4:amd64 (3.2.6-3) ...
  Setting up libgbm1:amd64 (11.2.2-1) ...
  Setting up libharfbuzz0b:amd64 (1.2.7-1+b1) ...
  Setting up libxau-dev:amd64 (1:1.0.8-1) ...
  Setting up libthai0:amd64 (0.1.25-1) ...
  Setting up libicu-dev (57.1-3) ...
  Setting up libglib2.0-dev (2.49.6-1) ...
  Setting up python-numpy (1:1.11.1~rc1-1) ...
  Setting up python-gobject-2-dev (2.28.6-13) ...
  Setting up gconf-service (3.2.6-3) ...
  Setting up libdrm-intel1:amd64 (2.4.70-1) ...
  Setting up libxdmcp-dev:amd64 (1:1.1.2-1.1) ...
  Setting up libice6:amd64 (2:1.0.9-1+b1) ...
  Setting up libavahi-common3:amd64 (0.6.32-1) ...
  Setting up libpng-dev:amd64 (1.6.24-2) ...
  Setting up x11proto-render-dev (2:0.11.1-2) ...
  Setting up dbus (1.10.10-1) ...
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up libwayland-dev:amd64 (1.11.0-2) ...
  Setting up dconf-gsettings-backend:amd64 (0.26.0-1) ...
  Setting up libxcb1:amd64 (1.11.1-1.1) ...
  Setting up x11proto-input-dev (2.3.2-1) ...
  Setting up libharfbuzz-gobject0:amd64 (1.2.7-1+b1) ...
  Setting up libxcb-present0:amd64 (1.11.1-1.1) ...
  Setting up libfontconfig1:amd64 (2.11.0-6.7) ...
  Setting up libxcb-dri2-0:amd64 (1.11.1-1.1) ...
  Setting up libsm6:amd64 (2:1.2.2-1+b1) ...
  Setting up libxcb-dri3-0:amd64 (1.11.1-1.1) ...
  Setting up libxcb-glx0:amd64 (1.11.1-1.1) ...
  Setting up libxcb-randr0:amd64 (1.11.1-1.1) ...
  Setting up libxcb-xfixes0:amd64 (1.11.1-1.1) ...
  Setting up libxcb-render0:amd64 (1.11.1-1.1) ...

Bug#835720: [Debian-med-packaging] Bug#835720: salmon: FTBFS: BAMQueue.tpp:88:29: error: no matching function for call to 'spdlog::logger::warn()'

[Sascha Steinbiss]

Hi again,

>> It would be great if somebody could fix the build to bring this forward
>> since I personally do not have any interest in salmon (yet).
> 
> I’ll look at it. There will be some patching necessary to bring the spdlog 
> API use in RepMap up to speed with the current spdlog version in unstable.

Builds now and produces a working executable, see git. There’s no manpage, 
copyright file, etc. yet, I can try to get this finished later.
I won’t be a first hand user of this tool either, but if it’s useful...

Cheers
Sascha



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#831096: opensurgsim: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory

[Andreas Tille]

[Paul, I wonder whether you realised the problems with opensurgsim]

Hi Graham,

On Thu, Aug 25, 2016 at 02:37:53PM +0200, Graham Inggs wrote:
> Hi Maintainer
> 
> The attached patch fixes the FTBFS with GCC 6.
> I'll open a separate bug for the eigen3 issue and mark it as being blocked
> by #835411.

I checked building opensurgsim and while I have not realised any
problems directly hinting to eigen3 I've got:

...
 2 FAILED TESTS

  Start 12: SurgSimPhysicsTest
12/12 Test #12: SurgSimPhysicsTest ...   Passed0.64 sec

92% tests passed, 1 tests failed out of 12

Total Test time (real) =   8.99 sec

The following tests FAILED:
 11 - SurgSimMathTest (Failed)
Errors while running CTest
Makefile:130: recipe for target 'test' failed
make[1]: *** [test] Error 8
make[1]: Leaving directory '/build/opensurgsim-0.6.0/obj-x86_64-linux-gnu'


-- 
http://fam-tille.de

Bug#835720: salmon: FTBFS: BAMQueue.tpp:88:29: error: no matching function for call to 'spdlog::logger::warn()'

[Sascha Steinbiss]

Hi,

> On Tue, Aug 30, 2016 at 12:16:26PM +0200, Andreas Tille wrote:
>> I tried to upgrade salmon to latest upstream where this problem might
>> have possibly solved.  I'm currently struck by the fact that
>> 
>>https://github.com/COMBINE-lab/RapMap
>> 
>> is needed to build.
> 
> I have commited[1] some rudimentary debian/ dir which needs to get the
> cmake packaging adapted to make sure all predependencies are found.
> 
> It would be great if somebody could fix the build to bring this forward
> since I personally do not have any interest in salmon (yet).

I’ll look at it. There will be some patching necessary to bring the spdlog API 
use in RepMap up to speed with the current spdlog version in unstable.

Cheers
Sascha


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#835075: Pending fixes for bugs in the libmail-gnupg-perl package

[pkg-perl-maintainers]

tag 835075 + pending
thanks

Some bugs in the libmail-gnupg-perl package are closed in revision
9f58451a7d53d816a2ae333ec6161fe0c63b3964 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libmail-gnupg-perl.git/commit/?id=9f58451

Commit message:

Add patch to make testsuite and autopkgtest work with gnupg2.

Thanks: Daniel Kahn Gillmor for the patch.
Closes: #835075

Processed: Pending fixes for bugs in the libmail-gnupg-perl package

[Debian Bug Tracking System]

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

> tag 835075 + pending
Bug #835075 [src:libmail-gnupg-perl] libmail-gnupg-perl: FTBFS: Failed 1/10 
test programs. 0/4 subtests failed.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#836391: gradle: recent update of jsch to version 0.1.54 breaks Gradle based projects

[Markus Koschany]

On 06.09.2016 21:35, Jeremy Bicha wrote:
> Do you know why the new gradle 2.13-4 still fails to build on Ubuntu yakkety?
> 
> https://launchpad.net/ubuntu/+source/gradle/2.13-4/+build/10712522
> 
> Thanks,
> Jeremy Bicha

Hi Jeremy,

the package FTBFS because gradle build-depends on itself and the current
version in Yakkety still requires jsch version 0.1.53. I guess this can
only be resolved by building in a local chroot that uses gradle 2.13-4.

Regards,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#836881: X509 card-based logins fail with SIGSEGV

[Jelmer Vernooij]

tags 836881 +moreinfo
thanks

On Tue, Sep 06, 2016 at 01:52:49PM -0500, Timothy Pearson wrote:
> Package: libhx509-5-heimdal
> Version: 1.7~git20160703+dfsg-1
> Severity: grave
> 
> Heimdal's X509 PAM authentication plugin crashes with the following
> backtrace when attempting to use a cryptographic card to log in:

> Program received signal SIGSEGV, Segmentation fault.
> 0x7f5c0f30e38d in _hx509_match_keys (c=0x18e2ed0, key=0x18e0960) at
> crypto.c:3018
> 3018crypto.c: No such file or directory.
> (gdb) bt
> #0  0x7f5c0f30e38d in _hx509_match_keys (c=0x18e2ed0, key=0x18e0960)
> at crypto.c:3018
Are you sure the version listed above is correct?

lib/hx509/crypto.c only has 2734 lines in 1.7~git20160703+dfsg.

Jelmer

Processed: Re: Bug#836881: X509 card-based logins fail with SIGSEGV

[Debian Bug Tracking System]

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

> tags 836881 +moreinfo
Bug #836881 [libhx509-5-heimdal] X509 card-based logins fail with SIGSEGV
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#836391: gradle: recent update of jsch to version 0.1.54 breaks Gradle based projects

[Jeremy Bicha]

Do you know why the new gradle 2.13-4 still fails to build on Ubuntu yakkety?

https://launchpad.net/ubuntu/+source/gradle/2.13-4/+build/10712522

Thanks,
Jeremy Bicha

Bug#836881: X509 card-based logins fail with SIGSEGV

[Jelmer Vernooij]

On Tue, Sep 06, 2016 at 01:52:49PM -0500, Timothy Pearson wrote:
> Package: libhx509-5-heimdal
> Version: 1.7~git20160703+dfsg-1
> Severity: grave
> 
> Heimdal's X509 PAM authentication plugin crashes with the following
> backtrace when attempting to use a cryptographic card to log in:
> 
Thanks for the bug report. Please note that we're in the process of removing
Heimdal from testing. See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834654 for details.

Bug#835720: salmon: FTBFS: BAMQueue.tpp:88:29: error: no matching function for call to 'spdlog::logger::warn()'

[Andreas Tille]

Hi,

On Tue, Aug 30, 2016 at 12:16:26PM +0200, Andreas Tille wrote:
> I tried to upgrade salmon to latest upstream where this problem might
> have possibly solved.  I'm currently struck by the fact that
> 
> https://github.com/COMBINE-lab/RapMap
> 
> is needed to build.

I have commited[1] some rudimentary debian/ dir which needs to get the
cmake packaging adapted to make sure all predependencies are found.

It would be great if somebody could fix the build to bring this forward
since I personally do not have any interest in salmon (yet).

Kind regards

  Andreas.

[1] https://anonscm.debian.org/git/debian-med/rapmap.git

-- 
http://fam-tille.de

Bug#836881: X509 card-based logins fail with SIGSEGV

[Timothy Pearson]

Package: libhx509-5-heimdal
Version: 1.7~git20160703+dfsg-1
Severity: grave

Heimdal's X509 PAM authentication plugin crashes with the following
backtrace when attempting to use a cryptographic card to log in:

Program received signal SIGSEGV, Segmentation fault.
0x7f5c0f30e38d in _hx509_match_keys (c=0x18e2ed0, key=0x18e0960) at
crypto.c:3018
3018crypto.c: No such file or directory.
(gdb) bt
#0  0x7f5c0f30e38d in _hx509_match_keys (c=0x18e2ed0, key=0x18e0960)
at crypto.c:3018
#1  0x7f5c0f30b17b in match_keys (value=0x18e0500, certs=0x18e1620,
context=0x18a0430) at collector.c:232
#2  _hx509_collector_collect_certs (context=context@entry=0x18a0430,
c=0x18e0b30, ret_certs=ret_certs@entry=0x18e0438) at collector.c:275
#3  0x7f5c0f315669 in p11_list_keys (certs=0x18e0438, lock=, session=26085952, slot=0x18e0410, p=0x18a3740, context=0x18a0430) at
ks_p11.c:804
#4  p11_init_slot (context=context@entry=0x18a0430, p=p@entry=0x18a3740,
lock=lock@entry=0x18a36a0, id=, num=,
slot=0x18e0410) at ks_p11.c:363
#5  0x7f5c0f315963 in p11_init (context=0x18a0430, certs=, data=0x1889f70, flags=, residue=,
lock=0x18a36a0) at ks_p11.c:933
#6  0x7f5c0f311b10 in hx509_certs_init (context=0x18a0430,
name=name@entry=0x1867910
"PKCS11:/usr/lib/x86_64-linux-gnu/opensc-pkcs11.so", flags=flags@entry=0,
lock=0x18a36a0, certs=certs@entry=0x18a3668) at keyset.c:159
#7  0x7f5c0fc72f0f in _krb5_pk_load_id
(context=context@entry=0x18a0240, ret_id=0x18a3580,
user_id=user_id@entry=0x1867910
"PKCS11:/usr/lib/x86_64-linux-gnu/opensc-pkcs11.so",
anchor_id=anchor_id@entry=0x18a3440
"FILE:/etc/trinity/ldap/tde-ca/public/odin.starlink.edu.ldap.crt",
chain_list=0x0, revoke_list=0x1889ba0, prompter=0x7f5c0feb30d0,
prompter_data=0x1867740, password=0x0) at pkinit.c:1882
#8  0x7f5c0fc74b07 in krb5_get_init_creds_opt_set_pkinit
(context=0x18a0240, opt=0x1867810, principal=0x1867880, user_id=0x1867910
"PKCS11:/usr/lib/x86_64-linux-gnu/opensc-pkcs11.so",
x509_anchors=0x18a3440
"FILE:/etc/trinity/ldap/tde-ca/public/odin.starlink.edu.ldap.crt",
pool=, pki_revoke=, flags=0,
prompter=0x7f5c0feb30d0, prompter_data=0x1867740, password=0x0) at
pkinit.c:2394
#9  0x7f5c0feb0e49 in ?? () from
/lib/x86_64-linux-gnu/security/pam_krb5.so
#10 0x7f5c0feb175b in ?? () from
/lib/x86_64-linux-gnu/security/pam_krb5.so
#11 0x7f5c0feb36b7 in pam_sm_authenticate () from
/lib/x86_64-linux-gnu/security/pam_krb5.so
#12 0x7f5c123c80a6 in ?? () from /lib/x86_64-linux-gnu/libpam.so.0
#13 0x7f5c123c781d in pam_authenticate () from
/lib/x86_64-linux-gnu/libpam.so.0
#14 0x004031b3 in ?? ()
#15 0x7f5c11c18700 in __libc_start_main (main=0x402a90, argc=3,
argv=0x7ffd37fe93f8, init=, fini=,
rtld_fini=, stack_end=0x7ffd37fe93e8) at
../csu/libc-start.c:291
#16 0x00404200 in ?? ()

Bug#832364: kodi: Crashes on trying to play any TV recording

[Tobias Grimm]

It's only 19k compressed, so I've attached the test file.

It plays fine in Kodi 16.1+dfsg1-2 but Kodi 16.1+dfsg1-1 crashes.
(libav* 7:3.1.2-1 installed)

This only happens with the TS format. The same video created as e.g. MP4
plays fine.

Tobias

On 06.09.2016 14:39, Bálint Réczey wrote:

> Hi Tobias,
> 
> 2016-09-06 14:35 GMT+02:00 Tobias Grimm :
>> I can provide a sample without any copyrighted content if that helps.
> 
> That would definitely be the best.
> Could you please link to it from the bug?
> 
> Cheers,
> Balint
> 
>>
>> Tobias
>>
>>
>> Am 06.09.2016 um 14:06 schrieb Carl Eugen Hoyos:
>>>
>>>
>>>
>>> On Tue, 6 Sep 2016, Bálint Réczey wrote:
>>>
 Could you please share the recording with Carl instead?
>>>
>>>
>>> Please don't!
>>> I would (immediately) make the sample public.
>>>
>>> Unfortunately, I also do not know how to test (let alone debug) Kodi,
>>> so I am not right person to investigate this.
>>>
>>> Sorry!
>>>
>>> Carl Eugen
>>
>>
> 



test2.ts.gz
Description: application/gzip


signature.asc
Description: OpenPGP digital signature

Processed: fixed 836706 in 2.0.23-1

[Debian Bug Tracking System]

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

> fixed 836706 2.0.23-1
Bug #836706 [src:inspircd] inspircd: CVE-2016-7142: certificate fingerprint 
spoofing through crafted SASL messages
Marked as fixed in versions inspircd/2.0.23-1.
> thanks
Stopping processing here.

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

Bug#836669:

[Greg Farough]

I can also confirm this bug with the same package version on Sid. I
assumed it was due to my switching locales recently: glad to see others
are having the same problem.

-- 
-g

"A man can live and be healthy without killing animals for food;
therefore, if he eats meat, he participates in taking animal life
merely for the sake of his appetite. And to act so is immoral."

Processed: calligra

[Debian Bug Tracking System]

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

> affects 836816 calligra-l10n-ca
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-ca
> affects 836816 calligra-l10n-cavalencia
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-cavalencia
> affects 836816 calligra-l10n-cs
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-cs
> affects 836816 calligra-l10n-da
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-da
> affects 836816 calligra-l10n-de
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-de
> affects 836816 calligra-l10n-el
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-el
> affects 836816 calligra-l10n-engb
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-engb
> affects 836816 calligra-l10n-es
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-es
> affects 836816 calligra-l10n-eu
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-eu
> affects 836816 calligra-l10n-et
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-et
> affects 836816 calligra-l10n-fi
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-fi
> affects 836816 calligra-l10n-fr
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-fr
> affects 836816 calligra-l10n-gl
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-gl
> affects 836816 calligra-l10n-hu
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-hu
> affects 836816 calligra-l10n-it
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-it
> affects 836816 calligra-l10n-ja
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-ja
> affects 836816 calligra-l10n-kk
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-kk
> affects 836816 calligra-l10n-nb
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-nb
> affects 836816 calligra-l10n-nds
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-nds
> affects 836816 calligra-l10n-pl
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-pl
> affects 836816 calligra-l10n-pt
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-pt
> affects 836816 calligra-l10n-ptbr
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-ptbr
> affects 836816 calligra-l10n-ru
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-ru
> affects 836816 calligra-l10n-sk
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-sk
> affects 836816 calligra-l10n-sv
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-sv
> affects 836816 calligra-l10n-uk
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-uk
> affects 836816 calligra-l10n-zhcn
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-zhcn
> affects 836816 calligra-l10n-zhtw
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added indication that 836816 affects calligra-l10n-zhtw
>
End of message, stopping processing here.

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

Bug#836874: sentinella: not installable in sid

[Ralf Treinen]

Package: sentinella
Version: 0.9.2-4
Severity:serious
User: trei...@debian.org
Usertags:edos-uninstallable

Hi, sentinella is not installable in sid on any architecture, at least since
2015-11-04. The reason is that it depends on libprocessui4a (>= 4:4.6.1) which
does not exist in sid.

-Ralf.

Bug#836669: caja: Crashes due to theme errors

[Maxxie]

Package: caja
Version: 1.14.2-1
Followup-For: Bug #836669

I can confirm that, probably being the same package version, this bug affects
stretch too.
Also I have ~9MB of stacktrace going like this: http://pastebin.com/JUKB4R1M
and then it just keeps looping...



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

Kernel: Linux 4.7.0-maxxie (SMP w/8 CPU cores; PREEMPT)
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 caja depends on:
ii  caja-common   1.14.2-1
ii  desktop-file-utils0.23-1
ii  gvfs  1.29.91-1
ii  libatk1.0-0   2.20.0-1
ii  libc6 2.23-5
ii  libcairo-gobject2 1.14.6-1+b1
ii  libcairo2 1.14.6-1+b1
ii  libcaja-extension11.14.2-1
ii  libexempi32.3.0-2
ii  libexif12 0.6.21-2
ii  libgail-3-0   3.21.5-3
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.49.6-1
ii  libglib2.0-data   2.49.6-1
ii  libgtk-3-03.21.5-3
ii  libice6   2:1.0.9-1+b1
ii  libmate-desktop-2-17  1.14.1-1
ii  libpango-1.0-01.40.2-1
ii  libpangocairo-1.0-0   1.40.2-1
ii  libselinux1   2.5-3
ii  libsm62:1.2.2-1+b1
ii  libstartup-notification0  0.12-4
ii  libunique-3.0-0   3.0.2-2
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.4+dfsg1-1+b1
ii  libxrender1   1:0.9.9-2
ii  mate-desktop  1.14.1-1
ii  shared-mime-info  1.6-1

Versions of packages caja recommends:
ii  gvfs-backends  1.29.91-1

Versions of packages caja suggests:
ii  engrampa1.14.1-1
ii  gstreamer1.0-tools  1.8.3-1
pn  meld

-- no debconf information

Bug#830529: marked as done (cdbs: curpythonindepbinary variable no longer works)

[Debian Bug Tracking System]

Your message dated Tue, 06 Sep 2016 16:52:33 +
with message-id 
and subject line Bug#830529: fixed in cdbs 0.4.145
has caused the Debian Bug report #830529,
regarding cdbs: curpythonindepbinary variable no longer works
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.)


-- 
830529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cdbs
Version: 0.4.142
Severity: serious
Justification: causes other package to fail to build from source

The uwsgi package has this line [1] in its debian/rules:
clean::
$(cdbs_curpythonindepbinary) $(UWSGI_BUILDER) --clean

The result is this, as seen in a successful build log [2]:

 dh_clean
 python uwsgiconfig.py -v --clean

Sometime after June 8, according to Debian's reproducible builder [3]
[4], that line stopped working.

 dh_clean
 uwsgiconfig.py -v --clean
 make: uwsgiconfig.py: Command not found
 debian/rules:335: recipe for target 'clean' failed
 make: *** [clean] Error 127


[1] https://anonscm.debian.org/cgit/pkg-uwsgi/uwsgi.git/tree/debian/rules#n333
[2] 
https://buildd.debian.org/status/fetch.php?pkg=uwsgi=i386=2.0.12-7=1462704762
[3] 
https://tests.reproducible-builds.org/debian/rbuild/testing/amd64/uwsgi_2.0.12-7.rbuild.log
[4] Check test history at
https://tests.reproducible-builds.org/debian/rb-pkg/testing/amd64/uwsgi.html

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: cdbs
Source-Version: 0.4.145

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated cdbs 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, 06 Sep 2016 17:52:42 +0200
Source: cdbs
Binary: cdbs
Architecture: source all
Version: 0.4.145
Distribution: unstable
Urgency: medium
Maintainer: CDBS Hackers 
Changed-By: Jonas Smedegaard 
Description:
 cdbs   - common build system for Debian packages
Closes: 830529
Changes:
 cdbs (0.4.145) unstable; urgency=medium
 .
   * Fix resolve deprecated variables cdbs_curpythonindepbinary
 cdbs_curpythonpribinary: Add python2 runtime as fallback.
 Closes: Bug#830529. Thanks to Jeremy Bicha.
   * Fix resolve default python runtimes internally (affecting deprecated
 variables cdbs_python_current_binary cdbs_python3_current_binary
 cdbs_curpythonindepbinary cdbs_curpythonpribinary).
   * Fix resolve installpath for flavored arch-indep python-distutils
 builds.
   * Introduce new variables:
 + cdbs_$python_allflavors
 + cdbs_$python_defaultflavor
 + cdbs_$python_defaultruntime
 + cdbs_curpythondefaultflavor
Checksums-Sha1:
 02afba3251e2d4569f68ae2119768d1b86266c1b 1846 cdbs_0.4.145.dsc
 424ae61f6d5605d6a80b94d5bfb535d16bcbe4be 204056 cdbs_0.4.145.tar.xz
 ea3a4d42b42a1e56cfecb40cc802a137878a77f4 81904 cdbs_0.4.145_all.deb
Checksums-Sha256:
 05530b4944e47fa98b06904c13afe905fd67bfb246c4ea8033b2690add66062e 1846 
cdbs_0.4.145.dsc
 b99867bf83b576b40e7a3e2e3d3eadb53ec52d755b45da1f1635ba1e907e715b 204056 
cdbs_0.4.145.tar.xz
 96a66d9e85eab679a1dfb4ffa3f7693a51ab333b19b032e3cd64ea4f53a5055f 81904 
cdbs_0.4.145_all.deb
Files:
 f82a1ea35c50e74432c44b965ff5dfff 1846 devel optional cdbs_0.4.145.dsc
 4d5a03795654a9c8775dffc9b1616ac5 204056 devel optional cdbs_0.4.145.tar.xz
 ca689f56faf56df39b55c3b9d0d45cf7 81904 devel optional cdbs_0.4.145_all.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJXzukzAAoJECx8MUbBoAEh/eEQAKdKRHwd5fEKL7uEqBIvWu8k
1ha/0cb9/4X5qoHbTzKOfDwFMLdlkfUxYBTEecuJB9wYqvsUftoaPGWd0fPoiIyY
6kzi70nI40vgFxxdO88cr27LnaqAIRqyvLo7EtLm/XCkrmnRdMDk5dtk/5iOMw05
ZaCsuffF5Op6qWkhal0QVglDmaSXrRCT0gcBufK5j8959Fb+HkqRxSYvCDw4giao
w+EPzOeipjYFwOIiFTUWgBXJE7dKjOxCS+8wkwBQhXW+FGQBkni3x58R6kzQAi+z
p/0rmJ+vqHota08GNufydc7JyE2gYPNEmBgy5AuiF4YYi9zD3xqbFBAC6UguqAHS
HeC54hwS5w/njJkDibDWnVsYOxfmERF87FEjF8ikiI4fhUI0yoX0vf7iNff62WQ6

Bug#836219: marked as done (pocl: FTBFS on mips64el: symbol mismatches)

[Debian Bug Tracking System]

Your message dated Tue, 06 Sep 2016 16:14:21 +
with message-id 
and subject line Bug#836219: fixed in pocl 0.13-6
has caused the Debian Bug report #836219,
regarding pocl: FTBFS on mips64el: symbol mismatches
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.)


-- 
836219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pocl
Version: 0.13-5
Severity: serious

Hi,

Your package built on mips64el in the past, but fails to build now because
of symbol mismatches. See

https://buildd.debian.org/status/fetch.php?pkg=pocl=mips64el=0.13-5=1471641759

Emilio

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: pocl
Source-Version: 0.13-6

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated pocl 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, 06 Sep 2016 14:55:01 +0200
Source: pocl
Binary: pocl-opencl-icd libpocl1-common libpocl1 libpoclu1 libpoclu-dev 
libpocl-dev pocl-doc
Architecture: source
Version: 0.13-6
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenCL Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libpocl-dev - development files for the pocl library
 libpocl1   - Portable Computing Language library
 libpocl1-common - common files for the pocl library
 libpoclu-dev - development files for the pocl utility library
 libpoclu1  - utility library for writing OpenCL programs
 pocl-doc   - documentation for the pocl library
 pocl-opencl-icd - pocl ICD
Closes: 835690 836219
Changes:
 pocl (0.13-6) unstable; urgency=medium
 .
   * Update symbols files.  (Closes: #835690, #836219)
Checksums-Sha1:
 5c0f72cf5ee0c4a3d270753f76f602aeb9f3540f 2468 pocl_0.13-6.dsc
 2c0ac83f415ee80f237c7c56f889b098d068e212 142500 pocl_0.13-6.debian.tar.xz
Checksums-Sha256:
 6e8cad6ec98d7e4610aa491fda855e3653ceba92486a5b56e746019835b239ce 2468 
pocl_0.13-6.dsc
 05b515bc75a83b3fe86adf435221a132eed685605e14bcf2370fe24d7203a0ad 142500 
pocl_0.13-6.debian.tar.xz
Files:
 9380b45e73a116063fee80c6dd787763 2468 libs extra pocl_0.13-6.dsc
 90fdaf318a139e1cf469fff9888f4c76 142500 libs extra pocl_0.13-6.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXzs+OAAoJEF+zP5NZ6e0IdcgP/iLQpdG4RaWYLu7ObXxsXKpw
KkdMR59/bsJTtNnOO6p/VAc65WXD49YekkjI1xwkEkXXqDhl8pEthAzSRrs0ZyOc
60kE/9Es4hBmerxUbD+xOlwmqVLDAuiR85aU97FLB8bECBcGnCg9V3g51Yo5AJlP
3rAcgAB2s7zoelh6Of+QlWZIPNzqMWbExWZY1IlXFLzOXOnfy17CyKqD5O1je4bO
2G7KHCaB6b4Ej2Cjp4KTuWFL5GGKo/5NAhcP+JVNmFwbX/tDflVsGeJDSViZJEmK
BHWxogqqtNFKlZzm/yKBYJ0VwAzkRtY+iI5O+T55m2bZKZ5z6qaUxiSrXifWl/E8
1f3qBQoyQPGI1DyaE6t/KJz554RVVUl62jyu5D7AoGs4KhYrxqPJQK6+L7MQ/1/j
44R0J2NcVHoZzUWiL59PYUtrVnqYoFes/VC9nv7N37cI3EXLCNZTtupGUbDERBnQ
eh5rFOgaMK10X5Sa/6iJxIFgp5meciZDCPMoLSxap32/+TnPjtN1+KpLYlwAtytq
v/nZrZ4I8XPanDaAjMKLWMFCoFOFKRBtVOnBU+/ab2PY/M01xAHyUw+X01dFqnb1
k7EuWtZWPgJkcNzFKF6jhb66MzXbalgHEIQvAqrZdB+ab2tiAhfUX2g72lHTMXcd
yOLq6Yg1PdgprCvESS6J
=YUzz
-END PGP SIGNATURE End Message ---

Bug#834035: marked as done (kdb5_util hangs forever on 32-bit systems)

[Debian Bug Tracking System]

Your message dated Tue, 06 Sep 2016 16:09:34 +
with message-id 
and subject line Bug#834035: fixed in krb5 1.14.3+dfsg-2
has caused the Debian Bug report #834035,
regarding kdb5_util hangs forever on 32-bit systems
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.)


-- 
834035: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: krb5-kdc
Version: 1.14.3+dfsg-1
Severity: critical

Hello,

I try create a database with the command

kdb5_util create -s -P foo

That seems to hang forever. Relevant part of a trace:


open("/var/lib/krb5kdc/principal.ok", O_RDWR|O_CREAT|O_TRUNC, 0600) = 3
fcntl64(3, F_OFD_SETLKW, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, 
l_len=6950411022381350912}) = -1 EINVAL (Invalid argument)
fcntl64(3, F_SETLKW, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
open("/var/lib/krb5kdc/principal", O_RDWR|O_CREAT|O_EXCL, 0600) = 4
fcntl64(4, F_SETFD, FD_CLOEXEC) = 0
fstat64(4, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
fstat64(4, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
lseek(4, 4096, SEEK_SET)= 4096
read(4, "", 4096)   = 0
open("/var/lib/krb5kdc/principal.kadm5", O_RDWR|O_CREAT|O_EXCL, 0600) = 5
fcntl64(5, F_SETFD, FD_CLOEXEC) = 0
fstat64(5, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
fstat64(5, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
lseek(5, 4096, SEEK_SET)= 4096
read(5, "", 4096)   = 0
lseek(5, 4096, SEEK_SET)= 4096
write(5, 
"\1\0\0\0\0\0\0\0\0\0\0\0\2\0\0\0\24\0\0\20\377\377\377\377\377\377\377\377\377\377\377\377"...,
 4096) = 4096
lseek(5, 0, SEEK_SET)   = 0
write(5, "b1\5\0\3\0\0\0\0\20\0\0\0\0\0\0\0\0\0\0 \0\0\0\0\0\0\0\0\0\0\0"..., 
4096) = 4096
fsync(5)= 0
close(5)= 0
open("/var/lib/krb5kdc/principal.kadm5.lock", O_RDWR|O_CREAT|O_EXCL, 0600) = 5
close(5)= 0
access("/etc/krb5kdc/kdc.conf", R_OK)   = 0
stat64("/etc/krb5kdc/kdc.conf", {st_mode=S_IFREG|0644, st_size=738, ...}) = 0
access("/etc/krb5.conf", R_OK)  = 0
stat64("/etc/krb5.conf", {st_mode=S_IFREG|0644, st_size=729, ...}) = 0
open("/dev/urandom", O_RDONLY)  = 5
fcntl64(5, F_SETFD, FD_CLOEXEC) = 0
fstat64(5, {st_mode=S_IFCHR|0666, st_rdev=makedev(1, 9), ...}) = 0
read(5, 
"\344\nx\207\216\231\370u\16cRW\251c*\240\37\20\310\236\304\211\322\242\275\26\271#\351I\26\321"...,
 64) = 64
close(5)= 0
gettimeofday({1470921186, 154266}, NULL) = 0
open("/var/lib/krb5kdc/principal.kadm5.lock", O_RDWR) = 5
fcntl64(5, F_SETFD, FD_CLOEXEC) = 0
fcntl64(5, F_OFD_SETLKW, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, 
l_len=6950411022381350912}) = -1 EINVAL (Invalid argument)
fcntl64(5, F_SETLKW, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
access("/var/lib/krb5kdc/principal.kadm5.lock", F_OK) = 0
fcntl64(5, F_OFD_SETLKW, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, 
l_len=6950411022381350912}) = -1 EINVAL (Invalid argument)
fcntl64(5, F_SETLKW, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
lseek(4, 4096, SEEK_SET)= 4096
write(4, 
"\1\0\0\0\0\0\0\0\0\0\0\0\2\0\0\0\24\0\0\20\377\377\377\377\377\377\377\377\377\377\377\377"...,
 4096) = 4096
lseek(4, 0, SEEK_SET)   = 0
write(4, "b1\5\0\3\0\0\0\0\20\0\0\0\0\0\0\0\0\0\0 \0\0\0\0\0\0\0\0\0\0\0"..., 
4096) = 4096
fsync(4)= 0
close(4)= 0
fcntl64(3, F_OFD_SETLKW, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, 
l_len=6950411022381350912}) = 0
fcntl64(3, F_OFD_SETLKW, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, 
l_len=6950411022381350912}


In the first few lines kdb5_util opens a file and acquires a lock.
Fast forward to the end of the trace, there the lock is released. Next
the process tries to re-acquire the lock and blocks. Sometimes, very
rarely, the process comes to a successful end without blocking.

Regards
hmw
--- End Message ---
--- Begin Message ---
Source: krb5
Source-Version: 1.14.3+dfsg-2

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

Bug#835735: marked as done (connman: FTBFS: dh_install: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Tue, 06 Sep 2016 16:06:02 +
with message-id 
and subject line Bug#835735: fixed in connman 1.32-1
has caused the Debian Bug report #835735,
regarding connman: FTBFS: dh_install: missing files, aborting
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> find /<> -name "*.la" -print -delete
> /<>/gdbus/libgdbus-internal.la
> /<>/gdbus/.libs/libgdbus-internal.la
> /<>/scripts/libppp-plugin.la
> /<>/scripts/.libs/libppp-plugin.la
> /<>/vpn/plugins/l2tp.la
> /<>/vpn/plugins/openvpn.la
> /<>/vpn/plugins/openconnect.la
> /<>/vpn/plugins/.libs/l2tp.la
> /<>/vpn/plugins/.libs/openvpn.la
> /<>/vpn/plugins/.libs/openconnect.la
> /<>/vpn/plugins/.libs/pptp.la
> /<>/vpn/plugins/pptp.la
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/connman/scripts/libppp-plugin.la
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/connman/plugins-vpn/l2tp.la
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/connman/plugins-vpn/openvpn.la
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/connman/plugins-vpn/openconnect.la
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/connman/plugins-vpn/pptp.la
> dh_install --fail-missing
> dh_install: Cannot find (any matches for) 
> "usr/lib/tmpfiles.d/connman_resolvconf.conf" (tried in "." and "debian/tmp")
> dh_install: connman missing files: usr/lib/tmpfiles.d/connman_resolvconf.conf
> dh_install: missing files, aborting
> debian/rules:24: recipe for target 'override_dh_install' failed
> make[1]: *** [override_dh_install] Error 2

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/08/28/connman_1.32-0.1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Alexander Sack  (supplier of updated connman 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, 06 Sep 2016 15:38:03 +0200
Source: connman
Binary: connman connman-vpn connman-dev connman-doc
Architecture: source
Version: 1.32-1
Distribution: unstable
Urgency: medium
Maintainer: Alexander Sack 
Changed-By: Alexander Sack 
Description:
 connman- Intel Connection Manager daemon
 connman-dev - Development files for connman
 connman-doc - ConnMan documentation
 connman-vpn - Intel Connection Manager daemon - VPN daemon
Closes: 742408 745874 751234 753022 763628 768116 797638 813580 813647 822393 
822610 833294 835735
Changes:
 connman (1.32-1) unstable; urgency=medium
 .
   * confirm NMUs 1.32-0.1, 1.21-1.1 and 1.21-1.2
   * fix FTBmFS in sid (Closes: #835735)
 - adding --with-tmpfilesdir=/usr/lib/tmpfiles.d to avoid systemd build-dep
   * fix missing manpage option (Closes: #822610)
 - debian/patches/deb822610-add-manpage-option.patch
   * remove /var/lib/connman on purge in connman.postrm (Closes: 833294)
 .
 connman (1.32-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Shawn Landden ]
   * New upstream release (1.29) (Closes: #742408)
 - Drop 02-test-pbkdf2-sha1-maximum-salt-len-should-be-32-instead.patch
   * Conflict with resolvconf (Closes: #763628)
   * Conflict with wicd-daemon instead of 

Bug#836862: libreswan: /etc/ipsec.conf is already shipped by strongswan-starter

[Andreas Beckmann]

Package: libreswan
Version: 3.18-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files.

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

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

  Selecting previously unselected package libreswan.
  Preparing to unpack .../43-libreswan_3.18-1_amd64.deb ...
  Unpacking libreswan (3.18-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-za7Gyz/43-libreswan_3.18-1_amd64.deb (--unpack):
   trying to overwrite '/etc/ipsec.conf', which is also in package 
strongswan-starter 5.5.0-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


Using Breaks+Replaces would most likely be the wrong solution here.
If the conffile can be shared by both packages (hopefully it does),
it should be factored out into a separate package instead and both
users should add a dependency on this new package.


cheers,

Andreas

Bug#836861: mongo-tools: many /usr/bin/mongo* binaries are already shipped by mongodb-clients

[Andreas Beckmann]

Package: mongo-tools
Version: 3.2.9-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package mongo-tools.
  Preparing to unpack .../3-mongo-tools_3.2.9-1_amd64.deb ...
  Unpacking mongo-tools (3.2.9-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-kuF4JE/3-mongo-tools_3.2.9-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/bsondump', which is also in package 
mongodb-clients 1:2.6.12-3
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-kuF4JE/3-mongo-tools_3.2.9-1_amd64.deb


Full list of files shipped by both packages:

usr/bin/bsondump
usr/bin/mongodump
usr/bin/mongoexport
usr/bin/mongofiles
usr/bin/mongoimport
usr/bin/mongooplog
usr/bin/mongorestore
usr/bin/mongostat
usr/bin/mongotop
usr/share/man/man1/bsondump.1.gz
usr/share/man/man1/mongodump.1.gz
usr/share/man/man1/mongoexport.1.gz
usr/share/man/man1/mongofiles.1.gz
usr/share/man/man1/mongoimport.1.gz
usr/share/man/man1/mongooplog.1.gz
usr/share/man/man1/mongorestore.1.gz
usr/share/man/man1/mongostat.1.gz
usr/share/man/man1/mongotop.1.gz


cheers,

Andreas


mongodb-clients=1%2.6.12-3_mongo-tools=3.2.9-1.log.gz
Description: application/gzip

Processed: libprelude: diff for NMU version 1.0.0-11.8

[Debian Bug Tracking System]

Processing control commands:

> tags 836636 + patch
Bug #836636 [libprelude] libprelude: please drop the build dependency on 
hardening-wrapper
Added tag(s) patch.
> tags 836636 + pending
Bug #836636 [libprelude] libprelude: please drop the build dependency on 
hardening-wrapper
Added tag(s) pending.

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

Bug#836636: libprelude: diff for NMU version 1.0.0-11.8

[gregor herrmann]

Control: tags 836636 + patch
Control: tags 836636 + pending

Dear maintainer,

I've prepared an NMU for libprelude (versioned as 1.0.0-11.8) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

(DELAYED/2 might look a bit short but this is the 8th NMU in a row.)

Regards.

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: hons: rise
diff -Nru libprelude-1.0.0/debian/changelog libprelude-1.0.0/debian/changelog
--- libprelude-1.0.0/debian/changelog	2015-12-20 23:03:06.0 +0100
+++ libprelude-1.0.0/debian/changelog	2016-09-06 17:33:46.0 +0200
@@ -1,3 +1,16 @@
+libprelude (1.0.0-11.8) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "please drop the build dependency on hardening-wrapper", which causes
+the package to FTBFS:
+drop hardening-wrapper from debian/control and related variables from
+debian/rules.
+(Closes: #836636)
+  * Bring back some hardening via dpkg-buildflags and DEB_BUILD_MAINT_OPTIONS
+in debian/rules.
+
+ -- gregor herrmann   Tue, 06 Sep 2016 17:33:46 +0200
+
 libprelude (1.0.0-11.7) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libprelude-1.0.0/debian/control libprelude-1.0.0/debian/control
--- libprelude-1.0.0/debian/control	2014-08-12 19:55:04.0 +0200
+++ libprelude-1.0.0/debian/control	2016-09-06 16:51:48.0 +0200
@@ -14,8 +14,7 @@
 libltdl-dev,
 pkg-config,
 gawk,
-swig,
-hardening-wrapper
+swig
 Standards-Version: 3.9.3
 
 Package: libprelude-dev
diff -Nru libprelude-1.0.0/debian/rules libprelude-1.0.0/debian/rules
--- libprelude-1.0.0/debian/rules	2014-08-05 19:31:31.0 +0200
+++ libprelude-1.0.0/debian/rules	2016-09-06 17:22:16.0 +0200
@@ -1,8 +1,7 @@
 #!/usr/bin/make -f
 #export DH_VERBOSE=1
 
-export DEB_BUILD_HARDENING=1
-export DEB_BUILD_HARDENING_FORMAT=0
+export DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie
 
 PYVERS=$(shell pyversions -vr)
 


signature.asc
Description: Digital Signature

Bug#836859: python-tango-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc-base/pytango-manual

[Andreas Beckmann]

Package: python-tango-doc
Version: 9.2.0-1~exp2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package python-tango-doc.
  Preparing to unpack .../1-python-tango-doc_9.2.0-1~exp2_all.deb ...
  Unpacking python-tango-doc (9.2.0-1~exp2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-sbKRNt/1-python-tango-doc_9.2.0-1~exp2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc-base/pytango-manual', which is also in 
package python-pytango-doc 8.1.8-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-sbKRNt/1-python-tango-doc_9.2.0-1~exp2_all.deb


cheers,

Andreas


python-pytango-doc=8.1.8-2_python-tango-doc=9.2.0-1~exp2.log.gz
Description: application/gzip

Bug#836858: nomacs-l10n: fails to upgrade from 'sid' - trying to overwrite /usr/share/nomacs/translations/nomacs_als.qm

[Andreas Beckmann]

Package: nomacs-l10n
Version: 3.4.1+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package nomacs-l10n.
  Preparing to unpack .../2-nomacs-l10n_3.4.1+dfsg-1_all.deb ...
  Unpacking nomacs-l10n (3.4.1+dfsg-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-66zg4p/2-nomacs-l10n_3.4.1+dfsg-1_all.deb (--unpack):
   trying to overwrite '/usr/share/nomacs/translations/nomacs_als.qm', which is 
also in package nomacs 3.0.0+dfsg2-1+b1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-66zg4p/2-nomacs-l10n_3.4.1+dfsg-1_all.deb


cheers,

Andreas


nomacs=3.0.0+dfsg2-1+b1_nomacs-l10n=3.4.1+dfsg-1.log.gz
Description: application/gzip

Bug#836853: zfsutils-linux: fails to upgrade from 'jessie' - trying to overwrite /usr/share/man/man1/ztest.1.gz

[Andreas Beckmann]

Package: zfsutils-linux
Version: 0.6.5.7-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package zfsutils-linux.
  Preparing to unpack .../zfsutils-linux_0.6.5.7-2_amd64.deb ...
  Unpacking zfsutils-linux (0.6.5.7-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/zfsutils-linux_0.6.5.7-2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/ztest.1.gz', which is also in 
package zutils 1.3-4
  Processing triggers for libc-bin (2.19-18+deb8u4) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/zfsutils-linux_0.6.5.7-2_amd64.deb


cheers,

Andreas


zutils=1.3-4_zfsutils-linux=0.6.5.7-2.log.gz
Description: application/gzip

Bug#835075: [PATCH] use fake-pinentry (Closes: #835075)

[Daniel Kahn Gillmor]

Hi Gregor--

Thanks for the followup!

On Sat 2016-09-03 03:58:34 -0400, gregor herrmann wrote:
> 1) After the build finishes there are 6 instances of gpg-agent
>   running. In my cowbuilder setup this doesn't cause any issues and
>   they time out after some time (1 minute I guess).

right, those processes should time out after their temporary home
directories are removed.  I'm working with upstream on making that
timeout happen faster than a 1 minute delay, but it's not done yet.

> 2) autopkgtests initially failed with:
>
> t/30.inline-decrypt.t  
> 1..5
> ok 1 - An object of class 'MIME::Entity' isa 'MIME::Entity'
> gpg: keybox 
> '/tmp/autopkgtest.n6im1C/autopkgtest_tmp/smoke7NpYaR/mgtrYHsk/pubring.kbx' 
> created
> gpg: 
> /tmp/autopkgtest.n6im1C/autopkgtest_tmp/smoke7NpYaR/mgtrYHsk/trustdb.gpg: 
> trustdb created
> gpg: key 49539D60EFEA4EAD marked as ultimately trusted
> gpg: key 49539D60EFEA4EAD: public key "Mail::GnuPG Test Key " 
> imported
> gpg: key 49539D60EFEA4EAD/49539D60EFEA4EAD: error sending to agent: No 
> pinentry
> gpg: error building skey array: No pinentry
> [..]

Sounds like autopkgtests needs to also use fake-pinentry.pl, as you
pointed out in (4) ;)

Once this changeset is included upstream, we won't need the "chmod +x" any
longer.

> 3) This is in schroot-on-lvm. And here unmounting fails because of the
>running gpg-agents leaving my schroot/lvm setup in a sad state.

right, but this is a different issue, related to gpg-agent not.
terminating rapidly enough when its socket is removed (same as (1)).
I'm happy to track this as an issue, but it is a different issue than
835075.

> Alltogether I think we need to think a bit more about this gpg-agent
> thing, currently this seems a bit too fragile to me.
>
> Another question is if we could have a fake-pinentry in some central
> place (gnupg binary package?) to be used from all packages instead of
> adding it everywhere?

I am happy to ship something like fake-pinentry.pl (a pinentry that
always returns "passphrase" and gamely accepts anything else) in a
separate package, or even in gnupg as /usr/lib/gnupg/fake-pinentry, but
it seems more important for me to get these fixes upstreamed.

I could even ship upstream's ./tests/openpgp/fake-pinentry.c there,
though i worry that it now has too many features, which might actually
encourage people to try to use it in non-dev environments; i think that
would be a bad outcome.

Also, for language-specific libraries like lib*-perl, upstream will want
this stuff to work on all platforms, and we can't guarantee that any
gnupg binary package on other platforms will ship a fake-pinentry.

So i think we should go ahead with this patch, as well as submitting it
upstream.  I'm happy to try to replicate it on the other lib*-perl
gnupg-related packages too if you're ok with this.

Regards,

   --dkg


signature.asc
Description: PGP signature

Bug#836851: python-django-registration-doc: fails to upgrade from 'jessie' - trying to overwrite /usr/share/doc-base/django-registration-overview

[Andreas Beckmann]

Package: python-django-registration-doc
Version: 2.1.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package python-django-registration-doc.
  Preparing to unpack .../python-django-registration-doc_2.1.2-2_all.deb ...
  Unpacking python-django-registration-doc (2.1.2-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-django-registration-doc_2.1.2-2_all.deb 
(--unpack):
   trying to overwrite '/usr/share/doc-base/django-registration-overview', 
which is also in package python-django-registration 1.0+dfsg-2
  Errors were encountered while processing:
   /var/cache/apt/archives/python-django-registration-doc_2.1.2-2_all.deb


cheers,

Andreas


python-django-registration=1.0+dfsg-2_python-django-registration-doc=2.1.2-2.log.gz
Description: application/gzip

Bug#836850: pymca-doc: fails to upgrade from 'jessie' - trying to overwrite /usr/share/doc-base/pymca

[PICCA Frederic-Emmanuel]

Hello Andreas, what is strange is this

https://piuparts.debian.org/sid/state-successfully-tested.html#pymca-doc

Is there a problem with piuparts ?

Processed: found 836717 in 15.04-4, found 836717 in 16.04-1, found 836718 in 16.04-1, found 836718 in 15.09-2 ...

[Debian Bug Tracking System]

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

> found 836717 15.04-4
Bug #836717 [alljoyn-services-1504,alljoyn-services-1604] alljoyn-services-1604 
and alljoyn-services-1504: error when trying to install together
There is no source info for the package 'alljoyn-services-1604' at version 
'15.04-4' with architecture ''
Marked as found in versions alljoyn-services-1504/15.04-4.
> found 836717 16.04-1
Bug #836717 [alljoyn-services-1504,alljoyn-services-1604] alljoyn-services-1604 
and alljoyn-services-1504: error when trying to install together
There is no source info for the package 'alljoyn-services-1504' at version 
'16.04-1' with architecture ''
Marked as found in versions alljoyn-services-1604/16.04-1.
> found 836718 16.04-1
Bug #836718 [alljoyn-services-1509,alljoyn-services-1604] alljoyn-services-1604 
and alljoyn-services-1509: error when trying to install together
There is no source info for the package 'alljoyn-services-1509' at version 
'16.04-1' with architecture ''
Marked as found in versions alljoyn-services-1604/16.04-1.
> found 836718 15.09-2
Bug #836718 [alljoyn-services-1509,alljoyn-services-1604] alljoyn-services-1604 
and alljoyn-services-1509: error when trying to install together
There is no source info for the package 'alljoyn-services-1604' at version 
'15.09-2' with architecture ''
Marked as found in versions alljoyn-services-1509/15.09-2.
> found 836719 15.04-4
Bug #836719 [liballjoynservices1504,liballjoynservices1604] 
liballjoynservices1604 and liballjoynservices1504: error when trying to install 
together
There is no source info for the package 'liballjoynservices1604' at version 
'15.04-4' with architecture ''
Marked as found in versions alljoyn-services-1504/15.04-4.
> found 836719 16.04-1
Bug #836719 [liballjoynservices1504,liballjoynservices1604] 
liballjoynservices1604 and liballjoynservices1504: error when trying to install 
together
There is no source info for the package 'liballjoynservices1504' at version 
'16.04-1' with architecture ''
Marked as found in versions alljoyn-services-1604/16.04-1.
> thanks
Stopping processing here.

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

Bug#836850: pymca-doc: fails to upgrade from 'jessie' - trying to overwrite /usr/share/doc-base/pymca

[Andreas Beckmann]

Package: pymca-doc
Version: 5.1.2+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package pymca-doc.
  Preparing to unpack .../pymca-doc_5.1.2+dfsg-1_all.deb ...
  Unpacking pymca-doc (5.1.2+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/pymca-doc_5.1.2+dfsg-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc-base/pymca', which is also in package 
pymca 4.7.4+dfsg-1
  Processing triggers for fontconfig (2.11.0-6.3) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/pymca-doc_5.1.2+dfsg-1_all.deb


cheers,

Andreas


pymca=4.7.4+dfsg-1_pymca-doc=5.1.2+dfsg-1.log.gz
Description: application/gzip

Processed: Re: hardening-wrapper breakage

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #836636 [libprelude] libprelude: please drop the build dependency on 
hardening-wrapper
Severity set to 'serious' from 'important'

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

Bug#833753: ledger: FTBFS on buildds after gcc6/icu57/boost1.61

[Matthias Liertzer]

This is most likely a gcc6 bug. When compiling ledger with clang via

DEB_BUILD_MAINT_OPTIONS=reproducible=-fixdebugpath CC=clang-3.8
CXX=clang++-3.8 dpkg-buildpackage

the package compiles successfully. Note, that clang-3.8 is needed
otherwise linking fails due to bug #797917.

Bug#836847: libmxml-bin: fails to upgrade from 'testing' - trying to overwrite /usr/bin/mxmldoc

[Andreas Beckmann]

Package: libmxml-bin
Version: 2.9-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libmxml-bin.
  Preparing to unpack .../1-libmxml-bin_2.9-3_amd64.deb ...
  Unpacking libmxml-bin (2.9-3) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-BT4BKF/1-libmxml-bin_2.9-3_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/mxmldoc', which is also in package libmxml-dev 
2.9-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-BT4BKF/1-libmxml-bin_2.9-3_amd64.deb


cheers,

Andreas


libmxml-dev=2.9-2_libmxml-bin=2.9-3.log.gz
Description: application/gzip

Bug#835966: RM: polyorb -- RoQA; unmaintained, RC-buggy

[Svante Signell]

On Tue, 2016-09-06 at 11:17 +0200, Xavier Grave wrote:
> You should also run the po_cos_naming, you can look at [1] in order to see how
> to "play" with dsa applications.
> 
> xavier
> [1] : http://wiki.ada-dk.org/a_dsa_tutorial
> 
The dsa exammple in that web page works!

The bank example almost works too:
(after changing 192.168.1.1:9099 to 127.0.0.1:9099)

./bank_server
...
Request : p

=> Print

   Customer : poor
   Password : 
   Balance  :  25

   Customer : middle
   Password : 
   Balance  :  250

   Customer : rich
   Password : 
   Balance  :  2500


Menu :

   Create
   Load
   Print
   Quit
   Save

Request : 

./bank_client
polyorb.utils.tcp_access_points: bind failed: [98] Address already in use

raised GNAT.SOCKETS.SOCKET_ERROR : [98] Address already in use

Bug#836846: Remove "Recommends: socklog-run" due to clash with systemd

[Jeroen Massar]

Package: runit
Version: 2.1.2-3
Severity: grave

Reporting for a friend...

Currently trying to install runit causes socklog-run to be 'suggested' and 
installed, which clashes with systemd which kinda removes your system when you 
don't pay attention. (Done on throw-away VM thus no harm came to it)

Please remove the recommend of socklog-run (or make that work with systemd).

Noting that socklog-run has:
```
Conflicts: linux-kernel-log-daemon, system-log-daemon
```

which is what clashes with systemd. As Debian chose to let systemd be the evil 
default well, no way to be suggesting socklog-run that conflicts then


Indeed, setting APT::Install-Recommends "0"; or using -—no-install-recommands 
would avoid the system from breaking... but those are not Debian defaults 
(though they should be ;)

Greets,
 Jeroen

```
root@box:~# apt-get install runit
Reading package lists... Done
Building dependency tree 
Reading state information... Done
The following extra packages will be installed:
fgetty runit sysvinit-core
Suggested packages:
socklog-run
The following packages will be REMOVED:
systemd systemd-sysv
The following NEW packages will be installed:
fgetty runit sysvinit-core
0 upgraded, 4 newly installed, 2 to remove and 0 not upgraded.
Need to get 278 kB of archives.
After this operation, 13.5 MB disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 http://ftp.us.debian.org/debian/ jessie/main sysvinit-core amd64 
2.88dsf-59 [132 kB]
Get:2 http://ftp.us.debian.org/debian/ jessie/main fgetty amd64 0.6-5 [25.9 kB] 
Get:3 http://ftp.us.debian.org/debian/ jessie/main runit amd64 2.1.2-3 [117 kB]
Fetched 278 kB in 0s (446 kB/s)
Preconfiguring packages ...
dpkg: systemd-sysv: dependency problems, but removing anyway as you requested:
init depends on systemd-sysv | sysvinit-core | upstart; however:
Package systemd-sysv is to be removed.
Package sysvinit-core is not installed.
Package upstart is not installed.

(Reading database ... 30202 files and directories currently installed.)
Removing systemd-sysv (215-17+deb8u4) ...
Processing triggers for man-db (2.7.0.2-5) ...
Selecting previously unselected package sysvinit-core.
(Reading database ... 30185 files and directories currently installed.)
Preparing to unpack .../sysvinit-core_2.88dsf-59_amd64.deb ...
Unpacking sysvinit-core (2.88dsf-59) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up sysvinit-core (2.88dsf-59) ...
Not restarting sysvinit
(Reading database ... 30210 files and directories currently installed.)
Removing systemd (215-17+deb8u4) ...
systemd is the active init system, please switch to another before removing 
systemd.
dpkg: error processing package systemd (--remove):
subprocess installed pre-removal script returned error exit status 1
Failed to stop lib-init-rw.mount: Unit lib-init-rw.mount not loaded.
addgroup: The group `systemd-journal' already exists as a system group. Exiting.
Errors were encountered while processing:
systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)
```

Bug#836842: pcp: B-D libpapi-dev is not available on s390x

[Andreas Beckmann]

Source: pcp
Version: 3.11.3.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

papi does not (yet) support s390x. Please build pcp without papi on that
architecture.


Andreas

Bug#836839: fwupdate: FTBFS against efivar 27

[Mario_Limonciello]

Thanks for reporting. This is already fixed in git, just waiting on a sponsor.

On Sep 06, 2016, 08:27 AM, Andreas Beckmann  wrote:


Source: fwupdate
Version: 0.5-4
Severity: serious
Justification: fails to build from source

Hi,

fwupdate FTBFS against the new efivar in sid:

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

make[3]: Entering directory '/«PKGBUILDDIR»/linux'
Package efiboot was not found in the pkg-config search path.
Perhaps you should add the directory containing `efiboot.pc'
to the PKG_CONFIG_PATH environment variable
No package 'efiboot' found
gcc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wno-unused-result -Wno-unused-function 
-Wsign-compare -Werror=sign-compare -fshort-wchar --std=gnu11 
-DLOCALEDIR=\"/usr/share/locale/\" -D_GNU_SOURCE -DFWUP_EFI_DIR_NAME=\"debian\" 
-I/«PKGBUILDDIR»/linux/include -iquote/«PKGBUILDDIR»/include/  
-I/usr/include/efivar-fPIC -c -o libfwup.o libfwup.c
libfwup.c:12:21: fatal error: efiboot.h: No such file or directory
 #include 
 ^
compilation terminated.


Andreas

Bug#836714: security upload for Charybdis

[Antoine Beaupré]

On 2016-09-06 02:53:51, Moritz Muehlenhoff wrote:
> Thanks. Looks good, please build with "-sa" and upload to security-master.

Done, thanks.

A.

-- 
Lorsque l'on range des objets dans des tiroirs, et que l'on a plus
d'objets que de tiroirs, alors un tiroir au moins contient deux
objets.
- Lejeune-Dirichlet, Peter Gustav

Processed: bug 836833 is forwarded to https://github.com/bestpractical/rt/pull/195

[Debian Bug Tracking System]

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

> forwarded 836833 https://github.com/bestpractical/rt/pull/195
Bug #836833 [src:request-tracker4] request-tracker4: FTBFS with '.' removed 
from @INC
Set Bug forwarded-to-address to 'https://github.com/bestpractical/rt/pull/195'.
> thanks
Stopping processing here.

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

Bug#836839: fwupdate: FTBFS against efivar 27

[Andreas Beckmann]

Source: fwupdate
Version: 0.5-4
Severity: serious
Justification: fails to build from source

Hi,

fwupdate FTBFS against the new efivar in sid:

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

make[3]: Entering directory '/«PKGBUILDDIR»/linux'
Package efiboot was not found in the pkg-config search path.
Perhaps you should add the directory containing `efiboot.pc'
to the PKG_CONFIG_PATH environment variable
No package 'efiboot' found
gcc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wno-unused-result -Wno-unused-function 
-Wsign-compare -Werror=sign-compare -fshort-wchar --std=gnu11 
-DLOCALEDIR=\"/usr/share/locale/\" -D_GNU_SOURCE -DFWUP_EFI_DIR_NAME=\"debian\" 
-I/«PKGBUILDDIR»/linux/include -iquote/«PKGBUILDDIR»/include/  
-I/usr/include/efivar-fPIC -c -o libfwup.o libfwup.c
libfwup.c:12:21: fatal error: efiboot.h: No such file or directory
 #include 
 ^
compilation terminated.


Andreas

Bug#836669: caja: Crashes due to theme errors

[Fernando C. Estrada]

Followup-For: Bug #836669
Package: caja
Version: 1.14.2-1

Dear Maintainer,

I confirm this report, when I start caja it crashes with the following
output (terminal):

(caja:3620): Gtk-WARNING **: Theme parsing error:
mate-applications.css:415:16: not a number

(caja:3620): Gtk-WARNING **: Theme parsing error:
mate-applications.css:415:16: Expected a string.

(caja:3620): Gtk-WARNING **: Theme parsing error:
other-applications.css:146:13: not a number

(caja:3620): Gtk-WARNING **: Theme parsing error:
other-applications.css:146:13: Expected a string.

Best Regards,

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

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

Versions of packages caja depends on:
ii  caja-common   1.14.2-1
ii  desktop-file-utils0.23-1
ii  gvfs  1.29.91-1
ii  libatk1.0-0   2.20.0-1
ii  libc6 2.23-5
ii  libcairo-gobject2 1.14.6-1+b1
ii  libcairo2 1.14.6-1+b1
ii  libcaja-extension11.14.2-1
ii  libexempi32.3.0-2
ii  libexif12 0.6.21-2
ii  libgail-3-0   3.21.5-3
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.49.6-1
ii  libglib2.0-data   2.49.6-1
ii  libgtk-3-03.21.5-3
ii  libice6   2:1.0.9-1+b1
ii  libmate-desktop-2-17  1.14.1-1
ii  libpango-1.0-01.40.2-1
ii  libpangocairo-1.0-0   1.40.2-1
ii  libselinux1   2.5-3
ii  libsm62:1.2.2-1+b1
ii  libstartup-notification0  0.12-4
ii  libunique-3.0-0   3.0.2-2
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.4+dfsg1-1+b1
ii  libxrender1   1:0.9.9-2
ii  mate-desktop  1.14.1-1
ii  shared-mime-info  1.6-1

Versions of packages caja recommends:
ii  gvfs-backends  1.29.91-1

Versions of packages caja suggests:
ii  engrampa1.14.1-1
pn  gstreamer1.0-tools  
ii  meld3.16.2-1

-- no debconf information
-- 
Fernando C. Estrada

Processed: Re: Bug#836508: barbican: FTBFS in testing (failing tests)

[Debian Bug Tracking System]

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

> found 836508 1:2.0.0-5
Bug #836508 {Done: Thomas Goirand } [src:barbican] barbican: 
FTBFS in testing (failing tests)
Did not alter found versions and reopened.
> tags 836508 + patch
Bug #836508 [src:barbican] barbican: FTBFS in testing (failing tests)
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: Re: Bug#836509: glance: FTBFS in testing (failing tests)

[Debian Bug Tracking System]

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

> found 836509 2:12.0.0-4
Bug #836509 {Done: Thomas Goirand } [src:glance] glance: 
FTBFS in testing (failing tests)
Did not alter found versions and reopened.
> tags 836509 + patch
Bug #836509 [src:glance] glance: FTBFS in testing (failing tests)
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#836509: glance: FTBFS in testing (failing tests)

[Santiago Vila]

found 836509 2:12.0.0-4
tags 836509 + patch
thanks

On Tue, Sep 06, 2016 at 02:17:54PM +0200, Thomas Goirand wrote:

> FYI, according to James Page, this was due to #836179.

That's a way to see it, but if you mean this package needs to be built
with pyopenssl >= 16.1.0 because otherwise the build fails, that's
precisely why we have versioned build-depends.

This kind of bugs should never happen in testing.

--- a/debian/control
+++ b/debian/control
@@ -40,7 +40,7 @@ Build-Depends-Indep: bandit,
  python-monotonic (>= 0.6),
  python-mox3,
  python-mysqldb,
- python-openssl,
+ python-openssl (>= 16.1.0),
  python-oslo.concurrency (>= 3.5.0),
  python-oslo.config (>= 1:3.7.0),
  python-oslo.context (>= 0.2.0),

Bug#836509: [PKG-Openstack-devel] Bug#836509: glance: FTBFS in testing (failing tests)

[James Page]

On Tue, 6 Sep 2016 at 13:57 Santiago Vila  wrote:

> > FYI, according to James Page, this was due to #836179.
>
> That's a way to see it, but if you mean this package needs to be built
> with pyopenssl >= 16.1.0 because otherwise the build fails, that's
> precisely why we have versioned build-depends.
>
> This kind of bugs should never happen in testing.


Neither glance nor barbican require pyopenssl 16.1.0; the problem was that
python-crytography was updated to 1.5, which broke pyopenssl 16.0.0 which
is not compatible with cryptography 1.5.  So the break in is pyopenssl IMHO
(as it was not functional) not in barbican or glance, resulting in this
transient build failure while that got sorted out.

Bug#831591: ffmpeg: kodi crash

[Bálint Réczey]

Hi Carl,

2016-09-06 12:41 GMT+02:00 Carl Eugen Hoyos :
> Hi!
>
>> Knowing what broke could be
>> interesting for FFmpeg devs
>
> It would most likely be even more interesting
> for the Kodi developers: We currently assume
> that there is an unknown bug in Kodi...

Well, the first suspect is ffmpeg because updating ffmpeg
broke kodi while there were no planned ABI change.

>
>> > Slightly related: More that half of the open tickets
>> > concerning FFmpeg in Debian either contain no samples to
>> > reproduce or will not be fixed or were never reproducible.
>> > If another FFmpeg developer were interested in fixing
>> > bugs reported here it would be very difficult for him to
>> > find something useful due to the low snr.
>>
>> Those can be marked with the moreinfo tag and IMO it is
>> OK to close them after a reasonable amount of time if
>> the originator is asked to provide a test file but she/he
>> did not.
>
> Are five months enough?

Generally I use a few years if I'm not pretty sure the bug is gone.
I agree with the concept that bugs are part of the documentation
thus closing possibly valid bugs is decreasing the quality of the
documentation, thus the software.

Note that there are way more users of stable and a bug not
reproducible on unstable may show up in stable later.

I went throught the unclassified bugs and set the proper state
to help tracking them.

Cheers,
Balint

Bug#836246: marked as done (libgtk-3-0: Upgrade from 3.20.9 to 3.21.5 broke Mate desktop)

[Debian Bug Tracking System]

Your message dated Tue, 6 Sep 2016 14:53:56 +0200
with message-id 
and subject line Re: Bug#836246: libgtk-3-0: Upgrade from 3.20.9 to 3.21.5 
broke Mate desktop
has caused the Debian Bug report #836246,
regarding libgtk-3-0: Upgrade from 3.20.9 to 3.21.5 broke Mate desktop
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.)


-- 
836246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgtk-3-0
Version: 3.20.9-1
Severity: normal

On three pc of mine i had to downgrade the following libraries to have a
functioning desktop:
libgail-3-0
libgtk-3-0
libgtk-3-bin

Up to version 3.20.9-1 all were fine but with 3.21.5-1 and 3.21.5-2 i
had so many issues that i had to find a way to come back to a previous
state.
These are the issue i can document, but certainly there are others:
- caja (file manager) doesn't start at all.
- desktop fonts look ugly, like there isn't any antialias.
- desktop doesn't repaint correctly: if you move an icon, the older is
  still there.
- mate terminal crash if you try to change color settings.

Journalctl reports tons of entries like those, indeed belonging to
applets that updates their visualization frequently:
--
ago 31 19:52:16 barone mate-cpufreq-ap[15177]: gtk_widget_size_allocate(): 
attempt to underallocate CPUFreqApplet's child GtkAlignment 0x8049a148. 
Allocation is 55x24, but minimum required size is 83x24.
ago 31 19:52:16 barone mate-cpufreq-ap[15177]: gtk_widget_size_allocate(): 
attempt to underallocate GtkAlignment's child GtkBox 0x80333fb8. Allocation is 
55x24, but minimum required size is 83x24.
ago 31 19:52:16 barone mate-cpufreq-ap[15177]: gtk_widget_size_allocate(): 
attempt to underallocate CPUFreqApplet's child GtkAlignment 0x8049a250. 
Allocation is 55x24, but minimum required size is 83x24.
ago 31 19:52:16 barone mate-cpufreq-ap[15177]: gtk_widget_size_allocate(): 
attempt to underallocate GtkAlignment's child GtkBox 0x80333ce8. Allocation is 
55x24, but minimum required size is 83x24.
ago 31 19:52:16 barone clock-applet[15178]: gtk_widget_size_allocate(): attempt 
to underallocate toplevel GtkPlug 0x80c171d0. Allocation is 178x24, but minimum 
required size is 178x26.
ago 31 19:52:16 barone clock-applet[15178]: gtk_widget_size_allocate(): attempt 
to underallocate GtkPlug's child MatePanelApplet 0x80adb138. Allocation is 
178x24, but minimum required size is 178x26.
ago 31 19:52:16 barone clock-applet[15178]: gtk_widget_size_allocate(): attempt 
to underallocate MatePanelApplet's child GtkToggleButton 0x80ae9898. Allocation 
is 178x24, but minimum required size is 178x26.
ago 31 19:52:16 barone clock-applet[15178]: gtk_widget_size_allocate(): attempt 
to underallocate GtkToggleButton's child ClockBox 0x80ce14a8. Allocation is 
168x14, but minimum required size is 168x16.
ago 31 19:52:16 barone clock-applet[15178]: gtk_widget_size_allocate(): attempt 
to underallocate ClockBox's child ClockBox 0x80ce1598. Allocation is 18x14, but 
minimum required size is 18x16.
ago 31 19:52:16 barone clock-applet[15178]: gtk_widget_size_allocate(): attempt 
to underallocate ClockBox's child GtkLabel 0x80cddc58. Allocation is 138x14, 
but minimum required size is 138x15.
--

The same issues happened on four different machine, with different
gtk theme, adwaita included: a 686, a 686-pae, two amd64.
On one of them i've installed a fresh Mate Desktop, so i think we could
say that the problem is always reproducible. You can try: i've just
installed task-mate-desktop, without any recommended or suggested packages.

I don't know what other infos i can provide.
I've kept a 686 PC with the broken libraries available in case you need
more infos or in case you want me to make some tests.

Cesare.


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

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

Versions of packages libgtk-3-0 depends on:
ii  adwaita-icon-theme  3.20-3
ii  hicolor-icon-theme  0.15-1
ii  libatk-bridge2.0-0  2.20.1-4
ii  libatk1.0-0 2.20.0-1
ii  libc6   2.23-5
ii  libcairo-gobject2   1.14.6-1+b1
ii  libcairo2   

Bug#836508: barbican: FTBFS in testing (failing tests)

[Santiago Vila]

found 836508 1:2.0.0-5
tags 836508 + patch
thanks

On Tue, Sep 06, 2016 at 02:18:33PM +0200, Thomas Goirand wrote:

> FYI, according to James Page, this was due to #836179.

That's a way to see it, but if you mean this package needs to be built
with pyopenssl >= 16.1.0 because otherwise the build fails, that's
precisely why we have versioned build-depends.

This kind of bugs should never happen in testing.

--- a/debian/control
+++ b/debian/control
@@ -30,7 +30,7 @@ Build-Depends-Indep: alembic (>= 0.8.0),
  python-pykmip (>= 0.4.0),
  python-ldap3 (>= 0.9.8.2),
  python-mock (>= 1.3),
- python-openssl (>= 0.14),
+ python-openssl (>= 16.1.0),
  python-openstackdocstheme (>= 1.0.3),
  python-oslo.context (>= 0.2.0),
  python-oslo.concurrency (>= 3.5.0),

Bug#834158: marked as pending

[Jaromír Mikeš]

tag 834158 pending
thanks

Hello,

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

http://git.debian.org/?p=pkg-multimedia/lvtk.git;a=commitdiff;h=29b51d9

---
commit 29b51d9e90b3b57f5937b8b0c899378e6e411bb8
Author: Jaromír Mikeš 
Date:   Tue Sep 6 14:27:15 2016 +0200

Finalize changelog.

diff --git a/debian/changelog b/debian/changelog
index 38b7a4d..c0c71f7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,15 @@
-lvtk (1.2.0~dfsg0-2) UNRELEASED; urgency=medium
+lvtk (1.2.0~dfsg0-2) unstable; urgency=medium
 
-  * Start new upload.
+  * Add b-d libboost-system-dev & link it. (Closes: #834158)
+  * Bump Standards.
+  * Fix VCS fields.
+  * Update copyright file.
+  * Fix some hardening.
+  * Section sound for lvtk-tools package.
+  * Not install md5 files in doc package.
+  * Avoid curly brackets.
+  * Add patch to fix pkg-config-bad-directive.
+  * Enable parallel build.
 
  -- Jaromír Mikeš   Wed, 31 Aug 2016 17:25:44 +0200
 

Bug#836452: marked as done (givaro: FTBFS when built with dpkg-buildpackage -A (chmod: cannot access '[...]/isgenerator.C': No such file or directory))

[Debian Bug Tracking System]

Your message dated Tue, 06 Sep 2016 12:33:44 +
with message-id 
and subject line Bug#836452: fixed in givaro 4.0.2-3
has caused the Debian Bug report #836452,
regarding givaro: FTBFS when built with dpkg-buildpackage -A (chmod: cannot 
access '[...]/isgenerator.C': 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.)


-- 
836452: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:givaro
Version: 4.0.2-2
Severity: serious
Tags: patch

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with autoreconf 
   dh_testdir -i
   dh_update_autotools_config -i
   dh_autoreconf -i
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'macros'.
libtoolize: copying file 'macros/libtool.m4'
libtoolize: copying file 'macros/ltoptions.m4'
libtoolize: copying file 'macros/ltsugar.m4'
libtoolize: copying file 'macros/ltversion.m4'
libtoolize: copying file 'macros/lt~obsolete.m4'

[... snipped ...]

make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/examples/RecInt'
make[3]: Leaving directory '/<>/examples/RecInt'
make[3]: Entering directory '/<>/examples'
make[4]: Entering directory '/<>/examples'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/examples'
make[3]: Leaving directory '/<>/examples'
make[2]: Leaving directory '/<>/examples'
Making install in benchmarks
make[2]: Entering directory '/<>/benchmarks'
make[3]: Entering directory '/<>/benchmarks'
make[4]: Entering directory '/<>/benchmarks'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/benchmarks'
make[3]: Leaving directory '/<>/benchmarks'
make[2]: Leaving directory '/<>/benchmarks'
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>'
 /bin/mkdir -p '/<>/debian/tmp/usr/bin'
 /usr/bin/install -c givaro-config givaro-makefile 
'/<>/debian/tmp/usr/bin'
 /bin/mkdir -p '/<>/debian/tmp/usr/include'
 /usr/bin/install -c -m 644 givaro-config.h 
'/<>/debian/tmp/usr/include'
 /bin/mkdir -p '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
 /usr/bin/install -c -m 644 givaro.pc 
'/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_install -i
   dh_installdocs -i
   dh_installchangelogs -i
   debian/rules override_dh_installexamples
make[1]: Entering directory '/<>'
dh_installexamples -XMakefile -XMakefile.am -XMakefile.in
make[1]: Leaving directory '/<>'
   dh_lintian -i
   dh_perl -i
   dh_link -i
   dh_strip_nondeterminism -i
   dh_compress -i
   debian/rules override_dh_fixperms
make[1]: Entering directory '/<>'
dh_fixperms
chmod -x 
debian/libgivaro-dev/usr/share/doc/libgivaro-dev/examples/Polynomial/isgenerator.C
chmod: cannot access 
'debian/libgivaro-dev/usr/share/doc/libgivaro-dev/examples/Polynomial/isgenerator.C':
 No such file or directory
debian/rules:35: recipe for target 'override_dh_fixperms' failed
make[1]: *** [override_dh_fixperms] Error 1
make[1]: Leaving directory '/<>'
debian/rules:41: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


This happens because debian/libgivaro-dev/[...] does not exist,
as we are creating arch-independent packages only and libgivaro-dev
is "Arch: any".

The patch below (trivial but untested) might fix this.

Thanks.

--- a/debian/rules
+++ b/debian/rules
@@ -31,7 +31,7 @@ override_dh_auto_build-indep:
 override_dh_auto_test:
dh_auto_test --max-parallel=1
 
-override_dh_fixperms:
+override_dh_fixperms-arch:
dh_fixperms
chmod -x 
debian/libgivaro-dev/usr/share/doc/libgivaro-dev/examples/Polynomial/isgenerator.C
 
--- End Message ---
--- Begin Message ---
Source: givaro
Source-Version: 4.0.2-3

We believe that the bug you reported is fixed in the 

Processed: Bug#834158 marked as pending

[Debian Bug Tracking System]

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

> tag 834158 pending
Bug #834158 [src:lvtk] lvtk: FTBFS: boost/system/error_code.hpp:221: undefined 
reference to `boost::system::generic_category()'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: limit source to request-tracker4, tagging 836833, tagging 835536

[Debian Bug Tracking System]

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

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

> tags 836833 + pending
Bug #836833 [src:request-tracker4] request-tracker4: FTBFS with '.' removed 
from @INC
Added tag(s) pending.
> tags 835536 + pending
Bug #835536 [src:request-tracker4] request-tracker4: FTBFS with gnupg 2.1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#836509: marked as done (glance: FTBFS in testing (failing tests))

[Debian Bug Tracking System]

Your message dated Tue, 6 Sep 2016 14:17:54 +0200
with message-id 
and subject line Re: Bug#836509: glance: FTBFS in testing (failing tests)
has caused the Debian Bug report #836509,
regarding glance: FTBFS in testing (failing tests)
to be marked as done.

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

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


-- 
836509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:glance
Version: 2:12.0.0-4
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python2,sphinxdoc,systemd
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions

[... snipped ...]

glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_non_integer_limit
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_non_integer_limit
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_dir_asc
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_dir_asc
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_dir_bad_value
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_dir_bad_value
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_key_id
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_key_id
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_strip_params_from_filters
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_strip_params_from_filters
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_with_filter_and_limit
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_with_filter_and_limit
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_with_many_filter
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_with_many_filter
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_zero_limit
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_zero_limit
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_create
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_create ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_create_ensure_expires_at_is_not_returned
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_create_ensure_expires_at_is_not_returned
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_get
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_get ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_get_ensure_expires_at_not_returned
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_get_ensure_expires_at_not_returned
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index_carries_query_parameters
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index_carries_query_parameters
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index_next_marker
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index_next_marker
 ... ok

==
FAIL: glance.tests.unit.common.test_utils.TestUtils.test_validate_key_cert_key

Bug#836508: marked as done (barbican: FTBFS in testing (failing tests))

[Debian Bug Tracking System]

Your message dated Tue, 6 Sep 2016 14:18:33 +0200
with message-id 
and subject line Re: Bug#836508: barbican: FTBFS in testing (failing tests)
has caused the Debian Bug report #836508,
regarding barbican: FTBFS in testing (failing tests)
to be marked as done.

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

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


-- 
836508: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:barbican
Version: 1:2.0.0-5
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python2,systemd,sphinxdoc
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions

[... snipped ...]

barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_handle_success_result_large_statuses_clipped
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_handle_success_result_large_statuses_clipped
 ... ok
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_handle_success_result_no_follow_on_needed
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_handle_success_result_no_follow_on_needed
 ... ok
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_retrieve_entity
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_retrieve_entity
 ... ok

==
FAIL: 
barbican.tests.plugin.test_snakeoil_ca.CertManagerTestCase.test_gen_cert_no_file_storage
barbican.tests.plugin.test_snakeoil_ca.CertManagerTestCase.test_gen_cert_no_file_storage
--
_StringException: Empty attachments:
  pythonlogging:''
  stderr
  stdout

Traceback (most recent call last):
  File "barbican/tests/plugin/test_snakeoil_ca.py", line 166, in 
test_gen_cert_no_file_storage
self.verify_sig(cert_enc)
  File "barbican/tests/plugin/test_snakeoil_ca.py", line 157, in verify_sig
crypto.verify(self.ca.cert, sig[1:], der[0], 'sha256')
  File "/usr/lib/python2.7/dist-packages/OpenSSL/crypto.py", line 2605, in 
verify
md_ctx = _ffi.new("EVP_MD_CTX*")
TypeError: cannot instantiate ctype 'EVP_MD_CTX' of unknown size


==
FAIL: 
barbican.tests.plugin.test_snakeoil_ca.CertManagerTestCase.test_gen_cert_with_file_storage
barbican.tests.plugin.test_snakeoil_ca.CertManagerTestCase.test_gen_cert_with_file_storage
--
_StringException: Empty attachments:
  pythonlogging:''
  stderr
  stdout

Traceback (most recent call last):
  File "barbican/tests/plugin/test_snakeoil_ca.py", line 182, in 
test_gen_cert_with_file_storage
self.verify_sig(cert_enc)
  File "barbican/tests/plugin/test_snakeoil_ca.py", line 157, in verify_sig
crypto.verify(self.ca.cert, sig[1:], der[0], 'sha256')
  File "/usr/lib/python2.7/dist-packages/OpenSSL/crypto.py", line 2605, in 
verify
md_ctx = _ffi.new("EVP_MD_CTX*")
TypeError: cannot instantiate ctype 'EVP_MD_CTX' of unknown size


--
Ran 1216 tests in 80.278s

FAILED (failures=2, skipped=4)
debian/rules:20: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:9: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2

Bug#836833: request-tracker4: FTBFS with '.' removed from @INC

[Dominic Hargreaves]

Source: request-tracker4
Version: 4.2.13-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: perl-cwd-inc-removal
Tags: patch

As reported in #835536 this package FTBFS with no '.' in @INC.
Patch from Niko attached.
>From 9251965c2ee5f9e23a9b196aad97fe404343b386 Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Sun, 4 Sep 2016 11:41:29 +0300
Subject: [PATCH] Fix RT::I18N and the test suite to work without cwd in @INC

---
 lib/RT/I18N.pm | 5 +++--
 t/lifecycles/basics.t  | 2 +-
 t/lifecycles/dates.t   | 2 +-
 t/lifecycles/moving.t  | 2 +-
 t/lifecycles/types.t   | 2 +-
 t/lifecycles/unresolved-deps.t | 2 +-
 6 files changed, 8 insertions(+), 7 deletions(-)

diff --git a/lib/RT/I18N.pm b/lib/RT/I18N.pm
index 60a6622..1bf0b57 100644
--- a/lib/RT/I18N.pm
+++ b/lib/RT/I18N.pm
@@ -56,6 +56,7 @@ package RT::I18N;
 
 use strict;
 use warnings;
+use Cwd ();
 
 
 use Locale::Maketext 1.04;
@@ -97,10 +98,10 @@ sub Init {
 @lang = ('*') unless @lang;
 
 # load default functions
-require substr(__FILE__, 0, -3) . '/i_default.pm';
+require substr(Cwd::abs_path(__FILE__), 0, -3) . '/i_default.pm';
 
 # Load language-specific functions
-foreach my $file ( File::Glob::bsd_glob(substr(__FILE__, 0, -3) . "/*.pm") ) {
+foreach my $file ( File::Glob::bsd_glob(substr(Cwd::abs_path(__FILE__), 0, -3) . "/*.pm") ) {
 my ($lang) = ($file =~ /([^\\\/]+?)\.pm$/);
 next unless grep $_ eq '*' || $_ eq $lang, @lang;
 require $file;
diff --git a/t/lifecycles/basics.t b/t/lifecycles/basics.t
index e18bea3..85e77c7 100644
--- a/t/lifecycles/basics.t
+++ b/t/lifecycles/basics.t
@@ -1,7 +1,7 @@
 use strict;
 use warnings;
 
-BEGIN {require  't/lifecycles/utils.pl'};
+BEGIN {require  './t/lifecycles/utils.pl'};
 
 my $general = RT::Test->load_or_create_queue(
 Name => 'General',
diff --git a/t/lifecycles/dates.t b/t/lifecycles/dates.t
index 0c74a1b..a8dd8cf 100644
--- a/t/lifecycles/dates.t
+++ b/t/lifecycles/dates.t
@@ -1,7 +1,7 @@
 use strict;
 use warnings;
 
-BEGIN {require 't/lifecycles/utils.pl'};
+BEGIN {require './t/lifecycles/utils.pl'};
 
 my $general = RT::Test->load_or_create_queue(
 Name => 'General',
diff --git a/t/lifecycles/moving.t b/t/lifecycles/moving.t
index 8a03e3e..379b646 100644
--- a/t/lifecycles/moving.t
+++ b/t/lifecycles/moving.t
@@ -1,7 +1,7 @@
 use strict;
 use warnings;
 
-BEGIN {require 't/lifecycles/utils.pl'};
+BEGIN {require './t/lifecycles/utils.pl'};
 
 my $general = RT::Test->load_or_create_queue(
 Name => 'General',
diff --git a/t/lifecycles/types.t b/t/lifecycles/types.t
index 79b0714..84cfd86 100644
--- a/t/lifecycles/types.t
+++ b/t/lifecycles/types.t
@@ -1,7 +1,7 @@
 use strict;
 use warnings;
 
-BEGIN {require  't/lifecycles/utils.pl'};
+BEGIN {require  './t/lifecycles/utils.pl'};
 
 is_deeply( [ RT::Lifecycle->ListAll ], [qw/ approvals default delivery /],
"Get the list of all lifecycles (implicitly for for tickets)");
diff --git a/t/lifecycles/unresolved-deps.t b/t/lifecycles/unresolved-deps.t
index 5da4b8f..fe09d3b 100644
--- a/t/lifecycles/unresolved-deps.t
+++ b/t/lifecycles/unresolved-deps.t
@@ -1,7 +1,7 @@
 use strict;
 use warnings;
 
-BEGIN {require  't/lifecycles/utils.pl'};
+BEGIN {require  './t/lifecycles/utils.pl'};
 
 my $general = RT::Test->load_or_create_queue(
 Name => 'General',
-- 
2.9.3

Bug#835930: marked as done (kodi: needs patches to avoid FTBFS with new flann)

[Debian Bug Tracking System]

Your message dated Tue, 06 Sep 2016 12:03:30 +
with message-id 
and subject line Bug#835930: fixed in kido 0.1.0+dfsg-2
has caused the Debian Bug report #835930,
regarding kodi: needs patches to avoid FTBFS with new flann
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.)


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

Justification: breaks reverse dependencies.

Hi, the latest flann broke kido build, now it fails with a missing LZ4 link.

Scanning dependencies of target testNearestNeighbor
make[4]: Leaving directory '/<>/kido-0.1.0+dfsg/build'
/usr/bin/make -f unittests/CMakeFiles/testNearestNeighbor.dir/build.make 
unittests/CMakeFiles/testNearestNeighbor.dir/build
make[4]: Entering directory '/<>/kido-0.1.0+dfsg/build'
[ 71%] Building CXX object 
unittests/CMakeFiles/testNearestNeighbor.dir/testNearestNeighbor.cpp.o
cd /<>/kido-0.1.0+dfsg/build/unittests && /usr/bin/c++   
-DBOOST_TEST_DYN_LINK -DHAVE_BULLET_COLLISION -I/<>/kido-0.1.0+dfsg 
-isystem /usr/include/eigen3 -isystem /usr/include/bullet 
-I/<>/kido-0.1.0+dfsg/build 
-I/<>/kido-0.1.0+dfsg/unittests/gtest/include 
-I/<>/kido-0.1.0+dfsg/unittests/gtest  -Wall -fPIC -std=c++11 -g -O2 
-fdebug-prefix-map=/<>/kido-0.1.0+dfsg=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2   -I/usr/include/bullet -o 
CMakeFiles/testNearestNeighbor.dir/testNearestNeighbor.cpp.o -c 
/<>/kido-0.1.0+dfsg/unittests/testNearestNeighbor.cpp
[ 71%] Linking CXX executable ../bin/tests/testNearestNeighbor
cd /<>/kido-0.1.0+dfsg/build/unittests && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/testNearestNeighbor.dir/link.txt --verbose=1
/usr/bin/c++   -Wall -fPIC -std=c++11 -g -O2 
-fdebug-prefix-map=/<>/kido-0.1.0+dfsg=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2   -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
CMakeFiles/testNearestNeighbor.dir/testNearestNeighbor.cpp.o  -o 
../bin/tests/testNearestNeighbor  -L/<>/kido-0.1.0+dfsg/build/lib 
-rdynamic ../lib/libkido-utils.so.0.1.0 ../lib/libgtest.a 
../lib/libkido.so.0.1.0 -lccd -lfcl -lassimp -lboost_regex -lboost_system -lGLU 
-lGL -lBulletSoftBody -lBulletDynamics -lBulletCollision -lLinearMath 
-lurdfdom_sensor -lurdfdom_model_state -lurdfdom_model -lurdfdom_world 
-lconsole_bridge -ltinyxml -ltinyxml2 -lpthread 
-Wl,-rpath,/<>/kido-0.1.0+dfsg/build/lib 
CMakeFiles/testNearestNeighbor.dir/testNearestNeighbor.cpp.o: In function 
`flann::serialization::SaveArchive::initBlock()':
/usr/include/flann/util/serialization.h:406: undefined reference to 
`LZ4_resetStreamHC'
CMakeFiles/testNearestNeighbor.dir/testNearestNeighbor.cpp.o: In function 
`flann::serialization::SaveArchive::flushBlock()':
/usr/include/flann/util/serialization.h:425: undefined reference to 
`LZ4_compress_HC_continue'
/usr/include/flann/util/serialization.h:443: undefined reference to 
`LZ4_compress_HC_continue'
CMakeFiles/testNearestNeighbor.dir/testNearestNeighbor.cpp.o: In function 
`flann::serialization::LoadArchive::decompressAndLoadV10(_IO_FILE*)':
/usr/include/flann/util/serialization.h:610: undefined reference to 
`LZ4_decompress_safe'
CMakeFiles/testNearestNeighbor.dir/testNearestNeighbor.cpp.o: In function 
`flann::serialization::LoadArchive::loadBlock(char*, unsigned int, _IO_FILE*)':
/usr/include/flann/util/serialization.h:690: undefined reference to 
`LZ4_decompress_safe_continue'
CMakeFiles/testNearestNeighbor.dir/testNearestNeighbor.cpp.o: In function 
`flann::serialization::LoadArchive::initBlock(_IO_FILE*)':
/usr/include/flann/util/serialization.h:667: undefined reference to 
`LZ4_setStreamDecode'
collect2: error: ld returned 1 exit status
unittests/CMakeFiles/testNearestNeighbor.dir/build.make:114: recipe for target 
'bin/tests/testNearestNeighbor' failed
make[4]: *** [bin/tests/testNearestNeighbor] Error 1
make[4]: Leaving directory '/<>/kido-0.1.0+dfsg/build'
CMakeFiles/Makefile2:1981: recipe for target 
'unittests/CMakeFiles/testNearestNeighbor.dir/all' failed
make[3]: *** [unittests/CMakeFiles/testNearestNeighbor.dir/all] Error 2
make[3]: Leaving directory '/<>/kido-0.1.0+dfsg/build'
Makefile:141: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/<>/kido-0.1.0+dfsg/build'
debian/rules:33: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory 

Bug#835734: marked as done (kido: FTBFS: FCLCollisionNode.cpp:354:5: error: 'boost' has not been declared)

[Debian Bug Tracking System]

Your message dated Tue, 06 Sep 2016 12:03:30 +
with message-id 
and subject line Bug#835734: fixed in kido 0.1.0+dfsg-2
has caused the Debian Bug report #835734,
regarding kido: FTBFS: FCLCollisionNode.cpp:354:5: error: 'boost' has not been 
declared
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.)


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

Hi,

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

Relevant part (hopefully):
> cd /<>/kido-0.1.0+dfsg/build/kido && /usr/bin/c++   
> -DBOOST_TEST_DYN_LINK -DHAVE_BULLET_COLLISION -Dkido_EXPORTS 
> -I/<>/kido-0.1.0+dfsg -isystem /usr/include/eigen3 -isystem 
> /usr/include/bullet -I/<>/kido-0.1.0+dfsg/build  -Wall -msse2 -fPIC 
> -std=c++11 -g -O2 -fdebug-prefix-map=/<>/kido-0.1.0+dfsg=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC   -I/usr/include/bullet -o 
> CMakeFiles/kido.dir/collision/fcl/FCLCollisionNode.cpp.o -c 
> /<>/kido-0.1.0+dfsg/kido/collision/fcl/FCLCollisionNode.cpp
> /<>/kido-0.1.0+dfsg/kido/collision/fcl/FCLCollisionNode.cpp: In 
> constructor 
> 'kido::collision::FCLCollisionNode::FCLCollisionNode(kido::dynamics::BodyNode*)':
> /<>/kido-0.1.0+dfsg/kido/collision/fcl/FCLCollisionNode.cpp:354:5: 
> error: 'boost' has not been declared
>  boost::shared_ptr fclCollGeom;
>  ^
> /<>/kido-0.1.0+dfsg/kido/collision/fcl/FCLCollisionNode.cpp:354:45: 
> error: expected primary-expression before '>' token
>  boost::shared_ptr fclCollGeom;
>  ^
> /<>/kido-0.1.0+dfsg/kido/collision/fcl/FCLCollisionNode.cpp:354:47: 
> error: 'fclCollGeom' was not declared in this scope
>  boost::shared_ptr fclCollGeom;
>^~~
> kido/CMakeFiles/kido.dir/build.make:1937: recipe for target 
> 'kido/CMakeFiles/kido.dir/collision/fcl/FCLCollisionNode.cpp.o' failed
> make[4]: *** [kido/CMakeFiles/kido.dir/collision/fcl/FCLCollisionNode.cpp.o] 
> Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/kido_0.1.0+dfsg-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Jose Luis Rivero  (supplier of updated kido 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, 30 Aug 2016 22:52:53 +
Source: kido
Binary: libkido-dev libkido0.1 libkido-planning-dev libkido-planning0.1 
libkido-utils-dev libkido-utils0.1 libkido-gui-dev libkido-gui0.1 
libkido-gui-osg-dev libkido-gui-osg0.1 libkido-optimizer-nlopt-dev 
libkido-optimizer-nlopt0.1 libkido-optimizer-ipopt-dev 
libkido-optimizer-ipopt0.1
Architecture: source
Version: 0.1.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jose Luis Rivero 
Description:
 libkido-dev - Kinematics Dynamics and Optimization Library - development files
 libkido-gui-dev - Kinematics Dynamics and Optimization Library - gui dev files
 libkido-gui-osg-dev - Kinematics Dynamics and Optimization Library - gui-osg 
dev files
 libkido-gui-osg0.1 - Kinematics Dynamics and Optimization Library - 

Bug#833817: marked as done (kido: FTBFS on non-x86 architectures due to hard-wired compiler flags)

[Debian Bug Tracking System]

Your message dated Tue, 06 Sep 2016 12:03:30 +
with message-id 
and subject line Bug#833817: fixed in kido 0.1.0+dfsg-2
has caused the Debian Bug report #833817,
regarding kido: FTBFS on non-x86 architectures due to hard-wired compiler flags
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.)


-- 
833817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kido
Version: 0.1.0+dfsg-1
Severity: important

Hello!

Your package fails to build from source on all non-x86 architectures because the
build system hard-wires the compiler flags to use x86-specific flags like 
"-msse2":

[  0%] Building CXX object kido/CMakeFiles/kido.dir/common/Console.cpp.o
cd /<>/kido-0.1.0+dfsg/build/kido && /usr/bin/c++   
-DBOOST_TEST_DYN_LINK -DHAVE_BULLET_COLLISION -Dkido_EXPORTS 
-I/<>/kido-0.1.0+dfsg -isystem /usr/include/eigen3 -isystem 
/usr/include/bullet -I/<>/kido-0.1.0+dfsg/build  -Wall -msse2 -fPIC 
-std=c++11 -g -O2 -fdebug-prefix-map=/<>/kido-0.1.0+dfsg=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC   -I/usr/include/bullet -o 
CMakeFiles/kido.dir/common/Console.cpp.o -c 
/<>/kido-0.1.0+dfsg/kido/common/Console.cpp
c++: error: unrecognized command line option '-msse2'
kido/CMakeFiles/kido.dir/build.make:65: recipe for target 
'kido/CMakeFiles/kido.dir/common/Console.cpp.o' failed
make[4]: *** [kido/CMakeFiles/kido.dir/common/Console.cpp.o] Error 1

Please modify the CFLAGS used to make your package build on all architectures!

Full build log available in [1].

Thanks!
Adrian

> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=kido=sparc64=0.1.0%2Bdfsg-1=1470693049

--
 .''`.  John Paul Adrian Glaubitz
 : :' :  Debian Developer - glaub...@debian.org
 `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
Source: kido
Source-Version: 0.1.0+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Jose Luis Rivero  (supplier of updated kido 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, 30 Aug 2016 22:52:53 +
Source: kido
Binary: libkido-dev libkido0.1 libkido-planning-dev libkido-planning0.1 
libkido-utils-dev libkido-utils0.1 libkido-gui-dev libkido-gui0.1 
libkido-gui-osg-dev libkido-gui-osg0.1 libkido-optimizer-nlopt-dev 
libkido-optimizer-nlopt0.1 libkido-optimizer-ipopt-dev 
libkido-optimizer-ipopt0.1
Architecture: source
Version: 0.1.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jose Luis Rivero 
Description:
 libkido-dev - Kinematics Dynamics and Optimization Library - development files
 libkido-gui-dev - Kinematics Dynamics and Optimization Library - gui dev files
 libkido-gui-osg-dev - Kinematics Dynamics and Optimization Library - gui-osg 
dev files
 libkido-gui-osg0.1 - Kinematics Dynamics and Optimization Library - gui-osg 
library
 libkido-gui0.1 - Kinematics Dynamics and Optimization Library - gui library
 libkido-optimizer-ipopt-dev - Kinematics Dynamics and Optimization Library - 
ipopt optimizer de
 libkido-optimizer-ipopt0.1 - Kinematics Dynamics and Optimization Library - 
ipopt optimizer li
 libkido-optimizer-nlopt-dev - Kinematics Dynamics and Optimization Library - 
optimizer dev file
 libkido-optimizer-nlopt0.1 - Kinematics Dynamics and Optimization Library - 
nlopt optimizer li
 libkido-planning-dev - Kinematics Dynamics and Optimization Library - planning 
dev files
 libkido-planning0.1 - Kinematics Dynamics and Optimization Library - planning 
library
 libkido-utils-dev - Kinematics Dynamics and Optimization Library - utils dev 
files
 libkido-utils0.1 - Kinematics Dynamics and Optimization Library - utils library
 

Bug#832364: kodi: Crashes on trying to play any TV recording

[Bálint Réczey]

Hi Tobias,

2016-08-19 19:54 GMT+02:00 Tobias Grimm :
> Hello Balint,
>
>> Tobias, could you please share the test file or test kodi again?
>
> I've just tested it. It crashes when playing a VDR TS recording with
> 16.1+dfsg1-1 and after upgrading to 16.1+dfsg1-2 it works fine for the
> same recording.

Could you please share the recording with Carl instead? He is an FFmpeg
dev thus probably can find the problem very quickly and maybe other
devs are interested as well.

>
> So I think 832364 can be closed.

I think merging with an other very similar bug reflects the situation
better (thus I did so).

Cheers,
Balint

Processed: retitle 836713 to usbguard: FTBFS: No package 'systemd' found, severity of 836713 is serious

[Debian Bug Tracking System]

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

> # not hppa-specific
> retitle 836713 usbguard: FTBFS: No package 'systemd' found
Bug #836713 [src:usbguard] usbguard: FTBFS on hppa: No package 'systemd' found
Changed Bug title to 'usbguard: FTBFS: No package 'systemd' found' from 
'usbguard: FTBFS on hppa: No package 'systemd' found'.
> severity 836713 serious
Bug #836713 [src:usbguard] usbguard: FTBFS: No package 'systemd' found
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#831591: ffmpeg: kodi crash

[Carl Eugen Hoyos]

Hi!

> Knowing what broke could be
> interesting for FFmpeg devs

It would most likely be even more interesting 
for the Kodi developers: We currently assume 
that there is an unknown bug in Kodi...

> > Slightly related: More that half of the open tickets
> > concerning FFmpeg in Debian either contain no samples to
> > reproduce or will not be fixed or were never reproducible.
> > If another FFmpeg developer were interested in fixing
> > bugs reported here it would be very difficult for him to
> > find something useful due to the low snr.
>
> Those can be marked with the moreinfo tag and IMO it is
> OK to close them after a reasonable amount of time if
> the originator is asked to provide a test file but she/he
> did not.

Are five months enough?

Carl Eugen

Bug#831591: ffmpeg: kodi crash

[Bálint Réczey]

Hi Carl,

2016-09-06 11:39 GMT+02:00 Carl Eugen Hoyos :
> Hi Bálint!
>
>> I don't have the test file.
>
> In this case I suggest to close the relevant tickets:
> We cannot reproduce, there is no backtrace and no bisect.

Tobias has test files as he wrote in #832364 and he would
share it privately.

>
> Since FFmpeg has made three point releases with the ABI
> that is apparently incompatible with (old) Kodi, it is
> very unlikely that it will be changed again (we would
> likely brake mpv that intentionally uses the invalid API).

>From practical POV I'm OK with closing this bug since it does
not affect unstable nor testing. Knowing what broke could be
interesting for FFmpeg devs and in case the change is reverted
I could update ffmpeg in jessie-backports without recompiling
kodi. This is why I have not back-ported latest ffmpeg yet.


>
> Slightly related: More that half of the open tickets
> concerning FFmpeg in Debian either contain no samples to
> reproduce or will not be fixed or were never reproducible.
> If another FFmpeg developer were interested in fixing
> bugs reported here it would be very difficult for him to
> find something useful due to the low snr.

Those can be marked with the moreinfo tag and IMO it is
OK to close them after a reasonable amount of time if
the originator is asked to provide a test file but she/he
did not.

Thanks for helping in managing the FFmpeg bugs in Debian!

Cheers,
Balint