Bug#837631: galileo: Please announce supported hardware using AppStream

[Petter Reinholdtsen]

Package: galileo
Version: 0.5.0-1
Severity: wishlist

Hi.

The galileo package is one of the packages in the Debian archive that
should be proposed for installation when a given hardware dongle is
inserted or available.  Thanks to the appstream system, this can now be
announced in a way other tools can use and act on.  I've written the
isenkram system to ask the current user if hardware specific packages
should be installed when a new dongle is installed, and isenkram now
uses appstream as one source for hardware to package mappings.

You can read more about this on my blog, 
http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
 >.

It would be great if you could add an appstream metainfo file to the
galileo package, with content similar to this:

  
  
   [...]
   
  usb:v2687pfb01d*

  

If there are other USB ids also supposed by the package, please add
those too. :)

-- 
Happy hacking
Petter Reinholdtsen

Bug#504266: closing RFP: darwin-calendar-server -- CalDAV calendar server

[Josh Triplett]

On Mon, Sep 12, 2016 at 10:01:57PM -0700, Josh Triplett wrote:
> On Mon, Sep 12, 2016 at 10:20:15AM +, Bart Martens wrote:
> > RFP 504266 has no visible progress for a long time, so closing.
> 
> It looks like the software got packaged (as "calendarserver") back in
> 2011, just without an update to the RFP.

Correction, packaged back in 2008.

Bug#837012: tachyon: FTBFS: ld: tachyon_ogl-glwin.o: undefined reference to symbol 'XNextEvent'

[Alastair McKinstry]

Hi,

I've uploaded an NMU of tachyon that fixes this to DELAYED/5.

The debdiff is:

