Bug#819582: dput-ng: dcut manpage incorect, cancel --filename should be cancel --file

[Salvatore Bonaccorso]

Control: retitle -1 dput-ng: dcut manpage incorect, --filename should be --file 
for various subcommands

Hi,

On Wed, Mar 30, 2016 at 07:58:55PM +0100, Colin Tuckley wrote:
> Package: dput-ng
> Version: 1.10
> Severity: minor
> 
> The man page for dcut says that the only valid option for the 'cancel' 
> command is:
> 
> -f, --filename=FILENAME
> 
> this is incorrect the option is actually:
> 
> -f, --file=FILENAME

It is actually as well for the other subcommands (reschedule, rm,
upload) as well).

Regards,
Salvatore

Bug#817650: ree: Removal of debhelper compat 4

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

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

  * debian/compat: Bump to 9.
  * debian/control:
- Build-depend on debhelper (>= 9).
- Depend on ${misc:Depends}.
- Remove dead homepage URL from description.
  * debian/rules: Convert to dh sequencer.
  * makefile:
- Add -f to rm command in clean target.
- Add variables to pass in hardening flags.
  * fontdump.c: Include  for the bcmp function.
  * ree.c: Include  for the strncmp function.

Thanks for considering the patch.

Logan Rosen
diff -u ree-1.3/makefile ree-1.3/makefile
--- ree-1.3/makefile
+++ ree-1.3/makefile
@@ -1,9 +1,9 @@
 all:
-	gcc ree.c -o ree
-	gcc fontdump.c -o fontdump
+	$(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) ree.c -o ree
+	$(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) fontdump.c -o fontdump
 
 clean:
-	rm fontdump ree
+	rm -f fontdump ree
 
 install:
 	cp fontdump $(DESTDIR)/usr/bin
diff -u ree-1.3/fontdump.c ree-1.3/fontdump.c
--- ree-1.3/fontdump.c
+++ ree-1.3/fontdump.c
@@ -12,6 +12,7 @@
 */
 
 #include 
+#include 
 
 #define	CHARA 65
 
diff -u ree-1.3/ree.c ree-1.3/ree.c
--- ree-1.3/ree.c
+++ ree-1.3/ree.c
@@ -17,6 +17,7 @@
 */
 
 #include 
+#include 
 
 char* ID_ROMEXT="Uª"; /* 0x55aa */
 
diff -u ree-1.3/debian/compat ree-1.3/debian/compat
--- ree-1.3/debian/compat
+++ ree-1.3/debian/compat
@@ -1 +1 @@
-4
+9
diff -u ree-1.3/debian/rules ree-1.3/debian/rules
--- ree-1.3/debian/rules
+++ ree-1.3/debian/rules
@@ -2,68 +2,2 @@
-# -*- makefile -*-
-# Sample debian/rules that uses debhelper.
-# GNU copyright 1997 to 1999 by Joey Hess.
-
-# Uncomment this to turn on verbose mode.
-#export DH_VERBOSE=1
-
-CFLAGS = -Wall -g
-
-ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
-	CFLAGS += -O0
-else
-	CFLAGS += -O2
-endif
-
-configure: configure-stamp
-configure-stamp:
-	dh_testdir
-	touch configure-stamp
-
-
-build: build-stamp
-
-build-stamp: configure-stamp 
-	dh_testdir
-	$(MAKE)
-	touch build-stamp
-
-clean:
-	dh_testdir
-	dh_testroot
-	rm -f build-stamp configure-stamp
-	-$(MAKE) clean
-	dh_clean 
-
-install: build
-	dh_testdir
-	dh_testroot
-	dh_clean -k 
-	dh_installdirs
-	$(MAKE) install DESTDIR=$(CURDIR)/debian/ree
-
-
-# Build architecture-independent files here.
-binary-indep: build install
-# We have nothing to do by default.
-
-# Build architecture-dependent files here.
-binary-arch: build install
-	dh_testdir
-	dh_testroot
-	dh_installchangelogs 
-	dh_installdocs
-	dh_installexamples
-#	dh_install
-	dh_installman
-	dh_link
-	dh_strip
-	dh_compress
-	dh_fixperms
-	dh_installdeb
-	dh_shlibdeps
-	dh_gencontrol
-	dh_md5sums
-	dh_builddeb
-
-binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+%:
+	dh $@
diff -u ree-1.3/debian/control ree-1.3/debian/control
--- ree-1.3/debian/control
+++ ree-1.3/debian/control
@@ -5,13 +5,11 @@
-Build-Depends: debhelper (>= 4.0.0)
+Build-Depends: debhelper (>= 9)
 Standards-Version: 3.6.2
 
 Package: ree
 Architecture: i386 amd64 ia64 kfreebsd-i386 hurd-i386 kfreebsd-amd64
-Depends: ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}
 Suggests: file, nasm, bc
 Description: Extract ROM extensions
  ROM extension extractor (ree) is a tool which extracts ROM extensions
  from the firmware of a PC computer. It can also extract font data from
  video card ROMs.
- .
- Homepage: http://gnu.ethz.ch/linuks.mine.nu/ree/

Bug#833570: fontconfig: diff for NMU version 2.11.0-6.5

[Salvatore Bonaccorso]

Hi Keith,

On Sat, Aug 06, 2016 at 03:04:14PM -0700, Keith Packard wrote:
> Salvatore Bonaccorso  writes:
> 
> > Control: tags 833570 + pending
> >
> > Hi Keith,
> >
> > I've prepared an NMU for fontconfig (versioned as 2.11.0-6.5) and
> > uploaded it to DELAYED/5. Please feel free to tell me if I
> > should delay it longer.
> 
> Looks like that patch is already in fontconfig 2.12.1; thanks for
> backporting. I don't see any reason to delay this any more than that,
> I'd be comfortable with having it move into unstable immediately.

Thanks a lot for your quick reply!

I will reschedule then to have the fix sooner in unstable.

As wrote in the previous bug mail, I have as well already prepared the
jessie-security based one, but I was still going to evaluate if we
have any reverse dependency using fontconfig in the explained way.
fbterm for example is not setuid in Debian at least.

Regards,
Salvatore


signature.asc
Description: PGP signature

Bug#830607: python-simpy: accesses the internet during build

[Andreas Tille]

Hi again,

may be this issue should be forwarded to Debian Python list as well.
Please note that I have now removed the whole docs/html dir in a
repackaged tarball since it is not used in the build anyway and now
lintian and disk space are more happy than before.

Please tell me whether I should upload the current state in Git
or close the bug manually?

Kind regards

   Andreas.

On Sun, Aug 07, 2016 at 12:43:06AM +0200, Andreas Tille wrote:
> Hi,
> 
> I have commited some enhancements to python-simpy (fixed lintian errors
> and other stuff) but I can not reproduce the described bug.  IMHO it
> should be closed - either manually or by uploading the changes in Git.
> 
> Kind regards
> 
>Andreas.
> 
> -- 
> http://fam-tille.de

-- 
http://fam-tille.de

Bug#833415: dialpad during calls

[Alexandre Viau]

Hello,

The fact that there is no dialpad during calls is a known missing
feature of Ring.

I have marked the bug as forwarded to upstream:
 - https://tuleap.ring.cx/plugins/tracker/?aid=154

Hopefully this gets addressed soon, sorry for the inconvenience.

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#833609: Duplicate of 833571

[Alexandre Viau]

Hello,

This bug is a duplicate of 833571.

The issue was fixed in 20160729.2.7a7dbd6~dfsg1-2, which is in unstable
and has an urgency of 'high'. It should migrate to testing any time now.

Thank you for reporting, and sorry for the inconvenience.

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#782904: python-debian test failures with gnupg-2.1.3

[Stuart Prescott]

Thanks for looking over the patch.
 
> PS Stuart, your patch has Subject: "PATCH 1/2" -- was there a second
>patch in the series, or did you just extract it from a larger
>patchset you were playing with?

The second patch is changing the related tests to use @unittest.skip* 
decorators rather than returning from the test if it can't be run because gpgv 
is not installed. It's just minor polishing that improves the test output 
(marking it as skipped is better than pretending it passed) using tools that 
we can now use given we no longer need to support older python versions. So: 
unrelated to gpgv output but in the same local branch on the basis that this 
sort of maintenance happens only reactively when someone is touching a bit of 
code anyway. Thanks for double checking!

cheers
Stuart

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

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

Bug#833074: chromium: hidpi cinammon

[Michael Gilbert]

control: tag -1 moreinfo
control: severity -1 minor

Do any of the suggestions in http://crbug.com/515984 help?

Best wishes,
Mike

Bug#694879: Blender + OpenCOLLADA FTBFS

[ian_bruce]

On Thu, 4 Aug 2016 04:08:30 -0700
 wrote:

> If removing the illegal UTF-8 and Windows-1252 characters doesn't fix
> the problem, then try this:
> 
> 
> --- opencollada/COLLADAFramework/COLLADAFWPrerequisites.h.orig
> 2014-07-03 09:30:54.0 -0700
> +++ opencollada/COLLADAFramework/COLLADAFWPrerequisites.h 2016-08-04 
> 03:42:44.765860036 -0700
> @@ -11,6 +11,7 @@
>  #ifndef __COLLADAFW_PREREQUISITES_H__
>  #define __COLLADAFW_PREREQUISITES_H__
>  
> +#include 
>  #include 
>  
>  namespace COLLADAFW

Apparently, I was right:


--- 
opencollada_0.1.0~20140703.ddf8f47+dfsg1/COLLADAFramework/include/COLLADAFWInstanceBindingBase.h
2014-07-03 09:30:54.0 -0700
+++ 
opencollada_0.1.0~20160714.0ec5063+dfsg1/COLLADAFramework/include/COLLADAFWInstanceBindingBase.h
2016-07-13 12:25:45.0 -0700
@@ -15,6 +15,11 @@
 #include "COLLADAFWInstanceBase.h"
 #include "COLLADAFWMaterialBinding.h"
 
+#include "COLLADABUURI.h"
+
+#include 
+
+
 namespace COLLADAFW
 {
 

Bug#833593: affected kernels

[Adam Borowski]

I've looked at which kernels support getrandom:

3.16: amd64, i386, ia64, sparc
3.17: arm, s390, arm64, microblaze, mips, hppa, m68k, powerpc
3.18: xtensa
4.0: avr32
4.1: blackfin, alpha
4.3: cris

so most architectures lack it even in jessie (3.16).

And ARM is notorious for vendor kernels that might (hopefully) get minor
version upgrades but never move past their original major version.  Like, a
not too shabby box I run armhf archive rebuilds on is stuck on (regularly
updated) 3.8.

-- 
An imaginary friend squared is a real enemy.

Bug#809611: d-i fails to boot on HP mv2120

[Martin Michlmayr]

* Mike Thompson  [2016-08-06 18:32]:
> OK Martin, that image worked.  I did a full install of Debian Stretch from
> it.  Below is the output at the tail end of bootup and login.

Thanks for testing it!

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

Bug#740068: debian-installer: segfaults when built against testing

[Witold Baryluk]

Package: debian-installer
Followup-For: Bug #740068

Indeed this looks to be happening in stretch alpha 7 too. My mistake for
mentioning a daily snapshot - there is a separate segfault for
choose-mirror, that happen before we load libc6-udeb, and it is a
regression in current daily snapshots. I filled separate bug for this
under #833599 (but there is also a duplicate #833432).

I was using netboot/mini.iso from here

http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/netboot/mini.iso

SHA256SUM

6726ded054619ec2898c82f78d03f4faa4e8b4800dfee7e4524eddfa14fc6e7d  
./netboot/mini.iso

6726ded054619ec2898c82f78d03f4faa4e8b4800dfee7e4524eddfa14fc6e7d  
debian-installer-amd64-stretch-alpha-7-netboot-mini-20160630.iso

So far I was not able to reproduce this segfault under qemu (with BIOS or
with UEFI).

Bug#833102: chromium: Chromium 52 (gtk+3 issue) does not honor gtk-key-theme

[Michael Gilbert]

control: tag -1 moreinfo
control: severity -1 minor

I don't think this is a chromium bug.  GTK3 settings live in a new path:
http://shallowsky.com/blog/linux/gtk3-emacs-key-theme.html

Best wishes,
Mike

Bug#833621: RFS: libgap-sage/4.8.3+ds-1 [ITP] -- GAP kernel as a C shared library

[Jerome Benoit]

Package: sponsorship-requests
Severity: wishlist

Dear Sponsors,

I am looking for sponsorship for the Debian package libgap-sage [1]: 
this
package brings to Debian libGAP, a C interleave library that permits to
play with GAP within C/C++/Cython code. As you already guessed, LibGAP
is used by the Sage[Math], a Computer Algebra System (CAS) that 
superseeds
the Singular and GAP CAS among a myriad of mathematical packages.
This Debian package is meant for the experimental distribution because
the upstream package was designed for the former GAP version 4r8p3
while the current GAP version 4r8p4 is already present in Sid and 
Stretch.
libgap-sage is part of the Sage[Math] packaging effort.

Thanks in advance,
Jerome

[1] https://anonscm.debian.org/cgit/debian-science/packages/libgap-sage.git

-- 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)

Bug#833620: please package clementine-1.3.1

[Nicholas D Steeves]

Package: clementine
Version: 1.3~rc1-1

Please package clementine-1.3.1.  It "Fixes a bug where ratings are deleted 
when upgrading from older versions" ( https://www.clementine-player.org/ ).  
Other than that, it looks like git will need to be used to get the delta of 
changes between 1.3~rc1 and 1.3.1, because the upstream changelog doesn't seem 
to have changed.

Due to changing upstream build requirements, I recommend this change:

diff --git a/debian/control b/debian/control
index 3b1b726..7dbe890 100644
--- a/debian/control
+++ b/debian/control
@@ -28,7 +28,7 @@ Build-Depends: cmake (>= 2.6),
libqxt-dev,
libsparsehash-dev,
libsqlite3-dev,
-   libtag1-dev (>= 1.8),
+   libtag1-dev (>= 1.11),
protobuf-compiler,
qt4-dev-tools,
 Standards-Version: 3.9.6

Additionally, I would like to backport v1.3.1 to jessie, because the Android 
remote control requires clementine >=v1.3.

Best regards,
Nicholas


signature.asc
Description: Digital signature

Bug#833432: Segfault in choose-mirror in PXE install, Stretch/daily

[Witold Baryluk]

Package: choose-mirror
Followup-For: Bug #833432


I think this is a regression in version 2.70, version 2.69 from alpha works.

I accidently opened bug in debian-installer, bug #833599 with same symptomps.

Bug#809611: d-i fails to boot on HP mv2120

[Mike Thompson]

OK Martin, that image worked.  I did a full install of Debian Stretch from
it.  Below is the output at the tail end of bootup and login.


Debian GNU/Linux stretch/sid backup ttyS0

backup login: root
Password:
Linux backup 4.6.0-1-marvell #1 Debian 4.6.4-1 (2016-07-18) armv5tel


The 0x60 change also still continues to boot my existing Debian Jessie
install.

Thanks for the work you do to keep these old pieces of NAS hardware working.

Mike

On Sat, Aug 6, 2016 at 12:37 PM, Martin Michlmayr  wrote:

> Hi Mike,
>
> * Mike Thompson  [2016-08-05 20:23]:
> > The good news is that given the load address change from 0x40 to
> > 0x60 allowed the MV2120 to boot into the ssh based installer.
>
> Great!
>
> > The bad news is the installed failed from what looked like some sort of
> > segmentation faults in the installer from the looks of the logs which I
> > included below.
>
> I wonder if this is the same as
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833599
>
> Can you please test this image:
> http://ftp.nl.debian.org/debian/dists/testing/main/
> installer-armel/current/images/orion5x/network-
> console/hp/mv2120/netboot.img
>
> --
> Martin Michlmayr
> http://www.cyrius.com/
>

Bug#833599: debian-installer: choose-mirror segfaults

[Witold Baryluk]

Package: debian-installer
Followup-For: Bug #833599


BTW. This is the source of the image downloaded:

https://d-i.debian.org/daily-images/amd64/daily/netboot/mini.iso

on 2016-08-06

MD256SUM

eda5ccb294131789f2b6f651b6a88ca805428f9cfb04e475e354b219ecc33731  
./netboot/mini.iso

renamed as

debian-installer-amd64-testing-netboot-mini-20160806.iso

MD256SUM

eda5ccb294131789f2b6f651b6a88ca805428f9cfb04e475e354b219ecc33731  
debian-installer-amd64-testing-netboot-mini-20160806.iso


It is easy to replicate (tested on a computer with very long and stable
operation) the problem under qemu:

qemu-system-x86_64 -enable-kvm -cdrom 
debian-installer-amd64-testing-netboot-mini-20160806.iso -m 1024

It happens both under BIOS and UEFI (-bios OVFM.fd switch). With -smp 4, and 
without.

It also happens in normal and expert installations.

Always in the same spot in choose-mirror.

Bug#833599: debian-installer: choose-mirror segfaults

[Witold Baryluk]

Package: debian-installer
Followup-For: Bug #833599

I can confirm this is unrelated to libc6-udeb issues.

I am able to go past choose-mirror on strech alpha 7 netboot.iso (however
it fails with libc6-udeb 2.23-4 , and a segfault in 'sh' much later in the
install process after retriving installer components).

Bug#833342: chromium: crashes upon the first keypress in wayland

[Michael Gilbert]

control: severity -1 minor
control: forwarded -1 http://crbug.com/615164

You should be able to work around this by using GDK_BACKEND=x11.

Best wishes,
Mike

Bug#833599: debian-installer: choose-mirror segfaults

[Witold Baryluk]

Package: debian-installer
Followup-For: Bug #833599

Same problem reported by another person for choose-mirror package in bug #833432

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

Regards,
Witek

Bug#833619: /usr/bin/qemu-system-x86_64: Option -memory doesn't work. But -m do.

[Witold Baryluk]

Package: qemu-system-x86
Version: 1:2.6+dfsg-3
Severity: normal
File: /usr/bin/qemu-system-x86_64

With

qemu-system-x86_64 -help

I see

-m[emory] [size=]megs[,slots=n,maxmem=size]
configure guest RAM
size: initial amount of guest memory
slots: number of hotplug slots (default: none)
maxmem: maximum amount of guest memory (default: none)


but when adding -memory 2048

qemu says there is no such option.

Using -m 2048 solves the problem.

Please fix the usage instructions or fix the bug in qemu.

Thanks.



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

