Bug#807040: crashed with 4.3

[Adam Borowski]

... and here comes the crash.
So it looks like the nouveau overhaul in 4.3 is not a fix, at least for my
hardware (GT 240).

-- 
A tit a day keeps the vet away.

Bug#807469: RM: wine-gecko-2.21 -- ROM; obsolete

[Stephen Kitt]

Package: ftp.debian.org
Severity: normal

Dear FTP team,

Nothing depends on wine-gecko-2.21 in unstable any more, and nothing
ever will again; I'd appreciate it if you could remove it!
(wine-gecko-2.40 will appear in NEW in due course...)

Thanks in advance,

Stephen

Bug#807468: mirror submission for mirrors.noction.com

[Noction Mirrors Service]

Package: mirrors
Severity: wishlist

Submission-Type: new
Site: mirrors.noction.com
Type: leaf
Archive-architecture: ALL amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mipsel powerpc s390x sparc 
Archive-ftp: /debian/debian/
Archive-http: /debian/debian/
Backports-ftp: /debian/debian-backports/
Backports-http: /debian/debian-backports/
CDImage-ftp: /debian/debian-cd/
CDImage-http: /debian/debian-cd/
IPv6: no
Archive-upstream: ftp.nl.debian.org
Backports-upstream: mirror.nl.leaseweb.net
CDImage-upstream: cdimage.debian.org
Updates: four
Maintainer: Noction Mirrors Service 
Country: NL Netherlands

Bug#798066: Multiarch-renamed python extensions not found during autopkgtest testing

[Afif Elghraoui]

Hi, debian-python,

For Debian Med's python packages that have compiled extensions, I
noticed that test suites run via autopkgtest fail because the package
cannot find those extensions, as they've been renamed with the multiarch
triplet.

It seems to only be a problem with autopkgtest because I have in one
case manually installed such a package and successfully ran its test
suite. I therefore reported #798066 [1] against autopkgtest, but quite
some time has elapsed since then and I'd like to get this resolved.

Does anyone know why this might be the case? Autopkgtest for these
packages is currently not very helpful because there are many spurious
failures due to this issue. There are more details in my original bug
report [1].

Many thanks and regards
Afif

1. http://bugs.debian.org/798066

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#807453: [Pkg-amule-devel] Bug#807453: amule: BaseClient.cpp(2143): assert "Assert failure" failed in ProcessPublicKeyPacket().

[Dmitry Smirnov]

On Wednesday 09 December 2015 06:34:20 Sandro Tosi wrote:
> To report a useful backtrace to developers please install amule-dbg,
> then run amule in gdb and when it crashed run these gdb command: bt;
> bt full; thread apply all bt   and report the output here (or on the
> github bug)
 
Thanks for reminder. This was just a quick backtrace dump as reported by 
amule's own crash handler (with "amule-dbg" installed).

Taking proper backtrace with "bt; bt full; thread apply all bt" might take a 
while assuming that it is possible to reproduce the crash...
For instance running aMule under gdb for a week was not enough to reproduce 
#795058...

If I encounter this "Assert failure" few more times I'll try to get a better 
backtrace.

-- 
Best wishes,
 Dmitry Smirnov.


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

Bug#805052: bitcoin: New upstream version

[Uwe Kleine-König]

Package: bitcoin-qt
Version: 0.11.1-1
Followup-For: Bug #805052

Hello,

I guess the new upstream release is also the reason that bitcoin-qt
shows a warning message now:

Warning: This version is obsolete; upgrade required!

?

Best regards
Uwe

Bug#807420: lwjgl: FTBFS on ppc64el: error: wrong type argument to unary exclamation mark

[tony mancill]

On 12/08/2015 08:32 AM, Fernando Seiti Furusato wrote:
> Source: lwjgl
> Version: 2.7.1+dfsg-4
> Severity: normal
> Tags: patch
> 
> Dear Maintainer,
> 
> I am aware that this package has a newer version available.
> But since it is in the repository, it would be good to have it building on
> ppc64el as well.
> 
> The reason for the failure is because altivec is enabled by default on
> ppc64el so all gets compiled with flag -maltivec on.
> Consequently, macros definitions from altivec.h such as bool, vector and 
> pixel get replaced along the code.
> 
> I included -mcpu-powerpc if the arch is ppc64le, but I am not sure this is
> the best way to do so.
> 
> I know it works, because I tested on x86_64 and ppc64el.

Hi Fernando,

thank you for the bug report and the patch.  I'll get this uploaded so
we're building on ppc64el.

Cheers,
tony



signature.asc
Description: OpenPGP digital signature

Bug#807407: icedove: stable 38.4 seems to forget SMTP password, can't send email

[Carsten Schoenert]

On Tue, Dec 08, 2015 at 04:03:59PM +0100, W. Martin Borgert wrote:
> >There is also a hint for iceowl-extension on not remebered passwords,
> >maybe this is issue?
> >
> >https://wiki.debian.org/Icedove#Iceowl-extension_does_not_remember_credentials
> 
> This is problably the cause of the message, that I related
> wrongly to the SMTP sending failure.
> 
> I wonder what your SMTP config is? Mine is:
> 
> Server: mydomain.com
> Port: 587
> Username: username
> Auth method: NTLM
> Security: STARTTLS

We use slightly the same configuration except small differences, but we got
also a load balancer between me and the exchange backend.

Security:   STARTTLS
Authentication: password, normal
Port:   25 (instead of 587)

