Bug#791300: tesseract: library transition may be needed when GCC 5 is the default

[Simon McVittie]

Control: reopen 791300

On Thu, 13 Aug 2015 at 09:36:18 +0200, Mehdi Dogguy wrote:
> The exposed symbols matching the mentioned tags are not part of the public 
> API.
> So, renaming of binary packages is not required here. Thus, closing.

I'm not so sure about that conclusion:
 says gimagereader
failed to start with missing tesseract-related symbols. Reopening.

S

Bug#796866: not accessible VCS reference

[Eduard Bloch]

Source: libzen
Version: 0.4.31-3
Severity: minor

Package info says that you use 
git://git.debian.org/git/pkg-multimedia/packages/libzen.git

But:
Klone nach 'libzen' ...
fatal: remote error: access denied or repository not exported: 
/git/pkg-multimedia/packages/libzen.git

Regards,
Eduard.

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

Kernel: Linux 4.2.0-rc8+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

-- 
 Der OOM-Killer hat mich überredet, meinen Arbeitsspeicher von
1GB auf 4GB zu vergrößern. Irgendwie stört es nämlich schon, wenn
der Rechner nicht reagiert und man warten muss bis der OOM-killer
chromium erledigt hat (was Dienstag mehrmals passiert ist)

Bug#793761: chromium: freezes at startup in xfce4

[Arturo Borrero Gonzalez]

On 25 August 2015 at 02:57, Michael Gilbert  wrote:
> On Mon, Aug 24, 2015 at 3:29 AM, Arturo Borrero Gonzalez wrote:
>>  $ chromium
>> [15556:15556:0824/092809:ERROR:master_preferences.cc(99)] Failed to
>> read preferences from /usr/share/chromium
>
> What are the permissions on /usr/share/chromium/master_preferences?
>

ll /usr/share/chromium/master_preferences
-rw-r--r-- 1 root root 724 jun 25 01:36 /usr/share/chromium/master_preferences


-- 
Arturo Borrero González

Bug#796759: reportbug: HTTPError 500 Internal Server Error

[Sandro Tosi]

On Mon, Aug 24, 2015 at 2:47 AM, Pierre Rudloff  wrote:
>   File "/usr/lib/pymodules/python2.7/debianbts.py", line 179, in get_status
> reply = server.get_status(*nr)
>   File "/usr/lib/python2.7/dist-packages/SOAPpy/Client.py", line 545, in
> __call__
> return self.__r_call(*args, **kw)
>   File "/usr/lib/python2.7/dist-packages/SOAPpy/Client.py", line 567, in
> __r_call
> self.__hd, self.__ma)
>   File "/usr/lib/python2.7/dist-packages/SOAPpy/Client.py", line 430, in 
> __call
> timeout = self.timeout)
>   File "/usr/lib/python2.7/dist-packages/SOAPpy/Client.py", line 318, in call
> raise HTTPError(code, msg)
> SOAPpy.Errors.HTTPError: 

This is actually a problem in python-debianbts, which was fixed in
version 1.13, so you should upgrade to it. I will use this bug to bump
the dependency in reportbug, so it will pull in an update package.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

Bug#796865: RM: goocanvas/experimental -- NVIU; obsoleted by goocanvas-2.0

[Alberto Garcia]

Package: ftp.debian.org
Severity: normal

goocanvas 2.0.2-1.1 in experimental is obsoleted by the new source
package goocanvas-2.0, which contains the same upstream version and is
already in unstable.

The original goocanvas package will keep track of the upstream 0.x
branch, whereas goocanvas-2.0 follows the 2.x.

Regards,

Berto

Bug#795014: fixed in adplug 2.2.1+dfsg3-0.3

[Adam Lee]

reopen 795014
thanks

On Mon, Aug 24, 2015 at 02:16:44PM +0300, Alex Moonshine wrote:
> On Mon, 24 Aug 2015 00:00:14 + Simon McVittie 
> wrote:
> > Source: adplug
> > Source-Version: 2.2.1+dfsg3-0.3
> > 
> > We believe that the bug you reported is fixed in the latest version of
> > adplug, which is due to be installed in the Debian FTP archive.
> 
> 
> mpd in Sid still depends on libadplug version 2.2.1+dfgs3-0.2+b1.
> It won't install with 2.2.1+dfsg3-0.3 in place, complains about broken
> packages.

force overriding with v5 2.2.1+dfsg3-0.3 doesn't work either, mpd
outputs the same error, reopen this bug then.

BTW, could maintainer please update the summary of libadplug-2.2.1-0 and
libadplug-2.2.1-0v5? I have some trouble to tell them apart...

Thanks.

-- 
Adam Lee

Bug#796863: libassa3.5-5v5 and libassa-3.5-5v5: error when trying to install together

[Ralf Treinen]

Package: libassa-3.5-5v5,libassa3.5-5v5
Version: libassa-3.5-5v5/3.5.1-6
Version: libassa3.5-5v5/3.5.1-4.1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2015-08-24
Architecture: amd64
Distribution: sid

Hi,

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


