Bug#829653: Info received (Bug#829653: Acknowledgement (RFS: caffe-contrib/1.0.0~rc3-1 -- cuda version of caffe [ITP]))

[Lumin]

http://debomatic-amd64.debian.net/distribution#experimental/caffe-contrib/1.0.0~rc3-1/buildlog

The lastest mentors package is fixed.
Please sponsor, thanks :-)

On 5 July 2016 at 03:30, Debian Bug Tracking System 
wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian Mentors 
>
> If you wish to submit further information on this problem, please
> send it to 829...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 829653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829653
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>



-- 
Best,
Lumin

Bug#810219: confirmation

[Vincent McIntyre]

We also hit this with Dell Optiplex 7040 desktops

% cat /etc/debian_version
8.5
% uname -v
#1 SMP Debian 3.16.7-ckt25-2+deb8u2 (2016-06-25)

% lspci
00:00.0 Host bridge: Intel Corporation Device 191f (rev 07)
00:01.0 PCI bridge: Intel Corporation Device 1901 (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Device 1912 (rev 06)
00:14.0 USB controller: Intel Corporation Device a12f (rev 31)
00:14.2 Signal processing controller: Intel Corporation Device a131 (rev 31)
00:16.0 Communication controller: Intel Corporation Device a13a (rev 31)
00:16.3 Serial controller: Intel Corporation Device a13d (rev 31)
00:17.0 SATA controller: Intel Corporation Device a102 (rev 31)
00:1c.0 PCI bridge: Intel Corporation Device a110 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Device a146 (rev 31)
00:1f.2 Memory controller: Intel Corporation Device a121 (rev 31)
00:1f.3 Audio device: Intel Corporation Device a170 (rev 31)
00:1f.4 SMBus: Intel Corporation Device a123 (rev 31)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-LM 
(rev 31)
01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 745] 
(rev a2)
01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
02:00.0 PCI bridge: Texas Instruments XIO2001 PCI Express-to-PCI Bridge

# lspci -n -s 00:1f.3
00:1f.3 0403: 8086:a170 (rev 31)

# lspci -vvv -s 00:1f.3
00:1f.3 Audio device: Intel Corporation Device a170 (rev 31)
Subsystem: Dell Device 06b9
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

Bug#827948: Debian Testing Cannot be installed on Hyper-V 2012 R2

[Cyril Brulebois]

Hi Larry,

Larry Sevilla  (2016-07-05):
> Tried again with the new image, but still failed.
> 
> Attached screenshot.

Thanks for following up. This seems like something that should be
reported against the linux kernel.


KiBi.


signature.asc
Description: Digital signature

Bug#829403: tlp: screen flickers every 2-10 seconds

[Thomas Koch]

Hi,

the T560 doesn't contain radeon graphics, so there's no point in trying
RADEON* settings.

The flickering occurs on battery power only? Then try to disable ALPM [1]:

>  SATA_LINKPWR_ON_BAT=max_performance

Please provide the full output of (as root)

> tlp-stat

[1] http://linrunner.de/en/tlp/docs/tlp-configuration.html#alpm

Regards

-- 
Thomas Koch

Bug#819546: vsftpd no longer starts with systemd because of listen_ipv6=NO from Bug: #803999

[Jeremy Bicha]

Control: severity -1 grave

Since the maintainer has orphaned this package [1] and therefore this
package is maintained by Debian in general, I'm resetting the bug
severity since I agree with the reporter that this is a RC issue.

Thanks,
Jeremy Bicha

Bug#802561: dep3_headers: Pre-fill 'Last-Update'.

[Daniel Shahaf]

Daniel Shahaf wrote on Wed, Oct 21, 2015 at 03:29:24 +:
> -+Last-Update: <-MM-DD, last update of the meta-information, 
> optional>
> ++Last-Update: $(LC_ALL=C date +%Y-%m-%d) <-MM-DD, last 
> update of the meta-information, optional>

