Bug#817116: civicrm: FTBFS: dh_linktree: link destination debian/civicrm-common/usr/share/civicrm/vendor/phenx/php-font-lib/classes is a directory

[Chris Lamb]

Source: civicrm
Version: 4.7.2+dfsg-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

civicrm fails to build from source in unstable/amd64:

  [..]

  mkdir: created directory 
'debian/civicrm-common/usr/share/civicrm/packages/tcpdf'
  pre-linktree: /usr/share/php/dompdf --> 
debian/civicrm-common/usr/share/civicrm/vendor/dompdf/dompdf
  pre-linktree: /usr/share/php/php-font-lib --> 
debian/civicrm-common/usr/share/civicrm/vendor/phenx/php-font-lib
  pre-linktree: /usr/share/php/Psr/Log --> 
debian/civicrm-common/usr/share/civicrm/vendor/psr/log/Psr/Log
  ## we need to call dh_linktree before dh_link, not after like it
  ## happens by default in "--with linktree" mode.
  dh_linktree
  dh_linktree: link destination 
debian/civicrm-common/usr/share/civicrm/vendor/phenx/php-font-lib/classes is a 
directory
  debian/rules:54: recipe for target 'override_dh_link' failed
  make[1]: *** [override_dh_link] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160308073122.zwCgusrmHz/civicrm-4.7.2+dfsg'
  debian/rules:7: recipe for target 'binary' failed
  make: *** [binary] Error 2

  [..]

The full build log is attached.


Regards,

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


civicrm.4.7.2+dfsg-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#817012: ruby-amqp and ruby-amq-client: error when trying to install together

[Ralf Treinen]

Bonjour Sebastien,

thanks for the removal of ruby-amq-client. However, I think that you
still should add to ruby-amqp Replaces/Conflicts with ruby-amq-client,
in order allow for smooth upgrade from old installations.

Cheers -Ralf.

Bug#814976: whitedune: diff for NMU version 0.30.10-2.1

[Raúl Benencia]

Control: tags 814976 + patch
Control: tags 814976 + pending

Dear maintainer,

This bug is caused by a recent update on grep. This update modified a bit
the heuristic used for determining when the given input is binary.

I've prepared an NMU for whitedune (versioned as 0.30.10-2.1). As I don't
have privileges to upload it to DELAYED, I've uploaded it to the mentors
repository.

To access further information about this package, please visit the
following URL:

  http://mentors.debian.net/package/whitedune


Alternatively, one can download the package with dget using this command:

  dget -x 
http://mentors.debian.net/debian/pool/main/w/whitedune/whitedune_0.30.10-2.1.dsc

