Bug#782005: ovirt-guest-agent spu

2016-08-22 Thread GCS
On Mon, Aug 22, 2016 at 4:45 PM, Milan Zamazal  wrote:
> László Böszörményi (GCS)  writes:
>> [1] dget -x 
>> http://http.debian.net/debian/pool/main/o/ovirt-guest-agent/ovirt-guest-agent_1.0.10.2.dfsg-2.dsc
>
> Is the URL correct?  This is the package from February 2015, isn't it?
 Indeed, I've pasted a wrong URL and didn't recognize. Please use the following:
dget -x 
http://www.barcikacomp.hu/gcs/ovirt-guest-agent_1.0.10.2.dfsg-2+deb8u1.dsc
Now double checked.

Thanks,
Laszlo/GCS



Bug#835159: RFS: cdist/4.3.1-1

2016-08-22 Thread Dmitry Bogatov
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name: cdist
  Version : 4.3.1-1
  Upstream Author : Nico Schottelius 
* Url : http://www.nico.schottelius.org/software/cdist/
* Licenses: GPL-3,GPL-3+
  Section : admin

It builds those binary packages:

  * cdist
  * cdist-doc

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

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

Alternatively, one can download the package with dget using this command:
dget -x http://mentors.debian.net/debian/pool/main/c/cdist/cdist_4.3.1-1.dsc

Alternatively, you can access package debian/ directory via git from URL:
https://anonscm.debian.org/cgit/users/kaction-guest/cdist.git

More information about cdist can be obtained from
http://www.nico.schottelius.org/software/cdist/

Changes since last upload:

  * New upstream release

Regards,
  Dmitry Bogatov



Bug#835081: RFS: iptables-persistent/1.0.4+nmu1 [NMU] [RC]

2016-08-22 Thread gustavo panizzo (gfa)
Gianfranco/BTS,

here is a new debdiff with the changes discused yesterday.

cheers



-- 
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: https://keybase.io/gfa
diff -Nru iptables-persistent-1.0.4/debian/changelog iptables-persistent-1.0.4+nmu1/debian/changelog
--- iptables-persistent-1.0.4/debian/changelog	2016-01-03 03:46:08.0 +0800
+++ iptables-persistent-1.0.4+nmu1/debian/changelog	2016-08-21 13:05:39.0 +0800
@@ -1,3 +1,18 @@
+iptables-persistent (1.0.4+nmu1) unstable; urgency=low
+
+  [ Jonathan Wiltshire ]
+  * Update debhelper to compat level 9
+  * Standards version 3.9.6 no changes needed.
+  * Re-tab plugins/15-ip4tables and plugins/25-ip6tables
+
+  [ gustavo panizzo ]
+  * Non-maintainer upload.
+  * Starts netfilter-persistent service before network-pre.target,
+as suggested by systemd upstream. Thanks to Patrick Schleizer
+(Closes: #829640).
+
+ -- gustavo panizzo   Sun, 21 Aug 2016 13:05:39 +0800
+
 iptables-persistent (1.0.4) unstable; urgency=medium
 
   * [d52b9e] During flush, set policy before flushing rules (Closes: #749790)
diff -Nru iptables-persistent-1.0.4/debian/compat iptables-persistent-1.0.4+nmu1/debian/compat
--- iptables-persistent-1.0.4/debian/compat	2016-01-03 03:46:08.0 +0800
+++ iptables-persistent-1.0.4+nmu1/debian/compat	2016-08-21 13:05:06.0 +0800
@@ -1 +1 @@
-7
+9
diff -Nru iptables-persistent-1.0.4/debian/control iptables-persistent-1.0.4+nmu1/debian/control
--- iptables-persistent-1.0.4/debian/control	2016-01-03 03:46:08.0 +0800
+++ iptables-persistent-1.0.4+nmu1/debian/control	2016-08-21 13:05:06.0 +0800
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Jonathan Wiltshire 
 Build-Depends: debhelper (>= 7.0.50~), dh-systemd, po-debconf
-Standards-Version: 3.9.5
+Standards-Version: 3.9.6
 Vcs-Browser: http://anonscm.debian.org/cgit/collab-maint/iptables-persistent.git/
 Vcs-Git: git://anonscm.debian.org/collab-maint/iptables-persistent.git
 
diff -Nru iptables-persistent-1.0.4/debian/rules iptables-persistent-1.0.4+nmu1/debian/rules
--- iptables-persistent-1.0.4/debian/rules	2016-01-03 03:46:08.0 +0800
+++ iptables-persistent-1.0.4+nmu1/debian/rules	2016-08-21 13:05:06.0 +0800
@@ -4,5 +4,5 @@
 	dh_installinit -- start 37 S . stop 37 0 1 6 .
 
 %:
-	dh --with systemd $@
+	dh $@ --with systemd
 
diff -Nru iptables-persistent-1.0.4/plugins/15-ip4tables iptables-persistent-1.0.4+nmu1/plugins/15-ip4tables
--- iptables-persistent-1.0.4/plugins/15-ip4tables	2016-01-03 03:46:08.0 +0800
+++ iptables-persistent-1.0.4+nmu1/plugins/15-ip4tables	2016-08-21 13:05:06.0 +0800
@@ -35,8 +35,8 @@
 	if [ ! -f /proc/net/ip_tables_names ]; then
 		echo "Warning: skipping IPv4 (no modules loaded)"
 	elif [ -x /sbin/iptables-save ]; then
-touch /etc/iptables/rules.v4
-chmod 0640 /etc/iptables/rules.v4
+		touch /etc/iptables/rules.v4
+		chmod 0640 /etc/iptables/rules.v4
 		iptables-save > /etc/iptables/rules.v4
 		if [ $? -ne 0 ]; then
 			rc=1
diff -Nru iptables-persistent-1.0.4/plugins/25-ip6tables iptables-persistent-1.0.4+nmu1/plugins/25-ip6tables
--- iptables-persistent-1.0.4/plugins/25-ip6tables	2016-01-03 03:46:08.0 +0800
+++ iptables-persistent-1.0.4+nmu1/plugins/25-ip6tables	2016-08-21 13:05:06.0 +0800
@@ -35,8 +35,8 @@
 	if [ ! -f /proc/net/ip6_tables_names ]; then
 		log_action_cont_msg "Warning: skipping IPv6 (no modules loaded)"
 	elif [ -x /sbin/ip6tables-save ]; then
-touch /etc/iptables/rules.v6
-chmod 0640 /etc/iptables/rules.v6
+		touch /etc/iptables/rules.v6
+		chmod 0640 /etc/iptables/rules.v6
 		ip6tables-save > /etc/iptables/rules.v6
 		if [ $? -ne 0 ]; then
 			rc=1
diff -Nru iptables-persistent-1.0.4/systemd/netfilter-persistent.service iptables-persistent-1.0.4+nmu1/systemd/netfilter-persistent.service
--- iptables-persistent-1.0.4/systemd/netfilter-persistent.service	2016-01-03 03:46:08.0 +0800
+++ iptables-persistent-1.0.4+nmu1/systemd/netfilter-persistent.service	2016-08-21 13:05:39.0 +0800
@@ -1,10 +1,16 @@
 [Unit]
 Description=netfilter persistent configuration
 DefaultDependencies=no
-Before=network.target
+
+Before=network-pre.target
+Wants=network-pre.target
+
 Wants=systemd-modules-load.service local-fs.target
 After=systemd-modules-load.service local-fs.target
 
+Conflicts=shutdown.target
+Before=shutdown.target
+
 [Service]
 Type=oneshot
 RemainAfterExit=yes
@@ -13,4 +19,3 @@
 
 [Install]
 WantedBy=multi-user.target
-


signature.asc
Description: PGP signature


Bug#834974: Installation Report: Stretch Alpha 7 on Cubox-i4pro

2016-08-22 Thread Rick Thomas
For what it’s worth, I just tried booting with an HDMI monitor connected to see 
if the silence on the serial-port was just a matter of console messages being 
directed to the HDMI video port instead.  Still no go.  Silence all-round.

Rick

> On Aug 22, 2016, at 9:15 PM, Rick Thomas  wrote:
> 
> I can confirm this problem.  I just got thru running a “stretch” install on 
> my test Cuboxi4Pro with ingredients from:
> 
>> wget 
>> http://ftp.us.debian.org/debian/dists/stretch/main/installer-armhf/current/images/netboot/SD-card-images/partition.img.gz
>> wget 
>> http://ftp.us.debian.org/debian/dists/stretch/main/installer-armhf/current/images/netboot/SD-card-images/firmware.MX6_Cubox-i.img.gz
>> wget 
>> http://ftp.us.debian.org/debian/dists/stretch/main/installer-armhf/current/images/netboot/SD-card-images/README.concatenateable_images
> 
> To be absolutely clear which components:
>> -rw-r--r-- 1 rbthomas rbthomas  871 Jun 29 15:56 
>> README.concatenateable_images
>> -rw-r--r-- 1 rbthomas rbthomas   187261 Jun 29 15:56 
>> firmware.MX6_Cubox-i.img.gz
>> -rw-r--r-- 1 rbthomas rbthomas 24210806 Jun 29 15:56 partition.img.gz
> 
> I got the same results as Rainer.  System would not boot after installation.  
> There was nothing at all on serial-port the console.
> 
> I also tried power-cycling the device.  Nothing on the serial-port console.
> 
> Can somebody tell me how to find out if there is a bootable u-boot on the SD 
> card?  Maybe the u-boot is getting clobbered by something in the installation 
> process?
> 
> Let me know if you want log files, etc...
> 
> Rick
> 
>> On Aug 21, 2016, at 10:44 AM, Martin Michlmayr  wrote:
>> 
>> * Rainer Dorsch  [2016-08-21 10:41]:
>>> The boot loader installation did not show an error, but the device did not 
>>> boot. 
>>> 
>>> The last "words" of the installer:
>>> 
>>> lqu Finishing the installation tqqk
>>> x x
>>> x   95%   x
>>> x x
>>> The system is going down NOW!ystem...   
>>> x
>>> Sent SIGKILL to all processes   
>>> x
>>> Requesting system 
>>> rebootj
>>>   [ 2730.956106] reboot: Restarting system
>> 
>> Can you 1) attach /var/log/installer/syslog from the SD card and b)
>> show the boot log (after the installer).
>> 
>> -- 
>> Martin Michlmayr
>> http://www.cyrius.com/
>> 
> 



Bug#834974: Installation Report: Stretch Alpha 7 on Cubox-i4pro

2016-08-22 Thread Rick Thomas
I can confirm this problem.  I just got thru running a “stretch” install on my 
test Cuboxi4Pro with ingredients from:

> wget 
> http://ftp.us.debian.org/debian/dists/stretch/main/installer-armhf/current/images/netboot/SD-card-images/partition.img.gz
> wget 
> http://ftp.us.debian.org/debian/dists/stretch/main/installer-armhf/current/images/netboot/SD-card-images/firmware.MX6_Cubox-i.img.gz
> wget 
> http://ftp.us.debian.org/debian/dists/stretch/main/installer-armhf/current/images/netboot/SD-card-images/README.concatenateable_images

To be absolutely clear which components:
> -rw-r--r-- 1 rbthomas rbthomas  871 Jun 29 15:56 
> README.concatenateable_images
> -rw-r--r-- 1 rbthomas rbthomas   187261 Jun 29 15:56 
> firmware.MX6_Cubox-i.img.gz
> -rw-r--r-- 1 rbthomas rbthomas 24210806 Jun 29 15:56 partition.img.gz

I got the same results as Rainer.  System would not boot after installation.  
There was nothing at all on serial-port the console.

I also tried power-cycling the device.  Nothing on the serial-port console.

Can somebody tell me how to find out if there is a bootable u-boot on the SD 
card?  Maybe the u-boot is getting clobbered by something in the installation 
process?

Let me know if you want log files, etc...

Rick

> On Aug 21, 2016, at 10:44 AM, Martin Michlmayr  wrote:
> 
> * Rainer Dorsch  [2016-08-21 10:41]:
>> The boot loader installation did not show an error, but the device did not 
>> boot. 
>> 
>> The last "words" of the installer:
>> 
>>  lqu Finishing the installation tqqk
>>  x x
>>  x   95%   x
>>  x x
>> The system is going down NOW!ystem...   x
>> Sent SIGKILL to all processes   x
>> Requesting system rebootj
>>[ 2730.956106] reboot: Restarting system
> 
> Can you 1) attach /var/log/installer/syslog from the SD card and b)
> show the boot log (after the installer).
> 
> -- 
> Martin Michlmayr
> http://www.cyrius.com/
> 



Bug#834633: Info received (Bug#834633: Acknowledgement (gpg: signing failed / agent_genkey failed: Operation cancelled))

2016-08-22 Thread Werner Koch
On Tue, 23 Aug 2016 00:56, linus.luess...@c0d3.blue said:

> * pinentry-curses: "Permission denied" (why?)

strace will help you.  Create a pinentry-wrapper script like

--8<---cut here---start->8---
#!/bin/sh
locale >/tmp/pinentry.err
set >>/tmp/pinentry.err
exec strace -o /tmp/pinentry.trc -e read=0 \ 
/somewhere/pinentry -d "$@" 2>>/tmp/pinentry.err
--8<---cut here---end--->8---

and put

pinentry-program /somewhere/else/pinentry-wrapper

into gpg-agent.conf.  GnuPG 2.1 also support a "debug-pinentry" option
for gpg-agent.conf which traces the communication between gpg-agent and
pinentry.

> should maybe try installing an alternative (non-broken?) pinentry

> PS: And with switching to pinentry-gtk2 I also had to add a
> "set pgp_use_gpg_agent=yes" to my muttrc to avoid being asked for

I'd suggest to use "set crypt_use_gpgme" instead of the old fashioned
interface.


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
 /* Join us at OpenPGP.conf   */


pgpbIkHjul93P.pgp
Description: PGP signature


Bug#835158: [cryptsetup] [INTL:id] Indonesian debconf templates translation for cryptsetup

2016-08-22 Thread Izharul Haq
Package: cryptsetup
Severity: wishlist
Tags: l10n patch
X-Debbugs-CC: debian-l10n-indones...@lists.debian.org

Dear cryptsetup Maintainer,

Please find attached an po-debconf translation of this package into
Indonesian.

$ msgfmt -cvo /dev/null debian/po/id.po
4 translated messages.

-- 
Regards,
Izharul Haq (atoz-chevara) | https://wiki.debian.org/Izharul%20Haq
Indonesian Debian Localization and Translation Team

PGP key id 4096R/A17F32B2
B862 27CA E76E 3B4A 3012  2260 68C6 D4C4 A17F 32B2


cryptsetup-id.tar.gz
Description: application/gzip


signature.asc
Description: OpenPGP digital signature


Bug#835157: [cernlib] [INTL:id] Indonesian debconf templates translation for cernlib

2016-08-22 Thread Izharul Haq
Package: cernlib
Version: 20061220+dfsg3-4.2
Severity: wishlist
Tags: l10n patch
X-Debbugs-CC: debian-l10n-indones...@lists.debian.org

Dear cernlib Maintainer,

Please find attached an po-debconf translation of this package into
Indonesian.

$ msgfmt -cvo /dev/null debian/po/id.po
4 translated messages.

-- 
Info:
- https://www.debian.org/international/l10n/po-debconf/README-trans
- https://www.debian.org/international/l10n/pseudo-urls

Regards,
Izharul Haq (atoz-chevara) | https://wiki.debian.org/Izharul%20Haq
Indonesian Debian Localization and Translation Team

PGP key id 4096R/A17F32B2
B862 27CA E76E 3B4A 3012  2260 68C6 D4C4 A17F 32B2


cernlib-id.tar.gz
Description: application/gzip


signature.asc
Description: OpenPGP digital signature


Bug#826300: [Pkg-pascal-devel] Bug#826300: Share knowledge on fpc and powerpc issue

2016-08-22 Thread peter green

On 22/08/16 21:01, Paul Gevers wrote:

I am including the patch right now in our packaging. I'll upload it to
the archive and I'll then continue bootstrapping on powerpc. Give me a
couple of days. Feel free to bootstrap powerpc before I do.
   
I tried building the new package in a jessie chroot (which worked with a 
few minor packaging tweaks), then running the results in a sid chroot 
(unfortunatley I was doing this on a porterbox so I couldn't install them).


Unfortunately it seems the new fpcmkcfg-3.0.0 binary still crashes. Not 
sure whether it's an artifact of building in jessie or a sign that the 
bug isn't fixed.


I may take another look once I get a qemu setup going so I can do stuff 
that needs root.



Paul

   




Bug#835155: dictionaries-common: Please replace build dependency on jade with openjade

2016-08-22 Thread Neil Roeth
Package: dictionaries-common
Version: 1.27.0
Severity: normal
Tags: patch

Dear maintainer,

The jade package is obsolete and will be removed from Debian.  Please replace
the build dependency on jade with openjade and change all uses of the command
"jade" with "openjade".  Patch attached.

diff -Nru dictionaries-common-1.27.0/debian/changelog 
dictionaries-common-1.27.0+nmu1/debian/changelog
--- dictionaries-common-1.27.0/debian/changelog 2016-05-19 09:50:47.0 
-0400
+++ dictionaries-common-1.27.0+nmu1/debian/changelog2016-08-22 
21:40:31.0 -0400
@@ -1,3 +1,10 @@
+dictionaries-common (1.27.0+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove jade dependency
+
+ -- Neil Roeth   Mon, 22 Aug 2016 21:40:31 -0400
+
 dictionaries-common (1.27.0) unstable; urgency=medium
 
   * New "/var/lib/dictionaries-common/hunspell" file trigger to run
diff -Nru dictionaries-common-1.27.0/debian/control 
dictionaries-common-1.27.0+nmu1/debian/control
--- dictionaries-common-1.27.0/debian/control   2016-05-19 09:50:47.0 
-0400
+++ dictionaries-common-1.27.0+nmu1/debian/control  2016-08-22 
21:40:31.0 -0400
@@ -5,7 +5,7 @@
 Uploaders: Rene Engelhard 
 Build-Depends-Indep: docbook-xml,
  docbook-dsssl,
- jade,
+ openjade,
  w3m,
  slice,
  autoconf,
diff -Nru 
dictionaries-common-1.27.0/debian/patches/990_switch-jade-to-openjade.patch 
dictionaries-common-1.27.0+nmu1/debian/patches/990_switch-jade-to-openjade.patch
--- dictionaries-common-1.27.0/debian/patches/990_switch-jade-to-openjade.patch 
1969-12-31 19:00:00.0 -0500
+++ 
dictionaries-common-1.27.0+nmu1/debian/patches/990_switch-jade-to-openjade.patch
2016-08-22 21:40:31.0 -0400
@@ -0,0 +1,11 @@
+--- a/Makefile.in
 b/Makefile.in
+@@ -126,7 +126,7 @@
+ # Policy XML document
+ 
+ $(policy).html: $(policy).xml $(html_stylesheet) $(maintainer_scripts)
+-  jade -t sgml -V nochunks -d $(html_stylesheet) \
++  openjade -t sgml -V nochunks -d $(html_stylesheet) \
+ /usr/share/sgml/declaration/xml.decl $< > $@
+ 
+ %.txt: %.html
diff -Nru dictionaries-common-1.27.0/debian/patches/series 
dictionaries-common-1.27.0+nmu1/debian/patches/series
--- dictionaries-common-1.27.0/debian/patches/series2015-07-30 
12:09:13.0 -0400
+++ dictionaries-common-1.27.0+nmu1/debian/patches/series   2016-08-22 
21:40:31.0 -0400
@@ -22,3 +22,4 @@
 990_flyspell.el_change-disclaimer+version.patch
 # 
 950_flyspell.el_revert-sgml-lexical-context.patch
+990_switch-jade-to-openjade.patch



Bug#823348: Limit the strongest dependencies on supplemental -doc packages

2016-08-22 Thread Josh Triplett
[Please CC me on replies, as I didn't receive this mail, and just
happened to see it in the archives.]

On Mon, 22 Aug 2016 13:38:42 +0100 George Bateman  
wrote:
> I'm currently making my first package, Processing. It's a GUI teaching
> tool for (usually Java) programming, with its own standard libraries
> for the code produced. It is currently split up into three packages:
> "processing" the GUI, "libprocessing3-java" the library, and
> "processing-doc" for documentation. It has the following dependency
> relationships:
> 
> processing –Depends→ libprocessing3-java
>–Depends→ processing-doc
> 
> libprocessing3-java –Sugggests→ processing-doc
> 
> This would violate the proposed policy change, but for very good
> reason because no educational program is very effective without some
> documentation.

Policy defines "Recommends" as "packages that would be found together
with this one in all but unusual installations."  That seems entirely
accurate here, and apt installs Recommends by default, so by default a
user who installed processing would get processing-doc.

Unless the processing GUI fails to run without its help files installed,
"Recommends" seems sufficient.  Does processing fail to start because it
expects the help files to exist, or crash/misbehave without the help
files present?

If not, "Recommends" seems appropriate.

> To resolve such issues, I would amend the last sentence of the patch to
> 
> + Otherwise,
> + package should declare at most a Recommends on
> + package-doc, unless package-doc is
> needed for the
> + practical use of package.

That doesn't seem like the right resolution to me.



Bug#835154: fonts-cantarell: Please package new release 0.0.25

2016-08-22 Thread Jeremy Bicha
Package: fonts-cantarell
Version: 0.0.24-1
Severity: wishlist

A new version of GNOME's default font, fonts-cantarell, is available.
Please package the update since this font is used by a lot of people.

https://mail.gnome.org/archives/ftp-release-list/2016-August/msg00104.html

Thanks,
Jeremy Bicha



Bug#835065: jade: Package rebuilt from source is broken

2016-08-22 Thread Neil Roeth
On 08/21/2016 07:34 PM, Daniel Schepler wrote:
> Source: jade
> Version: 1.2.1-49
> Severity: serious
>
> For example, if I rebuild jade locally, then try to build
> dictionaries-common using the rebuilt jade, it gives an error:
>
> jade -t sgml -V nochunks -d policy/html.dsl \
>   /usr/share/sgml/declaration/xml.decl policy/dsdt-policy.xml >
> policy/dsdt-policy.html
> jade:/usr/share/sgml/declaration/xml.decl:31:27:W: characters in the
> document character set with numbers exceeding 65535 not supported
> Segmentation fault
> Makefile:129: recipe for target 'policy/dsdt-policy.html' failed
> make[1]: *** [policy/dsdt-policy.html] Error 139
> make[1]: Leaving directory '/build/dictionaries-common-1.27.0'
> debian/rules:27: recipe for target 'build-stamp' failed
> make: *** [build-stamp] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
I am working on removing the jade package from Debian.  I'll file a bug
against dictionaries-common to replace jade with openjade.

Thanks.

-- 
Neil Roeth



Bug#833079: curl: --no-proxy

2016-08-22 Thread Fulano Diego Perez

is this deemed a bug based upon head request phenomena observed with proxy ?



Bug#835153: texlive-base: please set TDCOLORS in /e/t/texdoctk/texdocrc.defaults to silence texdoctk

2016-08-22 Thread Jerome Benoit
Package: texlive-base
Version: 2014.20141024-2
Severity: minor

Dear Maintainer,

please add the foloowing (magic) lines

# button colours: default and active back-/foreground
# names and RGB values are both allowed; use the form #xx for RGB
TDCOLORS=#d9d9d9 Black #ececec red

somewhere in /etc/texmf/texdoctk/texdocrc.defaults to make the message

NOTE: Button colours not set in /etc/texmf/texdoctk/texdocrc.defaults; 
using defaults.

just a very bad souvenir. These lines were pick up from the ~/.texdocrc 
generated via
Settings->Save .

Thanks in advance,
Jerome





-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource. 

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries 
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are 
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or 

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file


##
other files

##
 List of ls-R files

-rw-r--r-- 1 root root 2858 Aug 17 21:33 /var/lib/texmf/ls-R
-rw-r--r-- 1 root staff 4321 Aug 17 21:33 /usr/local/share/texmf/ls-R
lrwxrwxrwx 1 root root 29 Oct 21  2014 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Dec  2  2014 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Dec  2  2014 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 2344 Jan 19  2016 /etc/texmf/web2c/texmf.cnf
-rw-r--r-- 1 root root 9402 Aug 14 16:08 /var/lib/texmf/web2c/fmtutil.cnf
lrwxrwxrwx 1 root root 32 Dec  2  2014 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 12835 Aug 14 16:08 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root  283 Jan  9  2013 mktex.cnf
-rw-r--r-- 1 root root 2344 Jan 19  2016 texmf.cnf
##
 md5sums of texmf.d
3bb00b8d973d9968c7204e593c3249e3  /etc/texmf/texmf.d/000local.cnf
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf.disabled
055e06548bac99958d8ab2dd1248f2b4  /etc/texmf/texmf.d/80tex4ht.cnf
1df66bc319cec731e202eaf39f5d85e1  /etc/texmf/texmf.d/96JadeTeX.cnf

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

Kernel: Linux 3.16.7-ckt20-0001-mbp62 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages texlive-base depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  dpkg   1.18.3
ii  libpaper-utils 1.1.24+nmu4
ii  tex-common 5.03
ii  texlive-binaries   2014.20140926.35254-6
ii  ucf3.0030
ii  xdg-utils  1.1.0~rc1+git20111210-7.4

Versions of packages texlive-base recommends:
ii  lmodern  2.004.4-5

Versions of packages texlive-base suggests:
ii  evince-gtk [postscript-viewer]   3.14.1-2+deb8u1
ii  ghostscript [postscript-viewer]  9.06~dfsg-2+deb8u1
ii  gv [postscript-viewer]   1:3.7.4-1
ii  mupdf [pdf-viewer]   1.5-1+b2
ii  perl-tk  1:804.032-3+b3
ii  zathura [pdf-viewer] 0.3.1-2

Versions of packages tex-common depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  dpkg   1.18.3
ii  ucf  

Bug#835102: jquery-throttle-debounce: please provide a backports in jessie-backports

2016-08-22 Thread Ben Finney
On 22-Aug-2016, Mattia Rizzolo wrote:
> diffoscope very recently (still in git) gained a build-dependency on
> jquery-throttle-debounce.
> 
> Since I do regular backports of it, and I'd really like to avoid
> adding a delta during backports

This is unclear to me: of what do you do regular backports?

What is the bug in the ‘jquery-throttle-debounce’ source package? Did
you intend to report with “Severity: normal”, the default for new
reports?

> I wonder whether you'd be willing to provide a backport of this
> package.

How should this package change to resolve this bug report?

-- 
 \   “For fast acting relief, try slowing down.” —Jane Wagner, via |
  `\   Lily Tomlin |
_o__)  |
Ben Finney 



Bug#818142: flycheck: FTBFS in testing (failing tests)

2016-08-22 Thread Sean Whitton
Dear Santiago,

Thanks for your build logs.

1. flycheck tends to FTBFS because the test suite contains many tests
which encode expected output from ~30 command line tools.  When one of
those tools sees a new upstream version which tweaks its output, the
test breaks.

2. The test suite also fails under certain autobuilder setups.  In
particular, the reproducible builds team's automated builders fail with
mysterious permission errors.  I think it is something to do with their
tmpfs setup -- though I use tmpfs with sbuild and can't reproduce the
error.

Looking at the logs, I believe that the problems identified by both you
and Chris as type (1).  Since I can't reproduce it outside of the
reproducible build servers, I don't consider (2) a bug in flycheck at
present.  So I'll consider this bug as tracking current test suite
failures, and I'll close it with an upload in which the test suite
passes against current Debian sid.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#834814: wondershaper crashes entire system

2016-08-22 Thread vrishab in
Filed kernel bug https://bugzilla.kernel.org/show_bug.cgi?id=153561

Please resolve this bug accordingly.
​


Bug#835152: nautilus-open-terminal: plugin can use /etc/alternatives/x-terminal-emulator for non-gnome installations

2016-08-22 Thread Mark Hedges
Package: nautilus-open-terminal
Version: 0.20-1
Severity: normal

Hello,

I installed XFCE without much of gnome, but I like using Nautilus.  This plugin 
is great.  However, I do not have gnome-terminal installed.  I have 
xfce4-terminal installed.  This is also /etc/alternatives/x-terminal-emulator 
(/usr/bin/xfce4-terminal.wrapper).

However, when I right-click in a Nautilus folder and choose "Open in Terminal" 
it opens /usr/bin/xterm in that directory.

It would be nice if this plugin would follow the system default by using 
/etc/alternatives/x-terminal-emulator.

Thank you.

Mark Hedges


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

Kernel: Linux 4.6.0-1-rt-amd64 (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 nautilus-open-terminal depends on:
ii  gconf-service3.2.6-3
ii  gconf2   3.2.6-3
ii  libatk1.0-0  2.20.0-1
ii  libc62.23-4
ii  libcairo-gobject21.14.6-1+b1
ii  libcairo21.14.6-1+b1
ii  libgconf-2-4 3.2.6-3
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.48.1-2
ii  libgtk-3-0   3.20.7-1
ii  libnautilus-extension1a  3.20.1-3
ii  libpango1.0-01.40.1-1

nautilus-open-terminal recommends no packages.

nautilus-open-terminal suggests no packages.

-- no debconf information



Bug#835151: libsvrcore0: package is not installable as it depends on missing libnss3-1d

2016-08-22 Thread John David Anglin
Package: libsvrcore0
Version: 1:4.0.4-15+b3
Severity: normal

Dear Maintainer,

mx3210:/home/dave# apt-get install libsvrcore0
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libsvrcore0 : Depends: libnss3-1d but it is not installable
E: Unable to correct problems, you have held broken packages.

Last version of libnss3-1d was 2:3.25-1 but it isn't compatible with
libnss3 2:3.26-1.

Regards,
Dave Anglin

-- System Information:
Debian Release: stretch/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 4.7.2+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libsvrcore0 depends on:
ii  libc6 2.23-4+b1
ii  libnspr4  2:4.12-6
ii  libnss3   2:3.26-1

libsvrcore0 recommends no packages.

libsvrcore0 suggests no packages.

-- no debconf information



Bug#834633: Info received (Bug#834633: Acknowledgement (gpg: signing failed / agent_genkey failed: Operation cancelled))

2016-08-22 Thread Linus Lüssing
With some help from IRC the problem could be narrowed down to
pinentry. My setup so far involved a VNC session and the only
pinentry package installed was "pinentry-gnome3". What works for
me is pinentry-gtk2, for instance.

Using VNC:
* pinentry-gnome3: "Operation cancelled" (why?)
* pinentry-gtk2: works!
* pinentry-qt: Other, VNC+qt4 specific bug
* pinentry-curses: "Permission denied" (why?)

Using ssh:
* pinentry-gnome3: Permission denied (obviously,needs X11)
* pinentry-gtk2: Permission denied (obviously, needs X11)
* pinentry-qt: Permission denied (obviously, needs X11)
* pinentry-curses: Permission denied (why?) 

Using ssh with X-forwarding (ssh -X):
* pinentry-gnome3: Operation cancelled (why?)
* pinentry-gtk2: works!
* pinentry-qt:  works!
* pinentry-curses: Permission denied (why?)


So I'll be using pinentry-gtk2 for now which reduces the severity
of this bug for me. But the error message gnupg displays is a
little confusing and does not indicate to the user that s/he
should maybe try installing an alternative (non-broken?) pinentry
package.

Regards, Linus


PS: And with switching to pinentry-gtk2 I also had to add a
"set pgp_use_gpg_agent=yes" to my muttrc to avoid being asked for
a password twice (once within mutt and once in the pop-up).



Bug#833679: BitPaddedInt import error

2016-08-22 Thread Leandro Lucarella
On Mon, 08 Aug 2016 00:51:34 + Tristan Seligmann  
wrote:
> Your hypothesis was correct: `mutagen.id3.BitPaddedInt`used to be imported
> from `mutagen._id3util.BitPaddedInt` in `mutagen.id3`; however, `id3` was
> turned into a package, so now the import doesn't leak anymore. In addition,
> the helper class itself moved to `mutagen.id3._util.BitPaddedInt`.
> 
> Looks like this was reported upstream recently as well:
> http://tickets.musicbrainz.org/browse/PICARD-833

The upstream issue is fixed now, is there any ETA for a release with the
fix included? Here is the PR that is supposed to fix this:
https://github.com/metabrainz/picard/pull/479

Thanks!

-- 
Leandro Lucarella (AKA luca) http://llucax.com.ar/



Bug#835150: RFP: tis-interpreter -- C interpreter for detecting undefined behavior

2016-08-22 Thread Petter Reinholdtsen

Package: wnpp
Severity: wishlist

* Package name: tis-interpreter
  Version : n/a, git repo without tags
  Upstream Author : http://trust-in-soft.com/tis-interpreter/
* URL : https://github.com/TrustInSoft/tis-interpreter
* License : GPL
  Programming Lang: C, Ocaml
  Description : C interpreter for detecting undefined behavior

This is a tool to find bugs in C source code.  It use is described in
http://blog.regehr.org/archives/1405 >, "Isolating a Free-Range
Miscompilation".  It look like it would be useful to find bugs in the C
code in Debian.

-- 
Happy hacking
Petter Reinholdtsen



Bug#835149: dpkg: please adapt setting the default pie hardening flag to gcc's new defaults

2016-08-22 Thread Balint Reczey
Package: dpkg
Version: 1.18.10
Severity: wishlist
Tags: patch moreinfo

Dear Guillem,

As a continuation of the discussions [1][2] on debian-devel I'm
attaching the simple patch that changes dpkg's pie hardening flag
to adapt to GCC's new default settings proposed in #835148.

I'm continuing with the rebuild/autopkgtest tests according to
the Dpkg FAQ, hence the moreinfo tag.

Cheers,
Balint

[1] https://lists.debian.org/debian-devel/2016/05/msg00228.html
[2] https://lists.debian.org/debian-devel/2016/08/msg00324.html

>From c0d867dcd6bffe6a504c0699e64258191e760a49 Mon Sep 17 00:00:00 2001
From: Balint Reczey 
Date: Mon, 4 Jul 2016 20:06:55 +0200
Subject: [PATCH 2/2] Dpkg::Vendor::Debian: Enable PIE by default on some
 architectures

---
 scripts/Dpkg/Vendor/Debian.pm | 19 ++-
 1 file changed, 18 insertions(+), 1 deletion(-)

diff --git a/scripts/Dpkg/Vendor/Debian.pm b/scripts/Dpkg/Vendor/Debian.pm
index f8854e2..8e9a0ac 100644
--- a/scripts/Dpkg/Vendor/Debian.pm
+++ b/scripts/Dpkg/Vendor/Debian.pm
@@ -280,6 +280,13 @@ sub _add_hardening_flags {
 	bindnow => 1,
 );
 
+# GCC enables PIE by default on some architectures
+my $pie_by_default = 0;
+if ($arch =~ /^(?:amd64|ppc64el|s390x)$/) {
+	$pie_by_default = 1;
+	$use_feature{pie} = 1;
+}
+
 # Adjust features based on user or maintainer's desires.
 $self->_parse_feature_area('hardening', \%use_feature);
 
@@ -321,7 +328,17 @@ sub _add_hardening_flags {
 }
 
 # PIE
-if ($use_feature{pie}) {
+if ($pie_by_default == 1 and not $use_feature{pie}) {
+	my $flag = '-fno-PIE';
+	$flags->append('CFLAGS', $flag);
+	$flags->append('OBJCFLAGS',  $flag);
+	$flags->append('OBJCXXFLAGS', $flag);
+	$flags->append('FFLAGS', $flag);
+	$flags->append('FCFLAGS', $flag);
+	$flags->append('CXXFLAGS', $flag);
+	$flags->append('GCJFLAGS', $flag);
+	$flags->append('LDFLAGS', '-fno-PIE -no-pie');
+} elsif ($pie_by_default == 0 and $use_feature{pie}) {
 	my $flag = '-fPIE';
 	$flags->append('CFLAGS', $flag);
 	$flags->append('OBJCFLAGS',  $flag);
-- 
2.1.4



Bug#835148: gcc-6: please enable PIE hardening flags by default on amd64 ppc64el and s390x

2016-08-22 Thread Balint Reczey
Package: gcc-6
Version: 6.1.1-12
Severity: wishlist
Tags: patch

Dear Matthias,

As a continuation of the discussions [1][2] on debian-devel I'm
attaching the simple patch that implements enabling the PIE
hardening flags for a subset of the architectures.

I'm open to changing the subset, it matches the set selected in Ubuntu
as a start, but porters may have different preferences [2].

I'm continuing with a full archive rebuild to see the amount of packages
to be updated for the change in the default flags.

The same patch applies to gcc-5, too, if it does not get removed
from the archive before the patch is accepted for gcc-6.

Cheers,
Balint

[1] https://lists.debian.org/debian-devel/2016/05/msg00228.html
[2] https://lists.debian.org/debian-devel/2016/08/msg00324.html

>From 096fba7df4a9d699015c5f5457be7fdd21cde33e Mon Sep 17 00:00:00 2001
From: Balint Reczey 
Date: Sun, 3 Jul 2016 21:09:36 +0200
Subject: [PATCH] Enable PIE on Debian for amd64, ppc64el and s390x

---
 debian/rules.defs | 9 ++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/debian/rules.defs b/debian/rules.defs
index 47a067d..443eba4 100644
--- a/debian/rules.defs
+++ b/debian/rules.defs
@@ -1222,16 +1222,19 @@ endif
 
 # pie by default 
 with_pie :=
+pie_archs := amd64 ppc64el s390x
 ifeq ($(distribution),Ubuntu)
   ifeq (,$(filter $(distrelease),lucid precise trusty utopic vivid wily))
 pie_archs = s390x
+  else
+pie_archs =
   endif
   ifeq (,$(filter $(distrelease),lucid precise trusty utopic vivid wily xenial))
 pie_archs += amd64 ppc64el
   endif
-  ifneq (,$(filter $(DEB_TARGET_ARCH),$(pie_archs)))
-with_pie := yes
-  endif
+endif
+ifneq (,$(filter $(DEB_TARGET_ARCH),$(pie_archs)))
+  with_pie := yes
 endif
 
 # gold 
-- 
2.1.4



Bug#835147: javatools: please make the documention Recommends substvars reproducible

2016-08-22 Thread Chris Lamb
Source: javatools
Version: 0.58
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], I noticed
that javatools emits Recommends substvars that are not reproducible.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/jh_scanjavadoc b/jh_scanjavadoc
index 3d018d6..9abe6d2 100755
--- a/jh_scanjavadoc
+++ b/jh_scanjavadoc
@@ -18,4 +18,4 @@ foreach my $doclink ( map { scan_javadoc($_) } @ARGV){
 push(@dep, $doclink);
 }
 
-print join(', ', find_package_for_existing_files(@dep)), "\n" if(@dep);
+print join(', ', find_package_for_existing_files(sort @dep)), "\n" if(@dep);


Bug#826206: openjdk-8-jre-jamvm: relocation error, symbol JVM_GetResourceLookupCacheURLs not defined

2016-08-22 Thread Christoph Anton Mitterer
Hey.

The backports version (8u102-b14.1-1~bpo8+1) seems to be still
broken...
When can one expect a fix there?

Cheers,
Chris.

smime.p7s
Description: S/MIME cryptographic signature


Bug#835146: dpkg: please enable bindow hardening flag by default

2016-08-22 Thread Balint Reczey
Package: dpkg
Version: 1.18.10
Severity: wishlist
Tags: patch moreinfo

Dear Guillem,

As a continuation of the discussions [1][2] on debian-devel I'm
attaching the simple patch that implements enabling the bindnow
hardening flags.

I'm continuing with the rebuild/autopkgtest tests according to
the Dpkg FAQ, hence the moreinfo tag.

Cheers,
Balint

[1] https://lists.debian.org/debian-devel/2016/05/msg00228.html
[2] https://lists.debian.org/debian-devel/2016/08/msg00324.html
>From 93059236f0559649e052a1cae00ff7a5ba4cab05 Mon Sep 17 00:00:00 2001
From: Balint Reczey 
Date: Sun, 3 Jul 2016 21:12:09 +0200
Subject: [PATCH 1/2] Use bindnow hardening flag by default

---
 scripts/Dpkg/Vendor/Debian.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/Dpkg/Vendor/Debian.pm b/scripts/Dpkg/Vendor/Debian.pm
index ebb1750..f8854e2 100644
--- a/scripts/Dpkg/Vendor/Debian.pm
+++ b/scripts/Dpkg/Vendor/Debian.pm
@@ -277,7 +277,7 @@ sub _add_hardening_flags {
 	fortify => 1,
 	format => 1,
 	relro => 1,
-	bindnow => 0,
+	bindnow => 1,
 );
 
 # Adjust features based on user or maintainer's desires.
-- 
2.1.4



Bug#826718: fwknop 2.6.9

2016-08-22 Thread Markus Gerstel

Hi all,

I just started working on packaging fwknop 2.6.9 from scratch when I 
found this bug. I have spoken to infinity0 today, who would be happy to 
sponsor the upload as well.


As I only just started reading the Debian maintainers guide I tend to 
trust your work more than mine, too. I can try and have a look to see if 
I can identify what's going wrong with hardening flags though.


-Markus



Bug#835145: udpcast: please make the build reproducible

2016-08-22 Thread Chris Lamb
Source: udpcast
Version: 20120424-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], I noticed
that udpcast could not be built reproducibly.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproducible_build.diff1970-01-01 01:00:00.0 
+0100
--- b/debian/patches/reproducible_build.diff2016-08-22 22:55:53.225400230 
+0100
@@ -0,0 +1,15 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2016-08-22
+
+--- udpcast-20120424.orig/html2man.pl
 udpcast-20120424/html2man.pl
+@@ -122,7 +122,7 @@ if($release eq "") {
+   $release = "current";
+ }
+ if($date eq "") {
+-  my @lt = localtime(time);
++  my @lt = gmtime($ENV{SOURCE_DATE_EPOCH} || time);
+   $date = sprintf("%s %d, %d", $mons[$lt[4]], $lt[3], 1900+$lt[5]);
+ }
+ 
--- a/debian/patches/series 2016-08-22 22:45:55.992997564 +0100
--- b/debian/patches/series 2016-08-22 22:55:52.037382691 +0100
@@ -1,3 +1,4 @@
 nostrip.diff
 manpage_fixes.diff
 missing_fd_set.diff
+reproducible_build.diff


Bug#817067: [Pkg-clamav-devel] Bug#817067: Bug#817067: clamscan large archive DOS protection could be used to hide virus

2016-08-22 Thread Sebastian Andrzej Siewior
On 2016-03-07 21:32:22 [+0100], Sebastian Andrzej Siewior wrote:
> Sounds reasonable. I forwarded your report upstream.

proxy mode on.

|Kevin Lin 2016-03-10 21:24:37 CET
|Engine limitations, as well as certain non-fatal internal errors, are
|suppressed within the engine. This is done to simplify issues and
|suppress issues caused by a non-clean return code and allow the engine
|to continue parsing the file.
|
|The solution to the issue would be to track the limitation statuses,
|most likely in the scanning context and have clamscan changed to
|interpret the statuses. Note that this mostly likely would affect the
|ABI.

|Steven Morgan 2016-06-24 20:26:42 CEST May use a virus such as
|Heuristic.SizeLimitsExceeded under the control of clamd/clamscan option
|(BlockLimitsExceeded). Rational - its not really an error or a virus,
|but flagging an heuristic fits better within ClamAV processing modes.

proxy mode off.

Sebastian



Bug#835133: libnet-jabber-perl: FTBFS in testing

2016-08-22 Thread gregor herrmann
On Mon, 22 Aug 2016 22:03:42 +0200, Santiago Vila wrote:

> Package: libnet-jabber-perl
> Version: 2.0-6
> Severity: serious
 
> I can reproduce the failure as many times as desired in two different
> virtual machines where /etc/timezone is "Etc/UTC".

Which is happily ignored, according to the output of the test :)

# Failed test (t/query_time.t at line 58)
#   'MET DST'
# doesn't match '(?^:^\S+$)'
# Looks like you failed 1 tests of 39.
t/query_time.t 
1..39
ok 1 - use Net::Jabber;
ok 2 - new()
ok 3 - The object isa Net::Jabber::Stanza
ok 4 - The object isa Net::XMPP::Stanza
ok 5 - xmlns not defined
ok 6 - xmlns defined
ok 7 - xmlns eq 'jabber:iq:time'
ok 8 - display not defined
ok 9 - display defined
ok 10 - display eq 'display'
ok 11 - tz not defined
ok 12 - tz defined
ok 13 - tz eq 'tz'
ok 14 - utc not defined
ok 15 - utc defined
ok 16 - utc eq 'utc'
ok 17 - GetXML()
ok 18 - new()
ok 19 - The object isa Net::Jabber::Stanza
ok 20 - The object isa Net::XMPP::Stanza
ok 21 - xmlns not defined
ok 22 - xmlns defined
ok 23 - xmlns eq 'jabber:iq:time'
ok 24 - display defined
ok 25 - display eq 'display'
ok 26 - tz defined
ok 27 - tz eq 'tz'
ok 28 - utc defined
ok 29 - utc eq 'utc'
ok 30 - GetXML()
ok 31 - new()
ok 32 - The object isa Net::Jabber::Stanza
ok 33 - The object isa Net::XMPP::Stanza
ok 34 - xmlns not defined
ok 35 - xmlns defined
ok 36 - xmlns eq 'jabber:iq:time'
ok 37 - look like a utc?
ok 38 - look like a display?
not ok 39 - look like a timezone?
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/39 subtests

I can't quickly reproduce it but there's the same bug report at CPAN RT:
https://rt.cpan.org/Public/Bug/Display.html?id=96404
with a trivial patch
 

Cheers,
gregor

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


signature.asc
Description: Digital Signature


Bug#830265: ring: Backport to Jessie?

2016-08-22 Thread Petter Reinholdtsen

I had another go with the backport, and managed to get the code building
by downloading a lot of the dependencies instead of using the Debian
equvalents.  But the resulting dring binary do not work.  It crashes
with a segfault.  According to gdb, this is the crash site:

Program received signal SIGSEGV, Segmentation fault.
__memcpy_sse2_unaligned () at 
../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:36
36  ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: No such file or 
directory.
(gdb) bt
#0  __memcpy_sse2_unaligned () at 
../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:36
#1  0x75f0731f in memcpy (__len=32767, __src=0x7fffc35c, 
__dest=0x7fffc40c)
at /usr/include/x86_64-linux-gnu/bits/string3.h:51
#2  x86_sha1_update (ctx=0x7fffc3f0, length=, 
data=0x55b88df6 "")
at sha-x86-ssse3.c:126
#3  0x75f07757 in wrap_x86_hash_fast (algo=, 
text=0x55b88bd0, 
text_size=550, digest=0x7fffc640) at sha-x86-ssse3.c:339
#4  0x75e7eb26 in _gnutls_hash_fast 
(algorithm=algorithm@entry=GNUTLS_DIG_SHA1, 
text=0x55b88bd0, textlen=550, digest=digest@entry=0x7fffc640)
at gnutls_hash_int.c:114
#5  0x75ed6528 in _gnutls_get_key_id (pk=pk@entry=GNUTLS_PK_RSA, 
params=params@entry=0x7fffc550, 
output_data=output_data@entry=0x7fffc640 "", 
output_data_size=output_data_size@entry=0x7fffc638) at x509.c:2523
#6  0x75ed6680 in gnutls_x509_crt_get_key_id (crt=0x55b3a2d0, 
flags=, output_data=0x7fffc640 "", 
output_data_size=0x7fffc638)
at x509.c:2583
#7  0x557a4179 in dht::crypto::Certificate::getId 
(this=this@entry=0x7fffc7a0)
at crypto.cpp:627
#8  0x555fc928 in ring::RingAccount::loadIdentity 
(this=this@entry=0x55b35300)
at ringaccount.cpp:508
#9  0x555fdccd in ring::RingAccount::checkIdentityPath 
(this=0x55b35300)
at ringaccount.cpp:452
#10 0x5565232f in ring::Manager::loadAccount (
this=this@entry=0x55aef300 , 
node=..., 
errorCount=@0x7fffca4c: 0, accountOrder="61351441220ef85e/") at 
manager.cpp:2578
#11 0x556527fb in ring::Manager::loadAccountMap (
this=this@entry=0x55aef300 , 
node=...)
at manager.cpp:2615
#12 0x556531aa in ring::Manager::parseConfiguration (
this=this@entry=0x55aef300 )
at manager.cpp:237
#13 0x5565396f in ring::Manager::init (
this=0x55aef300 , config_file="")
at manager.cpp:287
#14 0x555c9e04 in DRing::start (config_file="") at ring_api.cpp:69
#15 0x55597453 in DBusClient::initLibrary 
(this=this@entry=0x55b24920, 
flags=flags@entry=0) at dbusclient.cpp:221
#16 0x55598691 in DBusClient::DBusClient (this=0x55b24920, flags=0, 
persistent=) at dbusclient.cpp:99
#17 0x5559113f in main (argc=1, argv=0x7fffdfe8) at main.cpp:194
(gdb)

But valgrind claim this is the problem:

==30187== Invalid read of size 8
==30187==at 0x4C2D800: memcpy@@GLIBC_2.14 (vg_replace_strmem.c:915)
==30187==by 0x6B6D31E: x86_sha1_update (in 
/usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28.41.0)
==30187==by 0x6B6D756: wrap_x86_hash_fast (in 
/usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28.41.0)
==30187==by 0x6AE4B25: _gnutls_hash_fast (in 
/usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28.41.0)
==30187==by 0x6AF182B: gnutls_fingerprint (in 
/usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28.41.0)
==30187==by 0x351627: dht::InfoHash::get(unsigned char const*, unsigned 
long) (infohash.cpp:57)
==30187==by 0x1B989C: get (infohash.h:185)
==30187==by 0x1B989C: ring::RingAccount::doRegister_() (ringaccount.cpp:884)
==30187==by 0x9AC396F: ??? (in 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.20)
==30187==by 0x6DD30A3: start_thread (pthread_create.c:309)
==30187==by 0xA31787C: clone (clone.S:111)
==30187==  Address 0xb39075d0 is not stack'd, malloc'd or (recently) free'd
==30187== 
==30187== 
==30187== Process terminating with default action of signal 11 (SIGSEGV)
==30187==  Access not within mapped region at address 0xB39075D0
==30187==at 0x4C2D800: memcpy@@GLIBC_2.14 (vg_replace_strmem.c:915)
==30187==by 0x6B6D31E: x86_sha1_update (in 
/usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28.41.0)
==30187==by 0x6B6D756: wrap_x86_hash_fast (in 
/usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28.41.0)
==30187==by 0x6AE4B25: _gnutls_hash_fast (in 
/usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28.41.0)
==30187==by 0x6AF182B: gnutls_fingerprint (in 
/usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28.41.0)
==30187==by 0x351627: dht::InfoHash::get(unsigned char const*, unsigned 
long) (infohash.cpp:57)
==30187==by 0x1B989C: get (infohash.h:185)
==30187==by 0x1B989C: ring::RingAccount::doRegister_() (ringaccount.cpp:884)

Bug#831322: debmirror consistently failing on unlink step for files in dep11 directory

2016-08-22 Thread Martin Dorey
Not the same file every day and a second run immediately after the first 
failure succeeds for me, on the three occurrences that I've noticed so far, 
making it just a minor issue for me.  It might have been happening to me every 
day for a while but any earlier failures will have been obscured by the 
excessive logging I added when I was experiencing 
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1562118.



Bug#835045: [pkg-gnupg-maint] Bug#835045: gnupg: cannot edit my key: "secret key parts are not available"

2016-08-22 Thread Julian Gilbey
On Mon, Aug 22, 2016 at 12:23:09PM +0200, Werner Koch wrote:
> On Sun, 21 Aug 2016 18:36, j...@debian.org said:
> 
> > gpg: secret key parts are not available
> 
> > And yet I do have my secret key available; "toggle" shows it quite
> > happily, for example.
> 
> I guess you took your primary key offline (replaced by a stub key) or
> you are using smartcard based keys.  Use gpg -K to check the key.  For
> example an old copy of my key listed with gpg 1.4:

Hi Werner,

Ah, thanks, that would be it!  Now I have to go and locate my primary
key (having had no recollection of doing this...).

Feel free to close this bug report.

Best wishes,

   Julian



Bug#835144: fresh upstream (4.5.0) is available - may be helps to resolve FTBFS issues

2016-08-22 Thread Yaroslav Halchenko
Package: mayavi2
Version: 4.4.3-2.1
Severity: wishlist

mayavi2 just got removed from testing (and thus python-mne I maintain was 
removed),
due to

#830342 [S|  |  ] [src:mayavi2] mayavi2: FTBFS: AttributeError: 'NoneType' 
object has no attribute 'find'

and Bug #830377: python-traits: FTBFS: dh_auto_test: pybuild --test -i 
python{version} -p 2.7 returned exit code 13   in python-traits

if looking at mayavi2, I just saw that new upstream is available:

$> uscan --report
uscan: Newest version of mayavi2 on remote site is 4.5.0, local version is 4.4.3
uscan:=> Newer package available from
  http://pypi.debian.net/mayavi/mayavi-4.5.0.tar.bz2

so thought it might be a good reason to look into uploading it, and possibly
addressing at least #830342 ? (didn't check)

Let me know if you need help

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

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

Versions of packages mayavi2 depends on:
ii  libc6 2.22-7
ii  libjs-jquery  1.11.3+dfsg-4
ii  python2.7.11-1
ii  python-apptools   4.3.0-1
ii  python-configobj  5.0.6-2
ii  python-envisage   4.4.0-1
ii  python-numpy [python-numpy-abi9]  1:1.11.1~rc1-1
ii  python-pkg-resources  20.10.1-1
ii  python-traits 4.5.0-1+b2
ii  python-traitsui   4.5.1-1
ii  python-vtk6   6.3.0+dfsg1-1
ii  python-wxgtk3.0   3.0.2.0+dfsg-1+b1
pn  python:any

mayavi2 recommends no packages.

Versions of packages mayavi2 suggests:
ii  ipython   2.4.1-1
ii  python-scipy  0.17.1-1

-- no debconf information



Bug#835143: ttf-tiresias: please make the build reproducible

2016-08-22 Thread Chris Lamb
Source: ttf-tiresias
Version: 0.1-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timezone
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], I noticed
that ttf-tiresias could not be built reproducibly.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/rules  2016-08-22 22:20:09.923418739 +0100
--- b/debian/rules  2016-08-22 22:21:25.660465702 +0100
@@ -3,7 +3,7 @@
dh $@
 
 override_dh_auto_build:
-   unzip -o -d . '*.zip'
+   TZ=UTC unzip -o -d . '*.zip'
rename 'y/A-Z/a-z/' *
rename 's/ /_/g' *
 


Bug#820333: RFA: hubicfuse -- Support for mounting Hubic drive

2016-08-22 Thread Sylvestre Ledru
-- Début de Rapport SpamAssassin -
Ce message est probablement du SPAM (message non sollicité envoyé en
masse, publicité, escroquerie...).

Cette notice a été ajoutée par le système d'analyse "SpamAssassin" sur
votre serveur de courrier "maralinga.yallingup.fr", pour vous
aider à identifier ce type de messages.

Le système SpamAssassin ajoute un en-tête "X-Spam-Flag: YES" aux
messages qu'il considère comme étant probablement du Spam.
Vous pouvez si vous le souhaitez utiliser cette caractéristique
pour régler un filtre dans votre logiciel de lecture de courrier,
afin de détruire ou de classer à part ce type de message.

Si ce robot a classifié incorrectement un message qui vous était
destiné, ou pour toute question, veuillez contacter l'administrateur
du système par e-mail à @@CONTACT_ADDRESS@@ .

Voir http://spamassassin.apache.org/tag/ pour plus de détails (en anglais).

Détails de l'analyse du message:   (6.3 points, 5.0 requis)
 2.7 RCVD_IN_PSBL   RBL: Received via a relay in PSBL
[195.154.220.89 listed in psbl.surriel.com]
 1.3 RCVD_IN_BL_SPAMCOP_NET RBL: Relais listé dans
http://spamcop.net/bl.shtml
  [Blocked - see ]
 0.8 BAYES_50   BODY: L'algorithme Bayésien a évalué la probabilité 
de spam
entre 40 et 60%
[score: 0.4780]
 1.4 RCVD_IN_BRBL_LASTEXT   RBL: RCVD_IN_BRBL_LASTEXT
[195.154.220.89 listed in bb.barracudacentral.org]

 Fin de Rapport SpamAssassin -

Le message original n'étant pas au format text brut, il est peut-être
dangereux de l'ouvrir avec votre logiciel e-mail ; en particulier il
pourrait contenir un virus, ou confirmer à l'expéditeur que votre
adresse e-mail est active, et peut recevoir du spam. Si vous voulez
lire ce message, et n'êtes pas certain de la sécurité de votre logiciel
e-mail, il est plus prudent d'enregistrer ce message sur votre disque
dur, et de l'afficher ensuite avec un éditeur de texte.

--- Begin Message ---
Le 22/08/2016 à 22:52, Stephen Kitt a écrit :
> Control: owner -1 !
> Control: retitle -1 ITA: hubicfuse -- Support for mounting Hubic drive
>
> On Mon, 22 Aug 2016 18:00:18 +0200, Sylvestre Ledru 
> wrote:
>> Le 22/08/2016 à 17:55, Stephen Kitt a écrit :
>>> I'm going in the opposite direction, so I might pick this up... Could
>>> you push the upstream branch to the Alioth repository? (And the
>>> pristine-tar branch if you have one!)  
>> Oups, done.
>> upstream + master
> Thanks! Do you have any tags to push too?
>
> Regards,
>
> Stephen

sorry again, pushed


S





signature.asc
Description: OpenPGP digital signature
--- End Message ---


Bug#618635: gsfonts: diff for NMU version 1:8.11+urwcyr1.0.7~pre44-4.3

2016-08-22 Thread Jakub Wilk

Control: tags 618635 + pending
Control: tags 817488 + patch
Control: tags 817488 + pending

I've prepared an NMU for gsfonts (versioned as 
1:8.11+urwcyr1.0.7~pre44-4.3) and uploaded it to DELAYED/10. Please feel 
free to tell me if I should delay it longer.


--
Jakub Wilk
diffstat for gsfonts-8.11+urwcyr1.0.7~pre44 gsfonts-8.11+urwcyr1.0.7~pre44

 changelog |   12 
 compat|2 +-
 control   |3 ++-
 postrm|2 +-
 rules |4 +++-
 5 files changed, 19 insertions(+), 4 deletions(-)


Control files: lines which differ (wdiff format)

Build-Depends: debhelper (>= [-4.0.0),-] {+5),+} sharutils
{+Depends: ${misc:Depends}+}

diff -Nru gsfonts-8.11+urwcyr1.0.7~pre44/debian/changelog gsfonts-8.11+urwcyr1.0.7~pre44/debian/changelog
--- gsfonts-8.11+urwcyr1.0.7~pre44/debian/changelog	2016-08-22 22:55:25.0 +0200
+++ gsfonts-8.11+urwcyr1.0.7~pre44/debian/changelog	2016-08-22 22:55:25.0 +0200
@@ -1,3 +1,15 @@
+gsfonts (1:8.11+urwcyr1.0.7~pre44-4.3) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Bump debhelper compatibility level to 5 (closes: #817488).
+Thanks to Niels Thykier for the bug report.
+  * Fix typo in the postrm scripts (closes: #618635).
+Thanks to Nathan Handler for the bug report and the patch.
+  * Add build-arch and build-indep targets.
+  * Add "Depends: ${misc:Depends}".
+
+ -- Jakub Wilk   Mon, 22 Aug 2016 22:53:12 +0200
+
 gsfonts (1:8.11+urwcyr1.0.7~pre44-4.2) unstable; urgency=high
 
   * Non-maintainer upload.
diff -Nru gsfonts-8.11+urwcyr1.0.7~pre44/debian/compat gsfonts-8.11+urwcyr1.0.7~pre44/debian/compat
--- gsfonts-8.11+urwcyr1.0.7~pre44/debian/compat	2016-08-22 22:55:25.0 +0200
+++ gsfonts-8.11+urwcyr1.0.7~pre44/debian/compat	2016-08-22 22:55:25.0 +0200
@@ -1 +1 @@
-4
+5
diff -Nru gsfonts-8.11+urwcyr1.0.7~pre44/debian/control gsfonts-8.11+urwcyr1.0.7~pre44/debian/control
--- gsfonts-8.11+urwcyr1.0.7~pre44/debian/control	2016-08-22 22:55:25.0 +0200
+++ gsfonts-8.11+urwcyr1.0.7~pre44/debian/control	2016-08-22 22:55:25.0 +0200
@@ -2,7 +2,7 @@
 Section: text
 Priority: optional
 Maintainer: Masayuki Hatta (mhatta) 
-Build-Depends: debhelper (>= 4.0.0), sharutils
+Build-Depends: debhelper (>= 5), sharutils
 Standards-Version: 3.8.0
 Uploaders: Torsten Landschoff 
 Homepage: http://www.ghostscript.com/
@@ -12,6 +12,7 @@
 
 Package: gsfonts
 Architecture: all
+Depends: ${misc:Depends}
 Conflicts: gs (<< 5.50-5), gs-aladdin (<< 6.50-4), gsfonts-x11 (<< 0.13)
 Description: Fonts for the Ghostscript interpreter(s)
  These are free look-alike fonts of the Adobe PostScript fonts.
diff -Nru gsfonts-8.11+urwcyr1.0.7~pre44/debian/postrm gsfonts-8.11+urwcyr1.0.7~pre44/debian/postrm
--- gsfonts-8.11+urwcyr1.0.7~pre44/debian/postrm	2016-08-22 22:55:25.0 +0200
+++ gsfonts-8.11+urwcyr1.0.7~pre44/debian/postrm	2016-08-22 22:55:25.0 +0200
@@ -21,7 +21,7 @@
 
 case "$1" in
 purge|remove)
-  if [ -x /usr/sbin/udpate-gsfontmap ]; then
+  if [ -x /usr/sbin/update-gsfontmap ]; then
 update-gsfontmap
   fi
 ;;
diff -Nru gsfonts-8.11+urwcyr1.0.7~pre44/debian/rules gsfonts-8.11+urwcyr1.0.7~pre44/debian/rules
--- gsfonts-8.11+urwcyr1.0.7~pre44/debian/rules	2016-08-22 22:55:25.0 +0200
+++ gsfonts-8.11+urwcyr1.0.7~pre44/debian/rules	2016-08-22 22:55:25.0 +0200
@@ -28,7 +28,9 @@
 	touch configure-stamp
 
 
-build: build-stamp
+build: build-arch build-indep
+build-arch:
+build-indep: build-stamp
 
 build-stamp: configure-stamp 
 	dh_testdir


Bug#820333: RFA: hubicfuse -- Support for mounting Hubic drive

2016-08-22 Thread Stephen Kitt
Control: owner -1 !
Control: retitle -1 ITA: hubicfuse -- Support for mounting Hubic drive

On Mon, 22 Aug 2016 18:00:18 +0200, Sylvestre Ledru 
wrote:
> Le 22/08/2016 à 17:55, Stephen Kitt a écrit :
> > I'm going in the opposite direction, so I might pick this up... Could
> > you push the upstream branch to the Alioth repository? (And the
> > pristine-tar branch if you have one!)  
> Oups, done.
> upstream + master

Thanks! Do you have any tags to push too?

Regards,

Stephen


pgpg5klqWLZhB.pgp
Description: OpenPGP digital signature


Bug#835142: fontconfig trigger can run with half-installed fonts

2016-08-22 Thread Simon Kirby
Package: fontconfig
Version: 2.11.0-6.5
Severity: important
User: Simon Kirby 

Similar to #828037, I just experienced an issue with fonts after an
"apt-get upgrade". However, this was caused by system-wide cache learning
about half-installed fonts with the .dpkg-new extension.

Pidgin begun drawing some characters as boxes. The cause seems to be that
the fontconfig cache was regenerated with some ".dpkg-new" files, which
were gone once apt-get finished:

stderr output and excerpt of "strace -e access" of pidgin starting:
(Pidgin:24512): Pango-WARNING **: failed to create cairo scaled font, expect 
ugly output. the offending font is 'DejaVu Sans Bold 13.1982421875'
(Pidgin:24512): Pango-WARNING **: font_face status is: file not found
access("/usr/share/fonts/truetype/dejavu/DejaVuSans-Bold.ttf.dpkg-new", R_OK) = 
-1 ENOENT (No such file or directory)

[sroot@oof:/var/cache/fontconfig]# grep -r DejaVuSans-Bold.ttf.dpkg-new .
Binary file ./d589a48862398ed80a3d6066f4f56f4c-le64.cache-4 matches

[sim@oof:/home/sim]% fc-list | grep dpkg
/usr/share/fonts/truetype/liberation/LiberationMono-Bold.ttf.dpkg-new: 
LiberationMono\-Bold.ttf
/usr/share/fonts/truetype/dejavu/DejaVuSans-Bold.ttf.dpkg-new: DejaVu 
Sans:style=Bold

My root shell runs with PAGER set to "less -Q -j16" which breaks debconf
frontends lately (another bug I need to submit), so an apt-get run often
aborts without finishing unless I remember to run it again with PAGER
cleared. I am not sure if this is the cause or not here, I see that
/var/log/dpkg.log has some interesting trigger information, which I've
posted at http://0x.ca/sim/ref/fontconfig/dpkg.log . Here is an excerpt
by "grep font | uniq":

2016-08-19 23:40:25 upgrade fonts-liberation:all 1.07.4-1 2.00.1-2
2016-08-19 23:40:25 status half-configured fonts-liberation:all 1.07.4-1
2016-08-19 23:40:25 status unpacked fonts-liberation:all 1.07.4-1
2016-08-19 23:40:25 status half-installed fonts-liberation:all 1.07.4-1
2016-08-19 23:40:25 status triggers-pending fontconfig:amd64 2.11.0-6.5
2016-08-19 23:40:25 status half-installed fonts-liberation:all 1.07.4-1
2016-08-19 23:40:25 status unpacked fonts-liberation:all 2.00.1-2
2016-08-19 23:40:42 upgrade fonts-opensymbol:all 2:102.7+LibO5.2.0-1 
2:102.7+LibO5.2.0-2
2016-08-19 23:40:42 status half-configured fonts-opensymbol:all 
2:102.7+LibO5.2.0-1
2016-08-19 23:40:42 status unpacked fonts-opensymbol:all 2:102.7+LibO5.2.0-1
2016-08-19 23:40:42 status half-installed fonts-opensymbol:all 
2:102.7+LibO5.2.0-1
2016-08-19 23:40:42 status unpacked fonts-opensymbol:all 2:102.7+LibO5.2.0-2
2016-08-19 23:40:52 upgrade fonts-dejavu-core:all 2.36-1 2.37-1
2016-08-19 23:40:52 status half-configured fonts-dejavu-core:all 2.36-1
2016-08-19 23:40:52 status unpacked fonts-dejavu-core:all 2.36-1
2016-08-19 23:40:52 status half-installed fonts-dejavu-core:all 2.36-1
2016-08-19 23:40:52 status unpacked fonts-dejavu-core:all 2.37-1
2016-08-19 23:40:52 upgrade fonts-dejavu-extra:all 2.36-1 2.37-1
2016-08-19 23:40:52 status half-configured fonts-dejavu-extra:all 2.36-1
2016-08-19 23:40:52 status unpacked fonts-dejavu-extra:all 2.36-1
2016-08-19 23:40:52 status half-installed fonts-dejavu-extra:all 2.36-1
2016-08-19 23:40:52 status unpacked fonts-dejavu-extra:all 2.37-1
2016-08-19 23:40:53 upgrade fonts-dejavu:all 2.36-1 2.37-1
2016-08-19 23:40:53 status half-configured fonts-dejavu:all 2.36-1
2016-08-19 23:40:53 status unpacked fonts-dejavu:all 2.36-1
2016-08-19 23:40:53 status half-installed fonts-dejavu:all 2.36-1
2016-08-19 23:40:53 status unpacked fonts-dejavu:all 2.37-1
2016-08-19 23:41:14 configure fonts-dejavu-core:all 2.37-1 
2016-08-19 23:41:14 status unpacked fonts-dejavu-core:all 2.37-1
2016-08-19 23:41:14 status half-configured fonts-dejavu-core:all 2.37-1
2016-08-19 23:41:14 status installed fonts-dejavu-core:all 2.37-1
2016-08-19 23:41:16 configure fonts-liberation:all 2.00.1-2 
2016-08-19 23:41:16 status unpacked fonts-liberation:all 2.00.1-2
2016-08-19 23:41:16 status half-configured fonts-liberation:all 2.00.1-2
2016-08-19 23:41:16 status installed fonts-liberation:all 2.00.1-2
2016-08-19 23:41:22 configure fonts-opensymbol:all 2:102.7+LibO5.2.0-2 
2016-08-19 23:41:22 status unpacked fonts-opensymbol:all 2:102.7+LibO5.2.0-2
2016-08-19 23:41:22 status half-configured fonts-opensymbol:all 
2:102.7+LibO5.2.0-2
2016-08-19 23:41:22 status installed fonts-opensymbol:all 2:102.7+LibO5.2.0-2
2016-08-19 23:41:22 configure fonts-dejavu-extra:all 2.37-1 
2016-08-19 23:41:22 status unpacked fonts-dejavu-extra:all 2.37-1
2016-08-19 23:41:22 status half-configured fonts-dejavu-extra:all 2.37-1
2016-08-19 23:41:22 status installed fonts-dejavu-extra:all 2.37-1
2016-08-19 23:41:23 trigproc fontconfig:amd64 2.11.0-6.5 
2016-08-19 23:41:23 status half-configured fontconfig:amd64 2.11.0-6.5
2016-08-19 23:41:25 status installed fontconfig:amd64 2.11.0-6.5
2016-08-19 23:41:25 configure fonts-dejavu:all 2.37-1 
2016-08-19 23:41:25 status unpacked 

Bug#835141: RFS: telegram-purple/1.3.0-1 [ITP] -- Purple plugin to support Telegram

2016-08-22 Thread Ben Wiederhake
Package: sponsorship-requests
Version: sponsorship-requests
Severity: wishlist

Dear mentors,

in this mail:
(1) Asking potential sponsor about state
(2) normal RFS stuff
(3) things where I need help


(1) @Josue Ortega:  Are you still interested in sponsoring this package?  If
not, no problem, just please say so :)


(2) normal RFS stuff:
I am looking for a sponsor for my package "telegram-purple":

 * Package name: telegram-purple
   Version : 1.3.0-1
   Upstream Author : Matthias Jentsch 
 * URL : https://github.com/majn/telegram-purple
 * License : GPL2+
   Programming Lang: C
   Section : net

It builds those binary packages:

  telegram-purple - Purple plugin to support Telegram

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

https://mentors.debian.net/package/telegram-purple

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

dget -x https://mentors.debian.net/debian/pool/main/t/telegram-purple
/telegram-purple_1.3.0-1.dsc

Or if you prefer to view the tree:

https://github.com/BenWiederhake/telegram-purple/tree/debian-develop

The package is (of course) mostly lintian clean and passes several other tests.
- Lintian "spelling-error-in-binary":  it's in a debug message of tgl.
- Lintian "hardening-no-bindnow":  see below

There is no pidgin-packaging team, otherwise I would have contacted
them nearly a year ago.

Please read README.source for some packaging choices.

Changes since the last upload (February 2016):
- new upstream version (finally! :D)
- bump standards from 3.9.6.0 to 3.9.8.0 (no-op)
- simplify orig-tar generation (upstream support)
- check for any changed copyrights (removal of "rawtar" process)
- reduce and fix d/docs
- update README.source ('make dist' and typos)
- update dev chat link in d/upstream/metadata


(3) Things where I need help:

The suggested fix for "hardening-no-bindnow" (namely, `hardening=+all`,
which inserts a `-fPIE`) breaks the build, as we need to build an
intermediate shared library, tgl, which can't work with PIE.  The
failing call to gcc looks like this:
gcc -shared -o libs/libtgl.so objs/${lot-of-objects}.o -fPIE -pie \
  -Wl,-z,relro -Wl,-z,now -L/usr/lib/${and/so/on} -rdynamic -ggdb -lz
-lgcrypt
/${path/to}/Scrt1.o: In function `_start':
(.text+0x20): undefined reference to `main'
Since technically that file doesn't need to be built, the final
shared library (would) also fails:
gcc -shared -o bin/telegram-purple.so objs/${lots}.o tgl/libs/libtgl.a \
  -fPIE -pie -Wl,-z,relro -Wl,-z,now -L${paths} -l${things} -rdynamic -ggdb
Being a shared library, there naturally is no `main`, and a shared library
shouldn't be compiled with -fPIE.  Thus, I ignore this warning.

QA on mentors claims that the watchfile isn't valid:
A watch file is present but doesn't work
- Scanning for watchfiles in .
- Found watchfile in ./debian
- Scan finished
I can't reproduce this on my local 'testing' installation, nor
'unstable' chroot, as `./debian/rules get-orig-source` works as
expected, and I don't know QA's exact invocation of uscan, or the
error they see.

Regards,
Ben Wiederhake



Bug#835140: ros-geometry-experimental: FTBFS: Could not find messages

2016-08-22 Thread Aaron M. Ucko
Source: ros-geometry-experimental
Version: 0.5.13-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of ros-geometry-experimental against libgeometry-msgs-dev
1.12.4-3 have been failing:

  Could not find messages which
  '/«PKGBUILDDIR»/tf2_msgs/msg/TFMessage.msg'
  depends on.  Did you forget to specify generate_messages(DEPENDENCIES ...)?

  Cannot locate message [TransformStamped] in package [geometry_msgs] with
  paths [['/usr/share/geometry_msgs/cmake/../msg']]

Could you please take a look?  I suspect you'll need an explicit
build dependency on the split-out ros-geometry-msgs package.

Thanks!



Bug#835139: tj3: Provide vim syntax highlighting for tjp and tji files

2016-08-22 Thread Christopher Hoskin
Package: tj3
Version: 3.6.0-2
Severity: wishlist
Tags: patch

Dear Maintainer,

TaskJuggler includes a Vim plugin for syntax highlighting for tjp and tji files 
[0]. This should be packaged in accordance with Debian's Vim packaging policy 
[1]. The attached patch provides such a package. It would be great if you could 
apply this to the source package.

Thanks.

Christopher Hoskin

[0] 
http://www.taskjuggler.org/tj3/manual/Installation.html#Installing_the_Vim_Support
[1] https://pkg-vim.alioth.debian.org/vim-policy.html/

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

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

Versions of packages tj3 depends on:
ii  ruby 1:2.3.0+4
ii  ruby-mail2.6.4+dfsg1-1
ii  ruby-term-ansicolor  1.3.0-1

tj3 recommends no packages.

tj3 suggests no packages.

-- no debconf information
diff --git a/debian/control b/debian/control
index e6153b2..094638b 100644
--- a/debian/control
+++ b/debian/control
@@ -32,3 +32,15 @@ Description: project management software, aka TaskJuggler
  to the completion of the project. It assists you during project scoping,
  resource assignment, cost and revenue planing, risk and communication
  management.
+
+Package: vim-tjp
+Architecture: all
+Recommends: vim-addon-manager
+Description: vim addon for TaskJuggler .tjp files
+ TaskJuggler is project management software for project scoping, resource 
+ assignment, cost and revenue planing, risk and communication management. It is
+ packaged in Debian as tj3.
+ .
+ This package provides a plugin for the vim editor prviding syntax highlighting
+ for .tjp files.
+
diff --git a/debian/rules b/debian/rules
index 26f8596..9287874 100755
--- a/debian/rules
+++ b/debian/rules
@@ -6,6 +6,12 @@
 override_dh_auto_build:
 	dh_auto_build
 	localehelper LANG=en_US.UTF-8 rake manual
+	rake vim 
+
+override_dh_clean:
+	rm -rf manual/html
+	rm data/tjp.vim
+	dh_clean
 
 override_dh_auto_test:
 	rake spec
diff --git a/debian/vim-tjp.install b/debian/vim-tjp.install
new file mode 100644
index 000..3ea6ab3
--- /dev/null
+++ b/debian/vim-tjp.install
@@ -0,0 +1,3 @@
+data/tjp.vim /usr/share/vim/addons/syntax/
+debian/vim/	/usr/share/
+
diff --git a/debian/vim/addons/ftdetect/tjp.vim b/debian/vim/addons/ftdetect/tjp.vim
new file mode 100644
index 000..401e13b
--- /dev/null
+++ b/debian/vim/addons/ftdetect/tjp.vim
@@ -0,0 +1,2 @@
+autocmd BufNewFile,BufRead *.tjp,*.tji setfiletype tjp
+
diff --git a/debian/vim/registry/vim-tjp.yaml b/debian/vim/registry/vim-tjp.yaml
new file mode 100644
index 000..c4a119c
--- /dev/null
+++ b/debian/vim/registry/vim-tjp.yaml
@@ -0,0 +1,5 @@
+addon: tjp
+description: "vim addon for TaskJuggler .tjp files"
+files:
+  - syntax/tjp.vim
+  - ftdetect/tjp.vim


Bug#835138: form: FTBFS: tests fail on several architectures

2016-08-22 Thread Aaron M. Ucko
Source: form
Version: 4.1-1
Severity: important
Justification: fails to build from source

form's tests failed on several architectures, as detailed at
https://buildd.debian.org/status/logs.php?pkg=form=4.1-1 .
Could you please take a look?

Thanks!



Bug#834644: RM: fpc reverse dependencies [powerpc] -- ROM; fpc doesn't build anymore on powerpc

2016-08-22 Thread Paul Gevers
Control: tags -1 moreinfo

On Wed, 17 Aug 2016 21:39:36 +0200 Paul Gevers  wrote:
> I believe it is time to acknowledge that no solution will come soon and
> therefor I request removal of all reverse dependencies of fpc on
> powerpc.

Please hold. Seems like upstream may have come up with a solution. I
will upload a patched version of fpc to the archive. One of the
following days, I will re-bootstrap fpc on powerpc and see where we get.

Paul



signature.asc
Description: OpenPGP digital signature


Bug#835137: neutron-lbaas-agent: Missing neutron-lbaasv2-agent init script

2016-08-22 Thread Turbo Fredriksson
Package: neutron-lbaas-agent
Version: 1:8.0.0-3
Severity: important

The package is missing the init script for the v2 agent.

I duplicated neutron-lbaas-agent (changing any reference to
"{lbaas|LBaaS}" to "lbaasv2|LBaaS v2}" (etc) init script and
got it working.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/16 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 neutron-lbaas-agent depends on:
ii  adduser   3.115
ii  debconf   1.5.59
ii  init-system-helpers   1.36
ii  lsb-base  9.20160629
ii  neutron-common2:8.1.2-1
ii  python-neutron-lbaas  1:8.0.0-3
pn  python2.7:any 

neutron-lbaas-agent recommends no packages.

neutron-lbaas-agent suggests no packages.

-- Configuration Files:
/etc/neutron/lbaas_agent.ini changed [not included]
/etc/neutron/neutron_lbaas.conf changed [not included]
/etc/neutron/services_lbaas.conf changed [not included]

-- no debconf information



Bug#834502: Proposed NMU, debdiff attached

2016-08-22 Thread Daniel Lange
Control: tags -1 + patch

The buffer overflow results from strings that are too short for a strcpy to 
always succeed.

Patch from 

 attached.

The input word is guaranteed to be at most STRINGSIZE-1 in length. One of the
mangle operations involves duplicating the input word, resulting in a string
twice the length to be accommodated by both area variables.

Howard Guo  2016-08-17

diff -rupN 3/lib/rules.c 3-patched/lib/rules.c
--- 3/lib/rules.c	2016-08-16 14:16:24.033261876 +0200
+++ 3-patched/lib/rules.c	2016-08-17 13:57:14.485782894 +0200
@@ -434,9 +434,8 @@ Mangle(input, control)		/* returns a poi
 {
 int limit;
 register char *ptr;
-static char area[STRINGSIZE];
-char area2[STRINGSIZE];
-area[0] = '\0';
+static char area[STRINGSIZE * 2] = {0};
+char area2[STRINGSIZE * 2] = {0};
 strcpy(area, input);
 
 for (ptr = control; *ptr; ptr++)


Bug#835124: dolphin: search doesn't work properly when started inside a linked folder

2016-08-22 Thread Maria
In Step 5 I forget to write the main information... It should have been:

Step 5) I get no result but if I click on "Everywhere" I am getting all
files and folders containing "Neuer" including this 'Neuer Ordner'.



Maria:
> Package: dolphin
> Version: 4:16.04.2-2
> Severity: normal
> 
> Dear Maintainer,
> 
> step 1) In my home I have a link into the folder foo. So '~/foo' links to
> '~/bar/foo'.
> step 2) In that folder there is a subfolder called 'Neuer Ordner'
> step 3) I am going into the folder '~/foo'
> step 4) I start the search with "Filename" and "From Here (foo)"; searchterm 
> is
> "Neuer"
> step 5) I click on "Everywhere" and getting all files and folders containing
> "Neuer"
> 
> step 6) I am changing into '~/bar/foo'
> step 7) I open the search from there with "Filename" and "From Here (foo)";
> searchterm is "Neuer"
> step 8) I get the correct result 'Neuer Ordner' (clicking on "Everywhere" 
> gives
> the same correct result like above)
> 
> Thanks - Maria
> 
> 
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
> 'testing'), (100, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages dolphin depends on:
> ii  libc6  2.23-4
> ii  libdolphinvcs5 4:16.04.2-2
> ii  libkf5baloo5   5.23.0-1
> ii  libkf5baloowidgets516.04.0-1
> ii  libkf5bookmarks5   5.23.0-1
> ii  libkf5codecs5  5.23.0-1
> ii  libkf5completion5  5.23.0-1
> ii  libkf5configcore5  5.23.0-1
> ii  libkf5configgui5   5.23.0-1
> ii  libkf5configwidgets5   5.23.0-1
> ii  libkf5coreaddons5  5.23.0-1
> ii  libkf5crash5   5.23.0-1
> ii  libkf5dbusaddons5  5.23.0-1
> ii  libkf5filemetadata35.23.0-1
> ii  libkf5i18n55.23.0-1
> ii  libkf5iconthemes5  5.23.0-1
> ii  libkf5itemviews5   5.23.0-1
> ii  libkf5jobwidgets5  5.23.0-1
> ii  libkf5kcmutils55.23.0-1
> ii  libkf5kiocore5 5.23.0-1
> ii  libkf5kiofilewidgets5  5.23.0-1
> ii  libkf5kiowidgets5  5.23.0-1
> ii  libkf5newstuff55.23.0-1
> ii  libkf5notifications5   5.23.0-1
> ii  libkf5parts5   5.23.0-1
> ii  libkf5service-bin  5.23.0-1
> ii  libkf5service5 5.23.0-1
> ii  libkf5solid5   5.23.0-1
> ii  libkf5textwidgets5 5.23.0-1
> ii  libkf5widgetsaddons5   5.23.0-1
> ii  libkf5windowsystem55.23.0-1
> ii  libkf5xmlgui5  5.23.0-1
> ii  libphonon4qt5-44:4.9.0-4
> ii  libqt5core5a   5.6.1+dfsg-3+b1
> ii  libqt5dbus55.6.1+dfsg-3+b1
> ii  libqt5gui5 5.6.1+dfsg-3+b1
> ii  libqt5widgets5 5.6.1+dfsg-3+b1
> ii  libqt5xml5 5.6.1+dfsg-3+b1
> ii  libstdc++6 6.1.1-11
> ii  phonon4qt5 4:4.9.0-4
> 
> Versions of packages dolphin recommends:
> ii  kio-extras  4:16.04.2-1
> ii  ruby1:2.3.0+4
> 
> Versions of packages dolphin suggests:
> ii  dolphin-plugins  4:16.04.0-1
> 
> -- no debconf information
> 



Bug#835136: lucene-solr: [INTL:nl] Dutch translation of debconf messages

2016-08-22 Thread Frans Spiesschaert
 

Package: lucene-solr 
Severity: wishlist 
Tags: l10n patch 
 

Dear Maintainer, 
 
== 
Please find attached the Dutch translation of lucene-solr debconf messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
=== 

-- 
Cheers,
Frans

===
http://home.base.be/vt6362833/



nl.po.gz
Description: application/gzip


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


Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

2016-08-22 Thread Markus Koschany
Control: tags -1 unreproducible
Control: severity -1 normal

On Thu, 18 Aug 2016 14:22:57 + Santiago Vila  wrote:
> Package: src:xmlgraphics-commons
> Version: 2.1-1
> Severity: serious
> Tags: patch
> 
> Dear maintainer:
> 
> I tried to build this package with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:
[...]

This package builds fine in a clean cowbuilder chroot environment and on
Debian's official buildd network. The issue is unreproducible hence I'm
going to downgrade the severity to normal until someone else can confirm
that this is a release critical issue. So far I cannot confirm this.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature


Bug#835135: ITP: r-bioc-metagenomeseq -- GNU R statistical analysis for sparse high-throughput sequencing

2016-08-22 Thread Andreas Tille
Package: wnpp
Severity: wishlist
Owner: Andreas Tille 

* Package name: r-bioc-metagenomeseq
  Version : 1.14.2
  Upstream Author : Joseph N. Paulson 
* URL : 
http://www.bioconductor.org/packages/release/bioc/html/metagenomeSeq.html
* License : Artistic-2.0
  Programming Lang: GNU R
  Description : GNU R statistical analysis for sparse high-throughput 
sequencing
 MetagenomeSeq is designed to determine features (be it Operational
 Taxanomic Unit (OTU), species, etc.) that are differentially abundant
 between two or more groups of multiple samples. metagenomeSeq is
 designed to address the effects of both normalization and under-sampling
 of microbial communities on disease association detection and the
 testing of feature correlations.


Remark: This package will be maintained by the Debian Med team at
   
svn://anonscm.debian.org/debian-med/trunk/packages/R/r-bioc-metagenomeseq/trunk/



Bug#835134: byobu: [INTL:nl] Dutch translation of debconf messages

2016-08-22 Thread Frans Spiesschaert
 

Package: byobu 
Severity: wishlist 
Tags: l10n patch 
 

Dear Maintainer, 
 
== 
Please find attached the Dutch translation of byobu debconf messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
=== 

-- 
Cheers,
Frans

===
http://home.base.be/vt6362833/



nl.po.gz
Description: application/gzip


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


Bug#835133: libnet-jabber-perl: FTBFS in testing

2016-08-22 Thread Santiago Vila
Package: libnet-jabber-perl
Version: 2.0-6
Severity: serious

Dear maintainer:

This package fails to build from source in stretch.

I can reproduce the failure as many times as desired in two different
virtual machines where /etc/timezone is "Etc/UTC".

As usual, I strongly encourage everybody to make uploads in
source-only form, so that we get pretty official build logs here:

https://buildd.debian.org/status/package.php?p=libnet-jabber-perl

I attach two different build logs, from two different autobuilders.

(My build logs are for "dpkg-buildpackage -A", but since this
package is "Arch: all", this is equivalent to a FTBFS bug in the
traditional sense).

Thanks.

libnet-jabber-perl_2.0-6_amd64-20160818T171131Z.gz
Description: application/gzip


libnet-jabber-perl_2.0-6_amd64-20160822T164949Z.gz
Description: application/gzip


Bug#826300: [Pkg-pascal-devel] Bug#826300: Share knowledge on fpc and powerpc issue

2016-08-22 Thread Paul Gevers
Hi,

On 22-08-16 17:49, Abou Al Montacir wrote:
> It seems that this is now fixed!
>
>>> Can you please check if r34366 resolves the problem?
> 
>>Sorry, I made a mistake, you need r34368 as well.
> 
> Can anybody test this?

I am including the patch right now in our packaging. I'll upload it to
the archive and I'll then continue bootstrapping on powerpc. Give me a
couple of days. Feel free to bootstrap powerpc before I do.

Paul



signature.asc
Description: OpenPGP digital signature


Bug#835132: dolphin: search doesn't work as expected

2016-08-22 Thread Maria
Package: dolphin
Version: 4:16.04.2-2
Severity: normal

Dear Maintainer,

in the documentation of Dolphin it is written, that "*foo* and foo are
equivalent" for the search function. That doesn't work as expected:

Step 1) I am inside the folder '~/bar/foo', inside that folder is a textfile
with the name 'foobar.txt'.
Step 2) I open the search function and search for "bar" or "bar.txt".
Step 3) the file foobar.txt is not found, no matter which options are chosen.

Control steps:
Step 4) When I search for "foo" I get the right result.
Step 5) When I search for "*bar" or "*bar.txt" I get the right result.

Oddly different with numbers:
Step 6) I create the file '~/bar/foo/190.txt'
Step 7) I open the search, searching for "19"
Step 8) no result

Step 9) I search for "190" and get the right result.

Thanks - Maria



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

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

Versions of packages dolphin depends on:
ii  libc6  2.23-4
ii  libdolphinvcs5 4:16.04.2-2
ii  libkf5baloo5   5.23.0-1
ii  libkf5baloowidgets516.04.0-1
ii  libkf5bookmarks5   5.23.0-1
ii  libkf5codecs5  5.23.0-1
ii  libkf5completion5  5.23.0-1
ii  libkf5configcore5  5.23.0-1
ii  libkf5configgui5   5.23.0-1
ii  libkf5configwidgets5   5.23.0-1
ii  libkf5coreaddons5  5.23.0-1
ii  libkf5crash5   5.23.0-1
ii  libkf5dbusaddons5  5.23.0-1
ii  libkf5filemetadata35.23.0-1
ii  libkf5i18n55.23.0-1
ii  libkf5iconthemes5  5.23.0-1
ii  libkf5itemviews5   5.23.0-1
ii  libkf5jobwidgets5  5.23.0-1
ii  libkf5kcmutils55.23.0-1
ii  libkf5kiocore5 5.23.0-1
ii  libkf5kiofilewidgets5  5.23.0-1
ii  libkf5kiowidgets5  5.23.0-1
ii  libkf5newstuff55.23.0-1
ii  libkf5notifications5   5.23.0-1
ii  libkf5parts5   5.23.0-1
ii  libkf5service-bin  5.23.0-1
ii  libkf5service5 5.23.0-1
ii  libkf5solid5   5.23.0-1
ii  libkf5textwidgets5 5.23.0-1
ii  libkf5widgetsaddons5   5.23.0-1
ii  libkf5windowsystem55.23.0-1
ii  libkf5xmlgui5  5.23.0-1
ii  libphonon4qt5-44:4.9.0-4
ii  libqt5core5a   5.6.1+dfsg-3+b1
ii  libqt5dbus55.6.1+dfsg-3+b1
ii  libqt5gui5 5.6.1+dfsg-3+b1
ii  libqt5widgets5 5.6.1+dfsg-3+b1
ii  libqt5xml5 5.6.1+dfsg-3+b1
ii  libstdc++6 6.1.1-11
ii  phonon4qt5 4:4.9.0-4

Versions of packages dolphin recommends:
ii  kio-extras  4:16.04.2-1
ii  ruby1:2.3.0+4

Versions of packages dolphin suggests:
ii  dolphin-plugins  4:16.04.0-1

-- no debconf information



Bug#816313: dash: executes binary data as a shell script in case of ENOEXEC (Exec format error)

2016-08-22 Thread Vincent Lefevre
On 2016-08-22 19:28:58 +0200, Jakub Wilk wrote:
> * Vincent Lefevre , 2016-02-29, 20:17:
> > $ /bin/dash -c tadd.exe
> > ./tadd.exe: 1: ./tadd.exe: MZ��¸@º´: not found
> > ./tadd.exe: 2: ./tadd.exe: : not found
> > ./tadd.exe: 1: ./tadd.exe: @.bss : not found
> > ./tadd.exe: 1: ./tadd.exe: .textd*,: not found
> > ./tadd.exe: 3: ./tadd.exe: JPL2@�.idata: not found
> > ./tadd.exe: 3: ./tadd.exe: u
> > : not found
> > ./tadd.exe: 4: ./tadd.exe: ~@0�.CRT4�@0�.tls: not found
> > ./tadd.exe: 5: ./tadd.exe: @B/81P: not found
> > ./tadd.exe: 13: ./tadd.exe: Syntax error: Missing '}'
> 
> This is standards-compliant behavior. SUSv3[0] reads:
> > If the execve() function fails due to an error equivalent to the
> > [ENOEXEC] error defined in the System Interfaces volume of IEEE Std
> > 1003.1-2001, the shell shall execute a command equivalent to having a
> > shell invoked with the pathname resulting from the search as its first
> > operand, with any remaining arguments passed to the new shell, except
> > that the value of "$0" in the new shell may be set to the command name.
> > If the executable file is not a text file, the shell may bypass this
> > command execution.

This is not because it is a standards-compliant behavior that it is
acceptable for data integrity. Things have evolved. If this were
decided again nowadays, it would probably not just a "may" (I suppose
that the intent was to allow a script working on included binary data,
such as compressed data, but even in such a case, the first word
would not contain non-printable characters). Nowadays one needs to
take into account:
  * Executables for other platforms may be more common than in the
past.
  * Security is more important (trying to execute binary data as a
shell script might be an attempt to exploit a vulnerability).

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



Bug#835131: freeipa: CVE-2016-5404: Insufficient privileges check in certificate revocation

2016-08-22 Thread Salvatore Bonaccorso
Source: freeipa
Version: 4.0.5-6
Severity: grave
Tags: security upstream
Forwarded: https://fedorahosted.org/freeipa/ticket/6232



*** /tmp/freeipa.reportbug
Package: freeipa
Severity: FILLINSEVERITY
Tags: security

Hi,

the following vulnerability was published for freeipa.

CVE-2016-5404[0]:
insufficient permission check

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-5404
[1] https://fedorahosted.org/freeipa/ticket/6232

Regards,
Salvatore



Bug#599902: add a cron entry to run mairix for each users

2016-08-22 Thread Sean Whitton
control: tag -1 +moreinfo

Dear Thomas,

This looks useful, though instead of enabling it by default I'd like to
ship it in /usr/share/doc/mairix/examples.

There is a problem with your script as it stands: it assumes that all
user home directories are under /home and that /home/username is the
home directory of the user username.  The script shouldn't assume this.
If you can avoid the assumption, I can include it in the package.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#835130: ircd-ircu: please make the build reproducible

2016-08-22 Thread Chris Lamb
Source: ircd-ircu
Version: 2.10.12.10.dfsg1-1.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], I noticed
that ircd-ircu could not be built reproducibly.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/ircd/version.c.SH 2016-08-22 20:22:46.861630224 +0100
--- b/ircd/version.c.SH 2016-08-22 20:27:14.677622664 +0100
@@ -14,7 +14,13 @@
 
 generation=`expr $generation + 1`
 
-creation=`date | \
+if test -n "$SOURCE_DATE_EPOCH"
+then
+  now=`LC_ALL=C date --utc --date="@$SOURCE_DATE_EPOCH"`
+else
+  now=`date`
+fi
+creation=`echo $now | \
 awk '{if (NF == 6) \
 { print $1 " " $2 " " $3 " " $6 " at " $4 " " $5 } \
 else \


Bug#835129: dateutils: please make the build reproducible

2016-08-22 Thread Chris Lamb
Source: dateutils
Version: 0.3.1-1.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], I noticed
that dateutils could not be built reproducibly.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/0002-reproducible-build.diff   1970-01-01 
01:00:00.0 +0100
--- b/debian/patches/0002-reproducible-build.diff   2016-08-22 
20:22:06.728424663 +0100
@@ -0,0 +1,54 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2016-08-22
+
+--- dateutils-0.3.1.orig/build-aux/yuck.c
 dateutils-0.3.1/build-aux/yuck.c
+@@ -1349,6 +1349,38 @@ bollocks:
+   _exit(EXIT_FAILURE);
+ }
+ 
++static time_t
++get_current_time(void)
++{
++  time_t now;
++  char *source_date_epoch, *endptr;
++  unsigned long long epoch;
++
++  source_date_epoch = getenv("SOURCE_DATE_EPOCH");
++
++  if (!source_date_epoch) {
++  return time(NULL);
++  }
++
++  errno = 0;
++  epoch = strtoull(source_date_epoch, , 10);
++
++  if ((errno == ERANGE && (epoch == ULLONG_MAX || epoch == 0)) || (errno 
!= 0 && epoch == 0)) {
++  now = (time_t)-1;
++  } else if (endptr == source_date_epoch) {
++  now = (time_t)-1;
++  } else if (*endptr != '\0') {
++  now = (time_t)-1;
++  } else if (epoch > ULONG_MAX) {
++  now = (time_t)-1;
++  } else {
++  now = (time_t)epoch;
++  }
++
++  return now;
++}
++
++
+ 
+ static int
+ wr_pre(void)
+@@ -1432,7 +1464,7 @@ wr_man_date(void)
+   char buf[32U];
+   int rc = 0;
+ 
+-  if ((now = time(NULL)) == (time_t)-1) {
++  if ((now = get_current_time()) == (time_t)-1) {
+   rc = -1;
+   } else if ((tp = gmtime()) == NULL) {
+   rc = -1;
--- a/debian/patches/series 2016-08-22 20:01:29.991392761 +0100
--- b/debian/patches/series 2016-08-22 20:17:05.127120394 +0100
@@ -1 +1,2 @@
 0001-do-not-use-march-native-compiler-flags.diff
+0002-reproducible-build.diff


Bug#835128: Mergeback of apt-transport-tor into apt?

2016-08-22 Thread David Kalnischkies
Package: apt-transport-tor
Version: 0.2.1-1
Severity: important
Tags: sid stretch
X-Debbugs-CC: de...@lists.debian.org

Hi,

as stated earlier this month in: 
https://lists.debian.org/deity/2016/08/msg00012.html
I would like to discuss the future of apt-transport-tor, rational:

On Thu, Aug 04, 2016 at 06:08:26PM +0200, David Kalnischkies wrote:
> back in 2014 then apt-transport-tor was introduced it started as
> a pretty straight copy of apt-transport-https with the reasoning of
> being able to backport it (#745259).
>
> It is two years later now with an eye on the upcoming stretch, so
> backporting shouldn't be an argument much longer, which raises the
> question if we need to carry a by now two years old copy[0] of apts
> https method into the stretch release.
[…]
> [0] no security bugs per-se, but even https gets bugfixes/features. The
> method is e.g. run as root while our http/https runs as _apt nowadays.


I have by now implemented and merged everything I "threated" to do into
src:apt to allow the included 'http' and 'https' methods to be called
'tor+http' and 'tor+https' respectively and do the right thing. If you
have apt (>= 1.3~rc1) and tor installed you can actually test this
virtually adding the methods by creating a config file in
/etc/apt/apt.conf.d/ containing:
Dir::Bin::Methods::tor+http "http";
Dir::Bin::Methods::tor+https "https";

It is possible then to use tor+http: and tor+https: in your sources and
apt will do the right thing™ talking via socks5h to the local tor
instance.


Beside bugs which have surely sneaked in the differences to a-t-t are:
> - tor+https options consistently fall back to tor -> https -> http
> - tor+http options consistently fall back to tor -> http
> - socks5h isn't forced. It is just the default (and the only one which
>   will work with (tor+)http at the moment; any with tor+https)
> - a tor-proxy having apt-transport-tor as username & no password
>   (default) will automatically pick a password based on the target
>   host to get you in a new circuit for each host.
> - the User-Agent isn't forced to an all-tor-users-have-the-same value.
>   Especially with tor+http being our normal http I think its better to
>   "hide" between other http users than saying straight that you are
>   a tor user (even if the IP gives it away that you are).
> - tor+https doesn't allow redirection to tor+http. We have this for
>   a while for https -> http already (-tor "broke" it). I think if a user
>   went as far as configuring a https source it should stay an https
>   source or fail.
- http/https can be disabled to avoid accidentally adding such sources
- http will not try to connect to .onion domains (RFC7687) and the error
  hints at using tor+http
- and as already mentioned: the methods run as _apt instead of root


Now that sounds like I would have the intention to shallow a-t-t as
a whole, but I actually think it should remain a separate package (but
perhaps under the APT team umbrella) because:

> So, assuming we can agree on that this is in general a good idea, this
> would leave apt-transport-tor relatively empty (expect three symlinks,
> a depends on apt and a recommends on -https & tor) but perhaps this
> frees resources for a-t-t to gain an option to turn all sources into
> tor+http(s) [with debconf] or even .onion addresses, additional
> documentation… instead of diverting energy into maintaining an -https
> fork.

I haven't got a whole lot of feedback on this, but so far no NACKs so by
recording this in a bugreport I hope to reach (again) out to people who
might have different ideas on how to solve what basically is a modified
embedded codecopy (of a Debian native tool none the less) which in terms
of stretch should be considered release-critical as that codecopy is
running with root rights and talking to the internet – I don't intend to
escalate it to RC just yet through as its summer/holiday season, but
just so we have a rough timeframe: I am going to in a months time if
noone is stopping me…


Best regards

David Kalnischkies


signature.asc
Description: PGP signature


Bug#805961: toilet: diff for NMU version 0.3-1.1

2016-08-22 Thread Jakub Wilk

Control: tags 805961 + pending

I've prepared an NMU for toilet (versioned as 0.3-1.1) and uploaded it 
to DELAYED/3. Please feel free to tell me if I should delay it longer.


--
Jakub Wilk
diffstat for toilet-0.3 toilet-0.3

 changelog |9 +
 rules |   55 ++-
 2 files changed, 39 insertions(+), 25 deletions(-)


No differences were encountered between the control files

diff -Nru toilet-0.3/debian/changelog toilet-0.3/debian/changelog
--- toilet-0.3/debian/changelog	2012-04-06 23:41:53.0 +0200
+++ toilet-0.3/debian/changelog	2016-08-22 21:05:36.0 +0200
@@ -1,3 +1,12 @@
+toilet (0.3-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix FTBFS when building only architeture-independent packages
+(closes: #805961). Thanks to Santiago Vila for the bug report and the
+patch.
+ 
+ -- Jakub Wilk   Mon, 22 Aug 2016 21:05:36 +0200
+
 toilet (0.3-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru toilet-0.3/debian/rules toilet-0.3/debian/rules
--- toilet-0.3/debian/rules	2012-04-06 23:45:04.0 +0200
+++ toilet-0.3/debian/rules	2016-08-22 21:02:44.0 +0200
@@ -51,34 +51,39 @@
 
 # Build architecture-independent files here.
 binary-indep: build install
-# We have nothing to do by default.
+	dh_installdocs -i -A README TODO NEWS
+	dh_installmenu -i
+	dh_installcron -i
+	dh_installinfo -i
+	dh_installmime -i
+	dh_installchangelogs -i ChangeLog
+	dh_link -i
+	dh_strip -i
+	dh_compress -i
+	dh_fixperms -i
+	dh_installdeb -i
+	dh_shlibdeps -i
+	dh_gencontrol -i
+	dh_md5sums -i
+	dh_builddeb -i
 
 # Build architecture-dependent files here.
 binary-arch: build install
-#	dh_testversion
-	dh_testdir
-	dh_testroot
-#	dh_installdebconf	
-	dh_installdocs -A README TODO NEWS
-#	dh_installexamples
-	dh_installmenu
-#	dh_installemacsen
-#	dh_installpam
-#	dh_installinit
-	dh_installcron
-#	dh_installmanpages
-	dh_installinfo
-	dh_installmime
-	dh_installchangelogs ChangeLog
-	dh_link
-	dh_strip
-	dh_compress
-	dh_fixperms
-	dh_installdeb
-	dh_shlibdeps
-	dh_gencontrol
-	dh_md5sums
-	dh_builddeb
+	dh_installdocs -a -A README TODO NEWS
+	dh_installmenu -a
+	dh_installcron -a
+	dh_installinfo -a
+	dh_installmime -a
+	dh_installchangelogs -a ChangeLog
+	dh_link -a
+	dh_strip -a
+	dh_compress -a
+	dh_fixperms -a
+	dh_installdeb -a
+	dh_shlibdeps -a
+	dh_gencontrol -a
+	dh_md5sums -a
+	dh_builddeb -a
 
 binary: binary-indep binary-arch
 .PHONY: build clean binary-indep binary-arch binary install configure


Bug#835127: tellico: Tellico always crashes at boot time

2016-08-22 Thread Luigi
Package: tellico
Version: 2.3.9+dfsg.1-1.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Tellico always crashes at boot time, immediately. The package is totally 
unusable.
When i lauched it in console i obtained this output:

tellico(4748)/kdeui (kdelibs): Attempt to use QAction "edit_undo" with 
KXMLGUIFactory! 
tellico(4748)/kdeui (kdelibs): Attempt to use QAction "edit_redo" with 
KXMLGUIFactory! 

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

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

Versions of packages tellico depends on:
ii  kde-runtime4:16.04.3-1+b1
ii  libc6  2.23-4
ii  libexempi3 2.3.0-2
ii  libkabc4   4:4.14.10-5
ii  libkcal4   4:4.14.10-5
ii  libkdecore54:4.14.22-2
ii  libkdeui5  4:4.14.22-2
ii  libkhtml5  4:4.14.22-2
ii  libkio54:4.14.22-2
ii  libknewstuff3-44:4.14.22-2
ii  libkparts4 4:4.14.22-2
ii  libkresources4 4:4.14.10-5
ii  libksane0  4:15.08.3-1
ii  libkxmlrpcclient4  4:4.14.10-5
ii  libnepomuk44:4.14.22-2
ii  libpoppler-qt4-4   0.44.0-3
ii  libqimageblitz41:0.0.6-4
ii  libqjson0  0.8.1-3
ii  libqt4-dbus4:4.8.7+dfsg-8
ii  libqt4-network 4:4.8.7+dfsg-8
ii  libqt4-xml 4:4.8.7+dfsg-8
ii  libqtcore4 4:4.8.7+dfsg-8
ii  libqtgui4  4:4.8.7+dfsg-8
ii  libsolid4  4:4.14.22-2
ii  libstdc++6 6.1.1-11
ii  libtag1v5  1.9.1-2.4
ii  libxml22.9.4+dfsg1-1+b1
ii  libxslt1.1 1.1.28-4
ii  libyaz44.2.30-4+b3
ii  tellico-data   2.3.9+dfsg.1-1.1
ii  tellico-scripts2.3.9+dfsg.1-1.1

Versions of packages tellico recommends:
ii  khelpcenter4  4:16.04.2-2
ii  tellico-doc   2.3.9+dfsg.1-1.1

tellico suggests no packages.

-- no debconf information



Bug#830344: Project Roadmap question - Call for votes

2016-08-22 Thread Didier 'OdyX' Raboud
Le dimanche, 21 août 2016, 09.41:40 h CEST Margarita Manterola a écrit :
> I'm a bit saddened by the lack of traction on this topic.
> We are holding other people's work back by our lack of involvement.
> 
> Therefore, I now call for a vote with the following options:
> 
> 1) The TC volunteers to be the Roadmap team
> 2) The TC volunteers to be part of the regular workflow of the
> Roadmap team, as an advisory body.
> 3) The TC shouldn't be part of the regular workflow of the Roadmap team.
> We will always be available for escalations, as usual.
> 4) Further Discussion.

I vote:

3 > 2 > 1 > 4

> Additionally, I'd like to ask each TC member to state if they would like
> to be part of the initial group for the Roadmap team if option 1 doesn't
> win.

I'd volunteer to be part of the initial Roadmap team.

-- 
Cheers,
OdyX



Bug#833115: Sponsoring hashid.

2016-08-22 Thread Hugo Lefeuvre
Built, signed & uploaded.

The package will now stay some days in the NEW queue, depending on how
the ftmasters are busy, if nothing goes wrong.

Cheers,
 Hugo

-- 
 Hugo Lefeuvre (hle)|www.owl.eu.com
4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E


signature.asc
Description: PGP signature


Bug#830213: tracker.debian.org: Accessibility regressions over old pts

2016-08-22 Thread Raphael Hertzog
On Mon, 11 Jul 2016, Sam Hartman wrote:
> First, that didn't make it clickable.  In general, I'd expect focusing
> on a button and pushing space to activate the button.  Enter sometimes
> activates a default action for a form, and definitely is the wrong
> keyboard approach to pushing a button outside a web browser.  However, I
> think most people will try enter when space fails.
[...]
> Luke Faraone (copied) said he'd be willing to help out with this.
> He has much more accessibility experience at the css and html layer than
> me.

Luke Faraone had a look. He committed a simple change to add href="#" to
the link behind the chevron used to toggle the display of more details.

Does it work better now?

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/



Bug#835114: airlift-slice: FTBFS in testing

2016-08-22 Thread Markus Koschany
Control: tags -1 confirmed pending

On 22.08.2016 18:17, Santiago Vila wrote:
> Package: airlift-slice
> Version: 0.10-1
> Severity: serious
> 
> Dear maintainer: This package FTBFS in testing.

Thank your for reporting this bug. This issue was caused by splitting
the findbugs package into several new binary packages. Not all
reverse-dependencies have been adjusted at the same time.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature


Bug#827684: cgoban: please make the build reproducible

2016-08-22 Thread Martin Godisch
On Sat, Aug 20, 2016 at 21:01:27 +0100, Chris Lamb wrote:

> There hasn't seem to be any update on this bug in 62 days, in which
> time the Reproducible Builds effort has come on a long way. :)
> 
> Would you consider applying this patch and uploading?

I'll do it this Saturday. -- Martin



Bug#815807: cups: printing on printers broadcast by old CUPS versions fails

2016-08-22 Thread Brian Potkin
Reassign 815807 cups-browsed
thanks



Thank you for this additional information, Patrick.


On Fri 19 Aug 2016 at 12:42:51 +0100, Patrick Welche wrote:

> I just reproduced this, admittedly between ubuntu rather than vanilla debian
> boxen, so it sounds like a real cups problem.

The work involved in testing with Ubuntu installs and an ancient version
of CUPS didn't exactly thrill me. So I used two servers, A and B.

A has cups 1.7.5-11+deb8u1 (Jessie) and B cups 2.1.2-2. The client is an
up-to-date unstable.

> "Old" cups is 1.4.3
> "New" cups is 2.1.3
> 
> extract of /etc/cups/printers.conf on old:
> 
> 
> DeviceURI socket://...
> ...
> Accepting Yes
> Shared Yes
> 
> on new, presumably having cups-browsed it:
> 
> 
> DeviceURI implicitclass:ufs2

You have duplicate queues being broadcast on the network; is this your
intention?  cups-browsed combines them into one Implicit Class queue.

> ...
> Accepting Yes
> Shared No
> 
> 
> So, apparently no longer shared... (is that right?)

Not shared by the client is what it means, I think.

>   Rejecting job because "ufs2" is not shared
> 
> quick round of lpadmin later, changed
> to Shared Yes, and thereafter

I'm not very sure I appreciate what you did here and whether it is
important. What command? Which machine was it executed on.

Servers A and B were set up with identical print queues. A largish file
was sent five times in rapid succession from the client. I expected the
printing to be distributed between A and B because of load balancing.
It wasn't; everything went to A.

I then disabled the queue on A, expecting B to be used. Then came

 No suitable destination host found by cups-browsed.

in 'lpstat -t'.

Maybe I am doing some wrong but it does look like a bug in cups-browsed.

You will have to explain what you think is happening at your end and
whether it fits our experiences.

Regards,

Brian.



Bug#834971: Acknowledgement (hash-slinger: 2.7 versions should depend on python-m2crypto (>= 0.24.0))

2016-08-22 Thread Willi Mann
Hi,

m2crypto has now been accepted to jessie-backports:

https://tracker.debian.org/news/792433

Bye
Willi



Bug#835126: doc package missing VectorDevices.htm

2016-08-22 Thread Anthony DeRobertis
Package: ghostscript-doc
Version: 9.19~dfsg-2
Severity: normal

file:///usr/share/doc/ghostscript/Devices.htm#High-level (at the bottom
of the section, under 4.5) links to VectorDevices.htm, but it's not in
the doc package.

I found it on the web at
http://www.ghostscript.com/doc/9.19/VectorDevices.htm 

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

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

ghostscript-doc depends on no packages.

ghostscript-doc recommends no packages.

Versions of packages ghostscript-doc suggests:
ii  ghostscript  9.19~dfsg-2

-- no debconf information



Bug#835125: jqueryui: Wrong licensing information: Licensed under MIT, *not* GPL-2

2016-08-22 Thread Gunnar Wolf
Source: jqueryui
Version: 1.10.1+dfsg
Severity: serious
Justification: Policy 2.3

The package's debian/copyright mentions all of the contents as being
licensed udner "GPL-2 or MIT", but they are exclusively licensed under
the MIT:

$ grep -ri 'gnu' . --exclude-dir=debian
Binary file ./development-bundle/demos/position/images/rocket.jpg matches
./development-bundle/demos/autocomplete/search.php:"Mute Swan"=>"Cygnus 
olor",
./development-bundle/demos/autocomplete/search.php:"Bewick`s Swan"=>"Cygnus 
bewickii",
./development-bundle/demos/autocomplete/search.php:"Whooper Swan"=>"Cygnus 
cygnus",
./development-bundle/demos/autocomplete/search.php:"Whistling 
Swan"=>"Cygnus columbianus",
$ grep -ri gpl . --exclude-dir=debian
./development-bundle/AUTHORS.txt:Garrison Locke 
$ grep -ri 'public license' . --exclude-dir=debian
$

Please fix this information. Thanks!

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

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



Bug#833950: [alsa-devel] locking looks odd

2016-08-22 Thread Elimar Riesebieter
* Samuel Thibault  [2016-08-22 19:52 +0200]:

> Elimar Riesebieter, on Mon 22 Aug 2016 19:33:26 +0200, wrote:
> >  If that dosn't come tto mind we either
> >  have to disable pthread (we can't forsee what breaks then)
> 
> Disabling pthread just drops the mutexes, without putting back the old
> locking code...

Let's wait 2 more weeks and hope of a solid solution from
alsa-devel. I try to discuss this with Jordi (MIA at the moment) and
Luke within this bug, so cc'ed.

Elimar
-- 
  Numeric stability is probably not all that
  important when you're guessing;-)


signature.asc
Description: PGP signature


Bug#834633: Acknowledgement (gpg: signing failed / agent_genkey failed: Operation cancelled)

2016-08-22 Thread Linus Lüssing
Actually, seems like the upgrade of the gnupg package from
1.4 to 2.1 is the issue (gnupg:armhf (1.4.20-6, 2.1.14-5) ).

Just reinstalled the old 1.4.20-6 version for the gnupg package
and things work nicely for me again.

Anyone having an idea why gnupg2 might fail for me?

Regards, Linus



Bug#833930: gitk: display shot, application usability gone

2016-08-22 Thread Oleg Pudeyev
Same issue here, and I agree that this makes gitk just about unusable.

The issue seems to affect testing but not stable distribution.

Things I tried with no effect:
- gitk 2.0 from git source repo
- compiling latest stable tcl/tk 8.5 and 8.6 from their websites

A fresh stable install works properly. apt-get upgrading and
dist-upgrading to testing breaks gitk. However, I then reverted
to the stable install and upgraded packages one or a few at a time and
was able to upgrade all of them to testing with gitk rendering
correctly at the end of the process. It seems that some dependency of
gitk/tk/tcl breaks gitk between stable and testing but this breakage is
dependent on the order of package upgrades.

When gitk breaks it does so without X server restart, suggesting a
client side issue.



Bug#835124: dolphin: search doesn't work properly when started inside a linked folder

2016-08-22 Thread Maria
Package: dolphin
Version: 4:16.04.2-2
Severity: normal

Dear Maintainer,

step 1) In my home I have a link into the folder foo. So '~/foo' links to
'~/bar/foo'.
step 2) In that folder there is a subfolder called 'Neuer Ordner'
step 3) I am going into the folder '~/foo'
step 4) I start the search with "Filename" and "From Here (foo)"; searchterm is
"Neuer"
step 5) I click on "Everywhere" and getting all files and folders containing
"Neuer"

step 6) I am changing into '~/bar/foo'
step 7) I open the search from there with "Filename" and "From Here (foo)";
searchterm is "Neuer"
step 8) I get the correct result 'Neuer Ordner' (clicking on "Everywhere" gives
the same correct result like above)

Thanks - Maria



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

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

Versions of packages dolphin depends on:
ii  libc6  2.23-4
ii  libdolphinvcs5 4:16.04.2-2
ii  libkf5baloo5   5.23.0-1
ii  libkf5baloowidgets516.04.0-1
ii  libkf5bookmarks5   5.23.0-1
ii  libkf5codecs5  5.23.0-1
ii  libkf5completion5  5.23.0-1
ii  libkf5configcore5  5.23.0-1
ii  libkf5configgui5   5.23.0-1
ii  libkf5configwidgets5   5.23.0-1
ii  libkf5coreaddons5  5.23.0-1
ii  libkf5crash5   5.23.0-1
ii  libkf5dbusaddons5  5.23.0-1
ii  libkf5filemetadata35.23.0-1
ii  libkf5i18n55.23.0-1
ii  libkf5iconthemes5  5.23.0-1
ii  libkf5itemviews5   5.23.0-1
ii  libkf5jobwidgets5  5.23.0-1
ii  libkf5kcmutils55.23.0-1
ii  libkf5kiocore5 5.23.0-1
ii  libkf5kiofilewidgets5  5.23.0-1
ii  libkf5kiowidgets5  5.23.0-1
ii  libkf5newstuff55.23.0-1
ii  libkf5notifications5   5.23.0-1
ii  libkf5parts5   5.23.0-1
ii  libkf5service-bin  5.23.0-1
ii  libkf5service5 5.23.0-1
ii  libkf5solid5   5.23.0-1
ii  libkf5textwidgets5 5.23.0-1
ii  libkf5widgetsaddons5   5.23.0-1
ii  libkf5windowsystem55.23.0-1
ii  libkf5xmlgui5  5.23.0-1
ii  libphonon4qt5-44:4.9.0-4
ii  libqt5core5a   5.6.1+dfsg-3+b1
ii  libqt5dbus55.6.1+dfsg-3+b1
ii  libqt5gui5 5.6.1+dfsg-3+b1
ii  libqt5widgets5 5.6.1+dfsg-3+b1
ii  libqt5xml5 5.6.1+dfsg-3+b1
ii  libstdc++6 6.1.1-11
ii  phonon4qt5 4:4.9.0-4

Versions of packages dolphin recommends:
ii  kio-extras  4:16.04.2-1
ii  ruby1:2.3.0+4

Versions of packages dolphin suggests:
ii  dolphin-plugins  4:16.04.0-1

-- no debconf information



Bug#833817: kido: FTBFS on non-x86 architectures due to hard-wired compiler flags

2016-08-22 Thread Julien Cristau
Control: severity -1 serious

On Tue, Aug  9, 2016 at 00:14:48 +0200, John Paul Adrian Glaubitz wrote:

> Source: kido
> Version: 0.1.0+dfsg-1
> Severity: important
> 
> Hello!
> 
> Your package fails to build from source on all non-x86 architectures because 
> the
> build system hard-wires the compiler flags to use x86-specific flags like 
> "-msse2":
> 
-msse2 is also a big no-no on i386, and a no-op on amd64...

Cheers,
Julien



Bug#833950: [alsa-devel] locking looks odd

2016-08-22 Thread Samuel Thibault
Elimar Riesebieter, on Mon 22 Aug 2016 19:33:26 +0200, wrote:
>  If that dosn't come tto mind we either
>  have to disable pthread (we can't forsee what breaks then)

Disabling pthread just drops the mutexes, without putting back the old
locking code...

Samuel



Bug#835123: xserver-xorg-video-modesetting: Keyboard events become extremely unresponsive after certain X events

2016-08-22 Thread Wirawan Purwanto
Package: xserver-xorg-video-modesetting
Version: 0.9.0-2
Severity: important

I have a laptop (thinkpad t450s) running mostly Debian Jessie (stable
system). Now with debian backport kernel 4.6 (package:
linux-image-4.6.0-0.bpo.1-amd64 version: 4.6.4-1~bpo8+1).
CPU is Intel Broadwell i5-5200U and HD5500 (Broadwell-U) integrated graphics.
Kernel loads i915.ko as the kernel graphics driver.
The X desktop uses stock xfce from Debian.

For the past few days I have been experimenting to use "modesetting" video
driver for my graphics card instead of the (older) Intel DDX driver
(xserver-xorg-video-intel).
The relevant segment of my xorg.conf is simply:

Section "Device"
   Identifier  "Intel Graphics"
   Driver  "modesetting"
EndSection

In general it has been doing well, except that I faced several occasion of
bugs wherein the keyboard/mouse interaction becomes extremely laggish
after certain things happened.

I noticed two instances that can trigger this sluggish behavior:
perhaps there are more with the same underlying issue:

1) using osd_cat (package: xosd-bin). example command was like this:

   osd_cat -w -p top -c green -s 2 -a 0 -d 1 -o 32 \
   -A right -b percentage -P 19 \
   -f "-*-helvetica-medium-r-*-*-*-200-*-*-*-*-*-*" \
   -l 1 -T "Volume: 19"

This was derived from a script in here:

https://ubuntuforums.org/showthread.php?t=1313831=2=8247224#post8247224

A much-reduced dummy script that can successfully reproduce this
bug on my system is this:

#!/bin/bash
CHANNEL=Master
amixer set $CHANNEL 4096+
osd_cat -w -p top -c green -s 2 -a 0 -d 1 -o 32 \
   -A right -b percentage -P 19 \
   -f "-*-helvetica-medium-r-*-*-*-200-*-*-*-*-*-*" \
   -l 1 -T "Volume: 19"

This worked ok when I used "intel" driver, until I started using
"modesetting" driver.
After I run that script above, whatever I typed using my
keyboard will not show up until 2-3 seconds later (or more, could be 5
seconds, probably).
If I type a lot of letterrr, then after those 2-3 seconds lag then all the
typed letters would show up.
Then the whole desktop became useless until I restarted the "lightdm"
service (i.e. restarted the X session).

I also found out that the lagginess applies to the X11 display after
the osd_cat call above.
I invoked `screen` from a terminal session on this laptop, then
ssh-ing from outside and reconnect via `screen -x`.
The screen session that was from outside the laptop has no laggy
behavior whatsoever, but inside the laptop (X11 desktop), the same
screen session is very laggy.

What frustrating was that no error was shown on /var/log/syslog, or
/var/log/Xorg.0.log, dmesg, or ~/.xsession-errors that relates to this
change of behavior of X input.

At the virtual console (Ctrl+Alt+F1 for example), this lagging behavior
was not observed at all.
Strangely, if at this moment I fired up another X desktop (i.e. log in via
second virtual console as another user then invoke startx), then this
second desktop has no laggy issue whatsoever.


2) I have another way to trigger this problem, which was accidentally
found by trying to display a corrupted PDF file on xpdf.  I can attach
this file if someone wants to try it.

I downgraded the kernel to package linux-image-4.3.0-0.bpo.1-amd64
version 4.3.5-1~bpo8+1 , then with modesetting DDS there was no
laggy problem like the above.
I have tested two version of the 4.6 kernel line, the laggy behavior
is observed in both.

So the bug is either in the modesetting driver (and wasn't exposed
until the newer kernel), or a newer kernel's i915 driver has that bug
in it.
I am posting this for further investigation.


Thanks,
Wirawan

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Jun 27  2015 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 2401376 Feb 10  2015 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation
Broadwell-U Integrated Graphics [8086:1616] (rev 09)

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
-
total 8
-rw-r--r-- 1 root root 315 Aug 19  2015 20-intel-use-uxa.conf
-rw-r--r-- 1 root root 321 Jul 16 09:48 20-use-generic-modesetting.conf0

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.6.0-0.bpo.1-amd64 (debian-ker...@lists.debian.org)
(gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.6.1-1~bpo8+1
(2016-06-14)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 27558 Jul 17 22:53 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 19194 Jul 19 11:58 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[ 62015.018]
X.Org X Server 1.16.4
Release Date: 2014-12-20
[ 

Bug#834968: apt-cacher: Fails to run due to curl errors

2016-08-22 Thread Helge Kreutzmann
Hello Mark,
On Mon, Aug 22, 2016 at 11:20:06AM +0100, Mark Hindley wrote:
> Thanks. I am wondering where your HTTPS upstream is configured? What do you 
> have in /etc/apt/sources.list?

root@samd:~# grep -v "^#" /etc/apt/sources.list
deb http://172.16.18.51:/debian testing main

Where 172.16.18.51 is the local IP of this machine.

> On Sun, Aug 21, 2016 at 05:03:29PM +0200, Helge Kreutzmann wrote:
> > > Are you trying to use HTTPS for upstream? If so, you will need to set 
> > > curl_ssl_insecure or use the libcurl option to configure CA to verify the 
> > > upstream connection.
> > 
> > Is there some documentation to do this libcurl configuration? I'd
> > rather configure the CA properly, but could not find any docs for
> > this.
> 
> Temporarily try the curl_ssl_insecure option first. If that helps we know we 
> are on the right track. 

Ok, I added:
libcurl = insecure
or
libcurl = curl_ssl_insecure

to /etc/apt-cacher/apt-cacher.conf but, unfortunately this does not
change anything.

> The libcurl option in mentioned in man apt-cacher(8). It should accept 
> anything from curl_easy_setopt(3), which requires the libcurl dev package

I installed libcurl4-doc but the curl_easy_setopt(3) does not specify
anything with INSECURE or insecure, nor did I find anything amongst
the many options under the heading of 
SSL and SECURITY OPTIONS

Could you check?

Thanks!

Greetings

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


signature.asc
Description: Digital signature


Bug#835122: php-doctrine-cache: FTBFS too much often (failing tests)

2016-08-22 Thread Santiago Vila
Package: src:php-doctrine-cache
Version: 1.6.0-2
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with phpcomposer
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
# Provide autoload for the binary package
phpab --output  lib/Doctrine/Common/Cache/autoload.php \
lib/Doctrine/Common/Cache
phpab %development% - Copyright (C) 2009 - 2016 by Arne Blankerts

Scanning directory lib/Doctrine/Common/Cache

Autoload file lib/Doctrine/Common/Cache/autoload.php generated.

# Provide autoload for tests
mkdir --parents vendor
phpab \
--output vendor/autoload.php \
lib/Doctrine/Common/Cache \
tests/Doctrine/Tests \
/usr/share/php/php-nrk-predis
phpab %development% - Copyright (C) 2009 - 2016 by Arne Blankerts

Scanning directory lib/Doctrine/Common/Cache
Scanning directory tests/Doctrine/Tests
Scanning directory /usr/share/php/php-nrk-predis

Autoload file vendor/autoload.php generated.

make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
php -d apc.enable_cli=on /usr/bin/phpunit
PHPUnit 5.4.6 by Sebastian Bergmann and contributors.

S   61 / 1309 (  4%)
SSS..  122 / 1309 (  9%)
.  183 / 1309 ( 13%)
S.S..S...  244 / 1309 ( 18%)
..S.S  305 / 1309 ( 23%)
...SS  366 / 1309 ( 27%)
SWWE.E...  427 / 1309 ( 32%)
..S.S...S  488 / 1309 ( 37%)
S  549 / 1309 ( 41%)
S  610 / 1309 ( 46%)
S  671 / 1309 ( 51%)
SSSE.E...  732 / 1309 ( 55%)
S.S...SSS  793 / 1309 ( 60%)
S  854 / 1309 ( 65%)
S  915 / 1309 ( 69%)
S  976 / 1309 ( 74%)
S 1037 / 1309 ( 79%)
S..SS 1098 / 1309 ( 83%)
S 1159 / 1309 ( 88%)
S 1220 / 1309 ( 93%)
S 1281 / 1309 ( 97%)
  1309 / 1309 (100%)

Time: 11.35 seconds, Memory: 12.00MB

There were 4 errors:

1) 
Doctrine\Tests\Common\Cache\FilesystemCacheTest::testWindowsPathLengthLimitIsCorrectlyHandled
 with data set #0 (257, false)
UnexpectedValueException: 
RecursiveDirectoryIterator::__construct(/tmp/do-not-try-to-enter-into-this-directory):
 failed to open dir: Permission denied

/<>/tests/Doctrine/Tests/Common/Cache/BaseFileCacheTest.php:27

2) 
Doctrine\Tests\Common\Cache\FilesystemCacheTest::testWindowsPathLengthLimitIsCorrectlyHandled
 with data set #2 (259, true)
UnexpectedValueException: 
RecursiveDirectoryIterator::__construct(/tmp/do-not-try-to-enter-into-this-directory):
 failed to open dir: Permission denied

/<>/tests/Doctrine/Tests/Common/Cache/BaseFileCacheTest.php:27

3) 
Doctrine\Tests\Common\Cache\PhpFileCacheTest::testWindowsPathLengthLimitIsCorrectlyHandled
 with data set #0 (257, false)
UnexpectedValueException: 
RecursiveDirectoryIterator::__construct(/tmp/do-not-try-to-enter-into-this-directory):
 failed to open dir: Permission denied

/<>/tests/Doctrine/Tests/Common/Cache/BaseFileCacheTest.php:27

4) 
Doctrine\Tests\Common\Cache\PhpFileCacheTest::testWindowsPathLengthLimitIsCorrectlyHandled
 with data set #2 (259, true)
UnexpectedValueException: 
RecursiveDirectoryIterator::__construct(/tmp/do-not-try-to-enter-into-this-directory):
 failed to open dir: Permission denied

/<>/tests/Doctrine/Tests/Common/Cache/BaseFileCacheTest.php:27

--

There were 6 warnings:

1) 
Doctrine\Tests\Common\Cache\FileCacheTest::testFilenameShouldCreateThePathWithOneSubDirectory
PHPUnit_Framework_TestCase::getMock() is deprecated, use 
PHPUnit_Framework_TestCase::createMock() or 

Bug#833950: [alsa-devel] locking looks odd

2016-08-22 Thread Elimar Riesebieter
* Samuel Thibault  [2016-08-20 14:12 +0200]:

> Jaroslav Kysela, on Wed 17 Aug 2016 19:46:42 +0200, wrote:
> > Dne 16.8.2016 v 23:03 Samuel Thibault napsal(a):
> > > - snd_pcm_new seems to initialize pcm->thread_safe to 0 by default, this
> > >   does not seem safe. The attached patch initializes it to 1, which
> > >   fixes the bug in our tests.
> > > 
> > > - snd_pcm_hw_open_fd forces it to 1, thus ignoring what snd_pcm_new set.
> > 
> > The thread_safe has this meaning:
> > 
> > 0  - the pcm plugin is not thread safe
> > 1  - the pcm plugin is thread safe (actually only the hw plugin)
> > -1 - disable thread safety
> 
> So now with rethinking all of this, I'm starting to understand: from
> reading the variable name, I would have thought "thread_safe=1" means
> "I want thread safety thanks to a mutex", while apparently it means
> "the plugin is already thread-safe, there is no need for a mutex"...
> Really, all of this should be documented clearly along the source code,
> otherwise people will get it wrong.
> 
> I'd just like to check something: do we agree that libasound must be
> thread-safe by default (otherwise it breaks the application assumption
> that it's thread-safe)?  If so, then there are thread-safety bugs: the
> mentioned Debian report is far from alone, the upgrade to the newer
> libasound has severely broken quite a few applications, I'm at the point
> of advising the Debian maintainer to just revert to the previous version
> for Stretch, otherwize we'll be shipping just very-buggy software.

 suppose that we should wait for a response of the maintainer
 Takashi Sakamoto mentioned. If that dosn't come tto mind we either
 have to disable pthread (we can't forsee what breaks then) or really
 downgrade to 1.1.1.

Elimar
-- 
  >what IMHO then?
  IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
  --posting from alex in debian-user--


signature.asc
Description: PGP signature


Bug#816313: dash: executes binary data as a shell script in case of ENOEXEC (Exec format error)

2016-08-22 Thread Jakub Wilk

* Vincent Lefevre , 2016-02-29, 20:17:

$ /bin/dash -c tadd.exe
./tadd.exe: 1: ./tadd.exe: MZ��¸@€º´: not found
./tadd.exe: 2: ./tadd.exe: : not found
./tadd.exe: 1: ./tadd.exe: @.bss €: not found
./tadd.exe: 1: ./tadd.exe: .textd*,: not found
./tadd.exe: 3: ./tadd.exe: JPL2@�.idata: not found
./tadd.exe: 3: ./tadd.exe: –u
: not found
./tadd.exe: 4: ./tadd.exe: ~@0�.CRT4�ˆ@0�.tls: not found
./tadd.exe: 5: ./tadd.exe: @B/81P: not found
./tadd.exe: 13: ./tadd.exe: Syntax error: Missing '}'


This is standards-compliant behavior. SUSv3[0] reads:
If the execve() function fails due to an error equivalent to the 
[ENOEXEC] error defined in the System Interfaces volume of IEEE Std 
1003.1-2001, the shell shall execute a command equivalent to having a 
shell invoked with the pathname resulting from the search as its first 
operand, with any remaining arguments passed to the new shell, except 
that the value of "$0" in the new shell may be set to the command name. 
If the executable file is not a text file, the shell may bypass this 
command execution.


"may" means optional behavior. I see no reason for this bug to remain 
release-critical.


[0] 
http://pubs.opengroup.org/onlinepubs/009604499/utilities/xcu_chap02.html#tag_02_09_01_01

--
Jakub Wilk



Bug#834155: rails: CVE-2016-6316: Possible XSS Vulnerability in Action View

2016-08-22 Thread Moritz Muehlenhoff
On Mon, Aug 22, 2016 at 02:09:32PM -0300, Antonio Terceiro wrote:
> Hi,
> 
> On Fri, Aug 12, 2016 at 05:18:55PM +0200, Salvatore Bonaccorso wrote:
> > Source: rails
> > Version: 2:4.1.8-1
> > Severity: important
> > Tags: security upstream patch
> > 
> > Hi,
> > 
> > the following vulnerability was published for rails.
> > 
> > CVE-2016-6316[0]:
> > Possible XSS Vulnerability in Action View
> > 
> > If you fix the vulnerability please also make sure to include the
> > CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> > 
> > For further information see:
> > 
> > [0] https://security-tracker.debian.org/tracker/CVE-2016-6316
> > [1] http://seclists.org/oss-sec/2016/q3/260
> > [2] 
> > https://groups.google.com/forum/#!msg/rubyonrails-security/I-VWr034ouk/gGu2FrCwDAAJ
> > 
> > Please adjust the affected versions in the BTS as needed.
> 
> AFAICT you got the versions right already. This issue affects stable,
> while the other does not.
> 
> For stable, I have prepared a security update, have successfully tested
> it on a sample application based on the upstream advisory description.
> Attached you will find both the debdiff (rails.diff) and the actual
> backported patch (CVE-2016-6316.patch); the later is easier to read than
> the diff-in-diff part of the former.

Thanks, please upload to security-master

Cheers,
Moritz



Bug#835121: castxml: FTBFS on armel will cause removal of reverse dependencies

2016-08-22 Thread Markus Koschany
Package: castxml
Version: 0.1+git20160706-1
Severity: serious


Hi,

castxml FTBFS on armel but build successfully in the past. Unless the
package in unstable migrates to testing, this will cause the removal of
castxml's reverse-dependencies (e.g spring).

It appears a missing test case is responsible for the FTBFS on armel.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature


Bug#835120: lintian: false positive: virtual-package-depends-without-real-package-depends in experimental

2016-08-22 Thread Carsten Leonhardt
Package: lintian
Version: 2.5.46
Severity: normal

Dear Maintainer,

lintian reports the following for bacula 7.4.3+dfsg-3, which is
currently in experimental:

bacula-server
W virtual-package-depends-without-real-package-depends
depends: bacula-director

Probably the confusion comes from the fact that it's a virtual package
in unstable, but in experimental it's a real package.

Carsten

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

Kernel: kFreeBSD 10.3-0-amd64
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages lintian depends on:
ii  binutils  2.27-6
ii  bzip2 1.0.6-8
ii  diffstat  1.61-1
ii  file  1:5.28-4
ii  gettext   0.19.8.1-1
ii  hardening-includes2.8+nmu2
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.29+b5
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2
ii  libdata-alias-perl1.20-1+b1
ii  libdpkg-perl  1.18.10
ii  libemail-valid-perl   1.200-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.94-1
ii  liblist-moreutils-perl0.416-1
ii  libparse-debianchangelog-perl 1.2.0-10
ii  libperl5.22 [libdigest-sha-perl]  5.22.2-3
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.71-1
ii  libyaml-libyaml-perl  0.41-6+b1
ii  man-db2.7.5-1
ii  patchutils0.3.4-1
ii  perl  5.22.2-3
ii  t1utils   1.39-2
ii  xz-utils  5.1.1alpha+20120614-2.1

Versions of packages lintian recommends:
ii  dpkg 1.18.10
ii  libperlio-gzip-perl  0.19-1+b1
ii  perl 5.22.2-3
ii  perl-modules-5.22 [libautodie-perl]  5.22.2-3

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.18.10
ii  libhtml-parser-perl3.72-2
ii  libtext-template-perl  1.46-1

-- no debconf information



Bug#834155: rails: CVE-2016-6316: Possible XSS Vulnerability in Action View

2016-08-22 Thread Antonio Terceiro
Hi,

On Fri, Aug 12, 2016 at 05:18:55PM +0200, Salvatore Bonaccorso wrote:
> Source: rails
> Version: 2:4.1.8-1
> Severity: important
> Tags: security upstream patch
> 
> Hi,
> 
> the following vulnerability was published for rails.
> 
> CVE-2016-6316[0]:
> Possible XSS Vulnerability in Action View
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> 
> For further information see:
> 
> [0] https://security-tracker.debian.org/tracker/CVE-2016-6316
> [1] http://seclists.org/oss-sec/2016/q3/260
> [2] 
> https://groups.google.com/forum/#!msg/rubyonrails-security/I-VWr034ouk/gGu2FrCwDAAJ
> 
> Please adjust the affected versions in the BTS as needed.

AFAICT you got the versions right already. This issue affects stable,
while the other does not.

For stable, I have prepared a security update, have successfully tested
it on a sample application based on the upstream advisory description.
Attached you will find both the debdiff (rails.diff) and the actual
backported patch (CVE-2016-6316.patch); the later is easier to read than
the diff-in-diff part of the former.

For unstable, both issues will be fixed by 2:4.2.7.1-1 (being uploaded
RSN)
diff --git a/debian/changelog b/debian/changelog
index aa08ba6..2e09ba0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+rails (2:4.1.8-1+deb8u3) jessie-security; urgency=high
+
+  * Security update
+  * CVE-2016-6316: Possible XSS Vulnerability in Action View
+(Closes: Bug#834155)
+
+ -- Antonio Terceiro   Mon, 22 Aug 2016 13:35:11 -0300
+
 rails (2:4.1.8-1+deb8u2) jessie-security; urgency=high
 
   * Security updates:
diff --git a/debian/patches/CVE-2016-6316.patch b/debian/patches/CVE-2016-6316.patch
new file mode 100644
index 000..4381974
--- /dev/null
+++ b/debian/patches/CVE-2016-6316.patch
@@ -0,0 +1,45 @@
+From: Andrew Carpenter 
+Date: Thu, 28 Jul 2016 16:12:21 -0700
+Subject: ensure tag/content_tag escapes " in attribute vals
+
+Many helpers mark content as HTML-safe without escaping double quotes -- including `sanitize`. Regardless of whether or not the attribute values are HTML-escaped, we want to be sure they don't include double quotes, as that can cause XSS issues. For example: `content_tag(:div, "foo", title: sanitize('" onmouseover="alert(1);//'))`
+
+CVE-2016-6316
+
+Author: Andrew Carpenter 
+Backported-by: Antonio Terceiro 
+---
+ actionview/lib/action_view/helpers/tag_helper.rb |  2 +-
+ actionview/test/template/tag_helper_test.rb  | 18 ++
+ 2 files changed, 19 insertions(+), 1 deletion(-)
+
+--- a/actionview/lib/action_view/helpers/tag_helper.rb
 b/actionview/lib/action_view/helpers/tag_helper.rb
+@@ -169,7 +169,7 @@ module ActionView
+ def tag_option(key, value, escape)
+   value = value.join(" ") if value.is_a?(Array)
+   value = ERB::Util.h(value) if escape
+-  %(#{key}="#{value}")
++  %(#{key}="#{value.gsub(/"/, ''.freeze)}")
+ end
+ end
+   end
+--- a/actionview/test/template/tag_helper_test.rb
 b/actionview/test/template/tag_helper_test.rb
+@@ -116,6 +116,16 @@ class TagHelperTest < ActionView::TestCa
+ end
+   end
+ 
++  def test_tag_does_not_honor_html_safe_double_quotes_as_attributes
++assert_dom_equal 'content',
++  content_tag('p', "content", title: '"'.html_safe)
++  end
++
++  def test_data_tag_does_not_honor_html_safe_double_quotes_as_attributes
++assert_dom_equal 'content',
++  content_tag('p', "content", data: { title: '"'.html_safe })
++  end
++
+   def test_skip_invalid_escaped_attributes
+ ['&1;', '

Bug#813079: chromium.desktop: StartupWMClass does not match actual WM_CLASS

2016-08-22 Thread Thomas Liske
found 813079 52.0.2743.116-2
affects 813079 docky
thanks


Hi,

it seems that the StartWMClass option has been already changed:

  $ dpkg-query -W chromium
  chromium52.0.2743.116-2

  $ grep WMClass /usr/share/applications/chromium.desktop
  StartupWMClass=chromium-browser

Sadly, the WM_CLASS of chromium's window does not match again:

  $ xprop | grep WM_CLASS
  WM_CLASS(STRING) = "chromium", "chromium"

Please change StartupWMClass to "chromium". The dock app "docky" shows
a wrong icon and name for chromium as a result of the mismatching
class name since it searches for the StartupWMClass option of
.desktop files[1] to find icons and names.

[1]
http://wiki.go-docky.com/index.php?title=How_to_Customize_Window_Matching


TIA & HTH,
Thomas


On Fri, Jan 29, 2016 at 02:25:56PM +0100, Alessio wrote:
> Package: chromium
> Version: 47.0.2526.80-1~deb8u1
> Severity: minor
> 
> Dear Maintainer,
> 
> launching Chromium from gnome-shell favourites crates a new icon on the bar,
> instead of marking the favourite icon as an open application.
> 
> This is due to a mismatch between the StartupWMClass in chromium.desktop
> ("Chromium") and the actual WM_CLASS of Chromium window ("chromium-browser").
> 
> Setting "StartupWMClass=chromium-browser" in chromium.desktop solves the
> problem.
> 
> Thanks for your work
> --
> Alessio Gaeta
> 
> 
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (850, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.3-3.dmz.6-liquorix-amd64 (SMP w/4 CPU cores; PREEMPT)
> Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages chromium depends on:
> ii  libasound2   1.0.29-1
> ii  libatk1.0-0  2.18.0-1
> ii  libc62.21-6
> ii  libcairo21.14.6-1
> ii  libcups2 2.1.2-2+b1
> ii  libdbus-1-3  1.10.6-1
> ii  libexpat12.1.0-7
> ii  libfontconfig1   2.11.0-6.3
> ii  libfreetype6 2.6.1-0.1
> ii  libgcc1  1:5.3.1-7
> ii  libgdk-pixbuf2.0-0   2.32.3-1
> ii  libglib2.0-0 2.46.2-3
> ii  libgnome-keyring03.12.0-1+b1
> ii  libgtk2.0-0  2.24.29-1
> ii  libjpeg62-turbo  1:1.4.1-2
> ii  libnspr4 2:4.11-1
> ii  libnspr4-0d  2:4.11-1
> ii  libnss3  2:3.21-1
> ii  libnss3-1d   2:3.21-1
> ii  libpango-1.0-0   1.38.1-1
> ii  libpangocairo-1.0-0  1.38.1-1
> ii  libpci3  1:3.3.1-1.1
> ii  libspeechd2  0.8-7
> ii  libsrtp0 1.4.5~20130609~dfsg-1.1
> ii  libstdc++6   5.3.1-7
> ii  libx11-6 2:1.6.3-1
> ii  libxcomposite1   1:0.4.4-1
> ii  libxcursor1  1:1.1.14-1+b1
> ii  libxdamage1  1:1.1.4-2+b1
> ii  libxext6 2:1.3.3-1
> ii  libxfixes3   1:5.0.1-2+b2
> ii  libxi6   2:1.7.5-1
> ii  libxml2  2.9.3+dfsg1-1
> ii  libxrandr2   2:1.5.0-1
> ii  libxrender1  1:0.9.9-2
> ii  libxslt1.1   1.1.28-2.1
> ii  libxss1  1:1.2.2-1
> ii  libxtst6 2:1.2.2-1+b1
> ii  x11-utils7.7+3
> ii  xdg-utils1.1.1-1
> 
> chromium recommends no packages.
> 
> Versions of packages chromium suggests:
> pn  chromium-inspector  
> ii  chromium-l10n   47.0.2526.80-1~deb8u1
> 
> -- no debconf information
> 
--

::  WWW:https://fiasko-nw.net/~thomas/  ::
   :::  Jabber:   xmpp:tho...@jabber.fiasko-nw.net  :::
::  flickr: https://www.flickr.com/photos/laugufe/  ::



Bug#835119: tor client does not immediately open new circuits after standby

2016-08-22 Thread Viktor Jägersküpper
Package: tor
Version: 0.2.8.6-3
Severity: normal

Dear Maintainer,

I use tor only as a client to connect icedove to the tor network with
the extension Torbirdy (on port 9050). With the tor version 0.2.8.6 I
can't immediately connect to any mail server or news feed after the pc
woke up from standby ("long" time in standby) and I started icedove. I
have to wait for several minutes in order to connect successfully, but
the timespan seems to be random. This does not occur after a (re)boot.
The first version I remember to have this issue is 0.2.8.6-2, I did an
upgrade from 0.2.7.6-1 to 0.2.8.6-2, so I skipped the alpha and rc
versions and the first upload to unstable. I am very sure that the issue
didn't occur in version 0.2.7.6-1 which I used for several months. I can
exclude network connectivity problems because e.g. I can immediately
start the Tor Browser after standby.

Today I purged tor, installed version 0.2.7.6-1, copied the old "state"
file to /var/lib/tor, and set the pc in standby mode for a couple of
minutes. After waking up from standby I immediately tried to connect to
a mail server which worked. Then I upgraded step by step to every
version of tor 0.2.8 which I could find on snapshot.debian.org and tried
to connect to a mail server immediately after waking up from standby.
Unfortunately I could not reproduce the bug then. Finally with version
0.2.8.6-3 the bug occured again, but only after a "long" standby time
(almost 90 minutes).

Attached are two log files from the weekend and the complete log from
today after the installation of version 0.2.7.6-1.

As you can see, the bug is not easily reproducible, and the logs don't
show any particular reason for why tor does not open new circuits
immediately. Please tell me what I can do to give you more information
about the bug.

Regards
Viktor



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

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

Versions of packages tor depends on:
ii  adduser  3.115
ii  init-system-helpers  1.42
ii  libc62.23-4
ii  libevent-2.0-5   2.0.21-stable-2+b1
ii  libseccomp2  2.3.1-2
ii  libssl1.0.2  1.0.2h-1
ii  libsystemd0  231-4
ii  lsb-base 9.20160629
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages tor recommends:
ii  logrotate3.8.7-2
pn  tor-geoipdb  
pn  torsocks 

Versions of packages tor suggests:
pn  apparmor-utils   
pn  mixmaster
pn  obfs4proxy   
pn  obfsproxy
pn  socat
ii  tor-arm  1.4.5.0-1.1
pn  torbrowser-launcher  

-- no debconf information
Aug 20 11:24:43.000 [notice] Tor 0.2.8.6 (git-89d2e261a925c6a6) opening new log 
file.
Aug 20 11:26:50.000 [notice] Tor has successfully opened a circuit. Looks like 
client functionality is working.
Aug 20 11:26:50.000 [notice] Tor has successfully opened a circuit. Looks like 
client functionality is working.
Aug 20 13:52:10.000 [notice] Your system clock just jumped 3486 seconds 
forward; assuming established circuits no longer work.
Aug 20 13:58:21.000 [notice] No circuits are opened. Relaxed timeout for 
circuit 22 (a General-purpose client 1-hop circuit in state doing handshakes 
with channel state open) to 337950ms. However, it appears the circuit has timed 
out anyway. 12 guards are live.
Aug 20 14:17:42.000 [notice] Tor has successfully opened a circuit. Looks like 
client functionality is working.
Aug 20 14:17:42.000 [notice] Tor has successfully opened a circuit. Looks like 
client functionality is working.
Aug 20 17:26:02.000 [notice] Your system clock just jumped 10956 seconds 
forward; assuming established circuits no longer work.
Aug 20 17:31:55.000 [notice] No circuits are opened. Relaxed timeout for 
circuit 29 (a General-purpose client 1-hop circuit in state doing handshakes 
with channel state open) to 337950ms. However, it appears the circuit has timed 
out anyway. 13 guards are live.
Aug 20 17:32:16.000 [notice] Tor has successfully opened a circuit. Looks like 
client functionality is working.
Aug 20 17:32:16.000 [notice] Tor has successfully opened a circuit. Looks like 
client functionality is working.
Aug 20 20:03:52.000 [notice] Your system clock just jumped 3806 seconds 
forward; assuming established circuits no longer work.
Aug 20 20:08:13.000 [notice] Tried for 120 seconds to get a connection to 
[scrubbed]:993. Giving up. (waiting for circuit)
Aug 20 20:10:18.000 [notice] Tried for 120 seconds to get a connection to 
[scrubbed]:993. Giving up. (waiting for circuit)
Aug 20 20:11:52.000 [notice] No circuits are opened. Relaxed timeout for 
circuit 40 (a General-purpose client 3-hop circuit in state doing handshakes 
with channel state 

Bug#724013: Gui is not shown

2016-08-22 Thread Harald Dunkel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Using sid and clementine 1.3.1+dfsg-1 it seems to work. I had to
remove my .config/Clementine directory, though.

Problem solved. Thanx very much

Harri

-BEGIN PGP SIGNATURE-

iQEcBAEBCAAGBQJXuysEAAoJEAqeKp5m04HLVzAH/jBMzNJooDb+SbBeSW41jcqP
UxG61DOkCJH0Gt6SEcs732vjH0NyDZIWc53VnPJf9p8giOtbbyyNH7eEvrBNoB+v
FjODib70EeGOK40ilW8iNXn0jMhe28TDDt1G0/d31Up0rjT1d5VMX9AsvymhSEgF
ffMIl38yvzKkrrXY1oCuT6FIHdAdW9SIqQ2UavvDW02LcfvpqV1IivPimdD6AGFf
nC9nYi/9fogevU9hT9yevr7/G10AWS+5q5rR+QgHkQDFR/uBHk6Hu8mPMI8fyMIy
O1WF/evHZ+PVFfqrC2rKj0fRERLd22skhZSr63RUeWOo//yPUj1xPfv3w/fo4vw=
=v3QO
-END PGP SIGNATURE-



Bug#779135: sgabios: please make the build reproducible

2016-08-22 Thread Chris Lamb
Hi Daniel,

> could you do the actual upload for me?

Sure, however, I think there were some limitations in my patch from
back then. Please could you change it to:

  -BUILD_HOST = debian
  +BUILD_HOST = generic
  -BUILD_USER = debian
  +BUILD_USER = generic
   BUILD_DATE = $(shell dpkg-parsechangelog --show-field=Date)
  -BUILD_SHORT_DATE = $(shell date --date="$(BUILD_DATE)" +%D)
  +BUILD_SHORT_DATE = $(shell date --utc --date="$(BUILD_DATE)" +%D)
 
It shouldn't "really" say Debian in our derivatives (or it would
just be a bit confusing), and we need to print the date in the UTC
timezone.

Very happy to upload once this is done.


Regards,

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



Bug#834826: uscan warning

2016-08-22 Thread juke
[juke@jhebert:~/tmpsqlparse/sqlparse-0.1.13] 1 % uscan 
uscan warning: In watchfile debian/watch, reading webpage
  https://pypi.python.org/packages/source/s/sqlparse/ failed: 404 Not Found



signature.asc
Description: Digital signature


Bug#835000: icedove: Running external application: Failed to execute child process "firefox-esr" (Permission denied)

2016-08-22 Thread Simon Deziel
Hi Emmanuel,

On Sun, 21 Aug 2016 14:45:56 +0200 Emmanuel Fleury
 wrote:
> Package: icedove
> Version: 1:45.2.0-4
> Severity: normal
> 
> Dear Maintainer,
> 
> When trying to access to a web link from an e-mail, I get the following 
> error message:
> 
>  Could not launch default application for URI: Failed to execute 
> child process "firefox-esr" (Permission denied)

Is there anything showing in /var/log/syslog about this? I suspect that
maybe Apparmor is getting in the way.

Regards,
Simon



signature.asc
Description: OpenPGP digital signature


Bug#834966: mirror submission for mirror.lstn.net

2016-08-22 Thread Logan Vig
Hello,

> On Aug 21, 2016, at 12:52 PM, Donald Norwood  wrote:
> 
> *Please check your configuration for active/passive modes:
> 
> Using binary mode to transfer files.
> ftp> ls
> 500 Illegal EPRT command.
> ftp: bind: Address already in use
> ftp> dir
> 500 Illegal EPRT command.
> ftp> passive
> Passive mode on.
> ftp> ls
> 229 Entering Extended Passive Mode (|||50457|)
> 150 Here comes the directory listing.
> -rw-r--r--2 33   33281 Jul 02 20:02 HEADER.html
> lrwxrwxrwx2 00  24 Aug 18 20:17 README.txt ->
> /var/www/html/README.txt
> drwxrwxr-x   43 33   33 72 Jul 13 14:22 centos
> drwxr-xr-x9 33   33 16 Aug 21 09:48 debian
> …

I do see there is an issue with active mode FTP transfers. It seems to be 
related to contention over the port 20 bind between our load balancer and the 
ftp daemon. Are all of your mirrors required to support FTP? Can we publish the 
mirror as only supporting http(s) and rsync? I’d like to fully support FTP at 
some point but I did not see a port bind option in the vsftpd config reference 
just now so we may have to look at other daemons/options for a fix.

> 
> *Rsync is not listing the Debian directories:
> 

Fixed this.

Logan

Bug#835118: libmatroska-dev: Should update the shlibs file to at least 1.4.4

2016-08-22 Thread Christian Marillat
Package: libmatroska-dev
Version: 1.4.5-1
Severity: serious

Hi,

Severity serious as the msissing version in the dependency breaks
mkvtoolnix and mkvtoolnix-gui packages.

As requested by the upstream author :

,
| MKVToolNix v9.3.1 and newer use features newly introduced in libMatroska 
v1.4.4. This means that you cannot compile MKVToolNix v1.4.5 and try to run it 
against v1.4.4 — that’ll fail with symbol lookup errors from ld.
`

https://www.bunkus.org/blog/2016/08/mkvtoolnix-v9-4-0-released/

Christian

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

Kernel: Linux 4.6.0-1-686-pae (SMP w/4 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 libmatroska6v5 depends on:
ii  libc6   2.23-4
ii  libebml4v5  1.3.4-1
ii  libgcc1 1:6.1.1-12
ii  libstdc++6  6.1.1-12

libmatroska6v5 recommends no packages.

libmatroska6v5 suggests no packages.

-- no debconf information



Bug#835116: airlift-slice: FTBFS: Could not resolve dependencies for project io.airlift:slice:jar:0.10

2016-08-22 Thread Chris Lamb
Source: airlift-slice
Version: 0.10-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

airlift-slice fails to build from source in unstable/amd64:

  [..]

  Setting up libplexus-i18n-java (1.0-beta-10-3) ...
  Setting up libplexus-cli-java (1.2-5) ...
  Setting up libwagon2-java (2.10-4) ...
  Setting up libplexus-velocity-java (1.1.8-1) ...
  Setting up libplexus-archiver-java (2.2-1) ...
  Setting up libdoxia-java (1.1.4-6) ...
  Setting up libmaven2-core-java (2.2.1-26) ...
  Setting up libfindbugs-java (3.1.0~preview2-1) ...
  Setting up libeclipse-aether-java (1.0.2-1) ...
  Setting up libmaven-common-artifact-filters-java (1.4-1) ...
  Setting up libdoxia-sitetools-java (1.1.4-1.1) ...
  Setting up libmaven-filtering-java (1.1-1) ...
  Setting up libmaven-clean-plugin-java (2.5-1) ...
  Setting up libfindbugs-ant-java (3.1.0~preview2-1) ...
  Setting up libplexus-compiler-java (2.4-3) ...
  Setting up libplexus-component-metadata-java (1.6-2) ...
  Setting up libmaven-resources-plugin-java (2.6-1) ...
  Setting up libmaven-archiver-java (2.6-3) ...
  Setting up libmaven-shared-incremental-java (1.1-1) ...
  Setting up libmaven-doxia-tools-java (1.2.1-2) ...
  Setting up libplexus-containers1.5-java (1.6-2) ...
  Setting up libmaven-compiler-plugin-java (3.2-5) ...
  Setting up libmaven-site-plugin-java (2.1-4) ...
  Setting up findbugs (3.1.0~preview2-1) ...
  Setting up libmaven-jar-plugin-java (2.4-1) ...
  Setting up libsisu-plexus-java (0.3.2-1) ...
  Setting up libmaven3-core-java (3.3.9-4) ...
  Setting up maven (3.3.9-4) ...
  update-alternatives: using /usr/share/maven/bin/mvn to provide /usr/bin/mvn 
(mvn) in auto mode
  Processing triggers for sgml-base (1.28) ...
  Setting up libmaven-reporting-impl-java (2.3-1) ...
  Setting up libmaven-plugin-tools-java (3.3-5) ...
  Setting up libsurefire-java (2.17-2) ...
  Setting up maven-debian-helper (2.1.1) ...
  Setting up airlift-slice-build-deps (0.10-1) ...
  Processing triggers for libc-bin (2.23-4) ...
  Processing triggers for systemd (231-4) ...
  Processing triggers for ca-certificates (20160104) ...
  Updating certificates in /etc/ssl/certs...
  173 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  
  Adding debian:ACCVRAIZ1.pem
  Adding debian:ACEDICOM_Root.pem
  Adding debian:AC_Raíz_Certicámara_S.A..pem
  Adding debian:Actalis_Authentication_Root_CA.pem
  Adding debian:AddTrust_External_Root.pem
  Adding debian:AddTrust_Low-Value_Services_Root.pem
  Adding debian:AddTrust_Public_Services_Root.pem
  Adding debian:AddTrust_Qualified_Certificates_Root.pem
  Adding debian:AffirmTrust_Commercial.pem
  Adding debian:AffirmTrust_Networking.pem
  Adding debian:AffirmTrust_Premium.pem
  Adding debian:AffirmTrust_Premium_ECC.pem
  Adding debian:ApplicationCA_-_Japanese_Government.pem
  Adding debian:Atos_TrustedRoot_2011.pem
  Adding debian:Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem
  Adding debian:Baltimore_CyberTrust_Root.pem
  Adding debian:Buypass_Class_2_CA_1.pem
  Adding debian:Buypass_Class_2_Root_CA.pem
  Adding debian:Buypass_Class_3_Root_CA.pem
  Adding debian:CA_Disig.pem
  Adding debian:CA_Disig_Root_R1.pem
  Adding debian:CA_Disig_Root_R2.pem
  Adding debian:CA_WoSign_ECC_Root.pem
  Adding debian:CFCA_EV_ROOT.pem
  Adding debian:CNNIC_ROOT.pem
  Adding debian:COMODO_Certification_Authority.pem
  Adding debian:COMODO_ECC_Certification_Authority.pem
  Adding debian:COMODO_RSA_Certification_Authority.pem
  Adding debian:Camerfirma_Chambers_of_Commerce_Root.pem
  Adding debian:Camerfirma_Global_Chambersign_Root.pem
  Adding debian:Certification_Authority_of_WoSign_G2.pem
  Adding debian:Certigna.pem
  Adding debian:Certinomis_-_Autorité_Racine.pem
  Adding debian:Certinomis_-_Root_CA.pem
  Adding debian:Certplus_Class_2_Primary_CA.pem
  Adding debian:Certum_Root_CA.pem
  Adding debian:Certum_Trusted_Network_CA.pem
  Adding debian:Chambers_of_Commerce_Root_-_2008.pem
  Adding 
debian:China_Internet_Network_Information_Center_EV_Certificates_Root.pem
  Adding debian:ComSign_CA.pem
  Adding debian:Comodo_AAA_Services_root.pem
  Adding debian:Comodo_Secure_Services_root.pem
  Adding debian:Comodo_Trusted_Services_root.pem
  Adding debian:Cybertrust_Global_Root.pem
  Adding debian:D-TRUST_Root_Class_3_CA_2_2009.pem
  Adding debian:D-TRUST_Root_Class_3_CA_2_EV_2009.pem
  Adding debian:DST_ACES_CA_X6.pem
  Adding debian:DST_Root_CA_X3.pem
  Adding debian:Deutsche_Telekom_Root_CA_2.pem
  Adding debian:DigiCert_Assured_ID_Root_CA.pem
  Adding debian:DigiCert_Assured_ID_Root_G2.pem
  Adding debian:DigiCert_Assured_ID_Root_G3.pem
  Adding debian:DigiCert_Global_Root_CA.pem
  Adding debian:DigiCert_Global_Root_G2.pem
  Adding debian:DigiCert_Global_Root_G3.pem
  Adding debian:DigiCert_High_Assurance_EV_Root_CA.pem
  Adding 

Bug#835098: gcr: FTBFS: Missing build-depends on gnupg

2016-08-22 Thread Michael Biebl
Am 22.08.2016 um 15:04 schrieb Santiago Vila:
> Package: src:gcr
> Version: 3.20.0-2
> Severity: serious
> Tags: patch
> 
> Dear maintainer:
> 
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:
> 
> 
> [...]
>  debian/rules build-indep
> dh build-indep --with autoreconf,gir,gnome
>dh_testdir -i
>dh_update_autotools_config -i
>debian/rules override_dh_autoreconf
> make[1]: Entering directory '/<>'
> dh_autoreconf --as-needed
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build'.
> libtoolize: copying file 'build/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'build/m4'.
> libtoolize: copying file 'build/m4/libtool.m4'
> libtoolize: copying file 'build/m4/ltoptions.m4'
> libtoolize: copying file 'build/m4/ltsugar.m4'
> 
> [...]
> 
> checking for gpg... no
> checking for gpg2... no
> 
> [...]
> 
> **
> ERROR:gcr/test-gnupg-collection.c:161:test_load: assertion failed (error == 
> NULL): Failed to execute child process "gpg" (No such file or directory) 
> (g-exec-error-quark, 8)
> FAIL: test-gnupg-collection 2 /gcr/gnupg-collection/load
> FAIL: test-gnupg-collection 3 /gcr/gnupg-collection/reload
> **
> ERROR:gcr/test-gnupg-collection.c:208:test_reload: assertion failed (error == 
> NULL): Failed to execute child process "gpg" (No such file or directory) 
> (g-exec-error-quark, 8)
> ERROR: test-gnupg-collection process failed: 250
> 
> [...]
> 
> debian/rules:24: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Error 1
> make[1]: Leaving directory '/<>'
> debian/rules:9: recipe for target 'build-indep' failed
> make: *** [build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
> 
> 
> The gnupg package is not essential, so if this package needs it during
> the build, it should declare it in Build-Depends.
> 
> [ In this case, the fact that I was doing "dpkg-buildpackage -A" does not 
> matter,
>   it would also fail with ordinary "dpkg-buildpackage" ].
> 
> To reproduce, please try to build the package on a chroot not having
> gnupg installed (neither gnupg1 or gnupg).
> 
> The attached patch (untested) might fix this bug.

It seems to be required to run the test-suite only.
So it would make sense to mark the build depedency with 
(requires a bump of dpkg-dev and debhelper as well).


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



signature.asc
Description: OpenPGP digital signature


Bug#834966: mirror submission for mirror.lstn.net

2016-08-22 Thread Logan Vig
Hello,

it is a gluster based mirror with quorum writes enabled. We should see strong 
write consistency between the nodes with writes failing if quorum issues exist. 
We prefer to see a sync fail if there are environment issues than end up with 
split brain scenarios between the nodes. I think this is in line with what you 
are expecting as well.

Logan

> On Aug 21, 2016, at 2:48 PM, Bastian Blank  wrote:
> 
> Hi
> 
> On Sun, Aug 21, 2016 at 01:52:19PM -0400, Donald Norwood wrote:
>> Node Name  : LSN-C78
>> Node Name  : LSN-C77
> 
> Quick questions: how do you make sure this different nodes share the
> same state?  The Debian archive layout currently have some pretty strict
> synchronization requirements.  If clients reach different nodes with
> different states of the archive, they will see checksum errors as every
> file of the archive is checked after download.
> 
> Regards,
> Bastian
> 
> -- 
> Beam me up, Scotty!  It ate my phaser!



Bug#835075: libmail-gnupg-perl: FTBFS: Failed 1/10 test programs. 0/4 subtests failed.

2016-08-22 Thread gregor herrmann
Control: tag -1 + confirmed upstream

On Mon, 22 Aug 2016 08:20:05 +0100, Chris Lamb wrote:

> Source: libmail-gnupg-perl
> Version: 0.22-1
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> libmail-gnupg-perl fails to build from source in unstable/amd64:
> 
>   [..]

>   t/20.inline-verify.t . skipped: failed to import GPG keys for testing
>   t/25.multipart-verify.t .. skipped: failed to import GPG keys for testing
>   You tried to plan twice at t/30.inline-decrypt.t line 30.
>   # Looks like you planned 5 tests but ran 1.
>   # Looks like your test exited with 2 just after 1.
>   t/30.inline-decrypt.t  
>   1..5
>   ok 1 - An object of class 'MIME::Entity' isa 'MIME::Entity'
>   gpg: keybox 
> '/home/lamby/temp/cdt.20160822081228.ynLAUew7Ua.db.libmail-gnupg-perl/libmail-gnupg-perl-0.22/mgtg4ltC/pubring.kbx'
>  created
>   gpg: 
> /home/lamby/temp/cdt.20160822081228.ynLAUew7Ua.db.libmail-gnupg-perl/libmail-gnupg-perl-0.22/mgtg4ltC/trustdb.gpg:
>  trustdb created
>   gpg: key 49539D60EFEA4EAD marked as ultimately trusted
>   gpg: key 49539D60EFEA4EAD: public key "Mail::GnuPG Test Key 
> " imported
>   gpg: can't connect to the agent: File name too long
>   gpg: error getting the KEK: No agent running
>   gpg: key 49539D60EFEA4EAD: "Mail::GnuPG Test Key " 1 new 
> signature
>   gpg: can't connect to the agent: File name too long
>   gpg: Total number processed: 2
>   gpg:   imported: 1
>   gpg: new signatures: 1
>   gpg:   secret keys read: 1
>   gpg: marginals needed: 3  completes needed: 1  trust model: pgp
>   gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
>   Dubious, test returned 2 (wstat 512, 0x200)
>   Failed 4/5 subtests 
>   t/35.has-public-key.t  skipped: failed to import GPG keys for testing
>   t/99.pod.t ... 
>   1..1
>   ok 1 - POD test for blib/lib/Mail/GnuPG.pm
>   ok
>   t/agent.t  skipped: unable to find gpg agent
>   t/base.t . 
>   1..1
>   ok 1
>   ok
>   t/round-trip.t ... skipped: failed to import GPG keys for testing

Interestingly, it fails differently for me:

t/05.load.t .. 
1..1
ok 1 - use Mail::GnuPG;
ok
t/20.inline-verify.t . 
gpg: keybox '/build/libmail-gnupg-perl-0.23/mgtBaEfN/pubring.kbx' created
gpg: /build/libmail-gnupg-perl-0.23/mgtBaEfN/trustdb.gpg: trustdb created
gpg: key 792152527B75921E: public key "Antoine Beaupré " 
imported
gpg: key 762B57BB784206AD: public key "David Bremner " 
imported
gpg: key FBE5FCA59456D16A: public key "Mauricio Campiglia 
" imported
gpg: Total number processed: 3
gpg:   imported: 3
gpg: no ultimately trusted keys found
1..5
ok 1 - An object of class 'MIME::Entity' isa 'MIME::Entity'
ok 2 - An object of class 'Mail::GnuPG' isa 'Mail::GnuPG'
ok 3 - verify success
ok 4 - verify keyid
ok 5 - verify uid
ok
t/25.multipart-verify.t .. 
gpg: keybox '/build/libmail-gnupg-perl-0.23/mgtNFlFc/pubring.kbx' created
gpg: /build/libmail-gnupg-perl-0.23/mgtNFlFc/trustdb.gpg: trustdb created
gpg: key 792152527B75921E: public key "Antoine Beaupré " 
imported
gpg: key 762B57BB784206AD: public key "David Bremner " 
imported
gpg: key FBE5FCA59456D16A: public key "Mauricio Campiglia 
" imported
gpg: Total number processed: 3
gpg:   imported: 3
gpg: no ultimately trusted keys found
1..5
ok 1 - An object of class 'MIME::Entity' isa 'MIME::Entity'
ok 2 - An object of class 'Mail::GnuPG' isa 'Mail::GnuPG'
ok 3 - verify success
ok 4 - verify keyid
ok 5 - verify uid
ok
You tried to plan twice at t/30.inline-decrypt.t line 30.
# Looks like you planned 5 tests but ran 1.
# Looks like your test exited with 2 just after 1.
t/30.inline-decrypt.t  
1..5
ok 1 - An object of class 'MIME::Entity' isa 'MIME::Entity'
gpg: keybox '/build/libmail-gnupg-perl-0.23/mgtHi1Tk/pubring.kbx' created
gpg: /build/libmail-gnupg-perl-0.23/mgtHi1Tk/trustdb.gpg: trustdb created
gpg: key 49539D60EFEA4EAD marked as ultimately trusted
gpg: key 49539D60EFEA4EAD: public key "Mail::GnuPG Test Key " 
imported
gpg: key 49539D60EFEA4EAD/49539D60EFEA4EAD: error sending to agent: 
Inappropriate ioctl for device
gpg: error building skey array: Inappropriate ioctl for device
gpg: key 49539D60EFEA4EAD: "Mail::GnuPG Test Key " 1 new 
signature
gpg: Total number processed: 2
gpg:   imported: 1
gpg: new signatures: 1
gpg:   secret keys read: 1
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
Dubious, test returned 2 (wstat 512, 0x200)
Failed 4/5 subtests 
t/35.has-public-key.t  skipped: 

  1   2   3   >