But I assume that the NTLM authentication is the origin of your
trouble. If possible try out SSL/TLS instead of NTLM. I can remember
that at least for old samaba servers (that can't handle NTLM v2) I had
to allow NTLM v1 on the local lan. But that's something you really don't
want to do in company areas.

This old article I found on the microsoft site.
https://support.microsoft.com/en-us/kb/976918

Regards
Carsten

Bug#807453: [Pkg-amule-devel] Bug#807453: amule: BaseClient.cpp(2143): assert "Assert failure" failed in ProcessPublicKeyPacket().

[Sandro Tosi]

On Wed, Dec 9, 2015 at 1:48 AM, Dmitry Smirnov  wrote:
> 
> ASSERT INFO:
> ../../src/BaseClient.cpp(2143): assert "Assert failure" failed in 
> ProcessPublicKeyPacket().
>
> BACKTRACE:
> [1] wxOnAssert(char const*, int, char const*, char const*, char const*)
...

To report a useful backtrace to developers please install amule-dbg,
then run amule in gdb and when it crashed run these gdb command: bt;
bt full; thread apply all bt   and report the output here (or on the
github bug)

Regards,

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

Bug#780940: Business Proposal From Tokyo

[SukiOsamu]

--
December 9, 2015

Konnichiwa! It is with respect to directly
write this proposal letter to you, informing you of a potential business
proposal project that can be established from your country with your 
help,

which will mutually be profitable to us having no risk involved.

If you are agreeable to this business proposal, please indicate your
interest by giving me a direct response email. Feel free to contact me 
via

electronic mail or telephone for further discussion. I look forward to
hearing from you positively on this proposal.

Domo arigato !
Suki

Bug#795879: curlftpfs misbuilds on 64-bit architectures (missing getpass prototype)

[Andreas Beckmann]

Followup-For: Bug #795879

Hi Vincent,

do you plan to fix this bug in jessie, too? The next point release will
probably be in January. A simple backport of the sid package should be
sufficient, proposed patch attached.


Andreas
diff -Nru curlftpfs-0.9.2/debian/changelog curlftpfs-0.9.2/debian/changelog
--- curlftpfs-0.9.2/debian/changelog	2014-05-15 10:23:06.0 +0200
+++ curlftpfs-0.9.2/debian/changelog	2015-12-09 07:14:10.0 +0100
@@ -1,3 +1,17 @@
+curlftpfs (0.9.2-9~deb8u1) jessie; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild for jessie.
+
+ -- Andreas Beckmann   Wed, 09 Dec 2015 07:13:25 +0100
+
+curlftpfs (0.9.2-9) unstable; urgency=medium
+
+  * Avoid unsafe cast for getpass() on 64-bit archs. Closes: #795879.
+  * Bump Standards-Version to 3.9.6.
+
+ -- Vincent Bernat   Mon, 17 Aug 2015 18:51:14 +0200
+
 curlftpfs (0.9.2-8) unstable; urgency=medium
 
   * Fix inconsistent use of _XOPEN_SOURCE flag. Closes: #748143.
diff -Nru curlftpfs-0.9.2/debian/control curlftpfs-0.9.2/debian/control
--- curlftpfs-0.9.2/debian/control	2014-05-10 09:47:33.0 +0200
+++ curlftpfs-0.9.2/debian/control	2015-08-17 18:53:36.0 +0200
@@ -6,7 +6,7 @@
 	   libglib2.0-dev, libcurl4-gnutls-dev, libfuse-dev,
dh-autoreconf
 Build-Conflicts: libcurl4-openssl-dev
-Standards-Version: 3.9.5
+Standards-Version: 3.9.6
 Homepage: http://curlftpfs.sourceforge.net
 Vcs-Svn: svn://anonscm.debian.org/collab-maint/deb-maint/curlftpfs/trunk/
 Vcs-Browser: http://anonscm.debian.org/viewvc/collab-maint/deb-maint/curlftpfs/trunk/
diff -Nru curlftpfs-0.9.2/debian/patches/getpass-prototype.patch curlftpfs-0.9.2/debian/patches/getpass-prototype.patch
--- curlftpfs-0.9.2/debian/patches/getpass-prototype.patch	1970-01-01 01:00:00.0 +0100
+++ curlftpfs-0.9.2/debian/patches/getpass-prototype.patch	2015-08-17 18:50:43.0 +0200
@@ -0,0 +1,20 @@
+Description: add getpass() prototype
+ This function has been deprecated and is not declared with
+ _XOPEN_SOURCE>=600. To avoid fiddling too much with feature flags, we
+ just add its prototype to ensure a correct declaration.
+Forwarded: no (dead upstream)
+Bug: #795879
+
+Index: curlftpfs-0.9.2/ftpfs.c
+===
+--- curlftpfs-0.9.2.orig/ftpfs.c
 curlftpfs-0.9.2/ftpfs.c
+@@ -36,6 +36,8 @@
+ 
+ #define MAX_BUFFER_LEN (300*1024)
+ 
++extern char *getpass(const char *prompt);
++
+ struct ftpfs ftpfs;
+ static char error_buf[CURL_ERROR_SIZE];
+ 
diff -Nru curlftpfs-0.9.2/debian/patches/series curlftpfs-0.9.2/debian/patches/series
--- curlftpfs-0.9.2/debian/patches/series	2014-05-15 10:13:21.0 +0200
+++ curlftpfs-0.9.2/debian/patches/series	2015-08-17 18:47:12.0 +0200
@@ -3,3 +3,4 @@
 nocache-memleak-fix.patch
 curlftpfs__no_verify_hostname.patch
 consistent-feature-flag.patch
+getpass-prototype.patch

Bug#708181: requests password to boot

[Tomar, Tejendra Singh]

Does anyone have any update on this bug ?

I can see the status is still open at https://savannah.gnu.org/bugs/?41801

Thanks and Best Regards
Tejendra

This message is subject to the following terms and conditions: MAIL 
DISCLAIMER

Bug#805684: python-box2d: FTBFS: swig doesn't like some comment styles any more

[Logan Rosen]

Package: python-box2d
Version: 2.0.2+svn20100109.244-1.1
Followup-For: Bug #805684
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch

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

  * debian/patches/fix_comments.patch: Fix comment formatting so that the
package doesn't FTBFS with SWIG 3 (patch courtesy of Jitka Plesnikova).

Thanks for considering the patch.


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

Kernel: Linux 4.2.0-19-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru python-box2d-2.0.2+svn20100109.244/debian/patches/fix_comments.patch python-box2d-2.0.2+svn20100109.244/debian/patches/fix_comments.patch
--- python-box2d-2.0.2+svn20100109.244/debian/patches/fix_comments.patch	1969-12-31 19:00:00.0 -0500
+++ python-box2d-2.0.2+svn20100109.244/debian/patches/fix_comments.patch	2015-12-09 00:50:31.0 -0500
@@ -0,0 +1,27 @@
+Description: fix malformed comments
+ The comments with # style cause an FTBFS with SWIG 3. This patch from Red Hat
+ changes them to the proper format.
+Author: Jitka Plesnikova 
+Origin: vendor, https://bugzilla.redhat.com/attachment.cgi?id=995672
+Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1196718
+Forwarded: not-needed
+Last-Update: 2015-12-09
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/Box2D/Box2D_pickling.i
 b/Box2D/Box2D_pickling.i
+@@ -538,9 +538,11 @@
+ 
+ %}
+ 
+-# These were originally set programmatically, which is perhaps cleaner,
+-# but this will set every class up properly without any unnecessary code
+-# execution
++/*
++ * These were originally set programmatically, which is perhaps cleaner,
++ * but this will set every class up properly without any unnecessary code
++ * execution
++ */
+ 
+ %extend b2World {
+  %pythoncode %{
diff -Nru python-box2d-2.0.2+svn20100109.244/debian/patches/series python-box2d-2.0.2+svn20100109.244/debian/patches/series
--- python-box2d-2.0.2+svn20100109.244/debian/patches/series	2010-07-19 12:25:43.0 -0400
+++ python-box2d-2.0.2+svn20100109.244/debian/patches/series	2015-12-09 00:44:33.0 -0500
@@ -1 +1,2 @@
 debian-changes-2.0.2+svn244-1
+fix_comments.patch

Bug#804584: python-enable: FTBFS: Error: Unknown SWIG preprocessor directive: map

[Logan Rosen]

Package: python-enable
Version: 4.5.1-2
Followup-For: Bug #804584
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu xenial ubuntu-patch

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

  * debian/patches/swig3.diff: Cherrypick from upstream Git to fix FTBFS with
SWIG 3.

Thanks for considering the patch.

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

Kernel: Linux 4.2.0-19-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru python-enable-4.5.1/debian/patches/series python-enable-4.5.1/debian/patches/series
--- python-enable-4.5.1/debian/patches/series	2015-09-27 00:40:01.0 -0400
+++ python-enable-4.5.1/debian/patches/series	2015-12-09 01:06:01.0 -0500
@@ -4,3 +4,4 @@
 gcc5.diff
 setup.diff
 no-opt.patch
+swig3.patch
diff -Nru python-enable-4.5.1/debian/patches/swig3.patch python-enable-4.5.1/debian/patches/swig3.patch
--- python-enable-4.5.1/debian/patches/swig3.patch	1969-12-31 19:00:00.0 -0500
+++ python-enable-4.5.1/debian/patches/swig3.patch	2015-12-09 01:10:22.0 -0500
@@ -0,0 +1,89 @@
+Description: fix FTBFS with SWIG 3
+Author: Jonathan Stickel 
+Origin: upstream
+Forwarded: not-needed
+Applied-Upstream: https://github.com/enthought/enable/commit/f0e399174c5f55eb3a72860c620fdd5193ad57da
+Last-Update: 2015-12-09
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+diff --git a/kiva/agg/src/affine_matrix.i b/kiva/agg/src/affine_matrix.i
+index 2f30e51..7c05a6a 100644
+--- a/kiva/agg/src/affine_matrix.i
 b/kiva/agg/src/affine_matrix.i
+@@ -157,7 +157,7 @@ namespace agg24
+ };
+ };
+ 
+-%pythoncode {
++%pythoncode %{
+ def is_sequence(arg):
+ try:
+ len(arg)
+@@ -184,7 +184,7 @@ class AffineMatrix(_AffineMatrix):
+ """
+ self.multiply(other)
+ return self
+-}
++%}
+ 
+ %extend agg24::trans_affine
+ {
+diff --git a/kiva/agg/src/constants.i b/kiva/agg/src/constants.i
+index b680cae..78f9d0c 100644
+--- a/kiva/agg/src/constants.i
 b/kiva/agg/src/constants.i
+@@ -44,7 +44,7 @@
+ unsigned path_cmd(unsigned c);
+ unsigned path_flags(unsigned c);
+ 
+-%pythoncode {
++%pythoncode %{
+ 
+ #
+ #
+@@ -141,4 +141,4 @@ interp_enum_map = {}
+ for key,value in interp_string_map.items():
+ interp_enum_map[value] = key
+ 
+-}
++%}
+diff --git a/kiva/agg/src/hit_test.i b/kiva/agg/src/hit_test.i
+index 76de0c9..2cfb1cf 100644
+--- a/kiva/agg/src/hit_test.i
 b/kiva/agg/src/hit_test.i
+@@ -22,7 +22,7 @@ namespace kiva
+ }
+ 
+ %pythoncode
+-{
++%{
+ from numpy import shape, transpose, zeros, rank, reshape, int32
+ 
+ def points_in_polygon(pts, poly_pts, use_winding=False):
+@@ -92,4 +92,4 @@ def points_in_polygon(pts, poly_pts, use_winding=False):
+ else:
+ _agg.points_in_polygon(pts, poly_pts, results)
+ return results
+-}
++%}
+diff --git a/kiva/agg/src/rgba.i b/kiva/agg/src/rgba.i
+index f7624b8..183014f 100644
+--- a/kiva/agg/src/rgba.i
 b/kiva/agg/src/rgba.i
+@@ -74,7 +74,7 @@ namespace agg24
+ }
+ 
+ 
+-%pythoncode {
++%pythoncode %{
+ def is_sequence(arg):
+ try:
+ len(arg)
+@@ -90,6 +90,6 @@ class Rgba(_Rgba):
+ if len(args) not in [3,4]:
+ raise ValueError, "array argument must be 1x3 or 1x4"
+ _Rgba.__init__(self,*args)
+-}
++%}
+ 
+ %clear double r, double g, double b, double a;

Bug#791961: saned won't run from systemd (bad status=22 or procnum=1)

[Vladimir K]

I've tested "Standard Input=null/Output=syslog/Error=syslog" unit variant on 
Jessie (without any foreign packages), it works.

Well, sort of (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807427), but 
at least it starts and works the same as init version.

Bug#807467: jessie-pu: package libapache-mod-fastcgi/2.4.7~0910052141-1.1+deb8u1

[Andreas Beckmann]

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

libapache-mod-fastcgi FTBFS in jessie due to missing libtool.
The fix is trivial: switching B-D from libtool to libtool-bin.


Andreas

(Note to self: non-free package, upload amd64+i386 binaries)
diff -u libapache-mod-fastcgi-2.4.7~0910052141/debian/control libapache-mod-fastcgi-2.4.7~0910052141/debian/control
--- libapache-mod-fastcgi-2.4.7~0910052141/debian/control
+++ libapache-mod-fastcgi-2.4.7~0910052141/debian/control
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Tatsuki Sugiura 
 Standards-Version: 3.9.1
-Build-Depends: debhelper (>> 5.0.0), cdbs, dh-apache2, apache2-dev (>= 2.2.4), dpatch (>= 2.0.0), libtool, libapr1-dev, pkg-config
+Build-Depends: debhelper (>> 5.0.0), cdbs, dh-apache2, apache2-dev (>= 2.2.4), dpatch (>= 2.0.0), libtool-bin, libapr1-dev, pkg-config
 Uploaders: Taku YASUI 
 Homepage: http://www.fastcgi.com/
 
diff -u libapache-mod-fastcgi-2.4.7~0910052141/debian/changelog libapache-mod-fastcgi-2.4.7~0910052141/debian/changelog
--- libapache-mod-fastcgi-2.4.7~0910052141/debian/changelog
+++ libapache-mod-fastcgi-2.4.7~0910052141/debian/changelog
@@ -1,3 +1,10 @@
+libapache-mod-fastcgi (2.4.7~0910052141-1.1+deb8u1) jessie; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch B-D from libtool to libtool-bin to fix FTBFS.  (Closes: #793189)
+
+ -- Andreas Beckmann   Wed, 09 Dec 2015 06:55:41 +0100
+
 libapache-mod-fastcgi (2.4.7~0910052141-1.1) unstable; urgency=low
 
   * Non-maintainer upload.

Bug#807427: sane-utils: Can not provide access to hplip scanner over network

[Vladimir K]

Saned output with debug enabled:



saned[6641]: saned (AF-indep+IPv6+systemd) from sane-backends 1.0.24 starting up
saned[6641]: check_host: access by remote host: :::[client_ip]
saned[6641]: init: access granted to user@:::[client_ip]
saned[6641]: [sanei_debug] Setting debug level of dll to 255.
saned[6641]: [dll] sane_init: SANE dll backend version 1.0.13 from 
sane-backends 1.0.24
saned[6641]: [dll] sane_init/read_dlld: attempting to open directory 
`/etc/sane.d/dll.d'
saned[6641]: [dll] sane_init/read_dlld: using config directory 
`/etc/sane.d/dll.d'
saned[6641]: [dll] sane_init/read_dlld: considering 
/etc/sane.d/dll.d/libsane-extras
saned[6641]: [dll] sane_init/read_config: reading dll.d/libsane-extras
saned[6641]: [dll] add_backend: adding backend `ls5000'
saned[6641]: [dll] sane_init/read_dlld: considering /etc/sane.d/dll.d/hplip
saned[6641]: [dll] sane_init/read_config: reading dll.d/hplip
saned[6641]: [dll] add_backend: adding backend `hpaio'
saned[6641]: [dll] sane_init/read_dlld: done.
saned[6641]: [dll] sane_init/read_config: reading dll.conf
saned[6641]: [dll] add_backend: adding backend `net'
saned[6641]: [dll] add_backend: adding backend `abaton'
saned[6641]: [dll] add_backend: adding backend `agfafocus'
saned[6641]: [dll] add_backend: adding backend `apple'
saned[6641]: [dll] add_backend: adding backend `avision'
saned[6641]: [dll] add_backend: adding backend `artec'
saned[6641]: [dll] add_backend: adding backend `artec_eplus48u'
saned[6641]: [dll] add_backend: adding backend `as6e'
saned[6641]: [dll] add_backend: adding backend `bh'
saned[6641]: [dll] add_backend: adding backend `canon'
saned[6641]: [dll] add_backend: adding backend `canon630u'
saned[6641]: [dll] add_backend: adding backend `canon_dr'
saned[6641]: [dll] add_backend: adding backend `cardscan'
saned[6641]: [dll] add_backend: adding backend `coolscan'
saned[6641]: [dll] add_backend: adding backend `coolscan3'
saned[6641]: [dll] add_backend: adding backend `dell1600n_net'
saned[6641]: [dll] add_backend: adding backend `dmc'
saned[6641]: [dll] add_backend: adding backend `epjitsu'
saned[6641]: [dll] add_backend: adding backend `epson2'
saned[6641]: [dll] add_backend: adding backend `fujitsu'
saned[6641]: [dll] add_backend: adding backend `genesys'
saned[6641]: [dll] add_backend: adding backend `gt68xx'
saned[6641]: [dll] add_backend: adding backend `hp'
saned[6641]: [dll] add_backend: adding backend `hp3900'
saned[6641]: [dll] add_backend: adding backend `hpsj5s'
saned[6641]: [dll] add_backend: adding backend `hp3500'
saned[6641]: [dll] add_backend: adding backend `hp4200'
saned[6641]: [dll] add_backend: adding backend `hp5400'
saned[6641]: [dll] add_backend: adding backend `hp5590'
saned[6641]: [dll] add_backend: adding backend `hpljm1005'
saned[6641]: [dll] add_backend: adding backend `hs2p'
saned[6641]: [dll] add_backend: adding backend `ibm'
saned[6641]: [dll] add_backend: adding backend `kodak'
saned[6641]: [dll] add_backend: adding backend `kodakaio'
saned[6641]: [dll] add_backend: adding backend `kvs1025'
saned[6641]: [dll] add_backend: adding backend `kvs20xx'
saned[6641]: [dll] add_backend: adding backend `leo'
saned[6641]: [dll] add_backend: adding backend `lexmark'
saned[6641]: [dll] add_backend: adding backend `ma1509'
saned[6641]: [dll] add_backend: adding backend `magicolor'
saned[6641]: [dll] add_backend: adding backend `matsushita'
saned[6641]: [dll] add_backend: adding backend `microtek'
saned[6641]: [dll] add_backend: adding backend `microtek2'
saned[6641]: [dll] add_backend: adding backend `mustek'
saned[6641]: [dll] add_backend: adding backend `mustek_usb'
saned[6641]: [dll] add_backend: adding backend `mustek_usb2'
saned[6641]: [dll] add_backend: adding backend `nec'
saned[6641]: [dll] add_backend: adding backend `niash'
saned[6641]: [dll] add_backend: adding backend `pie'
saned[6641]: [dll] add_backend: adding backend `pixma'
saned[6641]: [dll] add_backend: adding backend `plustek'
saned[6641]: [dll] add_backend: adding backend `qcam'
saned[6641]: [dll] add_backend: adding backend `ricoh'
saned[6641]: [dll] add_backend: adding backend `rts8891'
saned[6641]: [dll] add_backend: adding backend `s9036'
saned[6641]: [dll] add_backend: adding backend `sceptre'
saned[6641]: [dll] add_backend: adding backend `sharp'
saned[6641]: [dll] add_backend: adding backend `sm3600'
saned[6641]: [dll] add_backend: adding backend `sm3840'
saned[6641]: [dll] add_backend: adding backend `snapscan'
saned[6641]: [dll] add_backend: adding backend `sp15c'
saned[6641]: [dll] add_backend: adding backend `tamarack'
saned[6641]: [dll] add_backend: adding backend `teco1'
saned[6641]: [dll] add_backend: adding backend `teco2'
saned[6641]: [dll] add_backend: adding backend `teco3'
saned[6641]: [dll] add_backend: adding backend `u12'
saned[6641]: [dll] add_backend: adding backend `umax'
saned[6641]: [dll] add_backend: adding backend `umax1220u'
saned[6641]: [dll] add_backend: adding backend `v4l'
saned[6641]: [dll] add_backend: ad

Bug#798218: pbseqlib_0~20151014+gitbe5d1bf-1_amd64.changes is NEW

[Afif Elghraoui]

Hi, ftp-masters,
I was wondering if it's possible to have some expedited processing for
this package, pbseqlib. The sources for this are already included in the
current blasr package, but I packaged it separately here since it turns
out this specialized library is used by one other package (which is in
turn blocking still another package). I'm waiting for this one to be
accepted before I can move on with that work.

Many thanks and regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

على الأربعاء 18 تشرين الثاني 2015 ‫22:58، كتب Afif Elghraoui:
> 
> The package has been uploaded:
> 
>  رسالة ممرّرة 
> الموضوع: pbseqlib_0~20151014+gitbe5d1bf-1_amd64.changes is NEW
> التاريخ: Tue, 17 Nov 2015 07:48:58 +
> مِن: Debian FTP Masters 
> إلى: Debian Med Packaging Team
> , Afif Elghraoui
> , ti...@debian.org
> 
> binary:libblasr is NEW.
> binary:libblasr-dev is NEW.
> binary:libpbdata is NEW.
> binary:libpbdata-dev is NEW.
> binary:libpbihdf is NEW.
> binary:libpbihdf-dev is NEW.
> binary:libpbseq is NEW.
> binary:libpbseq-dev is NEW.
> source:pbseqlib is NEW.
> 
> Your package has been put into the NEW queue, which requires manual action
> from the ftpteam to process. The upload was otherwise valid (it had a good
> OpenPGP signature and file hashes are valid), so please be patient.
> 
> Packages are routinely processed through to the archive, and do feel
> free to browse the NEW queue[1].
> 
> If there is an issue with the upload, you will receive an email from a
> member of the ftpteam.
> 
> If you have any questions, you may reply to this email.
> 
> [1]: https://ftp-master.debian.org/new.html
> 
> 
> 

Bug#807040: general: System hangs and then restarts (kernel panic)

[Adam Borowski]

On Tue, Dec 08, 2015 at 07:14:26PM -0800, Nigra Truo wrote:
> I tried Kernel 4.2 from backports, no dice, thing still crashes.

Not surprising, the big overhaul was in 4.3.

I've just switched to nouveau on 4.3, no crash for me yet; it's been only
two hours of light activity though so it's not conclusive.  And my crash
looks different from yours save for the symptoms...

> How do I get the new version of nouveau?  Backports does not seem to offer
> any newer version.

For 4.3 you need to install it from experimental, as it'd be some time until
it reaches backports.  It's safe to add experimental to your apt sources as
packages are not installed automatically (except exp->exp upgrades).  It
appears that the experimental kernel has no dependencies that are
unsatisfiable in stable, so it can be installed by just "apt-get install
linux-image-4.3.0-trunk-amd64".

> I could compile nouveau from scratch, but it seems to be very complicated
> and hairy.

As there's a ready Debian kernel in experimental, there's no need.

> I might also go away from nouveau and use the proprietary drivers again. Do
> you know a manual how to easily install them on Debian Jessie? I remember
> the process very painful from before, not knowing which version to take and
> the machine staying without X for a while, while X failed to start till I
> could fix it.

You need to have kernel headers for your kernel version installed.

apt-get install nvidia-driver

The third step is writing a /etc/X11/xorg.conf that contains at least:
Section "Device"
Identifier "anything"
Driver "nvidia"
EndSection

-- 
A tit a day keeps the vet away.

Bug#783393: initramfs-tools: Missing crypto-components in initramfs when explicitly requested

[Guilhem Moulin]

Exporting the variable initramfs.conf will do the trick.  That's
somewhat dirty though, we should probably source that file in the hook
file instead.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#807466: virtualbox: FTBFS with GCC 5.3

[Andreas Beckmann]

Source: virtualbox
Version: 5.0.10-dfsg-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

vbox FTBFS in sid which recently got an upload of GCC 5.3:

[...]
 debian/rules build
dh build --with python2,dkms,systemd
   dh_testdir
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/build/virtualbox-5.0.10-dfsg'
Building for Debian/sid
mkdir -p out
../configure \
--ose \
--odir=/build/virtualbox-5.0.10-dfsg/out \
--with-linux="/usr" \
--disable-kmods \
--enable-webservice \
--enable-vde \
--enable-vnc
Checking for environment: Determined build machine: linux.x86, target machine: 
linux.x86, OK.
Checking for kBuild: found, OK.
Checking for gcc: 
  ** gcc version 5.3 found, expected gcc 3.x with x>1 or gcc 4.x with 0

Bug#774647: cryptsetup on initramfs does not support key files (resume swap on LVM)

[Guilhem Moulin]

Control: merge 776409 -1

Hi,

Yeah, it's because in the initramfs (before pivot_root) the key files
are relative to the real rootfs's mountpoint (/root).  Sergio Gelato has
found another workaround [0] using a dummy keyscript.

I'll see how to support this use case natively.  As documented in
crypttab(5), “the initramfs hook processes the root device, any resume
devices and any devices with the initramfs option set”, so indeed we
could safely include a keyfile if stored on an encrypted device that's
processed earlier.  AFAICT it's mostly a matter of getting the file's
mountpoint and finding out whether the device was already included in
conf.d/cryptroot.

Cheers,
-- 
Guilhem.

[0] https://bugs.debian.org/776409#74


signature.asc
Description: PGP signature

Bug#807456: mention how to abort, right there in the message

[積丹尼 Dan Jacobson]

And alas
# systemctl  set-property dictd.service TimeoutStopUSec=89sec
Unknown assignment TimeoutStopUSec=89sec.
one cannot change them except by editing each of e.g., /etc/init.d/dictd
individually.

Also Unknown assignment should be Readonly value.

Bug#807465: ITP: ruby-babosa -- library for creating slugs

[Balasankar C]

Package: wnpp
Owner: Balasankar C 
Severity: wishlist

* Package name : ruby-babosa
  Version : 1.0.2
  Upstream Author  : Norman Clarke 
* URL  : http://github.com/norman/babosa
* License: Expat
  Programming Lang   : Ruby
  Description  : library for creating slugs


-- 
Regards
Balasankar C
http://balasankarc.in

Bug#786578: cryptsetup: crypt asks passphrase instead of using keyfile

[Guilhem Moulin]

Hi there,

Patch enclosed, with the following documentation:

  Among the key files used in the crypttab(5), those matching the
  environment variable $KEYFILE_PATTERN (interpreted as a shell pattern)
  will be included in the initramfs image.  For instance if /etc/crypttab
  contains two key files /etc/keys/{root,swap}.key, you can add the
  following to initramfs.conf to add them to the initrd.

KEYFILE_PATTERN="/etc/keys/*.key"
export KEYFILE_PATTERN

I'm not super happy about the name of the variable, but I couldn't find
anything better :-P  Suggestions welcome.

Cheers,
-- 
Guilhem.
From ad449c5b2d84f3d093a0e3ba2667fc3e282aa8f8 Mon Sep 17 00:00:00 2001
From: Guilhem Moulin 
Date: Wed, 9 Dec 2015 04:53:41 +0100
Subject: [PATCH] Add support for storing keyfiles directly in the initrd.

---
 debian/README.initramfs | 18 ++
 debian/initramfs/cryptroot-hook | 22 ++
 2 files changed, 36 insertions(+), 4 deletions(-)

diff --git a/debian/README.initramfs b/debian/README.initramfs
index d7088b7..41f1f67 100644
--- a/debian/README.initramfs
+++ b/debian/README.initramfs
@@ -222,5 +222,23 @@ limitation:
 
 [1] https://bugs.debian.org/671037
 
+12. Storing keyfiles directly in the initrd
+---
+Normally devices using a keyfile are ignored (with a loud warning), and
+the key file itself is not included in the initrd, because the initramfs
+image typically lives on an unencrypted /boot partition.  However in
+some cases it is desirable to include the key file in the initrd; for
+instance recent versions of GRUB support booting from encrypted block
+devices, allowing an encrypted /boot partition.
+
+Among the key files used in the crypttab(5), those matching the
+environment variable $KEYFILE_PATTERN (interpreted as a shell pattern)
+will be included in the initramfs image.  For instance if /etc/crypttab
+contains two key files /etc/keys/{root,swap}.key, you can add the
+following to initramfs.conf to add them to the initrd.
+
+  KEYFILE_PATTERN="/etc/keys/*.key"
+  export KEYFILE_PATTERN
+
  -- David Härdeman 
  -- Jonas Meurer   Thu, 01 Nov 2012 13:44:31 +0100
diff --git a/debian/initramfs/cryptroot-hook b/debian/initramfs/cryptroot-hook
index 66a7175..4042917 100644
--- a/debian/initramfs/cryptroot-hook
+++ b/debian/initramfs/cryptroot-hook
@@ -232,10 +232,11 @@ get_lvm_deps() {
 }
 
 get_device_opts() {
-	local target source link extraopts rootopts opt
+	local target source link extraopts rootopts opt key
 	target="$1"
 	extraopts="$2"
 	KEYSCRIPT=""
+	KEYFILE=""
 	CRYPTHEADER=""
 	OPTIONS=""
 
@@ -279,7 +280,7 @@ get_device_opts() {
 	fi
 
 	# We have all the basic options, let's go trough them
-	OPTIONS="target=$target,source=$source,key=$key"
+	OPTIONS="target=$target,source=$source"
 	local IFS=", "
 	unset HASH_FOUND
 	unset LUKS_FOUND
@@ -359,9 +360,16 @@ get_device_opts() {
 
 	# If keyscript is set, the "key" is just an argument to the script
 	if [ "$key" != "none" ] && [ -z "$KEYSCRIPT" ]; then
-		echo "cryptsetup: WARNING: target $target uses a key file, skipped" >&2
-		return 1
+		case "$key" in
+			$KEYFILE_PATTERN)
+KEYFILE="$key"
+OPTIONS="$OPTIONS,keyscript=cat"
+key="/cryptroot-keyfiles/${target}.key";;
+			*) echo "cryptsetup: WARNING: target $target uses a key file, skipped" >&2
+			   return 1
+		esac
 	fi
+	OPTIONS="$OPTIONS,key=$key"
 }
 
 get_device_modules() {
@@ -517,6 +525,12 @@ add_device() {
 echo "cryptsetup: WARNING: failed to find keyscript $KEYSCRIPT" >&2
 continue
 			fi
+		elif [ -n "$KEYFILE" ]; then
+			case "$KEYFILE" in
+$KEYFILE_PATTERN)
+	mkdir -pm0700 "$DESTDIR/cryptroot-keyfiles"
+	cp --preserve=all "$KEYFILE" "$DESTDIR/cryptroot-keyfiles/${node}.key";;
+			esac
 		fi
 
 		# If we have a LUKS header, make sure it is included
-- 
2.6.2



signature.asc
Description: PGP signature

Bug#807464: systemctl man page needs full examples for multiple property assignment

[積丹尼 Dan Jacobson]

Package: systemd
Version: 228-2
Severity: wishlist
File: /usr/share/man/man1/systemctl.1.gz

We read:
   --runtime is passed, in which case the settings only apply until
   the next reboot. The syntax of the property assignment follows
   closely the syntax of assignments in unit files.

   Example: systemctl set-property foobar.service CPUShares=777

   Note that this command allows changing multiple properties at the
   same time, which is preferable over setting them individually. Like
   unit file configuration settings, assigning the empty list to list
   parameters will reset the list.

OK but you then need to add a further example:

   systemctl set-property foobar.service nurdbar.servive CPUShares=777

Or

   systemctl set-property foobar.service CPUShares=777 BlaBoo=888

Or

  systemctl set-property foobar.service nurdbar.servive CPUShares=777 BlaBoo=888

to clarify.

Also give an example of assigning the empty list.

Since the syntax "follows closely" but not exactly, hence full examples
are needed.

Bug#807463: RFS: pnmixer/0.6.1-1 [ITP] -- Simple mixer application for system tray

[Arnaud Rébillout]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "pnmixer".

 Package name: pnmixer
 Version : 0.6.1-1
 Upstream Author : Nick Lanham, Julian Ospald, Arnaud Rébillout
 URL : https://github.com/nicklan/pnmixer
 License : GPL-3
 Section : sound

This is my first package.

I built it carefully using `dh_make`, checked and fixed errors with
`lintian`. It took me almost two days, given the huge amount of
documentation out there :)

PNMixer is a simple mixer application for the system tray, for those
who use ALSA for sound management. It may be people who like to keep
their system simple and lightweight, or people who do MAO, therefore
using Jackd when working on their music, and simple ALSA when they're
not. I'm part of both use cases.

PNMixer integrates nicely into desktop environments that don't have
a panel that supports applets and therefore can't run a mixer applet.
In particular it's been used quite a lot with fbpanel and tint2, but
should run fine in any system tray.

PNMixer comes with plenty of options, which make it quite a complete
system tray mixer: hotkeys support, notifications, plenty of config...
This is described in details in the README.

How does it compare with other system tray ALSA mixers in Debian ?
- qasmixer is C++/Qt4, no translation
- volumeicon-alsa is C/GTk2, no translation
- volti is Python/GTk2, translated in 5 languages

PNMixer is C/GTk3, translated in 4 languages.

It has been around for almost 5 years now, and is actively maintained.
It is packaged in several distributions:

- ArchLinux: https://aur.archlinux.org/packages/pnmixer/
- Gentoo: https://packages.gentoo.org/packages/media-sound/pnmixer
- Fedora: https://apps.fedoraproject.org/packages/pnmixer

It was also the default sound mixer in Crunchbang, a Debian-derived
distribution that is known as BunsenLabs now. There's also an unofficial
package for Ubuntu.

I'm one of the maintainers of PNMixer, so yes, I'm advertising a little
bit here :)

However, before being a maintainer, I was a PNMixer user, because it was
definitely the best system tray ALSA mixer around. I sincerely believe
that it's a valuable piece of software, and that Debian users can
benefit from it.

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

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

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

dget -x 
http://mentors.debian.net/debian/pool/main/p/pnmixer/pnmixer_0.6.1-1.dsc

Best regards,

Arnaud Rébillout



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

Kernel: Linux 4.2.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#807456: mention how to abort, right there in the message

[積丹尼 Dan Jacobson]

Gasp, I finally found the culprits,

systemctl show \* -p TimeoutStopUSec -p Id|perl -e '
use strict;
use warnings FATAL => q(all);
my %h;
while (<>) {
chomp;
if ( !length ) {
printf "%s|%s\n", @h{ q(TimeoutStopUSec), q(Id) };
undef %h;
}
elsif (/(.*)=(.*)/) { $h{$1} = $2; }
else{ die; }
}
'|sort -n

...
1min 30s|systemd-user-sessions.service
1min 30s|systemd-vconsole-setup.service
1min 30s|user@1000.service
5min|dictd.service
5min|exim4.service
5min|nodm.service
5min|ntp.service
10min|mysql.service
30s|systemd-machine-id-commit.service
30s|systemd-random-seed.service
30s|systemd-rfkill.service

So much work to dig them out.

Bug#807391: libcommons-openpgp-java: FTBFS: BouncyCastleOpenPgpStreamingSignatureVerifier.java:92: error: cannot find symbol [..] sig.initVerify( key, "BC" );

[tony mancill]

On 12/08/2015 04:14 AM, Chris Lamb wrote:
> Source: libcommons-openpgp-java
> Version: 0+svn533492-5
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

I can't find any reverse dependencies for this package.  Any objections
to requesting its removal?




signature.asc
Description: OpenPGP digital signature

Bug#807239: lftp: can no longer connect with sftp (no matching host key type found)

[Russ Allbery]

Vincent Lefevre  writes:
> On 2015-12-06 16:48:35 +0100, Vincent Lefevre wrote:

>> Package: lftp
>> Version: 4.6.3a-1+b1
>> Severity: grave
>> Justification: renders package unusable
>> 
>> After a system upgrade, lftp can no longer connect with sftp.
>> When I type "dir", I get the error:
>> 
>> `ls' at 0 [Unable to negotiate with 192.168.1.4: no matching host key type 
>> found. Their offer: ssh-dss]
>> 
>> 4 days ago, I had no problems.

> The problem actually comes from openssh-client (on which lftp has
> no dependencies!).

> First, the error is surprising because I was just using an IP address,
> for which host key checking doesn't make much sense. But even if I set
> both CheckHostIP and StrictHostKeyChecking to "no", I get the error!

I think Colin is still working on making sure this change is visible
enough to everyone it affects, but see the changelog in openssh-client:

- Support for ssh-dss, ssh-dss-cert-* host and user keys is disabled by
  default at run-time.  These may be re-enabled using the instructions
  at http://www.openssh.com/legacy.html

It sounds like the remote host to which you're trying to connect only
offers ssh-dss keys, which are no longer supported by default (following
upstream) because they're not very secure.

This is unrelated to host key checking or IP checking.  It's about the
type of underlying crypto being used to secure the connection.

-- 
Russ Allbery (r...@debian.org)   

Bug#807462: grammar error on systemctl man page

[積丹尼 Dan Jacobson]

Package: systemd
Version: 228-2
Severity: minor


   are looking for computer-parsable output, use show instead. By
   default, this function only shows 10 lines of output and ellipsizes
   lines to fit in the terminal window. This can be changes with

s/ changes / changed /

   --lines and --full, see above. In addition, journalctl --unit=NAME
   or journalctl --user-unit=NAME use a similar filter for messages

Bug#807459: gedit: perl syntax highliting fails on s%a%b%

[=]

Package: gedit
Version: 3.14.0-3
Severity: minor

Dear Maintainer,

perl syntax hightling fails if it hits an expression of the form s%a%b%

(a regex-substitute command with % as the delimiter)

a work-around is to add a comment like #%# after the failing line.



-- Package-specific info:
Active plugins:
  - 'time'
  -  'modelines'
  -  'docinfo'
  -  'codecomment'
  -  'spell'

No plugin installed in $HOME.

Module versions:
  - glib  2.42.1
  - gtk+  
  - gtksourceview 
  - pygobject 
  - enchant   
  - iso-codes 3.57


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

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

Versions of packages gedit depends on:
ii  gedit-common   3.14.0-3
ii  gir1.2-peas-1.01.12.1-2
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  gsettings-desktop-schemas  3.14.1-1
ii  iso-codes  3.57-1
ii  libatk1.0-02.14.0-1
ii  libc6  2.19-19
ii  libcairo-gobject2  1.14.0-2.1
ii  libcairo2  1.14.0-2.1
ii  libenchant1c2a 1.6.0-10.1
ii  libgdk-pixbuf2.0-0 2.31.1-2+deb8u3
ii  libgirepository-1.0-1  1.42.0-2.2
ii  libglib2.0-0   2.42.1-1
ii  libgtk-3-0 3.14.5-1+deb8u1
ii  libgtksourceview-3.0-1 3.14.1-1
ii  libpango-1.0-0 1.36.8-3
ii  libpangocairo-1.0-01.36.8-3
ii  libpeas-1.0-0  1.12.1-2
ii  libx11-6   2:1.6.3-1
ii  libxml22.9.1+dfsg1-5
ii  python3-gi 3.14.0-1
ii  python3-gi-cairo   3.14.0-1
pn  python3:any

Versions of packages gedit recommends:
ii  yelp3.14.1-1
ii  zenity  3.14.0-1

Versions of packages gedit suggests:
ii  gedit-plugins  3.14.0-2

-- no debconf information

Bug#807461: lintian: check years in debian/copyright are not in the future

[Paul Wise]

Package: lintian
Severity: wishlist

I found a git commit in one of the d-i packages that fixed the
copyright year, changing it from 2103 to 2013. This wasn't in
debian/copyright but it would be great if lintian could catch such
typos in debian/copyright.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#807460: systemctl show ... -p ... -p ...: no way to order output

[積丹尼 Dan Jacobson]

Package: systemd
Version: 228-2
Severity: wishlist
File: /usr/share/man/man1/systemctl.1.gz

No way to order output. No matter which of
systemctl show \* -p Id -p TimeoutStopUSec
systemctl show \*  -p TimeoutStopUSec -p Id
systemctl show \*  -p TimeoutStopUSec -p Names
systemctl show \*  -p Names -p TimeoutStopUSec
we use, TimeoutStopUSec always comes out first.

Bug#795831: initramfs-tools: ensure error output from switch_root/run-init are on the console

[Ben Hutchings]

On Mon, 17 Aug 2015 10:44:28 +0100 Andy Whitcroft  wrote:
> Package: initramfs-tools
> Version: 0.120
> Severity: normal
> 
> When switching into the real root partition using switch_root/run-init
> we do not specifically direct the error output, as a result it may not
> end up visible to the user.  Send it with the primary output to the
> console.

Applied, thanks.

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett

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

Bug#793786: initramfs-tools: fix the broken netconsole feature in initramfs-tools

[Ben Hutchings]

On Sun, 2 Aug 2015 19:08:30 +0900 Roger Shimizu  wrote:
> Dear Ian,
> 
> Thanks for your feedback!
> 
> After reading your comment, I reviewed the whole procedure of loading
> netconsole module during initramfs-tools booting, previously and after
> my patch, I start to consider that original "modprobe netconsole
> netconsole=$param" line in init file is merely a dirty hack. The real
> fix is to load the netconsole module with param inside load_modules()
> routine.
> 
> So I created v3 patchset, which looks more clean to me.
> Of course patchset v2 & v3 both works well as I tested. So I let the
> package maintainer to choose which is better to merge.
[...]

An initramfs built with MODULES=most (default) always includes
netconsole.ko (assuming it was enabled in the kernel configuration).
So
the netconsole parameter needs to work even if netconsole doesn't
appear in /conf/modules, and your v3 breaks that.  So I applied your
v2.  Thanks.

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett

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

Bug#807458: :807: warning [p 10, 2.8i, div `3tbd1,1', 1.2i]: can't break line

[積丹尼 Dan Jacobson]

Package: systemd
Version: 228-2
Severity: wishlist
File: /usr/share/man/man1/systemctl.1.gz

$ man systemctl # seen with emacs' M-x man:

...ConsistsOf=, Wants=, BindsTo= dependencies. If no unit is
   specified, default.target is implied.

   By default, only target units are recursively expanded. When --all
   is passed, all oth:807: warning [p 10, 2.8i, div 
`3tbd1,1', 0.8i]: can't break line
:807: warning [p 10, 2.8i, div `3tbd1,1', 1.2i]: can't break 
line
:817: warning [p 10, 2.8i, div `3tbd3,1', 1.0i]: can't break 
line
:827: warning [p 10, 2.8i, div `3tbd5,1', 1.0i]: can't break 
line
er units are recursively expanded as well.

   Options --reverse, --after, --before may be used to change what

Bug#807457: lsinitramfs(8): multiple-segmented initramfs supported

[Ben Hutchings]

On Sat, 27 Jun 2015 08:53:59 +0900 Osamu Aoki  wrote:
[...]
> In addition to this, I wonder why not offer utility to extract the
> regular compressed initrams by using the same code with trivial changes.
> It is pain to manually extract the new initrd image content.
> 
> I attach patch here one as example against the git master.
[...]

Rather than duplicating code, please combine this with lsinitramfs
(checking $0 to determine which command was invoked) or move the common
code into a shell library.

Most decompression commands are named after the compressor plus 'un' so
I prefer the name 'unmkinitramfs'.

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett

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

Bug#790095: lsinitramfs(8): multiple-segmented initramfs supported

[Ben Hutchings]

Control: tag -1 pending

On Sat, 27 Jun 2015 08:53:59 +0900 Osamu Aoki  wrote:
> Package: initramfs-tools
> Version: 0.120
> Severity: normal
> Tags: patch
> 
> From initramfs-tools 0.118 (Oct. 2014):
>   * [d5f4cd6] lsinitramfs: Parse and list files that include early microcode.
> Thanks to Brett Parker and Olivier Berger. (Closes: #717805)
> 
> So the manpage description as the following is incorrect.
> | BUGS
> |lsinitramfs  cannot deal with multiple-segmented initramfs images, 
> such
> |as those created when an early  (uncompressed)  initramfs  with  
> system
> |firmware is prepended to the regular compressed initrams, or when 
> over$B!>(B
> |lay data is appended to the initramfs.
> 
> So please knock off these lines.
[...]

The last bit is still true - we only support a single uncompressed
segment followed by a single compressed segment.  I don't know how to
support multiple compressed segments, as in general we can't find out
how long each segment is.  (But I think dracut does it, so maybe we
could copy from them.)

So I've applied this change:

--- a/lsinitramfs.8
+++ b/lsinitramfs.8
@@ -38,10 +38,9 @@ List content of two initramfs files in verbose mode:
 
 .SH BUGS
 .BR lsinitramfs
-cannot deal with multiple-segmented initramfs images, such as those created
-when an early (uncompressed) initramfs with system firmware is prepended to
-the regular compressed initrams, or when overlay data is appended to the
-initramfs.
+cannot deal with multiple-segmented initramfs images, except where an
+early (uncompressed) initramfs with system firmware is prepended to
+the regular compressed initramfs.
 
 .SH AUTHOR
 The initramfs-tools are written by Maximilian Attems 
--- END ---

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett

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

Bug#807040: general: System hangs and then restarts (kernel panic)

[Nigra Truo]

I tried Kernel 4.2 from backports, no dice, thing still crashes. How do I
get the new version of nouveau? Backports does not seem to offer any newer
version.
I could compile nouveau from scratch, but it seems to be very complicated
and hairy.
I might also go away from nouveau and use the proprietary drivers again. Do
you know a manual how to easily install them on Debian Jessie? I remember
the process very painful from before, not knowing which version to take and
the machine staying without X for a while, while X failed to start till I
could fix it.

On Tue, Dec 8, 2015 at 12:35 PM, Adam Borowski  wrote:

> On Tue, Dec 08, 2015 at 08:11:56AM -0800, Nigra Truo wrote:
> > I found some logs that show that nouveau is logging some insane amount of
> > stuff, seems to be errors nonstop, in one instance it is more than a
> > thousand lines of the very same error.
> > I attached the logs.
>
> I'm afraid I'm not someone who can help you, I'm merely an user who got the
> same problem.  It does seem like a kernel driver rather than X driver
> problem too.  I guess, it'd be best to send the report/logs to nouveau guys
> upstream.
>
> > One thing I wonder is how to deactivate nouveau for now, I can't work
> with
> > my computer crashing every 5 minutes. Since reporting this bug, the
> machine
> > crashed about 20 times already, I'm not kidding, this is not Debian
> Stable,
> > far from it and it must stop, I need a workaround for this. Is there a
> way
> > to disable hardware accelleration?
>
> Setting the X driver to vesa maybe?  My solution is to use the proprietary
> driver, it works fine for me.
>
> I couldn't reboot with nouveau on new kernel before then got distracted,
> I'll see if it fixes things.  But, my logs and your logs look totally
> different so there's a big chance it's a different bug with same symptoms.
>
> > A good question would be how to get a newer kernel on Debian Stable and
> get
> > a newer version of nouveau too.
>
> It will hit backports in a while, currently both jessie-backports and
> unstable got 4.2.  The nouveau overhaul is in 4.3, which currently is only
> in experimental.  As jessie is pretty recent, I believe the experimental
> kernel can be installed without much trouble.
>
> Or, you can compile your own kernel, please say so if you need help.
>
>
> --
> A tit a day keeps the vet away.
>



-- 
*Por sperto kaj lerno ne sufiĉas eterno.*

Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'

[Milan Kupcevic]

On 12/08/2015 06:30 PM, John Paul Adrian Glaubitz wrote:
> On Fri, Apr 10, 2015 at 05:39:50PM -0400, Milan Kupcevic wrote:
>  > The module landed in sid D-I. It gets loaded automatically as it is not
>> blacklisted in D-I. I've been able to boot and run the installer on an
>> XServe G4 DP, a G4 Mac Mini, and a Pegasos II. All three machines have
>> radeon cards.
>  
> This reddit user got different results which rather support my stance:
> 
>> https://www.reddit.com/r/debian/3vyn0p/
> 


Hi John,

The module in question gets loaded and is used in D-I only. Pay
attention to the case you are pointing at: the graphics does not work on
boot/reboot into an installed system. At this point this module plays no
role because it is blacklisted in the main system. This user is having
some other issues unrelated to this module.

M





signature.asc
Description: OpenPGP digital signature

Bug#807456: #807456 to "A stop job is running" message should mention how to abort and what is making the message

[積丹尼 Dan Jacobson]

Actually it seems a "Failed to fork: Cannot allocate memory" triggered it.

Stopped LSB: No Display Manager.
Stopping ACPI event daemon...
Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Deactivating swap /dev/sda12...
Stopped target Sound Card.
Stopping Session c1 of user jidanni.
Starting Store Sound Card State...
Stopping User Manager for UID 1000...
Stopped target Graphical Interface.
Stopped target Multi-User System.
Stopping Deferred execution scheduler...
Stopping D-Bus System Message Bus...
Stopped target Login Prompts.
acpid: exiting
Stopping Getty on tty1...
dictd.service: Failed to fork: Cannot allocate memory
Stopping LSB: Start and stop dictionary server daemon...
exim4.service: Failed to fork: Cannot allocate memory
Stopping LSB: exim Mail Transport Agent...
Stopping Regular background program processing daemon...
Stopping Self Monitoring and Reporting Technology (SMART) Daemon...
Stopping System Logging Service...
Stopped target Timers.
Stopped Daily Cleanup of Temporary Directories.
Stopped Regular background program processing daemon.
Stopped target Default.
Stopped target Basic System.
Stopped target Sockets.
Stopped target Paths.
Reached target Shutdown.
systemd-exit.service: Failed to fork: Cannot allocate memory
Assertion 'pid >= 1' failed at ../src/core/unit.c:2026, function 
unit_watch_pid(). Aborting.
rsyslogd: [origin software="rsyslogd" swVersion="8.14.0" x-pid="465" 
x-info="http://www.rsyslog.com";] exiting on signal 15.

But still, in the message you need to say who is making the message and
how to leave now.

Bug#807456: mention how to abort, right there in the message

[積丹尼 Dan Jacobson]

I see, each one has a potentially different time:
# systemctl show dictd -p TimeoutStopUSec
TimeoutStopUSec=5min

However you should still have the "A stop job is running" message:
1) prefix itself with the name of the package (systemd) making the
message.
2) mention how to abort (four fingers placed on what keys) in order to
not scramble ones disks, in case one wants to go home.

All commands should mention how to safely abort.
No, the user might need to pull the plug now and take the disks with
him.
There might be a fire and he needs to leave now.

Forcing him to pull the power cord will guarantee data loss and thus
would make this a grave bug.

Bug#807456: "A stop job is running" now taking 15 instead of 1.5 minutes

[積丹尼 Dan Jacobson]

Package: systemd
Version: 228-2

Starting today "A stop job is running" now take 10 times as many minutes
than before. 10 or 15 minutes instead of 1.5 minutes. Yes the counter
says ../15 minutes.

Maybe it has something to do with linux-image-4.2.0-1-686-pae, which is
the only relevant package I installed recently.

But nobody knows, as the "A stop job is running" message doesn't give a
clue to what package makes the message.

Meaning one cannot turn off the power and leave the office until they
are through.

Or one can turn off the power and leave the office only to find ones
disks scrambled.

Nor is there any message on the screen about how to possibly abort the
thing. Even for some tiny dictionary server that hasn't stopped yet.

No, nothing changed in /etc/systemd/system.conf so perhaps it is
something in linux-image-4.2.0-1-686-pae version 4.2.6-3 interacting oddly.

Bug#782641: initramfs-tools: nfs booting requires /usr to be present on the nfs root filesystem

[Ben Hutchings]

Control: tag -1 pending

On Mon, 9 Nov 2015 08:58:49 +0100 Salvatore Bonaccorso  
wrote:
[...]
> After thinking a bit more on it, maybe doing the file check to test if
> the rootfs mount was successful could be better replaced by a return
> value check. The init is validated aftwards.
> 
> Attached is proposed patch for #782641 . Does it looks good to go
> ahead?

Applied, thanks.  (I'm assuming you've tested it.)

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett

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

Bug#807455: golang-src: includes race detector runtime files not built from source in the source package

[Michael Hudson-Doyle]

Package: golang-src
Version: 1.5.1-4
Severity: normal

Dear Maintainer,

The files installed as /usr/share/go/src/runtime/race/*.syso are not built
during package build, but rather come directly from the Go source distribution.
To ensure that they are built from what they claim to be, in Ubuntu we do not
distribute these files in the golang-src package but rather build them in a
separate golang-race-detector-runtime package which golang-go Recommends:. It
would be nice if Debian could steal this work :-)

Cheers,
mwh

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

Kernel: Linux 4.2.0-19-generic (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Bug#807454: python-django-tagging: FTBFS: /tagging_tags': cannot import name get_model

[Chris Lamb]

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

Dear Maintainer,

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

  [..]

File "/usr/lib/python2.7/dist-packages/django/test/client.py", line
503, in get
  **extra)
File "/usr/lib/python2.7/dist-packages/django/test/client.py", line
304, in get
  return self.generic('GET', path, secure=secure, **r)
File "/usr/lib/python2.7/dist-packages/django/test/client.py", line
380, in generic
  return self.request(**r)
File "/usr/lib/python2.7/dist-packages/django/test/client.py", line
449, in request
  response = self.handler(environ)
File "/usr/lib/python2.7/dist-packages/django/test/client.py", line
123, in __call__
  response = self.get_response(request)
File
"/usr/lib/python2.7/dist-packages/django/core/handlers/base.py",
line 230, in get_response
  response = self.handle_uncaught_exception(request, resolver,
  sys.exc_info())
File
"/usr/lib/python2.7/dist-packages/django/core/handlers/base.py",
line 296, in handle_uncaught_exception
  return callback(request, **param_dict)
File "/usr/lib/python2.7/dist-packages/django/utils/decorators.py",
line 149, in _wrapped_view
  response = view_func(request, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/django/views/defaults.py",
line 60, in server_error
  template = loader.get_template(template_name)
File "/usr/lib/python2.7/dist-packages/django/template/loader.py",
line 26, in get_template
  engines = _engine_list(using)
File "/usr/lib/python2.7/dist-packages/django/template/loader.py",
line 143, in _engine_list
  return engines.all() if using is None else [engines[using]]
File "/usr/lib/python2.7/dist-packages/django/template/utils.py",
line 110, in all
  return [self[alias] for alias in self]
File "/usr/lib/python2.7/dist-packages/django/template/utils.py",
line 101, in __getitem__
  engine = engine_cls(params)
File
"/usr/lib/python2.7/dist-packages/django/template/backends/django.py",
line 31, in __init__
  options['libraries'] = self.get_templatetag_libraries(libraries)
File
"/usr/lib/python2.7/dist-packages/django/template/backends/django.py",
line 49, in get_templatetag_libraries
  libraries = get_installed_libraries()
File
"/usr/lib/python2.7/dist-packages/django/template/backends/django.py",
line 131, in get_installed_libraries
  for name in get_package_libraries(pkg):
File
"/usr/lib/python2.7/dist-packages/django/template/backends/django.py",
line 148, in get_package_libraries
  "trying to load '%s': %s" % (entry[1], e)
  InvalidTemplateLibrary: Invalid template library specified.
  ImportError raised when trying to load
  'tagging.templatetags.tagging_tags': cannot import name get_model
  
  --
  Ran 72 tests in 0.602s
  
  FAILED (errors=6)
  Creating test database for alias 'default'...
  Destroying test database for alias 'default'...
  debian/rules:10: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory
  '/home/lamby/temp/cdt.20151209041815.24giKO3Hiy/python-django-tagging-0.4'
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


python-django-tagging.1:0.4-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#781180: Please add new youtube-dl in jessie-updates

[Nicholas Steeves]

Hello,

Because there was already an out-of-date version of youtube-dl in
backports, I thought I might be able to help out by updating it to
2015.11.27.1-1~bpo8+1.  Please let me know if you'd prefer if I look
for a sponsor @mentors.debian.net

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

  http://mentors.debian.net/package/youtube-dl


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

dget -x 
http://mentors.debian.net/debian/pool/main/y/youtube-dl/youtube-dl_2015.11.27.1-1~bpo8+1.dsc

Kind regards,
Nicholas

Bug#807294: golang-go: contains some but not all race-enabled packages

[Michael Hudson-Doyle]

And another one after I remember that make is not shell :/

On 9 December 2015 at 14:09, Michael Hudson-Doyle
 wrote:
> Here's a patch that removes the race enabled packages, which I'm
> planning to include in Ubuntu.
>
> On 7 December 2015 at 20:13, Michael Hudson-Doyle
>  wrote:
>> Package: golang-go
>> Version: 1.5.1-4
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> As you can see on https://packages.debian.org/sid/amd64/golang-go/filelist
>> there are quite a few race-enabled package .a files included in the package.
>> They are there because of the race-testing ./run.bash does. I think it's a 
>> bit
>> silly that a subset of such packages are installed: either all of them should
>> be installed (this is what the 1.4 packaging did I think), or none of them.
>> apart from anything else, this means that if DEB_BUILD_OPTIONS=nocheck 
>> actually
>> worked (see bug 807290 ), the files included in the package would 
>> change
>> depending on whether DEB_BUILD_OPTIONS=nocheck was set or not, which seems 
>> like
>> a bad thing to me.
>>
>> Happy to implement either option if given an opinion!
>>
>> Cheers,
>> mwh
>>
>> -- System Information:
>> Debian Release: stretch/sid
>>   APT prefers unstable
>>   APT policy: (500, 'unstable')
>> Architecture: amd64 (x86_64)
>>
>> Kernel: Linux 4.2.0-18-generic (SMP w/4 CPU cores)
>> Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=locale: Cannot set 
>> LC_CTYPE to default locale: No such file or directory
>> locale: Cannot set LC_MESSAGES to default locale: No such file or directory
>> locale: Cannot set LC_ALL to default locale: No such file or directory
>> ANSI_X3.4-1968)
>> Shell: /bin/sh linked to /bin/dash
>> Init: unable to detect
diff --git a/debian/rules b/debian/rules
index 268db73..7093818 100755
--- a/debian/rules
+++ b/debian/rules
@@ -31,6 +31,10 @@ ifeq (true, $(RUN_TESTS))
 		export PATH="$(GOROOT)/bin:$$PATH"; \
 		eval "$$(go tool dist env)"; \
 		bash run.bash --no-rebuild;
+	# On linux/amd64 run.bash installs some race enabled standard library
+	# packages. Delete them again to avoid accidentally including them in
+	# the package.
+	rm -rf "$(GOROOT)/pkg/linux_amd64_race/"
 else
 	# skip the tests on platforms where they fail
 endif

Bug#807453: amule: BaseClient.cpp(2143): assert "Assert failure" failed in ProcessPublicKeyPacket().

[Dmitry Smirnov]

Package: amule
Version: 2.4.0~git20151120.0023527bc2-1
Severity: important


ASSERT INFO:
../../src/BaseClient.cpp(2143): assert "Assert failure" failed in 
ProcessPublicKeyPacket().

BACKTRACE:
[1] wxOnAssert(char const*, int, char const*, char const*, char const*)
[2] CUpDownClient::ProcessPublicKeyPacket(unsigned char const*, unsigned int) 
/build/amule-2.4.0~git20151120.0023527bc2/obj-x86_64-linux-gnu/src/../../src/BaseClient.cpp:2143
[3] CClientTCPSocket::ProcessExtPacket(unsigned char const*, unsigned int, 
unsigned char) 
/build/amule-2.4.0~git20151120.0023527bc2/obj-x86_64-linux-gnu/src/../../src/ClientTCPSocket.cpp:1325
[4] CClientTCPSocket::PacketReceived(CPacket*) 
/build/amule-2.4.0~git20151120.0023527bc2/obj-x86_64-linux-gnu/src/../../src/ClientTCPSocket.cpp:1990
[5] CEMSocket::OnReceive(int) 
/build/amule-2.4.0~git20151120.0023527bc2/obj-x86_64-linux-gnu/src/../../src/EMSocket.cpp:275
[6] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, 
wxEvent&) const
[7] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, 
wxEvtHandler*, wxEvent&)
[8] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[9] wxEvtHandler::TryHereOnly(wxEvent&)
[10] wxEvtHandler::ProcessEventLocally(wxEvent&)
[11] wxEvtHandler::ProcessEvent(wxEvent&)
[12] wxEvtHandler::ProcessPendingEvents()
[13] wxAppConsoleBase::ProcessPendingEvents()
[14] wxApp::DoIdle()
[15] g_main_context_dispatch
[16] g_main_loop_run
[17] gtk_main
[18] wxGUIEventLoop::DoRun()
[19] wxEventLoopBase::Run()
[20] wxAppConsoleBase::MainLoop()
[21] wxEntry(int&, wchar_t**)
[22] main 
/build/amule-2.4.0~git20151120.0023527bc2/obj-x86_64-linux-gnu/src/../../src/amule-gui.cpp:93
[23] __libc_start_main
[24] main


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

Debian Release: stretch/sid
  500 testing-updates httpredir.debian.org 
  500 testing security.debian.org 
  500 testing httpredir.debian.org 
  333 unstablehttpredir.debian.org 

--- Package information. ---
Depends (Version) | Installed
=-+-===
amule-common (= 2.3.1-11) | 2.4.0~git20151120.0023527bc2-1
libc6   (>= 2.14) | 
libcrypto++9  | 
libgcc1  (>= 1:4.1.1) | 
libgeoip1 | 
libstdc++6   (>= 4.6) | 
libupnp6(>= 1:1.6.13) | 
libwxbase2.8-0 (>= 2.8.12.1+dfsg) | 
libwxgtk2.8-0  (>= 2.8.12.1+dfsg) | 
zlib1g   (>= 1:1.1.4) | 


Recommends   (Version) | Installed
==-+-===
amule-utils| 2.4.0~git20151120.0023527bc2-1
unzip  | 6.0-20


Suggests (Version) | Installed
==-+-===
amule-utils-gui| 

-- 
Regards,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B

---

Perhaps is is better to be irresponsible and right, than to be responsible
and wrong.
-- Winston Churchill


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

Bug#807452: ikiwiki: please upload stretch version to jessie-backports

[Sean Whitton]

Package: ikiwiki
Severity: wishlist

Dear Maintainer,

The stretch package of ikiwiki version 3.20150614 installs and runs
just fine on Debian Jessie with no dependency upgrades required.  I
would very much appreciate it if this version could be uploaded to
jessie-backports.  In my own case, the new emailauth plug-in in
3.20150614 is a very useful addition.

Thanks.

Sean Whitton

Bug#803319: chromium: GPU accelerated video decode failure

[Wolfgang Walter]

On Sat, 05 Dec 2015 15:07:42 +0100 Paride Legovini  wrote:
> Package: chromium
> Version: 47.0.2526.73-1
> Followup-For: Bug #803319
> 
> Duplicate of #804901, I already reported this issue while chromium 47
> was still in experimental, but unfortunately the report was ignored.
> The PDF attached to that bug shows the broken chrome://gpu.
> 
> Regards,
> 
> Paride
> 
> 

Same problem here: no gpu acceleration.

I can confirm that your suspicion that

Enable accelerated video decoding (closes: #793815).

is the culprit is correct. I built chromium without

system/vaapi.patch

and hardware acceleration works again.

Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts

Bug#807041: logind: laptop unexpectedly auto-suspends after some time of inactivity

[George B.]

On 08/12/15 14:52, Michael Biebl wrote:


Have you set IdleAction= and IdleActionSec= in /etc/systemd/logind.conf?

If not, this looks like the suspend request is triggered externally and
logind simply executes the action.


No, my logind.conf is the Debian default with all the options commented out.


Do you have a tool like xfce4-power-manager, mate-power-manager,
lxqt-powermanagement etc installed?


Not that I can find:

```
$ dpkg -l | awk '{print $2}' | grep power
powermgmt-base
powertop
ruby-power-assert
```


Does systemd-inhibit list anything?


```
$ systemd-inhibit
 Who: NetworkManager (UID 0/root, PID 935/NetworkManager)
What: sleep
 Why: NetworkManager needs to turn off networks
Mode: delay

1 inhibitors listed.
```


Can you run dbus-monitor --system (as root) and check if you get any
dbus messages for org.freedesktop.login1 at the time the suspend happens.


This is the first sleep-related thing - happens about 15 minutes of idle:

```
signal time=1449602082.422699 sender=:1.1 -> destination=(null destination) 
serial=264 path=/org/freedesktop/login1; interface=org.freedesktop.login1.Manager; 
member=PrepareForSleep
   boolean true
signal time=1449602082.423998 sender=:1.1 -> destination=(null destination) 
serial=265 path=/org/freedesktop/login1; 
interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
   string "org.freedesktop.login1.Manager"
   array [
  dict entry(
 string "DelayInhibited"
 variant string "sleep"
  )
   ]
   array [
   ]
method call time=1449602082.424179 sender=:1.1 -> 
destination=org.freedesktop.systemd1 serial=266 path=/org/freedesktop/systemd1; 
interface=org.freedesktop.systemd1.Manager; member=StartUnit
   string "suspend.target"
   string "replace-irreversibly"
```


Best regards,

George

Bug#807451: lftp: should recommend openssh-client

[Vincent Lefevre]

Package: lftp
Version: 4.6.3a-1+b1
Severity: wishlist

Since lftp uses ssh (with OpenSSH usage) for secure connections, it
should recommend openssh-client (or ssh-client | openssh-client?).

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

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, 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 lftp depends on:
ii  libc6  2.21-3
ii  libgcc11:5.3.1-3
ii  libgnutls-deb0-28  3.3.18-1
ii  libidn11   1.32-3
ii  libreadline6   6.3-8+b4
ii  libstdc++6 5.3.1-3
ii  libtinfo5  6.0+20151024-2
ii  netbase5.3
ii  zlib1g 1:1.2.8.dfsg-2+b1

lftp recommends no packages.

lftp suggests no packages.

-- no debconf information

Bug#807450: TP: libperinci-sub-util-perl -- Perl module that is a helper to write functions

[Lucas Kanashiroo]

Package: wnpp
Owner: Lucas Kanashiro 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libperinci-sub-util-perl
  Version : 0.42
  Upstream Author : perlancar 
* URL : https://metacpan.org/release/Perinci-Sub-Util
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Perl module that is a helper to write functions

Perinci::Sub::Util is a helper to write functions. This module could help with
handling errors, where the application can be killed or just throw some warn,
generate stub functions and be used as a caller.

The package will be maintained under the umbrella of the Debian Perl Group.


signature.asc
Description: PGP signature

Bug#807239: lftp: can no longer connect with sftp (no matching host key type found)

[Vincent Lefevre]

Control: reassign -1 openssh-client 1:7.1p1-1
Control: severity -1 normal
Control: retitle -1 openssh-client: ssh complains on host key type even when 
host key checking is disabled

On 2015-12-06 16:48:35 +0100, Vincent Lefevre wrote:
> Package: lftp
> Version: 4.6.3a-1+b1
> Severity: grave
> Justification: renders package unusable
> 
> After a system upgrade, lftp can no longer connect with sftp.
> When I type "dir", I get the error:
> 
> `ls' at 0 [Unable to negotiate with 192.168.1.4: no matching host key type 
> found. Their offer: ssh-dss]
> 
> 4 days ago, I had no problems.

The problem actually comes from openssh-client (on which lftp has
no dependencies!).

First, the error is surprising because I was just using an IP address,
for which host key checking doesn't make much sense. But even if I set
both CheckHostIP and StrictHostKeyChecking to "no", I get the error!

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#807449: ITP: klaus -- simple easy-to-set-up Git web viewer

[Jelmer Vernooij]

Package: wnpp
Severity: wishlist
Owner: Jelmer Vernooij 

* Package name: klaus
  Version : 0.7.1
  Upstream Author : Jonas Haag 
* URL : https://github.com/jonashaag/klaus
* License : MIT
  Programming Lang: Python
  Description : simple easy-to-set-up Git web viewer

Klaus is a simple web viewer for Git repositories, which
can display history, tree contents and file contents (including syntax
highlighting).

It also allows retrieval of archive contents as well as pulling
and pushing repositories using the Git smart server protocol.

Bug#807294: golang-go: contains some but not all race-enabled packages

[Michael Hudson-Doyle]

Here's a patch that removes the race enabled packages, which I'm
planning to include in Ubuntu.

On 7 December 2015 at 20:13, Michael Hudson-Doyle
 wrote:
> Package: golang-go
> Version: 1.5.1-4
> Severity: normal
>
> Dear Maintainer,
>
> As you can see on https://packages.debian.org/sid/amd64/golang-go/filelist
> there are quite a few race-enabled package .a files included in the package.
> They are there because of the race-testing ./run.bash does. I think it's a bit
> silly that a subset of such packages are installed: either all of them should
> be installed (this is what the 1.4 packaging did I think), or none of them.
> apart from anything else, this means that if DEB_BUILD_OPTIONS=nocheck 
> actually
> worked (see bug 807290 ), the files included in the package would change
> depending on whether DEB_BUILD_OPTIONS=nocheck was set or not, which seems 
> like
> a bad thing to me.
>
> Happy to implement either option if given an opinion!
>
> Cheers,
> mwh
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.2.0-18-generic (SMP w/4 CPU cores)
> Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=locale: Cannot set 
> LC_CTYPE to default locale: No such file or directory
> locale: Cannot set LC_MESSAGES to default locale: No such file or directory
> locale: Cannot set LC_ALL to default locale: No such file or directory
> ANSI_X3.4-1968)
> Shell: /bin/sh linked to /bin/dash
> Init: unable to detect
diff --git a/debian/rules b/debian/rules
index 268db73..5edcfd6 100755
--- a/debian/rules
+++ b/debian/rules
@@ -31,6 +31,10 @@ ifeq (true, $(RUN_TESTS))
 		export PATH="$(GOROOT)/bin:$$PATH"; \
 		eval "$$(go tool dist env)"; \
 		bash run.bash --no-rebuild;
+	# On linux/amd64 run.bash installs some race enabled standard library
+	# packages. Delete them again to avoid accidentally including them in
+	# the package.
+	rm -rf "$(GOROOT)/pkg/*_race"
 else
 	# skip the tests on platforms where they fail
 endif

Bug#806985: libinput10: please enable libinput tools

[Alessio Treglia]

Hi,

Please find the patch attached.

Thanks for considering.
Regards.

-- 
Alessio Treglia  | www.alessiotreglia.com
Debian Developer | ales...@debian.org
Ubuntu Core Developer|  quadris...@ubuntu.com
0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A
From 4c7d1ea61071d68328200a9ff8ab222ccc4ffe21 Mon Sep 17 00:00:00 2001
From: Alessio Treglia 
Date: Wed, 9 Dec 2015 01:04:38 +
Subject: [PATCH] Ship libinput-tools

Closes: #806985
Thanks: Ritesh Raj Sarraf for reporting this.
---
 debian/control| 18 ++
 debian/libinput-tools.install |  2 ++
 2 files changed, 20 insertions(+)
 create mode 100644 debian/libinput-tools.install

diff --git a/debian/control b/debian/control
index 464a4f6..cd5e772 100644
--- a/debian/control
+++ b/debian/control
@@ -76,3 +76,21 @@ Description: input device management and event handling library - development fi
  processing and abstraction so minimize the amount of custom input
  code the user of libinput need to provide the common set of
  functionality that users expect.
+
+Package: libinput-tools
+Section: libdevel
+Priority: extra
+Architecture: any
+Multi-Arch: allowed
+Depends:
+ libinput10 (= ${binary:Version}),
+ ${shlibs:Depends},
+ ${misc:Depends},
+Description: input device management and event handling library - command line tools
+ libinput is a library that handles input devices for display servers and
+ other applications that need to directly deal with input devices.
+ .
+ It provides device detection, device handling, input device event
+ processing and abstraction so minimize the amount of custom input
+ code the user of libinput need to provide the common set of
+ functionality that users expect.
diff --git a/debian/libinput-tools.install b/debian/libinput-tools.install
new file mode 100644
index 000..68671de
--- /dev/null
+++ b/debian/libinput-tools.install
@@ -0,0 +1,2 @@
+usr/bin/*
+usr/share/man/man1/*
-- 
2.5.0

Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'

[John Paul Adrian Glaubitz]

On Fri, Apr 10, 2015 at 05:39:50PM -0400, Milan Kupcevic wrote:
 > The module landed in sid D-I. It gets loaded automatically as it is not
> blacklisted in D-I. I've been able to boot and run the installer on an
> XServe G4 DP, a G4 Mac Mini, and a Pegasos II. All three machines have
> radeon cards.
 
This reddit user got different results which rather support my stance:

> https://www.reddit.com/r/debian/3vyn0p/

Frankly, I think it's more important to have a working graphics driver
on ubiqutous Apple PowerPC hardware than on these extremely obscure
Pegasos-II boards which have very negligible user base given the fact
that those were rather expensive due to their low production numbers.

So my opinion remains unchanged: Drop radeonfb by any means as it's
obsolete and breaks the way more ubiqutous radeon KMS driver.

Cheers,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#712841: Device identification to detect fanless systems

[Martin Michlmayr]

A user just reminded me that this issue is still outstanding.

I will search my emails archives to refresh my memory on using GPIOs
to detect the system.

I'll also send another email to QNAP to see if they have a good idea
how to solve this issue.

Finally, I remembered that the filesystem on (I believe) mtdblock5
contains a config file with the QNAP model, so if everything else
fails, we should be able to use that.

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#807446: oclgrind: tests fail on big-endian systems

[Rebecca N. Palmer]

Package: oclgrind
Version: 15.5-2
Severity: serious

oclgrind FTBFS on big-endian systems (mips,powerpc,s390x) with several 
test failures:

https://buildd.debian.org/status/fetch.php?pkg=oclgrind&arch=mips&ver=15.5-2&stamp=1449588354

Given that this is its first upload with tests enabled, it is fairly 
likely that it has never worked on such systems, and it may be 
appropriate to have it removed: see 
https://wiki.debian.org/ftpmaster_Removals for how to do this.

Bug#807447: 0ad: version 0.0.19 is out

[ydirson]

Package: 0ad
Version: 0.0.18-2
Severity: wishlist

0.0.19 was recently released, it would be great to have it :)

Bug#806965: [Pkg-opencl-devel] Bug#806965: oclgrind: FTBFS on ppc64el -- conflict with altivec keyword bool

[Rebecca N. Palmer]

You're right. Upstream needs the local copy since many systems don't
have recent enough OpenCL headers, but for Debian I could add a patch
to remove the local copy and have a build-dependency on opencl-headers
instead.


opencl-headers already has the __vector fix, but as already noted, the 
bool problem is a deeper "this is a keyword in standard C++" issue:


http://sources.debian.net/src/khronos-opencl-headers/2.0~svn32091-1/debian/patches/use__vector.patch

On 08/12/15 21:14, J Price wrote:

Reading some other bug reports (e.g. [1]) suggests that compiling with
`-std=gnu++11` instead of `-std=c++11` also fixes the problem. Is this
a viable workaround? This would be a simple patch to CMakeLists.txt.


Probably; if you want to test on ppc64el there's qemu-debootstrap (~10x 
slower, but shouldn't be a problem for a package this small), 
https://wiki.debian.org/CrossCompiling or the porterbox, but several of 
my FTBFS-on-$arch fixes were uploaded without testing on $arch.

Bug#807445: kopete crashes with kde4libs 4:4.14.14-1

[Wolfgang Walter]

Package: src:kde4libs
Version: 4:4.14.14-1
Severity: normal

kopete chrashes when one closes a chat window or the settings dialog. 
Downgrading kde4libs to 4:4.14.13-1 fixes the issue.

This is probably upstream

https://bugs.kde.org/show_bug.cgi?id=355275

According to Alex Merry a fix would be to revert commit 4f7ea2f77

https://bugs.kde.org/show_bug.cgi?id=355275#c25

Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts

Bug#770394: [PATCH initramfs-tools] update-initramfs: Use linux-version command to sort versions

[Ben Hutchings]

dpkg does not know how to sort -rc and -trunk suffixes as we want.
Also, we were using the deprecated '>' version operator which will
trigger warnings in newer versions of dpkg.

Closes: #770394, #795837
Signed-off-by: Ben Hutchings 
---
 debian/control   |  2 +-
 update-initramfs | 22 +-
 2 files changed, 2 insertions(+), 22 deletions(-)

diff --git a/debian/control b/debian/control
index 4da3477..67f5c5f 100644
--- a/debian/control
+++ b/debian/control
@@ -11,7 +11,7 @@ Vcs-Git: 
https://anonscm.debian.org/git/kernel/initramfs-tools.git
 Package: initramfs-tools
 Architecture: all
 Multi-Arch: foreign
-Depends: initramfs-tools-core, ${misc:Depends}
+Depends: initramfs-tools-core, linux-base, ${misc:Depends}
 Suggests: bash-completion
 Provides: linux-initramfs-tool
 Conflicts: linux-initramfs-tool, usplash (<< 0.5.50)
diff --git a/update-initramfs b/update-initramfs
index ea301ba..487b785 100755
--- a/update-initramfs
+++ b/update-initramfs
@@ -228,27 +228,7 @@ ro_boot_check()
 
 get_sorted_versions()
 {
-   version_list=""
-
-   for gsv_x in "${STATEDIR}"/*; do
-   gsv_x="$(basename "${gsv_x}")"
-   if [ "${gsv_x}" = '*' ]; then
-   return 0
-   fi
-   worklist=""
-   for gsv_i in $version_list; do
-   if dpkg --compare-versions "${gsv_x}" '>' "${gsv_i}" 
2>/dev/null; then
-   worklist="${worklist} ${gsv_x} ${gsv_i}"
-   gsv_x=""
-   else
-   worklist="${worklist} ${gsv_i}"
-   fi
-   done
-   if [ "${gsv_x}" != "" ]; then
-   worklist="${worklist} ${gsv_x}"
-   fi
-   version_list="${worklist}"
-   done
+   version_list="$(ls -1 "${STATEDIR}" | linux-version sort --reverse)"
 
    verbose "Available versions: ${version_list}"
 }
-- 
Ben Hutchings
Life would be so much easier if we could look at the source code.

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

Bug#806898: RFS: roxterm/3.3.1-1

[Tony Houghton]

On 08/12/15 14:05, Mattia Rizzolo wrote:

On Tue, Dec 08, 2015 at 01:59:56PM +, Tony Houghton wrote:

I must remember to change the level in my lintian options as well as fixing


I believe (because I have a pbuilder hook that runs lintian for me, I
rarely run it manyally) just dumping the following in ~/.lintianrc is
enough:
info=yes
display-info=yes
display-experimental=yes
pedantic=yes
show-overrides=no
color=always


I put in display-info=yes already, but I might as well include all of those.


this specific problem. It looks like a leftover from the deprecated debian
menu entry, but for some reason I can't find it in debian/rules or the
upstream build system.


just remove debian/dirs :)


I didn't spot that when I grepped the debian directory!

Bug#807444: stormbaancoureur: doc mentions non-shipped example keybinding file

[ydirson]

Package: stormbaancoureur
Version: 2.1.6-1.1

Quoting README:

>For keyboard controls, you can customize the key mapping by copying the file
>.stormbaancoureur.keys.example to $HOME/.stormbaancoureur.keys and then 
>editting
>it.

Having this file in the package would be a must!

Bug#697017: [PATCH initramfs-tools 2/3] parse_numeric: Add support for 20-bit minor numbers in 'root' parameter

[Ben Hutchings]

Linux supports 32-bit device numbers in the format 0xmmmMMMmm, where
each m is a hex digit of the minor number and each M is a hex digit of
the major number.

Currently parse_lilo only works if the top 3 digits are 0 (or absent).
Shift and mask the upper bits correctly.

Signed-off-by: Ben Hutchings 
---
 scripts/functions | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/functions b/scripts/functions
index 2da6173..adcfefa 100644
--- a/scripts/functions
+++ b/scripts/functions
@@ -121,8 +121,8 @@ parse_numeric() {
    *)
    # [A-Fa-f0-9]*
    value=$(( 0x${1} ))
-   minor=$(( ${value} % 256 ))
-   major=$(( ${value} / 256 ))
+   minor=$(( (${value} & 0xff) | (${value} >> 12) & 0xfff00 ))
+   major=$(( (${value} >> 8) & 0xfff ))
    ;;
    esac
 

-- 
Ben Hutchings
Life would be so much easier if we could look at the source code.

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

Bug#697017: [PATCH initramfs-tools 1/3] parse_numeric: Tighten check for whether 'root' parameter is a number

[Ben Hutchings]

Based on work by Jonathan Nieder.

Closes: #697017
Signed-off-by: Ben Hutchings 
---
 scripts/functions | 25 ++---
 1 file changed, 14 insertions(+), 11 deletions(-)

diff --git a/scripts/functions b/scripts/functions
index 33fddcf..2da6173 100644
--- a/scripts/functions
+++ b/scripts/functions
@@ -103,24 +103,27 @@ load_modules()
 # lilo compatibility
 parse_numeric() {
    case $1 in
-   "")
-   return
+   *:*)
+   # Does it match /[0-9]*:[0-9]*/?
+   minor=${1#*:}
+   major=${1%:*}
+   case $major$minor in
+   *[!0-9]*)
+   # No.
+   return
+   ;;
+   esac
    ;;
-   /*)
+   "" | *[!A-Fa-f0-9]*)
+   # "", "/*", etc.
    return
    ;;
-   [0-9]*:[0-9]*)
-   minor=$(( ${1#*:} ))
-   major=$(( ${1%:*} ))
-   ;;
-   [A-Fa-f0-9]*)
+   *)
+   # [A-Fa-f0-9]*
    value=$(( 0x${1} ))
    minor=$(( ${value} % 256 ))
    major=$(( ${value} / 256 ))
    ;;
-   *)
-   return
-   ;;
    esac
 
    if command -v udevd >/dev/null 2>&1; then

-- 
Ben Hutchings
Life would be so much easier if we could look at the source code.

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

Bug#807442: patch

[dann frazier]

Attached.
diff -Nru s390-tools-1.32.0/debian/changelog s390-tools-1.32.0/debian/changelog
--- s390-tools-1.32.0/debian/changelog	2015-10-25 17:12:02.0 +0100
+++ s390-tools-1.32.0/debian/changelog	2015-12-08 23:14:52.0 +0100
@@ -1,3 +1,9 @@
+s390-tools (1.32.0-2) UNRELEASED; urgency=medium
+
+  * Add dbginfo.sh. (Closes: #807442)
+
+ -- dann frazier   Tue, 08 Dec 2015 22:33:52 +0100
+
 s390-tools (1.32.0-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru s390-tools-1.32.0/debian/s390-tools.install s390-tools-1.32.0/debian/s390-tools.install
--- s390-tools-1.32.0/debian/s390-tools.install	2014-07-26 23:59:18.0 +0200
+++ s390-tools-1.32.0/debian/s390-tools.install	2015-12-08 23:08:30.0 +0100
@@ -10,6 +10,10 @@
 /sbin/dasdview
 /usr/share/man/man8/dasdview.8
 
+# dbginfo.sh
+/sbin/dbginfo.sh
+/usr/share/man/man1/dbginfo.sh.1
+
 # fdasd
 /sbin/fdasd
 /usr/share/man/man8/fdasd.8

Bug#807443: Better error message for incorrect apt sources?

[Petter Reinholdtsen]

Package: apt-transport-tor
Version: 0.2.1-1

When using apt-transport-tor, and there is a typo in the hostname of an
apt source, an error message like this show up when doing 'apt-get
update':

  Err tor+http://vxwakviie2ienjx6t.onion jessie/main amd64 Packages
Can't complete SOCKS5 connection to 0.0.0.0:0. (1)

The error message is not easy to understand, and I was unable to
understand that this was the same as this error when using the normal
http transport:

  Err http://http.debin.net jessie Release.gpg 
Something wicked happened resolving 'http.debin.net:http' (-5 - No
  address associated with hostname)

Would it be possible to change the message from apt-transport-tor to
explain that the hostname is unknown or missing in DNS or something
instead of the "Can't complete SOCKS5 connection to 0.0.0.0:0" message?

I suspect it would make debugging typos in sources.list a lot easier. :)

-- 
Happy hacking
Petter Reinholdtsen

Bug#807442: please include dbginfo.sh

[dann frazier]

Package: s390-tools
Version: 1.32.0-1
Severity: normal
Tags: patch

The source package provides a dbginfo.sh tool that is not currently
included in the binary package.

Bug#807441: Acknowledgement (rename procedure out of date)

[Antoine Beaupré]

It should also be "Breaks" and not "Conflicts", apparently. But this
seriously needs to be reviewed...

a.
-- 
Religion is like a blind man looking in a black room for a black cat
that isn't there, and finding it.
 - Oscar Wilde

Bug#807441: rename procedure out of date

[Antoine Beaupré]

Source: developers-reference
Severity: normal

The procedure documented here is badly out of date:

https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#s5.9.3

Among other things, it does not mention dummy packages and imposes
unnecessary load on FTP masters.

The procedure here seems to be a little more up to date:

https://wiki.debian.org/Renaming_a_Package

Maybe the two should be merged? At the very least, it should be
mentionned that leaf binary packages *do* need a dummy package
otherwise they will not be updated properly.

#486368 is similar, but since it's only asking for an example, i think
this is a different issue: the documentation there is not only
lacking, it's incorrect.

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

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

Bug#807440: patch

[dann frazier]

Attached.
diff -Nru s390-tools-1.32.0/debian/changelog s390-tools-1.32.0/debian/changelog
--- s390-tools-1.32.0/debian/changelog	2015-10-25 17:12:02.0 +0100
+++ s390-tools-1.32.0/debian/changelog	2015-12-08 22:53:28.0 +0100
@@ -1,3 +1,9 @@
+s390-tools (1.32.0-2) UNRELEASED; urgency=medium
+
+  * Add lsluns. (Closes: #807440)
+
+ -- dann frazier   Tue, 08 Dec 2015 22:33:52 +0100
+
 s390-tools (1.32.0-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru s390-tools-1.32.0/debian/control s390-tools-1.32.0/debian/control
--- s390-tools-1.32.0/debian/control	2015-08-16 21:03:16.0 +0200
+++ s390-tools-1.32.0/debian/control	2015-12-08 22:31:55.0 +0100
@@ -10,6 +10,7 @@
 Package: s390-tools
 Architecture: s390 s390x
 Depends: ${shlibs:Depends}, ${misc:Depends}, gawk
+Recommends: sg3-utils
 Description: A set of fundamental utilities for Linux on S/390
  The package contains:
   * dasdfmt, which is used to low-level format ECKD-DASDs with either
diff -Nru s390-tools-1.32.0/debian/patches/series s390-tools-1.32.0/debian/patches/series
--- s390-tools-1.32.0/debian/patches/series	2015-08-16 21:02:26.0 +0200
+++ s390-tools-1.32.0/debian/patches/series	2015-12-08 22:36:46.0 +0100
@@ -5,3 +5,4 @@
 error-manpages.patch
 zipl-optional.patch
 disable.patch
+sg3-utils.patch
diff -Nru s390-tools-1.32.0/debian/patches/sg3-utils.patch s390-tools-1.32.0/debian/patches/sg3-utils.patch
--- s390-tools-1.32.0/debian/patches/sg3-utils.patch	1970-01-01 01:00:00.0 +0100
+++ s390-tools-1.32.0/debian/patches/sg3-utils.patch	2015-12-08 22:47:59.0 +0100
@@ -0,0 +1,19 @@
+Description: Fix warning to emit proper sg3-utils package name for Debian
+Author: dann frazier 
+Forwarded: no
+Last-Update: 2015-12-08
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: s390-tools-1.32.0/zconf/lsluns
+===
+--- s390-tools-1.32.0.orig/zconf/lsluns
 s390-tools-1.32.0/zconf/lsluns
+@@ -321,7 +321,7 @@ push @port, map { @{$res_hash{$_}} } key
+ 
+ # checking for helper progs
+ 
+-die "$PROGRAM_NAME: Unable to execute due to missing sg3_utils package. ".
++die "$PROGRAM_NAME: Unable to execute due to missing sg3-utils package. ".
+ "Processing stopped.\n" if system("sg_luns -V > /dev/null 2>&1");
+ 
+ 
diff -Nru s390-tools-1.32.0/debian/s390-tools.install s390-tools-1.32.0/debian/s390-tools.install
--- s390-tools-1.32.0/debian/s390-tools.install	2014-07-26 23:59:18.0 +0200
+++ s390-tools-1.32.0/debian/s390-tools.install	2015-12-08 22:33:40.0 +0100
@@ -40,6 +40,10 @@
 /sbin/qethconf
 /usr/share/man/man8/qethconf.8
 
+# lsluns
+/usr/sbin/lsluns
+/usr/share/man/man8/lsluns.8
+
 # tape390
 /sbin/tape390_display
 /usr/share/man/man8/tape390_display.8

Bug#807440: please include lsluns

[dann frazier]

Package: s390-tools
Version: 1.32.0-1
Severity: normal
Tags: patch

The source package provides an lsluns tool that is not currently
included in the binary package.

Bug#807439: boxes: boxes.el in xemacs

[Kevin Ryde]

Package: boxes
Version: 1.1.2-3
Severity: normal
Tags: patch
File: /usr/share/emacs/site-lisp/boxes.el

boxes.el doesn't work in xemacs21 (which is still in debian) due to a
6-arg call to shell-command-on-region.

M-x boxes-create
=> Wrong number of arguments: shell-command-on-region, 6

I suggest omitting this arg since its `nil' there is the default anyway
in gnu emacs.

--- boxes.el.orig	2015-01-17 08:16:13.0 +1100
+++ boxes.el	2015-12-09 08:27:01.988263968 +1100
@@ -117,7 +117,7 @@
 		 (concat boxes-args " -r "))
 		 (if type
 		 (concat boxes-args " -d " type)
-(shell-command-on-region start end command-string nil 1 nil)))
+(shell-command-on-region start end command-string nil 1)))
 
 (provide 'boxes)
 ;;; boxes.el ends here


-- System Information:
Debian Release: stretch/sid
Architecture: i386 (i686)

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

Versions of packages boxes depends on:
ii  libc6  2.19-22

boxes recommends no packages.

boxes suggests no packages.

-- no debconf information

Bug#799041: Updated rules for isc-dhcp-server.

[Thibaut Chèze]

Hi,

Thank you.

In case you are interrested, here's my patch for it.
He keeps working with previous versions of /isc-dhcp-server/.

Best regards,
--- logcheck-1.3.17/rulefiles/linux/ignore.d.server/dhcp	2014-10-25 00:01:52.0 +0200
+++ logcheck-1.3.17-patched/rulefiles/linux/ignore.d.server/dhcp	2015-10-05 17:57:39.0 +0200
@@ -1,48 +1,48 @@
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|): Internet (Software|Systems) Consortium DHCP Server [._[:alnum:]-]+$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|): Copyright [0-9-]+ Internet (Software|Systems) Consortium\.$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|): All rights reserved\.$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|): For info, please visit http(://www\.isc\.org/(products/DHCP|sw/dhcp/)|s://www\.isc\.org/software/dhcp/)$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|): Wrote [0-9]+ (leases|(class|group|deleted host|new dynamic host) decls) to leases file\.$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|): (BOOTREQUEST|DHCPDISCOVER) from [:[:alnum:]]+ (\([\(\):._[:alnum:]-]+\) )?via [._[:alnum:]-]+$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|): BOOTREPLY (for|on) [.0-9]{7,15} to [:[:alnum:]]+ (\([:._[:alnum:]-]+\) )?via [._[:alnum:]-]+$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|): DHCPOFFER on [.0-9]{7,15} to [:[:alnum:]]+ (\([\(\)._[:alnum:]-]+\) )?via [._[:alnum:]-]+$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|): DHCPREQUEST for [.0-9]{7,15} (\([.0-9]{7,15}\) )?from [:._[:alnum:]-]+ (\([\(\)._[:alnum:]-]+\) )?via [._[:alnum:]-]+(: unknown lease [.0-9]{7,15}\.)?$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|): DHCPACK on [.0-9]{7,15} to [:[:alnum:]]+ (\([\(\)._[:alnum:]-]+\) )?via [._[:alnum:]-]+$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|): DHCP(NAK|RELEASE|INFORM) (on|from) ([.0-9]{7,15}|[:[:alnum:].]+)$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|\[[[:digit:]]+\]|): Internet (Software|Systems) Consortium DHCP Server [._[:alnum:]-]+$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|\[[[:digit:]]+\]|): Copyright [0-9-]+ Internet (Software|Systems) Consortium\.$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|\[[[:digit:]]+\]|): All rights reserved\.$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|\[[[:digit:]]+\]|): For info, please visit http(://www\.isc\.org/(products/DHCP|sw/dhcp/)|s://www\.isc\.org/software/dhcp/)$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|\[[[:digit:]]+\]|): Wrote [0-9]+ (leases|(class|group|deleted host|new dynamic host) decls) to leases file\.$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|\[[[:digit:]]+\]|): (BOOTREQUEST|DHCPDISCOVER) from [:[:alnum:]]+ (\([\(\):._[:alnum:]-]+\) )?via [._[:alnum:]-]+$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|\[[[:digit:]]+\]|): BOOTREPLY (for|on) [.0-9]{7,15} to [:[:alnum:]]+ (\([:._[:alnum:]-]+\) )?via [._[:alnum:]-]+$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|\[[[:digit:]]+\]|): DHCPOFFER on [.0-9]{7,15} to [:[:alnum:]]+ (\([\(\)._[:alnum:]-]+\) )?via [._[:alnum:]-]+$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|\[[[:digit:]]+\]|): DHCPREQUEST for [.0-9]{7,15} (\([.0-9]{7,15}\) )?from [:._[:alnum:]-]+ (\([\(\)._[:alnum:]-]+\) )?via [._[:alnum:]-]+(: unknown lease [.0-9]{7,15}\.)?$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|\[[[:digit:]]+\]|): DHCPACK on [.0-9]{7,15} to [:[:alnum:]]+ (\([\(\)._[:alnum:]-]+\) )?via [._[:alnum:]-]+$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd(-2\.2\.x|\[[[:digit:]]+\]|): DHCP(NAK|RELEASE|INFORM) (on|from) ([.0-9]{7,15}|[:[:alnum:].]+)$
 #Added for dhcp 3
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd: DHCPDISCOVER from [:[:alnum:]]+ (\([._[:alnum:]-]+\) |)via [._[:alnum:]-]+(: load balance to peer [._[:alnum:]-]+)?$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd: DHCPOFFER on [.0-9]{7,15} to [:[:alnum:]]+ (\([._[:alnum:]-]+\) |)via [._[:alnum:]-]+$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd: DHCPREQUEST for [.0-9]{7,15} (\([.0-9]{7,15}\) |)from [:[:alnum:]]+ (\([._[:alnum:]-]+\) )?via [._[:alnum:]-]+(: load balance to peer [._[:alnum:]-]+\.?|: lease owned by peer\.?|: wrong network\.?|: lease [.0-9]{7,15} unavailable\.?)?$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd: DHCPACK on [.0-9]{7,15} to [:[:alnum:]]+ (\([._[:alnum:]-]+\) |)via [._[:alnum:]-]+$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd: DHCPNAK on [.0-9]{7,15} to [:[:alnum:]]+ (\([._[:alnum:]-]+\) |)via [._[:alnum:]-]+$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd: DHCPINFORM from [.0-9]{7,15} via [._[:alnum:]-]+$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd: DHCPRELEASE of [.0-9]{7,15} from [:[:alnum:]]+ (\([._[:alnum:]-]+\) |)via [._[:alnum:]-]+ \((not |)found\)$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd: DHCPACK to [.0-9]{7,15}( \(([:[:xdigit:]]+|)\) via [._[:alnum:]-]+)?$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd: ((balancing|balanced) )?pool [0-9a-f]{6,7} [.0-9]{7,15}/[:[:alnum:]]+ ? total [:[:alnum:]]+  free [:[:alnum:]]+  backup [:[:alnum:]]+  lts [:[:alnum:]-]+.*

Bug#807371: apt hostname resoloution failure

[peter green]

On 08/12/15 09:42, Julian Andres Klode wrote:

You might want to try running the ping as the _apt user and check
if that works. Maybe the _apt user does not have access to
/etc/resolv.conf?
   
Indeed that seems to be the issue, the resolv.conf in the chroots in 
question is not world readable for some reason. It's not world readable 
on the host system either, so I presume debootstrap copied the broken 
permissions into the chroots.


Did the user used to run aptmethods change recently?

Bug#807430: closed by Michael Biebl (Re: [Pkg-utopia-maintainers] Bug#807430: Firewalld depends on systemd)

[Juliusz Chroboczek]

reopen 807430
thanks

$ sudo apt-get install --no-install-recommends firewalld
[...]
The following NEW packages will be installed:
  cgmanager firewalld libapparmor1:i386 libcap2:i386 libcgmanager0
  libcryptsetup4:i386 libdevmapper1.02.1:i386 libgcrypt20:i386
  libgpg-error0:i386 libkmod2:i386 libnih-dbus1 libnih1 libpam-systemd
  libpolkit-backend-1-0 libseccomp2:i386 libsystemd0:i386 libudev1:i386
  policykit-1 python3-decorator python3-selinux python3-six python3-slip
  python3-slip-dbus systemd:i386 systemd-shim

(It's trying to install the i386 version since I've blacklisted systemd.)

Thanks,

-- Juliusz

Bug#800574: Bug#807244: libegl1-nvidia: Programs crash due to elisian-unlock on skylake processor with nvidia driver 352.63-1 (experimental)

[Jelle Haandrikman]

Hi Andreas,

On 2015-12-08 19:25, Andreas Beckmann wrote:

Hi Aurelien,

... buggy software (#807244), which is only exposed by running on
hardware with working TSX-NI.
That could also explain the fact that the bug was introduced in 352+.

Jelle, I didn't dig through the nvidia forums, but if this info isn't
mentioned there already, maybe you could post it:


According to the backtrace the problem is typical of a call to
mutex_unlock() on a mutex which hasn't been locked with mutex_lock()
before.

(or was already unlocked.)

I'm not a member of any of any Nvidia forum. I'm more of an advanced
Debian user, with a technical background as a tester. All the searches 
that I
just did regarding mutex_unlock() and the driver point back to this 
post.


You really are doing the best anaylysis I had found. Unfortunately it's 
also

the only one I can find.

Thanks for already doing this investigation.

best regards,
Jelle

Bug#807438: libfile-fu-perl: test suite fails in non-English locales

[Niko Tyni]

Package: libfile-fu-perl
Version: 0.0.8-2
Severity: important
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs locale
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=110210
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

This package fails to build in non-English locales, because
t/00basic.t hardcodes English error messages.

This can be fixed either by setting LC_ALL=C in debian/rules or by using
setlocale(LC_ALL, 'C') in the relevant test scripts. Patch to do the
former attached (and already forwarded upstream.)
-- 
Niko Tyni   nt...@debian.org
>From 0b458588148ebcc5933085f0943bb9aa150c548d Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Tue, 8 Dec 2015 23:21:01 +0200
Subject: [PATCH] Set the locale to C for test scripts that hardcode English
 error messages

This fixes test failures in other locales, like fr_FR.UTF-8.

Bug: https://rt.cpan.org/Public/Bug/Display.html?id=110210
---
 t/dir.t| 5 +
 t/errors.t | 5 +
 2 files changed, 10 insertions(+)

diff --git a/t/dir.t b/t/dir.t
index 856fe0f..41aed6c 100755
--- a/t/dir.t
+++ b/t/dir.t
@@ -7,6 +7,11 @@ use Test::More qw(no_plan);
 
 use File::Fu;
 
+use POSIX qw(locale_h);
+
+# tests hardcode English error messages
+setlocale(LC_ALL, "C");
+
 {
   my $d = File::Fu->dir("foo." . $$);
   $d->e and $d->rmdir;
diff --git a/t/errors.t b/t/errors.t
index 635bf9d..26c6978 100755
--- a/t/errors.t
+++ b/t/errors.t
@@ -7,6 +7,11 @@ use Test::More qw(no_plan);
 
 use File::Fu;
 
+use POSIX qw(locale_h);
+
+# tests hardcode English error messages
+setlocale(LC_ALL, "C");
+
 { # invalid ops
   my $f = File::Fu->dir;
 
-- 
2.6.2

Bug#807437: maven: mvn dependency:tree fail with "Error injecting:"

[Tomas Martišius]

Package: maven
Version: 3.3.9-2
Severity: important

[INFO] --- maven-dependency-plugin:2.7:tree (default-cli) @ sveidra2eli ---
[WARNING] Error injecting:
org.apache.maven.shared.dependency.graph.internal.Maven3DependencyGraphBuilder 
java.lang.NoClassDefFoundError: org/sonatype/aether/graph/DependencyNode
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
at java.lang.Class.getDeclaredMethods(Class.java:1975)
at

com.google.inject.spi.InjectionPoint.getInjectionPoints(InjectionPoint.java:688)
at

com.google.inject.spi.InjectionPoint.forInstanceMethodsAndFields(InjectionPoint.java:380)
at

com.google.inject.internal.ConstructorBindingImpl.getInternalDependencies(ConstructorBindingImpl.java:164)
at

com.google.inject.internal.InjectorImpl.getInternalDependencies(InjectorImpl.java:613)
at
com.google.inject.internal.InjectorImpl.cleanup(InjectorImpl.java:569)
at

com.google.inject.internal.InjectorImpl.initializeJitBinding(InjectorImpl.java:555)
at

com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:884)
at

com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:805)
at

com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:282)
at

com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:214)
at

com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:1006)
at

com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1038)
at

com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1001)
at

com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1051)


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

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

Versions of packages maven depends on:
ii  default-jre-headless [java7-runtime-headless]2:1.8-53~bpo9+1
ii  libmaven3-core-java  3.3.9-2
ii  openjdk-8-jre-headless [java7-runtime-headless]  8u72-b05-2

maven recommends no packages.

maven suggests no packages.

-- no debconf information

Bug#807436: boxes: boxes.el autoloads

[Kevin Ryde]

Package: boxes
Version: 1.1.2-3
Severity: wishlist
Tags: patch

It'd be good to have emacs autoloads for the commands in boxes.el so
they're ready for use.  I suggest file debian/emacsen-startup below
which debhelper (dh_installemacsen) will automatically install to
/etc/emacs/site-start.d/50boxes.el

;;; 50boxes.el -- debian emacs setups for boxes

(if (not (file-exists-p "/usr/share/emacs/site-lisp/boxes.el"))
(message "boxes removed but not purged, skipping setup")

  ;; These autoloads as recommended by comments at the start of boxes.el.
  ;; The code has some more autoload cookies but don't think they're needed
  ;; for normal operation.
  (autoload 'boxes-command-on-region "boxes" nil t)
  (autoload 'boxes-remove "boxes" nil t)
  (autoload 'boxes-create "boxes" nil t))



-- System Information:
Debian Release: stretch/sid
Architecture: i386 (i686)

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

Versions of packages boxes depends on:
ii  libc6  2.19-22

boxes recommends no packages.

boxes suggests no packages.

-- no debconf information

Bug#724711: some notes

[Gert Wollny]

The last few days I did test the builds of ITK 4.8.2 on powerpc and
armhf - both without python bindings). Even so compiling took more than
24 hours, which means this was an experiment I'm not going to repeat
soon.

On armhf I have only a Ubuntu 15.10 installation (g++ 4.8), it builds
out of the box but the following tests fail:  

66:itkPatchBasedDenoisingImageFilterTest0
467:itkPatchBasedDenoisingImageFilterTestGaussian
468:itkPatchBasedDenoisingImageFilterTestRician
469:itkPatchBasedDenoisingImageFilterTestPoisson
789:itkHDF5ImageIOTest
983:itkReadWriteSpatialObjectTest
984:itkReadWriteSpatialObjectTest1
985:itkReadWriteSpatialObjectTest2
1563:itkSingleLevelSetsv4DenseImage2DTest
1565:itkSingleLevelSetsv4WhitakerImage2DTest
1566:itkSingleLevelSetsv4WhitakerImage2DTestThreads
1568:itkSingleLevelSetsv4ShiImage2DTest
1569:itkSingleLevelSetsv4WhitakerImage2DWithCurvatureTest
1573:itkLevelSetsv4EquationPropagationTermTest
1574:itkLevelSetsv4EquationLaplacianTermTest
1586:itkMultiLevelSetsv4WhitakerImageSubset2DTest

On powerpc the system was Debian/sid as of Saturday 2015/12/05. 

There was a problem with ITK_HAVE_SYNC_BUILTINS, I had to disable it,
otherwise some atomic operations were not properly linked. This may be
a problem with gcc. 

With this it compiled and the following tests failed: 

531:itkDicomDifficultFile
663:itkFFTWF_FFTTest
664:itkFFTWF_RealFFTTest
665:itkVnlFFTWF_FFTTest
666:itkVnlFFTWF_RealFFTTest
757:itkGDCMImageIOTest1
760:itkGDCMImageIOTest4
770:itkGDCMImageIONoCrashTest
789:itkHDF5ImageIOTest
1037:itkIOTransformMatlabTest
1563:itkSingleLevelSetsv4DenseImage2DTest
1565:itkSingleLevelSetsv4WhitakerImage2DTest
1566:itkSingleLevelSetsv4WhitakerImage2DTestThreads
1568:itkSingleLevelSetsv4ShiImage2DTest
1569:itkSingleLevelSetsv4WhitakerImage2DWithCurvatureTest
1573:itkLevelSetsv4EquationPropagationTermTest
1574:itkLevelSetsv4EquationLaplacianTermTest
1586:itkMultiLevelSetsv4WhitakerImageSubset2DTest

>From skimming over the logs I can say that there are all types of
errors - some are about floating point accuracy, but others are real
failures, like GDCM not understanding the input file, fftw not creating
a plan etc.

Bug#806965: oclgrind: FTBFS on ppc64el -- conflict with altivec keyword bool

[J Price]

On 8 December 2015 at 19:52, Fernando Seiti Furusato
 wrote:
> Just FYI.
> Not sure if they are public headers or not, but doing so on headers:
> src/runtime/icd.h
> src/core/common.h
>
> Made it build for me.
>
> Right below #include "CL/cl.h" I included this:
>
> #ifdef __ALTIVEC__
> # undef bool
> # undef vector
> # undef pixel
> #endif
>
> I tried adding to the .cpp files (not all of them) but it didn't work.
> The headers above are the ones that actually use cl.h.

You're right - this needs to be done in common.h for this to work
(since common.h uses the bool keyword), but common.h is installed by
the -dev package, so this goes against the idea of not messing with
macros in public headers.

Reading some other bug reports (e.g. [1]) suggests that compiling with
`-std=gnu++11` instead of `-std=c++11` also fixes the problem. Is this
a viable workaround? This would be a simple patch to CMakeLists.txt.

[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58241

Bug#807435: python3-pygit2: Fails to import because of PermissionError

[Michael Fladischer]

Package: python3-pygit2
Version: 0.23.0-1+b1
Severity: important

Dear Maintainer,

attempting to import pygit2 in pytho3 results in PermissionError:

$ python3 -c "import pygit2"
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pygit2/__init__.py", line 35, in 
from .blame import Blame, BlameHunk
  File "/usr/lib/python3/dist-packages/pygit2/blame.py", line 32, in 
from .errors import check_error
  File "/usr/lib/python3/dist-packages/pygit2/errors.py", line 29, in 
from .ffi import ffi, C
  File "/usr/lib/python3/dist-packages/pygit2/ffi.py", line 35, in 
ffi, C = get_ffi()
  File "/usr/lib/python3/dist-packages/pygit2/_utils.py", line 107, in get_ffi
include_dirs=[libgit2_include], library_dirs=[libgit2_lib])
  File "/usr/lib/python3/dist-packages/cffi/api.py", line 421, in verify
lib = self.verifier.load_library()
  File "/usr/lib/python3/dist-packages/cffi/verifier.py", line 109, in 
load_library
self._write_source()
  File "/usr/lib/python3/dist-packages/cffi/verifier.py", line 198, in 
_write_source
with open(self.sourcefilename, "w") as fp:
PermissionError: [Errno 13] Permission denied: 
'/usr/lib/python3/dist-packages/pygit2/__pycache__/pygit2_cffi_9f6c1c78xe8494016.c'


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

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

Versions of packages python3-pygit2 depends on:
ii  libc6  2.21-3
ii  libgit2-23 0.23.1-1+b1
ii  python33.4.3-7
ii  python3-cffi   1.3.1-1
pn  python3-cffi-backend-api-9729  

python3-pygit2 recommends no packages.

Versions of packages python3-pygit2 suggests:
pn  python-pygit2-doc  

-- no debconf information

Bug#807434: RFS: elpa-aggressive-indent/1.4.2-1 [ITP] -- Emacs minor mode that reindents code after every change

[Sean Whitton]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "elpa-aggressive-indent",
which I prepared using dh_elpa.

 Package name: elpa-aggressive-indent
 Version : 1.4.2-1
 Upstream Author : Artur Malabarba 
 URL : https://github.com/Malabarba/aggressive-indent-mode
 License : GPL-2+
 Section : lisp

It builds the binary packages elpa-aggressive-indent.  Although the
upstream repository is called "aggressive-indent-mode", the author has
specified its ELPA package name as "aggressive-indent" so the Debian
package name is "elpa-aggressive-indent".

This is a very useful minor mode for writing LISP, especially when
rearranging forms with paredit or smartparens.  Since all relevant lines
are immediately reindented when you make a change, you can clearly make
sense of the structure of your code.

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

http://mentors.debian.net/package/elpa-aggressive-indent

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

  dget -x 
http://mentors.debian.net/debian/pool/main/e/elpa-aggressive-indent/elpa-aggressive-indent_1.4.2-1.dsc

Regards,

Sean Whitton


signature.asc
Description: Digital signature

Bug#633582: [PATCH] mkinitramfs: fix bashism in script

[Ben Hutchings]

Control: tag -1 pending

On Tue,  9 Dec 2014 07:56:51 +0600 Boris Egorov  wrote:
> Closes: #633582
> Signed-off-by: Boris Egorov 

Applied; sorry for the delay.

Ben.

> ---
>  mkinitramfs | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/mkinitramfs b/mkinitramfs
> index 5baa955..4552046 100755
> --- a/mkinitramfs
> +++ b/mkinitramfs
> @@ -343,7 +343,7 @@ fi
>  
>  (
>  # preserve permissions if root builds the image, see #633582
> -[ "$UID" != 0 ] && cpio_owner_root="-R 0:0"
> +[ "$(id -ru)" != 0 ] && cpio_owner_root="-R 0:0"
>  
>  # work around lack of "set -o pipefail" for the following pipe:
>  # cd "${DESTDIR}" && find . | cpio --quiet $cpio_owner_root -o -H newc | 
>gzip >>"${outfile}" || exit 1
> -- 
> 2.1.3
> 
> 
> 
-- 
Ben Hutchings
Life would be so much easier if we could look at the source code.

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

Bug#807433: icedove: Icedove crashes while fetching users system mails

[Martin Dosch]

Package: icedove
Version: 42.0~b2-1
Severity: normal

Dear Maintainer,

Icedove is configured to fetch local users email in /var/mail/user. It's
crashing while checking for mails.

Please finde a backtrace attached.

Best regards,
Martin



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

Kernel: Linux 4.2.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 icedove depends on:
ii  debianutils   4.5.1
ii  fontconfig2.11.0-6.3
ii  libasound21.0.29-1
ii  libatk1.0-0   2.18.0-1
ii  libc6 2.19-22
ii  libcairo2 1.14.4-1
ii  libdbus-1-3   1.10.4-1
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-2+b1
ii  libffi6   3.2.1-3
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.6.1-0.1
ii  libgcc1   1:5.2.1-23
ii  libgdk-pixbuf2.0-02.32.2-1
ii  libglib2.0-0  2.46.2-1
ii  libgtk2.0-0   2.24.28-1
ii  libhunspell-1.3-0 1.3.3-3+b2
ii  libicu55  55.1-6
ii  libnspr4  2:4.11-1
ii  libnss3   2:3.21-1
ii  libpango-1.0-01.38.1-1
ii  libpangocairo-1.0-0   1.38.1-1
ii  libpangoft2-1.0-0 1.38.1-1
ii  libpixman-1-0 0.33.4-1
ii  libsqlite3-0  3.9.2-1
ii  libstartup-notification0  0.12-4
ii  libstdc++65.2.1-23
ii  libvpx2   1.4.0-4
ii  libx11-6  2:1.6.3-1
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxrender1   1:0.9.9-2
ii  libxt61:1.1.5-1
ii  psmisc22.21-2.1+b1
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages icedove recommends:
ii  iceowl-extension42.0~b2-1
ii  myspell-de-de [myspell-dictionary]  20131206-6

Versions of packages icedove suggests:
ii  fonts-lyx 2.1.4-2
ii  libgssapi-krb5-2  1.13.2+dfsg-4

-- debconf-show failed
GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from icedove...Reading symbols from 
/usr/lib/debug//usr/lib/icedove/icedove...done.
done.
(gdb) run
Starting program: /usr/bin/icedove 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe60cd700 (LWP 9066)]
[Thread 0x7fffe60cd700 (LWP 9066) exited]
[New Thread 0x7fffe60cd700 (LWP 9068)]
[New Thread 0x7fffde8ef700 (LWP 9069)]
[New Thread 0x7fffde0ee700 (LWP 9070)]
[New Thread 0x7fffdd5ff700 (LWP 9071)]
[New Thread 0x7fffdd3fe700 (LWP 9072)]
[New Thread 0x7fffdd1fd700 (LWP 9073)]
[New Thread 0x7fffdcffc700 (LWP 9074)]
[New Thread 0x7fffdcdfb700 (LWP 9075)]
[New Thread 0x7fffdcbfa700 (LWP 9076)]
[New Thread 0x7fffdc9f9700 (LWP 9077)]
[New Thread 0x7fffdc7f8700 (LWP 9078)]
[New Thread 0x7fffdb4ff700 (LWP 9079)]
[New Thread 0x7fffda9ff700 (LWP 9080)]
[New Thread 0x7fffda1fe700 (LWP 9081)]
[New Thread 0x76d26700 (LWP 9082)]
[New Thread 0x7fffd94ff700 (LWP 9083)]
[New Thread 0x7fffd86ff700 (LWP 9084)]
[calBackendLoader] Using libical backend at 
/usr/lib/icedove/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/libical-manifest
[New Thread 0x7fffd71ff700 (LWP 9085)]
[New Thread 0x7fffd628f700 (LWP 9086)]
[New Thread 0x7fffd4eff700 (LWP 9087)]
[New Thread 0x7fffd46fe700 (LWP 9088)]
[New Thread 0x7fffd3efd700 (LWP 9089)]
[New Thread 0x7fffd36fc700 (LWP 9090)]
[New Thread 0x7fffd2efb700 (LWP 9091)]
[New Thread 0x7fffd26fa700 (LWP 9092)]
[New Thread 0x7fffd1ef9700 (LWP 9093)]
[New Thread 0x7fffd086d700 (LWP 9094)]
[New Thread 0x7fffd006c700 (LWP 9095)]
enigmail.js: Registered components
[New Thread 0x7fffcf1ff700 (LWP 9096)]
[New Thread 0x7fffce9fe700 (LWP 9097)]
[New Thread 0x7fffcdfff700 (LWP 9098)]
[New Thread 0x7fffcd7fe700 (LWP 9099)]
[New Thread 0x7fffccdff700 (LWP 9100)]
[Thread 0x7fffd86ff700 (L

Bug#807432: RFS: python-jellyfish/0.5.1-1 [ITP]

[Diego M. Rodriguez]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "python-jellyfish"

* Package name: python-jellyfish
  Version : 0.5.1-1
  Upstream Author : James Turk 
* URL : https://github.com/jamesturk/jellyfish
* License : BSD-2-clause
  Section : python

It builds those binary packages:

python-jellyfish - Library for approximate and phonetic matching of strings 
(Python 2)
python-jellyfish-doc - Library for approximate and phonetic matching of strings 
(documentation)
python3-jellyfish - Library for approximate and phonetic matching of strings 
(Python 3)

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

http://mentors.debian.net/package/python-jellyfish


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

dget -x 
http://mentors.debian.net/debian/pool/main/p/python-jellyfish/python-jellyfish_0.5.1-1.dsc

More information about python-jellyfish can be obtained from 
https://github.com/jamesturk/jellyfish.

Regards,
 Diego M. Rodriguez



signature.asc
Description: Digital signature

Bug#807040: general: System hangs and then restarts (kernel panic)

[Adam Borowski]

On Tue, Dec 08, 2015 at 08:11:56AM -0800, Nigra Truo wrote:
> I found some logs that show that nouveau is logging some insane amount of
> stuff, seems to be errors nonstop, in one instance it is more than a
> thousand lines of the very same error.
> I attached the logs.

I'm afraid I'm not someone who can help you, I'm merely an user who got the
same problem.  It does seem like a kernel driver rather than X driver
problem too.  I guess, it'd be best to send the report/logs to nouveau guys
upstream.

> One thing I wonder is how to deactivate nouveau for now, I can't work with
> my computer crashing every 5 minutes. Since reporting this bug, the machine
> crashed about 20 times already, I'm not kidding, this is not Debian Stable,
> far from it and it must stop, I need a workaround for this. Is there a way
> to disable hardware accelleration?

Setting the X driver to vesa maybe?  My solution is to use the proprietary
driver, it works fine for me.

I couldn't reboot with nouveau on new kernel before then got distracted,
I'll see if it fixes things.  But, my logs and your logs look totally
different so there's a big chance it's a different bug with same symptoms.

> A good question would be how to get a newer kernel on Debian Stable and get
> a newer version of nouveau too.

It will hit backports in a while, currently both jessie-backports and
unstable got 4.2.  The nouveau overhaul is in 4.3, which currently is only
in experimental.  As jessie is pretty recent, I believe the experimental
kernel can be installed without much trouble.

Or, you can compile your own kernel, please say so if you need help.


-- 
A tit a day keeps the vet away.

Bug#763874: pepperflashplugin-nonfree: Patch to make update-pepperflashplugin-nonfree work with apt 1.1

[pada]

Package: pepperflashplugin-nonfree
Version: 1.8.1+b1
Followup-For: Bug #763874

Dear Maintainer,

   * What led up to the situation?

I upgraded to apt 1.1.3.

Afterwards the following directory and file were not readable by the
_apt user when running update-pepperflashplugin-nonfree:

/tmp/pepperflashplugin-nonfree.XX
/tmp/pepperflashplugin-nonfree.XX/etc/apt/pubring.gpg

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

/usr/sbin/update-pepperflashplugin-nonfree --status

   * What was the outcome of this action?

ERROR: failed to retrieve status information from google : W: Can't drop 
privileges for downloading as file 
'./var/lib/apt/lists/partial/dl.google.com_linux_chrome_deb_dists_stable_InRelease'
 couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Keine Berechtigung)
More information might be available at:
  http://wiki.debian.org/PepperFlashPlayer

   * What outcome did you expect instead?

# /usr/local/sbin/update-pepperflashplugin-nonfree --status
Flash Player version installed on this system  : 19.0.0.245
Flash Player version available on upstream site: 19.0.0.245

   * Patch attached

Patch pepperflashplugin-nonfree-with-apt-1.1.diff fixes the problem.
--- update-pepperflashplugin-nonfree.orig	2014-10-22 08:26:45.0 +0200
+++ update-pepperflashplugin-nonfree	2015-12-08 20:58:04.0 +0100
@@ -114,6 +114,7 @@
 
 UNPACKDIR=`mktemp -d /tmp/pepperflashplugin-nonfree.XX` || die_hard "mktemp failed"
 echo "$UNPACKDIR" | grep -q "^/tmp/pepperflashplugin-nonfree\." || die_hard "paranoia"
+chmod 711 "$UNPACKDIR" || die_hard "chmod failed"
 cd "$UNPACKDIR" || die_hard "cd failed"
 
 [ "$verbose" != "yes" ] || echo "temporary directory: $UNPACKDIR"
@@ -170,6 +171,7 @@
 	EOF
 
 	gpg --quiet --no-permission-warning --homedir "etc/apt" --import /usr/lib/pepperflashplugin-nonfree/pubkey-google.txt
+  chmod 644 etc/apt/pubring.gpg
 
 	[ "$verbose" != "yes" ] || echo "doing apt-get update on google repository"
 	stdouterr=`APT_CONFIG=apt.conf apt-get --quiet --quiet update 2>&1`

Bug#792827: geoip-bin: geoip-generator-asn produces malformed database

[Victor Klos]

hi,

    sudo apt-get install geoip-database-contrib

fixed the error for me.

cheers,
Victor

Bug#807431: libchi-perl: t/Driver-Memory.t sometimes fails

[Niko Tyni]

Package: libchi-perl
Version: 0.60-3
Severity: normal
User: debian-p...@lists.debian.org
Usertags: autopkgtest
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=109993

The autopkgtest checks of this package recently failed on ci.debian.net.
While it works fine for me locally, the upstream ticket [rt.cpan.org #109993]
indicates the test has also occasionally failed for others on the CPAN
testers system.

Possibly those tests should be skipped/marked TODO for now to make
the test suite more robust.
 
  https://ci.debian.net/packages/libc/libchi-perl/unstable/amd64/

  # 40 is not between 59 and 99
  not ok 952 - Memory:l1_cache size = 40
  
  #   Failed test 'Memory:l1_cache size = 40'
  #   at /usr/share/perl5/CHI/t/Driver.pm line 1555.
  #   (in CHI::t::Driver::Memory->test_size_awareness_with_subcaches)
  # 2 is not between 3 and 5
  not ok 953 - Memory:l1_cache keys = 2
  
  #   Failed test 'Memory:l1_cache keys = 2'
  #   at /usr/share/perl5/CHI/t/Driver.pm line 1557.
  #   (in CHI::t::Driver::Memory->test_size_awareness_with_subcaches)
  
  [...]
  Test Summary Report
  ---
  t/Driver-Memory.t  (Wstat: 512 Tests: 963 Failed: 2)
Failed tests:  952-953
Non-zero exit status: 2

-- 
Niko Tyni   nt...@debian.org

Bug#807430: Firewalld depends on systemd

[Juliusz Chroboczek]

Package: firewalld
Version:  0.3.14.2-2
Severity: wishlist

Firewalld depends on systemd, which makes it unusable for those of us who
run SV init on their systems.  Would it be a lot of work to make firewalld
not depend on a specific init system?

Bug#640356: more notes on very old genmon patch

[Jay Berkenbilt]

I happened to notice that there's activity on fbpanel on github from
just a few days ago, so I took the opportunity to port my old patch to
the current version of fbpanel and create a pull request:
https://github.com/aanatoly/fbpanel/pull/19

This is basically identical to what I posted here.

When you replied to my bug report in November, 2011 (!), you asked for a
configuration example, which I never provided. There's one in the pull
request to upstream, but I'll repeat what I put there. The pull request
includes an image as well.

Given this configuration fragment:

Plugin {
type = genmon
config {
Command = get_qbiff_output
AllowPangoMarkup = 1
PollingTime = 1
MaxTextLength = 500
}
}

this text:

● A Q v /vsm ●

Generates

● A Q v /vsm ●

in a fixed-width font with the bullets and upper-case letters in red and
the lower-case letters in green.

I'm not sure whether upstream is actually going to release 7.0 or
whether it will include my patch. I just keep patching fbpanel and using
a patched version. I don't run a graphical desktop on that many systems,
so this is not a huge deal for me

-- 
Jay Berkenbilt 

Bug#806965: oclgrind: FTBFS on ppc64el -- conflict with altivec keyword bool

[Fernando Seiti Furusato]

Andreas Beckmann  wrote on 08/12/2015 17:09:58:

> From: Andreas Beckmann 
> To: J Price 
> Cc: Fernando Seiti Furusato/Brazil/IBM@IBMBR, 806...@bugs.debian.org, 
Breno 
> Henrique Leitao/Brazil/IBM@IBMBR
> Date: 08/12/2015 17:10
> Subject: Re: Bug#806965: oclgrind: FTBFS on ppc64el -- conflict with 
altivec 
> keyword bool
> 
> On 2015-12-08 20:00, J Price wrote:
> >> I don't really like the idea of manipulating unrelated defines in
> >> headers ...
> > 
> > OK, so how about if I do this from the .cpp files instead? e.g.
> 
> That would be fine, since it's limited to oclgrind. Doing it in a
> (public) header could "contaminate" other projects that include the
> header, also it may depend on the order of the includes whether
> compilation fails or succeeds.
> 

Just FYI.
Not sure if they are public headers or not, but doing so on headers:
src/runtime/icd.h
src/core/common.h

Made it build for me.

Right below #include "CL/cl.h" I included this:

#ifdef __ALTIVEC__
# undef bool
# undef vector
# undef pixel
#endif

I tried adding to the .cpp files (not all of them) but it didn't work.
The headers above are the ones that actually use cl.h.

Regards.

Fernando

Bug#119911: ITP: alephone - marathon engine for data games

[PICCORO McKAY Lenz]

2015-12-08 1:33 GMT-04:30 Alexandre Detiste :
> I don't think anyone else will come up with an alternative marathon engine 
> anyday.
Yes, that its!

> So please: one alephone source package that builds one alephone binary package
> that includes three .desktop files (for a starter, the extra levels can be 
> added later)
> and the launcher if needed.
alephone source and the resulting alephone package now has those:
* /usr/games/alephone (engine itselft)
* /usr/share/games/alephone/alephone-laucher (bash script to suymlink
on each scenario package)
and its respective manpages
BUT:
> GDP will not provide things like the one provided by src:quake, as there's
> no way to update these after the local GDP package has been manually built.
if that its, so source engine will also made 3 packges
(marathon/1/2/3) that ship those files and depends of the packages
provides by GDP?

this mean the alephone source must produce :
* marathon
* marathon2
* marathon3
these packages will handle desktop files, desktop icons, root debian
menu entries and laucher symlink

and as seem you point, will depends of the data packages produced by GDP right?

please confirme for made the proper changes and send to you the dsc
files with all need!