Cheers,
Rul
diff -Nru whitedune-0.30.10/debian/changelog whitedune-0.30.10/debian/changelog
--- whitedune-0.30.10/debian/changelog	2016-01-09 12:53:49.0 -0800
+++ whitedune-0.30.10/debian/changelog	2016-03-07 08:19:38.0 -0800
@@ -1,3 +1,10 @@
+whitedune (0.30.10-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS due new binary matching behavior on grep (Closes: #814976)
+
+ -- Raúl Benencia   Mon, 07 Mar 2016 07:56:28 -0800
+
 whitedune (0.30.10-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru whitedune-0.30.10/debian/patches/avoid-grep-binary.patch whitedune-0.30.10/debian/patches/avoid-grep-binary.patch
--- whitedune-0.30.10/debian/patches/avoid-grep-binary.patch	1969-12-31 16:00:00.0 -0800
+++ whitedune-0.30.10/debian/patches/avoid-grep-binary.patch	2016-03-07 08:12:25.0 -0800
@@ -0,0 +1,13 @@
+Index: whitedune-0.30.10/src/Makefile.in
+===
+--- whitedune-0.30.10.orig/src/Makefile.in	2011-04-29 02:28:06.0 -0700
 whitedune-0.30.10/src/Makefile.in	2016-03-07 08:08:45.863708021 -0800
+@@ -771,7 +771,7 @@
+ resource.c: dune.rc swt/rc/rc $(ICONS) resource.h
+ 	sed 's../.' < dune.rc > dune1.rc.c
+ 	$(CXXCPP) dune1.rc.c > dune2.rc.c 
+-	grep -v '//' dune2.rc.c > dune3.rc.c
++	grep -av '//' dune2.rc.c > dune3.rc.c
+ 	if swt/rc/rc < dune3.rc.c > resource.c ; then echo > /dev/null; else rm  resource.c ; exit 1 ; fi
+ 	rm dune1.rc.c dune2.rc.c dune3.rc.c
+ 
diff -Nru whitedune-0.30.10/debian/patches/series whitedune-0.30.10/debian/patches/series
--- whitedune-0.30.10/debian/patches/series	2016-01-09 12:53:19.0 -0800
+++ whitedune-0.30.10/debian/patches/series	2016-03-07 08:12:25.0 -0800
@@ -1,2 +1,3 @@
 libxp-configure.patch
 png1.5.patch
+avoid-grep-binary.patch


signature.asc
Description: PGP signature

Bug#816376: [Pkg-owncloud-maintainers] Bug#816376: Unfit upstream

[Jos Poortvliet]

On Monday, March 7, 2016 5:43:20 PM AMT Sébastien Villemot wrote:
> Dear David,
> 
> First, let me thank you for the work that you put into packaging
> owncloud for Debian, it is really appreciated.
> 
> On Tue, 1 Mar 2016 07:07:10 -0400 David =?iso-8859-1?Q?Pr=E9vot?= 
>  wrote:
> 
> > Upstream doesn’t wish to see their software in Debian anymore. Unless
> > the situation changes in the next few months, owncloud will not be part
> > of Stretch.
> 
> Given that owncloud is such a useful and important package, and that
> there is currently no credible alternative, this is really sad news, and
> I am wondering whether this outcome could be avoided.
> 
> If I understand correctly, your decision is essentially based on social
> issues (upstream hostile to Debian packaging), coupled to some technical
> aspects (complex upgrade paths).

See my last email here - we'd love to have ownCloud included in Debian but 
obviously only if it provides a good experience to users. Right now, it seems 
that that is hard to do within the framework Debian provides.

http://lists.alioth.debian.org/pipermail/pkg-owncloud-maintainers/2016-March/002899.html

The situation is rather sad and frustrating as users who decided to trust the 
Debian developers and took their packages over ownCloud's provided packages are 
now stuck on a version which can't trivially be upgraded to either our upstream 
version or anything else. We would love to find a solution for them - as I've 
said many times, our main concern is the end users, rather than politics, rules 
or anything else.

Thanks for caring about this,
Jos

> At first glance, this does not seem to prevent the package from staying
> in Debian. Maybe this just means that the package needs a new
> maintainer, who is willing to handle the tough interaction with upstream
> and dealing with the technical issues (note that I am not applying for
> the job).
> 
> You are certainly in a better position than me to ascertain whether the
> package can stay in Debian or not, but I think that it would be useful
> if you could give a little more background on the issues that you
> encountered. And, if you think it makes sense to orphan the package,
> that would help prospective new maintainers in making the decision to
> adopt the package or not.
> 
> Cheers,
> 
> 



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

Bug#817006: ack to NMU

[Benda Xu]

Hi Adam,

Thank you for your report.  I appreciate your enthusiasm.

Sorry, I forgot to append my reply to Andreas to #811708:

  
http://lists.alioth.debian.org/pipermail/openrc-devel/Week-of-Mon-20160307/000436.html

Basically, my taking to this bug is to ignore it, leaving the users to
fix the breakage by

  dpkg-divert --remove /usr/sbin/invoke-rc.d
  dpkg-divert --remove /usr/sbin/update-rc.d

manually.  

0.20.4-1 lasted only 10days.  Only few users would be affected.
Provided OpenRC have already been removed from testing thanks to i-s-h
[1], such a breakage is tolerable for unstable.


That said, I understand theoretically your NMU is the correctly way to
go.  So if you intend to do so, consider this email as an ack to NMU
from the maintainer team.


One thing to notice is that we are tracking the package at

  http://anonscm.debian.org/cgit/openrc/openrc.git

Would you mind if I ask you to prepare a commit to the master
corresponding to the NMU?

BTW, if you are interested in OpenRC, you are welcomed to join the
maintenance team.

Yours,
Benda


1. 0.20.4-1 was uploaded in a hurry to keep itself in testing.  The pts
system lied and we did not make it.  divert should not have existed in
OpenRC.

Processed: whitedune: diff for NMU version 0.30.10-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 814976 + patch
Bug #814976 [src:whitedune] whitedune: FTBFS: dune1.rc.c:1392: syntax error
Added tag(s) patch.
> tags 814976 + pending
Bug #814976 [src:whitedune] whitedune: FTBFS: dune1.rc.c:1392: syntax error
Added tag(s) pending.

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

Bug#817112: libvirglrenderer0 and libvirglrenderer-dev: error when trying to install together

[Ralf Treinen]

Package: libvirglrenderer-dev,libvirglrenderer0
Version: libvirglrenderer-dev/0.4.0-4
Version: libvirglrenderer0/0.4.0-4
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-03-08
Architecture: amd64
Distribution: sid

Hi,

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


Selecting previously unselected package libdrm2:amd64.
(Reading database ... 10939 files and directories currently installed.)
Preparing to unpack .../libdrm2_2.4.67-1_amd64.deb ...
Unpacking libdrm2:amd64 (2.4.67-1) ...
Selecting previously unselected package libepoxy0:amd64.
Preparing to unpack .../libepoxy0_1.3.1-1_amd64.deb ...
Unpacking libepoxy0:amd64 (1.3.1-1) ...
Selecting previously unselected package libexpat1:amd64.
Preparing to unpack .../libexpat1_2.1.0-7_amd64.deb ...
Unpacking libexpat1:amd64 (2.1.0-7) ...
Selecting previously unselected package libffi6:amd64.
Preparing to unpack .../libffi6_3.2.1-4_amd64.deb ...
Unpacking libffi6:amd64 (3.2.1-4) ...
Selecting previously unselected package libwayland-client0:amd64.
Preparing to unpack .../libwayland-client0_1.9.0-1_amd64.deb ...
Unpacking libwayland-client0:amd64 (1.9.0-1) ...
Selecting previously unselected package libwayland-server0:amd64.
Preparing to unpack .../libwayland-server0_1.9.0-1_amd64.deb ...
Unpacking libwayland-server0:amd64 (1.9.0-1) ...
Selecting previously unselected package libgbm1:amd64.
Preparing to unpack .../libgbm1_11.1.2-1_amd64.deb ...
Unpacking libgbm1:amd64 (11.1.2-1) ...
Selecting previously unselected package libvirglrenderer0.
Preparing to unpack .../libvirglrenderer0_0.4.0-4_amd64.deb ...
Unpacking libvirglrenderer0 (0.4.0-4) ...
Selecting previously unselected package libvirglrenderer-dev.
Preparing to unpack .../libvirglrenderer-dev_0.4.0-4_amd64.deb ...
Unpacking libvirglrenderer-dev (0.4.0-4) ...
dpkg: error processing archive 
/var/cache/apt/archives/libvirglrenderer-dev_0.4.0-4_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libvirglrenderer.so', which is 
also in package libvirglrenderer0 0.4.0-4
Processing triggers for libc-bin (2.22-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libvirglrenderer-dev_0.4.0-4_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

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

  /usr/lib/x86_64-linux-gnu/libvirglrenderer.so

This bug has been filed against 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 then
also register in the BTS that the other package is affected by the bug.

-Ralf.

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

Bug#817057: network-manager-openconnect: Update unstable version to latest Upstream Build

[Michael Stapelberg]

Thanks for clarifying the issue you’re seeing. I don’t think this is
related to the D-Bus changes.

Also, to be clear: I’m not the maintainer of this package, I sponsored
mtmiller@’s uploads, who maintains the package.

On Tue, Mar 8, 2016 at 3:09 AM, Ryan Chewning  wrote:

> Michael, I copied you on this bug as you're the package maintainer for
> network-manager-openconnect and the imports of the upstream are failing.
> Currently, upstream for network-open-connect is at 1.91 and in Debian
> unstable/testing are both on the 1.0.2 release which isn't working with the
> network-manager builds in unstable and are on 1.91. I'm attempting to
> create an openconnect vpn profile but I get the following error messages in
> my .xsession-error log when launching nm-connection editor
>
> """
> ** Message: vpn: (iodine,/usr/lib/NetworkManager/VPN/
> nm-iodine-service.name) cannot load legacy-only plugin
> ** Message: vpn: (ssh,/usr/lib/NetworkManager/VPN/nm-ssh-service.name)
> cannot load legacy-only plugin
> ** Message: vpn: (openconnect,/usr/lib/NetworkManager/VPN/
> nm-openconnect-service.name) cannot load legacy-only plugin
> ** Message: vpn: (strongswan,/etc/NetworkManager/VPN/
> nm-strongswan-service.name) cannot load legacy-only plugin
> 
>
> I also only have the option to configure the following three types of vpns
> OpenVPN, PPTP or KVPNC even though I have iodine, ssh, openconnect and
> strongswan installed.
>
> If you think this bug is better suited for the network-manager package
> please let me know and I'll head over that way.
>
> Thanks,
>
> Ryan
>
> On Mon, Mar 7, 2016 at 12:22 PM, Michael Stapelberg  > wrote:
>
>>
>>
>> On Mon, Mar 7, 2016 at 9:07 AM, Ryan Chewning  wrote:
>>
>>> Package: network-manager-openconnect
>>> Version: 1.0.2-1+b1
>>> Severity: grave
>>> Tags: upstream
>>> Justification: renders package unusable
>>>
>>> The latest builds of networkmanager in testing/unstable no longer
>>> support dbus. https://blogs.gnome.org/dcbw/2016/02/19/die-dbus-glib-die/
>>>
>>
>> I’m only a bystander for the purpose of this bug, but “networkmanager […]
>> no longer supports dbus” conflicts with the article you refer to, which
>> mentions:
>>
>> """
>> I cannot understate how much work this was and how much careful planning
>> we (well, mostly Dan Winship) did to ensure we didn’t break backwards
>> compatibility of either the utility libraries or the D-Bus interface.
>> """
>>
>> The way I read this, the new networkmanager version is
>> backwards-compatible with regards to its D-Bus interface.
>>
>> Can you clarify? If it turns out that it’s actually backwards-compatible,
>> is severity: grave still justified?
>>
>>
>>> There is an updated version of the network-manager-openconnect but it is
>>> failing to be pulled down by uscan. Manual intervention is needed.
>>>
>>> Thanks,
>>>
>>> Ryan
>>>
>>> -- System Information:
>>> Debian Release: stretch/sid
>>>   APT prefers testing-updates
>>>   APT policy: (500, 'testing-updates'), (500, 'testing')
>>> Architecture: amd64 (x86_64)
>>> Foreign Architectures: i386
>>>
>>> Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
>>> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
>>> Shell: /bin/sh linked to /bin/dash
>>> Init: systemd (via /run/systemd/system)
>>>
>>> Versions of packages network-manager-openconnect depends on:
>>> ii  adduser   3.113+nmu3
>>> ii  libc6 2.21-9
>>> ii  libdbus-1-3   1.10.6-1
>>> ii  libdbus-glib-1-2  0.106-1
>>> ii  libglib2.0-0  2.46.2-3
>>> ii  libnm-glib-vpn1   1.1.90-6
>>> ii  libnm-glib4   1.1.90-6
>>> ii  libnm-util2   1.1.90-6
>>> ii  network-manager   1.1.90-6
>>> ii  openconnect   7.06-2+b2
>>>
>>> network-manager-openconnect recommends no packages.
>>>
>>> network-manager-openconnect suggests no packages.
>>>
>>> -- no debconf information
>>>
>>>
>>
>>
>> --
>> Best regards,
>> Michael
>>
>
>


-- 
Best regards,
Michael

Bug#784616: marked as done ([dff] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Tue, 08 Mar 2016 06:11:30 +
with message-id 
and subject line Bug#816970: Removed package(s) from unstable
has caused the Debian Bug report #784616,
regarding [dff] Qt4's WebKit removal
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.)


-- 
784616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dff
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal
Control: block 784513 by -1

Hi! As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce]. Your package seems to be using it via PyQt4's
QtWebKit module.

[announce] 


Basically we are about to get the last Qt4 point release and upstream is
migrating from WebKit to Blink in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit (Qt5's WebKit is expected to stay supported
until Qt6).

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5 
  port of your application
- if there are no activities regarding porting, investigate whether there are 
  suitable alternatives for your users
- if there is a Qt5/PyQt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian 
  archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] and the
PyQt4 vs PyQt5 differences page [pyqtchanges] whenever you start porting
your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html
[pyqtchanges] http://pyqt.sourceforge.net/Docs/PyQt5/pyqt4_differences.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE 
team at debian-qt-...@lists.debian.org.

--
Dmitry Shachnev,
on behalf of the Qt4 and PyQt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 1.3.0+dfsg.1-4.1+rm

Dear submitter,

as the package dff has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/816970

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#798168: marked as done (caret: depends on vtk 5)

[Debian Bug Tracking System]

Your message dated Tue, 08 Mar 2016 06:10:42 +
with message-id 
and subject line Bug#816918: Removed package(s) from unstable
has caused the Debian Bug report #798168,
regarding caret: depends on vtk 5
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.)


-- 
798168: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: caret
Version: 5.6.4~dfsg.1-3
Severity: serious
Tags: sid stretch
Control: block 798164 with -1

Hi,

your package depends on vtk 5.x, which should not be in stretch.  Please
switch to vtk 6.x or drop the dependency.

Thanks,
Julien


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 5.6.4~dfsg.1-3+rm

Dear submitter,

as the package caret has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/816918

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#817092: libjs-handlebars: Minified source is non-free

[Luke Faraone]

Package: libjs-handlebars
Version: 1.3.0-1
Severity: serious
Justification: DSFG §2

Hello,

I noticed that, aside from the version in experimental, libjs-handlebars is
combined into a single file and already pre-"built". That means that Debian is
not distributing the actual source, which fails DFSG §2

  -- Luke Faraone

Processed: patch and intent to NMU

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #817006 [openrc] openrc: dangling diversion of 
/usr/sbin/{invoke,update}-rc.d
Added tag(s) patch.

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

Bug#817006: patch and intent to NMU

[Adam Borowski]

Control: tags -1 +patch

Hi!
Here's a patch (attached).

Because of the bug's severity, and, unlike the cooperate-or-divert issue
recently, the fix being obvious, I intend to NMU by, say, today evening,
unless you say something.  Proposed debdiff attached as well.


Meow!
-- 
A tit a day keeps the vet away.
>From b4653519c5109967be09976e1fbf431316d07dcf Mon Sep 17 00:00:00 2001
From: Adam Borowski 
Date: Tue, 8 Mar 2016 05:19:25 +0100
Subject: [PATCH] Remove dangling diverts introduced by 0.20.4-1.

---
 debian/openrc.postinst | 13 +
 1 file changed, 13 insertions(+)

diff --git a/debian/openrc.postinst b/debian/openrc.postinst
index 4d09a68..cd0284e 100644
--- a/debian/openrc.postinst
+++ b/debian/openrc.postinst
@@ -2,6 +2,19 @@
 
 set -e
 
+# Remove diverts made by 0.20.4-1
+if [ "$(dpkg-divert --list /usr/sbin/invoke-rc.d)" = \
+ "diversion of /usr/sbin/invoke-rc.d to /usr/sbin/invoke-rc.d.init-system-helpers by openrc" ]
+	then dpkg-divert --package openrc --remove --rename \
+		--divert /usr/sbin/invoke-rc.d.init-system-helpers /usr/sbin/invoke-rc.d
+fi
+if [ "$(dpkg-divert --list /usr/sbin/update-rc.d)" = \
+ "diversion of /usr/sbin/update-rc.d to /usr/sbin/update-rc.d.init-system-helpers by openrc" ]
+	then dpkg-divert --package openrc --remove --rename \
+		--divert /usr/sbin/update-rc.d.init-system-helpers /usr/sbin/update-rc.d
+fi
+
+
 if [ "${1}" = "configure" ] ; then
 	echo "Add existing services ..."
 
-- 
2.7.0

diff -Nru openrc-0.20.4/debian/changelog openrc-0.20.4/debian/changelog
--- openrc-0.20.4/debian/changelog  2016-03-04 19:25:52.0 +0100
+++ openrc-0.20.4/debian/changelog  2016-03-08 05:18:35.0 +0100
@@ -1,3 +1,10 @@
+openrc (0.20.4-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove diversions to update-rc.d + invoke-rc.d (Closes: #817006).
+
+ -- Adam Borowski   Tue, 08 Mar 2016 05:17:44 +0100
+
 openrc (0.20.4-2) unstable; urgency=high
 
   * Bump standard to 3.9.7.
diff -Nru openrc-0.20.4/debian/openrc.postinst 
openrc-0.20.4/debian/openrc.postinst
--- openrc-0.20.4/debian/openrc.postinst2016-03-04 19:25:52.0 
+0100
+++ openrc-0.20.4/debian/openrc.postinst2016-03-08 05:17:41.0 
+0100
@@ -2,6 +2,19 @@
 
 set -e
 
+# Remove diverts made by 0.20.4-1
+if [ "$(dpkg-divert --list /usr/sbin/invoke-rc.d)" = \
+ "diversion of /usr/sbin/invoke-rc.d to 
/usr/sbin/invoke-rc.d.init-system-helpers by openrc" ]
+   then dpkg-divert --package openrc --remove --rename \
+   --divert /usr/sbin/invoke-rc.d.init-system-helpers 
/usr/sbin/invoke-rc.d
+fi
+if [ "$(dpkg-divert --list /usr/sbin/update-rc.d)" = \
+ "diversion of /usr/sbin/update-rc.d to 
/usr/sbin/update-rc.d.init-system-helpers by openrc" ]
+   then dpkg-divert --package openrc --remove --rename \
+   --divert /usr/sbin/update-rc.d.init-system-helpers 
/usr/sbin/update-rc.d
+fi
+
+
 if [ "${1}" = "configure" ] ; then
echo "Add existing services ..."
 

Bug#816517: marked as done (boxbackup: FTBFS: TEST FAILURE: Condition [::system("perl testfiles/testrequests.pl") == 0] )

[Debian Bug Tracking System]

Your message dated Tue, 08 Mar 2016 04:19:46 +
with message-id 
and subject line Bug#816517: fixed in boxbackup 0.11.1~r2837-2
has caused the Debian Bug report #816517,
regarding boxbackup: FTBFS: TEST FAILURE: Condition [::system("perl 
testfiles/testrequests.pl") == 0] 
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.)


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

boxbackup fails to build from source in unstable/amd64:

  [..]

  Waiting for bbackupd to try to access the store:  done.
  .Starting server: ../../bin/bbackupd/bbackupd  
testfiles/bbackupd-snapshot.conf
  Waiting for server to start:  done.
  Waiting for just before bbackupd recovers: 
...
 done.
  Waiting for bbackupd to recover: .. done.
  .Starting server: ../../bin/bbackupd/bbackupd  testfiles/bbackupd.conf
  Waiting for server to start:  done.
  Waiting for just before bbackupd recovers: 

 done.
  Waiting for bbackupd to recover: .. done.
  
   Replace symlink with directory, add new directory
  Waiting for bbackupd to sync the changes:  done.
  
   Replace directory with symlink
  Waiting for bbackupd to sync the changes:  done.
  
   Replace symlink with directory (which was a symlink)
  Waiting for bbackupd to sync the changes:  done.
  
   Put it all back to how it was
  Waiting for bbackupd to sync the changes:  done.
  
   Rename over existing untracked file
  Waiting for untracked files to be old enough: . done.
  Waiting for bbackupd to sync the untracked files:  done.
  Waiting for bbackupd to sync the untracked files again:  done.
  
   Rename over existing tracked file
  Waiting for tracked files to be old enough: . done.
  Waiting for bbackupd to sync the tracked files again:  done.
  
   Rename an existing file over a deleted file
  Waiting for bbackupd to sync:  done.
  
   Add files with old times, update attributes of one to latest time
  Waiting for bbackupd to sync old files:  done.
  
   Modify existing file, but change timestamp to rather old
  
   Add files and dirs for exclusion test
  
   Check that exclude/alwaysinclude commands actually work
  
   Add unreadable files
  Waiting for bbackupd to try to sync unreadable file:  done.
  
   Continuously update file, check isn't uploaded
  
  READ: WARNING: Local file 'testfiles/TestDir1/continousupdate' exists, but 
remote file '/Test1/continousupdate' does not.
  
   Keep on continuously updating file, check it is uploaded eventually
  
  READ: WARNING: Local file 'testfiles/TestDir1/continousupdate' has different 
attributes to store file '/Test1/continousupdate'.
  READ: WARNING: Local file 'testfiles/TestDir1/continousupdate' has different 
contents to store file '/Test1/continousupdate'.
  
   Delete directory, change attributes
  Waiting for bbackupd to sync deletion of directory:  done.
  
   Restore files and directories
  
  ..
  
   Try to restore to a path that doesn't exist
  
   Add files with current time
  Waiting for bbackupd to sync new files:  done.
  
   Rename directory
  Waiting for bbackupd to sync renamed directory:  done.
  WARNING: Quick compare used -- file attributes are not checked.
  
   Rename files
  Waiting for bbackupd to sync renamed files:  done.
  
   Create a file with timestamp way ahead in the future
  Waiting for bbackup to sync future file:  done.
  
   Change client store marker
  
   Check change of store marker pauses daemon
  Waiting for bbackupd to detect changed store marker: .. done.
  Waiting for bbackupd to recover: 
..
 done.
  
   Interrupted restore
  
   Interrupted restore
  
   Resume restore

Bug#816376: Unfit upstream

[David Prévot]

Hi Sébastien,

Le 07/03/2016 12:43, Sébastien Villemot a écrit :

> On Tue, 1 Mar 2016 07:07:10 -0400 David Prévot  wrote:
> 
>> Upstream doesn’t wish to see their software in Debian anymore. Unless
>> the situation changes in the next few months, owncloud will not be part
>> of Stretch.

[…]
> I am wondering whether this outcome could be avoided.
> 
> If I understand correctly, your decision is essentially based on social
> issues (upstream hostile to Debian packaging), coupled to some technical
> aspects (complex upgrade paths).

That description fits roughly my view of the problem, yes.

> At first glance, this does not seem to prevent the package from staying
> in Debian. Maybe this just means that the package needs a new
> maintainer, who is willing to handle the tough interaction with upstream
> and dealing with the technical issues

That might work. I honestly doubt upstream would be willing to have its
pet project properly packaged by anyone in the near future (most
distributions gave up before us), but I’d be happy to be proven wrong.

> You are certainly in a better position than me to ascertain whether the
> package can stay in Debian or not, but I think that it would be useful
> if you could give a little more background on the issues that you
> encountered.

Reading the (recent) threads on both the maintainer and upstream lists
should help anyone to make their mind about it (I’ll give a few
pointers). Seeing how Debian is described in upstream staff blog posts
and issue tracker goes further down (I don’t wish to publish some direct
links from the BTS, but they’re not hard to find).

[ When I realized they were going to make our life way more painful ]
https://lists.alioth.debian.org/pipermail/pkg-owncloud-maintainers/2016-February/002882.html

[ When they considered enforcing their trademark to throw us away ]
https://mailman.owncloud.org/pipermail/devel/2016-February/002106.html

> And, if you think it makes sense to orphan the package,
> that would help prospective new maintainers in making the decision to
> adopt the package or not.

I’m happy to give anyone write (and admin) access to our current
infrastructure. Feel free to open an RFA or O wnpp bug on my behalf if
you think it might help. But please, be aware that the enormous owncloud
package is only the tip of the iceberg: beyond the ~70 packages (some
were already removed via #816769) listed on the [DDPO], I was
maintaining a few more dozens on the PHP PEAR (and composer) Maintainers
team as well as some JavaScript packages.

DDPO:
https://qa.debian.org/developer.php?login=pkg-owncloud-maintainers%40lists.alioth.debian.org

Regards

David



signature.asc
Description: OpenPGP digital signature

Bug#817057: network-manager-openconnect: Update unstable version to latest Upstream Build

[Ryan Chewning]

Michael, I copied you on this bug as you're the package maintainer for
network-manager-openconnect and the imports of the upstream are failing.
Currently, upstream for network-open-connect is at 1.91 and in Debian
unstable/testing are both on the 1.0.2 release which isn't working with the
network-manager builds in unstable and are on 1.91. I'm attempting to
create an openconnect vpn profile but I get the following error messages in
my .xsession-error log when launching nm-connection editor

"""
** Message: vpn: (iodine,/usr/lib/NetworkManager/VPN/nm-iodine-service.name)
cannot load legacy-only plugin
** Message: vpn: (ssh,/usr/lib/NetworkManager/VPN/nm-ssh-service.name)
cannot load legacy-only plugin
** Message: vpn: (openconnect,/usr/lib/NetworkManager/VPN/
nm-openconnect-service.name) cannot load legacy-only plugin
** Message: vpn: (strongswan,/etc/NetworkManager/VPN/
nm-strongswan-service.name) cannot load legacy-only plugin


I also only have the option to configure the following three types of vpns
OpenVPN, PPTP or KVPNC even though I have iodine, ssh, openconnect and
strongswan installed.

If you think this bug is better suited for the network-manager package
please let me know and I'll head over that way.

Thanks,

Ryan

On Mon, Mar 7, 2016 at 12:22 PM, Michael Stapelberg 
wrote:

>
>
> On Mon, Mar 7, 2016 at 9:07 AM, Ryan Chewning  wrote:
>
>> Package: network-manager-openconnect
>> Version: 1.0.2-1+b1
>> Severity: grave
>> Tags: upstream
>> Justification: renders package unusable
>>
>> The latest builds of networkmanager in testing/unstable no longer support
>> dbus. https://blogs.gnome.org/dcbw/2016/02/19/die-dbus-glib-die/
>>
>
> I’m only a bystander for the purpose of this bug, but “networkmanager […]
> no longer supports dbus” conflicts with the article you refer to, which
> mentions:
>
> """
> I cannot understate how much work this was and how much careful planning
> we (well, mostly Dan Winship) did to ensure we didn’t break backwards
> compatibility of either the utility libraries or the D-Bus interface.
> """
>
> The way I read this, the new networkmanager version is
> backwards-compatible with regards to its D-Bus interface.
>
> Can you clarify? If it turns out that it’s actually backwards-compatible,
> is severity: grave still justified?
>
>
>> There is an updated version of the network-manager-openconnect but it is
>> failing to be pulled down by uscan. Manual intervention is needed.
>>
>> Thanks,
>>
>> Ryan
>>
>> -- System Information:
>> Debian Release: stretch/sid
>>   APT prefers testing-updates
>>   APT policy: (500, 'testing-updates'), (500, 'testing')
>> Architecture: amd64 (x86_64)
>> Foreign Architectures: i386
>>
>> Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
>> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>> Init: systemd (via /run/systemd/system)
>>
>> Versions of packages network-manager-openconnect depends on:
>> ii  adduser   3.113+nmu3
>> ii  libc6 2.21-9
>> ii  libdbus-1-3   1.10.6-1
>> ii  libdbus-glib-1-2  0.106-1
>> ii  libglib2.0-0  2.46.2-3
>> ii  libnm-glib-vpn1   1.1.90-6
>> ii  libnm-glib4   1.1.90-6
>> ii  libnm-util2   1.1.90-6
>> ii  network-manager   1.1.90-6
>> ii  openconnect   7.06-2+b2
>>
>> network-manager-openconnect recommends no packages.
>>
>> network-manager-openconnect suggests no packages.
>>
>> -- no debconf information
>>
>>
>
>
> --
> Best regards,
> Michael
>

Bug#817058: marked as done (sketch: FTBFS in stretch (TeX error))

[Debian Bug Tracking System]

Your message dated Tue, 08 Mar 2016 01:24:48 +
with message-id 
and subject line Bug#817058: fixed in sketch 1:0.3.7-2
has caused the Debian Bug report #817058,
regarding sketch: FTBFS in stretch (TeX error)
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.)


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

Dear maintainer:

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

The error, however, seems to happen with ordinary "dpkg-buildpackage"
as well, which is why I'm using "serious" severity here. See

https://reproducible.debian.net/rbuild/testing/amd64/sketch_0.3.7-1.rbuild.log

for the build log from the reproducible builds effort.


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
perl makever.pl

[... snipped ...]

Transcript written on mfput.log.
grep: ecrm1440.log: No such file or directory
mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input 
ecrm1440' failed to make ecrm1440.tfm.
kpathsea: Appending font creation commands to missfont.log.

./sketch.texi:3327: Font \thisecfont=ecrm1440 at 14.0pt not loadable: Metric (T
FM) file not found.
 
   \thisecfont 
\indexlbrace ->{\ifmonospace \else \ecfont 
   \fi \char 123}
 ... \kern -0.05em \secbf {\indexlbrace 
  }
\leftline #1->\line {#1
   \hss }
\initialx ...e {\secfonts \kern -0.05em \secbf #1}
  \nobreak \vskip .33\baseli...

\thisline ->\initial {{\indexlbrace }}
   
...
l.3327 @printindex sx
 
? 
./sketch.texi:3327: Emergency stop.
 
   \thisecfont 
\indexlbrace ->{\ifmonospace \else \ecfont 
   \fi \char 123}
 ... \kern -0.05em \secbf {\indexlbrace 
  }
\leftline #1->\line {#1
   \hss }
\initialx ...e {\secfonts \kern -0.05em \secbf #1}
  \nobreak \vskip .33\baseli...

\thisline ->\initial {{\indexlbrace }}
   
...
l.3327 @printindex sx
 
Output written on sketch.dvi (44 pages, 150420 bytes).
Transcript written on sketch.log.
/usr/bin/texi2dvi: etex exited with bad status, quitting.
Died at make.pl line 87,  line 3335.
debian/rules:27: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
debian/rules:21: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2



Apparently, this happened to work in the past and it does no longer
because of some new texlive package being used, it seems.

[ So I'll omit the standard blurb I add to these kind of bugs ]

Thanks.
--- End Message ---
--- Begin Message ---
Source: sketch
Source-Version: 1:0.3.7-2

We believe that the bug you reported is fixed in the latest version of
sketch, 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.
David Bremner  (supplier of updated sketch 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:43:34 -0400
Source: sketch
Binary: sketch sketch-doc
Architecture: source
Version: 1:0.3.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: David 

Processed: tagging 813647

[Debian Bug Tracking System]

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

> tags 813647 + sid stretch
Bug #813647 [connman] connman: daemon no longer starts after upgrade
Added tag(s) sid and stretch.
> thanks
Stopping processing here.

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

Bug#814970: marked as done (libm4ri: FTBFS: libpng12.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status)

[Debian Bug Tracking System]

Your message dated Mon, 7 Mar 2016 22:52:34 +
with message-id <56de0632.7040...@debian.org>
and subject line Re: FTBFS: libpng12.a: error adding symbols: Bad value 
collect2: error: ld returned 1 exit status
has caused the Debian Bug report #814970,
regarding libm4ri: FTBFS: libpng12.a: error adding symbols: Bad value   
collect2: error: ld returned 1 exit status
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.)


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

Dear Maintainer,

libm4ri fails to build from source in unstable/amd64:

  [..]

  libtool: link: gcc -shared  -fPIC -DPIC  m4ri/.libs/brilliantrussian.o 
m4ri/.libs/misc.o m4ri/.libs/mzd.o m4ri/.libs/graycode.o m4ri/.libs/strassen.o 
m4ri/.libs/mzp.o m4ri/.libs/triangular.o m4ri/.libs/triangular_russian.o 
m4ri/.libs/ple.o m4ri/.libs/ple_russian.o m4ri/.libs/solve.o 
m4ri/.libs/echelonform.o m4ri/.libs/mmc.o m4ri/.libs/debug_dump.o 
m4ri/.libs/io.o m4ri/.libs/djb.o m4ri/.libs/mp.o   -lpng12  -mmmx -msse -msse2 
-g -O2 -fstack-protector-strong -Wl,-z -Wl,relro   -Wl,-soname 
-Wl,libm4ri-0.0.20140914.so -o .libs/libm4ri-0.0.20140914.so
  /usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libpng12.a(libpng12_la-png.o):
 relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a 
shared object; recompile with -fPIC
  /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libpng12.a: error 
adding symbols: Bad value
  collect2: error: ld returned 1 exit status
  Makefile:887: recipe for target 'libm4ri.la' failed
  make[2]: *** [libm4ri.la] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160217092802.vNbHJmgW67/libm4ri-20140914'
  Makefile:763: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160217092802.vNbHJmgW67/libm4ri-20140914'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:15: 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
   `-


libm4ri.20140914-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Hi,

I believe the problem was caused by the first fix to #766809 in libpng,
which was uploaded the day before libm4ri failed to build and reportedly
broke building with -lpng12, which libm4ri does.

I cannot reproduce this FTBFS anymore, building on unstable with sbuild.
Also it builds again on reproducible builds:
https://tests.reproducible-builds.org/rb-pkg/unstable/amd64/libm4ri.html

Closing the bug.

Best,
Tobias Hansen--- End Message ---

Processed: notfixed 787294 in 2.1-1, reassign 817012 to ruby-amqp, affects 817012, fixed 817012 in 1.5.1-2

[Debian Bug Tracking System]

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

> # unconfuse bts
> notfixed 787294 2.1-1
Bug #787294 {Done: Thomas Liske } [needrestart] 
needrestart: provide Nagios/Icinga check for needrestart
No longer marked as fixed in versions needrestart/2.1-1.
> reassign 817012 ruby-amqp 1.5.1-1
Bug #817012 {Done: Sebastien Badia } 
[ruby-amq-client,ruby-amqp] ruby-amqp and ruby-amq-client: error when trying to 
install together
Bug reassigned from package 'ruby-amq-client,ruby-amqp' to 'ruby-amqp'.
Ignoring request to alter found versions of bug #817012 to the same values 
previously set
No longer marked as fixed in versions ruby-amqp/1.5.1-2.
Bug #817012 {Done: Sebastien Badia } [ruby-amqp] ruby-amqp and 
ruby-amq-client: error when trying to install together
Marked as found in versions ruby-amqp/1.5.1-1.
> affects 817012 + ruby-amq-client
Bug #817012 {Done: Sebastien Badia } [ruby-amqp] ruby-amqp and 
ruby-amq-client: error when trying to install together
Added indication that 817012 affects ruby-amq-client
> fixed 817012 1.5.1-2
Bug #817012 {Done: Sebastien Badia } [ruby-amqp] ruby-amqp and 
ruby-amq-client: error when trying to install together
Marked as fixed in versions ruby-amqp/1.5.1-2.
> thanks
Stopping processing here.

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

Bug#816801: Info from 817039

[Julian Calaby]

Hi,

Just to re-iterate the info I added in 817039 as it's kinda hidden by
the merging process:

An alternate fix would be to remove the erroneous version check
altogether as the version of python-dbus is managed by dpkg, making
this check redundant.

As to why I've upgraded this to grave: this failed assersion makes the
main "volti" command fail on startup rendering the main part of the
package, the systray icon, unusable.

Thanks,

-- 
Julian Calaby

Email: julian.cal...@gmail.com
Profile: http://www.google.com/profiles/julian.calaby/

Processed: Merge identical bugs 816801 and 817039

[Debian Bug Tracking System]

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

> package volti
Limiting to bugs with field 'package' containing at least one of 'volti'
Limit currently set to 'package':'volti'

> severity 816801 grave
Bug #816801 [volti] volti: The script /usr/bin/volti incorrectly checks the 
version of dbus
Severity set to 'grave' from 'important'
> merge 816801 817039
Bug #816801 [volti] volti: The script /usr/bin/volti incorrectly checks the 
version of dbus
Bug #817039 [volti] volti: Fails to start due to incorrect python-dbus version 
check
Added tag(s) newcomer.
Merged 816801 817039
> thanks
Stopping processing here.

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

Bug#813970: marked as done (dbus: purge fails: invoke-rc.d: initscript dbus, action "stop" failed.)

[Debian Bug Tracking System]

Your message dated Mon, 07 Mar 2016 22:22:22 +
with message-id 
and subject line Bug#813970: fixed in dbus 1.11.2-1
has caused the Debian Bug report #813970,
regarding dbus: purge fails: invoke-rc.d: initscript dbus, action "stop" failed.
to be marked as done.

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

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


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I cannot purge dbus package on my server:

(Læser database ... 104307 filer og kataloger installeret i øjeblikket.)
Afinstallerer dbus (1.8.20-0+deb8u1) ...
Job for dbus.service canceled.
invoke-rc.d: initscript dbus, action "stop" failed.
dpkg: fejl under behandling af pakken dbus (--purge):
 underproces installerede pre-removal-script returnerede afslutningsstatus 1
Der opstod fejl under behandlingen:
 dbus


 - Jonas

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWtvPYAAoJECx8MUbBoAEhx9QP/AppsKAuduB3uUQumOWKsDy6
HfiY2OupLX7RNyY+1eI60z4Lrqkh0DmO4wmO3InGgW6yJ32mYuTDgv4PcFlXxuNq
8CQuwIv+L46iy+6s0xoZN1Fs5hpaG9/wv7F6FgOLb1c/AE4LlPd2O5OWgDNHZJSy
XNEHzlfAJwcO78cnXG6VzzJiokn+oStQLVqvKLxMCLirHFvK28+coyfHaW6rxsf7
ke1X1NbqhuVjvhBa4nygZqwHv3q9KEUpMklzuYobPXJ0f2pAr7O+j9gPBsIg3bvT
zQJKZTHYBIqOWyoJ5ZDPkQBpXpzxC4g9FDGdfK4bmvVAK+ORRI4MVzmWZ4C0tLGQ
pyEQm9CSBBuEYKYl3hbVfoBmGMfEx7oI8XNhgL1y0ojcF9y2boBFvS+j79UKP6TG
s87171B+c5RLtTLa/ul3gU6lDqU5xMPuWtLt0d1pH5yPOC887YduHnBeSIgdBWEM
B+R+zqoxN1lX7NOjdX8pK6eXjqLXSi3aStz7t51K7DqMMNGZAXXX+bTkFcLVUHs8
Gu2opmxcf4VcVyaJ7odJ3Ev0ZUT7NUUCnz2MkeWQfrqWUgzIt12nRS4TgAQ/k6Dj
+E7LTsKRulMjPDjL4+LDXtL/+BPbHttoWxMA0KDPJyYluJUawdeu4/L0h/dPYyR1
XHm082GrYyU7b4pWR9Db
=pTWg
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: dbus
Source-Version: 1.11.2-1

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated dbus 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:10:23 +
Source: dbus
Binary: dbus dbus-1-dbg dbus-1-doc dbus-tests dbus-udeb dbus-user-session 
dbus-x11 libdbus-1-3 libdbus-1-3-udeb libdbus-1-dev
Architecture: source
Version: 1.11.2-1
Distribution: experimental
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Simon McVittie 
Description:
 dbus   - simple interprocess messaging system (daemon and utilities)
 dbus-1-dbg - simple interprocess messaging system (debug symbols)
 dbus-1-doc - simple interprocess messaging system (documentation)
 dbus-tests - simple interprocess messaging system (test infrastructure)
 dbus-udeb  - simple interprocess messaging system (minimal runtime) (udeb)
 dbus-user-session - simple interprocess messaging system (systemd --user 
integration)
 dbus-x11   - simple interprocess messaging system (X11 deps)
 libdbus-1-3 - simple interprocess messaging system (library)
 libdbus-1-3-udeb - simple interprocess messaging system (minimal library) 
(udeb)
 libdbus-1-dev - simple interprocess messaging system (development headers)
Closes: 813970 815503
Changes:
 dbus (1.11.2-1) experimental; urgency=medium
 .
   * Merge packaging from unstable
   * Change the experimental watch file to track development releases
   * New upstream release
   * debian/control: change Vcs-Git to point to the experimental branch
 .
 dbus (1.10.8-1) unstable; urgency=medium
 .
   * New upstream release
   * dbus.prerm: ensure that dbus.socket is stopped before removal,
 so that a new connection to the bus won't cause dbus.service to be
 restarted (Closes: #813970)
   * debian/75dbus_dbus-launch: when not using systemd --user or the
 dbus-user-session package is not installed, start dbus-daemon early,
 then upload the full environment from Xsession.d later on
 (in 95dbus_update-activation-env). This more 

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

[Jeff Breidenbach]

IRC people tell me that a transition bug will fix everything. There is
an existing transition bug #815919.

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

[rinni]

Hi Jeff,

> Jeff Breidenbach  hat am 7. März 2016 um 21:22
> geschrieben:
> Thanks for working with me and sorry about the trouble.
Don't worry, things like that happen - let's just try to solve the bug
completely now :)

> I don't know what you mean by not closing bug #815056
> properly. The bug tracker says it is closed.
> 
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=tesseract
> 
> If I look at the package tracking system, it seems to be claiming
> something else entirely as the culprit. Something that I don't
> currently understand.
> 
> https://release.debian.org/migration/testing.pl?package=tesseract

I'm not sure about #815056 either, but 

https://release.debian.org/migration/testing.pl?package=tesseract

says updating to -4 introduces new bugs (in the gone libtesseract4).

Best,
Philip

Processed: reassign 813972 to libncarg-dev, fixed 813972 in 6.3.0-7, affects 813972, tagging 816518 ...

[Debian Bug Tracking System]

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

> reassign 813972 libncarg-dev 6.3.0-6
Bug #813972 {Done: Alastair McKinstry } 
[libncarg-dev,libncl-dev] libncl-dev and libncarg-dev: error when trying to 
install together
Bug reassigned from package 'libncarg-dev,libncl-dev' to 'libncarg-dev'.
No longer marked as found in versions libncl/2.1.18+dfsg-2 and ncl/6.3.0-6.
No longer marked as fixed in versions ncl/6.3.0-7.
Bug #813972 {Done: Alastair McKinstry } [libncarg-dev] 
libncl-dev and libncarg-dev: error when trying to install together
Marked as found in versions ncl/6.3.0-6.
> fixed 813972 6.3.0-7
Bug #813972 {Done: Alastair McKinstry } [libncarg-dev] 
libncl-dev and libncarg-dev: error when trying to install together
Marked as fixed in versions ncl/6.3.0-7.
> affects 813972 + libncl-dev
Bug #813972 {Done: Alastair McKinstry } [libncarg-dev] 
libncl-dev and libncarg-dev: error when trying to install together
Added indication that 813972 affects libncl-dev
> tags 816518 + sid stretch
Bug #816518 {Done: Sebastien Badia } [src:gitmagic] gitmagic: 
FTBFS: LaTeX Error: File `ulem.sty' not found.
Added tag(s) sid and stretch.
> tags 816517 + sid stretch
Bug #816517 [src:boxbackup] boxbackup: FTBFS: TEST FAILURE: Condition 
[::system("perl testfiles/testrequests.pl") == 0] 
Added tag(s) stretch and sid.
> affects 816561 + libvotca-tools-dev
Bug #816561 {Done: Michael Banck } [libvotca-tools3] 
libvotca-tools3: missing Breaks+Replaces against libvotca-tools2 (<< 1.3)
Added indication that 816561 affects libvotca-tools-dev
> tags 816638 + sid stretch
Bug #816638 [mhonarc] mhonarc: fails to run with perl5.22
Added tag(s) stretch and sid.
> tags 816587 + sid stretch
Bug #816587 [docbook-utils] shared-mime-info: FTBFS: LaTeX Error: File 
`ulem.sty' not found.
Bug #817026 [docbook-utils] gstreamer0.10: FTBFS: ! LaTeX Error: File 
`ulem.sty' not found.
Bug #817027 [docbook-utils] gstreamer1.0: FTBFS: LaTeX Error: File `ulem.sty' 
not found.
Added tag(s) sid and stretch.
Added tag(s) stretch and sid.
Added tag(s) stretch and sid.
> tags 816994 + stretch sid
Bug #816994 [src:aegis] aegis: FTBFS in stretch, build dependencies not in 
stretch
Added tag(s) stretch and sid.
> tags 816995 + sid stretch
Bug #816995 [src:fam] fam: FTBFS in stretch with new perl: Unescaped left brace 
in regex is deprecated
Added tag(s) sid and stretch.
> tags 816996 + sid stretch
Bug #816996 [src:gmerlin] gmerlin: FTBFS in stretch with new perl: Unescaped 
left brace in regex is deprecated
Added tag(s) sid and stretch.
> tags 817058 + sid stretch
Bug #817058 [src:sketch] sketch: FTBFS in stretch (TeX error)
Added tag(s) stretch and sid.
> found 816699 0.0~git20160222-1
Bug #816699 [libarmci-mpi-dev,libga-dev] libga-dev and libarmci-mpi-dev: error 
when trying to install together
There is no source info for the package 'libga-dev' at version 
'0.0~git20160222-1' with architecture ''
Marked as found in versions armci-mpi/0.0~git20160222-1.
> found 816699 5.4~beta~r10636+dfsg-2
Bug #816699 [libarmci-mpi-dev,libga-dev] libga-dev and libarmci-mpi-dev: error 
when trying to install together
There is no source info for the package 'libarmci-mpi-dev' at version 
'5.4~beta~r10636+dfsg-2' with architecture ''
Marked as found in versions ga/5.4~beta~r10636+dfsg-2.
> found 816737 2.21-9
Bug #816737 [libc6] Broken after recent upgrade
Marked as found in versions glibc/2.21-9.
> tags 816756 + sid stretch experimental
Bug #816756 [php-pimple] Useless in Debian
Added tag(s) stretch, sid, and experimental.
> tags 816757 + sid stretch
Bug #816757 {Done: Hilko Bengen } [lzop] lzop: Does not 
build on powerpc
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
813972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813972
816517: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816517
816518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816518
816561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816561
816587: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816587
816638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816638
816699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816699
816737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816737
816756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816756
816757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816757
816994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816994
816995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816995
816996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816996
817026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817026
817027: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817027
817058: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#784514: QWT

[Sebastiaan Couwenberg]

On 07-03-16 21:36, Lisandro Damián Nicanor Pérez Meyer wrote:
> On Friday 22 January 2016 17:52:08 Sebastiaan Couwenberg wrote:
>> On 22-01-16 17:03, Lisandro Damián Nicanor Pérez Meyer wrote:
>>> FWIW you also need Qt5's QWT. The packages are kind of ready in
>>> experimental but need a transition. I haven't heard of qwt's
>>> maintainer in almost two months. I'll try poking him...
>>
>> Yes, please!
> 
> Transition started today tracked in bug 817035 (CC). Please feel free to 
> either upload or ask us for a binNMU.

Thanks for getting the qwt transition moving.

I'm currently updating the QGIS 2.14.0 package in preparation for the
move to unstable, I can do the upload later this week.

Regarding the Qt4 WebKit removal, we unfortunately cannot switch QGIS to
Qt5 without having to disable a significant portion of its
functionality. Most importantly, the Python support had to be disabled
and is pretty essential for running most QGIS plugins. As discussed on
the debian-gis list recently [0], I'd like to stick to Qt4 a little
longer, at least until the 2.16 release which should have dual Qt4/Qt5
support.

[0] https://lists.debian.org/debian-gis/2016/02/msg00037.html

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



signature.asc
Description: OpenPGP digital signature

Bug#815131: marked as done (hg-git: FTBFS: Warning: test-empty-working-tree.t output changed)

[Debian Bug Tracking System]

Your message dated Mon, 7 Mar 2016 21:13:51 +
with message-id <20160307211351.GA4393@tesla>
and subject line Re: [Python-apps-team] Bug#815131: hg-git: FTBFS: Warning: 
test-empty-working-tree.t output changed
has caused the Debian Bug report #815131,
regarding hg-git: FTBFS: Warning: test-empty-working-tree.t output changed
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.)


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

hg-git fails to build from source in unstable/amd64:

  [..]

  Warning: test-empty-working-tree.t output changed
  ~.
  --- 
/home/lamby/temp/cdt.20160219084537.lF7QXmaCQo/hg-git-0.8.3/tests/test-help.t
  +++ 
/home/lamby/temp/cdt.20160219084537.lF7QXmaCQo/hg-git-0.8.3/tests/test-help.t.err
  @@ -7,6 +7,6 @@
  hggit push and pull from a Git server
  git Working with Git Repositories
 $ hg help hggit | grep 'help git' | sed 's/:hg:`help git`/"hg help git"/g'
  -  For more information and instructions, see "hg help git"
  +  For more information and instructions, see 'hg help git'
 $ hg help git | grep 'Working with Git Repositories'
 Working with Git Repositories
  
  Warning: test-help.t output changed
  ~warning: Tested with unexpected mercurial lib: 
/usr/lib/python2.7/dist-packages/mercurial
   (expected /usr/bin/mercurial)
  
  Warned test-git-submodules.t: output changed
  Warned test-renames.t: output changed
  Warned test-pull.t: output changed
  Warned test-file-removal.t: output changed
  Warned test-hg-author.t: output changed
  Warned test-bookmark-workflow.t: output changed
  Warned test-extra.t: output changed
  Warned test-push.t: output changed
  Warned test-octopus.t: output changed
  Warned test-encoding.t: output changed
  Warned test-subrepos.t: output changed
  Warned test-branch-bookmark-suffix.t: output changed
  Warned test-git-workflow.t: output changed
  Warned test-incoming.t: output changed
  Warned test-outgoing.t: output changed
  Warned test-hg-tags-invalid.t: output changed
  Warned test-pull-after-strip.t: output changed
  Warned test-hg-branch.t: output changed
  Warned test-clone.t: output changed
  Warned test-merge.t: output changed
  Warned test-hg-tags.t: output changed
  Warned test-convergedmerge.t: output changed
  Warned test-conflict-2.t: output changed
  Warned test-conflict-1.t: output changed
  Warned test-tree-decomposition.t: output changed
  Warned test-keywords.t: output changed
  Warned test-git-tags.t: output changed
  Warned test-git-clone.t: output changed
  Warned test-empty-working-tree.t: output changed
  Warned test-help.t: output changed
  # Ran 37 tests, 0 skipped, 30 warned, 0 failed.
  Makefile:12: recipe for target 'tests' failed
  make[2]: *** [tests] Error 80
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160219084537.lF7QXmaCQo/hg-git-0.8.3'
  debian/rules:13: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160219084537.lF7QXmaCQo/hg-git-0.8.3'
  debian/rules:9: 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
   `-


hg-git.0.8.3-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: hg-git
Source-Version: 0.8.5-2

On Fri, Feb 19, 2016 at 09:13:41AM +0100, Chris Lamb wrote:
> Source: hg-git
> Version: 0.8.3-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,
> 
> hg-git fails to build from source in unstable/amd64:
> 
>   [..]
> 
>   Warning: test-empty-working-tree.t output changed
>   ~.
>   --- 
> /home/lamby/temp/cdt.20160219084537.lF7QXmaCQo/hg-git-0.8.3/tests/test-help.t
>   +++ 
> /home/lamby/temp/cdt.20160219084537.lF7QXmaCQo/hg-git-0.8.3/tests/test-help.t.err
>   @@ -7,6 +7,6 @@
>   hggit push and pull from a Git server
>   git Working with Git Repositories
>  $ hg help hggit | grep 'help git' | sed 's/:hg:`help git`/"hg help 
> git"/g'
>   -  For more information and 

Bug#817071: Backup fails if sync_first is used and some files are modified while rsync runs

[Uli Schlachter]

Package: rsnapshot
Version: 1.4.1-1
Severity: grave
Tags: upstream patch

Hi,

I just noticed that my backups are broken since a while. rsnapshot happily makes
backups of an old state of its .sync directory. Symptoms on stderr are:

[snip]

rsnapshot encountered an error! The program was invoked with these options:
/usr/bin/rsnapshot sync 

ERROR: /usr/bin/rsync returned 0.09375 while processing /
WARNING: Rolling back "hdd/"
[/snip]

(Notice that it says it's Rolling back, thus I get lots of disk activity and
think that it does a backup. Also, the mtimes in the backup directory suggest as
well that everything works. Oh and I had this error in the past, too, without
any problems. Hence the severity.)

Google found the following upstream report on this bug:

 https://github.com/rsnapshot/sourceforge-issues/issues/8

And indeed I see in /usr/bin/rsnapshot that first in line 3921, result is set
via

  $result = $? >> 8;

and then line 3929 does (where the function get_retval() just divides by its
argument by 256). As you see in the output above, this results in $retval being
set to 0.09375.

  my $retval = get_retval($result);

The fix should be the following chunk of an otherwise weirdly wrong commit
upstream:

https://github.com/rsnapshot/rsnapshot/commit/778ab47d8eb4891f464677a0e26c38b186a376c8#diff-70276296f2bdcc3adb72b3d823d07361L3922

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

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

Versions of packages rsnapshot depends on:
ii  liblchown-perl  1.01-3+b1
ii  logrotate   3.8.7-2
ii  perl5.22.1-8
ii  rsync   3.1.1-3

Versions of packages rsnapshot recommends:
ii  openssh-client [ssh-client]  1:7.1p2-2

rsnapshot suggests no packages.

-- Configuration Files:
/etc/logrotate.d/rsnapshot changed:
/var/log/rsnapshot.log /var/log/rsnapshot {
rotate 6
monthly
compress
missingok
}

/etc/rsnapshot.conf changed:
config_version  1.2
snapshot_root   /media/backup/
no_create_root  1
cmd_cp  /bin/cp
cmd_rm  /bin/rm
cmd_rsync   /usr/bin/rsync
cmd_logger  /usr/bin/logger
cmd_du  /usr/bin/du
cmd_rsnapshot_diff  /usr/bin/rsnapshot-diff
retain  daily   8
retain  weekly  5
retain  monthly 12
verbose 2
loglevel3
logfile /var/log/rsnapshot.log
lockfile/var/run/rsnapshot.pid
exclude kuja.in_home
exclude /proc
exclude /sys
exclude /tmp
exclude /var/tmp
exclude .ccache
exclude /dev/.udev
exclude /dev/pts
exclude /dev/shm
exclude /var/cache
link_dest   1
sync_first  1
backup  /   hdd/


-- no debconf information

Processed: reassign 817063 to src:linux, severity of 817063 is important

[Debian Bug Tracking System]

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

> reassign 817063 src:linux 4.3.5-1
Bug #817063 [linux-image-4.3.0-1-powerpc64le] Severe performance regression in 
Infiniband or IPoIB
Bug reassigned from package 'linux-image-4.3.0-1-powerpc64le' to 'src:linux'.
No longer marked as found in versions linux/4.3.5-1.
Ignoring request to alter fixed versions of bug #817063 to the same values 
previously set
Bug #817063 [src:linux] Severe performance regression in Infiniband or IPoIB
Marked as found in versions linux/4.3.5-1.
> severity 817063 important
Bug #817063 [src:linux] Severe performance regression in Infiniband or IPoIB
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

[Jeff Breidenbach]

 jbreiden: Just report a transition bug for release.debian.org to
+transition back
 So they rebuild the stuff against the old ABI again

Bug#784514: QWT

[Lisandro Damián Nicanor Pérez Meyer]

On Friday 22 January 2016 17:52:08 Sebastiaan Couwenberg wrote:
> On 22-01-16 17:03, Lisandro Damián Nicanor Pérez Meyer wrote:
> > FWIW you also need Qt5's QWT. The packages are kind of ready in
> > experimental but need a transition. I haven't heard of qwt's
> > maintainer in almost two months. I'll try poking him...
> 
> Yes, please!

Transition started today tracked in bug 817035 (CC). Please feel free to 
either upload or ask us for a binNMU.

Thanks a lot Bas!


-- 
127.0.0.1 sweet 127.0.0.1

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

[Jeff Breidenbach]

Thanks for working with me and sorry about the trouble.
I don't know what you mean by not closing bug #815056
properly. The bug tracker says it is closed.

https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=tesseract

If I look at the package tracking system, it seems to be claiming
something else entirely as the culprit. Something that I don't
currently understand.

https://release.debian.org/migration/testing.pl?package=tesseract

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

[Jeff Breidenbach]

It must be mad that there is no libtesseract4 anymore. I'm going
to try to get help for that on IRC.

Bug#812087: [pcscd]

[Philippe Teuwen]

On 03/07/2016 07:34 PM, Ludovic Rousseau wrote:
> printf("fds: %d %d\n", fds[0].revents, fds[1].revents);

fds: 0 1
always

I also printed udev_dev from udev_monitor_receive_device()
it's always null

So we get fds[1].revents but don't get anything from
udev_monitor_receive_device() so it's looping forever.


You may try to trigger the bug from your side:
It probably requires the same versions as me.
kernel 4.3.0-1-amd64
libusb-1.0-02:1.0.20-1
libudev1229-2
I've a Yubikey neo-n plugged in.
I start pcscd.
I plug a usb hub (or anything else)
=> CPU at 100%

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

[rinni]

Hi Jeff,

thanks for your  effort! I think the problem right now is that 3.04.01-4
is still not in testing (I think you didn't close bug #815056 properly).
So making tesseract transition to testing would make the situation much
better. It might be, that I still have to rebuild gimagereader, as it was
build against -3, but let's deal with that later. Please just make sure
that tesseract -4 enters testing soon. (And please help to convince
upstream to move the function to baseapi.cpp again).

Best,
Philip


> Jeff Breidenbach  hat am 7. März 2016 um 20:56
> geschrieben:
> 
> 
> I'm in over my head, so I asked for help. The folks on debian-devel
> IRC channel advised me to not bump soname and instead attempt
> an ABI repair. It was supposed to be harmless to gimagereader.
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815056
> 
> I'm really not sure what to do at this point.  The Debian package
> is doing exactly what you asked for, unless I made a mistake.
> 
> https://github.com/tesseract-ocr/tesseract/issues/254

Bug#816638: mhonarc: fails to run with perl5.22

[Jeff Breidenbach]

Yikes. I wasn't expecting this for mhonarc 2.6.19.  Patches from a perl
programmer appreciated. Will also check with upstream.

Bug#813647: connman: daemon no longer starts after upgrade

[Kevin Velghe]

I guess so. There have been updates however on the git, but they were
never uploaded:
http://anonscm.debian.org/cgit/collab-maint/connman.git/tree/debian/changelog

Anyway, it seems an updated package is on it's way:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816542

On Mon, Mar 07, 2016 at 09:59:27PM +0330, Tsu Jan wrote:
> Isn't connman maintained anymore in Debian ?!
> 
> -- 
> To unsubscribe, send mail to 813647-unsubscr...@bugs.debian.org.


signature.asc
Description: Digital signature

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

[Jeff Breidenbach]

I'm in over my head, so I asked for help. The folks on debian-devel
IRC channel advised me to not bump soname and instead attempt
an ABI repair. It was supposed to be harmless to gimagereader.

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

I'm really not sure what to do at this point.  The Debian package
is doing exactly what you asked for, unless I made a mistake.

https://github.com/tesseract-ocr/tesseract/issues/254

Bug#813970: marked as done (dbus: purge fails: invoke-rc.d: initscript dbus, action "stop" failed.)

[Debian Bug Tracking System]

Your message dated Mon, 07 Mar 2016 19:49:22 +
with message-id 
and subject line Bug#813970: fixed in dbus 1.10.8-1
has caused the Debian Bug report #813970,
regarding dbus: purge fails: invoke-rc.d: initscript dbus, action "stop" failed.
to be marked as done.

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

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


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I cannot purge dbus package on my server:

(Læser database ... 104307 filer og kataloger installeret i øjeblikket.)
Afinstallerer dbus (1.8.20-0+deb8u1) ...
Job for dbus.service canceled.
invoke-rc.d: initscript dbus, action "stop" failed.
dpkg: fejl under behandling af pakken dbus (--purge):
 underproces installerede pre-removal-script returnerede afslutningsstatus 1
Der opstod fejl under behandlingen:
 dbus


 - Jonas

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWtvPYAAoJECx8MUbBoAEhx9QP/AppsKAuduB3uUQumOWKsDy6
HfiY2OupLX7RNyY+1eI60z4Lrqkh0DmO4wmO3InGgW6yJ32mYuTDgv4PcFlXxuNq
8CQuwIv+L46iy+6s0xoZN1Fs5hpaG9/wv7F6FgOLb1c/AE4LlPd2O5OWgDNHZJSy
XNEHzlfAJwcO78cnXG6VzzJiokn+oStQLVqvKLxMCLirHFvK28+coyfHaW6rxsf7
ke1X1NbqhuVjvhBa4nygZqwHv3q9KEUpMklzuYobPXJ0f2pAr7O+j9gPBsIg3bvT
zQJKZTHYBIqOWyoJ5ZDPkQBpXpzxC4g9FDGdfK4bmvVAK+ORRI4MVzmWZ4C0tLGQ
pyEQm9CSBBuEYKYl3hbVfoBmGMfEx7oI8XNhgL1y0ojcF9y2boBFvS+j79UKP6TG
s87171B+c5RLtTLa/ul3gU6lDqU5xMPuWtLt0d1pH5yPOC887YduHnBeSIgdBWEM
B+R+zqoxN1lX7NOjdX8pK6eXjqLXSi3aStz7t51K7DqMMNGZAXXX+bTkFcLVUHs8
Gu2opmxcf4VcVyaJ7odJ3Ev0ZUT7NUUCnz2MkeWQfrqWUgzIt12nRS4TgAQ/k6Dj
+E7LTsKRulMjPDjL4+LDXtL/+BPbHttoWxMA0KDPJyYluJUawdeu4/L0h/dPYyR1
XHm082GrYyU7b4pWR9Db
=pTWg
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: dbus
Source-Version: 1.10.8-1

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated dbus 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 19:15:47 +
Source: dbus
Binary: dbus dbus-1-dbg dbus-1-doc dbus-tests dbus-udeb dbus-user-session 
dbus-x11 libdbus-1-3 libdbus-1-3-udeb libdbus-1-dev
Architecture: source
Version: 1.10.8-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Simon McVittie 
Description:
 dbus   - simple interprocess messaging system (daemon and utilities)
 dbus-1-dbg - simple interprocess messaging system (debug symbols)
 dbus-1-doc - simple interprocess messaging system (documentation)
 dbus-tests - simple interprocess messaging system (test infrastructure)
 dbus-udeb  - simple interprocess messaging system (minimal runtime) (udeb)
 dbus-user-session - simple interprocess messaging system (systemd --user 
integration)
 dbus-x11   - simple interprocess messaging system (X11 deps)
 libdbus-1-3 - simple interprocess messaging system (library)
 libdbus-1-3-udeb - simple interprocess messaging system (minimal library) 
(udeb)
 libdbus-1-dev - simple interprocess messaging system (development headers)
Closes: 813970 815503
Changes:
 dbus (1.10.8-1) unstable; urgency=medium
 .
   * New upstream release
   * dbus.prerm: ensure that dbus.socket is stopped before removal,
 so that a new connection to the bus won't cause dbus.service to be
 restarted (Closes: #813970)
   * debian/75dbus_dbus-launch: when not using systemd --user or the
 dbus-user-session package is not installed, start dbus-daemon early,
 then upload the full environment from Xsession.d later on
 (in 95dbus_update-activation-env). This more closely matches the
 behaviour with dbus-user-session. (Closes: #815503; thanks to Samuel
 Thibault)
   * Switch Vcs-Git to https (see #810378)
   * debian/upstream/signing-key.asc: add upstream signing keys
 (just my keys for now, in practice I do 

Processed: your mail

[Debian Bug Tracking System]

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

> severity 817063 serious
Bug #817063 [linux-image-4.3.0-1-powerpc64le] Severe performance regression in 
Infiniband or IPoIB
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> retitle 816997 Replace swig2.0 by swig in BD
Bug #816997 [src:gmsh] gmsh: FTBFS in stretch, build dependencies not in stretch
Changed Bug title to 'Replace swig2.0 by swig in BD' from 'gmsh: FTBFS in 
stretch, build dependencies not in stretch'
> severity 816997 important
Bug #816997 [src:gmsh] Replace swig2.0 by swig in BD
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: severity of 812335 is important

[Debian Bug Tracking System]

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

> severity 812335 important
Bug #812335 [pocketsphinx] pocketsphinx: FTBFS on mipsel/mips64el: testsuite 
failures
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#812087: [pcscd]

[Ludovic Rousseau]

Le 07/03/2016 10:21, Philippe Teuwen a écrit :

I recompiled libusb with debug symbols:


Normal CPU:

Thread 5 (Thread 0x7f0238fcb700 (LWP 24364)):
#0  0x7f02394dfb6d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f0238fdbafc in poll (__timeout=-1, __nfds=2,
__fds=0x7f0238fcaee0)
 at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  linux_udev_event_thread_main (arg=)
 at ../../libusb/os/linux_udev.c:175
#3  0x7f02397ab284 in start_thread (arg=0x7f0238fcb700)
 at pthread_create.c:333
#4  0x7f02394e8a4d in clone ()
 at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

100% CPU:

Thread 5 (Thread 0x7fbeac2a4700 (LWP 24181)):
#0 0x7fbeaca8cbdd in recvmsg () at ../sysdeps/unix/syscall-template.S:81
#1 0x7fbead2806ec in udev_monitor_receive_device ()
from /lib/x86_64-linux-gnu/libudev.so.1
#2 0x7fbeac2b4b8b in linux_udev_event_thread_main (arg=)
at ../../libusb/os/linux_udev.c:186
#3 0x7fbeaca84284 in start_thread (arg=0x7fbeac2a4700)
at pthread_create.c:333
#4 0x7fbeac7c1a4d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109



So the diff happens in that code from libusb/os/linux_udev.c:



usbi_dbg("udev event thread entering.");
while (poll(fds, 2, -1) >= 0) {
if (fds[0].revents & POLLIN) {
r = usbi_read(udev_control_pipe[0], , sizeof(dummy));
if (r <= 0) {
usbi_warn(NULL, "udev control pipe read failed");
}
break;
}
if (fds[1].revents & POLLIN) {
usbi_mutex_static_lock(_hotplug_lock);
udev_dev = udev_monitor_receive_device(udev_monitor);
if (udev_dev)
udev_hotplug_event(udev_dev);
usbi_mutex_static_unlock(_hotplug_lock);
}
}
usbi_dbg("udev event thread exiting");


I added error msgs in the loop.
When 100% CPU, the poll() is non-blocking and the loop becomes a busy loop.


Great.
I reported the problem on the libusb mailing list 
https://sourceforge.net/p/libusb/mailman/message/34914342/

Do you know a sequence of manipulations that triggers the bug?
I would like to reproduce the bug on my side.


Can you change the code of libusb to display the values fds[0].revents and 
fds[1].revents
Something like:
--- /tmp/XP5vZa_linux_udev.c2016-03-07 19:32:06.353701710 +0100
+++ libusb/os/linux_udev.c  2016-03-07 19:31:56.613374793 +0100
@@ -173,6 +173,7 @@ static void *linux_udev_event_thread_mai
usbi_dbg("udev event thread entering.");
 
while (poll(fds, 2, -1) >= 0) {

+   printf("fds: %d %d\n", fds[0].revents, fds[1].revents);
if (fds[0].revents & POLLIN) {
/* activity on control pipe, read the byte and exit */
r = usbi_read(udev_control_pipe[0], , sizeof(dummy));

What is the result when the problem occurs?

Bye

--
Dr. Ludovic Rousseau

Bug#816997: gmsh: FTBFS in stretch, build dependencies not in stretch

[Anton Gladky]

retitle 816997 Replace swig2.0 by swig in BD
severity 816997 important
thanks

Ok, thanks for clarification. Will fix it in next upload.

Cheers

Anton

Anton


2016-03-07 19:30 GMT+01:00 Julien Cristau :
> On Mon, Mar  7, 2016 at 19:23:41 +0100, Anton Gladky wrote:
>
>> Hi Santiago,
>>
>> thanks for the bug report. AFAIK the unsatisfied build dependencies
>> can only be a serious bug for the sid. In sid gmsh builds just fine.
>> Please close this bug.
>>
> No, Santiago's right, swig2.0 is replaced by swig, so your build-deps
> need fixing.  I'd have expected the swig maintainer to handle this...
>
> Cheers,
> Julien

Bug#816997: gmsh: FTBFS in stretch, build dependencies not in stretch

[Julien Cristau]

On Mon, Mar  7, 2016 at 19:23:41 +0100, Anton Gladky wrote:

> Hi Santiago,
> 
> thanks for the bug report. AFAIK the unsatisfied build dependencies
> can only be a serious bug for the sid. In sid gmsh builds just fine.
> Please close this bug.
> 
No, Santiago's right, swig2.0 is replaced by swig, so your build-deps
need fixing.  I'd have expected the swig maintainer to handle this...

Cheers,
Julien

Bug#813647: connman: daemon no longer starts after upgrade

[Tsu Jan]

Isn't connman maintained anymore in Debian ?!

Bug#816857: Submitted bug upstream

[Manolo Díaz]

On Mon, 7 Mar 2016 16:36:49 +0100
Philip Rinn wrote:

> Hi,
> 
> I just want to keep you in the loop: I filed a bug upstream to solve this at 
> the 
> bottom of the problem:
> 
> https://github.com/tesseract-ocr/tesseract/issues/254
> 
> Best,
> Philip

Thanks Philip.

Kind regards,
-- 
Manolo Díaz

Bug#816997: gmsh: FTBFS in stretch, build dependencies not in stretch

[Anton Gladky]

Hi Santiago,

thanks for the bug report. AFAIK the unsatisfied build dependencies
can only be a serious bug for the sid. In sid gmsh builds just fine.
Please close this bug.

Anton


2016-03-07 1:10 GMT+01:00 Santiago Vila :
> Package: src:gmsh
> Version: 2.11.0+dfsg1-2
> Severity: serious

Bug#816742: marked as done (libc6: sem_post/sem_wait not working for 32bit to 64bit inter-process communication)

[Debian Bug Tracking System]

Your message dated Mon, 7 Mar 2016 18:41:07 +0100
with message-id <20160307174107.ga29...@aurel32.net>
and subject line Re: Bug#816742: libc6: sem_post/sem_wait not working for 32bit 
to 64bit inter-process communication
has caused the Debian Bug report #816742,
regarding libc6: sem_post/sem_wait not working for 32bit to 64bit inter-process 
 communication
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.)


-- 
816742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.21
Severity: critical
Justification: breaks unrelated software

Inter-process communication between a 64bit and a 32bit process is not
working. At least pthread named semaphores are not working.
A sem_wait is not awaken if a corresponding sem_post is done on the other
side, which generated a dead lock.

This problem only exists if a 64bit process communicates with a 32bit
process but not for 32bit to 32bit communication or 64bit to 64bit
communication.
Moreover Debian 8.3 and all other tested distributions have no problem with
64bit to 32bit inter-process communication using pthread named semaphores.

The problem seems to be related to the (new) FUTEX_PRIVATE_FLAG flag of
futex. The sem_post command (for a named semaphore) seems to make a futex
system call using the FUTEX_PRIVATE_FLAG which seems to be wrong.

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On 2016-03-05 08:46, Carlos O'Donell wrote:
> On Sat, Mar 5, 2016 at 7:28 AM, Aurelien Jarno  wrote:
> > control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=17980
> 
> Semaphore interoperability between two different ABIs has never been
> supported. It worked because you were lucky and the implementation was
> flawed. To fix the implementation flaws (which are real), we've had to
> adopt slightly different algorithms for 32-bit and 64-bit.

Given this was something not officially supported, but only working by
chance, we can't consider that as a regression. I am therefore closing
the bug.

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

Bug#815062: marked as done (openttd-openmsx: FTBFS: override_dh_auto_test [..] Differences in md5sums)

[Debian Bug Tracking System]

Your message dated Mon, 07 Mar 2016 17:33:33 +
with message-id 
and subject line Bug#815062: fixed in openttd-openmsx 0.3.1-4
has caused the Debian Bug report #815062,
regarding openttd-openmsx: FTBFS: override_dh_auto_test [..] Differences in 
md5sums
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.)


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

openttd-openmsx fails to build from source in unstable/amd64:

  [..]

   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: source package openttd-openmsx
  dpkg-buildpackage: source version 0.3.1-3
  dpkg-buildpackage: source distribution unstable
  dpkg-buildpackage: source changed by Matthijs Kooijman 
   dpkg-source --before-build openttd-openmsx-0.3.1
  dpkg-buildpackage: host architecture amd64
   fakeroot debian/rules clean
  dh  clean
 dh_testdir
 debian/rules override_dh_auto_clean
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160218105550.q49Y2v5K53/openttd-openmsx-0.3.1'
  # Don't use dh_auto_clean. It thinks any target is valid because
  # it generates output (dependency analysis) before erroring out.
  make distclean
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160218105550.q49Y2v5K53/openttd-openmsx-0.3.1'
  Version change detected. Re-build forced.
  
  [Generating] Makefile.dep
  [Cleaning]
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160218105550.q49Y2v5K53/openttd-openmsx-0.3.1'
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160218105550.q49Y2v5K53/openttd-openmsx-0.3.1'
 dh_clean
   debian/rules build
  dh  build
 dh_testdir
 dh_update_autotools_config
 dh_auto_configure
 debian/rules override_dh_auto_build
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160218105550.q49Y2v5K53/openttd-openmsx-0.3.1'
  make  
"INSTALL_DIR=debian/openttd-openmsx/usr/share/games/openttd/baseset/openmsx" 
"UNIX2DOS=" "_V="
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160218105550.q49Y2v5K53/openttd-openmsx-0.3.1'
  Version change detected. Re-build forced.
  [ -e *.REV ] && rm *.REV || echo ""
  
  touch openmsx-0.3.1.REV
  [Generating] Makefile.dep
  for i in `: st -A | grep -v  "^I" | grep -v "^?" | grep -v "^R" | grep -v 
"^\!" | cut -d\  -f2 | grep -E '(list|grf)$'`; do echo "$i: "`for j in list 
mid; do cat $i |  grep -v '^//' | grep -o "[a-zA-Z0-9/_.-]\+\.$j" | sort | 
uniq; done` | grep -v -E ": $" ; done | sort | uniq | awk '{ print $0"\n\t$(_V) 
touch $@" }' > Makefile.dep
  for i in `ls Makefile* scripts/* | grep -v Makefile.dep`; do echo 
"Makefile.dep: $i"; done >> Makefile.dep
  [ -e openmsx-0.3.1.REV ] && [ "`cat openmsx-0.3.1.REV`" = "0.3.1" ] || echo 
"0.3.1" > openmsx-0.3.1.REV
  make  -f Makefile openmsx.obm
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160218105550.q49Y2v5K53/openttd-openmsx-0.3.1'
  [Generating] openmsx.obm
  cat docs/descriptions.ptxt | grep -E '^description' | sed 's/$/ [OpenMSX 
0.3.1]/' >> openmsx.obm
  cat src/themes.list | scripts/playlist.py >> openmsx.obm
  cat src/themes.list | scripts/sanitize_list.py | scripts/md5list.py >> 
openmsx.obm
  cat src/themes.list | scripts/sanitize_list.py | scripts/namelist.py >> 
openmsx.obm
  [Done] Basesound successfully generated.
  
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160218105550.q49Y2v5K53/openttd-openmsx-0.3.1'
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160218105550.q49Y2v5K53/openttd-openmsx-0.3.1'
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160218105550.q49Y2v5K53/openttd-openmsx-0.3.1'
 debian/rules override_dh_auto_test
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160218105550.q49Y2v5K53/openttd-openmsx-0.3.1'
  # Check md5sums of files. This isn't really useful (mostly meant
  # for use with opengfx), but we'll have to override dh_auto_test
  # anyway (since make test generates debug output), so we might
  # as well call make check.
  make check  
"INSTALL_DIR=debian/openttd-openmsx/usr/share/games/openttd/baseset/openmsx" 
"UNIX2DOS=" "_V="
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160218105550.q49Y2v5K53/openttd-openmsx-0.3.1'
  if [ -f openmsx-0.3.1.md5 ]; then echo "[CHECKING md5sums]"; else echo 
"Required file 

Bug#817057: network-manager-openconnect: Update unstable version to latest Upstream Build

[Michael Stapelberg]

On Mon, Mar 7, 2016 at 9:07 AM, Ryan Chewning  wrote:

> Package: network-manager-openconnect
> Version: 1.0.2-1+b1
> Severity: grave
> Tags: upstream
> Justification: renders package unusable
>
> The latest builds of networkmanager in testing/unstable no longer support
> dbus. https://blogs.gnome.org/dcbw/2016/02/19/die-dbus-glib-die/
>

I’m only a bystander for the purpose of this bug, but “networkmanager […]
no longer supports dbus” conflicts with the article you refer to, which
mentions:

"""
I cannot understate how much work this was and how much careful planning we
(well, mostly Dan Winship) did to ensure we didn’t break backwards
compatibility of either the utility libraries or the D-Bus interface.
"""

The way I read this, the new networkmanager version is backwards-compatible
with regards to its D-Bus interface.

Can you clarify? If it turns out that it’s actually backwards-compatible,
is severity: grave still justified?


> There is an updated version of the network-manager-openconnect but it is
> failing to be pulled down by uscan. Manual intervention is needed.
>
> Thanks,
>
> Ryan
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing-updates
>   APT policy: (500, 'testing-updates'), (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages network-manager-openconnect depends on:
> ii  adduser   3.113+nmu3
> ii  libc6 2.21-9
> ii  libdbus-1-3   1.10.6-1
> ii  libdbus-glib-1-2  0.106-1
> ii  libglib2.0-0  2.46.2-3
> ii  libnm-glib-vpn1   1.1.90-6
> ii  libnm-glib4   1.1.90-6
> ii  libnm-util2   1.1.90-6
> ii  network-manager   1.1.90-6
> ii  openconnect   7.06-2+b2
>
> network-manager-openconnect recommends no packages.
>
> network-manager-openconnect suggests no packages.
>
> -- no debconf information
>
>


-- 
Best regards,
Michael

Bug#817058: sketch: FTBFS in stretch (TeX error)

[Santiago Vila]

Package: src:sketch
Version: 1:0.3.7-1
Severity: serious

Dear maintainer:

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

The error, however, seems to happen with ordinary "dpkg-buildpackage"
as well, which is why I'm using "serious" severity here. See

https://reproducible.debian.net/rbuild/testing/amd64/sketch_0.3.7-1.rbuild.log

for the build log from the reproducible builds effort.


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
perl makever.pl

[... snipped ...]

Transcript written on mfput.log.
grep: ecrm1440.log: No such file or directory
mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input 
ecrm1440' failed to make ecrm1440.tfm.
kpathsea: Appending font creation commands to missfont.log.

./sketch.texi:3327: Font \thisecfont=ecrm1440 at 14.0pt not loadable: Metric (T
FM) file not found.
 
   \thisecfont 
\indexlbrace ->{\ifmonospace \else \ecfont 
   \fi \char 123}
 ... \kern -0.05em \secbf {\indexlbrace 
  }
\leftline #1->\line {#1
   \hss }
\initialx ...e {\secfonts \kern -0.05em \secbf #1}
  \nobreak \vskip .33\baseli...

\thisline ->\initial {{\indexlbrace }}
   
...
l.3327 @printindex sx
 
? 
./sketch.texi:3327: Emergency stop.
 
   \thisecfont 
\indexlbrace ->{\ifmonospace \else \ecfont 
   \fi \char 123}
 ... \kern -0.05em \secbf {\indexlbrace 
  }
\leftline #1->\line {#1
   \hss }
\initialx ...e {\secfonts \kern -0.05em \secbf #1}
  \nobreak \vskip .33\baseli...

\thisline ->\initial {{\indexlbrace }}
   
...
l.3327 @printindex sx
 
Output written on sketch.dvi (44 pages, 150420 bytes).
Transcript written on sketch.log.
/usr/bin/texi2dvi: etex exited with bad status, quitting.
Died at make.pl line 87,  line 3335.
debian/rules:27: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
debian/rules:21: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2



Apparently, this happened to work in the past and it does no longer
because of some new texlive package being used, it seems.

[ So I'll omit the standard blurb I add to these kind of bugs ]

Thanks.

Bug#817059: vagrant: domain_name gem not found

[Guy Hughes]

Package: vagrant
Version: 1.8.1+dfsg-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

Until #817011 on ruby-domain-name is fixed by the maintainer, vagrant
does not work without a manual fix (gemspec file) available in the bts
report.[1] See below.

I'm reporting this against your package for the benefit of others,
especially those using virtualbox from sid.

Guy Hughes

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817011

$ vagrant
Vagrant experienced a version conflict with some installed plugins!
This usually happens if you recently upgraded Vagrant. As part of the
upgrade process, some existing plugins are no longer compatible with
this version of Vagrant. The recommended way to fix this is to remove
your existing plugins and reinstall them one-by-one. To remove all
plugins:

rm -r ~/.vagrant.d/plugins.json ~/.vagrant.d/gems

Note if you have an alternate VAGRANT_HOME environmental variable
set, the folders above will be in that directory rather than your
user's home directory.

The error message is shown below:

Bundler could not find compatible versions for gem "domain_name":
  In Gemfile:
vagrant (= 1.8.1) was resolved to 1.8.1, which depends on
  rest-client (< 2.0, >= 1.6.0) was resolved to 1.8.0, which depends on
http-cookie (< 2.0, >= 1.0.2) was resolved to 1.0.2, which depends on
  domain_name (~> 0.5)

Could not find gem 'domain_name (~> 0.5)', which is required by gem 
'http-cookie (< 2.0, >= 1.0.2)', in any of the sources.
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJW3bWUAAoJEP5VHtX/6ko8rYIP/1IsuCxSQUi5ifmyxaxxhN3j
Hk+fa73j/nAWXPI/in4lky+heiWwbstvgvoir5zK9fftQAv58q6h/d1ExIvsqHei
ZfNdVJKFE0DYSCxjJYS6a33xof7/WhuhoE33kThuvbuinwnMOh4i5XN+x3Pr9KPx
mD7zBUDhbiEsbLYFguo1rpz6b05bkJD+NLbhgVSQ0z1G54AQPze9ZUfAqRmtgkWW
wU6p67zDWSn0E1NyRUPDOo8al7bXaqZ++D6B70Psk+7yxxaZF3HzqjSZUDRcgjMK
8f+4e4lQHccFJSAvdz0RRXMWUm+egVDpRSex71he4Z14g6MDoPUsodU3gvI4ns5M
sLrL2+q8r/UeDaVNEsJSQY1Igot+jQt0e8P1gsOxbaCM//SoW+1dqa9Hfza9HfQX
2D4TAXAamdxWvzBdViKCp4+8Dj4MfFBMrtyT3vWaJ/C80X5GyEQDNb9TEL2Owvvv
zxbG4i4D/bqLMFrEBB59q4u3V9XCFjh069fIMHVkgU60Lu3kVIZFQyhNUVlRtmfL
SOHoJfp1OQJEBH+ZPY/wx06BgR0xDKmz2cSf2C8heHkMberBrOvKrawHhIa4gqB+
iBhPAoMMzpaUThZkBMPAD8XvdhkkA1mxnB5zNbVLT+O/tBk7xF5YqlV5QYqLJBsj
PO0cwls0qMxPJftBuOr1
=7KLp
-END PGP SIGNATURE-

Bug#817057: network-manager-openconnect: Update unstable version to latest Upstream Build

[Ryan Chewning]

Package: network-manager-openconnect
Version: 1.0.2-1+b1
Severity: grave
Tags: upstream
Justification: renders package unusable

The latest builds of networkmanager in testing/unstable no longer support
dbus. https://blogs.gnome.org/dcbw/2016/02/19/die-dbus-glib-die/
There is an updated version of the network-manager-openconnect but it is
failing to be pulled down by uscan. Manual intervention is needed.

Thanks,

Ryan

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

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

Versions of packages network-manager-openconnect depends on:
ii  adduser   3.113+nmu3
ii  libc6 2.21-9
ii  libdbus-1-3   1.10.6-1
ii  libdbus-glib-1-2  0.106-1
ii  libglib2.0-0  2.46.2-3
ii  libnm-glib-vpn1   1.1.90-6
ii  libnm-glib4   1.1.90-6
ii  libnm-util2   1.1.90-6
ii  network-manager   1.1.90-6
ii  openconnect   7.06-2+b2

network-manager-openconnect recommends no packages.

network-manager-openconnect suggests no packages.

-- no debconf information

Bug#817012: marked as done (ruby-amqp and ruby-amq-client: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Mon, 07 Mar 2016 16:46:18 +
with message-id 
and subject line Bug#817012: fixed in ruby-amqp 1.5.1-2
has caused the Debian Bug report #817012,
regarding ruby-amqp and ruby-amq-client: 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.)


-- 
817012: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-amq-client,ruby-amqp
Version: ruby-amq-client/1.0.4-1
Version: ruby-amqp/1.5.1-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-03-07
Architecture: amd64
Distribution: sid

Hi,

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


Preconfiguring packages ...
Selecting previously unselected package libyaml-0-2:amd64.
(Reading database ... 10939 files and directories currently installed.)
Preparing to unpack .../libyaml-0-2_0.1.6-3_amd64.deb ...
Unpacking libyaml-0-2:amd64 (0.1.6-3) ...
Selecting previously unselected package gcc-5-base:amd64.
Preparing to unpack .../gcc-5-base_5.3.1-10_amd64.deb ...
Unpacking gcc-5-base:amd64 (5.3.1-10) ...
Setting up gcc-5-base:amd64 (5.3.1-10) ...
(Reading database ... 10953 files and directories currently installed.)
Preparing to unpack .../libstdc++6_5.3.1-10_amd64.deb ...
Unpacking libstdc++6:amd64 (5.3.1-10) over (4.8.2-19) ...
Processing triggers for libc-bin (2.21-9) ...
Setting up libstdc++6:amd64 (5.3.1-10) ...
Processing triggers for libc-bin (2.21-9) ...
Selecting previously unselected package libssl1.0.2:amd64.
(Reading database ... 10967 files and directories currently installed.)
Preparing to unpack .../libssl1.0.2_1.0.2g-1_amd64.deb ...
Unpacking libssl1.0.2:amd64 (1.0.2g-1) ...
Selecting previously unselected package openssl.
Preparing to unpack .../openssl_1.0.2g-1_amd64.deb ...
Unpacking openssl (1.0.2g-1) ...
Selecting previously unselected package ca-certificates.
Preparing to unpack .../ca-certificates_20160104_all.deb ...
Unpacking ca-certificates (20160104) ...
Selecting previously unselected package libffi6:amd64.
Preparing to unpack .../libffi6_3.2.1-4_amd64.deb ...
Unpacking libffi6:amd64 (3.2.1-4) ...
Selecting previously unselected package libgmp10:amd64.
Preparing to unpack .../libgmp10_2%3a6.1.0+dfsg-2_amd64.deb ...
Unpacking libgmp10:amd64 (2:6.1.0+dfsg-2) ...
Selecting previously unselected package rubygems-integration.
Preparing to unpack .../rubygems-integration_1.10_all.deb ...
Unpacking rubygems-integration (1.10) ...
Selecting previously unselected package ruby-did-you-mean.
Preparing to unpack .../ruby-did-you-mean_1.0.0-2_all.deb ...
Unpacking ruby-did-you-mean (1.0.0-2) ...
Selecting previously unselected package ruby-minitest.
Preparing to unpack .../ruby-minitest_5.8.4-2_all.deb ...
Unpacking ruby-minitest (5.8.4-2) ...
Selecting previously unselected package ruby-net-telnet.
Preparing to unpack .../ruby-net-telnet_0.1.1-2_all.deb ...
Unpacking ruby-net-telnet (0.1.1-2) ...
Selecting previously unselected package ruby-power-assert.
Preparing to unpack .../ruby-power-assert_0.2.7-1_all.deb ...
Unpacking ruby-power-assert (0.2.7-1) ...
Selecting previously unselected package ruby-test-unit.
Preparing to unpack .../ruby-test-unit_3.1.7-2_all.deb ...
Unpacking ruby-test-unit (3.1.7-2) ...
Selecting previously unselected package libruby2.3:amd64.
Preparing to unpack .../libruby2.3_2.3.0-4_amd64.deb ...
Unpacking libruby2.3:amd64 (2.3.0-4) ...
Selecting previously unselected package ruby2.3.
Preparing to unpack .../ruby2.3_2.3.0-4_amd64.deb ...
Unpacking ruby2.3 (2.3.0-4) ...
Selecting previously unselected package ruby.
Preparing to unpack .../ruby_1%3a2.3.0+1_all.deb ...
Unpacking ruby (1:2.3.0+1) ...
Selecting previously unselected package rake.
Preparing to unpack .../archives/rake_10.5.0-2_all.deb ...
Unpacking rake (10.5.0-2) ...
Selecting previously unselected package ruby-eventmachine.
Preparing to unpack .../ruby-eventmachine_1.0.7-3+b4_amd64.deb ...
Unpacking ruby-eventmachine (1.0.7-3+b4) ...
Selecting previously unselected package ruby-amq-protocol.
Preparing to unpack .../ruby-amq-protocol_1.9.2-2_all.deb ...
Unpacking ruby-amq-protocol (1.9.2-2) ...
Selecting previously unselected package ruby-amq-client.
Preparing to unpack .../ruby-amq-client_1.0.4-1_all.deb ...
Unpacking ruby-amq-client (1.0.4-1) ...
Selecting previously unselected package ruby-amqp.
Preparing to unpack 

Bug#816376: Unfit upstream

[Sébastien Villemot]

Dear David,

First, let me thank you for the work that you put into packaging
owncloud for Debian, it is really appreciated.

On Tue, 1 Mar 2016 07:07:10 -0400 David =?iso-8859-1?Q?Pr=E9vot?= 
 wrote:

> Upstream doesn’t wish to see their software in Debian anymore. Unless
> the situation changes in the next few months, owncloud will not be part
> of Stretch.

Given that owncloud is such a useful and important package, and that
there is currently no credible alternative, this is really sad news, and
I am wondering whether this outcome could be avoided.

If I understand correctly, your decision is essentially based on social
issues (upstream hostile to Debian packaging), coupled to some technical
aspects (complex upgrade paths).

At first glance, this does not seem to prevent the package from staying
in Debian. Maybe this just means that the package needs a new
maintainer, who is willing to handle the tough interaction with upstream
and dealing with the technical issues (note that I am not applying for
the job).

You are certainly in a better position than me to ascertain whether the
package can stay in Debian or not, but I think that it would be useful
if you could give a little more background on the issues that you
encountered. And, if you think it makes sense to orphan the package,
that would help prospective new maintainers in making the decision to
adopt the package or not.

Cheers,

-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594

Bug#812638: marked as done (gbirthday: FTBFS - build-depends on non-existent package python-support)

[Debian Bug Tracking System]

Your message dated Mon, 07 Mar 2016 16:22:17 +
with message-id 
and subject line Bug#812638: fixed in gbirthday 0.6.10-0.1
has caused the Debian Bug report #812638,
regarding gbirthday: FTBFS - build-depends on non-existent package 
python-support
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.)


-- 
812638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gbirthday
Version: 0.6.7-1
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
 -> Considering build-dep python-support
   -> Trying python-support
   -> Cannot install python-support; apt errors follow:
Reading package lists...
Building dependency tree...
Reading state information...
Package python-support is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'python-support' has no installation candidate
E: Could not satisfy build-dependency.


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


gbirthday-build-log.txt.gz
Description: application/gunzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: gbirthday
Source-Version: 0.6.10-0.1

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated gbirthday 
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, 02 Mar 2016 15:09:20 +0100
Source: gbirthday
Binary: gbirthday
Architecture: source
Version: 0.6.10-0.1
Distribution: unstable
Urgency: medium
Maintainer: Rolf Leggewie 
Changed-By: Gianfranco Costamagna 
Description:
 gbirthday  - birthday reminder applet
Closes: 812638
Changes:
 gbirthday (0.6.10-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Upload to unstable.
   * New upstream release (Closes: #812638)
   * Bump Standards-Version to 3.9.7: no changes needed.
   * Drop patch remove-too-early-import: upstream
Checksums-Sha1:
 db3bc5ffe20c9166521506832d603a47678c93cc 1911 gbirthday_0.6.10-0.1.dsc
 3699c70e1977ed6e3e8e0d490ba2849f53851842 74873 gbirthday_0.6.10.orig.tar.gz
 bcb8111af5f538c04778ef2c0f3b2fccb34262b1 3816 
gbirthday_0.6.10-0.1.debian.tar.xz
Checksums-Sha256:
 0f0b621a7bae0075c659b6d8852733797030c635440b78cebb2e9ebd668f557b 1911 
gbirthday_0.6.10-0.1.dsc
 ff4e4aa08d4fe4a72b4d95a58e223f9e80aabe98fb9335e7c01ef65bc167bc67 74873 
gbirthday_0.6.10.orig.tar.gz
 a484ca5dec60dc2de7302cddeeac5885e2707fdfa2ba31f5e2a520ea2f1bcf59 3816 
gbirthday_0.6.10-0.1.debian.tar.xz
Files:
 5a659a725b39a16f27ce4fb9396d21d4 1911 gnome extra gbirthday_0.6.10-0.1.dsc
 0924f095b64f91bc63948943cdf80a49 74873 gnome extra gbirthday_0.6.10.orig.tar.gz
 a341d2f0444147d71014cc90d49dbb0e 3816 gnome extra 
gbirthday_0.6.10-0.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJW1vSwAAoJEPNPCXROn13ZBVgP/125fU09GNb4XRsjnkUH6Uif
E/QDJdr1VqCx3Yo5FZD/qJq+pnM/ydV0RTAqCYEk2q3/+6YZheSRdn9V1IW2JFCB
5ojdXs+7udGPWpxapP1A9SN68zBbQ4lzlCMOLqmjElePSKmPGNIS5xtE4eZlJ0ra
1xcxTLkPlcxyPup0ZTXUFQ4RJ1LAqzgYsq5v2s4sy0ZaaRy2bmmTrW+Evz3wy2NZ
vcuW8cO5yGAvLAf9z7mJfq7q2jxxCYk43w3QdP0+WYXR9fUEahNGp29q8OeQfKIZ
7I6nyyEHzYyOag0oEyhzpFA34cDynxMaDO6tzTGYbqgHuMh6kEWPLSxgrqO15skr
xBWVKrEUSjhl71KUUHGN+JdSfJwXBfxrDH8INrstccuORcleODTGkvaNMdVjsmc+
sKZux+IttX6H0sHB5GRnAM12+jHnjCCjCpXG8vnimsmdTJHUEeTwt8LKaB7+7edn
J1/FZafV7TnKfB8ZP2z/RaF86i/zGu4UX0KlKhCJUQhhq1sVqsA/YhEcnmMfk3XK
z1/fmnbrqPy0IzqstlkQcM6a2ALS2FWv0UcrsKg0jQIM1e5Dym61g7l1Tlf9wYds
a52/USvwLuIjWmetMhCXTBVOha/GekWBb5/V7NOxc9AK/Ob8QMJQp7ymDjJmK96g
iuHVwwa7h9a26zx9j8/P
=kN2m
-END PGP SIGNATURE End 

Processed: retitle 815125 to Boot failure in 4.4 related to EFI run-time calls, forcibly merging 815125 816157

[Debian Bug Tracking System]

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

> retitle 815125 Boot failure in 4.4 related to EFI run-time calls
Bug #815125 [src:linux] linux-image-4.4.0-1-amd64 fails to load initrd - no 
booting
Bug #815779 [src:linux] linux-image-4.4.0-1-amd64: Recent kernels freeze after 
loading initramfs on HP HBook 80
Changed Bug title to 'Boot failure in 4.4 related to EFI run-time calls' from 
'linux-image-4.4.0-1-amd64 fails to load initrd - no booting'
Changed Bug title to 'Boot failure in 4.4 related to EFI run-time calls' from 
'linux-image-4.4.0-1-amd64: Recent kernels freeze after loading initramfs on HP 
HBook 80'
> forcemerge 815125 816157
Bug #815125 [src:linux] Boot failure in 4.4 related to EFI run-time calls
Bug #815779 [src:linux] Boot failure in 4.4 related to EFI run-time calls
Bug #816157 [src:linux] linux-image-4.4.0-1-amd64: Lenovo Ideapad Y700 failts 
to boot
Set Bug forwarded-to-address to 'm...@codeblueprint.co.uk'.
Severity set to 'critical' from 'important'
Marked as found in versions linux/4.4.2-2 and linux/4.4.2-1.
Added tag(s) moreinfo and upstream.
Bug #815779 [src:linux] Boot failure in 4.4 related to EFI run-time calls
Merged 815125 815779 816157
> thanks
Stopping processing here.

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

Bug#816857: Submitted bug upstream

[Philip Rinn]

Hi,

I just want to keep you in the loop: I filed a bug upstream to solve this at 
the 
bottom of the problem:

https://github.com/tesseract-ocr/tesseract/issues/254

Best,
Philip


signature.asc
Description: PGP signature

Processed: Re: linux-image-4.4.0-trunk-686-pae: sdhci module repeatedly crashes, eventually brings whole system down

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #815298 [src:linux] linux-image-4.4.0-trunk-686-pae: sdhci module 
repeatedly crashes, eventually brings whole system down
Severity set to 'important' from 'grave'
> tag -1 moreinfo
Bug #815298 [src:linux] linux-image-4.4.0-trunk-686-pae: sdhci module 
repeatedly crashes, eventually brings whole system down
Added tag(s) moreinfo.

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

Bug#815298: linux-image-4.4.0-trunk-686-pae: sdhci module repeatedly crashes, eventually brings whole system down

[Ben Hutchings]

Control: severity -1 important
Control: tag -1 moreinfo

On Sat, 20 Feb 2016 17:30:59 + Thomas Thurman  wrote:
[...]
> Here's an excerpt from kern.log a few days ago, showing the problem:
> 
> Feb 15 11:21:48 emley-moor kernel: [  169.188034] usb 1-1.2: reset high-speed 
> USB device number 4 using xhci_hcd
> Feb 15 11:22:45 emley-moor kernel: [  196.640590] sdhci: Timeout waiting for 
> Buffer Read Ready interrupt during tuning procedure, falling back to fixed 
> sampling clock
> Feb 15 11:22:45 emley-moor kernel: [  196.642950] [ cut here 
> ]
> Feb 15 11:22:45 emley-moor kernel: [  196.642964] WARNING: CPU: 1 PID: 0 at 
> /build/linux-TrvjeN/linux-4.4/drivers/mmc/host/sdhci.c:1003 
> sdhci_send_command+0x727/0xbc0 [sdhci]()
> Feb 15 11:22:45 emley-moor kernel: [  196.642968] Modules linked in: loop 
> fuse nls_utf8 nls_cp437 vfat fat snd_soc_sst_baytrail_pcm snd_soc_sst_ipc 
> iTCO_wdt sparse_keymap iTCO_vendor_support ak8975 snd_soc_sst_byt_rt5640_mach 
> rfkill snd_soc_sst_dsp intel_rapl gpio_keys intel_powerclamp coretemp 
> kvm_intel kvm irqbypass crc32_pclmul aesni_intel aes_i586 xts lrw gf128mul 
> ablk_helper cryptd sg snd_soc_rt5640 snd_soc_rl6231 efi_pstore evdev 
> snd_soc_core joydev snd_pcm_oss snd_mixer_oss snd_pcm efivars hid_multitouch 
> pcspkr snd_timer snd soundcore regmap_i2c inv_mpu6050 
> industrialio_triggered_buffer battery kfifo_buf industrialio i2c_mux i915 
> drm_kms_helper drm i2c_algo_bit lpc_ich mfd_core button 8250_fintek video wmi 
> tpm_crb dw_dmac dw_dmac_core soc_button_array processor_thermal_device 
> intel_soc_dts_iosf iosf_mbi int3400_thermal int3402_thermal int3403_thermal 
> acpi_thermal_rel int340x_thermal_zone snd_soc_sst_acpi 
> i2c_designware_platform i2c_designware_core tpm_tis tpm ac acpi_pad processor 
> parport_pc ppdev lp parport efivarfs autofs4 sd_mod hid_generic usbhid uas 
> usb_storage scsi_mod ext4 crc16 mbcache jbd2 mmc_block crc32c_intel xhci_pci 
> xhci_hcd usbcore usb_common thermal i2c_hid hid sdhci_acpi sdhci mmc_core
> Feb 15 11:22:45 emley-moor kernel: [  196.643119] CPU: 1 PID: 0 Comm: 
> swapper/1 Tainted: G  D W   4.4.0-trunk-686-pae #1 Debian 4.4-1~exp1
[...]

This indicates that there were earlier BUG and WARNING messages; please
send those as well.

Ben.

-- 
Ben Hutchings
The most exhausting thing in life is being insincere. - Anne Morrow Lindberg

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

Processed: tagging 815125, bug 815125 is forwarded to m...@codeblueprint.co.uk

[Debian Bug Tracking System]

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

> tags 815125 + upstream
Bug #815125 [src:linux] linux-image-4.4.0-1-amd64 fails to load initrd - no 
booting
Bug #815779 [src:linux] linux-image-4.4.0-1-amd64: Recent kernels freeze after 
loading initramfs on HP HBook 80
Added tag(s) upstream.
Added tag(s) upstream.
> forwarded 815125 m...@codeblueprint.co.uk
Bug #815125 [src:linux] linux-image-4.4.0-1-amd64 fails to load initrd - no 
booting
Bug #815779 [src:linux] linux-image-4.4.0-1-amd64: Recent kernels freeze after 
loading initramfs on HP HBook 80
Set Bug forwarded-to-address to 'm...@codeblueprint.co.uk'.
Set Bug forwarded-to-address to 'm...@codeblueprint.co.uk'.
> thanks
Stopping processing here.

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

Processed: Re: linux-image-4.4.0-1-amd64 spontaneously reboots my Braswell NUC5PPYH

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #815652 [src:linux] linux-image-4.4.0-1-amd64 spontaneously reboots my 
Braswell NUC5PPYH
Severity set to 'important' from 'critical'
> tag -1 moreinfo
Bug #815652 [src:linux] linux-image-4.4.0-1-amd64 spontaneously reboots my 
Braswell NUC5PPYH
Added tag(s) moreinfo.

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

Bug#815652: linux-image-4.4.0-1-amd64 spontaneously reboots my Braswell NUC5PPYH

[Ben Hutchings]

Control: severity -1 important
Control: tag -1 moreinfo

On Tue, 23 Feb 2016 05:50:26 -0500 james sarbello  
wrote:
[...]
> Just to note in passing, the last two kernel message lines
> before the reboot is related to ACPI, something like:
> 
> [#] ACPI: Core revision #
> [#] ACPI: 5 ACPI AML tables successfully acquired and loaded
> 
> The bug may be related to the apparent EFI bug described
> in Debian Bug No. 815173, which has been marked as closed.
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815173
> 
> However, the boot crash occurs even with the latest patched
> kernel version used as the basis for closing the bug report.

Have you tried adding the kernel parameter "efi=noruntime"?  Does that
make a difference?

Does Linux 4.5-rc4 (available in the experimental suite) have the same
problem?

Is a crash log visible through the pstore interface (files
/sys/fs/pstore/dmesg-*)?

Ben.

-- 
Ben Hutchings
The most exhausting thing in life is being insincere. - Anne Morrow Lindberg

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

Processed: retitle 808038 to linux-image should force upgrade of initramfs-tools to ensure nvme is included ...

[Debian Bug Tracking System]

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

> retitle 808038 linux-image should force upgrade of initramfs-tools to ensure 
> nvme is included
Bug #808038 [src:linux] linux-image-4.4.0-rc4-amd64: Fails to boot on kernel 
4.4rc4
Changed Bug title to 'linux-image should force upgrade of initramfs-tools to 
ensure nvme is included' from 'linux-image-4.4.0-rc4-amd64: Fails to boot on 
kernel 4.4rc4'
> severity 808038 important
Bug #808038 [src:linux] linux-image should force upgrade of initramfs-tools to 
ensure nvme is included
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#817011: ruby-domain-name: missing RubyGems integration, breaks other softwares like Vagrant

[Pirate Praveen]

On Mon, 07 Mar 2016 15:15:38 +0900 =?UTF-8?Q?Marc_Dequ=C3=A8nes_=28duck=29?= 
 wrote:
> I'm in the team but I don't have time or tools at the moment to get into 
> more details why this file is missing (I remember gem2deb to already 
> have all the necessary magic and this package is using it), sorry.

Its a common issue and I think gem2deb should handle it.

It happens when gemspec uses git ls-files command to list files. It fails when 
building in a clean chroot. The fix is to remove git usage in gemspec.

> Regards.
> 

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#812406: usb: Strange USB bugs

[Aurelien Jarno]

On 2016-01-23 23:56, Aurelien Jarno wrote:
> control: tag -1 + moreinfo
> control: tag -1 - upstream
> 
> Hi,
> 
> On 2016-01-23 15:05, Nickolay Ilyushin wrote:
> > Package: libusb-1.0-0
> > Version: 2:1.0.20-1
> > Severity: critical
> > File: usb
> > Tags: upstream
> > Justification: causes serious data loss
> 
> It is not clear from your description how you have lost data. Can you
> please give us more details?
> 
> > One PC sees only 10 MiB on my JetFlash Transcend USB and NTFS partition. 
> > Second PC (this) sees ~16 GiB and Mac & EFI partitions. But all statements 
> > are false: i don't have Windows, i don't have Mac, size of USB - 4 GiB. 
> > Also, sometimes, sector size from kernel does not matches sector size from 
> > usb driver. Can you fix it, maintainer?
> 
> This is not clear from your description where you "see" the wrong
> information. Without more details like for example the name of your
> desktop environment or a screenshot it would be difficult to get your
> problem fixed.
> 
> Also please note that libusb has nothing to do with USB flash disk, so
> the bug is likely reported against the wrong package.

Any news about this, can you please give us more details about the
issue?

Thanks,
Aurelien

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

Bug#817042: duplicity: corrupted files when backup is interrupted

[Martin Monperrus]

Package: duplicity
Version: 0.7.06-1
Severity: critical
Justification: causes serious data loss


   * What led up to the situation?
I backup my homedir with duplicity

   * What exactly did you do (or not do) that was effective (or ineffective)?
I try to restore a file

   * What was the outcome of this action?
Error 'librsync error 103 while in patch cycle' patching file
python2: ERROR: (rs_file_copy_cb) unexpected eof on fd169
python2: ERROR: (rs_job_complete) patch job failed: unexpected end of input

   * What outcome did you expect instead?
To restore the file


A "duplicity verify" shows that many files are corrupted. Seems related to
https://bugs.launchpad.net/duplicity/+bug/1252484.



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

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

Versions of packages duplicity depends on:
ii  libc62.21-9
ii  librsync10.9.7-10
ii  python   2.7.11-1
ii  python-lockfile  1:0.10.2-2

Versions of packages duplicity recommends:
ii  python-oauthlib  1.0.3-1
ii  python-paramiko  1.15.3-1
ii  python-urllib3   1.13.1-1
ii  rsync3.1.1-3

Versions of packages duplicity suggests:
ii  lftp4.6.3a-1+b2
pn  ncftp   
pn  python-boto 
pn  python-cloudfiles   
ii  python-gdata2.0.18+dfsg1-2
pn  python-swiftclient  
pn  tahoe-lafs  

-- no debconf information

Bug#817008: unfulfilled dependencies

[殷啟聰]

Thank you for reporting the bug. Actually the reason to this is that I
used ${source:Version} for "android-sdk-platform-tools" and
"android-sdk-build-tools", which is substituted to the version of the
source package rather than their own. I have fixed it but not yet
uploaded it.

The reason of setting the version differently is simple: They have
different versions :(

Bug#817041: librem0: Missing run-time dependency on libre0

[Guillem Jover]

Package: librem0
Version: 0.4.7-1
Severity: serious

Hi!

This package provides a shared library that is not self-contained, and
it is missing a run-time dependency on libre0, as it uses some of its
symbols. The library should link against all libraries it uses directly,
because otherwise it is pushing an internal implementation detail towards
its users.

A very simple example to illustrate:

  $ echo 'int main() { return 0; }' >rem.c
  $ gcc -o rem rem.c -lrem
  [ lots of undefined references to missing symbols… ]

I guess there's just a «-lre» missing somewhere in the build system.

(I found this while trying to build a local baresip package, so thanks
for trying to get that in Debian. :)

Thanks,
Guillem

Processed: Re: ruby-amqp and ruby-amq-client: error when trying to install together

[Debian Bug Tracking System]

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

> tags 817012 + pending
Bug #817012 [ruby-amq-client,ruby-amqp] ruby-amqp and ruby-amq-client: error 
when trying to install together
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#817012: ruby-amqp and ruby-amq-client: error when trying to install together

[Sebastien Badia]

tags 817012 + pending
thanks

Hi Ralf,

Thanks for this bug report!

Just fixed the issue (request a ROM of ruby-amq-client, (upstream dead), and
prepared a new version for ruby-amqp).

Cheers,

Seb


signature.asc
Description: PGP signature

Bug#817039: volti: Fails to start due to incorrect python-dbus version check

[Julian Calaby]

Package: volti
Version: 0.2.3-6
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The python-dbus version check on line 27 of /usr/lib/volti/volti.run is
incorrect due to recent changes to how the version of python-dbus is stored.

> assert dbus.version >= (0, 80, 0)

Alternatively, as the version of python-dbus is managed by Debian, this check
is redundant and the line could be removed.

This failed assersion makes the main "volti" command fail on startup rendering
the main part of the package, the systray icon, unusable.

I'd propose a patch, however I don't know enough Python to be certain that
it'd be correct. That said this should be rapidly fixable by anyone fluent in
Python.

Thanks,

Julian Calaby


-- System Information:
Distributor ID: Ubuntu
Description:Ubuntu 12.04.2 LTS
Release:12.04
Codename:   precise
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-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 volti depends on:
ii  python-alsaaudio  0.7-1
ii  python-dbus   1.2.2-1
ii  python-gobject3.18.2-2
ii  python-gtk2   2.24.0-4
ii  python-xlib   0.14+20091101-5
pn  python:any

volti recommends no packages.

volti suggests no packages.

-- no debconf information

Bug#803286: marked as done (prepare for giflib5)

[Debian Bug Tracking System]

Your message dated Mon, 07 Mar 2016 13:50:02 +
with message-id 
and subject line Bug#803286: fixed in mtpaint 3.40-2.2
has caused the Debian Bug report #803286,
regarding prepare for giflib5
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.)


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

Package: src:mtpaint
Version: 3.40-2
Tags: sid stretch patch
Blocks: 803158
User: gif...@packages.debian.org
Usertags: giflib5

Planning an update of giflib to the current version 5.1.1. Giflib slightly 
changes it's API, requiring soureful changes. There are some options for getting 
giflib5.1 support:


- Look for a newer upstream version, if upstream supports
both giflib4 and giflib5.1. Upload the new package,
and close the bug report.

- Patch the code to both use the NEW API. This can be done using
#if GIFLIB_MAJOR >= 5

#else

#endif
Please upload the package, and close the report.

- Unconditionally patch the code, not supporting giflib4 anymore.
Please upload a package to experimental once giflib5 hits
experimental.

For the latter two options, please see a patch at
http://launchpadlibrarian.net/222926300/mtpaint_3.40-2build2_3.40-2ubuntu1.diff.gz

To test your changes before giflib5 is found in experimental, please use

deb https://people.debian.org/~doko/tmp/giflib5 ./

Thanks, Matthias
--- End Message ---
--- Begin Message ---
Source: mtpaint
Source-Version: 3.40-2.2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated mtpaint package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 07 Mar 2016 13:46:16 +0100
Source: mtpaint
Binary: mtpaint
Architecture: source
Version: 3.40-2.2
Distribution: unstable
Urgency: medium
Maintainer: Muammar El Khatib 
Changed-By: Markus Koschany 
Description:
 mtpaint- painting program to create pixel art and manipulate digital photo
Closes: 803286
Changes:
 mtpaint (3.40-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove unnecessary build-dependency on libgif4. (Closes: #803286)
   * Refresh giflib5.diff because it did not apply cleanly.
   * Remove quilt from Build-Depends because source format 3.0 uses quilt by
 default.
   * Fix Lintian warning dep5-copyright-license-name-not-unique. In fact all
 files are licensed under GPL-3+ now.
Checksums-Sha1:
 eff71e65ba028ff2ce9f703cc95dfe0da735aa3f 1930 mtpaint_3.40-2.2.dsc
 2f69ca7160f0d9fc766b3379efd1a5c79c9164ae 185172 mtpaint_3.40-2.2.debian.tar.xz
Checksums-Sha256:
 49864c0047c20458a27f3620121bde307a3ccf5c51a7eb57198664c4753bb453 1930 
mtpaint_3.40-2.2.dsc
 878b2ace8fbcb37eaf2a31f3058d4b09137a0fed9dcf0899d47079d9cc6626d0 185172 
mtpaint_3.40-2.2.debian.tar.xz
Files:
 303a981732a02c9dcd2575e2fc3cb38e 1930 graphics optional mtpaint_3.40-2.2.dsc
 3b0569fe1faaf3a4272f28cb880dec78 185172 graphics optional 
mtpaint_3.40-2.2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJW3X3gXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE
OUFEMTRCOTUxM0I1MUU0AAoJENmtFLlRO1HkNlwP/0IrVyiO1MDscfXzaFRllAVl
JD5/80I1qwBsg7dkTSotIYoJ6CLnrAjQde+UKeyaB5xT3hnsA86cDq4Z/CSs/RLV
0K0IkjV9hQSkHc5t+hAcH3dpfQO2HSr4MD2q3+Ww5gFHfxFH4eqQuG/bq78Uhq4O
D6S2yIF4cRmGRsEZowuUT4xI0DcUQWFOpBSQmCX31djeMkBPQW7YVzjMJB+rnuVh
KV2skUHsteN3C+0RKSrZ+3M0k9hCu2KBi+vaCW9ru998u609u1/G5d9hO2qp9uuZ
f0zCJWYfYMCWpG3Lnw1mjlF1qtKXnYuTrgdowJKPG1ASBCXCKwvQfR7zqNPfjuGN
a1TB9C9Zs2V1h//+XbvGRXaYan7ZRevzmvFO1B2eGRqIuD0lWk42bJNiu47N+OZn
xQbieXu64mwHJW/kT8Dy4h1nci8iQzZe9KlbTKluIfnD4dLnEq56th4190+5FKcB
0XaHrHoF49Xf73ST4UUxUxkmNAdgAYJrzTZ2nSB87hHXB28owHzta75Ak1nys6mB
r8nbqJudvemGnz0wodXK6cZTKOM7hWTs8h6wi1MkVWxyKBPjm13pPJQqT2hf/P6+
egBNeytgiMdeeXGuOOH8ZnAEH4vcI2ASUqFAHezjdY6w7mUs61Gri7UpKjXCS99f
78gWf/7yYKzMkC1Vdh6W
=CG72
-END PGP SIGNATURE 

Bug#803286: mtpaint: diff for NMU version 3.40-2.2

[Markus Koschany]

Control: tags 803286 + pending

Dear maintainer,

I've prepared an NMU for mtpaint (versioned as 3.40-2.2) and
uploaded it to unstable. I am attaching the debdiff to this bug
report.

Regards,

Markus
diff -Nru mtpaint-3.40/debian/changelog mtpaint-3.40/debian/changelog
--- mtpaint-3.40/debian/changelog	2015-12-16 06:10:31.0 +0100
+++ mtpaint-3.40/debian/changelog	2016-03-07 14:02:46.0 +0100
@@ -1,3 +1,15 @@
+mtpaint (3.40-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove unnecessary build-dependency on libgif4. (Closes: #803286)
+  * Refresh giflib5.diff because it did not apply cleanly.
+  * Remove quilt from Build-Depends because source format 3.0 uses quilt by
+default.
+  * Fix Lintian warning dep5-copyright-license-name-not-unique. In fact all
+files are licensed under GPL-3+ now.
+
+ -- Markus Koschany   Mon, 07 Mar 2016 13:46:16 +0100
+
 mtpaint (3.40-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru mtpaint-3.40/debian/control mtpaint-3.40/debian/control
--- mtpaint-3.40/debian/control	2014-07-20 13:25:14.0 +0200
+++ mtpaint-3.40/debian/control	2016-03-07 14:02:46.0 +0100
@@ -5,14 +5,12 @@
 Build-Depends: debhelper (>= 7.0.50~),
libpng-dev,
zlib1g-dev,
-   libgif4,
libjpeg-dev,
libtiff-dev,
gettext,
pkg-config,
libgtk2.0-dev,
-   libgif-dev,
-   quilt
+   libgif-dev
 Standards-Version: 3.9.5
 Homepage: http://mtpaint.sourceforge.net/
 
diff -Nru mtpaint-3.40/debian/copyright mtpaint-3.40/debian/copyright
--- mtpaint-3.40/debian/copyright	2012-01-03 15:23:20.0 +0100
+++ mtpaint-3.40/debian/copyright	2016-03-07 14:02:46.0 +0100
@@ -6,24 +6,7 @@
 Files: *
 Copyright: 2004-2007, Mark Tyler 
   Dmitry Groshev 
-License: GPL-3
- This program is free software: you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation, either version 3 of the License, or
- (at your option) any later version.
- .
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
- GNU General Public License for more details.
- .
- You should have received a copy of the GNU General Public
- License along with this package; if not, write to the Free
- Software Foundation, Inc., 51 Franklin St, Fifth Floor,
- Boston, MA  02110-1301 USA
- .
- On Debian systems, the full text of the GNU General Public
- License version 3 can be found in the file `/usr/share/common-licenses/GPL-3'.
+License: GPL-3+
 
 Files: po/*.po
 Copyright: 2005, Myrk Tyler 
@@ -32,38 +15,21 @@
2006, Simek 
2006, Tutku Dalmaz 
2006, Wei-Lun Chao 
-	   2007, Norihiro YONEDA 
-	   2008, Sergei Irupin 
-	   2007, Jozef Riha 
-	   2008, Cecc 
-License: GPL-2
- This program is free software; you can redistribute it
- and/or modify it under the terms of the GNU General Public
- License as published by the Free Software Foundation; either
- version 2 of the License, or (at your option) any later
- version.
- .
- This program is distributed in the hope that it will be
- useful, but WITHOUT ANY WARRANTY; without even the implied
- warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
- PURPOSE.  See the GNU General Public License for more
- details.
- .
- You should have received a copy of the GNU General Public
- License along with this package; if not, write to the Free
- Software Foundation, Inc., 51 Franklin St, Fifth Floor,
- Boston, MA  02110-1301 USA
- .
- On Debian systems, the full text of the GNU General Public
- License version 2 can be found in the file `/usr/share/common-licenses/GPL-2'.
+   2007, Norihiro YONEDA 
+   2008, Sergei Irupin 
+   2007, Jozef Riha 
+   2008, Cecc 
+License: GPL-3+
 
 Files: debian/*
 Copyright: 2011, Muammar El Khatib 
-License: GPL-3
+License: GPL-3+
+
+License: GPL-3+
  This program is free software; you can redistribute it
  and/or modify it under the terms of the GNU General Public
  License as published by the Free Software Foundation; either
- version 2 of the License, or (at your option) any later
+ version 3 of the License, or (at your option) any later
  version.
  .
  This program is distributed in the hope that it will be
diff -Nru mtpaint-3.40/debian/patches/giflib5.diff mtpaint-3.40/debian/patches/giflib5.diff

Processed: mtpaint: diff for NMU version 3.40-2.2

[Debian Bug Tracking System]

Processing control commands:

> tags 803286 + pending
Bug #803286 [src:mtpaint] prepare for giflib5
Added tag(s) pending.

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

Bug#800188: marked as done (ebook-dev-alp: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Mon, 07 Mar 2016 11:49:45 +
with message-id 
and subject line Bug#800188: fixed in ebook-dev-alp 200407-2
has caused the Debian Bug report #800188,
regarding ebook-dev-alp: Please migrate a supported debhelper compat level
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.)


-- 
800188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ebook-dev-alp
Severity: important
Usertags: deprecated-debhelper-compat-leq-3

Hi,

The package ebook-dev-alp is using a debhelper compat level of 3 or less
according to lintian.  These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).

 * Please migrate the package to a supported debhelper compat level.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum (compat 4 will be removed soon as
 well)

 * If your package uses any of the following tools, please remove them
   from the rules files.  Neither of them does anything except warn
   about their deprecation.
   - dh_desktop
   - dh_scrollkeeper (deadline: January 1st 2016)
   - dh_suidregister
   - dh_undocumented

 * Please note that your package might have been flagged for using
   e.g. "DH_COMPAT=2 dh_foo ...".
   - This will still cause issues when the compat level is removed.

 * If the package has been relying on dh_install being lenient about
   missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Deadline: 
   - compat 1+2: November 1st 2015
   - compat 3: January 1st 2016

If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: ebook-dev-alp
Source-Version: 200407-2

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

Debian distribution maintenance software
pp.
Francesco Paolo Lovergine  (supplier of updated 
ebook-dev-alp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 07 Mar 2016 11:47:16 +0100
Source: ebook-dev-alp
Binary: ebook-dev-alp
Architecture: source all
Version: 200407-2
Distribution: unstable
Urgency: medium
Maintainer: Francesco Paolo Lovergine 
Changed-By: Francesco Paolo Lovergine 
Description:
 ebook-dev-alp - Advanced Linux Programming
Closes: 800188
Changes:
 ebook-dev-alp (200407-2) unstable; urgency=medium
 .
   * Policy bumped to 3.9.7.
   * Debhelper level set to current (9).
 (closes: #800188)
   * Removed [EBOOK-DEV] tag in short description.
Checksums-Sha1:
 347b7644ae9d9aaeff37f650a552cbd699bb9c26 1701 ebook-dev-alp_200407-2.dsc
 8abd968f41c06dd446b1e4b193d7edce2d869510 4237 ebook-dev-alp_200407-2.diff.gz
 7c6da7e22abc01bf13ea1b19bf0b24ee8506bbeb 3583540 ebook-dev-alp_200407-2_all.deb
Checksums-Sha256:
 f7081aa100c962ab8f1fb525c7ab84d99b642989f19e5d7502a381a7c94b3685 1701 
ebook-dev-alp_200407-2.dsc
 997306bf23e14deb427755bb0118df96c25d97e3e4708b3eafd934f95ef7ea8a 4237 
ebook-dev-alp_200407-2.diff.gz
 a821891e95d89fc1897eb5be3a05fd04d17458125c5efefb03da410773bc3a6a 3583540 
ebook-dev-alp_200407-2_all.deb
Files:
 7740a0770261626d855fce6827f721fa 1701 non-free/doc optional 
ebook-dev-alp_200407-2.dsc
 ebf1dfd5f4fbe7741baaef1ed613067b 4237 non-free/doc optional 
ebook-dev-alp_200407-2.diff.gz
 c4f83e4e44f4e81a116ae0820c8ca0d5 3583540 non-free/doc optional 
ebook-dev-alp_200407-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJW3WekAAoJEA8CpeEWNoak13sQALN9UamFr9Kl8dSV0+7tA7QN
NF45m93OfcT8RCcZMNjmr0NOT5CCb5azE94JATeUggQgHI04/FFxT+sGL3rFJ8g3
1lssYp6LkE/pnJgpBWxmmmsyCvTLNxMVJY+B1JNrlNswGInC4+pXxIym3TkZkQAm
3XkIfBIOjPf7C5pFFGlkr6KaU/afFFGWBqBGH6swFa2tUhoSiV3aIadY6PlUyHL6
Z1rMH/qCEl5BKC6AMYZZcIOMDkN5mFs/JB10DVteTy/xO/GsLkAUU9PrExXnSjOX

Bug#800306: marked as done (mpi-specs: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Mon, 07 Mar 2016 11:20:19 +
with message-id 
and subject line Bug#800306: fixed in mpi-specs 20040719-3
has caused the Debian Bug report #800306,
regarding mpi-specs: Please migrate a supported debhelper compat level
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.)


-- 
800306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpi-specs
Severity: important
Usertags: deprecated-debhelper-compat-leq-3

Hi,

The package mpi-specs is using a debhelper compat level of 3 or less
according to lintian.  These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).

 * Please migrate the package to a supported debhelper compat level.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum (compat 4 will be removed soon as
 well)

 * If your package uses any of the following tools, please remove them
   from the rules files.  Neither of them does anything except warn
   about their deprecation.
   - dh_desktop
   - dh_scrollkeeper (deadline: January 1st 2016)
   - dh_suidregister
   - dh_undocumented

 * Please note that your package might have been flagged for using
   e.g. "DH_COMPAT=2 dh_foo ...".
   - This will still cause issues when the compat level is removed.

 * If the package has been relying on dh_install being lenient about
   missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Deadline: 
   - compat 1+2: November 1st 2015
   - compat 3: January 1st 2016

If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: mpi-specs
Source-Version: 20040719-3

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

Debian distribution maintenance software
pp.
Francesco Paolo Lovergine  (supplier of updated mpi-specs 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 07 Mar 2016 09:48:38 +0100
Source: mpi-specs
Binary: mpi-specs
Architecture: source all
Version: 20040719-3
Distribution: unstable
Urgency: medium
Maintainer: Francesco Paolo Lovergine 
Changed-By: Francesco Paolo Lovergine 
Description:
 mpi-specs  - MPI 1.1 and 2.0 Specifications of MPI Forum
Closes: 800306
Changes:
 mpi-specs (20040719-3) unstable; urgency=medium
 .
   * Revamped with a modern version of debhelper
 (closes: #800306)
   * Policy bumped to 3.9.7.
   * Removed [] tag in debian/control short description.
Checksums-Sha1:
 0dd77a4ced497979b181ba5d3e00a2e437042b31 1726 mpi-specs_20040719-3.dsc
 20daff55d3deb7513ef7f5a2b4d15b16c8d85755 3847 mpi-specs_20040719-3.diff.gz
 9797bc9f345fbc86bf8251540f0440cf776aee54 614982 mpi-specs_20040719-3_all.deb
Checksums-Sha256:
 b53507e343aa5589b49fa42d48d0886ba76fd5cb3ab0206e248e5ccd974aa534 1726 
mpi-specs_20040719-3.dsc
 7ddff21fdece7d49c2359c581ef121e25e47e2b288336fae9dda2c3d36815b7e 3847 
mpi-specs_20040719-3.diff.gz
 2f033c987e3bf268f6c9a188593e7055f15d57e3e9cbae6de0aece5f9001aeae 614982 
mpi-specs_20040719-3_all.deb
Files:
 b500d6f871acd2c8d8fae45a339e593d 1726 non-free/doc optional 
mpi-specs_20040719-3.dsc
 8fb41fc68cb44bd883546f9a64bf5792 3847 non-free/doc optional 
mpi-specs_20040719-3.diff.gz
 3bdac957eda770bc458e4c10ad323895 614982 non-free/doc optional 
mpi-specs_20040719-3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJW3Vu2AAoJEA8CpeEWNoakcxkQAK2oRlkbiuK3ZrlRx6vZZ7I9
vfXW2Afl/JoaroHumk3wCWfB/be3hbZMB01lH5f1+h6dUBIKnVmoNHnffnzK7IKk
SyCvfNFlP4cm6VcuEnK0fbIFF9nEb4uEg4nL7Ic3J0V8ZVqSIP4llqW17Tu5ivzL
7q34ff9JKRWjg7Q0mJ1Hr7Pep5CQnGO5gACSKEtznkOBwObt7ktfJkDMxhoHw7RF
wPcL9pVWyT72zdJjxNH+Xm08P4zcCE6uZbZG6tFuRiNLTNj5TzHGq/x/9M1y6WSM

Processed: bug 817025 is forwarded to https://github.com/coreos/fleet/issues/1468

[Debian Bug Tracking System]

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

> forwarded 817025 https://github.com/coreos/fleet/issues/1468
Bug #817025 [src:fleet] fleet: FTBFS: coreos.go:26:2: cannot find package 
"github.com/opencontainers/runc/libcontainer/netlink
Set Bug forwarded-to-address to 'https://github.com/coreos/fleet/issues/1468'.
> thanks
Stopping processing here.

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

Processed: tagging 817025

[Debian Bug Tracking System]

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

> tags 817025 + confirmed upstream
Bug #817025 [src:fleet] fleet: FTBFS: coreos.go:26:2: cannot find package 
"github.com/opencontainers/runc/libcontainer/netlink
Added tag(s) confirmed and upstream.
> thanks
Stopping processing here.

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

Bug#816587: shared-mime-info: FTBFS: LaTeX Error: File `ulem.sty' not found.

[Sebastian Dröge]

reassign 816587 docbook-utils
reassign 817026 docbook-utils
reassign 817027 docbook-utils
forcemerge 816587 817026 817027
thanks

On Do, 2016-03-03 at 10:45 +0200, Sebastian Dröge wrote:
> On Do, 2016-03-03 at 08:36 +, Chris Lamb wrote:
> > 
> > Source: shared-mime-info
> > Version: 1.5-2
> > Severity: serious
> > Justification: fails to build from source
> > User: reproducible-bui...@lists.alioth.debian.org
> > Usertags: ftbfs
> > X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> > 
> > Dear Maintainer,
> > 
> > shared-mime-info fails to build from source in unstable/amd64:
> Yes, for whatever reason texlive-generic-recommended is not
> automatically pulled in anymore. Should check first if this was
> intentional.

docbook-utils' docbook2pdf needs ulem.sty from texlive-generic-
recommended. At some point something in the texlive dependencies
changed so it's not automatically pulled in anymore.

Means that either that texlive change has to be reverted, or docbook-
tools has to depend on texlive-generic-recommended.

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

Processed: Re: Bug#816587: shared-mime-info: FTBFS: LaTeX Error: File `ulem.sty' not found.

[Debian Bug Tracking System]

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

> reassign 816587 docbook-utils
Bug #816587 [src:shared-mime-info] shared-mime-info: FTBFS: LaTeX Error: File 
`ulem.sty' not found.
Bug reassigned from package 'src:shared-mime-info' to 'docbook-utils'.
No longer marked as found in versions shared-mime-info/1.5-2.
Ignoring request to alter fixed versions of bug #816587 to the same values 
previously set
> reassign 817026 docbook-utils
Bug #817026 [src:gstreamer0.10] gstreamer0.10: FTBFS: ! LaTeX Error: File 
`ulem.sty' not found.
Bug reassigned from package 'src:gstreamer0.10' to 'docbook-utils'.
No longer marked as found in versions gstreamer0.10/0.10.36-1.5.
Ignoring request to alter fixed versions of bug #817026 to the same values 
previously set
> reassign 817027 docbook-utils
Bug #817027 [src:gstreamer1.0] gstreamer1.0: FTBFS: LaTeX Error: File 
`ulem.sty' not found.
Bug reassigned from package 'src:gstreamer1.0' to 'docbook-utils'.
No longer marked as found in versions gstreamer1.0/1.6.3-1.
Ignoring request to alter fixed versions of bug #817027 to the same values 
previously set
> forcemerge 816587 817026 817027
Bug #816587 [docbook-utils] shared-mime-info: FTBFS: LaTeX Error: File 
`ulem.sty' not found.
Bug #817026 [docbook-utils] gstreamer0.10: FTBFS: ! LaTeX Error: File 
`ulem.sty' not found.
Bug #817027 [docbook-utils] gstreamer1.0: FTBFS: LaTeX Error: File `ulem.sty' 
not found.
Merged 816587 817026 817027
> thanks
Stopping processing here.

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

Bug#817000: pymvpa2: FTBFS in stretch, build dependencies not in stretch

[Santiago Vila]

On Sun, 6 Mar 2016, Yaroslav Halchenko wrote:

> On Mon, 07 Mar 2016, Santiago Vila wrote:
> > The following packages have unmet dependencies:
> >  sbuild-build-depends-pymvpa2-dummy : Depends: swig2.0 but it is not 
> > installable or
> >swig (<= 3.0.5) but it is 
> > not going to be installed
> 
> well -- swig2.0 was removed from testing but present in sid
> 
> my guess is that pymvpa2 pkg would eventually be autoremoved from
> testing, and there is nothing for me to do about it neither now nor
> later to "close" this issue.
> 
> FWIW -- can't use swig 3.x due to
> https://github.com/swig/swig/issues/563 which could have been a
> proper 'fix'.  But as long as swig2.0 is part of the archive, issue is
> not really an issue for me to tackle.  So I will close it for now, feel
> free to reopen if you feel it would be of some value (please describe of
> which)

Ok, you reopened later but maybe I should explain a little bit:

The testing distribution is supposed to be in an "always releaseable" state.

Since packages in stable should never build-depend on packages not in stable,
it follows that packages in testing should never build-depend on packages
not in testing.

So, even if we are not going to release stretch as stable today or tomorrow,
this would still be a RC bug, i.e. a bug that must not be present in testing.

The scripts that create the testing distribution from the "pool" ensure
that dependencies are always met in testing, by construction, but I think
they do not make the same check for build-depends (yet).

So, if pymvpa2 is to be autoremoved from testing, it would be because
of RC bugs like this one being open (which is why this bug is here to
begin with), not because the testing scripts decide to remove it on
their own.

There are two common cases for bugs like this one:

* The missing build depends package is in unstable but it has not
  entered testing yet. We sort of tolerate bugs like this one (maybe
  to the point of downgrading the bug to "important" to save some
  work), because we know it is a matter of time that they get fixed.

* The missing build depends package was in testing but it was removed
  to not come back again. This is a RC bug in all cases.

As I am building packages with "dpkg-buildpackage -A" in a random
fashion, not because I use those packages myself, I don't have any
familiarity with the affected packages, so I leave to the maintainer
to decide which one of the two common cases is the one that actually
happens.

Thanks.

Bug#817025: fleet: FTBFS: coreos.go:26:2: cannot find package "github.com/opencontainers/runc/libcontainer/netlink

[Chris Lamb]

Source: fleet
Version: 0.11.5+dfsg1-3
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,

fleet fails to build from source in unstable/amd64:

   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: source package fleet
  dpkg-buildpackage: source version 0.11.5+dfsg1-3
  dpkg-buildpackage: source distribution unstable
  dpkg-buildpackage: source changed by Dmitry Smirnov 
   dpkg-source --before-build fleet-0.11.5+dfsg1
  dpkg-buildpackage: host architecture amd64
   fakeroot debian/rules clean
  dh clean --buildsystem=golang --with=golang,systemd --builddirectory=_build
 dh_testdir -O--buildsystem=golang -O--builddirectory=_build
 dh_auto_clean -O--buildsystem=golang -O--builddirectory=_build
 debian/rules override_dh_clean
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160307093644.V5UHlwQuzu/fleet-0.11.5+dfsg1'
  dh_clean
  ## Remove Files-Excluded (when built from checkout or non-DFSG tarball):
  rm -f -rv `perl -0nE 'say $1 if 
m{^Files\-Excluded\:\s*(.*?)(?:\n\n|Files:|Comment:)}sm;' debian/copyright`
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160307093644.V5UHlwQuzu/fleet-0.11.5+dfsg1'
   debian/rules build
  make: 'build' is up to date.
   fakeroot debian/rules binary
  dh binary --buildsystem=golang --with=golang,systemd --builddirectory=_build
 dh_testdir -O--buildsystem=golang -O--builddirectory=_build
 dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=_build
 debian/rules override_dh_auto_configure
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160307093644.V5UHlwQuzu/fleet-0.11.5+dfsg1'
  dh_auto_configure
  perl -0nE 'say $1 if 
m{^Files\-Excluded\:\s*(.*?)(?:\n\n|Files:|Comment:)}sm;' debian/copyright \
  | while read D; do D="${D##Godeps/_workspace/src/}" ; printf 
"Removing third party bundle: $D\n" ;\
  perl -pi -E 
"s{github.com/coreos/fleet/Godeps/_workspace/src/$D}{$D}msg;" `find _build/src 
-type f -name "*.go"` ;\
  done
  Removing third party bundle: code.google.com/p/go-uuid
  Removing third party bundle: github.com/coreos/etcd
  Removing third party bundle: github.com/coreos/go-semver
  Removing third party bundle: 
~Godeps/_workspace/src/github.com/coreos/go-systemd
  Removing third party bundle: github.com/docker/libcontainer
  Removing third party bundle: github.com/godbus/dbus
  Removing third party bundle: github.com/jonboulle/clockwork
  Removing third party bundle: github.com/rakyll/globalconf
  Removing third party bundle: github.com/rakyll/goini
  Removing third party bundle: golang.org/x/crypto
  Removing third party bundle: golang.org/x/net
  Removing third party bundle: google.golang.org/api/google-api-go-generator
  Removing third party bundle: google.golang.org/api/googleapi
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160307093644.V5UHlwQuzu/fleet-0.11.5+dfsg1'
 dh_auto_build -O--buildsystem=golang -O--builddirectory=_build
go install -v github.com/coreos/fleet/fleetd 
github.com/coreos/fleet/fleetctl
  src/github.com/coreos/fleet/machine/coreos.go:26:2: cannot find package 
"github.com/opencontainers/runc/libcontainer/netlink" in any of:
/usr/lib/go/src/github.com/opencontainers/runc/libcontainer/netlink 
(from $GOROOT)

/home/lamby/temp/cdt.20160307093644.V5UHlwQuzu/fleet-0.11.5+dfsg1/_build/src/github.com/opencontainers/runc/libcontainer/netlink
 (from $GOPATH)
  dh_auto_build: go install -v github.com/coreos/fleet/fleetd 
github.com/coreos/fleet/fleetctl returned exit code 1
  debian/rules:10: recipe for target 'binary' failed
  make: *** [binary] Error 1

  [..]

The full build log is attached.


Regards,

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


fleet.0.11.5+dfsg1-3.unstable.amd64.log.txt.gz
Description: Binary data

Bug#817027: gstreamer1.0: FTBFS: LaTeX Error: File `ulem.sty' not found.

[Chris Lamb]

Source: gstreamer1.0
Version: 1.6.3-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,

gstreamer1.0 fails to build from source in unstable/amd64:

  [..]

  (/usr/share/texlive/texmf-dist/tex/latex/graphics/color.sty
  (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/color.cfg)
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/dvips.def)
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/dvipsnam.def))
  (/usr/share/texlive/texmf-dist/tex/latex/colortbl/colortbl.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/marvosym/marvosym.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg)))
  (/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty)
  
  ! LaTeX Error: File `ulem.sty' not found.
  
  [..]

The full build log is attached.


Regards,

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


gstreamer1.0.1.6.3-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#817026: gstreamer0.10: FTBFS: ! LaTeX Error: File `ulem.sty' not found.

[Chris Lamb]

Source: gstreamer0.10
Version: 0.10.36-1.5
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,

gstreamer0.10 fails to build from source in unstable/amd64:

  [..]

DOC   Building XML
  ./gstreamer-decl.txt:7864: warning: GstTagList has multiple definitions.
  ../../gst/gstplugin.h:297: warning: GST_PLUGIN_DEFINE_STATIC is deprecated in 
the inline comments, but no deprecation guards were found around the 
declaration. (See the --deprecated-guards option for gtkdoc-scan.)
  ../../gst/gstiterator.h:204: warning: Field description for 
GstIterator::resync is not used from source code comment block.
  ../../gst/gstiterator.h:204: warning: Field description for GstIterator::lock 
is not used from source code comment block.
  ../../gst/gstiterator.h:204: warning: Field description for GstIterator::free 
is not used from source code comment block.
  ../../gst/gstiterator.h:204: warning: Field description for 
GstIterator::pushed is not used from source code comment block.
  ../../gst/gstiterator.h:204: warning: Field description for GstIterator::type 
is not used from source code comment block.
  ../../gst/gstiterator.h:204: warning: Field description for GstIterator::next 
is not used from source code comment block.
  ../../gst/gstiterator.h:204: warning: Field description for 
GstIterator::master_cookie is not used from source code comment block.
  ../../gst/gstiterator.h:204: warning: Field description for 
GstIterator::cookie is not used from source code comment block.
  ../../gst/gstiterator.h:204: warning: Field description for GstIterator::item 
is not used from source code comment block.
  ./gstreamer-unused.txt:1: warning: 5 unused declarations.They should be added 
to gstreamer-sections.txt in the appropriate place.
DOC   Building HTML
DOC   Fixing cross-references
  html/gstreamer-GstUriHandler.html:309: warning: no link for: 
'api-index-0.10.13' -> (0.10.13).
  html/gstreamer-GstUriHandler.html:372: warning: no link for: 
'api-index-0.10.4' -> (0.10.4).
  html/gstreamer-GstUriHandler.html:506: warning: no link for: 
'api-index-0.10.33' -> (0.10.33).
  html/GstRegistry.html:424: warning: no link for: 'api-index-0.10.26' -> 
(0.10.26).
  html/GstBus.html:599: warning: no link for: 'api-index-0.10.15' -> (0.10.15).
  html/GstBus.html:644: warning: no link for: 'api-index-0.10.12' -> (0.10.12).
  html/gstreamer-GstDateTime.html:230: warning: no link for: 
'api-index-0.10.31' -> (0.10.31).
  html/gstreamer-GstValue.html:1440: warning: no link for: 'api-index-0.10.32' 
-> (0.10.32).
  html/gstreamer-Gst.html:281: warning: no link for: 'gtk-init' -> (gtk_init()).
  html/gstreamer-Gst.html:470: warning: no link for: 'api-index-0.10.10' -> 
(0.10.10).
  html/gstreamer-GstBufferList.html:462: warning: no link for: 
'api-index-0.10.24' -> (0.10.24).
  html/GstTagSetter.html:253: warning: no link for: 'api-index-0.10.22' -> 
(0.10.22).
  html/gstreamer-GstPoll.html:292: warning: no link for: 'api-index-0.10.18' -> 
(0.10.18).
  html/gstreamer-GstPoll.html:667: warning: no link for: 'api-index-0.10.23' -> 
(0.10.23).
  html/gstreamer-GstIterator.html:530: warning: no link for: 
'api-index-0.10.25' -> (0.10.25).
  html/GstElementFactory.html:871: warning: no link for: 'api-index-0.10.14' -> 
(0.10.14).
  html/gstreamer-GstInfo.html:2018: warning: no link for: 'api-index-0.10.30' 
-> (0.10.30).
  html/GstClock.html:620: warning: no link for: 'api-index-0.10.16' -> 
(0.10.16).
  html/gstreamer-GstMessage.html:1617: warning: no link for: 
'api-index-0.10.11' -> (0.10.11).
  html/gstreamer-GstMessage.html:1700: warning: no link for: 
'api-index-0.10.20' -> (0.10.20).
  html/gstreamer-GstMessage.html:3012: warning: no link for: 
'api-index-0.10.29' -> (0.10.29).
  html/gstreamer-GstMessage.html:3338: warning: no link for: 
'api-index-0.10.22.' -> (0.10.22.).
  html/gstreamer-GstMessage.html:3500: warning: no link for: 
'api-index-0.10.24.' -> (0.10.24.).
  html/GstGhostPad.html:623: warning: no link for: 'api-index-0.10.36' -> 
(0.10.36).
  html/gstreamer-GstTagList.html:4167: warning: no link for: 'GstTagImageType' 
-> (GstTagImageType).
  html/gstreamer-GstTagList.html:4168: warning: no link for: 'api-index-0.10.6' 
-> (0.10.6).
  html/gstreamer-GstTagList.html:4177: warning: no link for: 'api-index-0.10.7' 
-> (0.10.7).
  html/gstreamer-GstTagList.html:4187: warning: no link for: 
'api-index-0.10.21' -> (0.10.21).
  html/gstreamer-GstEvent.html:845: warning: no link for: 'api-index-0.10.3' -> 
(0.10.3).
  html/gstreamer-GstMiniObject.html:339: warning: no link for: 
'api-index-0.10.35' -> (0.10.35).
  html/GstPipeline.html:640: warning: no link for: 'api-index-0.10.5' -> 
(0.10.5).
  html/gstreamer-GstBuffer.html:892: warning: no link for: 'api-index-0.10.9' 
-> (0.10.9).
  html/GstXML.html:202: warning: no link for: 'FILE:CAPS' -> (FILE).
  make[6]: 

Processed: bug 812114 is forwarded to https://github.com/jsonpickle/jsonpickle/issues/142

[Debian Bug Tracking System]

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

> forwarded 812114 https://github.com/jsonpickle/jsonpickle/issues/142
Bug #812114 [src:jsonpickle] jsonpickle: FTBFS: SyntaxError: unexpected EOF 
while parsing
Set Bug forwarded-to-address to 
'https://github.com/jsonpickle/jsonpickle/issues/142'.
> thanks
Stopping processing here.

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

Bug#812087: [pcscd]

[Philippe Teuwen]

I forgot to say, removing TEMP_FAILURE_RETRY() didn't change anything.

Bug#812087: [pcscd]

[Philippe Teuwen]

I recompiled libusb with debug symbols:


Normal CPU:

Thread 5 (Thread 0x7f0238fcb700 (LWP 24364)):
#0  0x7f02394dfb6d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f0238fdbafc in poll (__timeout=-1, __nfds=2,
__fds=0x7f0238fcaee0)
at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  linux_udev_event_thread_main (arg=)
at ../../libusb/os/linux_udev.c:175
#3  0x7f02397ab284 in start_thread (arg=0x7f0238fcb700)
at pthread_create.c:333
#4  0x7f02394e8a4d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

100% CPU:

Thread 5 (Thread 0x7fbeac2a4700 (LWP 24181)):
#0 0x7fbeaca8cbdd in recvmsg () at ../sysdeps/unix/syscall-template.S:81
#1 0x7fbead2806ec in udev_monitor_receive_device ()
from /lib/x86_64-linux-gnu/libudev.so.1
#2 0x7fbeac2b4b8b in linux_udev_event_thread_main (arg=)
at ../../libusb/os/linux_udev.c:186
#3 0x7fbeaca84284 in start_thread (arg=0x7fbeac2a4700)
at pthread_create.c:333
#4 0x7fbeac7c1a4d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109



So the diff happens in that code from libusb/os/linux_udev.c:



usbi_dbg("udev event thread entering.");
while (poll(fds, 2, -1) >= 0) {
if (fds[0].revents & POLLIN) {
r = usbi_read(udev_control_pipe[0], , sizeof(dummy));
if (r <= 0) {
usbi_warn(NULL, "udev control pipe read failed");
}
break;
}
if (fds[1].revents & POLLIN) {
usbi_mutex_static_lock(_hotplug_lock);
udev_dev = udev_monitor_receive_device(udev_monitor);
if (udev_dev)
udev_hotplug_event(udev_dev);
usbi_mutex_static_unlock(_hotplug_lock);
}
}
usbi_dbg("udev event thread exiting");


I added error msgs in the loop.
When 100% CPU, the poll() is non-blocking and the loop becomes a busy loop.



On 03/06/2016 11:49 PM, Philippe Teuwen wrote:
> #0 0x7f196a6cabdd in recvmsg () at ../sysdeps/unix/syscall-template.S:81
> #1 0x7f196aebe6ec in udev_monitor_receive_device () from
> /lib/x86_64-linux-gnu/libudev.so.1
> #2 0x7f1969ef2bcb in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
> #3 0x7f196a6c2284 in start_thread (arg=0x7f1969ee2700) at
> pthread_create.c:333
> #4 0x7f196a3ffa4d in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Bug#811185: failed tests

[olivier sallou]

I need to test on my computer, this could be related to a new swi-prolog
version introduction incompatible backwards modifications.

Processed: more fiddling to get bts to understand its done

[Debian Bug Tracking System]

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

> notfound 810881 totem-pl-parser/3.10.6-1
Bug #810881 {Done: Andreas Henriksson } [libtotem-plparser18] 
libtotem-plparser18: linker issue, causes grilo-plugins to FTBFS
No longer marked as found in versions totem-pl-parser/3.10.6-1.
> found 810881 libtotem-plparser18/3.10.6-1
Bug #810881 {Done: Andreas Henriksson } [libtotem-plparser18] 
libtotem-plparser18: linker issue, causes grilo-plugins to FTBFS
The source libtotem-plparser18 and version 3.10.6-1 do not appear to match any 
binary packages
Marked as found in versions libtotem-plparser18/3.10.6-1.
> thanks
Stopping processing here.

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