Bug#817869: tortoisehg: uninstallable with current mercurial

[Julien Cristau]

Source: tortoisehg
Version: 3.6.2-1
Severity: serious

tortoisehg has:
Depends: mercurial (>= 3.5~), mercurial (<< 3.7~)
mercurial in sid is 3.7.2, making tortoisehg uninstallable.

Cheers,
Julien

Bug#817008: unfulfilled dependencies

[殷啟聰]

I am confident that 24.3.3+2 solved the bug, but I prefer to wait for
the package getting accepted. Just want to be cautious :)

Processed: Re: Bug#817816: System freeze with CPU hotplug

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #817816 {Done: Ben Hutchings } 
[linux-image-4.4.0-1-amd64] System freeze with CPU hotplug
Bug reopened
Ignoring request to alter fixed versions of bug #817816 to the same values 
previously set
> severity -1 normal
Bug #817816 [linux-image-4.4.0-1-amd64] System freeze with CPU hotplug
Severity set to 'normal' from 'critical'

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

Bug#817816: System freeze with CPU hotplug

[Ben Hutchings]

Control: reopen -1
Control: severity -1 normal

On Fri, 2016-03-11 at 01:12 +0100, Harry Junior wrote:
> On Thu, 10 Mar 2016 17:34:54 + Ben Hutchings  wrote:
> > 
> > On Thu, 2016-03-10 at 17:32 +0100, Harry Junior wrote:
> > > 
> > > Package: linux-image-4.4.0-1-amd64
> > > Version: 4.4.4-1
> > > Severity: critical
> > > Justification: renders system unusable
> > > 
> > > 
> > > When I run the following commands, the system freezes:
> > > 
> > > # echo 0 | tee /sys/devices/system/cpu/cpu*/online && echo 1 | sudo
> > > tee /sys/devices/system/cpu/cpu*/online
> > > 
> > > The system freezes randomly when the CPUs are being onlined or
> > > offlined. The system is installed on a VMware virtual machine with 4
> > > processors. Here's a stacktrace of the infinite loop:
> > [...]
> > 
> > You just asked to offline all CPUs, making the system unusable. Â I
> > don't see any bug here.
> I'm sorry to disagree, but the CPU0 can't be offlined and remains online:
[...]

Depending on the configuration, it may be possible to offline CPU0.
However, I have been informed that the kernel still prevents offlining
the last CPU - or at least it is supposed to.

So I'm reopening this, but correcting the severity.  ("renders system
unusable" does *not* mean the system hangs or crashes, it means the
system becomes unbootable or otherwise persistently broken.)

Ben.

-- 
Ben Hutchings
73.46% of all statistics are made up.

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

Processed: Bug#800242: hearse: Please migrate a supported debhelper compat level

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #800242 [src:hearse] hearse: Please migrate a supported debhelper compat 
level
Added tag(s) pending.
> tags 290937 patch pending
Bug #290937 [hearse] hearse doesn't support 64-bit platforms
Added tag(s) patch and pending.
> tags 816952 pending
Bug #816952 [hearse] hearse: [INTL:pt_BR] Brazilian Portuguese debconf 
templates translation
Added tag(s) pending.

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

Bug#800242: hearse: Please migrate a supported debhelper compat level

[James Cowgill]

Control: tags -1 pending
Control: tags 290937 patch pending
Control: tags 816952 pending

Hi,