dpkg-source: warning: extracting unsigned source package
(/srv/build/tachyon/tachyon_0.99~b6+dsx-5.1.dsc)
diff -Nru tachyon-0.99~b6+dsx/debian/changelog
tachyon-0.99~b6+dsx/debian/changelog
--- tachyon-0.99~b6+dsx/debian/changelog2016-08-01
02:23:29.0 +0100
+++ tachyon-0.99~b6+dsx/debian/changelog2016-09-12
14:12:26.0 +0100
@@ -1,3 +1,10 @@
+tachyon (0.99~b6+dsx-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS: Needs to link against libX11 explicitly. Closes: #837012.
+
+ -- Alastair McKinstry   Mon, 12 Sep 2016
14:12:26 +0100
+
 tachyon (0.99~b6+dsx-5) unstable; urgency=medium

   * Debianization:
diff -Nru tachyon-0.99~b6+dsx/debian/patches/series
tachyon-0.99~b6+dsx/debian/patches/series
--- tachyon-0.99~b6+dsx/debian/patches/series2016-08-01
02:12:39.0 +0100
+++ tachyon-0.99~b6+dsx/debian/patches/series2016-09-12
14:12:26.0 +0100
@@ -10,3 +10,4 @@
 upstream-rationalization-autotools.patch
 debianization.patch
 debianization-documentation.patch
+x11.patch
diff -Nru tachyon-0.99~b6+dsx/debian/patches/x11.patch
tachyon-0.99~b6+dsx/debian/patches/x11.patch
--- tachyon-0.99~b6+dsx/debian/patches/x11.patch1970-01-01
01:00:00.0 +0100
+++ tachyon-0.99~b6+dsx/debian/patches/x11.patch2016-09-12
14:12:26.0 +0100
@@ -0,0 +1,19 @@
+Author: Alastair McKinstry 
+Description: X11 lib is needed for linking
+Bug-Debian: https://bugs.debian.org/837012
+Last-Update: 2016-09-12
+Forwarded: no
+
+Index: tachyon-0.99~b6+dsx/demosrc/Makefile.am
+===
+--- tachyon-0.99~b6+dsx.orig/demosrc/Makefile.am
 tachyon-0.99~b6+dsx/demosrc/Makefile.am
+@@ -5,7 +5,7 @@ bin_PROGRAMS += tachyon-nox tachyon-ogl
+ man_MANS += tachyon-nox.1 tachyon-ogl.1
+ endif
+
+-
++X_LIBS= -lX11
+ AM_CFLAGS = -Wno-unused-result
+
+ tachyon_SOURCES = \

regards
Alastair


On 13/09/2016 01:50, Jerome BENOIT wrote:
> Hello Lucas, thanks for the report.
>
>
>
> On 07/09/16 23:18, Lucas Nussbaum wrote:
> > Source: tachyon
> > Version: 0.99~b6+dsx-5
> > Severity: serious
> > Tags: stretch sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20160906 qa-ftbfs
> > Justification: FTBFS on amd64
>
> > Hi,
>
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
>
> > Relevant part (hopefully):
> >> /bin/bash ../libtool  --tag=CC   --mode=link gcc -Wno-unused-result
> -I/usr/include/libdrm -I/usr/include/libdrm -g -O3
> -fdebug-prefix-map=/<>/tachyon-0.99~b6+dsx=. -fPIE
> -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT
> -ffast-math -fomit-frame-pointer   -o tachyon-ogl tachyon_ogl-main.o
> tachyon_ogl-getargs.o tachyon_ogl-parse.o tachyon_ogl-nffparse.o
> tachyon_ogl-mgfparse.o tachyon_ogl-ac3dparse.o tachyon_ogl-glwin.o
> tachyon_ogl-spaceball.o tachyon_ogl-trackball.o ../src/libtachyon.la
> -lm -lGL  -lGL
> >> libtool: link: gcc -Wno-unused-result -I/usr/include/libdrm
> -I/usr/include/libdrm -g -O3
> "-fdebug-prefix-map=/<>/tachyon-0.99~b6+dsx=." -fPIE
> -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT
> -ffast-math -fomit-frame-pointer -o .libs/tachyon-ogl
> tachyon_ogl-main.o tachyon_ogl-getargs.o tachyon_ogl-parse.o
> tachyon_ogl-nffparse.o tachyon_ogl-mgfparse.o tachyon_ogl-ac3dparse.o
> tachyon_ogl-glwin.o tachyon_ogl-spaceball.o tachyon_ogl-trackball.o 
> ../src/.libs/libtachyon.so -lm -lGL
> >> /usr/bin/ld: tachyon_ogl-glwin.o: undefined reference to symbol
> 'XNextEvent'
> >> //usr/lib/x86_64-linux-gnu/libX11.so.6: error adding symbols: DSO
> missing from command line
> >> collect2: error: ld returned 1 exit status
>
> > The full build log is available from:
> >   
> http://people.debian.org/~lucas/logs/2016/09/06/tachyon_0.99~b6+dsx-5_unstable.log
>
> I could reproduce the issue in a chroot environment.
> I am working on it.
>
>
>
> > A list of current common problems and possible solutions is available at
> > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to
> contribute!
>
> > About the archive rebuild: The rebuild was done on EC2 VM instances from
> > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> > failed build was retried once to eliminate random failures.
>
>
> Thanks,
> Jerome
>
>

-- 
Alastair McKinstry, , ,
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered.

Bug#504266: closing RFP: darwin-calendar-server -- CalDAV calendar server

[Josh Triplett]

On Mon, Sep 12, 2016 at 10:20:15AM +, Bart Martens wrote:
> RFP 504266 has no visible progress for a long time, so closing.

It looks like the software got packaged (as "calendarserver") back in
2011, just without an update to the RFP.

Bug#837630: transition: xapian-core

[Olly Betts]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

I'd like to transition the archive to Xapian 1.4 before the next
release.

There are packages of xapian-core 1.4.0 in experimental.  I maintain
xapian-bindings and xapian-omega, and packages of 1.4.0 for those are
also in experimental.  All three packages have built on all release
architectures:

https://buildd.debian.org/status/package.php?p=xapian-bindings+xapian-core+xapian-omega=experimental

I've test rebuilt the other reverse dependencies and they all built
cleanly with the exception of:

 * pinot - this FTBFS in unstable due to GCC 6 (RC bug #812165) and
   (as I've noted in that bug) when I patch that and rebuild against
   xapian-core 1.4.0 the resulting binary segfaults when run, due to
   something which appears to be related to symbol mangling.  Since
   Xapian is GPLv2+ and pinot also links to openssl the package
   doesn't appear to be distributable anyway (RC bug #833692), and
   pinot has already been removed from testing, so this doesn't seem
   like a blocker for the transition.

 * libsearch-xapian-perl - this needs a patch for compatibility with
   xapian-core 1.4.  I have just completed such a patch, which I'm
   going to apply upstream, so depending when the transition is
   schedule we can either apply the patch or package a newer upstream
   version if one has been released by then.  I'm an uploader for this
   package, so can easily do either.

The auto-generated tracker looks good to me:
https://release.debian.org/transitions/html/auto-xapian-core.html

Cheers,
Olly


signature.asc
Description: PGP signature

Bug#836585: celery: FTBFS in testing (failing tests)

[Paul Wise]

On Sun, 4 Sep 2016 11:54:01 +0200 (CEST) Santiago Vila wrote:

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

I can't reproduce this build failure using `pdebuild --debbuildopts -A`.

Which version of python-openssl did you have installed?

I have version python-openssl 16.1.0-1 installed.

It looks like this issue was fixed by skipping PyOpenSSL tests on Python 3:

$ egrep -iC3 'test_unmatched_key_cert|test_unknown_source' ../*.build
test_self_send (celery.tests.security.test_serialization.test_SecureSerializer) 
... ok
test_separate_ends 
(celery.tests.security.test_serialization.test_SecureSerializer) ... ok
test_serialize (celery.tests.security.test_serialization.test_SecureSerializer) 
... ok
test_unknown_source 
(celery.tests.security.test_serialization.test_SecureSerializer) ... ok
test_unmatched_key_cert 
(celery.tests.security.test_serialization.test_SecureSerializer) ... ok
test_AsyncResult_when_not_registered 
(celery.tests.tasks.test_canvas.test_Signature) ... ok
test_INVERT (celery.tests.tasks.test_canvas.test_Signature) ... ok
test_OR (celery.tests.tasks.test_canvas.test_Signature) ... ok
--
test_self_send (celery.tests.security.test_serialization.test_SecureSerializer) 
... SKIP: PyOpenSSL does not work on Python 3
test_separate_ends 
(celery.tests.security.test_serialization.test_SecureSerializer) ... SKIP: 
PyOpenSSL does not work on Python 3
test_serialize (celery.tests.security.test_serialization.test_SecureSerializer) 
... SKIP: PyOpenSSL does not work on Python 3
test_unknown_source 
(celery.tests.security.test_serialization.test_SecureSerializer) ... SKIP: 
PyOpenSSL does not work on Python 3
test_unmatched_key_cert 
(celery.tests.security.test_serialization.test_SecureSerializer) ... SKIP: 
PyOpenSSL does not work on Python 3
test_AsyncResult_when_not_registered 
(celery.tests.tasks.test_canvas.test_Signature) ... ok
test_INVERT (celery.tests.tasks.test_canvas.test_Signature) ... ok
test_OR (celery.tests.tasks.test_canvas.test_Signature) ... ok

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#835967: Also hitting this.

[Paul Wise]

I've had a look at this, everyone seems to be complaining about the
Leaseweb replica but I haven't been able to reproduce the problems
that have been reported.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#837629: u-boot 2016.09~rc2+dfsg1-1 bricks my openrd ultimate

[Rick Thomas]

Package: u-boot
Version: 2016.09~rc2+dfsg1-1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
As requested by Vagrant I'm testing u-boot 2016.09~rc2+dfsg1-1 on my OpenRD 
Ultimate machine.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I followed the instructions for upgrading u-boot on Martin's web page at
 https://www.cyrius.com/debian/kirkwood/openrd/uboot-upgrade/
   * What was the outcome of this action?
After telling u-boot to "reset", the machine went dead.  There was no output on 
the serial console, no answer to ping ... nothing.
   * What outcome did you expect instead?
I expected it to reset and reboot.  But it didn't do that.

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

I unbricked it follwing the instructions at
https://www.newit.co.uk/forum/index.php?topic=2835.0
and I'm writing this bugreport on it.  It boots using
U-Boot 2016.03+dfsg1-3 (Apr 04 2016 - 18:23:06 +)

Please advise what I can do to help debug this.


-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (900, 'stable-updates'), (900, 'testing'), (900, 'stable'), (50, 
'unstable')
Architecture: armel (armv5tel)

Kernel: Linux 4.6.0-1-marvell
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Bug#837628: Removal of Heimdal from testing

[jelmer]

Package: libkadm5-heimdal-perl
Severity: normal

Just an FYI to let you know that the heimdal maintainers are planning to remove 
Heimdal from testing because of its upstream state. (See the severe bugs filed 
against it for details)

For other packages that are built against heimdal, we have suggested building 
against MIT instead. That is probably not as easy as option here.

Bug#816593: (no subject)

[taro110]

Hi, after checking some information, I guessyour error will be fixed if

1. you add -lrt flag appropriately.

or

2. you upgrade glibc (libc6 package)
from 2.13 to 2.19.

For more detail, you can see this thread:
http://stackoverflow.com/questions/2418157/ubuntu-linux-c-error-undefined-reference-to-clock-gettime-and-clock-settim

By the way, upgrading libc6 from 2.13 to 2.19
almost means upgrading from Wheezy to Jessie.
https://packages.debian.org/search?suite=default=all=any=names=libc6
If you try this build on Jessie, you won't have error any more.

Also, please note that the main stream support of
Wheezy already finished.
(Now, only LTS support which is all about security.)

This means this subject should be "Normal bugs; Will Not Fix".  Taro

Bug#836251: linux: [armhf] Please enable support for veyron-speedy

[Vagrant Cascadian]

On 2016-08-31, Vagrant Cascadian wrote:
> Please enable support for veyron-speedy (a.k.a. ASUS Chromebook C201)
> to linux 4.8.x.
...
> Haven't had success getting output form the speakers or headphone
> jack, though the OS seems to detect at least one device.

headphone jack works, too!


live well,
  vagrant


> diff --git a/debian/config/armhf/config b/debian/config/armhf/config
> index 0a9be6f..4fc638c 100644
> --- a/debian/config/armhf/config
> +++ b/debian/config/armhf/config
> @@ -1262,3 +1263,28 @@ CONFIG_SND_SOC_TEGRA_ALC5632=m
>  CONFIG_SND_SOC_TEGRA_MAX98090=m
>  CONFIG_SND_SOC_TEGRA_RT5677=m
>  
> +CONFIG_BATTERY_SBS=m
> +CONFIG_DRM_PANEL=y
> +CONFIG_DRM_PANEL_SIMPLE=m
> +CONFIG_BACKLIGHT_PWM=m
> +CONFIG_CHARGER_GPIO=m
> +CONFIG_MFD_CROS_EC=m
> +CONFIG_I2C_CROS_EC_TUNNEL=m
> +CONFIG_MOUSE_ELAN_I2C=m
> +CONFIG_KEYBOARD_CROS_EC=m
> +CONFIG_KEYBOARD_GPIO=m
> +CONFIG_POWER_RESET_GPIO=y
> +CONFIG_POWER_RESET_GPIO_RESTART=y
> +CONFIG_MFD_RK808=y
> +CONFIG_COMMON_CLK_RK808=m
> +CONFIG_REGULATOR_RK808=m
> +CONFIG_RTC_DRV_RK808=y
> +CONFIG_PHY_ROCKCHIP_DP=m
> +CONFIG_MFD_CROS_EC_SPI=m
> +CONFIG_ROCKCHIP_DW_MIPI_DSI=m
> +CONFIG_DRM_ANALOGIX_DP=m
> +CONFIG_ROCKCHIP_ANALOGIX_DP=m
> +CONFIG_PHY_ROCKCHIP_EMMC=m
> +CONFIG_ROCKCHIP_IODOMAIN=m
> +CONFIG_POWER_AVS=y
> +CONFIG_ROCKCHIP_PM_DOMAINS=y


signature.asc
Description: PGP signature

Bug#837627: [armhf] linux-image-4.7.0-1-armmp: Enable options for Novena

[Vagrant Cascadian]

Package: linux
Version: 4.7.2-1
Severity: wishlist
Tags: patch

Please enable the following options to add support for hardware
present on Novena systems.

Thanks!

live well,
  vagrant

diff --git a/debian/config/armhf/config b/debian/config/armhf/config
index 0a9be6f..d17e003 100644
--- a/debian/config/armhf/config
+++ b/debian/config/armhf/config
@@ -1262,3 +1262,10 @@ CONFIG_SND_SOC_TEGRA_ALC5632=m
 CONFIG_SND_SOC_TEGRA_MAX98090=m
 CONFIG_SND_SOC_TEGRA_RT5677=m
 
+CONFIG_BACKLIGHT_PWM=m
+CONFIG_DRM_PANEL_SIMPLE=m
+CONFIG_MFD_STMPE=y
+CONFIG_TOUCHSCREEN_STMPE=m
+CONFIG_SND_SOC_IMX_ES8328=m
+CONFIG_BATTERY_SBS=m
+CONFIG_MMA8452=m


signature.asc
Description: PGP signature

Bug#837341: [Pkg-openldap-devel] Bug#837341: libldap fails to connect to ldaps servers without the ca-certificates package installed

[Ryan Tandy]

Control: tag -1 confirmed

On Sat, Sep 10, 2016 at 09:37:17PM +0300, Tero Marttila wrote:
The package libldap-2.4-2 ships a default configuration file for 
/etc/ldap/ldap.conf with the following:



TLS_CACERT  /etc/ssl/certs/ca-certificates.crt


It appears that libldap fails to connect to any ldaps servers if the 
ca-certificates.crt file is missing, even if using 'TLS_REQCERT 
allow'. Installing the ca-certificates package allows the connection 
to succeed.


Thanks for the detailed report. Reproduced here, exactly as you said.

Looks like what's happening is gnutls_certificate_set_x509_trust_file() 
returns an error, and we bail out straight away. TLS_REQCERT allow does 
indeed work as advertised with cert errors during the handshake, but we 
never make it to that point.


I don't think redefining TLS_REQCERT to permit this invalid 
configuration would be the right thing to do, but there's certainly room 
for improved logging here.


I suspect that the libldap package should have a Depends: on the 
ca-certificates package if this file is required for the correct 
operation of libldap?


I don't think that would be correct, as the library operates just fine 
if you comment out that default or point it at your own CA store.


In unstable, it looks like gnutls is now built with a default system 
trust store configured, so we may be able to drop that TLS_CACERT 
default altogether. I'll look into that.

Bug#836925: u-boot: installation report for u-boot and u-boot-tools 2016.09~rc2+dfsg1-1

[Rick Thomas]

On Sep 12, 2016, at 2:30 PM, Vagrant Cascadian  wrote:

> Control: severity 836925 important
> 
> On 2016-09-07, Rick Thomas wrote:
>> I installed the new u-boot using the procedure in
>> /usr/share/doc/u-boot/README.Debian
>> 
>> The newly installed u-boot loaded and executed after a linux "reboot"
>> command.
>> 
>> Unfortunately it destroyed the u-boot environment, so it tried to boot
>> using the default env.  This failed to boot Linux.
> 
> What version of u-boot were you upgrading from?

I’m pretty sure it was “U-Boot 2016.01-rc3+dfsg1-3 (Jan 02 2016 - 23:19:11 
+)".  That’s the version on its twin.  I’m pretty sure I upgraded them both 
at the same time with the same version.

In case it matters, the /boot partition is on the SDcard.

> 
> The u-boot env values were changed somewhere around 2016.01, possibly:
> 
>  https://bugs.debian.org/781874
> 
> Or has the u-boot environment configuration changed again since then?

It seems likely that the environment configuration changed between 
2016.01-rc3+dfsg1-3 and 2016.09~rc2+dfsg1-1.  Would it be possible for you to 
check that?

> I went to Martin's page,
>> https://www.cyrius.com/debian/kirkwood/sheevaplug/install/ , and
>> followed the instructions there to restore the environment for booting
>> from the SD card.  I also had to restore the "ethaddr" u-boot
>> environment variable.
> 
>> After having restored the u-boot environment, I issued a "reset", and
>> it then happily booted as expected.
> 
>> I'd recommend that /usr/share/doc/u-boot/README.Debian give a warning
>> about needing to restore the u-boot environment, at least for the
>> sheevaplug.
> 
> Or NEWS.Debian, given that it can actually cause a failure to
> boot.

Yeah, you’re right.  NEWS.Debian would be the right place.

> If you could propose some text describing the issue, when it is
> encountered, and what to do about it, that would be helpful; the details
> of the issue are a bit unclear to me to start writing anything.

If you can verify exactly when the environment config changed, I’ll try to 
describe what I did to fix the problem.

> live well,
>  vagrant

Bug#772190: Debian bug reports for aufs-utils

[J. R. Okajima]

Jan Luca Naumann:
> Both reported problems seem not to be fixed in the current version yet
> so you want to fix them maybe :-)

Thanx lettng me know. I didn't know that.

I don't think these are bugs since they are following "Dashism" instead
of "Bashism." I understand that debian has a policy to be
posix-compliant shell script, but DASH (which debian recommends)
supports these non-posix-compliant features. I don't know why this
contradiction happes. Maybe there are too many scripts using these
features in our real world?

As an upstream developer, I won't fix them because it is a debian local
policy. But someday if DASH stops supporting these features, I will
re-consider. More simply if someone who really cares the policy sends a
patch to me (which must be a generic solution for other shells too), I
will probably re-consider too.

IIRC, there was a similar discussion on aufs-uses ML about "test cond1
-a cond2" vs "test cond1 && test cond2". My conclusion was same, ie. it
was supported by DASH.


J. R. Okajima

Bug#777559: Debian bug reports for aufs-utils

[J. R. Okajima]

Jan Luca Naumann:
> Both reported problems seem not to be fixed in the current version yet
> so you want to fix them maybe :-)

Thanx lettng me know. I didn't know that.

Yes, this is an aufs bug. Thanx for reporting and fixing.
As an upstream developer, I will merge and release the patch in next
week with adding these tags in the commit.

Reported-by: Torok Edwin 
Fixed-by: Henrik Ahlgren 

But currently aufs-utils.git (the debian pkg name is aufs-tools)
supports the versions for linux-v4.1 and later. It means the upsteam fix
goes to the "future" for aufs-tools pkg and it doesn't affect debian.
It might be one reason that no one had ever forwarded me this report.
Anyway I don't think it a big problem since aufs-tools has already
contained the fix.

FYI, The versions in this report are
- aufs-tools1:3.2+20130722-1.1
- linux-image   3.16.7-ckt2-1

and the aufs supported version history is
- 3.2   Unsupported since Nov 2013
- 3.16  Unsupported since Oct 2015


J. R. Okajima

Bug#837626: New upstream version 23 available

[Michael Biebl]

Source: kmod
Version: 22-1.1
Severity: wishlist

Hi Marco,

there is a new upstream version 23 available:
http://permalink.gmane.org/gmane.linux.kernel/2269953

Would be nice to have this packaged for Debian.

Cheers,
Michael


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

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

-- no debconf information

Bug#835967: Also hitting this.

[Kris Shannon]

%  wget 
http://snapshot.debian.org/archive/debian/20160325T044307Z/dists/jessie/main/source/Sources.gz
--2016-09-13 11:37:22--
http://snapshot.debian.org/archive/debian/20160325T044307Z/dists/jessie/main/source/Sources.gz
Resolving snapshot.debian.org (snapshot.debian.org)...
2001:1af8:4020:b030:deb::185, 2001:630:206:4000:1a1a::c13e:ca1e,
193.62.202.30, ...
Connecting to snapshot.debian.org
(snapshot.debian.org)|2001:1af8:4020:b030:deb::185|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/octet-stream]
Saving to: ‘Sources.gz’

Sources.gz[
<=>
]   2.17M   315KB/sin 8.1s

2016-09-13 11:37:31 (276 KB/s) - Read error at byte 2277376 (Success).Retrying.

Bug#836885: [Pkg-openldap-devel] Bug#836885: please stop building against Heimdal

[Ryan Tandy]

Control: tag -1 confirmed

Will do. Thanks for the heads-up.

Bug#837012: tachyon: FTBFS: ld: tachyon_ogl-glwin.o: undefined reference to symbol 'XNextEvent'

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello Lucas, thanks for the report.



On 07/09/16 23:18, Lucas Nussbaum wrote:
> Source: tachyon
> Version: 0.99~b6+dsx-5
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20160906 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
>> /bin/bash ../libtool  --tag=CC   --mode=link gcc -Wno-unused-result 
>> -I/usr/include/libdrm -I/usr/include/libdrm -g -O3 
>> -fdebug-prefix-map=/<>/tachyon-0.99~b6+dsx=. -fPIE 
>> -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT 
>> -ffast-math -fomit-frame-pointer   -o tachyon-ogl tachyon_ogl-main.o 
>> tachyon_ogl-getargs.o tachyon_ogl-parse.o tachyon_ogl-nffparse.o 
>> tachyon_ogl-mgfparse.o tachyon_ogl-ac3dparse.o tachyon_ogl-glwin.o 
>> tachyon_ogl-spaceball.o tachyon_ogl-trackball.o ../src/libtachyon.la -lm 
>> -lGL  -lGL 
>> libtool: link: gcc -Wno-unused-result -I/usr/include/libdrm 
>> -I/usr/include/libdrm -g -O3 
>> "-fdebug-prefix-map=/<>/tachyon-0.99~b6+dsx=." -fPIE 
>> -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT 
>> -ffast-math -fomit-frame-pointer -o .libs/tachyon-ogl tachyon_ogl-main.o 
>> tachyon_ogl-getargs.o tachyon_ogl-parse.o tachyon_ogl-nffparse.o 
>> tachyon_ogl-mgfparse.o tachyon_ogl-ac3dparse.o tachyon_ogl-glwin.o 
>> tachyon_ogl-spaceball.o tachyon_ogl-trackball.o  ../src/.libs/libtachyon.so 
>> -lm -lGL
>> /usr/bin/ld: tachyon_ogl-glwin.o: undefined reference to symbol 'XNextEvent'
>> //usr/lib/x86_64-linux-gnu/libX11.so.6: error adding symbols: DSO missing 
>> from command line
>> collect2: error: ld returned 1 exit status
> 
> The full build log is available from:
>
> http://people.debian.org/~lucas/logs/2016/09/06/tachyon_0.99~b6+dsx-5_unstable.log

I could reproduce the issue in a chroot environment.
I am working on it.


> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.
> 

Thanks,
Jerome

- -- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B
-BEGIN PGP SIGNATURE-

iQQcBAEBCgAGBQJX101PAAoJED+SGaZ/NsaLFKEf/jJj8WCg4UkPgR577HQQjIEQ
Cf57htSrZ21id9z3WSV5kI56Bd7hr2nP/6gPme5O1RxdhKpCA4G8ZyVpVMgiVV2e
4SYklDUJACj902uDj5//5i9HoOK1S6W6iFc7qAT92q2H9HD56eSw6xaT0//Lfmlp
nStHRFO4AvVg2i1KmvK2YBrW/DDnYRA4SIf2m0ESXIISA6CDzuRiNgk/C6DwKGO1
lusHHwLXStGKnb/A1OYDyz1tyeP4PdxoJiSOYPWdmqlw5Mb13UXuPesAR8YpSPjo
PoItPxPGxkG0lIcxuIVxLWUB9jM/jtdF0s94IU8HbgU6BHjnXYntx0cnbEcKEfPK
BNZnbkoNWCmfhlOeeB0M114p4WUiedrkXjIU+qEWZP1uEh7dX1FnfMlxutgL9q3g
2SwZovd55VEnZEs5kWdoqfUCBLHvBoHxI3rZRBl0SGe29ljcwu6NlUyb//DuCum4
HSb7L3ShKX9MLzPLPbruSIeJdmaIt2AjNMiOLCCsfgS3F6berFtXm3k5maPddvuC
wUVVbHvdP+La4meTWjQ+CBnfOs4BxzG2vA5AVBjYMY8B6/eJ6wmuiJ8W98rOMz59
VrUFPZh3CdPN/0TIz2jH14u4U1TfHz7nTfZ4PBRzvycz0tU0xya6g7IuM30rExpo
ARznnvc394rlKe5V9d/ewXzMPpgzcMEIA09a9G4CnP9uNDYhVHe0m8FuW3LLfoQg
47lwYgRho9FBabo5TXU6CJOUv8zt4wyhAqWLzL4h8y8x/xlh5dBNnEEqH2FGVhov
haRBEdlv+0LpnqyCYaKKFD+fmYkw9QrwH+P7B1c1p4MfTPDSEd3PFoT5ySiq1CDb
dWF1f1mzzZI6CvwIl02WKfrxcPw0O4x7S3cKjdL9hIihQ4IYEmxxkDMbZJKI5t5X
MidKSdiXZmF2X1DGqcmkMEVPTJOWQvAJmzmNTCUjjkeMbZGmWq7fsR+qeMGd4OQN
mWTYVcuaFrTXfQLfFDXW2tQ5fGzm1hhra9iwbmEcsiPJqKWlEjX8d8BkuCwoHI7u
ky/GUxj0pn3evbeo0086dY5bV7naopxTc5zsYCXJgMhDZkHjF6kpxunA+dJgAd2i
ty1cZ6z5YMuW1d7vi/iVsJ9QdaHbmAMw7QmB/d5TYBNo8/OTVUE/i9AundmUyb6g
bMJ2JfPowczhGZOKjx+GRwLGdRWmNLPYH02y2eoH3/jvmfCIK41aMu4HgFUbYAeC
twoTSeUU8sW8D10T/KGWmkb48dyp3TCaAlJwo0LPX2beM/E3VydnfuM0rBgv4nSp
fX5RJYriTMeWmeXH8kepAEKmaYnDfamT4tE0U/Q7BX9U4MtEWbbxUHUlqj92wiI=
=3XQj
-END PGP SIGNATURE-

Bug#591430: Jessie-Backport for xserver-xorg-core

[Christopher Studer]

Can we get an xserver-xorg-core backport for use with jessie. I have talked
to upstream and the fix seem to be in 1.18 > .

https://bugs.freedesktop.org/show_bug.cgi?id=9209

Just wondering if we can get that version somehow in jessie?

This would really help fix the issues.

Thanks,
CS

Bug#837541: gambas3: FTBFS with bindnow and PIE enabled

[Bálint Réczey]

Hi Gianfranco,

2016-09-12 13:49 GMT+02:00 Gianfranco Costamagna
:
> control: tags -1 patch
>
> Hi Balint
>
>>During a rebuild of all packages in sid, your package failed to build on
>>amd64 with patched GCC and dpkg.
>
>
> looking at the error, I would say gambas is using an unexisting function
>
>
>>c_window.c:563:19: warning: implicit declaration of function 
>>'SDL_GetWindowId' [-Wimplicit-function-declaration]
>>GB.ReturnInteger(SDL_GetWindowId(WINDOW));
>>
>
>>/<>/debian/tmp/usr/bin/gbi3: symbol lookup error: 
>>/<>/debian/tmp/usr/lib/gambas3/gb.sdl2.so: undefined symbol: 
>>SDL_GetWindowId
>
> it might be because of a lower/uppercase issue, at least according to google 
> and libsdl2.
>
> Can you please try the following attached diff?
>
> -   GB.ReturnInteger(SDL_GetWindowId(WINDOW));
> +   GB.ReturnInteger(SDL_GetWindowID(WINDOW));


Thanks, it fixed the build.

Cheers,
Balint

Bug#94164:

[Katherine LeBlanc]

Business Proposal kindly view attach for more detail!!!
CONFIDENTIALITY NOTICE: This email and any attachment(s) are intended for a 
specific person(s). It may contain privileged or confidential information. If 
you are not the intended recipient, do not distribute or copy it. Please delete 
and advise me by return email or telephone. Thank you.
AVIS DE CONFIDENTIALIT?: Ce courriel (et toute pi?ce jointe) est destin? 
strictement ? son ou ses destinataire(s). Son contenu peut ?tre confidentiel ou 
privil?gi?. Si cette communication vous est parvenue par erreur, veuillez ne 
pas la distribuer et ne pas la reproduire. Veuillez la supprimer enti?rement de 
tout syst?me ?lectronique et m'aviser imm?diatement par retour de courriel ou 
par appel t?l?phonique. Merci.


Business Deal!!!.docx
Description: Business Deal!!!.docx

Bug#837625: Debian on a TrekStor MiniPC W2/Type2 (fanless) installed. Audio not working, sometimes not booting.

[christina_c]

 

Package: installation-reports
Severity: normal

Dear Maintainer,

No errors during the installation process, but 2 problems:
- about every 2nd time freeze at boot
- audio not working

[ 31.283772] ioremap error for 0x7bbc9000-0x7bbca000, requested 0x2, got
0x0
[ 31.283952] esrt: ioremap(0x7bbc9f10, 56) failed.
/dev/mmcblk2p2: clean, 105404/726240 files, 804455/2902832 blocks
[ 34.874968] intel_sst_acpi 80860F28:00: firmware: failed to load
intel/fw_sst_0f28.bin (-2)
[ 34.875156] intel_sst_acpi 80860F28:00: request fw failed
System stops booting at this point, but once successfully booted, it is
running stable.

some dmesg-output:
[ 31.284850] ioremap error for 0x7bbc9000-0x7bbca000, requested 0x2, got
0x0
[ 31.285320] esrt: ioremap(0x7bbc9f10, 56) failed.
...
[ 34.939128] intel_sst_acpi 80860F28:00: firmware: failed to load
intel/fw_sst_0f28.bin (-2)
[ 34.939313] intel_sst_acpi 80860F28:00: Direct firmware load for
intel/fw_sst_0f28.bin failed with error -2
[ 34.939321] intel_sst_acpi 80860F28:00: request fw failed
...
[ 35.059777] WARNING: CPU: 3 PID: 680 at
/build/linux-sI189k/linux-4.6.4/drivers/pinctrl/intel/pinctrl-baytrail.c:212
byt_gpio_request+0x9a/0xd0
...
[ 54.301776] intel_sst_acpi 80860F28:00: firmware: failed to load
intel/fw_sst_0f28.bin (-2)
[ 54.301788] intel_sst_acpi 80860F28:00: Direct firmware load for
intel/fw_sst_0f28.bin failed with error -2
[ 54.301795] intel_sst_acpi 80860F28:00: fw is returning as null
[ 54.301801] intel_sst_acpi 80860F28:00: FW download fail -22
[ 54.302275] Baytrail Audio Port: ASoC: no backend DAIs enabled for
Baytrail Audio Port
[ 54.302674] Baytrail Audio Port: ASoC: no backend DAIs enabled for
Baytrail Audio Port
[ 54.302960] Baytrail Audio Port: ASoC: no backend DAIs enabled for
Baytrail Audio Port
[ 54.303952] Baytrail Audio Port: ASoC: no backend DAIs enabled for
Baytrail Audio Port
... (some hundred times this llne)

-- Package-specific info:

Boot method: USB memory stick
Image version: Debian GNU/Linux testing "Stretch" - Official Snapshot
i386 NETINST - Binary-1 20160829-05:41
Date: 29. Aug. 2016

Machine: TrekStor MiniPC W2/Type2 - Board Product Name, BIOS
TREK.W8.RNNN02 11/24/2015 - EFI v2.40 by INSYDE Corp.
Partitions: Model: SD SS32G (sd/mmc)
Disk /dev/mmcblk2: 31,9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number Start End Size File system Name Flags
 1 1kB 110MB 100MB fat32 primary boot, esp
 2 110MB 12,0GB 11,9GB ext4 primary
 3 12,0GB 31,9GB 19,9GB ext4 primary

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot: [O]
Detect network card: [O]
Configure network: [O]
Detect usb stick: [O]
Load installer modules: [O]
Clock/timezone setup: [O]
User/password setup: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Install base system: [O]
Install tasks: [O]
Install boot loader: [ ]
Overall install: [O]

Comments/Problems:

I installed Debian onto a microSD card with its own 100 MB
EFI-partition.
systemd-boot:
Initially at installation I mounted the EFI-partition at /boot/ with the
kernel and initrd.img on the EFI-partion.
I did not install a boot loader. In rescue mode of the installer and
/dev/mmcblk2p2 mounted at /:
bootctl --no-variables --path /boot/ install 
After the first boot I changed the mountpoint of the EFI-partition to
/boot/efi/ with a copy of kernel and initrd.img on it
and installed systemd-boot new from within the booted system. It seemed
that in rescue-shell bootctl --path /boot/efi/ doesn't work.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20160829-00:34"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux christina1 4.6.0-1-686 #1 SMP Debian 4.6.4-1
(2016-07-18) i686 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Atom Processor
Z36xxx/Z37xxx Series SoC Transaction Register [8086:0f00] (rev 0f)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: Kernel driver in use: iosf_mbi_pci
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation
Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev
0f)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Atom
Processor Z36xxx/Z37xxx Series USB xHCI [8086:0f35] (rev 0f)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:1a.0 Encryption controller [1080]: Intel Corporation Atom
Processor Z36xxx/Z37xxx Series Trusted Execution Engine [8086:0f18] (rev
0f)
lspci -knn: Subsystem: Intel Corporation Device [8086:7270]
lspci -knn: 

Bug#836347: gkrellweather: weather.noaa.gov has been shut down

[Dario Andres Susman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

This has fixed the problem for me as well.

Thank you Roland!

Cheers,
Dario Susman

On Fri, 02 Sep 2016 01:18:06 +0200 Roland Hieber   
wrote:

> Package: gkrellweather
> Version: 2.0.8-2
> Severity: grave
> Tags: patch
> Justification: renders package unusable
>
> Dear Maintainer,
>
> weather.noaa.gov has been shut down [0], and the METAR data is now  
available on

> a different site. This patch works for me:
>
> - snip  
- -

> --- a/gkrellweather-2.0.8/GrabWeather
> +++ b/gkrellweather-2.0.8/GrabWeather
> @@ -11,8 +11,7 @@
>  #
>
>  $ReportDir  = '.wmWeatherReports';
> -#$WeatherSrc = 'ftp://weather.noaa.gov/data/observations/metar/decoded' 
;
> -$WeatherSrc = 'http://weather.noaa.gov/pub/data/observations/metar/decoded' 
;
> +$WeatherSrc = 'http://tgftp.nws.noaa.gov/data/observations/metar/decoded' 
;

>
>  use strict;
>  use vars qw( $ReportDir $WeatherSrc );
> - snip  
- -

>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing-debug
>   APT policy: (500, 'testing-debug'), (500, 'testing'), (170,  
'unstable'), (1, 'unstable-debug'), (1, 'experimental')

> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.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 gkrellweather depends on:
> ii  gkrellm 2.3.7-1
> ii  libatk1.0-0 2.20.0-1
> ii  libc6   2.23-4
> ii  libcairo2   1.14.6-1+b1
> ii  libfontconfig1  2.11.0-6.5
> ii  libfreetype62.6.3-3+b1
> ii  libglib2.0-02.48.1-2
> ii  libgtk2.0-0 2.24.30-4
> ii  libpango1.0-0   1.40.1-1
> ii  libwww-perl 6.15-1
> ii  perl5.22.2-3
> ii  wget1.18-2+b1
>
> gkrellweather recommends no packages.
>
> gkrellweather suggests no packages.
>
> -- no debconf information
>
> 
-BEGIN PGP SIGNATURE-

Version: GnuPG v1.4.11 (Darwin)

iF4EAREIAAYFAlfXOGIACgkQq6Svsk8XewD06wEAlVl9kXH2fRJ1DY2jHG+eLwHf
dmmyHNkbvYR14jVugPsA/1hFyrBhgfi0l/gTuukltQuzjweMFBNs3FrK2j3g4cdK
=DCaq
-END PGP SIGNATURE-

Bug#825217: Response to Debian Bug #825217

[Deniz Akcal]

For what it's worth, I too am interested in having this packaged in the 
official Debian repositories. 

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

[Pete Batard]

Yes! At long last 231-6 seems to have cleared the systemd issue I was 
observing on Raspberry Pi:


--
root@pi ~ # systemctl status
● pi
State: running
 Jobs: 0 queued
   Failed: 0 units
--

Many thanks to the people who spent time on this!

Regards,

/Pete

Bug#837624: golang-goleveldb: FTBFS in testing (failing tests)

[Santiago Vila]

Note: Yes, I know that this bug is apparently similar to #834959,
but I have been advised that it's better to err on the side of filing
duplicate bugs than mixing two different problems in the same bug
report (which usually results in a big mess).

Whether they are the same or not, I don't really know, but I hope you
can determine it.

Thanks.

Bug#835587: openconnect + gnutls: Re: Bug#835587: still not working for me

[Daniel Kahn Gillmor]

On Mon 2016-09-12 11:38:21 +0200, Andreas Bourges wrote:

> ...just wanted to let you know that the latest updates in sid seem to fix my 
> problem. Looks like I did something wrong, when applying the patch or when 
> downgrading to the snapshot packages.
>
> Anyway - using the new packages for >2h now and had no hang!

I was also having the problem with openconnect hanging with "dead peer
detected" when using openconnect.

I can confirm that upgrading libgnutls30 from 3.5.3-4 to 3.5.4-2 also
seems to have resolved the problem for me.

thanks for the work sorting this out!

   --dkg


signature.asc
Description: PGP signature

Bug#827936: [Po4a-devel] Bug#827936: po4a: please implement support for Ruby document format

[Martin Quinson]

> Are you willing to convert my tests to a proper test integrated in po4a
> test infrastructure?
> I really hope you are, since I am not knowledgeable enough to do so by
> myself...

Yes I am. But that's 10 years since the last time I added something
into the t/ directory, so I have to check again. Times are really
packed right now for me, so po4a will have to way a few days/weeks.
I am preparing my lecture of tomorrow morning and afterward, I have
some paperwork to fill for my administration for tomorrow too.

Sorry about the delay. Maybe you could try to have a look in t/ if I'm
too slow. I'd be sorry about it, but I cannot do much better.

Sorry, Mt.

-- 
The greatest performance improvement of all is when a system goes from
not-working to working.  -- Osterhaut


signature.asc
Description: PGP signature

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

[Santiago Vila]

retitle 837613 libconfig-model-itself-perl: FTBFS in sid (failing tests)
thanks

Here is the build log in sid. It uses libconfig-model-perl version 2.090-1.

My guess is that this is not really the same bug (well, it may still be
"essentially the same bug", just in a different package :-).

Ok to reopen?

Thanks.

libconfig-model-itself-perl_2.005-1_amd64-20160912T221114Z.gz
Description: application/gzip

Bug#813754: [Pkg-mpd-maintainers] Bug#813754: Bug#813754: Can't open port 6600 when run syste, -wide vis systemd

[Florian Schlichting]

On Mon, Sep 12, 2016 at 06:36:00PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> I expect that, if the daemon is not running and a client tries to connect to 
> port 6600 then systemd will start the daemon and the client wouldn't even 
> notice it.

yes, and that works for me.


1) There is no mpd running, mpd.service is inactive, while mpd.socket is
active and PID 1/systemd is listening on port 6600:

[fs@tp] 1 (~): pgrep mpd
(empty)

[fs@tp] 2 (~): systemctl status mpd.service
 mpd.service - Music Player Daemon
   Loaded: loaded (/lib/systemd/system/mpd.service; disabled; vendor preset: 
enabled)
   Active: inactive (dead) since Di 2016-09-13 00:10:44 CEST; 9s ago
[...]

[fs@tp] 3 (~): systemctl status mpd.socket
 mpd.socket
   Loaded: loaded (/lib/systemd/system/mpd.socket; disabled; vendor preset: 
enabled)
   Active: active (listening) since Di 2016-09-13 00:09:40 CEST; 1min 23s ago
   Listen: /run/mpd/socket (Stream)
   [::]:6600 (Stream)

[fs@tp] 4 (~): sudo netstat -lntp | grep 6600
tcp6   0  0 :::6600 :::*LISTEN  
1/systemd



2) Now if I issue a command to the socket (either through mpc or by
starting up MPDroid), the mpd.service unit is activated, an mpd process
is started, but port 6600 still seems to be owned by systemd:

[fs@tp] 5 (~): mpc -h localhost play
Adele/Adele - Hello.mp3
[playing] #2/3   0:14/6:07 (3%)
volume: n/a   repeat: off   random: off   single: off   consume: off

[fs@tp] 6 (~): systemctl status mpd.service
 mpd.service - Music Player Daemon
   Loaded: loaded (/lib/systemd/system/mpd.service; disabled; vendor preset: 
enabled)
   Active: active (running) since Di 2016-09-13 00:12:48 CEST; 15min ago

[fs@tp] 7 (~): pgrep mpd
25884

[fs@tp] 8 (mpd/mpd): sudo netstat -lntp | grep 6600
tcp6   0  0 :::6600 :::*LISTEN  
1/systemd


> That's not happening.

I can't imagine why that may be. Are you sure you're running with the same mpd
config in both cases, and it's not just an artefact of systemd starting
an mpd with an empty music database?

> > netstat output doesn't show
> > "mpd", but everything still works as one would expect, no?
> 
> No, the client can't reach the server unless I start mpd as described in the 
> bug.

Since netstat shows "something" listening on port 6600, what does 

mpc -h localhost status

show? What do you get when you 'telnet localhost 6600'?

Florian

Bug#722496: debdiff v2

[Dan Streetman]

sorry, there was a problem with the last patch; it didn't work if the
vlan interface already existed, even if the raw device mtu was too
low.  this updated debdiff checks and increases the dev mtu even if
the vlan interface already exists.
diff -u vlan-1.9/debian/changelog vlan-1.9/debian/changelog
--- vlan-1.9/debian/changelog
+++ vlan-1.9/debian/changelog
@@ -1,3 +1,10 @@
+vlan (1.9-3.3) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Increase vlan raw device mtu if less than vlan mtu. (Closes: #722496)
+
+ -- Dan Streetman   Fri, 09 Sep 2016 09:03:11 
-0400
+
 vlan (1.9-3.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u vlan-1.9/debian/network/if-pre-up.d/vlan 
vlan-1.9/debian/network/if-pre-up.d/vlan
--- vlan-1.9/debian/network/if-pre-up.d/vlan
+++ vlan-1.9/debian/network/if-pre-up.d/vlan
@@ -49,6 +49,14 @@
   ;;
 esac
 
+if [ -n "$IF_MTU" -a -n "$IF_VLAN_RAW_DEVICE" ]; then
+CUR_DEV_MTU=`cat /sys/class/net/$IF_VLAN_RAW_DEVICE/mtu`
+# increase the vlan raw device mtu if needed
+if [ -n "$CUR_DEV_MTU" ] && [ $CUR_DEV_MTU -lt $IF_MTU ]; then
+ip link set dev $IF_VLAN_RAW_DEVICE mtu $IF_MTU
+fi
+fi
+
 if [ -n "$IF_VLAN_RAW_DEVICE" ]; then
 if [ ! -x /sbin/vconfig ]; then
 exit 0

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

[Santiago Vila]

I am not even sure that we are doing it right.

I've just built libconfig-model-itself-perl in sid.

The libconfig-model-perl version used in the build-dependency was
2.090-1, which is supposed to be the fixed version.

And the package failed to build as well.

So: Are you sure that it was libconfig-model-perl who made
libconfig-model-itself-perl to fail?

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

[gregor herrmann]

On Mon, 12 Sep 2016 23:24:03 +0100, Santiago Vila wrote:

> > > If, OTOH, you mean that the reason this package fails is in another
> > > package which is in the build-depends of this one, then please use
> > > affects to avoid more duplicates.
> > Everything there already :)
> > https://bugs.debian.org/libconfig-model-itself-perl shows #837133.
> Oh, I see.
> But when a package may not be built at all, the bug is really in the
> source package, not in any of the binary packages, which do not even exist.

Ah, good point, thank you for fixing the affects.
 

Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

[Santiago Vila]

affects 837133 = src:libconfig-model-itself-perl
thanks

On Tue, Sep 13, 2016 at 12:10:09AM +0200, gregor herrmann wrote:
> On Mon, 12 Sep 2016 22:57:08 +0100, Santiago Vila wrote:
> 
> > > This is a duplicate of #837133 which is fixed since yesterday,
> > > therefore closing this bug report.
> > It may not be a duplicate because the package in #837133 is 
> > libconfig-model-perl
> > and the package that FTBFS now is libconfig-model-itself-perl.
> 
> #837133 was originally reported against libconfig-model-itself-perl
> (with the exact same error as in your log). Then reassigned to
> libconfig-model-perl plus affects libconfig-model-itself-perl.
>  
> > If, OTOH, you mean that the reason this package fails is in another
> > package which is in the build-depends of this one, then please use
> > affects to avoid more duplicates.
> 
> Everything there already :)
> 
> https://bugs.debian.org/libconfig-model-itself-perl shows #837133.

Oh, I see.

But when a package may not be built at all, the bug is really in the
source package, not in any of the binary packages, which do not even exist.

I was looking here:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=0;dist=unstable;ordering=normal;repeatmerged=0;src=libconfig-model-itself-perl

so no surprise that I didn't found the bug.

But now it will show there.

[ Feel free to reassign and forcemerge if you want ]

Thanks.

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

[gregor herrmann]

On Mon, 12 Sep 2016 23:03:19 +0100, Santiago Vila wrote:

> > fixed since yesterday,
> BTW: I usually build only packages which are in the same version in
> testing and unstable (i.e. in sync), so if you want to apply bayesian
> analysis to my bug reports, you can assign a high probability that
> when I report something, it was not fixed yesterday (because most
> probably I would have skipped the package).

Your log is from

| libconfig-model-itself-perl 2.005-1 (amd64)  Mon, 12 Sep 2016 18:21:03 + |

#837133 was closed at "Mon, 12 Sep 2016 11:50:08 +" -- so yes, my
"yesterday" was wrong, I looked at the date in the .changes which is
"Sun, 11 Sep 2016 19:48:32 +0200", sorry for confusing the two dates.


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Die Schmetterlinge: Lied des Richters


signature.asc
Description: Digital Signature

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

[gregor herrmann]

On Mon, 12 Sep 2016 22:57:08 +0100, Santiago Vila wrote:

> > This is a duplicate of #837133 which is fixed since yesterday,
> > therefore closing this bug report.
> It may not be a duplicate because the package in #837133 is 
> libconfig-model-perl
> and the package that FTBFS now is libconfig-model-itself-perl.

#837133 was originally reported against libconfig-model-itself-perl
(with the exact same error as in your log). Then reassigned to
libconfig-model-perl plus affects libconfig-model-itself-perl.
 
> If, OTOH, you mean that the reason this package fails is in another
> package which is in the build-depends of this one, then please use
> affects to avoid more duplicates.

Everything there already :)

https://bugs.debian.org/libconfig-model-itself-perl shows #837133.
 

Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Joan Baez: Will the circle be unbroken


signature.asc
Description: Digital Signature

Bug#827936: po4a: please implement support for Ruby document format

[Francesco Poli]

On Wed, 7 Sep 2016 00:04:43 +0200 Francesco Poli wrote:

> On Tue, 6 Sep 2016 02:40:49 +0200 Martin Quinson wrote:
> 
[...]
> > A first point would be to convert your tests to a proper test of our
> > infrastructure, somewhere under t/ Once you have some automated tests,
> > I will happily integrate your work in the main archive.
> 
> This is where I need your help most: could you please do the conversion
> yourself?
> I am convinced that this would be the best option, since I have zero
> familiarity with the test infrastructure used in po4a and I am afraid
> I would mess everything up...   :-p

Are you willing to convert my tests to a proper test integrated in po4a
test infrastructure?
I really hope you are, since I am not knowledgeable enough to do so by
myself...

Please let me know.
Thanks a lot for any help you may provide!

> 
> > 
> > Then, the next step will be to test your work against the existing
> > Ruby documentation, and fix it until it works properly.
> 
> I'll try and find a little more time and test Rd.pm against some
> existing Ruby documentation.
[...]

I tested Rd.pm against more existing Ruby documentation, and it seems
to behave correctly...


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


pgpqlWvqlZp26.pgp
Description: PGP signature

Bug#837621: simpleid: PHP Fatal error: Cannot redeclare random_bytes()

[James Valleroy]

Package: simpleid
Version: 0.8.1-15
Severity: important

Dear Maintainer,

After installing simpleid, and visiting http://localhost/simpleid, I just get a
blank page. Apache error log shows:

[Mon Sep 12 17:59:29.513676 2016] [:error] [pid 31620] [client 127.0.0.1:49100]
PHP Fatal error:  Cannot redeclare random_bytes() in
/usr/share/simpleid/www/random.inc on line 68

I saw this error both with the default configuration, and after modifying the
configuration as mentioned in README.Debian.



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

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

Versions of packages simpleid depends on:
ii  debconf [debconf-2.0]   1.5.59
ii  dpkg1.18.10
ii  libapache2-mod-php  1:7.0+44
ii  libapache2-mod-php7.0 [libapache2-mod-php]  7.0.10-1
ii  libjs-jquery2.1.1-1
ii  php 1:7.0+44
ii  php7.0 [php]7.0.10-1

Versions of packages simpleid recommends:
ii  apache2 [httpd]  2.4.23-4

simpleid suggests no packages.

-- no debconf information

Bug#837623: [firefox-esr] text with background in the HTML is printing without it

[Enrique Garcia]

Package: firefox-esr
Version: 45.3.0esr-1
Severity: minor

--- Please enter the report below this line. ---

 If a text in the HTML has a given background, the HTML is rendered fine 
but when printing the background disappears altogether.

 I attach a very simple HTML page and the result of printing it.
 
  Thank you

--- System information. ---
Architecture: amd64
Kernel:   Linux 4.6.0-1-amd64

Debian Release: stretch/sid
  500 testing ftp.de.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===
-+-===
libasound2  (>= 1.0.16) | 1.1.2-1
libatk1.0-0 (>= 1.12.4) | 2.21.90-2
libc6 (>= 2.17) | 2.23-5
libcairo2(>= 1.2.4) | 1.14.6-1+b1
libdbus-1-3 (>= 1.9.14) | 1.10.10-1
libdbus-glib-1-2  (>= 0.78) | 0.106-1
libevent-2.0-5   (>= 2.0.10-stable) | 2.0.21-stable-2+b1
libffi6  (>= 3.0.4) | 3.2.1-4
libfontconfig1(>= 2.11) | 2.11.0-6.7
libfreetype6 (>= 2.2.1) | 2.6.3-3+b1
libgcc1  (>= 1:4.0) | 1:6.1.1-11
libgdk-pixbuf2.0-0  (>= 2.22.0) | 2.34.0-1
libglib2.0-0(>= 2.20.0) | 2.49.6-1
libgtk2.0-0 (>= 2.24.0) | 2.24.30-4
libhunspell-1.4-0   | 1.4.1-2
libnspr4  (>= 2:4.10.3) | 2:4.12-2
libnss3 (>= 2:3.19) | 2:3.25-1
libpango-1.0-0  (>= 1.14.0) | 1.40.2-1
libsqlite3-0 (>= 3.7.12-1~) | 3.14.1-1
libstartup-notification0   (>= 0.8) | 0.12-4
libstdc++6 (>= 5.2) | 6.1.1-11
libvpx3  (>= 1.5.0) | 1.5.0-4
libx11-6| 2:1.6.3-1
libxcomposite1 (>= 1:0.3-1) | 1:0.4.4-1
libxdamage1  (>= 1:1.1) | 1:1.1.4-2+b1
libxext6| 2:1.3.3-1
libxfixes3  | 1:5.0.2-1
libxrender1 | 1:0.9.9-2
libxt6  | 1:1.1.5-1
zlib1g (>= 1:1.2.0) | 1:1.2.8.dfsg-2+b1
fontconfig  | 2.11.0-6.7
procps  | 2:3.3.12-2
debianutils   (>= 1.16) | 4.8


Recommends (Version) | Installed
-+-
===
gstreamer1.0-libav   | 1.8.3-1
gstreamer1.0-plugins-good| 1.8.3-1+b1


Suggests  (Version) | Installed
===-+-===
fonts-stix  | 
 OR otf-stix| 
fonts-lmodern   | 2.004.5-3
mozplugger  | 
libgssapi-krb5-2| 1.14.3+dfsg-2
 OR libkrb53| 
libgnomeui-0| 2.24.5-3.1
libcanberra0| 0.30-3



--- Output from package bug script ---


Title: Example






  Example


Date
Column 1Column 2  


  12.09.2016
  
  

  
  Text with no background  


  
Text with bgcolor="#00" 

  
  
  18.09.2016
  
  

  


  
  
  

  
  





test.pdf
Description: Adobe PDF document

Bug#837622: python-stetl: FTBFS in testing (failing tests)

[Santiago Vila]

Package: src:python-stetl
Version: 1.0.9+ds-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep \
--buildsystem=pybuild \
--with python2 \
--parallel
   dh_testdir -i -O--buildsystem=pybuild -O--parallel
   dh_update_autotools_config -i -O--buildsystem=pybuild -O--parallel
   dh_auto_configure -i -O--buildsystem=pybuild -O--parallel
I: pybuild base:184: python2.7 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/python-stetl-1.0.9+ds'
# Create man page from DocBook XML

[... snipped ...]

writing output... [ 44%] contact
writing output... [ 55%] index
writing output... [ 66%] install
writing output... [ 77%] intro
writing output... [ 88%] links
writing output... [100%] using

generating indices... genindex py-modindex
highlighting module code... [  3%] stetl.outputs.httpoutput
highlighting module code... [  6%] stetl.outputs.standardoutput
highlighting module code... [ 10%] stetl.outputs.wfsoutput
highlighting module code... [ 13%] stetl.factory
highlighting module code... [ 17%] stetl.outputs.ogroutput
highlighting module code... [ 20%] stetl.main
highlighting module code... [ 24%] stetl.input
highlighting module code... [ 27%] stetl.outputs.fileoutput
highlighting module code... [ 31%] stetl.filters.stringfilter
highlighting module code... [ 34%] stetl.inputs.deegreeinput
highlighting module code... [ 37%] stetl.filters.gmlfeatureextractor
highlighting module code... [ 41%] stetl.filters.formatconverter
highlighting module code... [ 44%] stetl.component
highlighting module code... [ 48%] stetl.inputs.httpinput
highlighting module code... [ 51%] stetl.filters.gmlsplitter
highlighting module code... [ 55%] stetl.filters.templatingfilter
highlighting module code... [ 58%] stetl.filters.xsltfilter
highlighting module code... [ 62%] stetl.inputs.ogrinput
highlighting module code... [ 65%] stetl.outputs.dboutput
highlighting module code... [ 68%] stetl.output
highlighting module code... [ 72%] stetl.etl
highlighting module code... [ 75%] stetl.filter
highlighting module code... [ 79%] stetl.filters.xmlassembler
highlighting module code... [ 82%] stetl.packet
highlighting module code... [ 86%] stetl.outputs.deegreeoutput
highlighting module code... [ 89%] stetl.chain
highlighting module code... [ 93%] stetl.inputs.fileinput
highlighting module code... [ 96%] stetl.inputs.dbinput
highlighting module code... [100%] stetl.filters.xmlvalidator

writing additional pages... search
copying static files... done
copying extra files... done
dumping search index in English (code: en) ... done
dumping object inventory... done
build succeeded, 1 warning.
Makefile:45: recipe for target 'html' failed
make[2]: *** [html] Segmentation fault
make[2]: Leaving directory '/<>/python-stetl-1.0.9+ds/docs'
debian/rules:27: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/python-stetl-1.0.9+ds'
debian/rules:14: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


I can reproduce the error on several unrelated autobuilders.

A full build log is attached.

Thanks.

python-stetl_1.0.9+ds-1_amd64-20160912T211122Z.gz
Description: application/gzip

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

[Santiago Vila]

On Mon, Sep 12, 2016 at 11:39:27PM +0200, gregor herrmann wrote:

> fixed since yesterday,

BTW: I usually build only packages which are in the same version in
testing and unstable (i.e. in sync), so if you want to apply bayesian
analysis to my bug reports, you can assign a high probability that
when I report something, it was not fixed yesterday (because most
probably I would have skipped the package).

Thanks.

Bug#837617: snoopy: Compile with --enable-config-file

[Alex Henry]

Just saw on the changelog file that the configuration file is disabled due
to performance issues, which is understandable. It's a shame though since
the configuration file is indeed very useful (thinking of filters mostly
here). Are you sure that there is overhead other than in snoopy's startup
routine? I'd imagine such a piece of software would be written with that
sort of concern in mind.

The devs seem pretty approachable on GitHub, maybe they can clear this out
or offer a solution with low overhead? Let me know if I can help in any way.

On 12 September 2016 at 18:50, Alex Henry  wrote:

> Package: snoopy
> Version: 2.3.1-2
> Severity: normal
>
> Hello! The doc files provided for snoopy reference the
> /etc/snoopy.ini file but I can't seem to find it.
> Perhaps this package has been compiled without
> the config file support?
>
> If that is the case then some of the doc files need
> to be either updated or removed. If the file is
> somehwere but I can't seem to find it then the docs
> should be updated and probably a symbolic link be
> created from /etc/snoopy.etc to the actual file.
>
> In any case, if that is not already being done, I
> believe that snoopy should definitely be compiled with
> --enable-config-file for maximum admin control, since
> the whole point of having a binary package via apt is
> to avoid having to compile the source code ourselves
> (which we could do to change compile-time
> parameters/configuration/options).
>
> Thanks for maintaning this package. I just found out
> today about it and it will certainly help me
> diagnose a problem here. To find it already on Debian
> was a real treat and made me proud of my distro!
>
> Thanks a bunch!
>
> PS: `find /|grep snoopy.ini` finds nothing for me.
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages snoopy depends on:
> ii  debconf [debconf-2.0]  1.5.59
> ii  libc6  2.23-5
>
> snoopy recommends no packages.
>
> snoopy suggests no packages.
>
> -- debconf information excluded
>

Bug#837620: w3-dtd-mathml: FTBFS: dh_installxmlcatalogs: Unexpected debhelper version format

[Chris Lamb]

Source: w3-dtd-mathml
Version: 2.0.0.0-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,

w3-dtd-mathml fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  w3-dtd-mathml
   Version:  2.0.0.0-5
   Build architecture:   amd64
   Date: Mon, 12 Sep 2016 22:53:57 +0100
   Hostname: a2852fa5efcf
   Uname:Linux a2852fa5efcf 4.7.0-1-amd64 #1 SMP Debian 4.7.2-1 
(2016-08-28) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'w3-dtd-mathml-build-deps' in 
'../w3-dtd-mathml-build-deps_2.0.0.0-5_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package w3-dtd-mathml-build-deps.
  (Reading database ... 23321 files and directories currently installed.)
  Preparing to unpack w3-dtd-mathml-build-deps_2.0.0.0-5_all.deb ...
  Unpacking w3-dtd-mathml-build-deps (2.0.0.0-5) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
sgml-base xml-core
  Suggested packages:
sgml-base-doc
  The following NEW packages will be installed:
sgml-base xml-core
  0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 38.9 kB of archives.
  After this operation, 263 kB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 sgml-base all 1.28 
[14.7 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 xml-core all 
0.13+nmu2 [24.2 kB]
  Fetched 38.9 kB in 0s (0 B/s)
  Selecting previously unselected package sgml-base.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23325 files and directories currently installed.)
  Preparing to unpack .../0-sgml-base_1.28_all.deb ...
  Unpacking sgml-base (1.28) ...
  Selecting previously unselected package xml-core.
  Preparing to unpack .../1-xml-core_0.13+nmu2_all.deb ...
  Unpacking xml-core (0.13+nmu2) ...
  Setting up sgml-base (1.28) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up xml-core (0.13+nmu2) ...
  Processing triggers for sgml-base (1.28) ...
  Setting up w3-dtd-mathml-build-deps (2.0.0.0-5) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=a2852fa5efcf
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  
PWD=/home/lamby/temp/cdt.20160912225355.JoOsKTq0ko.db.w3-dtd-mathml/w3-dtd-mathml-2.0.0.0
  OLDPWD=/home/lamby/temp/cdt.20160912225355.JoOsKTq0ko.db.w3-dtd-mathml
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  GPG_KEY=1E953E27D4311E58
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building w3-dtd-mathml 2.0.0.0-5 

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

[Santiago Vila]

On Mon, Sep 12, 2016 at 11:39:27PM +0200, gregor herrmann wrote:

> This is a duplicate of #837133 which is fixed since yesterday,
> therefore closing this bug report.

It may not be a duplicate because the package in #837133 is libconfig-model-perl
and the package that FTBFS now is libconfig-model-itself-perl.

If, OTOH, you mean that the reason this package fails is in another
package which is in the build-depends of this one, then please use
affects to avoid more duplicates.

(Or just say so and I put the affects in place, I don't mind).

Thanks.

Bug#837619: jdeb: FTBFS: Failed tests: org.vafer.jdeb.signing.PGPSignerTestCase#testClearSign

[Chris Lamb]

Source: jdeb
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,

jdeb fails to build from source in unstable/amd64:

  [..]

  Adding debian:WoSign.pem
  Adding debian:WoSign_China.pem
  Adding debian:XRamp_Global_CA_Root.pem
  Adding debian:certSIGN_ROOT_CA.pem
  Adding debian:ePKI_Root_Certification_Authority.pem
  Adding debian:thawte_Primary_Root_CA.pem
  Adding debian:thawte_Primary_Root_CA_-_G2.pem
  Adding debian:thawte_Primary_Root_CA_-_G3.pem
  done.
  done.
  Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.35.4-4) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=89a63a68b5f3
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  PWD=/home/lamby/temp/cdt.20160912225159.DpKdGEDtQm.db.jdeb/jdeb-1.5
  OLDPWD=/home/lamby/temp/cdt.20160912225159.DpKdGEDtQm.db.jdeb
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  GPG_KEY=1E953E27D4311E58
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building jdeb 1.5-2 on amd64   
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package jdeb
  dpkg-buildpackage: info: source version 1.5-2
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Emmanuel Bourg 
   dpkg-source --before-build jdeb-1.5
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh clean --buildsystem=maven
 dh_testdir -O--buildsystem=maven
 dh_auto_clean -O--buildsystem=maven
"for dir in \$(find . -name target -type d); do if [ -f \$(echo \$dir | 
sed -e s/target\$/pom.xml/) ]; then rm -Rf \$dir; fi done"
mh_unpatchpoms -plibjdeb-java
 dh_clean -O--buildsystem=maven
   debian/rules build
  dh build --buildsystem=maven
 dh_testdir -O--buildsystem=maven
 dh_update_autotools_config -O--buildsystem=maven
 dh_auto_configure -O--buildsystem=maven
  find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
  find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
No such file or directory
  find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
No such file or directory
mh_patchpoms -plibjdeb-java --debian-build --keep-pom-version 
--maven-repo=/home/lamby/temp/cdt.20160912225159.DpKdGEDtQm.db.jdeb/jdeb-1.5/debian/maven-repo
 dh_auto_build -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20160912225159.DpKdGEDtQm.db.jdeb/jdeb-1.5
 -Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/home/lamby/temp/cdt.20160912225159.DpKdGEDtQm.db.jdeb/jdeb-1.5/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/home/lamby/temp/cdt.20160912225159.DpKdGEDtQm.db.jdeb/jdeb-1.5/debian
 
-Dmaven.repo.local=/home/lamby/temp/cdt.20160912225159.DpKdGEDtQm.db.jdeb/jdeb-1.5/debian/maven-repo
 package -DskipTests -Dnotimestamp=true -Dlocale=en_US
  [INFO] Scanning for projects...
  [INFO]
 
  [INFO] 

  [INFO] Building jdeb 1.5
  [INFO] 

  [INFO] 
  [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ jdeb ---
  [INFO] Using 'UTF-8' encoding to copy filtered resources.
  [INFO] Copying 2 resources
  [INFO] 
  [INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ jdeb ---
  [INFO] Changes detected - recompiling the module!
  [INFO] Compiling 49 source files to 
/home/lamby/temp/cdt.20160912225159.DpKdGEDtQm.db.jdeb/jdeb-1.5/target/classes
  [INFO] 

Bug#837615: [debian-mysql] Bug#837615: Don't include in stretch

[Moritz Mühlenhoff]

On Mon, Sep 12, 2016 at 10:42:31PM +0100, Robie Basak wrote:
> On Mon, Sep 12, 2016 at 11:37:49PM +0200, Moritz Muehlenhoff wrote:
> > As per previous discussion, don't include in stretch/blocker bug to
> > keep it out.
> 
> What previous discussion? I'm aware of a decision for things to depend
> on src:mariadb-10.0 instead, not of any decision to keep src:mysql-5.6
> out.

Of course not, the whole discussion was about picking one version for
stretch and that turned out to be mariadb-10.0.

Bug#837618: docbook-slides: FTBFS: dh_installxmlcatalogs: Unexpected debhelper version format

[Chris Lamb]

Source: docbook-slides
Version: 3.4.0-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,

docbook-slides fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  docbook-slides
   Version:  3.4.0-5
   Build architecture:   amd64
   Date: Mon, 12 Sep 2016 22:51:50 +0100
   Hostname: 8f539c25af1f
   Uname:Linux 8f539c25af1f 4.7.0-1-amd64 #1 SMP Debian 4.7.2-1 
(2016-08-28) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'docbook-slides-build-deps' in 
'../docbook-slides-build-deps_3.4.0-5_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package docbook-slides-build-deps.
  (Reading database ... 23321 files and directories currently installed.)
  Preparing to unpack docbook-slides-build-deps_3.4.0-5_all.deb ...
  Unpacking docbook-slides-build-deps (3.4.0-5) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
sgml-base xml-core
  Suggested packages:
sgml-base-doc
  The following NEW packages will be installed:
sgml-base xml-core
  0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 38.9 kB of archives.
  After this operation, 263 kB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 sgml-base all 1.28 
[14.7 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 xml-core all 
0.13+nmu2 [24.2 kB]
  Fetched 38.9 kB in 0s (0 B/s)
  Selecting previously unselected package sgml-base.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23325 files and directories currently installed.)
  Preparing to unpack .../0-sgml-base_1.28_all.deb ...
  Unpacking sgml-base (1.28) ...
  Selecting previously unselected package xml-core.
  Preparing to unpack .../1-xml-core_0.13+nmu2_all.deb ...
  Unpacking xml-core (0.13+nmu2) ...
  Setting up sgml-base (1.28) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up xml-core (0.13+nmu2) ...
  Processing triggers for sgml-base (1.28) ...
  Setting up docbook-slides-build-deps (3.4.0-5) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=8f539c25af1f
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  
PWD=/home/lamby/temp/cdt.20160912225148.W8rB87PWuO.db.docbook-slides/docbook-slides-3.4.0
  OLDPWD=/home/lamby/temp/cdt.20160912225148.W8rB87PWuO.db.docbook-slides
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  GPG_KEY=1E953E27D4311E58
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building docbook-slides 3.4.0-5 on 

Bug#836364: please provide a stable backport

[W. Martin Borgert]

Note, that 0.16.5 is necessary for OMEMO encryption.
The backport would help users of stable to communicate securely.

Bug#837617: snoopy: Compile with --enable-config-file

[Alex Henry]

Package: snoopy
Version: 2.3.1-2
Severity: normal

Hello! The doc files provided for snoopy reference the
/etc/snoopy.ini file but I can't seem to find it.
Perhaps this package has been compiled without
the config file support?

If that is the case then some of the doc files need
to be either updated or removed. If the file is
somehwere but I can't seem to find it then the docs
should be updated and probably a symbolic link be
created from /etc/snoopy.etc to the actual file.

In any case, if that is not already being done, I
believe that snoopy should definitely be compiled with
--enable-config-file for maximum admin control, since
the whole point of having a binary package via apt is
to avoid having to compile the source code ourselves
(which we could do to change compile-time
parameters/configuration/options).

Thanks for maintaning this package. I just found out
today about it and it will certainly help me
diagnose a problem here. To find it already on Debian
was a real treat and made me proud of my distro!

Thanks a bunch!

PS: `find /|grep snoopy.ini` finds nothing for me.


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

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

Versions of packages snoopy depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  libc6  2.23-5

snoopy recommends no packages.

snoopy suggests no packages.

-- debconf information excluded

Bug#837615: [debian-mysql] Bug#837615: Don't include in stretch

[Robie Basak]

On Mon, Sep 12, 2016 at 11:37:49PM +0200, Moritz Muehlenhoff wrote:
> As per previous discussion, don't include in stretch/blocker bug to
> keep it out.

What previous discussion? I'm aware of a decision for things to depend
on src:mariadb-10.0 instead, not of any decision to keep src:mysql-5.6
out.

Bug#837616: ITP: gajim-urlimagepreview -- displays images inside Gajim chat window

[W. Martin Borgert]

Package: wnpp
Severity: wishlist
Owner: "W. Martin Borgert" 

* Package name: gajim-urlimagepreview
  Version : 0.9.5
  Upstream Author : Denis Fomin ,
Yann Leboulanger ,
Anders Sandblad ,
Thilo Molitor ,
Philipp Hoerist 
* URL : https://trac-plugins.gajim.org/wiki/UrlImagePreviewPlugin
* License : GPL3
  Programming Lang: Python
  Description : displays images inside Gajim chat window

This Gajim plugin let the user display images inside the chat window.
If they right click on the picture they have several options:
 - save the picture to a location of their choice
 - open the picture with their file manager
 - open the link with their browser 

Bug#835488: When is the next update?

[Rainer Dorsch]

Hi Cam,

I agree with all you wrote. For the time being I use as workaround to 
downgrade the imagemagick packages using

blackbox:~# cat /usr/local/sbin/imagemagick-gscan2pdf.sh
#!/bin/bash

echo "Downgrading imagemagick for operation with gscan"

apt-get install imagemagick=8:6.8.9.9-5+deb8u2 imagemagick-
common=8:6.8.9.9-5+deb8u2 imagemagick-6.q16=8:6.8.9.9-5+deb8u2 
libmagickcore-6.q16-2=8:6.8.9.9-5+deb8u2 
libmagickwand-6.q16-2=8:6.8.9.9-5+deb8u2
blackbox:~# 

temporarily (which brings all the fixed security issues back) and do an "apt-
get upgrade" after I have finished gscan2pdf.

I cannot tell if it works for your usecase, but I thought it is worth sharing.

Kind regards
Rainer

On Monday 12 September 2016 10:24:05 Cam Hutchison wrote:
> Roucaries,
> 
> When will the update be going out, as in approximate time frame? I don't
> know when the next security update is scheduled, if at all, but for me this
> is a serious regression that has broken some pretty important stuff for me.
> I use Debian stable to avoid the churn so I do not have my important
> processes broken.
> 
> I would appreciate it if you could push the fix ASAP regardless of whether
> there are other security updates or not.
> 
> Thanks.

-- 
Rainer Dorsch
Lärchenstr. 6
72135 Dettenhausen
07157/734133

Bug#813754: [Pkg-mpd-maintainers] Bug#813754: Bug#813754: Can't open port 6600 when run syste, -wide vis systemd

[Lisandro Damián Nicanor Pérez Meyer]

Control: tag -1 - moreinfo

On lunes, 12 de septiembre de 2016 10:50:00 P. M. ART Florian Schlichting 
wrote:
> Hi Lisandro,

Hi!
 
> back in February you reported #813754 against mpd, claiming it would not
> open port 6600 if started via systemd.
> 
> I just re-read our email exchange, and I think you'were just confused
> about how systemd socket activation works. 

I expect that, if the daemon is not running and a client tries to connect to 
port 6600 then systemd will start the daemon and the client wouldn't even 
notice it.

That's not happening.

If I'm still wrong in my expectations about systemd and sockets, please read 
below at least to understand what I see as a bug.

> netstat output doesn't show
> "mpd", but everything still works as one would expect, no?

No, the client can't reach the server unless I start mpd as described in the 
bug.

> Please confirm that #813754 doesn't need to be kept open, or else please
> describe what is not working for you?

I would expect turning on my machine, fire my mpd android client app and enjoy 
music :) But I'm getting a client that can't connect to the server unless I 
start mpd as described in the bug.

-- 
Gabardinas "Windows 95". Se cuelgan solas.

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#837615: Don't include in stretch

[Moritz Muehlenhoff]

Source: mysql-5.6
Severity: serious

As per previous discussion, don't include in stretch/blocker bug to
keep it out.

Cheers,
Moritz

Bug#834281: libgnupg-interface-perl not migrating to testing

[gregor herrmann]

On Mon, 12 Sep 2016 20:40:34 +0100, Adam D. Barratt wrote:

> On Mon, 2016-09-12 at 20:37 +0200, intrigeri wrote:
> > Can anyone please help me understand about why libgnupg-interface-perl
> > is not migrating to testing?
> The log - https://release.debian.org/britney/update_output.txt - should
> be your next port of call. That gives us:

Oh, wow, that was not on my radar.
 
> Examining the changes in the new version of libgnupg-interface-perl and
> the dependencies of the affected packages shows that
> libgnupg-interface-perl now depends on "gnupg1". libmail-gnupg-perl,
> meanwhile, depends on "gnupg".
> 
> "gnupg1" declares a conflict on "gnupg (< 1.4.20-6+exp1)" and:
> 
> gnupg  | 1.4.20-6| testing| source, amd64, arm64, 
> armel, armhf, i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x

D'oh.

And gnupg 2.x doesn't migrate because of #836259.
And libgnupg-interface-perl is about to be removed from testing
because of #834281 -- but, I think, this bug doesn't affect testing
since there's gnupg 1.4.x. So removing the stretch tag might already
help?

Or at least cc'ing the bug to reset the autoremoval counter :)
 
> Therefore unstable's libgnupg-interface-perl and testing's
> libmail-gnupg-perl are not co-installable, but the latter depends on the
> former.

Thanks for this analysis!


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: The Dubliners: Spanish Lady


signature.asc
Description: Digital Signature

Bug#837613: libconfig-model-itself-perl: FTBFS in testing (failing tests)

[Santiago Vila]

Package: src:libconfig-model-itself-perl
Version: 2.005-1
Severity: serious

Dear maintainer:

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


[...]

Test Summary Report
---
t/load_write_itself.t(Wstat: 512 Tests: 4 Failed: 0)
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 8 tests but ran 4.
Files=12, Tests=108, 53 wallclock secs ( 0.04 usr  0.01 sys + 43.91 cusr  1.22 
csys = 45.18 CPU)
Result: FAIL
Failed 1/12 test programs. 0/108 subtests failed.
dh_auto_test: perl Build test --verbose 1 returned exit code 255
debian/rules:7: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


[ Using -A is probably not an issue here ]

I can reproduce the error on several unrelated autobuilders.

A full build log is attached.

Thanks.

libconfig-model-itself-perl_2.005-1_amd64-20160912T182103Z.gz
Description: application/gzip

Bug#836925: u-boot: installation report for u-boot and u-boot-tools 2016.09~rc2+dfsg1-1

[Vagrant Cascadian]

Control: severity 836925 important

On 2016-09-07, Rick Thomas wrote:
> I installed the new u-boot using the procedure in
> /usr/share/doc/u-boot/README.Debian
>
> The newly installed u-boot loaded and executed after a linux "reboot"
> command.
>
> Unfortunatels it destroyed the u-boot environment, so it tried to boot
> using the default env.  This failed to boot Linux.

What version of u-boot were you upgrading from?

The u-boot env values were changed somewhere around 2016.01, possibly:

  https://bugs.debian.org/781874

Or has the u-boot environment configuration changed again since then?


> I went to Martin's page,
> https://www.cyrius.com/debian/kirkwood/sheevaplug/install/ , and
> followed the instructions there to restore the environment for booting
> from the SD card.  I also had to restore the "ethaddr" u-boot
> environment variable.

> After having restored the u-boot environment, I issued a "reset", and
> it then happily booted as expected.

> I'd recommend that /usr/share/doc/u-boot/README.Debian give a warning
> about needing to restore the u-boot environment, at least for the
> sheevaplug.

Or NEWS.Debian, given that it can actually cause a failure to
boot.

If you could propose some text describing the issue, when it is
encountered, and what to do about it, that would be helpful; the details
of the issue are a bit unclear to me to start writing anything.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#837614: python-geopandas: FTBFS in testing (failing tests)

[Santiago Vila]

Package: src:python-geopandas
Version: 0.2.1-1
Severity: serious

Dear maintainer:

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


[...]
--
Ran 164 tests in 57.060s

OK (SKIP=9)
Segmentation fault
E: pybuild pybuild:276: test: plugin custom failed with: exit code=139: 
nosetests -v -e test_geocode.py
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
debian/rules:17: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


[ Using -A is probably not an issue here ]

I can reproduce the error on several unrelated autobuilders.

A full build log is attached.

Thanks.

python-geopandas_0.2.1-1_amd64-20160912T205720Z.gz
Description: application/gzip

Bug#837606: closed by Ben Hutchings <b...@decadent.org.uk> (Re: Bug#837606: additional infromation)

[Rouven-Matthias Müller]

thanks ben
this was the last time i tried to help debian
i think you have succeded


have a nice day


Am Montag, 12. September 2016, 21:27:04 schrieben Sie:
> This is an automatic notification regarding your Bug report
> which was filed against the general package:
> 
> #837606: general: system freeze
> 
> It has been closed by Ben Hutchings .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Ben Hutchings
>  by replying to this email.

Bug#837606: general: system freeze

[Ben Caradoc-Davies]

Rouven,

you have provided very little information so it will be hard for anyone 
to reproduce this problem.


- What causes the problem? Are you running any program in particular?

- What is your hardware? Desktop, laptop? Models? Video cards and 
drivers can cause of hangs.


- What do you mean by "freezes"? Can you ssh into the machine? Can you 
suspend/resume? If you press the power button what happens?


- Does your keyboard work? Are you able to switch to a console with 
Ctrl-Alt-F1? Back with Ctrl-F7?


- Any indication of hardware problems such as failing storage or memory 
errors? Overheating?


- Wireless keyboard low battery or lost connection?

In any case, the Debian Bug Tracking System is not the most suitable 
forum for general support unless you can determine specific steps to 
reproduce this problem.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#818448: fixed in imapcopy 1.04-2.1

[Peter Green]

On 12/09/16 20:51, Gianfranco Costamagna wrote:



Gianfranco, as per Policy §4.4, please put your own name in the
changelog trailer when making an upload.
 


well, it seems unfair wrt Peter,
   

IMO what the changelog should look like in a case like this is

imapcopy (1.04-2.1) unstable; urgency=medium
  * Non-maintainer upload
  [Peter Michael Green]
  * Fix build with fpc 3.0.0 (Closes: 818448)

 -- Gianfranco Costamagna   

This way it correctly identifies both who authored the change and who decided 
it was ready to upload to Unstable.

You should only upload with someone else's name in the chagelog trailer if they 
have explicitly asked for sponsorship.


who actually did *all* the work

<--snip-->

BTW on top of the changes, me and a friend of mine, tested the basic
functions of the imapcopy tool.
(not sure if the testing was complete or not, since it was just a FTBFS
fix and it was somewhere trivial).
the fix was referring network operations, it might break somewhere in some 
particular
networks, but I think this isn't the case.
   
Maybe i'm overcautious but I will only NMU if I have tested at least the 
basic functioning of the application and ideally have tested it in a way 
that I know will hit the codepath I changed.


Figuring out how to test a given application, preparing a suitable test 
environment etc is often more work than writing the actual patch. That 
is why in this case I merely subimitted a patch to the bug report and 
did not upload as a NMU myself.


IMO your actions testing that the fix was indeed ready for upload are as 
valuable as my figuring out what needed to be changed to make the 
package build.

Bug#837495: gnome-shell-extension-suspend-button: uninstallable in sid: Depends: gnome-shell (< 3.21) but 3.21.91-2 is to be installed

[Tobias Frost]

Control: forwarded -1 
https://github.com/laserb/gnome-shell-extension-suspend-button/issues/20
Control: tags -1 upstream

On Mon, Sep 12, 2016 at 01:33:27AM +0200, Andreas Beckmann wrote:
> Package: gnome-shell-extension-suspend-button
> Version: 0~git20160525-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package is no longer
> installable in sid:
> 
>   The following packages have unmet dependencies:
>  gnome-shell-extension-suspend-button : Depends: gnome-shell (< 3.21) but 
> 3.21.91-2 is to be installed
> 
> 
> Cheers,
> 
> Andreas

Opened an issue upstream...

Bug#837606: additional infromation

[Rouven-Matthias Müller]

it seems very much that you do not understand that it is not applicable for 
the operating system to be blocked by a other program. the system controlles 
the programs!!! not the programs the system
it does not matter what you think about that subject. it is a fact!

it happened months ago with libre office running on my second laptop. nobody 
fixed the operating system, they changed something on libre office and so the 
problem is still there. it does not matter wich program causes it. get that 
into your smallminded head!

greetings
rouven

Bug#837547: pristine-tar commit fails if tarball contains German umlauts

[Carsten Schoenert]

Hello Tomasz,

On Mon, Sep 12, 2016 at 10:38:49PM +0200, Tomasz Buchert wrote:
> Hi Carsten,
> 
> I cannot reproduceyour problem. I took the tarball from here:
> https://github.com/KiCad/Shielding_Cabinets.pretty/releases and I was
> able to commit it and check it out afterwards with zero problems.
> 
> I see that your tarballs has been dfsg-repacked. I wonder if it isn't
> the repack that failed to properly create a +dfsg tarball. Can you please
> provide me with the failing tarball?

the tarball is unfortunately very big, but I append the slightly
modified script I use to prepare the various tarballs. It will be part
of the next changes for a new KiCad upload hopefully.

The scipt is needing bash tp work properly, simple append the current
tag for the stable version to get all needed archives.

  $ create_kicad_upstream_tarballs.sh 4.0.4

The tarballs will be created in /tmp/kicad-tmp/, you can use '-v'
optionally to see a more verbose output of script.

I was also thinking that maybe there is something got broken while
recreating the tarballs. But the libraries for KiCad are just extracted
and repacked with 'tar -Jcf'.
I hope you can enlighten the situation.

Regards
Carsten


create_kicad_upstream_tarballs.sh
Description: Bourne shell script

Bug#837612: hplip-gui 3.16.8+repack0-2~bpo8+1 can't be installed in Jessie because of missing packages default-dbus-session-bus and dbus-session-bus

[rolu87-kontakt]

Package: hplip-gui
Version: 3.16.8+repack0-2~bpo8+1 

I can no longer install or update hplip-gui (3.16.8.+repack0-2~bpo8+1) from 
jessie-backports because of the missing dependencies default-dbus-sessions-bus 
or dbus-session-bus.

These packages seem to exist in Stretch/Testing and Unstable/Sid but do not 
exist in Jessie. 


This problem may have happend after substituting the dependency dbus-x11 as 
requested in bug-report 835911 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835911) with the two 
dependencies mentioned above. 


I am using Debian Jessie 8.5 64bit, 3.16.36-1+deb8u1

Bug#837611: ITP: uctodata -- Data for ucto tokeniser

[Maarten van Gompel]

Package: wnpp
Severity: wishlist
Owner: Maarten van Gompel 

* Package name: uctodata
  Upstream Author : Centre for Language and Speech Technology, Radboud 
University Nijmegen
* URL : https://languagemachines.github.io/ucto
* License : GPL-3
  Programming Lang: C++
  Description : Data for Unicode Tokenizer

 Ucto can tokenize UTF-8 encoded text files (i.e. separate words from
 punctuation, split sentences, generate n-grams), and  offers several other
 basic preprocessing steps that make your text suited for further processing 
 such as indexing, part-of-speech tagging, or machine translation.

 This package provides necessary language-specific datafiles for running Ucto.

 Ucto was written by Maarten van Gompel and Ko van der Sloot.  Work on Ucto
 was funded by NWO, the Netherlands Organisation for Scientific Research,
 under the Implicit Linguistics project, the CLARIN-NL program, and the 
 CLARIAH project.

 Ucto is a product of the Centre of Language and Speech Technology (Radboud
 University Nijmegen), and previously the ILK Research Group (Tilburg
 University, The Netherlands).



This is a split from package ucto, which previously contained the data as well.

--

Maarten van Gompel
Centre for Language Studies
Radboud Universiteit Nijmegen

proy...@anaproy.nl
http://proycon.anaproy.nl
http://github.com/proycon

GnuPG key:  0x1A31555C  XMPP: proy...@anaproy.nl
Telegram:   proycon IRC: proycon (freenode)
Twitter:https://twitter.com/proycon
Bitcoin:1BRptZsKQtqRGSZ5qKbX2azbfiygHxJPsd

Bug#772190: Debian bug reports for aufs-utils

[Jan Luca Naumann]

Hey,

in Debian there are two open bugs for aufs-utils that belongs to the
upstream code:

1. https://bugs.debian.org/772190
2. https://bugs.debian.org/777559 (contains patch)

Both reported problems seem not to be fixed in the current version yet
so you want to fix them maybe :-)

Best regards,
Jan



signature.asc
Description: OpenPGP digital signature

Bug#837610: please install gupnp-av-1.0.pc in a multiarch location

[Helmut Grohne]

Package: libgupnp-av-1.0-dev
Version: 0.12.8-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

dleyna-server fails to cross build from source, because pkg-config does
not find gupnp-av-1.0.pc. That's due to cross pkg-config not considering
/usr/lib/pkgconfig, which is a deliberate choice by the pkg-config
maintainer. Thus libgupnp-av-1.0-dev needs to move its .pc file to a
multiarch location to be useful for cross compilation. The attached
patch does just that.

This patch/bug is not about multiarch in general. It may be feasible to
add Multi-Arch headers to debian/control after applying it, but that's
not required for making cross builds work. So this patch only does the
minimum amount of work to support cross builds. Making multiarch work is
welcome nonetheless.

Helmut
diff --minimal -Nru gupnp-av-0.12.8/debian/changelog 
gupnp-av-0.12.8/debian/changelog
--- gupnp-av-0.12.8/debian/changelog2016-03-09 17:00:20.0 +0100
+++ gupnp-av-0.12.8/debian/changelog2016-09-12 22:40:41.0 +0200
@@ -1,3 +1,10 @@
+gupnp-av (0.12.8-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move gupnp-av-1.0.pc to a multiarch path (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 12 Sep 2016 22:40:15 +0200
+
 gupnp-av (0.12.8-2) unstable; urgency=medium
 
   * debian/copyright: Updated and switched to DEP5 format
diff --minimal -Nru gupnp-av-0.12.8/debian/gir1.2-gupnp-av-1.0.install 
gupnp-av-0.12.8/debian/gir1.2-gupnp-av-1.0.install
--- gupnp-av-0.12.8/debian/gir1.2-gupnp-av-1.0.install  2016-03-09 
16:48:35.0 +0100
+++ gupnp-av-0.12.8/debian/gir1.2-gupnp-av-1.0.install  2016-09-12 
22:41:54.0 +0200
@@ -1 +1 @@
-usr/lib/girepository-1.0/GUPnPAV-1.0.typelib
+usr/lib/*/girepository-1.0/GUPnPAV-1.0.typelib
diff --minimal -Nru gupnp-av-0.12.8/debian/libgupnp-av-1.0-2.install 
gupnp-av-0.12.8/debian/libgupnp-av-1.0-2.install
--- gupnp-av-0.12.8/debian/libgupnp-av-1.0-2.install2016-03-09 
16:48:35.0 +0100
+++ gupnp-av-0.12.8/debian/libgupnp-av-1.0-2.install2016-09-12 
22:39:51.0 +0200
@@ -1,2 +1,2 @@
-usr/lib/*.so.*
+usr/lib/*/*.so.*
 usr/share/gupnp-av/*.xsd
diff --minimal -Nru gupnp-av-0.12.8/debian/libgupnp-av-1.0-dev.install 
gupnp-av-0.12.8/debian/libgupnp-av-1.0-dev.install
--- gupnp-av-0.12.8/debian/libgupnp-av-1.0-dev.install  2016-03-09 
16:48:35.0 +0100
+++ gupnp-av-0.12.8/debian/libgupnp-av-1.0-dev.install  2016-09-12 
22:39:58.0 +0200
@@ -1,7 +1,7 @@
 usr/include/gupnp-av-1.0/*
-usr/lib/*.so
-usr/lib/*.a
-usr/lib/pkgconfig/*
+usr/lib/*/*.so
+usr/lib/*/*.a
+usr/lib/*/pkgconfig/*
 usr/share/gir-1.0/GUPnPAV-1.0.gir
 usr/share/vala/vapi/gupnp-av-1.0.vapi
 usr/share/vala/vapi/gupnp-av-1.0.deps
diff --minimal -Nru gupnp-av-0.12.8/debian/rules gupnp-av-0.12.8/debian/rules
--- gupnp-av-0.12.8/debian/rules2016-03-09 16:56:39.0 +0100
+++ gupnp-av-0.12.8/debian/rules2016-09-12 22:39:38.0 +0200
@@ -1,5 +1,6 @@
 #! /usr/bin/make -f 
 
+include /usr/share/dpkg/architecture.mk
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/autotools.mk
 include /usr/share/cdbs/1/rules/utils.mk
@@ -9,5 +10,7 @@
 
 DEB_DH_MAKESHLIBS_ARGS_ALL := -V -- -c4
 
+DEB_CONFIGURE_EXTRA_FLAGS += --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)
+
 common-binary-predeb-arch:: list-missing
 

Bug#813754: [Pkg-mpd-maintainers] Bug#813754: Bug#813754: Can't open port 6600 when run syste, -wide vis systemd

[Florian Schlichting]

Control: tags 813754 +moreinfo


Hi Lisandro,

back in February you reported #813754 against mpd, claiming it would not
open port 6600 if started via systemd.

I just re-read our email exchange, and I think you'were just confused
about how systemd socket activation works. netstat output doesn't show
"mpd", but everything still works as one would expect, no?

Please confirm that #813754 doesn't need to be kept open, or else please
describe what is not working for you?

Florian


On Tue, Feb 09, 2016 at 01:16:15AM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> On Monday 08 February 2016 21:21:20 you wrote:
> > Hi Lisandro,
> > 
> > > Hi! I use mpd on my personal machine as a system service, without
> > > pulseaudio.
> > > 
> > > I noticed that if I let mpd start via systemd port 6600 will not be
> > > opened.
> > 
> > mpd uses systemd's socket activation feature, as defined in
> > /lib/systemd/system/mpd.socket,
> 
> Correct.
> 
> > so port 6600 should be open and you
> > should see systemd listening there until the first connection is
> > actually made.
> > 
> > What is the netstat output after system startup?
> 
> # netstat -putan | grep mpd
> tcp0  0 0.0.0.0:80000.0.0.0:*   LISTEN
>   721/mpd
> 
> Nos I never though of grepping 6600:
>  
> # netstat -putan | grep 6600
> tcp6   0  0 :::6600 :::*LISTEN
>   1/init

Bug#837609: RFS: budgie-desktop/10.2.7-1

[foss.freedom]

Package: sponsorship-requests
  Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "budgie-desktop"

 * Package name: budgie-desktop
   Version : 10.2.7-1
   Upstream Author : i...@solus-project.com
 * URL : https://github.com/solus-project/budgie-desktop
 * License : LGPL-2.1/GPL2.0
   Section : x11

  It builds those binary packages:

 budgie-core - Core package for Budgie-Desktop
 budgie-core-dev - Development package for budgie-desktop
 budgie-desktop - Desktop package for budgie-desktop
 budgie-desktop-doc - documentation files for the budgie-desktop
 gir1.2-budgie-desktop-1.0 - GNOME introspection library for budgie-desktop
 libbudgie-plugin0 - Plugin library for budgie-desktop
 libbudgietheme0 - Theme library for budgie-desktop
 libraven0  - Raven library for budgie-desktop

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

  https://mentors.debian.net/package/budgie-desktop


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

dget -x 
https://mentors.debian.net/debian/pool/main/b/budgie-desktop/budgie-desktop_10.2.7-1.dsc

  Notes:

  upstream released 10.2.7.  Series of patches have subsequently been
added to git by the maintainer,

 summary of patches follows:


  patch 1: 0001 is requested by the upstream maintainer since causes
serious display issues with

  the budgie icon-tasklist is not displayed correctly.

  patch 2: Debian and Ubuntu only patch. Workaround patch for Debian based

  systems to stop crashes for budgie-panel and whole session crashes

  patch 3: volume patch

  upstream usability patch since volume indicator is not discoverable


  Debian packaging:

  have retested package but with a standard simpler debhelper package

  but unfortunately the same issues as previous budgie-desktop version, that is

  the package appears to build correctly but does not launch correctly on logon.

  Therefore have kept the identical packaging as the previous upload in stretch.


  Tested the source and .debs with lintian -i -I and identical results

  as for the previous package 10.2.6-2

  Changes since the last upload:

  * New upstream release
- upstream release 10.2.7
  * Add upstream recommended patch
- 0001 - fix icontask lisk spacing after reboot
  * add patch to stop budgie-panel menu crash on apt refresh
  * add volume patch
- 0002 - fix volume usability for panel indicator
  * Packaging changes
- drop patches gtk-link and GNOME 3.22 build since
  these are included in the 10.2.7 release


  Regards,
   David Mohammed

Bug#829690: [git-buildpackage/master] Command: redirect stdout/stderr to sys.stdout/stderr

[Markus Lehtonen]

tag 829690 pending
thanks

Date:   Fri Oct 9 14:22:31 2015 +0300
Author: Markus Lehtonen 
Commit ID: c6b32c81df7b5f70a339270369a12adaf0238730
Commit URL: 
https://git.sigxcpu.org/cgit/git-buildpackage/;a=commitdiff;h=c6b32c81df7b5f70a339270369a12adaf0238730
Patch URL: 
https://git.sigxcpu.org/cgit/git-buildpackage/;a=commitdiff_plain;h=c6b32c81df7b5f70a339270369a12adaf0238730

Command: redirect stdout/stderr to sys.stdout/stderr

Redirect stdout and stderr of the (child) command to sys.stdout and
sys.stderr of the caller, respectively. This change is mainly for the
unit tests. It makes Python nose to correctly capture the output of the
child command, too, which in turn suppresses a lot of spurious output
when running nosetests.

Closes: #829690

Signed-off-by: Markus Lehtonen 

A snapshot build including this change will be available at
http://honk.sigxcpu.org:8001/job/git-buildpackage/
  

Bug#837608: [libc++-dev] package is outdated/glibc dependant

[Gravis]

Package: libc++-dev
Version: 3.7.0-1
Severity: normal

--- Please enter the report below this line. ---
The libc++-dev package is out of date as the headers contained rely on
glibc specific macros.  It's been several releases since the ability to
utilize other libc implementations (e.g. musl) has been added.  It would be
great if someone could update the libc++ related packages.

--- System information. ---
Architecture: amd64
Kernel:   Linux 4.7.0-1-amd64

Debian Release: stretch/sid
  500 unstablemirrors.kernel.org
  500 testing mirrors.kernel.org
  500 stable  mirrors.kernel.org
  500 oldstable   mirrors.kernel.org

--- Package information. ---
Depends  (Version) | Installed
==-+-
libc++1(= 3.7.0-1) | 3.7.0-1
libc++-helpers | 3.7.0-1


Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#836972: All gnome packages should be linked by version dependencies

[Stijn Segers]

I've been bitten by this bug as well, can confirm upgrading to the 
3.21.9x packages from unstable fixes the backlight control / no info on 
screen found problems.


Cheers

Stijn

On Sat, 10 Sep 2016 21:53:36 +0200 Petr Pulc  wrote:
> Just to make things clear, at least the core packages should be all
> version-linked:
>
> gnome-color-manager
> gnome-control-center
> gnome-settings-daemon
> gnome-shell
>
> Otherwise, key components such as backlight dimming, will not work.

Bug#837547: pristine-tar commit fails if tarball contains German umlauts

[Tomasz Buchert]

On 12/09/16 13:58, Carsten Schoenert wrote:
> Package: pristine-tar
> Version: 1.37
> Severity: important
> 
> Dear Maintainer,
> 
> I need to commit a tarball that is containing content with German
> umlauts within the kicad source package.

Hi Carsten,

I cannot reproduceyour problem. I took the tarball from here:
https://github.com/KiCad/Shielding_Cabinets.pretty/releases and I was
able to commit it and check it out afterwards with zero problems.

I see that your tarballs has been dfsg-repacked. I wonder if it isn't
the repack that failed to properly create a +dfsg tarball. Can you please
provide me with the failing tarball?

Cheers,
Tomasz


signature.asc
Description: PGP signature

Bug#834683: [pkg-gnupg-maint] Bug#834683: fixed in mini-buildd 1.0.17

[Santiago Vila]

On Mon, Sep 12, 2016 at 07:34:09PM +0200, Daniel Kahn Gillmor wrote:

> An even easier approach might be to do the following within the build:
> 
>   * ln -sf /dev/urandom /dev/random
> 
> why would we need the blocking kernel RNG in the buildd anyway?

Either that, or maybe a build-depends on a package specifically
created to do that (as I'm not sure we could really ask all buildd
operators to make the symlink permanently).

A good solution should be automatic and not need manual intervention,
and should be independent of the machine on which the build is done.

> Lastly, one other option for gnupg at least is to patch upstream to use
> --debug-quick-random in the build-time test.
> 
> do any of these options sound more appealing than the others?

I didn't know about --debug-quick-random, it seems perfect to me.

Stephan, do you think it would be possible to patch mini-buildd so
that --debug-quick-random is added to gnupg command line, but only
when the package is doing the tests following the build?

Thanks.

Bug#837594: gnome-shell-extension-autohidetopbar: Not compatible with gnome-shell 3.21.x/3.22

[Tobias Frost]

Package: src:gnome-shell-extension-autohidetopbar
Followup-For: Bug #837594
Control: tags -1 upstream
Control: forwarded -1 https://github.com/mlutfy/hidetopbar/issues/107

Upstream has already a bug recorded, setting forwarded accordingly.

-- 
tobi


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

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

Bug#837607: jessie-pu: package elog/2.9.2+2014.05.11git44800a7-2

[Roger Kalt]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

Update closes bug https://bugs.debian.org/836505 which allowed to post entry as
arbitrary username by improper authentication.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
diff -Nru elog-2.9.2+2014.05.11git44800a7/debian/changelog elog-2.9.2+2014.05.11git44800a7/debian/changelog
--- elog-2.9.2+2014.05.11git44800a7/debian/changelog	2014-10-23 20:38:25.0 +0200
+++ elog-2.9.2+2014.05.11git44800a7/debian/changelog	2016-09-12 22:22:49.0 +0200
@@ -1,3 +1,10 @@
+elog (2.9.2+2014.05.11git44800a7-3) jessie; urgency=medium
+
+  * Added patch 0005_elogd_CVE-2016-6342_fix to fix posting entry as
+arbitrary username (Closes: #836505, CVE-2016-6342)
+
+ -- Roger Kalt   Mon, 12 Sep 2016 20:22:36 +0200
+
 elog (2.9.2+2014.05.11git44800a7-2) unstable; urgency=low
 
   * debian/control:
diff -Nru elog-2.9.2+2014.05.11git44800a7/debian/patches/0005_elogd_CVE-2016-6342_fix elog-2.9.2+2014.05.11git44800a7/debian/patches/0005_elogd_CVE-2016-6342_fix
--- elog-2.9.2+2014.05.11git44800a7/debian/patches/0005_elogd_CVE-2016-6342_fix	1970-01-01 01:00:00.0 +0100
+++ elog-2.9.2+2014.05.11git44800a7/debian/patches/0005_elogd_CVE-2016-6342_fix	2016-09-03 22:12:44.0 +0200
@@ -0,0 +1,345 @@
+backport these two upstream patches for newer release: https://bitbucket.org/ritt/elog/commits/2f6a300572bd6048351af8c45394ae62230c83d9 + https://bitbucket.org/ritt/elog/commits/9ca611aca2b1860efac15f806bf907cc2e6f870a/#Lsrc/elogd.cF26100T26104
+--- a/src/elogd.c
 b/src/elogd.c
+@@ -3443,7 +3443,7 @@
+ break;
+  get_user_line(lbs, login_name, NULL, NULL, email_from, NULL, NULL, NULL);
+  sprintf(email_from_name, "%s <%s>", login_name, email_from);
+- if (is_admin_user(lbs->name, login_name) && strchr(email_from, '@'))
++ if (is_admin_user(lbs, login_name) && strchr(email_from, '@'))
+ break;
+   }
+}
+@@ -8578,7 +8578,7 @@
+wrong_pwd = 2;
+  } else {
+ /* administrator does not have to supply old password if changing other user's password */
+-if (isparam("unm") && is_admin_user(lbs->name, getparam("unm"))
++if (isparam("unm") && is_admin_user(lbs, getparam("unm"))
+ && stricmp(getparam("unm"), user) != 0)
+wrong_pwd = 0;
+ else {
+@@ -8652,7 +8652,7 @@
+ 
+/* do not ask for old pwasword if admin changes other user's password */
+if (isparam("unm")) {
+-  if (!is_admin_user(lbs->name, getparam("unm")) || stricmp(getparam("unm"), user) == 0) {
++  if (!is_admin_user(lbs, getparam("unm")) || stricmp(getparam("unm"), user) == 0) {
+  if (isparam("oldpwd") && !(wrong_pwd == 1))// hidden password for password recovery
+ rsprintf("name, getparam("unm")))
++   if (is_admin_user(lbs, getparam("unm")))
+   return TRUE;
+ 
+/* search attribute which contains short_name of author */
+@@ -12126,7 +12126,7 @@
+rsprintf("\n", loc("Cancel"));
+ 
+if (lbs->top_group[0] && (!top_group || strieq(top_group, "global"))) {
+-  if (is_admin_user("global", getparam("unm"))) {
++  if (is_admin_user(lbs, getparam("unm"))) {
+  if (lbs->top_group[0]) {
+ 
+ sprintf(str, "global %s", lbs->top_group);
+@@ -12159,7 +12159,7 @@
+}
+ 
+if (is_group("global") && !strieq(top_group, "global")) {
+-  if (is_admin_user("global", getparam("unm"))) {
++  if (is_admin_user(lbs, getparam("unm"))) {
+  rsprintf("\n", loc("Delete this logbook"));
+  rsprintf("\n", loc("Rename this logbook"));
+  rsprintf("\n", loc("Create new logbook"));
+@@ -13275,7 +13275,7 @@
+ 
+/* if admin user, show user list */
+ 
+-   if (is_admin_user(logbook, getparam("unm"))) {
++   if (is_admin_user(lbs, getparam("unm"))) {
+   rsprintf("\n");
+   rsprintf("%s:\n", loc("Select user"));
+   rsprintf("\n");
+@@ -13323,7 +13323,7 @@
+else
+   strlcpy(str, user, sizeof(str));
+ 
+-   if (is_admin_user(logbook, getparam("unm"))) {
++   if (is_admin_user(lbs, getparam("unm"))) {
+   rsprintf("%s:\n", loc("Active"));
+   if (stricmp(user, getparam("unm")) == 0)
+  rsprintf
+@@ -13427,13 +13427,13 @@
+ 
+rsprintf("\n");
+ 
+-   if (is_admin_user(logbook, getparam("unm")) || !getcfg(logbook, "allow password change", str, sizeof(str))
++   if (is_admin_user(lbs, getparam("unm")) || !getcfg(logbook, "allow password change", str, sizeof(str))
+|| atoi(str) == 1)
+   rsprintf("\n", loc("Change password"));
+ 
+rsprintf("\n", loc("Remove user"));
+ 
+-   if (is_admin_user(logbook, 

Bug#837499: [Pkg-libvirt-maintainers] Bug#837499: virt-viewer & virt-manager's Spice viewer crash on first mouse click on GNOME+Wayland

[intrigeri]

Hi,

Guido Günther:
> I don't know about any such issues so it might be worth reporting this
> upstream.

OK, I'll try to do that next time I try to switch to Wayland again (my
only other identified blocker is also related to
virt-{viewer,manager}, not reported yet). Thanks!

> Do we have a Waylland session available via gdm3 nowadays

Yes :)

Cheers,
-- 
intrigeri

Bug#828593: virtualbox: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

On 2016-09-10 01:30:13 [+0200], Kurt Roeckx wrote:
> The code seems to be doing: The signature algorithm was
> sha1WithRSAEncryption, so the public key they passed us must
> have been an RSA key. But from what I understand, what the code
> really did was: it's an EVP_sha1(), it's an an RSA key. But if it
> was EVP_sha256(), it was an unknown key type. What they do might
> have worked in the past by accident. But it clearly doesn't work
> properly.
> 
> I don't think there is a way of doing what they want to do.  They
> should really just pass the type of the public key to the
> function.

I think I've found it a few lines above.

VirtualBox hackers! Could you please take a look at this? It should
compile against openssl 1.1.0 and 1.0.2h and work.

> Kurt

Sebastian
>From 0e3d6cc69959fdf4f4fd56f65353b76897c0daad Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior 
Date: Wed, 7 Sep 2016 20:22:54 +
Subject: [PATCH] virtualbox 5.1.4: get it built against openssl-1.1

Signed-off-by: Sebastian Andrzej Siewior 
---
 src/VBox/RDP/client-1.8.3/ssl.c| 70 +-
 src/VBox/Runtime/VBox/VBoxRTDeps.cpp   | 14 +++---
 src/VBox/Runtime/common/crypto/pkix-verify.cpp | 46 +++--
 3 files changed, 83 insertions(+), 47 deletions(-)

diff --git a/src/VBox/RDP/client-1.8.3/ssl.c b/src/VBox/RDP/client-1.8.3/ssl.c
index dac5511..bd207d5 100644
--- a/src/VBox/RDP/client-1.8.3/ssl.c
+++ b/src/VBox/RDP/client-1.8.3/ssl.c
@@ -97,7 +97,7 @@ rdssl_rsa_encrypt(uint8 * out, uint8 * in, int len, uint32 modulus_size, uint8 *
 		  uint8 * exponent)
 {
 	BN_CTX *ctx;
-	BIGNUM mod, exp, x, y;
+	BIGNUM *mod, *exp, *x, *y;
 	uint8 inr[SEC_MAX_MODULUS_SIZE];
 	int outlen;
 
@@ -107,24 +107,24 @@ rdssl_rsa_encrypt(uint8 * out, uint8 * in, int len, uint32 modulus_size, uint8 *
 	reverse(inr, len);
 
 	ctx = BN_CTX_new();
-	BN_init();
-	BN_init();
-	BN_init();
-	BN_init();
-
-	BN_bin2bn(modulus, modulus_size, );
-	BN_bin2bn(exponent, SEC_EXPONENT_SIZE, );
-	BN_bin2bn(inr, len, );
-	BN_mod_exp(, , , , ctx);
-	outlen = BN_bn2bin(, out);
+	mod = BN_new();
+	exp = BN_new();
+	x = BN_new();
+	y = BN_new();
+
+	BN_bin2bn(modulus, modulus_size, mod);
+	BN_bin2bn(exponent, SEC_EXPONENT_SIZE, exp);
+	BN_bin2bn(inr, len, x);
+	BN_mod_exp(y, x, exp, mod, ctx);
+	outlen = BN_bn2bin(y, out);
 	reverse(out, outlen);
 	if (outlen < (int) modulus_size)
 		memset(out + outlen, 0, modulus_size - outlen);
 
-	BN_free();
-	BN_clear_free();
-	BN_free();
-	BN_free();
+	BN_free(y);
+	BN_clear_free(x);
+	BN_free(exp);
+	BN_free(mod);
 	BN_CTX_free(ctx);
 }
 
@@ -149,18 +149,25 @@ rdssl_cert_to_rkey(RDSSL_CERT * cert, uint32 * key_len)
 	EVP_PKEY *epk = NULL;
 	RDSSL_RKEY *lkey;
 	int nid;
+	X509_PUBKEY *x509_pk;
+	X509_ALGOR *algor;
+	const ASN1_OBJECT *alg_obj;
 
 	/* By some reason, Microsoft sets the OID of the Public RSA key to
 	   the oid for "MD5 with RSA Encryption" instead of "RSA Encryption"
 
 	   Kudos to Richard Levitte for the following (. intiutive .) 
 	   lines of code that resets the OID and let's us extract the key. */
-	nid = OBJ_obj2nid(cert->cert_info->key->algor->algorithm);
+
+	x509_pk = X509_get_X509_PUBKEY(cert);
+	X509_PUBKEY_get0_param(NULL, NULL, NULL, , x509_pk);
+	X509_ALGOR_get0(_obj, NULL, NULL, algor);
+
+	nid = OBJ_obj2nid(alg_obj);
 	if ((nid == NID_md5WithRSAEncryption) || (nid == NID_shaWithRSAEncryption))
 	{
 		DEBUG_RDP5(("Re-setting algorithm type to RSA in server certificate\n"));
-		ASN1_OBJECT_free(cert->cert_info->key->algor->algorithm);
-		cert->cert_info->key->algor->algorithm = OBJ_nid2obj(NID_rsaEncryption);
+		X509_ALGOR_set0(algor, OBJ_nid2obj(NID_rsaEncryption), 0, NULL);
 	}
 	epk = X509_get_pubkey(cert);
 	if (NULL == epk)
@@ -203,21 +210,37 @@ rdssl_rkey_free(RDSSL_RKEY * rkey)
 	RSA_free(rkey);
 }
 
+#if OPENSSL_VERSION_NUMBER < 0x1010
+static inline void RSA_get0_key(const RSA *r, const BIGNUM **n,
+const BIGNUM **e, const BIGNUM **d)
+{
+	if (n != NULL)
+		*n = r->n;
+	if (e != NULL)
+		*e = r->e;
+	if (d != NULL)
+		*d = r->d;
+}
+#endif
+
 /* returns error */
 int
 rdssl_rkey_get_exp_mod(RDSSL_RKEY * rkey, uint8 * exponent, uint32 max_exp_len, uint8 * modulus,
 		   uint32 max_mod_len)
 {
 	int len;
+	const BIGNUM *e, *n;
+
+	RSA_get0_key(rkey, , , NULL);
 
-	if ((BN_num_bytes(rkey->e) > (int) max_exp_len) ||
-	(BN_num_bytes(rkey->n) > (int) max_mod_len))
+	if ((BN_num_bytes(e) > (int) max_exp_len) ||
+	(BN_num_bytes(n) > (int) max_mod_len))
 	{
 		return 1;
 	}
-	len = BN_bn2bin(rkey->e, exponent);
+	len = BN_bn2bin(e, exponent);
 	reverse(exponent, len);
-	len = BN_bn2bin(rkey->n, modulus);
+	len = BN_bn2bin(n, modulus);
 	reverse(modulus, len);
 	return 0;
 }
@@ -238,8 +261,5 @@ void
 rdssl_hmac_md5(const void *key, int key_len, const unsigned char *msg, int msg_len,
 	   unsigned char *md)
 {
-	HMAC_CTX ctx;
-	HMAC_CTX_init();
 	HMAC(EVP_md5(), key, key_len, msg, msg_len, 

Bug#835253: RFS: steghide/0.5.1-11 [QA]

[Gianfranco Costamagna]

Hi,



>I was actually referring to the original version 0.5.1-10 from the
>Debian archive.
>When you have doxygen it builds the same way you have in the version I
>uploaded. I was just reproducing the same result.
>I was not clear about it, sorry.
>In any case:


ok this makes sense now :)

BTW, what about having the documentation in a separate -doc package?
(and in the doc standard location)


>dget -x 
>https://mentors.debian.net/debian/pool/main/s/steghide/steghide_0.5.1-11.dsc



seems really better, however I have some last complains
1) std-version is now 3.9.8

2) 
-rw-r--r-- root/root  6816 2016-08-22 23:03 
./usr/share/doc/steghide/COPYING.gz


now this file is installed (and probably useless)
quoting changelog:

+  * Refixed so that INSTALL and COPYING information is not in the
+deb archive.



quoting old rules:

+   $(MAKE) install prefix=`pwd`/debian/steghide/usr
+   rm -rf `pwd`/debian/steghide/usr/doc
+   rm -f `pwd`/debian/steghide/usr/share/doc/steghide/INSTALL
+   rm -f `pwd`/debian/steghide/usr/share/doc/steghide/INSTALL.gz
+   rm -f `pwd`/debian/steghide/usr/share/doc/steghide/COPYING


so, I would try to remove it again

3) this RFS has been picked up by Breno, so he should have the final words 
about the
package :)
(I hope he don't mind my review, and hope he won't ask you to change something 
back)

G.

Bug#837606: general: system freeze

[Rouven-Matthias Müller]

Package: general
Severity: important

Dear Maintainer,

the system freezes after a random amount of time. the mouse is still moving but
anything else is frozen. what i consider to be a very big bug is the fact, that
a program can cause this effect. it does not matter if that problem is related
to a other program. the problem is that programs can freeze the entire system!

thank you for your attention.
rouven



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

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

Bug#835502: [Pkg-mpd-maintainers] Bug#835502: mpd: add systemd user unit for autorun with systemd user-session

[Florian Schlichting]

Hi Protserovsd,

> In Archlinux mpd package provides /usr/lib/systemd/user/mpd.service file, 
> which
> allows mpd to be started by systemd user session (useful for autostart on user
> login). It would be great if Debian packages' also provided this unit.

this is an interesting suggestion. I don't have much experience with
user units, but I think it's not too dangerous to experiment a bit. So
mpd 0.19.19-1 which I'm just uploading to unstable has a user unit,
slightly adjusted from the system unit (simplified - do you know what
Arch is using?).

I wonder how that works together with the XDG autostart .desktop file
that we ship?

Please try it out and send me your suggestions!

Florian

PS:
Since you seem to be using stable, can you just add the unit file there
and see if that works well?
as /usr/lib/systemd/user/mpd.service:

[Unit]
Description=Music Player Daemon (user unit)
Documentation=man:mpd(1) man:mpd.conf(5)
Documentation=file:///usr/share/doc/mpd/user-manual.html

[Service]
ExecStart=/usr/bin/mpd --no-daemon

# disallow writing to /usr, /bin, /sbin, ...
ProtectSystem=yes

[Install]
WantedBy=default.target

Bug#834683: [pkg-gnupg-maint] Bug#834683: fixed in mini-buildd 1.0.17

[Daniel Kahn Gillmor]

Hi Santiago and all--

On Sun 2016-09-11 21:30:22 +0200, Santiago Vila wrote:
> Well, maybe the problem has always been there.
>
> Maybe official autobuilders have a lot of entropy and we have never
> found the problem there, but IMHO we should not take that for granted
> in the general case.

I would hope that the autobuilders never actually *need* entropy to
build packages.  we want package builds to be reproducible, and entropy
isn't necessary for that :)

> But I really don't know. A quick search on gnupg and /dev/random
> led me to the "haveged" package you mention.
>
> This is the kind of "entropy helper" package I believed it "had" to exist,
> but I have never used any of them really.
>
> Would be possible to have haveged as a build-dependency of this
> package so that it works automatically and avoids the problem in a
> generic way for every kind of autobuilder trying to build the package?

I've used haveged with gnupg before.  It certainly removes the kernel's
sense of lacking entropy, but i have had no time to verify that the bits
mixed into the random pool by haveged is in any way a robust entropy
source.  I'm also not sure that haveged is available (or well-motivated)
on all architectures, since what little logic i've understood about how
haveged works sounded processor-specific to me.

> Maybe we should ask dkg and the other people maintaining gnupg about
> what it's usually done in cases like this (package needing a lot of
> entropy in its build system).

An even easier approach might be to do the following within the build:

  * ln -sf /dev/urandom /dev/random

why would we need the blocking kernel RNG in the buildd anyway?

Lastly, one other option for gnupg at least is to patch upstream to use
--debug-quick-random in the build-time test.

do any of these options sound more appealing than the others?

 --dkg
 


signature.asc
Description: PGP signature

Bug#837605: libgksu FTCBFS: uses build architecture pkg-config in a few places

[Helmut Grohne]

Source: libgksu
Version: 2.0.13~pre1-8
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

libgksu fails to cross build from source, because it uses the build
architecture pkg-config in a few places and thus fails finding e.g. gtk.
It does discover the right pkg-config in configure but fails to use the
discovered tool. I am attaching a patch that replaces a few bare
"pkg-config" with "$(PKG_CONFGI)" and thus makes a cross build succeed.
Please consider applying it.

Helmut
diff --minimal -Nru libgksu-2.0.13~pre1/debian/changelog 
libgksu-2.0.13~pre1/debian/changelog
--- libgksu-2.0.13~pre1/debian/changelog2014-09-06 23:08:49.0 
+0200
+++ libgksu-2.0.13~pre1/debian/changelog2016-09-12 21:57:28.0 
+0200
@@ -1,3 +1,10 @@
+libgksu (2.0.13~pre1-8.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Add 24_cross.patch (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 12 Sep 2016 21:42:15 +0200
+
 libgksu (2.0.13~pre1-8) unstable; urgency=medium
 
   * Adding myself to uploaders
diff --minimal -Nru libgksu-2.0.13~pre1/debian/patches/24_cross.patch 
libgksu-2.0.13~pre1/debian/patches/24_cross.patch
--- libgksu-2.0.13~pre1/debian/patches/24_cross.patch   1970-01-01 
01:00:00.0 +0100
+++ libgksu-2.0.13~pre1/debian/patches/24_cross.patch   2016-09-12 
21:57:02.0 +0200
@@ -0,0 +1,45 @@
+From: Helmut Grohne 
+Subject: fix cross compilation by using the cross tools discovered by configure
+
+Index: libgksu-2.0.13~pre1/libgksuui/Makefile.am
+===
+--- libgksu-2.0.13~pre1.orig/libgksuui/Makefile.am
 libgksu-2.0.13~pre1/libgksuui/Makefile.am
+@@ -1,10 +1,10 @@
+ AM_CFLAGS = -g -O2 -Wall
+-INCLUDES = `pkg-config --cflags gtk+-2.0 gconf-2.0`
++INCLUDES = `$(PKG_CONFIG) --cflags gtk+-2.0 gconf-2.0`
+ AM_CPPFLAGS = -DLOCALEDIR=\"$(datadir)/locale\" -DDATA_DIR=\"$(datadir)\" 
-DPREFIX=\"$(prefix)\"
+ 
+ noinst_LTLIBRARIES = libgksuui1.0.la
+ libgksuui1_0_la_SOURCES = gksuui-dialog.c
+-libgksuui1_0_la_LDFLAGS = -Wl,-O1 `pkg-config --libs gtk+-2.0 gconf-2.0 x11`
++libgksuui1_0_la_LDFLAGS = -Wl,-O1 `$(PKG_CONFIG) --libs gtk+-2.0 gconf-2.0 
x11`
+ 
+ noinst_HEADERS = defines.h gksuui.h gksuui-dialog.h
+ includedir = ${prefix}/include/$(PACKAGE)
+@@ -12,4 +12,4 @@
+ noinst_PROGRAMS = test-gksuui
+ test_gksuui_SOURCES = test-gksuui.c
+ test_gksuui_LDADD = libgksuui1.0.la
+-test_gksuui_LDFLAGS = `pkg-config --libs glib-2.0 x11`
++test_gksuui_LDFLAGS = `$(PKG_CONFIG) --libs glib-2.0 x11`
+Index: libgksu-2.0.13~pre1/libgksu/Makefile.am
+===
+--- libgksu-2.0.13~pre1.orig/libgksu/Makefile.am
 libgksu-2.0.13~pre1/libgksu/Makefile.am
+@@ -28,12 +28,12 @@
+ 
+ pkglibdir = ${libdir}/${PACKAGE}
+ pkglibexec_PROGRAMS = gksu-run-helper
+-gksu_run_helper_LDFLAGS = `pkg-config --libs glib-2.0`
++gksu_run_helper_LDFLAGS = `$(PKG_CONFIG) --libs glib-2.0`
+ gksu_run_helper_SOURCES = gksu-run-helper.c
+ 
+ noinst_PROGRAMS = test-gksu
+ test_gksu_SOURCES = test-gksu.c
+ test_gksu_LDADD = libgksu2.la
+-test_gksu_LDFLAGS = `pkg-config --libs glib-2.0 gtk+-2.0`
++test_gksu_LDFLAGS = `$(PKG_CONFIG) --libs glib-2.0 gtk+-2.0`
+ 
+ EXTRA_DIST = libgksu.ver
diff --minimal -Nru libgksu-2.0.13~pre1/debian/patches/series 
libgksu-2.0.13~pre1/debian/patches/series
--- libgksu-2.0.13~pre1/debian/patches/series   2014-09-06 22:31:11.0 
+0200
+++ libgksu-2.0.13~pre1/debian/patches/series   2016-09-12 21:41:43.0 
+0200
@@ -5,4 +5,5 @@
 05_ja.patch
 06_unguarded_child_stderr.patch
 23_correct_colormap_get.patch
+24_cross.patch
 99_intltool.patch

Bug#837499: [Pkg-libvirt-maintainers] Bug#837499: virt-viewer & virt-manager's Spice viewer crash on first mouse click on GNOME+Wayland

[Guido Günther]

On Mon, Sep 12, 2016 at 02:08:57AM +0200, intrigeri wrote:
> Package: virt-viewer
> Version: 4.0-1
> Severity: normal
> 
> Hi,
> 
> on current Debian sid, running GNOME on Wayland, I start a Debian sid
> desktop VM with libvirt/QEMU. It boots fine up to the graphical
> interface, but as soon as I click somewhere it crashes. The exact
> error message depends on how exactly I display the VM locally:
> 
>  * using virt-manager's own Spice viewer:
> 
>python2: ../../../../src/cairo-surface.c:928: cairo_surface_reference: 
> Assertion `(_cairo_atomic_int_get (&(>ref_count)->ref_count) > 0)' 
> failed.
> 
>  * running a standalone virt-viewer:
> 
>../../../../src/cairo-surface.c:953: cairo_surface_destroy: Assertion 
> `(_cairo_atomic_int_get (&(>ref_count)->ref_count) > 0)' failed.
> 
> I've also seen in the Journal, around the time of the crash:
> 
>   gnome-shell[11969]: 
> (wayland/meta-wayland-surface.c:424):meta_wayland_surface_ref_buffer_use_count:
>  runtime check failed: (surface->buffer_ref.buffer->resource)
> 
> Running virt-manager with GDK_BACKEND=x11 fixes this problem.
> 
> I've found no corresponding bug in upstream bug tracker
> (https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW_status=ASSIGNED=Community=Virtualization%20Tools_format=advanced),
> so I wonder if that's a known issue or something specific to my setup.

I don't know about any such issues so it might be worth reporting this
upstream. Do we have a Waylland session available via gdm3 nowadays or
is there a specific setup required?
Cheers,
 -- Guido

Bug#818448: fixed in imapcopy 1.04-2.1

[Gianfranco Costamagna]

Hi

>This upload looks like it was made by Peter Green.
>But I was told on IRC that his only involvement was posting a patch to 
>the BTS (with a comment that the patch was only build-tested).
>The actual upload was made by Gianfranco Costamagna.


yes this is true
>Gianfranco, as per Policy §4.4, please put your own name in the 
>changelog trailer when making an upload.


well, it seems unfair wrt Peter, who actually did *all* the work and
even updated the changelog.
I also fail to parse policy in that case, but I fully trust your words
so next time I'll just override the signature
(this is something I usually do when people submit just patches, not
the whole work on BTS).

e.g. with a patch I would have done
apply the patch

[ foo bar ]
* fix patch foobar

signed by me

In this case the signature was already there...

>Please also always post debdiff to the BTS before making an NMU.


being lazy, and having the debdiff already there... made me think
it was good to avoid this step

>(I guess that in this case debdiff is equal to what Peter posted in the 
>BTS, but it's not obvious, and I shouldn't have to guess.)


I hope you agree it was somewhere a corner case, I though about sending to the 
BTS
something like
"I uploaded the debdiff posted before", but I forgot :(

Sorry for that!

BTW on top of the changes, me and a friend of mine, tested the basic
functions of the imapcopy tool.
(not sure if the testing was complete or not, since it was just a FTBFS
fix and it was somewhere trivial).
the fix was referring network operations, it might break somewhere in some 
particular
networks, but I think this isn't the case.

Sorry again, and yes
please consider the above debdiff uploaded bit-bit identical.

thanks!

G.

Bug#837601: [Pkg-mutt-maintainers] Bug#837601: mutt segfaults when leaving pager view on new message

[Hannes von Haugwitz]

Hi,

Thanks for your reply.

I can reproduce it on an up to date sid:

- install postfix (local only config), mutt and bsd-mailx

- # echo Test | mail -s "Test" hvhaugwitz

- run mutt as user hvhaugwitz (without config) and open mail in pager

- # echo Test | mail -s "Test" hvhaugwitz

- leave pager by pressing 'i' or 'q'

Best regards

Hannes

Bug#818448: fixed in imapcopy 1.04-2.1

[Jakub Wilk]

* Peter Michael Green , 2016-09-11, 16:20:

Changed-By: Peter Michael Green 
Description:
imapcopy   - IMAP backup, copy and migration tool
Closes: 818448
Changes:
imapcopy (1.04-2.1) unstable; urgency=medium
.
  * Non-maintainer upload.
  * Fix build with fpc 3.0.0 (Closes: 818448)


This upload looks like it was made by Peter Green.
But I was told on IRC that his only involvement was posting a patch to 
the BTS (with a comment that the patch was only build-tested).

The actual upload was made by Gianfranco Costamagna.

Gianfranco, as per Policy §4.4, please put your own name in the 
changelog trailer when making an upload.


Please also always post debdiff to the BTS before making an NMU.

(I guess that in this case debdiff is equal to what Peter posted in the 
BTS, but it's not obvious, and I shouldn't have to guess.)


--
Jakub Wilk

Bug#836741: linux: FTBFS on powerpcspe due to the use of unsupported instructions

[Ben Hutchings]

Control: tag -1 upstream patch

On Sat, 2016-09-10 at 11:01 +0200, John Paul Adrian Glaubitz wrote:
> Control: forwarded -1 
> https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-September/148424.html
> Control: tags -1 +pending
> 
> There is now a suggested patch on the linuxppc-dev mailing list which fixes
> this issue [1]. Should be part of the next stable kernel update, will 
> therefore
> tag this bug report as pending.

It won't, it's not even in linux-next yet.  Please don't add the
pending tag just because a patch has been accepted upstream.

Anyway, I have applied this to the sid branch so it really is pending
now.

Ben.

-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
A fail-safe circuit will destroy
others.


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

Bug#837530: [Debichem-devel] Bug#837530: elpa: FTBFS due to symbols changes

[Graham Inggs]

On 12 September 2016 at 11:00, Bas Couwenberg  wrote:
> The upload of openmpi (2.0.1-3) to unstable has triggered an
> uncoordinated transition (#836917). Unfortunately your package FTBFS due
> to symbols changes:

Interesting that these two symbols disappeared everywhere except on amd64.
I've just done a test rebuild in Ubuntu Yakkety (which still has
openmpi 1.10) and the symbols remained on amd64 and disappeared
everywhere else, so I'd say this wasn't caused by the openmpi
transition.  I'll try to investigate further.

Bug#798301: Me too

[Salvo Tomaselli]

I can confirm this problem. It's a pain in the ass.

Bug#837588: hppa: Please disable CONFIG_FTRACE for hppa architecture

[Ben Hutchings]

Control: tag -1 pending

On Mon, 2016-09-12 at 18:17 +0200, Helge Deller wrote:
[...]
> So, can you please deactivate CONFIG_FTRACE completely for 32- and 64bit hppa 
> configs?
> Is it sufficient to add "CONFIG_FTRACE=n" to debian/config/hppa/config ?

Done.

Ben.

-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
A fail-safe circuit will destroy
others.


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

Bug#837604: openjpeg2: CVE-2016-7163: Integer overflow in opj_pi_create_decode

[Salvatore Bonaccorso]

Source: openjpeg2
Version: 2.1.0-2
Severity: grave
Tags: security upstream patch
Control: fixed -1 2.1.0-2+deb8u1

Hi,

the following vulnerability was published for openjpeg2.

CVE-2016-7163[0]:
Integer overflow in opj_pi_create_decode

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-7163

Regards,
Salvatore

Bug#837553: patch included

[Ghislain Vaillant]

 >From 625526d0e5b739908fd190cfed9c80f599d607d1 Mon Sep 17 00:00:00 2001
From: Ghislain Antony Vaillant 
Date: Mon, 12 Sep 2016 20:26:04 +0100
Subject: [PATCH] Track gitlab releases.

---
 debian/watch | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/debian/watch b/debian/watch
index d2d9238..415b26b 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,2 +1,3 @@
 version=3
-http://byuu.org/emulation/higan/ .*higan_v(\d+)-source\.7z
+opts=filenamemangle=s/.*\.tar\.gz\?ref=v?(\d\S*)/higan-$1\.tar\.gz/g \
+https://gitlab.com/higan/higan/tags .*archive\.tar\.gz\?ref=v?(\d\S*)
-- 
2.9.3

Bug#806563: openjdk-8-jre: java leaks memory in when using JTree if used from debian package. Orginal binary works fine

[Wiktor Niesiobedzki]

I've just noticed, that there is one crucial step missing - between 4
and 5 should be:
4b. Minimize the command stack windows by pressing "down arrow" icon
on the topleft corner of command stack window.

Bug#811818: crrcsim: FTBFS with GCC 6: no match for

[Gert Wollny]

Control: tags -1 patch

Dear maintainer,

please find enclosed a patch that fixes building with gcc-6.

Note that the patch makes the assumption that a newline was expected in 
the output instead of std::cerr.


best regards,

Gert

Description: Correct compilation with gcc-6
 The patch assumes that a newline was the intended output after the 
 according message. 
Author: Gert Wollny  
Forwarded:no
Debian-Bug: https://bugs.debian.org/811818

--- a/src/mod_video/crrc_animation.cpp
+++ b/src/mod_video/crrc_animation.cpp
@@ -84,7 +84,7 @@
   else
   {
 std::cerr << "createAnimation: unknown animation type '"
-  << type << "'" << std::cerr;
+  << type << "'" << std::endl;
   }
   
   if (anim != NULL)

Bug#837601: [Pkg-mutt-maintainers] Bug#837601: mutt segfaults when leaving pager view on new message

[Antonio Radici]

Control: tag -1 moreinfo

On Mon, Sep 12, 2016 at 08:41:41PM +0200, Hannes von Haugwitz wrote:
> Package: mutt
> Version: 1.7.0-3
> Severity: important
> 
> Hi,
> 
> mutt 1.7.0-3 segfaults when leaving the pager view on new message:
> 
> Reading /var/mail/hvhaugwitz... 0Segmentation fault
> 
> Steps to reproduce:
> 1. read a mail
> 2. send mail to mailbox
> 3. leave pager view (eg by pressing 'i')
> 

Hi Hannes, thanks for your bug report.

Adding Mattia who, I believe, has the same problem, unfortunately I'm unable to
reproduce :(

Can you attach your muttrc? or, even better, does it segfaults if you have a
MINIMAL muttrc with your spoolfile to imap (if you use imap) and start it with

mutt -n -F .minimal-muttrc

Please let me know, I'm eager to debug this as soon as it is reproducible

Bug#837584: [Pkg-mutt-maintainers] Bug#837584: mutt: crash while navigating through inbox

[Antonio Radici]

forcemerge 837601 837584
thanks

Same as #837601, it is high on my priority list as soon as I'm able to reproduce
it.