Kernel: Linux 4.7.0-rc7-wc1-6-g63bab22 (SMP w/12 CPU cores; PREEMPT)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages qemu-system-x86 depends on:
ii  ipxe-qemu   1.0.0+git-20150424.a25a16d-1
ii  libaio1 0.3.110-3
ii  libasound2  1.1.1-2
ii  libbluetooth3   5.36-1+b1
ii  libbrlapi0.65.3.1-3
ii  libc6   2.23-4
ii  libcacard0  1:2.5.0-2
ii  libfdt1 1.4.0+dfsg-2
ii  libgcc1 1:6.1.1-10
ii  libglib2.0-02.48.1-2
ii  libgnutls30 3.5.2-2
ii  libjpeg62-turbo 1:1.5.0-1
ii  libncurses5 6.0+20160625-1
ii  libnettle6  3.2-1
ii  libpixman-1-0   0.33.6-1
ii  libpng16-16 1.6.23-1
ii  libpulse0   9.0-1.1
ii  libsasl2-2  2.1.26.dfsg1-15
ii  libsdl1.2debian 1.2.15+dfsg1-4
ii  libseccomp2 2.3.1-2
ii  libspice-server10.12.8-1
ii  libtinfo5   6.0+20160625-1
ii  libusb-1.0-02:1.0.20-1
ii  libusbredirparser1  0.7.1-1
ii  libuuid12.28-6
ii  libvdeplug2 2.3.2+r586-2+b1
ii  libx11-62:1.6.3-1
ii  libxen-4.6  4.6.0-1+nmu2
ii  libxenstore3.0  4.6.0-1+nmu2
ii  qemu-system-common  1:2.6+dfsg-3
ii  seabios 1.8.2-1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages qemu-system-x86 recommends:
ii  qemu-utils  1:2.6+dfsg-3

Versions of packages qemu-system-x86 suggests:
ii  kmod  22-1.1
ii  ovmf  0~20160408.ffea0a2c-2
pn  qemu-block-extra  
pn  samba 
pn  sgabios   
ii  vde2  2.3.2+r586-2+b1

-- no debconf information

Bug#540852: Latest info on urgency

[Sean Whitton]

control: tag -1 +patch

Hello,

On Tue, Aug 02, 2016 at 08:30:26PM -0700, Sean Whitton wrote:
> The information about urgency in this announcement from the release team
> should probably be included in the Developer's Reference:
> 

And here's a git-am-able patch doing that.  Please consider applying it.

-- 
Sean Whitton
From 1cb003f98cdec9e272cb950aaa46f99fd21463d2 Mon Sep 17 00:00:00 2001
From: Sean Whitton 
Date: Sat, 6 Aug 2016 17:00:45 -0700
Subject: [PATCH] add section "Selecting the upload urgency"

Based on https://lists.debian.org/debian-devel-announce/2013/11/msg7.html
---
 best-pkging-practices.dbk | 16 
 debian/changelog  |  7 +++
 2 files changed, 23 insertions(+)

diff --git a/best-pkging-practices.dbk b/best-pkging-practices.dbk
index 1651ddb..664722e 100644
--- a/best-pkging-practices.dbk
+++ b/best-pkging-practices.dbk
@@ -462,6 +462,22 @@ linkend="upload-bugfix"/> for more information.
 
 
 
+
+Selecting the upload urgency
+
+The release team have indicated that they expect most uploads to
+unstable to use urgency=medium.  That is, you should choose
+urgency=medium unless there is some
+particular reason for the upload to migrate to
+testing more quickly or slowly (see ).  For example, you might select
+urgency=low if the changes since
+the last upload are large and might be disruptive in unanticipated
+ways.
+
+
+
 
 Common misconceptions about changelog entries
 
diff --git a/debian/changelog b/debian/changelog
index 5b60efd..864269d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+developers-reference (3.4.19) UNRELEASED; urgency=medium
+
+  * Add section "Selecting the upload urgency" to best-pkging-practices
+(Closes: #540852).
+
+ -- Sean Whitton   Sat, 06 Aug 2016 16:55:31 -0700
+
 developers-reference (3.4.18) unstable; urgency=medium
 
   [ Raphaël Hertzog ]
-- 
2.8.1



signature.asc
Description: PGP signature

Bug#833617: [nvidia-settings] update to 367.35

[Michał Mirosław]

Source: nvidia-settings
Severity: normal
Tags: patch

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

Please consider updating to new upstream version 367.35. PoC patch attached.
diff -urN nvidia-settings-346.59/debian/patches/04_link_as-needed.diff nvidia-settings-367.35/debian/patches/04_link_as-needed.diff
--- nvidia-settings-346.59/debian/patches/04_link_as-needed.diff	2015-03-18 20:47:55.0 +0100
+++ nvidia-settings-367.35/debian/patches/04_link_as-needed.diff	2016-08-07 00:12:40.0 +0200
@@ -1,9 +1,11 @@
 Author: Andreas Beckmann 
 Description: link with -Wl,--as-needed to reduce library footprint
 
 a/utils.mk
-+++ b/utils.mk
-@@ -36,6 +36,9 @@
+Index: nvidia-settings-367.35/utils.mk
+===
+--- nvidia-settings-367.35.orig/utils.mk
 nvidia-settings-367.35/utils.mk
+@@ -42,6 +42,9 @@ CC_ONLY_CFLAGS?=
  LDFLAGS   ?=
  BIN_LDFLAGS   ?=
  
@@ -13,9 +15,11 @@
  HOST_CC   ?= $(CC)
  HOST_LD   ?= $(LD)
  HOST_CFLAGS   ?= $(CFLAGS)
 a/samples/Makefile
-+++ b/samples/Makefile
-@@ -59,6 +59,8 @@
+Index: nvidia-settings-367.35/samples/Makefile
+===
+--- nvidia-settings-367.35.orig/samples/Makefile
 nvidia-settings-367.35/samples/Makefile
+@@ -59,6 +59,8 @@ LDFLAGS   += $(X_LDFLAGS)
  LDFLAGS   += -L $(XNVCTRL_DIR)
  LIBS  += -lXNVCtrl -lXext -lX11
  
diff -urN nvidia-settings-346.59/debian/patches/05_nostrip.diff nvidia-settings-367.35/debian/patches/05_nostrip.diff
--- nvidia-settings-346.59/debian/patches/05_nostrip.diff	2015-03-18 20:47:55.0 +0100
+++ nvidia-settings-367.35/debian/patches/05_nostrip.diff	2016-08-07 00:12:40.0 +0200
@@ -1,13 +1,16 @@
 Description: Install unstripped binaries, dh_strip takes care of this.
 Author: Andreas Beckmann 
 
 a/utils.mk
-+++ b/utils.mk
-@@ -53,6 +53,7 @@
-   STRIP_CMD   ?= true
+Index: nvidia-settings-367.35/utils.mk
+===
+--- nvidia-settings-367.35.orig/utils.mk
 nvidia-settings-367.35/utils.mk
+@@ -61,7 +61,7 @@ ifeq ($(DEBUG),1)
CFLAGS  += -O0 -g
  else
-+  STRIP_CMD   ?= true # let dh_strip do the stripping
STRIP_CMD   ?= strip
+-  DO_STRIP?= 1
++  DO_STRIP?= 0 # let dh_strip do the stripping
  endif
  
+ INSTALL   ?= install
diff -urN nvidia-settings-346.59/debian/patches/10_libxnvctrl_so_0.diff nvidia-settings-367.35/debian/patches/10_libxnvctrl_so_0.diff
--- nvidia-settings-346.59/debian/patches/10_libxnvctrl_so_0.diff	2015-03-18 21:05:06.0 +0100
+++ nvidia-settings-367.35/debian/patches/10_libxnvctrl_so_0.diff	2016-08-07 00:12:40.0 +0200
@@ -2,8 +2,10 @@
 Description: build a shared library for libXNVCtrl
 Bug-Debian: http://bugs.debian.org/666909
 
 a/src/Makefile
-+++ b/src/Makefile
+Index: nvidia-settings-367.35/src/Makefile
+===
+--- nvidia-settings-367.35.orig/src/Makefile
 nvidia-settings-367.35/src/Makefile
 @@ -106,6 +106,9 @@ endif
  XNVCTRL_DIR ?= libXNVCtrl
  XNVCTRL_MAKEFILE?= Makefile
@@ -14,39 +16,42 @@
  XCONFIG_PARSER_DIR  ?= XF86Config-parser
  COMMON_UTILS_DIR?= common-utils
  COMMON_UNIX_DIR ?= common-unix
-@@ -280,14 +283,17 @@ NVIDIA_SETTINGS_install: $(NVIDIA_SETTIN
+@@ -280,15 +283,18 @@ NVIDIA_SETTINGS_install: $(NVIDIA_SETTIN
  	$(MKDIR) $(BINDIR)
  	$(INSTALL) $(INSTALL_BIN_ARGS) $< $(BINDIR)/$(notdir $<)
  
--$(NVIDIA_SETTINGS): $(OBJS) $(XNVCTRL_ARCHIVE)
 +$(XNVCTRL_ARCHIVE) $(XNVCTRL_SHARED):
 +	$(MAKE) -C $(XNVCTRL_DIR)
 +
-+$(NVIDIA_SETTINGS): $(OBJS) $(XNVCTRL_LIB)
+ $(eval $(call DEBUG_INFO_RULES, $(NVIDIA_SETTINGS)))
+-$(NVIDIA_SETTINGS).unstripped: $(OBJS) $(XNVCTRL_ARCHIVE)
++$(NVIDIA_SETTINGS).unstripped: $(OBJS) $(XNVCTRL_LIB)
  	$(call quiet_cmd,LINK) $(CFLAGS) $(LDFLAGS) $(BIN_LDFLAGS) \
 -	-rdynamic -o $@ $(OBJS) $(XNVCTRL_ARCHIVE) $(LIBS)
 +	-rdynamic -o $@ $(OBJS) $(XNVCTRL_LIB) $(LIBS)
- 	$(call quiet_cmd,STRIP_CMD) $@
  
- $(GTK2LIB): $(GTK2_OBJS) $(XCP_OBJS) $(VERSION_MK)
+ $(eval $(call DEBUG_INFO_RULES, $(GTK2LIB)))
+ $(GTK2LIB).unstripped: $(GTK2_OBJS) $(XCP_OBJS) $(VERSION_MK)
  	$(call quiet_cmd,LINK) -shared $(CFLAGS) $(LDFLAGS) $(BIN_LDFLAGS) \
 -	$(XNVCTRL_ARCHIVE) $(LIBS) $(GTK2_LIBS) \
 +	$(XNVCTRL_LIB) $(LIBS) $(GTK2_LIBS) \
- 	-Wl,--unresolved-symbols=ignore-all -o $(GTK2LIB) \
+ 	-Wl,--unresolved-symbols=ignore-all -o $@ \
  	-Wl,-soname -Wl,$(GTK2LIB_SONAME) \
  	$(GTK2_OBJS) $(XCP_OBJS)
-@@ -296,7 +302,7 @@ $(GTK2LIB): $(GTK2_OBJS) $(XCP_OBJS) $(V
- ifdef BUILD_GTK3LIB
- $(GTK3LIB): $(GTK3_OBJS) $(XCP_OBJS) $(VERSION_MK)
+@@ -297,7 +303,7 @@ ifdef BUILD_GTK3LIB
+ $(eval $(call 

Bug#833616: [libopencv-dev] missing dependency on libopencv3.0-jni

[Michał Mirosław]

Package: libopencv-dev
Version: 3.0.0+dfsg-1~exp7
Severity: important

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

libopencv-dev should depend on libopencv3.0-jni - if that's not 
installed CMake's "FIND_PACKAGE(OpenCV REQUIRED)" generates:

CMake Error at /usr/share/OpenCV/OpenCVModules.cmake:120 (message):
   The imported target "opencv_java" references the file

  "/usr/lib/jni/libopencv_java300.so"

   but this file does not exist.  Possible reasons include:

   * The file was deleted, renamed, or moved to another location.

   * An install or uninstall procedure did not complete successfully.

   * The installation package was faulty and contained

  "/usr/share/OpenCV/OpenCVModules.cmake"

   but not all the files it references.

Call Stack (most recent call first):
   /usr/share/OpenCV/OpenCVConfig.cmake:86 (include)
   CMakeLists.txt:17 (FIND_PACKAGE)

Maybe similar to bug #818738.

--- System information. ---
Architecture: amd64
Kernel: Linux 4.6.3mq

Debian Release: stretch/sid
900 testing ftp.icm.edu.pl
800 jessie-backports ftp.icm.edu.pl
750 stable www.deb-multimedia.org
750 stable security.debian.org
750 stable repos.fds-team.de
750 stable ftp.icm.edu.pl
700 unstable ftp.icm.edu.pl
600 experimental ftp.icm.edu.pl
500 unstable-debug debug.mirrors.debian.org
500 testing-debug debug.mirrors.debian.org
500 stable dl.google.com
500 stable deb.opera.com
500 proposed-updates ftp.icm.edu.pl
1 experimental-debug debug.mirrors.debian.org

--- Package information. ---
Depends (Version) | Installed
==-+-==
libatomic1 (>= 4.8) | 6.1.1-10
libc6 (>= 2.14) |
libgcc1 (>= 1:3.0) |
libopencv-calib3d3.0 |
libopencv-core3.0 |
libopencv-features2d3.0 |
libopencv-flann3.0 |
libopencv-highgui3.0 |
libopencv-imgcodecs3.0 |
libopencv-imgproc3.0 |
libopencv-ml3.0 |
libopencv-objdetect3.0 |
libopencv-videoio3.0 |
libstdc++6 (>= 5.2) |
libtbb2 |
libopencv-core-dev (= 3.0.0+dfsg-1~exp7) |
libopencv-ml-dev (= 3.0.0+dfsg-1~exp7) |
libopencv-imgproc-dev (= 3.0.0+dfsg-1~exp7) |
libopencv-video-dev (= 3.0.0+dfsg-1~exp7) |
libopencv-videoio-dev (= 3.0.0+dfsg-1~exp7) |
libopencv-objdetect-dev (= 3.0.0+dfsg-1~exp7) |
libopencv-highgui-dev (= 3.0.0+dfsg-1~exp7) |
libopencv-calib3d-dev (= 3.0.0+dfsg-1~exp7) |
libopencv-flann-dev (= 3.0.0+dfsg-1~exp7) |
libopencv-features2d-dev (= 3.0.0+dfsg-1~exp7) |
libopencv-ts-dev (= 3.0.0+dfsg-1~exp7) |
libopencv-hal-dev (= 3.0.0+dfsg-1~exp7) |
libopencv-photo-dev (= 3.0.0+dfsg-1~exp7) |
libopencv-videostab-dev (= 3.0.0+dfsg-1~exp7) |
libopencv-shape-dev (= 3.0.0+dfsg-1~exp7) |
libopencv-stitching-dev (= 3.0.0+dfsg-1~exp7) |
libopencv-superres-dev (= 3.0.0+dfsg-1~exp7) |
libopencv-imgcodecs-dev (= 3.0.0+dfsg-1~exp7) |
libopencv-viz-dev (= 3.0.0+dfsg-1~exp7) |
pkg-config |


Recommends (Version) | Installed
==-+-===
opencv-data | 3.0.0+dfsg-1~exp7


Package's Suggests field is empty.

Bug#833607: nmu: python-mapnik_1:0.0~20160726-1c4a51d-1~exp1 & node-mapnik_3.5.13+dfsg-1~exp1

[Adam D. Barratt]

On Sun, 2016-08-07 at 00:11 +0200, Sebastiaan Couwenberg wrote:
> The wanna-build documentation on release.d.o [0] mentions "If you are
> asking for a dep-wait, an additional give-back is not needed", which
> seems to be incorrect based on your reply.
> 
> Is the documentation outdated perhaps?
> 
> [0] https://release.debian.org/wanna-build.txt

No, I think I was just impatient and forgot that while the state
initially changed to "bd-uninstallable", the dep-wait would have become
visible after the next trigger run, rather than immediately.

(However, it appears that it didn't work, in any case:

dose-builddebcheck changed state of node-mapnik_3.5.13+dfsg-1~exp1
(ppc64el) from dep-wait to Needs-Build
dose-builddebcheck changed state of
python-mapnik_1:0.0~20160726-1c4a51d-1~exp1 (ppc64el) from dep-wait to
Needs-Build

followed by repeated failures. If there any other queries, please raise
them on debian-wb-team@).

Regards,

Adam

Bug#833615: [nvidia-graphics-drivers] update to 367.35

[Michał Mirosław]

Source: nvidia-graphics-drivers
Severity: normal
Tags: patch

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

Please consider updating to 367.35. PoC patch attached.
diff --git a/debian/libcuda1.symbols b/debian/libcuda1.symbols
index 1408c7f..b9236b1 100644
--- a/debian/libcuda1.symbols
+++ b/debian/libcuda1.symbols
@@ -156,6 +156,8 @@ libcuda.so.1 #PACKAGE# #MINVER#
  cuMemHostRegister@Base 270
  cuMemHostRegister_v2@Base 340
  cuMemHostUnregister@Base 270
+ cuMemPrefetchAsync@Base 367
+ cuMemPrefetchAsync_ptsz@Base 367
  cuMemcpy2D@Base 169
  cuMemcpy2DAsync@Base 169
  cuMemcpy2DAsync_v2@Base 260
diff --git a/debian/libgl1-glvnd-nvidia-glx.symbols b/debian/libgl1-glvnd-nvidia-glx.symbols
index b16f37d..120848f 100644
--- a/debian/libgl1-glvnd-nvidia-glx.symbols
+++ b/debian/libgl1-glvnd-nvidia-glx.symbols
@@ -99,6 +99,7 @@
  glConvolutionParameterivEXT@Base 361
  glConvolutionParameterxOES@Base 361
  glConvolutionParameterxvOES@Base 361
+ glConservativeRasterParameterfNV@Base 352
  glCopyColorSubTableEXT@Base 361
  glCopyColorTableSGI@Base 361
  glCopyConvolutionFilter1DEXT@Base 361
@@ -143,6 +144,7 @@
  glDrawElementArrayATI@Base 361
  glDrawElementsInstancedANGLE@Base 361
  glDrawMeshArraysSUN@Base 361
+ glDrawMeshNV@Base 1.0.4349
  glDrawRangeElementArrayAPPLE@Base 361
  glDrawRangeElementArrayATI@Base 361
  glEGLImageTargetRenderbufferStorageOES@Base 361
diff --git a/debian/libgl1-nvidia-glx.symbols b/debian/libgl1-nvidia-glx.symbols
index 70df789..4bb7f91 100644
--- a/debian/libgl1-nvidia-glx.symbols
+++ b/debian/libgl1-nvidia-glx.symbols
@@ -1,8 +1,17 @@
 #include "libgl1-nvidia-glx.symbols.common"
  __glx_Main@Base 361.28
+ glConservativeRasterParameterfNV@Base 352
+ glConservativeRasterParameteriNV@Base 367
  glDebugControlNVX@Base 177
  glDevtoolsInvokeFunctorNVX@Base 349
+ glDrawVkImageNV@Base 367
+ glGetVkProcAddrNV@Base 367
+ glLogTokenFlushNVX@Base 367
  glQueryResourceNVX@Base 355
+ glSignalVkFenceNV@Base 367
+ glSignalVkSemaphoreNV@Base 367
  glViewportPositionWScaleNV@Base 361
+ glWaitVkSemaphoreNV@Base 367
  glcuR0d4nX@Base 195.36
  gldbc3cfnX@Base 325
+ vk_icdGetInstanceProcAddr@Base 367
diff --git a/debian/libgl1-nvidia-glx.symbols.common b/debian/libgl1-nvidia-glx.symbols.common
index 4bccd48..ffd5e71 100644
--- a/debian/libgl1-nvidia-glx.symbols.common
+++ b/debian/libgl1-nvidia-glx.symbols.common
@@ -265,7 +265,6 @@ libGL.so.1 libgl1-mesa-glx | libgl1
  glCompressedTextureSubImage2DEXT@Base 180
  glCompressedTextureSubImage3D@Base 346
  glCompressedTextureSubImage3DEXT@Base 180
- glConservativeRasterParameterfNV@Base 352
  glConvolutionFilter1D@Base 1.0.4349
  glConvolutionFilter2D@Base 1.0.4349
  glConvolutionParameterf@Base 1.0.4349
@@ -449,7 +448,7 @@ libGL.so.1 libgl1-mesa-glx | libgl1
  glDrawElementsInstancedBaseVertexOES@Base 349
  glDrawElementsInstancedEXT@Base 1.0.9746
  glDrawElementsInstancedNV@Base 325
- glDrawMeshNV@Base 1.0.4349
+#MISSING: 367# glDrawMeshNV@Base 1.0.4349
  glDrawPixels@Base 1.0.4349
  glDrawRangeElements@Base 1.0.4349
  glDrawRangeElementsBaseVertex@Base 190.18.05
diff --git a/debian/libglx-nvidia0.symbols b/debian/libglx-nvidia0.symbols
index c3dbc15..c465fc8 100644
--- a/debian/libglx-nvidia0.symbols
+++ b/debian/libglx-nvidia0.symbols
@@ -263,6 +263,7 @@ libGLX_nvidia.so.0 #PACKAGE# #MINVER#
  glCompressedTextureSubImage3D@Base 361.28
  glCompressedTextureSubImage3DEXT@Base 361.28
  glConservativeRasterParameterfNV@Base 361.28
+ glConservativeRasterParameteriNV@Base 367
  glConvolutionFilter1D@Base 361.28
  glConvolutionFilter2D@Base 361.28
  glConvolutionParameterf@Base 361.28
@@ -447,7 +448,7 @@ libGLX_nvidia.so.0 #PACKAGE# #MINVER#
  glDrawElementsInstancedBaseVertexOES@Base 361.28
  glDrawElementsInstancedEXT@Base 361.28
  glDrawElementsInstancedNV@Base 361.28
- glDrawMeshNV@Base 361.28
+#MISSING: 367# glDrawMeshNV@Base 361.28
  glDrawPixels@Base 361.28
  glDrawRangeElements@Base 361.28
  glDrawRangeElementsBaseVertex@Base 361.28
@@ -469,6 +470,7 @@ libGLX_nvidia.so.0 #PACKAGE# #MINVER#
  glDrawTransformFeedbackNV@Base 361.28
  glDrawTransformFeedbackStream@Base 361.28
  glDrawTransformFeedbackStreamInstanced@Base 361.28
+ glDrawVkImageNV@Base 367
  glEdgeFlag@Base 361.28
  glEdgeFlagFormatNV@Base 361.28
  glEdgeFlagPointer@Base 361.28
@@ -977,6 +979,7 @@ libGLX_nvidia.so.0 #PACKAGE# #MINVER#
  glGetVideoivNV@Base 361.28
  glGetVideoui64vNV@Base 361.28
  glGetVideouivNV@Base 361.28
+ glGetVkProcAddrNV@Base 367
  glGetnColorTable@Base 361.28
  glGetnColorTableARB@Base 361.28
  glGetnCompressedTexImage@Base 361.28
@@ -1132,6 +1135,7 @@ libGLX_nvidia.so.0 #PACKAGE# #MINVER#
  glLoadTransposeMatrixf@Base 361.28
  glLoadTransposeMatrixfARB@Base 361.28
  glLockArraysEXT@Base 361.28
+ glLogTokenFlushNVX@Base 367
  glLogicOp@Base 361.28
  glMakeBufferNonResidentNV@Base 361.28
  glMakeBufferResidentNV@Base 361.28
@@ -1822,6 +1826,8 @@ libGLX_nvidia.so.0 #PACKAGE# #MINVER#
  glShaderSource@Base 361.28
  glShaderSourceARB@Base 361.28
  

Bug#833532: Rebuild against libicu57 causes icedove to crash

[Viktor Jägersküpper]

Dear Maintainers,

I assume my problem is related to this bug. After the last upgrade from
1:45.2.0-2 to 1:45.2.0-2+b1 icedove does not start or crashes reliably.
I found the following behaviour (plugins are always disabled):

- with iceowl-extension and its german language pack enabled icedove
fails to start
- with iceowl-extension and its german language pack disabled icedove
starts, but crashes when I click on the "I'll be careful, I promise!"
button for about:config. I didn't try much more.
- in safe-mode icedove starts and I could click on the button. I didn't
try much more.

On the command line I get "Speicherzugriffsfehler" when icedove fails to
start or crashes, is this a segmentation fault?

I had no problems with version 1:45.2.0-2. So I suspect the rebuild
against libicu57 causes these problems. Note that I have not installed
the calendar-google-provider addon.

Please tell me if I can help you with more information. I am just a
user, but maybe I am able to help.

Regards
Viktor

Bug#833614: firefox: refuses to load fonts from /usr/share when viewing HTML documentation in /usr/share/doc

[Sean Whitton]

Package: firefox
Version: 48.0-1
Severity: minor
Affects: projectile-doc

Dear maintainer,

My package projectile-doc installs HTML documentation into
/usr/share/doc.  The webpages under this directory try to load
fontawesome-webfont.eot from /usr/share/fonts (via a chain of several
symlinks, traversing /usr/share/mkdocs).  Thanks to Firefox's
same-origin policy, Firefox refuses to load this font and the glyphs do
not appear.  This is not a problem for other web browsers which might be
used to look at projectile-doc's documentation.

If there is a sane way to make an exception, it would be good if the
Debian packaging of Firefox ignored the same-origin policy for pages in
/usr/share/doc trying to load external resources.  We can trust the
contents of those pages, since they come from Debian packages.  Perhaps
all of /usr/share could be considered an origin.

There is some relevant discussion in this upstream bug:


Thanks for considering this bug report.

-- Package-specific info:

-- Extensions information
Name: Classic Theme Restorer
Location: /usr/share/xul-ext/classic-theme-restorer
Package: xul-ext-classic-theme-restorer
Status: enabled

Name: Default theme
Location: 
/usr/lib/firefox/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi
Package: firefox
Status: enabled

Name: DownThemAll!
Location: ${PROFILE_EXTENSIONS}/{DDC359D1-844A-42a7-9AA1-88A850A938A8}.xpi
Status: enabled

Name: EPUBReader
Location: ${PROFILE_EXTENSIONS}/{5384767E-00D9-40E9-B72F-9CC39D655D6F}
Status: enabled

Name: Firefox Hello
Location: ${PROFILE_EXTENSIONS}/l...@mozilla.org.xpi
Status: enabled

Name: Instaread (Instapaper Bookmarklet)
Location: ${PROFILE_EXTENSIONS}/@instaread.xpi
Status: enabled

Name: It's All Text!
Location: ${PROFILE_EXTENSIONS}/itsallt...@docwhat.gerf.org
Status: enabled

Name: KeySnail
Location: ${PROFILE_EXTENSIONS}/keysn...@mooz.github.com
Status: enabled

Name: LeechBlock
Location: ${PROFILE_EXTENSIONS}/{a95d8332-e4b4-6e7f-98ac-20b733364387}
Status: user-disabled

Name: Multi-process staged rollout
Location: ${PROFILE_EXTENSIONS}/e10sroll...@mozilla.org.xpi
Status: enabled

Name: Pocket
Location: ${PROFILE_EXTENSIONS}/fire...@getpocket.com.xpi
Status: enabled

Name: Save Images
Location: ${PROFILE_EXTENSIONS}/ldsi_plash...@gmail.com.xpi
Status: enabled

Name: Self-Destructing Cookies
Location: /usr/share/xul-ext/self-destructing-cookies
Package: xul-ext-self-destructing-cookies
Status: enabled

Name: uBlock Origin
Location: /usr/share/xul-ext/ublock-origin
Package: xul-ext-ublock-origin
Status: enabled

Name: Y U no validate
Location: /usr/share/xul-ext/y-u-no-validate
Package: xul-ext-y-u-no-validate
Status: enabled

-- Plugins information
Name: IcedTea-Web Plugin (using IcedTea-Web 1.6.2 (1.6.2-3))
Location: /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/IcedTeaPlugin.so
Package: icedtea-8-plugin:i386
Status: enabled


-- Addons package information
ii  firefox  48.0-1   i386 Mozilla Firefox 
web browser
ii  icedtea-8-plugin:i3861.6.2-3  i386 web browser 
plugin based on OpenJDK and IcedTea to execute Java applets
ii  xul-ext-classic-theme-restorer   1.5.5.1-1all  customize the 
new Firefox interface
ii  xul-ext-self-destructing-cookies 0.4.10-1 all  delete cookies 
and LocalStorage after tabs using them have been closed
ii  xul-ext-ublock-origin1.8.2+dfsg-1 all  general-purpose 
lightweight ads, malware, trackers blocker
ii  xul-ext-y-u-no-validate  2013052407-2 all  browser 
extension to make security exceptions temporary by default

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

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

Versions of packages firefox depends on:
ii  debianutils   4.8
ii  fontconfig2.11.0-6.4
ii  libasound21.1.1-2
ii  libatk1.0-0   2.20.0-1
ii  libc6 2.23-4
ii  libcairo2 1.14.6-1+b1
ii  libdbus-1-3   1.10.8-1
ii  libdbus-glib-1-2  0.106-1
ii  libevent-2.0-52.0.21-stable-2+b1
ii  libffi6   3.2.1-4
ii  libfontconfig12.11.0-6.4
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:6.1.1-10
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.48.1-2
ii  libgtk2.0-0   2.24.30-4
ii  libhunspell-1.4-0 1.4.1-2
ii  libnspr4  2:4.12-2
ii  libnss3   2:3.23-2
ii  libpango-1.0-01.40.1-1
ii  libsqlite3-0  3.13.0-1
ii  libstartup-notification0  0.12-4
ii  libstdc++66.1.1-10
ii  libvpx3   1.5.0-3
ii  

Bug#833613: lintian: fails to detect embedded javascript provided in libjs-* packages

[Sean Whitton]

Package: lintian
Version: 2.5.45
Severity: normal

Dear maintainers,

Steps to reproduce:

1. debsnap projectile 0.14.0-1
2. cd source-projectile
3. dpkg-source -x projectile_0.14.0-1.dsc
4. cd projectile-0.14.0
5. sed -i 's/ --with linktree//' debian/rules
6. sbuild# unsigned .dsc
7. lintian

Expected result:

Lintian emits several embedded-javascript-library warnings.  With
dh_linktree turned off, the package installs copies of
bootstrap-3.0.3.min.js, jquery-1.10.2.min.js, lunr-0.5.7.min.js,
mustache.min.js and several others.

Actual result:

Lintian emits no such warnings.

Thanks!

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

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

Versions of packages lintian depends on:
ii  binutils  2.26.1-1
ii  bzip2 1.0.6-8
ii  diffstat  1.61-1
ii  file  1:5.28-2
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.57-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.9
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.7
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.9
ii  libhtml-parser-perl3.72-2
ii  libtext-template-perl  1.46-1

-- no debconf information

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#811718: pacman: diff for NMU version 10-17.2

[Markus Koschany]

Control: tags 811718 + patch
Control: tags 811718 + pending

Dear maintainer,

I've prepared an NMU for pacman (versioned as 10-17.2) and
uploaded it to unstable.

Please find attached the debdiff.

Regards,

Markus
diff -u pacman-10/debian/changelog pacman-10/debian/changelog
--- pacman-10/debian/changelog
+++ pacman-10/debian/changelog
@@ -1,3 +1,11 @@
+pacman (10-17.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with GCC-6. (Closes: #811718)
+  * Declare compliance with Debian Policy 3.9.8.
+
+ -- Markus Koschany   Sun, 07 Aug 2016 00:16:45 +0200
+
 pacman (10-17.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u pacman-10/debian/control pacman-10/debian/control
--- pacman-10/debian/control
+++ pacman-10/debian/control
@@ -2,7 +2,7 @@
 Section: games
 Priority: optional
 Maintainer: Joe Nahmias 
-Standards-Version: 3.9.6
+Standards-Version: 3.9.8
 Build-Depends: debhelper (>= 9), xutils-dev, libncurses5-dev, libx11-dev,
  libxext-dev
 
only in patch2:
unchanged:
--- pacman-10.orig/corner1.cc
+++ pacman-10/corner1.cc
@@ -3,6 +3,6 @@
 Corner1::Corner1() {
  
 consfn();
-pix(,corner1_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
+pix(,(char*)corner1_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
 };
 
only in patch2:
unchanged:
--- pacman-10.orig/corner2.cc
+++ pacman-10/corner2.cc
@@ -3,6 +3,6 @@
 Corner2::Corner2() {
  
 consfn();
-pix(,corner2_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
+pix(,(char*)corner2_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
 };
 
only in patch2:
unchanged:
--- pacman-10.orig/corner3.cc
+++ pacman-10/corner3.cc
@@ -3,6 +3,6 @@
 Corner3::Corner3() {
  
 consfn();
-pix(,corner3_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
+pix(,(char*)corner3_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
 };
 
only in patch2:
unchanged:
--- pacman-10.orig/corner4.cc
+++ pacman-10/corner4.cc
@@ -3,6 +3,6 @@
 Corner4::Corner4() {
  
 consfn();
-pix(,corner4_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
+pix(,(char*)corner4_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
 };
 
only in patch2:
unchanged:
--- pacman-10.orig/cross.cc
+++ pacman-10/cross.cc
@@ -3,7 +3,7 @@
 Cross::Cross() {
  
 consfn();
-pix(,cross_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
+pix(,(char*)cross_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
 
 };
 
only in patch2:
unchanged:
--- pacman-10.orig/e0.cc
+++ pacman-10/e0.cc
@@ -3,6 +3,6 @@
 E0::E0() {
  
 consfn();
-pix(,e0_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
+pix(,(char*)e0_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
 }
 
only in patch2:
unchanged:
--- pacman-10.orig/e180.cc
+++ pacman-10/e180.cc
@@ -3,6 +3,6 @@
 E180::E180() {
  
 consfn();
-pix(,e180_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
+pix(,(char*)e180_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
 }
 
only in patch2:
unchanged:
--- pacman-10.orig/e270.cc
+++ pacman-10/e270.cc
@@ -3,6 +3,6 @@
 E270::E270() {
  
 consfn();
-pix(,e270_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
+pix(,(char*)e270_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
 }
 
only in patch2:
unchanged:
--- pacman-10.orig/e90.cc
+++ pacman-10/e90.cc
@@ -3,5 +3,5 @@
 E90::E90() {
  
 consfn();
-pix(,e90_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
+pix(,(char*)e90_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
 }
only in patch2:
unchanged:
--- pacman-10.orig/gblank.cc
+++ pacman-10/gblank.cc
@@ -3,7 +3,7 @@
 G_Blank::G_Blank() {
  
 consfn();
-pix(,blank_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
+pix(,(char*)blank_bits,Colour::WALLCOLOUR,Colour::MYBACKGROUND);
 }
 
 
only in patch2:
unchanged:
--- pacman-10.orig/gbonlife.cc
+++ pacman-10/gbonlife.cc
@@ -3,7 +3,7 @@
 G_BonusLife::G_BonusLife() {
  
 consfn();
-pix(,bonuslife_bits,Colour::BONUSLIFECOLOUR,Colour::MYBACKGROUND);
+pix(,(char*)bonuslife_bits,Colour::BONUSLIFECOLOUR,Colour::MYBACKGROUND);
 
 };
 
only in patch2:
unchanged:
--- pacman-10.orig/gbonpnt.cc
+++ pacman-10/gbonpnt.cc
@@ -3,7 +3,7 @@
 G_BonusPoint::G_BonusPoint() {
  
 consfn();
-pix(,bonuspoint_bits,Colour::BONUSPOINTCOLOUR,Colour::MYBACKGROUND);
+pix(,(char*)bonuspoint_bits,Colour::BONUSPOINTCOLOUR,Colour::MYBACKGROUND);
 
 };
 
only in patch2:
unchanged:
--- pacman-10.orig/gfood.cc
+++ pacman-10/gfood.cc
@@ -3,7 +3,7 @@
 G_Food::G_Food() {
  
 consfn();
-pix(,food_bits,Colour::FOODCOLOUR,Colour::MYBACKGROUND);
+pix(,(char*)food_bits,Colour::FOODCOLOUR,Colour::MYBACKGROUND);
 
 };
 
only in patch2:
unchanged:
--- pacman-10.orig/gghost.cc
+++ pacman-10/gghost.cc
@@ -3,8 +3,8 @@
 G_Ghost::G_Ghost(COLOURTYPE farge) {
 
 consfn();
-pix(,ghost_bits,farge,Colour::MYBACKGROUND);
-pix(,ghost_bits,Colour::RUNGHOSTCOLOUR,Colour::MYBACKGROUND);
+pix(,(char*)ghost_bits,farge,Colour::MYBACKGROUND);
+pix(,(char*)ghost_bits,Colour::RUNGHOSTCOLOUR,Colour::MYBACKGROUND);
 pixmap=pixmapn;
 
 };
only in patch2:
unchanged:
--- pacman-10.orig/gpacman.cc
+++ pacman-10/gpacman.cc
@@ -4,11 +4,11 @@
 G_Pacman::G_Pacman() {
 
 

Bug#832593: apt-listbugs: Ctrl-C is not handled correctly

[Julian Andres Klode]

On Sun, Aug 07, 2016 at 12:22:47AM +0200, Francesco Poli wrote:
> Control: reassign -1 apt 1.3~pre2
> Control: affects -1 + apt-listbugs
> 
> 
> 
> On Fri, 29 Jul 2016 19:41:28 +0200 Francesco Poli wrote:
> 
> > Hence, I am suspecting that the misbehavior has something to do with
> > the way the package manager invokes its hooks...
> [...]
> > 
> > I am Cc-ing the APT Development Team: could any of you take a look at
> > bug #832593, please?
> > Any ideas on why a hook that traps SIGINT runs into troubles, when it
> > catches such signal, but does not immediately exit?
> 
> Hello again, APT Development Team.
> 
> I prepared an overly simple script that traps SIGINT, asks the user to
> press [Enter] and then goes on with its own business
> (simple-trap-sigint.sh, that should be found attached to this message).
> 
> I believe that trapping SIGINT and using this signal for something
> other than an immediate exit is a perfectly legitimate use of SIGINT.
> An already cited document [1] confirms this.

Fixed in git (but see below), and already tagged pending by the git hook.

> After pressing [Ctrl+C], the hook (simple-trap-sigint.sh) shows the
> expected "Press [Enter] to continue" message, but immediately goes
> on with its output, without waiting for input from the user.
> The final prompt is obtained after hitting [Enter]. But apt has
> already exited, instead of waiting for the hook to exit and checking
> whether the hook was killed by a SIGINT...

Well, it obviously continues directly, because APT is feeding it
package names via a pipe. But once all package names are piped
thing should work as expected.

We could also stop writing package names when interrupted, but I'm
not sure if that makes a difference: Some might be buffered already.
It's also a lot more work.

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Bug#833612: nsnake: please make the build reproducible

[Chris Lamb]

Source: nsnake
Version: 3.0.1-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

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

Patch attached.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproducible-build.patch   1970-01-01 01:00:00.0 
+0100
--- b/debian/patches/reproducible-build.patch   2016-08-06 23:48:47.355996205 
+0100
@@ -0,0 +1,18 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2016-08-06
+
+--- nsnake-3.0.1.orig/Makefile
 nsnake-3.0.1/Makefile
+@@ -39,7 +39,11 @@
+ # General Info
+ PACKAGE = nsnake
+ VERSION = 3.0.0
++ifdef SOURCE_DATE_EPOCH
++DATE= $(shell LC_ALL=C date --utc --date="@$(SOURCE_DATE_EPOCH)" "+%b%Y")
++else
+ DATE= $(shell date "+%b%Y")
++endif
+ 
+ # Install dirs
+ PREFIX  = /usr
--- a/debian/patches/series 2016-08-06 23:42:32.808924284 +0100
--- b/debian/patches/series 2016-08-06 23:48:46.227986952 +0100
@@ -1,2 +1,3 @@
 install-on-usr-games.patch
 hardening.patch
+reproducible-build.patch

Bug#811789: zvbi: diff for NMU version 0.2.35-10.1

[Eriberto Mota]

Hi Breno,

2016-07-17 21:52 GMT-03:00 Breno Leitao :
> Control: tags 811789 + patch
>
> Dear maintainer,
>
> I've prepared an NMU for zvbi (versioned as 0.2.35-10.1). The diff
> is attached to this message.


Thanks a lot for your patch. I will upload your NMU now.

Regards,

Eriberto

PS: congratulations for your "DAM approved".

Bug#830607: python-simpy: accesses the internet during build

[Andreas Tille]

Hi,

I have commited some enhancements to python-simpy (fixed lintian errors
and other stuff) but I can not reproduce the described bug.  IMHO it
should be closed - either manually or by uploading the changes in Git.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#833611: fntsample: please make the build reproducible

[Chris Lamb]

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

Hi,

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

Patch attached.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/control2016-08-06 23:30:43.895098667 +0100
--- b/debian/control2016-08-06 23:38:37.890994350 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Євгеній Мещеряков 
 Build-Depends: debhelper (>= 9~), gawk, libcairo2-dev, unicode-data, 
libglib2.0-dev,
-  pkg-config, libfreetype6-dev, libpango1.0-dev (>= 1.16), gettext, 
autotools-dev
+  pkg-config, libfreetype6-dev, libpango1.0-dev (>= 1.16), gettext, 
autotools-dev, dh-autoreconf
 Standards-Version: 3.9.6
 Vcs-Git: git://anonscm.debian.org/collab-maint/fntsample.git
 Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/fntsample.git
--- a/debian/patches/reproducible-build.patch   1970-01-01 01:00:00.0 
+0100
--- b/debian/patches/reproducible-build.patch   2016-08-06 23:34:48.621109953 
+0100
@@ -0,0 +1,19 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2016-08-06
+
+--- fntsample-4.0.orig/configure.ac
 fntsample-4.0/configure.ac
+@@ -35,7 +35,11 @@ Use --with-unicode-blocks option to spec
+ Blocks.txt file is available at Unicode site: 
http://unicode.org/Public/UNIDATA/Blocks.txt])
+ fi
+ 
+-DATE=`date +%F`
++if test -n "$SOURCE_DATE_EPOCH"; then
++  DATE=`date --utc --date="@$SOURCE_DATE_EPOCH" +%F`
++else
++  DATE=`date +%F`
++fi
+ AC_SUBST([DATE])
+ 
+ AC_CONFIG_FILES([Makefile fntsample.1 pdfoutline.1 po/Makefile.in])
--- a/debian/patches/series 1970-01-01 01:00:00.0 +0100
--- b/debian/patches/series 2016-08-06 23:34:46.333091146 +0100
@@ -0,0 +1 @@
+reproducible-build.patch
--- a/debian/rules  2016-08-06 23:30:43.895098667 +0100
--- b/debian/rules  2016-08-06 23:38:32.950953747 +0100
@@ -1,7 +1,7 @@
 #!/usr/bin/make -f
 
 %:
-   dh $@ --with autotools_dev
+   dh $@ --with autotools_dev,autoreconf
 
 override_dh_gencontrol:
dh_gencontrol -- -VBuilt-Using="`dpkg-query -f'$${source:Package} (= 
$${source:Version})' -W unicode-data`"

Bug#833610: ara: please make the build reproducible

[Chris Lamb]

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

Hi,

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

Patch attached.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/common/mkversion.sh   2016-08-06 23:30:32.763007181 +0100
--- b/common/mkversion.sh   2016-08-06 23:37:00.142190926 +0100
@@ -1,7 +1,7 @@
 #!/bin/sh
 
 VERSION=`sed -n -e '1s/^ara (\([^ ]*\)) .*$/\1/p' ../debian/changelog`
-DATE=`date +'%04Y-%02m-%02d'`
+DATE=$(date --utc --date="@${SOURCE_DATE_EPOCH:-$(date +%s)}" 
+'%04Y-%02m-%02d')
 
 rm -f version.ml
 sed -e 's/\$VERSION\$/'"$VERSION"'/g' \

Bug#832593: apt-listbugs: Ctrl-C is not handled correctly

[Francesco Poli]

Control: reassign -1 apt 1.3~pre2
Control: affects -1 + apt-listbugs



On Fri, 29 Jul 2016 19:41:28 +0200 Francesco Poli wrote:

> Hence, I am suspecting that the misbehavior has something to do with
> the way the package manager invokes its hooks...
[...]
> 
> I am Cc-ing the APT Development Team: could any of you take a look at
> bug #832593, please?
> Any ideas on why a hook that traps SIGINT runs into troubles, when it
> catches such signal, but does not immediately exit?

Hello again, APT Development Team.

I prepared an overly simple script that traps SIGINT, asks the user to
press [Enter] and then goes on with its own business
(simple-trap-sigint.sh, that should be found attached to this message).

I believe that trapping SIGINT and using this signal for something
other than an immediate exit is a perfectly legitimate use of SIGINT.
An already cited document [1] confirms this.

[1] https://www.cons.org/cracauer/sigint.html

When this script is called by a trivial script executed by bash
(calling-script.sh, also attached), everything works as expected, since
GNU bash implements the WCE approach (explained in [1]):

  $ ./calling-script.sh 
  Start
  Hello!
  Output 1
  Output 2
  Output 3
  ^CPress [Enter] to continue
  Output 4
  Output 5
  Output 6
  Output 7
  Output 8
  Output 9
  Output 10
  Bye!
  End

Of course, the last part of the output (from "Output 4" onwards) is
shown after hitting [Enter], as requested.

On the other hand, when the script is executed by APT as a hook, things
go wrong somehow:

  # cat /etc/apt/apt.conf.d/05test 
  DPkg::Pre-Install-Pkgs {"/root/simple-trap-sigint.sh";};
  # apt install locales
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libc-l10n
  The following NEW packages will be installed:
libc-l10n locales
  0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/4198 kB of archives.
  After this operation, 17.1 MB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Hello!
  Output 1
  Output 2
  Output 3
  Output 4
  ^CPress [Enter] to continueOutput 5
  
  # Output 6
  Output 7
  Output 8
  Output 9
  Output 10
  Bye!
  
  #

After pressing [Ctrl+C], the hook (simple-trap-sigint.sh) shows the
expected "Press [Enter] to continue" message, but immediately goes
on with its output, without waiting for input from the user.
The final prompt is obtained after hitting [Enter]. But apt has
already exited, instead of waiting for the hook to exit and checking
whether the hook was killed by a SIGINT...

What's wrong? Does libapt implement the IUE approach (explained in [1])?
If this is the case, then I think that the WCE approach should be
implemented instead, at least when executing hooks, since some hooks
may use SIGINT for purposes other than an immediate exit.

I am consequently reassigning this bug report to apt/1.3~pre2 ...
Please fix this issue.

Thanks for your time.
Bye.

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


simple-trap-sigint.sh.gz
Description: application/gzip


calling-script.sh.gz
Description: application/gzip


pgpRb_ez1sNY2.pgp
Description: PGP signature

Bug#828103: needrestart: false positive: pulseaudio: orcexec files in /run

[Thomas Liske]

tags 828103 upstream fixed-upstream
thanks


Hi Paul,

On Sat, Jun 25, 2016 at 07:36:22AM +0200, Paul Wise wrote:
> There is a false positive with pulseaudio and files in /run:
> 
> needrestart output:
> # needrestart -v
> ...
> [main] #1976 uses deleted /run/user/1000/orcexec.nXwDNz

although there was already a detection of Oil Runtime Compiler's JIT
files it did not work for deleted files (due to the suffix '
(deleted)' in /proc/$$/maps). I've extended the regex accordingly.


Thanks & HTH,
Thomas

--

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

Bug#833607: nmu: python-mapnik_1:0.0~20160726-1c4a51d-1~exp1 & node-mapnik_3.5.13+dfsg-1~exp1

[Sebastiaan Couwenberg]

Hi Adam,

On 08/07/2016 12:04 AM, Adam D. Barratt wrote:
> On Sat, 2016-08-06 at 23:47 +0200, Bas Couwenberg wrote:
>> Please binNMU python-mapnik & node-mapnik in experimental, they need to
>> be rebuild with libmapnik-dev (3.0.12~rc1+ds-1~exp2) which depends on
>> the correct libmapbox-variant-dev (from experimental not unstable).
>>
>> dep-wait was already set for these packages by the wanna-build team, but
>> that was not sufficient for the architectures where the build had
>> already failed.
> 
> One can't binNMU a package on an architecture where it hasn't built;
> that's rather by definition - a binNMU is a rebuild of the existing
> binary package.
> 
> You want give-backs, which are handled on the wanna-build side. I've
> actioned them this time - and added the dep-waits on those architectures
> - but please use the correct address in future.

Thanks for this.

The wanna-build documentation on release.d.o [0] mentions "If you are
asking for a dep-wait, an additional give-back is not needed", which
seems to be incorrect based on your reply.

Is the documentation outdated perhaps?

[0] https://release.debian.org/wanna-build.txt

Kind Regards,

Bas

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

Bug#833570: fontconfig: diff for NMU version 2.11.0-6.5

[Keith Packard]

Salvatore Bonaccorso  writes:

> Control: tags 833570 + pending
>
> Hi Keith,
>
> I've prepared an NMU for fontconfig (versioned as 2.11.0-6.5) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.

Looks like that patch is already in fontconfig 2.12.1; thanks for
backporting. I don't see any reason to delay this any more than that,
I'd be comfortable with having it move into unstable immediately.

-- 
-keith


signature.asc
Description: PGP signature

Bug#833570: fontconfig: diff for NMU version 2.11.0-6.5

[Keith Packard]

Salvatore Bonaccorso  writes:

> Control: tags 833570 + pending
>
> Hi Keith,
>
> I've prepared an NMU for fontconfig (versioned as 2.11.0-6.5) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.

Also, thanks for doing this upload!
-- 
-keith


signature.asc
Description: PGP signature

Bug#833603: src:strip-nondeterminism: Please provide a process to remove unused handlers over time

[Chris Lamb]

> [..]

Just to expound a bit more:

Whilst I really like hacking on strip-nondeterminsm I feel it might
hold back the Reproducible Builds effort in general by hiding the full
impact of issues.

Its certainly not a Debian-specific tool per se but I feel like it could
be fairly labelled as such in an informal context ("Debian run this tool",
etc.) which isn't excellent marketing for widespread adoption.

It also mean that any distribution that (for whatever reason) cannot use
it will be exposed to a whole bunch of issues that we are not working on
because they are "fixed" by strip-nondeterminism.


Regards,

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

Bug#833609: ring: Crashes on startup after showing popup - triggered by missing dring?

[Petter Reinholdtsen]

Package: ring
Version: 20160729.2.7a7dbd6~dfsg1-1

When running gnome-ring in testing right now, the client pop up a error
message with strange content and crashes (sorry for the norwegian error
message):

  % LANGUAGE= LC_ALL=C DISPLAY=:0 gnome-ring
  ** Message: Ring GNOME client version: 1.0.0
  ** Message: git ref: unknown
  "Error : dring is not available, make sure it is running"

  ** (gnome-ring:3414): WARNING **: Error : dring is not available, make sure 
it is running
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

  ** (gnome-ring:3414): ERROR **: 
  Sporings-/stoppunkts-felle
  %

Valgrind report several issues:

==3636== Memcheck, a memory error detector
==3636== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==3636== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info
==3636== Command: gnome-ring
==3636== 
** Message: Ring GNOME client version: 1.0.0
** Message: git ref: unknown
==3642== Warning: invalid file descriptor 1024 in syscall close()
==3642== Warning: invalid file descriptor 1025 in syscall close()
==3642== Warning: invalid file descriptor 1026 in syscall close()
==3642== Warning: invalid file descriptor 1027 in syscall close()
==3642==Use --log-fd= to select an alternative log fd.
==3642== Warning: invalid file descriptor 1028 in syscall close()
==3642== Warning: invalid file descriptor 1029 in syscall close()
==3642== Warning: invalid file descriptor 1030 in syscall close()
"Error : dring is not available, make sure it is running"
==3636== Invalid read of size 1
==3636==at 0xF171410: vfprintf (vfprintf.c:1632)
==3636==by 0xF220044: __vasprintf_chk (vasprintf_chk.c:66)
==3636==by 0x7326CE8: vasprintf (stdio2.h:210)
==3636==by 0x7326CE8: g_vasprintf (gprintf.c:316)
==3636==by 0x730167C: g_strdup_vprintf (gstrfuncs.c:514)
==3636==by 0x72E9821: g_logv (gmessages.c:987)
==3636==by 0x72E9BDE: g_log (gmessages.c:1119)
==3636==by 0x12D97D: init_exception_dialog(char const*) 
(ring_client.cpp:131)
==3636==by 0x12F78A: ring_client_startup(_GApplication*) 
(ring_client.cpp:443)
==3636==by 0x70561D3: _g_closure_invoke_va (gclosure.c:867)
==3636==by 0x70709A5: g_signal_emit_valist (gsignal.c:3294)
==3636==by 0x707108E: g_signal_emit (gsignal.c:3441)
==3636==by 0x6D6B0B1: g_application_register (gapplication.c:2049)
==3636==  Address 0x205e8d68 is 24 bytes inside a block of size 80 free'd
==3636==at 0x4C2CDFB: free (vg_replace_malloc.c:530)
==3636==by 0x505EED1: 
Interfaces::DBusErrorHandlerDefault::invalidInterfaceError(QString const&) 
(dbuserrorhandlerdefault.cpp:33)
==3636==by 0x505C605: VideoManager::instance() (videomanager.cpp:42)
==3636==by 0x506A1BE: VideoRendererManager::VideoRendererManager() 
(videorenderermanager.cpp:84)
==3636==by 0x506A394: VideoRendererManager::instance() 
(videorenderermanager.cpp:98)
==3636==by 0x4F8AF02: CallModel::CallModel() (callmodel.cpp:155)
==3636==by 0x4F9204C: CallModel::instance() (callmodel.cpp:132)
==3636==by 0x12ED18: ring_client_startup(_GApplication*) 
(ring_client.cpp:441)
==3636==by 0x70561D3: _g_closure_invoke_va (gclosure.c:867)
==3636==by 0x70709A5: g_signal_emit_valist (gsignal.c:3294)
==3636==by 0x707108E: g_signal_emit (gsignal.c:3441)
==3636==by 0x6D6B0B1: g_application_register (gapplication.c:2049)
==3636==  Block was alloc'd at
==3636==at 0x4C2BBCF: malloc (vg_replace_malloc.c:299)
==3636==by 0x7658AA1: QArrayData::allocate(unsigned long, unsigned long, 
unsigned long, QFlags) (in 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.6.1)
==3636==by 0x765B2AF: QByteArray::QByteArray(int, Qt::Initialization) (in 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.6.1)
==3636==by 0x76E8744: QString::toLatin1_helper(QChar const*, int) (in 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.6.1)
==3636==by 0x76E878F: QString::toLatin1_helper(QString const&) (in 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.6.1)
==3636==by 0x505EEBC: toLatin1 (qstring.h:509)
==3636==by 0x505EEBC: 
Interfaces::DBusErrorHandlerDefault::invalidInterfaceError(QString const&) 
(dbuserrorhandlerdefault.cpp:33)
==3636==by 0x505C605: VideoManager::instance() (videomanager.cpp:42)
==3636==by 0x506A1BE: VideoRendererManager::VideoRendererManager() 
(videorenderermanager.cpp:84)
==3636==by 0x506A394: VideoRendererManager::instance() 
(videorenderermanager.cpp:98)
==3636==by 0x4F8AF02: CallModel::CallModel() (callmodel.cpp:155)
==3636==by 0x4F9204C: CallModel::instance() (callmodel.cpp:132)
==3636==by 0x12ED18: ring_client_startup(_GApplication*) 
(ring_client.cpp:441)
==3636== 
==3636== Invalid read of size 1
==3636==at 0x4C32EE0: __GI_mempcpy (vg_replace_strmem.c:1518)
==3636==by 0xF19B66D: _IO_default_xsputn (genops.c:438)
==3636==by 0xF170C5A: vfprintf (vfprintf.c:1632)
==3636==by 0xF220044: __vasprintf_chk (vasprintf_chk.c:66)
==3636==by 0x7326CE8: 

Bug#826220: needrestart: Allow usage of different config file when run from APT

[Thomas Liske]

tags 826220 upstream fixed-upstream
thanks

Hi Wolfgang,

On Fri, Jun 03, 2016 at 02:12:17PM +0200, Wolfgang Karall-Ahlborn wrote:
> It would be nice to be able to set a different config for APT, so the
> interactive call of needrestart is could be plain 'needrestart' again.

I've changed call of needrestart with-in apt-pinvoke to pass
arguments. This allows you to adjust the config file
/etc/apt/apt.conf.d/99needrestart to pass a configuration file option
to needrestart.


HTH,
Thomas


> Cheers
> Wolfgang
> 
> -- Package-specific info:
> needrestart output:
> Your outdated processes:
> ApacheDirectory[9304], at-spi-bus-laun[2309], at-spi2-registr[2346], 
> bash[2241, 2245, 2104, 2116, 2246, 2108, 2243, 2110], chromium[3537, 3545, 
> 3587, 3576], dane-plug[3958],
>  dbus-daemon[2340, 1846], dbus-launch[1845], dconf-service[19859], 
> dnssec-plug[3843], gconfd-2[3638], gkrellm[2055], gvfsd[1952], 
> gvfsd-metadata[20750], gvfsd-trash[19829],
>  gvfs-udisks2-vo[19817], mosh-client[8020], panel-13-systra[1983], 
> panel-16-action[1984], sh[1809], systemd[1796], Thunar[1881], 
> thunderbird[9255], tpb[1854],
>  wicd-client[2092], xfce4-panel[1883], xfce4-session[1871], 
> xfce4-volumed[2100], xfconfd[1875], xfdesktop[1982], xfrun4[9247], 
> xfsettingsd[1888], xfwm4[1879],
>  xscreensaver[2097], xterm[2060, 2061, 2058, 2057, 2063, 2056, 2059, 2062], 
> x-www-browser[3634]
> 
> checkrestart output:
> 
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: i386 (i686)
> 
> Kernel: Linux 4.5.0-2-686-pae (SMP w/4 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> Init: sysvinit (via /sbin/init)
> 
> Versions of packages needrestart depends on:
> ii  dpkg   1.18.7
> ii  gettext-base   0.19.7-2
> ii  libintl-perl   1.24-1
> ii  libmodule-find-perl0.13-1
> ii  libmodule-scandeps-perl1.21-1
> ii  libproc-processtable-perl  0.53-1+b1
> ii  libsort-naturally-perl 1.03-1
> ii  libterm-readkey-perl   2.33-1+b1
> ii  perl   5.22.2-1
> ii  xz-utils   5.1.1alpha+20120614-2.1
> 
> needrestart recommends no packages.
> 
> Versions of packages needrestart suggests:
> ii  libnotify-bin  0.7.6-2
> 
> -- no debconf information
> 
--

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

Bug#833561: arm64: dtbs no longer installed in vendor subdir

[Martin Michlmayr]

* Ian Campbell  [2016-08-06 11:38]:
> But indeed in https://packages.debian.org/experimental/arm64/linux-imag
> e-4.7.0-rc7-arm64-unsigned/filelist the subdirectory is missing.

linux-image-4.7.0-rc3-arm64-unsigned from snapshot has the problem too.

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

Bug#833608: lintian: version-substvar-for-external-package, but external package is versioned provides

[Julian Andres Klode]

Package: lintian
Version: 2.5.45
Severity: normal

In trying to simplify the APT build system, I changed the library package
libapt-pkg5.0 and libapt-inst2.0 to provide a versionless-name:

  Package: libapt-pkg5.0
  Provides: libapt-pkg (= ${binary:Version})

So I can depend on it like this:

  Package: libapt-pkg-dev
  Depends: libapt-pkg (= ${binary:Version})

This however leads to a version-substvar-for-external-package error
from lintian, as it does not understand that the package name is a
versioned provides.

We previously had a substvar that ${libapt-pkg-name}, but I wanted
to get rid of substvars as far as possible, as that involves non-declarative
stuff in rules.

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

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

Versions of packages lintian depends on:
ii  binutils  2.26.1-1
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.58-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
pn  libperlio-gzip-perl  
ii  perl 5.22.2-3
ii  perl-modules-5.22 [libautodie-perl]  5.22.2-3

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

-- Configuration Files:
/etc/lintianrc changed [not included]

-- no debconf information

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Bug#833597: [l10n] Updated Czech translation of debian-edu-config debconf messages

[Holger Levsen]

control: tags -1 pending

Hi Miroslav,

On Sat, Aug 06, 2016 at 06:32:02PM +0200, Miroslav Kure wrote:
> in attachement there is updated Czech (cs.po) translation of 
> debian-edu-config debconf messages. Please include it with the
> package.

thanks, committed to git, branch master. :-)


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#833607: nmu: python-mapnik_1:0.0~20160726-1c4a51d-1~exp1 & node-mapnik_3.5.13+dfsg-1~exp1

[Bas Couwenberg]

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

Please binNMU python-mapnik & node-mapnik in experimental, they need to
be rebuild with libmapnik-dev (3.0.12~rc1+ds-1~exp2) which depends on
the correct libmapbox-variant-dev (from experimental not unstable).

dep-wait was already set for these packages by the wanna-build team, but
that was not sufficient for the architectures where the build had
already failed.

nmu python-mapnik_1:0.0~20160726-1c4a51d-1~exp1 . arm64 i386 powerpc ppc64el . 
experimental . -m "Rebuild with libmapnik-dev (3.0.12~rc1+ds-1~exp2)"
nmu node-mapnik_3.5.13+dfsg-1~exp1 . arm64 i386 powerpc ppc64el . experimental 
. -m "Rebuild with libmapnik-dev (3.0.12~rc1+ds-1~exp2)"

Kind Regards,

Bas

Bug#833603: src:strip-nondeterminism: Please provide a process to remove unused handlers over time

[Chris Lamb]

> One way we could do this would be to log that we applied $handler
> on $filename then that could be parsed by external tools.

It could be enabled with an environment variable pointing to a
filename, which we would enable on Jenkins. We could then parse
and add the results to our database for display/stats.


Regards,

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

Bug#832166: please don't restart lxcfs by default

[Thomas Liske]

tags 832166 fixed-upstream
thanks


Hi,

On Sat, Jul 23, 2016 at 08:33:36AM +0200, Evgeni Golov wrote:
> needrestart currently will try to restart lxcfs if that got upgraded, however 
> restarting it would result in all containers using it hanging, so please 
> don't :)

I've added an override for lxcfs to the shipped configuration so it is
not selected by default.


HTH,
Thomas

> Greets
> Evgeni
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.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)
> 
--

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

Bug#831840: needrestart: false positive: restart due to grsec Linux kernel variant installed

[Thomas Liske]

severity 831840 minor
tags 831840 wontfix upstream
thanks

Hi Paul,

On Wed, Jul 20, 2016 at 12:52:16PM +0800, Paul Wise wrote:
> I have linux-image-4.6.0-1-amd64 and linux-image-4.6.0-1-grsec-amd64
> installed and am running linux-image-4.6.0-1-amd64 because various
> services fail under linux-image-4.6.0-1-grsec-amd64. Every time I run
> needrestart I get a notice to reboot even though the Linux kernel
> variant I am running has not been upgraded. Please change the code to
> take into account the possibility of alternate kernel variants.
> On Debian amd64 there are currently two kernel variants: rt grsec

I have no idea howto reliable detect different variants of linux
images. Looking for non-numeric or well known parts in the version
string is fragile.


Regards,
Thomas


> Scanning linux images...
> Pending kernel upgrade!
> 
> Running kernel version:
>   4.6.0-1-amd64
> 
> Diagnostics:
>   The currently running kernel version is not the expected kernel version 
> 4.6.0-1-grsec-amd64.
> 
> Restarting the system to load the new kernel will not be handled 
> automatically, so you should consider rebooting. [Return]
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing-debug
>   APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
> 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
> 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages needrestart depends on:
> ii  dpkg   1.18.9
> ii  gettext-base   0.19.8.1-1
> ii  libintl-perl   1.24-1
> ii  libmodule-find-perl0.13-1
> ii  libmodule-scandeps-perl1.21-1
> ii  libproc-processtable-perl  0.53-1+b1
> ii  libsort-naturally-perl 1.03-1
> ii  libterm-readkey-perl   2.33-1+b1
> ii  perl   5.22.2-2
> ii  xz-utils   5.1.1alpha+20120614-2.1
> 
> needrestart recommends no packages.
> 
> Versions of packages needrestart suggests:
> ii  libnotify-bin0.7.6-2
> ii  needrestart-session  0.3-2
> 
> -- no debconf information
> 
> -- 
> bye,
> pabs
> 
> https://wiki.debian.org/PaulWise


--

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

Bug#827352: jessie-pu: package automake-1.14/1.14.1-4+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Wed, 2016-06-15 at 11:12 +0200, Petter Reinholdtsen wrote:
> On my Debian Jessie machine, I would like to fix a security problem with
> automake-1.14 that show up the debsecan report, see
>  https://security-tracker.debian.org/tracker/source-package/automake-1.14 >.
> The issue never got a CVE (no reply to the request), so I point to the
> source package entry instead of the some times changing TEMP reference.
> 
> The issue is fixed in automake-1.15, but not in automake-1.14 that is in
> stable but removed from unstable.
> 
> The issue is unsafe use of /tmp/.  The patch is similar to the code in
> version 1.15.
> 
> OK to upload?

Assuming that the resulting package has been tested on stable, please go
ahead, except:

+automake-1.14 (1:1.14.1-4+deb8u1) unstable; urgency=medium

That distribution is a little wrong. :-p "jessie", please.

Regards,

Adam

Bug#833550: jessie-pu: package gnome-maps/3.14.1.2-1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Fri, 2016-08-05 at 23:14 +0200, Emilio Pozuelo Monfort wrote:
> gnome-maps is currently unusable in Jessie. It used the MapQuest provider,
> which has closed access to external applications[1].
> 
> This is already fixed in unstable, see #830842.
> 
> For Jessie, I have updated to the new point release. Excluding the autotools
> changes in the debdiff (which are autogenerated anyway through dh_autoreconf),
> the only changes are a few translation updates, and the changes for this fix
> (which are the changes in src/, plus the mapbox logo), as can also be seen
> in [2].

fwiw, this didn't make it to debian-release, probably due to the size of
the debdiff; you might want to compress larger ones in future.

> I could backport these changes instead, but given that the new release is
> basically this fix, I thought it would be fine.

 const MapType = {
-STREET:  Champlain.MAP_SOURCE_OSM_MAPQUEST,
-AERIAL:  Champlain.MAP_SOURCE_OSM_AERIAL_MAP,
-CYCLING: Champlain.MAP_SOURCE_OSM_CYCLE_MAP,
-TRANSIT: Champlain.MAP_SOURCE_OSM_TRANSPORT_MAP
+STREET: 'MapsStreetSource',
+AERIAL: 'MapsAerialSource'
 };

I assume this means that the change also ends up dropping
functionality? :-(

Please go ahead.

Regards,

Adam

Bug#833606: E: flAbsPath on ./var/lib/dpkg/status failed - realpath (2: No such file or directory)

[Anthony]

Package: browser-plugin-freshplayer-pepperflash
Version: 0.3.5-1
Severity: important

Dear Maintainer,

   * What led up to the situation?
I did 'sudo apt install --reinstall pepperflashplugin-nonfree browser-plugin-
freshplayer-pepperflash'

   * What was the outcome of this action?
Get:1 http://http.us.debian.org/debian sid/contrib amd64 pepperflashplugin-
nonfree amd64 1.8.2+nmu1 [10.9 kB]
Fetched 10.9 kB in 0s (71.4 kB/s)
(Reading database ... 325163 files and directories currently installed.)
Preparing to unpack .../pepperflashplugin-nonfree_1.8.2+nmu1_amd64.deb ...
Unpacking pepperflashplugin-nonfree (1.8.2+nmu1) over (1.8.2+nmu1) ...
Preparing to unpack .../browser-plugin-freshplayer-
pepperflash_0.3.5-1_amd64.deb ...
Unpacking browser-plugin-freshplayer-pepperflash (0.3.5-1) over (0.3.5-1) ...
Setting up browser-plugin-freshplayer-pepperflash (0.3.5-1) ...
Setting up pepperflashplugin-nonfree (1.8.2+nmu1) ...
ERROR: failed to retrieve status information from google : E: flAbsPath on
./var/lib/dpkg/status failed - realpath (2: No such file or directory)
E: Could not open file  - open (2: No such file or directory)
E: Problem opening
E: The package lists or status file could not be parsed or opened.
More information might be available at:
  http://wiki.debian.org/PepperFlashPlayer



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

Kernel: Linux 4.5-5.dmz.1-liquorix-amd64 (SMP w/8 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 browser-plugin-freshplayer-pepperflash depends on:
ii  libasound21.1.2-1
ii  libavcodec57  7:3.1.1-4
ii  libavutil55   7:3.1.1-4
ii  libc6 2.23-4
ii  libcairo2 1.14.6-1+b1
ii  libevent-2.0-52.0.21-stable-2+b1
ii  libevent-pthreads-2.0-5   2.0.21-stable-2+b1
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:6.1.1-11
ii  libgl1-mesa-glx [libgl1]  11.2.2-1
ii  libglib2.0-0  2.48.1-2
ii  libgtk2.0-0   2.24.30-4
ii  libpango-1.0-01.40.1-1
ii  libpangocairo-1.0-0   1.40.1-1
ii  libpangoft2-1.0-0 1.40.1-1
ii  libpulse0 9.0-1.1
ii  libssl1.0.2   1.0.2h-1
ii  libstdc++66.1.1-11
ii  libv4l-0  1.10.1-1
ii  libva-x11-1   1.7.1-2
ii  libva11.7.1-2
ii  libvdpau1 1.1.1-3
ii  libx11-6  2:1.6.3-1
ii  libxcursor1   1:1.1.14-1+b1
ii  libxrandr22:1.5.0-1
ii  libxrender1   1:0.9.9-2

Versions of packages browser-plugin-freshplayer-pepperflash recommends:
ii  pepperflashplugin-nonfree  1.8.2+nmu1

browser-plugin-freshplayer-pepperflash suggests no packages.

-- no debconf information

Bug#833605: monkeysign --no-mail is not encrypted

[Nicholas D Steeves]

Package: monkeysign
Version: 2.0.2
Severity: important

Hi Antoine,

When Alexandre Viau and I met up for keysigning, I did not have an mta
configured on my laptop, so I used monkeysign --no-mail, and pasted the output
into a webmail interface.  The situation could have been avoided if I had used
an MUA such as Mutt which would have detected that I was capable of encrypting
the email to the receiver.

The current behaviour is that monkeysign outputs something like the following,
which is not encrypted to the receiver:

Content-Type: multipart/mixed;
boundary="===23452345234757845773574757862=="
MIME-Version: 1.0

--===567676757658477222==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable


Please find attached your signed OpenPGP key. You can import the
signed key by running each through `gpg --import`.

If you have multiple user ids, each signature was sent in a separate
email to each user id.

Note that your key was not uploaded to any keyservers. If you want
this new signature to be available to others, please upload it
yourself.  With GnuPG this can be done using:

gpg --keyserver pool.sks-keyservers.net --send-key 

Regards,

--===9780435690834575340984537098347==
Content-Type: application/pgp-keys;
 name="signed-9898I9OINEGR0GR098JOAEWO23RNR4NOIEFIF09RJRG.asc"
MIME-Version: 1.0
Content-Disposition: attachment;
 filename="signed-9AWRG9G5E98GERGWNGERGR098GRE04TW04TMGH.asc"
Content-Transfer-Encoding: 7bit
Content-Description: signed OpenPGP Key
 asdfsadfsdfFFasdfsdfasdf0EasdfA3A,
 uid Someone you met 

-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v1

SIGNED KEY BLOCK

-END PGP PUBLIC KEY BLOCK-

--===9876243958724689747247==--

Thanks,
Nicholas



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

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

Versions of packages monkeysign depends on:
ii  gnupg 1.4.18-7+deb8u1
ii  gnupg-agent   2.0.26-6
ii  python2.7.9-1
ii  python-pkg-resources  20.10.1-1.1~bpo8+1

Versions of packages monkeysign recommends:
ii  python-gtk2   2.24.0-4
ii  python-qrencode   1.01-4
ii  python-zbar   0.10+doc-10
ii  python-zbarpygtk  0.10+doc-10

monkeysign suggests no packages.

-- no debconf information

Bug#833575: jessie-pu: package javatools/0.48+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sat, 2016-08-06 at 11:02 +0200, Julien Cristau wrote:
> collectd on security.d.o fails to build on ppc64el, apparently because
> java changed its paths there and javatools needs an update.

Please go ahead.

Regards,

Adam

Bug#833604: qingy: No systemd service file

[Joonas Kylmälä]

Package: qingy
Version: 0.9.7-2+b1
Severity: normal

Dear Maintainer,

I wanted to replace getty with qingy but I couldn't find any systemd
service files provided for running qingy when the system starts.
Systemd service file
/etc/systemd/system/getty.target.wants/getty@tty1.service is provided
for getty so maybe something similar could be done for qingy? Or is
there some other way that users could easily replace getty with qingy
on Debian system that uses systemd?

Thanks,
Joonas

-- 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)

Versions of packages qingy depends on:
ii  dpkg   1.18.10
ii  install-info   6.1.0.dfsg.1-8
ii  libc6  2.23-4
ii  libdirectfb-1.2-9  1.2.10.0-5.2+b1
ii  libdirectfb-extra  1.2.10.0-5.2+b1
ii  libncurses56.0+20160625-1
ii  libpam0g   1.1.8-3.3
ii  libtinfo5  6.0+20160625-1
ii  libx11-6   2:1.6.3-1
ii  libxss11:1.2.2-1

qingy recommends no packages.

qingy suggests no packages.

-- no debconf information

Bug#831335: jessie-pu: package publicsuffix/20160703-1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Fri, 2016-07-15 at 00:25 +0200, Daniel Kahn Gillmor wrote:
> On Thu 2016-07-14 20:06:27 +0200, Adam D. Barratt wrote:
> > Please could we have a debdiff, relative to the current package in
> > jessie, in this bug log? (We prefer p-u bugs to be self-contained, and
> > not have to rely on your git tree existing for arbitrary periods in the
> > future, or on it not changing after we give an ack.)
> 
> sure.  the debdiff is quite large, primarily due to upstream renaming
> effective_tld_names.dat to public_suffix_list.dat (and adding a
> python-based "linter", and changing how they produce their upstream
> changelog), but i've attached the gzip'ed debdiff below.

Thanks; please feel free to upload that, with a small tweak:

+publicsuffix (20160703-0+deb8u1) stable; urgency=medium
+
+  * prepare for stable-proposed-updates.

"jessie" is generally preferred as the changelog distribution and maybe
"Upload to stable" or something similar?

> The git tree's jessie branch which i'm proposing is at commit ID
> 6520ee81d3e2d73192e67685652ef6bccdb2e637, fwiw, so you don't have to
> worry about it changing.

Thanks for that, but we'd still prefer p-u bug reports to be
free-standing.

[...]
> I expect the packaging should be able to remain basically as-is for
> jessie's lifetime, since we're basically just shipping a static global
> file.

That's good to know.

> > How frequently would you imagine that the package would need to be
> > updated in stable?
> 
> Upstream makes several additions to the psl per month, but the new
> editions are rarely super-urgent.  I'd imagine doing a "roll-up" release
> of changes every month or two to more accurately track the state of
> global DNS administrative boundaries.

Every couple of months is when we aim (not always successfully) to do a
stable point release, so that hopefully works out well all around.

Regards,

Adam

Bug#723763: monkeysign should not sign revoked uids

[Nicholas D Steeves]

Control: found -1 monkeysign/2.0.2

Hi Antoine,

I think by default Monkeysign still signs revoked keys and sends
emails to addresses that might no longer be active.  I just ran a
monkeysign 7B75921E, and I think you have received a signed key for a
few of your revoked ones.

Cheers,
Nicholas

Bug#833603: src:strip-nondeterminism: Please provide a process to remove unused handlers over time

[Chris Lamb]

Source: strip-nondeterminism
Version: 0.022-1
Severity: wishlist

Hi,

As we fix various issues in packages and toolchains, the number of
handlers in strip-nondetermism should eventually (!) drop to zero. 

I think we can speed this up by getting some visibility on which
handlers are actually being used and pro-actively removing them
when they drop below a certain level.

One way we could do this would be to log that we applied $handler
on $filename then that could be parsed by external tools.

If it then appears more sensible to fix each package individually
(ie. due to a low number of packages requiring it) or to attack the
root cause of the problem (eg. some kind of toolchain fix), we can
eventually remove the handler.


Regards,

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

Bug#809022: [debian-mysql] Bug#809022: autopkgtest patch for MariaDB

[Paul Gevers]

Ouch...

On 06-08-16 22:38, Paul Gevers wrote:
> It would be interesting
> to know why the server of MySQL pulls in everything required and the
  ^^ = mysql-testsuite-5.6 package

> MariaDB server does not. Isn't this somewhat unexpected (and may point
  ^^ = mariadb-test package

> at a packaging issue)? Please comment.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#809022: [debian-mysql] Bug#809022: autopkgtest patch for MariaDB

[Paul Gevers]

Hi Otto,

On 03-08-16 15:38, Otto Kekäläinen wrote:
> Unfortunately it seems that this ci test fails in Debian production CI
> systems: https://ci.debian.net/packages/m/mariadb-10.0/unstable/amd64/
> 
> Can you help here? Should the test have libmariadbclient18 installed
> before it runs?

On first glance it indeed looks like libmariadbclient18 is needed to fix
two of the three failures. Or maybe libmariadb2. It would be interesting
to know why the server of MySQL pulls in everything required and the
MariaDB server does not. Isn't this somewhat unexpected (and may point
at a packaging issue)? Please comment. Also why do you think it is the
client lib that is needed and not the server lib?

The fix for the last failure is trivial, just update
mysql-test/r/information_schema_stats.result after you verified that the
new result is indeed the proper order (two lines are reversed in order).

Paul



signature.asc
Description: OpenPGP digital signature

Bug#833602: dolfin: please enable parallel building

[Aurelien Jarno]

Source: dolfin
Version: 2016.1.0-1
Severity: wishlist

Dear Maintainer,

dolfin takes a significant time to build even on fast architectures. It
appears it only use a single CPU during the build, while all build
daemons have multiple CPUs.

Therefore please enable parallel building. Given the package uses dh and
cmake, it should only be a matter of adding "--parallel" to the dh $@
call.

Thanks,
Aurelien

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

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

Bug#828779: Info received (Illegal instruction: me too)

[Joey Hess]

Unsurprisingly, building the package from source got a working program.

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#833601: kde-telepathy: add kaccounts-providers to recommended packages

[HJ]

Package: kde-telepathy
Version: 15.08.3
Severity: wishlist

Dear Maintainer,

kaccounts is needed to support more protocols(eg: Hangouts)


-- System Information:
Distributor ID: Devuan
Description:Devuan GNU/Linux unstable (ceres)
Release:unstable
Codename:   ceres
Architecture: x86_64

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

Versions of packages kde-telepathy depends on:
ii  kde-telepathy-desktop-applets   15.08.3-1
ii  kde-telepathy-filetransfer-handler  15.08.3-1
ii  kde-telepathy-minimal   15.08.3
ii  kde-telepathy-send-file 15.08.3-1
ii  plasma-runner-telepathy-contact 15.08.3-1

kde-telepathy recommends no packages.

kde-telepathy suggests no packages.

-- no debconf information

Bug#833600: nsntrace: Please package a new upstream snapshot

[Chris Lamb]

> Let me think about it, I'll let you know if I plan to step back.

No problem, was just throwing it out there. I'd also love a
backport to jessie-backports, although that can wait for another
day.. :)

Enjoy your Saturday evening.


Regards,

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

Bug#833395: emacspeak: please make the build reproducible

[Chris Lamb]

> I seeded with a slightly more random number.

:)
 
> Why the seed in one file and not in the other?

IIRC, I believe the "seed " isn't actually needed as pinkish has its
own seed. Apologies for the, err, noise.


Regards,

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

Bug#833600: nsntrace: Please package a new upstream snapshot

[GCS]

Hi Chris,

On Sat, Aug 6, 2016 at 9:29 PM, Chris Lamb  wrote:
> I've been working with upstream in fixing a bunch of issues which
> have now been merged:
[...]
> Please could you package another snapshot?
 I've seen your commits and while I've no connection with its
upstream, many thanks for those!

> (Alternatively, I could take over as maintainer of this package? I
> plan to use it extensively..)
 I've also plan of daily use, that's why I've packaged it. I'm
watching over it and trying to be quick with it even on Saturday
evenings. Let me think about it, I'll let you know if I plan to step
back.

Thanks again,
Laszlo/GCS

Bug#833395: emacspeak: please make the build reproducible

[Paul Gevers]

On 06-08-16 22:12, Chris Lamb wrote:
>> What a shame I already had the patch since Debconf. I just haven't had
>> the time to upload the fix.
> 
> Not to worry. :)  Does your solution differ greatly?

Not much... although I only have the fix for sounds/3d/src/scroll.csd
locally.

So, syntax "," looks different and I used an additional argument. I
seeded with a slightly more random number.

Why the seed in one file and not in the other?

paul@ruapehu ~/a11y/emacspeak $ git diff
diff --git a/sounds/3d/src/scroll.csd b/sounds/3d/src/scroll.csd
index f926ce6..930c5f4 100644
--- a/sounds/3d/src/scroll.csd
+++ b/sounds/3d/src/scroll.csd
@@ -13,8 +13,8 @@ kaz1  linseg -90, p3, 90
 kaz2   linseg 45, p3, 225
 kenv linseg 0.5, p3, 0.1
 ; generate pink noise
-an1  pinkish 1
-an2  pinkish  0.25
+an1  pinkish 1, 0, 20, 179
+an2  pinkish  0.25, 0, 20, 179
 al1, ar1 hrtfmove2 an1, kaz1, -40,
"hrtf-44100-left.dat","hrtf-44100-right.dat"
 al2, ar2 hrtfmove2 an2, kaz2, 40,
"hrtf-44100-left.dat","hrtf-44100-right.dat"
 ; write audio out

Paul



signature.asc
Description: OpenPGP digital signature

Bug#833395: emacspeak: please make the build reproducible

[Paul Gevers]

Control: tags -1 pending

On 03-08-16 22:08, Chris Lamb wrote:
> Patch attached.

What a shame I already had the patch since Debconf. I just haven't had
the time to upload the fix.

Paul




signature.asc
Description: OpenPGP digital signature

Bug#833187: RFS: yuma123/2.8-1 [ITP] -- netconf/YANG toolchain

[Vincent Bernat]

control: owner -1 !

 ❦  2 août 2016 00:25 CEST, Vladimir Vassilev  :

> libyuma-base - Netconf configuration script, YANG models and documentation
> libyuma-dev - Netconf/YANG development files
> libyuma2   - Netconf/YANG library
> libyuma2-dbg - Netconf/YANG library debug
> netconfd   - netconf (RFC-6241) agent
> netconfd-module-ietf-interfaces - SIL module for netconfd implementing 
> ietf-interfaces.yang
> netconfd-module-ietf-system - SIL module for netconfd implementing 
> ietf-system.yang
> yangcli- netconf/YANG command line client application

 - d/watch: missing, please add one. It allows you (or me) to
   conveniently know if there is a new version available. This appears
   on various tools like tracker.debian.org or qa.debian.org.

 - d/control: no need to Build-Depends on autotools-dev, dh-autoreconf
   already does everything.

 - d/control: the latest Standards-Version is 3.9.8.

 - d/control: the Homepage should be the homepage of the software, not
   the homepage of the company backing it.

 - d/control: there is an extra dot at the end of the long description
   of libyuma-base

 - d/control: drop the libyuma2-dbg package, they are now generated
   automatically.

 - d/control: no need to depends on libc6-dev for libyuma-dev, this
   package is part of build-essentials.

 - d/control: you can drop the versioned dependency on lsb-base as the
   requested version is available even in oldstable (and the package it
   self is priority required)

 - d/control: libyuma2 dependency should come directly from
   ${shlibs:Depends}, isn't it?

 - d/copyright: the file uses almost DEP-5 format except the header is
   missing and the licenses are not formatted correctly (missing space
   column and dot between paragraphs). See:
   http://dep.debian.net/deps/dep5/#header-paragraph

 - d/copyright: add a section for debian/* using the most prominent
   license and with yourself as copyright holder.

 - d/copyright: there are some missing files and copyright holders, like
   "Netconf Central", "Bob Trower/Trantor Standard Systems"... rgrep -i
   copyright to find them.

 - d/patches: I don't think that the patch is useful. If it's just here
   to not have a debian directory elsewhere in the tree, it's not
   needed.

 - d/rules: only use autoreconf, let dh_strip generate dbgsym package
   itself

 - add a lintian override for (with a comment explaining the three
   libraries share the same source and API/ABI versioning and don't need
   3 different packages):
 libyuma2: package-name-doesnt-match-sonames libyumaagt2 libyumamgr2 
libyumancx2

 - you may want to add a libyuma2.symbols file. It can be generated with
   dpkg-gensymbols (and modified manually to remove the debian part of
   the version number).

How should netconfd be running? I see that netconf-subsystem should be
configured inside OpenSSH. What about netconfd? Is it spawned by
netconf-subsystem?

Some files are generated. They are marked with "Generated by
yangdump". This means you'll have to build them during build. If this is
already possible in the default build system, just ensure they are
removed before build by adding them to debian/clean.

The MIB files are not free material and you need to strip them from the
original tarball. To do that, the easiest way is to add them to
debian/copyright. This is explained in the manual page of uscan (you
need the debian/watch file to work correctly). You'll need to add +dfsg
extension to the version: 2.8+dfsg for the upstream version, 2.8+dfsg-1
for the Debian version. If some of the files above are generated from
the MIB, this is quite annoying as I don't have a solution for this.

I see that the .yang files are copyright IETF/Internet Society. I have
looked to a few of them and they use a "simplified BSD license". I don't
know if this is the 1-clause or 2-clause one. You should add the
appropriate section in debian/copyright. Some other files are generated
From the MIB. You cannot use them, sorry. There may be some debate here
as MIB are used as an interface documentation. However, they are really
non-free material. Maybe bringing this to debian-legal@ may help.

Except the RFC stuff, most problems are rather small and the package
looks good!
-- 
Debian package sponsoring guidelines:
 https://vincent.bernat.im/en/debian-package-sponsoring.html


signature.asc
Description: PGP signature

Bug#833395: emacspeak: please make the build reproducible

[Chris Lamb]

> What a shame I already had the patch since Debconf. I just haven't had
> the time to upload the fix.

Not to worry. :)  Does your solution differ greatly?


Regards,

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

Bug#828779: Illegal instruction: me too

[Joey Hess]

Package: libargon2-0
Version: 0~20160406-2
Severity: normal

Both the command line program argon2 and the library fail with SIGILL on
my laptop.

processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 69
model name  : Intel(R) Core(TM) i5-4210Y CPU @ 1.50GHz
stepping: 1
microcode   : 0x14
cpu MHz : 1507.148
cache size  : 3072 KB
physical id : 0
siblings: 4
core id : 0
cpu cores   : 2
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 
ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm epb tpr_shadow vnmi 
flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid 
xsaveopt dtherm ida arat pln pts
bugs:
bogomips: 2992.96
clflush size: 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

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

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

Versions of packages libargon2-0 depends on:
ii  libc6  2.23-4

libargon2-0 recommends no packages.

libargon2-0 suggests no packages.

-- no debconf information

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#833570: fontconfig: diff for NMU version 2.11.0-6.5

[Salvatore Bonaccorso]

Control: tags 833570 + pending

Hi Keith,

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

Regards,
Salvatore
diff -Nru fontconfig-2.11.0/debian/changelog fontconfig-2.11.0/debian/changelog
--- fontconfig-2.11.0/debian/changelog	2016-03-12 19:01:15.0 +0100
+++ fontconfig-2.11.0/debian/changelog	2016-08-06 10:24:50.0 +0200
@@ -1,3 +1,11 @@
+fontconfig (2.11.0-6.5) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * CVE-2016-5384: Possible double free due to insufficiently validated cache
+files (Closes: #833570)
+
+ -- Salvatore Bonaccorso   Sat, 06 Aug 2016 10:24:50 +0200
+
 fontconfig (2.11.0-6.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru fontconfig-2.11.0/debian/patches/07_CVE-2016-5384-Properly-validate-offsets-in-cache-files.patch fontconfig-2.11.0/debian/patches/07_CVE-2016-5384-Properly-validate-offsets-in-cache-files.patch
--- fontconfig-2.11.0/debian/patches/07_CVE-2016-5384-Properly-validate-offsets-in-cache-files.patch	1970-01-01 01:00:00.0 +0100
+++ fontconfig-2.11.0/debian/patches/07_CVE-2016-5384-Properly-validate-offsets-in-cache-files.patch	2016-08-06 10:24:50.0 +0200
@@ -0,0 +1,160 @@
+From 7a4a5bd7897d216f0794ca9dbce0a4a5c9d14940 Mon Sep 17 00:00:00 2001
+From: Tobias Stoeckmann 
+Date: Sat, 25 Jun 2016 19:18:53 +0200
+Subject: [PATCH] Properly validate offsets in cache files.
+
+The cache files are insufficiently validated. Even though the magic
+number at the beginning of the file as well as time stamps are checked,
+it is not verified if contained offsets are in legal ranges or are
+even pointers.
+
+The lack of validation allows an attacker to trigger arbitrary free()
+calls, which in turn allows double free attacks and therefore arbitrary
+code execution. Due to the conversion from offsets into pointers through
+macros, this even allows to circumvent ASLR protections.
+
+This attack vector allows privilege escalation when used with setuid
+binaries like fbterm. A user can create ~/.fonts or any other
+system-defined user-private font directory, run fc-cache and adjust
+cache files in ~/.cache/fontconfig. The execution of setuid binaries will
+scan these files and therefore are prone to attacks.
+
+If it's not about code execution, an endless loop can be created by
+letting linked lists become circular linked lists.
+
+This patch verifies that:
+
+- The file is not larger than the maximum addressable space, which
+  basically only affects 32 bit systems. This allows out of boundary
+  access into unallocated memory.
+- Offsets are always positive or zero
+- Offsets do not point outside file boundaries
+- No pointers are allowed in cache files, every "pointer or offset"
+  field must be an offset or NULL
+- Iterating linked lists must not take longer than the amount of elements
+  specified. A violation of this rule can break a possible endless loop.
+
+If one or more of these points are violated, the cache is recreated.
+This is current behaviour.
+
+Even though this patch fixes many issues, the use of mmap() shall be
+forbidden in setuid binaries. It is impossible to guarantee with these
+checks that a malicious user does not change cache files after
+verification. This should be handled in a different patch.
+
+Signed-off-by: Tobias Stoeckmann 
+---
+ src/fccache.c | 81 ++-
+ 1 file changed, 80 insertions(+), 1 deletion(-)
+
+--- a/src/fccache.c
 b/src/fccache.c
+@@ -27,6 +27,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+ #if defined(HAVE_MMAP) || defined(__CYGWIN__)
+@@ -544,6 +545,82 @@ FcCacheTimeValid (FcCache *cache, struct
+ return cache->checksum == (int) dir_stat->st_mtime;
+ }
+ 
++static FcBool
++FcCacheOffsetsValid (FcCache *cache)
++{
++char		*base = (char *)cache;
++char		*end = base + cache->size;
++intptr_t		*dirs;
++FcFontSet		*fs;
++int			 i, j;
++
++if (cache->dir < 0 || cache->dir > cache->size - sizeof (intptr_t) ||
++memchr (base + cache->dir, '\0', cache->size - cache->dir) == NULL)
++return FcFalse;
++
++if (cache->dirs < 0 || cache->dirs >= cache->size ||
++cache->dirs_count < 0 ||
++cache->dirs_count > (cache->size - cache->dirs) / sizeof (intptr_t))
++return FcFalse;
++
++dirs = FcCacheDirs (cache);
++if (dirs)
++{
++for (i = 0; i < cache->dirs_count; i++)
++{
++FcChar8	*dir;
++
++if (dirs[i] < 0 ||
++dirs[i] > end - (char *) dirs - sizeof (intptr_t))
++return FcFalse;
++
++dir = FcOffsetToPtr (dirs, dirs[i], FcChar8);
++if (memchr (dir, '\0', end - (char *) dir) == NULL)
++return FcFalse;
++ }
++}
++
++if (cache->set < 0 || 

Bug#833580: pcscada fails to build with ld --as-needed as the default

[Reto Buerki]

Hi Matthias

Thanks for the report.

On 08/06/2016 12:12 PM, Matthias Klose wrote:
>
> gnatbind-6 -shared -E -x /«PKGBUILDDIR»/obj/utests/runner.ali
> gnatlink-6 /«PKGBUILDDIR»/obj/utests/runner.ali -shared-libgcc -lpcsclite -R
> /«PKGBUILDDIR»/lib/static/libpcscada.a -L/usr/lib/ -lahven -o
> /«PKGBUILDDIR»/obj/utests/runner
> /«PKGBUILDDIR»/lib/static/libpcscada.a(pcsc-scard.o): In function
> `pcsc__scard__get_return_code':
> /«PKGBUILDDIR»/src/pcsc-scard.adb:402: undefined reference to 
> `pcsc_stringify_error'
> /«PKGBUILDDIR»/lib/static/libpcscada.a(pcsc-scard.o): In function
> `pcsc__scard__is_valid':
> /«PKGBUILDDIR»/src/pcsc-scard.adb:473: undefined reference to 
> `SCardIsValidContext'
> 
> Here is a workaround
> http://launchpadlibrarian.net/277411681/pcscada_0.7.3-1_0.7.3-1ubuntu1.diff.gz
> 
> however you really should pass '-lpcsclite' behind libpcscada.a.  Isn't there
> anything which allows you to pass this as LIBS, not LDFLAGS?

Does the attached patch work for you?

Kind regards
- reto

>From 1ec12f52a0ef36f1dca6a20009c2691e2c468683 Mon Sep 17 00:00:00 2001
From: Reto Buerki 
Date: Sat, 6 Aug 2016 21:24:44 +0200
Subject: [PATCH] Pass external libs as Linker_Options in test project

This fixes build errors on Ubuntu as it has -Wl,--as-needed enabled by
default and somehow gnatmake does not get the ordering right when using
Linker.Default_Switches.
---
 pcscada_utests.gpr | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pcscada_utests.gpr b/pcscada_utests.gpr
index d111386..20c695f 100644
--- a/pcscada_utests.gpr
+++ b/pcscada_utests.gpr
@@ -37,7 +37,7 @@ project PCSCAda_UTests is
end Compiler;
 
package Linker is
-  for Default_Switches ("ada") use PCSCAda_Common.Linker_Switches;
+  for Linker_Options use PCSCAda_Common.Linker_Switches;
end Linker;
 
package Binder is
-- 
2.1.4

Bug#809611: d-i fails to boot on HP mv2120

[Martin Michlmayr]

Hi Mike,

* Mike Thompson  [2016-08-05 20:23]:
> The good news is that given the load address change from 0x40 to
> 0x60 allowed the MV2120 to boot into the ssh based installer.

Great!

> The bad news is the installed failed from what looked like some sort of
> segmentation faults in the installer from the looks of the logs which I
> included below.

I wonder if this is the same as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833599

Can you please test this image:
http://ftp.nl.debian.org/debian/dists/testing/main/installer-armel/current/images/orion5x/network-console/hp/mv2120/netboot.img

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

Bug#820434: About #820434

[Stephen Kitt]

Control: tag -1 + patch

Hi Peter,

On Mon, 11 Jul 2016 10:59:39 +0200, Stephen Kitt  wrote:
> Le 07/07/2016 21:55, Peter Spiess-Knafl a écrit :
> > According to
> > https://www.debian.org/doc/debian-policy/ch-sharedlibs.html I
> > probably have to create a file under debian/shlibs containing the
> > following line:
> > 
> > libjsoncpp 1
> > 
> > Would that be enough?  
> 
> That should be enough, but it would perhaps be better to add a symbols
> file instead; if you're using cdbs or dh, you can add an empty
> libjsoncppsymbols file (using the correct soname for libjsoncpp),
> and the next build will fail but show you what needs to be added to the
> symbols file.

The attached symbols file should do the trick. (I've included symbols for
1.6.5 and 1.7.2.) Simply save it in the debian directory of the libjsoncpp
source package, it will be picked up during the build. In the future, if the
symbols change the build will fail and produce a diff for you to apply to the
symbols file.

Regards,

Stephen


libjsoncpp1.symbols
Description: Binary data


pgpELWdeDxUje.pgp
Description: OpenPGP digital signature

Bug#833600: nsntrace: Please package a new upstream snapshot

[Chris Lamb]

Package: nsntrace
Version: 0~20160722-1
Severity: wishlist

Hi,

I've been working with upstream in fixing a bunch of issues which
have now been merged:

 https://github.com/jonasdn/nsntrace/pull/10 (!)
 https://github.com/jonasdn/nsntrace/pull/11
 https://github.com/jonasdn/nsntrace/pull/12
 https://github.com/jonasdn/nsntrace/pull/13
 https://github.com/jonasdn/nsntrace/pull/14
 https://github.com/jonasdn/nsntrace/pull/15

Please could you package another snapshot?

(Alternatively, I could take over as maintainer of this package? I
plan to use it extensively..)


Regards,

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

Bug#740068: debian-installer: segfaults when built against testing

[Witold Baryluk]

Package: debian-installer
Followup-For: Bug #740068

I do have same problem when suing today's (and last few days)
netboot/mini.iso amd64 images. I was going crazy it is something with my
machine memory, but normal memtest86+ is passing, including sequential
tests on all cores. The memtest86+ parallel test fails always on 4th
core, but I found it fails on few other machines, so this must be a bug
in memtest86+ probably.

Anyway, It returns a segfault, usually during preparing libc6, but it
sometimes happens at a different times. After that, the progress bar is
stuck, and essentially every command in the shell fails. Maybe the libc6
was already unpacked and it affects all programs, or it is a kernel bug.

Regards,
Witek

Bug#833599: debian-installer: choose-mirror segfaults

[Witold Baryluk]

Package: debian-installer
Severity: grave
Tags: d-i
Justification: renders package unusable

Hi.

When using todays (and few previous days) netboot/mini.iso amd64
snapshot, I am consistently getting segfault when executing "Choose
mirror to install from (menu item)" during expert install.

in the dmesg:

segfault at 0 ip 4017c0 sp  error 4 in 
choose-mirror[400+6000]

I do not think this is related to libc6 issues reported in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740068

I had no issues with debian 8.5.0 netboot iso.

Regards,
Witold

Bug#833591: [iceowl-extension] Segmentation fault

[Carsten Schoenert]

Hello Thomas,

On Sat, Aug 06, 2016 at 08:27:11PM +0200, Thomas Florek wrote:
 
> ... am not sure, if I did it right, but enclosed find the gdb logfile
> 
> I will give more detailed info, if needed and I would be able ;)

the log looks good so far, but I can't see a segfault message. So the
log is mostly useless for us, unfortunately.

[SNIP
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from /usr/lib/icedove/icedove-bin...Reading symbols from 
> /usr/lib/debug//usr/lib/icedove/icedove-bin...done.
> done.
> (gdb) handle SIGPIPE nostop
> SignalStopPrint   Pass to program Description
> SIGPIPE   No  Yes Yes Broken pipe
> (gdb) handle SIG38 nostop
> SignalStopPrint   Pass to program Description
> SIG38 No  Yes Yes Real-time event 38
> (gdb) run

...

> Thread 1 "icedove-bin" received signal SIG38, Real-time event 38.

Icedove created a SIG38 signal here, nothing relevant.

From here down there are "just" messages about various threads Icedove
was starting and closing.

... 
> Thread 1 "icedove-bin" received signal SIG38, Real-time event 38.
> [Thread 0x7fffd9bff700 (LWP 5139) exited]
> [New Thread 0x7fffd9bff700 (LWP 5165)]
> [New Thread 0x7fffbb8ff700 (LWP 5168)]
> [Thread 0x7fffbb8ff700 (LWP 5168) exited]
> [Thread 0x7fffd9bff700 (LWP 5165) exited]
> [New Thread 0x7fffbb8ff700 (LWP 5170)]
> [New Thread 0x7fffd9bff700 (LWP 5171)]
> [New Thread 0x7fffbaefb700 (LWP 5172)]
> [New Thread 0x7fffba6fa700 (LWP 5173)]
> [New Thread 0x7fffb9ef9700 (LWP 5174)]

Why Icedove is here exiting normaly? Do you have closed the application
here?

> [Inferior 1 (process 5114) exited normally]
> (gdb) exir t
> Undefined command: "exit".  Try "help".
> (gdb) quit

You closed gdb to early here so you don't see any information about the
threads that was running. You need here to call 'thread apply all bt' to
see this information.
But only if Icedove was segfaulting, otherwise we (you) don't see
anything that's useful to solve the problem.

Regards
Carsten

Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A

[Santiago Vila]

On Sat, Aug 06, 2016 at 08:49:24PM +0200, Kurt Roeckx wrote:
> Version: 2.4.6-1
> 
> On Sat, Aug 06, 2016 at 07:11:50PM +0200, Santiago Vila wrote:
> > On Sat, Aug 06, 2016 at 05:57:20PM +0200, Kurt Roeckx wrote:
> > 
> > > 2.4.6-0.1 builds fine for me using -A.
> > 
> > Please provide a build log for any of your successful
> > "dpkg-buildpackage -A" builds of libtool 2.4.6-0.1 in stretch.
> 
> That was stupid of me.  Not wanting to wait for the test suite, it
> takes a long time, I skipped the test suite.  And of course the
> problem you reported was that that test suite gave errors.
> 
> So I could reproduce it with 2.4.6-0.1 but not with 2.4.6-1.

Finally. Thank you.

Bug#833598: /usr/share/doc/libio-stringy-perl/html/index.html is a broken symlink

[Jakub Wilk]

Package: libio-stringy-perl
Version: 2.111-1
User: debian...@lists.debian.org
Usertags: adequate broken-symlink

$ dpkg -L libio-stringy-perl | xargs -n1 file | grep broken
/usr/share/doc/libio-stringy-perl/html/index.html: broken symbolic link to 
Stringy.pm.html


This bug was found using adequate:
https://packages.debian.org/unstable/main/adequate


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

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

Versions of packages libio-stringy-perl depends on:
ii  perl  5.22.2-3

--
Jakub Wilk

Bug#833591: [iceowl-extension] Segmentation fault

[Thomas Florek]

Hello Carsten,

>>> I hope that tomorrow can post debugging results.
>> 
>> Yes please, I can't reproduce this issue right now.

... am not sure, if I did it right, but enclosed find the gdb logfile

I will give more detailed info, if needed and I would be able ;)

Regards
Tom
MOZILLA_FIVE_HOME=/usr/lib/icedove
  LD_LIBRARY_PATH=/usr/lib/icedove:/usr/lib/icedove/plugins:/usr/lib/icedove
DISPLAY=:0
DYLD_LIBRARY_PATH=/usr/lib/icedove:/usr/lib/icedove
 LIBRARY_PATH=
   SHLIB_PATH=/usr/lib/icedove:/usr/lib/icedove
  LIBPATH=/usr/lib/icedove:/usr/lib/icedove
   ADDON_PATH=
  MOZ_PROGRAM=/usr/lib/icedove/icedove-bin
  MOZ_TOOLKIT=
moz_debug=1
 moz_debugger=
moz_debugger_args=
/usr/bin/gdb  --args /usr/lib/icedove/icedove-bin --safe-mode
GNU gdb (Debian 7.11.1-2) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/icedove/icedove-bin...Reading symbols from /usr/lib/debug//usr/lib/icedove/icedove-bin...done.
done.
(gdb) handle SIGPIPE nostop
SignalStop	Print	Pass to program	Description
SIGPIPE   No	Yes	Yes		Broken pipe
(gdb) handle SIG38 nostop
SignalStop	Print	Pass to program	Description
SIG38 No	Yes	Yes		Real-time event 38
(gdb) run
Starting program: /usr/lib/icedove/icedove-bin --safe-mode
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe5ccf700 (LWP 5120)]
[Thread 0x7fffe5ccf700 (LWP 5120) exited]
[New Thread 0x7fffe5ccf700 (LWP 5122)]
[New Thread 0x7fffe3cff700 (LWP 5123)]
[New Thread 0x77fee700 (LWP 5124)]
[New Thread 0x7fffe34fe700 (LWP 5125)]
[New Thread 0x7fffe29ff700 (LWP 5126)]
[New Thread 0x7fffe27fe700 (LWP 5127)]
[New Thread 0x7fffe25fd700 (LWP 5128)]
[New Thread 0x7fffe23fc700 (LWP 5129)]
[New Thread 0x7fffe21fb700 (LWP 5130)]
[New Thread 0x7fffe1ffa700 (LWP 5131)]
[New Thread 0x7fffe0cff700 (LWP 5132)]
[New Thread 0x7fffe01ff700 (LWP 5133)]
[New Thread 0x7fffdf9fe700 (LWP 5134)]
[New Thread 0x7fffe4f60700 (LWP 5135)]
[New Thread 0x7fffde9ff700 (LWP 5136)]
[New Thread 0x7fffdd669700 (LWP 5137)]
[New Thread 0x7fffdce68700 (LWP 5138)]
[New Thread 0x7fffd9bff700 (LWP 5139)]

Thread 1 "icedove-bin" received signal SIG38, Real-time event 38.
[New Thread 0x7fffd7dff700 (LWP 5140)]
[New Thread 0x7fffd75fe700 (LWP 5141)]
[New Thread 0x7fffd6dfd700 (LWP 5142)]
[New Thread 0x7fffd65fc700 (LWP 5143)]
[New Thread 0x7fffd5dfb700 (LWP 5144)]
[New Thread 0x7fffd55fa700 (LWP 5145)]
[New Thread 0x7fffd4aff700 (LWP 5146)]
[New Thread 0x7fffd42fe700 (LWP 5147)]
[New Thread 0x7fffd38ff700 (LWP 5148)]

(icedove:5114): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[New Thread 0x7fffd2eff700 (LWP 5150)]
[New Thread 0x7fffd26fe700 (LWP 5151)]
[Thread 0x7fffd26fe700 (LWP 5151) exited]
[Thread 0x7fffd2eff700 (LWP 5150) exited]
[New Thread 0x7fffd2eff700 (LWP 5152)]
[New Thread 0x7fffd26fe700 (LWP 5153)]
[New Thread 0x7fffc3af2700 (LWP 5154)]
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
[New Thread 0x7fffbc735700 (LWP 5157)]
klauncher(5162) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
startkdeinitlock(5114) KMimeTypePrivate::ensureXmlDataLoaded: Got name "application/vnd.ms-excel.addin.macroEnabled.12" in file "application/vnd.ms-excel.addin.macroenabled.12.xml" expected "application/vnd.ms-excel.addin.macroenabled.12" 
startkdeinitlock(5114) KMimeTypePrivate::ensureXmlDataLoaded: Got name "application/vnd.ms-excel.sheet.binary.macroEnabled.12" in file "application/vnd.ms-excel.sheet.binary.macroenabled.12.xml" expected "application/vnd.ms-excel.sheet.binary.macroenabled.12" 
startkdeinitlock(5114) KMimeTypePrivate::ensureXmlDataLoaded: Got name "application/vnd.ms-excel.sheet.macroEnabled.12" in file "application/vnd.ms-excel.sheet.macroenabled.12.xml" expected "application/vnd.ms-excel.sheet.macroenabled.12" 
startkdeinitlock(5114) KMimeTypePrivate::ensureXmlDataLoaded: Got name "application/vnd.ms-excel.template.macroEnabled.12" in 

Bug#833597: [l10n] Updated Czech translation of debian-edu-config debconf messages

[Miroslav Kure]

Package: debian-edu-config
Severity: wishlist
Tags: l10n, patch

Hi,

in attachement there is updated Czech (cs.po) translation of 
debian-edu-config debconf messages. Please include it with the
package.

Thank you
-- 
Miroslav Kure
# Czech translation of debian-edu-config debconf messages.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the debian-edu-config 
package.
# Miroslav Kure , 2006, 2016.
#
msgid ""
msgstr ""
"Project-Id-Version: debian-edu-config\n"
"Report-Msgid-Bugs-To: debian-edu-con...@packages.debian.org\n"
"POT-Creation-Date: 2013-05-22 15:09+0200\n"
"PO-Revision-Date: 2016-08-06 18:30+0200\n"
"Last-Translator: Miroslav Kure \n"
"Language-Team: Czech \n"
"Language: cs\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../debian-edu-config.templates:1001
msgid "Should the init.d/update-hostname script run at boot time?"
msgstr "Má se během zavádění systému spustit skript init.d/update-hostname?"

#. Type: boolean
#. Description
#: ../debian-edu-config.templates:2001
msgid "Do you want to run enable-nat on your system?"
msgstr "Chcete na svém systému spouštět enable-nat?"

#. Type: boolean
#. Description
#: ../debian-edu-config.templates:2001
msgid ""
"The enable-nat script activates NAT for your Thin-Clients and overwrites "
"your iptables rules."
msgstr ""
"Skript enable-nat na tenkých klientech aktivuje NAT (překlad síťových adres) "
"a přepíše vaše pravidla iptables."

#. Type: password
#. Description
#: ../debian-edu-config.templates:4001
msgid "Enter the Kerberos KDC master key:"
msgstr "Zadejte hlavní klíč pro Kerberos KDC:"

#. Type: password
#. Description
#: ../debian-edu-config.templates:4001
msgid ""
"A password is needed as Kerberos master key and for all default principals.  "
"You can use your root password or type something else. Make sure you "
"remember the password."
msgstr ""
"Zadané heslo se použije jako hlavní klíč pro Kerberos a pro všechny výchozí "
"principály. Můžete použít heslo uživatele root, nebo si vymyslet něco "
"jiného. Důležité je, abyste si heslo zapamatovali."

#. Type: password
#. Description
#. Type: password
#. Description
#: ../debian-edu-config.templates:4001 ../debian-edu-config.templates:9001
msgid "Note that you will not be able to see the password as you type it."
msgstr "Při zadávání se heslo nebude zobrazovat."

#. Type: password
#. Description
#. Type: password
#. Description
#: ../debian-edu-config.templates:5001 ../debian-edu-config.templates:10001
msgid "Re-enter password to verify:"
msgstr "Znovu zadejte heslo pro ověření:"

#. Type: password
#. Description
#. Type: password
#. Description
#: ../debian-edu-config.templates:5001 ../debian-edu-config.templates:10001
msgid ""
"Please enter the same password again to verify that you have typed it "
"correctly."
msgstr "Zadejte heslo ještě jednou pro ověření, že jste ho napsali správně."

#. Type: error
#. Description
#. Type: error
#. Description
#: ../debian-edu-config.templates:6001 ../debian-edu-config.templates:11001
msgid "Password input error"
msgstr "Chyba při zadávání hesla"

#. Type: error
#. Description
#. Type: error
#. Description
#: ../debian-edu-config.templates:6001 ../debian-edu-config.templates:11001
msgid "The two passwords you entered were not the same. Please try again."
msgstr "Zadaná hesla jsou různá. Zkuste to prosím znovu."

#. Type: error
#. Description
#. Type: error
#. Description
#: ../debian-edu-config.templates:7001 ../debian-edu-config.templates:12001
msgid "Empty password"
msgstr "Prázdné heslo"

#. Type: error
#. Description
#. Type: error
#. Description
#: ../debian-edu-config.templates:7001 ../debian-edu-config.templates:12001
msgid ""
"You entered an empty password, which is not allowed. Please choose a non-"
"empty password."
msgstr ""
"Zadali jste prázdné heslo, což není dovoleno. Zadejte prosím neprázdné "
"heslo."

#. Type: password
#. Description
#: ../debian-edu-config.templates:9001
msgid "Enter the LDAP super-admin password:"
msgstr "Zadejte heslo pro správce LDAP:"

#. Type: password
#. Description
#: ../debian-edu-config.templates:9001
msgid ""
"A password is used as initial password for the super-admin user of GOsa². "
"You can use your root password or type something else. Make sure you "
"remember the password."
msgstr ""
"Zadané heslo se použije jako počáteční heslo pro správce GOsa². "
"Můžete použít heslo uživatele root, nebo si vymyslet něco jiného. "
"Důležité je, abyste si heslo zapamatovali."

Bug#833179: [Pkg-openldap-devel] Bug#833179: openldap: please make the build reproducible (username, hostname, buildpath)

[Ryan Tandy]

Control: tag -1 pending

Hello,

On Mon, Aug 01, 2016 at 06:51:08PM +, Daniel Shahaf wrote:

While working on the “reproducible builds” effort [1], we have noticed
that openldap could not be built reproducibly [2].

The attached patch removes variable information from the build.


Thank you for working on making Debian reproducible, and for submitting 
this patch. Unfortunately it doesn't seem to work exactly as intended, 
probably because mkversion is not invoked from the root of the build 
tree.


For now I committed an alternate patch just setting WHOWHERE to a static 
string, which should make the build reproducible as desired. The rest 
can be revisited later.


thanks,
Ryan

Bug#833596: systemd user service {gpg-agent,dirmngr} breaks GNOME session startup

[Stefano Zacchiroli]

Package: gnupg
Version: 2.1.14-3

Forwarding from debian-devel
https://lists.debian.org/debian-devel/2016/08/msg00093.html , as
requested by dkg.

- Forwarded message from Stefano Zacchiroli  -

Date: Sat, 6 Aug 2016 12:32:39 +0200
From: Stefano Zacchiroli 
To: debian-de...@lists.debian.org
Subject: Re: [pkg-gnupg-maint] Beware of leftover gpg-agent processes
Message-ID: <20160806103239.ga12...@upsilon.cc>
Resent-From: debian-de...@lists.debian.org

[ quoted text reordered ]

On Fri, Aug 05, 2016 at 02:43:30PM -0400, Daniel Kahn Gillmor wrote:
> The simplest way to see the control group hierarchy is with "systemctl
> status".  When these processes are launched by the user service, they'll
> end up in the user@.service like this:
[...]
> If they've been autolaunched, they'll end up in the sesion-X.scope
> sub-tree.

It was indeed the case for me: they had been auto-launched.

> > On Fri, Aug 05, 2016 at 12:41:18PM -0400, Daniel Kahn Gillmor wrote:
> >> On desktop systems (where i'd expect the majority of secret key access
> >> happens), for folks who are running systemd, i recommend enabling the
> >> systemd user services, as documented in
> >> /usr/share/doc/{gnupg-agent,dirmngr}/README.Debian :
> >> 
> >>   systemctl --user enable gpg-agent
> >>   systemctl --user enable dirmngr

OTOH, doing this inhibited a proper start of my GNOME session at next
login: only Nautilus started (I can tell because I've it handle my
desktop icons) and I could use it to browse the filesystem, but GNOME
Shell didn't see to be running.  Reverting the above with "disable" [*]
fixed the issue, and at next login GNOME session started properly,
including GNOME Shell.

I haven't yet filed this as a bug report, because my package mix is
kinda unusual at present: Debian testing + hand-picked gpg from
experimental. But it might be useful for you to know about this. Let me
know how I can debug it further and/or if you'd like to move this
discussion into a dedicated bug report (and when).

Cheers.

[*] actually, I manually removed the symlinks from
.config/systemd/user/default.target.wants/, but AFAICT the effect is
the same
-- 
Stefano Zacchiroli  . . . . . . .  z...@upsilon.cc . . . . o . . . o . o
Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o
Former Debian Project Leader . . . . . @zacchiro . . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »

Bug#833595: jessie-pu: package nullmailer/1.13-1+deb8u1

[Christian Hofstaedtler]

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

Dear Release Team,

#831813 is an rc-bug in nullmailer, which, for some configurations,
keeps username/passwords in the debconf db. I've fixed this in
unstable as an NMU; Security has suggested doing the same for jessie
in a point release.

Debdiff attached.

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

diff -Nru nullmailer-1.13/debian/changelog nullmailer-1.13/debian/changelog
--- nullmailer-1.13/debian/changelog2014-08-08 00:19:32.0 +
+++ nullmailer-1.13/debian/changelog2016-08-06 17:38:32.0 +
@@ -1,3 +1,12 @@
+nullmailer (1:1.13-1+deb8u1) jessie; urgency=medium
+
+  * Non-maintainer upload.
+  * Do not keep relayhost data in debconf database longer than
+strictly needed. (Closes: #831813)
+Backport of 1:1.13-1.2 from unstable.
+
+ -- Christian Hofstaedtler   Sat, 06 Aug 2016 17:36:35 +
+
 nullmailer (1:1.13-1) unstable; urgency=low
 
   * Ack NMU, thankyou for your help with this package.
diff -Nru nullmailer-1.13/debian/postinst nullmailer-1.13/debian/postinst
--- nullmailer-1.13/debian/postinst 2012-08-21 08:07:21.0 +
+++ nullmailer-1.13/debian/postinst 2016-08-06 17:35:13.0 +
@@ -37,6 +37,8 @@
 -e 's/[[:space:]]*:[[:space:]]*/\n/g' \
 -e ':b s/(\[[^]=]*)=/\1:/; tb' \
 -e 's/[][]//g' > /etc/nullmailer/remotes
+   # zap debconf entry, as this key may contain sensitive data.
+   db_set nullmailer/relayhost ""
 
db_get nullmailer/adminaddr
if [ "$RET" ]; then


signature.asc
Description: PGP signature

Bug#833591: [iceowl-extension] Segmentation fault

[Carsten Schoenert]

Hello Thomas,

please "Reply all" next time so the BTS will get the information as well.

Am 06.08.2016 um 19:25 schrieb Thomas Florek:
> Hello Carsten,
> 
> sorry for my first content poor bug report.

No problem if the related information will provided later.

> Now can fully confirm message
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833532#10

I thought so already. I will rename this report and reassign your report
to package calendar-google-provider.
For your side nothing will change, the report number will stay the same.

> I hope that tomorrow can post debugging results.

Yes please, I can't reproduce this issue right now.

-- 
Regards
Carsten

Bug#833594: fizmo: please make the build reproducible

[Sascha Steinbiss]

Source: fizmo
Version: 0.7.10-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: fileordering

Dear maintainer,

while working on the “reproducible builds” effort [1], we have noticed
that fizmo could not be built reproducibly.

The attached patch ensures a stable file order when creating a static 
library. Once applied, fizmo can be built reproducibly in our current
experimental framework.

Thanks
Sascha

[1]: https://wiki.debian.org/ReproducibleBuilds
diff -Nru fizmo-0.7.10/debian/changelog fizmo-0.7.10/debian/changelog
--- fizmo-0.7.10/debian/changelog	2016-04-04 08:23:31.0 +
+++ fizmo-0.7.10/debian/changelog	2016-08-06 16:09:06.0 +
@@ -1,3 +1,10 @@
+fizmo (0.7.10-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Make build reproducible.
+
+ -- Sascha Steinbiss   Sat, 06 Aug 2016 16:08:57 +
+
 fizmo (0.7.10-2) unstable; urgency=low
 
   * Correctly implemented alternatives for zcode-interpreter (Closes: #812412).
diff -Nru fizmo-0.7.10/debian/patches/reproducible.patch fizmo-0.7.10/debian/patches/reproducible.patch
--- fizmo-0.7.10/debian/patches/reproducible.patch	1970-01-01 00:00:00.0 +
+++ fizmo-0.7.10/debian/patches/reproducible.patch	2016-08-06 16:08:45.0 +
@@ -0,0 +1,14 @@
+Description: Make build reproducible
+ Address stable file ordering issue in ar call.
+Author: Sascha Steinbiss 
+--- a/libfizmo/Makefile.am
 b/libfizmo/Makefile.am
+@@ -50,7 +50,7 @@
+ 	cd "$(tmplibdir)" ; \
+ 	"$(AR)" x ../src/tools/libtools.a ; \
+ 	"$(AR)" x ../src/interpreter/libinterpreter.a ; \
+-	"$(AR)" $(ARFLAGS) ../libfizmo.a *.o ; \
++	find -name '*.o' -print0 | LC_ALL=C sort -z | xargs -0 "$(AR)" $(ARFLAGS) ../libfizmo.a ; \
+ 	"$(RANLIB)" ../libfizmo.a ; \
+ 	cd .. ; \
+ 	rm -r "$(tmplibdir)"
diff -Nru fizmo-0.7.10/debian/patches/series fizmo-0.7.10/debian/patches/series
--- fizmo-0.7.10/debian/patches/series	2016-04-04 08:23:31.0 +
+++ fizmo-0.7.10/debian/patches/series	2016-08-06 16:08:45.0 +
@@ -1 +1,2 @@
 manpage-patch.diff
+reproducible.patch

Bug#833511: Filtering is possible, but badly broken

[Werner Mahr]

Hi,

the filters can be set when clicking on the icon left in the search bar. The 
big problem is, that the filter works instantly.

In the old version, kept the headlines after they have been marked read, till 
you changed the feed and go back there, or new articles arrive.

In the new version, you click on a headline and it get marked as read and is 
removed at the same moment, you just can't read the overview or open the 
article. After the removal the next article get's focus and the all starts 
over again.

I just needed less than a second to not read over 25 headlines.

-- 
MfG. usw.

Werner Mahr

Bug#831688: Bug confirmed as upstream

[Robert J. Clay]

tag -1 + confirmed upstream

thanks

-- 
Robert J. Clay
rjc...@gmail.com
j...@rocasa.com

Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A

[Santiago Vila]

On Sat, Aug 06, 2016 at 05:57:20PM +0200, Kurt Roeckx wrote:

> 2.4.6-0.1 builds fine for me using -A.

Please provide a build log for any of your successful
"dpkg-buildpackage -A" builds of libtool 2.4.6-0.1 in stretch.

Thanks.

Bug#825121: changed severity

[Daniel Pocock]

Based on that feedback, I've raised the severity again, but I won't have
time to start trying to code a solution for at least another 2 or 3
weeks, has anybody seen any code in any other preinst / postinst that
can be copied for this purpose?

If anybody else wants to try uploading a fix for this it would be very
welcome, please just put a note in the bug if you start working on it.

Bug#805454: [security] libtoolize behavior depends on parent directories

[Vincent Lefevre]

Could this bug be eventually fixed?

One can compromise other users' account for those who run things
from /tmp subdirectories, e.g.

User1:
  echo "echo Hacked >> ~/.profile" > /tmp/install-sh
  chmod 755 /tmp/install-sh
  cp /tmp/install-sh /tmp/config.guess

User2:
* Have some libtool-based source in /tmp/some_dir
* From this directory, run:
  autoreconf -i
  ./configure

The consequence is that User2 has "Hacked" written at the end of
his .profile file. Of course, one can do much worse...

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

Bug#833593: mutt: whines about getrandom on old kernels

[Adam Borowski]

Package: mutt
Version: 1.6.2-1
Severity: minor

Hi!
New versions of mutt will try to use getrandom() before reading /dev/urandom.
I see three issues:
* no need to #ifdef __linux__, solaris has getrandom() too
* it'd be nice to use getentropy() on [k]freebsd
* on older kernels supported by stretch (3.2..3.16) mutt complains that this
  function is not implemented.  This warning will scare users, and it's not
  that rare to use new userspace on old kernels: vserver/openvz/lxc hosting,
  ARMs with vendor kernels, etc.  The fallback is fully secure: if
  /dev/urandom cannot be read, mutt quits instead of using bad randomness.


-- Package-specific info:
Mutt 1.6.2-neo (2016-07-23)
Copyright (C) 1996-2016 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 3.14.67-vs2.3.6.15-x32-vserver+ (x86_64)
libidn: 1.33 (compiled with 1.33)
hcache backend: tokyocabinet 1.4.48

Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/5/lto-wrapper
Target: i686-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 5.4.0-6' 
--with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs 
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-5 --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib 
--disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo 
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-i386/jre --enable-java-home 
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-i386 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-i386 
--with-arch-directory=i386 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--enable-objc-gc --enable-targets=all --enable-multiarch --with-arch-32=i686
  --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-checking=release --build=i686-linux-gnu --host=i686-linux-gnu 
--target=i686-linux-gnu
Thread model: posix
gcc version 5.4.0 20160609 (Debian 5.4.0-6) 

Configure options: '--build=i686-linux-gnu' '--prefix=/usr' 
'--includedir=\${prefix}/include' '--mandir=\${prefix}/share/man' 
'--infodir=\${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' 
'--disable-silent-rules' '--libdir=\${prefix}/lib/i386-linux-gnu' 
'--libexecdir=\${prefix}/lib/i386-linux-gnu' '--disable-maintainer-mode' 
'--disable-dependency-tracking' '--with-mailpath=/var/mail' 
'--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' 
'--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-pop' 
'--enable-sidebar' '--enable-nntp' '--enable-notmuch' '--with-curses' 
'--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster' '--with-sasl' 
'--without-gdbm' '--without-bdb' '--without-qdbm' 'build_alias=i686-linux-gnu' 
'CFLAGS=-g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security' 
'LDFLAGS=-fPIE -pie -Wl,-z,relro -Wl,-z,now' 'CPPFLAGS=-Wdate-time 
-D_FORTIFY_SOURCE=2'

Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O2 -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security

Compile options:
+CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME 
+DEBUG +DL_STANDALONE +ENABLE_NLS -EXACT_ADDRESS -HOMESPOOL -LOCALES_HACK 
-SUN_ATTACHMENT +HAVE_BKGDSET +HAVE_COLOR +HAVE_CURS_SET +HAVE_GETADDRINFO 
+HAVE_GETSID +HAVE_ICONV +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR 
+HAVE_LIBIDN +HAVE_META +HAVE_REGCOMP +HAVE_RESIZETERM +HAVE_START_COLOR 
+HAVE_TYPEAHEAD +HAVE_WC_FUNCS +ICONV_NONTRANS +USE_COMPRESSED +USE_DOTLOCK 
+USE_FCNTL -USE_FLOCK -USE_GNU_REGEX +USE_GSS +USE_HCACHE +USE_IMAP 
+USE_NOTMUCH +USE_NNTP +USE_POP +USE_SASL +USE_SETGID +USE_SIDEBAR +USE_SMTP 
+USE_SSL_GNUTLS -USE_SSL_OPENSSL 
-DOMAIN
MIXMASTER="mixmaster"
-ISPELL
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/usr/share/mutt"
SYSCONFDIR="/etc"
EXECSHELL="/bin/sh"

patch-quasi-delete-neo-git
patch-progress-neo-git
patch-status-color-neo-git
patch-index-color-neo-git
patch-nested-if-neo-git
patch-cond-date-neo-git
patch-tls-sni-neo-git
patch-sidebar-neo-git
patch-ifdef-neo-git
patch-fmemopen-neo-git
patch-initials-neo-git
patch-trash-neo-git
patch-limit-current-thread-neo-git
patch-skip-quoted-neo-git
patch-compress-neo-git
patch-keywords-neo-git
patch-nntp-neo-git
patch-lmdb-neo-git
patch-1.5.23.smime-encrypt-self.1
patch-new-mail-neo-git
patch-smime-encrypt-to-self-neo-git
patch-sensible-browser-neo-UNKNOWN

To learn more about NeoMutt, visit: http://www.neomutt.org/
If you find a bug in NeoMutt, please raise an issue at:

Bug#833588: apt: Packages held in aptitude get installed with apt anyway

[Manuel A. Fernandez Montecelo]

Control: reassign -1 aptitude


Hi,

2016-08-06 15:29 Salvo Tomaselli:

Package: apt
Version: 1.3~pre3
Severity: normal

Dear Maintainer,
as per subject, holding a package with aptitude and then running dist-upgrade 
with apt, will
try to upgrade the packages in hold anyway.


I can reproduce it, but it would be nice to have some details about the
bug when submitting it, like a way to reproduce it, and:

aptitude search ~ahold
apt-mark showhold
dpkg --get-selections $PKGNAME

as well as the version of aptitude, etc.


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#833592: powerpc: kernel 4.4.(16|13) don't build with gcc-6 but with gcc-5

[Elimar Riesebieter]

Package: gcc-6
Version: 6.1.1-11
Severity: important


Hi all,

building a 4.4 Kernel with gcc-6 fails on arch ppc. Build with gcc-5 works fine.
Kernel 4.7 builds fine with gcc-6. The faillog:

In file included from include/linux/linkage.h:4:0,
 from include/linux/kernel.h:6,
 from arch/powerpc/kernel/ptrace.c:18:
arch/powerpc/kernel/ptrace.c: In function ‘fpr_get’:
arch/powerpc/kernel/ptrace.c:379:24: error: index 32 denotes an offset greater 
than size of ‘u64[32][1] {aka long long unsigned int[32][1]}’ 
[-Werror=array-bounds]
offsetof(struct thread_fp_state, fpr[32][0]));
^
include/linux/compiler.h:464:19: note: in definition of macro 
‘__compiletime_assert’
   bool __cond = !(condition);\
   ^
include/linux/compiler.h:484:2: note: in expansion of macro 
‘_compiletime_assert’
  _compiletime_assert(condition, msg, __compiletime_assert_, __LINE__)
  ^~~
include/linux/bug.h:50:37: note: in expansion of macro ‘compiletime_assert’
 #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
 ^~
include/linux/bug.h:74:2: note: in expansion of macro ‘BUILD_BUG_ON_MSG’
  BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition)
  ^~~~
arch/powerpc/kernel/ptrace.c:378:2: note: in expansion of macro ‘BUILD_BUG_ON’
  BUILD_BUG_ON(offsetof(struct thread_fp_state, fpscr) !=
  ^~~~
include/linux/stddef.h:16:32: note: in expansion of macro ‘__compiler_offsetof’
 #define offsetof(TYPE, MEMBER) __compiler_offsetof(TYPE, MEMBER)
^~~
arch/powerpc/kernel/ptrace.c:379:8: note: in expansion of macro ‘offsetof’
offsetof(struct thread_fp_state, fpr[32][0]));
^~~~
arch/powerpc/kernel/ptrace.c: In function ‘fpr_set’:
arch/powerpc/kernel/ptrace.c:407:24: error: index 32 denotes an offset greater 
than size of ‘u64[32][1] {aka long long unsigned int[32][1]}’ 
[-Werror=array-bounds]
offsetof(struct thread_fp_state, fpr[32][0]));
^
include/linux/compiler.h:464:19: note: in definition of macro 
‘__compiletime_assert’
   bool __cond = !(condition);\
   ^
include/linux/compiler.h:484:2: note: in expansion of macro 
‘_compiletime_assert’
  _compiletime_assert(condition, msg, __compiletime_assert_, __LINE__)
  ^~~
include/linux/bug.h:50:37: note: in expansion of macro ‘compiletime_assert’
 #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
 ^~
include/linux/bug.h:74:2: note: in expansion of macro ‘BUILD_BUG_ON_MSG’
  BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition)
  ^~~~
arch/powerpc/kernel/ptrace.c:406:2: note: in expansion of macro ‘BUILD_BUG_ON’
  BUILD_BUG_ON(offsetof(struct thread_fp_state, fpscr) !=
  ^~~~
include/linux/stddef.h:16:32: note: in expansion of macro ‘__compiler_offsetof’
 #define offsetof(TYPE, MEMBER) __compiler_offsetof(TYPE, MEMBER)
^~~
arch/powerpc/kernel/ptrace.c:407:8: note: in expansion of macro ‘offsetof’
offsetof(struct thread_fp_state, fpr[32][0]));
^~~~
cc1: all warnings being treated as errors
make[3]: *** [arch/powerpc/kernel/ptrace.o] Error 1
make[2]: *** [arch/powerpc/kernel] Error 2
make[1]: *** [bindeb-pkg] Error 2
make: *** [bindeb-pkg] Error 2


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (100, 'experimental')
Architecture: powerpc (ppc)

Kernel: Linux 4.7.0-aragorn-lxtec-ppc
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 gcc-6 depends on:
ii  binutils  2.26.1-1
ii  cpp-6 6.1.1-11
ii  gcc-6-base6.1.1-11
ii  libatomic16.1.1-11
ii  libc6 2.23-4
ii  libcc1-0  6.1.1-11
ii  libgcc-6-dev  6.1.1-11
ii  libgcc1   1:6.1.1-11
ii  libgmp10  2:6.1.1+dfsg-1
ii  libisl15  0.17.1-1
ii  libmpc3   1.0.3-1
ii  libmpfr4  3.1.4-2
ii  libstdc++66.1.1-11
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages gcc-6 recommends:
ii  libc6-dev  2.23-4

Versions of packages gcc-6 suggests:
pn  gcc-6-doc 
pn  gcc-6-locales 
pn  gcc-6-multilib
pn  libasan3-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libmpx2-dbg   
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- no debconf information

Bug#832907: n and . same?

[積丹尼 Dan Jacobson]

OK one day I will try "r" and "a".