Selecting previously unselected package gcc-5-base:amd64.
(Reading database ... 10899 files and directories currently installed.)
Preparing to unpack .../gcc-5-base_5.2.1-15_amd64.deb ...
Unpacking gcc-5-base:amd64 (5.2.1-15) ...
Setting up gcc-5-base:amd64 (5.2.1-15) ...
(Reading database ... 10906 files and directories currently installed.)
Preparing to unpack .../libstdc++6_5.2.1-15_amd64.deb ...
Unpacking libstdc++6:amd64 (5.2.1-15) over (4.8.2-19) ...
Setting up libstdc++6:amd64 (5.2.1-15) ...
Processing triggers for libc-bin (2.19-19) ...
Selecting previously unselected package libassa-3.5-5v5:amd64.
(Reading database ... 10920 files and directories currently installed.)
Preparing to unpack .../libassa-3.5-5v5_3.5.1-6_amd64.deb ...
Unpacking libassa-3.5-5v5:amd64 (3.5.1-6) ...
Selecting previously unselected package libassa3.5-5v5:amd64.
Preparing to unpack .../libassa3.5-5v5_3.5.1-4.1_amd64.deb ...
Unpacking libassa3.5-5v5:amd64 (3.5.1-4.1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libassa3.5-5v5_3.5.1-4.1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libassa-3.5.so.5.0.1', which is 
also in package libassa-3.5-5v5:amd64 3.5.1-6
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libassa3.5-5v5_3.5.1-4.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

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

  /usr/lib/x86_64-linux-gnu/libassa-3.5.so.5
  /usr/lib/x86_64-linux-gnu/libassa-3.5.so.5.0.1

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

-Ralf.

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

Bug#796864: libmodglue1v5 and libmodglue1: error when trying to install together

[Ralf Treinen]

Package: libmodglue1,libmodglue1v5
Version: libmodglue1/1.17-2.2+b1
Version: libmodglue1v5/1.17-2.3
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2015-08-24
Architecture: amd64
Distribution: sid

Hi,

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


(Reading database ... 10899 files and directories currently installed.)
Preparing to unpack .../aptitude_0.7-1+b1_amd64.deb ...
Unpacking aptitude (0.7-1+b1) over (0.6.10-1) ...
Preparing to unpack .../aptitude-common_0.7-1_all.deb ...
Unpacking aptitude-common (0.7-1) over (0.6.10-1) ...
Selecting previously unselected package gcc-5-base:amd64.
Preparing to unpack .../gcc-5-base_5.2.1-15_amd64.deb ...
Unpacking gcc-5-base:amd64 (5.2.1-15) ...
Processing triggers for man-db (2.7.2-1) ...
Setting up gcc-5-base:amd64 (5.2.1-15) ...
(Reading database ... 10900 files and directories currently installed.)
Preparing to unpack .../libstdc++6_5.2.1-15_amd64.deb ...
Unpacking libstdc++6:amd64 (5.2.1-15) over (4.8.2-19) ...
Setting up libstdc++6:amd64 (5.2.1-15) ...
Processing triggers for libc-bin (2.19-19) ...
Selecting previously unselected package libapt-pkg4.16:amd64.
(Reading database ... 10914 files and directories currently installed.)
Preparing to unpack .../libapt-pkg4.16_1.0.10.2_amd64.deb ...
Unpacking libapt-pkg4.16:amd64 (1.0.10.2) ...
Selecting previously unselected package libboost-iostreams1.58.0:amd64.
Preparing to unpack .../libboost-iostreams1.58.0_1.58.0+dfsg-3_amd64.deb ...
Unpacking libboost-iostreams1.58.0:amd64 (1.58.0+dfsg-3) ...
(Reading database ... 10968 files and directories currently installed.)
Removing libcwidget3:amd64 (0.5.17-1) ...
Removing libsigc++-2.0-0c2a:amd64 (2.4.1-1) ...
Processing triggers for libc-bin (2.19-19) ...
Selecting previously unselected package libsigc++-2.0-0v5:amd64.
(Reading database ... 10915 files and directories currently installed.)
Preparing to unpack .../libsigc++-2.0-0v5_2.4.1-2_amd64.deb ...
Unpacking libsigc++-2.0-0v5:amd64 (2.4.1-2) ...
Selecting previously unselected package libcwidget3v5:amd64.
Preparing to unpack .../libcwidget3v5_0.5.17-4_amd64.deb ...
Unpacking libcwidget3v5:amd64 (0.5.17-4) ...
(Reading database ... 10968 files and directories currently installed.)
Removing libept1.4.12:amd64 (1.0.12) ...
Removing libxapian22 (1.2.17-1) ...
Processing triggers for libc-bin (2.19-19) ...
Selecting previously unselected package libxapian22v5.
(Reading database ... 10955 files and directories currently installed.)
Preparing to unpack .../libxapian22v5_1.2.21-1.2_amd64.deb ...
Unpacking libxapian22v5 (1.2.21-1.2) ...
Selecting previously unselected package libmodglue1.
Preparing to unpack .../libmodglue1_1.17-2.2+b1_amd64.deb ...
Unpacking libmodglue1 (1.17-2.2+b1) ...
Selecting previously unselected package libmodglue1v5.
Preparing to unpack .../libmodglue1v5_1.17-2.3_amd64.deb ...
Unpacking libmodglue1v5 (1.17-2.3) ...
dpkg: error processing archive 
/var/cache/apt/archives/libmodglue1v5_1.17-2.3_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man1/prompt.1.gz', which is also in 
package libmodglue1 1.17-2.2+b1
Processing triggers for man-db (2.7.2-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libmodglue1v5_1.17-2.3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

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

  /usr/bin/prompt
  /usr/bin/ptywrap
  /usr/lib/libmodglue.a
  /usr/lib/libmodglue.so.1
  /usr/lib/libmodglue.so.1.0.17
  /usr/lib/pkgconfig/modglue.pc
  /usr/share/man/man1/prompt.1.gz
  /usr/share/man/man1/ptywrap.1.gz

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

-Ralf.

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

Bug#796862: ITP: golang-github-d2g-dhcp4client -- DHCP client written in Go

[Potter, Tim (Cloud Services)]

X-Debbugs-Cc: debian-de...@lists.debian.org, 
pkg-go-maintain...@lists.alioth.debian.org
Package: wnpp
Severity: wishlist
Owner: Tim Potter 

* Package name: golang-github-d2g-dhcp4client
 Version : 0.0~git20150520
 Upstream Author : Dan Goldsmith
* URL : https://github.com/d2g/dhcp4client
* License : BSD-3-clause
 Programming Lang: Go
 Description : DHCP client written in Go

A DHCP4 client implemetation written in Go using AF_PACKET
support.

Bug#796861: ITP: golang-github-d2g-dhcp4 -- DHCP packet creation library for Go

[Potter, Tim (Cloud Services)]

X-Debbugs-Cc: debian-de...@lists.debian.org, 
pkg-go-maintain...@lists.alioth.debian.org
Package: wnpp
Severity: wishlist
Owner: Tim Potter 

* Package name: golang-github-d2g-dhcp4
 Version : 0.0~git20150413
 Upstream Author : Dan Goldsmith
* URL : https://github.com/d2g/dhcp4
* License : BSD-3-clause
 Programming Lang: Go
 Description : DHCP packet creation library for Go

This library contains functions to generate DHCP request and
response packets in the Go language.

Bug#796860: freedombox-setup: Remove unused and not-working code

[Sunil Mohan Adapa]

Package: freedombox-setup
Version: 0.5
Severity: normal
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

There are some components that are not being used and are
not even working currently.  This make is it harder for us
test and make major changes.  Remove any such code.


-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJV2/Y1AAoJEDbDYUQMm8lxe6wP/2eNd+M5x0/vk86MqiLJaYBj
+fB1weaJ8fphf4nTs+4WNXo9E4Z3CNCyK7aBKkOiaZvLYYiuchXbJ7mL7kXbcWIg
+ETu35wvG18iyQpd4BkcPtM89Gk69to8lTtS++o/kFOeCyoYRk8ejFNjYZHWprUa
/iVpSLzYZUnlK36IjBH3LWllE4sAaiKQyAfzgYIRmMRs5XJuHi9VBpFKmGTwSbrA
djY6pOANiNzGkN58qnP3sdTX22UW/RZD1ETQAW97w/zJVYRSFk3jDOjlqScSbRW7
SyQzDFibAl+pctyoB/2UT+glZ8Bi6ETH/gVmLR6O8xtmJKJiD3GAA28yCaNfjz1Q
MP+zU4+PoeHxQ1LJyh7SukHCmGOMrjk00Eemh4tZjEmklbKuj4jmTMOYC2XC7M9E
bAWU3iMjwcezIl/UbEjDPgTsBLQev34y8aoxxHhl6cXFyiNR77m/bqRg4vXPaIgU
au0Z+5v5swjw2+Dy+kg2LS5fY3OhcVVAERGnCn8Y7j2lawxFydloeLu5i4/hmnon
H980XOtAeeBEBSbyGr7xLb2tDGVkI243JqnqhhfZ2ycAFHmOrtVJmdAl13MU121N
6GuWJL4o/PlJ0heGRVp+A3TIoyv4qAzi5PdldhV9NwHLYH0Xu9N6cWzeGnzgko5V
sPximrR3hTOcOhhXM/gH
=zDFQ
-END PGP SIGNATURE-
>From 7c021be3c3eb84cc1936b1161d141b2ead0612e0 Mon Sep 17 00:00:00 2001
From: Sunil Mohan Adapa 
Date: Thu, 13 Aug 2015 21:47:57 +0530
Subject: [PATCH 1/4] Remove unused OpenVPN setup file

- When OpenVPN service is provided, it's setup and configuration will be
  in Plinth.
---
 setup.d/50_openvpn | 8 
 1 file changed, 8 deletions(-)
 delete mode 100755 setup.d/50_openvpn

diff --git a/setup.d/50_openvpn b/setup.d/50_openvpn
deleted file mode 100755
index d64e17e..000
--- a/setup.d/50_openvpn
+++ /dev/null
@@ -1,8 +0,0 @@
-#!/bin/sh
-
-# Disabled as it seem to be just cruft from earlier [pere 2013-10-28]
-exit 0
-
-mkdir -p /etc/openvpn
-touch /etc/openvpn/static.key
-touch /etc/openvpn/client.conf
-- 
2.1.4


>From faf2c2850f9103cad70b9f1c6a51af79ed9cbbaf Mon Sep 17 00:00:00 2001
From: Sunil Mohan Adapa 
Date: Thu, 13 Aug 2015 22:01:09 +0530
Subject: [PATCH 2/4] Remove unused GPG key generation

- This must be implemented in Plinth first boot.
---
 first-run.d/20_gpg-key | 13 -
 1 file changed, 13 deletions(-)
 delete mode 100755 first-run.d/20_gpg-key

diff --git a/first-run.d/20_gpg-key b/first-run.d/20_gpg-key
deleted file mode 100755
index 5acd609..000
--- a/first-run.d/20_gpg-key
+++ /dev/null
@@ -1,13 +0,0 @@
-#!/bin/sh
-#
-# see http://lists.gnupg.org/pipermail/gnupg-users/2003-March/017376.html
-
-# . /lib/lsb/init-functions
-
-#log_action_begin_msg "Creating GPG key"
-#echo "  Need to create other keys."
-#if gpg --batch --gen-key ; then
-#log_action_end_msg 0
-# else
-#log_action_end_msg 1
-# fi
-- 
2.1.4


>From 48b09f964b7d9441df4ad0b7bf06efea1324ebe0 Mon Sep 17 00:00:00 2001
From: Sunil Mohan Adapa 
Date: Sun, 16 Aug 2015 15:12:01 +0530
Subject: [PATCH 3/4] Remove referenceto a non-existing init script

---
 debian/rules | 1 -
 1 file changed, 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 190d67f..01209da 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,5 +4,4 @@
 
 override_dh_installinit:
 	dh_installinit --no-start --name=freedombox-first-run -u"start 20 2 3 4 5 ."
-	dh_installinit --no-start --name=freedombox-client-proxy -u"start 20 2 3 4 5 ."
 	dh_installinit --no-start --name=freedombox-create-uap0 -u"start 20 2 3 4 5 ."
-- 
2.1.4


>From e85537a6b5234a7235ae815e39d2c5ed02ffa307 Mon Sep 17 00:00:00 2001
From: Sunil Mohan Adapa 
Date: Sun, 16 Aug 2015 16:01:32 +0530
Subject: [PATCH 4/4] Remove unused script copy2dream

- It appears it is an artifact of a time when images where build without
  vmdebootstrap.

- Only documentation in freedom-maker refers to it.
---
 sbin/copy2dream | 47 ---
 1 file changed, 47 deletions(-)
 delete mode 100644 sbin/copy2dream

diff --git a/sbin/copy2dream b/sbin/copy2dream
deleted file mode 100644
index 267c2b6..000
--- a/sbin/copy2dream
+++ /dev/null
@@ -1,47 +0,0 @@
-#!/bin/sh
-#
-# this script assumes the current root filesystem is the source, and the
-# internal microSD on a DreamPlug is the target .. all existing content on
-# the microSD card will be lost.
-#
-
-# partition microSD card inside DreamPlug
-echo "=> partition internal microSD card"
-parted -s /dev/sda mklabel msdos
-parted -s /dev/sda mkpart primary fat16 0 128
-parted -s /dev/sda mkpart primary ext2 128 100%
-
-# create filesystems on new partitions
-echo "=> create filesystems on internal microSD card"
-mkdosfs /dev/sda1
-mke2fs -j /dev/sda2
-
-echo "=> mount target partitions"
-mount /dev/sda2 /media
-mkdir -p /media/boot
-mount /dev/sda1 /media/boot
-
-echo "=> copy filesystem content from USB stick to target partitions"
-(cd / ; tar cpSf - `/bin/ls | grep -v boot | grep -v proc | grep -v sys | grep -v media | grep -v dev`) | (cd /media ; tar xpf -)
-# the following intentionally ignores subdirectories 
-cp /boot/* /media/boot/
-
-echo "=> touch up target root partition"
-mkdir /media/proc /media/

Bug#796859: ITP: golang-github-coreos-go-iptables -- Go bindings for iptables utility

[Potter, Tim (Cloud Services)]

X-Debbugs-Cc: debian-de...@lists.debian.org, 
pkg-go-maintain...@lists.alioth.debian.org
Package: wnpp
Severity: wishlist
Owner: Tim Potter 

* Package name: golang-github-coreos-go-iptables
  Version : 0.0~git20150805
  Upstream Author : Eugene Yakubovich
* URL : https://github.com/eyakubovich/go-iptables
* License : Apache-2.0
  Programming Lang: Go
  Description : Go bindings for iptables utility

The go-iptables module wraps the invocation of the iptables
utility with Go functions to append and delete iptables rules,
as well as create, clear and delete iptables chains.

Bug#796858: [libreoffice-calc] Text color only appears in cell edit mode

[Bzzzz]

Package: libreoffice-calc
Version: 1:5.0.1~rc1-2
Severity: normal

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

Hi folks,

Text color isn't normally displayed, only in cell edit mode.

PS: Just in case… I only target a very few bunubu repo to get those
pkgs:

tlp | 0.8-1~trusty |
http://ppa.launchpad.net/linrunner/tlp/ubuntu/ trusty/main amd64 Packages

tlp-rdw | 0.8-1~trusty |
http://ppa.launchpad.net/linrunner/tlp/ubuntu/ trusty/main amd64 Packages

wxformbuilder | 3.5.01.01-0ubuntu1~trusty1 |
http://ppa.launchpad.net/wxformbuilder/release/ubuntu/ trusty/main amd64
Packages

libwxadditions30 | 3.0.10.6-0ubuntu1~trusty1 |
http://ppa.launchpad.net/wxformbuilder/release/ubuntu/ trusty/main amd64
Packages

wxfb-wxadditions | 1.15.1-0ubuntu1~trusty2 |
http://ppa.launchpad.net/wxformbuilder/release/ubuntu/ trusty/main amd64
Packages

virtualbox-5.0 | 5.0.2-102096~Ubuntu~trusty |
http://download.virtualbox.org/virtualbox/debian/ trusty/contrib amd64
Packages

--- System information. ---
Architecture: amd64
Kernel:   Linux 4.1.0-2-amd64

Debian Release: stretch/sid
  500 unstablepackages.x2go.org 
  500 unstableftp.ch.debian.org 
  500 unstablefiles.freeswitch.org 
  500 trusty  ppa.launchpad.net 
  500 stable  download.bitdefender.com 

--- Package information. ---
Depends (Version) | Installed
=-+-=
libreoffice-base-core   (= 1:4.3.0-2) | 1:5.0.1~rc1-2
libreoffice-core(= 1:4.3.0-2) | 1:5.0.1~rc1-2
lp-solve   (>= 5.5.0.13-5+b1) | 5.5.0.13-7+b1
libboost-iostreams1.55.0  | 1.55.0+dfsg-4
libc6   (>= 2.14) | 
libgcc1  (>= 1:4.1.1) | 
libicu52(>= 52~m1-1~) | 
liblcms2-2   (>= 2.2+git20110628) | 
libmwaw-0.3-3 | 
libodfgen-0.1-1   | 
liborcus-0.8-0| 
librevenge-0.0-0  | 
libstdc++6   (>= 4.9) | 
libwps-0.3-3  | 
libxml2(>= 2.7.4) | 
uno-libs3(>= 4.3.0~alpha) | 
ure   | 
zlib1g   (>= 1:1.1.4) | 
fontconfig| 
fonts-opensymbol  | 
libreoffice-common   (>> 1:4.3.0) | 
ure (>= 4.2~) | 
libatk1.0-0   (>= 1.12.4) | 
libboost-date-time1.55.0  | 
libc6   (>= 2.16) | 
libcairo2  (>= 1.2.4) | 
libclucene-contribs1 (>= 2.3.3.4) | 
libclucene-core1 (>= 2.3.3.4) | 
libcmis-0.4-4  (>= 0.4.0) | 
libcups2   (>= 1.4.0) | 
libcurl3-gnutls   (>= 7.16.2) | 
libdbus-1-3(>= 1.0.2) | 
libdbus-glib-1-2(>= 0.78) | 
libeot0   | 
libexpat1  (>= 2.0.1) | 
libexttextcat-2.0-0(>= 2.2-8) | 
libfontconfig1  (>= 2.11) | 
libfreetype6   (>= 2.3.5) | 
libgcc1  (>= 1:4.1.1) | 
libgdk-pixbuf2.0-0(>= 2.22.0) | 
libgl1-mesa-glx   | 
 OR libgl1| 
libglew1.10   (>= 1.10.0) | 
libglib2.0-0  (>= 2.15.0) | 
libglu1-mesa  | 
 OR libglu1   | 
libgraphite2-3 (>= 1.2.2) | 
libgtk2.0-0   (>= 2.24.0) | 
libharfbuzz-icu0  (>= 0.9.18) | 
libharfbuzz0b (>= 0.9.18) | 
libhunspell-1.3-0  (>= 1.3.3) | 
libhyphen0 (>= 2.7.1) | 
libice6  (>= 1:1.0.0) | 
libicu52(>= 52~m1-1~) | 
libjpeg8   2

Bug#796572: python-nemu: diff for NMU version 0.2-1.1

[Martín Ferrari]

Andrey,

On 22/08/15 19:39, Andrey Rahmatullin wrote:

> I've prepared an NMU for python-nemu (versioned as 0.2-1.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.

Thank you very much for this, I had forgotten to fix this!

I have incorporated your diff into the package, and uploaded a new
version of including some changes I had pending, so you can cancel your
upload (or just let it be rejected automatically).

Thanks again.

-- 
Martín Ferrari (Tincho)

Bug#791016: ctpp2: ftbfs, and library transition is needed when GCC 5 is the default

[Vasudev Kamath]

Simon McVittie  writes:

> On Sat, 22 Aug 2015 at 14:32:59 +0530, Vasudev Kamath wrote:
>> I've updated the package droping libjs-jquery related modification. I've
>> pushed the changes to collab.
>
> Thanks, I've sponsored that upload for you. It should go into the NEW
> queue shortly.

Thank you!.

>
>> PS: I've not added lintian override, I think its not needed as issue is
>> already known. Let me know if otherwise.
>
> I think what you've done is fine.
>
> S
Alright.

Bug#796442: §5.5 Uploads to suites other than unstable/experimental should use codenames, not suites

[Charles Plessy]

Control: tag -1 pending

> > Le Fri, Aug 21, 2015 at 10:59:23PM +0200, Didier 'OdyX' Raboud a écrit :
> > > 
> > > --- devref.orig.txt 2015-08-21 22:49:46.985614431 +0200
> > > +++ devref.new.txt  2015-08-21 22:58:15.226984105 +0200
> > > @@ -2209,9 +2209,10 @@
> > >  from the first line of the debian/changelog file and places it in
> > >  the Distribution field of the .changes file.
> > >  
> > > -There are several possible values for this field: stable,
> > > -    unstable, testing-proposed-updates and experimental. Normally,
> > > -packages are uploaded into unstable.
> > > +Packages are normally uploaded into unstable. Uploads to unstable or
> > > +experimental should use these suite names in the changelog entry;
> > > +uploads for other supported suites should use the suite codenames,
> > > +as they avoid any ambiguity.

> Charles Plessy  (2015-08-22):
> > 
> > Are there other comments on Didier's proposal ?

Le Tue, Aug 25, 2015 at 04:01:16AM +0200, Cyril Brulebois a écrit :
> 
> Seconded, thanks.

Committed and pushed, thanks.

-- 
Charles

Bug#796838: [pkg-go] Bug#796838: golang-snappy-go-dev and golang-github-golang-snappy-dev: error when trying to install together

[Martín Ferrari]

Hi Ralf,

On 24/08/15 21:36, Ralf Treinen wrote:

> Here is a list of files that are known to be shared by both packages
> (according to the Contents file for sid/amd64, which may be
> slightly out of sync):
> 
>   /usr/share/gocode/src/github.com/golang/snappy/decode.go
>   /usr/share/gocode/src/github.com/golang/snappy/encode.go
>   /usr/share/gocode/src/github.com/golang/snappy/snappy.go
>   /usr/share/gocode/src/github.com/golang/snappy/snappy_test.go

Well, it seems that we have two different packages for the same source :-)

Hilko, I see you uploaded with the new naming standard, so we should
keep that one, but it would be good to create transitional packages and
to sync maintainer stuff.

-- 
Martín Ferrari (Tincho)

Bug#682580: [bug-gettext] Bug#682580: xgettext: fails to properly replace some placeholders in output .pot (PACKAGE, YEAR, C. HOLDER) (fwd)

[Daiki Ueno]

Francesco Poli  writes:

> I'd definitely vote for 3, but, wait!, even better, I would add a new
> option named --copyright-notices (or maybe there's a better name, I
> don't know...), where all the copyright notices may be specified with
> their own line breaks, as in:

I'm afraid it would break configurability through po/Makevars, since a
make variable including a multi-line argument cannot be used in a
portable Makefile.

By the way, if we chose (4), the patch would be like the attached, which
reads the file po/HEADER (if exists) and insert the content into POT
file.  The file would look like:

  # Copyright (C) 2001-2012 Python Software Foundation.
  # Copyright (C) 2000 BeOpen.com.
  # Copyright (C) 1995-2000 Corporation for National Research Initiatives.
  # Copyright (C) 1991-1995 Stichting Mathematisch Centrum.

If this is sufficient, I would revert the multiple --copyright-holder
change, as I am reluctant to add new option to xgettext, which already
has too many options.

Regards,
-- 
Daiki Ueno
>From c8f8099dca7976fa26d7ac671446144f1fe044c9 Mon Sep 17 00:00:00 2001
From: Daiki Ueno 
Date: Tue, 25 Aug 2015 11:47:20 +0900
Subject: [PATCH] po: Insert HEADER file into POT file

* gettext-tools/po/Makefile.in.in ($(DOMAIN).pot-update): Add
insert-header.sed to prerequisites.  Insert the contents of the file
"HEADER".
(mostlyclean): Remove insert-header.sed.
---
 gettext-runtime/po/ChangeLog  | 6 ++
 gettext-runtime/po/Makefile.in.in | 8 +++-
 2 files changed, 13 insertions(+), 1 deletion(-)

diff --git a/gettext-runtime/po/ChangeLog b/gettext-runtime/po/ChangeLog
index e5d8f0d..73ccaa2 100644
--- a/gettext-runtime/po/ChangeLog
+++ b/gettext-runtime/po/ChangeLog
@@ -1,3 +1,9 @@
+2015-08-25  Daiki Ueno  
+
+	* Makefile.in.in ($(DOMAIN).pot-update): Add insert-header.sed to
+	prerequisites.  Insert the contents of the file "HEADER".
+	(mostlyclean): Remove insert-header.sed.
+
 2015-07-10  Daiki Ueno  
 
 	* gettext 0.19.5 released.
diff --git a/gettext-runtime/po/Makefile.in.in b/gettext-runtime/po/Makefile.in.in
index c36f1ad..f4267ab 100644
--- a/gettext-runtime/po/Makefile.in.in
+++ b/gettext-runtime/po/Makefile.in.in
@@ -150,7 +150,7 @@ stamp-po: $(srcdir)/$(DOMAIN).pot
 # The determination of whether the package xyz is a GNU one is based on the
 # heuristic whether some file in the top level directory mentions "GNU xyz".
 # If GNU 'find' is available, we avoid grepping through monster files.
-$(DOMAIN).pot-update: $(POTFILES) $(srcdir)/POTFILES.in remove-potcdate.sed
+$(DOMAIN).pot-update: $(POTFILES) $(srcdir)/POTFILES.in remove-potcdate.sed insert-header.sed
 	package_gnu="$(PACKAGE_GNU)"; \
 	test -n "$$package_gnu" || { \
 	  if { if (LC_ALL=C find --version) 2>/dev/null | grep GNU >/dev/null; then \
@@ -195,6 +195,11 @@ $(DOMAIN).pot-update: $(POTFILES) $(srcdir)/POTFILES.in remove-potcdate.sed
 	;; \
 	esac
 	test ! -f $(DOMAIN).po || { \
+	  if test -f $(srcdir)/HEADER; then \
+	sed -f insert-header.sed < $(DOMAIN).po > $(DOMAIN).1po && \
+	rm -f $(DOMAIN).po && \
+	mv $(DOMAIN).1po $(DOMAIN).po; \
+	  fi; \
 	  if test -f $(srcdir)/$(DOMAIN).pot; then \
 	sed -f remove-potcdate.sed < $(srcdir)/$(DOMAIN).pot > $(DOMAIN).1po && \
 	sed -f remove-potcdate.sed < $(DOMAIN).po > $(DOMAIN).2po && \
@@ -365,6 +370,7 @@ info dvi ps pdf html tags TAGS ctags CTAGS ID:
 
 mostlyclean:
 	rm -f remove-potcdate.sed
+	rm -f insert-header.sed
 	rm -f stamp-poT
 	rm -f core core.* $(DOMAIN).po $(DOMAIN).1po $(DOMAIN).2po *.new.po
 	rm -fr *.o
-- 
2.4.3

Bug#791151: liborigin2 done

[Scott Kitterman]

All (both) reverse-build deps rebuilt.

Scott K

Bug#441404: Laurasofia1

[Lizeth marzory Caycedo sanjuan]

Enviado desde mi iPad

Bug#796466: pepper: FTBFS: error: ‘svn_sort__hash’ was not declared in this scope

[Antoine Beaupré]

This was fixed in pysvn by rewriting that code, which seems pretty
amazing, but could be considered a canonical way.

http://pysvn.tigris.org/source/browse/pysvn/trunk/pysvn/Extension/Source/pysvn_client_cmd_info.cpp?r1=1601&r2=1600&pathrev=1601

And I *think* this is how it was fixed in kdevelop:

https://git.reviewboard.kde.org/r/124783/diff/1#index_header

... according to this post:

http://article.gmane.org/gmane.comp.kde.devel.kdevelop/41420

Jonas, can you take a look at this? I think this is a little beyond what
I can do as the Debian package maintainer in the short term.. :)

(If this is not fixed, Pepper will be taken out of Debian stretch, the
next stable release, unfortunately.)

A.

-- 
Every one of us is, in the cosmic perspective, precious. If a human
disagrees with you, let him live. In a hundred billion galaxies, you
will not find another.  - Carl Sagan

Bug#796857: pspp: halts when reading sintax file

[alvaro rincon]

Package: pspp
Version: 0.7.9+git20120620-1.1
Severity: important

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?

when you run  the sintax file

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

changing the sintax stops the problem




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

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=es_VE.UTF-8, LC_CTYPE=es_VE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages pspp depends on:
ii  dpkg   1.16.16
ii  install-info   4.13a.dfsg.1-10
ii  libatk1.0-02.4.0-2
ii  libc6  2.13-38+deb7u8
ii  libcairo2  1.12.2-3
ii  libfontconfig1 2.9.0-7.1
ii  libfreetype6   2.4.9-1.1+deb7u1
ii  libgdk-pixbuf2.0-0 2.26.1-1
ii  libglib2.0-0   2.33.12+really2.32.4-5
ii  libgsl0ldbl1.15+dfsg.2-2
ii  libgtk2.0-02.24.10-2
ii  libgtksourceview2.0-0  2.10.4-1
ii  libncurses55.9-10
ii  libpango1.0-0  1.30.0-1
ii  libpq5 9.1.16-0+deb7u2
ii  libreadline6   6.2+dfsg-0.1
ii  libtinfo5  5.9-10
ii  libxml22.8.0+dfsg1-7+wheezy4
ii  zlib1g 1:1.2.7.dfsg-13

pspp recommends no packages.

pspp suggests no packages.

-- no debconf information

Bug#796442: §5.5 Uploads to suites other than unstable/experimental should use codenames, not suites

[Cyril Brulebois]

Charles Plessy  (2015-08-22):
> Le Fri, Aug 21, 2015 at 10:59:23PM +0200, Didier 'OdyX' Raboud a écrit :
> > 
> > --- devref.orig.txt 2015-08-21 22:49:46.985614431 +0200
> > +++ devref.new.txt  2015-08-21 22:58:15.226984105 +0200
> > @@ -2209,9 +2209,10 @@
> >  from the first line of the debian/changelog file and places it in
> >  the Distribution field of the .changes file.
> >  
> > -There are several possible values for this field: stable,
> > -    unstable, testing-proposed-updates and experimental. Normally,
> > -packages are uploaded into unstable.
> > +Packages are normally uploaded into unstable. Uploads to unstable or
> > +experimental should use these suite names in the changelog entry;
> > +uploads for other supported suites should use the suite codenames,
> > +as they avoid any ambiguity.
> >  
> >  Actually, there are other possible distributions: codename
> >      -security, but read Section 5.8.5, “Handling security-related
> 
> Thanks Didier, I think that the change reflects current practice and
> should be committed.  Here is a DocBook-ised version.
> 
> diff --git a/pkgs.dbk b/pkgs.dbk
> index 457619d..126eaac 100644
> --- a/pkgs.dbk
> +++ b/pkgs.dbk
> @@ -285,10 +285,10 @@ The package build process extracts this information 
> from the first line of the
>  Distribution field of the .changes 
> file.
>  
>  
> -There are several possible values for this field: stable,
> -unstable, testing-proposed-updates and
> -experimental.  Normally, packages are uploaded into
> -unstable.
> +Packages are normally uploaded into unstable. Uploads to
> +unstable or experimental should use 
> these
> +suite names in the changelog entry; uploads for other supported suites should
> +use the suite codenames, as they avoid any ambiguity.
>  
>  
>  Actually, there are other possible distributions:
> 
> Are there other comments on Didier's proposal ?

Seconded, thanks.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#795844: armel and armhf images missing kernel and initramfs

[Cyril Brulebois]

Hi,

Steve McIntyre  (2015-08-17):
> Package: cdimage.debian.org
> Severity: serious
> Tags: d-i
> 
> As mentioned by bwh: existing armel and armhf installer CDs are
> currently missing vmlinuz and the initramfs...

Do we have any clue about what's going on here? It would have been nice
to have cc'd me. Looks like something that should be documented in
errata.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#790494: modem-manager-gui: libebook 3.16 API break

[Persmule]

Dear Graham,

There already is a patch 
http://download.tuxfamily.org/gsf/patch/modem-manager-gui-0.0.17.1-fix-libebook-api-break-v2.patch
 
linked on 
http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?0.item.3.31.0 
,
but the bug remains not tracked.

In order to use modem-manager-gui on stretch, I applied this patch locally to 
build new .deb packages, and the result works like a charm. 
In the process I created a debianized patch file. May it be useful to you and 
every stretch users.

Best regards

Persmule

Description: temporarily fix bug #790494
Author: Xie Tianming 

Origin: other, http://download.tuxfamily.org/gsf/patch/modem-manager-gui-0.0.17.1-fix-libebook-api-break-v2.patch
Bug: http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?0.item.3.31.0
Bug-Debian: https://bugs.debian.org/790494
Forwarded: no
Last-Update: 2015-05-02

--- modem-manager-gui-0.0.17.1.orig/src/addressbooks.c
+++ modem-manager-gui-0.0.17.1/src/addressbooks.c
@@ -36,6 +36,8 @@
 #include "vcard.h"
 #include "addressbooks.h"
 
+#define MMGUI_ADDRESSBOOKS_GNOME_CONNECT_TIMEOUT 15
+
 #define MMGUI_ADDRESSBOOKS_AKONADI_LINK_PATH "%s/.local/share/akonadi/socket-localhost"
 #define MMGUI_ADDRESSBOOKS_AKONADI_SOCKET_PATH   "%s/akonadiserver.socket"
 #define MMGUI_ADDRESSBOOKS_AKONADI_DBUS_INTERFACE"org.freedesktop.Akonadi.Control"
@@ -78,7 +80,6 @@ struct _mmgui_addressbooks_akonadi_colle
 
 typedef struct _mmgui_addressbooks_akonadi_collection *mmgui_addressbooks_akonadi_collection_t;
 
-
 //KDE (Akonadi)
 static gboolean mmgui_addressbooks_session_service_activate(gchar *interface, guint *status);
 static gint mmgui_addressbooks_open_kde_socket(void);
@@ -95,7 +96,7 @@ static guint mmgui_addressbooks_akonadi_
 static gboolean mmgui_addressbooks_get_kde_contacts(mmgui_addressbooks_t addressbooks);
 //GNOME (Evolution data server)
 static void mmgui_addressbooks_get_gnome_contacts_foreach(gpointer data, gpointer user_data);
-static gboolean mmgui_addressbooks_get_gnome_contacts(mmgui_addressbooks_t addressbooks);
+static gboolean mmgui_addressbooks_get_gnome_contacts(mmgui_addressbooks_t addressbooks, mmgui_libpaths_cache_t libcache);
 //Other
 static void mmgui_addressbooks_free_contacts_list_foreach(gpointer data, gpointer user_data);
 
@@ -787,7 +788,7 @@ static void mmgui_addressbooks_get_gnome
 	g_list_free(emails);
 }
 
-static gboolean mmgui_addressbooks_get_gnome_contacts(mmgui_addressbooks_t addressbooks)
+static gboolean mmgui_addressbooks_get_gnome_contacts(mmgui_addressbooks_t addressbooks, mmgui_libpaths_cache_t libcache)
 {
 	EBookQuery *queryelements[2];
 	EBookQuery *query;
@@ -802,12 +803,17 @@ static gboolean mmgui_addressbooks_get_g
 	EBook *book;
 	GList *dcontacts;
 	
-	if (addressbooks == NULL) return FALSE;
+	if ((addressbooks == NULL) || (libcache == NULL)) return FALSE;
 	if (!addressbooks->gnomesupported) return FALSE;
 	if (addressbooks->ebookmodule == NULL) return FALSE;
 	
 	error = NULL;
 	
+	if (!mmgui_libpaths_cache_check_library_version(libcache, "libebook-1.2", 12, 3, 0)) {
+		g_debug("GNOME contacts API isn't supported\n");
+		return FALSE;
+	}
+	
 	queryelements[0] = (addressbooks->e_book_query_field_exists)(E_CONTACT_PHONE_HOME);
 	queryelements[1] = (addressbooks->e_book_query_field_exists)(E_CONTACT_PHONE_MOBILE);
 	
@@ -817,39 +823,63 @@ static gboolean mmgui_addressbooks_get_g
 		return FALSE;
 	}
 	
-	if (addressbooks->e_book_new_system_addressbook != NULL) {
-		g_debug("Using old GNOME contacts API\n");
-		book = (addressbooks->e_book_new_system_addressbook)(&error);
-		if (book == NULL) {
+	if (mmgui_libpaths_cache_check_library_version(libcache, "libebook-1.2", 14, 3, 0)) {
+		g_debug("Using GNOME contacts API version 3.6 ... ?\n");
+		registry = (addressbooks->e_source_registry_new_sync)(NULL, &error);
+		if (registry == NULL) {
 			(addressbooks->e_book_query_unref)(query);
-			g_debug("Failed to load GNOME system addressbook: %s\n", error->message);
+			g_debug("Failed to get ESourceRegistry: %s\n", error->message);
 			g_error_free(error);
 			return FALSE;
 		}
 		
-		if (!(addressbooks->e_book_open)(book, TRUE, &error)) {
+		source = (addressbooks->e_source_registry_ref_builtin_address_book)(registry);
+		if (source == NULL) {
 			(addressbooks->e_book_query_unref)(query);
-			g_debug("Failed to load GNOME system addressbook: %s\n", error->message);
-			g_error_free(error);
+			g_debug("Failed to get ESource\n");
 			return FALSE;
 		}
 		
-		source = (addressbooks->e_book_get_source)(book);
+		addressbooks->gnomesourcename = (addressbooks->e_source_get_display_name)(source);
 		
-		if (addressbooks->e_source_get_display_name != NULL) {
-			addressbooks->gnomesourcename = (addressbooks->e_source_get_display_name)(source);
+		if (mmgui_libpaths_cache_check_library_version(libcache, "libebook-1.2", 16, 3, 0)) {
+			/*Version 3.16 ... ?*/
+			client = (EBookClient *)(addressbooks->e_book_client_connect_sync316)(source, MMGUI_ADDRESSBOOKS_GNOME_CONNECT_T

Bug#793876: RFS: chrony/1.31.1-1

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 25/08/15 02:00, Vincent Blut wrote:
> Le mar. 25 août 2015 à 0:33, Jerome BENOIT  a écrit :
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi:
>>
>> On 24/08/15 23:52, Vincent Blut wrote:
>>>  After inspecting Jerome’s custom init script, it appreared it was buggy.
>>
>> To my defence: 1] the buggy part was commented as obsoleted, 2] it contains 
>> more material,
>> in particular support for /etc/network/if-*.d
> 
> You're right, my sentence sounds like the whole init script was buggy, but 
> that isn't the case.
> The context was about the supposedly "breakage" of the "-u" option expressed 
> in 55d503b7.7050...@rezozer.net
> 
> Sorry, if that offended you!

I just wanted to clarify :-) I am bad, but that bad.

> 
>>>  However I’ll have to find a way not to mess with users who set the default
>>>  chronyd user in the init script instead of using the "user" directive in
>>>  /etc/chrony/chrony.conf. To be honest I don’t see an easy way of doing it,
>>>  so a first good step will probably be to add a "warning" in a NEWS file.
>>
>> Note that regular users are not supposed to modify their /etc/init.d/chrony 
>> but
>> they are supposed to configure properly their  /etc/chrony/chrony.conf .
> 
> Sure, but it'd be great to mitigate upgrade issues for those that did so.

1] modified init.d scripts are managed by Debian at, so you do not have to 
worry about this;
2] most importantly, adventurous folks who modified their init.d scripts are 
supposed to know what they do.

> 
>> I modify my /etc/init.d/chrony mainly to get /etc/network/if-*.d support.
>> BTW, is PPP stuff still needed ?
> 
> Yes, there are still Dial-up only internet accesses here and there, but its
> usage dropped significantly in favor of broadband Internet access.
> 
>> In short, you may rather focus on #312092 and #633422
>>
>> hth,
>> Jerome
> 
> Cheers,
> Vincent

Best wishes,
Jerome
> 
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJV27+EAAoJEIC/w4IMSybjRnYIAITEFF3Su3naL4SGDt0TpieR
vxSqaN/lfgluHso5/HqmHMemMQM17WgVWSgVTMjO0kexl6/ZBJI1WoLiPL236vWY
1wOHu11ks1XD9S7WLDkoFUkg9gDUFMcT9T7GMUh9TAGTaEgfNauWSbIWNfl+fj2t
c91W16WLldoFnKCIHfAjhRGLuvhfEKRDY08uo5Q35r6yUjTeHNeLZiggmuv5U8FT
1rc5lDEcGWmPX8gK0Z4X6m+CVdA+Xzowaq2qX2pBMLYn/H84+WOUvJmsaF93HD2g
PyOj2WaZg9q7SZ5MsedY1sUItgunA9+gbtdKLoXbNkOZaKA5+GP/N/3b9L83AYI=
=mxTm
-END PGP SIGNATURE-

Bug#663185: interested in (co-)maintaining midori

[Sergio Durigan Junior]

On Friday, August 14 2015, Andres Salomon wrote:

>> Your work was done back in June, so if you prefer I can provide
>> patches against your branch to implement/fix the issues I have been
>> working on. It won't really matter much, I think: in the end, we'll
>> have to use the "official" repository anyway and patch it.
>> 
>
> That would be highly preferred, simply for reviewing purposes.  I'm
> also happy to rewrite parts of my history to, for example, not include
> the -O--buildsystem stuff.  But the existing git history is useful, and
> I'd rather work from that.

OK, I've done it:

  

It's the same link, but the repository is a new one, based on the
official repository.

I tried to make my commits more granular, but there's a limit for that.
The first commit is the biggest one, but they should all be
self-explanatory (along with their commit messages).