An analogous change was just made to 'dpkg-source --commit' (in #828146).

Bug#829658: RFS: caffe/1.0.0~rc3-3

[Lumin]

Package: sponsorship-requests
Severity: normal
​X-Debbugs-CC: costamagnagianfra...@yahoo.it


Dear mentors,

 Debomatic-amd64 build success[1]. As for 32-bit architecture
 FTBFS issue of caffe, I'd cherry-pick upstream fix at next
 time upload, synchronizing caffe and caffe-contrib packaging.

 [1]
​​
http://debomatic-amd64.debian.net/distribution#experimental/caffe/1.0.0~rc3-3/buildlog

  I am looking for a sponsor for my package "caffe"

 * Package name: caffe
   Version : 1.0.0~rc3-3
   Upstream Author : BVLC
 * URL : github.com/bvlc/caffe
 * License : BSD-2-clause
   Section : science

  It builds those binary packages:

caffe-cpu  - Fast, open framework for Deep Learning (Meta)
 caffe-doc  - Doxygen Document of Caffe
 caffe-tools-cpu - Tools for fast, open framework for Deep Learning
(CPU_ONLY)
 libcaffe-cpu-dev - development files for Caffe (CPU_ONLY)
 libcaffe-cpu1 - library of Caffe, deep learning framework (CPU_ONLY)
 python3-caffe-cpu - Python3 interface of Caffe (CPU_ONLY)

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

  https://mentors.debian.net/package/caffe


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

dget -x
https://mentors.debian.net/debian/pool/main/c/caffe/caffe_1.0.0~rc3-3.dsc


  Changes since the last upload:

caffe (1.0.0~rc3-3) experimental; urgency=medium

  * Remove octave related packages and corresponding builds, because
upstream support for octave is limited.
  * Fix typo in package descriptions, update descriptions.
  * Update rules.
  * Add symbols control file for libcaffe.so .
  * Update README.Debian .

-- 
Best,
Lumin

Bug#829657: python-bioblend-doc: Typo in dependency

[Jeremy Bicha]

Package: python-bioblend-doc
Version: 0.7.0-1
Severity: serious

python-bioblend-doc should depend on
-libjs-query
+libjs-jquery

Currently, python-bioblend-doc is uninstallable.

Also, please point both your Vcs-Git and Vcs-Browser to:
https://anonscm.debian.org/git/python-modules/packages/python-bioblend.git

(The lintian tag vcs-field-uses-insecure-uri recommends using https://
instead of git:// )

Thanks,
Jeremy Bicha

Bug#829656: mkdocs: Missing dependencies

[Jeremy Bicha]

Package: mkdocs
Version: 0.15.3-3
Severity: serious
Justification: not binNMU safe

When python-mkdocs is built in a clean chroot (like on Ubuntu or in
Debian's reproducible builds), it is missing some dependencies
(mkdocs-bootstrap and mkdocs-bootswatch) that were somehow present in
the package that was uploaded to Debian.

https://launchpad.net/ubuntu/+source/python-mkdocs/0.15.3-3/+build/9729927

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/python-mkdocs_0.15.3-3.rbuild.log

https://packages.debian.org/unstable/mkdocs

The logs have these warnings:
I: dh_python3 pydist:184: Cannot find package that provides
mkdocs_bootstrap. Please add package that provides it to Build-Depends
or add "mkdocs_bootstrap python3-mkdocs-bootstrap" line to
debian/py3dist-overrides or add proper  dependency to Depends by hand
and ignore this info.
I: dh_python3 pydist:184: Cannot find package that provides
mkdocs_bootswatch. Please add package that provides it to
Build-Depends or add "mkdocs_bootswatch python3-mkdocs-bootswatch"
line to debian/py3dist-overrides or add proper  dependency to Depends
by hand and ignore this info.

Please add the appropriate lines to debian/py3dist-overrides.

And please consider switching to source-only uploads:

https://wiki.debian.org/SourceOnlyUpload

Thanks,
Jeremy Bicha

Bug#829655: ITP: python-openid-teams -- OpenID teams extension for python-openid

[Sergio Durigan Junior]

Package: wnpp
Severity: wishlist
Owner: Sergio Durigan Junior 

* Package name: python-openid-teams
  Version : 1.1
  Upstream Author : Patrick Uiterwijk 
* URL : https://github.com/puiterwijk/python-openid-teams
* License : BSD-3-clause
  Programming Lang: Python
  Description : OpenID teams extension for python-openid

 Implementation of the OpenID teams extension for python-openid.

This package is a dependency necessary for pagure.

Thanks,

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


signature.asc
Description: PGP signature

Bug#829654: src:fcgiwrap: Co-maintaining fcgiwrap

[Peter Colberg]

Package: src:fcgiwrap
Severity: wishlist

Hi Jordi,

I have been using fcgiwrap together with nginx for many years, mostly
to run the cgit git browser. Would you be interested in co-maintaining
fcgiwrap (or, iff you are no longer interested, passing on maintenance)?

I recently became DM [1] and would need upload rights sponsorship.
For an example of prior work, please see the cgit package [2, 3].

[1] https://qa.debian.org/developer.php?login=peter%40colberg.org
[2] https://bugs.debian.org/826764
[3] https://anonscm.debian.org/git/pkg-cgit/pkg-cgit.git

If you are interested, I would begin by creating a collab-maint git
repository from the svn history, and then fix all outstanding bugs.

Regards,
Peter


signature.asc
Description: PGP signature

Bug#829653: Acknowledgement (RFS: caffe-contrib/1.0.0~rc3-1 -- cuda version of caffe [ITP])

[Lumin]

Well it seems that the first time mentors upload is going to FTBFS[1].
Hold on and I'll make an fixed upload.

the fix is to add flag -D_FORCE_INLINES to nvcc.

​[1] dom-amd64: CUDA memcpy problem​


-- 
Best,
Lumin

Bug#829054: Needs IPv6 support

[Elliott Mitchell]

Upon a bit more playing with things, I needed to include a tiny bit of
additional patching.  This includes a fix on line 69 of ipme.c, simply
another tiny spot where "ix.ip" needed to be "is.addr.ip".

This also needs #741153 to fully take care of this IPv6 issue.


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445


Qmail IPv6 patch
	Kazunori Fujiwara 
	originally 1997,1998
	2002 Oct. 6.

This patch enables qmail to receive and send mail via IPv6 network.

This patch was not guaranteed.
The fault by having applied this patch belongs to one which applied the patch.

apply this patch and defines some macros on conf-cc.
INET6   (default)	enables IPv6 transport
TCPTO_REFUSED		when enabled, tcpto denial cache caches
			connection refused hosts.
			(normaly, timeout only)

patch needed part:

DNS Resolving:
	o resolve  with A
	o IPv6 address reverse resolve.
	o resolve MX's  and A

Receiving:
	tcp_env resolves IPv6 and IPv4 socket address to environ.

Sending:
	A and  are also resolved.
	IPv4 address and an IPv6 address are treated similarly.
	tcpto denial cache caches IPv4 and IPv6 addresses.


You need IPv6'ed inetd and tcp wrappers.

You want to use IPv6 only life, You need OSs which have IPv6 resolver
like *BSD.


-
Changes:
	I found my old patch's tcpto bug on 2002 Oct. 6.
	Older patch's tcpto is not work.
	without dinial cache, sending mails works.
	but some useless connects increase.


Please inform me something wrong with this patch and this text.



diff -ub qmail-1.03/conf-cc qmail-1.03+v6/conf-cc
--- qmail-1.03/conf-cc	Mon Jun 15 19:53:16 1998
+++ qmail-1.03+v6/conf-cc	Mon Oct  7 01:05:47 2002
@@ -1,3 +1,5 @@
+cc -O2 -DINET6
 cc -O2
+cc -O2 -DINET6 -DTCPTO_REFUSED
 
 This will be used to compile .c files.
diff -ub qmail-1.03/dns.c qmail-1.03+v6/dns.c
--- qmail-1.03/dns.c	Mon Jun 15 19:53:16 1998
+++ qmail-1.03+v6/dns.c	Sun Oct  6 15:52:29 2002
@@ -3,6 +3,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 extern int res_query();
@@ -27,6 +28,9 @@
 static int numanswers;
 static char name[MAXDNAME];
 static struct ip_address ip;
+#ifdef INET6
+static struct ip6_address ip6;
+#endif
 unsigned short pref;
 
 static stralloc glue = {0};
@@ -140,6 +144,43 @@
  return 0;
 }
 
+#ifdef INET6
+static int findip6(wanttype)
+int wanttype;
+{
+ unsigned short rrtype;
+ unsigned short rrdlen;
+ int i;
+
+ if (numanswers <= 0) return 2;
+ --numanswers;
+ if (responsepos == responseend) return DNS_SOFT;
+
+ i = dn_expand(response.buf,responseend,responsepos,name,MAXDNAME);
+ if (i < 0) return DNS_SOFT;
+ responsepos += i;
+
+ i = responseend - responsepos;
+ if (i < 4 + 3 * 2) return DNS_SOFT;
+   
+ rrtype = getshort(responsepos);
+ rrdlen = getshort(responsepos + 8);
+ responsepos += 10;
+
+ if (rrtype == wanttype)
+  {
+   if (rrdlen < 16)
+ return DNS_SOFT;
+   bcopy([0], , 16);
+   responsepos += rrdlen;
+   return 1;
+  }
+   
+ responsepos += rrdlen;
+ return 0;
+}
+#endif
+
 static int findmx(wanttype)
 int wanttype;
 {
@@ -261,6 +302,57 @@
  return DNS_HARD;
 }
 
+#ifdef INET6
+static int iaafmt6(s,ip)
+char *s;
+struct ip6_address *ip;
+{
+ unsigned int i;
+ int j;
+ unsigned int len;
+ static char data[] = "0123456789abcdef";
+ len = 0;
+
+ if (s) {
+   for (j = 15; j >= 0; j--) {
+ *s++ = data[ip->d[j] & 0x0f];
+ *s++ = '.';
+ *s++ = data[(ip->d[j] >> 4) & 0x0f];
+ *s++ = '.';
+   }
+   strcpy(s, "ip6.int");
+ }
+ return 71;
+ /* 1.2.3.4.5.6.7.8.9.a.b.c.d.e.f.1.2.3.4.5.6.7.8.9.a.b.c.d.e.f.ip6.int */
+}
+
+int dns_ptr6(sa,ip)
+stralloc *sa;
+struct ip6_address *ip;
+{
+ int r;
+
+ if (!stralloc_ready(sa,iaafmt6((char *) 0,ip))) return DNS_MEM;
+ sa->len = iaafmt6(sa->s,ip);
+ switch(resolve(sa,T_PTR)) 
+  {
+   case DNS_MEM: return DNS_MEM;
+   case DNS_SOFT: return DNS_SOFT;
+   case DNS_HARD: return DNS_HARD;
+  }
+ while ((r = findname(T_PTR)) != 2)
+  {
+   if (r == DNS_SOFT) return DNS_SOFT;
+   if (r == 1)
+{
+ if (!stralloc_copys(sa,name)) return DNS_MEM;
+ return 0;
+}
+  }
+ return DNS_HARD;
+}
+#endif
+
 static int dns_ipplus(ia,sa,pref)
 ipalloc *ia;
 stralloc *sa;
@@ -268,33 +360,66 @@
 {
  int r;
  struct ip_mx ix;
+ int err4 = 0, err6 = 0;
 
  if (!stralloc_copy(,sa)) return DNS_MEM;
  if (!stralloc_0()) return DNS_MEM;
  if (glue.s[0]) {
ix.pref = 0;
-   if (!glue.s[ip_scan(glue.s,)] || !glue.s[ip_scanbracket(glue.s,)])
+   ix.af = AF_INET;
+   if (!glue.s[ip_scan(glue.s,)] || !glue.s[ip_scanbracket(glue.s,)])
 {
  if (!ipalloc_append(ia,)) return DNS_MEM;
  return 0;
 }
  }
 
- switch(resolve(sa,T_A))
+#ifdef INET6
+ switch(resolve(sa,T_))
   {
-   case DNS_MEM: return DNS_MEM;
-   case DNS_SOFT: return DNS_SOFT;
-   case DNS_HARD: 

Bug#829653: RFS: caffe-contrib/1.0.0~rc3-1 -- cuda version of caffe [ITP]

[Lumin]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: costamagnagianfra...@yahoo.it
​, ghisv...@gmail.com​


Dear mentors,

​  This cuda version is basically synced with the CPU version in
  packaging.​


  I am looking for a sponsor for my package "caffe-contrib"

 * Package name: caffe-contrib
   Version : 1.0.0~rc3-1
   Upstream Author : Berkeley vision and learning center
 * URL : github.com/bvlc/caffe
 * License : BSD-2-Clause
   Section : science

  It builds those binary packages:

caffe-cuda - Fast, open framework for Deep Learning (Meta)
 caffe-tools-cuda - Tools for fast, open framework for Deep Learning (CUDA)
 libcaffe-cuda-dev - development files for Caffe (CUDA)
 libcaffe-cuda1 - library of Caffe, a deep leanring framework (CUDA)
 python3-caffe-cuda - Python3 interface of Caffe (CUDA)

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

  https://mentors.debian.net/package/caffe-contrib


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

dget -x
https://mentors.debian.net/debian/pool/contrib/c/caffe-contrib/caffe-contrib_1.0.0~rc3-1.dsc


  Changes since the last upload:

caffe-contrib (1.0.0~rc3-1) experimental; urgency=low

  * Initial release. (Closes: #823308)


-- 
Best,
Lumin

Bug#829652: qmail-uids-gids: shell setting of qmail users dangerous

[Elliott Mitchell]

Package: qmail-uids-gids
Version: 1.06-5
Severity: important

The shell used for the qmail-uids-gids users is bad, even dangerous.  The
qmail documentation explicitly stated those users should have a shell of
/bin/false.  In the modern era /usr/sbin/nologin might be substituted.

Problem is, the way the qmail-uids-gids was written, the qmail users will
have a shell of /bin/bash, and the error message will suggest a shell of
/bin/sh.

This is VERY bad.  The attached patch fixes this for new installations,
but won't fix the issue for existing installations.  The original script
doesn't really do much for installations that were older either.

This URGENTLY needs to be fixed!


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445


--- netqmail-1.06.orig/debian/qmail-uids-gids.postinst	2016-07-04 19:47:23.0 -0700
+++ netqmail-1.06/debian/qmail-uids-gids.postinst	2016-07-04 19:52:15.44000 -0700
@@ -45,13 +45,13 @@
 
   $DEBUG groupadd -g 64010 qmail || return 1
   $DEBUG addgroup --system nofiles || return 1
-  $DEBUG useradd -u 64010 -g nofiles -d /var/lib/qmail/alias alias || return 1
-  $DEBUG useradd -u 64011 -g nofiles -d /var/lib/qmail qmaild || return 1
-  $DEBUG useradd -u 64015 -g nofiles -d /var/lib/qmail qmaill || return 1
-  $DEBUG useradd -u 64016 -g nofiles -d /var/lib/qmail qmailp || return 1
-  $DEBUG useradd -u 64014 -g qmail -d /var/lib/qmail qmailq || return 1
-  $DEBUG useradd -u 64013 -g qmail -d /var/lib/qmail qmailr || return 1
-  $DEBUG useradd -u 64012 -g qmail -d /var/lib/qmail qmails || return 1
+  $DEBUG useradd -u 64010 -s /bin/false -g nofiles -d /var/lib/qmail/alias alias || return 1
+  $DEBUG useradd -u 64011 -s /bin/false -g nofiles -d /var/lib/qmail qmaild || return 1
+  $DEBUG useradd -u 64015 -s /bin/false -g nofiles -d /var/lib/qmail qmaill || return 1
+  $DEBUG useradd -u 64016 -s /bin/false -g nofiles -d /var/lib/qmail qmailp || return 1
+  $DEBUG useradd -u 64014 -s /bin/false -g qmail -d /var/lib/qmail qmailq || return 1
+  $DEBUG useradd -u 64013 -s /bin/false -g qmail -d /var/lib/qmail qmailr || return 1
+  $DEBUG useradd -u 64012 -s /bin/false -g qmail -d /var/lib/qmail qmails || return 1
   # done
   return 0
 }
@@ -83,13 +83,13 @@
 exist yet, this package will add them automatically.
 
 /etc/passwd:
-alias:x:64010:X:qmail alias:/var/lib/qmail/alias:/bin/sh
-qmaild:x:64011:X:qmail daemon:/var/lib/qmail:/bin/sh
-qmails:x:64012:64010:qmail send:/var/lib/qmail:/bin/sh
-qmailr:x:64013:64010:qmail remote:/var/lib/qmail:/bin/sh
-qmailq:x:64014:64010:qmail queue:/var/lib/qmail:/bin/sh
-qmaill:x:64015:X:qmail log:/var/lib/qmail:/bin/sh
-qmailp:x:64016:X:qmail pw:/var/lib/qmail:/bin/sh
+alias:x:64010:X:qmail alias:/var/lib/qmail/alias:/bin/false
+qmaild:x:64011:X:qmail daemon:/var/lib/qmail:/bin/false
+qmails:x:64012:64010:qmail send:/var/lib/qmail:/bin/false
+qmailr:x:64013:64010:qmail remote:/var/lib/qmail:/bin/false
+qmailq:x:64014:64010:qmail queue:/var/lib/qmail:/bin/false
+qmaill:x:64015:X:qmail log:/var/lib/qmail:/bin/false
+qmailp:x:64016:X:qmail pw:/var/lib/qmail:/bin/false
 /etc/group:
 qmail:x:64010:
 nofiles:x:X:

Bug#811831: projectm: FTBFS with GCC 6: no match for

[Matt Beary]

an upstream patch is available which addresses GCC-6 compatibility:

https://sourceforge.net/p/projectm/code/ci/92226e25192a69839b9ae3b66ea7173732c639b3/

Bug#829651: libapt-pkg5.0: segfault at 30 ip … sp … error 4 in libapt-pkg.so.5.0.0

[Axel Beckert]

Package: libapt-pkg5.0
Version: 1.2.14

Hi,

by accident I found these two lines in dmesg just now:

[3880700.754578] apt-get[29062]: segfault at 30 ip 7fd1a0b76181 sp 
7fff604076c0 error 4 in libapt-pkg.so.5.0.0[7fd1a0aac000+16e000]
[3880731.329977] apt-get[29438]: segfault at 30 ip 7fbc3d48e181 sp 
7ffe360517a0 error 4 in libapt-pkg.so.5.0.0[7fbc3d3c4000+16e000]

Luckily I have corekeeper installed, so I can provide you with
backtraces:

Core was generated by `apt-get indextargets --format $(CREATED_BY) 
$(ARCHITECTURE) $(SUITE) $(FILENAME'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  pkgCache::RlsFileBegin (this=0x0) at ../build/include/apt-pkg/pkgcache.h:799
799 ../build/include/apt-pkg/pkgcache.h: No such file or directory.
(gdb) bt
#0  pkgCache::RlsFileBegin (this=0x0) at ../build/include/apt-pkg/pkgcache.h:799
#1  debReleaseIndex::FindInCache (this=, Cache=..., 
ModifyCheck=)
at /build/apt-wHz6zS/apt-1.2.14/apt-pkg/deb/debmetaindex.cc:778
#2  0x55dc500b6738 in DoIndexTargets (CmdL=...) at 
/build/apt-wHz6zS/apt-1.2.14/cmdline/apt-get.cc:266
#3  0x7fd1a0b46be6 in CommandLine::DispatchArg (this=0x7fff60407da0, 
Map=, NoMatch=NoMatch@entry=true)
at /build/apt-wHz6zS/apt-1.2.14/apt-pkg/contrib/cmndline.cc:369
#4  0x7fd1a086f263 in DispatchCommandLine (CmdL=..., Cmds=...) at 
/build/apt-wHz6zS/apt-1.2.14/apt-private/private-cmndline.cc:511
#5  0x55dc500b3b19 in main (argc=, argv=0x7fff60407ee8) at 
/build/apt-wHz6zS/apt-1.2.14/cmdline/apt-get.cc:446

Core was generated by `apt-get indextargets --format $(CREATED_BY) 
$(ARCHITECTURE) $(SUITE) $(FILENAME'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  pkgCache::RlsFileBegin (this=0x0) at ../build/include/apt-pkg/pkgcache.h:799
799 ../build/include/apt-pkg/pkgcache.h: No such file or directory.
(gdb) bt
#0  pkgCache::RlsFileBegin (this=0x0) at ../build/include/apt-pkg/pkgcache.h:799
#1  debReleaseIndex::FindInCache (this=, Cache=..., 
ModifyCheck=)
at /build/apt-wHz6zS/apt-1.2.14/apt-pkg/deb/debmetaindex.cc:778
#2  0x558abcfa1738 in DoIndexTargets (CmdL=...) at 
/build/apt-wHz6zS/apt-1.2.14/cmdline/apt-get.cc:266
#3  0x7fbc3d45ebe6 in CommandLine::DispatchArg (this=0x7ffe36051e80, 
Map=, NoMatch=NoMatch@entry=true)
at /build/apt-wHz6zS/apt-1.2.14/apt-pkg/contrib/cmndline.cc:369
#4  0x7fbc3d187263 in DispatchCommandLine (CmdL=..., Cmds=...) at 
/build/apt-wHz6zS/apt-1.2.14/apt-private/private-cmndline.cc:511
#5  0x558abcf9eb19 in main (argc=, argv=0x7ffe36051fc8) at 
/build/apt-wHz6zS/apt-1.2.14/cmdline/apt-get.cc:446

Looks like twice the same issue.

Not sure what called these commands (maybe it was apprec from the
package apprecommender) as they were run under my personal user id
(1000), but I've not run them on purpose. (And if I do so, they do not
crash. And if I run apprec again, I get no new segfault or core dump. So
maybe it was something else.)

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 
'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libapt-pkg5.0 depends on:
ii  libbz2-1.0  1.0.6-8
ii  libc6   2.23-1
ii  libgcc1 1:6.1.1-8
ii  liblz4-10.0~r131-2
ii  liblzma55.1.1alpha+20120614-2.1
ii  libstdc++6  6.1.1-8
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages libapt-pkg5.0 recommends:
ii  apt  1.2.14

libapt-pkg5.0 suggests no packages.

-- no debconf information

Bug#829055: Dependancy on procmail needs adjustment

[Elliott Mitchell]

Control: tags 829055 + patch

A patch should be attached.  Since it is effects the same line #741153
does, this also fixes that in a way I suspect Gerrit Pape would have
prefered.


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445


--- qmail-run-2.0.2+nmu1/debian/control.orig	2016-07-04 18:09:06.42400 -0700
+++ qmail-run-2.0.2+nmu1/debian/control	2016-07-04 18:08:19.84800 -0700
@@ -6,7 +6,7 @@
 
 Package: qmail-run
 Architecture: all
-Depends: qmail (>= 1.06-2.1), fastforward (>= 1:0.51-3), daemontools (>> 1:0.76), ucspi-tcp (>> 1:0.88), runit (>> 1.8.0-2) | daemontools-run (>> 1:0.76), procmail
+Depends: qmail (>= 1.06-2.1), fastforward (>= 1:0.51-3), daemontools (>> 1:0.76), ucspi-tcp (>> 1:0.88) | ucspi-tcp-ipv6 (>> 1:0.88), runit (>> 1.8.0-2) | daemontools-run (>> 1:0.76), procmail | mailutils
 Suggests: dot-forward, mail-reader
 Conflicts: mail-transport-agent, lsb-core
 Replaces: mail-transport-agent, fastforward (<= 0.51-zarge1)

Bug#829650: jessie-pu: package ruby-eventmachine/1.0.3-6+deb8u1

[Balint Reczey]

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

Dear Release Team,

The Security Team suggested fixing the TEMP-0678512-2E167C [1] security
issue through a point release.

The issue is a remotely triggerable crash due to stack overflow.

Please see the debdiff attached.

The fix for Wheezy which is very similar was discussed [2] on the Wheezy
LTS list.

Cheers,
Balint

[1] https://security-tracker.debian.org/tracker/TEMP-0678512-2E167C
[2] https://lists.debian.org/debian-lts/2016/06/msg00141.html
diff -Nru ruby-eventmachine-1.0.3/debian/changelog ruby-eventmachine-1.0.3/debian/changelog
--- ruby-eventmachine-1.0.3/debian/changelog	2014-04-07 00:34:46.0 +0200
+++ ruby-eventmachine-1.0.3/debian/changelog	2016-07-04 22:00:03.0 +0200
@@ -1,3 +1,12 @@
+ruby-eventmachine (1.0.3-6+deb8u1) stable; urgency=medium
+
+  * Team upload
+  * Fix remotely triggerable crash due to FD handling
+(Closes: #678512, #696015)
+  * Fix memory leak caused when fixing crash
+
+ -- Balint Reczey   Mon, 04 Jul 2016 21:48:06 +0200
+
 ruby-eventmachine (1.0.3-6) unstable; urgency=low
 
   * Bump gem2deb build dependency to 0.7.5~
diff -Nru ruby-eventmachine-1.0.3/debian/patches/0001-use-ruby-select-api-with-expandable-fd-sets.patch ruby-eventmachine-1.0.3/debian/patches/0001-use-ruby-select-api-with-expandable-fd-sets.patch
--- ruby-eventmachine-1.0.3/debian/patches/0001-use-ruby-select-api-with-expandable-fd-sets.patch	1970-01-01 01:00:00.0 +0100
+++ ruby-eventmachine-1.0.3/debian/patches/0001-use-ruby-select-api-with-expandable-fd-sets.patch	2016-07-04 22:00:03.0 +0200
@@ -0,0 +1,217 @@
+From eab3baaba75c8c9e549aea54d3b356ab287a57b0 Mon Sep 17 00:00:00 2001
+From: Patrick Reynolds 
+Date: Tue, 11 Mar 2014 16:01:25 -0500
+Subject: [PATCH 1/3] use ruby select api with expandable fd sets
+
+Conflicts:
+	ext/em.h
+---
+ ext/em.cpp | 54 +-
+ ext/em.h   | 10 +-
+ tests/test_many_fds.rb | 22 
+ 3 files changed, 54 insertions(+), 32 deletions(-)
+ create mode 100644 tests/test_many_fds.rb
+
+diff --git a/ext/em.cpp b/ext/em.cpp
+index 670da31..6a3a2ef 100644
+--- a/ext/em.cpp
 b/ext/em.cpp
+@@ -524,12 +524,12 @@ void EventMachine_t::_RunEpollOnce()
+ 	#ifdef HAVE_RB_WAIT_FOR_SINGLE_FD
+ 	if ((ret = rb_wait_for_single_fd(epfd, RB_WAITFD_IN|RB_WAITFD_PRI, )) < 1) {
+ 	#else
+-	fd_set fdreads;
++	rb_fdset_t fdreads;
+ 
+-	FD_ZERO();
+-	FD_SET(epfd, );
++	rb_fd_init();
++	rb_fd_set(epfd, );
+ 
+-	if ((ret = rb_thread_select(epfd + 1, , NULL, NULL, )) < 1) {
++	if ((ret = rb_thread_fd_select(epfd + 1, , NULL, NULL, )) < 1) {
+ 	#endif
+ 		if (ret == -1) {
+ 			assert(errno != EINVAL);
+@@ -601,12 +601,12 @@ void EventMachine_t::_RunKqueueOnce()
+ 	#ifdef HAVE_RB_WAIT_FOR_SINGLE_FD
+ 	if ((ret = rb_wait_for_single_fd(kqfd, RB_WAITFD_IN|RB_WAITFD_PRI, )) < 1) {
+ 	#else
+-	fd_set fdreads;
++	rb_fdset_t fdreads;
+ 
+-	FD_ZERO();
+-	FD_SET(kqfd, );
++	rb_fd_init();
++	rb_fd_set(kqfd, );
+ 
+-	if ((ret = rb_thread_select(kqfd + 1, , NULL, NULL, )) < 1) {
++	if ((ret = rb_thread_fd_select(kqfd + 1, , NULL, NULL, )) < 1) {
+ 	#endif
+ 		if (ret == -1) {
+ 			assert(errno != EINVAL);
+@@ -792,9 +792,9 @@ SelectData_t::SelectData_t
+ SelectData_t::SelectData_t()
+ {
+ 	maxsocket = 0;
+-	FD_ZERO ();
+-	FD_ZERO ();
+-	FD_ZERO ();
++	rb_fd_init ();
++	rb_fd_init ();
++	rb_fd_init ();
+ }
+ 
+ 
+@@ -807,7 +807,7 @@ _SelectDataSelect
+ static VALUE _SelectDataSelect (void *v)
+ {
+ 	SelectData_t *sd = (SelectData_t*)v;
+-	sd->nSockets = select (sd->maxsocket+1, &(sd->fdreads), &(sd->fdwrites), &(sd->fderrors), &(sd->tv));
++	sd->nSockets = rb_fd_select (sd->maxsocket+1, &(sd->fdreads), &(sd->fdwrites), &(sd->fderrors), &(sd->tv));
+ 	return Qnil;
+ }
+ #endif
+@@ -848,9 +848,9 @@ void EventMachine_t::_RunSelectOnce()
+ 
+ 	SelectData_t SelectData;
+ 	/*
+-	fd_set fdreads, fdwrites;
+-	FD_ZERO ();
+-	FD_ZERO ();
++	rb_fdset_t fdreads, fdwrites;
++	rb_fd_init ();
++	rb_fd_init ();
+ 
+ 	int maxsocket = 0;
+ 	*/
+@@ -860,7 +860,7 @@ void EventMachine_t::_RunSelectOnce()
+ 	// running on localhost with a randomly-chosen port. (*Puke*)
+ 	// Windows has a version of the Unix pipe() library function, but it doesn't
+ 	// give you back descriptors that are selectable.
+-	FD_SET (LoopBreakerReader, &(SelectData.fdreads));
++	rb_fd_set (LoopBreakerReader, &(SelectData.fdreads));
+ 	if (SelectData.maxsocket < LoopBreakerReader)
+ 		SelectData.maxsocket = LoopBreakerReader;
+ 
+@@ -875,15 +875,15 @@ void EventMachine_t::_RunSelectOnce()
+ 		assert (sd != INVALID_SOCKET);
+ 
+ 		if (ed->SelectForRead())
+-			FD_SET (sd, &(SelectData.fdreads));
++			rb_fd_set (sd, &(SelectData.fdreads));
+ 		if (ed->SelectForWrite())
+-			FD_SET (sd, &(SelectData.fdwrites));
++			rb_fd_set (sd, &(SelectData.fdwrites));
+ 
+ 		

Bug#829649: lintian: Spurious error: init.d-script-missing-dependency-on-remote_fs

[Roberto C. Sanchez]

Package: lintian
Version: 2.5.45
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

In preparing a new upstream release of the shorewall-init package, I
found that lintian gave the following errors:

E: shorewall-init: init.d-script-missing-dependency-on-remote_fs 
etc/init.d/shorewall-init: required-start
E: shorewall-init: init.d-script-missing-dependency-on-remote_fs 
etc/init.d/shorewall-init: required-stop

I checked with upstream was informed that shorewall-init doesn't work
with NFS mount /usr and so assumes /usr is accessible without the need
for $remote_fs in Required-Start and Required-Stop.  I inquired in
#debian-devel on OFTC about this to see if it was OK to override.  I was
told that this error is spurious as initramfs now mounts /usr and was
suggested to file a bug report against lintian.

Please let me know if I can provide any additional information to help
resolve this.

Regards,

- -Roberto

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

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


-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXexsIAAoJECzXeF7dp7IP1ncP/iLrjg9C57918NMRL0gLauN9
wdgqLgzFeZ8NgzWNMzfUEvuJcQtZoXb1LQnQ+eId53BM7fF35rfmuRgLk6K3tMAm
C1R4uR+BXs65lJyDLjG/GTHqwTCXeDXe6dISsHrSmSBCKJHJV7RHGnW5eNUzXWYU
rmOuCEz6CeDlO+Ei2oWZT8ahUucsiGL8Xika9KurWwNMHP3u4zjE7ALt9AEePJBO
0Eewpk5mXoK3da4QWDuZsFNfGPX9s7DdQp0MAPLBueyWMXv0G+RrLDdPEdX41yt9
J22XtiSO+biPHNI1OUlJJKiBfyJedY7AzpjwxmAFH4R+8sxfdkSELuZOzvETTijV
KFS+Ejwnca978EMwfdPAFU7NIl6ZEICZG7S76SVdhLrx2n6PXKCQdGxEj/oMhDMJ
zyD121n2dI4VQ0G9CdhLWJNs5cyhVBJ8ZYod6a1/LIKRPsDQenEwY+igZ32ts/L2
e9+zmusK+DpCHCAaYM+UfGmskYjUD4ZyHfwAVwf16lKkt0yrTinZElbySBDlz0Vy
u3h1Be6+WsUzEjxaEkCW2j5C7o9636ZYH10zVcu9aK1YGxIYOgvBMiTWncrZwTRo
sDE3FvML2xnyy78pSRjRPYbDrJL8ZkojpAVuuYanPgEyPA7Kl6K7ov5pUa5EhmSm
3OOvkDtecZ4tAn+hvI19
=JL6U
-END PGP SIGNATURE-

Bug#820026: icedove crashes suddenly

[jathan]

Am 21.06.2016 um 07:49 schrieb Laurent:
> I have a problem those days with Icedove : when running (writting an 
> email, searching in a list or any simple operation), it crashes. This >
never happened before.
>

I do have the same issue. It have been happening since the beginning
when I start to use Debian Jessie, but crashes were less common. Now
with the latest icedove version 1:45.1.0-1~deb8u1, the crashes occurs
during all the time that I am using Icedove. For me it happens randomly
when clicking on any mail, about 5-10 times everyday. After
starting icedove again, there's no problem when opening the mail clicked
on before.

The installed addons are enigmail and iceowl from jessie repo. In all
the computers that I use Debian and Icedove happend the same. This the
terminal message when Icedove crash:

@debian:~$ icedove
[calBackendLoader] Using libical backend at
/usr/lib/icedove/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/libical-manifest
enigmail.js: Registered components
mimeVerify.jsm: module initialized
Violación de segmento
@debian:~$

Best regards,
Jathan

-- 
Por favor evita enviarme adjuntos en formato de word o powerpoint, si
quieres saber porque lee esto:
http://www.gnu.org/philosophy/no-word-attachments.es.html
¡Cámbiate a GNU/Linux! http://getgnulinux.org/es



signature.asc
Description: OpenPGP digital signature

Bug#820026: icedove crashes suddenly

[jathan]

Am 21.06.2016 um 07:49 schrieb Laurent:
> I have a problem those days with Icedove : when running (writting an >
email, searching in a list or any simple operation), it crashes. This >
never happened before.
>

I do have the same issue. It have been happening since the beginning
when I start to use Debian Jessie, but crashes were less common. Now
with the latest icedove version 1:45.1.0-1~deb8u1, the crashes occurs
during all the time that I am using Icedove. For me it happens randomly
when clicking on any mail, about 5-10 times everyday. After
starting icedove again, there's no problem when opening the mail clicked
on before.

The installed addons are enigmail and iceowl from jessie repo. In all
the computers that I use Debian and Icedove happend the same. This the
terminal message when Icedove crash:

@debian:~$ icedove
[calBackendLoader] Using libical backend at
/usr/lib/icedove/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/libical-manifest
enigmail.js: Registered components
mimeVerify.jsm: module initialized
Violación de segmento
@debian:~$

Best regards,
Jathan

-- 
Por favor evita enviarme adjuntos en formato de word o powerpoint, si
quieres saber porque lee esto:
http://www.gnu.org/philosophy/no-word-attachments.es.html
¡Cámbiate a GNU/Linux! http://getgnulinux.org/es

Bug#829597: [Pkg-clamav-devel] Bug#829597: clamav-daemon: LocalSocket not created.

[Gordon Dickens]

On 07/04/2016 06:09 PM, Sebastian Andrzej Siewior wrote:
and you remained on Jessie, correct? 


Yes, all three of my Debian servers are running Debian 8.5 as per the 
/etc/debian_version files.



You should have /run which is a tmpfs:
|$ mount|grep "run "
|tmpfs on /run type tmpfs (rw,nosuid,relatime,size=1607508k,mode=755)

and /var/run should be a symlink:

|$ ls -l /var/ | grep "run "
|lrwxrwxrwx  1 root root  4 Aug  3  2013 run -> /run


Yes, here are the results from one of my servers and which are 
essentially the same as yours:


|$ mount|grep "run "
|tmpfs on /run type tmpfs (rw,nosuid,relatime,size=1632120k,mode=755)
|
|ls -l /var/ | grep "run "
|lrwxrwxrwx  1 root root 4 Jun 11  2013 run -> /run


and since you run systemd there should be two service files:
|# systemctl status clamav-daemon.socket
|● clamav-daemon.socket - Socket for Clam AntiVirus userspace daemon
|   Loaded: loaded (/lib/systemd/system/clamav-daemon.socket; enabled)
|  Drop-In: /etc/systemd/system/clamav-daemon.socket.d
|   └─extend.conf
|   Active: active (running) since Thu 2016-05-26 22:35:00 CEST; 1 months 8 
days ago
| Docs: man:clamd(8)
|   man:clamd.conf(5)
|   http://www.clamav.net/lang/en/doc/
|   Listen: /var/run/clamav/clamd.ctl (Stream)
|
|Warning: Journal has been rotated since unit was started. Log output is 
incomplete or unavailable.
|# systemctl status clamav-daemon.service
|● clamav-daemon.service - Clam AntiVirus userspace daemon
|   Loaded: loaded (/lib/systemd/system/clamav-daemon.service; enabled)
|   Active: active (running) since Thu 2016-05-26 22:35:00 CEST; 1 months 8 
days ago
| Docs: man:clamd(8)
|   man:clamd.conf(5)
|   http://www.clamav.net/lang/en/doc/
| Main PID: 11021 (clamd)
|   CGroup: /system.slice/clamav-daemon.service
|   └─11021 /usr/sbin/clamd --foreground=true
|


Yes, I have both of these service files and I previously posted  the 
"systemctl status" results for both services in my initial bug report.



If you read the .socket file then you will see that one creates the
socket and the .service file depends on it. Uppon start, systemd passes
the socket to clamd then. I *assume* that the socket part is not started
for some reason on your machines.
Exactly!  The socket is not being started on either of my three debian 
machines.  Here is the contents of my clamav-daemon.socket file:


|cat /lib/systemd/system/clamav-daemon.socket
|[Unit]
|Description=Socket for Clam AntiVirus userspace daemon
|Documentation=man:clamd(8) man:clamd.conf(5) 
http://www.clamav.net/lang/en/doc/

|# Check for database existence
|ConditionPathExistsGlob=/var/lib/clamav/main.{c[vl]d,inc}
|ConditionPathExistsGlob=/var/lib/clamav/daily.{c[vl]d,inc}
|
|[Socket]
|ListenStream=/run/clamav/clamd.ctl
|#ListenStream=127.0.0.1:1024
|SocketUser=clamav
|SocketGroup=clamav
|RemoveOnStop=True
|
|[Install]
|WantedBy=sockets.target

Please advise

Gordon

Bug#829648: RFS: twinkle/1:1.9.0+git20160520.0.be8b8df+dfsg-1~bpo8+1 -- Voice over Internet Protocol (VoIP) SIP

[Peter Colberg]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor to upload the package "twinkle" to
jessie-backports. I have been added to the backports ACL for
subsequent maintenance.

git clone https://anonscm.debian.org/git/pkg-voip/twinkle.git
cd twinkle && pristine-tar checkout 
../twinkle_1.9.0+git20160520.0.be8b8df+dfsg.orig.tar.xz
git checkout debian/jessie-backports

Please include all changes since the last stable version [1] in your upload:

sbuild -j4 --dist=jessie --debbuildopts=-v1:1.4.2-2 --force-orig-source

[1] https://archive.debian.net/squeeze/twinkle

For historic background, twinkle had been removed from testing before
the release of wheezy due to only building with Qt3. For a while the
console client with limited functionality was available in unstable.
A year ago twinkle was ported to Qt5 by a new upstream maintainer.

Regards,
Peter


signature.asc
Description: PGP signature

Bug#829597: [Pkg-clamav-devel] Bug#829597: clamav-daemon: LocalSocket not created.

[Gordon Dickens]

Here are the "systemctl status" results for clamav-daemon and 
clamav-daemon.socket on my servers:


|$ systemctl status clamav-daemon
|● clamav-daemon.service - Clam AntiVirus userspace daemon
|   Loaded: loaded (/lib/systemd/system/clamav-daemon.service; enabled)
|   Active: active (running) since Mon 2016-07-04 10:21:16 EDT; 11h ago
| Docs: man:clamd(8)
|   man:clamd.conf(5)
|   http://www.clamav.net/lang/en/doc/
| Main PID: 5340 (clamd)
|   CGroup: /system.slice/clamav-daemon.service
|   └─5340 /usr/sbin/clamd --foreground=true
|
|$ systemctl status clamav-daemon.socket
|● clamav-daemon.socket - Socket for Clam AntiVirus userspace daemon
|   Loaded: loaded (/lib/systemd/system/clamav-daemon.socket; enabled)
|  Drop-In: /etc/systemd/system/clamav-daemon.socket.d
|   └─extend.conf
|   Active: active (running) since Mon 2016-07-04 10:21:16 EDT; 11h ago
| Docs: man:clamd(8)
|   man:clamd.conf(5)
|   http://www.clamav.net/lang/en/doc/
|   Listen: [::]:3310 (Stream)

I thought that I had included these results on my initial post but I was 
mistaken


Please advise...

Gordon

Bug#829647: pdns-server: Using an RFC7505 null MX entry crashes pdns-server threads

[Florian Steinel]

Package: pdns-server
Version: 3.4.1-4+deb8u5
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
 I was adding null MX entrys as defined in RFC7505 to the pdns-server 
running with the bind backend 
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Added "@ IN MX 0 ." for a Host wich does not run a MTA.
   * What was the outcome of this action?
 The pdns-Server threads crashes, the dns changes and any further changes 
are not published.
 Logentries:
Jul 05 00:00:17 dns pdns_server[8928]: Jul 05 00:00:17 Signing thread died 
because of std::exception: All data was not consumed
Jul 05 00:00:17 dns pdns[8930]: Signing thread died because of std::exception: 
All data was not consumed
Jul 05 00:00:17 dns pdns[8930]: Signing thread died because of std::exception: 
All data was not consumed
Jul 05 00:00:17 dns pdns_server[8928]: Jul 05 00:00:17 Signing thread died 
because of std::exception: All data was not consumed
Jul 05 00:00:17 dns pdns[8930]: Signing thread died because of std::exception: 
failed in writen2: Broken pipe  
Jul 05 00:00:17 dns pdns[8930]: TCP Connection Thread died because of STL 
error: Reading from socket in Signing Pipe loop: Connection reset by peer
Jul 05 00:00:17 dns pdns_server[8928]: Jul 05 00:00:17 Signing thread died 
because of std::exception: failed in writen2: Broken pipe
Jul 05 00:00:17 dns pdns_server[8928]: Jul 05 00:00:17 TCP Connection Thread 
died because of STL error: Reading from socket in Signing Pipe loop: Connection 
reset by peer

   * What outcome did you expect instead?
 The change were published to dns

See Upstream Bug https://github.com/PowerDNS/pdns/issues/2836
and Upstream Commit 
https://github.com/PowerDNS/pdns/commit/e94c2c40ac6e0ecf8a5fdf7c415da5c59a8330d6

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


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

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

Versions of packages pdns-server depends on:
ii  adduser 3.113+nmu3
ii  debconf [debconf-2.0]   1.5.56
ii  init-system-helpers 1.22
ii  libboost-program-options1.55.0  1.55.0+dfsg-3
ii  libboost-serialization1.55.01.55.0+dfsg-3
ii  libbotan-1.10-0 1.10.8-2+deb8u1
ii  libc6   2.19-18+deb8u4
ii  libcrypto++95.6.1-6+deb8u2
ii  libgcc1 1:4.9.2-10
ii  libgmp102:6.0.0+dfsg-6
ii  liblua5.1-0 5.1.5-7.1
ii  libpolarssl71.3.9-2.1+deb8u1
ii  libsqlite3-03.8.7.1-1+deb8u1
ii  libstdc++6  4.9.2-10
ii  lsb-base4.1+Debian13+nmu1
ii  ucf 3.0030

pdns-server recommends no packages.

Versions of packages pdns-server suggests:
ii  pdns-backend-geo [pdns-backend]  3.4.1-4+deb8u5
ii  pdns-recursor3.6.2-2+deb8u2

-- debconf information:
* pdns-server/localaddress: 217.70.197.53
* pdns-server/allowrecursion: 127.0.0.1


signature.asc
Description: PGP signature

Bug#829525: [PATCH] 1.15 requires libdrm-dev >= 2.4.64

[Nicholas D Steeves]

On 3 July 2016 at 22:21, Vincent Cheng  wrote:
> Control: tag -1 + pending
>
> On Sun, Jul 3, 2016 at 6:48 PM, Nicholas D Steeves  wrote:
>> Package: intel-gpu-tools
>> Version: 1.15-1
>>
>> I'm working on backporting intel-vaapi-driver to Jessie; it depends on
>> intel-gpu-tools (>= 1.9) so I'm also working on backporting
>> intel-gpu-tools.  I discovered that intel-gpu-tools-1.15 requires
>> libdrm-dev >= 2.4.64.  Patch attached!
>>
>> Thank you,
>> Nicholas
>
> Applied, thanks for the patch.
>
> Regards,
> Vincent

You're welcome.  Sorry I missed Bug #829612 when writing this patch!

Cheers,
Nicholas

Bug#829646: mk-origtargz: Files-Excluded-Ignore

[Dmitry Smirnov]

Package: devscripts
Version: 2.16.6
Severity: wishlist

In Golang team we routinely use (very useful) Files-Excluded
feature to get rid of bundled/vendored libraries.

Usually we can remove all 3rd party libs but occasionally few dependencies
should be preserved in which case we have to maintain explicit long lists
of exclusions like in following example:

http://anonscm.debian.org/cgit/docker/docker.io.git/tree/debian/copyright?h=experimental

IMHO it could be useful to be able to drop everything _but_ some folders:

Files-Excluded: vendor/src/*
Files-Excluded-Ignore: vendor/src/github.com/docker/notary

hence I'd like to propose new "Files-Excluded-Ignore" field.

-- 
All the best,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B

---

The truth is incontrovertible, malice may attack it, ignorance may deride
it, but in the end; there it is.
-- Winston Churchill


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

Bug#829159: mention what will happen when colrm used with no args

[積丹尼 Dan Jacobson]

> "MM" == Michael Meskes  writes:
MM> On Fri, Jul 01, 2016 at 01:44:48PM +0800, 積丹尼 Dan Jacobson wrote:
>> Mention what will happen if both start and stop are omitted.
>> E.g.,
>> $ date | colrm

MM> Eh? What else would you expect?

A usage message.

Anyway it turns out colrm with no args is more like colrm infinity, than
colrm 3, colrm 2, colrm 1 etc.

$ date|colrm 0
colrm: illegal column -- 0

At least it says something some times.

Bug#829645: src:gtest: Cannot build against libgtest-dev with std=c++11

[Afif Elghraoui]

Package: src:gtest
Version: 1.7.0-4
Severity: important

Hello,

I'm trying to enable tests for the pbbam package, but there is a compilation 
error that is triggered by simply including gtest.h:


tests/CMakeFiles/test_pbbam.dir/build.make:65: recipe for target 
'tests/CMakeFiles/test_pbbam.dir/src/test_Accuracy.cpp.o' failed
make[3]: *** [tests/CMakeFiles/test_pbbam.dir/src/test_Accuracy.cpp.o] Error 1
make[3]: *** Waiting for unfinished jobs
In file included from /usr/include/gtest/internal/gtest-port.h:213:0,
 from /usr/include/gtest/internal/gtest-internal.h:40,
 from /usr/include/gtest/gtest.h:58,
 from /<>/tests/src/test_AlignmentPrinter.cpp:43:
/usr/include/c++/5/sstream:300:7: error: ‘struct 
std::__cxx11::basic_stringbuf<_CharT, _Traits, _Alloc>::__xfer_bufptrs’ 
redeclared with different access
   struct __xfer_bufptrs
   ^
In file included from /usr/include/gtest/internal/gtest-port.h:213:0,
 from /usr/include/gtest/internal/gtest-internal.h:40,
 from /usr/include/gtest/gtest.h:58,
 from /<>/tests/src/test_BamFile.cpp:43:
/usr/include/c++/5/sstream:300:7: error: ‘struct 
std::__cxx11::basic_stringbuf<_CharT, _Traits, _Alloc>::__xfer_bufptrs’ 
redeclared with different access
   struct __xfer_bufptrs
   ^
tests/CMakeFiles/test_pbbam.dir/build.make:89: recipe for target 
'tests/CMakeFiles/test_pbbam.dir/src/test_AlignmentPrinter.cpp.o' failed



Line 43 of my file /<>/tests/src/test_AlignmentPrinter.cpp has:

#include 

The error looks like one of the GCC transition issues, and the last formal
gtest release is several years old despite the code base being actively
developed. I think it would be good to update the package to a recent git
snapshot since it seems upstream cannot be convinced to make a new release [1].

Many thanks and regards
Afif

1. https://github.com/google/googletest/issues/746

Bug#829644: please convert haskell-mode to use dh_elpa

[Sean Whitton]

Source: haskell-mode
Severity: wishlist
Version: 13.14.2-1

Dear maintainer,

It would be great if you could convert haskell-mode to use the new dh_elpa
infrastructure for Emacs Lisp addons. [1]

This would allow it to interoperate better with other packages.  It
would also allow a call to `package-initialize' to load up haskell-mode and
packages depending on it without any workarounds.

I would be willing to adopt the package if you don't have time to do
this.

[1] http://pkg-emacsen.alioth.debian.org/elpa-hello/

-- 
Sean Whitton

Bug#829642: pulseaudio 9 breaks SPDIF/iec958 and Intel HDMI audio on ASUS B85-Pro motherboard

[Felipe Sateler]

Control: tags -1 moreinfo

On 4 July 2016 at 19:21, Adam Warner  wrote:
>
> Package: pulseaudio
> Version: 9.0-1
> Severity: serious
> Justification: keep out of testing. Workaround is to downgrade to the
> version in testing
>
>
> Installation is x86-64 stock sid/unstable as of an hour ago
> (with libwebrtc-audio-processing-0 held after downgrade to
> pulseaudio 8.0-2+b2)
>
> Before pulseaudio upgrade:
>
> $ pacmd list-sinks | grep name:
> name: 
> name: 



> After reboot:
>  pacmd list-sinks | grep name:
> name: 


Could you please attach a verbose log of both versions of pulseaudio?
https://wiki.ubuntu.com/PulseAudio/Log

-- 

Saludos,
Felipe Sateler

Bug#829643: tiger: Filesystem 'fuse.lxcfs' used by 'lxcfs' is not recognised as a valid filesystem

[Francois Marier]

Package: tiger
Version: 1:3.2.3-14.1
Severity: normal
Tags: patch

The cronjob generates the following output everytime it runs gen_mounts:

  --CONFIG-- [con010c] Filesystem 'fuse.lxcfs' used by 'lxcfs' is not 
recognised as a valid filesystem

Attached is a simple patch which fixes that.

Francois

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

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

Versions of packages tiger depends on:
ii  binutils   2.26.1-1
ii  bsdmainutils   9.0.10
ii  debconf [debconf-2.0]  1.5.59
ii  libc6  2.22-13
ii  net-tools  1.60+git20150829.73cef8a-2
ii  ucf3.0036

Versions of packages tiger recommends:
ii  chkrootkit  0.50-3.2
pn  john
ii  postfix [mail-transport-agent]  3.1.0-3
pn  tripwire | aide 

Versions of packages tiger suggests:
ii  lsof  4.89+dfsg-0.1

-- debconf information excluded
diff --git a/systems/Linux/2/gen_mounts b/systems/Linux/2/gen_mounts
index dd5efdf..3034242 100755
--- a/systems/Linux/2/gen_mounts
+++ b/systems/Linux/2/gen_mounts
@@ -151,6 +151,7 @@ localfs()
   [ "$1" = "fuse.gvfs-fuse-daemon" ] && LOCAL=1 # Used in Ubuntu 'hardy'
   [ "$1" = "fuse.gvfsd-fuse" ] && LOCAL=1   # Used in Ubuntu 13.10 (Saucy Salamander) replaces fuse.gvfs-fuse-daemon
   [ "$1" = "fuse.ltspfs" ] && LOCAL=0 		# Used by LTSP 5.x
+  [ "$1" = "fuse.lxcfs" ] && LOCAL=0
   [ "$1" = "ecryptfs" ] && LOCAL=0  # Encrypted filesystem used by ecryptfs-utils
   [ "$1" = "xenfs" ] && LOCAL=0 # Virtual fs for Xen
   [ "$1" = "cgroup" ] && LOCAL=0# General access point to Kernel Control Groups

Bug#828509: postgis: FTBFS with openssl 1.1.0

[Sebastiaan Couwenberg]

Control: tags -1 - moreinfo
Control: tags -1 - pending

Hi Kurt,

On 06/26/2016 08:11 PM, Kurt Roeckx wrote:
> Only packages linking to libssl/libcrypto should be affected.  I'm
> not sure why you build depend on libssl if you don't.
> 
> Anyway, if you can't reproduce this, feel free to close it.

libssl-dev was included in the Build-Dependencies since the initial
revision of the package, it has simply always been there.

I've dropped the build dependency from the packaging in git, and a new
upload to unstable will follow soon.

Kind Regards,

Bas

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

Bug#826241: [Pkg-dns-devel] Bug#826241: Bug#826241: Bug#826241: unbound: Provide $named facility under systemd

[Robert Edmonds]

Michael Biebl wrote:
> Ok, I guess I have the missing ingredient now. We need to make the
> unbound-resolvconf.service unit use Type=simple not oneshot.
> oneshot blocks until the started process has completed, with Type=simple
> we don't block.

Hi, Michael:

I tested this (actually your later version with the typo fix), but it
seems unbound-resolvconf.service starts, but then immediately stops:

● unbound-resolvconf.service - Unbound DNS server via resolvconf
   Loaded: loaded (/lib/systemd/system/unbound-resolvconf.service; enabled; 
vendor preset: enabled)
   Active: inactive (dead) since Mon 2016-07-04 23:27:10 UTC; 10s ago
  Process: 1416 ExecStop=/usr/lib/unbound/package-helper resolvconf_stop 
(code=exited, status=0/SUCCESS)
  Process: 1387 ExecStart=/usr/lib/unbound/package-helper resolvconf_start 
(code=exited, status=0/SUCCESS)
 Main PID: 1387 (code=exited, status=0/SUCCESS)

Jul 04 23:27:10 debian systemd[1]: Started Unbound DNS server via resolvconf.
Jul 04 23:27:10 debian package-helper[1387]: executing resolvconf_start
Jul 04 23:27:10 debian package-helper[1416]: executing resolvconf_stop

(I inserted an echo at the top of the package-helper script just to
verify.)

This is not what we need, because the local Unbound gets added to
/etc/resolv.conf (when ExecStart runs) and then immediately removed a
split second later (when ExecStop runs).

Do we need to set “RemainAfterExit=yes” in unbound-resolvconf.service?

Thanks!

-- 
Robert Edmonds
edmo...@debian.org

Bug#824944: Update on #824944

[Jason Pleau]

Hey,

On 07/04/2016 06:43 PM, Julian Wollrath wrote:
> Hi,
> 
> thanks for your interest. I modified it myself to incorporate (and
> hopefully support) the flags of discount 2.1.8, therefore the version
> change, since upstream seems inactive. I am in contact with Enrico
> Tassi, who sponsored previous uploads to get it uploaded.
> 

Awesome, thanks for the swift reply and explanation !

> Cheers,
> Julian
> 

Cheers

-- 
Jason Pleau

Bug#829642: pulseaudio 9 breaks SPDIF/iec958 and Intel HDMI audio on ASUS B85-Pro motherboard

[Adam Warner]

Package: pulseaudio
Version: 9.0-1
Severity: serious
Justification: keep out of testing. Workaround is to downgrade to the
version in testing


Installation is x86-64 stock sid/unstable as of an hour ago
(with libwebrtc-audio-processing-0 held after downgrade to
pulseaudio 8.0-2+b2)

Before pulseaudio upgrade:

$ pacmd list-sinks | grep name:
name: 
name: 


consisting of:
device.product.name = "8 Series/C220 Series Chipset High Definition
Audio Controller"
device.description = "Built-in Audio Digital Stereo (IEC958)"
alsa.mixer_name = "Realtek ALC1150"
alsa.components = "HDA:10ec0900,10438610,0011"
module-udev-detect.discovered = "1"

and:
device.product.name = "Xeon E3-1200 v3/4th Gen Core Processor HD Audio
Controller"
device.description = "Built-in Audio Digital Stereo (HDMI)"
alsa.mixer_name = "Intel Haswell HDMI"
alsa.components = "HDA:80862807,80860101,0010"
module-udev-detect.discovered = "1"



Upgrade to pulseaudio 9.0-1:

~# apt-get install libpulse-mainloop-glib0 libpulse0 libpulsedsp
pulseaudio pulseaudio-utils
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer
required:
  libwebrtc-audio-processing-0
Use 'apt autoremove' to remove it.
Suggested packages:
  pavumeter paman paprefs
Recommended packages:
  pulseaudio-module-x11 rtkit pulseaudio-module-udev
The following packages will be upgraded:
  libpulse-mainloop-glib0 libpulse0 libpulsedsp pulseaudio pulseaudio-
utils
5 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/1,467 kB of archives.
After this operation, 36.9 kB of additional disk space will be used.
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
(Reading database ... 359743 files and directories currently
installed.)
Preparing to unpack .../libpulsedsp_9.0-1_amd64.deb ...
Unpacking libpulsedsp:amd64 (9.0-1) over (8.0-2+b2) ...
Preparing to unpack .../pulseaudio-utils_9.0-1_amd64.deb ...
Unpacking pulseaudio-utils (9.0-1) over (8.0-2+b2) ...
Preparing to unpack .../pulseaudio_9.0-1_amd64.deb ...
Unpacking pulseaudio (9.0-1) over (8.0-2+b2) ...
Preparing to unpack .../libpulse-mainloop-glib0_9.0-1_amd64.deb ...
Unpacking libpulse-mainloop-glib0:amd64 (9.0-1) over (8.0-2+b2) ...
Preparing to unpack .../libpulse0_9.0-1_amd64.deb ...
Unpacking libpulse0:amd64 (9.0-1) over (8.0-2+b2) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for dbus (1.10.8-1) ...
Processing triggers for libc-bin (2.23-1) ...
Setting up libpulse0:amd64 (9.0-1) ...
Setting up libpulsedsp:amd64 (9.0-1) ...
Setting up pulseaudio-utils (9.0-1) ...
Setting up pulseaudio (9.0-1) ...
Installing new version of config file /etc/pulse/daemon.conf ...
Installing new version of config file /etc/pulse/default.pa ...
Setting up libpulse-mainloop-glib0:amd64 (9.0-1) ...
Processing triggers for libc-bin (2.23-1) ...


After reboot:
 pacmd list-sinks | grep name:
name: 

consisting of:
device.product.name = "8 Series/C220 Series Chipset High Definition
Audio Controller"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "Realtek ALC1150"
alsa.components = "HDA:10ec0900,10438610,0011"


Downgrade to pulseaudio 8.0-2+b2:
~# apt-get install libpulse-mainloop-glib0/testing libpulse0/testing
libpulsedsp/testing pulseaudio/testing pulseaudio-utils/testing
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '8.0-2+b2' (Debian:testing [amd64]) for 'libpulse-
mainloop-glib0'
Selected version '8.0-2+b2' (Debian:testing [amd64]) for 'libpulse0'
Selected version '8.0-2+b2' (Debian:testing [amd64]) for 'libpulsedsp'
Selected version '8.0-2+b2' (Debian:testing [amd64]) for 'pulseaudio'
Selected version '8.0-2+b2' (Debian:testing [amd64]) for 'pulseaudio-
utils'
The following package was automatically installed and is no longer
required:
  libwebrtc-audio-processing1
Use 'apt autoremove' to remove it.
Suggested packages:
  pavumeter paman paprefs
Recommended packages:
  pulseaudio-module-x11 rtkit
The following packages will be DOWNGRADED:
  libpulse-mainloop-glib0 libpulse0 libpulsedsp pulseaudio pulseaudio-
utils
0 upgraded, 0 newly installed, 5 downgraded, 0 to remove and 1 not
upgraded.
Need to get 0 B/1,455 kB of archives.
After this operation, 36.9 kB disk space will be freed.
Do you want to continue? [Y/n] 
dpkg: warning: downgrading libpulsedsp:amd64 from 9.0-1 to 8.0-2+b2
(Reading database ... 359736 files and directories currently
installed.)
Preparing to unpack .../libpulsedsp_8.0-2+b2_amd64.deb ...
Unpacking libpulsedsp:amd64 (8.0-2+b2) over (9.0-1) ...
dpkg: warning: downgrading pulseaudio-utils from 9.0-1 to 8.0-2+b2
Preparing to unpack .../pulseaudio-utils_8.0-2+b2_amd64.deb ...
Unpacking pulseaudio-utils (8.0-2+b2) over (9.0-1) ...
dpkg: warning: downgrading pulseaudio from 9.0-1 to 8.0-2+b2
Preparing to 

Bug#829641: libnss-ldapd configuration questions does not respect the information in debconf

[Andre Kostur]

Package: libnss-ldapd
Version: 0.9.4-3+deb8u1
Severity: minor

Dear Maintainer,

libnss-ldapd does not appear to respect the content of debconf when asking its
question of which items to configure in nsswitch.conf.

When you perform a dpkg-reconfigure on libnss-ldapd, it will show you the list
of databases as configured in nsswitch.conf, not as recorded in debconf.  It
does record the answer into debconf.

As an example, let's assume that I originally installed the package and selected
the passwd and group databases to look up using ldap.  This adjusts 
nsswitch.conf
and records in debconf that I'd selected passwd and group.   Next, I change that
answer (using debconf-set-selections) to only choose passwd.   Run
dpkg-reconfigure and it again shows both passwd and group, since that is what
nsswitch.conf is currently configured with.  I was expecting this to show me
just passwd as that is what is stored in debconf.

This bug prevents me from being able to change the answer in debconf and then
cause the package to apply that configuration via running:
"dpkg-reconfigure -fnoninteractive libnss-ldapd".  I would presume that this
would also prevent me from pre-answering the question before installing the
package too.

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

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

Versions of packages libnss-ldapd depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  libc6  2.19-18+deb8u4
ii  multiarch-support  2.19-18+deb8u4
ii  nslcd [nslcd-2]0.9.4-3+deb8u1

libnss-ldapd recommends no packages.

libnss-ldapd suggests no packages.

-- debconf information:
  libnss-ldapd/clean_nsswitch: false
* libnss-ldapd/nsswitch: group, passwd

Bug#829605: RFS: aspell-sk/2.02-0-0.1 [RC, NMU]

[Jakub Wilk]

Control: owner -1 !
Control: tags -1 + moreinfo

* Pali Rohár , 2016-07-04, 18:13:

dget -x 
https://mentors.debian.net/debian/pool/main/a/aspell-sk/aspell-sk_2.02-0-0.1.dsc

Changes since the last upload:

 * Non-maintainer upload.
 * New upstream release (Closes: #603719).


debian/copyright says that the package "was downloaded from 
ftp://ftp.gnu.org/gnu/aspell/dict/sk/;, but there is no 2.02-0 at this 
location.


BTW, what's the difference between 2.01-2 and 2.02-0? There's no entry 
for the latter version in doc/CHANGELOG. :-\


Also, the copyright file says that the package is under GPL, whereas 
this new version is tri-licensed: LGPLv2.1, GPLv2, MPLv1.1.



 * Use compat level 9 (Closes: #817360).


Did you need to do any packaging changes to bump compat?


 * Add Homepage and update Standards-Version.


Why are these two in a single item? They seem unrelated to me.

Did you need to do any packaging changes to update S-V?
I wouldn't recommend updating S-V in an NMU.

Addition of debian/watch is not documented in the changelog.

You changed source format to "3.0 (quilt)", but this change is not 
documented either. Also, changing source format is not suitable for an 
NMU, unless you have a very good reason.


--
Jakub Wilk

Bug#829640: netfilter-persistent loads firewall rules too late

[Patrick Schleizer]

Package: netfilter-persistent
Severity: grave
X-Debbugs-CC: whonix-de...@whonix.org
Tags: security

Dear maintainer,

there is a security issue with the netfilter-persistent systemd service. [1]

netfilter-persistent orders itself before the wrong target. Should be
'Before=network-pre.target'.

The systemd manual is quite clear on network.target and
network-pre.target. [2]

Credits for finding this bug go to rustybird. [3] [4] (I am only
seconding and reporting it.)

(Using severity grave as this could pose a security risk, i.e. the
firewall getting up too late.)

Cheers,
Patrick

[1]
https://anonscm.debian.org/cgit/collab-maint/iptables-persistent.git/tree/systemd/netfilter-persistent.service
[2] https://www.freedesktop.org/software/systemd/man/systemd.special.html
[3] https://github.com/rustybird
[4] https://github.com/rustybird/corridor/issues/8#issuecomment-230266161

Bug#829633: license-reconcile: Missing depends on licensecheck

[Adam Conrad]

Package: license-reconcile
Version: 0.10
Followup-For: Bug #829633
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch



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

  * Replace devscripts dependencies with licensecheck (closes: #829633)

The patch should be self-explanatory.  The tests all pass with the
deps swapped.  As a side note, it's a but nutty that one has to change
the version string in 28 places when bumping the package version. :P

... Adam

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

Kernel: Linux 4.4.0-28-lowlatency (SMP w/4 CPU cores; PREEMPT)
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 license-reconcile-0.10/debian/control license-reconcile-0.10ubuntu1/debian/control
--- license-reconcile-0.10/debian/control	2016-03-02 09:16:27.0 -0700
+++ license-reconcile-0.10ubuntu1/debian/control	2016-07-04 16:25:51.0 -0600
@@ -8,7 +8,7 @@
libmodule-build-perl,
perl (>= 5.18),
bash-completion
-Build-Depends-Indep: devscripts (>= 2.15.10~),
+Build-Depends-Indep: licensecheck,
  libclass-xsaccessor-perl,
  libconfig-any-perl,
  libdebian-copyright-perl (>= 0.2),
@@ -40,7 +40,7 @@
 Architecture: all
 Depends: ${misc:Depends},
  ${perl:Depends},
- devscripts (>= 2.15.10~),
+ licensecheck,
  libclass-xsaccessor-perl,
  libconfig-any-perl,
  libdebian-copyright-perl (>= 0.2),
diff -Nru license-reconcile-0.10/lib/Debian/LicenseReconcile/App.pm license-reconcile-0.10ubuntu1/lib/Debian/LicenseReconcile/App.pm
--- license-reconcile-0.10/lib/Debian/LicenseReconcile/App.pm	2016-03-02 09:16:27.0 -0700
+++ license-reconcile-0.10ubuntu1/lib/Debian/LicenseReconcile/App.pm	2016-07-04 16:20:16.0 -0600
@@ -244,11 +244,11 @@
 
 =head1 VERSION
 
-Version 0.10
+Version 0.10ubuntu1
 
 =cut
 
-our $VERSION = '0.10';
+our $VERSION = '0.10ubuntu1';
 
 
 =head1 SYNOPSIS
diff -Nru license-reconcile-0.10/lib/Debian/LicenseReconcile/CopyrightDatum/Holder.pm license-reconcile-0.10ubuntu1/lib/Debian/LicenseReconcile/CopyrightDatum/Holder.pm
--- license-reconcile-0.10/lib/Debian/LicenseReconcile/CopyrightDatum/Holder.pm	2016-03-02 09:16:27.0 -0700
+++ license-reconcile-0.10ubuntu1/lib/Debian/LicenseReconcile/CopyrightDatum/Holder.pm	2016-07-04 16:20:16.0 -0600
@@ -61,11 +61,11 @@
 
 =head1 VERSION
 
-Version 0.10
+Version 0.10ubuntu1
 
 =cut
 
-our $VERSION = '0.10';
+our $VERSION = '0.10ubuntu1';
 
 
 =head1 SYNOPSIS
diff -Nru license-reconcile-0.10/lib/Debian/LicenseReconcile/CopyrightDatum.pm license-reconcile-0.10ubuntu1/lib/Debian/LicenseReconcile/CopyrightDatum.pm
--- license-reconcile-0.10/lib/Debian/LicenseReconcile/CopyrightDatum.pm	2016-03-02 09:16:27.0 -0700
+++ license-reconcile-0.10ubuntu1/lib/Debian/LicenseReconcile/CopyrightDatum.pm	2016-07-04 16:20:16.0 -0600
@@ -214,11 +214,11 @@
 
 =head1 VERSION
 
-Version 0.10
+Version 0.10ubuntu1
 
 =cut
 
-our $VERSION = '0.10';
+our $VERSION = '0.10ubuntu1';
 
 =head1 DESCRIPTION
 
diff -Nru license-reconcile-0.10/lib/Debian/LicenseReconcile/CopyrightTarget.pm license-reconcile-0.10ubuntu1/lib/Debian/LicenseReconcile/CopyrightTarget.pm
--- license-reconcile-0.10/lib/Debian/LicenseReconcile/CopyrightTarget.pm	2016-03-02 09:16:27.0 -0700
+++ license-reconcile-0.10ubuntu1/lib/Debian/LicenseReconcile/CopyrightTarget.pm	2016-07-04 16:20:16.0 -0600
@@ -100,11 +100,11 @@
 
 =head1 VERSION
 
-Version 0.10
+Version 0.10ubuntu1
 
 =cut
 
-our $VERSION = '0.10';
+our $VERSION = '0.10ubuntu1';
 
 
 =head1 SYNOPSIS
diff -Nru license-reconcile-0.10/lib/Debian/LicenseReconcile/Errors.pm license-reconcile-0.10ubuntu1/lib/Debian/LicenseReconcile/Errors.pm
--- license-reconcile-0.10/lib/Debian/LicenseReconcile/Errors.pm	2016-03-02 09:16:27.0 -0700
+++ license-reconcile-0.10ubuntu1/lib/Debian/LicenseReconcile/Errors.pm	2016-07-04 16:20:16.0 -0600
@@ -29,11 +29,11 @@
 
 =head1 VERSION
 
-Version 0.10
+Version 0.10ubuntu1
 
 =cut
 
-our $VERSION = '0.10';
+our $VERSION = '0.10ubuntu1';
 
 
 =head1 SYNOPSIS
diff -Nru license-reconcile-0.10/lib/Debian/LicenseReconcile/Filter/ChangeLog.pm license-reconcile-0.10ubuntu1/lib/Debian/LicenseReconcile/Filter/ChangeLog.pm
--- license-reconcile-0.10/lib/Debian/LicenseReconcile/Filter/ChangeLog.pm	2016-03-02 09:16:27.0 -0700
+++ license-reconcile-0.10ubuntu1/lib/Debian/LicenseReconcile/Filter/ChangeLog.pm	2016-07-04 16:20:16.0 -0600
@@ -96,11 +96,11 @@
 
 =head1 VERSION
 
-Version 0.10
+Version 0.10ubuntu1
 
 =cut
 
-our $VERSION = '0.10';
+our $VERSION = '0.10ubuntu1';
 
 
 =head1 SYNOPSIS
diff -Nru 

Bug#826615: iverilog NMU prepared

[Steffen Möller]

Hello,

My team membership application pending I have prepared an NMU for
iverilog 10.1. Is anything speaking against the version update?

Best,

Steffen

Bug#818370: [Pkg-dns-devel] Bug#818370: Fails to bind ports but suggests it started

[Robert Edmonds]

martin f krafft wrote:
> also sprach martin f krafft  [2016-03-16 15:05 +0100]:
> > I have no idea why it failed to bind the port on ::1. Nothing else
> > has this port bound.
> 
> The loopback interface was not up.

I can replicate this bug with unbound 1.5.8-1, but not with 1.5.9-1. It
looks like it was fixed by:

  * debian/unbound.init: Add "pidfile" magic comment (Closes: #807132)

This is with 1.5.9-1:

root@debian:~# systemctl stop unbound.service 
root@debian:~# systemctl status unbound.service 
● unbound.service
   Loaded: loaded (/etc/init.d/unbound; generated; vendor preset: enabled)
  Drop-In: /run/systemd/generator/unbound.service.d
   └─50-insserv.conf-$named.conf, 50-unbound-$named.conf
   Active: inactive (dead) since Mon 2016-07-04 22:47:42 UTC; 1s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 2650 ExecStop=/etc/init.d/unbound stop (code=exited, 
status=0/SUCCESS)
  Process: 2535 ExecStart=/etc/init.d/unbound start (code=exited, 
status=0/SUCCESS)
 Main PID: 2547 (code=exited, status=0/SUCCESS)

Jul 04 22:47:03 debian unbound[2547]: [2547:0] notice: init module 1: iterator
Jul 04 22:47:03 debian unbound[2547]: [2547:0] info: start of service (unbound 
1.5.9).
Jul 04 22:47:03 debian unbound[2535]: Starting DNS server: unbound.
Jul 04 22:47:03 debian systemd[1]: Started unbound.service.
Jul 04 22:47:42 debian systemd[1]: Stopping unbound.service...
Jul 04 22:47:42 debian unbound[2547]: [2547:0] info: service stopped (unbound 
1.5.9).
Jul 04 22:47:42 debian unbound[2547]: [2547:0] info: server stats for thread 0: 
0 queries, 0 answers from cache, 0 recursions,...refetch
Jul 04 22:47:42 debian unbound[2547]: [2547:0] info: server stats for thread 0: 
requestlist max 0 avg 0 exceeded 0 jostled 0
Jul 04 22:47:42 debian unbound[2650]: Stopping DNS server: unbound.
Jul 04 22:47:42 debian systemd[1]: Stopped unbound.service.
Hint: Some lines were ellipsized, use -l to show in full.
root@debian:~# ifdown lo
root@debian:~# systemctl start unbound.service 
Job for unbound.service failed because of unavailable resources or another 
system error.
See "systemctl status unbound.service" and "journalctl -xe" for details.
root@debian:~# systemctl status -l unbound.service 
● unbound.service
   Loaded: loaded (/etc/init.d/unbound; generated; vendor preset: enabled)
  Drop-In: /run/systemd/generator/unbound.service.d
   └─50-insserv.conf-$named.conf, 50-unbound-$named.conf
   Active: failed (Result: resources) since Mon 2016-07-04 22:47:56 UTC; 24s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 2650 ExecStop=/etc/init.d/unbound stop (code=exited, 
status=0/SUCCESS)
  Process: 2692 ExecStart=/etc/init.d/unbound start (code=exited, 
status=0/SUCCESS)
 Main PID: 2547 (code=exited, status=0/SUCCESS)

Jul 04 22:47:55 debian systemd[1]: Starting unbound.service...
Jul 04 22:47:56 debian unbound-anchor[2699]: /var/lib/unbound/root.key has 
content
Jul 04 22:47:56 debian unbound-anchor[2699]: success: the anchor is ok
Jul 04 22:47:56 debian unbound[2692]: Starting DNS server: unbound[1467672476] 
unbound[2703:0] error: can't bind socket: Cannot assign requested address for 
::1
Jul 04 22:47:56 debian unbound[2692]: [1467672476] unbound[2703:0] fatal error: 
could not open ports
Jul 04 22:47:56 debian unbound[2692]:  failed!
Jul 04 22:47:56 debian systemd[1]: unbound.service: PID file /run/unbound.pid 
not readable (yet?) after start: No such file or directory
Jul 04 22:47:56 debian systemd[1]: Failed to start unbound.service.
Jul 04 22:47:56 debian systemd[1]: unbound.service: Unit entered failed state.
Jul 04 22:47:56 debian systemd[1]: unbound.service: Failed with result 
'resources'.
root@debian:~# 

-- 
Robert Edmonds
edmo...@debian.org

Bug#824944: Update on #824944

[Julian Wollrath]

Hi,

thanks for your interest. I modified it myself to incorporate (and
hopefully support) the flags of discount 2.1.8, therefore the version
change, since upstream seems inactive. I am in contact with Enrico
Tassi, who sponsored previous uploads to get it uploaded.

Cheers,
Julian

Bug#829639: libosinfo: Failing autopkgtest

[Jeremy Bicha]

Patches attached.

Jeremy


0001-Have-build-test-autopkgtest-depend-on-build-essentia.patch
Description: Binary data


0002-Have-libosinfo-dev-depend-on-libglib2.0-dev.patch
Description: Binary data


0003-Point-Vcs-Browser-to-cgit.patch
Description: Binary data

Bug#828699: [Pkg-dns-devel] Bug#828699: libunbound2: please compile against libnettle

[Robert Edmonds]

brian m. carlson wrote:
> Currently, GnuTLS cannot be compiled with DANE support as that would
> require linking against libunbound2; that is unsuitable since
> libunbound2 links against OpenSSL.  As of unbound 1.5.7, compiling
> against libnettle is supported for libunbound2.  Doing so would allow
> GnuTLS (and other GPL-licensed software) to make use of libunbound2.
> Could you please do so?

Hi, brian:

It turns out libunbound won't build against the version of nettle in
testing/unstable. I've submitted a fix upstream:

https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=788

I'll wait to hear back from upstream before patching it in Debian.

-- 
Robert Edmonds
edmo...@debian.org

Bug#829270: [Pkg-clamav-devel] Bug#829270: tomsfastmath: please make the build reproducible

[Sebastian Andrzej Siewior]

control: tags -1 + pending fixed-upstream

On 2016-07-01 22:49:49 [+0200], Reiner Herrmann wrote:
> Hi!
Hi,

> While working on the "reproducible builds" effort [1], we have noticed
> that tomsfastmath could not be built reproducibly.
> A list of object files is unsorted, which causes a non-deterministic
> linking order.
> 
> The attached patch fixes this.

I commited your patch.
I don't mind getting a debdiff patch. But _please_ make a patch (talking
about reproducible-build.patch here) which follows a standard which is
used by quilt or git and that is:

|From: Author as you did
|Subject: Title
|
|description
|
|---
|Patch

> Regards,
>  Reiner

Sebastian

Bug#829639: libosinfo: Failing autopkgtest

[Jeremy Bicha]

Source: libosinfo
Version: 0.3.1-3
Tags: patch

libosinfo's autopkgtest doesn't work. I'm submitting a patch that
should fix this.

Jeremy Bicha

Bug#824944: Update on #824944

[Jason Pleau]

Hi,

I saw you seem to have fixed the bug in git last week [1]

Is the new version going to be uploaded to unstable soonish ? I also
noticed the version string in debian/changelog didn't really match
anything that upstream released. (I can't find 2.1.8 anywhere)

I'd be glad to help if you need. (I have a package that has a build-dep
that depends on lua-discount, so I got notified)

1:
https://anonscm.debian.org/cgit/pkg-lua/lua-discount.git/commit/?id=25d62151f8ed866ee938eb6e8191771b22e834ca

Thanks !

-- 
Jason Pleau

Bug#829597: [Pkg-clamav-devel] Bug#829597: clamav-daemon: LocalSocket not created.

[Sebastian Andrzej Siewior]

On 2016-07-04 10:37:01 [-0400], Gordon Dickens wrote:
> Dear Maintainer,
Hi Gordon,

> I just upgraded three Debian exim mail servers from clamav 0.99 to clamav 
> 0.99.2 and now all three mail servers are broken. That is, I have LocalSocket 
> defined in /etc/clamav/clamd.conf as follows:

and you remained on Jessie, correct?

> LocalSocket /var/run/clamav/clamd.ctl
> 
> However, the /var/run/clamav/clamd.ctl socket is never created on any of the 
> three systems. Furthermore, the /var/run/clamav directory is never created at 
> boot time either. So, could this be a systemd issue? The bottom line is that 
> clamav is now totally broken which has subsequently broken exim's virus 
> checking as well. freshclam reports the following in /var/log/freshclam.log:

You should have /run which is a tmpfs:
|$ mount|grep "run "
|tmpfs on /run type tmpfs (rw,nosuid,relatime,size=1607508k,mode=755)

and /var/run should be a symlink:

|$ ls -l /var/ | grep "run "
|lrwxrwxrwx  1 root root  4 Aug  3  2013 run -> /run

and since you run systemd there should be two service files:
|# systemctl status clamav-daemon.socket
|● clamav-daemon.socket - Socket for Clam AntiVirus userspace daemon
|   Loaded: loaded (/lib/systemd/system/clamav-daemon.socket; enabled)
|  Drop-In: /etc/systemd/system/clamav-daemon.socket.d
|   └─extend.conf
|   Active: active (running) since Thu 2016-05-26 22:35:00 CEST; 1 months 8 
days ago
| Docs: man:clamd(8)
|   man:clamd.conf(5)
|   http://www.clamav.net/lang/en/doc/
|   Listen: /var/run/clamav/clamd.ctl (Stream)
|
|Warning: Journal has been rotated since unit was started. Log output is 
incomplete or unavailable.
|# systemctl status clamav-daemon.service
|● clamav-daemon.service - Clam AntiVirus userspace daemon
|   Loaded: loaded (/lib/systemd/system/clamav-daemon.service; enabled)
|   Active: active (running) since Thu 2016-05-26 22:35:00 CEST; 1 months 8 
days ago
| Docs: man:clamd(8)
|   man:clamd.conf(5)
|   http://www.clamav.net/lang/en/doc/
| Main PID: 11021 (clamd)
|   CGroup: /system.slice/clamav-daemon.service
|   └─11021 /usr/sbin/clamd --foreground=true
|

If you read the .socket file then you will see that one creates the
socket and the .service file depends on it. Uppon start, systemd passes
the socket to clamd then. I *assume* that the socket part is not started
for some reason on your machines.

Sebastian

Bug#828979: pyosmium: FTBFS in testing (FAIL: test_location_tuple)

[Sebastiaan Couwenberg]

Control: tags -1 pending

Hi Santiago,

On 06/29/2016 05:47 PM, Sebastiaan Couwenberg wrote:
> Thanks for reporting this issue, I've forwarded it upstream.
> 
> I suspect the test failure is caused by changes in Python 2.7.12~rc1,
> because all the tests succeeded with Python 2.7.11.

I've added a patch to fix the test failure by changing the expected
output, that allows the tests to succeed on unstable and jessie (for the
backport). The patch has also been forwarded upstream.

Kind Regards,

Bas

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

Bug#829621: mdadm sends spurious "Fail event" messages on shutdown

[Dimitri John Ledkov]

Hello,

On 4 July 2016 at 20:26, Gábor Gombás  wrote:
> Package: mdadm
> Version: 3.4-1
> Severity: normal
>
> Hello,
>
> /lib/systemd/system/mdmonitor.service does not kill the monitoring
> daemon on shutdown, which results in spurious "Fail event" mails
> being sent while the arrays are being stopped by "/etc/init.d/mdadm-raid
> stop".
>

On systemd based systems, mdadm-raid script should not be used at
all... I believe it is currently possible to end up in such a
situation and I am working on fixing this and other problems related
to udev/initramfs/systemd/sysvinit integration of mdadm in debian
currently.

Regards,

Dimitri.


> Gabor
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (102, 'unstable'), (101, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.6.3 (SMP w/4 CPU cores; PREEMPT)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages mdadm depends on:
> ii  debconf [debconf-2.0]  1.5.59
> ii  initscripts2.88dsf-59.7
> ii  libc6  2.22-13
> ii  lsb-base   9.20160629
> ii  udev   230-2
>
> Versions of packages mdadm recommends:
> ii  kmod22-1.1
> ii  postfix [mail-transport-agent]  3.1.0-3
>
> mdadm suggests no packages.
>
> -- debconf information:
>   mdadm/initrdstart_msg_errexist:
>   mdadm/initrdstart_msg_errmd:
>   mdadm/initrdstart_notinconf: false
>   mdadm/initrdstart_msg_errconf:
> * mdadm/initrdstart: all
> * mdadm/start_daemon: true
>   mdadm/initrdstart_msg_intro:
> * mdadm/autocheck: true
> * mdadm/mail_to: root
>   mdadm/initrdstart_msg_errblock:
>
> ___
> pkg-mdadm-devel mailing list
> pkg-mdadm-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mdadm-devel



-- 
Regards,

Dimitri.

Bug#829638: usb-modeswitch: provide backport for jessie

[Michael Prokop]

Package: usb-modeswitch
Version: 2.4.0+repack0-1
Severity: wishlist

Hi,

in jessie we've usb-modeswitch version 2.2.0+repack0-2 but for a
systemd backport we're working on we've got a breaks on
usb-modeswitch (<< 2.3.0+repack0-1~), so it would be great if you
could provide a backport of usb-modeswitch 2.4.0+repack0-1 for
jessie-backports.

Same probably applies to usb-modeswitch-data 20160612-1 as well,
please let me know if you'd prefer a separate bug report about it.

(In terms of a build-dependencies a simple rebuild seems to be
enough.)

Thanks for consideration!

regards,
-mika-

Bug#829631:

[Ondrej Novy]

Thanks for your bugreport.

I uploaded newer version of python-funcsigs to experimental and added
versioned depends to python-mock package (git only for now).

-- 
Best regards
 Ondřej Nový

Bug#829591: hurd: pseudoterminal hangs when I press ^O (flush)

[Kalle Olavi Niemitalo]

Control: retitle -1 hurd: should clear discard-output flag when pseudoterminal 
is destroyed

Samuel Thibault noted that pressing ^O a second time makes the
terminal work again.  It turns out this is a documented feature.
https://www.gnu.org/software/libc/manual/html_node/Other-Special.html#index-VDISCARD
says:

> The DISCARD character is recognized only when IEXTEN is set,
> but in both canonical and noncanonical mode. Its effect is to
> toggle the discard-output flag. When this flag is set, all
> program output is discarded. Setting the flag also discards all
> output currently in the output buffer. Typing any other
> character resets the flag.
>
> This character is available on BSD systems and GNU/Linux and
> GNU/Hurd systems.

Contrary to this glibc documentation, typing another character
does not reset the flag on GNU/Hurd.  I don't know whether that
is a bug in Hurd.  IEEE Std 1003.1, 2013 Edition reserves the
VDISCARD name but does not say how it works.
http://www.unix.com/man-page/freebsd/4/termios/ describes the
DISCARD character but does not say that other characters reset
the flag.

Linux 3.16.0 has room for the DISCARD character in struct termios
but does not recognize it when typed, even if IEXTEN is set.
This explains why I was not familiar with the feature.

That leaves one problem: if I first set the discard-output flag
by pressing ^O, and then kill the ssh client so that the
processes using the pseudoterminal get SIGHUP and die, the flag
remains set.  If someone else then logs in via ssh and happens to
get the same tty/pty pair, they get neither /etc/motd nor the
shell prompt.  They can fix the situation by pressing ^O but
surely the discard-output should be cleared automatically.

In the hurd/term code, the flag is termflags & FLUSH_OUTPUT.
The flag is changed only in main.c (main), which initializes the
whole termflags variable, and in munge.c (input_character),
which toggles the flag if it gets the DISCARD character.
There is no ioctl that explicitly reports or changes the state of
the flag.  It is thus not feasible for sshd to clear the flag;
instead, the term translator should do that on its own.

Samuel Thibault suggests that the flag should be cleared in
ptyio.c (pty_po_destroy_hook) or users.c (po_destroy_hook).
I think pseudoterminals should entirely reinitialize termflags
and other terminal-specific state between sessions because that's
what would happen with /dev/pts/ (Debian bug#556550) too.
With other kinds of terminals ("device" or "hurdio"), one can
expect that the same device will remain connected, so it seems
better to preserve the terminal settings.

Bug#800634: [Pkg-opencl-devel] OpenCL architectures

[Rebecca N. Palmer]

Non-portable packages are required to fail to build on architectures 
where they can't work ( 
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#packages-arch-specific 
).  A build-dependency automatically does that (e.g. nodejs is arch:any, 
libv8 isn't), but one can't build-depend on virtual packages.


A third option would be

Architecture: any
Build-Depends: pocl-opencl-icd [!armhf !kfreebsd-i386]

which would also allow running the test suite (pocl is the CPU ICD, and 
hence the only one likely to work on a buildd).


(Not sure whether including ppc64el is allowed, as main can't depend on 
non-free)

Bug#711350: Solution to fake js device

[Matías Costa]

Dear mantainer, I found:

https://github.com/denilsonsa/udev-joystick-blacklist

It solved this problem with my keyboard, and btw it will be solved for a
lot of other people if included in the udev package.

Reporting this bug I found bug #635589 to be a duplicate of this one.

Thank you.

Bug#718284: [Pkg-mailman-hackers] Bug#718284: postfix-to-mailman: can't run genaliases properly (maybe doc bug?)

[Jérôme]

Hi.

I'm trying to configure Mailman and I just fell on this as well.

I want to use dedicated virtual subdomains like

@lists.virtual_dom_1.tld
@lists.virtual_dom_2.tld

and I thought following the advices in files

/usr/share/doc/mailman/README.Debian
/etc/mailman/postfix-to-mailman.py

would lead me to it, as it reads

--

Postfix
---
For those using postfix who are able to devote a full subdomain
lists.example.com for use by Mailman, please see the comments in
/etc/mailman/postfix-to-mailman.py .

--

IIUC, this method is broken.

I guess I'll have to find my way through Postfix/Mailman configuration.

Maybe those files ought to be updated to remove (or better, fix) the
instructions they provide.

Thanks.

-- 
Jérôme

Bug#829630: O: pythonqt

[Scott Kitterman]

On Monday, July 04, 2016 10:08:47 PM Andreas Tille wrote:
> Package: wnpp
> Severity: normal
> 
> Hi,
> 
> the package pythonqt was once a dependency of a Debian Med package but
> this was removed.  Now pythonqt has no rdepends any more and is hard to
> maintain since it needs Qt4.  May be its the best to remove the package
> at all from Debian.  If anybody (may be Debian Python) might like to
> take over the package that's perfectly fine.
> 
> Currently the packaging remains in Debian Med SVN
> 
> svn://anonscm.debian.org/debian-med/trunk/packages/pythonqt/trunk/
> 
> I tried to convert it to Git but svn2git failed and I gave up since
> spending more time into the package does not sound sensible to me.

Removal sounds best to me.

Scott K

Bug#829636: ITP: fatx -- Complete XBOX filesystem support (FATX)

[Christophe DUVERGER]

Package: wnpp
Severity: wishlist
Owner: Christophe Duverger 

* Package name: fatx
  Version : 1.11
  Upstream Author : Christophe Duverger 
* URL : http://sourceforge.net/projects/fatx
* License : GPL
  Programming Lang: C++
  Description : Complete XBOX filesystem support (FATX)

 Includes:
 fusefatx: filesystem mounting using fuse,
 mkfs.fatx: make filesystem,
 fsck.fatx: check and correct filesystem,
 label.fatx: change or display volume name,
 unrm.fatx: undelete files

Bug#827707: duck: Should not report sites which are available via HTTPS but redirect from HTTPS to HTTP

[Simon Kainz]

tags 827707 pending
thanks

This issue is fixed and currently in the repo, commit
bda736a6cad1807b2a20d03ae2a99b1b31cc3b38 [1]

Bye,

Simon


Am 2016-06-20 um 20:35 schrieb Simon Kainz:
> Hello,
> 
> thanks for this suggestion, but i think there is a bug in detecting, if
> a given website offers the same content via HTTPS as via HTTP:
> 
> My check should *not* allow/follow a redirect back to HTTP if i am
> checking for content via HTTPS, so this is clearly a bug. If this would
> be working correctly, the issue you mentioned should not be possible.
> 
> I will fix this - either by fixing my check routines or by following
> your suggestion.
> 
> Thanks,
> Simon
> 
> 
> Am 2016-06-20 um 02:39 schrieb Axel Beckert:
>> Package: duck Version: 0.9 Severity: wishlist
>>
>> Dear Maintainer,
>>
>> duck reported the following for the screen package:
>>
>> I: debian/patches/52fix_screen_utf8_nfd.patch:10: URL:
>> http://d.hatena.ne.jp/mrkn/20101014/fix_screen_utf8_nfd_bug:
>> INFORMATION (Certainty:possible) The web page at
>> http://d.hatena.ne.jp/mrkn/20101014/fix_screen_utf8_nfd_bug works,
>> but is also available via
>> https://d.hatena.ne.jp/mrkn/20101014/fix_screen_utf8_nfd_bug, please
>> consider switching to HTTPS urls.
>>
>> But https://d.hatena.ne.jp/mrkn/20101014/fix_screen_utf8_nfd_bug 
>> redirects back to 
>> http://d.hatena.ne.jp/mrkn/20101014/fix_screen_utf8_nfd_bug
>>
>> So if I change this as recommend, I get again a warning:
>>
>> I: debian/patches/52fix_screen_utf8_nfd.patch:10: URL:
>> https://d.hatena.ne.jp/mrkn/20101014/fix_screen_utf8_nfd_bug:
>> INFORMATION (Certainty:possible) Secure URL redirects to an insecure
>> URL: https://d.hatena.ne.jp -> http://d.hatena.ne.jp
>>
>> I suggest to avoid the initial warning if HTTPS redirects back to
>> HTTP, but keep the latter warning.
>>
>> -- System Information: Debian Release: stretch/sid APT prefers
>> unstable APT policy: (990, 'unstable'), (600, 'testing'), (500,
>> 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'),
>> (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture:
>> amd64 (x86_64)
>>
>> Kernel: Linux 4.6.0-trunk-amd64 (SMP w/8 CPU cores) Locale:
>> LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked
>> to /bin/dash Init: sysvinit (via /sbin/init)
>>
>> Versions of packages duck depends on: ii  devscripts
>> 2.16.5 ii  dpkg-dev 1.18.7 ii
>> libconfig-inifiles-perl  2.89-1 ii  libconfig-simple-perl
>> 4.59-6 ii  libdomain-publicsuffix-perl  0.10-1 ii
>> libfile-which-perl   1.21-1 ii  libmailtools-perl
>> 2.13-1 ii  libnet-dns-perl  1.05-2 ii
>> libparse-debcontrol-perl 2.005-4 ii  libpath-class-perl
>> 0.36-1 ii  libregexp-common-email-address-perl  1.01-4 ii
>> libregexp-common-perl2016060801-1 ii
>> libstring-similarity-perl1.04-1+b3 ii  libwww-curl-perl
>> 4.17-2+b1 ii  libxml-xpath-perl1.36-1 ii
>> libyaml-libyaml-perl 0.41-6+b1 ii  lynx
>> 2.8.9dev9-1 ii  perl 5.22.2-1 ii
>> publicsuffix 20160613-1
>>
>> duck recommends no packages.
>>
>> Versions of packages duck suggests: ii  bzr 2.7.0-7 ii  git
>> 1:2.8.1-1 ii  mercurial   3.8.3-1 ii  subversion  1.9.4-1
>>
>> -- no debconf information
>>
> 

Bug#816720: Bug##816720: gail-common: provide udeb for accessibility

[Samuel Thibault]

Hello,

Ping?

Samuel

Samuel Thibault, on Sun 20 Mar 2016 17:48:05 +0100, wrote:
> Samuel Thibault, on Sun 20 Mar 2016 17:20:19 +0100, wrote:
> > Michael Biebl, on Sun 20 Mar 2016 03:05:55 +0100, wrote:
> > > Related to  that, the generated shlibs file for libgail8 has
> > > 
> > > > libgailutil 18 libgail18 (>= 2.24.0), libgail-common (>= 2.24.0)
> > > > udeb: libgailutil 18 libgail18-udeb (>= 2.24.0), libgail-common (>= 
> > > > 2.24.0)
> > > 
> > > The udeb line is broken, as it produces a dependency on a non-udeb 
> > > package.
> > 
> > Uh. The rules file indeed uses
> > 
> > dh_makeshlibs -plibgail18 \
> > -X$(MODULES_BASE_PATH) \
> > -V"libgail18 (>= $(SHVER)), libgail-common (>= $(SHVER))" \
> > -- -c4
> > 
> > My addition of --add-udeb=libgail18-udeb replaces libgail18 by
> > libgail18-udeb on the udeb line, but I don't see any way to make
> > dh_makeshlibs either drop the libgail-common dependency or replace it
> > with libgaim-common-udeb... Debhelper maintainers, any idea?
> > In the meanwhile, we can use a horrible sed hack :/
> 
> It works with the attached patch.
> 
> Samuel
Index: debian/control
===
--- debian/control  (révision 47627)
+++ debian/control  (copie de travail)
@@ -254,6 +254,22 @@
  .
  This package contains the shared library.
 
+Package: libgail18-udeb
+Package-Type: udeb
+Architecture: any
+Depends: ${misc:Depends},
+ ${shlibs:Depends},
+ libgtk2.0-0-udeb (= ${binary:Version})
+Multi-Arch: same
+Pre-Depends: ${misc:Pre-Depends}
+Description: GNOME Accessibility Implementation Library -- shared libraries
+ Gail implements ATK interfaces for GTK+ widgets which are dynamically
+ loadable at runtime by a GTK+ application. Once loaded, those parts of
+ an application that use standard GTK+ widgets will have a basic level
+ of accessibility, without the need to modify the application at all.
+ .
+ This package contains the shared library for the Debian installer.
+
 Package: libgail-common
 Architecture: any
 Depends: ${misc:Depends},
Index: debian/control.in
===
--- debian/control.in   (révision 47627)
+++ debian/control.in   (copie de travail)
@@ -254,6 +254,22 @@
  .
  This package contains the shared library.
 
+Package: libgail18-udeb
+Package-Type: udeb
+Architecture: any
+Depends: ${misc:Depends},
+ ${shlibs:Depends},
+ @UDEB_PKG@ (= ${binary:Version})
+Multi-Arch: same
+Pre-Depends: ${misc:Pre-Depends}
+Description: GNOME Accessibility Implementation Library -- shared libraries
+ Gail implements ATK interfaces for GTK+ widgets which are dynamically
+ loadable at runtime by a GTK+ application. Once loaded, those parts of
+ an application that use standard GTK+ widgets will have a basic level
+ of accessibility, without the need to modify the application at all.
+ .
+ This package contains the shared library for the Debian installer.
+
 Package: libgail-common
 Architecture: any
 Depends: ${misc:Depends},
Index: debian/libgail18-udeb.install.in
===
--- debian/libgail18-udeb.install.in(nonexistent)
+++ debian/libgail18-udeb.install.in(copie de travail)
@@ -0,0 +1,2 @@
+debian/install/shared_udeb/@LIBDIR@/libgail*.so.* @LIBDIR@
+debian/install/shared_udeb/@LIBDIR@/gtk-@APIVER@/modules/*.so 
@LIBDIR@/gtk-@APIVER@/modules
Index: debian/rules
===
--- debian/rules(révision 47627)
+++ debian/rules(copie de travail)
@@ -81,7 +81,7 @@
 
 # package groups, used in rule dependencies and in cleanup
 BINARY_INDEP_PKGS := $(COMMON_PKG) $(DOC_PKG) libgail-doc
-BINARY_ARCH_PKGS := $(SHARED_PKG) $(BIN_PKG) $(UDEB_PKG) $(DEV_PKG) 
$(DEBUG_PKG) $(EXAMPLES_PKG) $(PIXBUF_PKG) gir1.2-gtk-2.0 libgail18 libgail-dbg 
libgail-dev libgail-common
+BINARY_ARCH_PKGS := $(SHARED_PKG) $(BIN_PKG) $(UDEB_PKG) $(DEV_PKG) 
$(DEBUG_PKG) $(EXAMPLES_PKG) $(PIXBUF_PKG) gir1.2-gtk-2.0 libgail18 
libgail18-udeb libgail-dbg libgail-dev libgail-common
 ALL_PKGS := $(BINARY_INDEP_PKGS) $(BINARY_ARCH_PKGS)
 
 # list of flavors we build; each gets a builddir, a configure pass (configure
@@ -287,9 +287,9 @@
dh_installman -s
dh_installexamples -s
dh_link -s
-   dh_strip -s --dbg-package=$(DEBUG_PKG) -N$(UDEB_PKG) -Nlibgail18 
-Nlibgail-common
+   dh_strip -s --dbg-package=$(DEBUG_PKG) -N$(UDEB_PKG) -Nlibgail18 
-Nlibgail18-udeb -Nlibgail-common
dh_strip -plibgail18 -plibgail-common --dbg-package=libgail-dbg
-   dh_strip -p$(UDEB_PKG)
+   dh_strip -p$(UDEB_PKG) -plibgail18-udeb
dh_compress -s -X.sgml -X.devhelp
dh_fixperms -s -X$(LIBDIR)/$(SHARED_PKG)
dh_makeshlibs -p$(SHARED_PKG) \
@@ -300,7 +300,9 @@
dh_makeshlibs -plibgail18 \
-X$(MODULES_BASE_PATH) \

Bug#829618: pulseaudio: FTBFS on systems with dynamic CPU configurations

[John Paul Adrian Glaubitz]

Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=96809

On 07/04/2016 08:52 PM, Felipe Sateler wrote:
>> I will report this bug upstream,
> 
> Yes please.

Done. Set the forwarded tag of this bug report accordingly.

> Are there systems where _SC_NPROCEESSORS_CONF is available but
> _SC_NPROCEESSORS_ONLN isn't? If so, this should probably be a new
> case, not replace the existing one.

Since the glibc manual explicitly recommends using _SC_NPROCESSORS_ONLN
over _SC_NPROCESSORS_CONF [1], I don't think we should fear any regressions.

_SC_NPROCESSORS_ONLN is also available on FreeBSD [2] as well as on
GNU/Hurd [3]. I also think that it would make sense to call the
variable _SC_NPROCESSORS_CONF and not just _SC_NPROCESSORS if on
a system which has _SC_NPROCESSORS_ONLN.

> I may be a bit slow in uploading, so feel free to NMU this change if
> you want it faster.

Thanks, will do that now.

Adrian

> [1] 
> https://www.gnu.org/software/libc/manual/html_node/Processor-Resources.html
> [2] https://www.freebsd.org/cgi/man.cgi?query=sysconf=3
> [3] 
> http://www.hpl.hp.com/hosted/linux/mail-archives/gc/2007-August/001835.html

-- 
 .''`.  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#829635: lintian: FTBFS: dpkg-source: error: syntax error in .../debian/tests/control

[Jakub Wilk]

Source: lintian
Version: 2.5.45
Severity: serious
Justification: fails to build from source

lintian FTBFS when built against dpkg-dev_1.18.9, because the following 
tests fail:


* tests::testsuite-control-not-file
| dpkg-buildpackage: info: source package testsuite-control-not-file
| dpkg-buildpackage: info: source version 1.0
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by Debian Lintian Maintainers 

|  dpkg-source -iNEVER_MATCH_ANYTHING -INEVER_MATCH_ANYTHING --auto-commit 
--before-build testsuite-control-not-file-1.0
| dpkg-buildpackage: info: host architecture i386
| dpkg-source: error: test control debian/tests/control is not a regular file
| dpkg-buildpackage: error: dpkg-source -iNEVER_MATCH_ANYTHING 
-INEVER_MATCH_ANYTHING --auto-commit --before-build 
testsuite-control-not-file-1.0 gave error exit status 255

* tests::testsuite-control-syntax
| dpkg-buildpackage: info: source package testsuite-control-syntax
| dpkg-buildpackage: info: source version 1.0
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by Debian Lintian Maintainers 

|  dpkg-source -iNEVER_MATCH_ANYTHING -INEVER_MATCH_ANYTHING --auto-commit 
--before-build testsuite-control-syntax-1.0
| dpkg-buildpackage: info: host architecture i386
| dpkg-source: error: syntax error in 
testsuite-control-syntax-1.0/debian/tests/control at line 1: line with unknown 
format (not field-colon-value)
| dpkg-buildpackage: error: dpkg-source -iNEVER_MATCH_ANYTHING 
-INEVER_MATCH_ANYTHING --auto-commit --before-build 
testsuite-control-syntax-1.0 gave error exit status 25

* tests::testsuite-general:
| dpkg-buildpackage: info: source package testsuite-general
| dpkg-buildpackage: info: source version 1.0
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by Debian Lintian Maintainers 

|  dpkg-source -iNEVER_MATCH_ANYTHING -INEVER_MATCH_ANYTHING --auto-commit 
--before-build testsuite-general-1.0
| dpkg-buildpackage: info: host architecture i386
| dpkg-source: error: syntax error in 
testsuite-general-1.0/debian/tests/control at line 26: block lacks either Tests 
or Test-Command fields
| dpkg-buildpackage: error: dpkg-source -iNEVER_MATCH_ANYTHING 
-INEVER_MATCH_ANYTHING --auto-commit --before-build testsuite-general-1.0 gave 
error exit status 25

--
Jakub Wilk

Bug#829634: collectd: Please rebuild with linux-libc-dev >= 4.6

[Gábor Gombás]

Package: collectd
Version: 5.5.1-4
Severity: normal

Hi,

The size of the rtnl_link_stats64 structure changed in Linux 4.6 by
commit 6e7333d315a768170a59ac771297ee0551bdddbf, which causes the
netlink plugin to fail:

Jul  4 22:14:28 host collectd[3022]: netlink plugin: link_filter_cb: 
IFLA_STATS64 mnl_attr_validate2 failed.
Jul  4 22:14:28 host collectd[3022]: netlink plugin: ir_read: 
mnl_socket_recvfrom failed.
Jul  4 22:14:28 host collectd[3022]: read-function of plugin `netlink' failed. 
Will suspend it for 120.000 seconds.

Recompiling with headers from 4.6 should fix this (and would make the
plugin fail with older kernels). The right fix would be to handle such
structure extensions gracefully, but after a quick look, the libmnl
library which the netlink plugin uses does not seem to have built-in
support for that.

Gabor

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

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

Versions of packages collectd depends on:
ii  collectd-core  5.5.1-4
ii  libc6  2.22-13
ii  librrd81.6.0-1

Versions of packages collectd recommends:
pn  default-jre-headless  
ii  iptables  1.6.0-2
ii  libatasmart4  0.19-4
ii  libcurl3-gnutls   7.47.0-1
ii  libdbi1   0.9.0-4
pn  libesmtp6 
pn  libganglia1   
ii  libgcrypt20   1.7.1-2
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.48.1-1
pn  libhiredis0.13
ii  libldap-2.4-2 2.4.42+dfsg-2+b2
ii  liblvm2app2.2 2.02.156-1
pn  libmemcached11
ii  libmnl0   1.0.3-5
pn  libmodbus5
ii  libmysqlclient18  5.6.30-1
ii  libnotify40.7.6-2
ii  libnspr4  2:4.12-2
ii  libnss3   2:3.23-2
pn  libopenipmi0  
pn  liboping0 
pn  libowcapi-3.1-1   
ii  libpcap0.81.7.4-2
ii  libperl5.22   5.22.2-1
ii  libpq59.5.3-1
ii  libprotobuf-c11.2.1-1
ii  libpython2.7  2.7.12-1
pn  librabbitmq4  
pn  librdkafka1   
ii  librrd8   1.6.0-1
ii  libsensors4   1:3.4.0-3
pn  libsigrok2
ii  libsnmp30 5.7.3+dfsg-1.4
ii  libssl1.0.2   1.0.2h-1
pn  libtokyotyrant3   
ii  libudev1  230-2
pn  libupsclient4 
pn  libvarnishapi1
ii  libvirt0  2.0.0-1
ii  libxml2   2.9.3+dfsg1-1.2
ii  libyajl2  2.1.0-2
ii  zlib1g1:1.2.8.dfsg-2+b1

collectd suggests no packages.

-- Configuration Files:
/etc/collectd/collectd.conf changed [not included]

-- no debconf information

Bug#817973: icedove not playing nice with GNOME default app mechanism

[Carsten Schoenert]

Control: tags 817973 pending

Hello Laurent,

On Sat, Mar 12, 2016 at 11:40:56PM +0100, Laurent Bigonville wrote:
> Le 12/03/16 12:15, Carsten Schoenert a écrit :
> > Hello Laurent,
> > 
> > On Sat, Mar 12, 2016 at 11:03:46AM +0100, Laurent Bigonville wrote:
> > > Hi,
> > > 
> > > I quickly tested with the Fedora LiveCD and I cannot reproduce this.
> > > 
> > > In the mimeapps.list, I see there they are using
> > > mozilla-thunderbird.desktop, also I don't see any userapp-*.desktop file 
> > > is
> > > created.
> > > 
> > > Could this be an issue with the rebranding?
> > maybe, but currently I don't think so. But I'm not that deep familar
> > with the respective source code at the moment.
> > 
> > As we currently thinking about the re re-branding back to Thunderbird I
> > wont spent much time on this issue until we came to a final decision.
> > The removing of the branding is a lot of work especially as we are on
> > starting of a new ESR version and we have to check the three platforms
> > for a hopefully successful build.
> > 
> > But sadly I must confirm your report. ;)
> 
> MMh, apparently firefox is doing the same (firefox pkg 45 from debian)

I think I know why this is happen.
Since several versions we dont ship the default preference
'mail.shell.checkDefaultClient' with a value 'false'. I don't know why,
it's probably no once before got attraction on this.

You can disable this as default in the file /etc/icedove/pref/icedove.js
by adding the value

  pref("mail.shell.checkDefaultClient", false);

or switch the check of by changing the setting within your user
settings.

  https://support.mozilla.org/en-US/kb/make-thunderbird-default-mail-client

We will probaly not fix this in the next Icedove version as we prepare
the de-branding of Icedove back to Thundebird.
After turning of the check you can safely remove the extra file in 

  ~/.local/share/applications/userapp-Icedove-3UJNEY.desktop

and associations in

  ~/.local/share/applications/mimeapps.list
or
  ~/.config/mimeapps.list

Regards
Carsten

Bug#829557: [Pkg-xfce-devel] Bug#829557: firefox: error box at start-up / D-BUS related issue

[Simon McVittie]

On Mon, 04 Jul 2016 at 21:22:01 +0200, Yves-Alexis Perez wrote:
> One thing I've noticed is that system --user session keeps running after the
> session is ended

It keeps running as long as any processes from your login-session (look
for "session-*.slice" in systemd-cgls output) are still running. The
services it started (including dbus.service if you have dbus-user-session)
persist as long as it does.

You can use KillUserProcesses=yes in /etc/systemd/logind.conf if you
want logind to terminate everything in your login session when lightdm
tells it that you have logged out. (This breaks screen, tmux and similar,
which rely on processes inside your login-session persisting longer than
the login-session itself, unless you start their servers as their own
logind sessions.)

A dbus-daemon that was started in the traditional way, by dbus-launch,
has no particular connection with systemd life-cycles: it's part of the
login session just like your window manager (and so is dbus-launch
itself), and it gets terminated when dbus-launch is disconnected from
the X11 server.

S

Bug#829633: license-reconcile: Missing depends on licensecheck

[Jeremy Bicha]

Package: license-reconcile
Version: 0.10

licensecheck from devscripts has been split off into a separate
package. devscripts recommends licensecheck but autopkgtest does not
install recommends by default. Therefore, license-reconcile's
autopkgtest will fail as of devscripts 2.16.6.

You can see this in Ubuntu (it hasn't hit debci yet):

http://autopkgtest.ubuntu.com/packages/l/license-reconcile/yakkety/amd64/

I believe the easy fix is just to have license-reconcile depend on licensecheck.

Thanks,
Jeremy Bicha

Bug#518002: [Pkg-dns-devel] Bug#518002: Add apparmor profile for unbound

[Robert Edmonds]

Nicolas Braud-Santoni wrote:
> On Mon, Feb 22, 2016 at 11:08:30AM -0500, Simon Deziel wrote:
> > > Note that Simon and Nicolas have refreshed this profile recently:
> > > https://code.launchpad.net/~sdeziel/apparmor-profiles/refresh-unbound/+merge/268924
> > 
> > It was further refreshed for unbound 1.5.7:
> > https://bazaar.launchpad.net/~apparmor-dev/apparmor-profiles/master/view/head:/ubuntu/16.04/usr.sbin.unbound
> 
> It was again touched up very recently.
> 
> I tested the last revision (168.1.1) on Debian sid,
> and did not encounter any issues.
> 
> It is, however, missing the usual local/usr.sbin.haveged include.
> I will send a patch back upstream.
> 
> In any case, it seems reasonable to add the profile (with the local
> include) now.
> 
> 
> Sorry this bug somewhat fell to the wayside, but I would rather
> see this added now rather than never  ;)
> 
> 
> Best,
> 
>   nicoo

Hi, nicoo:

I'd be happy to ship an apparmor profile for unbound in the Debian
package. Can you please send a patch that applies to the master branch
of the packaging repository?

https://anonscm.debian.org/cgit/pkg-dns/unbound.git/

-- 
Robert Edmonds
edmo...@debian.org

Bug#829632: neat: please make the build reproducible

[Chris Lamb]

Source: neat
Version: 2.0-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Whilst working on the "reproducible builds" effort [0], we noticed that neat 
could not be built reproducibly.

Patch attached.

 [0] https://wiki.debian.org/ReproducibleBuilds


Regards,

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


neat.diff.txt
Description: Binary data

Bug#829631: python-mock: Depends on funcsigs 1 but Debian only has 0.4-2

[Jeremy Bicha]

python-funcsigs has been Github-forked

from:
https://github.com/aliles/funcsigs/commits/master

to:
https://github.com/testing-cabal/funcsigs/commits/master

Thanks,
Jeremy

Bug#828177: jessie-pu: package unbound/1.4.22-3+deb8u2

[Robert Edmonds]

Robert Edmonds wrote:
> Julien Cristau wrote:
> > May I take the opportunity to ask you to also fix the 'stop' action from
> > the init script?
> > 
> > We've been using this patch on the debian.org hosts for a year now.
> > Previously restarting the service would quite often result in no running
> > unbound, because (AIUI) systemd doesn't use the init script 'restart'
> > action (uses stop && start instead), the 'stop' action would not wait
> > for the process to actually die before returning, and then 'start' would
> > say "I'm already running, nothing to do".
> 
> Wow, thanks for pointing that out. Yes, I'd be happy to fix that one too
> in a stable update.

Here is the updated debdiff for the package I'd like to upload to
jessie.

diff -Nru unbound-1.4.22/debian/changelog unbound-1.4.22/debian/changelog
--- unbound-1.4.22/debian/changelog 2016-02-21 18:43:22.0 -0500
+++ unbound-1.4.22/debian/changelog 2016-07-04 15:58:35.0 -0400
@@ -1,3 +1,11 @@
+unbound (1.4.22-3+deb8u2) jessie; urgency=medium
+
+  * debian/unbound.init: Add "pidfile" magic comment (Closes: #807132)
+  * debian/unbound.init: Call start-stop-daemon with --retry for 'stop'
+action (patch from Julien Cristau)
+
+ -- Robert Edmonds   Mon, 04 Jul 2016 15:58:01 -0400
+
 unbound (1.4.22-3+deb8u1) jessie; urgency=medium
 
   * iterator/iter_hints.c: Update hints for H.ROOT-SERVERS.NET
diff -Nru unbound-1.4.22/debian/patches/debian-changes 
unbound-1.4.22/debian/patches/debian-changes
--- unbound-1.4.22/debian/patches/debian-changes2016-02-22 
10:58:04.0 -0500
+++ unbound-1.4.22/debian/patches/debian-changes2016-07-04 
16:06:41.0 -0400
@@ -5,12 +5,13 @@
  information below has been extracted from the changelog. Adjust it or drop
  it.
  .
- unbound (1.4.22-3+deb8u1) jessie; urgency=medium
+ unbound (1.4.22-3+deb8u2) jessie; urgency=medium
  .
-   * iterator/iter_hints.c: Update hints for H.ROOT-SERVERS.NET
- (Closes: #815370)
+   * debian/unbound.init: Add "pidfile" magic comment (Closes: #807132)
+   * debian/unbound.init: Call start-stop-daemon with --retry for 'stop'
+ action (patch from Julien Cristau)
 Author: Robert Edmonds 
-Bug-Debian: https://bugs.debian.org/815370
+Bug-Debian: https://bugs.debian.org/807132
 
 ---
 The information above should follow the Patch Tagging Guidelines, please
@@ -23,7 +24,7 @@
 Bug-Ubuntu: https://launchpad.net/bugs/
 Forwarded: 
 Reviewed-By: 
-Last-Update: 
+Last-Update: 2016-07-04
 
 --- unbound-1.4.22.orig/acx_python.m4
 +++ unbound-1.4.22/acx_python.m4
diff -Nru unbound-1.4.22/debian/unbound.init unbound-1.4.22/debian/unbound.init
--- unbound-1.4.22/debian/unbound.init  2016-02-21 18:43:22.0 -0500
+++ unbound-1.4.22/debian/unbound.init  2016-07-04 15:58:35.0 -0400
@@ -7,6 +7,7 @@
 # Default-Start: 2 3 4 5
 # Default-Stop:  0 1 6
 ### END INIT INFO
+# pidfile: /run/unbound.pid
 
 NAME=unbound
 DESC="recursive DNS server"
@@ -121,7 +122,7 @@
 stop)
 if $UNBOUND_ENABLE; then
 log_daemon_msg "Stopping $DESC" "$NAME"
-if start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE 
--name $NAME; then
+if start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE 
--name $NAME --retry 5; then
 do_resolvconf_stop
 log_end_msg 0
 else

-- 
Robert Edmonds
edmo...@debian.org

Bug#506859: bz2: BZ2File should expose compression level as an attribute

[Josh Triplett]

Control: tags -1 + upstream
Control: forwarded 506859 https://bugs.python.org/issue27451
Control: forwarded 507943 https://bugs.python.org/issue27450

On Mon, Jul 04, 2016 at 04:05:54PM +0200, Matthias Klose wrote:
> Control: tags -1 + wontfix
> 
> so you don't reply for about seven years, and then just re-open the issue
> without any other action?  Sorry, but please file this upstream.  This is
> nothing to fix in Debian, and I assume upstream will reject that as well at
> least for 2.7.

I had reopened these issues after carefully checking the current
versions of both python2.7 and python3.5 to confirm that they still
exist in those versions.  (I should have included a comment to that
effect in the bts invocation.)  Several of the other bugs closed had
long since been forwarded to upstream, fixed, and included in Debian; I
checked those too, and didn't reopen them.  I was already planning to
file these upstream today and mark them forwarded, and I had appreciated
the reminder that I'd lost track of these.

I've now forwarded these upstream as https://bugs.python.org/issue27450
and https://bugs.python.org/issue27451 .  I've tagged and forwarded the
BTS bugs accordingly for reference, though I haven't reopened them to
avoid playing ping-pong.  (Personally, I prefer to track things
consistently in the Debian BTS, rather than a thousand different
upstream bug trackers, but that's your call as the maintainer.)

Bug#829630: O: pythonqt

[Andreas Tille]

Package: wnpp
Severity: normal

Hi,

the package pythonqt was once a dependency of a Debian Med package but
this was removed.  Now pythonqt has no rdepends any more and is hard to
maintain since it needs Qt4.  May be its the best to remove the package
at all from Debian.  If anybody (may be Debian Python) might like to
take over the package that's perfectly fine.

Currently the packaging remains in Debian Med SVN

svn://anonscm.debian.org/debian-med/trunk/packages/pythonqt/trunk/

I tried to convert it to Git but svn2git failed and I gave up since
spending more time into the package does not sound sensible to me.

Kind regards

  Andreas.

Bug#829631: python-mock: Depends on funcsigs 1 but Debian only has 0.4-2

[Jeremy Bicha]

Package: python-mock
Version: 2.0.0-1

The first line of python-mock's requirements.txt has this line:
funcsigs>=1;python_version<"3.3"

python-mock does depend on funcsigs but the version of funcsigs in
Debian is only 0.4-2.

I think this is making various builds fail in Ubuntu (which synced
python-mock from experimental), such as python-acme (see
https://bugs.debian.org/829285 ) and tryton-server:


https://launchpadlibrarian.net/266703082/buildlog_ubuntu-yakkety-amd64.tryton-server_4.0.1-1_BUILDING.txt.gz

make[1]: Leaving directory '/«PKGBUILDDIR»'
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py test
running test
Searching for funcsigs>=1

Note: Bypassing https://pypi.python.org/simple/funcsigs/ (disallowed
host; see http://bit.ly/1dg9ijs for details).

Couldn't find index page for 'funcsigs' (maybe misspelled?)
Scanning index of all packages (this may take a while)

Note: Bypassing https://pypi.python.org/simple/ (disallowed host; see
http://bit.ly/1dg9ijs for details).

No local packages or download links found for funcsigs>=1
error: Could not find suitable distribution for Requirement.parse('funcsigs>=1')
E: pybuild pybuild:274: test: plugin distutils failed with: exit
code=1: python2.7 setup.py test
dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir .
returned exit code 13


Thanks,
Jeremy Bicha

Bug#796585: #796585: aoetools: Has init script in runlevel S but no matching service file

[Christian Hofstaedtler]

* Christian Hofstaedtler  [160704 20:01]:
> I'm attaching a debdiff of something that -works-, but causes a
> 60sec wait for AoE mount points listed in fstab (with
> defaults,_netdev).

After some additional debugging I found aoe-discover.service starts
too early, just before my network interface has an IP address (from
DHCP). Even with After=network-online.target.

Calling aoe-discover from /etc/network/if-up.d improves this for me
to a "works fine at every other boot" situation.

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#828807: newlisp: FTBFS on powerpc: test suite segmentation fault

[Aaron M. Ucko]

Sergio Durigan Junior  writes:

> I can't reproduce this.  I believe it may have something to do with the
> machine it was built.  I'll upload a fix for the other bugs soon, and
> see how the ppc build performs.  Depending on the results I'll close
> this bug.

OK, thanks.  Alas, it looks like this failure's still occurring.  (The
other builds look good, though a couple of non-release architectures ran
into a dpkg-dev bug.)

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#829629: ITP: ruby-hamlit -- High Performance Haml Implementation

[Abhijith PA]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: wnpp
Severity: wishlist
Owner: Abhijith PA 


* Package name: ruby-hamlit
  Version : 2.5.0
  Upstream Author : Takashi Kokubun,Hampton Catlin,Natalie Weizenbaum
* URL or Web page : https://github.com/k0kubun/hamlit/tree
* License : MIT
  Programming Lang: Ruby
  Description : High Performance Haml Implementation
- -- 
 അഭി‍ജിത്ത് പി എ
GPG Key: EF13 EA26 A698 FF35 FD7C  902E 863D 4DF2 ED9C 28EF
more about me: newbeast.ml
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXesDUAAoJEIY9TfLtnCjvY3AP/RJeXmdTIjgU4FkDBelLIJti
tc/AjIRpBEfBjN91vgZTlgS77jSCWhsjmsX7bHslMmOpvNtJmvVnsb44e0ODLQd8
V8RYwSvTJtiwyUW0HJm4ltXfreLyL3GwmXgkZwdIP0IEeMdnYGrgOv9y4kCpswWC
1/UD44dQkyreeiPBu83uA/kcwR2hPmmxOQBSBIX3ebVKVBMHR91EdvXcLRsXyw1A
Un1DhamqJEijfKcx9MM93bf3BhA0QxbWkR1kD0juzuIWibpJYhju3OGJvwRa2yv4
lVU1UBO14pVIRUW2gRRdNGGyytmC2VF/jRN1rOD1lWi/fXtFF27L/kCI+5z0QGFu
als0t8k0bYcrEihclPGsRUjoUI2umZXcnGM6mEK1/q255dJW6BS9cDPS4PzlQCnE
KWuTX7HiTy4nWUyNSgo4PXPoo1eqxqRaQBoJTN8dicJCjJ0tJy1k7gIUQKlEct9Y
GIPnQakkOKoYHixMVldoLnIwc5hkN6tTJ8WlVfWfpxonK1Ldz+SDv/sRb7JgV14e
ADU0lwZt5etblLFF37FW8l3D5FkQB0E/LRFyrH9/DG9If4YGxfjCNBxJmvI7FcOA
tGjsnb8ICUINdKovlA+eG8jcu/LRbPVVuvtXDNM7VH/fhGfWuF5YIvhYviSouAWV
fUX63TjuwG7hRD7GGR1B
=ti6v
-END PGP SIGNATURE-

Bug#829628: irsim: please make the build reproducible

[Chris Lamb]

Source: irsim
Version: 9.7.93-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Whilst working on the "reproducible builds" effort [0], we noticed that irsim 
could not be built reproducibly.

Patch attached; the previous one was incomplete.

 [0] https://wiki.debian.org/ReproducibleBuilds


Regards,

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


irsim.diff.txt
Description: Binary data

Bug#829622: [Debian-med-packaging] Bug#829622: consensuscore2: FTBFS on hurd-i386: 'dict' object has no attribute 'iteritems'

[Afif Elghraoui]

على الإثنين  4 تـمـوز 2016 ‫12:08، كتب Aaron M. Ucko:
> Source: consensuscore2
> Version: 0.12.0-1
> Severity: important
> Justification: fails to build from source
> 
> The hurd-i386 build of consensuscore2 failed when trying to install
> the Python 3 module:
> 
[...]
> 
> The dict.iteritems method is only available in Python 2.x, but it
> looks like the (Linux) i386 build was unaffected because it didn't
> invoke setup.py here at all:
> 
>  dh_auto_install -a -O--buildsystem=pybuild
>   I: pybuild base:184: dh_auto_install --buildsystem=cmake 
> --builddirectory="/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build" 
> --destdir="/«PKGBUILDDIR»/debian/python-consensuscore2" -- 
>   I: pybuild base:184: dh_auto_install --buildsystem=cmake 
> --builddirectory="/«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build" 
> --destdir="/«PKGBUILDDIR»/debian/python3-consensuscore2" -- 
>  dh_install -a -O--buildsystem=pybuild
> 
> I'm not sure offhand why not.  Could you please take a look?
> 

It looks like the linux i386 python module packages come out empty.
Thanks for pointing this out. I'll have a look.

Thanks and regards
Afif

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

Bug#774111: Patch for terminology to provide the x-terminal-emulator alternative

[Алексей Шилин]

Dear maintainer,

The attached patch makes terminology provide the x-terminal-emulator 
alternative.


-- 
Алексей Шилинdiff -aNru terminology-0.7.0.orig/debian/terminology.postinst terminology-0.7.0/debian/terminology.postinst
--- terminology-0.7.0.orig/debian/terminology.postinst	1970-01-01 00:00:00.0 +
+++ terminology-0.7.0/debian/terminology.postinst	2016-06-16 19:00:33.116245973 +
@@ -0,0 +1,10 @@
+#!/bin/sh
+
+set -e
+
+if [ "$1" = "configure" ]; then
+	update-alternatives --install /usr/bin/x-terminal-emulator \
+	  x-terminal-emulator /usr/bin/terminology 40 \
+	  --slave /usr/share/man/man1/x-terminal-emulator.1.gz \
+	  x-terminal-emulator.1.gz /usr/share/man/man1/terminology.1.gz
+fi
diff -aNru terminology-0.7.0.orig/debian/terminology.prerm terminology-0.7.0/debian/terminology.prerm
--- terminology-0.7.0.orig/debian/terminology.prerm	1970-01-01 00:00:00.0 +
+++ terminology-0.7.0/debian/terminology.prerm	2016-06-16 19:00:33.116245973 +
@@ -0,0 +1,7 @@
+#!/bin/sh
+
+set -e
+
+if [ "$1" = "remove" ] || [ "$1" = "deconfigure" ]; then
+	update-alternatives --remove x-terminal-emulator /usr/bin/terminology
+fi

Bug#829627: ITP: fatx -- Complete FATX filesystem support

[Christian Seiler]

On 07/04/2016 09:38 PM, Christophe DUVERGER wrote:
>   Description : Complete FATX filesystem support
> 
>  Includes:
>  fusefatx: filesystem mounting using fuse,
>  mkfs.fatx: make filesystem,
>  fsck.fatx: check and correct filesystem,
>  label.fatx: change or display volume name,
>  unrm.fatx: undelete files

Could you please mention in the package description (maybe even
in the short description) that this is the filesystem used by
the XBOX console? I think "FATX" is quite confusing if you have
never heard the term before, so adding "XBOX" will likely make
more sense to people looking at the description.

Thanks!

Regards,
Christian



signature.asc
Description: OpenPGP digital signature

Bug#826994: [Pkg-zfsonlinux-devel] Bug#826994: Bug#826994: Bug#826994: Missing init-script(s)?

[Petter Reinholdtsen]

[Craig Sanders]
> I've since seen notes saying:
>
> INSTALLING INIT SCRIPT LINKS
>
>   To setup the init script links in /etc/rc?.d manually on a Debian
>   GNU/Linux (or derived) system, run the following commands (the
>   order is important!):
>
> update-rc.d zfs-import start 07 S .   stop 07 0 1 6 .
> update-rc.d zfs-mount  start 02 2 3 4 5 . stop 06 0 1 6 .
> update-rc.d zfs-zedstart 07 2 3 4 5 . stop 08 0 1 6 .
> update-rc.d zfs-share  start 27 2 3 4 5 . stop 05 0 1 6 .

These notes are obsolete.  Debian no longer support the start/stop
arguments to update-rc.d, as dependency based boot ordering is used.
Use the 'defaults' versions mentioned above.  Note the ordering is still
important, as the dependencies must be registered before the scripts
using them.

> I guess that means "patches welcome".

Yeah.  Especially tested patches. :)

-- 
Happy hacking
Petter Reinholdtsen

Bug#829627: ITP: fatx -- Complete FATX filesystem support

[Christophe DUVERGER]

Package: wnpp
Severity: wishlist
Owner: Christophe Duverger 

* Package name: fatx
  Version : 1.11
  Upstream Author : Christophe Duverger 
* URL : http://sourceforge.net/projects/fatx
* License : GPL
  Programming Lang: C++
  Description : Complete FATX filesystem support

 Includes:
 fusefatx: filesystem mounting using fuse,
 mkfs.fatx: make filesystem,
 fsck.fatx: check and correct filesystem,
 label.fatx: change or display volume name,
 unrm.fatx: undelete files

Bug#591904: libavcodec52: text relocations on AMD64

[Fabian Greffrath]

Control: tags -1 moreinfo

Am Sonntag, den 03.07.2016, 18:54 +0200 schrieb Carl Eugen Hoyos:
> Is this still reproducible?
> Why is this an issue? I don't remember that this was ever reported
> upstream 
> (text relocations on x86-32 are reported on a regular basis).

Tagging as moreinfo.

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

Bug#493705: ffmpeg-debian: Libraries have text relocations

[Fabian Greffrath]

Control: tags -1 wontfix

Am Sonntag, den 03.07.2016, 18:47 +0200 schrieb Carl Eugen Hoyos:
> Same as for #528080: This will not be fixed in FFmpeg upstream, so I
> suggest 
> to close as wont-fix.

Tagging as wontfix, but not closing.

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

Bug#528080: ffmpeg-debian: ffmpeg still has shlib-with-non-pic-code lintian errors

[Fabian Greffrath]

Control: tags -1 wontfix

Am Sonntag, den 03.07.2016, 18:45 +0200 schrieb Carl Eugen Hoyos:
> Different FFmpeg developers have explained repeatedly (including
> recently) 
> that this will not be fixed within FFmpeg, so I suggest to close this
> bug 
> report as wont-fix.


Tagging wontfix, though not closing.


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

Bug#829626: tasksh: FTBFS on hurd-i386: 'PATH_MAX' was not declared in this scope

[Aaron M. Ucko]

Source: tasksh
Version: 1.0.0-1
Severity: important
Justification: fails to build from source

The hurd-i386 build of tasksh failed:

  /«PKGBUILDDIR»/src/Directory.cpp:166:12: error: 'PATH_MAX' was not declared 
in this scope
 char buf[PATH_MAX];

This is a common portability issue on the Hurd, which imposes no hard
limit here.  IIRC, the usual fix is to add a conditional definition:

  #ifndef PATH_MAX
  #  define PATH_MAX 4096
  #endif

Could you please take a look?

Thanks!

Bug#829557: [Pkg-xfce-devel] Bug#829557: firefox: error box at start-up / D-BUS related issue

[Yves-Alexis Perez]

On lun., 2016-07-04 at 17:48 +0100, Simon McVittie wrote:
> For a session startup less closely resembling a Rube Goldberg machine,
> consider installing dbus-user-session. This makes a semantic change
> to the meaning of "D-Bus session", which is why it is not the default:
> it is meant to be "opt-in". See its Description for details.

So I managed to reproduce the issue, and will try to look at what changes in
lightdm led to this (nothing stands out in the source diff but maybe that's
also a how the version were built).

I've tried to install dbus-user-session and it seems to fix the issue indeed.

One thing I've noticed is that system --user session keeps running after the
session is ended, which maybe doesn't happen under the previous lightdm
version. Could that be related?

Regards,
-- 

Yves-Alexis

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

Bug#829570: FTBFS on hurd-i386

[Felipe Sateler]

Hi,

On Mon, 04 Jul 2016 12:50:13 +0200 Svante Signell
 wrote:
> Hi,
>
> webrtc-audio-processing fails to build on GNU/Hurd and GNU/kFreeBSD due
> to missing $host cases for Hurd and kFreeBSD, with the corresponding
> changes in the file webrtc/base/platform_thread.cc. The attached patch,
> non-linux.patch fixes the build problems for both Hurd and kFreeBSD.
> Build tested on hurd-i386 and kfreebsd-i386.

Thanks for the patch. I have one suggestion though:

Index: webrtc-audio-processing-0.3/configure.ac
===
--- webrtc-audio-processing-0.3.orig/configure.ac
+++ webrtc-audio-processing-0.3/configure.ac
@@ -44,6 +44,11 @@ AS_CASE(["${host}"],
  OS_CFLAGS="-DWEBRTC_LINUX"
  PLATFORM_CFLAGS="-DWEBRTC_POSIX"
 ],
+[*-k*bsd-gnu* | *-*gnu*],
+[
+ OS_CFLAGS="-DWEBRTC_NONLINUX"
+ PLATFORM_CFLAGS="-DWEBRTC_POSIX"
+],


NONLINUX appears to me to be a too generic word. Maybe change to
WEBRTC_GNU? After all, this module is supposed to be buildable on
windows and osx platforms.

Also, it would be great if you could forward this upstream as well[1].
I can do this as well, but it will probably faster if you forward it.

Saludos

[1] https://bugs.freedesktop.org/enter_bug.cgi?product=PulseAudio

Bug#829491: mariadb-server-10.0: Removes lost+found directory if purged, /var/lib/mysql is a mountpoint with an ext4 filesystem, and user requests to remove all databases

[Otto Kekäläinen]

Hello Axel!

I committed your patch in
https://github.com/ottok/mariadb-10.0/commit/fddb4c3d2a74d25c5aef057674d561fbc874d14c
on my own development branch.

Packages built from that commit are now available at

  # Debian unstable
  deb http://labs.seravo.fi/~otto/mariadb-repo/ mariadb-10.0-sid-amd64/
  deb http://labs.seravo.fi/~otto/mariadb-repo/ mariadb-10.0-sid-i386/

Please test them and confirm that the bug you reported has been fixed
by this commit.

Bug#824894: fix available

[Nicholas D Steeves]

Because I do not yet have Debian upload privileges I have requested
sponsorship for an NMU that solves this bug.  The associated
sponsorship request, and the rationale for uploading 4.5.3 rather than
4.6.1 can be found in Bug #829205.

Cheers,
Nicholas

Bug#829625: pulseaudio: FTBFS on x32: cpu-volume-test segfaults

[Aaron M. Ucko]

Source: pulseaudio
Version: 9.0-1
Severity: important
Justification: fails to build from source (but built successfully in the past)

Hi, Felipe.

The latest x32 build of pulseaudio has failed with

  FAIL: cpu-volume-test
  =
  
  Running suite(s): CPU
  66%: Checks: 3, Failures: 0, Errors: 1
  tests/cpu-volume-test.c:188:E:svolume:svolume_orc_test:0: (after this point) 
Received signal 11 (Segmentation fault)
  FAIL cpu-volume-test (exit status: 1)

Could you please take a look?

Thanks!

Bug#829624: mdocml: FTBFS on hurd-i386: 'PATH_MAX' undeclared

[Aaron M. Ucko]

Source: mdocml
Version: 1.13.3-1
Severity: important
Justification: fails to build from source

The hurd-i386 build of mdocml failed:

  cc -g -W -Wall -Wstrict-prototypes -Wno-unused-parameter -Wwrite-strings 
-Wdate-time -D_FORTIFY_SOURCE=2  -c -o manpath.o manpath.c
  manpath.c: In function 'manpath_parse':
  manpath.c:44:14: error: 'PATH_MAX' undeclared (first use in this function)
char   cmd[(PATH_MAX * 3) + 20];

This is a common portability issue on the Hurd, which imposes no hard
limit here.  IIRC, the usual fix is to add a conditional definition:

  #ifndef PATH_MAX
  #  define PATH_MAX 4096
  #endif

Could you please take a look?

Thanks!

Bug#829623: libcoap: FTBFS on non-Linux: unsupported operating system

[Aaron M. Ucko]

Source: libcoap
Version: 4.1.2~rc+git20160626-1
Severity: important
Justification: fails to build from source

Builds of libcoap for kFreeBSD and the Hurd have been failing with
errors along the lines of

  checking operating system... configure: WARNING: ==> Currently unsupported 
operating system x86_64-pc-kfreebsd-gnu!
  configure: error: ==> If you can provide patches to support your operating 
system please write to 'libcoap-develop...@lists.sourceforge.net'.

Please either implement support for these architectures (bearing in
mind that they still use GNU libc) or adjust the package's overall
Architecture setting to linux-any.

Thanks!

Bug#829286: RFS: newlisp/10.7.0-2

[Sergio Durigan Junior]

On Monday, July 04 2016, Gianfranco Costamagna wrote:

>>Still nothing.  I had read the page, but it mentions the format of the
>>.commands file, and not dcut's CLI options.  I also tried specifying the
>>options in a different order, but I get the same error.
>
>
> dcut ftp-master reschedule -d 0  -f newlisp_10.7.0-2_source.changes
>
> this works for dput-ng I think

Alright, after installing dput-ng (I had the "normal" dput package
installed) it works.  And I can confirm that the commands were accepted
and that the package apparently has moved to the 0-day queue.  Indeed,
it seems like a bug...

Thanks!

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


signature.asc
Description: PGP signature

Bug#829348: [Pkg-xfce-devel] Bug#829348: lightdm: LightDM + MATE: switching users fails, unable to connect to D-Bus

[Yves-Alexis Perez]

control: forcemerge -1 829557

On lun., 2016-07-04 at 15:01 +0200, Vincent Lefevre wrote:
> 
> I get D-BUS related errors even for only one user (but the problem
> occurs only after a logout + login again). See:
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829557

Indeed, I can reproduce it too, and I guess it's definitely the same thing.
> 
> > This bug is introduced in 1.18.2-1, it's a workaround to downgrade both
> > lightdm and liblightdm-gobject-1-0 to 1.18.1-1 and then reboot.
> 
> Ditto.

I'll merge the bugs then, and try to followup on Simon's suggestion on
#829557.

Regards,
-- 

Yves-Alexis

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

Bug#824895: [PATCH] warn against likely data loss

[Nicholas D Steeves]

Justification: Problems like these [1] still exist.

[1] https://www.spinics.net/lists/linux-btrfs/msg56596.html

Bug#829622: consensuscore2: FTBFS on hurd-i386: 'dict' object has no attribute 'iteritems'

[Aaron M. Ucko]

Source: consensuscore2
Version: 0.12.0-1
Severity: important
Justification: fails to build from source

The hurd-i386 build of consensuscore2 failed when trying to install
the Python 3 module:

 dh_auto_install -a -O--buildsystem=pybuild
  I: pybuild base:184: dh_auto_install --buildsystem=cmake 
--builddirectory="/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build" 
--destdir="/«PKGBUILDDIR»/debian/python-consensuscore2" -- 
  I: pybuild base:184: /usr/bin/python3 setup.py install --root 
/«PKGBUILDDIR»/debian/python3-consensuscore2 
  Traceback (most recent call last):
File "setup.py", line 138, in 
  cmake(thisDir)
File "setup.py", line 112, in __call__
  for k, v in self.definitions.iteritems():
  AttributeError: 'dict' object has no attribute 'iteritems'
  E: pybuild pybuild:274: install: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py install --root 
/«PKGBUILDDIR»/debian/python3-consensuscore2 
  dh_auto_install: pybuild --install -i python{version} -p 3.5 --dest-dir 
/«PKGBUILDDIR»/debian/tmp returned exit code 13
  debian/rules:9: recipe for target 'binary-arch' failed
  make: *** [binary-arch] Error 13

The dict.iteritems method is only available in Python 2.x, but it
looks like the (Linux) i386 build was unaffected because it didn't
invoke setup.py here at all:

 dh_auto_install -a -O--buildsystem=pybuild
  I: pybuild base:184: dh_auto_install --buildsystem=cmake 
--builddirectory="/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build" 
--destdir="/«PKGBUILDDIR»/debian/python-consensuscore2" -- 
  I: pybuild base:184: dh_auto_install --buildsystem=cmake 
--builddirectory="/«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build" 
--destdir="/«PKGBUILDDIR»/debian/python3-consensuscore2" -- 
 dh_install -a -O--buildsystem=pybuild

I'm not sure offhand why not.  Could you please take a look?

Thanks!

Bug#829621: mdadm sends spurious "Fail event" messages on shutdown

[Gábor Gombás]

Package: mdadm
Version: 3.4-1
Severity: normal

Hello,

/lib/systemd/system/mdmonitor.service does not kill the monitoring
daemon on shutdown, which results in spurious "Fail event" mails
being sent while the arrays are being stopped by "/etc/init.d/mdadm-raid
stop".

Gabor

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

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

Versions of packages mdadm depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  initscripts2.88dsf-59.7
ii  libc6  2.22-13
ii  lsb-base   9.20160629
ii  udev   230-2

Versions of packages mdadm recommends:
ii  kmod22-1.1
ii  postfix [mail-transport-agent]  3.1.0-3

mdadm suggests no packages.

-- debconf information:
  mdadm/initrdstart_msg_errexist:
  mdadm/initrdstart_msg_errmd:
  mdadm/initrdstart_notinconf: false
  mdadm/initrdstart_msg_errconf:
* mdadm/initrdstart: all
* mdadm/start_daemon: true
  mdadm/initrdstart_msg_intro:
* mdadm/autocheck: true
* mdadm/mail_to: root
  mdadm/initrdstart_msg_errblock: