Bug#855595: unblock: atheme-services/7.2.9

[Niels Thykier]

Control: tags -1 confirmed

Antoine Beaupre:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package atheme-services
> 
> There is a security issue that was fixed in the upstream 7.2.8 package
> (#855588), which introduced a new security issue, which was fixed in
> the 7.2.9 package.
> 
> [...]
> 
> Attached is the debdiff against 7.2.7-1 (stretch/sid).
> 
> unblock atheme-services/7.2.9
> 
> [...]

Please go ahead with this, thanks.

~Niels

Bug#856001: fastboot reports wrong version

[Senthil Kumaran S]

Package: fastboot
Version: 1:7.0.0+r1-2
Severity: normal

Dear Maintainer,

fastboot gives wrong version number as seen below:


$ sudo fastboot --version
fastboot version debian
$ 


The version provided above is not useful and creates confusion. The fastboot
binary provided by AOSP platform-tools report the following, which is useful:


$ sudo ./fastboot --version
fastboot version 0e9850346394-android
$ 


This is important since there are differences in how fastboot packaged in
stretch ie., 1:7.0.0+r1-2 behaves with a Google Pixel phone, than the fastboot
provided by AOSP platform-tools and the one packaged in Debian jessie release.

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

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

Versions of packages fastboot depends on:
ii  android-libadb 1:7.0.0+r1-2
ii  android-libbase1:7.0.0+r1-2
ii  android-libcutils  1:7.0.0+r1-2
ii  android-libext4-utils  7.0.0+r1-2
ii  android-libf2fs-utils  7.0.0+r1-2
ii  android-libsparse  1:7.0.0+r1-2
ii  android-libziparchive  1:7.0.0+r1-2
ii  libc6  2.24-9
ii  libgcc11:6.3.0-6
ii  libstdc++6 6.3.0-6

fastboot recommends no packages.

fastboot suggests no packages.

-- no debconf information

Bug#855824: unblock: multipath-tools/0.6.4-4

[Niels Thykier]

Control: tags -1 confirmed

Ritesh Raj Sarraf:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package multipath-tools
> 
> These are minor changes, which should qualify for an upload exception. The new
> file additions are mostly autopkg tests related, which have no impact on the
> software. The other changes are good to have for Stretch.
> 
> unblock multipath-tools/0.6.4-4
> 
> [...]

Ok with me. KiBi, is this upload ok for d-i?

Thanks,
~Niels

Bug#856000: maxima: "maxima --list-avail" reports nothing contrary to man page

[Atsuhito Kohda]

Package: maxima
Version: 5.38.1-8
Severity: normal

Dear Maintainer,

"man maxima" told me that
--init-lisp=file
   Load the Lisp initialization file file at startup.
but when I did "maxima --list-aval" it reported only
$ maxima --list-avail
Available versions:

This is aparently wrong behavior.

Thanks for your maintenance.

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

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

Versions of packages maxima depends on:
ii  libc6 2.24-9
ii  libgmp10  2:6.1.2+dfsg-1
ii  libreadline7  7.0-2
ii  libx11-6  2:1.6.4-3

Versions of packages maxima recommends:
pn  gnuplot-x11   
ii  maxima-share  5.38.1-8

Versions of packages maxima suggests:
pn  maxima-doc
pn  maxima-emacs  
ii  texmacs   1:1.0.7.18-1
ii  tk [wish] 8.6.0+9
pn  xmaxima   

-- no debconf information

Bug#855999: Pbuilder hangs until timeout when output is piped

[Yuri Gribov]

Package: pbuilder
Version: 0.223

Hi,

When using --timeout option of pbuilder and piping output to e.g. cat,
pbuilder will hang until timeout expires (instead of terminating once
build is done):

$ sudo pbuilder build --timeout 1h  lua5.2_5.2.4-1ubuntu1.dsc 2>&1 | cat
...
I: Copying back the cached apt archive contents
I: unmounting dev/pts filesystem
I: unmounting run/shm filesystem
I: unmounting proc filesystem
I: cleaning the build env
I: removing directory /var/cache/pbuilder/build/5322 and its subdirectories
I: Current time: Fri Feb 24 06:57:25 GMT 2017
I: pbuilder-time-stamp: 1487919445  # <-- Hangs for 1 hour

It seems that the issue is in /usr/lib/pbuilder/pbuilder-buildpackage :

if [ -n "${TIMEOUT_TIME}" ]; then
(
: Timeout process
sleep "${TIMEOUT_TIME}"
log.i "Terminating build process due to timeout "
kill "${BUILD_PID}" || true
) & # timeout process
KILL_WAIT_PID="kill $! || true; echo \"I: Terminate timeout process\"; "
...
eval "${KILL_WAIT_PID}"

Note that KILL_WAIT_PID will kill the parent shell but keep sleep
running. Sleep child process will become a zombie and keep writing to
pipe which will _probably_ prevent it from being reaped by the kernel.

A simple fix which worked for me is to redirect sleep's output to
/dev/null (both stdout and stderr need to be redirected):

sleep "${TIMEOUT_TIME}" &> /dev/null

As far as I can see, the issue is still present in latest pbuilder.

-Iurii

Bug#281639: sed's documentation is non-free

[Assaf Gordon]

Hello,

If it helps in any way, the documentation in sed-4.4 (included in 
'stretch') as licensed under GFDLv1.3 and explicitly states:


 "with no Invariant Sections, no Front-Cover Texts, and no
  Back-Cover Texts."

http://git.savannah.gnu.org/cgit/sed.git/tree/doc/sed.texi#n39

regards,
- assaf

Bug#855996: apt-cacher-ng: cron.daily: always fails if ReportPage is disabled

[Paul Wise]

Package: apt-cacher-ng
Version: 2-1
Severity: minor
File: /etc/cron.daily/apt-cacher-ng

I disabled the ReportPage option in acng.conf and now I get daily mails
from cron saying that the cron job failed with no further info:

run-parts: /etc/cron.daily/apt-cacher-ng exited with return code 255

It would be better to have acngtool do one of these things:

 * exit successfully if ReportPage is enabled
 * warn that ReportPage is enabled and suggest to disable the cron job
 * run expiry/etc via the socket instead of http

-- System Information:
Debian Release: 9.0
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages apt-cacher-ng depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.60
ii  dpkg   1.18.22
ii  init-system-helpers1.47
ii  libbz2-1.0 1.0.6-8.1
ii  libc6  2.24-9
ii  libgcc11:6.3.0-6
ii  liblzma5   5.2.2-1.2
ii  libssl1.1  1.1.0e-1
ii  libstdc++6 6.3.0-6
ii  libsystemd0232-15
ii  libwrap0   7.6.q-26
ii  lsb-base   9.20161125
ii  zlib1g 1:1.2.8.dfsg-5

apt-cacher-ng recommends no packages.

Versions of packages apt-cacher-ng suggests:
ii  avahi-daemon  0.6.32-2
pn  doc-base  
ii  libfuse2  2.9.7-1

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#855995: apt-cacher-ng: acng.conf: ReportPage: incorrect comment

[Paul Wise]

Package: apt-cacher-ng
Version: 2-1
Severity: minor
File: /etc/apt-cacher-ng/acng.conf

The comment before the ReportPage option in acng.conf says this:

# Default: not set, should be set by the system administrator

This is very much incorrect, the default is enabled:

ReportPage: acng-report.html
https://codesearch.debian.net/search?q=package:apt-cacher-ng+ReportPage

-- System Information:
Debian Release: 9.0
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages apt-cacher-ng depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.60
ii  dpkg   1.18.22
ii  init-system-helpers1.47
ii  libbz2-1.0 1.0.6-8.1
ii  libc6  2.24-9
ii  libgcc11:6.3.0-6
ii  liblzma5   5.2.2-1.2
ii  libssl1.1  1.1.0e-1
ii  libstdc++6 6.3.0-6
ii  libsystemd0232-15
ii  libwrap0   7.6.q-26
ii  lsb-base   9.20161125
ii  zlib1g 1:1.2.8.dfsg-5

apt-cacher-ng recommends no packages.

Versions of packages apt-cacher-ng suggests:
ii  avahi-daemon  0.6.32-2
pn  doc-base  
ii  libfuse2  2.9.7-1

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#855208: runc: 1.0 release candidate breaks docker 1.11 - oci runtime error: flag provided but not defined: -bundle

[Witold Baryluk]

Package: runc
Version: 1.0.0~rc2+git20161109.131.5137186-2
Followup-For: Bug #855208

Do, now with Breaks,

doing

apt-get dist-upgrade --purge

installs new runc, at the expense of removing docker.io from the sytem.
It would be better to not upgrade any of these.

How about removing or holding off the new runc version from repositories?

Cheers,
Witek

Bug#855994: password rotation needed field

[Joey Hess]

Package: assword
Version: 0.10-2
Severity: normal

It would be very useful to have a field for each password indicating
when it needs to be rotated. assword could then warn when the user uses
that password, and have a button to generate a new password, replacing
the old one in the db.

Given Cloudbleed, it would also be nice to have an option that can set
the field to "immediately" for all passwords..

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

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

Versions of packages assword depends on:
ii  python3-gi   3.22.0-2
ii  python3-gpg  1.8.0-3
pn  python3:any  

Versions of packages assword recommends:
ii  gir1.2-gtk-3.0  3.22.7-1
ii  python3-xdo 0.3-2
ii  xclip   0.12+svn84-4

assword suggests no packages.

-- no debconf information

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#466862: sed: documentation bug: no mention of semicolon as command terminator

[Assaf Gordon]

Hello,

Panu Kalliokoski wrote:

However, the possibility of using semicolons in not mentioned on sed's
man page nor in its info document.  Instead, both insist that every
command must be on its own line.


There's now a dedicated section
in gnu sed's manual about multiple commands and semicolons:

https://www.gnu.org/software/sed/manual/html_node/Multiple-commands-syntax.html#Multiple-commands-syntax

It is included in the texinfo file of sed-4.4 (which is now in 
'testing').


regards,
- assaf

Bug#284646: sed: Documentation does not properly document effects of multiple commands

[Assaf Gordon]

Hello,


- Usage of multiple commands [...]
- The possibility to use a semicolon instead of a newline [...]


12 years later, there's now a dedicated section
in gnu sed's manual about multiple commands and semicolons:

https://www.gnu.org/software/sed/manual/html_node/Multiple-commands-syntax.html#Multiple-commands-syntax

It is included in the texinfo file of sed-4.4 (which is now in 
'testing').



- it is not specified whether address selections following a command
  act on unchanged input lines [...] or on the lines as changed by the 
  previous command


That's a good point.

The 'address' section is much expanded:
https://www.gnu.org/software/sed/manual/html_node/sed-addresses.html#sed-addresses

But I'll add explicit mention of this issue.

regards,
- assaf

Bug#605142: sed: incorrectly interprets \x hexadecimal escapes sometimes

[Assaf Gordon]

Hello,

Picking up an old sed bug:

Matija Nalis wrote:

echo 'a^c' | sed -e 's/\x5e/b/'
should produce output "abc" (as it does in "ssed" or "perl -pe"), but 
in GNU sed it produces "ba^c".


I agree this is indeed GNU sed's behavior,
but it's not clear it is incorrect behavior (or if there is 
a correct one).


GNU sed internally converts escape seqeunces to their
corresponding characters *before* passing it on
to glibc's regex engine (or doing other operations).

It is glibc's regex that does not support unescaping,
which is why this is needed.

Few additional cases:

Un-escaping works in other sed commands:

   $ echo 'a^c' | sed 'y/\x5e/b/'
   abc

And gnu grep, which doesn't unescape, passes the string
to the regex engine, which then doesn't match at all:

   $ echo 'a^c' | gnu-grep-2.26 '\x5e'

As opposed to freebsd's grep:

   $ echo 'a^c' | freebsd-grep-2.5.1 '\x5e'
   a^c

Many other sed implementations don't support unescaping
at all, and return:

   $ echo 'a^c' | sed 's/\x5e/b/'
   a^c
   $ echo 'a^c' | sed 'y/\x5e/b/'
   sed: 1: "y/\x5e/b/": transform strings are not the same length

This is the case for sed from FreeBSD, OpenBSD, BusyBox, ToyBox.

Lastly, POSIX does not mention anything about '\xXX' escape
sequences, so this is left to implementors to decide.

As such, I would suggest marking #605142 as notabug and closing it.

I will add some info about it to sed's manual.

If someone wants to suggest this as a new feature,
please write to sed-de...@gnu.org .
However since this breaks existing behavior, the bar to accepting
it might be high.

regards,
- assaf

Bug#855991: unblock: kstars-data-extra-tycho2/1.1r1-9.1

[Adrian Bunk]

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

Please unblock package kstars-data-extra-tycho2

unblock kstars-data-extra-tycho2/1.1r1-9.1


diff -Nru kstars-data-extra-tycho2-1.1r1/debian/changelog 
kstars-data-extra-tycho2-1.1r1/debian/changelog
--- kstars-data-extra-tycho2-1.1r1/debian/changelog 2013-01-10 
20:52:03.0 +0200
+++ kstars-data-extra-tycho2-1.1r1/debian/changelog 2017-02-24 
05:03:46.0 +0200
@@ -1,3 +1,13 @@
+kstars-data-extra-tycho2 (1.1r1-9.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Move data file to /usr/share/kstars where kstars expects it.
+(Closes: #854008)
+  * Add Turkish debconf template translation from Mert Dirik.
+(Closes: #757490)
+
+ -- Adrian Bunk   Fri, 24 Feb 2017 05:03:46 +0200
+
 kstars-data-extra-tycho2 (1.1r1-9) unstable; urgency=low
 
   * Package moved to non-free (but I still think it's free). Closes: #681654
diff -Nru kstars-data-extra-tycho2-1.1r1/debian/install 
kstars-data-extra-tycho2-1.1r1/debian/install
--- kstars-data-extra-tycho2-1.1r1/debian/install   2010-12-05 
15:10:30.0 +0200
+++ kstars-data-extra-tycho2-1.1r1/debian/install   2017-02-24 
05:03:46.0 +0200
@@ -1 +1 @@
-deepstars.dat usr/share/kde4/apps/kstars
+deepstars.dat usr/share/kstars
diff -Nru kstars-data-extra-tycho2-1.1r1/debian/po/tr.po 
kstars-data-extra-tycho2-1.1r1/debian/po/tr.po
--- kstars-data-extra-tycho2-1.1r1/debian/po/tr.po  1970-01-01 
02:00:00.0 +0200
+++ kstars-data-extra-tycho2-1.1r1/debian/po/tr.po  2017-02-24 
05:03:46.0 +0200
@@ -0,0 +1,172 @@
+# Turkish translation of kstars-data-extra-tycho2 package
+# Copyright (C) 2014 Mert Dirik
+# This file is distributed under the same license as the 
kstars-data-extra-tycho2 package.
+# Mert Dirik , 2014.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: kstars-data-extra-tycho2\n"
+"Report-Msgid-Bugs-To: kstars-data-extra-tyc...@packages.debian.org\n"
+"POT-Creation-Date: 2011-07-27 09:34+0200\n"
+"PO-Revision-Date: 2014-08-08 22:34+0200\n"
+"Last-Translator: Mert Dirik \n"
+"Language-Team: Debian L10n Turkish \n"
+"Language: tr\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: Poedit 1.5.4\n"
+
+#. Type: title
+#. Description
+#: ../templates:2001
+msgid "Handling of kstars configuration file"
+msgstr "kstars yapılandırma dosyasınına yapılacak eylem"
+
+#. Type: select
+#. Choices
+#: ../templates:3001
+msgid "keep"
+msgstr "olduğu gibi bırak"
+
+#. Type: select
+#. Choices
+#: ../templates:3001
+msgid "replace (preserving backup)"
+msgstr "yenisiyle değiştir (eskisinin yedeğini alır)"
+
+#. Type: select
+#. Choices
+#: ../templates:3001
+msgid "overwrite"
+msgstr "üzerine yaz"
+
+#. Type: select
+#. Description
+#: ../templates:3002
+msgid "Action for the /etc/kde4/kstarsrc file:"
+msgstr "/etc/kde4/kstarsrc dosyasına yapılacak eylem:"
+
+#. Type: select
+#. Description
+#: ../templates:3002
+msgid "A kstars global configuration file already exists."
+msgstr ""
+"Sizteminizde halihazırda bir kstars genel yapılandırma dosyası bulunuyor."
+
+#. Type: select
+#. Description
+#: ../templates:3002
+msgid ""
+"The package installation process can't modify it, but you can back it up now "
+"and create a new one. You will be prompted for options in this file."
+msgstr ""
+"Paket kurulum süreci bu dosyayı düzenleyemez, fakat istediğiniz takdirde "
+"mevcut dosyayı yedekleyip yerine yeni bir dosya oluşturabilir. Seçenekler "
+"size danışılacaktır."
+
+#. Type: boolean
+#. Description
+#: ../templates:4001
+msgid "Create /etc/kde4/kstarsrc file?"
+msgstr "/etc/kde4/kstarsrc dosyası oluşturulsun mu?"
+
+#. Type: boolean
+#. Description
+#: ../templates:4001
+msgid "There is no kstars global configuration file."
+msgstr "Genel bir kstars yapılandırma dosyası mevcut değil. "
+
+#. Type: boolean
+#. Description
+#: ../templates:4001
+msgid ""
+"A configuration file will be needed if user downloads should be disabled, "
+"but if not then it is still safe to create one. You will be prompted for "
+"options in this file."
+msgstr ""
+"Kullanıcıların indirme yapmasını engellemek istiyorsanız bir yapılandırma "
+"dosyası oluşturmanız gerekir. Eğer mevcut bir yapılandırma dosyası yoksa "
+"yeni bir yapılandırma oluşturmak zararsız bir eylemdir. Dosyada kullanılacak "
+"olan seçenekler size danışılacaktır."
+
+#. Type: title
+#. Description
+#: ../templates:5001
+msgid "Disable or lock data downloads"
+msgstr "Veri indirmeyi yasakla ya da kilitle"
+
+#. Type: select
+#. Choices
+#: ../templates:6001
+msgid "enable"
+msgstr "etkinleştir"
+
+#. Type: select
+#. Choices
+#: ../templates:6001
+msgid "disable"
+msgstr "etkisiz hale getir"
+
+#. Type: select
+#. Choices
+#: ../templates:6001
+msgid "lock"
+msgstr "kilitle"
+
+#. Type: 

Bug#855662: fakeroot: when msgrcv is interrupted by a signal, faked accidentally reprocesses the previous message

[Martin Dorey]

> Good luck.

Sadly, after several days of parallel package building later, I've had another 
failure.  Happily, now errno's been preserved by my previous patch, I have A 
New Clue:

FAKEROOT: r=-1, received message type=1, message=3
FAKEROOT, get_msg: Identifier removed
errno=43, EINTR=4

On this system, that's:

martind@ussw-cbld00:~$ grep -w 43 /usr/include/asm-generic/errno.h 
#define EIDRM   43  /* Identifier removed */
martind@ussw-cbld00:~$

Now through early evening fog I see that the message queues and the semaphore 
are being generated with a random key.  Collisions with existing keys aren't 
detected.  I have a patch that I hope will detect that and retry.  Would you 
like that here or in a new bug?  Including the first patch or assuming it's 
applied first or against the baseline version?  Any way is easy for me.  I 
imagine the BTS will just do the right thing with a text attachment but five 
minutes of googling hasn't confirmed that's how to submit a patch to an 
existing Debian bug.  Waiting a week for the patch to dis/prove itself would be 
perfectly sensible, but I'm happy to embarrass myself if you're happy to look 
at it before then.

Bug#855662: fakeroot: when msgrcv is interrupted by a signal, faked accidentally reprocesses the previous message

[Clint Adams]

On Fri, Feb 24, 2017 at 02:58:41AM +, Martin Dorey wrote:
> Now through early evening fog I see that the message queues and the semaphore 
> are being generated with a random key.  Collisions with existing keys aren't 
> detected.  I have a patch that I hope will detect that and retry.  Would you 
> like that here or in a new bug?  Including the first patch or assuming it's 
> applied first or against the baseline version?  Any way is easy for me.  I 
> imagine the BTS will just do the right thing with a text attachment but five 
> minutes of googling hasn't confirmed that's how to submit a patch to an 
> existing Debian bug.  Waiting a week for the patch to dis/prove itself would 
> be perfectly sensible, but I'm happy to embarrass myself if you're happy to 
> look at it before then.

A new bug is better since it's fixing a different thing, preferably based off of

https://anonscm.debian.org/cgit/users/clint/fakeroot.git/log/?id=refs/heads/upstream

, text attachments work fine, whenever you're ready.

Bug#784014: Feature wish: detox and non-existent files

[Doug Harple]

Hello,

Apologies for my very late reply.  Detox already supports this feature,
through a second binary, called inline-detox.  This works as a Unix stream,
taking input on stdin, and returning output on stdout.  So, in the simplest
case, you could do:

echo "Filename that needs to be (cleaned up).mp3" | inline-detox

and it will return:

Filename_that_needs_to_be-cleaned_up-.mp3

On stdout.

Hope that helps!

Doug Harple

-- Forwarded message --
From: Ari Moisio 
Date: 2015-04-23 11:02 GMT+02:00
Subject: Feature wish: detox and non-existent files
To: schoenf...@debian.org


Hi

May i suggesta new functionality on detox:

a new parameter,  for example -N that will pass the command line argument
thru defined sequence but does not care if the file exists and of course
will not try to rename it, olyn outputs  a cleaned filename to   the stdout.

I'm asking this for a CD ripping script   wwhere the filename comes from
cddb and i would like to pass already valid file name for the lame encoder.

Best regards
-- 
Terveisin
Ari Moisio
Atk-suunnittelija
Tiedonhallintapalvelut
Näkövammaisten Keskusliitto ry.
050 401 5875
ari.moi...@thp.nkl.fi

Bug#849077: [pkg-wpa-devel] Bug#849077: new version of wpa-supplicant uploaded -- please test

[Andrew Shadura]

Hi,

On 23 February 2017 at 19:37, Scott Mcdermott
 wrote:
> On Thu, 26 Jan 2017 18:36:08 +0100 Andrew Shadura  wrote:
>> I have cherry-picked a few patches from the upstream Git repository.
>
> I tried this on my mbpr 11,1 with wl.ko and still same result.  Scan failure
> in endless loop return -22 just like in my previously attached log dump.
>
>> Please test this version, ensuring you have the latest NM/wicd/whatever
>
> Again I'm NOT using NetworkManager, wicd or anything else.  Just
> wpa_supplicant with a dead simple configuration and an ordinary
> WAP.
>
> 2.5-2+v2.4-3+b1 is the last version that works.

Right. Please report this to the upstream at
hos...@lists.infradead.org. Please bear in mind "2.5-2+v2.4-3+b1" is,
in fact, 2.4, not 2.5, despite the confusing version number. I will
upload another update to 2.4 with a fix for another bug fixed in 2.5
soon. 2.6 will be available in experimental.

-- 
Cheers,
  Andrew

Bug#848895: Chromium freezes randomly

[Luke Kenneth Casson Leighton]

On Thu, Feb 23, 2017 at 9:41 PM, Ximin Luo  wrote:
> Luke Kenneth Casson Leighton:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=87
>>
>> now ain't that fascinating.  optirun combined with fvwm2 is a
>> sure-fire extremely fast and 100% *guaranteed* way to repro this
>> "freezing but you can ctrl-alt-f1 then ctrl-alt-f7 and it miraculously
>> all works whoopidoo" problem.
>>
>> [..]
>
> Hi,
>
> I am not sure if primus is the problem. I don't have it installed.

 primus is an example of another application, like the many other
applications, where this underlying bug occurs for reasons as yet
unresolved.  we may therefore logically deduce that it's not a
chromium bug *per se* but is something to do with the dependencies
and/or interaction with the dependencies.

 the fact that running glxgears (or in fact *any* application -
openscad, vlc, *anything*) under optirun results pretty much
immediately (i.e. within seconds or minutes) in this bug being
reproduced is itself fascinating and also a useful setup for working
out what the hell is going on.

> In fact when I had the bug (on chromium 55.0.2883.75-6) I was using the free 
> nouveau drivers, not the nvidia drivers.

 from scanning the various responses it seems not to matter precisely
which underlying GPU hardware is used.  you're using nvidia, or
nouveau, others have reported different GPUs: it's not the GPU
*itself* which is the problem.


> I am now using the nvidia drivers with the same chromium version, and I have 
> not seen the bug for a few days. But if you do see it with nvidia drivers, 
> then something else must be the actual problem.

 it's not chromium itself that is the problem.  i can run "optirun
glxgears" then move / resize the window and it freezes.  therefore we
*know* that it's going to reoccur with chromium.

> I haven't yet tried 56.0.2924.76-4 that Michael says is fixed. BTW he has 
> closed the bug report #848895, I did not get a notification about this and I 
> only noticed when visiting the bug report web page. If any of you can 
> reproduce the bug with version 56.0.2924.76-4 please let us know so we can 
> re-open the bug.

prediction with 95% confidence: you'll need to reopen the bug.  the
remaining 5%, if it *has* been "fixed" with some form of workaround,
it should be very well documented *exactly* how, so that other
software can deploy the exact same "fix".  also the xorg team can be
alerted as there might be something that they can do which stops this
(endemic) bug from affecting other applications.

remember it's *not* just chromium that's affected.


 root@fizzy:/home/lkcl# apt-get install chromium
Reading package lists... Done
Building dependency tree
Reading state information... Done
chromium is already the newest version (55.0.2883.75-6).

so it's not hit debian/testing yet.  i'll wait another week until it does.

l.

Bug#855985: (no subject)

[Michael Lustfield]

Control: retitle -1  golang-github-facebookgo-stack -- Stack provides utilities 
to capture and handle stack traces

I'm also aware the description needs to be improved.

-- 
Michael Lustfield

Bug#855984: ddd: support for trepan3k?

[Dale Harris]

Package: ddd
Version: 1:3.3.12-5.1
Severity: wishlist
Tags: upstream

Dear Maintainer,

Just tried using ddd with trepan3k which purports to be a gdb like
debugger, and debugs python3, which pydb does not.  I tried launching
with:

You can install trepan3k with pip3:

sudo pip3 install trepan3k xdis

ddd --debugger trepan3k 

No source gets displayed, and it only appears pydb is being loaded. 

More info on trepan3k at:

https://github.com/rocky/python3-trepan


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

Kernel: Linux 4.9.0-2-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)

Versions of packages ddd depends on:
ii  libc6   2.24-9
ii  libgcc1 1:6.3.0-8
ii  libstdc++6  6.3.0-8
ii  libtinfo5   6.0+20161126-1
ii  libx11-62:1.6.4-3
ii  libxaw7 2:1.0.13-1
ii  libxm4  2.3.4-13
ii  libxmu6 2:1.1.2-2
ii  libxpm4 1:3.5.12-1
ii  libxt6  1:1.1.5-1

Versions of packages ddd recommends:
ii  gdb  7.12-6

Versions of packages ddd suggests:
ii  cups-bsd [lpr]   2.2.1-8
pn  ddd-doc  
pn  glibc-doc
ii  gnuplot  5.0.5+dfsg1-5
ii  info 6.3.0.dfsg.1-1+b1
ii  openssh-client [rsh-client]  1:7.4p1-6
ii  perl 5.24.1-1
ii  pydb 1.26-2
ii  x11-utils7.7+3
ii  xterm327-2

-- no debconf information

-- 
Dale Harris   
rod...@maybe.org
rod...@gmail.com
/.-)

Bug#855943: Pending fixes for bugs in the shadow package

[pkg-shadow-devel]

tag 855943 + pending
thanks

Some bugs in the shadow package are closed in revision
bc6cd09194f3d289bbd1729260ae2869989e9182 in branch 'master' by Balint
Reczey

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-shadow/shadow.git/commit/?id=bc6cd09

Commit message:

su: properly clear child PID (CVE-2017-2616)

Closes: #855943

Bug#854792: fails when there are two users with the same UID

[Axel Beckert]

Dear Emilio,

Emilio Pozuelo Monfort wrote:
> > Summary: accounts-daemon.service fails to work properly when there are
> > two users in the system with the same UID.
[...]
> I'm not sure that's a system configuration that is supported.

it's a not seldom thing to have a second root account which is often
called toor as that's its common name in the BSD world, see
https://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/security.html#idp60124648

There are multiple reasons to do that:

* If the beginning of /etc/passwd is wrecked for some reason, the
  second root user at the end of the passwd can still login

* root usually has the default login shell. Some people do not want to
  change that but have a user with root permissions and their
  favourite interactive shell, e.g. tcsh or zsh.

* The second root account could also sport a less comfortable but
  statically compiled shell including some builtin commands (e.g.
  busybox-static or sash) for fixing the system with onboard tools if
  libc6 is broken for some reason.

Actually Debian's sash package even encouraged the admin via debconf
to create such a second root user (called sashroot). That feature
though has been removed from the sash package quite a while ago
(although I learned about this only now and was unpleasantly surprised
about that maintainer's move).

> If you shoot yourself in the foot, you should expect some
> problems...

Unfortunately it has been become very common in Debian recently to use
such arguments to get rid of unpleasant bugs.

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

Bug#855982: pydb: just found python3-trepan

[Dale Harris]

Package: pydb
Version: 1.26-2
Followup-For: Bug #855982

Dear Maintainer,

I found https://github.com/rocky/python3-trepan, that would seem to be
future path for python3 support. 


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

Kernel: Linux 4.9.0-2-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)

Versions of packages pydb depends on:
pn  python:any  

pydb recommends no packages.

Versions of packages pydb suggests:
ii  ddd  1:3.3.12-5.1
pn  emacs22  

-- no debconf information

-- 
Dale Harris   
rod...@maybe.org
rod...@gmail.com
/.-)

Bug#855982: pydb: support for Python3?

[Dale Harris]

Package: pydb
Version: 1.26-2
Severity: wishlist
Tags: upstream

Dear Maintainer,


Doesn't appear pydb supports python3. Do you know if upstream plans
to add this functionality? 


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

Kernel: Linux 4.9.0-2-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)

Versions of packages pydb depends on:
pn  python:any  

pydb recommends no packages.

Versions of packages pydb suggests:
ii  ddd  1:3.3.12-5.1
pn  emacs22  

-- no debconf information

-- 
Dale Harris   
rod...@maybe.org
rod...@gmail.com
/.-)

Bug#855981: ITP: golang-github-denisenkom-go-mssqldb -- Microsoft SQL server driver written in go language

[Michael Lustfield]

Package: wnpp
Severity: wishlist
Owner: Michael Lustfield 

* Package name: golang-github-denisenkom-go-mssqldb
  Version : 0.0~git20170117.0.9e40d9d-1
  Upstream Author : The Go Authors
* URL : https://github.com/denisenkom/go-mssqldb
* License : BSD-3-clause
  Programming Lang: Go
  Description : Microsoft SQL server driver written in go language

 A pure Go MSSQL driver for Go's database/sql package.
 .
 Features:
   * Can be used with SQL Server 2005 or newer
   * Can be used with Microsoft Azure SQL Database
   * Can be used on all go supported platforms (e.g. Linux, Mac OS X and
 Windows)
   * Supports new date/time types: date, time, datetime2, datetimeoffset
   * Supports string parameters longer than 8000 characters
   * Supports encryption using SSL/TLS
   * Supports SQL Server and Windows Authentication
   * Supports Single-Sign-On on Windows
   * Supports connections to AlwaysOn Availability Group listeners, including
 re-direction to read-only replicas.
   * Supports query notifications

This Go library is being packaged as a build dependency of gitea (a gogs fork).

-- 
Michael Lustfield


pgp_y_ygpl2xF.pgp
Description: OpenPGP digital signature

Bug#855980: xinit within X session causes black screen -> need to restart lightdm

[mviereck]

Package: xinit
Version: 1.3.4-3
Severity: normal

Dear Maintainer,

I'm used to run several X sessions from within already running X (Xorg, xpra, 
Xephyr, Xvfb, Xdummy) using xinit. 
Since X no longer is a setuid wrapper for Xorg (and /etc/X11/Xwrapper.config is 
gone), I cannot run Xorg on other ttys/vts 
with 'xinit xterm -- :1 vt8'. (With exception being logged in on tty1...tty6 
and running X with complying vt1...vt6)

If I run 'xinit xterm -- :1' without specifying a vt, Xorg trys to get 
tty7/vt0, fails, and left a black screen. 
The already running X session is unrecoverable, running applications, open 
documents etc. are lost. I have to restart lightdm.

A special situation is using an Xdummy configuration. I'm using a sample 
xorg.conf from xpra (attached to end of this report).
I can run it with 'xinit xterm -- /usr/bin/Xorg :100 -config 
/etc/xpra/xorg.conf'. Everything is fine until I terminate xterm,
then I get a black screen too, with some damaged session login messages. 

Same issue with startx as it uses xinit.

I expect at least an error message and a furthermore working X session instead 
of a blue, err, black screen. 
I wish the possibility to run 'xinit xterm -- :1 vt8' as it was possible in 
debian 8. (Without regression using xserver-xorg-legacy)

Thanks for your great work on debian!


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

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

Versions of packages xinit depends on:
ii  coreutils   8.26-2
ii  libc6   2.24-9
ii  libx11-62:1.6.4-3
ii  x11-common  1:7.7+18
ii  xauth   1:1.0.9-1

Versions of packages xinit recommends:
ii  compiz [x-window-manager] 1:0.9.13.0+16.10.20160818.2-4
ii  kwin-x11 [x-window-manager]   4:5.8.4-1
ii  metacity [x-window-manager]   1:3.22.1-1
ii  xfce4-session [x-session-manager] 4.12.1-5
ii  xfce4-terminal [x-terminal-emulator]  0.8.3-1
ii  xfwm4 [x-window-manager]  4.12.3-3
ii  xserver-xephyr [xserver]  2:1.19.1-4
ii  xserver-xorg [xserver]1:7.7+18
ii  xterm [x-terminal-emulator]   327-2
ii  xvfb [xserver]2:1.19.1-4

xinit suggests no packages.

-- no debconf information


xorg.conf for Xdummy (/etc/xpra/xorg.conf):

# This xorg configuration file is meant to be used by xpra
# to start a dummy X11 server.
# For details, please see:
# https://xpra.org/Xdummy.html

Section "ServerFlags"
  Option "DontVTSwitch" "true"
  Option "AllowMouseOpenFail" "true"
  Option "PciForceNone" "true"
  Option "AutoEnableDevices" "false"
  Option "AutoAddDevices" "false"
EndSection

Section "Device"
  Identifier "dummy_videocard"
  Driver "dummy"
  DacSpeed 600
  Option "ConstantDPI" "true"
  #VideoRam 2048000
  #VideoRam 1024000
  #VideoRam 384000
  VideoRam 256000
  #VideoRam 192000
EndSection

Section "Monitor"
  Identifier "dummy_monitor"
  HorizSync   1.0 - 2000.0
  VertRefresh 1.0 - 200.0
  #To add your own modes here, use a modeline calculator, like:
  # cvt:
  # http://www.x.org/archive/X11R7.5/doc/man/man1/cvt.1.html
  # xtiming:
  # http://xtiming.sourceforge.net/cgi-bin/xtiming.pl
  # gtf:
  # http://gtf.sourceforge.net/

  #This can be used to get a specific DPI, but only for the default resolution:
  #DisplaySize 508 317
  #NOTE: the highest modes will not work without increasing the VideoRam
  # for the dummy video card.
  #Modeline "16000x15000" 300.00  16000 16408 18000 2  15000 15003 15013 
15016
  #Modeline "15000x15000" 281.25  15000 15376 16872 18744  15000 15003 15013 
15016
  #Modeline "16384x8192" 167.75  16384 16800 18432 20480  8192 8195 8205 8208
  #Modeline "15360x8640" 249.00 15360 15752 17280 19200 8640 8643 8648 8651
  Modeline "8192x4096" 193.35 8192 8224 8952 8984 4096 4196 4200 4301
  Modeline "7680x4320" 208.00 7680 7880 8640 9600 4320 4323 4328 4335
  Modeline "6400x4096" 151.38 6400 6432 7000 7032 4096 4196 4200 4301
  Modeline "6400x2560" 91.59 6400 6432 6776 6808 2560 2623 2626 2689
  Modeline "6400x2160" 160.51 6400 6432 7040 7072 2160 2212 2216 2269
  Modeline "5760x2160" 149.50 5760 5768 6320 6880 2160 2161 2164 2173  
  Modeline "5680x1440" 142.66 5680 5712 6248 6280 1440 1474 1478 1513
  Modeline "5496x1200" 199.13 5496 5528 6280 6312 1200 1228 1233 1261
  Modeline "5280x2560" 75.72 5280 5312 5592 5624 2560 2623 2626 2689
  Modeline "5280x1920" 56.04 5280 5312 5520 5552 1920 1967 1969 2017
  Modeline "5280x1200" 191.40 5280 5312 6032 6064 1200 1228 1233 1261
  Modeline "5280x1080" 169.96 5280 5312 5952 5984 1080 1105 1110 1135
  Modeline "5120x3200" 199.75 5120 5152 5904 5936 3200 3277 3283 3361
  Modeline "5120x2560" 73.45 5120 5152 5424 5456 2560 2623 2626 2689
  Modeline "5120x2880" 185.50 5120 5256 5760 6400 2880 2883 2888 2899
  Modeline "4800x1200" 64.42 

Bug#855073: qbittorrent: Data Loss after reboot

[Frédéric Brière]

On Tue, Feb 14, 2017 at 09:01:01AM +0500, Khurram Mahmood wrote:
> *HiIn my case I think the force recheck didnt do any good.

(Sorry for the delay.)

A recheck alone will not suffice; qBittorrent is no longer looking in
the right location, so it assumes all files are now missing.

> *Kindly explain:
> "manually rename the directory to whatever libtorrent is expecting".

Once qBittorrent has begun re-downloading the files, it will create them
at their new location.  Simply replace them with the old (good) copies,
and qBittorrent will be happy again.


For example, let's say you have two (100% complete) torrents: one with
files under "Something/", and one with files under "Something else/".
After restarting qBittorrent, the "Something else" torrent is now at 0%.

Once that torrent has begun downloading again, you will notice that
qBittorrent has started creating files under "Something/else/" instead.
(Notice the extra directory level.)  This is where qBittorrent is now
looking, therefore this is where you want to relocate the files.

Pause the torrent, delete the new (0%) directory, move the old one to
this location, and force a recheck.

> *I changed the location via set location, but to no avail.*

Note that if you attempt to correct the location by setting it back to
its previous value, you will most likely trigger that bug again.  It's
probably easiest to not struggle, and simply accept the new location of
your files.  :)

(Once that bug is fixed, you could always delete and re-add the torrent,
renaming the files back to their old location.)

Bug#855621: docker.io: Doesn't start: bad listen address format

[Potter, Tim]

On 21 Feb 2017, at 7:48 AM, Samuel Thibault  wrote:
> 
> Samuel Thibault, on lun. 20 févr. 2017 21:37:11 +0100, wrote:
>> Samuel Thibault, on lun. 20 févr. 2017 21:30:58 +0100, wrote:
>>> 2017-02-20T21:29:05.031246+01:00 var docker[4807]: 
>>> time="2017-02-20T21:29:05.030971938+01:00" level=info msg="New containerd 
>>> process, pid: 4822\n"
>>> 2017-02-20T21:29:05.046488+01:00 var docker[4807]: 
>>> time="2017-02-20T21:29:05.046388294+01:00" level=fatal msg="bad listen 
>>> address format /var/run/docker/libcontainerd/docker-containerd.sock, 
>>> expected proto://address"
>> 
>> I found this:
>> 
>> https://patrick.georgi.family/2017/02/18/bad-listen-address-format-docker-error-on-debian-and-elsewhere/
>> 
>> which I'll use as workaround (it seems to work fine here),
> 
> I spoke too fast, I'm getting other incompatibilities. I had to
> downgrade containerd.

Hi Samuel.  I'm afraid I messed up by uploading containerd, libnetwork and runc 
to unstable and the
appropriate Docker version (1.13) to experimental which is why you are seeing 
this problem.  Next
time I'll make sure to upload all four packages to the same place.

I've just re-uploaded containerd, libnetwork and runc with Breaks lines in 
place to ensure that this
doesn't happen during the 1.13 upload process.

As you mention downgrading fixes things.  You might like to also downgrade runc 
and libnetwork
just to be safe.


Regards,

Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#855407: docker.io: Dependency missmatch (docker.io 1.11.2~ds1-6 vs. containerd 0.2.3~git20161117.78.03e5862~ds1-1)

[Potter, Tim]

Hi Roland.  I messed up by uploading containerd (as well as runc and 
libnetwork) to unstable
while uploading the matching Docker package to experimental.

If you downgrade to the original containerd, runc and libnetwork you should see 
the
problem disappear.  I've done a new upload adding Break lines to avoid this 
happening
until Docker 1.13 hits unstable.


Regards,

Tim.

> On 18 Feb 2017, at 2:36 AM, Roland Kammerer  wrote:
> 
> Package: docker.io
> Version: 1.11.2~ds1-6
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> After the upgrade docker does not start anymore. Starting it manually produces
> the following output:
> 
> sudo docker daemon --debug
> DEBU[] docker group found. gid: 125
> DEBU[] Listener created for HTTP on unix (/var/run/docker.sock)
> INFO[] New containerd process, pid: 15658
> 
> DEBU[] containerd connection state change: CONNECTING
> DEBU[] containerd connection state change: TRANSIENT_FAILURE
> WARN[] containerd: low RLIMIT_NOFILE changing to max  current=1024 
> max=65536
> DEBU[] containerd: read past events  count=0
> DEBU[] containerd: supervisor runningcpus=4 memory=7826
> runtime=runc runtimeArgs=[] stateDir="/run/containerd"
> FATA[] bad listen address format
> /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address
> 
> This is caused by a very well known mismatch between docker and containerd of
> current sid. See for example [1].
> 
> [1] https://github.com/docker/containerd/issues/299#issuecomment-240618355
> 
> -- System Information:
> Debian Release: 9.0
>  APT prefers testing
>  APT policy: (650, 'testing'), (600, 'unstable'), (550, 'experimental'), 
> (500, 'testing-debug')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages docker.io depends on:
> ii  adduser  3.115
> ii  containerd   0.2.3~git20161117.78.03e5862~ds1-1
> ii  init-system-helpers  1.47
> ii  iptables 1.6.0+snapshot20161117-5
> ii  libapparmor1 2.11.0-2
> ii  libc62.24-9
> ii  libdevmapper1.02.1   2:1.02.137-1
> ii  libsqlite3-0 3.16.2-2
> ii  libsystemd0  232-15
> ii  runc 0.1.1+dfsg1-2
> 
> Versions of packages docker.io recommends:
> ii  ca-certificates  20161130
> ii  cgroupfs-mount   1.3
> ii  git  1:2.11.0-2
> ii  xz-utils 5.2.2-1.2
> 
> Versions of packages docker.io suggests:
> pn  aufs-tools   
> pn  btrfs-progs  
> ii  debootstrap  1.0.88
> pn  docker-doc   
> pn  rinse
> pn  zfs-fuse | zfsutils  
> 
> -- Configuration Files:
> /etc/default/docker changed:
> DOCKER_OPTS="--storage-driver=devicemapper -H unix:///var/run/docker.sock"
> 
> 
> -- no debconf information
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#855922: [pkg-go] Bug#855922: containerd: 0.2.3 ds1-1 breaks docker 1.11 - unable to start containerd

[Potter, Tim]

On 24 Feb 2017, at 12:25 AM, Ricardo Sateler  wrote:
> 
> Package: containerd
> Version: 0.2.3~git20161117.78.03e5862~ds1-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> After upgrading containerd from 0.2.1~ds1-3 to
> 0.2.3~git20161117.78.03e5862~ds1-1, docker service does not start correctly
> (hangs).

> Downgrading containerd to 0.2.1-ds1-3 fixes the issue

Hi Ricardo.  Thanks for the bug report.  I messed up by uploading some of the 
Docker 1.13
dependencies to unstable instead of experimental - my apologies.

I've done a new upload with a Breaks line to avoid this bug occurring until I 
finish testing
1.13 and uploading to unstable.


Regards,

Tim.

> 
> 
> 
> -- System Information:
> Debian Release: 9.0
>  APT prefers unstable
>  APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages containerd depends on:
> ii  libc6  2.24-9
> ii  runc   0.1.1+dfsg1-2
> 
> containerd recommends no packages.
> 
> containerd suggests no packages.
> 
> -- no debconf information
> 
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#855979: detox: New upstream homepage and email address

[Joao Eriberto Mota Filho]

Package: detox
Severity: minor

This is a remind about some new information about detox.

Detox has a new homepage, at https://github.com/dharple/detox

The current upstream email addresses are detox.dhar...@gmail.com
and dhar...@gmail.com.

Eriberto

Bug#855978: fdroidserver: Depend on default-jdk-headless instead of default-jdk

[Paride Legovini]

Package: fdroidserver
Severity: wishlist

Dear Maintainer,

Is it possible to Depend: on the headless version of the JDK, instead of
depending on the full one? The GUI part should not be needed to build
apps, and it's unconveninet to install all the graphic libraries on a
headless server.

Thank you,

Paride

Bug#755911: Python3 version

[Diane Trout]

I updated the package to use upstream version 0.10.5, pybuild and build
a python3 version. (0.10.2 had an error)

Attached are the changes I made (minus the patch importing the new
version from upstream).

I can push the changes to alioth and make a new release, but I don't
like changing packages I'm not normally responsible for with out some
acknowledgement.

DianeFrom 9edf66eaa3d609aaae5f8d6d44c0958ba58c63b8 Mon Sep 17 00:00:00 2001
From: Diane Trout 
Date: Thu, 23 Feb 2017 14:09:45 -0800
Subject: [PATCH 2/6] New upstream version 0.10.5

---
 debian/changelog | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index fa5cd33..c579640 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,4 +1,4 @@
-rope (0.10.2-2) UNRELEASED; urgency=low
+rope (0.10.5-1) UNRELEASED; urgency=low
 
   [ Arnaud Fontaine ]
   * d/source/options: Ignore .egg-info directory.
@@ -6,6 +6,9 @@ rope (0.10.2-2) UNRELEASED; urgency=low
   [ Ondřej Nový ]
   * Fixed VCS URL (https)
 
+  [ Diane Trout ]
+  * New upstream version 0.10.5
+
  -- Arnaud Fontaine   Fri, 18 Jul 2014 10:45:28 +0900
 
 rope (0.10.2-1) unstable; urgency=low
-- 
2.11.0

From 9940a80fc9c91307526f488a78c91e39a9a3ea12 Mon Sep 17 00:00:00 2001
From: Diane Trout 
Date: Thu, 23 Feb 2017 14:14:48 -0800
Subject: [PATCH 3/6] Build a python3 version using pybuild

Update to debhelper 10
Add dh-python to build-depends
Add Python 3 & setuptools to build-depends
---
 debian/changelog |  5 +
 debian/compat|  2 +-
 debian/control   | 29 -
 debian/copyright |  1 +
 debian/rules |  7 ---
 5 files changed, 35 insertions(+), 9 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index c579640..a6f0dca 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -8,6 +8,11 @@ rope (0.10.5-1) UNRELEASED; urgency=low
 
   [ Diane Trout ]
   * New upstream version 0.10.5
+  * Build a python3 version using pybuild
++ Update to debhelper 10
++ Add dh-python to build-depends
++ Add Python 3 & setuptools to build-depends
++ Remove cdbs
 
  -- Arnaud Fontaine   Fri, 18 Jul 2014 10:45:28 +0900
 
diff --git a/debian/compat b/debian/compat
index 7f8f011..f599e28 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-7
+10
diff --git a/debian/control b/debian/control
index 4fe596c..af7fc52 100644
--- a/debian/control
+++ b/debian/control
@@ -3,10 +3,14 @@ Section: devel
 Priority: optional
 Maintainer: Arnaud Fontaine 
 Uploaders: Debian Python Modules Team 
-Build-Depends: cdbs (>= 0.4.90~),
-   debhelper (>= 7.0.0),
-   python (>= 2.6.6-3~)
-X-Python-Version: >= 2.5
+Build-Depends: debhelper (>= 10),
+   dh-python,
+   python-all (>= 2.6.6-3~),
+   python-setuptools,
+   python3-all,
+   python3-setuptools
+X-Python-Version: >= 2.6
+X-Python3-Version: >= 3.2
 Standards-Version: 3.9.5
 Vcs-Git: https://anonscm.debian.org/git/python-modules/packages/rope.git
 Vcs-Browser: https://anonscm.debian.org/cgit/python-modules/packages/rope.git
@@ -19,7 +23,7 @@ Depends: ${python:Depends},
 Recommends: python-svn,
 mercurial,
 git-core
-Description: Python refactoring library
+Description: Python 2 refactoring library
  Rope is a Python refactoring library that can be used with several editors
  and IDEs. It provides many refactoring operations as well as forms of code 
  assistance like auto-completion and access to documentation. To make use of 
@@ -28,3 +32,18 @@ Description: Python refactoring library
  . 
  In Debian, this package is used by the Python-ropemacs package, an Emacs mode 
  that adds Python refactoring and IDE features to the Emacs editor.
+ .
+ This provides the Python 2 version of the library.
+
+Package: python3-rope
+Architecture: all
+Depends: ${misc:Depends}, ${python:Depends}
+Recommends: git-core, mercurial, python3-svn
+Description: Python 3 refactoring library
+ Rope is a Python refactoring library that can be used with several editors
+ and IDEs. It provides many refactoring operations as well as forms of code
+ assistance like auto-completion and access to documentation. To make use of
+ refactoring in Mercurial, Git and Svn repositories, the recommended packages
+ must be installed. For a complete list of features, see the project homepage.
+ .
+ This provides the Python3 version of the library.
diff --git a/debian/copyright b/debian/copyright
index 9c2ac77..7fa96ea 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -10,6 +10,7 @@ License: GPL-2+
 Files: debian/*
 Copyright: 2008-2014 David Spreen 
2014 Arnaud Fontaine 
+   2016 Diane Trout 
 License: GPL-2+
 
 License: GPL-2+
diff --git a/debian/rules b/debian/rules
index 

Bug#832170: Pending fixes for bugs in the shadow package

[pkg-shadow-devel]

tag 832170 + pending
thanks

Some bugs in the shadow package are closed in revision
dd729b3572a957a12d83d3f1549ea05e1d269839 in branch '  jessie' by
Balint Reczey

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-shadow/shadow.git/commit/?id=dd729b3

Commit message:

Fix integer overflow in getulong.c (CVE-2016-6252)

Closes: #832170

Bug#855943: Pending fixes for bugs in the shadow package

[pkg-shadow-devel]

tag 855943 + pending
thanks

Some bugs in the shadow package are closed in revision
1edacbf29a564b64282b09f0a3a37dd654e3a743 in branch '  jessie' by
Salvatore Bonaccorso

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-shadow/shadow.git/commit/?id=1edacbf

Commit message:

su: properly clear child PID

Closes: #855943

Bug#855977: evince: hyperlinks not clickable - feature request: automatic links

[Petr Vanek]

Package: evince
Version: 3.22.1-3
Severity: wishlist



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

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

Versions of packages evince depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  evince-common3.22.1-3
ii  gsettings-desktop-schemas3.22.0-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-9
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libevdocument3-4 3.22.1-3
ii  libevview3-3 3.22.1-3
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-1
ii  libgnome-desktop-3-123.22.2-1
ii  libgtk-3-0   3.22.8-1
ii  libnautilus-extension1a  3.22.2-1
ii  libpango-1.0-0   1.40.3-3
ii  libsecret-1-00.18.5-2
ii  shared-mime-info 1.8-1

Versions of packages evince recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.10.16-1
ii  dbus-x11 [dbus-session-bus]   1.10.16-1

Versions of packages evince suggests:
ii  gvfs 1.30.3-1
pn  nautilus-sendto  
ii  poppler-data 0.4.7-8
ii  unrar1:5.4.5-1

-- debconf-show failed


Thank you for all your hard work.

I have been using Evince for years and am happy with it, but for
whatever reason, it doesn't make links clickable in my own created
documents, see example here: http://www.penguin.cz/~vanous/out.pdf - the
numbers in circles have hyperlinks underneath.

Acrobat reader (acroread) achieves this by what they call "automatic
links", where not only Annotations with subtype /Link are processed as
links but also FQ URLs and PQ URLs are recognized, please see some
description here: [1]

[1] 
https://blogs.adobe.com/acrolaw/2013/03/removing-hyperlinks-from-a-pdf-and-featuregotcha/

I have reported/discussed this in poppler mailing list [2] and it was suggested 
to report here, as
Debian Evince bug/feature request.

[2] https://lists.freedesktop.org/archives/poppler/2017-February/012082.html

Thank you for all your work on keeping Evince in Debian!

cheers
--
Petr

Bug#855945: pyfg: no tests discovered

[Vincent Bernat]

 ❦ 23 février 2017 18:08 -0500, Sandro Tosi  :

>> pybuild tries to run tests unconditionnaly. I don't really want to add
>> code in debian/rules just to skip tests.
>
> funny you did that in napalm-iosxr: export PYBUILD_DISABLE=test

There are tests and they require some virtual machine to run.
-- 
If two people love each other, there can be no happy end to it.
-- Ernest Hemingway


signature.asc
Description: PGP signature

Bug#855945: pyfg: no tests discovered

[Sandro Tosi]

On Thu, Feb 23, 2017 at 12:19 PM, Vincent Bernat  wrote:
> pybuild tries to run tests unconditionnaly. I don't really want to add
> code in debian/rules just to skip tests.

funny you did that in napalm-iosxr: export PYBUILD_DISABLE=test


-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#855976: [Patch] In os-prober script in /etc/grub.d/, better detection of other Linux OS partitions' codename & kernel version

[dg1727]

Package: grub-common
Version: 2.02~beta2-22+deb8u1

Scenario:
* Say the Debian-derived Linux OS from which "update-grub" is run is "A".
* Say another Linux OS on the same hard drive is "B".
* Say "B" has multiple kernel versions (when each version was installed, the
previous one wasn't deleted).

In this case, GRUB2 makes a submenu for the available kernels in B, plus a main-
menu entry for one of those kernels. That is expected.

The problem is that, in my testing, the submenu looked like:

Ubuntu XX.YY (XX.YY)
Ubuntu XX.YY (XX.YY)
Ubuntu XX.YY (XX.YY)
Ubuntu XX.YY (XX.YY)

... where XX was the same in every menu entry (*including the main-menu
entry*), and YY was also the same. There was no way to tell which menu entry
would start which kernel version. In fact, I believe the kernel versions were
sorted backward, so that the main-menu entry started the *oldest* available
kernel version of B, whereas a user would expect the main-menu entry to start
the newest available kernel of B.

The following patch fixed this in my testing. Please consider adding this
patch (or a modified version of it, if bugs are found in this patch) to GRUB2.

For my testing, I renamed the os-prober script from 30_os-prober to
15_os-prober, because I wanted the OS boot options to be before memtest86+. In
the diff, the name difference indicates the original vs. modified files:

30_os-prober = existing file in Debian package
15_os-prober = my modified file

--- 30_os-prober 2015-12-14 12:37:32.0 -0500
+++ 15_os-prober 2017-02-23 17:28:47.692140837 -0500
@@ -27,6 +27,9 @@

. "${datarootdir}/grub/grub-mkconfig_lib"

+safe_echo () { printf %s\\n "$*" ; }
+# from http://www.etalabs.net/sh_tricks.html
+
found_other_os=

adjust_timeout () {
@@ -232,6 +235,11 @@
title_correction_code=
OS="${LONGNAME}"

+ LINUXPROBED=$(safe_echo "${LINUXPROBED}" | tr " " "\n" | \
+ sort -t ":" -k 4 -rV | tr "\n" " ")
+ # Try to sort the kernels with the newest first, so the newest one will
+ # be the default.
+
for LINUX in ${LINUXPROBED} ; do
LROOT="`echo ${LINUX} | cut -d ':' -f 1`"
LBOOT="`echo ${LINUX} | cut -d ':' -f 2`"
@@ -254,6 +262,68 @@
[ "${prepare_boot_cache}" ] || continue
fi

+LSB_QUERY_MOUNT_POINT=$(findmnt -flno TARGET ${DEVICE})
+
+if [ -z "${LSB_QUERY_MOUNT_POINT}" ] ; then
+ LSB_QUERY_MOUNT_POINT=$(mktemp -d)
+ mount ${DEVICE} ${LSB_QUERY_MOUNT_POINT}
+ TEMP_MOUNT="true"
+ # It appears that this code doesn't run: Although syslog indicates that
+ # /usr/lib/os-probes/mounted/40lsb indeed scans unmounted partitions, it
+ # seems that /usr/bin/os-prober (which is indirectly the parent process of
+ # "40lsb") still doesn't report any OS that exists on such a partition. The
+ # partition tested was formatted as btrfs.
+else
+ TEMP_MOUNT="false"
+fi
+
+LSB_DATABASE=${LSB_QUERY_MOUNT_POINT}/etc/lsb-release
+
+LCODENAME=$(grep ^DISTRIB_CODENAME ${LSB_DATABASE} | cut -d "=" -f 2)
+LDESC=$(grep ^DISTRIB_DESCRIPTION ${LSB_DATABASE} | cut -d "=" -f 2)
+
+if [ ${TEMP_MOUNT} = true ] ; then
+ # not "x${TEMP_MOUNT}=xtrue", because ${TEMP_MOUNT} is known to have a value
+ umount ${LSB_QUERY_MOUNT_POINT}
+fi
+
+if safe_echo "${LDESC}" | egrep "^(['\"]).*\1$" >/dev/null; then
+ LDESC=$(safe_echo "${LDESC}" | cut -c 2- | rev | cut -c 2- | rev)
+fi # If ${LDESC} is quoted, then remove the quote marks.
+
+LKERNEL_DISPLAY=$(safe_echo "${LKERNEL}" | cut -d "-" -f 2-)
+# Try to extract the version number of the kernel image file.
+
+name_to_compare () { echo "${1}" | tr -c "[:alpha:]" " " | tr -s " " | \
+ tr "[:upper:]" "[:lower:]" | \
+ sed "s/[ ]\+$//" ; }
+# Convert all non-letters in ${1} to spaces.
+# Convert multiple consecutive spaces to single spaces.
+# Convert all uppercase letters to lowercase.
+# Then remove trailing spaces if present
+# (sed "s/ $//" doesn't seem to work for this).
+# We do these things so an LCODENAME of "betsy" will be detected at the end of
+# an LDESC of "LMDE 2 (Betsy)", but not in an LDESC of "LMDE blah b_e.t-s.y"
+
+LDESC_CMP=$(name_to_compare "${LDESC}")
+LCODENAME_CMP=$(name_to_compare "${LCODENAME}")
+
+if safe_echo "${LDESC_CMP}" | egrep "${LCODENAME_CMP}$" >/dev/null; then
+ # ${LDESC} ends in ${LCODENAME}.
+ OS_SUBMENU="${LDESC}"
+else
+ # ${LDESC} doesn't end in ${LCODENAME}.
+ OS_SUBMENU="${LDESC} \"${LCODENAME}\""
+fi
+
+OS="${OS_SUBMENU}, with Linux kernel ${LKERNEL_DISPLAY}"
+# Examples:
+# LMDE 2 Betsy, with Linux kernel 3.16.0-4-amd64
+# (if codename is "betsy" & description ends in "Betsy")
+# Ubuntu 13.04 "raring", with Linux kernel 3.8.0-35-generic
+
+printf "Adding '%s' to menu\n" "${OS}" >&2
+
found_other_os=1
onstr="$(gettext_printf "(on %s)" "${DEVICE}")"
recovery_params="$(echo "${LPARAMS}" | grep 'single\|recovery')" || true
@@ -283,10 +353,11 @@
cat << EOF
}
EOF
- echo "submenu '$(gettext_printf "Advanced options for %s" "${OS} $onstr" | 
grub_quote)' \$menuentry_id_option 'osprober-gnulinux-advanced-$boot_device_id' 
{"
+ echo "submenu '$(gettext_printf "Advanced options for %s" "${OS_SUBMENU} 

Bug#853886: cowbuilder: doesn't create _amd64.changes for binary-indep-only or source-only builds

[James Clarke]

On 23 Feb 2017, at 22:51, Thorsten Glaser  wrote:
> 
> James Clarke dixit:
> 
>> Why not use --source-only-changes and upload the _source.changes from
>> your final test binary build?
> 
> This is actually required; uploading it as _amd64.changes will
> prevent the buildds from uploading amd64 binaries, as the changes
> file will already be present in the distribution. (BTDT, oops.)

Maybe that used to be true, but it definitely isn't any more.

Regards,
James

Bug#853886: cowbuilder: doesn't create _amd64.changes for binary-indep-only or source-only builds

[Thorsten Glaser]

James Clarke dixit:

>Why not use --source-only-changes and upload the _source.changes from
>your final test binary build?

This is actually required; uploading it as _amd64.changes will
prevent the buildds from uploading amd64 binaries, as the changes
file will already be present in the distribution. (BTDT, oops.)

bye,
//mirabilos
-- 
Stéphane, I actually don’t block Googlemail, they’re just too utterly
stupid to successfully deliver to me (or anyone else using Greylisting
and not whitelisting their ranges). Same for a few other providers such
as Hotmail. Some spammers (Yahoo) I do block.

Bug#855975: reprepro should generate SHA512 fields

[Jason Self]

Package: reprepro
Version: 4.13.1-1build1
Severity: wishlist

It appears that sha512 is allowed in a repository: 
https://wiki.debian.org/RepositoryFormat

reprepro should support this and generate appropriate sha512 fields.

Bug#855974: ITP: vibe.d -- High-performance asynchronous I/O web application toolkit

[Matthias Klumpp]

Package: wnpp
Severity: wishlist
Owner: Matthias Klumpp 

* Package name: vibe.d
  Version : 0.7.30
  Upstream Author : rejectedsoftware e.K.
* URL : http://vibed.org/
* License : MIT
  Programming Lang: D
  Description : High-performance asynchronous I/O web application toolkit

vibe.d is a high-performance asynchronous I/O, concurrency and web
application toolkit written in D. It already contains many supplemental
features such as database support to be able to offer a complete
development environment.

The packaging is done under the D team umbrella at
https://anonscm.debian.org/git/pkg-d/vibe.d.git

Bug#855973: reportbug: Add danish translation to desktop file

[scootergrisen]

Package: reportbug
Version: 7.1.5
Severity: wishlist
Tags: patch

I would like to add danish translation to the reportbug desktop file.

Maybe this is not the correct way to do it but here it is:

[Desktop Entry]
Type=Application
Name=Reportbug
Name[da]=Reportbug
Name[ru]=Reportbug
Name[zh_CN]=报告漏洞
Comment=Report bugs to the Debian BTS
Comment[da]=Rapportér fejl til Debian fejlrapporteringssystem
Comment[ru]=Создание и отправка отчёта об ошибке в Debian BTS
Comment[zh_CN]=向 Debian 缺陷跟踪系统报告漏洞
GenericName=Debian bug reporting tool
GenericName[da]=Debian fejlrapporteringsværktøj
GenericName[ru]=Отчёт об ошибке Reportbug
GenericName[zh_CN]=Debian 缺陷报告工具
X-GNOME-FullName[da]=Debian fejlrapporteringsværktøj
X-GNOME-FullName[ru]=Отчёт об ошибке Reportbug
X-GNOME-FullName[zh_CN]=Debian 缺陷报告工具
Icon=debian-swirl
TryExec=reportbug
Exec=reportbug --exit-prompt --ui gtk2
Categories=System;
Keywords=Debian;Bug;Bugs;BTS;
Keywords[da]=Debian;Bug;Bugs;BTS;Fejlrapporteringssystem;Fejl;
Keywords[zh_CN]=漏洞;报告;缺陷;



-- Package-specific info:
** Environment settings:
INTERFACE="gtk2"

** /home/scootergrisen/.reportbugrc:
reportbug_version "6.6.3"
mode standard
ui gtk2
email "scootergri...@gmail.com"
no-cc
header "X-Debbugs-CC: scootergri...@gmail.com"
smtphost reportbug.debian.org

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

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

Versions of packages reportbug depends on:
ii  apt1.4~rc1
ii  python3-reportbug  7.1.5
pn  python3:any

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
pn  debconf-utils  
ii  debsums2.2
pn  dlocate
pn  emacs23-bin-common | emacs24-bin-common
ii  exim4  4.88-5
ii  exim4-daemon-light [mail-transport-agent]  4.88-5
ii  file   1:5.29-3
ii  gir1.2-gtk-3.0 3.22.7-2
ii  gir1.2-vte-2.910.46.1-1
ii  gnupg  2.1.18-3
ii  python3-gi 3.22.0-2
ii  python3-gi-cairo   3.22.0-2
pn  python3-gtkspellcheck  
ii  python3-urwid  1.3.1-2+b1
ii  xdg-utils  1.1.1-1

Versions of packages python3-reportbug depends on:
ii  apt1.4~rc1
ii  file   1:5.29-3
ii  python3-debian 0.1.30
ii  python3-debianbts  2.6.1
ii  python3-requests   2.12.4-1
pn  python3:any

python3-reportbug suggests no packages.

-- no debconf information
--- reportbug.desktop.o 2017-02-21 20:36:55.996894741 +0100
+++ reportbug.desktop   2017-02-21 20:41:55.372908065 +0100
@@ -1,14 +1,18 @@
 [Desktop Entry]
 Type=Application
 Name=Reportbug
+Name[da]=Reportbug
 Name[ru]=Reportbug
 Name[zh_CN]=报告漏洞
 Comment=Report bugs to the Debian BTS
+Comment[da]=Rapportér fejl til Debian fejlrapporteringssystem
 Comment[ru]=Создание и отправка отчёта об ошибке в Debian BTS
 Comment[zh_CN]=向 Debian 缺陷跟踪系统报告漏洞
 GenericName=Debian bug reporting tool
+GenericName[da]=Debian fejlrapporteringsværktøj
 GenericName[ru]=Отчёт об ошибке Reportbug
 GenericName[zh_CN]=Debian 缺陷报告工具
+X-GNOME-FullName[da]=Debian fejlrapporteringsværktøj
 X-GNOME-FullName[ru]=Отчёт об ошибке Reportbug
 X-GNOME-FullName[zh_CN]=Debian 缺陷报告工具
 Icon=debian-swirl
@@ -16,4 +20,5 @@
 Exec=reportbug --exit-prompt --ui gtk2
 Categories=System;
 Keywords=Debian;Bug;Bugs;BTS;
+Keywords[da]=Debian;Bug;Bugs;BTS;Fejlrapporteringssystem;Fejl;
 Keywords[zh_CN]=漏洞;报告;缺陷;

Bug#851060: New dsniff revision

[Marcos Fouces]

Hi James,


El 23/02/17 a las 12:57, James Cowgill escribió:

Hi,

On 22/02/17 23:16, Marcos Fouces wrote:

Hello

I uploaded to repo a first attempt of libnids1.24 package wich aims to
close its two critical bugs:

#855602: fixed upstream in 1.24 release.

As I wrote in the bugreport, the fix applied by upstream is not enough
to fix this. You also need to apply the patch from Fedora otherwise
dsniff will FTBFS on i386.


I applied the patch you mentioned and after a rebuild of dsniff and 
libnids, it still seems to work properly at least on amd64


Please, check it:

https://anonscm.debian.org/cgit/pkg-security/libnids.git



#851060: i tried using -fno-strict-aliasing flag as reporter indicates.
I didn't noticed any change on my amd64, but he talked about armhf arch.

I built dsniff (1) against this new version of libnids-dev (2) and here
is the result:

* Run dsniff

* Run the same test as bug reporter: curl -v --basic --user foo:bar
http://neverssl.com/

dsniff says this:

dsniff: listening on eth0
-
02/22/17 23:56:32 tcp 192.168.1.3.47942 ->
s3-website-us-west-2.amazonaws.com.80 (http)
GET / HTTP/1.1
Host: neverssl.com
Authorization: Basic Zm9vOmJhcg== [foo:bar]

So interestingly, after recompiling your new versions of both libnids
and dsniff, things start working again. I'm not sure what happened
before when I couldn't get anything to work.

I really don't know, i couldn' t reproduce this bug at any time.


(1) https://anonscm.debian.org/cgit/pkg-security/dsniff.git

For stretch, I don't think dsniff needs to be changed.


(2) https://anonscm.debian.org/cgit/pkg-security/libnids.git

At the moment Debian is frozen and you've made a number of changes here
which are not sutible for the freeze. These include:
- Packaging a new version of libnids.
- Breaking the ABI of libnids.
- Bumping debhelper compat

For stretch, the fixes need to be targeted so as to only change as much
stuff as necessary to fix the two RC bugs.


I am agree with you, when i fix these bugs i will create a separate git 
branch, cherry-pick only freeze-allowed changes and try to get a package 
ready for stretch.


For buster, can I suggest you rewrite the rules file. I expect it could
be simplified much more using dh.


Sure


Looking at the diff from upstream, I can't help but stare in disbelief
at this:

diff --git a/src/hash.c b/src/hash.c
index 7e4c611..3eb28ca 100644
--- a/src/hash.c
+++ b/src/hash.c
@@ -57,7 +57,8 @@ mkhash (u_int src, u_short sport, u_int dest,

u_short dport)

u_int res = 0;
int i;
u_char data[12];
-  *(u_int *) (data) = src;
+  u_int *stupid_strict_aliasing_warnings=(u_int*)data;
+  *stupid_strict_aliasing_warnings = src;
*(u_int *) (data + 4) = dest;
*(u_short *) (data + 8) = sport;
*(u_short *) (data + 10) = dport;

A minor note: as someone not part of the pkg-security team, I find it
confusing to have both a "debian/master" and "master" branch in the same
repository both referring to Debian packaging. I think you should remove
the "master" branch (unless this is a team policy?)

Thanks,
James
This is the default behaviour of gbp when creating a repo. In 
pkg-security team we don't use it but you can see it in some packages. 
Anyway, i deleted it. :-)


Cheers,

Marcos

Bug#855967: x11vnc suddenly dropped the connection

[zoltan herman]

Tags: moreinfo

after checked logfile, found error.
23/02/2017 22:24:30 passing arg to libvncserver: -desktop
23/02/2017 22:24:30 passing arg to libvncserver: dl360g7:0.0
###
#@#
#@   @#
#@  **  WARNING  **  WARNING  **  WARNING  **  WARNING  **   @#
#@   @#
#@YOU ARE RUNNING X11VNC WITHOUT A PASSWORD!!@#
#@   @#
#@  This means anyone with network access to this computer   @#
#@  may be able to view and control your desktop.@#
#@   @#
#@ >>> If you did not mean to do this Press CTRL-C now!! <<< @#
#@   @#
#@#
#@   @#
#@  You can create an x11vnc password file by running:   @#
#@   @#
#@   x11vnc -storepasswd password /path/to/passfile  @#
#@  or   x11vnc -storepasswd /path/to/passfile   @#
#@  or   x11vnc -storepasswd @#
#@   @#
#@  (the last one will use ~/.vnc/passwd)@#
#@   @#
#@  and then starting x11vnc via:@#
#@   @#
#@  x11vnc -rfbauth /path/to/passfile@#
#@   @#
#@  an existing ~/.vnc/passwd file from another VNC  @#
#@  application will work fine too.  @#
#@   @#
#@  You can also use the -passwdfile or -passwd options. @#
#@  (note -passwd is unsafe if local users are not trusted)  @#
#@   @#
#@  Make sure any -rfbauth and -passwdfile password files@#
#@  cannot be read by untrusted users.   @#
#@   @#
#@  Use x11vnc -usepw to automatically use your  @#
#@  ~/.vnc/passwd or ~/.vnc/passwdfile password files.   @#
#@  (and prompt you to create ~/.vnc/passwd if neither   @#
#@  file exists.)  Under -usepw, x11vnc will exit if it  @#
#@  cannot find a password to use.   @#
#@   @#
#@   @#
#@  Even with a password, the subsequent VNC traffic is  @#
#@  sent in the clear.  Consider tunnelling via ssh(1):  @#
#@   @#
#@http://www.karlrunge.com/x11vnc/#tunnelling@#
#@   @#
#@  Or using the x11vnc SSL options: -ssl and -stunnel   @#
#@   @#
#@  Please Read the documention for more info about  @#
#@  passwords, security, and encryption. @#
#@   @#
#@http://www.karlrunge.com/x11vnc/faq.html#faq-passwd@#
#@   @#
#@  To disable this warning use the -nopw option, or put @#
#@  'nopw' on a line in your ~/.x11vncrc file.   @#
#@   @#
#@#
###
23/02/2017 22:24:31 x11vnc version: 0.9.13 lastmod: 2011-08-10  pid: 11706
23/02/2017 22:24:31 XOpenDisplay("") failed.
23/02/2017 22:24:31 Trying again with XAUTHLOCALHOSTNAME=localhost ...
23/02/2017 22:24:31 
23/02/2017 22:24:31 *** XOpenDisplay failed. No -display or DISPLAY.
23/02/2017 22:24:31 *** Trying ":0" in 4 seconds.  Press Ctrl-C to abort.
23/02/2017 22:24:31 *** 1 2 3 4 
23/02/2017 22:24:35 *** XOpenDisplay of ":0" successful.
23/02/2017 22:24:35 
23/02/2017 22:24:35 Using X display :0
23/02/2017 22:24:35 rootwin: 0x49e reswin: 0x121 dpy: 0xf5454ac0
23/02/2017 22:24:35 
23/02/2017 22:24:35 -- USEFUL INFORMATION --
23/02/2017 22:24:35 X DAMAGE available on display, using it for polling hints.
23/02/2017 22:24:35   To disable this behavior use: '-noxdamage'
23/02/2017 22:24:35 
23/02/2017 22:24:35   Most compositing window managers like 'compiz' or 'beryl'
23/02/2017 22:24:35   cause X DAMAGE to fail, and so you may not see any screen
23/02/2017 22:24:35   updates via VNC.  Either 

Bug#855933: GnuTLS 3.5.9 compatibility

[Thomas Klute]

If a patched upload goes through unstable, I suggest also including
commit 61353933986460ea2d7bcbc57531ecd066795f0d (patch attached). It's
just one line, but without it we'll be back to FTBFS when GnuTLS 3.5.9
hits unstable.

From 61353933986460ea2d7bcbc57531ecd066795f0d Mon Sep 17 00:00:00 2001
From: Thomas Klute 
Date: Sun, 19 Feb 2017 18:57:56 +0100
Subject: [PATCH] Do not treat warnings about deprecated declarations as errors

GnuTLS has declared OpenPGP support as deprecated in version
3.5.9. Treating deprecation warnings as errors causes the build to
fail with this version, so exempt them from "-Werror" until OpenPGP
support is removed from mod_gnutls.
---
 configure.ac | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configure.ac b/configure.ac
index cc3e8ae..3335773 100644
--- a/configure.ac
+++ b/configure.ac
@@ -64,7 +64,7 @@ AC_ARG_ENABLE(strict,
 
 STRICT_CFLAGS=""
 if test "$use_strict" != "no"; then
-STRICT_CFLAGS="-Wall -Werror -Wextra"
+	STRICT_CFLAGS="-Wall -Werror -Wextra -Wno-error=deprecated-declarations"
 fi
 
 AC_MSG_CHECKING([whether to enable SRP functionality])
-- 
2.9.3

Bug#855933: mod-gnutls: FTBFS: Test failures

[Thomas Klute]

These look like the timeout issues I discovered in the build logs for
0.8.2-2, see [1] for Daniel's report and [2] for my analysis, plus my
two follow up mails if jessie-backports and hurd-i386 matter. I'm going
to quote that mail below.

Just a little clarification ahead: I've since confirmed that the issue
was definitely the combination of parallel=32 and a pretty short timeout
for the flock calls. All test cases got started simultaneously but had
to wait their turn for the port(s) used in the tests (that's what the
flock calls around Apache are for), effectively making the flock timeout
(30 seconds by default) a timeout for the whole test suite except the
last test case to complete.

[1]
https://lists.gnupg.org/pipermail/mod_gnutls-devel/2017-February/000185.html
[2]
https://lists.gnupg.org/pipermail/mod_gnutls-devel/2017-February/000186.html


Looking at both build logs my best guess is that the tests are hitting
timeouts, both when getting the server instance locks (used to prevent
port conflicts) and running HTTPS requests against them. The log for
test-15_basic_msva.bash on sparc64 even looks like the timeout hit in
the middle of request handling.

I've pushed three related commits to master (the attached patch combines
all three), in order:

8184ad0eda43102d24d7cf158710e0109c7e293b Test suite: Run flock with
"--verbose" to log timeouts
bbfcbb57c2cb89790316b66bdd475c3a64ca4080 Test suite: Log if a process to
be stopped by PID file is not running
6c030c14da928da3e05f232e3fb8dd5aa98c659a Test suite: Make timeouts for
server locks and HTTPS requests configurable

Commits 8184ad0eda43102d24d7cf158710e0109c7e293b and
bbfcbb57c2cb89790316b66bdd475c3a64ca4080 just make the logging more
detailed to show if the tests are really hitting timeouts.

To change the timeouts, you can either cherry-pick
6c030c14da928da3e05f232e3fb8dd5aa98c659a and pass TEST_LOCK_WAIT and
TEST_QUERY_TIMEOUT with large values (e.g. 300 or even 600, default is
30 [seconds]) to ./configure, or patch the values of lock_wait and
TEST_QUERY_DELAY in test/Makefile.am (I've replaced/renamed the
variables in the patch).

> I can make force the entire build to not be parallel if you think it
> would be useful to test.  While i see "parallel=32" in the sparc64
> transcript, i don't see a "parallel=" note at all in ppc64.

Running in parallel definitely makes hitting the timeouts more likely,
but shouldn't cause any additional problems. You can force just the test
part of the build to run serially by passing --disable-flock to
./configure, which will add the special target .NOTPARALLEL to
test/Makefile. I'd prefer if you try the patches first, though.

Bug#855971: unblock: system-config-printer/1.5.7-3

[Laurent Bigonville]

Package: release.debian.org
Followup-For: Bug #855971

Ouups forgot the debdiff

-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru system-config-printer-1.5.7/debian/changelog 
system-config-printer-1.5.7/debian/changelog
--- system-config-printer-1.5.7/debian/changelog2016-06-02 
11:17:13.0 +0200
+++ system-config-printer-1.5.7/debian/changelog2017-02-23 
17:55:32.0 +0100
@@ -1,3 +1,14 @@
+system-config-printer (1.5.7-3) unstable; urgency=medium
+
+  * debian/patches/0010-no-start-printer-applet-gnome.patch: Do not start the
+printer-applet in GNOME or Cinnamon {gnome,cinnamon}-settings-daemon is
+already take care of this.
+  * debian/rules: Move the definition of DEB_PYTHON3_MODULE_PACKAGES before
+including python-module.mk otherwise cdbs is not calling dh_python3 as
+expected
+
+ -- Laurent Bigonville   Thu, 23 Feb 2017 17:55:32 +0100
+
 system-config-printer (1.5.7-2) unstable; urgency=medium
 
   * Move part of system-config-printer to system-config-printer-common
@@ -7,13 +18,13 @@
   * debian/control.in: Bump Standards-Version to 3.9.8 (no further changes)
   * Drop debian/gpk-install-package-name, this doesn't seem needed anymore
   * Drop adwaita-icon-theme dependency, try to avoid individual packages to
-depends against themes.
+depend against themes.
   * Add debian/patches/0008-fix-device-sorting.patch: Fix sorting of devices,
 taken from upstream
   * Drop debian/patches/0002-Disable-firewall-checks.patch: firewalld is
 available in Debian as well, let's integrate with it.
   * Add debian/patches/0009-fix-udev-add-printer-shbang.patch: Fix incorrect
-python3 invocation, taken from upstream
+python3 invocation, taken from upstream (Closes: #823472)
 
  -- Laurent Bigonville   Thu, 02 Jun 2016 11:16:46 +0200
 
diff -Nru system-config-printer-1.5.7/debian/control 
system-config-printer-1.5.7/debian/control
--- system-config-printer-1.5.7/debian/control  2016-06-02 11:19:11.0 
+0200
+++ system-config-printer-1.5.7/debian/control  2017-02-23 17:55:32.0 
+0100
@@ -6,7 +6,7 @@
 Section: gnome
 Priority: optional
 Maintainer: Debian GNOME Maintainers 

-Uploaders: Dmitry Shachnev , Emilio Pozuelo Monfort 
, Laurent Bigonville , Guido Günther 

+Uploaders: Dmitry Shachnev , Laurent Bigonville 
, Guido Günther 
 Build-Depends: autotools-dev,
cdbs (>= 0.4.90~),
debhelper (>= 9),
diff -Nru 
system-config-printer-1.5.7/debian/patches/0010-no-start-printer-applet-gnome.patch
 
system-config-printer-1.5.7/debian/patches/0010-no-start-printer-applet-gnome.patch
--- 
system-config-printer-1.5.7/debian/patches/0010-no-start-printer-applet-gnome.patch
 1970-01-01 01:00:00.0 +0100
+++ 
system-config-printer-1.5.7/debian/patches/0010-no-start-printer-applet-gnome.patch
 2016-06-08 11:20:59.0 +0200
@@ -0,0 +1,24 @@
+From 4450fd4a2ad3c5447118d33ee373e555f0e81ab3 Mon Sep 17 00:00:00 2001
+From: Laurent Bigonville 
+Date: Thu, 2 Jun 2016 14:41:48 +0200
+Subject: [PATCH] Do not start the applet on GNOME and Cinnamon desktops
+ (Closes: #40)
+
+{gnome,cinnamon}-settings-daemon are also claiming the D-Bus interfaces
+provided by the applet
+---
+ print-applet.desktop.in | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/print-applet.desktop.in b/print-applet.desktop.in
+index c8fd345..0e38ee1 100644
+--- a/print-applet.desktop.in
 b/print-applet.desktop.in
+@@ -5,6 +5,6 @@ Exec=system-config-printer-applet
+ Terminal=false
+ Type=Application
+ Icon=printer
+-NotShowIn=KDE;
++NotShowIn=KDE;GNOME;Cinnamon;
+ StartupNotify=false
+ X-GNOME-Autostart-Delay=30
diff -Nru system-config-printer-1.5.7/debian/patches/series 
system-config-printer-1.5.7/debian/patches/series
--- system-config-printer-1.5.7/debian/patches/series   2016-06-02 
11:16:36.0 +0200
+++ system-config-printer-1.5.7/debian/patches/series   2016-06-08 
11:21:13.0 +0200
@@ -3,3 +3,4 @@
 0007-fix-pk-package-name.patch
 0008-fix-device-sorting.patch
 0009-fix-udev-add-printer-shbang.patch
+0010-no-start-printer-applet-gnome.patch
diff -Nru system-config-printer-1.5.7/debian/rules 
system-config-printer-1.5.7/debian/rules
--- system-config-printer-1.5.7/debian/rules2016-06-01 16:06:39.0 
+0200
+++ system-config-printer-1.5.7/debian/rules2017-02-23 17:52:03.0 

Bug#855953: mplayer: Stops playing when switching to text consoles

[James Cowgill]

Hi,

On 23/02/17 19:28, Helge Kreutzmann wrote:
> Package: mplayer
> Version: 2:1.3.0-6
> Severity: normal
> 
> When I play videos and switch to text consoles (via Ctrl-Alt-F1 for
> example) audio and video playback stops and is not resumed until I
> return to the X shell again.

This isn't a bug, but an intentional design choice of pulseaudio /
systemd-logind. The permissions are setup in such a way that only the
"active" user ever has access to the audio hardware so when you switch
to another virtual terminal the old user can no longer play any audio.

James



signature.asc
Description: OpenPGP digital signature

Bug#855972: 2ping: Missing dependency on python-pkg-resources

[Felix Lechner]

Package: 2ping
Version: 3.2.1-1
Severity: normal

Starting 2ping or 2ping6 aborts with the error below. Please add a
dependency on python-pkg-resources. Thank you!

Traceback (most recent call last):
  File "/usr/bin/2ping", line 5, in 
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources


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

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

Versions of packages 2ping depends on:
ii  init-system-helpers1.47
ii  libpython2.7-stdlib [python-argparse]  2.7.13-2
ii  python 2.7.13-2
pn  python:any 

2ping recommends no packages.

2ping suggests no packages.

-- no debconf information

Bug#855971: unblock: system-config-printer/1.5.7-3

[Laurent Bigonville]

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

Hi,

Please unblock package system-config-printer

The 1.5.7-3 upload includes two changes:

 - I discovered that cdbs has (I think) changed its behaviour (see bug
   #828726 that has been unfortunately closed IMVHO) and that dh_python3
   was not called on all the packages as I was expecting. Moving
   DEB_PYTHON3_MODULE_PACKAGES above the includes fixed the issues.
 - I changed the print-applet.desktop file to not start the applet on
   GNOME and Cinnamon. The applet is not needed as the D-Bus names are
   already claimed by {gnome,cinnamon}-settings-daemon.

unblock system-config-printer/1.5.7-3

Regards,

Laurent Bigonville

-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#855970: [debian-archive-keyring] The release repository of testing (Stretch), and security updates repository too, have three misiing public keys

[Adam D. Barratt]

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

On Thu, 2017-02-23 at 22:30 +0100, Łukasz Konieczny wrote:
> Package: debian-archive-keyring
> Version: 2014.3
> Severity: serious
> Tags: security
> X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org
> 
> --- Please enter the report below this line. ---
> The release repository of testing (Stretch), and security updates 
> repository too, have three misiing public keys. Terminal output of 
> apt-get update is attached to this mail. Some text is in Polish language.

The keys are certainly in the package, so I'm not sure why your apt
isn't seeing them.

What does

gpg --keyring /usr/share/keyrings/debian-archive-keyring.gpg --list-keys 
8B48AD6246925553

produce on your system?

Regards,

Adam

Bug#841369: Wishlist: Change icon image for CQRLOG

[Colin Tuckley]

On 23/02/17 21:41, asciiw...@seznam.cz wrote:
> Any news regarding this issue?

The bug is fixed upstream *but* there are problems with the upstream
change on systems that do not use Gnome. For example on KDE systems the
icon is not displayed.

I've built a package for 2.0.4 with this fixed.

However there is another, much bigger problem with cqrlog 2.0.4 ...

Open SSL changes have broken the cqrlog interface to LotW and Clublog,
until this is also fixed I will not do *any* uploads of cqrlog.

Colin

Bug#855970: [debian-archive-keyring] The release repository of testing (Stretch), and security updates repository too, have three misiing public keys

[Łukasz Konieczny]

Package: debian-archive-keyring
Version: 2014.3
Severity: serious
Tags: security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org

--- Please enter the report below this line. ---
The release repository of testing (Stretch), and security updates 
repository too, have three misiing public keys. Terminal output of 
apt-get update is attached to this mail. Some text is in Polish language.


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

Debian Release: 9.0
500 testing ftp.pl.debian.org

--- Package information. ---
Depends (Version) | Installed
==-+-===
gpgv | 2.1.18-3


Recommends (Version) | Installed
=-+-===
gnupg | 2.1.18-3


Package's Suggests field is empty.
root@BlackMachine:Pobrane# apt-get update
Pobieranie:1 http://ftp.pl.debian.org/debian stretch InRelease [184 kB]
Pobieranie:2 http://security.debian.org/debian-security stretch/updates 
InRelease [62,9 kB]
Ign:1 http://ftp.pl.debian.org/debian stretch InRelease   
Ign:2 http://security.debian.org/debian-security stretch/updates InRelease
Pobrano 247 kB w 0s (325 kB/s)
Czytanie list pakietów... Gotowe
W: Błąd GPG: http://ftp.pl.debian.org/debian stretch InRelease: Następujące 
podpisy nie mogły zostać zweryfikowane z powodu braku klucza publicznego: 
NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010
W: The repository 'http://ftp.pl.debian.org/debian stretch InRelease' is not 
signed.
N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.
W: Błąd GPG: http://security.debian.org/debian-security stretch/updates 
InRelease: Następujące podpisy nie mogły zostać zweryfikowane z powodu braku 
klucza publicznego: NO_PUBKEY 9D6D8F6BC857C906 NO_PUBKEY 8B48AD6246925553
W: The repository 'http://security.debian.org/debian-security stretch/updates 
InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.
root@BlackMachine:Pobrane# 

Bug#855969: gitolite3: Please package ukm tool from contrib

[Matthew Gabeler-Lee]

Package: gitolite3
Version: 3.6.1-2+deb8u1
Severity: wishlist

The upstream gitolite source includes a very useful "contrib" tool 'ukm' to
help with key management.  It would be nice if the Debian package included
this tool in some fashion.

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

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

Bug#855968: unblock: ekg/1:1.9~pre+r2855-5

[Adrian Bunk]

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

Please unblock package ekg

unblock ekg/1:1.9~pre+r2855-5


diff -Nru ekg-1.9~pre+r2855/debian/changelog ekg-1.9~pre+r2855/debian/changelog
--- ekg-1.9~pre+r2855/debian/changelog  2016-12-09 21:07:36.0 +0200
+++ ekg-1.9~pre+r2855/debian/changelog  2017-02-23 16:37:45.0 +0200
@@ -1,3 +1,11 @@
+ekg (1:1.9~pre+r2855-5) unstable; urgency=medium
+
+  * QA upload.
+  * Disable parallel building to work around a FTBFS.
+(Closes: #811234)
+
+ -- Adrian Bunk   Thu, 23 Feb 2017 16:37:45 +0200
+
 ekg (1:1.9~pre+r2855-4) unstable; urgency=medium
 
   * QA upload.
diff -Nru ekg-1.9~pre+r2855/debian/rules ekg-1.9~pre+r2855/debian/rules
--- ekg-1.9~pre+r2855/debian/rules  2016-12-09 21:07:36.0 +0200
+++ ekg-1.9~pre+r2855/debian/rules  2017-02-23 16:37:45.0 +0200
@@ -42,7 +42,7 @@
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 %:
-   dh $@ --with autoreconf --parallel
+   dh $@ --with autoreconf --no-parallel
 
 
 override_dh_autoreconf:

Bug#726230: Mozilla Location Service

[Dj Chey Velasco]

On Fri, 31 Jan 2014 23:52:54 +0100 Pierre Rudloff 
wrote:
> Changing /geo.wifi.uri/ to
> /https://location.services.mozilla.com/v1/geolocate/ seems to work fine.
> The only problem is that coverage is not really good for now.
>
> Regards,

Bug#855967: x11vnc suddenly dropped the connection

[zoltan herman]

Package: x11vnc
Version: 0.9.13-2
Severity: normal
Tags: newcomer

Dear Maintaners,
after upgrade the system, x11vnc dropped the connection(s),
especially when I use Firefox/CodeBlocks applications.
I have not found error in log files.

After dropped the connection, service wrote info :
systemctl status myvncserver
● myvncserver.service - VNC Server for X11
   Loaded: loaded (/lib/systemd/system/myvncserver.service; disabled; vendor
preset: enabled)
   Active: failed (Result: exit-code) since cs 2017-02-23 21:26:57 CET; 43min
ago
  Process: 8310 ExecStart=/usr/bin/x11vnc -auth /tmp/xauth-1000-_0 -desktop
dl360g7:0.0 -forever -bg -o /var/log/x1
 Main PID: 8312 (code=exited, status=2)

febr 23 21:14:16 dl360g7 systemd[1]: Starting VNC Server for X11...
febr 23 21:14:22 dl360g7 x11vnc[8310]: PORT=5900
febr 23 21:14:22 dl360g7 systemd[1]: Started VNC Server for X11.
febr 23 21:26:57 dl360g7 systemd[1]: myvncserver.service: Main process exited,
code=exited, status=2/INVALIDARGUMEN
febr 23 21:26:57 dl360g7 systemd[1]: myvncserver.service: Unit entered failed
state.
febr 23 21:26:57 dl360g7 systemd[1]: myvncserver.service: Failed with result
'exit-code'.

x11vnc log part after restarted it :

23/02/2017 22:25:23 Got connection from client 192.168.0.13
23/02/2017 22:25:23   other clients:
23/02/2017 22:25:23 Normal socket connection
23/02/2017 22:25:23 incr accepted_client=1 for 192.168.0.13:26525  sock=11
23/02/2017 22:25:23 Client Protocol Version 3.8
23/02/2017 22:25:23 Protocol version sent 3.8, using 3.8
23/02/2017 22:25:23 rfbProcessClientSecurityType: executing handler for type 1
23/02/2017 22:25:23 rfbProcessClientSecurityType: returning securityResult for
client rfb version >= 3.8
23/02/2017 22:25:23 rfbProcessClientNormalMessage: ignoring unsupported
encoding type Enc(0x0016)
23/02/2017 22:25:23 rfbProcessClientNormalMessage: ignoring unsupported
encoding type Enc(0x0015)
23/02/2017 22:25:23 rfbProcessClientNormalMessage: ignoring unsupported
encoding type Enc(0x000F)
23/02/2017 22:25:23 rfbProcessClientNormalMessage: ignoring unsupported
encoding type Enc(0xFEC6)
23/02/2017 22:25:23 Enabling full-color cursor updates for client 192.168.0.13
23/02/2017 22:25:23 Enabling NewFBSize protocol extension for client
192.168.0.13
23/02/2017 22:25:23 Using ZRLE encoding for client 192.168.0.13
23/02/2017 22:25:23 Pixel format for client 192.168.0.13:
23/02/2017 22:25:23   32 bpp, depth 24, little endian
23/02/2017 22:25:23   true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
23/02/2017 22:25:23 no translation needed
23/02/2017 22:25:23 copy_tiles: allocating first_line at size 41
23/02/2017 22:25:24 client useCopyRect: 192.168.0.13 -1
23/02/2017 22:25:24 client_set_net: 192.168.0.13  0.0098
23/02/2017 22:25:24 created   xdamage object: 0x120002c
23/02/2017 22:25:26 client 1 network rate 2533.8 KB/sec (69257.0 eff KB/sec)
23/02/2017 22:25:26 client 1 latency:  3.8 ms
23/02/2017 22:25:26 dt1: 0.0212, dt2: 0.0126 dt3: 0.0038 bytes: 80860
23/02/2017 22:25:26 link_rate: LR_LAN - 3 ms, 2533 KB/s
23/02/2017 22:25:33 created selwin: 0x120002d
23/02/2017 22:25:33 called initialize_xfixes()
23/02/2017 22:31:04 cursor_noshape_updates_clients: 0
23/02/2017 22:31:26 added missing keysym to X display: 093 0xd6 "Odiaeresis"
23/02/2017 22:39:22 cursor_noshape_updates_clients: 0
23/02/2017 22:39:30 cursor_noshape_updates_clients: 0



Greetings
hz



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

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

Versions of packages x11vnc depends on:
ii  libavahi-client3  0.6.32-2
ii  libavahi-common3  0.6.32-2
ii  libc6 2.24-9
ii  libjpeg62-turbo   1:1.5.1-2
ii  libssl1.1 1.1.0e-1
ii  libvncclient1 0.9.11+dfsg-1
ii  libvncserver1 0.9.11+dfsg-1
ii  libx11-6  2:1.6.4-3
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.3-1
ii  libxinerama1  2:1.1.3-1+b1
ii  libxrandr22:1.5.1-1
ii  libxtst6  2:1.2.3-1
ii  openssl   1.1.0e-1
ii  tk8.6.0+9
ii  x11vnc-data   0.9.13-2
ii  zlib1g1:1.2.8.dfsg-5

x11vnc recommends no packages.

x11vnc suggests no packages.

-- no debconf information

Bug#848895: Chromium freezes randomly

[Ximin Luo]

Luke Kenneth Casson Leighton:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=87
> 
> now ain't that fascinating.  optirun combined with fvwm2 is a
> sure-fire extremely fast and 100% *guaranteed* way to repro this
> "freezing but you can ctrl-alt-f1 then ctrl-alt-f7 and it miraculously
> all works whoopidoo" problem.
> 
> [..]

Hi,

I am not sure if primus is the problem. I don't have it installed. In fact when 
I had the bug (on chromium 55.0.2883.75-6) I was using the free nouveau 
drivers, not the nvidia drivers.

I am now using the nvidia drivers with the same chromium version, and I have 
not seen the bug for a few days. But if you do see it with nvidia drivers, then 
something else must be the actual problem.

I haven't yet tried 56.0.2924.76-4 that Michael says is fixed. BTW he has 
closed the bug report #848895, I did not get a notification about this and I 
only noticed when visiting the bug report web page. If any of you can reproduce 
the bug with version 56.0.2924.76-4 please let us know so we can re-open the 
bug.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#841369: Wishlist: Change icon image for CQRLOG

[asciiwolf]

Any news regarding this issue?

Bug#849249: fldigi: Icon improvements

[asciiwolf]

Any news regarding this issue?

Bug#855434: SSL_PROTOCOL_ERROR in chromium-browser

[Steven Valdez]

Unfortunately some Chromium-derived browsers (including the copy of
chromium-browser shipping in Debian) are shipping with features turned on
as if they were developer builds.

Chromium developer builds by default ship all experimental features,
including ones that aren't ready to be shipped yet. End-user builds of
Chromium-derived code need to build with
fieldtrial_testing_like_official_build=true to disable these features.

See this thread where this was announced in 2015 for details:
https://groups.google.com/a/chromium.org/d/msg/chromium-packagers/UmdUH3AkQRE/TifdFA-OAgAJ

Notably, some experimental features in M56 were incompatible with each
other (one of the field trials is not shipping for M56). See https:/
/bugs.chromium.org/p/chromium/issues/detail?id=693943

A Debian packager will need to build a new copy of chromium-browser with
the correct flags in order to fix this issue.

-Steven

Bug#855933: mod-gnutls: FTBFS: Test failures

[Daniel Kahn Gillmor]

On Thu 2017-02-23 08:28:03 -0500, Lucas Nussbaum wrote:
> During a rebuild of all packages in stretch (in a stretch chroot, not a
> sid chroot), your package failed to build on amd64.

here's the actual relevant part:

FAIL: test-22_TLS_reverse_proxy_crl_revoke.bash
FAIL: test-21_TLS_reverse_proxy_wrong_cert.bash
FAIL: test-04_basic_nosni.bash
FAIL: test-09_verify_no_sni_fails_with_wrong_order.bash
PASS: test-23_TLS_reverse_proxy_mismatched_priorities.bash
===
   mod_gnutls 0.8.2: test/test-suite.log
===

# TOTAL: 28
# PASS:  24
# SKIP:  0
# XFAIL: 0
# FAIL:  4
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: test-04_basic_nosni.bash
==

TESTING: 04_basic_nosni
./runtests failed at line 188!
FAILURE: 04_basic_nosni
FAIL test-04_basic_nosni.bash (exit status: 1)

FAIL: test-09_verify_no_sni_fails_with_wrong_order.bash
===

TESTING: 09_verify_no_sni_fails_with_wrong_order (expected: fail.*)
./runtests failed at line 188!
FAILURE: 09_verify_no_sni_fails_with_wrong_order
AH00548: NameVirtualHost has no effect and will be removed in the next release 
/<>/test/tests/09_verify_no_sni_fails_with_wrong_order/apache.conf:5
FAIL test-09_verify_no_sni_fails_with_wrong_order.bash (exit status: 1)

FAIL: test-21_TLS_reverse_proxy_wrong_cert.bash
===

FAIL test-21_TLS_reverse_proxy_wrong_cert.bash (exit status: 1)

FAIL: test-22_TLS_reverse_proxy_crl_revoke.bash
===

FAIL test-22_TLS_reverse_proxy_crl_revoke.bash (exit status: 1)


--

I'm afraid i don't know exactly what this means, though.

perhaps Thomas Klute (cc'ed here) has some suggestions...

--dkg

Bug#855966: qemu: Please use full version number (2.8.0 instead of 2.8)

[Jeremy Bicha]

Source: qemu
Version: 1:2.8+dfsg-2
Severity: low

Could you please use the full version number 2.8.0 instead of 2.8?

https://tracker.debian.org/pkg/qemu complains that a newer upstream
version is available because that's what the watch file indicates.

Thanks,
Jeremy Bicha

Bug#855902: [Pkg-xfce-devel] Bug#855902: xfce4: Moving mouse won't bring a locked screen back. Have to use Ctrl-Alt-F2, Ctrl-Alt-F1, which brings the Desktop Manager (such as GDM) login screen.

[Yves-Alexis Perez]

control: tag -1 moreinfo

On Wed, 2017-02-22 at 22:53 -0800, Hong Xu wrote:
> If wait long enough after the screen is locked, I have to use "Ctrl-Alt-F2,
> Ctrl-Alt-F1" to bring the screen back on. However, when it is on, the desktop
> manager (GDM) pops up, instead of the xfce password dialog.

What screen locker are you using? Note that light-locker only works with
lightdm, not GDM.

Regards,
-- 
Yves-Alexis

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

Bug#855965: libdebian-installer: Please add support for NETGEAR ReadyNAS Duo v2

[Scott Barker]

Package: libdebian-installer
Version: 0.108
Severity: wishlist

Dear Maintainer,

Please add support for NETGEAR ReadyNAS Duo v2, which uses a "kirkwood" 
processor:

# cat /proc/device-tree/model
NETGEAR ReadyNAS Duo v2

# cat /proc/cpuinfo
processor   : 0
model name  : Feroceon 88FR131 rev 1 (v5l)
BogoMIPS: 1594.36
Features: swp half thumb fastmult edsp 
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant : 0x2
CPU part: 0x131
CPU revision: 1

Hardware: Marvell Kirkwood (Flattened Device Tree)
Revision: 
Serial  : 

I believe you can add this to map_hardware[] :

  { "NETGEAR ReadyNAS Duo v2" , "kirkwood" },

Thank you.


-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armel (armv5tel)

Kernel: Linux 3.16.0-4-kirkwood
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#819811: ITP: leiningen -- simple build system for Clojure

[Elana Hashman]

All the first-degree dependencies should now be marked as blocking. Now 
for some packaging...


There are a lot of deps and granddeps so if you're interested in helping 
out, please feel free to claim one (or many)!


- e

Bug#855342: RFH: ntp

[Guus Sliepen]

On Thu, Feb 23, 2017 at 09:47:06PM +0100, Bernhard Schmidt wrote:

> I've imported the NMU and added the missing tags for the last couple of
> revisions. gbp buildpackage from the repo works fine and produces very
> similar packages compared to the one in sid right now (no changes in
> debdiff, diffoscope sees some diffs that are likely related to toolchain
> changes).

Hm, gbp clone worked fine, but gbp buildpackage results in an error:

cd . && env 
PATH="/scratch/users/guus/ntp/pkg-ntp/sntp:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11"
 AUTOGEN_DNE_DATE=-D autogen -L include -L ag-tpl --writable -Tagtexi-cmd.tpl 
-DLEVEL=section sntp-opts.def
config.status: creating sntp.1+
mv sntp.1+ sntp.1
./../scripts/build/check--help invoke-sntp.texi
Makefile:1607: recipe for target 'invoke-sntp.texi' failed
make[5]: *** [invoke-sntp.texi] Error 1
make[5]: Leaving directory '/scratch/users/guus/ntp/pkg-ntp/sntp'

This is the first time I've ever tried building NTP though.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: Digital signature

Bug#855954: autopkgtest: can't handle packages with a + in its name

[Martin Pitt]

Control: tag -1 pending

Hello Ralf, Antonio,

Antonio Terceiro [2017-02-23 17:10 -0300]:
> $ autopkgtest --apt-upgrade minisat+ -- lxc --sudo adt-sid-amd64
> [...]
> E: Version '1:2.2.1-5+b1' for 'minisat+' was not found

Ah, gotta love apt.. a --debug run shows what's going on:

+ apt-cache policy ^minisat+$
+ sed -n /Candidate:/ { s/^.* //; /none/d; p}
+ pkg_candidate=1:2.2.1-5+b1
+ [ -n 1:2.2.1-5+b1 ]

I have to do this ^$ wrapping as otherwise apt-cache policy does some sort of
substring matching. RE-magic chars allowed in package names are '.' and '+', so
these need to be escaped. Fixed in

  
https://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=e3163e9cad34

(Don't look too closely at this shell hell, your eyes will pop out..)

Thanks,

Martin


signature.asc
Description: PGP signature

Bug#855851: gcc-3.3: still in stretch

[Philipp Kern]

On 2017-02-23 09:49, Santiago Vila wrote:

Of course it's not word-by-word what I wrote, but it was clearly the
meaning: When we remove packages from the distribution because we
don't need them anymore, we don't just remove them from testing, we
remove them from both testing and unstable.

[...]

So what's the point in talking about the freeze in your previous
message? It's not too late to remove a whole compiler but it's too
late to remove a leaf package on which no other Debian package depends
for years?

I would really like to understand the logic of your reasoning, but I
still can't, sorry.


You are talking about stretch. The bug's title is stretch. You are 
talking about a removal from a frozen set of packages right after we 
have frozen. In your mind freezing is only to not allow new packages to 
go in. In my mind it's also freezing the set of packages to not 
arbitrarily remove them post-freeze. Especially if the reverse 
dependencies are outside of the archive and hence unknown.


Kind regards
Philipp Kern

Bug#855963: RFP: libreply-clojure -- A fitter, happier, more productive REPL for Clojure

[Elana Hashman]

Package: wnpp
Severity: wishlist
Control: block 819811 by -1

* Package name: libreply-clojure
  Version : 0.3.7
  Upstream Author : Colin Jones
* URL : https://github.com/trptcolin/reply
* License : EPL 1.0
  Programming Lang: Clojure
  Description : A fitter, happier, more productive REPL for Clojure

This library is a build-dep for leiningen2.

Bug#855892: [debian-mysql] Bug#855892: [mysql-server] more info

[Robie Basak]

Ah. In that case you have a dupe of bug 850216/855935/855936.


signature.asc
Description: PGP signature

Bug#855962: acme-tiny: fail to parse openssl 1.1 CSR output

[Aurelien Jarno]

Package: acme-tiny
Version: 20160801-1
Severity: serious

openssl 1.1 slightly changed the way the Subject of a certificate
request is formated:

-Subject: CN=foobar.domain.net
+Subject: CN = foobar.domain.net

This causes acme-tiny to fail to get the domain from certificate requests
without SAN. This in turns causes the certificate signing to be rejected
by letsencrypt with error urn:acme:error:unauthorized unless it has been
validated relatively recently.

Here is a possible patch to make it compatible with both openssl 1.0 and
1.1:

--- a/acme_tiny.py
+++ b/acme_tiny.py
@@ -69,7 +69,7 @@
 if proc.returncode != 0:
 raise IOError("Error loading {0}: {1}".format(csr, err))
 domains = set([])
-common_name = re.search(r"Subject:.*? CN=([^\s,;/]+)", out.decode('utf8'))
+common_name = re.search(r"Subject:.*? CN\s*=\s*([^\s,;/]+)", 
out.decode('utf8'))
 if common_name is not None:
 domains.add(common_name.group(1))
 subject_alt_names = re.search(r"X509v3 Subject Alternative Name: \n 
+([^\n]+)\n", out.decode('utf8'), re.MULTILINE|re.DOTALL)


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

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

Versions of packages acme-tiny depends on:
ii  openssl1.1.0d-2
ii  python3-pkg-resources  33.1.1-1
pn  python3:any

acme-tiny recommends no packages.

acme-tiny suggests no packages.

-- no debconf information

Bug#840657: [Pkg-xfce-devel] Bug#840657: Corrected patch

[Murray, Ronald]

Yes, the bad CSS appears to be fixed (checked by uninstalling and re-installing 
xfce4-notifyd). I don't know whether the "org.ally.Bus name" problem has been 
fixed or not: I couldn't reproduce that one.

Note that my patch was designed to only fix the CSS problem (my emails to this 
bug arrived out of order). I suspect that bug #838722 is the same problem; if 
so, it should also be fixed now.

Thanks,

 .Ron

-Original Message-
From: Yves-Alexis Perez [mailto:cor...@debian.org] 
Sent: Saturday, February 18, 2017 9:28 AM
To: Murray, Ronald; 840...@bugs.debian.org
Subject: Re: [Pkg-xfce-devel] Bug#840657: Corrected patch

On Thu, 2016-10-20 at 14:40 -0400, Ron Murray wrote:
> Corrected patch attached (fixes gtk-3.0 as well as gtk-3.20 branch).

Does this still happen? I think it's been fixed with 0.3.3-2 but a confirmation 
would be nice.

Regards,
--
Yves-Alexis

**
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this mail in error please notify the postmaster at 
dor.state.ma.us.

Bug#855892: [mysql-server] more info

[Jason Cormie]

Package: mysql-server
Version: 5.7.17-1

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

It looks like I have mariadb-common installed and it has taken over the my.cnf
It is now redirected to mariadb.cnf
This seems to have an include for /etc/mysql/mariadb.conf.d/

mariadb-common   10.0.29-0+deb8u1






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

Debian Release: 9.0
  870 stable  security.debian.org 
  870 stable  repository.spotify.com 
  870 stable  http.us.debian.org 
  870 stable  ftp.debian.org 
  860 testing ftp.debian.org 
  500 unstableftp.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-===
mysql-server-5.7| 5.7.17-1


Package's Recommends field is empty.

Package's Suggests field is empty.




-- 
Jason Cormie

Bug#855342: RFH: ntp

[Bernhard Schmidt]

On 23.02.2017 19:06, Kurt Roeckx wrote:
> On Thu, Feb 23, 2017 at 01:33:09PM +0100, Bernhard Schmidt wrote:
>>
>> Will check what could be causing this.
> 
> That has been fixed in an NMU, see #851803

Ah right, silly me.

I've imported the NMU and added the missing tags for the last couple of
revisions. gbp buildpackage from the repo works fine and produces very
similar packages compared to the one in sid right now (no changes in
debdiff, diffoscope sees some diffs that are likely related to toolchain
changes).

Repo has been pushed.

Best Regards,
Bernhard

Bug#855427: quicktun: Does not work

[James Cloos]

Theonly other issue is that the web site claims that REMOTE_PORT
defaults to LOCAL_PORT.  When specifying ports in interfaces with
qt_local_port and qt_remote_port, remote does not default to local.

The readme should detail all of the qt_ options and their (actual)
defaults.

-JimC
-- 
James Cloos  OpenPGP: 0x997A9F17ED7DAEA6

Bug#855961: Cups PPD Update authentication requested

[Jeff Burns]

Package: cups
Version: 1.7.5-11+deb8u1

When doing an installation of the latest cups package, when PPDs can be 
updated, you are prompted for root password on localhost. You can hit enter to 
by pass, and this is confirmed to break even when running as root. 
Unfortunately this breaks unattended upgrades.

Processes that get stuck:

root 11264 0.0 0.4 63060 16884 pts/1 S+ 11:48 0:00 _ /usr/bin/perl -w 
/usr/share/debconf/frontend /var/lib/dpkg/info/cups.postinst triggered 
/usr/share/cups/ppd-updaters
root 11268 0.0 0.0 4336 1596 pts/1 S+ 11:48 0:00 _ /bin/sh 
/var/lib/dpkg/info/cups.postinst triggered /usr/share/cups/ppd-updaters
root 11345 0.0 0.1 65696 5388 pts/1 S+ 11:48 0:00 _ lpadmin -h 
/var/run/cups/cups.sock -p LANIER_5622 -m gutenprint.5.2://lanier-5622/expert

If you run apt-get from CLI to update you get this prompted:
“Password for root on localhost?”

This appears to be relevant to past cups bug report #662915.

Jeff Burns
Engineering Systems Administrator

5011 Gate Parkway
Building 100 Suite 225
Jacksonville, FL 32256
(800) 624 5999 ext 9325
www.efi.com



Confidentiality notice: This message may contain confidential information. It 
is intended only for the person to whom it is addressed. If you are not that 
person, you should not use this message. We request that you notify us by 
replying to this message, and then delete all copies including any contained in 
your reply. Thank you.

Bug#814057: diffoscope: Add option to ignore mtimes

[Leo Famulari]

On Tue, Feb 07, 2017 at 10:24:58PM +1300, Chris Lamb wrote:
> Hi Leo,
> 
> > Since I am comparing the entire output of Python 2.7's build process,
> > there are a lot of files, and they *all* have different ctimes (we set
> > mtimes to epoch).
> 
> So, we already ignore mtimes on specified command-line arguments:
> 
>   $ touch --date="@0" epoch
> 
>   $ touch now
> 
>   $ diffoscope epoch now --no-progress
> 
>   $ echo $?
>   0
> 
> Are you referring to {m,c}times, etc. within archives?

I was referring to {m,c}times of the files being compared themselves.

If by "within archives" you mean "of files within, for example, two zip
archives being compared", that's not what I meant.

I just tested diffoscope 77 and it ignores the different {m,c}times of
two otherwise identical test files. Great!

Now, it would be nice if diffoscope had an option to report these
differences :) I wondered if --fuzzy-threshold could be tweaked to make
diffoscope report them, but it did not for the values of 0, 1, and 400.

If I understood your question correctly, please feel free to close this
bug, or ask me to close it.

I'm sorry for the sloow response to your question. Thanks for the
ping!


signature.asc
Description: PGP signature

Bug#855960: flash-kernel: Please add support for NETGEAR ReadyNAS Duo v2

[Scott Barker]

Package: flash-kernel
Version: 3.70~bpo8+1
Severity: wishlist

Dear Maintainer,

Please add suuport for NETGEAR ReadyNAS Duo v2. The db entry that works for me 
is:

Machine: NETGEAR ReadyNAS Duo v2
DTB-Id: kirkwood-netgear_readynas_duo_v2.dtb
DTB-Append: yes
Mtd-Kernel: uImage
Mtd-Initrd: minirootfs
U-Boot-Kernel-Address: 0x8000
U-Boot-Initrd-Address: 0x
Required-Packages: u-boot-tools
Bootloader-Sets-Incorrect-Root: yes

Thank you.

-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armel (armv5tel)

Kernel: Linux 3.16.0-4-kirkwood
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages flash-kernel depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  devio  1.2-1+b1
ii  initramfs-tools0.120+deb8u2
ii  linux-base 3.5
ii  mtd-utils  1:1.5.1-1
ii  ucf3.0030

Versions of packages flash-kernel recommends:
ii  u-boot-tools  2014.10+dfsg1-5

flash-kernel suggests no packages.

-- debconf information:
  flash-kernel/linux_cmdline: quiet

Bug#855955: aisleriot: Variants "Westhaven" and "Diamond-Mine" interfere: crash with wrong-number-of-args

[BenWiederhake.GitHub]

Reported upstream as https://bugzilla.gnome.org/show_bug.cgi?id=779149

Bug#855954: autopkgtest: can't handle packages with a + in its name

[Antonio Terceiro]

Control: reassign -1 autopkgtest
Control: retitle -1 autopkgtest: can't handle packages with a + in its name

On Thu, Feb 23, 2017 at 08:29:40PM +0100, Ralf Treinen wrote:
> Package: debci
> 
> Hello,
> 
> ci.debian.net has never succeeded in running the testsuite of the
> minisat+ package. In the summary table for that package, the version
> is only displayed as n/a. Furthermore, the test log says :
> 
> adt-run [05:21:43]:  apt-source minisat+
> E: Version '1:2.2.1-5+b1' for 'minisat+' was not found
> E: No packages found
> blame: minisat+
> 
> However, 1:2.2.1-5+b1 is not the version of the "minisat+" package in sid
> - it rather is the version of the package "minisat2" in sid ! I suppose
> that debci gets confused by the "+ in the package name.
> 
> Cheers -Ralf.

this is an issue in autopkgtest.

$ dpkg-query --show autopkgtest
autopkgtest 4.3
$ autopkgtest --apt-upgrade minisat+ -- lxc --sudo adt-sid-amd64
autopkgtest [17:06:12]: version 4.3
autopkgtest [17:06:12]: host homer; command line: /usr/bin/autopkgtest 
--apt-upgrade minisat+ -- lxc --sudo adt-sid-amd64
autopkgtest [17:06:24]:  test bed setup
Get:1 http://httpredir.debian.org/debian sid InRelease [231 kB]
Get:2 http://httpredir.debian.org/debian sid/main Sources.diff/Index [27.9 kB]
Get:3 http://httpredir.debian.org/debian sid/main amd64 Packages.diff/Index 
[27.9 kB]
Get:4 http://incoming.debian.org/debian-buildd buildd-sid InRelease [58.1 kB]
Get:5 http://httpredir.debian.org/debian sid/main Sources 
2017-02-23-1426.01.pdiff [1780 B]
Get:5 http://httpredir.debian.org/debian sid/main Sources 
2017-02-23-1426.01.pdiff [1780 B]
Get:6 http://httpredir.debian.org/debian sid/main amd64 Packages 
2017-02-23-1426.01.pdiff [9481 B]
Get:6 http://httpredir.debian.org/debian sid/main amd64 Packages 
2017-02-23-1426.01.pdiff [9481 B]
Get:7 http://incoming.debian.org/debian-buildd buildd-sid/main Sources [53.2 kB]
Get:8 http://incoming.debian.org/debian-buildd buildd-sid/main amd64 Packages 
[98.6 kB]
Fetched 508 kB in 1s (271 kB/s)
Reading package lists...
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
autopkgtest [17:06:28]: testbed dpkg architecture: amd64
autopkgtest [17:06:29]: testbed running kernel: Linux 4.9.0-2-amd64 #1 SMP 
Debian 4.9.10-1 (2017-02-17)
autopkgtest [17:06:29]:  apt-source minisat+
E: Version '1:2.2.1-5+b1' for 'minisat+' was not found
E: No packages found
blame: minisat+
badpkg: rules extract failed with exit code 1
autopkgtest [17:06:29]: ERROR: erroneous package: rules extract failed with 
exit code 1



signature.asc
Description: PGP signature

Bug#855959: libwagon2-java: Could use rebuild to drop unnecessary dependencies on junit4, libeasymock-java

[Daniel Schepler]

Package: libwagon2-java
Version: 2.10-6
Severity: wishlist

If I rebuild src:wagon2 from source then the resulting libwagon2-java
package doesn't have the dependencies on junit4, libeasymock-java, or
libplexus-containers-java.  It would be nice to get a new upload to
reflect this fix (I think it was a fix in maven-debian-helper maybe?).
-- 
Daniel Schepler

Bug#855958: xserver-xorg-video-nv: not installable in sid, on any architecture

[Ralf Treinen]

Package: xserver-xorg-video-nv
Version: 1:2.1.20-3
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hello,

xserver-xorg-video-nv is not installable in sid on any of the three
architectures where it is available. The reason is that it depends on
xorg-video-abi-18, which does not exist in sid.

-Ralf.

Bug#855957: unblock: coreutils/8.26-3

[Michael Stone]

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

Please unblock package coreutils. SHA performance problem caused by buggy gcc
optimizer seems to make powerpc users sad. Change is fairly trivial and
architecture-specific. 

--- coreutils-8.26/debian/changelog 2017-01-20 09:46:22.0 -0500
+++ coreutils-8.26/debian/changelog 2017-02-22 07:23:45.0 -0500
@@ -1,3 +1,11 @@
+coreutils (8.26-3) unstable; urgency=medium
+
+  * Update standards version to 3.9.8.0 (no changes)
+  * Add -fno-schedule-insns to CFLAGS for sha256.o on PPC to fix
+performance regression (Closes: #854053)
+
+ -- Michael Stone   Wed, 22 Feb 2017 07:23:45 -0500
+
 coreutils (8.26-2) unstable; urgency=low
 
   * Fix regression in which specifying a TZ in date -d causes the 
diff -Nru coreutils-8.26/debian/control coreutils-8.26/debian/control
--- coreutils-8.26/debian/control   2016-01-29 10:53:58.0 -0500
+++ coreutils-8.26/debian/control   2017-01-24 07:56:59.0 -0500
@@ -2,7 +2,7 @@
 Maintainer: Michael Stone 
 Section: utils
 Priority: required
-Standards-Version: 3.9.6.0
+Standards-Version: 3.9.8.0
 Build-Depends: gettext (>= 0.10.37), debhelper (>= 9.20120115), autotools-dev, 
texinfo (>= 4.2), groff, libattr1-dev [linux-any], libacl1-dev [linux-any], 
libselinux1-dev (>= 1.32) [linux-any], gperf, bison
 
 Package: coreutils
diff -Nru coreutils-8.26/debian/patches/ppc_sha256_flags.patch 
coreutils-8.26/debian/patches/ppc_sha256_flags.patch
--- coreutils-8.26/debian/patches/ppc_sha256_flags.patch1969-12-31 
19:00:00.0 -0500
+++ coreutils-8.26/debian/patches/ppc_sha256_flags.patch2017-02-22 
07:18:59.0 -0500
@@ -0,0 +1,15 @@
+Index: coreutils-8.26/Makefile.in
+===
+--- coreutils-8.26.orig/Makefile.in2016-11-30 13:34:55.0 -0500
 coreutils-8.26/Makefile.in 2017-02-22 07:18:55.352394058 -0500
+@@ -14661,6 +14661,10 @@
+ 
+ $(TEST_LOGS): $(PROGRAMS)
+ 
++ifeq ($(DEB_TARGET_ARCH), ppc64el)
++lib/sha256.o: CFLAGS+=-fno-schedule-insns
++endif
++
+ # Tell versions [3.59,3.63) of GNU make to not export all variables.
+ # Otherwise a system limit (for SysV at least) may be exceeded.
+ .NOEXPORT:
diff -Nru coreutils-8.26/debian/patches/series 
coreutils-8.26/debian/patches/series
--- coreutils-8.26/debian/patches/series2017-01-20 09:37:07.0 
-0500
+++ coreutils-8.26/debian/patches/series2017-02-22 07:18:48.0 
-0500
@@ -1,3 +1,4 @@
+ppc_sha256_flags.patch
 date_tz_handling
 no_ls_quoting.patch
 61_whoips.patch

unblock coreutils/8.26-3

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

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

Bug#855956: linux-image-4.9.0-0.bpo.1-amd64-unsigned: kworker blocked for more than 120 seconds.

[E Barker]

Package: linux-image-4.9.0-0.bpo.1-amd64-unsigned
Version: 4.9.2-2~bpo8+1
Severity: important

Dear Debian folks,

Apologies for the duplication, sending to the main submission list.

After upgrading 3 Debian Jessie servers to kernel 4.9.2 from
jessie-backports I encountered multiple
kernel traces on 3 separate servers at random times after boot. As a
result, one of the kworker processes
and several user space pids are stuck in 'D' state and encounter
issues accessing the XFS file system.

A proper shutdown will not complete and a reset is required when this
occurs. In one case this caused
file system corruption and prevented the server from booting normally
(dropped into a generic grub shell).

No specific workflow to trigger these events (so far).

The systems involved are:

System Information
Manufacturer: Supermicro
Product Name: X9DRT

System Information
Manufacturer: Supermicro
Product Name: X8DTT-H

The example traces are as follows:

[812709.892923] INFO: task kworker/u49:0:13127 blocked for more than
120 seconds.
[812709.892989]   Tainted: GE   4.9.0-0.bpo.1-amd64 #1
[812709.893031] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[812709.893085] kworker/u49:0   D0 13127  2 0x
[812709.893100] Workqueue: writeback wb_workfn (flush-253:0)
[812709.893104]  8f8d1a76d800  8f8d1bda3140
8f8aa3e550c0
[812709.893108]  8f8d1fb587c0 b6820c9477a0 81ff536d
0001c053ad80
[812709.893112]   18af7798 81abb2ee
8f8aa3e550c0
[812709.893116] Call Trace:
[812709.893125]  [] ? __schedule+0x23d/0x6d0
[812709.893130]  [] ? __wake_up_common+0x4e/0x90
[812709.893133]  [] ? bit_wait_timeout+0x90/0x90
[812709.893135]  [] ? schedule+0x32/0x80
[812709.893138]  [] ? schedule_timeout+0x21c/0x3c0
[812709.893145]  [] ? blk_flush_plug_list+0xa0/0x220
[812709.893148]  [] ? blk_flush_plug_list+0xa0/0x220
[812709.893151]  [] ? bit_wait_timeout+0x90/0x90
[812709.893153]  [] ? io_schedule_timeout+0xb4/0x130
[812709.893156]  [] ? prepare_to_wait_exclusive+0x57/0x80
[812709.893158]  [] ? bit_wait_io+0x17/0x60
[812709.893161]  [] ? __wait_on_bit_lock+0x7f/0xb0
[812709.893163]  [] ? bit_wait_timeout+0x90/0x90
[812709.893166]  [] ? out_of_line_wait_on_bit_lock+0x7e/0xa0
[812709.893169]  [] ? autoremove_wake_function+0x40/0x40
[812709.893238]  [] ? xfs_do_writepage+0x44d/0x700 [xfs]
[812709.893244]  [] ? page_mkclean+0x6e/0xc0
[812709.893247]  [] ? __page_check_address+0x1b0/0x1b0
[812709.893252]  [] ? write_cache_pages+0x207/0x480
[812709.893299]  [] ? xfs_aops_discard_page+0x130/0x130 [xfs]
[812709.893310]  [] ? dm_make_request+0x76/0xc0 [dm_mod]
[812709.893356]  [] ? xfs_vm_writepages+0xba/0xf0 [xfs]
[812709.893360]  [] ? __writeback_single_inode+0x3d/0x330
[812709.893363]  [] ? writeback_sb_inodes+0x23d/0x470
[812709.893367]  [] ? __writeback_inodes_wb+0x87/0xb0
[812709.893371]  [] ? wb_writeback+0x282/0x310
[812709.893374]  [] ? wb_workfn+0x214/0x3e0
[812709.893378]  [] ? process_one_work+0x14b/0x410
[812709.893381]  [] ? worker_thread+0x65/0x4a0
[812709.893383]  [] ? rescuer_thread+0x340/0x340
[812709.893386]  [] ? rescuer_thread+0x340/0x340
[812709.893390]  [] ? do_group_exit+0x39/0xb0
[812709.893393]  [] ? kthread+0xe0/0x100
[812709.893398]  [] ? __switch_to+0x2bb/0x700
[812709.893401]  [] ? kthread_park+0x60/0x60
[812709.893405]  [] ? ret_from_fork+0x25/0x30

Server2:
[1004725.175725] INFO: task kworker/u49:2:20785 blocked for more than
120 seconds.
[1004725.175790]   Not tainted 4.9.0-0.bpo.1-amd64 #1
[1004725.175818] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[1004725.175859] kworker/u49:2   D0 20785  2 0x
[1004725.175875] Workqueue: writeback wb_workfn (flush-253:0)
[1004725.175879]  92d41a0efc00  92cc1bdb3080
92cbcfb5b0c0
[1004725.175882]  92cc1fc187c0 a85ae2aab7a0 aa3f536d
0001c0326d80
[1004725.175885]   1b30ca18 a9ebb2ee
92cbcfb5b0c0
[1004725.175888] Call Trace:
[1004725.175898]  [] ? __schedule+0x23d/0x6d0
[1004725.175904]  [] ? __wake_up_common+0x4e/0x90
[1004725.175906]  [] ? bit_wait_timeout+0x90/0x90
[1004725.175908]  [] ? schedule+0x32/0x80
[1004725.175910]  [] ? schedule_timeout+0x21c/0x3c0
[1004725.175918]  [] ? blk_flush_plug_list+0xa0/0x220
[1004725.175921]  [] ? blk_flush_plug_list+0xa0/0x220
[1004725.175923]  [] ? bit_wait_timeout+0x90/0x90
[1004725.175925]  [] ? io_schedule_timeout+0xb4/0x130
[1004725.175927]  [] ? prepare_to_wait_exclusive+0x57/0x80
[1004725.175928]  [] ? bit_wait_io+0x17/0x60
[1004725.175930]  [] ? __wait_on_bit_lock+0x7f/0xb0
[1004725.175932]  [] ? bit_wait_timeout+0x90/0x90
[1004725.175934]  [] ? out_of_line_wait_on_bit_lock+0x7e/0xa0
[1004725.175936]  [] ? autoremove_wake_function+0x40/0x40
[1004725.176006]  [] ? xfs_do_writepage+0x44d/0x700 [xfs]
[1004725.176011]  [] ? page_mkclean+0x6e/0xc0

Bug#855955: aisleriot: Variants "Westhaven" and "Diamond-Mine" interfere: crash with wrong-number-of-args

[Ben Wiederhake]

Package: aisleriot
Version: 1:3.22.1-1
Severity: normal

Dear Maintainer,

first of all: I'm unable to run the program with LC_ALL=C, so I'm sorry that
I can only provide the German name.
The German names are "Westhafen" and "Diamantenmine", which translates to
"Westhaven" and "Diamonmine".

The error is an "unexpected scheme error", which appears to be a 
wrong-number-of-args exception.
If I read the stack trace correctly, then this is due to some remnant code from 
Diamondmine
calling into code from Westhaven.

Steps to reproduce:
- Start aisleriot
- Select "Diamondmine"
- Quit aisleriot (apparently it's necessary that the *starting* game is 
Diamondmine)
- Start aisleriot
- Play a full game (not sure in how far this is necessary, but if you play 
through
  a whole game then it *always* happens.)
- Select "Westhaven"

Expected behavior:
Westhaven starts.

Actual behavior, on my i386 system:
The canvas goes blank (well, background-green), a dialog opens up saying
"Ein Schema-Ausnahmefehler ist aufgetreten
Bitte melden Sie diesen Fehler an die Entwickler.
[Nicht melden] [Melden]"
which translates to something like:
"An unexpected scheme exception occurred
Please report this issue to the developers.
[Don't report] [Report]"
Those brackets are supposed to indicate buttons.

Actual behavior 2, on my amd64 system (used to generate this report) :
Westhaven appears to start normally, but within a few actions (1 or 2, 
typically),
the above-mentioned dialog pops up.

Clicking "Report" doesn't do anything, and on the console reports that 
"bug-buddy"
couldn't be launched, which I guess is their intended bug reporter.
Since there doesn't seem to be a package called "bug-buddy",
or any package containing a relevant file [1],
I can't use this (apparently desired) path for this bug report.

After dealing with this error, Westhaven loads successfully, but may 
intermittently
crash and restart (the particular game, not aisleriot as a whole) during 
operation.

Manual workaround:
Restart aisleriot so that Westhaven is selected from the very beginning.

Please find attached a generated crash report by aisleriot, on my amd64 system.
I assume that aisleriot attempted to forward these data to "bug-buddy".
It includes stacktraces which indicate that Diamondmine somehow calls into 
Westhaven,
up to impedance mismatch.

Cheers,
Ben Wiederhake

[1] 
https://packages.debian.org/search?suite=testing=any=filename=contents=bug-buddy


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

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

Versions of packages aisleriot depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  gconf-service3.2.6-4
ii  gconf2   3.2.6-4
ii  guile-2.0-libs   2.0.13+1-4
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-9
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libcanberra-gtk3-0   0.30-3
ii  libcanberra0 0.30-3
ii  libgc1c2 1:7.4.2-8
ii  libgconf-2-4 3.2.6-4
ii  libgdk-pixbuf2.0-0   2.36.4-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk-3-0   3.22.7-2
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  librsvg2-2   2.40.16-1
ii  libx11-6 2:1.6.4-3

Versions of packages aisleriot recommends:
ii  yelp  3.22.0-1

Versions of packages aisleriot suggests:
pn  gnome-cards-data  

-- no debconf information
Variation: westhaven
Scheme error:
(#f Wrong number of arguments to ~A (#) #f)
Scheme tag:
wrong-number-of-args

Backtrace:
In ice-9/boot-9.scm:
 160: 8 [catch #t # ...]
In unknown file:
   ?: 7 [apply-smob/1 #]
In ice-9/boot-9.scm:
 160: 6 [catch #t # ...]
In unknown file:
   ?: 5 [apply-smob/1 #]
In westhaven.scm:
 304: 4 [get-hint]
 271: 3 [tableau-to-tableau? 6 10]
In diamond-mine.scm:
 278: 2 [find-card 6 (12 0 #t)]
In ice-9/boot-9.scm:
 105: 1 [# 
wrong-number-of-args ...]
In unknown file:
   ?: 0 [apply-smob/1 # wrong-number-of-args ...]


Deck State:
Slot 0
(3 3 #f) ,(0 5 #f) ,(0 8 #f)
 ,(3 8 #f) ,(1 13 #f) ,(1 7 #f) ,(3 10 #f) ,(0 4 #f) ,(0 10 #f) ,(3 7 #f) ,(3 
12 #f) ,(0 6 #f) ,(2 6 #f) ,(2 11 #f)
Slot 1
(Empty)
Slot 2
(2 1 #t)
Slot 3
   

Bug#855579: gitlab: fails to purge - command in postrm not found: dropdb

[Adrian Bunk]

Control: severity -1 serious

On Mon, Feb 20, 2017 at 12:13:37PM +0100, Andreas Beckmann wrote:
> Package: gitlab
> Version: 8.13.11+dfsg-3
> Severity: important
> User: debian...@lists.debian.org
> Usertags: piuparts
>...
> Filing this as important because a.) it's a clear policy violation (to
> not clean up at purge) b.) having a piuparts clean archive is a release
> goal since lenny and c.) this package being piuparts buggy blocks
> packages depending on it from being tested by piuparts (and thus
> possibly the detection of more severe problems).
>...

I am raising the severity to serious since this piuparts issue is
blocking the testing migration of gitlab.

> cheers,
> 
> Andreas

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#336001: proftpd: improving documentation

[Hilmar Preuße]

tags 336001 + fixed-upstream
stop

Am 27.10.2005 um 11:54 tastete Fabrice LORRAIN:

Hi,


This is a follow-up to BTS #335902.

The problem reported in this previous bug report, sum up in been a
configuration error. This problem would have been avoided with a better
documentation of the Maxinstance directive.

I would suggest changing the MaxIntances description in
file:///usr/share/doc/proftpd-doc/Configuration.html with the following:

Upstream adapted your phrasing, see [1]. I tag that bug a fixed upstream 
for now, as the updated docs will be contained in one of the next releases.


Hilmar

[1] http://www.proftpd.org/docs/modules/mod_core.html#MaxInstances
--
#206401 http://counter.li.org

Bug#845979: workaround to the bug

[Brent Van Dussen]

Hi Bugs Team,

I am also experiencing the same libqmi error (64) when trying to connect to
the Internet using my Sierra Wireless MC7700 and the latest libqmi-utils
1.16.2-1 version.

root@vanputer:/home/bvd# qmicli -d /dev/cdc-wdm0
--wds-start-network="apn=broadband" --client-no-release-cid
error: couldn't start network: QMI protocol error (64): '(null)'
[/dev/cdc-wdm0] Client ID not released:
Service: 'wds'
CID: '2'

root@vanputer:/home/bvd# qmicli -d /dev/cdc-wdm0
--wds-start-network="apn=broadband,ip-type=4" --client-no-release-cid
[/dev/cdc-wdm0] Network started
Packet data handle: '41221944'
[/dev/cdc-wdm0] Client ID not released:
Service: 'wds'
CID: '4'

For some reason the ip-type=4 is required now in the --wds-start-network
command and it's not called for in the qmicli

I also had to modify /usr/bin/qmi-network start_network() subroutine as
follows:

START_NETWORK_ARGS="'apn=$APN'"

before the placement of quotes was incorrect and qmicli wasn't accepting
the argument with the two values.

Thanks so much for this great collection of packages and software and
hopefully this helps someone out in the meantime while patches make their
way to new distros.

Happy Open Sourcing!
-Brent

Bug#855954: ci.debian.net: confused by package names containing "+" ?

[Ralf Treinen]

Package: debci

Hello,

ci.debian.net has never succeeded in running the testsuite of the
minisat+ package. In the summary table for that package, the version
is only displayed as n/a. Furthermore, the test log says :

adt-run [05:21:43]:  apt-source minisat+
E: Version '1:2.2.1-5+b1' for 'minisat+' was not found
E: No packages found
blame: minisat+

However, 1:2.2.1-5+b1 is not the version of the "minisat+" package in sid
- it rather is the version of the package "minisat2" in sid ! I suppose
that debci gets confused by the "+ in the package name.

Cheers -Ralf.

Bug#855953: mplayer: Stops playing when switching to text consoles

[Helge Kreutzmann]

Package: mplayer
Version: 2:1.3.0-6
Severity: normal

When I play videos and switch to text consoles (via Ctrl-Alt-F1 for
example) audio and video playback stops and is not resumed until I
return to the X shell again.

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

Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mplayer depends on:
ii  liba52-0.7.4  0.7.4-19
ii  libaa11.4p5-44
ii  libasound21.1.3-5
ii  libass5   1:0.13.4-2
ii  libaudio2 1.9.4-5
ii  libavcodec57  7:3.2.4-1
ii  libavformat57 7:3.2.4-1
ii  libavutil55   7:3.2.4-1
ii  libbluray11:0.9.3-3
ii  libbs2b0  3.1.0+dfsg-2.2
ii  libc6 2.24-9
ii  libcaca0  0.99.beta19-2+b1
ii  libcdio-cdda1 0.83-4.3
ii  libcdio-paranoia1 0.83-4.3
ii  libcdio13 0.83-4.3
ii  libdca0   0.0.5-10
ii  libdirectfb-1.2-9 1.2.10.0-8
ii  libdv41.0.0-11
ii  libdvdnav45.0.3-3
ii  libdvdread4   5.0.3-2
ii  libenca0  1.19-1
ii  libfaad2  2.8.0~cvs20161113-1
ii  libfontconfig12.11.0-6.7
ii  libfreetype6  2.6.3-3+b1
ii  libfribidi0   0.19.7-1
ii  libgif7   5.1.4-0.4
ii  libgl1-mesa-glx [libgl1]  13.0.4-1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.10+20150825git1ed50c92~dfsg-4+b1
ii  libjpeg62-turbo   1:1.5.1-2
ii  liblirc-client0   0.9.4c-7
ii  libmad0   0.15.1b-8
ii  libmpeg2-40.5.1-7
ii  libmpg123-0   1.23.8-1
ii  libogg0   1.3.2-1
ii  libopenal11:1.17.2-4
ii  libpng16-16   1.6.28-1
ii  libpostproc54 7:3.2.4-1
ii  libpulse0 10.0-1
ii  libsdl1.2debian   1.2.15+dfsg1-4
ii  libsmbclient  2:4.5.4+dfsg-1
ii  libspeex1 1.2~rc1.2-1
ii  libswresample27:3.2.4-1
ii  libswscale4   7:3.2.4-1
ii  libtheora01.1.1+dfsg.1-14
ii  libtinfo5 6.0+20161126-1
ii  libvdpau1 1.1.1-6
ii  libvorbisidec11.0.2+svn18153-1
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1
ii  libxinerama1  2:1.1.3-1+b1
ii  libxss1   1:1.2.2-1
ii  libxv12:1.0.11-1
ii  libxvidcore4  2:1.3.4-1
ii  libxvmc1  2:1.0.10-1
ii  libxxf86dga1  2:1.1.4-1+b1
ii  libxxf86vm1   1:1.1.4-1
ii  zlib1g1:1.2.8.dfsg-5

mplayer recommends no packages.

Versions of packages mplayer suggests:
ii  bzip2   1.0.6-8.1
ii  fontconfig  2.11.0-6.7
ii  fonts-freefont-ttf  20120503-6
ii  mplayer-doc 2:1.3.0-6
pn  netselect | fping   

-- no debconf information

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: Digital signature

Bug#833190: Please provide an option to not add X-getmail-retrieved-from-mailbox header

[Daniel Kahn Gillmor]

Control: tags 833190 + patch

On Mon 2016-08-01 19:25:38 -0400, Josh Triplett wrote:

> When getmail retrieves a mail, it unconditionally adds a header
> X-getmail-retrieved-from-mailbox with the name of the mailbox it retrieved the
> mail from.  As far as I can tell, getmail doesn't have any option to avoid
> adding that header.  I'd like to leave the mail completely unmodified.  Would
> you consider adding an option to not add that header?

I went to report this issue on the BTS, but saw that Josh has beaten me
to it, as usual. :)

Attached is a patch that seems to work for me.

To use it, i added:

 record_retrieved_from_mailbox = False

to the [Retriever] section of ~/.getmail/config/mymailprovider

Feel free to forward it upstream :)

hth,

 --dkg

From: Daniel Kahn Gillmor 
Date: Thu, 23 Feb 2017 13:56:54 -0500
Subject: Make X-getmail-retrieved-from-mailbox optional (Closes: #833190)

In https://bugs.debian/833190, Josh Triplett asked for getmail to
avoid modifying messages as they are fetched via IMAP.

This should provide such an option.
---
 docs/configuration.html| 7 +++
 docs/configuration.txt | 5 +
 getmailcore/_retrieverbases.py | 7 ---
 getmailcore/retrievers.py  | 4 
 4 files changed, 20 insertions(+), 3 deletions(-)

diff --git a/docs/configuration.html b/docs/configuration.html
index 0508ddf..c79610a 100644
--- a/docs/configuration.html
+++ b/docs/configuration.html
@@ -635,6 +635,13 @@ mailboxes = ALL
 http://honk.sigxcpu.org/projects/pykerberos/;>http://honk.sigxcpu.org/projects/pykerberos/;
 for details.
 
+
+record_retrieved_from_mailbox
+(boolean)
+ whether to add a X-getmail-retrieved-from-mailbox header
+to each message fetched; the default is True.  Note that setting this to False
+will break the use of %(mailbox) as a substitution in MDA_external arguments.
+
 
 
 SSL Client Parameters
diff --git a/docs/configuration.txt b/docs/configuration.txt
index a3cbe0d..ed4fdc0 100644
--- a/docs/configuration.txt
+++ b/docs/configuration.txt
@@ -401,6 +401,11 @@ mailboxes = ALL
pykerberos with GSS support is installed; check your OS
distribution or see http://honk.sigxcpu.org/projects/pykerberos/;
for details.
+ * record_retrieved_from_mailbox (boolean) -- whether to add a
+   X-getmail-retrieved-from-mailbox header to each message
+   fetched; the default is True.  Note that setting this to False
+   will break the use of %(mailbox) as a substitution in
+   MDA_external arguments.
 
 SSL Client Parameters
 
diff --git a/getmailcore/_retrieverbases.py b/getmailcore/_retrieverbases.py
index e4592e0..31e7170 100755
--- a/getmailcore/_retrieverbases.py
+++ b/getmailcore/_retrieverbases.py
@@ -1556,9 +1556,10 @@ class IMAPRetrieverBase(RetrieverSkeleton):
 raise getmailRetrievalError('failed to retrieve msgid %s' 
 % msgid)
 
-# record mailbox retrieved from in a header
-msg.add_header('X-getmail-retrieved-from-mailbox', 
-   self.mailbox_selected)
+if self.conf['record_retrieved_from_mailbox']:
+# record mailbox retrieved from in a header
+msg.add_header('X-getmail-retrieved-from-mailbox', 
+   self.mailbox_selected)
 
 # google extensions: apply labels, etc
 if 'X-GM-EXT-1' in self.conn.capabilities:
diff --git a/getmailcore/retrievers.py b/getmailcore/retrievers.py
index 6e82df7..a2b36bb 100755
--- a/getmailcore/retrievers.py
+++ b/getmailcore/retrievers.py
@@ -376,6 +376,7 @@ class SimpleIMAPRetriever(IMAPRetrieverBase, IMAPinitMixIn):
 # .authenticate(), so we can't do this yet (?).
 ConfBool(name='use_cram_md5', required=False, default=False),
 ConfBool(name='use_kerberos', required=False, default=False),
+ConfBool(name='record_retrieved_from_mailbox', required=False, default=True),
 )
 received_from = None
 received_with = 'IMAP4'
@@ -423,6 +424,7 @@ class SimpleIMAPSSLRetriever(IMAPRetrieverBase, IMAPSSLinitMixIn):
 # .authenticate(), so we can't do this yet (?).
 ConfBool(name='use_cram_md5', required=False, default=False),
 ConfBool(name='use_kerberos', required=False, default=False),
+ConfBool(name='record_retrieved_from_mailbox', required=False, default=True),
 )
 received_from = None
 received_with = 'IMAP4-SSL'
@@ -463,6 +465,7 @@ class MultidropIMAPRetriever(MultidropIMAPRetrieverBase, IMAPinitMixIn):
 ConfBool(name='use_cram_md5', required=False, default=False),
 ConfBool(name='use_kerberos', required=False, default=False),
 ConfString(name='envelope_recipient'),
+ConfBool(name='record_retrieved_from_mailbox', required=False, default=True),
 )
 received_from = None
 

Bug#855951: libsecret FTBFS with test failures on many architectures

[Adrian Bunk]

Source: libsecret
Version: 0.18.5-2
Severity: serious

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

FAIL: test-collection 18 /collection/delete-sync
- arm*
- i386
- ppc64el
- s390x

FAIL: test-session 4 /session/ensure-async-aes
- mipsel

Bug#855606: sqrt() regression on powerpc/jessie

[James Cloos]

> Christoph Berg  writes:

> Jessie: 0X1.C48C6001F0ABFP+3
> Sid:0X1.C48C6001F0ACP+3

Looking tat the code glibc switched from fsqrt to a software version,
resulting in the ulp difference.

I see on pgsql-hackers, though, that glibc has enabled fma and as a
result that difference is avoided.

So jessie's libc6 on ppc32 needs to include the fma patch or switch back
to using fsqrt.

-JimC
-- 
James Cloos  OpenPGP: 0x997A9F17ED7DAEA6

Bug#855952: unblock: vlc/2.2.4-14

[Sebastian Ramacher]

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

Please unblock package vlc version 2.2.4-14. It updates the embedded copy of
ffmpeg 2.8 to the latest upstream bug fix release.

Since debdiff does not cope very well with multi-component upstream tarballs,
there are two diffs attached. vlc.diff contains the changes to debian/ and
ffmpeg.diff contains the changes between ffmpeg 2.8.10 and 2.8.11.

The changelog for ffmpeg 2.8.11 is below. The release fixes CVE-2016-9561,
CVE-2017-5024 and CVE-2017-5025.

version 2.8.11
- avcodec/h264_slice: Clear ref_counts on redundant slices
- lavf/mov.c: Avoid heap allocation wrap in mov_read_uuid
- lavf/mov.c: Avoid heap allocation wrap in mov_read_hdlr
- avcodec/pictordec: Fix logic error
- avcodec/movtextdec: Fix decode_styl() cleanup
- lavf/matroskadec: fix is_keyframe for early Blocks
- configure: bump year
- avcodec/pngdec: Check trns more completely
- avcodec/interplayvideo: Move parameter change check up
- avcodec/mjpegdec: Check for for the bitstream end in 
mjpeg_decode_scan_progressive_ac()
- avformat/flacdec: Check avio_read result when reading flac block header.
- avcodec/utils: correct align value for interplay
- avcodec/vp56: Check for the bitstream end, pass error codes on
- avcodec/mjpegdec: Check remaining bitstream in ljpeg_decode_yuv_scan()
- avcodec/pngdec: Fix off by 1 size in decode_zbuf()
- avformat/avidec: skip odml master index chunks in avi_sync
- avcodec/mjpegdec: Check for rgb before flipping
- avutil/random_seed: Reduce the time needed on systems with very low precision 
clock()
- avutil/random_seed: Improve get_generic_seed() with higher precision clock()
- avformat/utils: Print verbose error message if stream count exceeds 
max_streams
- avformat/options_table: Set the default maximum number of streams to 1000
- avutil: Add av_image_check_size2()
- avformat: Add max_streams option
- avcodec/ffv1enc: Allocate smaller packet if the worst case size cannot be 
allocated
- avcodec/mpeg4videodec: Fix undefined shifts in 
mpeg4_decode_sprite_trajectory()
- avformat/oggdec: Skip streams in duration correction that did not had their 
duration set.
- avcodec/ffv1enc: Fix size of first slice
- pgssubdec: reset rle_data_len/rle_remaining_len on allocation error


unblock vlc/2.2.4-14


Cheers
-- 
Sebastian Ramacher
diff --git a/debian/changelog b/debian/changelog
index 781f9848c9..739c269c42 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+vlc (2.2.4-14) unstable; urgency=medium
+
+  [ Mateusz Łukasik ]
+  * Update to ffmpeg 2.8.11.
+
+ -- Sebastian Ramacher   Tue, 14 Feb 2017 20:17:50 +0100
+
 vlc (2.2.4-13) unstable; urgency=medium
 
   * debian/control: Switch to libopenmpt's libmodplug comat layer.
diff --git a/debian/rules b/debian/rules
index 35ebba4e17..8d48ec81b8 100755
--- a/debian/rules
+++ b/debian/rules
@@ -346,7 +346,7 @@ override_dh_autoreconf:
 override_dh_auto_configure:
mkdir -p $(ffmpegbuild) $(ffmpegprefix)
cd $(ffmpegbuild) && \
-   $(CURDIR)/ffmpeg-2-8-10/configure $(ffmpegflags)
+   $(CURDIR)/ffmpeg-2-8-11/configure $(ffmpegflags)
dh_auto_build --sourcedirectory $(ffmpegbuild) -- V=1
$(MAKE) -C $(ffmpegbuild) install-libs install-headers V=1
PKG_CONFIG_PATH=$(ffmpegprefix)/lib/pkgconfig \
diff --git a/debian/watch b/debian/watch
index 764a7c1834..8c442743e7 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,5 +1,5 @@
 version=4
 opts=pgpsigurlmangle=s/$/.asc/ \
 
http://download.videolan.org/pub/videolan/vlc/([\d][\d\.]+[a-z]?)/vlc-([\d][\d\.]+[a-z]?)\.tar\.xz
 debian
-opts=component=ffmpeg-2-8-10 \
-https://ffmpeg.org/releases/ffmpeg-2\.8\.([0-9.]+)\.tar\.xz 2.8.10
+opts=component=ffmpeg-2-8-11 \
+https://ffmpeg.org/releases/ffmpeg-2\.8\.([0-9.]+)\.tar\.xz 2.8.11
diff --git a/Changelog b/Changelog
index ac863b2260..83004c4fd9 100644
--- a/Changelog
+++ b/Changelog
@@ -1,6 +1,36 @@
 Entries are sorted chronologically from oldest to youngest within each release,
 releases are sorted from youngest to oldest.
 
+version 2.8.11
+- avcodec/h264_slice: Clear ref_counts on redundant slices
+- lavf/mov.c: Avoid heap allocation wrap in mov_read_uuid
+- lavf/mov.c: Avoid heap allocation wrap in mov_read_hdlr
+- avcodec/pictordec: Fix logic error
+- avcodec/movtextdec: Fix decode_styl() cleanup
+- lavf/matroskadec: fix is_keyframe for early Blocks
+- configure: bump year
+- avcodec/pngdec: Check trns more completely
+- avcodec/interplayvideo: Move parameter change check up
+- avcodec/mjpegdec: Check for for the bitstream end in mjpeg_decode_scan_progressive_ac()
+- avformat/flacdec: Check avio_read result when reading flac block header.
+- avcodec/utils: correct align value for interplay
+- avcodec/vp56: Check for the bitstream end, pass error codes on
+- avcodec/mjpegdec: Check remaining bitstream in ljpeg_decode_yuv_scan()
+- avcodec/pngdec: Fix off by 1 size in 

Bug#724627: cracklib-runtime: cracklib-check should deny key-runs with dvorak keyboard variants

[Alexander Perlis]

It's not that qwerty layout runs per se are denied, it's that too many 
consecutive character pairs are denied. Certain qwerty layout runs 
simply happen to contain many consecutive character pairs.


As the prior message observes, the bug is annoying: augmenting an 
otherwise acceptable password by appending consecutive characters 
renders it no longer acceptable!


The bug is real, but has nothing to do with qwerty-vs-dvorak. The Fedora 
project addresses it by simply disregarding consecutive character pairs 
as adding any "length strength".


-/*  Change by Ben Karsin from ITS at University of Hawaii at Manoa. 
 Static MAXSTEP

-would generate many false positives for long passwords. */
-maxrepeat = 3+(0.09*strlen(password));
-if (i > maxrepeat)
+/*  We were still generating false positives for long passwords.
+Just count systematic double as a single character. */
+if (len - i < MINLEN)

Regards,
Alex

Bug#855219: ghostscript: Please add gspcl

[Patrik Schindler]

Hello Jonas,

Am 23.02.2017 um 19:51 schrieb Jonas Smedegaard :

>> So I may look forward for a gpcl package for unstable in a not all to 
>> far future?
> Yes.

Thank you very much!

> ...and if at some point in time you realize that "not all too far" have 
> different meaning for me than for you, then feel free to ping this 
> bugreport - or roll up your sleeves and join the packaging effort!

Since it will for sure not make it to testing, I don’t expect anything before 
unstable becomes the new testing. Of course there is a short cut called 
backports… ;-)

I’m still not seasoned enough in packaging such a complex beast like gs or 
gpcl. in fact, I’m glad if I can do proper packaging for my planned PDF-Tool.

:wq! PoC