The package builds successfully here, without any lintian warnings (I've
had to silence a bunch of them; I'll contact the lintian maintainers
later to do a case-by-case analysis).  I have also renamed some stuff,
like the conf/*.h files, and deleted others.

Comments are welcome, of course.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Bug#793761: chromium: freezes at startup in xfce4

[Michael Gilbert]

On Mon, Aug 24, 2015 at 3:29 AM, Arturo Borrero Gonzalez wrote:
>  $ chromium
> [15556:15556:0824/092809:ERROR:master_preferences.cc(99)] Failed to
> read preferences from /usr/share/chromium

What are the permissions on /usr/share/chromium/master_preferences?

Best wishes,
Mike

Bug#728691: Version is now 1.3.8 and filed new RFS

[Jeroen van Aart]

Please note the version now has bumped to 1.3.8 and I filed a new RFS, 
the last one was closed. The RFS is 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796828 which block 
this bug .

Bug#796856: browser-plugin-freshplayer-pepperflash: Version 0.3.2 availible

[Achim Schaefer]

Package: browser-plugin-freshplayer-pepperflash
Version: 0.3.1-2+b1
Severity: normal
Tags: upstream

Dear Maintainer,

the version 0.3.2 was released upstream.

Thanks


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

Kernel: Linux 4.1.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)

Versions of packages browser-plugin-freshplayer-pepperflash depends on:
ii  libasound21.0.29-1
ii  libatk1.0-0   2.16.0-2
ii  libavcodec-ffmpeg56   7:2.7.2-1
ii  libavutil-ffmpeg547:2.7.2-1
ii  libc6 2.19-19
ii  libcairo2 1.14.2-2
ii  libconfig91.5-0.2
ii  libevent-2.0-52.0.21-stable-2
ii  libevent-pthreads-2.0-5   2.0.21-stable-2
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-4
ii  libgdk-pixbuf2.0-02.31.5-1
ii  libgl1-mesa-glx [libgl1]  10.6.4-1
ii  libgles2-mesa [libgles2]  10.6.4-1
ii  libglib2.0-0  2.45.1-2
ii  libgtk2.0-0   2.24.28-1
ii  libpango-1.0-01.36.8-3
ii  libpangocairo-1.0-0   1.36.8-3
ii  libpangoft2-1.0-0 1.36.8-3
ii  libpulse0 6.0-5
ii  libssl1.0.0   1.0.2d-1
ii  libv4l-0  1.6.3-1
ii  libva-x11-1   1.6.0-1
ii  libva11.6.0-1
ii  libvdpau1 1.1-1
ii  libx11-6  2:1.6.3-1
ii  libxcursor1   1:1.1.14-1+b1
ii  libxrandr22:1.5.0-1
ii  libxrender1   1:0.9.8-1+b1

Versions of packages browser-plugin-freshplayer-pepperflash recommends:
ii  pepperflashplugin-nonfree  1.8.1+b1

browser-plugin-freshplayer-pepperflash suggests no packages.

-- no debconf information

Bug#786216: python-poster: diff for NMU version 0.8.1-0.2

[Andrey Rahmatullin]

Control: tags 786216 + patch
Control: tags 786216 + pending

Dear maintainer,

I've prepared an NMU for python-poster (versioned as 0.8.1-0.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
WBR, wRAR
diff -u python-poster-0.8.1/debian/control python-poster-0.8.1/debian/control
--- python-poster-0.8.1/debian/control
+++ python-poster-0.8.1/debian/control
@@ -4,8 +4,8 @@
 Maintainer: Robert Collins 
 Build-Depends: debhelper (>= 7.0.50~), cdbs (>= 0.4.49),
  python-all (>= 2.3.5-11),
+ dh-python,
  python-setuptools
-Build-Depends-Indep: python-support (>= 0.5.3)
 Standards-Version: 3.9.1.0
 Homepage: http://atlee.ca/software/poster/
 Vcs-Bzr: lp:debian/sid/python-poster/packaging
diff -u python-poster-0.8.1/debian/changelog python-poster-0.8.1/debian/changelog
--- python-poster-0.8.1/debian/changelog
+++ python-poster-0.8.1/debian/changelog
@@ -1,3 +1,11 @@
+python-poster (0.8.1-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Port from python-support to dh-python (Closes: #786216)
+  * Drop obsolete debian/{pycompat,pyversions}
+
+ -- Andrey Rahmatullin   Tue, 25 Aug 2015 00:17:36 +0500
+
 python-poster (0.8.1-0.1) unstable; urgency=low
 
   * Non-maintainer upload.
reverted:
--- python-poster-0.8.1/debian/pycompat
+++ python-poster-0.8.1.orig/debian/pycompat
@@ -1 +0,0 @@
-2
diff -u python-poster-0.8.1/debian/rules python-poster-0.8.1/debian/rules
--- python-poster-0.8.1/debian/rules
+++ python-poster-0.8.1/debian/rules
@@ -1,6 +1,5 @@
 #!/usr/bin/make -f
 
-DEB_PYTHON_SYSTEM=pysupport
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/python-distutils.mk
 include /usr/share/cdbs/1/rules/simple-patchsys.mk
reverted:
--- python-poster-0.8.1/debian/pyversions
+++ python-poster-0.8.1.orig/debian/pyversions
@@ -1 +0,0 @@
-2.4-


signature.asc
Description: Digital signature

Bug#793876: RFS: chrony/1.31.1-1

[Vincent Blut]

Le mar. 25 août 2015 à 0:33, Jerome BENOIT  a 
écrit :

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi:

On 24/08/15 23:52, Vincent Blut wrote:
 After inspecting Jerome’s custom init script, it appreared it was 
buggy.


To my defence: 1] the buggy part was commented as obsoleted, 2] it 
contains more material,

in particular support for /etc/network/if-*.d


You're right, my sentence sounds like the whole init script was buggy, 
but that isn't the case.
The context was about the supposedly "breakage" of the "-u" option 
expressed in 55d503b7.7050...@rezozer.net


Sorry, if that offended you!

 However I’ll have to find a way not to mess with users who set 
the default
 chronyd user in the init script instead of using the "user" 
directive in
 /etc/chrony/chrony.conf. To be honest I don’t see an easy way of 
doing it,
 so a first good step will probably be to add a "warning" in a NEWS 
file.


Note that regular users are not supposed to modify their 
/etc/init.d/chrony but
they are supposed to configure properly their  
/etc/chrony/chrony.conf .


Sure, but it'd be great to mitigate upgrade issues for those that did 
so.


I modify my /etc/init.d/chrony mainly to get /etc/network/if-*.d 
support.

BTW, is PPP stuff still needed ?


Yes, there are still Dial-up only internet accesses here and there, but 
its

usage dropped significantly in favor of broadband Internet access.


In short, you may rather focus on #312092 and #633422

hth,
Jerome


Cheers,
Vincent

Bug#570267: libcdk5: new upstream release

[Jose G. López]

On Wed, 12 Aug 2015 16:29:14 -0300
Herbert Parentes Fortes Neto (hpfn)  wrote:

> On Thu, 6 Aug 2015 10:51:50 -0300 Herbert Parentes Fortes Neto (hpfn) 
>  wrote:
> > Hi Jose,
> > 
> > On Sun, 20 Oct 2013 22:38:22 +0200 "Jose G. =?UTF-8?B?TMOzcGV6?=" 
> >  wrote:
> > > Hello,
> > > 
> > > I have packaged the new upstream release. Some time ago I tried to adopt 
> > > this package but I couldn't find a sponsor. I didn't want to waste all 
> > > the work done, so here it is:
> > > 
> > > http://mentors.debian.net/package/libcdk5
> > > 
> > > And the development is done at: https://gitorious.org/deb-pkg/libcdk5
> > > 
> > > Regards
> > 
> > How things are going on ?
> > 
> > I saw here[0] you did the package of the last version in Jan 2015 but
> > there is nothing on PTS[1].
> > 
> > My interest is because gphoto2 depends on libcdk5.
> > 
> > [0] - https://gitlab.com/deb-pkg/libcdk5/blob/master/debian/changelog
> > [1] - https://packages.qa.debian.org/libc/libcdk5.html
> > 
> 
> Ok, I will redo the task.
> 

Hi Herbert!,

Sorry for this late reply, I've been away from home on holidays. 
Feel free to take the package over as I have lost interest in
maintaining it.

Regards,


pgpHhK4_Paisi.pgp
Description: PGP signature

Bug#786017: Patch for 786017

[Alexandre Viau]

Control: tags 786017 + patch

Hello,

I have ported this package to dh_python2.

See the patch attached.

Thanks,

-- 
Alexandre Viau
alexan...@alexandreviau.net
diff -Nru python-mailer-0.7/debian/control python-mailer-0.7/debian/control
--- python-mailer-0.7/debian/control	2011-08-07 16:33:42.0 -0400
+++ python-mailer-0.7/debian/control	2015-08-24 19:27:53.0 -0400
@@ -2,7 +2,7 @@
 Section: python
 Priority: extra
 Maintainer: David Watson 
-Build-Depends: debhelper (>= 7), python, python-support, python-setuptools
+Build-Depends: debhelper (>= 7), python, dh-python, python-setuptools
 Standards-Version: 3.9.2
 Homepage: http://pypi.python.org/pypi/mailer
 
diff -Nru python-mailer-0.7/debian/rules python-mailer-0.7/debian/rules
--- python-mailer-0.7/debian/rules	2010-07-07 06:21:01.0 -0400
+++ python-mailer-0.7/debian/rules	2015-08-24 19:27:53.0 -0400
@@ -1,4 +1,4 @@
 #!/usr/bin/make -f
 
 %:
-	dh  $@
+	dh  $@ --with python2


signature.asc
Description: OpenPGP digital signature

Bug#796855: gcc-5: guile-2.0 fails to build with offset problem on armel

[Rob Browning]

Feel free to downgrade this if you think appropriate, but given that 4.8
is scheduled to be removed from stretch at some point, this will
eventually become grave for guile-2.0.  (The problem appears to affect
gcc-4.9 as well.)

For reference, it looks like a similar problem on armhf may have been fixed:

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

For reference, I'm running a build on harris.debian.org (armhf) which
has already made it past the invocation that failed.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#785874: Pending

[Lisandro Damián Nicanor Pérez Meyer]

tag 785874 pending
thanks

Hi! We are going to fix this first in experimental and (most probably) push Qt 
5.5.x to unstable once the gcc5 transition ends and we are greenlighted by the 
RT.

-- 

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#796758: [pkg-wine-party] Bug#796758: Bug#796758: Bug#796758: Update dependency on wine-gecko to 2.40.

[Michael Gilbert]

On Mon, Aug 24, 2015 at 4:55 PM, Jens Reyer wrote:
> Alternatively I can add a changelog entry for UNRELEASED if you prefer,
> just tell me your preferences.

Either way works.

Best wishes,
Mike

Bug#786014: Wrong patch

[Alexandre Viau]

Hello,

I had attached the NMU diff to the last mail instead of just the patch.

This one contains just the patch, without debian/changelog.

Thanks,

--
Alexandre Viau
alexan...@alexandreviau.net
diff -u python-ipcalc-0.3/debian/rules python-ipcalc-0.3/debian/rules
--- python-ipcalc-0.3/debian/rules
+++ python-ipcalc-0.3/debian/rules
@@ -3 +3 @@
-   dh $@
+   dh $@ --with python2
diff -u python-ipcalc-0.3/debian/control python-ipcalc-0.3/debian/control
--- python-ipcalc-0.3/debian/control
+++ python-ipcalc-0.3/debian/control
@@ -2,10 +2,9 @@
 Section: python
 Priority: optional
 Maintainer: MEZGANI Ali 
-Build-Depends: debhelper (>= 7), python-support, python-dev 
+Build-Depends: debhelper (>= 7), dh-python, python-dev
 Standards-Version: 3.8.2 
 Homepage: http://dev.tehmaze.com/projects/ipcalc
-XB-Python-Version: ${python:Versions}
 
 Package: python-ipcalc
 Architecture: all


signature.asc
Description: OpenPGP digital signature

Bug#578937: Problem still exists with courier 0.65.0-2

[Nick Guerette]

This seems to indicate that either libfam0 or courier-imap should have a 
dependency on fam, but does not.  This has been an issue for a long time 
now, and seems quite simple.


Nick Guerette
Embedded Systems Engineer
Mosaic Industries, Inc.
510-790-8222
http://mosaic-industries.com/embedded-systems

Bug#796854: openbabel: transition needed for g++-5 ABIs

[Simon McVittie]

Source: openbabel
Version: 2.3.2+dfsg-2.1
Severity: serious
Justification: breaks reverse-dependencies
Tags: patch

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of openbabel, std::string appears in header files that
get installed, so it seems very likely that a transition is needed.
The transition consists of renaming the library package
containing libopenbabel.so.4 from "libopenbabel4" to "libopenbabel4v5".
A patch is available in Ubuntu,
.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the libraries on which openbabel depends
have started their transitions if required, openbabel should do the same,
closing this bug; the release team will deal with binNMUs as needed.

In the case of openbabel, libwxgtk3.0-dev has already started its
transition, and libeigen3-dev appears to be unaffected, so openbabel
is ready for its rename now.

The package might be NMU'd in the near future, with a patch very similar
to the one in Ubuntu, if its maintainers do not respond; the release
team have declared a 2 day NMU delay[2] for packages involved in the
libstdc++ transition, in order to get unstable back to a usable state
in a finite time.

S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html

Bug#796179: tesseract-ocr: tesseract fails to generate output

[Jeff Breidenbach]

I'd like to think if this were widespread, I'd be hearing about it
from multiple sources. So any sort of confirmation (or refutation)
from others is appreciated.

Bug#705225: python-passlib: bcrypt not usable from python-passlib -- missing backend

[Brian May]

On Thu, Apr 11, 2013 at 04:39:12PM +0200, Marios Makassikis wrote:
> The report in [2] suggests python-passlib as an alternative. Upon installing
> it, I attempted to use bcrypt(), only to find out it relies on py-bcrypt 
> (which 
> is the module formerly packaged as python-bcrypt) or bcryptor [3]. None of
> these modules are available in Debian repositories, leading me to the
> conclusion that bcrypt is currently unusable in python on Debian (other than
> installing the module from PyPI or building a custom .deb).

This report confused me at first. python-bcrypt and python3-bcrypt are
available in Debian.

It is based on py-bcrypt however, which passlib says has a security
issue.

I just opened #796853 for this security issue.

Bug#786014: Patch for 786014

[Alexandre Viau]

Control: tags 786014 + patch

Hello,

I have ported this package to dh_python2.

See the patch attached.

I will prepare an NMU.

Thanks,

-- 
Alexandre Viau
alexan...@alexandreviau.net
diff -u python-ipcalc-0.3/debian/rules python-ipcalc-0.3/debian/rules
--- python-ipcalc-0.3/debian/rules
+++ python-ipcalc-0.3/debian/rules
@@ -3 +3 @@
-   dh $@
+   dh $@ --with python2
diff -u python-ipcalc-0.3/debian/control python-ipcalc-0.3/debian/control
--- python-ipcalc-0.3/debian/control
+++ python-ipcalc-0.3/debian/control
@@ -2,10 +2,9 @@
 Section: python
 Priority: optional
 Maintainer: MEZGANI Ali 
-Build-Depends: debhelper (>= 7), python-support, python-dev 
+Build-Depends: debhelper (>= 7), dh-python, python-dev
 Standards-Version: 3.8.2 
 Homepage: http://dev.tehmaze.com/projects/ipcalc
-XB-Python-Version: ${python:Versions}
 
 Package: python-ipcalc
 Architecture: all
diff -u python-ipcalc-0.3/debian/changelog python-ipcalc-0.3/debian/changelog
--- python-ipcalc-0.3/debian/changelog
+++ python-ipcalc-0.3/debian/changelog
@@ -1,3 +1,10 @@
+python-ipcalc (0.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Port from python-support to dh_python2 (Closes: #786014)
+
+ -- Alexandre Viau   Mon, 24 Aug 2015 18:54:58 
-0400
+
 python-ipcalc (0.3-1) unstable; urgency=low
 
   * Initial release (Closes: #533437) 


signature.asc
Description: OpenPGP digital signature

Bug#796853: python-bcrypt: passlib says this library is broken

[Brian May]

Package: python-bcrypt
Version: 0.4-2+b1
Severity: grave
Tags: security
Justification: renders package unusable

According to https://pythonhosted.org/passlib/history.html:

"It will now issue a PasslibSecurityWarning if the active backend is
vulnerable to the wraparound bug, and automatically enable a workaround
(py-bcrypt is known to be vulnerable as of v0.4)."

After running the tests, you get the following passlib warning:

/«PKGBUILDDIR»/passlib/handlers/bcrypt.py:320: UserWarning:
passlib.hash.bcrypt: Your installation of the 'pybcrypt' backend is
vulnerable to the bsd wraparound bug, and should be upgraded or replaced
with another backend (this warning will be fatal under passlib 1.7)
  "(this warning will be fatal under passlib 1.7)" % backend)

python-bcrypt is py-bcrypt 0.4
https://pypi.python.org/pypi/py-bcrypt/0.4

The recommended library to use is bcrypt:
https://pypi.python.org/pypi/bcrypt

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

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

Versions of packages python-bcrypt depends on:
ii  libc6   2.19-18
ii  python  2.7.9-1

python-bcrypt recommends no packages.

python-bcrypt suggests no packages.

-- no debconf information

Bug#796591: debian-installer: beep on x86 UEFI for accessibility

[Samuel Thibault]

Ben Hutchings, le Sun 23 Aug 2015 09:50:40 +0200, a écrit :
> On Sun, 2015-08-23 at 00:44 +0200, Samuel Thibault wrote:
> > Ben Hutchings, le Sun 23 Aug 2015 00:39:20 +0200, a écrit :
> > > On Sat, 2015-08-22 at 22:30 +0200, Samuel Thibault wrote:
> > > > As raised during the accessibility talk, we need to emit a beep at boot
> > > > menu in the UEFI case too (grub menu).
> > > > 
> > > > I don't really know how to test this (can qemu emulate it?), so for
> > > > now I'm just attaching a patch which should be working, but which is
> > > > not tested.  Also, we probably need to make it conditionalized under
> > > > official uploads like was done for the syslinux prompt.
> > > 
> > > Sound works in the SDL interface or over SPICE (-spice option).
> > 
> > I know, but the question is about emulating *UEFI* on qemu.
> 
> Ah!  Then you need the ovmf package.

Thanks!

It does work fine with UEFI.

Samuel

Bug#791016: ctpp2: ftbfs, and library transition is needed when GCC 5 is the default

[Simon McVittie]

On Sat, 22 Aug 2015 at 14:32:59 +0530, Vasudev Kamath wrote:
> I've updated the package droping libjs-jquery related modification. I've
> pushed the changes to collab.

Thanks, I've sponsored that upload for you. It should go into the NEW
queue shortly.

> PS: I've not added lintian override, I think its not needed as issue is
> already known. Let me know if otherwise.

I think what you've done is fine.

S

Bug#796852: apport: test

[Yuru Shao]

Package: apport
Version: 2.17.3-1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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

bug

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

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

Versions of packages apport depends on:
ii  gir1.2-glib-2.0  1.42.0-2.2
ii  lsb-base 4.1+Debian13+nmu1
ii  python3  3.4.2-2
ii  python3-apport   2.17.3-1
ii  python3-gi   3.14.0-1
pn  python:any   

Versions of packages apport recommends:
ii  policykit-1  0.105-8

Versions of packages apport suggests:
ii  apport-gtk  2.17.3-1

-- no debconf information

Bug#796851: request-tracker4: show Debian revision in web interface

[Dominic Hargreaves]

Package: request-tracker4
Version: 4.2.11-3
Severity: wishlist

It would be nice to show the Debian revision in the web interface, as
a quick sanity check about whether an upgrade has happened, for example.

Dominic.

Bug#793876: RFS: chrony/1.31.1-1

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi:

On 24/08/15 23:52, Vincent Blut wrote:
> After inspecting Jerome’s custom init script, it appreared it was buggy.

To my defence: 1] the buggy part was commented as obsoleted, 2] it contains 
more material,
in particular support for /etc/network/if-*.d


> However I’ll have to find a way not to mess with users who set the default
> chronyd user in the init script instead of using the "user" directive in
> /etc/chrony/chrony.conf. To be honest I don’t see an easy way of doing it,
> so a first good step will probably be to add a "warning" in a NEWS file.

Note that regular users are not supposed to modify their /etc/init.d/chrony but
they are supposed to configure properly their  /etc/chrony/chrony.conf .

I modify my /etc/init.d/chrony mainly to get /etc/network/if-*.d support.
BTW, is PPP stuff still needed ?

In short, you may rather focus on #312092 and #633422

hth,
Jerome



-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJV25urAAoJEIC/w4IMSybjGwMH/1mbGWS/iBvOfJBUG7od8wW9
ff22VEsvY8GoRw0qNXpVbI+FNRn2uroOS/Q1m8MWzNflnVjUnZ84DUsnsupfLFuV
wUdDyU5/vVaK4KrouigPdGVHc7LTs4thmqlSP+FL/eSyvQIu4+XNB6BUDGtXKOOZ
Ec5/Vep8MMzv/Cx9rr6oUPfx8pVk0RfmHnlWtH5q07PZNAOu3UyLeEPYVVIqY2VI
ntYvEmlrw7aB05gDNFHKJmDYcI8mj6ZboJ18fzx5sdG6E4mLoRM/xr0LvlC/zxbJ
XR/Q0tw2IzxjKrRMWiq+QvKkK/kPDoXhY+ZhVpAOyNq8MODXkpyY3Acqb4NHx2Q=
=mRUF
-END PGP SIGNATURE-

Bug#793886: Bug#791917: dbus: Missing dependency on mountpoint from util-linux package

[Simon McVittie]

Control: reassign 791917 initscripts
Control: found 791917 2.88dsf-59.1
Control: fixed 791917 2.88dsf-59.2

On Sun, 02 Aug 2015 at 00:41:23 +0100, Simon McVittie wrote:
> This means you had this as the broken situation:
> 
> initscripts 2.88dsf-59.1
> sysvinit-utils 2.88dsf-59
> util-linux 2.25.2-6
> 
> initscripts 2.88dsf-59.2 has a Breaks on util-linux (<< 2.26.2-4~), and
> has now replaced 2.88dsf-59.1 in testing, so this shouldn't happen again.
> 
> > Can we get the depends/breaks between them so that you can't install a
> > combination that doesn't work?
> 
> My understanding is that this was a bug in initscripts 2.88dsf-59.1 and
> was fixed in 2.88dsf-59.2: namely, it dropped mountpoint from the
> Essential set, but did not ensure that a sufficiently new util-linux to
> provide mountpoint was installed. Now that initscripts 2.88dsf-59.1 is
> no longer available in any suite, upgrades from stable shouldn't run
> into this.

In the absence of any feedback to the contrary, I'm going to consider this
to be a bug in initscripts, which was present in 2.88dsf-59.1
but fixed in 2.88dsf-59.2. Without a time machine to go back and
fix this before it happened, I don't think we can fix these partial
upgrades.

There doesn't seem to be much I can or should do about this in dbus;
partly because it affects other packages, not just dbus (e.g. uswsusp,
#793886), and partly because if people are doing partial upgrades that
pick up the latest initscripts without the latest util-linux,
there doesn't seem to be anything to guarantee that they'll
upgrade to the latest dbus either.

S

Bug#796850: ITP: asl -- multiphysics simulation software

[Ghislain Antony Vaillant]

Package: wnpp
Severity: wishlist
Owner: Ghislain Antony Vaillant 

* Package name: asl
  Version : 0.1.6
  Upstream Author : Avtech Scientific 
* URL : http://asl.org.il/
* License : AGPL-3
  Programming Lang: C++
  Description : multiphysics simulation software

Long-Description:
 The Advanced Simulation Library (ASL) is a free and open source multiphysics
 simulation software package.
 .
 Its computational engine is based, among others, on the Lattice Boltzmann
 Methods and is written in OpenCL which enable extraordinarily efficient
 deployment on a variety of massively parallel architectures, ranging from
 inexpensive FPGAs, DSPs and GPUs up to heterogeneous clusters and
 supercomputers. The engine is hidden entirely behind C++ classes, so that no
 OpenCL knowledge is required from application programmers.
 .
 ASL can be utilized to model various coupled physical and chemical phenomena
 and employed in a multitude of fields: computational fluid dynamics, virtual
 sensing, industrial process data validation and reconciliation, image-guided
 surgery, computer-aided engineering, high-performance scientific computing,
 etc...

This package will be co-maintained by the Debian Science Team.

Bug#796848: debianutils: Missing dependency on awk

[Croxell, Jeffrey]

Package: debianutils
Version: 4.4+b1
Severity: important
Tags: d-i

Dear Maintainer,


   * What led up to the situation?
   Using cdebootstrap-static with a limited local mirror.
   The local mirror included 'gawk'.
   It appeared to be a race condition - gawk installed after debianutils.
   Adding 'mawk' allows debianutils to install successfully
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Added mawk to local mirror.
   * What was the outcome of this action?
   Mawk by chance gets installed first
   * What outcome did you expect instead?
   Since debianutils 'add-shell' uses 'awk' it should have an explicit
   dependency on awk


-- System Information:
Debian Release: 8.0
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-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: sysvinit (via /sbin/init)

Versions of packages debianutils depends on:
ii  libc6   2.19-13
ii  sensible-utils  0.0.9

debianutils recommends no packages.

debianutils suggests no packages.

-- no debconf information


Jeff Croxell
Senior Software Developer
Camber Corporation
Office: 618-624-7833
Cell: 618-606-5069



The information contained in this email message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient and have received this
communication in error, please contact the sender by reply e-mail and destroy 
all
copies of the original message.

Bug#796849: qbittorrent: FTBFS: has_binary_operator.hp:50: Parse error at "BOOST_JOIN"

[Chris Lamb]

Source: qbittorrent
Version: 3.1.11-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

qbittorrent fails to build from source in unstable/amd64:

  [..]
  g++ -c -m64 -pipe -Wformat -Wformat-security -g -O2
  -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
  -D_FORTIFY_SOURCE=2 -O2 -D_REENTRANT -Wall -W -DDISABLE_GUI
  -DQT_NO_DEBUG_OUTPUT -DVERSION=\"v3.1.11\" -DVERSION_MAJOR=3
  -DVERSION_MINOR=1 -DVERSION_BUGFIX=11 -DQT_NO_CAST_TO_ASCII
  -DQT_USE_FAST_CONCATENATION -DQT_USE_FAST_OPERATOR_PLUS
  -DBOOST_FILESYSTEM_VERSION=2 -DTORRENT_USE_OPENSSL
  -DBOOST_ASIO_HASH_MAP_BUCKETS=1021 -DBOOST_EXCEPTION_DISABLE
  -DBOOST_ASIO_ENABLE_CANCELIO -DBOOST_ASIO_DYN_LINK
  -DTORRENT_LINKING_SHARED -DQT_NO_DEBUG -DQT_NETWORK_LIB -DQT_CORE_LIB
  -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I../../src
  -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork
  -I/usr/include/qt4 -I/usr/include/libtorrent -I/usr/include
  -I../../src -I../../src/qtsingleapp -I../../src/qtlibtorrent
  -I../../src/webui -I../../src/webui/qjson -I../../src/tracker
  -I../../src/preferences -I. -I../../src -I. -o dnsupdater.o
  ../../src/dnsupdater.cpp
  usr/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse
  error at "BOOST_JOIN"
  Makefile:817: recipe for target 'main.moc' failed
  make[3]: *** [main.moc] Error 1
  make[3]: *** Waiting for unfinished jobs
  ../../src/qtlibtorrent/qbtsession.cpp: In member function
  'QTorrentHandle QBtSession::addMagnetUri(QString, bool, bool, const
  QString&)':
  ../../src/qtlibtorrent/qbtsession.cpp:1030:71: warning:
  'libtorrent::torrent_handle
  libtorrent::add_magnet_uri(libtorrent::session&, const string&,
  libtorrent::add_torrent_params)' is deprecated
  [-Wdeprecated-declarations]
   h =  QTorrentHandle(add_magnet_uri(*s, magnet_uri.toStdString(),
   p));
 ^
  In file included from ../../src/torrentpersistentdata.h:38:0,
   from ../../src/qtlibtorrent/qbtsession.cpp:53:
  /usr/include/libtorrent/magnet_uri.hpp:62:32: note: declared here
torrent_handle TORRENT_EXPORT add_magnet_uri(session& ses,
std::string const& uri
  ^
  ../../src/qtlibtorrent/qbtsession.cpp: In member function 'void
  QBtSession::readAlerts()':
  ../../src/qtlibtorrent/qbtsession.cpp:2357:18: warning: unused
  variable 'will_shutdown' [-Wunused-variable]
   bool will_shutdown = false;
^
  make[3]: Leaving directory
  '/tmp/buildd/qbittorrent-3.1.11/build-nox/src'
  Makefile:39: recipe for target 'sub-src-make_default' failed
  make[2]: *** [sub-src-make_default] Error 2
  make[2]: Leaving directory '/tmp/buildd/qbittorrent-3.1.11/build-nox'
  dh_auto_build: make -j23 returned exit code 2
  debian/rules:17: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 25
  make[1]: Leaving directory '/tmp/buildd/qbittorrent-3.1.11'
  debian/rules:8: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/qbittorrent_3.1.11-1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Mon Aug 24 07:26:43 GMT+12 2015
I: pbuilder-time-stamp: 144003
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 7.4.12), dpkg-dev (>= 1.16.1), libtorrent-rasterbar-dev 
(>= 0.15.4), libboost-dev, libqt4-dev (>= 4.6.0)
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20247 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepend

Bug#794222: Missing patch

[Tulio Magno Quites Machado Filho]

"Carlos O'Donell"  writes:

> On Mon, Aug 17, 2015 at 4:34 PM, Aurelien Jarno  wrote:
>>> So this is IMO, the wrong thing to do. You should push the patch into
>>> upstream 2.19 stable and rebase instead of keeping the patch in debian
>>> svn. Given the patch is already in upstream master it is OK to commit
>>> to 2.19 stable, and post to libc-stable stating you checked in this
>>> fix. That way debian gets broader testing of the patches we are using
>>> instead of the narrower "just debian" users.
>>
>> If it is fine to push this kind of patch in this branch, I would
>> certainly do that. I also backported for debian patch b0a3c164. Would
>> it be possible to also push it to the branch?
>
> If the patch doesn't change API/ABI, and it was accepted for master,
> then it's perfectly acceptable to push to 2.19 stable branch.

Patch pushed to release/2.19.master as commit 980a63b3.

-- 
Tulio Magno

Bug#793331: RFS: postsrsd/1.2-1 [ITP]

[Oxan van Leeuwen]

Hi Thomas,

On 24-08-15 14:10, Tomasz Buchert wrote:

Nicely done, but there is one issue. If you modify conffiles in postinst
it marks them as changed, and this is not something you want to do.

In my branch "tomasz-changes" I followed ADVANCED PROGRAMMING WITH
DEBCONF section in "man debconf-devel". The outcome is that the config
file is not tracked by conffiles machinery and hence the problem does
not exist. Please review.


Yeah, that's definitely true. Your branch looks good to me. It's 
probably a bit cleaner to wrap the config-writing machinery in the 
postinst in an if [ "$1" = "configure" ], but I don't think it hurts to 
execute it for the other postinst invocations as well.


Other than that, I don't think there are any remaining issues preventing 
upload?


Cheers,
Oxan

Bug#796846: jessie-pu: package akonadi/1.13.0-2

[Lisandro Damián Nicanor Pérez Meyer]

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

Hi RT!

The akonadi package in stable suffers from a bug that makes it leaks
files thus filling the hard drive with useless data.

The patch that I'm attaching has been in testing for more than a month already
and several people in our mailing lists (including myself in two machines) have
tested that it works.

So I would appreciate if this patch could be considered for the next stable
update.

Thanks in advance, Lisandro.

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

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)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#796845: Uses gcc-4.8 on s390x and m68k

[Moritz Muehlenhoff]

Source: linux
Severity: important

On s390x and m68k, gcc-4.8 is used which will not be released with
stretch (#765380), so the severity of this bug will be bumped when we
get closer to the release (m68k isn't RC of course).

On a related note, ia64 used gcc-4.6, which was removed from the
archive a few days ago. Since ia64 has been dropped entirely and
no porters are left in Debian, maybe simply drop it from the
architectures list of src:linux?

Cheers,
Moritz

Bug#796836: libglib2.0-0-refdbg: Please change section to misc

[Niels Thykier]

On 2015-08-24 23:48, Michael Biebl wrote:
> Hi Niels,
> 
> [...]
> 
> Shouldn't this bug be filed against ftp-master then, since sections
> can't be changed via debian/control, which you certainly know?
> 
> 
> Michael
> 

Normally yes.  However, in the given case, DAK actually uses the raw
field from the package rather than its own overrides.  At least in the
current patch set.

See also: https://lists.debian.org/debian-devel/2015/08/msg00443.html

Thanks,
~Niels





signature.asc
Description: OpenPGP digital signature

Bug#793876: RFS: chrony/1.31.1-1

[Vincent Blut]

Le ven. 21 août 2015 à 9:21, Paul Gevers  a écrit 
:

Hi Vincent,


Hey Paul,


[I am merging the e-mails you send yesterday to make the thread easier
again.]

On 20-08-15 18:12, Vincent Blut wrote:
 Le jeu. 20 août 2015 à 12:10, Paul Gevers  a 
écrit :

 Your priority switch from extra to optional may require a ping to
 somebody. I am not sure and I would need to search, so please do 
that

 yourself.


 Yes. I’ll have to send a bug report to the ftp.debian.org 
pseudo-package
 asking for the modification of the section/priority in the 
"override-file".

 Will do later today… or tomorrow.


Ack.


Bug report sent¹.


 Which file do you have in common with ntp? Please re-read ¹.


 I guess I’ve been misled by § 7.6.2! The previous section shows 
the
 usage of the 'replaces:' field for packages providing *files* 
already

 provided by another package. However, the section 7.6.2 seems to be
 for *packages* that /do conflict/; I interpreted that /do conflict/
 by "packages providing the same functionality". I even was quite 
sure

 my interpretation was correct after seeing the usage example about
 MTAs.


I didn't check if ntp is also doing the conflicts/replaces/provides
dance on time-deamon. If so I than you don't need to mention ntp
specifically at all¹¹.


It does not. There is still an opened bug report² about adding ntp to 
the time-daemon

virtual package, but the discussion has stalled since few years now.


 Anyway, depending on your answer, I’ll revert this commit.


Lets not do that until we agree. :)


Ok.


 Wouldn't the hwclockfile stuff in /etc not warrant an debian/NEWS
 update? Or at the very least some help in the changelog?


 I don’t think so. Finally, that change have no impact for the 
user.

 Previously we had to check (in the postinst script) if the RTC keeps
 local time or UTC by parsing /etc/adjtime and/or /etc/default/rcS.
 Depending on the result, we set (or no) the "rtconutc" directive in
 /etc/chrony.conf. But now chrony is grown enough to check that by
 itself. Each time it is started, it will parse the correspondent
 value in the /etc/adjtime file.

 So, as you can see, the whole point of using the hwclockfile
 directive is to have something cleaner than playing the text
 processing game for the same result.


 Doesn't this actually require a migration path? What if the
 /etc/chrony and /etc/adjtime are NOT answering the same?


 Well, I’m not sure I’m understanding you here. The chronyd 
daemon

 will use what /etc/adjtime returns, thanks to the 'hwclockfile
 /etc/adjtime' directive.


Oh, you not understanding me makes sense. It was me who didn't
understand what you were doing. I was assuming there now was a new
mechanism, but now you explained it is just a better implementation of
"the same thing". But then again, maybe make that a little clearer in
your changelog for others like me?


Ok, maybe adding something like:

“Basically, this directive makes the detection of the standard (Local 
or
UTC time) set in /etc/adjtime — and used by the hardware clock — 
clearer
compared to the text processing method we used to use in the post 
install

script to complete the same task.”

What do you think?


 Can you please explain me how commit 1ce86d3 works (the Breaks of
 util-linux).


 As the hwclockfile directive can only deal with /etc/adjtime, we 
need

 to ensure that we migrated from /etc/default/rcS to /etc/adjtime. To
 be honest, I’m not sure that break is even needed, because this
 migration happened prior to Wheezy.


I haven't looked it up, is util-linux in essential? Otherwise, 
shouldn't

you depend on it with the higher than dependency?


Indeed, util-linux is essential hence the fact it is not listed in the 
'Depends:' field.


 I assume you tested all migrations for admins that already ran 
chrony as

 a different users as described in the README.Debian. Are the manual
 steps even needed? Shouldn't this go into a NEWS file instead of 
the

 README file?


 I tested a lot of use cases, but Jerome Benoit informed me he had an
 issue possibly related to this change, but as he uses a custom init
 script etc., I will have to check his atypical configuration.


Ack.


After inspecting Jerome’s custom init script, it appreared it was 
buggy.
However I’ll have to find a way not to mess with users who set the 
default

chronyd user in the init script instead of using the "user" directive in
/etc/chrony/chrony.conf. To be honest I don’t see an easy way of 
doing it,

so a first good step will probably be to add a "warning" in a NEWS file.

 Line 36 of the README.Debian file ends weird now, you removed a 
filename

 but not the "and" in front.


 Indeed, will fix. You mean line 27 right?


I am talking about "The scripts /etc/ppp/ip-up.d/chrony,
/etc/ppp/ip-down.d/chrony, and read key 1 from /etc/chrony/chrony.keys
and use it as the password to send chronyc commands." In my version 
that

is on line 36.


My bad, I was checking the file with "nl" which doesn't count blank 
lines

Bug#735134: perl: rename(1) is ancient

[Dominic Hargreaves]

On Fri, Aug 21, 2015 at 06:54:01PM +0200, Axel Beckert wrote:
> Hi Dominic,
> 
> Dominic Hargreaves wrote:
> > Details of the use of (p)rename in your package follow:
> 
> JFYI: I feel that this search wasn't sufficient. I miss at least two
> packages co-maintained by myself and missing in that list: xymon and
> hobbit-plugins:
> 
> [...]
> > Anton Gladky 
> >vtk6 (U)
> > 
> > Bastian Blank 
> >lvm2 (U)
> [...]

Okay. I think I put too much faith in codesearch.debian.org giving me
complete results. I'll look again.

Cheers,
Dominic.

Bug#796836: libglib2.0-0-refdbg: Please change section to misc

[Simon McVittie]

On 24/08/15 22:48, Michael Biebl wrote:
> Shouldn't this bug be filed against ftp-master then, since sections
> can't be changed via debian/control, which you certainly know?

I said the same on #debian-devel, and actually the answer seems to be no:

< nthykier> smcv: Except their current patch uses the package value
  instead of the FTP master override

S

Bug#796844: Build-depends on gcc-4.8

[Moritz Muehlenhoff]

Source: starpu-contrib
Severity: serious

gcc 4.8 will not be shipped with stretch (765380) and starpu-contrib
currently Build-Depends on it (gcc-4.8, g++-4.8, gfortran-4.8,
gcc-4.8-plugin-dev)

Cheers,
Moritz

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

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

Bug#796836: libglib2.0-0-refdbg: Please change section to misc

[Michael Biebl]

Hi Niels,

Am 24.08.2015 um 23:24 schrieb Niels Thykier:
> Control: retitle -1  libglib2.0-0-refdbg: Please change section to devel
> 
> On 2015-08-24 23:16, Simon McVittie wrote:
>> On 24/08/15 22:04, Niels Thykier wrote:
>>> Please consider moving libglib2.0-0-refdbg to a different section.
>>
>> devel seems a little less inappropriate than misc, perhaps?
>>
>> Some other packages similar to libglib2.0-0-refdbg:
>>
>> * python2.7-dbg (and other versions) are the Python interpreter
>>   and standard library, rebuilt with debugging features
>> * dbus-1-dbg contains debug symbols, but also rebuilt versions
>>   of libdbus with extra tests/assertions/misc, and the regression
>>   tests that use them
>>
>> Regards,
>> S
>>
> 
> Seems reasonable to me. :)

Shouldn't this bug be filed against ftp-master then, since sections
can't be changed via debian/control, which you certainly know?


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



signature.asc
Description: OpenPGP digital signature

Bug#791721: Workaround possible (Was: [owncloud-devel] oC 8.1.x and sync client from debian%2

[Chris]

Hi,

On Mon, 10 Aug 2015 19:10:44 +0200 Simon Josefsson 
wrote:

> I assumed jessie had 1.7 but apparently there is a difference between
> the 1.7rc and final 1.7.

Jessie has 1.7.0~beta1+really1.6.4+dfsg-1 which seems to be 1.6.4

> If anyone can explain what the disadvantages (if any) will be with
> this setting, that would be useful.

Background infos seems to be available here:

https://github.com/owncloud/core/pull/15683

Bug#763541: pkg-perl-autopkgtest: environment variables for the smoke test

[gregor herrmann]

On Mon, 24 Aug 2015 21:18:05 +0300, Niko Tyni wrote:

> (I was about to file a bug about this, until I found I'd already
>  done so a year ago...)

Heh :)
 
> Also, people have expressed needs for HOME for at least libgtk3-perl and
> libextutils-modulemaker-perl. It's not clear to me how that should work
> wrt. absolute vs. relative paths: the tests are presumably run under
> /tmp in a directory that can't be hardcoded in an environment list.

Can't we build on ADTTMP here, i.e. create either a tmpdir or a dir
with a nice name like fakehomeforautopkgtest under
$ADTTMP and export HOME=$ADTTMP/whateverwetake?

I also guess that we need HOME only for the smoke tests, so this
could just be added to our smoke script.
OTOH, that defeats the idea of a generic env-smoke setup.
 
> Finally, my original concerns in this bug about executable configuration
> files still apply. I would appreciate input on this. See
>  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763541#5

I'm also a bit weary about running a random pre-smoke script; your
comment

| Or we could implement 'env-smoke' now and leave 'pre-smoke' for
| later, which I guess is the normal Debian way of not deciding
| anything :)

sounds good to me.


Cheers,
gregor

-- 
 .''`.  Homepage: http://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: Page&Plant: Shining In The Light


signature.asc
Description: Digital Signature

Bug#796819: [pkg-wine-party] Bug#796819: WoW stops working with version 1.7.50-1

[Jens Reyer]

control: tag -1 upstream

On 08/24/2015 09:34 PM, Klaus Ethgen wrote:
> With the new version, WoW stops working. When trying to start it, only a
> Memory access violation will occur.

I assume WoW = "World of Warcraft".

Please file a bug at bugs.winehq.org and link back here by sending a
mail to cont...@bugs.debian.org with content:
  forwarded 796819 https://bugs.winehq.org/show_bug.cgi?id=X

Even better if you can git bisect to the commit reintroducing the problem.

Greets
jre

Bug#726768: libmodplug-dev: pkg-config file removed -I${includedir}/libmodplug which causes problems

[Stephen Kitt]

Control: tag -1 + wontfix

Hi Manuel,

I'm adopting libmodplug (at Zed's request).

On Fri, Oct 18, 2013 at 11:11:43PM +0100, Manuel A. Fernandez Montecelo wrote:
> Anyway, please let me know if the decision to keep it like it is is
> final or not, SDL_mixer is quite popular with hundreds of rdepends,
> although at the moment only affects the recently introduced SDL2
> version (the previous one used mikmod, not modplug).  Nevertheless, I
> don't want to keep it FTBFSing for long or introduce temporary fixes
> that cause unintended consequences.

Given how much time has passed now, this decision is final; all
downstreams have adapted...

Regards,

Stephen


signature.asc
Description: Digital signature

Bug#793987: xul-ext-torbirdy: Torbirdy options not visible in Icedove 31.7.0

[intrigeri]

Hi,

[fully quoting because I'm adding the privacy team to recipients.]

Jacob Appelbaum wrote (24 Aug 2015 20:33:02 GMT) :
> On 8/24/15, intrigeri  wrote:
>> Hi Ben, hi Jacob,
>>
>> Ben Bailess wrote (29 Jul 2015 15:55:12 GMT) :
>>> I recently installed Torbirdy using the pkg xul-ext-torbirdy in order to
>>> have
>>> connection to system tor by default. When I open icedove, I do not see the
>>>
>>> typical green text at the bottom of the status bar stating "Torbirdy
>>> Enabled:
>>> Tor"... so I purged the pkg and reinstalled, with no change.
>>
>> Thanks for this bug report. It seems that Icedove 31.7 landed in
>> stable and testing ~3 months ago, so I'm kinda surprised that nobody
>> else reported this problem to Debian. popcon is low, but still.
>>

> I'm also surprised - I totally missed this bug though, so I'm not too 
> surprised.

>> Jake: are you aware of this problem? Is it fixed upstream in 0.1.4?

> I think it is indeed fixed in 0.1.4 and it seems that Ben has confirmed it.

>> Do you have time to take care of it? Or should we look into other
>> options (e.g. pkg-moz-ext, as suggested a while ago, and/or the new
>> pkg-privacy team)?
>>

> I don't have time in the next week or two - no.

@Privacy team: can anyone give a hand?

>> Also, note that torbirdy is scheduled to be removed from testing in
>> a few days, due to this bug.

> Oh dear - I had missed that entirely.

>>
>>> I then purged the pkg again and installed from Icedove add-ons, and
>>> it worked as intended, [...]
>>
>> Ben: what exact version of Torbirdy did you install this way?

> I think based on timing it had to be 0.1.4 if it was installed from
> addons.mozilla.org.

>>
>>> Let me know if I can help with anything to facilitate the package
>>> being updated.
>>
>> Ben: If you are knowledgeable about Debian packaging, the you'll find
>> all the pointers you need there:
>> https://tracker.debian.org/pkg/torbirdy

> If I understand the issue, I believe we just need to upload 0.1.4 - it
> is straight forward.

OK, thanks a lot for the clarification!

Cheers,
-- 
intrigeri

Bug#796840: telepathy-gabble-tests: Please change section to misc

[Niels Thykier]

On 2015-08-24 23:07, Niels Thykier wrote:
> Package: telepathy-gabble-tests
> Severity: wishlist
> Usertags: ddeb-support
> 
> Hi,
> 
> Please consider moving telepathy-gabble-tests to a different section.
> 
> To better support ddebs, the FTP masters have decided to implement a
> change in DAK that will make DAK move *all* packages in the debug
> section into a separate archive for debug symbols[1].
> 
> As telepathy-gabble-tests is not purely a package containing debug
> symbols, it should probably change section.
> 
> ~Niels
> 
> [1] I will write a mail to debian-devel@ with more information about
> this change.
> 

Per Simon McVitte's suggestion, the "devel" section is properly more suited.

Thanks,
~Niels



signature.asc
Description: OpenPGP digital signature

Bug#796839: libzorpll3.9-1-memtrace: Please change section to misc

[Niels Thykier]

On 2015-08-24 23:05, Niels Thykier wrote:
> Package: libzorpll3.9-1-memtrace
> Severity: wishlist
> Usertags: ddeb-support
> 
> Hi,
> 
> Please consider moving libglib2.0-0-refdbg to a different section.
> 
> To better support ddebs, the FTP masters have decided to implement a
> change in DAK that will make DAK move *all* packages in the debug
> section into a separate archive for debug symbols[1].
> 
> As libzorpll3.9-1-memtrace is not purely a package containing debug
> symbols, it should probably change section.
> 
> ~Niels
> 
> [1] I will write a mail to debian-devel@ with more information about
> this change.
> 


Per Simon McVitte's suggestion, the "devel" section is properly more suited.

Thanks,
~Niels




signature.asc
Description: OpenPGP digital signature

Bug#796836: libglib2.0-0-refdbg: Please change section to misc

[Niels Thykier]

Control: retitle -1  libglib2.0-0-refdbg: Please change section to devel

On 2015-08-24 23:16, Simon McVittie wrote:
> On 24/08/15 22:04, Niels Thykier wrote:
>> Please consider moving libglib2.0-0-refdbg to a different section.
> 
> devel seems a little less inappropriate than misc, perhaps?
> 
> Some other packages similar to libglib2.0-0-refdbg:
> 
> * python2.7-dbg (and other versions) are the Python interpreter
>   and standard library, rebuilt with debugging features
> * dbus-1-dbg contains debug symbols, but also rebuilt versions
>   of libdbus with extra tests/assertions/misc, and the regression
>   tests that use them
> 
> Regards,
> S
> 

Seems reasonable to me. :)






signature.asc
Description: OpenPGP digital signature

Bug#588153: closed by Marc Fournier (Bug#588153: fixed in collectd 5.5.0-1)

[Sebastian Harl]

Hi,

On Fri, Aug 21, 2015 at 06:42:17PM +0100, Ian Jackson wrote:
> Debian Bug Tracking System writes ("Bug#588153 closed by Marc Fournier 
>  (Bug#588153: fixed in collectd 5.5.0-1)"):
> >  - Add Build-depend on libudev-dev (used by disk plugin to enable
> >udev-based device renaming on Linux) (Closes: #588153, #632936).
> 
> This doesn't seem to be anything related to my bug report.  But I
> think in fact #632936 is similar to my bug report and 

The udev-based device renaming (indirectly) addresses your bug by
providing stable identifiers.

> >  - The disk plugin now (optionally) supports instance names
> >based on a udev attribute; thanks to Trent W. Buck for
> >reporting this (Closes: #632936).
> 
> this seems to be actually relevant.
> 
> I note that #632936 appears twice in the changelog.

Oops. I added this entry and missed that the bug was already referenced
in the other entry.

> But anyway if #632936 is fixed I think #588153 is too, pretty much.

I think so, too. Note that filtering is applied after renaming the
device which should cover the other aspect of your original report. If
there's anything else, please reopen or open a new bug.

> I thought I would email you about these changelog oddities just to
> double-check.

Thanks for checking.

Cheers,
Sebastian

-- 
Sebastian "tokkee" Harl +++ GnuPG-ID: 0x2F1FFCC7 +++ http://tokkee.org/

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin



signature.asc
Description: Digital signature

Bug#796834: perl-debug: Please change section to devel

[Niels Thykier]

Control: retitle -1 perl-debug: Please change section to devel

On 2015-08-24 23:03, Niels Thykier wrote:
> Package: perl-debug
> Severity: wishlist
> Usertags: ddeb-support
> 
> Hi,
> 
> Please consider moving perl-debug to a different section.
> 
> To better support ddebs, the FTP masters have decided to implement a
> change in DAK that will make DAK move *all* packages in the debug
> section into a separate archive for debug symbols[1].
> 
> As perl-debug is not (purely?) a package containing debug symbols,
> it should probably change section.
> 
> ~Niels
> 
> [1] I will write a mail to debian-devel@ with more information about
> this change.
> 

Per Simon McVitte's suggestion, the "devel" section is probably more suited.

Thanks,
~Niels




signature.asc
Description: OpenPGP digital signature

Bug#726965: (no subject)

[Ondrej Zary]

There's a fix available upstream and also in unstable.

Downloading source package of xserver-xorg-video-trident from unstable 
(1:1.3.7-1), compiling it (dpkg-buildpackage) and installing makes the driver 
work.

-- 
Ondrej Zary

Bug#771666: dirmngr: Hostname verification uses the wrong hostname

[intrigeri]

Control: tag -1 + moreinfo

Hi,

Tristan Seligmann wrote (01 Dec 2014 11:30:51 GMT) :
> When connecting to an hkps keyserver, dirmngr performs hostname
> verification using the wrong hostname, like so: [...]

Can you reproduce this with 2.1.7-2, that's now in sid?

Cheers,
--
intrigeri

Bug#796843: python-clang-3.8 and python-clang-3.7: error when trying to install together

[Ralf Treinen]

Package: python-clang-3.7,python-clang-3.8
Version: python-clang-3.7/1:3.7~+rc3-1
Version: python-clang-3.8/1:3.8~svn245286-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2015-08-24
Architecture: amd64
Distribution: sid

Hi,

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


Selecting previously unselected package libpython2.7-minimal:amd64.
(Reading database ... 10899 files and directories currently installed.)
Preparing to unpack .../libpython2.7-minimal_2.7.10-3_amd64.deb ...
Unpacking libpython2.7-minimal:amd64 (2.7.10-3) ...
Selecting previously unselected package python2.7-minimal.
Preparing to unpack .../python2.7-minimal_2.7.10-3_amd64.deb ...
Unpacking python2.7-minimal (2.7.10-3) ...
Selecting previously unselected package python-minimal.
Preparing to unpack .../python-minimal_2.7.9-1_amd64.deb ...
Unpacking python-minimal (2.7.9-1) ...
Selecting previously unselected package mime-support.
Preparing to unpack .../mime-support_3.59_all.deb ...
Unpacking mime-support (3.59) ...
Selecting previously unselected package libdb5.3:amd64.
Preparing to unpack .../libdb5.3_5.3.28-9+b1_amd64.deb ...
Unpacking libdb5.3:amd64 (5.3.28-9+b1) ...
Selecting previously unselected package libexpat1:amd64.
Preparing to unpack .../libexpat1_2.1.0-7_amd64.deb ...
Unpacking libexpat1:amd64 (2.1.0-7) ...
Selecting previously unselected package libffi6:amd64.
Preparing to unpack .../libffi6_3.2.1-3_amd64.deb ...
Unpacking libffi6:amd64 (3.2.1-3) ...
Selecting previously unselected package libpython2.7-stdlib:amd64.
Preparing to unpack .../libpython2.7-stdlib_2.7.10-3_amd64.deb ...
Unpacking libpython2.7-stdlib:amd64 (2.7.10-3) ...
Selecting previously unselected package python2.7.
Preparing to unpack .../python2.7_2.7.10-3_amd64.deb ...
Unpacking python2.7 (2.7.10-3) ...
Selecting previously unselected package libpython-stdlib:amd64.
Preparing to unpack .../libpython-stdlib_2.7.9-1_amd64.deb ...
Unpacking libpython-stdlib:amd64 (2.7.9-1) ...
Processing triggers for man-db (2.7.2-1) ...
Setting up libpython2.7-minimal:amd64 (2.7.10-3) ...
Setting up python2.7-minimal (2.7.10-3) ...
Setting up python-minimal (2.7.9-1) ...
Selecting previously unselected package python.
(Reading database ... 11692 files and directories currently installed.)
Preparing to unpack .../python_2.7.9-1_amd64.deb ...
Unpacking python (2.7.9-1) ...
Selecting previously unselected package python-clang-3.7.
Preparing to unpack .../python-clang-3.7_1%3a3.7~+rc3-1_amd64.deb ...
Unpacking python-clang-3.7 (1:3.7~+rc3-1) ...
Selecting previously unselected package python-clang-3.8.
Preparing to unpack .../python-clang-3.8_1%3a3.8~svn245286-1_amd64.deb ...
Unpacking python-clang-3.8 (1:3.8~svn245286-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/python-clang-3.8_1%3a3.8~svn245286-1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/lib/python2.7/dist-packages/clang/enumerations.py', 
which is also in package python-clang-3.7 1:3.7~+rc3-1
Processing triggers for man-db (2.7.2-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/python-clang-3.8_1%3a3.8~svn245286-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

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

  /usr/lib/python2.7/dist-packages/clang/__init__.py
  /usr/lib/python2.7/dist-packages/clang/cindex.py
  /usr/lib/python2.7/dist-packages/clang/enumerations.py

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

-Ralf.

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

Bug#796010: python-pymysql: The attached patch fixes the failing tests for python-pymysql.

[Corey Bryant]

Package: python-pymysql
Version: 0.6.2-1
Followup-For: Bug #796010
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu wily ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/test-issue-36.patch: Added to fix failing test, test_issue_36().
  * d/p/test-datatypes.patch: Added to fix failing test, test_datatypes.

Thanks for considering the patch.


-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-26-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
=== removed file '.pc/applied-patches'
=== modified file 'debian/changelog'

=== added directory 'debian/patches'
=== added file 'debian/patches/series'
--- debian/patches/series	1970-01-01 00:00:00 +
+++ debian/patches/series	2015-08-24 20:56:08 +
@@ -0,0 +1,2 @@
+test-datatypes.patch
+test-issue-36.patch

=== added file 'debian/patches/test-datatypes.patch'
--- debian/patches/test-datatypes.patch	1970-01-01 00:00:00 +
+++ debian/patches/test-datatypes.patch	2015-08-24 20:58:36 +
@@ -0,0 +1,27 @@
+Description: Partial cherry-pick from upstream commit f43aeeaf
+ to fix failing test, test_datatypes().
+Author: Corey Bryant 
+Forwarded: not-needed
+
+--- a/pymysql/tests/test_basic.py
 b/pymysql/tests/test_basic.py
+@@ -18,16 +18,13 @@
+ c.execute("create table test_datatypes (b bit, i int, l bigint, f real, s varchar(32), u varchar(32), bb blob, d date, dt datetime, ts timestamp, td time, t time, st datetime)")
+ try:
+ # insert values
+-v = (True, -3, 123456789012, 5.7, "hello'\" world", u"Espa\xc3\xb1ol", "binary\x00data".encode(conn.charset), datetime.date(1988,2,2), datetime.datetime.now(), datetime.timedelta(5,6), datetime.time(16,32), time.localtime())
++
++v = (True, -3, 123456789012, 5.7, "hello'\" world", u"Espa\xc3\xb1ol", "binary\x00data".encode(conn.charset), datetime.date(1988,2,2), datetime.datetime(2014, 5, 15, 7, 45, 57), datetime.timedelta(5,6), datetime.time(16,32), time.localtime())
+ c.execute("insert into test_datatypes (b,i,l,f,s,u,bb,d,dt,td,t,st) values (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s)", v)
+ c.execute("select b,i,l,f,s,u,bb,d,dt,td,t,st from test_datatypes")
+ r = c.fetchone()
+ self.assertEqual(util.int2byte(1), r[0])
+-self.assertEqual(v[1:8], r[1:8])
+-# mysql throws away microseconds so we need to check datetimes
+-# specially. additionally times are turned into timedeltas.
+-self.assertEqual(datetime.datetime(*v[8].timetuple()[:6]), r[8])
+-self.assertEqual(v[9], r[9]) # just timedeltas
++self.assertEqual(v[1:10], r[1:10])
+ self.assertEqual(datetime.timedelta(0, 60 * (v[10].hour * 60 + v[10].minute)), r[10])
+ self.assertEqual(datetime.datetime(*v[-1][:6]), r[-1])
+ 

=== added file 'debian/patches/test-issue-36.patch'
--- debian/patches/test-issue-36.patch	1970-01-01 00:00:00 +
+++ debian/patches/test-issue-36.patch	2015-08-24 20:57:30 +
@@ -0,0 +1,16 @@
+Description: Partial cherry-pick from upstream commit eb172754
+ to fix failing test, test_issue_36().
+Author: Corey Bryant 
+Forwarded: not-needed
+
+--- a/pymysql/tests/test_issues.py
 b/pymysql/tests/test_issues.py
+@@ -197,7 +197,7 @@
+ kill_id = id
+ break
+ # now nuke the connection
+-conn.kill(kill_id)
++self.connections[1].kill(kill_id)
+ # make sure this connection has broken
+ try:
+ c.execute("show tables")

Bug#796836: libglib2.0-0-refdbg: Please change section to misc

[Simon McVittie]

On 24/08/15 22:04, Niels Thykier wrote:
> Please consider moving libglib2.0-0-refdbg to a different section.

devel seems a little less inappropriate than misc, perhaps?

Some other packages similar to libglib2.0-0-refdbg:

* python2.7-dbg (and other versions) are the Python interpreter
  and standard library, rebuilt with debugging features
* dbus-1-dbg contains debug symbols, but also rebuilt versions
  of libdbus with extra tests/assertions/misc, and the regression
  tests that use them

Regards,
S

Bug#796088: jessie-pu: package libvirt/1.2.9-9+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2015-08-24 at 20:10 +0200, intrigeri wrote:
> Control: tag -1 - moreinfo
> 
> Hi,
> 
> Guido Günther wrote (20 Aug 2015 11:57:36 GMT) :
> > On Wed, Aug 19, 2015 at 04:53:32PM +0100, Adam D. Barratt wrote:
> >> I have to admit that I'm also confused by the patch for #786650:
[...]
> We've discussed this on #786650, and as a result here's an updated
> debdiff: the only change, compared to the one Guido submitted
> initially, is that Allow-access-to-libnl-3-config-files.patch now does
> not include these changes, that are unrelated to #786650, that this
> patch as meant to fix.

That means it also still contains the typo where it claims to fix bug
#7788171. :-)

> I've just built and tested on Jessie, and could successfully start
> a VM with AppArmor enforced.

Thanks. Please feel free to upload, preferably with the changelog typo
fixed.

Regards,

Adam

Bug#796841: RFP: xul-ext-fokus -- Fokus emphasizes anything you select by covering the rest of the page with semi-transparent black.

[shirish शिरीष]

Package: wnpp
Severity: wishlist

* Package name: xul-ext-fokus
  Version : 0.5.2.1
  Upstream Author : Aaron Raimist 
* URL : https://github.com/hakimel/fokus
* License : MIT/X
  Programming Lang: JS,XUL
  Description : Fokus emphasizes anything you select by covering
the rest of the page with semi-transparent black.

Fokus uses JavaScript to emphasize anything you select by covering the
rest of the page with semi-transparent black.

The library has no dependencies and weighs in at around 3kb. A
 element is used to paint the cut-out cover. Works in most
modern browsers except IE and touch devices.

If you want to use this on your site simply include the fokus.min.js script.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#796842: togl-demos: Please change section to misc

[Niels Thykier]

Package: togl-demos
Severity: wishlist
Usertags: ddeb-support

Hi,

Please consider moving togl-demos to a different section.

To better support ddebs, the FTP masters have decided to implement a
change in DAK that will make DAK move *all* packages in the debug
section into a separate archive for debug symbols[1].

As togl-demos is not purely a package containing debug symbols, it
should probably change section.

~Niels

[1] I will write a mail to debian-devel@ with more information about
this change.

Bug#796840: telepathy-gabble-tests: Please change section to misc

[Niels Thykier]

Package: telepathy-gabble-tests
Severity: wishlist
Usertags: ddeb-support

Hi,

Please consider moving telepathy-gabble-tests to a different section.

To better support ddebs, the FTP masters have decided to implement a
change in DAK that will make DAK move *all* packages in the debug
section into a separate archive for debug symbols[1].

As telepathy-gabble-tests is not purely a package containing debug
symbols, it should probably change section.

~Niels

[1] I will write a mail to debian-devel@ with more information about
this change.

Bug#796839: libzorpll3.9-1-memtrace: Please change section to misc

[Niels Thykier]

Package: libzorpll3.9-1-memtrace
Severity: wishlist
Usertags: ddeb-support

Hi,

Please consider moving libglib2.0-0-refdbg to a different section.

To better support ddebs, the FTP masters have decided to implement a
change in DAK that will make DAK move *all* packages in the debug
section into a separate archive for debug symbols[1].

As libzorpll3.9-1-memtrace is not purely a package containing debug
symbols, it should probably change section.

~Niels

[1] I will write a mail to debian-devel@ with more information about
this change.

Bug#796088: jessie-pu: package libvirt/1.2.9-9+deb8u1

[intrigeri]

Control: tag -1 - moreinfo

Hi,

Guido Günther wrote (20 Aug 2015 11:57:36 GMT) :
> On Wed, Aug 19, 2015 at 04:53:32PM +0100, Adam D. Barratt wrote:
>> I have to admit that I'm also confused by the patch for #786650:
[...]
>> That seems to make sense...
>> 
>> +   # for hostdev
>> +   /sys/devices/ r,
>> +   /sys/devices/** r,
>> ++  deny /dev/sd* r,
>> ++  deny /dev/vd* r,
>> ++  deny /dev/dm-* r,
>> ++  deny /dev/mapper/ r,
>> ++  deny /dev/mapper/* r,
>> 
>> ... these not so much.

> According to Felix (cc:) these are only here to silence some denials
> filling the logs otherwise. So they cause not harm but are not mentioned
> in the changelog. I could fix that up before an upload.

We've discussed this on #786650, and as a result here's an updated
debdiff: the only change, compared to the one Guido submitted
initially, is that Allow-access-to-libnl-3-config-files.patch now does
not include these changes, that are unrelated to #786650, that this
patch as meant to fix.

I've just built and tested on Jessie, and could successfully start
a VM with AppArmor enforced.

Cheers,
--
intrigeri

diff -Nru libvirt-1.2.9/debian/changelog libvirt-1.2.9/debian/changelog
--- libvirt-1.2.9/debian/changelog	2015-02-06 15:43:48.0 +0100
+++ libvirt-1.2.9/debian/changelog	2015-08-24 16:21:08.0 +0200
@@ -1,3 +1,28 @@
+libvirt (1.2.9-9+deb8u1) jessie; urgency=medium
+
+  [ Guido Günther ]
+  * [8e4cf5a] Teach virt-aa-helper to use TEMPLATE.qemu if the domain is kvm
+or kqemu.
+Thanks to Luke Faraone for the report (Closes: #786650)
+  * [ad1ff0b] Adjust gbp.conf for jessie
+  * [c830a54] Disable test suite due to libxml2 bug #781232 in jessie
+  * [be70aec] Fix crash on live migration
+this supplements 07dbec0a64783f644854a22aa0355720f0328d17.
+Thanks to Eckebrecht von Pappenheim (Closes: #7788171)
+
+  [ Felix Geyer ]
+  * [9fb6c59] Allow access to libnl-3 configuration (Closes: #786652)
+
+  [ intrigeri ]
+  * Allow-access-to-libnl-3-config-files.patch: revert changes that are
+unrelated to the bug this patch is meant to fix.
+
+  [ Daniel P. Berrange ]
+  * [afae69a] Report original error when QMP probing fails with new QEMU
+(Closes: #780093)
+
+ -- Guido Günther   Thu, 13 Aug 2015 15:56:49 +0200
+
 libvirt (1.2.9-9) unstable; urgency=medium
 
   * [4c14b83] qemu: Don't try to parse -help for new QEMU.
diff -Nru libvirt-1.2.9/debian/gbp.conf libvirt-1.2.9/debian/gbp.conf
--- libvirt-1.2.9/debian/gbp.conf	2015-02-05 21:22:11.0 +0100
+++ libvirt-1.2.9/debian/gbp.conf	2015-08-24 16:21:08.0 +0200
@@ -1,6 +1,7 @@
 [DEFAULT]
 upstream-branch=upstream/sid
-debian-branch=master
+debian-branch=debian/jessie
+dist=jessie
 
 [gbp-pq]
 patch-numbers = False
diff -Nru libvirt-1.2.9/debian/patches/Allow-access-to-libnl-3-config-files.patch libvirt-1.2.9/debian/patches/Allow-access-to-libnl-3-config-files.patch
--- libvirt-1.2.9/debian/patches/Allow-access-to-libnl-3-config-files.patch	1970-01-01 01:00:00.0 +0100
+++ libvirt-1.2.9/debian/patches/Allow-access-to-libnl-3-config-files.patch	2015-08-24 16:21:08.0 +0200
@@ -0,0 +1,22 @@
+From: Felix Geyer 
+Date: Sat, 13 Jun 2015 10:22:40 +0200
+Subject: Allow access to libnl-3 config files
+
+Closes: #786650
+---
+ examples/apparmor/usr.lib.libvirt.virt-aa-helper | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/examples/apparmor/usr.lib.libvirt.virt-aa-helper b/examples/apparmor/usr.lib.libvirt.virt-aa-helper
+index bceaaff..a3c9938 100644
+--- a/examples/apparmor/usr.lib.libvirt.virt-aa-helper
 b/examples/apparmor/usr.lib.libvirt.virt-aa-helper
+@@ -16,6 +16,8 @@
+   owner @{PROC}/[0-9]*/status r,
+   @{PROC}/filesystems r,
+ 
++  /etc/libnl-3/classid r,
++
+   # for hostdev
+   /sys/devices/ r,
+   /sys/devices/** r,
diff -Nru libvirt-1.2.9/debian/patches/Fix-crash-on-live-migration.patch libvirt-1.2.9/debian/patches/Fix-crash-on-live-migration.patch
--- libvirt-1.2.9/debian/patches/Fix-crash-on-live-migration.patch	1970-01-01 01:00:00.0 +0100
+++ libvirt-1.2.9/debian/patches/Fix-crash-on-live-migration.patch	2015-08-24 16:21:08.0 +0200
@@ -0,0 +1,25 @@
+From: =?utf-8?q?Guido_G=C3=BCnther?= 
+Date: Sat, 13 Jun 2015 10:38:26 +0200
+Subject: Fix crash on live migration
+
+this supplements 07dbec0a64783f644854a22aa0355720f0328d17.
+
+Closes: #7788171
+Thanks: Eckebrecht von Pappenheim
+---
+ src/qemu/qemu_migration.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/qemu/qemu_migration.c b/src/qemu/qemu_migration.c
+index e18556f..87f3f1a 100644
+--- a/src/qemu/qemu_migration.c
 b/src/qemu/qemu_migration.c
+@@ -2746,7 +2746,7 @@ qemuMigrationPrepareAny(virQEMUDriverPtr driver,
+ QEMU_ASYNC_JOB_MIGRATION_IN) < 0)
+ goto stop;
+ 
+-if (STREQ(protocol, "rdma") &&
++if (STREQ_NULLABLE(protocol, "rdma") &&
+ virProcessSetMaxMemLock(vm->pid, vm->def->mem.hard_limit << 10) < 0) {
+ goto stop;
+ }
dif

Bug#796838: golang-snappy-go-dev and golang-github-golang-snappy-dev: error when trying to install together

[Ralf Treinen]

Package: golang-github-golang-snappy-dev,golang-snappy-go-dev
Version: golang-github-golang-snappy-dev/0.0~git20150730.0.723cc1e-1
Version: golang-snappy-go-dev/0.0+git20150730.723cc1e-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2015-08-24
Architecture: amd64
Distribution: sid

Hi,

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


Selecting previously unselected package golang-src.
(Reading database ... 10899 files and directories currently installed.)
Preparing to unpack .../golang-src_2%3a1.4.2-3_amd64.deb ...
Unpacking golang-src (2:1.4.2-3) ...
Selecting previously unselected package golang-go-linux-amd64.
Preparing to unpack .../golang-go-linux-amd64_2%3a1.4.2-3_amd64.deb ...
Unpacking golang-go-linux-amd64 (2:1.4.2-3) ...
Selecting previously unselected package golang-go.
Preparing to unpack .../golang-go_2%3a1.4.2-3_amd64.deb ...
Unpacking golang-go (2:1.4.2-3) ...
Selecting previously unselected package golang-github-golang-snappy-dev.
Preparing to unpack 
.../golang-github-golang-snappy-dev_0.0~git20150730.0.723cc1e-1_all.deb ...
Unpacking golang-github-golang-snappy-dev (0.0~git20150730.0.723cc1e-1) ...
Selecting previously unselected package golang-snappy-go-dev.
Preparing to unpack .../golang-snappy-go-dev_0.0+git20150730.723cc1e-2_all.deb 
...
Unpacking golang-snappy-go-dev (0.0+git20150730.723cc1e-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/golang-snappy-go-dev_0.0+git20150730.723cc1e-2_all.deb 
(--unpack):
 trying to overwrite 
'/usr/share/gocode/src/github.com/golang/snappy/snappy_test.go', which is also 
in package golang-github-golang-snappy-dev 0.0~git20150730.0.723cc1e-1
Processing triggers for man-db (2.7.2-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/golang-snappy-go-dev_0.0+git20150730.723cc1e-2_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

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

  /usr/share/gocode/src/github.com/golang/snappy/decode.go
  /usr/share/gocode/src/github.com/golang/snappy/encode.go
  /usr/share/gocode/src/github.com/golang/snappy/snappy.go
  /usr/share/gocode/src/github.com/golang/snappy/snappy_test.go

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

-Ralf.

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

Bug#786650: virt-aa-helper: incomplete apparmor profile

[intrigeri]

intrigeri wrote (24 Aug 2015 09:12:33 GMT) :
> Once the Git repo is up-to-date, I'll send an updated debdiff to the
> release team.

Done.

Bug#796836: libglib2.0-0-refdbg: Please change section to misc

[Niels Thykier]

Package: libglib2.0-0-refdbg
Severity: wishlist
Usertags: ddeb-support

Hi,

Please consider moving libglib2.0-0-refdbg to a different section.

To better support ddebs, the FTP masters have decided to implement a
change in DAK that will make DAK move *all* packages in the debug
section into a separate archive for debug symbols[1].

As libglib2.0-0-refdbg is not purely a package containing debug
symbols, it should probably change section.

~Niels

[1] I will write a mail to debian-devel@ with more information about
this change.

Bug#796835: release.debian.org: Transition: ncurses-6.0

[Sven Joachim]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-CC: ncur...@packages.debian.org
Control: block 230990 by -1

For quite some time, ncurses had the option to be built with a new ABI
that enables applications to use mouse wheels, among other good things
(see #230990).  Switching to this ABI had been stalled due to the lack
of symbol versioning and the rather large number of ncurses' reverse
dependencies, with quite a few libraries among them.

In the latest ncurses release (6.0), symbol versioning was added to the
libraries, and we would like to see ncurses' reverse dependencies to be
rebuilt during the Stretch release cycle so that the long requested ABI
change becomes possible after the Debian 9 release.

The new ncurses version has already migrated to testing, and there is no
hurry to rebuild reverse dependencies right away, but I would like to
see a mass rebuild some time before the Stretch freeze and set up a
tracker in the meantime.

Suggested ben file (only lightly tested, please check):

title = "ncurses-6.0";
is_affected = .depends ~ /libncursesw?5|libtinfo5/;
is_good = .depends ~ /libncursesw?5 \(>= 6|libtinfo5 \(>= 6/;
is_bad = .depends ~ /libncursesw?5 \(>= 5|libtinfo5(,|$)|libtinfo5\(>= 5/;


Cheers,
   Sven

Bug#796837: libsofthsm2-dev and libsofthsm-dev: error when trying to install together

[Ralf Treinen]

Package: libsofthsm-dev,libsofthsm2-dev
Version: libsofthsm-dev/1.3.7-2+b1
Version: libsofthsm2-dev/2.0.0-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2015-08-24
Architecture: amd64
Distribution: sid

Hi,

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


Preconfiguring packages ...
Selecting previously unselected package gcc-5-base:amd64.
(Reading database ... 10899 files and directories currently installed.)
Preparing to unpack .../gcc-5-base_5.2.1-15_amd64.deb ...
Unpacking gcc-5-base:amd64 (5.2.1-15) ...
Setting up gcc-5-base:amd64 (5.2.1-15) ...
(Reading database ... 10906 files and directories currently installed.)
Preparing to unpack .../libstdc++6_5.2.1-15_amd64.deb ...
Unpacking libstdc++6:amd64 (5.2.1-15) over (4.8.2-19) ...
Setting up libstdc++6:amd64 (5.2.1-15) ...
Processing triggers for libc-bin (2.19-19) ...
Selecting previously unselected package ucf.
(Reading database ... 10920 files and directories currently installed.)
Preparing to unpack .../archives/ucf_3.0030_all.deb ...
Moving old data out of the way
Unpacking ucf (3.0030) ...
Selecting previously unselected package libgmp10:amd64.
Preparing to unpack .../libgmp10_2%3a6.0.0+dfsg-7_amd64.deb ...
Unpacking libgmp10:amd64 (2:6.0.0+dfsg-7) ...
Selecting previously unselected package libbotan-1.10-1.
Preparing to unpack .../libbotan-1.10-1_1.10.10-6_amd64.deb ...
Unpacking libbotan-1.10-1 (1.10.10-6) ...
Selecting previously unselected package softhsm-common.
Preparing to unpack .../softhsm-common_1.3.7-2+b1_amd64.deb ...
Unpacking softhsm-common (1.3.7-2+b1) ...
Selecting previously unselected package libsofthsm.
Preparing to unpack .../libsofthsm_1.3.7-2+b1_amd64.deb ...
Unpacking libsofthsm (1.3.7-2+b1) ...
Selecting previously unselected package libsofthsm-dev.
Preparing to unpack .../libsofthsm-dev_1.3.7-2+b1_amd64.deb ...
Unpacking libsofthsm-dev (1.3.7-2+b1) ...
Selecting previously unselected package softhsm2-common.
Preparing to unpack .../softhsm2-common_2.0.0-1_amd64.deb ...
Unpacking softhsm2-common (2.0.0-1) ...
Selecting previously unselected package libsofthsm2.
Preparing to unpack .../libsofthsm2_2.0.0-1_amd64.deb ...
Unpacking libsofthsm2 (2.0.0-1) ...
Selecting previously unselected package libsofthsm2-dev.
Preparing to unpack .../libsofthsm2-dev_2.0.0-1_amd64.deb ...
Unpacking libsofthsm2-dev (2.0.0-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libsofthsm2-dev_2.0.0-1_amd64.deb (--unpack):
 trying to overwrite '/usr/include/softhsm/pkcs11.h', which is also in package 
libsofthsm-dev 1.3.7-2+b1
Processing triggers for man-db (2.7.2-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libsofthsm2-dev_2.0.0-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

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

  /usr/include/softhsm/pkcs11.h

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

-Ralf.

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

Bug#796834: perl-debug: Please change section to misc

[Niels Thykier]

Package: perl-debug
Severity: wishlist
Usertags: ddeb-support

Hi,

Please consider moving perl-debug to a different section.

To better support ddebs, the FTP masters have decided to implement a
change in DAK that will make DAK move *all* packages in the debug
section into a separate archive for debug symbols[1].

As perl-debug is not (purely?) a package containing debug symbols,
it should probably change section.

~Niels

[1] I will write a mail to debian-devel@ with more information about
this change.

Bug#796690: screen: Has init script in runlevel S but no matching service file

[Felipe Sateler]

On 24 August 2015 at 12:36, Axel Beckert  wrote:
> Hi Felipe,
>
> Felipe Sateler wrote:
>> On 23 August 2015 at 12:18, Axel Beckert  wrote:
>> > from my point of view, this bug report is a false positive.
>>
>> Indeed.
>
> Thanks for the confirmation!
>
>> Hmm, interesting. It had not occurred to me that uninstalling the
>> package will not remove the init script until purge.
>
> Yep, that's occassionally a burden. Then again, there are many cases
> where I'm happy that init scripts are conffiles and can be edited by
> the local admin.
>
>> Please silence the lintian warning, so that you will not get bugged
>> about this until we figure out a way to detect this case.
>
> Will do.
>
> Shortest workaround is probably to mention this false positive in the
> long description of the tag and to suggest a lintian override in that
> case. (Then again, this may lead to too eager overriding.)

Long term the problem will disappear because the runlevel S patch will
go away. In the meantime we are investigating adding support to
dh_systemd for preserving the mask after remove but before purge. This
way you would be able to drop the post{inst,rm} snippet you currently
have and let dh_systemd handle it; at the same time the lintian
warning would not trigger (because the mask would be in the package
list). But we are not there yet.

-- 

Saludos,
Felipe Sateler

Bug#796833: process-shared semaphores/mutexes not implemented

[Ryan Tandy]

Package: hurd
Version: 1:0.6.git20150704-3
Severity: wishlist
Control: forwarded -1 http://savannah.gnu.org/task/?7050
Control: block 796826 by -1

Hello,

I'm aware this is a known issue or limitation. This is just a bug for 
tracking...


Thanks for your work on GNU.

Bug#796832: pandoc generating bibliography issue

[Riccardo Romoli]

Package: pandoc
Version: 1.12.4.2

I would try to convert the way I write my scientific articles from 
Sweave/LaTeX to knitr/pandoc.
I've been able to reproduce almost everithing with the exceptions of the 
references.
I googled a lot and I read the official and unofficial guide to the 
pandoc references but I've not
yet found the right solution to my problem: no citations are included in 
my document.


This is what I've done:

added bibliography: myBib.bib to the header of the file
added the citation using [@KEY], where KEY is the key entry in my 
.bib file

added # References section at the bottom of my document
convert .Rmd file to .md file using knitr

from shell I run:

pandoc -H headers.tex --bibliography=myBib.bib -o article.pdf 
article.md


The .pdf file was generated but with non citation references

I've also tried to generate the .tex file and then to compile it

pandoc --bibliography=myBib.bib -o article.tex article.md

also using the --natbib and --biblatex switch, but nothing changes.
Opening the .tex file I noticed that the citations were converted as: 
{[}@01, @46{]}

while in the .md file I wrote: [@01, @46].

I installed pandoc (1.15.0.6) and pandoc-citeproc from source and all 
seems to work properly.



-- System Information:
Debian Release: 8.1
  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/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pandoc depends on:
ii  libc62.19-18
ii  libffi6  3.1-2+b2
ii  libgmp10 2:6.0.0+dfsg-6
ii  libicu52 52.1-8+deb8u2
ii  liblua5.1-0  5.1.5-7.1
ii  libpcre3 2:8.35-3.3
ii  libyaml-0-2  0.1.6-3
ii  pandoc-data  1.12.4.2~dfsg-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

pandoc recommends no packages.

Versions of packages pandoc suggests:
pn  etoolbox   
ii  pandoc-citeproc0.4.0.1-1
ii  texlive-latex-recommended  2014.20141024-2
ii  texlive-luatex 2014.20141024-2
ii  texlive-xetex  2014.20141024-2

-- no debconf information
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Riccardo 
To: Debian Bug Tracking System <700...@bugs.debian.org>
Subject: pandoc generating bibliography issue
Message-ID: <20150824175846.29380.79392.reportbug@mb>
X-Mailer: reportbug 6.6.3
Date: Mon, 24 Aug 2015 19:58:46 +0200
X-Debbugs-Cc: ric.rom...@gmail.com

Package: pandoc
Followup-For: Bug #700329

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?


I would try to convert the way I write my scientific articles from Sweave/LaTeX 
to knitr/pandoc. 
I've been able to reproduce almost everithing with the exceptions of the 
references. 
I googled a lot and I read the official and unofficial guide to the pandoc 
references but I've not 
yet found the right solution to my problem: no citations are included in my 
document.

This is what I've done:

added bibliography: myBib.bib to the header of the file
added the citation using [@KEY], where KEY is the key entry in my .bib file
added # References section at the bottom of my document
convert .Rmd file to .md file using knitr

from shell I run:

pandoc -H headers.tex --bibliography=myBib.bib -o article.pdf article.md

The .pdf file was generated but with non citation references

I've also tried to generate the .tex file and then to compile it 

pandoc --bibliography=myBib.bib -o article.tex article.md 

also using the --natbib and --biblatex switch, but nothing changes. 
Opening the .tex file I noticed that the citations were converted as: {[}@01, 
@46{]} 
while in the .md file I wrote: [@01, @46].

I installed pandoc and pandoc-citeproc from source and all seems to work 
properly.



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


-- System Information:
Debian Release: 8.1
  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/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pandoc depends on:
ii  libc62.19-18
ii  libffi6  3.1-2+b2
ii  libgmp10 2:6.0.0+dfsg-6
ii  libicu52 52.1-8+deb8u2
ii  liblua5.1-0  5.1.5-7.1
ii  libpcre3 2:8.35-3.3
ii  libyaml-0-2  0.1.6-3
ii  pandoc-data  1.12.4.2~dfsg-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

pandoc recommends no packages.

Versions of packages pandoc suggests:
pn  

Bug#796758: [pkg-wine-party] Bug#796758: Bug#796758: Update dependency on wine-gecko to 2.40.

[Jens Reyer]

On 08/24/2015 03:45 AM, Michael Gilbert wrote:
> On Sun, Aug 23, 2015 at 9:22 PM, Jens Reyer wrote:
>> wine 1.7.50 needs a new wine-gecko version (2.40).
>> See http://wiki.winehq.org/Gecko.
> 
> Please feel ok to commit to git :)

Great :)

Done. I've committed my changes only (without a changelog entry) in a
way that "gbp dch" understands them (matching my preferred workflow).

Alternatively I can add a changelog entry for UNRELEASED if you prefer,
just tell me your preferences.

Greets
jre

Bug#796831: vim-runtime: syntax/sh.vim highlights "type="

[Christoph Anton Mitterer]

Package: vim-runtime
Version: 2:7.4.826-1
Severity: minor


Hey.
When having a line like:
type=foo
then "type" is highlighted as if it was a reserved word like "if", "case" or 
"easc".

However type isn't a reserved word in the shell command language.
Even in bash, which knows "type" as a built-in command, "type" can be used as 
variable
name.


Cheers,
Chris.

Bug#756253: Upgrade from 2.02~beta2-10 to 2.02~beta2-11 left grub unbootable

[Felix Zielcke]

Am Montag, den 24.08.2015, 10:28 +0200 schrieb Giorgio Valocchi:
> The problem was that the nvram entry wasn't properly created under 
> sid.
> 
> I managed to login in a stable distribution I have on the same system 
> to 
> create it.

In that case it would be a bug either in efibootmgr or the Linux
Kernel.
grub-install just calls efibootmgr to create the entry

Bug#796815: lintian: Correct "The rules files appear" grammatical error in debian-rules-should-not-use-or-modify-user-only-variable

[Jakub Wilk]

Hi Chris!

* Chris Lamb , 2015-08-24, 22:12:

-Info: The rules files appear to be reading or modifying a variable not
+Info: The rules files appears to be reading or modifying a variable not


Hmm, this doesn't look right to me. You made the verb singular, but the 
subject is plural.


But I don't know why the subject is plural in the first place. It 
probably should be something like this instead:


Info: The debian/rules file appears to be ...

--
Jakub Wilk

Bug#796518: ITP: dominate -- Python library for creating and manipulating HTML documents

[Ross Gammon]

Control: owner 796518 !
Control: tags -1 pending

The package is prepared and uploaded to mentors for sponsorship.

I have also requested to become a Debian Python Modules Packaging Team
member.

Ross



signature.asc
Description: OpenPGP digital signature

Bug#796815: lintian: Correct "The rules files appear" grammatical error in debian-rules-should-not-use-or-modify-user-only-variable

[Chris Lamb]

> It probably should be something like this instead:
> 
> Info: The debian/rules file appears to be ...

Ah yes, that bit is odd too. :)


Regards,

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

Bug#796664: signing-party: gpglist does not show all valid identities

[Tomasz Buchert]

On 24/08/15 14:52, Guilhem Moulin wrote:
> Control: tags -1 pending
>
> Hi Tomasz,
>
> On Sun, 23 Aug 2015 at 12:47:01 +0200, Tomasz Buchert wrote:
> > my gpg key is paticular: it has an uid that has been revoked and then
> > subsequently recreated. As a result, it does not show up in the output of
> > gpglist.
> >
> > I've created a patch that fixes that. It slightly changes
> > the output of gpglist to show the status of each identity.
>
> I'd rather avoid that if possible.  Your UID doesn't show up because
> gpglist(1) currently prunes revoked UIDs, while it should keep those
> with a subsequent selfsig.  I pushed a simpler fix in r815.

Nice, your change does the same thing in the end.

>
> > I attach another patch as well, that adds an option (--show-revoked) that 
> > shows
> > all identities.
>
> Thanks, pushed a slightly modified version of your patch in r816.

Great! Thanks for fast feedback!

Tomasz

>
> Cheers,
> --
> Guilhem.


signature.asc
Description: Digital signature