I have uploaded an NMU to fix this bug (#800242), the 64-bit support
bug (#290937) and the brazillian debconf translations bug (#816952) to
DELAYED/10.

Please tell me if you want it cancelled / delayed longer.

The NMU is attached.

Thanks,
Jamesdiff -u hearse-1.5/debian/changelog hearse-1.5/debian/changelog
--- hearse-1.5/debian/changelog
+++ hearse-1.5/debian/changelog
@@ -1,3 +1,16 @@
+hearse (1.5-8.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch to debhelper compat 9. (Closes: #800242)
+  * Add support for 64-bit platforms. (Closes: #290937) (LP: #591773)
+Thanks to PJ Weisberg for the patch.
+  * Add Brazilian Portuguese debconf translations. (Closes: #816952)
+  * Small packaging cleanups:
+- Add support for the build-arch and build-indep targets.
+- Replace obsolete call to dh_clean -k with dh_prep.
+
+ -- James Cowgill   Fri, 11 Mar 2016 02:27:51 +
+
 hearse (1.5-8.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u hearse-1.5/debian/control hearse-1.5/debian/control
--- hearse-1.5/debian/control
+++ hearse-1.5/debian/control
@@ -3,11 +3,11 @@
 Priority: optional
 Maintainer: Roderick Schertler 
 Standards-Version: 3.7.2
-Build-Depends: debhelper (>= 4.1.68), perl (>= 5.6.0-16), po-debconf
+Build-Depends: debhelper (>= 9), perl (>= 5.6.0-16), po-debconf
 
 Package: hearse
 Architecture: all
-Depends: debconf (>= 1.2.0) | debconf-2.0, ${perl:Depends}, libwww-perl, nethack-common | nethack
+Depends: debconf (>= 1.2.0) | debconf-2.0, ${perl:Depends}, libwww-perl, nethack-common | nethack, ${misc:Depends}
 Description: exchange Nethack bones files with other players
  Nethack sometimes saves the level on which you die (including your
  stuff, what killed you, and your ghost) in a "bones file".  These files
diff -u hearse-1.5/debian/rules hearse-1.5/debian/rules
--- hearse-1.5/debian/rules
+++ hearse-1.5/debian/rules
@@ -11,10 +11,11 @@
 ifneq "" "$(findstring debug,$(DEB_BUILD_OPTIONS))"
 CFLAGS		+= -g
 endif
-export DH_COMPAT	:= 3
 PERL			?= perl
 
-build: $(stamp_build)
+build: build-arch build-indep
+build-arch:
+build-indep: $(stamp_build)
 $(stamp_build):
 	dh_testdir
 	$(PERL) Makefile.PL INSTALLDIRS=vendor
@@ -26,7 +27,7 @@
 $(stamp_install): $(stamp_build)
 	dh_testdir
 	dh_testroot
-	dh_clean -k
+	dh_prep
 	dh_installdirs
 	$(MAKE) install DESTDIR=$(prefix)
 	cp hearse.conf $(dt)/etc/nethack
diff -u hearse-1.5/hearse hearse-1.5/hearse
--- hearse-1.5/hearse
+++ hearse-1.5/hearse
@@ -754,26 +754,6 @@
 	return;
 }
 
-# The 4 version numbers are stored by Nethack as 4 unsigned longs
-# in host byte order at the start of the file.  I don't want to
-# read them in host order, though, because that would mask byte sex
-# differences between platforms.
-#
-# If the platform's longs aren't 4 bytes, though, I've got a
-# separate problem.  I need to read the right number of bytes
-# else I'll only get part of the version data, and what I do get
-# will end up in the wrong places.  I test for this using Perl
-# 5.6's 'L!' pack format (and just hope for the best for earlier
-# versions).  I haven't actually written the code to deal with
-# this case yet (it needs special handling because there's no
-# format to read a native-sized long but with a specific byte
-# order), I just detect it and choke.
-
-my $ulong_size = eval { length pack 'L!', 0 } || 4;	# punt for Perl < 5.6
-if ($ulong_size != 4) {
-	xdie "size of unsigned long is $ulong_size rather than 4\n";
-}
-
 # struct version_info {
 # unsigned long   incarnation;/* actual version number */
 # unsigned long   feature_set;/* bitmask of config settings */
@@ -781,7 +761,7 @@
 # unsigned long   struct_sizes;   /* size of key structs */
 # };
 
-@version = unpack 'V' x HEADER_VERSION_COUNT, $data;
+@version = unpack 'L!<' x HEADER_VERSION_COUNT, $data;
 if (@version != HEADER_VERSION_COUNT) {
 	xwarn "$open_spec is too short (", length($data), ")\n";
 	return;
only in patch2:
unchanged:
--- hearse-1.5.orig/debian/compat
+++ hearse-1.5/debian/compat
@@ -0,0 +1 @@
+9
only in patch2:
unchanged:
--- hearse-1.5.orig/debian/po/pt_BR.po
+++ hearse-1.5/debian/po/pt_BR.po
@@ -0,0 +1,56 @@
+# Debconf translations for hearse.
+# Copyright (C) 2016 THE hearse'S COPYRIGHT HOLDER
+# This file is distributed under the same license as the hearse package.
+# Adriano Rafael Gomes , 2016.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: hearse 1.5-8.2\n"
+"Report-Msgid-Bugs-To: hea...@packages.debian.org\n"
+"POT-Creation-Date: 2009-12-22 08:53-0500\n"
+"PO-Revision-Date: 2016-02-09 23:05-0200\n"
+"Last-Translator: Adriano Rafael Gomes \n"
+"Language-Team: Brazilian Portuguese 

Bug#817857: util-linux: Depends/Breaks loop with Essential packages prevents upgrade from Jessie

[Ben Bailess]

I am seeing the same behavior. Just installed fresh from netinst today, and
tried to dist-upgrade to stretch (with the expectation I'd be moving to
sid after another reboot + dist-upgrade) and I hit the dep loop as
described above.

Tried going straight from Jessie --> sid too but ran into same error and
cannot proceed (thinking perhaps the fix had hit Sid but not stretch).

Thanks for th effort to fix.

Ben

Bug#816857: marked as done (libtesseract3: renders gimagereader unusable)

[Debian Bug Tracking System]

Your message dated Fri, 11 Mar 2016 02:31:40 +0100
with message-id <20160311023140.64bbe...@gmail.com>
and subject line Fixed in libtesseract3 version 3.04.01-4
has caused the Debian Bug report #816857,
regarding libtesseract3: renders gimagereader unusable
to be marked as done.

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

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


-- 
816857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gimagereader
Version: 3.1.2+git368fa8f-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

This is the complete error messager:

gimagereader-gtk: symbol lookup error: gimagereader-gtk:
undefined symbol: _ZN9tesseract11TessBaseAPI13AnalyseLayoutEv

The application never gets launched.

Kind regards,
Manolo Díaz


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

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

Versions of packages gimagereader depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  libatkmm-1.6-1v5 2.24.2-1
ii  libc62.21-9
ii  libcairomm-1.0-1v5   1.12.0-1
ii  libgcc1  1:5.3.1-10
ii  libglib2.0-0 2.46.2-3
ii  libglibmm-2.4-1v52.46.3-1
ii  libgomp1 5.3.1-10
ii  libgtk-3-0   3.18.8-1
ii  libgtkmm-3.0-1v5 3.18.0-1
ii  libgtksourceviewmm-3.0-0v5   3.18.0-1
ii  libgtkspellmm-3.0-0v53.0.3+dfsg-2
ii  libpangomm-1.4-1v5   2.38.1-1
ii  libpoppler-glib8 0.38.0-2
ii  libsane  1.0.25-2
ii  libsigc++-2.0-0v52.6.2-1
ii  libstdc++6   5.3.1-10
ii  libtesseract33.04.00-5+b2

gimagereader recommends no packages.

gimagereader suggests no packages.

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

After upgrading libtesseract3 from version 3.04.00-5+b2 to 3.04.01-4
(now in testing) I can't reproduce this bug any more.

Kind regards,
-- 
Manolo Díaz--- End Message ---

Processed: Reassigning to libtesseract3

[Debian Bug Tracking System]

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

> reassign 816857 libtesseract3 3.04.00-5+b2
Bug #816857 [gimagereader] gimagereader: fails to launch with "symbol lookup 
error"
Bug reassigned from package 'gimagereader' to 'libtesseract3'.
No longer marked as found in versions gimagereader/3.1.2+git368fa8f-2.
Ignoring request to alter fixed versions of bug #816857 to the same values 
previously set
Bug #816857 [libtesseract3] gimagereader: fails to launch with "symbol lookup 
error"
Marked as found in versions tesseract/3.04.00-5.
> fixed 816857 3.04.01-4
Bug #816857 [libtesseract3] gimagereader: fails to launch with "symbol lookup 
error"
Marked as fixed in versions tesseract/3.04.01-4.
> retitle 816857 libtesseract3: renders gimagereader unusable
Bug #816857 [libtesseract3] gimagereader: fails to launch with "symbol lookup 
error"
Changed Bug title to 'libtesseract3: renders gimagereader unusable' from 
'gimagereader: fails to launch with "symbol lookup error"'
> thanks
Stopping processing here.

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

Bug#817857: util-linux: Depends/Breaks loop with Essential packages prevents upgrade from Jessie

[Josh Triplett]

Package: util-linux
Version: 2.27.1-5
Severity: serious

Even with util-linux 2.27.1-5, I still hit a dependency loop that caused
apt to refuse to proceed:

util-linux 2.27.1-5 Depends on init-system-helpers (>= 1.29~)
init-system-helpers 1.29 Breaks sysvinit-utils (< 2.88dsf-59.3~)
sysvinit-utils 2.88dsf-59.3 Breaks util-linux (< 2.26.2-3)

sysvinit-utils and util-linux are both Essential.

Result:

~$ sudo apt install util-linux
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  init-system-helpers libfdisk1 sysvinit-utils
Suggested packages:
  bootlogd sash dosfstools kbd | console-tools util-linux-locales
The following NEW packages will be installed:
  libfdisk1
The following packages will be upgraded:
  init-system-helpers sysvinit-utils util-linux
3 upgraded, 1 newly installed, 0 to remove and 11 not upgraded.
Need to get 0 B/1198 kB of archives.
After this operation, 930 kB of additional disk space will be used.
Do you want to continue? [Y/n]
E: This installation run will require temporarily removing the essential 
package sysvinit-utils:amd64 due to a Conflicts/Pre-Depends loop. This is often 
bad, but if you really want to do it, activate the APT::Force-LoopBreak option.
E: Internal Error, Could not early remove sysvinit-utils:amd64 (2)

Bug#817816: System freeze with CPU hotplug

[Harry Junior]

On Thu, 10 Mar 2016 17:34:54 + Ben Hutchings  wrote:
> On Thu, 2016-03-10 at 17:32 +0100, Harry Junior wrote:
>> Package: linux-image-4.4.0-1-amd64
>> Version: 4.4.4-1
>> Severity: critical
>> Justification: renders system unusable
>> 
>> 
>> When I run the following commands, the system freezes:
>> 
>> # echo 0 | tee /sys/devices/system/cpu/cpu*/online && echo 1 | sudo
>> tee /sys/devices/system/cpu/cpu*/online
>> 
>> The system freezes randomly when the CPUs are being onlined or
>> offlined. The system is installed on a VMware virtual machine with 4
>> processors. Here's a stacktrace of the infinite loop:
> [...]
> 
> You just asked to offline all CPUs, making the system unusable. Â I
> don't see any bug here.

I'm sorry to disagree, but the CPU0 can't be offlined and remains online:

$ ls -l /sys/devices/system/cpu/ | grep cpu | head -4
drwxr-xr-x 6 root root0 Mar 10 18:41 cpu0
drwxr-xr-x 6 root root0 Mar 10 18:41 cpu1
drwxr-xr-x 6 root root0 Mar 10 18:41 cpu2
drwxr-xr-x 6 root root0 Mar 10 18:41 cpu3

$ ls -l /sys/devices/system/cpu/cpu*/online
-rw-r--r-- 1 root root 4096 Mar 10 18:40 /sys/devices/system/cpu/cpu1/online
-rw-r--r-- 1 root root 4096 Mar 10 18:40 /sys/devices/system/cpu/cpu2/online
-rw-r--r-- 1 root root 4096 Mar 10 18:40 /sys/devices/system/cpu/cpu3/online

  

Bug#814722: (no subject)

[David Demonchy]

I have the same bug in unstable branch.

i can fix this bug with a rollback the kernel (version 4.3.0-1) (testing 
branch)

Bug#817794: marked as done (qtsensors-opensource-src: B-D on obsolete package libqt5xcbqpa5)

[Debian Bug Tracking System]

Your message dated Thu, 10 Mar 2016 22:30:43 +
with message-id 
and subject line Bug#817794: fixed in qtsensors-opensource-src 5.5.1-3
has caused the Debian Bug report #817794,
regarding qtsensors-opensource-src: B-D on obsolete package libqt5xcbqpa5
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.)


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

Hi,

your package Build-Depends on the obsolete transitional package
libqt5xcbqpa5 which is no longer built by qtbase-opensource-src. Please
switch to libqt5gui5.


Andreas
--- End Message ---
--- Begin Message ---
Source: qtsensors-opensource-src
Source-Version: 5.5.1-3

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

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

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

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
qtsensors-opensource-src package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 10 Mar 2016 16:57:18 -0300
Source: qtsensors-opensource-src
Binary: libqt5sensors5 qml-module-qtsensors libqt5sensors5-dev 
qtsensors5-examples qtsensors5-dbg qtsensors5-doc qtsensors5-doc-html
Architecture: source
Version: 5.5.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Description:
 libqt5sensors5 - Qt Sensors module
 libqt5sensors5-dev - Qt 5 Sensors development files
 qml-module-qtsensors - Qt 5 Sensors QML module
 qtsensors5-dbg - Qt sensors library debugging symbols
 qtsensors5-doc - Qt 5 Sensors documentation
 qtsensors5-doc-html - Qt 5 Sensors HTML documentation
 qtsensors5-examples - Qt 5 sensors examples
Closes: 817794
Changes:
 qtsensors-opensource-src (5.5.1-3) unstable; urgency=medium
 .
   * Drop libqt5xcbqpa5, we merged it's contents in libqt5gui5, provided by
 qtbase5-dev (Closes: #817794).
Checksums-Sha1:
 e1ae139f336504612266a3710d272c3c4d20c564 2791 
qtsensors-opensource-src_5.5.1-3.dsc
 3b10f4a60861c0ba799a17bb74d88086e42c884d 10976 
qtsensors-opensource-src_5.5.1-3.debian.tar.xz
Checksums-Sha256:
 2c4a4107bdf65a5f2cc6bef0866a987055db7fa4c4769280ac9d67dc8af21bf2 2791 
qtsensors-opensource-src_5.5.1-3.dsc
 9528902c99688f619f144dac2112f556f42fb08624e42bd9cf757043a540790f 10976 
qtsensors-opensource-src_5.5.1-3.debian.tar.xz
Files:
 78c8b8c59d7b3c7b0a3a768d07982341 2791 libs optional 
qtsensors-opensource-src_5.5.1-3.dsc
 d1fc4d3de7a37dc30929fd432f248951 10976 libs optional 
qtsensors-opensource-src_5.5.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW4dHvAAoJEKtkX0BihqfQp50P/03jd5DUCcXq0GydNJy3qrY6
gzDN3uIAD7FeFH1xrJfFncaqOEH5mdeFTf8CdyNlI+wY+CFDb1usX9qwk1freEA7
LqWGuVlVCIvEJl5ubGwqpohFuymbZwZW808AsShmE/xC4DosXPyFe28C+xuzxtdR
e6oYTOD+H+eeNw0hXuvkLNE8ZrJ8kQ3M+bHw4OiWmSG06/JSidNQFcwo75eGkyab
YOmN+xDKIR5IMFo/iHdEHs4Knzh9CueRGdjc/MwFsMnEq+yR+0MlUrFXGH1loQ6Q
icnKM3NBW66FPDX7uSwRazKmgxlyvJc99EP9tm9aIpCgs32JTTY3d2Lc7qRhltWD
Fj29LXbdQ8mg2LuPHFX/6SFC2L4A9ZYw5+1X5N1W/2ASY7sg7JWIZQKv0uin/RKC
/qJys+LUjAw3AY5BQjMp9ilNcN+EmIpCKK2XKQZw5yrubHijXfEEMjqk9saVtGn/
enXrr635J87wguicMBYujmKMoaGzRjVXX2T2Z6mZyKLR+KCs2NfbM3+2kHX0xU/2
ExBAAPV2suuoHOPk65Mv5oD3hcKe6Keikvhcw0YvkZBDkHrurXvxkH6qAE4+F+Zj
7QGt8aseuSecgX4q+yGJj2/2wU/Ow/xvJ7TagXnAgA5z4P8n7ZXB1GXFU20iFoj6
+8I6aq+RKBHqlpm+39el
=whxE
-END PGP SIGNATURE End Message ---

Bug#811340: marked as done (php5-lasso: fails to install: php5-lasso.postinst: php5enmod: not found)

[Debian Bug Tracking System]

Your message dated Thu, 10 Mar 2016 22:21:30 +
with message-id 
and subject line Bug#811340: fixed in lasso 2.5.0-4
has caused the Debian Bug report #811340,
regarding php5-lasso: fails to install: php5-lasso.postinst: php5enmod: not 
found
to be marked as done.

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

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


-- 
811340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-lasso
Version: 2.5.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package php5-lasso.
  (Reading database ... 
(Reading database ... 7614 files and directories currently installed.)
  Preparing to unpack .../php5-lasso_2.5.0-3_amd64.deb ...
  Unpacking php5-lasso (2.5.0-3) ...
  Setting up php5-lasso (2.5.0-3) ...
  /var/lib/dpkg/info/php5-lasso.postinst: 4: 
/var/lib/dpkg/info/php5-lasso.postinst: php5enmod: not found
  dpkg: error processing package php5-lasso (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   php5-lasso


cheers,

Andreas


php5-lasso_2.5.0-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: lasso
Source-Version: 2.5.0-4

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 10 Mar 2016 22:38:24 +0100
Source: lasso
Binary: liblasso3-dev liblasso3 python-lasso python3-lasso liblasso-perl 
php5-lasso
Architecture: source amd64
Version: 2.5.0-4
Distribution: unstable
Urgency: medium
Maintainer: Frederic Peters 
Changed-By: Frederic Peters 
Description:
 liblasso-perl - Library for Liberty Alliance and SAML protocols - Perl bindings
 liblasso3  - Library for Liberty Alliance and SAML protocols - runtime library
 liblasso3-dev - Library for Liberty Alliance and SAML protocols - development 
kit
 php5-lasso - Library for Liberty Alliance and SAML protocols - PHP 5 bindings
 python-lasso - Library for Liberty Alliance and SAML protocols - Python 
bindings
 python3-lasso - Library for Liberty Alliance and SAML protocols - Python 
bindings
Closes: 811340
Changes:
 lasso (2.5.0-4) unstable; urgency=medium
 .
   * d/control: add missing php5-common dependency. (closes: #811340)
Checksums-Sha1:
 349a90d5a9ccc99fd050f697039ba36251e2d38b 2197 lasso_2.5.0-4.dsc
 a1cb5f568355d05461ab488467e1e39edc6c6e2b 9092 lasso_2.5.0-4.debian.tar.xz
 31548728df44c3c116a8356d290ce7833d45e6ed 148388 
liblasso-perl-dbgsym_2.5.0-4_amd64.deb
 120115a45502ca7183f42364d624f3031751fb0d 144980 liblasso-perl_2.5.0-4_amd64.deb
 4196af40e3f915e2f6686bf5872038a65bd4548b 22732 
liblasso3-dbgsym_2.5.0-4_amd64.deb
 4e4f0b0322e6badd240a7a45d62db9b2a0312a5c 226926 liblasso3-dev_2.5.0-4_amd64.deb
 bd2e4ee58b56409901a0f313364685c36f2926df 157936 liblasso3_2.5.0-4_amd64.deb
 cf5c768c7d65bfc87db6199f608d8807f0176064 18058 
php5-lasso-dbgsym_2.5.0-4_amd64.deb
 dceccb868d183a38b59888de5de878fbbb1a310a 133562 php5-lasso_2.5.0-4_amd64.deb
 3cef5a99510ecc56a03bc13f8b97b7ac3805ee78 14754 
python-lasso-dbgsym_2.5.0-4_amd64.deb
 3e3fe47344d10d8577be021f6412173f98d36891 112110 python-lasso_2.5.0-4_amd64.deb
 55a3ec11ae8ba95dfabe5542b7ffa3dce9d9fb89 14896 
python3-lasso-dbgsym_2.5.0-4_amd64.deb
 a5442d93c920948bb317c005eeccf5e7f10e9bc2 116462 python3-lasso_2.5.0-4_amd64.deb
Checksums-Sha256:
 bc3ff43a336d5fa262489114412298c6fa285d8a6a871fdb200a784d9b8c1c71 2197 
lasso_2.5.0-4.dsc
 6035040a514bcbcba5dcdd8c1a567ec2ac0481d69bd655c21800b1e02b1ab814 9092 
lasso_2.5.0-4.debian.tar.xz
 

Bug#814944: marked as done (mariadb-connect-engine-10.0: ODBC support apparently not compiled in)

[Debian Bug Tracking System]

Your message dated Thu, 10 Mar 2016 22:26:52 +
with message-id 
and subject line Bug#814944: fixed in mariadb-10.0 10.0.24-4
has caused the Debian Bug report #814944,
regarding mariadb-connect-engine-10.0: ODBC support apparently not compiled in
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.)


-- 
814944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mariadb-connect-engine-10.0
Version: 10.0.23-0+deb8u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Trying to connect to an ODBC database, get: SQL Error (1105): Unsupported table 
type ODBC

Search quickly arrives at https://mariadb.atlassian.net/browse/MDEV-4555 which 
had same problem.

Solution there was that odbc needs to be compiled in (ODBC_SUPPORT precompiler 
option).

ldd /usr/lib/mysql/plugin/ha_connect.so output should include unixodbc libs, it 
doesn't.

Looking at build log 
(https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.0=arm64=10.0.23-2=1453644048),
 test section includes...

connect.odbc w5 [ skipped ]  No ODBC support
connect.odbc_oracle  w5 [ skipped ]  No ODBC support
spider/bg.direct_update_part w4 [ pass ] 83
connect.odbc_postgresql  w5 [ skipped ]  No ODBC support
connect.odbc_sqlite3 w5 [ skipped ]  No ODBC support
connect.odbc_sqlite3_grant   w5 [ skipped ]  No ODBC support
connect.odbc_xls w5 [ skipped ]  No ODBC support

Given that the package description says "Connect engine supports ... 
connections to ODBC tables ..." and lists unixODBC as a dep,
I would expect ODBC support to be compiled in?

(similarly, XML support seems to be missing too?)

-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages mariadb-connect-engine-10.0 depends on:
ii  libc62.19-18+deb8u1
ii  libstdc++6   4.9.2-10
ii  libxml2  2.9.1+dfsg1-5+deb8u1
ii  mariadb-server-10.0  10.0.23-0+deb8u1
ii  unixodbc 2.3.1-3
ii  zlib1g   1:1.2.8.dfsg-2+b1

mariadb-connect-engine-10.0 recommends no packages.

mariadb-connect-engine-10.0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mariadb-10.0
Source-Version: 10.0.24-4

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

Debian distribution maintenance software
pp.
Otto Kekäläinen  (supplier of updated mariadb-10.0 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: Thu, 10 Mar 2016 18:40:51 +0200
Source: mariadb-10.0
Binary: libmariadbd18 libmariadbd-dev mariadb-common mariadb-client-core-10.0 
mariadb-client-10.0 mariadb-server-core-10.0 mariadb-test mariadb-test-data 
mariadb-server-10.0 mariadb-server mariadb-client mariadb-plugin-connect 
mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga 
mariadb-plugin-cassandra mariadb-plugin-spider
Architecture: source
Version: 10.0.24-4
Distribution: unstable
Urgency: low
Maintainer: Debian MySQL Maintainers 
Changed-By: Otto Kekäläinen 
Description:
 libmariadbd-dev - MariaDB embedded database, development files
 libmariadbd18 - MariaDB embedded database
 mariadb-client - MariaDB database client (metapackage depending on the latest 
vers
 mariadb-client-10.0 - MariaDB database client binaries
 mariadb-client-core-10.0 - MariaDB database core client binaries
 mariadb-common - MariaDB common metapackage
 mariadb-plugin-cassandra - Cassandra storage engine for MariaDB
 mariadb-plugin-connect - Connect 

Processed: Bug#817208: Cannot load library /usr/lib/kde4/kio_digikamdates.so

[Debian Bug Tracking System]

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

> reassign 817208 libc6
Bug #817208 [digikam] Cannot load library /usr/lib/kde4/kio_digikamdates.so
Bug reassigned from package 'digikam' to 'libc6'.
No longer marked as found in versions digikam/4:4.14.0-3.
Ignoring request to alter fixed versions of bug #817208 to the same values 
previously set
> forcemerge 817826 817208
Bug #817826 [libc6] libc6: kdeinit4 should be restarted after glibc upgrade
Bug #817208 [libc6] Cannot load library /usr/lib/kde4/kio_digikamdates.so
Severity set to 'important' from 'grave'
Marked as found in versions glibc/2.22-2.
Added tag(s) moreinfo.
Merged 817208 817826
> thanks
Stopping processing here.

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

Bug#817208: Cannot load library /usr/lib/kde4/kio_digikamdates.so

[Aurelien Jarno]

reassign 817208 libc6
forcemerge 817826 817208
thanks

On 2016-03-08 20:35, Ryan Kavanagh wrote:
> Package: digikam
> Version: 4:4.14.0-3
> Severity: grave
> Justification: renders package unusable
> 
> As of today, digikam no longer displays any pictures from my albums.
> 
> The following errors can be found in ~/.xsession-errors:
> 
> Could not open library '/usr/lib/kde4/kio_digikamdates.so'.
> Cannot load library /usr/lib/kde4/kio_digikamdates.so: 
> (/lib/x86_64-linux-gnu/libresolv.so.2: symbol __h_errno, version 
> GLIBC_PRIVATE not defined in file libc.so.6 with link time reference)
> Could not open library '/usr/lib/kde4/kio_digikamalbums.so'.
> Cannot load library /usr/lib/kde4/kio_digikamalbums.so: 
> (/lib/x86_64-linux-gnu/libresolv.so.2: symbol __h_errno, version 
> GLIBC_PRIVATE not defined in file libc.so.6 with link time reference)
> 

This is likely due to the upgrade to glibc 2.22. The workaround is to
restart your KDE session, we don't have any other option right now.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Bug#817840: libvigraimpex: fail of test/math on mips

[Daniel Stender]

Source: libvigraimpex
Version: 1.10.0+git20160120.803d5d4-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Since 1.10.0+git20160120.803d5d4-1 the build breaks on mips [1] with a failure
of test/math:


[ 57%] Linking CXX executable test_math
cd /«BUILDDIR»/libvigraimpex-1.10.0+git20160120.803d5d4/obj/test/math && 
/usr/bin/cmake -E cmake_link_script CMakeFiles/test_math.dir/link.txt 
--verbose=1
/usr/bin/c++   -pthread -std=c++11 -W -Wall -Wextra -Wno-unused-parameter 
-Wno-sign-compare -Wno-unused-variable -Wno-type-limits -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time 
-D_FORTIFY_SOURCE=2 --param ggc-min-expand=20   
CMakeFiles/test_math.dir/test.cxx.o CMakeFiles/test_math.dir/testsuccess.cxx.o  
-o test_math -rdynamic 
Running test_math
cd /«BUILDDIR»/libvigraimpex-1.10.0+git20160120.803d5d4/obj/test/math && 
./run_test_math.sh
Illegal instruction
test/math/CMakeFiles/test_math.dir/build.make:123: recipe for target 
'test/math/test_math' failed
make[5]: *** [test/math/test_math] Error 1
make[5]: *** Deleting file 'test/math/test_math'


This needs to be fixed to complete the ongoing transition [2] to build on all
officially supported archs.

DS

[1] https://buildd.debian.org/status/logs.php?pkg=libvigraimpex=mips

[2] https://bugs.debian.org/815153 (transition: libvigraimpex)

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

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

Bug#812488: Debian jessie removal of certs breaks some irc chats

[Michael Fox]

Another url to test is irc.esper.net (sometimes it works and sometimes it 
doesnt because this url goes to different servers with different certs).
Can this please get an official fix soon as this is causing problems everywhere.

Bug#810506: Opinion about linux-grsec in a stable release

[Moritz Mühlenhoff]

On Wed, Mar 02, 2016 at 09:01:34PM +0100, Yves-Alexis Perez wrote:
> On mer., 2016-03-02 at 20:06 +0100, Moritz Muehlenhoff wrote:
> > Before considering that, did anyone approch grsecurity whether we can get
> > access to the grsecurity stable patches? We would most definitely have 
> > Debian
> > funds to become grsecurity sponsors to obtain access to stable patches.
> 
> I think that'd be something nice anyway, but…
> > 
> > Whether that's possible/desirable by grsecurity is the question, though:
> > Having the stable patches in Debian would make them available to the
> > general public (including those sleazy embedded companies which made them
> > change their distribution scheme).
> 
> Indeed, I didn't even bother to ask because when you gain access to the stable
> patches, you commit yourself to not make them available publicly, which is
> obviously exactly what we would do.

It's the release team's call, but IMO unless upstream changes their policy to
allow public access to stable patches again, this seems rather like a case
for a PPA or possibly backports (but they generally require backports from
what is in testing).

Cheers,
Moritz

Processed: reopening bugs wrt mistaken mariadb-10.0 removal

[Debian Bug Tracking System]

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

> reopen 787118
Bug #787118 {Done: Debian FTP Masters } 
[mariadb-server-10.0] mariadb-server-10.0: Compile with OpenSSL (instead of 
YaSSL)
'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 10.0.24-3+rm.
> reopen 793787
Bug #793787 {Done: Debian FTP Masters } 
[mariadb-client-10.0] mariadb-client-10.0: indirect dependency on 
libmysqlclient18
'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 10.0.24-3+rm.
> reopen 808419
Bug #808419 {Done: Debian FTP Masters } 
[mariadb-10.0] TODO: Add debconf question to make feedback plugin opt-in very 
easy
'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 10.0.24-3+rm.
> reopen 808421
Bug #808421 {Done: Debian FTP Masters } 
[mariadb-10.0] TODO: Implement metadata.yml (DEP12)
'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 10.0.24-3+rm.
> reopen 797210
Bug #797210 {Done: Debian FTP Masters } 
[mariadb-10.0] mariadb-10.0: mariadb-server does not ship a debconf set for 
creating a adminitrative user (like mysql-server do)
'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 10.0.24-3+rm.
> reopen 801959
Bug #801959 {Done: Debian FTP Masters } 
[mariadb-10.0] TODO: Tag mariadb packages with debtags
'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 10.0.24-3+rm.
> reopen 809022
Bug #809022 {Done: Debian FTP Masters } 
[mariadb-10.0] TODO: Add autopkg tests to detect changes introduced by other 
uploaded packages
'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 10.0.24-3+rm.
> reopen 810968
Bug #810968 {Done: Debian FTP Masters } 
[mariadb-server-10.0] mariadb-server-10.0: Logrotate exists 1 if a non-debian 
mysqld is running (e.g. containerized mysqld)
'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 10.0.24-3+rm.
> reopen 808420
Bug #808420 {Done: Debian FTP Masters } 
[mariadb-10.0] TODO: Implement systemd scripts
'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 10.0.24-3+rm.
> reopen 815599
Bug #815599 {Done: Debian FTP Masters } 
[mariadb-server-10.0] mariadb-server-10.0: Postinstall script does not clear 
the  mysql-server/root_password_again field
'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 10.0.24-3+rm.
> reopen 814944
Bug #814944 {Done: Debian FTP Masters } 
[mariadb-connect-engine-10.0] mariadb-connect-engine-10.0: ODBC support 
apparently not compiled in
'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 10.0.24-3+rm.
> kthxbye
Stopping processing here.

Please contact me if you need assistance.
-- 
787118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787118
793787: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793787
797210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797210
801959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801959
808419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808419
808420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808420
808421: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808421
809022: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809022
810968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810968
814944: 

Bug#816063: emacs24: TLS certificate validation is silently broken

[Moritz Muehlenhoff]

On Fri, Feb 26, 2016 at 09:34:33PM -0800, Nathaniel Smith wrote:
> Package: emacs24
> Version: 24.5+1-6+b1
> Severity: serious
> Tags: security
> Justification: 5(b) of https://release.debian.org/testing/rc_policy.txt
> 
> Debian's emacs builds are linked against gnutls:
> 
> (gnutls-available-p)
> t
> 
> By default, they aren't configured to validate TLS certificates,
> leaving users open to trivial MITM attacks:
> 
> (require 'gnutls)
> gnutls-verify-error
> nil
> 
> (url-retrieve-synchronously "https://wrong.host.badssl.com;)
> #
> (url-retrieve-synchronously "https://self-signed.badssl.com;)
> #
> 
> Okay, fine, but at least it is easy to turn this on:
> 
> (setq gnutls-verify-error t)
> 
> There are even some nice docs explaining how and why to do this:
>https://glyph.twistedmatrix.com/2015/11/editor-malware.html
> (Short version: if you aren't using https for the package servers --
> #797477 -- and haven't enabled TLS checking, and ever run
> package-install over coffee-shop wifi, then congratulations, you've
> just allowed anyone within wifi range to execute arbitrary code on
> your user account.)
> 
> However, Debian's emacs24 somehow manages to be so broken that turning
> on cert verification via (setq gnutls-verify-error t) *doesn't
> work*. The docs say it should work, and explain in detail how to
> configure finding the CA trust store (this is configured correctly
> out-of-the-box on Debian). And sometimes I've even had it fail on
> https://wrong.host.badssl.com after setting this (but not
> always). However, it always happily loads
> https://self-signed.badssl.com, which means it's providing no
> protection at all against MITM attacks.
> 
> Bottom line: even if you configure everything correctly, Debian's
> emacs will still happily execute whatever random code your barista
> gives you.

There don't appear to be any gnutls-specific patches in Debian's
emacs24 package, so this is most definitely an upstream bug.

Could you please report it upstream?

Cheers,
Moritz

Bug#813258: [Pkg-sugar-devel] Bug#813258: sugar-record-activity: Should sugar-record-activity be removed?

[Moritz Mühlenhoff]

reassign 813258 ftp.debian.org
retitle 813258 RM: Depends on gstreamer 0.10
severity 813258 normal
thanks

On Tue, Feb 16, 2016 at 11:23:57PM +0100, Moritz Mühlenhoff wrote:
> On Sun, Jan 31, 2016 at 08:16:47AM +0530, Jonas Smedegaard wrote:
> > Quoting Moritz Muehlenhoff (2016-01-31 04:00:28)
> > > Should sugar-record-activity be removed? It depends on gstreamer, 
> > > which is scheduled for removal and there doesn't seem to be any 
> > > upstream activity to port it to modern gstreamer.
> > >
> > > Please address the outstanding bugs or reassign this to ftp.debian.org 
> > > for removal.
> > 
> > Thanks for the concern.  Upstream is quite slow but not dead, so I will 
> > keep waiting.
> 
> Ok. Since there's now only a handful of packages left using gstreamer 0.10
> I will file removal bugs for it and the remaining reverse deps in 3-4 weeks.
> 
> If sugar-record-activity can't be updated in time, it can easily re-enter
> the archive after it has been ported to gstreamer 1.0.

We're down to three remaining reverse deps of gstreamer 0.10. Doing so now.

Cheers,
Moritz

Processed: Re: [Pkg-sugar-devel] Bug#813258: sugar-record-activity: Should sugar-record-activity be removed?

[Debian Bug Tracking System]

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

> reassign 813258 ftp.debian.org
Bug #813258 [sugar-record-activity] sugar-record-activity: Should 
sugar-record-activity be removed?
Bug reassigned from package 'sugar-record-activity' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #813258 to the same values 
previously set
Ignoring request to alter fixed versions of bug #813258 to the same values 
previously set
> retitle 813258 RM: Depends on gstreamer 0.10
Bug #813258 [ftp.debian.org] sugar-record-activity: Should 
sugar-record-activity be removed?
Changed Bug title to 'RM: Depends on gstreamer 0.10' from 
'sugar-record-activity: Should sugar-record-activity be removed?'
> severity 813258 normal
Bug #813258 [ftp.debian.org] RM: Depends on gstreamer 0.10
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#817837: l2tpns: *** buffer overflow detected ***: l2tpns terminated

[Dave Reeve]

Package: l2tpns
Version: 2.2.1-1+b1
Severity: grave
Tags: patch
Justification: renders package unusable

Dear Maintainer,

Running l2tpns causes an instance crash as follows:

# l2tpns -v
*** buffer overflow detected ***: l2tpns terminated
(full trace removed as it doesn't help)

The problem exists in the ring buffer logging code.  Specially the vsprintf
is called with a length of 4095 when the size of the buffer is MAX_LOG_LENGTH
(defined as 512 in l2tpns.h).  The result is that as soon as the program is
executed it crashes as soon as a few log messages are printed.  The following
patch resolves the problem.

I also have some more minor fixes, which resolve compiler warnings.  I am happy
to share these if you let me know where to send them!

Dave 

-- Begin patch
diff --git a/l2tpns.c b/l2tpns.c
index 41e12de..2680908 100644
--- a/l2tpns.c
+++ b/l2tpns.c
@@ -268,7 +268,7 @@ void _log(int level, sessionidt s, tunnelidt t, const char 
*format, ...)
ringbuffer->buffer[ringbuffer->tail].session = s;
ringbuffer->buffer[ringbuffer->tail].tunnel = t;
va_start(ap, format);
-   vsnprintf(ringbuffer->buffer[ringbuffer->tail].message, 4095, 
format, ap);
+   vsnprintf(ringbuffer->buffer[ringbuffer->tail].message, 
MAX_LOG_LENGTH-1, format, ap);
va_end(ap);
}
 #endif
-- End patch

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages l2tpns depends on:
ii  libc6  2.19-18+deb8u3
ii  libcli1.9  1.9.7-1

l2tpns recommends no packages.

l2tpns suggests no packages.

-- no debconf information

Bug#814516: marked as done (pcs,python-pcs: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Thu, 10 Mar 2016 19:35:04 +
with message-id 
and subject line Bug#814516: fixed in pcs 0.9.149-1
has caused the Debian Bug report #814516,
regarding pcs,python-pcs: error when trying to install together
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.)


-- 
814516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pcs,python-pcs
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 0.9.148-1
Control: found -1 0.5+debian-1.2

Hi,

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

  Selecting previously unselected package python-pcs.
  Preparing to unpack .../python-pcs_0.5+debian-1.2_all.deb ...
  Unpacking python-pcs (0.5+debian-1.2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-pcs_0.5+debian-1.2_all.deb (--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/pcs/__init__.py', 
which is also in package pcs 0.9.148-1
  Processing triggers for libc-bin (2.21-7) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/python-pcs_0.5+debian-1.2_all.deb


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

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

  usr/lib/python2.7/dist-packages/pcs/__init__.py

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


pcs=0.9.148-1_python-pcs=0.5+debian-1.2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pcs
Source-Version: 0.9.149-1

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated pcs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 10 Mar 2016 20:04:36 +0100
Source: pcs
Binary: pcs
Architecture: source
Version: 0.9.149-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 

Changed-By: Christoph Berg 
Description:
 pcs- Pacemaker Configuration System
Closes: 814450 814516
Changes:
 pcs (0.9.149-1) unstable; urgency=medium
 .
   * New upstream version.
   * Use non-multi-arch settings.py/rb on all architectures.
 (Closes: #814450)
   * Conflict with python-pcs. This (unrelated) python module installs files to
 the same location as we do. (Closes: #814516)
 Installing our files to a different location would still risk this module
 getting loaded when we wanted our own files. The real solution would be
 renaming our (private) module, but this seems infeasible for now.
Checksums-Sha1:
 0933b986b2a642adac845b25800bdf5c367b2b9c 1980 pcs_0.9.149-1.dsc
 b277913a11b337a1d4bb4cd57a1bfc9205c9611a 1557619 pcs_0.9.149.orig.tar.gz
 0f103d6a162a0cdcd6fb2d323c801a1a3f81cc73 

Bug#817793: marked as done (qt3d-opensource-src: B-D on obsolete package libqt5xcbqpa5)

[Debian Bug Tracking System]

Your message dated Thu, 10 Mar 2016 19:20:17 +
with message-id 
and subject line Bug#817793: fixed in qt3d-opensource-src 5.5.1-5
has caused the Debian Bug report #817793,
regarding qt3d-opensource-src: B-D on obsolete package libqt5xcbqpa5
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.)


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

Hi,

your package Build-Depends on the obsolete transitional package
libqt5xcbqpa5 which is no longer built by qtbase-opensource-src. Please
switch to libqt5gui5.


Andreas
--- End Message ---
--- Begin Message ---
Source: qt3d-opensource-src
Source-Version: 5.5.1-5

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

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

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

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
qt3d-opensource-src package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 10 Mar 2016 16:03:18 -0300
Source: qt3d-opensource-src
Binary: libqt53dcore5 libqt53dquick5 libqt53dquickrenderer5 libqt53dinput5 
libqt53drenderer5 libqt53dlogic5 libqt53dcollision5 qt3d-gltfsceneparser-plugin 
qt3d-assimpsceneparser-plugin qml-module-qt3d qml-module-qtquick-scene3d 
qt3d5-dev qt3d5-examples qt3d5-dbg qt3d5-doc qt3d5-doc-html
Architecture: source
Version: 5.5.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Description:
 libqt53dcollision5 - Qt 3D collision module
 libqt53dcore5 - Qt 3D module
 libqt53dinput5 - Qt 3D Input module
 libqt53dlogic5 - Qt 3D logic module
 libqt53dquick5 - Qt 3D Quick module
 libqt53dquickrenderer5 - Qt 3D Quick Renderer module
 libqt53drenderer5 - Qt 3D Renderer module
 qml-module-qt3d - Qt 5 3D QML module
 qml-module-qtquick-scene3d - Qt 5 Quick Scene 3D QML module
 qt3d-assimpsceneparser-plugin - Qt 3D GL Transmission Format scene parser 
plugin
 qt3d-gltfsceneparser-plugin - Qt 3D GL Transmission Format scene parser plugin
 qt3d5-dbg  - Qt 3D library debugging symbols
 qt3d5-dev  - Qt 5 3D development files
 qt3d5-doc  - Qt 3D documentation
 qt3d5-doc-html - Qt 3D HTML documentation
 qt3d5-examples - Qt 5 3d examples
Closes: 817793
Changes:
 qt3d-opensource-src (5.5.1-5) unstable; urgency=medium
 .
   * Remove libqt5xcb5 from build dependencies. It is now part of libqt5gui5
 which is dragged in by qtbase5-dev (Closes: #817793).
   * Add qml-module-qtquick-scene3d as a qt3d5-examples' dependency, needed
 by qt3d's controls.
Checksums-Sha1:
 2881228aaf3eaf2ce86f3b88c145be143d89be3e 3435 qt3d-opensource-src_5.5.1-5.dsc
 ca744fa8fb88ea99b7d3673857cf0b8524cfb4e8 25140 
qt3d-opensource-src_5.5.1-5.debian.tar.xz
Checksums-Sha256:
 f5f6c17323bd539f60a72ddbe8afac48c6eabd1fe262a9089be2c7dafecea887 3435 
qt3d-opensource-src_5.5.1-5.dsc
 43217d79939e8bf8aff04099f6178901ee5e522fd31cd980e594e231d66d77f4 25140 
qt3d-opensource-src_5.5.1-5.debian.tar.xz
Files:
 b2774d6539896b23773bb1cea1e5eb92 3435 libs optional 
qt3d-opensource-src_5.5.1-5.dsc
 6c0524ab111c517b5ff0a1227e75dc1f 25140 libs optional 
qt3d-opensource-src_5.5.1-5.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW4cUcAAoJEKtkX0BihqfQpsIP/i/Yy1Lx/nW/UTTfHl00n1Fn
X7omPrRN8aaHuL3xjR6Yjd3aBc1KBdcX3w4xgjncUOb1ek5U0AeLI3LkcBsH98b7
64nY6YqLmbkX6y2KJyKirQDoGxv305oAPYYAxCsNNUb6ukqJza0P/wBfngEQevSn
+oTsp4q46LUEVMO5BLA3U+AA0cXx3zqUgF2YJEvVCMGPXze1C0W7uUnMx/Q+MSE0
5ju32Ig4HnMxy1/3fOKp2luC2pS1G1kJJpAL/9CMunTfnlJFp9k9qKbMPA1aruc4
FjnuwlZlMu/jxAZvEFgRZUnhlUse2gAPCJ0FDcKBI5BkkYsoZ2MMyGsj4cPvcMQI
ht2Lir2GpFgSXJaUYEUYcAAH6uc6DrOJPWVRJM+no6XebC+WAflGZc5l4V7+IXQm
aW1CrKTPvbFiXH153ZK6F40KWqh4j+7rBYrhi/nNTkY2CK5ln6/pfC4dHeOlNpcF

Bug#817262: marked as done (ruby-libvirt: B-D on cruft package libvirt-bin)

[Debian Bug Tracking System]

Your message dated Thu, 10 Mar 2016 19:20:23 +
with message-id 
and subject line Bug#817262: fixed in ruby-libvirt 0.6.0-1
has caused the Debian Bug report #817262,
regarding ruby-libvirt: B-D on cruft package libvirt-bin
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.)


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

Hi,

libvirt-bin was a transitional package and is no longer built by
src:libvirt. Please adjust your Build-Depends.


Andreas
--- End Message ---
--- Begin Message ---
Source: ruby-libvirt
Source-Version: 0.6.0-1

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

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

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated ruby-libvirt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 10 Mar 2016 19:53:27 +0100
Source: ruby-libvirt
Binary: ruby-libvirt
Architecture: source
Version: 0.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Libvirt Maintainers 

Changed-By: Guido Günther 
Closes: 817262
Description: 
 ruby-libvirt - Ruby bindings for libvirt
Changes:
 ruby-libvirt (0.6.0-1) unstable; urgency=medium
 .
   * [dc7846f] New upstream version 0.6.0
   * [f33fafb] Build-dep on libvirt-daemon instead of libvirt-bin since the
 later is no more (Closes: #817262)
   * [e2d0e90] Bump standards version
Checksums-Sha1: 
 ee7e2fd5a7b0f6d928cec74684a7c13947dd39e7 2034 ruby-libvirt_0.6.0-1.dsc
 bea12787fee8e3cc9dd76cfc332a207c0d4c0946 113866 ruby-libvirt_0.6.0.orig.tar.gz
 b1ec48678338e1e48fd9b933be13054e6805c902 3336 
ruby-libvirt_0.6.0-1.debian.tar.xz
Checksums-Sha256: 
 3ce1f74c6ede942295b978d7a7017325c8e0fe90341aa3d2d52591ff015b8367 2034 
ruby-libvirt_0.6.0-1.dsc
 18ccacf3b3be3912b326a910c4c148c4ff5428ac2bff7d35a93eed786a17404c 113866 
ruby-libvirt_0.6.0.orig.tar.gz
 302130af2ce539a33f3aad8914bb110a4b9febad9428d6b5f6035d1cf8cac20a 3336 
ruby-libvirt_0.6.0-1.debian.tar.xz
Files: 
 3c25d59581cd1f40644049cfa08f7d57 2034 ruby optional ruby-libvirt_0.6.0-1.dsc
 4eaf85dfc0653b0966d889745b42bd3d 113866 ruby optional 
ruby-libvirt_0.6.0.orig.tar.gz
 9a424c301da26b93d53490fab6927580 3336 ruby optional 
ruby-libvirt_0.6.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJW4cX+AAoJEAe4t7DqmBILio8P/inmqpTS9+Dm+pVrrCmY2QCf
ptvdYdodiHT+jImcdrW+4x1eHTFr1zqUsWBCapUwxKvp0ayDvIY4+xGQRs7ZAEgG
YES+G/EfyvQYWqz46MjCcmKWK5uY851oKCeyITvkDvdpmHh9g5XNKw9Toef9R3D8
BaSMiBN3AF3/elL9zLElDZI2HM4Y+ceDA7pwj5ri73EroSqb9nEfvaYQ81V3fuvQ
9wsKHmDaU/+tGFA3Gl5ScVdFn073Ed1rznuD/wfJMHd4AwpLFov8FM9Eyz55ACNn
v3KMItnRAiPgYBUy9HgFEWQGrDnwnCA4eHrsaawP+dXRM26gCJfeno0g7UQXDHkQ
V1hLVmqkxNQQ36b/JBIZBX8CBtyAI69EZ6Rn60/FDETYMA4SGG2l5dClkLSxkSdA
iiCED+IXFOjY3Ft6wmCnMm5jJUhsVm8MBw674uO2ckcyjhqTCUETAiD7Jtu+Ddsa
QNmnN3USS1azKvKgvbqII1PnJzx858+bcF5Tqtsm14X0Duf8cDZByTp+cjvhEIHP
7UfKZE2RzrYiblVLIThgKb8qwts2QigdC9RPVomVaBbZiUtp3BW1/twEAKbrKpWE
vevwxDLrR1qziQtpqJWbvV16anVT0pEoKGhj3oQ19RRHsRpro1tnvqotjEusF31p
+t0AEn2KVd1yU/xZTfaN
=SXmC
-END PGP SIGNATURE End Message ---

Bug#811340: php5-lasso: fails to install: php5-lasso.postinst: php5enmod: not found

[Frederic Peters]

Hi,

Thijs Kinkhorst wrote:
> Hi Frederic,
> 
> > Severity: serious
> 
> >  Setting up php5-lasso (2.5.0-3) ...
> >  /var/lib/dpkg/info/php5-lasso.postinst: 4: /var/lib/dpkg/info/php5-
> > lasso.postinst: php5enmod: not found
> >  dpkg: error processing package php5-lasso (--configure):
> >   subprocess installed post-installation script returned error exit
> > status 127
> 
> Have you been able to look at this yet? It's keeping lasso and by
> extension libapache2-mod-auth-mellon out of testing currently.

Indeed.  A new upstream version was planned and I hoped to use it but
it seems like it has some more fundamental bugs; I should probably
ignore it and fix packaging of the 2.5.0 version.  I'll do that.


> Not sure if upstream is already working on a PHP 7 compatible module.

Not yet.


Frederic

Processed: reassign 814516 to pcs, affects 814516

[Debian Bug Tracking System]

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

> reassign 814516 pcs
Bug #814516 [pcs,python-pcs] pcs,python-pcs: error when trying to install 
together
Bug reassigned from package 'pcs,python-pcs' to 'pcs'.
No longer marked as found in versions pcs/0.9.148-1 and 
python-pcs/0.5+debian-1.2.
Ignoring request to alter fixed versions of bug #814516 to the same values 
previously set
> affects 814516 python-pcs
Bug #814516 [pcs] pcs,python-pcs: error when trying to install together
Added indication that 814516 affects python-pcs
> thanks
Stopping processing here.

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

Processed: user debian...@lists.debian.org, usertagging 811185, usertagging 809998, affects 809998 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 811185 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 809998 piuparts
Usertags were: piuparts.
Usertags are now: piuparts.
> affects 809998 + libboost-mpi-python1.55.0 libboost-mpi1.55-dev
Bug #809998 [libboost-date-time1.55.0] libboost-date-time1.55.0: not 
installable in sid
Added indication that 809998 affects libboost-mpi-python1.55.0 and 
libboost-mpi1.55-dev
> usertags 812743 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 812743 + ros-simulators-dev
Bug #812743 [libsdformat4-dev] libsdformat4-dev and libsdformat3-dev: error 
when trying to install together
Added indication that 812743 affects ros-simulators-dev
> found 813247 0.4.9-1
Bug #813247 [python-greenlet-dbg,python3-greenlet,python-greenlet-dev] 
python*-greenlet*: unhandled symlink to directory conversion: 
/usr/share/doc/PACKAGE
Marked as found in versions python-greenlet/0.4.9-1.
> usertags 816965 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 816965 + mathematica-fonts
Bug #816965 {Done: Adam Borowski } [fonts-mathematica] 
fonts-mathematica: fails to install if mathematica-fonts 17 is installed
Added indication that 816965 affects mathematica-fonts
> tags 817262 + sid stretch
Bug #817262 [src:ruby-libvirt] ruby-libvirt: B-D on cruft package libvirt-bin
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

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

Bug#813359: xserver-xorg-input-aiptek: Compilation fails due to API change in xorg

[Julien Cristau]

On Wed, Mar  9, 2016 at 21:10:31 +0100, Tobias Schlemmer wrote:

> Hi,
> 
> Am 04.03.2016 um 20:13 schrieb Julien Cristau:
> > On Thu, Mar  3, 2016 at 21:36:38 +0100, Tobias Schlemmer wrote:
> > 
> >> Package: xserver-xorg-input-aiptek
> >> Version: 1:1.4.1-1
> >> Followup-For: Bug #813359
> > is the aiptek tablet not supported by any of the better maintained
> > drivers (libinput/evdev/wacom)?
> 
> Thanks for the question. But those drivers have all their drawbacks.
> 
> • libinput simply crashes xorg when I tap with the pen on the tablet. If
> I'm not mistaken I read, that this driver does not support tablets, yet.
> 
> • Wacom seems not to be of any help.
> 
> • evdev does not work out of the box. With no configuration the X server
> searches for the aiptek drivers, even if evdev is loaded. So I had to
> modify xorg.conf in order to get the driver running at all. But then it
> does not work as expected. It uses the key area for the pen pointer AND
> sends keyboard events when I tapped on one Key symbols. This is bad
> behaviour as it leads to unpredictable results.
> 
> • Furthermore searching the internet for Aiptek and Xorg does not reveal
> any of the other optiions. For my devices it's even worse at it is
> branded as Trust.
> 
> • The Ubuntu Wiki only talks about the aiptek module.
> 
> Conclusion: The aiptek module seems to be the most useful one, so far.
> 
Alright, thanks.  Pushed your patch to
https://cgit.freedesktop.org/xorg/driver/xf86-input-aiptek/commit/?id=f075deff61d3092d6754e48a3b63d40647888a35
and hopefully someone will find time to update the debian package soon.

Cheers,
Julien

Bug#814589: otrs2: source-less files; undocumented copyrights/licenses; abuse of lintian-overrides; systematic DFSG violations

[Patrick Matthäi]

Am 03.03.2016 um 14:31 schrieb Julien Cristau:

On Wed, Mar  2, 2016 at 12:36:46 +0100, Patrick Matthäi wrote:


@Debian release team:
I would like to request a strech ignore for this bug. I am aware of these
problems, but I am not able to fix them nor did anyone ever offered me help
with this JS foo. If it would not be possible I had to resign otrs packaging
in Debian.


There's two issues as I understand it:
- embedded copies of third-party code
- lack of source for some of them

The former is not necessarily RC, and I'm not thrilled about ignoring
the latter.  Not to mention we're months away from freeze, so this isn't
the time to consider stretch-ignore tags, there's plenty of time to fix
bugs still.



Thanks for your answer.
I will try to fix the serious bugs in the next time. Just get a new 
notebook after my workstation crashed...

Bug#817828: php-mail-mime: Missing dependency on php-pear

[Pierre Pronchery]

Package: php-mail-mime
Version: 1.8.9-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

please consider registering a hard dependency on the php-pear package
for php-mail-mime, as it will not work otherwise.

As seen in /usr/share/php/Mail/mime.php:
  66 require_once 'PEAR.php';   
  

This is the first effective line of code in this file.

Thank you!

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

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

Versions of packages php-mail-mime depends on:
ii  php5-common  5.6.17+dfsg-0+deb8u1

php-mail-mime recommends no packages.

php-mail-mime suggests no packages.

-- debconf-show failed

Bug#817008: unfulfilled dependencies

[Mattia Rizzolo]

On Mon, Mar 07, 2016 at 10:27:09PM +0800, 殷啟聰 wrote:
> I have fixed it but not yet uploaded it.

So, is this by any chance fixed by 24.3.3+2?

If so, can you please close this bug with a fixed version set?

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#817816: marked as done (System freeze with CPU hotplug)

[Debian Bug Tracking System]

Your message dated Thu, 10 Mar 2016 17:34:54 +
with message-id <1457631294.3001.54.ca...@decadent.org.uk>
and subject line Re: Bug#817816: System freeze with CPU hotplug
has caused the Debian Bug report #817816,
regarding System freeze with CPU hotplug
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.)


-- 
817816: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-4.4.0-1-amd64
Version: 4.4.4-1
Severity: critical
Justification: renders system unusable


When I run the following commands, the system freezes:

# echo 0 | tee /sys/devices/system/cpu/cpu*/online && echo 1 | sudo tee 
/sys/devices/system/cpu/cpu*/online

The system freezes randomly when the CPUs are being onlined or offlined. The 
system is installed on a VMware virtual machine with 4 processors. Here's a 
stacktrace of the infinite loop:

---[regs]
  RAX: 0x8160AC40  RBX: 0x0003  RCX: 0x  
RDX: 0x0003  o d i t s Z a P c 
  RSI: 0x0286  RDI: 0x88004E6B7D98  RBP: 0x88004E6B7D98  
RSP: 0x88007CFCFDC0  RIP: 0x8110AD52
  R8 : 0x88007F60F380  R9 : 0x  R10: 0x81B004C0  
R11: 0x  R12: 0x88004E6B7DBC
  R13: 0x0282  R14: 0x88007F60F300  R15: 0x8110AD10
  CS: 0010  DS:   ES:   FS:   GS:   SS: 0018

---[code]
=> 0x8110ad52 :  mov    ebx,DWORD PTR [rbp+0x20]
   0x8110ad55 :  cmp    edx,ebx
   0x8110ad57 :  je     0x8110ad74 

   0x8110ad59 :  cmp    ebx,0x2
   0x8110ad5c :  je     0x8110ad9e 

   0x8110ad5e :  cmp    ebx,0x3
   0x8110ad61 :  jne    0x8110ad68 

   0x8110ad63 :  test   r14b,r14b
-
multi_cpu_stop (data=0x88004e6b7d98) at 
/build/linux-xT7CCq/linux-4.4.4/kernel/stop_machine.c:197
197 /build/linux-xT7CCq/linux-4.4.4/kernel/stop_machine.c: No such file or 
directory.
gdb$ bt
#0  multi_cpu_stop (data=0x88004e6b7d98) at 
/build/linux-xT7CCq/linux-4.4.4/kernel/stop_machine.c:197
#1  0x8110afed in cpu_stopper_thread (cpu=) at 
/build/linux-xT7CCq/linux-4.4.4/kernel/stop_machine.c:456
#2  0x81097d49 in smpboot_thread_fn (data=0x88004e6b7d98) at 
/build/linux-xT7CCq/linux-4.4.4/kernel/smpboot.c:163
#3  0x81094dfd in kthread (_create=0x88007ce82100) at 
/build/linux-xT7CCq/linux-4.4.4/kernel/kthread.c:209
#4  0x8158ed8f in ret_from_fork () at 
/build/linux-xT7CCq/linux-4.4.4/arch/x86/entry/entry_64.S:486
#5  0x in ?? ()
gdb$ x/x $rbp+0x20
0x88004e6b7db8: 0x0003

In the function multi_cpu_stop(), curstate equals MULTI_STOP_RUN and seems to 
never become equal to MULTI_STOP_EXIT. Let me know if you require additional 
informations.
Thanks--- End Message ---
--- Begin Message ---
On Thu, 2016-03-10 at 17:32 +0100, Harry Junior wrote:
> Package: linux-image-4.4.0-1-amd64
> Version: 4.4.4-1
> Severity: critical
> Justification: renders system unusable
> 
> 
> When I run the following commands, the system freezes:
> 
> # echo 0 | tee /sys/devices/system/cpu/cpu*/online && echo 1 | sudo
> tee /sys/devices/system/cpu/cpu*/online
> 
> The system freezes randomly when the CPUs are being onlined or
> offlined. The system is installed on a VMware virtual machine with 4
> processors. Here's a stacktrace of the infinite loop:
[...]

You just asked to offline all CPUs, making the system unusable.  I
don't see any bug here.

Ben.

-- 
Ben Hutchings
To err is human; to really foul things up requires a computer.


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

Bug#811340: php5-lasso: fails to install: php5-lasso.postinst: php5enmod: not found

[Thijs Kinkhorst]

Hi Frederic,

> Severity: serious

>  Setting up php5-lasso (2.5.0-3) ...
>  /var/lib/dpkg/info/php5-lasso.postinst: 4: /var/lib/dpkg/info/php5-
> lasso.postinst: php5enmod: not found
>  dpkg: error processing package php5-lasso (--configure):
>   subprocess installed post-installation script returned error exit
> status 127

Have you been able to look at this yet? It's keeping lasso and by
extension libapache2-mod-auth-mellon out of testing currently.

Not sure if upstream is already working on a PHP 7 compatible module.

Cheers,
Thijs



signature.asc
Description: OpenPGP digital signature

Bug#817820: fonts-mathematica: missing Depends: wget

[Andreas Beckmann]

Package: fonts-mathematica
Version: 19
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

Selecting previously unselected package fonts-mathematica.
Preparing to unpack .../fonts-mathematica_19_all.deb ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
debconf: falling back to frontend: Readline
The license has already been accepted
Unpacking fonts-mathematica (19) ...
Setting up unzip (6.0-20) ...
Setting up fonts-mathematica (19) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
debconf: falling back to frontend: Readline
/var/lib/dpkg/info/fonts-mathematica.postinst: 65: 
/var/lib/dpkg/info/fonts-mathematica.postinst: wget: not found
Download seems to fail.
checking TrueType.zip
Downloaded file looks corrupted!
The fonts might be removed on the Web and if so we can do nothing, sorry.



cheers,

Andreas

Bug#817819: susv4tc1.tar.bz2 has changed again ...

[Andreas Beckmann]

Package: susv4
Version: 7.20160107
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 7.20160107~deb8u1

Hi,

http://pubs.opengroup.org/onlinepubs/9699919799/download/susv4tc1.tar.bz2
has changed, again:

  Selecting previously unselected package susv4.
  (Reading database ... 
(Reading database ... 7503 files and directories currently installed.)
  Preparing to unpack .../susv4_7.20160107_all.deb ...
  Unpacking susv4 (7.20160107) ...
  Setting up susv4 (7.20160107) ...
  Fetching file...
  --2016-03-05 04:43:27--  
http://pubs.opengroup.org/onlinepubs/9699919799/download/susv4tc1.tar.bz2
  Resolving localhost (localhost)... 127.0.0.1
  Connecting to localhost (localhost)|127.0.0.1|:3128... connected.
  Proxy request sent, awaiting response... 200 OK
  Length: 3638404 (3.5M) [application/x-bzip2]
  Saving to: '/tmp/tmp.N54Wdshhjm/susv4tc1.tar.bz2'
  
  
susv4tc1.tar.bz2  0%[]   0  --.-KB/s   
susv4tc1.tar.bz2 64%[===>]   2.24M  10.8MB/s   
susv4tc1.tar.bz2100%[===>]   3.47M  15.9MB/sin 0.2s
  
  2016-03-05 04:43:27 (15.9 MB/s) - '/tmp/tmp.N54Wdshhjm/susv4tc1.tar.bz2' 
saved [3638404/3638404]
  
  Verifying SHA512 checksum...
  dpkg: error processing package susv4 (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   susv4


Cheers,

Andreas

Processed: susv4tc1.tar.bz2 has changed again ...

[Debian Bug Tracking System]

Processing control commands:

> found -1 7.20160107~deb8u1
Bug #817819 [susv4] susv4tc1.tar.bz2 has changed again ...
Marked as found in versions sus/7.20160107~deb8u1.

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

Bug#817818: ruby-pgplot: out of date binaries on i386

[Emilio Pozuelo Monfort]

Source: ruby-pgplot
Version: 0.1.9-3
Severity: serious

There are no i386 binaries for 0.1.9-3, preventing the new version from
entering testing.

Likewise for arm64, but I have pinged the porter who uploaded the previous
binaries. Feel free to build and upload them if you want to though.

Cheers,
Emilio

Bug#815364: OpenSLP 1.2 should not be part of stretch

[Luca BRUNO]

severity 815364 important
tags + 815364 pending
thanks

On Thu, 13 Aug 2015 23:55:59 +0200 Moritz Muehlenhoff  wrote:

> The last maintainer upload of openslp happened in 2007
> and it's orphaned for 5.5 years now. The 1.2 branch is
> completely abandoned upstream.

Thanks for the report.
We already discussed dropping OpenSLP support from OpenLDAP and it is a 
planned change:
http://lists.alioth.debian.org/pipermail/pkg-openldap-devel/2016-January/006598.html

Our git trunk is currently entangled in a larger new upstream change, so we'll
queue this for later.

Cheers, Luca

-- 
 .''`.  ** Debian GNU/Linux **  | Luca Bruno (kaeso)
: :'  :   The Universal O.S.| lucab (AT) debian.org
`. `'`  | GPG: 0xBB1A3A854F3BBEBF
  `- http://www.debian.org  | Debian GNU/Linux Developer


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

Processed (with 1 error): Re: OpenSLP 1.2 should not be part of stretch

[Debian Bug Tracking System]

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

> severity 815364 important
Bug #815364 [openldap] openldap: build-depends on libslp-dev
Severity set to 'important' from 'serious'
> tags + 815364 pending
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#815125: Boot failure with Debian linux 4.4.2 package

[Matt Fleming]

On Wed, 09 Mar, at 10:56:07PM, Matt Fleming wrote:
> On Wed, 09 Mar, at 11:01:18PM, Alexis Murzeau wrote:
> > 
> > Indeed I get the "Could not reserve range" message, and with a kernel
> > v4.3 the physical address 0x1 contains the value 1.
> > And this patch works and make a unmodified + this patch 4.4 debian
> > kernel boots, nice well found :)
>  
> Great, thanks for testing.
> 
> > However, now a bad page state is reported in dmesg (which doesn't seem
> > to affect the kernel to me as a user but might hide something buggy) :
> > [0.030096] BUG: Bad page state in process swapper/0  pfn:0
> > [0.030100] page:ea00 count:0 mapcount:1 mapping:
> >(null) index:0x0
> > [0.030102] flags: 0x0()
> > 
> > The efi_free_boot_services function seems to expect size == 0 to not
> > free non reserved memory according to commit 7d68dc3.
> > Not sure if this bad page state is related to this patch though, but I
> > don't get this with the 4.3 kernel.
> 
> Yeah, it's definitely related to my quick and dirty patch. I'll have a
> think about how to fix it properly tomorrow morning.

Alexis, could you, and anybody else that hit this bug, please try out
the attached patch? If it works for you I'll pull it into the EFI tree
ASAP - the merge window is approaching fast. 
commit 7738188068b9
Author: Matt Fleming 
Date:   Wed Mar 9 14:34:24 2016 +

x86/efi: Allow reserving E820_RESERVED regions

Some machines place EFI regions in the zero page (physical address
0x) and we need to ensure that they're mapped into the EFI
page tables now that the kernel doesn't do it for us with
trim_bios_range().

commit 7d68dc3f1003 ("x86, efi: Do not reserve boot services regions
within reserved areas").

Reported-by: Alexis Murzeau 
Link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815125
Cc: Maarten Lankhorst 
Cc: Borislav Petkov 
Cc: Ingo Molnar 
Cc: Ben Hutchings 
Signed-off-by: Matt Fleming 

diff --git a/arch/x86/platform/efi/quirks.c b/arch/x86/platform/efi/quirks.c
index 2326bf51978f..ae850932dd16 100644
--- a/arch/x86/platform/efi/quirks.c
+++ b/arch/x86/platform/efi/quirks.c
@@ -164,6 +164,25 @@ efi_status_t efi_query_variable_store(u32 attributes, 
unsigned long size,
 EXPORT_SYMBOL_GPL(efi_query_variable_store);
 
 /*
+ * This function must be used to ensure we do not free already reserved
+ * regions, since that means they're owned by somebody else. Only
+ * reserve (and then free) regions:
+ *
+ * - Not within any part of the kernel
+ * - Not the bios reserved area (E820_RESERVED)
+ */
+static bool can_free_region(u64 start, u64 size)
+{
+   if (start + size > __pa_symbol(_text) && start <= __pa_symbol(_end))
+   return false;
+
+   if (!e820_all_mapped(start, start+size, E820_RAM))
+   return false;
+
+   return true;
+}
+
+/*
  * The UEFI specification makes it clear that the operating system is free to 
do
  * whatever it wants with boot services code after ExitBootServices() has been
  * called. Ignoring this recommendation a significant bunch of EFI 
implementations 
@@ -180,26 +199,50 @@ void __init efi_reserve_boot_services(void)
efi_memory_desc_t *md = p;
u64 start = md->phys_addr;
u64 size = md->num_pages << EFI_PAGE_SHIFT;
+   bool already_reserved;
 
if (md->type != EFI_BOOT_SERVICES_CODE &&
md->type != EFI_BOOT_SERVICES_DATA)
continue;
-   /* Only reserve where possible:
-* - Not within any already allocated areas
-* - Not over any memory area (really needed, if above?)
-* - Not within any part of the kernel
-* - Not the bios reserved area
-   */
-   if ((start + size > __pa_symbol(_text)
-   && start <= __pa_symbol(_end)) ||
-   !e820_all_mapped(start, start+size, E820_RAM) ||
-   memblock_is_region_reserved(start, size)) {
-   /* Could not reserve, skip it */
-   md->num_pages = 0;
-   memblock_dbg("Could not reserve boot range 
[0x%010llx-0x%010llx]\n",
-start, start+size-1);
-   } else
+
+   already_reserved = memblock_is_region_reserved(start, size);
+
+   /*
+* Because the following memblock_reserve() is paired
+* with free_bootmem_late() for this region in
+* efi_free_boot_services(), we must be extremely
+* careful not to reserve, and subsequently free,
+* critical regions of memory (like the kernel image) or
+

Bug#817816: System freeze with CPU hotplug

[Harry Junior]

Package: linux-image-4.4.0-1-amd64
Version: 4.4.4-1
Severity: critical
Justification: renders system unusable


When I run the following commands, the system freezes:

# echo 0 | tee /sys/devices/system/cpu/cpu*/online && echo 1 | sudo tee 
/sys/devices/system/cpu/cpu*/online

The system freezes randomly when the CPUs are being onlined or offlined. The 
system is installed on a VMware virtual machine with 4 processors. Here's a 
stacktrace of the infinite loop:

---[regs]
  RAX: 0x8160AC40  RBX: 0x0003  RCX: 0x  
RDX: 0x0003  o d i t s Z a P c 
  RSI: 0x0286  RDI: 0x88004E6B7D98  RBP: 0x88004E6B7D98  
RSP: 0x88007CFCFDC0  RIP: 0x8110AD52
  R8 : 0x88007F60F380  R9 : 0x  R10: 0x81B004C0  
R11: 0x  R12: 0x88004E6B7DBC
  R13: 0x0282  R14: 0x88007F60F300  R15: 0x8110AD10
  CS: 0010  DS:   ES:   FS:   GS:   SS: 0018

---[code]
=> 0x8110ad52 :  mov    ebx,DWORD PTR [rbp+0x20]
   0x8110ad55 :  cmp    edx,ebx
   0x8110ad57 :  je     0x8110ad74 

   0x8110ad59 :  cmp    ebx,0x2
   0x8110ad5c :  je     0x8110ad9e 

   0x8110ad5e :  cmp    ebx,0x3
   0x8110ad61 :  jne    0x8110ad68 

   0x8110ad63 :  test   r14b,r14b
-
multi_cpu_stop (data=0x88004e6b7d98) at 
/build/linux-xT7CCq/linux-4.4.4/kernel/stop_machine.c:197
197 /build/linux-xT7CCq/linux-4.4.4/kernel/stop_machine.c: No such file or 
directory.
gdb$ bt
#0  multi_cpu_stop (data=0x88004e6b7d98) at 
/build/linux-xT7CCq/linux-4.4.4/kernel/stop_machine.c:197
#1  0x8110afed in cpu_stopper_thread (cpu=) at 
/build/linux-xT7CCq/linux-4.4.4/kernel/stop_machine.c:456
#2  0x81097d49 in smpboot_thread_fn (data=0x88004e6b7d98) at 
/build/linux-xT7CCq/linux-4.4.4/kernel/smpboot.c:163
#3  0x81094dfd in kthread (_create=0x88007ce82100) at 
/build/linux-xT7CCq/linux-4.4.4/kernel/kthread.c:209
#4  0x8158ed8f in ret_from_fork () at 
/build/linux-xT7CCq/linux-4.4.4/arch/x86/entry/entry_64.S:486
#5  0x in ?? ()
gdb$ x/x $rbp+0x20
0x88004e6b7db8: 0x0003

In the function multi_cpu_stop(), curstate equals MULTI_STOP_RUN and seems to 
never become equal to MULTI_STOP_EXIT. Let me know if you require additional 
informations.
Thanks

Bug#816739: rsyslog-gnutls: imtcp/TLS hangs on dropped packages

[Luca BRUNO]

On Wednesday, March 09, 2016 09:09:42 PM you wrote:

> I don't have the setup to test this. So if you want to see this fixed in
> stable, it would be great if you can apply the upstream fix on top of
> 8.4.2 and test whether it actually fixes the issue.

I have this running live in a log aggregation center, but unfortunately 
reproducing this is somehow non-deterministic (it randomly happens from time 
to time, after several weeks that it is running under moderate load, without 
simple triggers).

I have now applied this patch on top of 8.4.2-1+deb8u2, and I'll let it run 
for some time in the environment above to check if it still deadlocks (however 
I can't exclude false negatives if the bug doesn't trigger).

Ciao, Luca
-- 
 .''`.  ** Debian GNU/Linux **  | Luca Bruno (kaeso)
: :'  :   The Universal O.S.| lucab (AT) debian.org
`. `'`  | GPG: 0xBB1A3A854F3BBEBF
  `- http://www.debian.org  | Debian GNU/Linux Developer


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

Bug#817815: drupal7-mod-civicrm: directory vs. symlink conflict: /usr/share/drupal7/sites -> /etc/drupal/7/sites

[Andreas Beckmann]

Package: drupal7-mod-civicrm
Version: 4.7.2+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package installs files over
an existing symlink shipped or created by another package.

Your package ships:

drwxr-xr-x root/root 0 2016-02-26 15:34 ./usr/share/drupal7/
drwxr-xr-x root/root 0 2016-02-26 15:34 ./usr/share/drupal7/sites/
drwxr-xr-x root/root 0 2016-02-26 15:34 
./usr/share/drupal7/sites/default/
drwxr-xr-x root/root 0 2016-02-26 15:34 
./usr/share/drupal7/sites/default/files/
lrwxrwxrwx root/root 0 2016-02-26 15:34 
./usr/share/drupal7/sites/default/files/civicrm -> /var/lib/civicrm
lrwxrwxrwx root/root 0 2016-02-26 15:34 
./usr/share/drupal7/sites/default/civicrm -> /etc/civicrm

but package drupal7 ships:

drwxr-xr-x root/root 0 2016-02-26 05:58 ./etc/drupal/
drwxr-xr-x root/root 0 2016-02-26 05:58 ./etc/drupal/7/
drwxr-xr-x root/root 0 2016-02-26 05:58 ./etc/drupal/7/sites/
drwxr-xr-x root/root 0 2016-02-26 05:58 ./etc/drupal/7/sites/default/
drwxr-xr-x root/root 0 2016-02-26 05:58 ./usr/share/drupal7/
lrwxrwxrwx root/root 0 2016-02-26 05:58 
./etc/drupal/7/sites/default/files -> /var/lib/drupal7/files
lrwxrwxrwx root/root 0 2016-02-26 05:58 ./usr/share/drupal7/sites -> 
/etc/drupal/7/sites


Installing something over existing symlinks is considered bad practice.
See e.g. https://lists.debian.org/87ehlevcrf@windlord.stanford.edu

It may break in subtle ways and dpkg cannot detect this as a problem.
* Your package might silently overwrite files installed at the symlink
  destination by other packages.
* If the package shipping the symlink decides to make the link point
  somewhere else (or turn it into a real directory), the files owned
  by your package "will be lost" somewhere in the filesystem.
* Depending on installation order the problematic path will be created
  either as a symlink or a directory: the package installed first will
  "win" and all others have "lost".
  Note that dpkg intentionally does not replace directories with
  symlinks and vice versa, see in particular the end of point 4 in
  
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase
  (Note: Adding Pre-Depends is *not* a solution.)

Please move the files shipped in your package to the "real" location.

>From the attached log (usually somewhere in the middle...):

3m15.9s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/drupal7/sites/default (drupal7-mod-civicrm) != 
/etc/drupal/7/sites/default (drupal7)
/usr/share/drupal7/sites -> /etc/drupal/7/sites
  /usr/share/drupal7/sites/default/civicrm (drupal7-mod-civicrm) != 
/etc/drupal/7/sites/default/civicrm (?)
/usr/share/drupal7/sites -> /etc/drupal/7/sites
  /usr/share/drupal7/sites/default/files (drupal7-mod-civicrm) != 
/etc/drupal/7/sites/default/files (drupal7)
/usr/share/drupal7/sites -> /etc/drupal/7/sites
  /usr/share/drupal7/sites/default/files/civicrm (drupal7-mod-civicrm) != 
/var/lib/drupal7/files/civicrm (?)
/usr/share/drupal7/sites -> /etc/drupal/7/sites
/etc/drupal/7/sites/default/files -> /var/lib/drupal7/files


cheers,

Andreas


drupal7-mod-civicrm_4.7.2+dfsg-2.log.gz
Description: application/gzip

Bug#808922: marked as done (pycurl uses deprecated find -perm +xxx syntax, please switch to find -perm /+++)

[Debian Bug Tracking System]

Your message dated Thu, 10 Mar 2016 11:17:13 -0500
with message-id <20160310111713.37b08...@subdivisions.wooz.org>
and subject line 
has caused the Debian Bug report #808922,
regarding pycurl uses deprecated find -perm +xxx syntax, please switch to find 
-perm /+++
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.)


-- 
808922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pycurl
Version: 7.19.5.3-1
User: ametz...@debian.org
Usertags: find-perm-plus

Hello,

the pycurl package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
pycurl_7.19.5.3-1/Makefile

chgrp $(CHMOD_VERBOSE) -R pycurl $(BUILD_WWW)
chmod $(CHMOD_VERBOSE) g+r `find $(BUILD_WWW) -perm +400 -print`
chmod $(CHMOD_VERBOSE) g+w `find $(BUILD_WWW) -perm +200 -print`
chmod $(CHMOD_VERBOSE) g+s `find $(BUILD_WWW) -type d -print`
##  chmod $(CHMOD_VERBOSE) g+rws `find $(BUILD_WWW) -type d -perm -770 
-print`

PathRank: 1.5498571, Final: 1.6265751
pycurl_7.19.5.3-1/Makefile

rsync-prepare:
chgrp $(CHMOD_VERBOSE) -R pycurl $(BUILD_WWW)
chmod $(CHMOD_VERBOSE) g+r `find $(BUILD_WWW) -perm +400 -print`
chmod $(CHMOD_VERBOSE) g+w `find $(BUILD_WWW) -perm +200 -print`
chmod $(CHMOD_VERBOSE) g+s `find $(BUILD_WWW) -type d -print`
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- End Message ---
--- Begin Message ---
This nmu was uploaded and the diff apply to vcs.


pgpp8pUXYiuDL.pgp
Description: OpenPGP digital signature
--- End Message ---

Processed: severity of 816294 is important

[Debian Bug Tracking System]

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

> severity 816294 important
Bug #816294 [slapd] slapd segfault on update dbconfig
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#817814: php-pear: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: php-pear
Version: 1:1.10.1+submodules+notgz-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  testing -> sid

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

3m15.9s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/php-pear/Archive_Tar (php-pear) != 
/usr/share/doc/php5-common/Archive_Tar (?)
/usr/share/doc/php-pear -> php5-common
  /usr/share/doc/php-pear/Archive_Tar/docs (php-pear) != 
/usr/share/doc/php5-common/Archive_Tar/docs (?)
/usr/share/doc/php-pear -> php5-common
  /usr/share/doc/php-pear/Archive_Tar/docs/Archive_Tar.txt.gz (php-pear) != 
/usr/share/doc/php5-common/Archive_Tar/docs/Archive_Tar.txt.gz (?)
/usr/share/doc/php-pear -> php5-common
  /usr/share/doc/php-pear/Archive_Tar_package.xml.gz (php-pear) != 
/usr/share/doc/php5-common/Archive_Tar_package.xml.gz (?)
/usr/share/doc/php-pear -> php5-common
  /usr/share/doc/php-pear/Console_Getopt_package.xml.gz (php-pear) != 
/usr/share/doc/php5-common/Console_Getopt_package.xml.gz (?)
/usr/share/doc/php-pear -> php5-common
  /usr/share/doc/php-pear/PEAR (php-pear) != /usr/share/doc/php5-common/PEAR (?)
/usr/share/doc/php-pear -> php5-common
  /usr/share/doc/php-pear/PEAR/README.rst (php-pear) != 
/usr/share/doc/php5-common/PEAR/README.rst (?)
/usr/share/doc/php-pear -> php5-common
  /usr/share/doc/php-pear/PEAR_package2.xml.gz (php-pear) != 
/usr/share/doc/php5-common/PEAR_package2.xml.gz (?)
/usr/share/doc/php-pear -> php5-common
  /usr/share/doc/php-pear/Structures_Graph (php-pear) != 
/usr/share/doc/php5-common/Structures_Graph (?)
/usr/share/doc/php-pear -> php5-common
  /usr/share/doc/php-pear/Structures_Graph/docs (php-pear) != 
/usr/share/doc/php5-common/Structures_Graph/docs (?)
/usr/share/doc/php-pear -> php5-common
  /usr/share/doc/php-pear/Structures_Graph/docs/tutorials (php-pear) != 
/usr/share/doc/php5-common/Structures_Graph/docs/tutorials (?)
/usr/share/doc/php-pear -> php5-common
  /usr/share/doc/php-pear/Structures_Graph/docs/tutorials/Structures_Graph 
(php-pear) != 
/usr/share/doc/php5-common/Structures_Graph/docs/tutorials/Structures_Graph (?)
/usr/share/doc/php-pear -> php5-common
  
/usr/share/doc/php-pear/Structures_Graph/docs/tutorials/Structures_Graph/Structures_Graph.pkg
 (php-pear) != 
/usr/share/doc/php5-common/Structures_Graph/docs/tutorials/Structures_Graph/Structures_Graph.pkg
 (?)
/usr/share/doc/php-pear -> php5-common
  /usr/share/doc/php-pear/Structures_Graph_package.xml.gz (php-pear) != 
/usr/share/doc/php5-common/Structures_Graph_package.xml.gz (?)
/usr/share/doc/php-pear -> php5-common
  /usr/share/doc/php-pear/XML_Util (php-pear) != 
/usr/share/doc/php5-common/XML_Util (?)
/usr/share/doc/php-pear -> php5-common
  /usr/share/doc/php-pear/XML_Util/examples (php-pear) != 
/usr/share/doc/php5-common/XML_Util/examples (?)
/usr/share/doc/php-pear -> php5-common
  /usr/share/doc/php-pear/XML_Util/examples/example.php.gz (php-pear) != 
/usr/share/doc/php5-common/XML_Util/examples/example.php.gz (?)
/usr/share/doc/php-pear -> php5-common
  /usr/share/doc/php-pear/XML_Util/examples/example2.php.gz (php-pear) != 
/usr/share/doc/php5-common/XML_Util/examples/example2.php.gz (?)
/usr/share/doc/php-pear -> php5-common
  /usr/share/doc/php-pear/XML_Util_package.xml.gz (php-pear) != 
/usr/share/doc/php5-common/XML_Util_package.xml.gz (?)
/usr/share/doc/php-pear -> php5-common
  /usr/share/doc/php-pear/changelog.Debian.gz 

Processed: libimage-transport0d: fails to upgrade from 'testing' - trying to overwrite /usr/share/image_transport/default_plugins.xml

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + ros-desktop-full
Bug #817813 [libimage-transport0d] libimage-transport0d: fails to upgrade from 
'testing' - trying to overwrite /usr/share/image_transport/default_plugins.xml
Added indication that 817813 affects ros-desktop-full

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

Bug#817813: libimage-transport0d: fails to upgrade from 'testing' - trying to overwrite /usr/share/image_transport/default_plugins.xml

[Andreas Beckmann]

Package: libimage-transport0d
Version: 1.11.10-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + ros-desktop-full

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...):

  Preparing to unpack .../libimage-transport0d_1.11.10-3_amd64.deb ...
  Unpacking libimage-transport0d:amd64 (1.11.10-3) over (1.11.10-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libimage-transport0d_1.11.10-3_amd64.deb (--unpack):
   trying to overwrite '/usr/share/image_transport/default_plugins.xml', which 
is also in package image-transport-tools 1.11.10-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


cheers,

Andreas


ros-desktop-full_1.5.log.gz
Description: application/gzip

Processed: notfound 812809 in yard/0.8.7.6+git20160220-2

[Debian Bug Tracking System]

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

> notfound 812809 yard/0.8.7.6+git20160220-2
Bug #812809 {Done: Cédric Boutillier } [ruby-appraiser,yard] 
yard and ruby-appraiser: error when trying to install together
Ignoring request to alter found versions of bug #812809 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#817808: php-kolab: postrm is buggy, breaks upgrades

[Andreas Beckmann]

Package: php-kolab
Version: 0.6.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid'.
It installed fine in 'sid', then the upgrade to 'experimental' fails.

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

  Preparing to unpack .../php-kolab_1.0.2-1_amd64.deb ...
  Unpacking php-kolab (1.0.2-1) over (0.6.0-2) ...
  /var/lib/dpkg/info/php-kolab.postrm: 11: local: 1.0.2-1: bad variable name
  dpkg: warning: subprocess old post-removal script returned error exit status 2
  dpkg: trying script from the new package instead ...
  /var/lib/dpkg/tmp.ci/postrm: 11: local: 0.6.0-2: bad variable name
  dpkg: error processing archive 
/var/cache/apt/archives/php-kolab_1.0.2-1_amd64.deb (--unpack):
   subprocess new post-removal script returned error exit status 2
  /var/lib/dpkg/tmp.ci/postrm: 11: local: 0.6.0-2: bad variable name
  dpkg: error while cleaning up:
   subprocess new post-removal script returned error exit status 2
  Processing triggers for libc-bin (2.21-9) ...
  Processing triggers for systemd (229-2) ...
  Processing triggers for fontconfig (2.11.0-6.3) ...
  Processing triggers for udev (229-2) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/php-kolab_1.0.2-1_amd64.deb

There seemes to be some quoting missing quoting ...

remove_module () {
local step=$1 module=$2 inifile=$2.ini package=$3 args=$4
...
}

remove_module $1 kolab php-kolab "$*"
remove_module $1 kolabdummy php-kolab "$*"


Looks like you wanted 

remove_module $1 kolab php-kolab "$@"
remove_module $1 kolabdummy php-kolab "$@"


cheers,

Andreas


php-kolab_1.0.2-1.log.gz
Description: application/gzip

Bug#817154: marked as done (libnih1: uninstallable in unstable)

[Debian Bug Tracking System]

Your message dated Thu, 10 Mar 2016 22:12:59 +0800
with message-id <56e180eb.8040...@gmail.com>
and subject line Re: Bug#817154: lxc: Can not install lxc 1.1.5-1
has caused the Debian Bug report #817154,
regarding libnih1: uninstallable in unstable
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.)


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

Dear Maintainer,

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


   sudo apt-get install lxc
   Reading package lists... Done
   Building dependency tree   
   Reading state information... Done
   Some packages could not be installed. This may mean that you have
   requested an impossible situation or if you are using the unstable
   distribution that some required packages have not yet been created
   or been moved out of Incoming.
   The following information may help to resolve the situation:

   The following packages have unmet dependencies:
   lxc : Depends: liblxc1 (= 1:1.1.5-1) but it is not going to be
   installed
   Recommends: cgmanager but it is not going to be installed
   E: Unable to correct problems, you have held broken packages.


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


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

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

On Tuesday, March 08, 2016 10:27 PM, john wrote:

Package: lxc
Version: 1.1.5-1
Severity: normal

Dear Maintainer,

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


sudo apt-get install lxc
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
lxc : Depends: liblxc1 (= 1:1.1.5-1) but it is not going to be
installed
Recommends: cgmanager but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


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


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

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

fixed--- End Message ---

Bug#817799: marked as done (libotr5: Exploitable integer overflow vulnerability (CVE-2016-2851))

[Debian Bug Tracking System]

Your message dated Thu, 10 Mar 2016 15:07:51 +0100
with message-id <20160310140751.ga24...@lorien.valinor.li>
and subject line Re: Bug#817799: libotr5: Exploitable integer overflow 
vulnerability (CVE-2016-2851)
has caused the Debian Bug report #817799,
regarding libotr5: Exploitable integer overflow vulnerability (CVE-2016-2851)
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.)


-- 
817799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libotr5
Version: 4.1.0-7
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

the libotr versions prior to 4.1.1 contain an integer overflow vulnerability.
This can cause buffer overflow that could lead to code execution. The
vulnerability has been assigned the CVE-2016-2851.

You can find more information here:

https://www.x41-dsec.de/lab/advisories/x41-2016-001-libotr/

Sincerely,

Michail Bachmann



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (300, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.4.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=C.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 libotr5 depends on:
ii  libc62.22-2
ii  libgcrypt20  1.6.5-2

libotr5 recommends no packages.

Versions of packages libotr5 suggests:
pn  libotr5-bin  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libotr
Source-Version: 4.1.1-1

Hi,

On Thu, Mar 10, 2016 at 02:49:20PM +0100, Michail Bachmann wrote:
> Package: libotr5
> Version: 4.1.0-7
> Severity: grave
> Tags: security
> Justification: user security hole
> 
> Dear Maintainer,
> 
> the libotr versions prior to 4.1.1 contain an integer overflow vulnerability.
> This can cause buffer overflow that could lead to code execution. The
> vulnerability has been assigned the CVE-2016-2851.
> 
> You can find more information here:
> 
> https://www.x41-dsec.de/lab/advisories/x41-2016-001-libotr/

Thanks. The fix is already on the way, cf.
https://tracker.debian.org/news/754059 thus fixing the bugreport with
that version.

Regards,
Salvatore--- End Message ---

Processed: found 817799 in 3.2.1-1, fixed 817799 in 3.2.1-1+deb7u2, fixed 817799 in 4.1.0-2+deb8u1

[Debian Bug Tracking System]

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

> found 817799 3.2.1-1
Bug #817799 {Done: Salvatore Bonaccorso } [libotr5] libotr5: 
Exploitable integer overflow vulnerability (CVE-2016-2851)
There is no source info for the package 'libotr5' at version '3.2.1-1' with 
architecture ''
Unable to make a source version for version '3.2.1-1'
Marked as found in versions 3.2.1-1.
> fixed 817799 3.2.1-1+deb7u2
Bug #817799 {Done: Salvatore Bonaccorso } [libotr5] libotr5: 
Exploitable integer overflow vulnerability (CVE-2016-2851)
There is no source info for the package 'libotr5' at version '3.2.1-1+deb7u2' 
with architecture ''
Unable to make a source version for version '3.2.1-1+deb7u2'
Marked as fixed in versions 3.2.1-1+deb7u2.
> fixed 817799 4.1.0-2+deb8u1
Bug #817799 {Done: Salvatore Bonaccorso } [libotr5] libotr5: 
Exploitable integer overflow vulnerability (CVE-2016-2851)
Marked as fixed in versions libotr/4.1.0-2+deb8u1.
> thanks
Stopping processing here.

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

Bug#817799: libotr5: Exploitable integer overflow vulnerability (CVE-2016-2851)

[Michail Bachmann]

Package: libotr5
Version: 4.1.0-7
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

the libotr versions prior to 4.1.1 contain an integer overflow vulnerability.
This can cause buffer overflow that could lead to code execution. The
vulnerability has been assigned the CVE-2016-2851.

You can find more information here:

https://www.x41-dsec.de/lab/advisories/x41-2016-001-libotr/

Sincerely,

Michail Bachmann



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (300, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.4.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=C.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 libotr5 depends on:
ii  libc62.22-2
ii  libgcrypt20  1.6.5-2

libotr5 recommends no packages.

Versions of packages libotr5 suggests:
pn  libotr5-bin  

-- no debconf information

Bug#817795: sysvinit-utils - Contains pre-depends loop

[Petter Reinholdtsen]

[Bastian Blank]
> In sysvinit-utils or somewhere of it's dependency chain is a
> pre-dependency/conflict loop, which apt is unable to break.  This breaks
> the upgrade from Jessie.

Could this be caused by util-linux?  It modified its dependencies
related to initscripts:

util-linux (2.27.1-4) unstable; urgency=medium

  * Drop initscripts dependency now that update-rc.d no longer
requires it to process init scripts with LSB header dependencies.
- note that it's still likely to be installed (even under systemd)
  since it's priority is required, it's just that util-linux no longer
  needs to require it to be around.
  * Add dependency on init-system-helpers (>= 1.29~) which contains
the previously mentioned update-rc.d fix.
- this can be dropped once init-system-helpers is always >= 1.29~.
  * Drop lsb-base dependency
- strictly speaking we should have it since hwclock.sh uses
  lsb-base, but initscripts will pull it in for us anyway under
  sysvinit(-core) so this dependency makes no practical gain.
  Dropping it avoids pulling it in when we don't need it (eg. under
  systemd-sysv where hwclock.sh is masked by the systemd package).
  * Add systemd-sysv as an alternative to tzdata dependency.
- tzdata was according to this changelog added for the benefit of
  the hwclock.sh init script. (Not sure it's required.)
  It's among the top size of debootstrap --variant=minbase packages
  so might be useful to make it uninstallable on minimal containers,
  which this change should accomplish (under systemd-sysv atleast).
  * Finally move sysvinit-utils back to Breaks instead of Depends
- now that initscript dependency is dropped, the issue with cyclic
  dependency should be no more and we can properly describe the
  relation.
  * Add debian/patches/build-sys-use-PKG_CONFIG.patch
- cherry-picked from upstream git, fixes crossbuilding (Closes: #811546)

 -- Andreas Henriksson   Thu, 03 Mar 2016 14:30:19 +0100

-- 
Happy hacking
Petter Reinholdtsen

Bug#817795: sysvinit-utils - Contains pre-depends loop

[Bastian Blank]

Package: sysvinit-utils
Version: 2.88dsf-59.3
Severity: grave

In sysvinit-utils or somewhere of it's dependency chain is a
pre-dependency/conflict loop, which apt is unable to break.  This breaks
the upgrade from Jessie.

| # apt install sysvinit-utils
| Reading package lists... Done
| Building dependency tree   
| Reading state information... Done
| The following additional packages will be installed:
|   init-system-helpers libfdisk1 libncurses5 libncursesw5 libsmartcols1 
libtinfo5 util-linux
| Suggested packages:
|   bootlogd sash dosfstools kbd | console-tools util-linux-locales
| The following NEW packages will be installed:
|   libfdisk1
| The following packages will be upgraded:
|   init-system-helpers libncurses5 libncursesw5 libsmartcols1 libtinfo5 
sysvinit-utils util-linux
| 7 upgraded, 1 newly installed, 0 to remove and 215 not upgraded.
| Need to get 0 B/1.816 kB of archives.
| After this operation, 882 kB of additional disk space will be used.
| Do you want to continue? [Y/n] 
| E: This installation run will require temporarily removing the essential 
package sysvinit-utils:amd64 due to a Conflicts/Pre-Depends loop. This is often 
bad, but if you really want to do it, activate the APT::Force-LoopBreak option.

Bastian

-- 
Bastian Blank
Berater
Telefon: +49 2161 / 4643-194
E-Mail: bastian.bl...@credativ.de
credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209
Hohenzollernstr. 133, 41061 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer

Bug#817794: qtsensors-opensource-src: B-D on obsolete package libqt5xcbqpa5

[Andreas Beckmann]

Source: qtsensors-opensource-src
Version: 5.5.1-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

your package Build-Depends on the obsolete transitional package
libqt5xcbqpa5 which is no longer built by qtbase-opensource-src. Please
switch to libqt5gui5.


Andreas

Bug#812794: marked as done (Build-Depends not installable in testing)

[Debian Bug Tracking System]

Your message dated Thu, 10 Mar 2016 13:57:36 +0100
with message-id <20160310125736.ga12...@entropy.proba.jussieu.fr>
and subject line ruby-gsl now in testing
has caused the Debian Bug report #812794,
regarding Build-Depends not installable in testing
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.)


-- 
812794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812794
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hi,

ruby-integration Build-Depends on ruby-gsl, which is not in testing.
(Also nobody seems to be working on fixing ruby-gsl for it to reenter
testing.)

Thanks,
Christian
--- End Message ---
--- Begin Message ---
Hi!

ruby-gsl now made its way back to testing. The packages ruby-integration
and ruby-distribution can be built from testing. I am therefore closing
these bugs.

Thanks!

Cédric


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

Bug#812793: marked as done (Build-Depends not installable in testing)

[Debian Bug Tracking System]

Your message dated Thu, 10 Mar 2016 13:57:36 +0100
with message-id <20160310125736.ga12...@entropy.proba.jussieu.fr>
and subject line ruby-gsl now in testing
has caused the Debian Bug report #812793,
regarding Build-Depends not installable in testing
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.)


-- 
812793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hi,

ruby-distribution Build-Depends on ruby-gsl, which is not in testing.
(Also nobody seems to be working on fixing ruby-gsl for it to reenter
testing.)

Thanks,
Christian
--- End Message ---
--- Begin Message ---
Hi!

ruby-gsl now made its way back to testing. The packages ruby-integration
and ruby-distribution can be built from testing. I am therefore closing
these bugs.

Thanks!

Cédric


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

Bug#817793: qt3d-opensource-src: B-D on obsolete package libqt5xcbqpa5

[Andreas Beckmann]

Source: qt3d-opensource-src
Version: 5.5.1-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

your package Build-Depends on the obsolete transitional package
libqt5xcbqpa5 which is no longer built by qtbase-opensource-src. Please
switch to libqt5gui5.


Andreas

Bug#815292: marked as done (libreoffice: FTBFS on i386: test failure: testFlipAndRotateCustomShape::Import_Export_Import)

[Debian Bug Tracking System]

Your message dated Thu, 10 Mar 2016 12:45:56 +
with message-id 
and subject line Bug#815292: fixed in libreoffice 1:5.1.1-1
has caused the Debian Bug report #815292,
regarding libreoffice: FTBFS on i386: test failure: 
testFlipAndRotateCustomShape::Import_Export_Import
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.)


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

Hi,

libreoffice FTBFS on i386:

https://buildd.debian.org/status/fetch.php?pkg=libreoffice=i386=1%3A5.1.1~rc1-1=1455588828

[...]
FDO74774.docx,526
File tested,Execution Time (ms)
FDO74774.docx,1483
xmltesttools.cxx:99:Assertion
Test name: testFlipAndRotateCustomShape::Import_Export_Import
equality assertion failed
- Expected: 2351
- Actual  : 2350
- In , attribute 'x' of 
'//a:custGeom/a:pathLst/a:path/a:lnTo[1]/a:pt' incorrect value.

Failures !!!
Run: 104   Failure total: 1   Failures: 1   Errors: 0

Error: a unit test failed, please do one of:
make CppunitTest_sw_ooxmlexport7 CPPUNITTRACE="gdb --args"
# for interactive debugging on Linux
make CppunitTest_sw_ooxmlexport7 VALGRIND=memcheck
# for memory checking
make CppunitTest_sw_ooxmlexport7 DEBUGCPPUNIT=TRUE
# for exception catching

/«PKGBUILDDIR»/solenv/gbuild/CppunitTest.mk:90: recipe for target 
'/«PKGBUILDDIR»/workdir/CppunitTest/sw_ooxmlexport7.test' failed
make[3]: *** [/«PKGBUILDDIR»/workdir/CppunitTest/sw_ooxmlexport7.test] Error 1
make[3]: Leaving directory '/«PKGBUILDDIR»'
Makefile:244: recipe for target 'build' failed
make[2]: *** [build] Error 2


Andreas
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 1:5.1.1-1

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libreoffice package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Mar 2016 20:31:50 +0100
Source: libreoffice
Binary: libreoffice libreoffice-l10n-za libreoffice-l10n-in libreoffice-core 
libreoffice-common libreoffice-java-common libreoffice-writer libreoffice-calc 
libreoffice-impress libreoffice-draw libreoffice-math libreoffice-base-core 
libreoffice-base libreoffice-style-oxygen libreoffice-style-breeze 
libreoffice-style-tango libreoffice-style-hicontrast libreoffice-style-sifr 
libreoffice-style-galaxy libreoffice-gtk libreoffice-gnome python3-uno 
libreoffice-officebean libreoffice-script-provider-python 
libreoffice-script-provider-bsh libreoffice-script-provider-js 
libreoffice-pdfimport libreoffice-avmedia-backend-gstreamer 
libreoffice-avmedia-backend-vlc libreoffice-sdbc-firebird 
libreoffice-sdbc-hsqldb libreoffice-base-drivers libreoffice-l10n-af 
libreoffice-l10n-am libreoffice-l10n-ar libreoffice-l10n-as 
libreoffice-l10n-ast libreoffice-l10n-be libreoffice-l10n-bg 
libreoffice-l10n-bn libreoffice-l10n-br libreoffice-l10n-bs libreoffice-l10n-ca 
libreoffice-l10n-cs
 libreoffice-l10n-cy libreoffice-l10n-da libreoffice-l10n-de 
libreoffice-l10n-dz libreoffice-l10n-el libreoffice-l10n-en-gb 
libreoffice-l10n-en-za libreoffice-l10n-eo libreoffice-l10n-es 
libreoffice-l10n-et libreoffice-l10n-eu libreoffice-l10n-fa libreoffice-l10n-fi 
libreoffice-l10n-fr libreoffice-l10n-ga libreoffice-l10n-gd libreoffice-l10n-gl 
libreoffice-l10n-gu libreoffice-l10n-gug libreoffice-l10n-he 
libreoffice-l10n-hi libreoffice-l10n-hr libreoffice-l10n-hu libreoffice-l10n-id 
libreoffice-l10n-is libreoffice-l10n-it libreoffice-l10n-ja libreoffice-l10n-ka 
libreoffice-l10n-kk libreoffice-l10n-km libreoffice-l10n-ko 
libreoffice-l10n-kmr libreoffice-l10n-lt libreoffice-l10n-lv 
libreoffice-l10n-mk libreoffice-l10n-mn libreoffice-l10n-ml libreoffice-l10n-mr 
libreoffice-l10n-nb libreoffice-l10n-ne libreoffice-l10n-nl libreoffice-l10n-nn 

Bug#812852: Vigra auf ppc64el -- continues a little bit

[Ullrich Koethe]

I upgraded the RC to use the newest LZ4 version which has significantly 
better byte order handling. Hopefully, this fixes the problem. One could 
also add a cmake option to use a pre-installed LZ4 library when 
available and just fall-back to the internal version if not.


Best
Ulli

Bug#817233: ODP: Bug#817233: CVE-2016-1968

[Tomasz Buchert]

Hi guys,
I'm out of town and cannot work on this. NMUs welcome. :D

Tomasz


Wysłane z telefonu Samsung

Salvatore Bonaccorso  pisze:

null

Bug#812852: Vigra auf ppc64el -- continues a little bit

[Ullrich Koethe]

* Remove all occurencies of threading::memory_order* in multi_array_chunked.hxx 
(or equivalently, replace them with threading::memory_order_seq_cst). This will 
force all atomic accesses to use sequentially consistent ordering, the most 
strict possibility.


That worked out ... much thanks!


- First of all, there was a little mistake, that was the wrong log file. 
Unfortunately, the
   problem with test_multiarray_chunked resp. multi_array_chunked.hxx on 
ppc64el/le remains also
   with changing `memory_order_release/acquire` to `memory_order_seq_cst`.


bummer!


I'm further experimenting with VIGRA_SINGLE_THREADED but no breakthrough so far 
...


Looking at the log again, it occured to me that the error might not be 
related to multi-threading at all. Possibly, all failing tests are on 
ChunkedArrayCompressed with T being float and double. Can you please 
check this? If this is true, the error might go away be changing the 
compression algorithm in test_chunked.cxx line 121 from LZ4 into 
ZLIB_FAST or NO_COMPRESSION. If this works, there might be a byte order 
problem in the LZ4 algorithm. Endianess is decided in 
/src/impex/lz4.c lines 65 to 79. Please check if the correct 
endianess for your platform is retrieved there, and possibly propose a 
fix if it isn't.


Best
Ulli

Bug#814765: marked as done (python-pysam: FTBFS: samtools index: "ex2_truncated.bam" is corrupted or unsorted)

[Debian Bug Tracking System]

Your message dated Thu, 10 Mar 2016 10:21:55 +
with message-id 
and subject line Bug#814765: fixed in python-pysam 0.9.0+ds-1
has caused the Debian Bug report #814765,
regarding python-pysam: FTBFS: samtools index: "ex2_truncated.bam" is corrupted 
or unsorted
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.)


-- 
814765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pysam
Version: 0.8.4+ds-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,

python-pysam fails to build from source in unstable/amd64:

  [..]

  samtools index softclip.bam
  samtools index tag_bug.bam
  samtools index ex10.bam
  samtools index example_empty_header.bam
  samtools index test_unaligned.bam
  samtools index ex9_fail.bam
  samtools index issue100.bam
  samtools index ex5.bam
  samtools index ex6.bam
  samtools index rg_with_tab.bam
  samtools index ex9_nofail.bam
  samtools index example_btag.bam
  samtools index example_unmapped_reads_no_sq.bam
  samtools index ex4.bam
  samtools index example_user_header.bam
  samtools index ex8.bam
  samtools index ex3.bam
  samtools view -bC -T ex1.fa ex1.sam > ex1.cram
  samtools view -bC -T ex1.fa ex2.sam > ex2.cram
  samtools view -bC -T ex1.fa ex3.sam > ex3.cram
  samtools index ex1.cram
  samtools index ex2.cram
  samtools index ex3.cram
  cp ex1.bam example_bai.bam
  samtools index example_bai.bam
  mv example_bai.bam.bai example_bai.bai
  head -c 124000 ex2.bam > ex2_truncated.bam
  samtools index ex2_truncated.bam
  [W::bam_hdr_read] EOF marker is absent. The input is probably truncated.
  samtools index: "ex2_truncated.bam" is corrupted or unsorted
  Makefile:48: recipe for target 'ex2_truncated.bam.bai' failed
  make[2]: *** [ex2_truncated.bam.bai] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160215090723.RznKM9ufGc/python-pysam-0.8.4+ds/tests/pysam_data'
  debian/rules:26: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160215090723.RznKM9ufGc/python-pysam-0.8.4+ds'
  debian/rules:20: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


python-pysam.0.8.4+ds-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-pysam
Source-Version: 0.9.0+ds-1

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

Debian distribution maintenance software
pp.
Afif Elghraoui  (supplier of updated python-pysam 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, 09 Mar 2016 23:43:59 -0800
Source: python-pysam
Binary: python-pysam python3-pysam python-pysam-tests
Architecture: source
Version: 0.9.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Afif Elghraoui 
Description:
 python-pysam - interface for the SAM/BAM sequence alignment and mapping format 
(
 python-pysam-tests - interface for the SAM/BAM sequence alignment and mapping 
format (
 python3-pysam - interface for the SAM/BAM sequence alignment and mapping 
format (
Closes: 814765
Changes:
 python-pysam (0.9.0+ds-1) unstable; urgency=medium
 .
   * Add filenamemangle to d/watch and space out content
   * Imported Upstream version 0.9.0+ds (Closes: #814765)
   * Bump htslib and samtools minimum versions
   * Update policy statndards-version to 3.9.7
   * Use encrypted protocols for Vcs URLs in d/control
   * Use readthedocs page as pysam's homepage
   * Update packaging for external htslib link
   * Refresh patches
   * 

Bug#817188: marked as done (libbamtools-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/libbamtools-dev/html/functions_v.html)

[Debian Bug Tracking System]

Your message dated Thu, 10 Mar 2016 10:19:42 +
with message-id 
and subject line Bug#817188: fixed in bamtools 2.4.0+dfsg-6
has caused the Debian Bug report #817188,
regarding libbamtools-doc: fails to upgrade from 'testing' - trying to 
overwrite /usr/share/doc/libbamtools-dev/html/functions_v.html
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.)


-- 
817188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbamtools-doc
Version: 2.4.0+dfsg-4
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 libbamtools-doc.
  Preparing to unpack .../libbamtools-doc_2.4.0+dfsg-4_all.deb ...
  Unpacking libbamtools-doc (2.4.0+dfsg-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libbamtools-doc_2.4.0+dfsg-4_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libbamtools-dev/html/functions_v.html', 
which is also in package libbamtools-dev 2.4.0+dfsg-3+b1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libbamtools-doc_2.4.0+dfsg-4_all.deb


cheers,

Andreas


libbamtools-dev=2.4.0+dfsg-3+b1_libbamtools-doc=2.4.0+dfsg-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: bamtools
Source-Version: 2.4.0+dfsg-6

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

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

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated bamtools 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: Thu, 10 Mar 2016 01:38:21 -0800
Source: bamtools
Binary: bamtools libbamtools-dev libbamtools2.4.0 libbamtools-doc
Architecture: source
Version: 2.4.0+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Description:
 bamtools   - toolkit for manipulating BAM (genome alignment) files
 libbamtools-dev - C++ API for manipulating BAM (genome alignment) files
 libbamtools-doc - docs for dynamic library for manipulating BAM (genome 
alignment)
 libbamtools2.4.0 - dynamic library for manipulating BAM (genome alignment) 
files
Closes: 817188
Changes:
 bamtools (2.4.0+dfsg-6) unstable; urgency=medium
 .
   * Whoops, forgot the '+dfsg' in my fix for the movement of the development
 docs into their own -doc package. Thanks go to Andreas Beckmann
  for his patience and help. (Closes: 817188)
Checksums-Sha1:
 1ac5cc6a50cb47d1b21d7473782974ecfaec368e 2318 bamtools_2.4.0+dfsg-6.dsc
 975087cf228f8d02ab75b60b8670331777b47f66 11784 
bamtools_2.4.0+dfsg-6.debian.tar.xz
Checksums-Sha256:
 2816be9758dd00638b6d67e7b1d0ba356fb19f36431d5d8017c54b639e2259e2 2318 
bamtools_2.4.0+dfsg-6.dsc
 77be240628229c6ab790da5f515848cd5455211c63dbeaf5fa3d6619c2983311 11784 
bamtools_2.4.0+dfsg-6.debian.tar.xz
Files:
 1e1dc193cfc9ef9ab63d969ed9b0309a 2318 science extra bamtools_2.4.0+dfsg-6.dsc
 d41adf6d69938ab62859ff07d3fe2181 11784 science extra 
bamtools_2.4.0+dfsg-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJW4UDWAAoJEDwmdj9sZ+biM7kQALFiABu6raO1/PcuYGkviBua
PDDAxoDv1fAfN6pMLZvtRKq6fl6DG6Whmj24DieXaSFvcVNmmjcQXPyUrIcShfia
o8doRxkSRBfEIUAyqUptYusRs3ElU9kkGa0I+Dm7Laa2/EydJBdZMFbrz/YSIgdv
bMa4Kbb81+mx8cCdTpnyQaqzWzxsEHS0fEGu7iTMWBy5bWMgYP+EKIMErVkQzpn1
N1L8VcByL02gvQQ+pfE2pq0/L4Kml7JY6AjbPnIRykP9FHI+ndIdaoJghAhnYb0J
z0JL7q5vfg0XDJmFyOvKHMhrS7gKgQNi/LYWIFckg5zmKdyQtrsYr3LMdOsaE2fN

Bug#817275: marked as done (acme-tiny: missing dependency on python3-pkg-resources (ImportError: No module named 'pkg_resources'))

[Debian Bug Tracking System]

Your message dated Thu, 10 Mar 2016 10:19:36 +
with message-id 
and subject line Bug#817275: fixed in acme-tiny 20151229-3
has caused the Debian Bug report #817275,
regarding acme-tiny: missing dependency on python3-pkg-resources (ImportError: 
No module named 'pkg_resources')
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.)


-- 
817275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: acme-tiny
Version: 20151229-2
Severity: serious

Hi,

acme-tiny only depends on openssl and python3, but actually seems to
need at least one more package: If python3-pkg-resources is not
installed, acme-tiny bails out as follows:

$ acme-tiny
Traceback (most recent call last):
  File "/usr/bin/acme-tiny", line 5, in 
from pkg_resources import load_entry_point
ImportError: No module named 'pkg_resources'
$

Installing python3-pkg-resources solves the issue.

I noticed this issue initially in my acme-tiny backport to Debian 7
Wheezy with Python 3.2, but could also reproduce it on Debian Sid with
Python 3.5, so it seems independent of the used Python version.

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

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

Versions of packages acme-tiny depends on:
ii  openssl  1.0.2g-1
pn  python3:any  

acme-tiny recommends no packages.

acme-tiny suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: acme-tiny
Source-Version: 20151229-3

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

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

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

Debian distribution maintenance software
pp.
Jeremías Casteglione  (supplier of updated acme-tiny 
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, 09 Mar 2016 21:53:02 +
Source: acme-tiny
Binary: acme-tiny
Architecture: source all
Version: 20151229-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Let's Encrypt 
Changed-By: Jeremías Casteglione 
Description:
 acme-tiny  - letsencrypt tiny Python client
Closes: 817275
Changes:
 acme-tiny (20151229-3) unstable; urgency=medium
 .
   * install depends on python3-pkg-resources (Closes: #817275)
   * fix manpage typo: ownership vs ownsership (Thanks Axel Beckert)
Checksums-Sha1:
 3e0fbc1cbeb4eb85a49d0bd6831b37906974cd30 2110 acme-tiny_20151229-3.dsc
 5897e9b98ef432d45114475126e9e2a6c619ae44 7832 
acme-tiny_20151229-3.debian.tar.xz
 46213f698f11cc1c6c5e13fb3ab4783752ba1437 13068 acme-tiny_20151229-3_all.deb
Checksums-Sha256:
 b87d2ccaa26d2a4dce4da427658b77040f77a31353777b09b429c075c96ebd9e 2110 
acme-tiny_20151229-3.dsc
 047a7c596f05a16f7d5e7540cc58c8532e0addba3c09b9cb66130dc40f6d8018 7832 
acme-tiny_20151229-3.debian.tar.xz
 9d0fb8be2736e160c881f31a0dd3d88a1b215fa3cc3da0cd749d8db83ba916a1 13068 
acme-tiny_20151229-3_all.deb
Files:
 1e445ac79abd68aee0c33714e7d93720 2110 utils optional acme-tiny_20151229-3.dsc
 f0d240c3b5900ea29b450c5b0663d93b 7832 utils optional 
acme-tiny_20151229-3.debian.tar.xz
 f52aeaee77f1b1a1dcc695ec44720cfc 13068 utils optional 
acme-tiny_20151229-3_all.deb

-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJW4Sn9XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4QzQ3MEIyQTBCMzE1NjhFMTEwRDQzMjUx
NjI4MUYyRTAwN0M5OEQxAAoJEBYoHy4AfJjRWhQP+we6Kopt59P71YyubFeE6VPD
PhCqzpb/ekGYfiOVydja/Vk+8Vm24j0iZrQVRPJwJwBuH2Ma/XLUfKonwFnR1Nh1
mKWI3KGp+5tz270nsfoK5TkmVXe6hGKEZ0HHQ0D4tVxX1gMwFhx4XMcXXoAlnImK
oK0b2DEg7Js+SY2Qvh52z/JbfqkFue/GiQp3YM9Tb0JpL+216sUHcAihkzpf4WVA

Bug#817139: [Pkg-sass-devel] Bug#817139: sassc: trying to overwrite '/usr/share/man/man1/sassc.1.gz', which is also in package pysassc 0.9.3-1

[Frederic Bonnard]

On Wed, 09 Mar 2016 17:27:35 +0100, Jonas Smedegaard  wrote:
> 
> Hi Frederic,
> 
> Quoting Frederic Bonnard (2016-03-09 15:36:53)
> >> The name "sassc" means "Sass implemented in C".
> >>
> >> Since the package name "pysassc" seems to imply "sassc wrapper 
> >> implemented in Python", I believe the proper fix here is for pysassc 
> >> to not provide binary "sassc" but instead "pysassc".
> >
> > right
> >
> >> ...or simply drop the package pysassc, because there should be no 
> >> need for that wrapper on systems where the real sassc is available.
> >
> > sure ; but I'd prefer to let users choose.
> >
> > Actually one of the project I use, needed as a build-dep sassc from 
> > python-libsass, because as many python projects they drag build-deps 
> > with pip and don't bother with original C projects with native tools.
> 
> pip means sidestepping Debian packaging, and is therefore irrelevant for 
> Debian packaging.
> 
> 
> > And the latter has specific options also, different from the one from 
> > sassc package with is embarassing for dependant projects.
> 
> Varying options is a real pain, however.
> 
> 
> > I see 3 possibilities :
> > - we remove sassc from python-libsass but we'll have to do something 
> >   for projects using it as build-deps.
> > - we rename sassc in python-libsass pysassc, same point.
> >   In both last 2 points, we could see with upstream libsass-python if 
> >   they can do the same on python sassc script to prevent more deb/ 
> >   work to patch other projects depending in python sassc, but it's 
> >   unsure they'll follow.
> > - or I put in python-libsass's control an exclude with sassc
> > 
> > Last point would be the least work solution on all sides, and that'd 
> > be up to users to choose if they want the "real" sassc or the pythonic 
> > one. Any thoughts ?
> 
> If by last option you mean mark the package as conflicting with sassc, 
> then that is a bad approach, as that makes it impossible to use sassc 
> for some things and the Python flavor for other things - on same system.

Indeed, that is restrictive.

> I recommend option 2 (rename binary).  And I recommend to get in touch 
> with upstream and recommend them to do the same, to avoid confusion over 
> two implementations with same name having different options.
> 
> As _extension_ to option 2 - you could document in README.Debian for 
> your package how the local admin can locally register that binary as an 
> alternative to sassc.  I feel it is bad for the package to do so, 
> however, due to those varying options (unless it is a strict superset of 
> the options of sassc).  You could contact upstream and try convince them 
> to coordinate aligning options with sassc authors, and when aligned the 
> package could register as alternative.

Perfect, I'm going to talk to upstream libsass-python.
Thanks a lot Jonas for helping,

F.

Bug#812413: marked as done (cups-driver-gutenprint: transitional arch:all package uninstallable after binNMU due to strict versioned dependency)

[Debian Bug Tracking System]

Your message dated Wed, 09 Mar 2016 15:01:02 +0100
with message-id <1542837.qNFzgqpIa2@gyllingar>
and subject line Re: Bug#812413: cups-driver-gutenprint: transitional arch:all 
package uninstallable after binNMU due to strict versioned dependency
has caused the Debian Bug report #812413,
regarding cups-driver-gutenprint: transitional arch:all package uninstallable 
after binNMU due to strict versioned dependency
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.)


-- 
812413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cups-driver-gutenprint
Version: 5.2.10-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

The following packages have unmet dependencies:
 cups-driver-gutenprint : Depends: printer-driver-gutenprint (= 5.2.10-3) but 
5.2.10-3+b1 is to be installed

This is also a problem on jessie/s390x where the package got binNMUed
long ago.


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Version: 5.2.11~pre2-1

cups-driver-gutenprint was dropped from unstable in 5.2.11~pre2-1, so this is 
only a problem if stable needs a binNMU. Closing as not affecting current 
testing/unstable.

This doesn't seem important enough to warrant a stable update either…

Le samedi, 23 janvier 2016, 14.21:23 Andreas Beckmann a écrit :
> during a test with piuparts I noticed your package is no longer
> installable in sid:
> 
> The following packages have unmet dependencies:
>  cups-driver-gutenprint : Depends: printer-driver-gutenprint (= 5.2.10-3)
> but 5.2.10-3+b1 is to be installed
> 
> This is also a problem on jessie/s390x where the package got binNMUed
> long ago.

-- 
Cheers,
OdyX

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

Bug#816492: marked as done (galera-3: Galera fails to build with pbuilder for armhf (on amd64))

[Debian Bug Tracking System]

Your message dated Thu, 10 Mar 2016 10:29:53 +0200
with message-id 

and subject line Re: [debian-mysql] Bug#816492: Bug#816492: galera-3: Galera 
fails to build with pbuilder for armhf (on amd64)
has caused the Debian Bug report #816492,
regarding galera-3: Galera fails to build with pbuilder for armhf (on amd64)
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.)


-- 
816492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: galera-3
Version: 25.3.13-2
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

Failed to build Galera in pbuilder for armhf (Debian Jessie) on amd64.
I could successfully build Galera 2.3.6, however, I face problems building 
other versions. One of the problems is that all versions of Galera after 2.3.6 
and before 2.3.14 have the same debian/changelog file that refers to version 
2.3.6. The up-to-date version of this file is required, because it is used by 
the pbuilder to detect version of the package. So, in order to start a build 
(pass through the pbuilder's pre-build checks) I had to write the correct 
version into that file, e.g. 2.3.13-1 (quilt format) for Galera 2.3.13. After 
that the compilation of the Galera 2.3.13 finishes successfully, but the build 
process fails on builder unit tests (the last important lines of the build log):

g++ -o galera/tests/galera_check -Wl,-z,relro galera/tests/galera_check.o 
galera/tests/data_set_check.o galera/tests/key_set_check.o galera$
builder_unit_test(["galera/tests/galera_check.passed"], 
["galera/tests/galera_check"])
Running suite(s): DataSet
100%: Checks: 1, Failures: 0, Errors: 0
Running suite(s): KeySet
100%: Checks: 1, Failures: 0, Errors: 0
Running suite(s): WriteSet
100%: Checks: 2, Failures: 0, Errors: 0
Running suite(s): write_set
100%: Checks: 8, Failures: 0, Errors: 0
Running suite(s): trx_handle
100%: Checks: 2, Failures: 0, Errors: 0
Running suite(s): service_thd
100%: Checks: 3, Failures: 0, Errors: 0
Running suite(s): ist
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
100%: Checks: 6, Failures: 0, Errors: 0
Running suite(s): saved_state
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
33%: Checks: 3, Failures: 1, Errors: 1
galera/tests/saved_state_check.cpp:48:E:saved_state:test_unsafe:0: (after this 
point) Received signal 11 (Segmentation fault)
galera/tests/saved_state_check.cpp:155:F:saved_state:test_corrupt:0: Failure 
'uuid == WSREP_UUID_UNDEFINED' occured
Total tests failed: 2
scons: *** [galera/tests/galera_check.passed] Error 1
scons: building terminated because of errors.
debian/rules:28: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2

The log above was generated using qemu-user-static (1:2.1+dfsg-12+deb8u5a) - 
the default version in Debain Jessie. Then I upgraded this package to 
qemu-user-static (1:2.5+dfsg-4~bpo8+1) using jessie-backports repositories. The 
build in the newer environment gave similar results:

g++ -o galera/tests/galera_check -Wl,-z,relro galera/tests/galera_check.o 
galera/tests/data_set_check.o galera/tests/key_set_check.o galera$
builder_unit_test(["galera/tests/galera_check.passed"], 
["galera/tests/galera_check"])
Running suite(s): DataSet
100%: Checks: 1, Failures: 0, Errors: 0
Running suite(s): KeySet
100%: Checks: 1, Failures: 0, Errors: 0
Running suite(s): WriteSet
100%: Checks: 2, Failures: 0, Errors: 0
Running suite(s): write_set
100%: Checks: 8, Failures: 0, Errors: 0
Running suite(s): trx_handle
100%: Checks: 2, Failures: 0, Errors: 0
Running suite(s): service_thd
100%: Checks: 3, Failures: 0, Errors: 0
Running suite(s): ist
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
qemu: Unsupported syscall: 350
100%: Checks: 6, Failures: 0, Errors: 0
Running suite(s): saved_state
33%: Checks: 3, Failures: 1, Errors: 1
galera/tests/saved_state_check.cpp:48:E:saved_state:test_unsafe:0: (after this 
point) Test timeout expired

Bug#816517: ulem.sty from texlive-generic- recommended

[Norbert Preining]

Hi all,

> or wait until I have uploaded the new package.

Which has happened just now, so should be available in a day.
Simply closing the FTBFS after a pbuilder/cowbuilder check should
suffice. No need for new uploads.

Or you reassign to texlive-htmlxml and merge with the closed bug
816584 where exactly this probelms was described and explained.

Thanks

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13