Bug#851459: snap: Update autokpgtest for name change

[Jeremy Bicha]

Package: snap
Version: 2013-11-29-5
Tags: patch

snap was renamed in the latest Debian version, but the autopkgtest
needs to be renamed to match. I'm attaching a patch for this.

Thanks,
Jeremy
=== modified file 'debian/tests/run-unit-test'
--- debian/tests/run-unit-test	2016-12-23 15:34:24 +
+++ debian/tests/run-unit-test	2016-12-23 15:36:28 +
@@ -5,6 +5,6 @@
   ADTTMP=`mktemp -d /tmp/${pkg}-test.XX`
 fi
 cd $ADTTMP
-snap /usr/share/snap/HMM/thale /usr/share/doc/${pkg}/examples/DNA/thale.dna.gz
-snap /usr/share/snap/HMM/worm  /usr/share/doc/${pkg}/examples/DNA/worm.dna.gz
+snap-hmm /usr/share/snap/HMM/thale /usr/share/doc/${pkg}/examples/DNA/thale.dna.gz
+snap-hmm /usr/share/snap/HMM/worm  /usr/share/doc/${pkg}/examples/DNA/worm.dna.gz
 

Bug#851388: Affects mtpolicyd

[Scott Kitterman]

In the mtpolicyd plugin for querying a spamassassin AWL database for 
reputation there is:

lib/Mail/MtPolicyd/Plugin/SaAwlLookup.pm:my $addr = NetAddr::IP->new6( 
$ip.'/48' );

If I understand the bug correctly, then it's affected.

Scott K

Bug#851443: linux-image-4.9.0-1-amd64: Regression from 4.8 under X: USB input devices no more work, degraded resolution, "open /dev/dri/card0: No such file or directory" in Xorg.0.log [Intel Skylake,

[Jose R R]

Just built Reiser4-patched jessie-backport -- modified for GCC-4.9:

uname -v
#1 SMP Debian 4.9.2-2.1 (2017-01-14)

uname -a
Linux tzitzimecitlalli 4.9.0-1+reiser4.0.1-amd64 #1 SMP Debian
4.9.2-2.1 (2017-01-14) x86_64 GNU/Linux

On Sat, Jan 14, 2017 at 4:32 PM, Axel Beckert  wrote:
> Package: src:linux
> Version: 4.9.2-2
> Severity: important
>
> Dear Debian Linux Kernel Maintainers,
>
> booting linux-image-4.9.0-1-amd64/4.9.2-2 instead of
> linux-image-4.8.0-2-amd64/4.8.15-2 (or
> linux-image-4.8.0-2-grsec-amd64/4.8.15-2+grsec201701031913+1) shows a
> severe regression on my system wrt. to X.org:
>
> With 4.8.15-2, all three screens, USB mouse and USB keyboard work fine
> under X and the screens have the expected resolutions.
>
> With 4.9.2-2, several things failed:
>
> * X is only shown on two of three screens and both show the same
>   contents instead of different content.
>
> * Resolution is only (1x) 1024x768 instead of the expected 1920x1080 +
>   1280x720 (+ 2048x1152)

In this laptop, the resolution 1366x768 was not affected with kernel
of reference.
< https://pbs.twimg.com/media/C2MMUKUUoAAicJJ.jpg:large >
>
> * As soon as X starts, neither USB keyboard nor mouse are working
>   anymore under X. Pressing Ctrl-Alt-F1 to get to a text console has no
>   effect. (I do get a text console if I login remotely via SSH as root
>   and call "chvt 1". On the text console the USB keyboard is working
>   again.)

I am using a USB mouse and it, too, was not affected by the kernel of reference.
sudo dmesg | grep -i usb
[1.596782] ACPI: bus type USB registered
[1.596813] usbcore: registered new interface driver usbfs
[1.596828] usbcore: registered new interface driver hub
[1.596856] usbcore: registered new device driver usb
[1.597335] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[1.597710] ehci-pci :00:1a.0: new USB bus registered, assigned
bus number 1
[1.616344] ehci-pci :00:1a.0: USB 2.0 started, EHCI 1.00
[1.616600] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[1.616602] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[1.616604] usb usb1: Product: EHCI Host Controller
[1.616605] usb usb1: Manufacturer: Linux 4.9.0-1+reiser4.0.1-amd64 ehci_hcd
[1.616606] usb usb1: SerialNumber: :00:1a.0
[1.617057] hub 1-0:1.0: USB hub found
[1.617430] xhci_hcd :13:00.0: new USB bus registered, assigned
bus number 2
[1.618385] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[1.618388] usb usb2: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[1.618389] usb usb2: Product: xHCI Host Controller
[1.618391] usb usb2: Manufacturer: Linux 4.9.0-1+reiser4.0.1-amd64 xhci-hcd
[1.618393] usb usb2: SerialNumber: :13:00.0
[1.618565] hub 2-0:1.0: USB hub found
[1.618977] xhci_hcd :13:00.0: new USB bus registered, assigned
bus number 3
[1.621193] usb usb3: We don't know the algorithms for LPM for this
host, disabling LPM.
[1.621610] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
[1.621612] usb usb3: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[1.621614] usb usb3: Product: xHCI Host Controller
[1.621615] usb usb3: Manufacturer: Linux 4.9.0-1+reiser4.0.1-amd64 xhci-hcd
[1.621617] usb usb3: SerialNumber: :13:00.0
[1.621808] hub 3-0:1.0: USB hub found
[1.621993] ehci-pci :00:1d.0: new USB bus registered, assigned
bus number 4
[1.640357] ehci-pci :00:1d.0: USB 2.0 started, EHCI 1.00
[1.640752] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
[1.640754] usb usb4: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[1.640755] usb usb4: Product: EHCI Host Controller
[1.640756] usb usb4: Manufacturer: Linux 4.9.0-1+reiser4.0.1-amd64 ehci_hcd
[1.640756] usb usb4: SerialNumber: :00:1d.0
[1.641001] hub 4-0:1.0: USB hub found
[1.944426] usb 1-1: new high-speed USB device number 2 using ehci-pci
[1.968409] usb 4-1: new high-speed USB device number 2 using ehci-pci
[2.093181] usb 1-1: New USB device found, idVendor=8087, idProduct=0024
[2.093187] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[2.093804] hub 1-1:1.0: USB hub found
[2.117199] usb 4-1: New USB device found, idVendor=8087, idProduct=0024
[2.117205] usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[2.117869] hub 4-1:1.0: USB hub found
[2.404401] usb 4-1.1: new full-speed USB device number 3 using ehci-pci
[2.514549] usb 4-1.1: New USB device found, idVendor=062a, idProduct=4101
[2.514552] usb 4-1.1: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[2.514555] usb 4-1.1: Product: 2.4G Keyboard Mouse
[2.514556] usb 4-1.1: Manufacturer: MOSART Semi.
[2.522039] usbcore: registered new interface driver usbhid
[2.522040] usbhid: USB HID core driver
[2.522885] input: MOSART Semi. 

Bug#851458: not-enough-i18n'ed string on devel/website/stats/ pages

[victory]

Package: www.debian.org
Severity: wishlist
Tags: patch l10n

I-have-known-since-5-years-ago bug, though, 
on current devel/website/stats/ pages,
a gettext string is not enough i18n'ed as it does not include its object;

w/ the patch applied, the string will become like
 "Created with "
instead of
 "Created with"
so we can translate it as
 " により生成しました"

patch below

Index: stattrans.pl
===
--- stattrans.pl(revision 240)
+++ stattrans.pl(working copy)
@@ -535,6 +535,11 @@
 if (open (HTML, ">$config{'htmldir'}/$l.wml")) {
printf HTML "#use wml::debian::template 
title=\"<:=\$trans{\$CUR_ISO_LANG}{%s}:>\"\n", $lang;
print HTML "#use wml::debian::toc\n";
+printf HTML qq|webwml-stattrans\n|,
+   alioth_cvs_view_url('stattrans.pl');
+printf HTML "\n";
+printf HTML "Created with 
\n"
+printf HTML "\n";
 print HTML "\n\n";
 $color = get_color ($percent_a{$lang});
 
@@ -655,10 +660,7 @@
 print HTML "\n";
 }
 
-print HTML
-'Created with webwml-stattrans' . "\n";
+print HTML "\n";
 close (HTML);
 } else {
 print "Can't open $config{'htmldir'}/$l.wml\n";
@@ -809,10 +811,7 @@
 print HTMLI "";
 print HTMLI "\n";
 
-print HTMLI
-'Created with webwml-stattrans' . "\n";
+print HTMLI "\n";
 close (HTMLI);
 
 print "done.\n" if ($config{'verbose'});


-- 
victory
no need to CC me :-)

Bug#851179: closed by Michael Gilbert <mgilb...@debian.org> (re: chromium: dependency conflict)

[Luke Kenneth Casson Leighton]

it appears that there isn't a version of virtualbox from debian-testing.

root@fizzy:/home/lkcl# apt-cache show virtualbox
Package: virtualbox
Version: 4.3.36-dfsg-1+deb8u1
Installed-Size: 56553
Maintainer: Debian Virtualbox Team

Architecture: amd64
Depends: adduser, python (<< 2.8), python (>= 2.7~), python2.7,
python:any (>= 2.7.5-5~), libc6 (>= 2.15), libcurl3-gnutls (>=
7.16.2), libgcc1 (>= 1:4.1.1), libgsoap5, libpng12-0 (>= 1.2.13-4),
libpython2.7 (>= 2.7), libsdl1.2debian (>= 1.2.11), libssl1.0.0 (>=
1.0.0), libstdc++6 (>= 4.9), libvncserver0 (>= 0.9.9), libvpx1 (>=
1.0.0), libx11-6, libxcursor1 (>> 1.1.2), libxext6, libxml2 (>=
2.7.4), libxmu6, libxt6, zlib1g (>= 1:1.1.4), virtualbox-dkms (>=
4.3.36-dfsg-1+deb8u1) | virtualbox-source (>= 4.3.36-dfsg-1+deb8u1) |
virtualbox-modules
Recommends: virtualbox-qt (= 4.3.36-dfsg-1+deb8u1), libgl1-mesa-glx |
libgl1, libqt4-opengl (>= 4:4.5.3), libqtcore4 (>= 4:4.5.3), libqtgui4
(>= 4:4.5.3)
Suggests: vde2, virtualbox-guest-additions-iso
Conflicts: virtualbox-2.0, virtualbox-2.1, virtualbox-2.2,
virtualbox-3.0, virtualbox-3.1, virtualbox-3.2, virtualbox-4.0,
virtualbox-4.1, virtualbox-4.2, virtualbox-4.3, virtualbox-5.0
Description-en: x86 virtualization solution - base binaries
 VirtualBox is a free x86 virtualization solution allowing a wide range
 of x86 operating systems such as Windows, DOS, BSD or Linux to run on a
 Linux system.
 .
 This package provides the binaries for VirtualBox. Either the virtualbox-dkms
 or the virtualbox-source package is also required in order to compile the
 kernel modules needed for virtualbox. A graphical user interface for
 VirtualBox is provided by the package virtualbox-qt.
Description-md5: 30f96d22c1a6ca04db16bdc1e79ad965
Homepage: http://www.virtualbox.org/
Tag: hardware::emulation, implemented-in::c, interface::x11, role::program,
 scope::application, uitoolkit::qt, uitoolkit::sdl, x11::application
Section: contrib/misc
Priority: optional
Filename: pool/contrib/v/virtualbox/virtualbox_4.3.36-dfsg-1+deb8u1_amd64.deb
Size: 13465384
MD5sum: 600eca648bb6819de5e6683e77614d98
SHA1: b8d62ea34818a3ac82780b1549ad0ae2df810750
SHA256: 5d18a18000ebc312ae5f01d9a64c5d652dcbc535e3c27d92b289c402c2df8e86


---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68


On Sat, Jan 14, 2017 at 7:51 PM, Debian Bug Tracking System
 wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the chromium package:
>
> #851179: chromium: dependency conflict
>
> It has been closed by Michael Gilbert .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Michael Gilbert 
>  by
> replying to this email.
>
>
> --
> 851179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851179
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> -- Forwarded message --
> From: Michael Gilbert 
> To: 851179-cl...@bugs.debian.org
> Cc:
> Date: Sat, 14 Jan 2017 14:49:17 -0500
> Subject: re: chromium: dependency conflict
> The conflict is correct.  The problem is that you have a mixed system
> with chromium from testing and virtualbox from stable.  You should
> either choose both from stable, or both from testing.
>
> Best wishes,
> Mike
>
> -- Forwarded message --
> From: lkcl 
> To: Debian Bug Tracking System 
> Cc:
> Date: Thu, 12 Jan 2017 19:06:22 +
> Subject: chromium: dependency conflict
> Package: chromium
> Version: 53.0.2785.143-1
> Severity: important
>
> best illustrated as follows:
>
> # apt-get install chromium virtualbox
>
> virtualbox is already the newest version (4.3.36-dfsg-1+deb8u1).
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>  chromium : Conflicts: libnettle4 but 2.7.1-5+deb8u1 is to be installed
> E: Unable to correct problems, you have held broken packages.
>
>
>
> -- System Information:
> Debian Release: 7.4
>   APT prefers testing
>   APT policy: (500, 'testing'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.7.8lkcl (SMP w/8 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages chromium depends on:
> ii  libasound2   1.1.2-1
> ii  libatk1.0-0  2.18.0-1
> ii  libavcodec57 10:3.2-dmo1
> ii  libavformat5710:3.2-dmo1
> ii  libavutil55  

Bug#851443: linux-image-4.9.0-1-amd64: Regression from 4.8 under X: USB input devices no more work, degraded resolution, "open /dev/dri/card0: No such file or directory" in Xorg.0.log [Intel Skylake,

[Ben Hutchings]

Control: tag -1 moreinfo

On Sun, 2017-01-15 at 01:32 +0100, Axel Beckert wrote:
> Package: src:linux
> Version: 4.9.2-2
> Severity: important
> 
> Dear Debian Linux Kernel Maintainers,
> 
> booting linux-image-4.9.0-1-amd64/4.9.2-2 instead of
> linux-image-4.8.0-2-amd64/4.8.15-2 (or
> linux-image-4.8.0-2-grsec-amd64/4.8.15-2+grsec201701031913+1) shows a
> severe regression on my system wrt. to X.org:
> 
> With 4.8.15-2, all three screens, USB mouse and USB keyboard work fine
> under X and the screens have the expected resolutions.
> 
> With 4.9.2-2, several things failed:
> 
> * X is only shown on two of three screens and both show the same
>   contents instead of different content.
> 
> * Resolution is only (1x) 1024x768 instead of the expected 1920x1080 +
>   1280x720 (+ 2048x1152)

This looks like X is having to use a generic vesa driver.

> * As soon as X starts, neither USB keyboard nor mouse are working
>   anymore under X. Pressing Ctrl-Alt-F1 to get to a text console has no
>   effect. (I do get a text console if I login remotely via SSH as root
>   and call "chvt 1". On the text console the USB keyboard is working
>   again.)

I don't know why that would happen, though.

> The most relevant difference from the two Xorg.0.log files seems to be:
> 
> 4.8: (II) xfree86: Adding drm device (/dev/dri/card0)
> 4.8: xf86EnableIOPorts: failed to set IOPL for I/O (No such device)
> 4.8: (II) modeset(0): using drv /dev/dri/card0
> 4.8: (WW) Falling back to old probe method for fbdev
> 
> 4.9: (EE) open /dev/dri/card0: No such file or directory
> 4.9: (WW) Falling back to old probe method for modesetting
> 4.9: (EE) open /dev/dri/card0: No such file or directory

This confirms X didn't find a DRM/KMS driver.

[...]
> 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 
> [8086:1912] (rev 06) (prog-if 00 [VGA controller])
>   Subsystem: ASRock Incorporation HD Graphics 530 [1849:1912]
>   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
> Stepping- SERR- FastB2B- DisINTx-
>   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-  SERR-Latency: 0
>   Interrupt: pin A routed to IRQ 11
>   Region 0: Memory at de00 (64-bit, non-prefetchable) [size=16M]
>   Region 2: Memory at c000 (64-bit, prefetchable) [size=256M]
>   Region 4: I/O ports at f000 [size=64]
>   [virtual] Expansion ROM at 000c [disabled] [size=128K]
>   Capabilities: 
[...]

And no driver is bound to the graphics device.

This device is still listed in i915's device ID table, so it should
have been loaded and would then have probed the device (even though
that may have failed).  Yet it's not even on the loaded module list.

Does 'modprobe i915' have any effect?

Ben.

-- 
Ben Hutchings
Hoare's Law of Large Problems:
Inside every large problem is a small problem struggling to get
out.



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

Bug#817718: wayv: 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/rules:
- Remove legacy DH_COMPAT export.
- Add recommended build-arch and build-indep targets.
- Use dh_prep instead of dh_clean -k.
- Don't allow distclean to ignore all errors.
  * debian/compat: Indicate compatibility level of 10.
  * debian/control:
- Build-depend on debhelper (>= 10).
- Depend on ${misc:Depends}.

Thanks for considering the patch.

Logan Rosen
diff -u wayv-0.3/config.sub wayv-0.3/config.sub
--- wayv-0.3/config.sub
+++ wayv-0.3/config.sub
@@ -1,44 +1,40 @@
 #! /bin/sh
 # Configuration validation subroutine script.
-#   Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
-#   2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008
-#   Free Software Foundation, Inc.
+#   Copyright 1992-2016 Free Software Foundation, Inc.
 
-timestamp='2008-01-16'
+timestamp='2016-11-04'
 
-# This file is (in principle) common to ALL GNU software.
-# The presence of a machine in this file suggests that SOME GNU software
-# can handle that machine.  It does not imply ALL GNU software can.
-#
-# This file is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
+# This file is free software; you can redistribute it and/or modify it
+# under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3 of the License, or
 # (at your option) any later version.
 #
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-# GNU General Public License for more details.
+# This program is distributed in the hope that it will be useful, but
+# WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+# General Public License for more details.
 #
 # You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 51 Franklin Street - Fifth Floor, Boston, MA
-# 02110-1301, USA.
+# along with this program; if not, see .
 #
 # As a special exception to the GNU General Public License, if you
 # distribute this file as part of a program that contains a
 # configuration script generated by Autoconf, you may include it under
-# the same distribution terms that you use for the rest of that program.
+# the same distribution terms that you use for the rest of that
+# program.  This Exception is an additional permission under section 7
+# of the GNU General Public License, version 3 ("GPLv3").
 
 
-# Please send patches to .  Submit a context
-# diff and a properly formatted ChangeLog entry.
+# Please send patches to .
 #
 # Configuration subroutine to validate and canonicalize a configuration type.
 # Supply the specified configuration type as an argument.
 # If it is invalid, we print an error message on stderr and exit with code 1.
 # Otherwise, we print the canonical config type on stdout and succeed.
 
+# You can get the latest version of this script from:
+# http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub
+
 # This file is supposed to be the same for all GNU packages
 # and recognize all the CPU types, system types and aliases
 # that are meaningful with *any* GNU software.
@@ -57,8 +53,7 @@
 me=`echo "$0" | sed -e 's,.*/,,'`
 
 usage="\
-Usage: $0 [OPTION] CPU-MFR-OPSYS
-   $0 [OPTION] ALIAS
+Usage: $0 [OPTION] CPU-MFR-OPSYS or ALIAS
 
 Canonicalize a configuration name.
 
@@ -72,8 +67,7 @@
 version="\
 GNU config.sub ($timestamp)
 
-Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001,
-2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
+Copyright 1992-2016 Free Software Foundation, Inc.
 
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
@@ -120,12 +114,18 @@
 # Here we must recognize all the valid KERNEL-OS combinations.
 maybe_os=`echo $1 | sed 's/^\(.*\)-\([^-]*-[^-]*\)$/\2/'`
 case $maybe_os in
-  nto-qnx* | linux-gnu* | linux-dietlibc | linux-newlib* | linux-uclibc* | \
-  uclinux-uclibc* | uclinux-gnu* | kfreebsd*-gnu* | knetbsd*-gnu* | 
netbsd*-gnu* | \
+  nto-qnx* | linux-gnu* | linux-android* | linux-dietlibc | linux-newlib* | \
+  linux-musl* | linux-uclibc* | uclinux-uclibc* | uclinux-gnu* | 
kfreebsd*-gnu* | \
+  knetbsd*-gnu* | netbsd*-gnu* | netbsd*-eabi* | \
+  kopensolaris*-gnu* | cloudabi*-eabi* | \
   storm-chaos* | os2-emx* | rtmk-nova*)
 os=-$maybe_os
 basic_machine=`echo $1 | sed 

Bug#851457: openldap: [l10n] update Japanese debconf translation

[Kenshi Muto]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Source: openldap
Severity: wishlist
Version: 2.4.44+dfsg-4
Tags: l10n patch

Hi,

I updated Japanese translation of debconf messages (ja.po).
Please apply this.

Thanks,
- -- 
Kenshi Muto
km...@debian.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Processed by Mailcrypt 3.5.9 

iQIcBAEBCgAGBQJYev78AAoJEB0hyD3EUuD8M8YP/2JVcxTe/YDcyrHMg+OqHO7G
8V1lz+6ZlV6ubOGBwbirLxNRMcer/tgPgvSToWWT2Pkww7F4JPckib38RxBfEp3J
TEh3opTpZCWDc0a464fpiYGM40COajMsS95osZTtqOnBU7AAwIdHji3wBgXpRshC
NQncUul9+zVyTa6H2p12EGa9xte8eGxr11579YHG77Xu74oshaSsmgK54eZy373f
g07tcjylwSlONzi4RFvlOPQvNPEqnEdsBBRMFpaDHFL2fYfeTHdOvmth/etqf/ju
LC/Y1F7SeZt46dFK6EYQkNKGkP/cuJGPqTFCStypvgPZbehVilyJ+zqECNo+vwce
zGpY/nyBIue13kpn1xGOC6VN6zdt0JJtspdp4tG5xegu0/EHHK5jJ1ScEGqP3Zd9
Q2K8ECCEjfNqBxZ/X6zQa12gVUWfX2Jc17/M+dEBD587RDtzGzTAMP9FK21uyWJw
AYHuMBNIVlsht6myO8RgaLhlTyf04csOW9JCoJlF7HyvHB+S9ILRd8/BAg+Ge8r7
Y3qHIZpXAW+X9cnQMzZwcxn8OVOw2OD/JBsfvbCJFG78Edd1wgn9t2rRB/fnKE/r
O7QO5q//2ap0ld4bmwSBB1Po99B/2q6ViIoOiWVs0BeR0lDxrqgWXcXa+leZIIDF
H9z3tVV+mM4wZDojcZ7N
=z3ew
-END PGP SIGNATURE-


ja.po
Description: Binary data

Bug#817579: mendexk: 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 10.
  * debian/control:
- Build-depend on debhelper (>= 10).
- Depend on ${misc:Depends}.
  * debian/rules:
- Use dh_prep instead of dh_clean -k.
- Add recommended build-arch and build-indep targets.

Thanks for considering the patch.

Logan Rosen
diff -u mendexk-2.6e/debian/compat mendexk-2.6e/debian/compat
--- mendexk-2.6e/debian/compat
+++ mendexk-2.6e/debian/compat
@@ -1 +1 @@
-4
+10
diff -u mendexk-2.6e/debian/control mendexk-2.6e/debian/control
--- mendexk-2.6e/debian/control
+++ mendexk-2.6e/debian/control
@@ -3,11 +3,11 @@
 Priority: optional
 Maintainer: Masayuki Hatta (mhatta) 
 Standards-Version: 3.8.0
-Build-Depends: libkpathsea-dev, debhelper (>> 4.0.0)
+Build-Depends: libkpathsea-dev, debhelper (>= 10)
 
 Package: mendexk
 Architecture: any
-Depends: ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}
 Description: a replacement for makeindex with many enhancements
  This is an upper-compatible(but slow) substitute for the makeindex program
  which forms part of standard TeX distribution.  Mendex features better 
diff -u mendexk-2.6e/debian/rules mendexk-2.6e/debian/rules
--- mendexk-2.6e/debian/rules
+++ mendexk-2.6e/debian/rules
@@ -7,7 +7,9 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-build: build-stamp
+build: build-arch build-indep
+build-arch: build-stamp
+build-indep: build-stamp
 build-stamp:
dh_testdir
 
@@ -30,7 +32,7 @@
 install-stamp: build-stamp
dh_testdir
dh_testroot
-   dh_clean -k
+   dh_prep
dh_installdirs
 
# Add here commands to install the package into debian/mendexk.

Bug#844184: RFS: muse-el/3.20+dfsg-1 [ITA]

[Nicholas D Steeves]

Dear Sean,

I think it's finally ready.

On Sat, Dec 31, 2016 at 02:19:27PM +, Sean Whitton wrote:

> Thank you for your updated package.  As mentioned previously, we're
> still in time for binNEW.  I've found six remaining issues.  All are
> very easy to fix/check.  Some of these I should have found earlier, so
> my apologies for that.  Some of them are due to your most recent
> changes, though.
> 
> 1) From running adequate:
> 
> 2m48.4s ERROR: FAIL: Inadequate results from running adequate!
>   muse-el: obsolete-conffile /etc/emacs/site-start.d/50muse-el.el

Fixed by adding muse-el.maintscript.  For renamed
packages/transitions, it looks like it needs to be old-name.maintscript.

> 2) "License: MIT" should be "License: Expat".
> 
> "MIT" is ambiguous between various different licenses.

Fixed.

> 3) Eric Marden's copyright on contrib/{cgi.el, httpd.el} is not
> reflected in d/copyright.

I broke these out into individual stanzas, because I'm short on time
right now and wasn't able to find canonical documentation quickly
enough.  Comma separated or
Files: file1
   file2

both seem like likely possibilities.  Would it be a nuisance to the
maint-guide maintainers if I filed a bug requesting some guidelines on
how to group things?  Is that the most appropriate package to file a
bug against for this issue?

> 4) contrib/pyblosxom/make-blog has a custom license.
This one required research.  Fixed.

> 5) COPYING is not copyright the muse-el authors!  By convention, we
> ignore copies of licenses in d/copyright, so you can just remove it.
Thanks for the tip!

> 6) elpa-muse_3.20+dfsg-1_all.deb did not install cleanly.  I pushed a
> commit fixing the problem -- please check it is okay with you.

Back in August, I remember consulting you about what package to source
htmlize from, but forgot that this was the original cause, so yes, I'm
ok with it ;-)

> Don't forget to update the changelog for the above, and `dch -r`.  I
> would recommend testing with piuparts to confirm the (1) and (6) are
> resolved.  I'm confident that I'll be able to upload once you've
> resolved these six points, though I've replied to your other comments
> below.

For some reason my piuparts installation isn't working properly, but
manually I tested both clean install and upgrading in a clean sid
chroot. (this is how I tested #1 and #6)

> > On Sat, Dec 10, 2016 at 02:46:11PM -0700, Sean Whitton wrote:
> > > Dear Nicholas,
> > > 
> > > On Wed, Dec 07, 2016 at 09:16:28PM -0500, Nicholas D Steeves wrote:
[...]
> > > 4. "- Change section to editors; Change priority to optional."
> > > 
> > > This should be two separate lines.
> > 
> > Notice of this kind of convention I'd like to see in a "New Packages
> > Guide" ;-)
> 
> This should probably be in maint-guide.  You could file a bug if there
> is no mention there.  The idea is simply that each '*' is a separate
> change.

Bug filed!

Thanks again for the help!
Nicholas

Bug#851456: Please document this changelog convention

[Nicholas D Steeves]

Package: maint-guide
Version: 1.2.35
Control: found -1 maint-guide/1.2.37

I had thought that it was sometimes ok to " * list a couple; of
closely; related changes" or " * change this and this to fix this" in
d/changelog, until Sean Whitton pointed it out that this was not
correct in Bug #844184.

Please add something to the affect as "individual changes should be on
individual lines, even if they are part of the same fix"

Sincerely,
Nicholas

Bug#820846: do not change the default compression level

[Antoine Beaupré]

Control: retitle -1 build tarballs reproducibly (compression level and date)

Actually, it's more than the compression level - because of the way gbp
builds the tarball, it can't build the tarball reproducibly. Or at
least, it varies from what would be expected from git archive $tag.

According to strace(1), gbp calls the equivalent of this on the
commandline:

git archive --format=tar --prefix=tty-clock-2.2/ 
71343a5968157b95f15b3b1ca0856874 | gzip -9nc

71343a5968157b95f15b3b1ca0856874 is the *tree* associated with the
requested tag (!!). The tree has no notion of timestamp at all, so git
will assign the current time as mtime fields in the generated
tarball. The proper pipeline would be, in my case:

git archive --format=tar --prefix=tty-clock-2.2/ v2.2 | gzip -nc

Changes: no -9, and using the tag directly instead of the tree. This
way, git knows what timestamp to put in the tarball, and will always
create the same tarball if the same tag is given. This is the diffoscope
output between those two pipelines:


$ diffoscope a b
||
  100%  Time: 0:00:00
--- a
+++ b
├── metadata
│ @@ -1 +1 @@
│ -gzip compressed data, max compression, from Unix
│ +gzip compressed data, from Unix
│   --- a-content
├── +++ b-content
│   ├── file list
│   │ @@ -1,7 +1,7 @@
│   │ -drwxrwxr-x   0 root (0) root (0)0 2017-01-15 
03:41:27.00 tty-clock-2.2/
│   │ --rw-rw-r--   0 root (0) root (0)   26 2017-01-15 
03:41:27.00 tty-clock-2.2/.gitignore
│   │ --rw-rw-r--   0 root (0) root (0) 1434 2017-01-15 
03:41:27.00 tty-clock-2.2/Makefile
│   │ --rw-rw-r--   0 root (0) root (0) 1379 2017-01-15 
03:41:27.00 tty-clock-2.2/README
│   │ --rw-rw-r--   0 root (0) root (0) 3232 2017-01-15 
03:41:27.00 tty-clock-2.2/tty-clock.1
│   │ --rw-rw-r--   0 root (0) root (0)20471 2017-01-15 
03:41:27.00 tty-clock-2.2/ttyclock.c
│   │ --rw-rw-r--   0 root (0) root (0) 4183 2017-01-15 
03:41:27.00 tty-clock-2.2/ttyclock.h
│   │ +drwxrwxr-x   0 root (0) root (0)0 2017-01-13 
22:02:02.00 tty-clock-2.2/
│   │ +-rw-rw-r--   0 root (0) root (0)   26 2017-01-13 
22:02:02.00 tty-clock-2.2/.gitignore
│   │ +-rw-rw-r--   0 root (0) root (0) 1434 2017-01-13 
22:02:02.00 tty-clock-2.2/Makefile
│   │ +-rw-rw-r--   0 root (0) root (0) 1379 2017-01-13 
22:02:02.00 tty-clock-2.2/README
│   │ +-rw-rw-r--   0 root (0) root (0) 3232 2017-01-13 
22:02:02.00 tty-clock-2.2/tty-clock.1
│   │ +-rw-rw-r--   0 root (0) root (0)20471 2017-01-13 
22:02:02.00 tty-clock-2.2/ttyclock.c
│   │ +-rw-rw-r--   0 root (0) root (0) 4183 2017-01-13 
22:02:02.00 tty-clock-2.2/ttyclock.h
│   ╵
╵
Note that the timestamps in "a" will reflect when the command is ran,
not the tag timestamp.

Thanks for considering this!

A.

-- 
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are, by
definition, not smart enough to debug it.
- Brian W. Kernighan

Bug#851455: Please stop mentioning haldaemon

[Michael Biebl]

Package: base-passwd
Version: 3.5.42
Severity: normal

Hi,

the hal package has long been deprecated and removed from the archive.
The haldaemon group is unused nowadays so I'd like to see it removed
from base-passwd:
doc/users-and-groups.sgml:  haldaemon

Regards,
Michael


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

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

Versions of packages base-passwd depends on:
ii  libc6  2.24-8
ii  libdebconfclient0  0.219

Versions of packages base-passwd recommends:
ii  debconf [debconf-2.0]  1.5.59

base-passwd suggests no packages.

-- debconf information excluded

Bug#820846: do not change the default compression level

[Antoine Beaupré]

On 2016-05-27 09:29:55, Guido Günther wrote:
> On Tue, Apr 12, 2016 at 08:58:13PM -0400, Antoine Beaupré wrote:
>> git-buildpackage correctly uses the -n flag to make the archive
>> reproducible otherwise, so one has to wonder why there is this
>> needless override, by default. if packages want maximum compression,
>> they can specify that option in gbp.conf!
>> 
>> (tagged as timestamp for reproducible builds, but it's not really a
>> timestamp, it's just the closest tag i could find)
>
> Just to bu sure: your suggestion is to not mess with compression levels
> at all by default and use the configures system defaults?

*nudge* - can we get this updated for stretch?

thanks!

-- 
We must shift America from a needs- to a desires-culture. People must
be trained to desire, to want new things, even before the old have
been entirely consumed. Man's desires must overshadow his needs.
 - Paul Mazur, Lehman Brothers

Bug#851454: desktopnova: should build-depend on python-minimal; FTBFS in Ubuntu

[Logan Rosen]

Package: desktopnova
Version: 0.8.1-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu zesty ubuntu-patch

Dear Maintainer,

desktopnova recently starting failing to build from source in Ubuntu
because it was pulling in python-minimal via a transitive dependency
that no longer existed.

Please build-depend on python-minimal so that the package builds
regardless of what its dependencies transitively depend on. It requires
the python command during the build process.

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

  * Build-depend on python-minimal to fix FTBFS.

Thanks for considering the patch.

Logan Rosen

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

Kernel: Linux 4.4.0-21-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru desktopnova-0.8.1/debian/control desktopnova-0.8.1/debian/control
--- desktopnova-0.8.1/debian/control2011-11-10 11:52:01.0 -0500
+++ desktopnova-0.8.1/debian/control2017-01-14 21:58:29.0 -0500
@@ -2,7 +2,7 @@
 Section: misc
 Priority: optional
 Maintainer: Stefan Haller 
-Build-Depends: debhelper (>= 7), cmake, libglib2.0-dev, libgconf2-dev, 
libgtk2.0-dev, intltool, libxml2-dev, libdbus-glib-1-dev, libxfconf-0-dev
+Build-Depends: debhelper (>= 7), cmake, libglib2.0-dev, libgconf2-dev, 
libgtk2.0-dev, intltool, libxml2-dev, libdbus-glib-1-dev, libxfconf-0-dev, 
python-minimal
 Standards-Version: 3.9.2
 Homepage: http://launchpad.net/desktopnova
 

Bug#850501: rerunning using diffoscope 67-21-gfe7ae15

[Maria Glukhova]

Chris,

вс, 15 янв. 2017 г. в 4:57, Chris Lamb :

> As it happens I wrote my own fix before I saw your email
> and I have pushed it — what do you think?
>
>
Making APK metadata appear at fixed place surely looks better. IMO, that
approach follows the original intent of the request much more closely :)
Thank you very much for your work on this!  (And sorry, once again, for not
doing it properly from the start)

Maria

Bug#850501: rerunning using diffoscope 67-21-gfe7ae15

[Chris Lamb]

Hi Maria,

> Rewrote it so file ordering is not taken into account. Does it work now?

Yes, although this would still mean the output of diffoscope itself
is not determinstic. As it happens I wrote my own fix before I saw your email
and I have pushed it — what do you think?


Regards,

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

Bug#851453: age-days: check-all-the-things/2017.01.15

[Paul Wise]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: age-days

Please reduce the migration time for check-all-the-things to two days.

The version in unstable fixes arbitrary code execution security issues
reported by Jakub Wilk because `python -m` adds '.' to sys.path.

age-days 2 check-all-the-things/2017.01.15

-- 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.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
bye,
pabs

https://wiki.debian.org/PaulWise
diff -Nru check-all-the-things-2016.12.25/check-all-the-things check-all-the-things-2017.01.15/check-all-the-things
--- check-all-the-things-2016.12.25/check-all-the-things	2016-12-25 07:43:10.0 +0800
+++ check-all-the-things-2017.01.15/check-all-the-things	2017-01-15 10:37:30.0 +0800
@@ -36,6 +36,7 @@
 import time
 import signal
 import subprocess as ipc
+import string
 import sys
 from textwrap import TextWrapper
 
@@ -61,6 +62,7 @@
 from curses import tigetstr, setupterm
 setupterm()
 erase_line = tigetstr('el')
+reset_term = tigetstr('sgr0')
 
 try:
 from shutil import which
@@ -139,7 +141,7 @@
 return False
 
 
-def spawn_ptyprocess(cmd, hide, header, footer, limit):
+def spawn_ptyprocess(terminal, cmd, hide, header, footer, limit):
 lines = 0
 trimmed = False
 
@@ -158,6 +160,8 @@
 lines += 1
 if lines > limit:
 trimmed = True
+if terminal:
+sys.stdout.buffer.write(reset_term)
 print(*footer, sep='\n')
 sys.stdout.flush()
 proc.kill(signal.SIGTERM)
@@ -170,10 +174,12 @@
 break
 if header and not hide:
 output_header()
+if terminal and not trimmed:
+sys.stdout.buffer.write(reset_term)
 return not bool(header), trimmed
 
 
-def spawn_pty(cmd, hide, header, footer, limit):
+def spawn_pty(terminal, cmd, hide, header, footer, limit):
 lines = 0
 trimmed = False
 pipe = None
@@ -198,6 +204,8 @@
 lines += 1
 if lines > limit:
 trimmed = True
+if terminal:
+sys.stdout.buffer.write(reset_term)
 print(*footer, sep='\r\n', end='\r\n')
 sys.stdout.flush()
 raise OSError
@@ -209,10 +217,12 @@
 pipe.close()
 if header and not hide:
 output_header()
+if terminal and not trimmed:
+sys.stdout.buffer.write(reset_term)
 return not bool(header), trimmed
 
 
-def spawn_pipe(cmd, hide, header, footer, limit):
+def spawn_pipe(terminal, cmd, hide, header, footer, limit):
 lines = 0
 trimmed = False
 
@@ -231,6 +241,8 @@
 lines += 1
 if lines > limit:
 trimmed = True
+if terminal:
+sys.stdout.buffer.write(reset_term)
 print(*footer, sep='\n')
 sys.stdout.flush()
 proc.terminate()
@@ -250,26 +262,30 @@
 sys.stdout.flush()
 if header and not hide:
 output_header()
+if terminal and not trimmed:
+sys.stdout.buffer.write(reset_term)
 return not bool(header), trimmed
 
 
-def spawn_none(cmd, header):
+def spawn_none(terminal, cmd, header):
 show_header(header)
 ipc.call(cmd, shell=True, stderr=ipc.STDOUT)
+if terminal:
+sys.stdout.buffer.write(reset_term)
 return True, False
 
 
-def spawn(method, cmd, hide, header, footer, limit):
+def spawn(terminal, method, cmd, hide, header, footer, limit):
 if method == 'pipe':
-return spawn_pipe(cmd, hide, header, footer, limit)
+return spawn_pipe(terminal, cmd, hide, header, footer, limit)
 elif method == 'ptyprocess':
 show_progress(cmd)
-return spawn_ptyprocess(cmd, hide, header, footer, limit)
+return spawn_ptyprocess(terminal, cmd, hide, header, footer, limit)
 elif method == 'pty':
 show_progress(cmd)
-return spawn_pty(cmd, hide, header, footer, limit)
+return spawn_pty(terminal, cmd, hide, header, footer, limit)
 elif method == 'none':
-return spawn_none(cmd, header)
+return spawn_none(terminal, cmd, header)
 else:
 raise RuntimeError
 
@@ -373,9 +389,12 @@
 
 def set_command(self, value):
 self.cmd = cmd = value.strip()
-d = collections.defaultdict(str)
-cmd.format(**d)
-nargs = 1 * ('file' in d) + 2 * 

Bug#851452: O: gitg -- git repository viewer/browser

[Dmitry Smirnov]

Package: wnpp
Severity: normal

"gitg" needs new maintainer...

-- 
Regards,
 Dmitry Smirnov.


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

Bug#851451: O: libgit2-glib -- glib wrapper library around the libgit2 git access library

[Dmitry Smirnov]

Package: wnpp
Severity: normal

"libgit2-glib" needs new maintainer...

-- 
Regards,
 Dmitry Smirnov


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

Bug#851450: pan won't start without gpg2, should depend on gnupg2

[Bert Riding]

Package: pan
Version: 0.141-1
Severity: important

Dear Maintainer,

Recent upgrade of pan resulted in error message stating gpg2 not found.

Linked gpg2 to gpg as a quick fix.  Further investigation showed gpg2 to
be included in the gnupg2 package, a transitional package that created a
link gpg2 to gpg.  Removed my own link and installed gnupg2 with
positive results.  Pan now starts normally.  

Either gnupg2 should be a depedency of pan, or pan should move to
requiring gpg instead of gpg2.


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

Kernel: Linux 4.9.3 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages pan depends on:
ii  gnome-keyring3.20.0-3
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-8
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libgcc1  1:6.3.0-2
ii  libgdk-pixbuf2.0-0   2.36.3-1
ii  libglib2.0-0 2.50.2-2
ii  libgmime-2.6-0   2.6.21-1
ii  libgnome-keyring03.12.0-1+b1
ii  libgnutls30  3.5.8-1
ii  libgtk-3-0   3.22.6-1
ii  libnotify4   0.7.7-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libstdc++6   6.3.0-2
ii  zlib1g   1:1.2.8.dfsg-4

pan recommends no packages.

pan suggests no packages.

-- no debconf information

Bug#851449: kali: my kali linux black screen suddenly when i use it,i dont know why

[kali]

Package: kali-linux
Version: 2016.2.12
Severity: important
File: kali

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

-what i do is typing on terminal,it always black screen suddenly when im 
typing i didnt expect this

-- System Information: Distributor ID:  Kali Description:   Kali 
GNU/Linux Rolling Release:  kali-rolling Codename:  kali-rolling 
Architecture: i686

Kernel: Linux 4.6.0-kali1-686-pae (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 kali-linux depends on: ii apache2 2.4.23-4 ii 
atftpd 0.7.git20120829-2.1 ii axel 2.11-1 ii exe2hexbat 1.4.1-1kali1 ii 
expect 5.45-7 ii florence 0.6.3-1 ii gdisk 1.0.1-1 ii git 1:2.9.3-1 ii 
gparted 0.25.0-1 ii iw 3.17-1 ii kali-desktop-common 2016.2.12 ii lvm2 
2.02.164-1 ii mercurial 3.8.4-1 ii mysql-server 5.6.30-1 ii 
netcat-traditional 1.10-41 ii openssh-server 1:7.3p1-1 ii openvpn 
2.3.11-2 ii p7zip-full 16.02+dfsg-1 ii parted 3.2-15 ii php 1:7.0+44 ii 
php-mysql 1:7.0+44 ii php7.0 [php] 7.0.9-2 ii rdesktop 1.8.3-1+b1 ii 
rfkill 0.5-1 ii samba 2:4.4.5+dfsg-2 ii screen 4.4.0-4 ii snmp 
5.7.3+dfsg-1.4 ii snmpd 5.7.3+dfsg-1.4 ii subversion 1.9.4-2 ii sudo 
1.8.17p1-2 ii tcpdump 4.7.4-1+b1 ii testdisk 7.0-1+b1 ii tftp 0.17-18 ii 
tightvncserver 1.3.9-8 ii tmux 2.2-3 ii unrar 1:5.3.2-1 ii upx-ucl 
3.91-2 ii vim 2:7.4.1829-1 ii vim-gtk [vim] 2:7.4.1829-1 ii whois 5.2.12 
ii zerofree 1.0.3-1

kali-linux recommends no packages.

kali-linux suggests no packages.

-- no debconf information

Bug#851448: clonezilla: Check for compressor existence

[Celelibi]

Package: clonezilla
Version: 3.21.13-1
Severity: normal

Dear Maintainer,

It looks like the existence of the compressor is not checked when saving
a partition (or a whole disk, which use the same task_saveparts
function).

I had pxz installed, but it uses pixz. Which make the partition saving
fail with an inexplicit message.

Best regards,
Celelibi

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

Kernel: Linux 3.10.11 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages clonezilla depends on:
ii  bc 1.06.95-9+b2
ii  drbl   2.20.11-1
ii  file   1:5.29-2
ii  gdisk  1.0.1-1
ii  pigz   2.3.4-1

Versions of packages clonezilla recommends:
pn  partclone  
pn  partimage  

Versions of packages clonezilla suggests:
ii  cifs-utils  2:6.6-4
ii  openssh-client  1:7.3p1-5

-- no debconf information

Bug#850501: rerunning using diffoscope 67-21-gfe7ae15

[Maria Glukhova]

Chris,

I see. Seems like file ordering differs for some reason. I should not have
relied on it, anyway.
Rewrote it so file ordering is not taken into account. Does it work now?

Thank you,
Maria

вс, 15 янв. 2017 г. в 2:43, Chris Lamb :

> Maria,
>
> Thank you so much for these :)
>
> > Added some tests for APK comparator, see attached patch.
>
> Unfortunately I'm seeing:
>
> differences = [,  metadata -- APK metadata []>,  AndroidManifest.xml []>,  original/AndroidManifest.xml []>]
>
> @skip_unless_tools_exist('apktool', 'zipinfo')
> def test_android_manifest(differences):
> >   assert differences[1].source1 == 'AndroidManifest.xml'
> E   assert 'APK metadata' == 'AndroidManifest.xml'
> E - APK metadata
> E + AndroidManifest.xml
>
> Any ideas?
>
> > However, please keep in mind apktool takes a lot of time to run even on
> toy
> > examples
>
> Whilst I am not a fan of it slowing down this much, I think I'd
> prefer to see some tests in there (that we can speed up later)
> rather than none.
>
>
> Regards,
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
>
From 67e0ca7b632699f54aec27069efd4e0c547ab708 Mon Sep 17 00:00:00 2001
From: Maria Glukhova 
Date: Fri, 13 Jan 2017 23:22:10 +0200
Subject: [PATCH] Add some tests for APK comarator.

---
 tests/comparators/test_apk.py |  66 ++
 tests/data/apk_manifest_expected_diff |  11 ++
 tests/data/apk_zipinfo_expected_diff  |   6 
 tests/data/test1.apk  | Bin 0 -> 866 bytes
 tests/data/test2.apk  | Bin 0 -> 864 bytes
 5 files changed, 83 insertions(+)
 create mode 100644 tests/comparators/test_apk.py
 create mode 100644 tests/data/apk_manifest_expected_diff
 create mode 100644 tests/data/apk_zipinfo_expected_diff
 create mode 100644 tests/data/test1.apk
 create mode 100644 tests/data/test2.apk

diff --git a/tests/comparators/test_apk.py b/tests/comparators/test_apk.py
new file mode 100644
index 000..3093027
--- /dev/null
+++ b/tests/comparators/test_apk.py
@@ -0,0 +1,66 @@
+# -*- coding: utf-8 -*-
+#
+# diffoscope: in-depth comparison of files, archives, and directories
+#
+# Copyright © 2017 Maria Glukhova 
+#
+# diffoscope is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# diffoscope is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with diffoscope.  If not, see .
+
+import pytest
+
+from diffoscope.comparators.apk import ApkFile
+
+from utils import skip_unless_tools_exist, data, load_fixture, \
+assert_non_existing
+
+apk1 = load_fixture(data('test1.apk'))
+apk2 = load_fixture(data('test2.apk'))
+
+def test_identification(apk1):
+assert isinstance(apk1, ApkFile)
+
+def test_no_differences(apk1):
+difference = apk1.compare(apk1)
+assert difference is None
+
+@pytest.fixture
+def differences(apk1, apk2):
+return apk1.compare(apk2).details
+
+@skip_unless_tools_exist('apktool', 'zipinfo')
+def test_compare_non_existing(monkeypatch, apk1):
+assert_non_existing(monkeypatch, apk1)
+
+@skip_unless_tools_exist('apktool', 'zipinfo')
+def test_zipinfo(differences):
+assert differences[0].source1 == 'zipinfo {}'
+assert differences[0].source2 == 'zipinfo {}'
+expected_diff = open(data('apk_zipinfo_expected_diff')).read()
+assert differences[0].unified_diff == expected_diff
+
+@skip_unless_tools_exist('apktool', 'zipinfo')
+def test_android_manifest(differences):
+manifest_diff = next((d for d in differences
+  if d.source1 == 'AndroidManifest.xml'), None)
+assert manifest_diff is not None
+assert manifest_diff.source2 == 'AndroidManifest.xml'
+expected_diff = open(data('apk_manifest_expected_diff')).read()
+assert manifest_diff.unified_diff == expected_diff
+
+@skip_unless_tools_exist('apktool', 'zipinfo')
+def test_apk_metadata_source(differences):
+metadata_diff = next((d for d in differences
+  if d.source1 == 'APK metadata'), None)
+assert metadata_diff is not None
+assert metadata_diff.source2 == 'APK metadata'
diff --git a/tests/data/apk_manifest_expected_diff b/tests/data/apk_manifest_expected_diff
new file mode 100644
index 000..9d37a92
--- /dev/null
+++ b/tests/data/apk_manifest_expected_diff
@@ -0,0 +1,11 @@
+@@ -1,9 +1,9 @@
+ 
+-http://schemas.android.com/apk/res/android;>
+ 
+ 
+ 
+ 
+ 
+ 

Bug#849483: debian-policy: emacs build dependencies probably need adjustment

[Russ Allbery]

Guillem Jover  writes:
> On Sun, 2017-01-08 at 11:29:05 -0800, Russ Allbery wrote:

>> Just converting that file to Markdown is probably the best solution.
>> Thanks!  I just switched Emacs versions since that was easy and simple,
>> but org-mode is a bit obscure as a document formatting mechanism, and
>> we're already using Markdown for something else.

> Perfect, let me know if you want something else changed/improved in
> that patch.

Patch now applied for the next release.  Thanks again!

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

Bug#850646: [copyright-format] Allow https version of Format URI

[Russ Allbery]

Control: tags -1 pending

Didier 'OdyX' Raboud  writes:
> Le dimanche, 8 janvier 2017, 12.02:38 h CET Russ Allbery a écrit :

>> Here's an updated patch that also fixes the other examples.

> Seconded.

Thanks everyone.  This has been applied for the next release.

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

Bug#817802: chromium: Scrolling over tabs doesn't work as expected.

[Awtul]

Package: chromium
Version: 55.0.2883.75-3
Followup-For: Bug #817802

Dear Maintainer,

Please consider reopening this bug since it still present in chromium 55x.
Mouse scroll  over tabs for switch between tabs doesn't work as expected. I 
have to scroll twice up/down
if the mouse pointer leaves chromium window instead of once for switch between 
tabs. It worked fine in earlier versions, 
before 55x and after 49x.

Scroll over tabs for switch between tabs is a nice feature provided by 
chromium. I know it's a trivial issue but
it would be nice to have it working just fine, as expected, under Stretch.

Regards,

Awtul

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

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

Versions of packages chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 7:3.2.2-1
ii  libavformat577:3.2.2-1
ii  libavutil55  7:3.2.2-1
ii  libc62.24-8
ii  libcairo21.14.8-1
ii  libcups2 2.2.1-5
ii  libdbus-1-3  1.10.14-1
ii  libevent-2.0-5   2.0.21-stable-2.1
ii  libexpat12.2.0-2
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.3.0-2
ii  libgdk-pixbuf2.0-0   2.36.3-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk2.0-0  2.24.31-1
ii  libharfbuzz0b1.2.7-1+b1
ii  libicu57 57.1-5
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26.2-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpng16-16  1.6.28-1
ii  libpulse09.0-5
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.3-3
ii  libstdc++6   6.3.0-2
ii  libvpx4  1.6.0-3
ii  libwebp6 0.5.2-1
ii  libwebpdemux20.5.2-1
ii  libx11-6 2:1.6.4-2
ii  libx11-xcb1  2:1.6.4-2
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.8-2
ii  libxml2  2.9.4+dfsg1-2.1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.3-1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-l10n  

-- no debconf information

Bug#851447: distro-info-data: please add bullseye to list of releases

[Stuart Prescott]

Package: distro-info-data
Version: 0.26
Severity: normal

Dear Maintainer,

We already know bullseye will be the codename for buster+1, so let's include
it in distro-info for stretch.

  https://lists.debian.org/debian-devel-announce/2016/07/msg2.html

cheers
Stuart

Bug#851429: installation-reports: mounting CD fails on qemu-system-aarch64

[Steve McIntyre]

Hi Adam,

On Sat, Jan 14, 2017 at 10:34:18PM +0100, Adam Borowski wrote:
>Package: installation-reports
>Severity: normal
>
>Hi!
>I'm afraid that regular arm64 d-i images fail to detect qemu's CD-ROM, and
>there's apparently no way to direct it to load udebs from a network mirror
>like mini.iso does.  On the other hand, installation with mini.iso works
>well.
>
>The failing step is "Detecting hardware to find CD-ROM drives".
>
>CD=debian-stretch-DI-rc1-arm64-netinst.iso
>NET="-net bridge -net nic"
>
>qemu-system-aarch64 -machine virt -nographic -cpu cortex-a57 \
> -bios /usr/share/qemu-efi/QEMU_EFI.fd -m 2048 $NET \
> -drive file="$DISK",cache=writeback,index=0,media=disk,format=raw \
> -drive file="$CD",cache=writeback,index=1,media=cdrom -boot d

I think the problem is with your setup. I've just booted that exact
netinst image happily using

qemu-system-aarch64 -m 4G -cpu cortex-a57 -M virt -smp 8 -nographic
-pflash AAVMF_CODE.fd -pflash AAVMF_VARS.fd -drive
file=/scratch/iso/debian-stretch-DI-rc1-arm64-netinst.iso,id=cdrom,if=none,media=cdrom
-device virtio-scsi-device -device scsi-cd,drive=cdrom -k en-gb
-netdev user,id=eth0 -device virtio-net-device,netdev=eth0

and it's running the installer right now with udebs from the netinst
iso. What version of qemu-efi are you using for
/usr/share/qemu-efi/QEMU_EFI.fd?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Further comment on how I feel about IBM will appear once I've worked out
 whether they're being malicious or incompetent. Capital letters are forecast."
 Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html

Bug#851442: clonezilla: Unhandled spaces in disk serial numbers

[Celelibi]

Package: clonezilla
Version: 3.21.13-1
Severity: normal

Dear Maintainer,

When building the list of devices that can be choosen to backup, the
serial number of every disk is parsed. If one of them contains spaces, a
subsequent call to whiptail fails, leading to an abort with the message:

"Box" is an unknown hard drive device. Program terminated!.


Here is the serial number on my system (not sure if that's expected).
$ udevadm info -q env -n /dev/nvme0n1 | grep ID_SERIAL=
ID_SERIAL=PM961 NVMe SAMSUNG 512GB_  S33YNX0HB18834


I would suggest that the function get_disk_serial_no in the file
/usr/share/drbl/sbin/ocs-functions replaces spaces with underscores.
Maybe adding something like that before exiting would be enough.
  serialno="$(echo $serialno | tr ' ' _ 2>/dev/null)"


Best regards,
Celelibi

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

Kernel: Linux 3.10.11 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages clonezilla depends on:
ii  bc 1.06.95-9+b2
ii  drbl   2.20.11-1
ii  file   1:5.29-2
ii  gdisk  1.0.1-1
ii  pigz   2.3.4-1

Versions of packages clonezilla recommends:
pn  partclone  
pn  partimage  

Versions of packages clonezilla suggests:
ii  cifs-utils  2:6.6-4
ii  openssh-client  1:7.3p1-5

-- no debconf information

Bug#850733: [Reportbug-maint] Bug#850733: Crashes with "TypeError: GObject.__init__() takes exactly 0 arguments (1 given)"

[Simon McVittie]

On Sat, 14 Jan 2017 at 23:36:55 +, James Clarke wrote:
> It seems GetMultilinePage's get_value also has a call to get_text without
> the extra parameter, but a grep for GetMultilinePage only shows the class
> definition, with no uses... deletion candidate? From what I can tell, it
> was added in 3739eb89aa, but even then it wasn't being used by anything?
> Anyway, if it needs to stay, the extra True needs to be added to it too.

There's also infinite recursion here, if the prompt doesn't contain ENTER:

def get_multiline(prompt, *args, **kwargs):
_assert_context(reportbug_context)
if 'ENTER' in prompt:
# This is a list, let's handle it the best way
return get_list(prompt, *args, **kwargs)
else:
return get_multiline(prompt, *args, **kwargs)

I suspect that last line was intended to be a GetMultilinePage wrapper.
But I can't actually test this, because the only use of get_multiline()
does have ENTER in its prompt (and it crashes - fix attached).

I also turned on deprecation warnings (python -Wall) and fixed most
of them. Some remain, particularly constructors for dialogs; I don't
know PyGTK well enough to immediately know what it wants there.

S
>From a79911a14a226cd068bdb5d1e8e1bd101e457ea5 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sat, 14 Jan 2017 23:59:01 +
Subject: [PATCH 10/14] gtk2_ui: hook up GetMultilinePage the way it was
 presumably meant to work

---
 reportbug/ui/gtk2_ui.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/reportbug/ui/gtk2_ui.py b/reportbug/ui/gtk2_ui.py
index f055d23..50bd195 100644
--- a/reportbug/ui/gtk2_ui.py
+++ b/reportbug/ui/gtk2_ui.py
@@ -1731,7 +1731,7 @@ def get_multiline(prompt, *args, **kwargs):
 # This is a list, let's handle it the best way
 return get_list(prompt, *args, **kwargs)
 else:
-return get_multiline(prompt, *args, **kwargs)
+return _get_multiline(prompt, *args, **kwargs)
 
 pages = {'get_string': GetStringPage,
  'get_password': GetPasswordPage,
@@ -1745,6 +1745,7 @@ pages = {'get_string': GetStringPage,
  'select_options': SelectOptionsPage,
  'get_list': GetListPage,
  'system': SystemPage,
+ '_get_multiline': GetMultilinePage,
  }
 dialogs = {'yes_no': YesNoDialog,
'get_filename': GetFilenameDialog,
-- 
2.11.0

>From c94b7604ca402727ea0c01126dab4cfe3464ec05 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sun, 15 Jan 2017 00:21:57 +
Subject: [PATCH 11/14] gtk2_ui: Use modern form of constructor for
 Gtk.Alignment

The one with positional parameters is no longer supported.
---
 reportbug/ui/gtk2_ui.py | 15 +--
 1 file changed, 9 insertions(+), 6 deletions(-)

diff --git a/reportbug/ui/gtk2_ui.py b/reportbug/ui/gtk2_ui.py
index 50bd195..a6b0e11 100644
--- a/reportbug/ui/gtk2_ui.py
+++ b/reportbug/ui/gtk2_ui.py
@@ -158,13 +158,16 @@ class CustomDialog(Gtk.Dialog):
 hbox = Gtk.HBox(spacing=10)
 vbox.pack_start(hbox, False, True, 0)
 
-align = Gtk.Alignment(0.5, 0.5, 1.0, 1.0)
+# TODO: deprecated, new code is meant to set the halign/valign/margin
+# properties on the child widget instead. Also this is probably
+# useless without having a child widget?
+align = Gtk.Alignment(xalign=0.5, yalign=0.5, xscale=1.0, yscale=1.0)
 hbox.pack_start(align, False, True, 0)
 
 image = Gtk.Image.new_from_stock(stock_image, Gtk.IconSize.DIALOG)
 hbox.pack_start(image, True, True, 0)
 
-label = Gtk.Label(message)
+label = Gtk.Label(label=message)
 label.set_line_wrap(True)
 label.set_justify(Gtk.Justification.FILL)
 label.set_selectable(True)
@@ -395,7 +398,7 @@ class BugPage(Gtk.EventBox, threading.Thread):
 self.bug_status = None
 
 vbox = Gtk.VBox(spacing=12)
-vbox.pack_start(Gtk.Label("Retrieving bug information."), False, True, 0)
+vbox.pack_start(Gtk.Label(label="Retrieving bug information."), False, True, 0)
 
 self.progress = Gtk.ProgressBar()
 self.progress.set_pulse_step(0.01)
@@ -436,7 +439,7 @@ class BugPage(Gtk.EventBox, threading.Thread):
 def not_found(self):
 _assert_context(ui_context)
 self.drop_progressbar()
-self.add(Gtk.Label("The bug can't be fetched or it doesn't exist."))
+self.add(Gtk.Label(label="The bug can't be fetched or it doesn't exist."))
 self.show_all()
 
 def found(self, info):
@@ -446,7 +449,7 @@ class BugPage(Gtk.EventBox, threading.Thread):
 bodies = info[1]
 vbox = Gtk.VBox(spacing=12)
 vbox.set_border_width(12)
-label = Gtk.Label('Description: ' + desc)
+label = Gtk.Label(label='Description: ' + desc)
 label.set_line_wrap(True)
 label.set_justify(Gtk.Justification.FILL)
 vbox.pack_start(label, False, True, 0)
@@ -465,7 +468,7 @@ 

Bug#810158: ksh fails to install on systems with merged /usr

[Axel Beckert]

Control: severity -1 important

Marco d'Itri wrote:
> Control: severity -1 grave
> > Patch attached.
> Merged /usr is the default since debootstrap 1.0.85, so the package
> is uninstallable on new systems.

Merged /usr is no more the default since debootstrap 1.0.87, so the
package is installable on new systems.

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

Bug#850733: [Reportbug-maint] Bug#850733: Crashes with "TypeError: GObject.__init__() takes exactly 0 arguments (1 given)"

[James Clarke]

On 15 Jan 2017, at 00:47, James Clarke  wrote:
> On 15 Jan 2017, at 00:37, Simon McVittie  wrote:
>> On Sun, 15 Jan 2017 at 00:32:15 +, Simon McVittie wrote:
>>> I suspect that last line was intended to be a GetMultilinePage wrapper.
>>> But I can't actually test this, because the only use of get_multiline()
>>> does have ENTER in its prompt (and it crashes - fix attached).
>> 
>> On testing it by hacking the prompt for Cc in advanced mode to not include
>> ENTER, sure enough it doesn't work.
> 
> Oh, also, s/python-gtkspellcheck/python3-gtkspellcheck/ in gtk2_ui.py.

... and similarly for python-urwid in urwid_ui.py. Looks like d/README.*
might also need updating, as well as .gitignore:

> debian:git-src james% git status --porcelain
> ?? debian/python3-reportbug.substvars
> ?? debian/python3-reportbug/

Regards,
James

Bug#851446: mkdir: cannot create directory `/run/shm': File exists

[Simon McVittie]

On Sat, 24 Sep 2016 at 20:44:49 +0200, Simó Albert i Beltran wrote:
> I found the same issue upgrading a VPS from wheezy to jessie with the
> version 2.88dsf-59.

Please don't reopen old bug reports, even if the symptoms are the same,
unless you are absolutely sure the root cause is also the same.
It usually just causes confusion - it's quite common to see several
bugs cause the same superficial symptoms, and if they all share one
bug number it's hard to track which ones are fixed in which versions.

We can merge bugs if they are duplicates, and that doesn't result in
ambiguity. I've "cloned" this bug to give you a new bug number,
#851446, as though you had opened a new one bug yourself. Please
send any further information to that bug number.

> $ ls -l /dev/shm
> lrwxrwxrwx 1 root root 8 Nov 28  2014 /dev/shm -> /run/shm
> $ ls -l /run/shm
> lrwxrwxrwx 1 root root 8 Oct 13  2015 /run/shm -> /dev/shm
> $ mountpoint /dev
> /dev is not a mountpoint

Obviously, that really shouldn't happen. I don't suppose you have
backups or some other record that would indicate what state the VPS
was in before the upgrade? Otherwise it's probably going to be
difficult to reproduce this issue.

S

Bug#850733: [Reportbug-maint] Bug#850733: Crashes with "TypeError: GObject.__init__() takes exactly 0 arguments (1 given)"

[James Clarke]

On 15 Jan 2017, at 00:37, Simon McVittie  wrote:
> On Sun, 15 Jan 2017 at 00:32:15 +, Simon McVittie wrote:
>> I suspect that last line was intended to be a GetMultilinePage wrapper.
>> But I can't actually test this, because the only use of get_multiline()
>> does have ENTER in its prompt (and it crashes - fix attached).
> 
> On testing it by hacking the prompt for Cc in advanced mode to not include
> ENTER, sure enough it doesn't work.

Oh, also, s/python-gtkspellcheck/python3-gtkspellcheck/ in gtk2_ui.py.

Regards,
James

Bug#851445: /etc/machine-id is not guaranteed to exist, makes test-suite failures non-fatal

[Michael Biebl]

Am 15.01.2017 um 01:43 schrieb Michael Biebl:

> We have three options

a/ b/ c/ d/

Apparently I can't count :-)


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



signature.asc
Description: OpenPGP digital signature

Bug#850501: rerunning using diffoscope 67-21-gfe7ae15

[Chris Lamb]

Maria,

Thank you so much for these :)

> Added some tests for APK comparator, see attached patch.

Unfortunately I'm seeing:

differences = [, , , ]

@skip_unless_tools_exist('apktool', 'zipinfo')
def test_android_manifest(differences):
>   assert differences[1].source1 == 'AndroidManifest.xml'
E   assert 'APK metadata' == 'AndroidManifest.xml'
E - APK metadata
E + AndroidManifest.xml

Any ideas?

> However, please keep in mind apktool takes a lot of time to run even on toy
> examples

Whilst I am not a fan of it slowing down this much, I think I'd
prefer to see some tests in there (that we can speed up later)
rather than none.


Regards,

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

Bug#851445: /etc/machine-id is not guaranteed to exist, makes test-suite failures non-fatal

[Michael Biebl]

Source: systemd
Version: 232-10
Severity: important

While investigating #851412, I noticed that we have a couple of buildds,
where the test-suite fails but we ignore the error, because
/etc/machine-id does not exist.
In case of mips64el this did hide a real bug.

As init is no longer essential, the assumption that /etc/machine-id is
always available and the absence means an old sysv chroot where we can
ignore test suite failures is no longer correct:
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=bb42ca5806768929f4b31db04ad651cedcbf421c

We have three options
a/ Add a Build-Depends: systemd 
   This ensures /etc/machine-id exists while still making the package
   bootstrappable by using "nocheck". The only downside afaics is that
   we ignore test suite failures during the initial bootstrap.

b/ Restore
   
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=e27b77c90e48f37495f7792318f9394b41f41420
   Upstream is pretty clear that such a patch won't be merged, so the
   obbvious downside is that we will basically have to carry that
   forever downstream including the ongoing maintainance effort.
   To prove that point, the original patch by Martin no longer applies
   cleanly and would need to be forward ported.

c/ Get /etc/machine-id in a different, essential package so we can
   depend on it existing always.
   We tried that in #745876 but the base-files maintainer did not take
   that patch.

d/ Use an LD_PRELOAD hack, which overrides sd_id128_get_machine. An
   example that was mentioned in IRC by waldi was
   thin-provisioning-tools.

a/ strikes me as the most simple solution, which always has a certain
appeal. I'd appreciate more feedback why we should not pick that obvious
solution and go a different way. Maybe there is a different way I forgot
to think about.


The status quo of ignoring test suite failures is bad. I suspect this to
regress once more build chroots are rebuilt where init is not essential.

Michael

-- Package-specific info:

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

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

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.126
ii  udev 232-10

-- no debconf information

Bug#851444: ITP: python-xarray -- N-D labeled arrays and datasets in Python

[Ghislain Antony Vaillant]

Package: wnpp
Severity: wishlist
Owner: Ghislain Antony Vaillant 

* Package name: python-xarray
  Version : 0.8.2
  Upstream Author : xarray Developers
* URL : http://xarray.pydata.org
* License : Apache-2.0
  Programming Lang: Python
  Description : N-D labeled arrays and datasets in Python

Long-Description:
 xarray (formerly xray) is an open source project and Python package
 that aims to bring the labeled data power of pandas to the physical
 sciences, by providing N-dimensional variants of the core pandas data
 structures.
 .
 It provides a pandas-like and pandas-compatible toolkit for analytics
 on multi-dimensional arrays, rather than the tabular data for which
 pandas excels.

This package will be maintained by the Debian Science Team.

Bug#851443: linux-image-4.9.0-1-amd64: Regression from 4.8 under X: USB input devices no more work, degraded resolution, "open /dev/dri/card0: No such file or directory" in Xorg.0.log [Intel Skylake,

[Axel Beckert]

Package: src:linux
Version: 4.9.2-2
Severity: important

Dear Debian Linux Kernel Maintainers,

booting linux-image-4.9.0-1-amd64/4.9.2-2 instead of
linux-image-4.8.0-2-amd64/4.8.15-2 (or
linux-image-4.8.0-2-grsec-amd64/4.8.15-2+grsec201701031913+1) shows a
severe regression on my system wrt. to X.org:

With 4.8.15-2, all three screens, USB mouse and USB keyboard work fine
under X and the screens have the expected resolutions.

With 4.9.2-2, several things failed:

* X is only shown on two of three screens and both show the same
  contents instead of different content.

* Resolution is only (1x) 1024x768 instead of the expected 1920x1080 +
  1280x720 (+ 2048x1152)

* As soon as X starts, neither USB keyboard nor mouse are working
  anymore under X. Pressing Ctrl-Alt-F1 to get to a text console has no
  effect. (I do get a text console if I login remotely via SSH as root
  and call "chvt 1". On the text console the USB keyboard is working
  again.)

The most relevant difference from the two Xorg.0.log files seems to be:

4.8: (II) xfree86: Adding drm device (/dev/dri/card0)
4.8: xf86EnableIOPorts: failed to set IOPL for I/O (No such device)
4.8: (II) modeset(0): using drv /dev/dri/card0
4.8: (WW) Falling back to old probe method for fbdev

4.9: (EE) open /dev/dri/card0: No such file or directory
4.9: (WW) Falling back to old probe method for modesetting
4.9: (EE) open /dev/dri/card0: No such file or directory

>From then on things seemed to go downhill…

Attached is the full diff between the two files (again, with timing
information being stripped), generated using "diff -u <(perl -pE
's/^\[[^]]*\] *//' < /var/log/Xorg.0.log-4.8) <(perl -pE 's/^\[[^]]*\]
*//' < /var/log/Xorg.0.log-4.9)", i.e. "-" means "4.8" and "+" means
"4.9".

--- /proc/self/fd/11	2017-01-15 01:12:37.722837254 +0100
+++ /proc/self/fd/12	2017-01-15 01:12:37.718837243 +0100
@@ -3,8 +3,8 @@
 Release Date: 2016-11-15
 X Protocol Version 11, Revision 0
 Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
-Current Operating System: Linux c6 4.8.0-2-grsec-amd64 #1 SMP Debian 4.8.15-2+grsec201701031913+1 (2017-01-06) x86_64
-Kernel command line: BOOT_IMAGE=/vmlinuz-4.8.0-2-grsec-amd64 root=/dev/mapper/vgc6-root ro quiet
+Current Operating System: Linux c6 4.9.0-1-amd64 #1 SMP Debian 4.9.2-2 (2017-01-12) x86_64
+Kernel command line: BOOT_IMAGE=/vmlinuz-4.9.0-1-amd64 root=/dev/mapper/vgc6-root ro quiet
 Build Date: 16 December 2016  07:30:27PM
 xorg-server 2:1.19.0-3 (https://www.debian.org/support) 
 Current version of pixman: 0.34.0
@@ -13,7 +13,7 @@
 Markers: (--) probed, (**) from config file, (==) default setting,
 	(++) from command line, (!!) notice, (II) informational,
 	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
-(==) Log file: "/var/log/Xorg.0.log", Time: Sat Jan 14 21:53:48 2017
+(==) Log file: "/var/log/Xorg.0.log", Time: Sat Jan 14 22:05:23 2017
 (==) Using system config directory "/usr/share/X11/xorg.conf.d"
 (==) No Layout section.  Using the first Screen section.
 (==) No screen section available. Using defaults.
@@ -38,7 +38,7 @@
 (==) ModulePath set to "/usr/lib/xorg/modules"
 (II) The server relies on udev to provide the list of input devices.
 	If no devices become available, reconfigure udev or disable AutoAddDevices.
-(II) Loader magic: 0x2808e31e00
+(II) Loader magic: 0x5607fd35ee00
 (II) Module ABI versions:
 	X.Org ANSI C Emulation: 0.4
 	X.Org Video Driver: 23.0
@@ -47,7 +47,6 @@
 (++) using VT number 7
 
 (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
-(II) xfree86: Adding drm device (/dev/dri/card0)
 (--) PCI:*(0:0:2:0) 8086:1912:1849:1912 rev 6, Mem @ 0xde00/16777216, 0xc000/268435456, I/O @ 0xf000/64, BIOS @ 0x/131072
 (II) LoadModule: "glx"
 (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
@@ -79,540 +78,65 @@
 (II) modesetting: Driver for Modesetting Kernel Drivers: kms
 (II) FBDEV: driver for framebuffer: fbdev
 (II) VESA: driver for VESA chipsets: vesa
-xf86EnableIOPorts: failed to set IOPL for I/O (No such device)
-(II) modeset(0): using drv /dev/dri/card0
-(WW) Falling back to old probe method for fbdev
+(EE) open /dev/dri/card0: No such file or directory
+(WW) Falling back to old probe method for modesetting
+(EE) open /dev/dri/card0: No such file or directory
 (II) Loading sub module "fbdevhw"
 (II) LoadModule: "fbdevhw"
 (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
 (II) Module fbdevhw: vendor="X.Org Foundation"
 	compiled for 1.19.0, module version = 0.0.2
 	ABI class: X.Org Video Driver, version 23.0
+(**) FBDEV(1): claimed PCI slot 0@0:2:0
+(II) FBDEV(1): using default device
 (WW) Falling back to old probe method for vesa
-(II) modeset(0): Creating default Display subsection in Screen section
+(EE) Screen 0 deleted because of no matching config section.
+(II) UnloadModule: "modesetting"
+(II) FBDEV(0): Creating default Display subsection in Screen section
 	"Default Screen 

Bug#850733: [Reportbug-maint] Bug#850733: Crashes with "TypeError: GObject.__init__() takes exactly 0 arguments (1 given)"

[Simon McVittie]

On Sun, 15 Jan 2017 at 00:32:15 +, Simon McVittie wrote:
> I suspect that last line was intended to be a GetMultilinePage wrapper.
> But I can't actually test this, because the only use of get_multiline()
> does have ENTER in its prompt (and it crashes - fix attached).

On testing it by hacking the prompt for Cc in advanced mode to not include
ENTER, sure enough it doesn't work.

S
>From 247e9aefba791ba037ac737cc061d5d445a86a15 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sun, 15 Jan 2017 00:35:21 +
Subject: [PATCH 15/15] gtk2_ui: fix unbound local variable in GetMultilinePage

---
 reportbug/ui/gtk2_ui.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/reportbug/ui/gtk2_ui.py b/reportbug/ui/gtk2_ui.py
index 0388668..8b41ae8 100644
--- a/reportbug/ui/gtk2_ui.py
+++ b/reportbug/ui/gtk2_ui.py
@@ -790,7 +790,7 @@ class GetMultilinePage(Page):
 vbox.pack_start(self.label, False, True, 0)
 
 self.view = Gtk.TextView()
-self.buffer = view.get_buffer()
+self.buffer = self.view.get_buffer()
 scrolled = create_scrollable(self.view)
 vbox.pack_start(scrolled, True, True, 0)
 return vbox
-- 
2.11.0

Bug#851441: dpkg-source --commit infinite loop asking for patch name

[James Clarke]

On Sat, Jan 14, 2017 at 11:30:54PM +, Ian Jackson wrote:
> Package: dpkg-source
> Version: 1.18.15
>
> To reproduce:
>   git clone git://git.chiark.greenend.org.uk/~ianmdlvl/dgit.git
>   cd dgit
>   git checkout for-dpkg-source.2017-01-14
>   DGIT_DRS_DEBUG=2 DGIT_TEST_DEBUG=-D tests/using-intree \
>   tests/tests/gitattributes 2>&1 
> You may need to install the test dependencies:
>   dgit, dgit-infrastructure, devscripts, debhelper (>=8), fakeroot, 
> build-essential
>
> Observed behaviour:
>   dpkg-source goes into an infinite loop printing
>  Enter the desired patch name:
>
> Expected behaviour:
>   It should stop with some kind of error message, or perhaps
>   carry on with a default patch name

Easier reproduction: run dpkg-source --commit in any 2.0 or 3.0 (quilt)
package tree that has been modified, then send an EOF at the prompt.

This is a pretty simple bug, too: Dpkg/Source/Package/V2.pm:725 (sub
do_commit) loops until it gets a valid string from stdin, but treats an
undefined value as invalid, rather than aborting or using a default
patch name.

Regards,
James

Bug#850733: [Reportbug-maint] Bug#850733: Crashes with "TypeError: GObject.__init__() takes exactly 0 arguments (1 given)"

[James Clarke]

On 14 Jan 2017, at 23:55, Simon McVittie  wrote:
> On Sat, 14 Jan 2017 at 23:24:25 +, James Clarke wrote:
>> I'm not sure why it's working for me and not you.
> 
> Ah, that would be because I have reportbug configured to use mutt to write
> the actual bug report, and that disables the Gtk editor.

That explains it. I thought I had configured it to use a different editor
too... maybe I just manually edited afterwards. I tend to write the emails
directly in mutt.

> Your change looks fine. I also needed to use the attached.

I don't have gtkspellcheck installed so I didn't hit that.

Thanks,
James

Bug#850733: [Reportbug-maint] Bug#850733: Crashes with "TypeError: GObject.__init__() takes exactly 0 arguments (1 given)"

[Simon McVittie]

On Sat, 14 Jan 2017 at 23:24:25 +, James Clarke wrote:
> I'm not sure why it's working for me and not you.

Ah, that would be because I have reportbug configured to use mutt to write
the actual bug report, and that disables the Gtk editor.

Your change looks fine. I also needed to use the attached.

S
>From dd64cbfb2d8f8b4c816cffdd43d9be41c1aedfa3 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sat, 14 Jan 2017 23:48:12 +
Subject: [PATCH 7/8] gtk2_ui: lazily import gtkspellcheck from the UI thread

If we import it globally (in the reportbug thread), we get:

sqlite3.ProgrammingError: SQLite objects created in a thread can only be
used in that same thread. The object was created in thread id
 and this is thread id 
---
 reportbug/ui/gtk2_ui.py | 21 ++---
 1 file changed, 14 insertions(+), 7 deletions(-)

diff --git a/reportbug/ui/gtk2_ui.py b/reportbug/ui/gtk2_ui.py
index 5a5e92c..ca89eaf 100644
--- a/reportbug/ui/gtk2_ui.py
+++ b/reportbug/ui/gtk2_ui.py
@@ -47,11 +47,7 @@ except ImportError:
 
 global Vte
 
-try:
-import gtkspellcheck
-has_spell = True
-except:
-has_spell = False
+gtkspellcheck = None
 
 #gtk.set_interactive(0)
 Gdk.threads_init()
@@ -1309,7 +1305,18 @@ class EditorPage(Page):
 self.view = Gtk.TextView()
 self.view.modify_font(Pango.FontDescription("Monospace"))
 self.view.set_wrap_mode(Gtk.WrapMode.WORD)
-if has_spell:
+
+# We have to do the import in the UI thread, because it loads a
+# SQLite database at import time, and the Python SQLite bindings
+# don't allow transferring a SQLite handle between threads.
+global gtkspellcheck
+if gtkspellcheck is None:
+try:
+import gtkspellcheck
+except:
+gtkspellcheck = NotImplemented
+
+if gtkspellcheck is not NotImplemented:
 gtkspellcheck.SpellChecker(self.view)
 self.info_buffer = self.view.get_buffer()
 scrolled = create_scrollable(self.view)
@@ -1323,7 +1330,7 @@ class EditorPage(Page):
 expander.add(scrolled)
 vbox.pack_start(expander, False, True, 0)
 
-if not has_spell:
+if gtkspellcheck is NotImplemented:
 box = Gtk.EventBox()
 label = Gtk.Label("Please install python-gtkspellcheck to enable spell checking")
 label.set_use_markup(True)
-- 
2.11.0

Bug#850733: [Reportbug-maint] Bug#850733: Crashes with "TypeError: GObject.__init__() takes exactly 0 arguments (1 given)"

[James Clarke]

On 14 Jan 2017, at 23:24, James Clarke  wrote:
> On Sat, Jan 14, 2017 at 09:38:53PM +, Simon McVittie wrote:
>> On Sat, 14 Jan 2017 at 19:50:17 +, Simon McVittie wrote:
 On Mon, Jan 9, 2017 at 2:21 PM, James Clarke  wrote:
> I would guess there are some UI
> interactions happening not on the main UI thread.
>>> 
>>> I found a couple of places where this was done wrong. I'll send a
>>> patch series soon.
>> 
>> Try these?
>> 
>> They seem to work here, but I didn't get this crash myself (in GNOME
>> on Wayland with Gtk's standard Adwaita theme, if it matters) so I can't
>> say whether they are a complete fix.
> 
> I'm not sure why it's working for me and not you. That fixes the
> segfault, but I still get:
> 
>> Traceback (most recent call last):
>>  File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 692, in 
>> validate
>>value = self.get_value()
>>  File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 1355, 
>> in get_value
>>self.info_buffer.get_end_iter())
>> TypeError: Gtk.TextBuffer.get_text() takes exactly 4 arguments (3 given)
> 
> After applying the attached patch on top of your series, I can get to
> the editor, type, and progress to the final submission options screen. I
> have yet to use it to report an actual bug, but it looks promising :)

It seems GetMultilinePage's get_value also has a call to get_text without
the extra parameter, but a grep for GetMultilinePage only shows the class
definition, with no uses... deletion candidate? From what I can tell, it
was added in 3739eb89aa, but even then it wasn't being used by anything?
Anyway, if it needs to stay, the extra True needs to be added to it too.

Regards,
James

Bug#851439: packages.debian.org: [PATCH] Inaccurate message on package download page (right click needed in some browsers)

[Laura Arjona Reina]

Package: www.debian.org
Followup-For: Bug #851439

I'm attaching a patch that removes the paragraph about the need of right click
in some browsers.
I can commit it in some days, if nobody disagrees.
Cheers



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

Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
>From 8b537184c2f1ba7b122ba800ddd81a38e8c5ef24 Mon Sep 17 00:00:00 2001
From: Laura Arjona Reina 
Date: Sun, 15 Jan 2017 00:23:59 +0100
Subject: [PATCH] Remove old reference to need of right click in browsers to
 download. Closes: #851439

---
 templates/html/download.tmpl | 2 --
 1 file changed, 2 deletions(-)

diff --git a/templates/html/download.tmpl b/templates/html/download.tmpl
index 82509a8..b6c8e05 100644
--- a/templates/html/download.tmpl
+++ b/templates/html/download.tmpl
@@ -97,8 +97,6 @@ deb http://[% mirrors.$archive.europa.0 %] [% suite %] main [% section
 	port.name, organisation, port.name, port.url, port.name) %]
 [% END %]
 
-[% g('Note that in some browsers you will need to tell your browser you want the file saved to a file. For example, in Firefox or Mozilla, you should hold the Shift key when you click on the URL.') %]
-
 
 
 [% g('More information on %s:', filename.file) %]
-- 
2.1.4

Bug#851441: dpkg-source --commit infinite loop asking for patch name

[Ian Jackson]

Package: dpkg-source
Version: 1.18.15

To reproduce:
  git clone git://git.chiark.greenend.org.uk/~ianmdlvl/dgit.git
  cd dgit
  git checkout for-dpkg-source.2017-01-14
  DGIT_DRS_DEBUG=2 DGIT_TEST_DEBUG=-D tests/using-intree \
  tests/tests/gitattributes 2>&1 =8), fakeroot, 
build-essential

Observed behaviour:
  dpkg-source goes into an infinite loop printing
 Enter the desired patch name:

Expected behaviour:
  It should stop with some kind of error message, or perhaps
  carry on with a default patch name

Ian.

-- 
Ian Jackson    These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#851440: sign_and_send_pubkey: signing failed: agent refused operation

[Dominik George]

Package: gnupg-agent
Version: 2.1.17-4
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Suddenly, using gpg-agent as ssh-agent with authentication subkeys
stopped working:

sign_and_send_pubkey: signing failed: agent refused operation

I can, however, still see my authentication subkeys in ssh-add -l:

% ssh-add -l
4096 SHA256:VCiRCk+EswSfauAe4hYWweglX6WqsIrtU08PGr7LL38 (none) (RSA)
256 SHA256:SqObMOMaC5eckW3g9nvbOnQljUjjq8Hez5U0TcQqIwM (none) (ED25519)

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

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

Versions of packages gnupg-agent depends on:
ii  libassuan0  2.4.3-2
ii  libc6   2.24-8
ii  libgcrypt20 1.7.5-3
ii  libgpg-error0   1.26-1
ii  libnpth01.3-1
ii  libreadline77.0-1
ii  pinentry-qt [pinentry]  1.0.0-1

Versions of packages gnupg-agent recommends:
ii  gnupg  2.1.17-4
ii  gpgsm  2.1.17-4

Versions of packages gnupg-agent suggests:
ii  scdaemon  2.1.17-4

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJ4BAEBCABiFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlh6srIxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxIcbmlrQG5h
dHVyYWxuZXQuZGUACgkQt5o8FqDE8paqMRAAwwZeMyM0qVbdMiKzMkH9ld9/m9My
VOij/H5wV7aa/N6uUn6JRYQ3AWW9+HtxzG4fReinh8Fr+0v/2q1MSZgeK7hD7Pvt
Mo+68nm75L6fMO0mFHBaF62n573XswVknZiqguaA2SCqaTrLkl6AdigGHujJX27H
BARM75TTO00P0GRYf+EptWmdHFry+SwvBPs7h46m2aRIB9Yim2nwmwYh0FYxH6J1
BJxKu5PbRd8mSw/wXrLlA/XCXpCNvvTjK3YMy6KfwrjxVhUdFzDkhGbGniCmlivd
Ey2PxlvgW4Xn18BpwFv7d7Pwjb3kw0unHqG+TMLsbeqykAikVzRgxMOxWOSCJvjf
96KyUjiyAynOU72RnYcE5G4+27sezZCWHNWmBw8LZ9AuqN3WlZO14EEjR9BYoypr
mY3J0gQNaq/9UFIhFqt3qeN2fwuQd8+imqN3GLAgpeOF2fsk6MG70itEKrOMl/Zo
yqUPqPgWFXAtnfr4jf4rVmvcQdDREIrqi91UVDJPYASvimAOYbvRj7ZwLEJDTq/p
a/gRK9C++3DuoGGEeogDDIHXcY4s3L+CCouSGydWbS9YjI9itlp740VV/+yXX6IC
RtW9IV26BgI1GRLvs05moq2oE+tfbjwmhaKkp6s0lu+gedcYOfAPIay02rwXJR/r
R600rwhwZl8GC7I=
=cRUe
-END PGP SIGNATURE-

Bug#850733: [Reportbug-maint] Bug#850733: Crashes with "TypeError: GObject.__init__() takes exactly 0 arguments (1 given)"

[James Clarke]

On Sat, Jan 14, 2017 at 09:38:53PM +, Simon McVittie wrote:
> On Sat, 14 Jan 2017 at 19:50:17 +, Simon McVittie wrote:
> > > On Mon, Jan 9, 2017 at 2:21 PM, James Clarke  wrote:
> > > > I would guess there are some UI
> > > > interactions happening not on the main UI thread.
> > 
> > I found a couple of places where this was done wrong. I'll send a
> > patch series soon.
> 
> Try these?
> 
> They seem to work here, but I didn't get this crash myself (in GNOME
> on Wayland with Gtk's standard Adwaita theme, if it matters) so I can't
> say whether they are a complete fix.

I'm not sure why it's working for me and not you. That fixes the
segfault, but I still get:

> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 692, in 
> validate
> value = self.get_value()
>   File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 1355, 
> in get_value
> self.info_buffer.get_end_iter())
> TypeError: Gtk.TextBuffer.get_text() takes exactly 4 arguments (3 given)

After applying the attached patch on top of your series, I can get to
the editor, type, and progress to the final submission options screen. I
have yet to use it to report an actual bug, but it looks promising :)

Regards,
James
>From c88fbf24a8fb7f77d4ffa6b9b46d6d2e09912345 Mon Sep 17 00:00:00 2001
From: James Clarke 
Date: Sat, 14 Jan 2017 23:15:49 +
Subject: [PATCH] gtk2_ui: Gtk.TextBuffer.get_text needs include_hidden_chars
 given

This used to default to True with PyGTK, but needs to be given
explicitly with gi.
---
 reportbug/ui/gtk2_ui.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/reportbug/ui/gtk2_ui.py b/reportbug/ui/gtk2_ui.py
index 5a5e92c..c29ec7e 100644
--- a/reportbug/ui/gtk2_ui.py
+++ b/reportbug/ui/gtk2_ui.py
@@ -1352,7 +1352,8 @@ class EditorPage(Page):
 def get_value(self):
 _assert_context(ui_context)
 info = self.info_buffer.get_text(self.info_buffer.get_start_iter(),
- self.info_buffer.get_end_iter())
+ self.info_buffer.get_end_iter(),
+ True)
 if not info.strip():
 return None
 subject = self.subject.get_text().strip()
-- 
2.11.0

Bug#851439: packages.debian.org: Inaccurate message on package download page (right click needed in some browsers)

[Laura Arjona Reina]

Package: www.debian.org
Severity: normal
User: www.debian@packages.debian.org
Usertags: packages

Resending to the BTS so it doesn't get lost.

Cheers

-- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona


 Mensaje reenviado 
Asunto: Inaccurate message on package download page
Resent-Date: Thu, 28 Jul 2016 15:03:13 + (UTC)
Resent-From: debian-...@lists.debian.org
Fecha: Thu, 28 Jul 2016 15:45:26 +0100
De: George Bateman 
Para: debian-...@lists.debian.org

Dear Debian Website mailing list,

At (eg.) https://packages.debian.org/wheezy/all/libtomcat7-java/download,
the following message is displayed:

>Note that in some browsers you will need to tell your browser you want the 
>file saved to a file. For example, in Firefox or Mozilla, you should hold the 
>Shift key when you click on the URL.

This isn't true any more; please could it be removed?

Thanks,

George Bateman.

Bug#851438: Please restart journald on upgrades

[Jarek Kamiński]

Package: systemd
Version: 232-8
Severity: minor
File: /lib/systemd/systemd-journald

Hello,

W dniu 14.01.2017 o 18:58, Michael Biebl pisze:
> Am 14.01.2017 um 18:40 schrieb Jarek Kamiński:
>> #771122 explains that journald can't be restarted, as all stdout and
>> stderr fds used by daemons to log would be lost. If I understand
>> correctly, that was fixed in v219[1] though:
>>> * systemd now provides a way to store file descriptors
>>>   per-service in PID 1.This is useful for daemons to ensure
>>>   that fds they require are not lost during a daemon
>>>   restart. The fds are passed to the deamon on the next
>>>   invocation in the same way socket activation fds are
>>>   passed. This is now used by journald to ensure that the
>>>   various sockets connected to all the system's stdout/stderr
>>>   are not lost when journald is restarted. File descriptors
>>>   may be stored in PID 1 via the sd_pid_notify_with_fds() API,
>>>   an extension to sd_notify(). Note that a limit is enforced
>>>   on the number of fds a service can store in PID 1, and it
>>>   defaults to 0, so that no fds may be stored, unless this is
>>>   explicitly turned on.
>>
>> Is it related, or am I mixing things? If yes, can #771122 be reverted?
> 
> It should be possible now, I think. That said, I feel a bit uneasy doing
> that so close to the freeze.
> Doing it early in the buster release cycle seems safer.

Fully agreed.

> Would you mind filing a bug report for that?

Certainly.


Thanks!


-- Package-specific info:

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

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2) (ignored: LC_ALL
set to pl_PL)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser 3.115
ii  libacl1 2.2.52-3
ii  libapparmor12.10.95-8
ii  libaudit1   1:2.6.7-1
ii  libblkid1   2.29-1
ii  libc6   2.24-8
ii  libcap2 1:2.25-1
ii  libcryptsetup4  2:1.7.3-3
ii  libgcrypt20 1.7.5-2
ii  libgpg-error0   1.26-1
ii  libidn111.33-1
ii  libip4tc0   1.6.0+snapshot20161117-4
ii  libkmod223-2
ii  liblz4-10.0~r131-2
ii  liblzma55.2.2-1.2
ii  libmount1   2.29-1
ii  libpam0g1.1.8-3.4
ii  libseccomp2 2.3.1-2.1
ii  libselinux1 2.6-3
ii  libsystemd0 232-8
ii  mount   2.29-1
ii  util-linux  2.29-1

Versions of packages systemd recommends:
ii  dbus1.10.14-1
ii  libpam-systemd  232-8

Versions of packages systemd suggests:
ii  policykit-10.105-17
pn  systemd-container  
ii  systemd-ui 3-4

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.126
ii  udev 232-8

-- no debconf information

-- 
pozdr(); // Jarek




signature.asc
Description: OpenPGP digital signature

Bug#851427: sysvinit makes /dev/shm a symlink to /run/shm, should be other way round

[Simon McVittie]

On Sat, 14 Jan 2017 at 21:50:43 +, Holger Levsen wrote:
> On Sat, Jan 14, 2017 at 09:15:42PM +, Simon McVittie wrote:
> > Expected result:
> > 
> > * /dev/shm is a tmpfs
> 
> and /dev/shm is owned by root:root and has perms 1755?

No, it should have the ownership and permissions that are the default
for tmpfs filesystems (root:root 01777), the same as a correctly
configured /tmp or /var/tmp.

$ ls -ld /dev/shm
drwxrwxrwt 2 root root 220 Jan 14 20:44 /dev/shm

Regards,
S

Bug#851437: astroplan: FTBFS (requires Internet to build)

[Santiago Vila]

Package: src:astroplan
Version: 0.2-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
Freezing version number to astroplan/version.py
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild base:184: /usr/bin/python setup.py build 

[... snipped ...]

response = self._open(req, data)

  File "/usr/lib/python2.7/urllib2.py", line 447, in _open
'_open', req)

  File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain
result = func(*args)

  File "/usr/lib/python2.7/urllib2.py", line 1228, in http_open
return self.do_open(httplib.HTTPConnection, req)

  File "/usr/lib/python2.7/urllib2.py", line 1195, in do_open
h.request(req.get_method(), req.get_selector(), req.data, headers)

  File "/usr/lib/python2.7/httplib.py", line 1042, in request
self._send_request(method, url, body, headers)

  File "/usr/lib/python2.7/httplib.py", line 1082, in _send_request
self.endheaders(body)

  File "/usr/lib/python2.7/httplib.py", line 1038, in endheaders
self._send_output(message_body)

  File "/usr/lib/python2.7/httplib.py", line 882, in _send_output
self.send(msg)

  File "/usr/lib/python2.7/httplib.py", line 844, in send
self.connect()

  File "/usr/lib/python2.7/httplib.py", line 821, in connect
self.timeout, self.source_address)

  File "/usr/lib/python2.7/dist-packages/astropy/tests/disable_internet.py", 
line 75, in new_function
"requested host was: {0}".format(host))

IOError: An attempt was made to connect to the internet by a test that was not 
marked `remote_data`. The requested host was: data.astropy.org

/tmp/astroplan-test-w5w2JP/docs/tutorials/summer_triangle.rst:49: 
UnexpectedException
= 60 failed, 31 passed, 1 skipped, 2 error in 1871.77 seconds ==
debian/rules:27: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:12: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


I've put a build log here:

https://people.debian.org/~sanvila/build-logs/astroplan/

The error message speaks by itself:

IOError: An attempt was made to connect to the internet by a test that was not 
marked `remote_data`. The requested host was: data.astropy.org

Packages must not require Internet connectivity to build.

Thanks.

Bug#851436: nmu: llvm-defaults_1:3.8-34

[Adrian Bunk]

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

nmu llvm-defaults_1:3.8-34 . armel . unstable . -m "llvm-toolchain-3.8 is now 
available on armel"

Bug#851435: unblock: duperemove/0.11~beta4-1

[Adam Borowski]

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

Hi!
Would it be possible to unblock duperemove for stretch?  It was uploaded 2¾
days before the 10-day deadline, but somehow it sat in NEW until now.  Yeah,
it's our fault -- the ITP was worked on by multiple non-DDs, with large gaps
between any actions; when I finally intervened and forced the issue it was
close to the deadline, and ftpmasters don't operate on a FIFO.

Multiple people expressed interest in this package; I for one use it
heavily.  Without it, those elebenty billion deduplicators we have in the
archive are mostly worthless -- all they can do is to notify the user or at
most hard- or symlink duplicates which tends to be a pretty bad idea
(modifying one of the copies tramples all others).  On the other hand, BTRFS
(since kernel 3.13) and XFS (experimentally in 4.9) have in-kernel support
for CoW shared extents.  That support needs an userspace tool.

Thus, it'd be nice if you allowed it in.


unblock duperemove/0.11~beta4-1

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

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

Bug#851434: phantomjs: crash with [FATAL] Could not initialize GLX when rendering geotraceroute

[Petter Reinholdtsen]

Package: phantomjs
Version: 2.1.1+dfsg-2

When trying to render geotraceroute.com as PDF, I get this crash in
phantomjs:

  2017-01-14T23:48:10 [FATAL] Could not initialize GLX
  PhantomJS has crashed. Please read the bug reporting guide at
   and file a bug report.
  Aborted

I expected it to render the web page to file instead of crashing.  To
reproduce, run

  sudo apt install xvfb phantomjs
  wget 
https://raw.githubusercontent.com/ariya/phantomjs/master/examples/render_multi_url.js
  xvfb-run phantomjs --ssl-protocol any render_multi_url.js 
'geotraceroute.com/index.php?node=4=www.google-analytics.com'

-- 
Happy hacking
Petter Reinholdtsen

Bug#850948: needrestart: Hangs in apt hook with a zombie

[Thomas Liske]

Re,


Jonas Smedegaard  writes:

>> I think the severity of this bug should be lowered to important since 
>> there is no policy violation of needrestart at all.
>
> I think it is quite worrisome if simply installing (not actively using)
> needrestart inside a chroot spawns daemons - and that is not treated as 
> serious (no matter framed by some geleral Debian Policy wording).

Needrestart was never written nor designed to run within a chroot. This
use case does not make any sense at all. Just don't do it (should be
added to the README ;-) .


>> I (upstream) or Patrick (maintainer) could add a patch to needrestart 
>> to use invoke-rc.d instead of the service command. That would only be 
>> a Debian specific workaround.
>
> Please do.  That sounds like it would solve this issue.

ACK


>> Neighter do I. Another workaround could be to change needrestart to 
>> list only mode within piupart using some local config snippet as they 
>> do for policy-rc.d.
>
> If I understand you corretly, that you suggest to invent a mechanism 
> essentially doing the same as policy-rc.d, then I see no need for that: 
> Please respect the already existing policy-rc.d instead.
>
> I guess what you seek is a solution not specific to Debian - and find 
> that wuite sensible.  I suspect, however, that there is no XDG or 
> similar more generic standard for respecting deployment-specific hooks - 
> which is really what policy-rc.d is about (not only chroot support).

Yes, since I'm upstream it is required that needrestart focuses an
generic approach. A patch kept in Pattricks packaging VCS should keep
the balance.


HTH,
Thomas

-- 

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

Bug#851433: mydumper: FTBFS: .../man1/mydumper.1: No such file or directory

[Aaron M. Ucko]

Source: mydumper
Version: 0.9.1-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Thanks for taking care of #850847/#850969.

Alas, builds of mydumper covering only only its architecture-dependent
binary packages (as on the autobuilders, or with dpkg-buildpackage -B)
are still failing:

 dh_installman -a
  debian/tmp/usr/share/man/man1/mydumper.1: No such file or directory at 
/usr/bin/dh_installman line 131.
  debian/rules:13: recipe for target 'binary-arch' failed
  make: *** [binary-arch] Error 2

Could you please take a look?

Thanks!

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

Bug#851026: ffmpeg: FTBFS: ffconf.bVIjAhhQ.c:2: undefined reference to `dlopen'

[Adrian Bunk]

Control: retitle -1 ffmpeg: ChromaprintContext FTBFS
Control: forwarded -1 https://trac.ffmpeg.org/ticket/5997
Control: tags -1 fixed-upstream

On Sat, Jan 14, 2017 at 06:47:02AM +0100, Carl Eugen Hoyos wrote:
> The relevant lines in the build log are afaict:
> 
> src/libavformat/chromaprint.c: In function 'write_packet':
> src/libavformat/chromaprint.c:113:1: error: control reaches end of non-void 
> function [-Werror=return-type]
>  }
>  ^
> 
> The function looks like this:
> 
> static int write_packet(AVFormatContext *s, AVPacket *pkt)
> {
> ChromaprintMuxContext *cpr = s->priv_data;
> return chromaprint_feed(cpr->ctx, pkt->data, pkt->size / 2) ? 0 : 
> AVERROR(EINVAL);
> }
> 
> I guess this is a compiler bug.

No, you should only look at the first compile error in that file:

src/libavformat/chromaprint.c:42:24: error: field 'ctx' has incomplete type
 ChromaprintContext ctx;
^~~
This is the actual error.

Whatever the compiler comes up with for cpr->ctx in the place you quoted 
might be garbage, but at that point it is already game over.

Upstream fix:
  
http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=581f93f37ef2e7a00662828ed0348d1edb9041fe

> Carl Eugen

cu
Adrian

-- 

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

Bug#851241: packages.debian.org: update hangs every now and then

[Laura Arjona Reina]

Package: www.debian.org
User: www.debian@packages.debian.org
Usertags: packages

thanks

-- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona

Bug#754242: (no subject)

[Patrick Schleizer]

Is this actually implemented despite saying wontfix?

Acquire::BlockDotOnion "false";

allows connecting to http://asdfasdf.onion without tor://

Thank you for implementing 'Acquire::BlockDotOnion "false";' - very
useful for Whonix!

Best regards,
Patrick

Bug#838360: needrestart: Wants to restart services, even if these were restarted already

[Thomas Liske]

tags 838360 upstream fixed-upstream
thanks

Hi Georg,

"ge...@riseup.net"  writes:

> Hi Patrick,
>
> On 16-09-20 12:12:50, ge...@riseup.net wrote:
>> needrestart wants to restart {ganeti,ssh}.service, even if these were
>> restarted already:

the repeating restart of ssh.service might be triggered by one or more
running user session. Do you have libpam-systemd installed and enabled?
There is an issue in needrestart assuming that libpam-systemd (if systemd is 
used at
all) is used to assign user sessions processes into according
cgroups. If libpam-systemd is not running all session process are part
of sshd's cgroup, so needrestart suggests to restart ssh.service (which
won't affect any session processes). A new config option has been
added[1] to address this option.

[1]
https://github.com/liske/needrestart/commit/6a29143e1c6439e1f851b172e468aeef17b261b2


The repeating restart of ganeti.service might be triggered by some
ganeti child processes managing virtual machines. It might not be
possible to fix this problem without stopping the VMs.


HTH,
Thomas

-- 

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

Bug#851337: [pkg-wine-party] Bug#851337: Desktop Integration Folder paths resets on upgrade

[Michael Gilbert]

control: tag -1 moreinfo

On Sat, Jan 14, 2017 at 7:47 AM, Jens Reyer wrote:
> What exactly did you set, which is then reverted by Wine?
>
> ftr, recently we (only) changed something in this area in
> wine-development 2.0~rc4-1 / wine 1.8.6-2, so I don't think there's a
> regression in the Debian packaging itself.

I don't think this is the same issue.  I think he is referring to the
Desktop Integration settings available from winecfg (like themes and
folders I guess), not default file associations.

Best wishes,
Mike

Bug#851427: [Pkg-sysvinit-devel] Bug#851427: sysvinit makes /dev/shm a symlink to /run/shm, should be other way round

[Henrique de Moraes Holschuh]

On Sat, 14 Jan 2017, Holger Levsen wrote:
> On Sat, Jan 14, 2017 at 09:50:43PM +, Holger Levsen wrote:
> > and /dev/shm is owned by root:root and has perms 1755?
> 
> actually I have both 1777 and 0755 here, which of the two is correct or
> are both fine??

It has to be mode 01777, read+write.  Otherwise, it breaks glibc's shm_*
and SuS/POSIX compliance, and you get to keep the pieces of everthing
that will fail in both subtle, and very non-subtle ways.

Such as Google Chrome / chromium.

-- 
  Henrique Holschuh

Bug#790454: Fix from Ubuntu for netmrg

[Andreas Beckmann]

Control: tag -1 pending

On Mon, 21 Nov 2016 22:53:43 +0200 Adrian Bunk  wrote:
> The fix I found in Ubuntu for these bugs is attached.

Thanks.

I uploaded a NMU to DELAYED/2 fixing these issues. Please let me know if
I should delay it longer.

 netmrg (0.20-7.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * PHP 7.0 transition, based on patch from Ubuntu.  (Closes: #821537)
   * Switch Build-Depends to default-libmysqlclient-dev.  (Closes: #790454)
   * Switch Depends/Recommends to default-mysql-* | virtual-mysql-*.
 (Closes: #848476, #732898)
   * Add Brazilian Portuguese (pr_BR) debconf translation, thanks to
 José de Figueiredo.  (Closes: #771130)
   * Add missing build-{arch,indep} targets.
   * Build with autotools-dev to update config.{sub,guess}.
   * Switch to source format 3.0 (quilt).


Andreas

Bug#851432: installation-reports: reboot or halt hangs after unmounting all disks on active update task

[Rudy Zijlstra]

Package: installation-reports
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
   ==> Any reboot or halt triggers it
   ==> at shutdown system goes through all needed actions, unmounts the
   remote and local disks, then waits for an update action to finish
   (which can never finish as all disks have been unmounted). The stated
   wait time is 15 min some seconds. (but did not wait for that).  
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   ==> "solved" by doing a HW switch off (4 seconds power button)
   * What was the outcome of this action?
   ==> system power-off
   * What outcome did you expect instead?
   ==> reboot should reboot, and not result in long wait time. 

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


-- Package-specific info:

Boot method: network for install, after that local disk (SDD)
Image version: netboot builddate 11 nov 2016
Date: Installed nov 2016. with all updates since. 

Machine: Dell precision T7500
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems: install seems OK, shutdown is KO



System is normally either active or in RAM-sleep. Did not do shutdown,
as system typically crashed before. When starting to debug that, and
looking for other ongoing issues, the problem on shutdown was found. 

The ongoing issue is not related, and seems an initialisation issue of
the graphics subsystem. 

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20161101-00:08"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux cenedra 4.7.0-1-amd64 #1 SMP Debian 4.7.8-1 (2016-10-19) x86_64 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 5520 I/O Hub to ESI 
Port [8086:3406] (rev 13)
lspci -knn: Subsystem: Dell Device [1028:026d]
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub 
PCI Express Root Port 1 [8086:3408] (rev 13)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub 
PCI Express Root Port 3 [8086:340a] (rev 13)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:07.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub 
PCI Express Root Port 7 [8086:340e] (rev 13)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:14.0 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub 
System Management Registers [8086:342e] (rev 13)
lspci -knn: Subsystem: Device [0028:006d]
lspci -knn: 00:14.1 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub 
GPIO and Scratch Pad Registers [8086:3422] (rev 13)
lspci -knn: Subsystem: Device [0028:006d]
lspci -knn: 00:14.2 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub 
Control Status and RAS Registers [8086:3423] (rev 13)
lspci -knn: Subsystem: Device [0028:006d]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801JI (ICH10 
Family) USB UHCI Controller #4 [8086:3a37]
lspci -knn: Subsystem: Dell Device [1028:026d]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801JI (ICH10 
Family) USB UHCI Controller #5 [8086:3a38]
lspci -knn: Subsystem: Dell Device [1028:026d]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1a.2 USB controller [0c03]: Intel Corporation 82801JI (ICH10 
Family) USB UHCI Controller #6 [8086:3a39]
lspci -knn: Subsystem: Dell Device [1028:026d]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801JI (ICH10 
Family) USB2 EHCI Controller #2 [8086:3a3c]
lspci -knn: Subsystem: Dell Device [1028:026d]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 

Bug#755992: proftpd-mod-clamav: error: Can not stat file (9): Bad file descriptor

[Hilmar Preuße]

On 13.01.2017 20:28, Adrian Bunk wrote:

Hi,

> Has there been any feedback regarding whether this might already be fixed?
> 
> Currently this bug would prevent that proftpd-mod-clamav could be in 
> stretch.
> 
OK, I'm able to reproduce the bug, I'll try to test the fix.

Hilmar
-- 
http://www.hilmar-preusse.de.vu/   #206401 http://counter.li.org

Bug#851427: sysvinit makes /dev/shm a symlink to /run/shm, should be other way round

[Holger Levsen]

On Sat, Jan 14, 2017 at 09:50:43PM +, Holger Levsen wrote:
> and /dev/shm is owned by root:root and has perms 1755?

actually I have both 1777 and 0755 here, which of the two is correct or
are both fine??


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#851022: The most important part of the error message

[Adrian Bunk]

Control: retitle -1 libpqxx FTBFS: sed: character class syntax is [[:space:]], 
not [:space:]

The most important part of the error message is:

...
checking for PQexec in -lpq... yes
sed: character class syntax is [[:space:]], not [:space:]
checking for correct C++ linkage of basic libpq functions... configure: error: 
Linking a call to libpq failed in C++, even though it succeeded in C.  If your
C and C++ compilers are very different beasts, this may mean that we do not have
the right options for linking with it after all.
...


The root cause is that sed recently became more strict, and the 
following sed call in configure.ac now fails resulting in empty LIBS:

  LIBS="`echo "$LIBS" | sed -e 's/-lpq[[:space:]]*[[:space:]]-lpq\>/-lpq/g'`"



cu
Adrian

-- 

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

Bug#851431: ITP: bart-view -- Image viewer for multi-dimensional data (add-on to BART)

[Martin Uecker]

Package: wnpp
Severity: wishlist
Owner: Martin Uecker 

* Package name: bart-view
  Version : 0.0.01
  Upstream Author : Martin Uecker 
* URL : https://github.com/mrirecon/view/
* License : BSD
  Programming Lang: C
  Description : Image viewer for multi-dimensional data (add-on to BART)

This is a viewer for multi-dimensional complex-valued
data. It is useful as an add-on to the Berkeley Advanced
Reconstruction Toolbox (BART) for computational Magnetic
Resonance Imaging which has been packaged for Debian
already. This package will be maintained as part of
the Debian Med team.

Bug#851427: sysvinit makes /dev/shm a symlink to /run/shm, should be other way round

[Holger Levsen]

Hi Simon,

thanks for this bug report, much appreciated!

On Sat, Jan 14, 2017 at 09:15:42PM +, Simon McVittie wrote:
> Expected result:
> 
> * /dev/shm is a tmpfs

and /dev/shm is owned by root:root and has perms 1755?


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#814030: Security flaw fixed in version 6.2.0

[Moritz Mühlenhoff]

On Mon, Jan 09, 2017 at 09:39:30PM +0100, Raphael Hertzog wrote:
> Hi everybody,
> 
> On Thu, 05 Jan 2017, Raphael Hertzog wrote:
> > CCing upstream author for confirmation. Nicola we are trying to understand
> > what security fix went into tcpdf 6.2.0. The bug is private on
> > sourceforge, could you make it public now?
> 
> The upstream bug is now public:
> https://sourceforge.net/p/tcpdf/bugs/1005/

Since K_TCPDF_CALLS_IN_HTML defaults to jessie, we should fix this in jessie.

Could someone of the maintainers prepare an update?

Cheers,
Moritz

Bug#851413: gertty: Uninstallable in Debian Unstable

[Piotr Ożarowski]

[Axel Beckert, 2017-01-14]
> gertty is uninstallable in Debian Unstable (but not in Debian Testing)
> since it depends on python-sqlalchemy (< 1.1), but Debian Unstable
> currently contains python-sqlalchemy at version 1.1.4+ds1-1.

I uploaded rebuilt version to DELAYED/2

I don't know why I missed this one, it's in my SA 1.1 transition file...
but marked as one without << 1.1...

> This is probably also the reason why python-sqlalchemy >> 1.1 never
> migrated to testing despite it's considered a valid candidate:
> https://qa.debian.org/excuses.php?package=sqlalchemy

yeah, this page is not really helpful...

Bug#851430: CVE-2016-9571

[Moritz Muehlenhoff]

Source: resteasy
Severity: important
Tags: security

There's not a great of information on this one other then this Red Hat 
bugtracker entry:
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-9571

Cheers,
Moritz

Bug#850948: needrestart: Hangs in apt hook with a zombie

[Jonas Smedegaard]

Quoting Thomas Liske (2017-01-14 16:09:26)
> I've replied to #850948 where I think you wan't to discuss the 
> piuparts-needrestart-* issue.

Thanks for correcting my error (I realized it only after posting)


> Jonas Smedegaard  writes:
> >> Maybe it is just a debconf frontend issue? In cases needrestart 
> >> does seems to hang it trackes down to:
> >> 
> >> - daemons hangig while restarting them (init scripts)
> >
> > Agreed. This would imply that either piuparts fail to setup 
> > policy-rc.d appropriately, or that needrestart ignores policy-rc.d.  
> > The latter is a Policy violation.
> 
> You are referencing Debian Policy's section 9.3.3 [1]?

Correct.  Sorry for sloppily not mentioning it explicitly.


[...]
> I think the severity of this bug should be lowered to important since 
> there is no policy violation of needrestart at all.

I think it is quite worrisome if simply installing (not actively using)
needrestart inside a chroot spawns daemons - and that is not treated as 
serious (no matter framed by some geleral Debian Policy wording).


> needrestart uses the service command of init-system-helpers to restart 
> daemons. A quick look into /usr/sbin/service shows that if there is no 
> systemd the service command calls the init script directly (look at 
> run_via_sysvinit).

Thanks for clarifying.


> So you might consider to move the bug to init-system-helpers.

No need: init-system-helpers provide tools both to interacti via 
policy-rc.d and tools to bypass that layer - which is perfectly fine.  
Problem is when package install routines (even if indirectly - e.g. 
using inappropriate helper tools) bypass policy-rc.d.


> I (upstream) or Patrick (maintainer) could add a patch to needrestart 
> to use invoke-rc.d instead of the service command. That would only be 
> a Debian specific workaround.

Please do.  That sounds like it would solve this issue.


[...]
> Needrestart's use of debconf should be aware if piuparts already tells 
> debconf that it is called non-interactive. So it seems to hang due to 
> some init scripts problem as discussed above.

Agreed.


>>> Feel free to open a new bug to needrestart to track down this issue.
>>
>> Thanks for the suggestion.  I am not familiar with piupart I will 
>> likely not do so, but welcome others to pick up where I left.
>
> Neighter do I. Another workaround could be to change needrestart to 
> list only mode within piupart using some local config snippet as they 
> do for policy-rc.d.

If I understand you corretly, that you suggest to invent a mechanism 
essentially doing the same as policy-rc.d, then I see no need for that: 
Please respect the already existing policy-rc.d instead.

I guess what you seek is a solution not specific to Debian - and find 
that wuite sensible.  I suspect, however, that there is no XDG or 
similar more generic standard for respecting deployment-specific hooks - 
which is really what policy-rc.d is about (not only chroot support).


Regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#848592: cable usbblaster ID 09fb:6001 Altera Blaster

[Geert Stappers]

On Sat, Jan 14, 2017 at 08:25:14AM +0100, Geert Stappers wrote:
> 
> `lsusb` shows 'Bus 001 Device 016: ID 09fb:6001 Altera Blaster'
> 
> In urtjag is the response on `cable usbblaster':
> error: Couldn't connect to suitable USB device.
> error: ftdi/ftd2xx error: ftdi_usb_open_desc() failed: device not found

That "not found" was more "permission denied" ...


> So now I looking for messages like
> * Works for me
> * Works for me after ...addition_tweaking...
> * Used to work, that was with version ...  and kernel ...

Works after `sudo chgrp my_group /dev/bus/usb/001/042`,
which is something that can a "udev rule" much better.


Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#850733: [Reportbug-maint] Bug#850733: Crashes with "TypeError: GObject.__init__() takes exactly 0 arguments (1 given)"

[Simon McVittie]

On Sat, 14 Jan 2017 at 19:50:17 +, Simon McVittie wrote:
> > On Mon, Jan 9, 2017 at 2:21 PM, James Clarke  wrote:
> > > I would guess there are some UI
> > > interactions happening not on the main UI thread.
> 
> I found a couple of places where this was done wrong. I'll send a
> patch series soon.

Try these?

They seem to work here, but I didn't get this crash myself (in GNOME
on Wayland with Gtk's standard Adwaita theme, if it matters) so I can't
say whether they are a complete fix.

S
>From 60718170c596a5daf38c84214941a69c3b05c897 Mon Sep 17 00:00:00 2001
From: James Clarke 
Date: Mon, 9 Jan 2017 18:48:43 +
Subject: [PATCH 1/6] gtk2_ui: Avoid deprecated Gtk.Expander(str) constructor
 not exposed by gi

---
 reportbug/ui/gtk2_ui.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/reportbug/ui/gtk2_ui.py b/reportbug/ui/gtk2_ui.py
index 2829cf0..e9099c2 100644
--- a/reportbug/ui/gtk2_ui.py
+++ b/reportbug/ui/gtk2_ui.py
@@ -191,7 +191,7 @@ class ExceptionDialog(CustomDialog):
 
 def setup_dialog(self, vbox, tb):
 # The traceback
-expander = Gtk.Expander("More details")
+expander = Gtk.Expander.new_with_mnemonic("More details")
 vbox.pack_start(expander, True, True, 0)
 
 view = Gtk.TextView()
@@ -1170,7 +1170,7 @@ class EditorPage(Page):
 scrolled = create_scrollable(self.view)
 vbox.pack_start(scrolled, True, True, 0)
 
-expander = Gtk.Expander("Other system information")
+expander = Gtk.Expander.new_with_mnemonic("Other system information")
 view = Gtk.TextView()
 view.set_editable(False)
 self.others_buffer = view.get_buffer()
-- 
2.11.0

>From 533afffd7494d9257f89c4195d631b412a579a3f Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sat, 14 Jan 2017 17:14:54 +
Subject: [PATCH 2/6] gtk2_ui: Consistently call set_progress_label in UI
 thread

Previously, log_message() would call it from the reportbug thread.
---
 reportbug/ui/gtk2_ui.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/reportbug/ui/gtk2_ui.py b/reportbug/ui/gtk2_ui.py
index e9099c2..0d3f14e 100644
--- a/reportbug/ui/gtk2_ui.py
+++ b/reportbug/ui/gtk2_ui.py
@@ -1448,6 +1448,7 @@ class ReportbugAssistant(Gtk.Assistant):
 if self.showing_page == self.progress_page:
 self.set_current_page(page.page_num)
 
+# Called in UI thread
 def set_progress_label(self, text, *args, **kwargs):
 self.progress_page.set_label(text % args)
 
@@ -1520,8 +1521,9 @@ class GetFilenameDialog(ReportbugConnector, Gtk.FileChooserDialog):
 self.show_all()
 
 
+# Called in reportbug thread
 def log_message(*args, **kwargs):
-return assistant.set_progress_label(*args, **kwargs)
+application.run_once_in_main_thread(assistant.set_progress_label, *args, **kwargs)
 
 
 def select_multiple(*args, **kwargs):
-- 
2.11.0

>From 2294fc174ef4e6ca97c36b040700b10cf510cec0 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sat, 14 Jan 2017 18:32:11 +
Subject: [PATCH 3/6] gtk2_ui: Create a GLib main-context for each thread

A main context represents a set of callbacks, sockets and other
event sources, and each main-context can be acquired (owned) by at
most one thread at a time. A main-context is normally owned by the
same thread for its entire lifetime, and that's how we use them here.

The "thread-default main context" is how GLib and GIO track the thread
in which the callback for an async operation should be called; we don't
actually use any GIO async operations at the moment, but it's a good
idea to set it correctly. This also gives us the ability to give better
diagnostics than just asserting is_owner(), because we can show both
the expected thread and the actual thread in the assertion message.
---
 reportbug/ui/gtk2_ui.py | 28 ++--
 1 file changed, 26 insertions(+), 2 deletions(-)

diff --git a/reportbug/ui/gtk2_ui.py b/reportbug/ui/gtk2_ui.py
index 0d3f14e..87a8d79 100644
--- a/reportbug/ui/gtk2_ui.py
+++ b/reportbug/ui/gtk2_ui.py
@@ -71,7 +71,7 @@ from reportbug.urlutils import launch_browser
 ISATTY = True
 DEBIAN_LOGO = "/usr/share/pixmaps/debian-logo.png"
 
-global application, assistant, report_message
+global application, assistant, report_message, reportbug_context, ui_context
 
 # Utilities
 
@@ -347,6 +347,7 @@ class BugPage(Gtk.EventBox, threading.Thread):
 threading.Thread.__init__(self)
 Gtk.EventBox.__init__(self)
 self.setDaemon(True)
+self.context = GLib.MainContext()
 
 self.dialog = dialog
 self.assistant = assistant
@@ -371,6 +372,11 @@ class BugPage(Gtk.EventBox, threading.Thread):
 self.add(vbox)
 
 def run(self):
+if not self.context.acquire():
+# should be impossible
+raise AssertionError('Could not acquire my own main-context')
+

Bug#851429: installation-reports: mounting CD fails on qemu-system-aarch64

[Adam Borowski]

Package: installation-reports
Severity: normal

Hi!
I'm afraid that regular arm64 d-i images fail to detect qemu's CD-ROM, and
there's apparently no way to direct it to load udebs from a network mirror
like mini.iso does.  On the other hand, installation with mini.iso works
well.

The failing step is "Detecting hardware to find CD-ROM drives".

CD=debian-stretch-DI-rc1-arm64-netinst.iso
NET="-net bridge -net nic"

qemu-system-aarch64 -machine virt -nographic -cpu cortex-a57 \
 -bios /usr/share/qemu-efi/QEMU_EFI.fd -m 2048 $NET \
 -drive file="$DISK",cache=writeback,index=0,media=disk,format=raw \
 -drive file="$CD",cache=writeback,index=1,media=cdrom -boot d


Host's data:
qemu-*   1:2.8+dfsg-1 amd64
qemu-efi 0~20161202.7bbe0b3e-1
-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#782434: [pkg-dhcp-devel] Bug#782434: isc-dhcp-server: DHCP server segfaults when exceeding lease limit

[Michael Gilbert]

control: tag -1 moreinfo

On Sun, Apr 12, 2015 at 4:14 AM, Jose Miguel Sanchez Ales wrote:
> The dhcpd server dies with segmentation fault when exceeds the lease
> limit in a class.

A similar problem with lease limits on 64-bit systems was fixed in the
client in 4.3.3-2, bug #795227.  Did that also fix this?

Best wishes,
Mike

Bug#175064: DocBook XML conversion is read with this script

[Simon McVittie]

On Sat, 14 Jan 2017 at 11:32:09 -0800, Russ Allbery wrote:
> Bill Allombert  writes:
> 
> > I am concerned that DocBook is much too complex to be used for Debian
> > policy.  We need to people to write patches without trouble and we do
> > not have many editors available for fixing the XML. Debiandoc-SGML
> > virtue is that it is simple.
[...]
> The alternative, I guess, would be to use Markdown for the whole thing,
> but I think it's worthwhile to have sections and internal links and a bit
> more formatting than Markdown gives us.

asciidoc, then? Or Markdown with pandoc extensions?

asciidoc is another wiki-like language, but has semantics defined in
terms of Docbook rather than HTML.

Pandoc's Markdown dialect includes footnotes and explicit or implicit
anchors in headings.

S

Bug#851428: urjtag: access permission on device

[Geert Stappers]

Package: urjtag
Version: 0.10+r2052

Given:
* JTAG adapter is a hardware device.
* device is from root and not world accessable
* urjtag is run as non-root user

Problem:
* user has no access permisson on device


Wanted:
* access permission on device for non-root user


Possible solution:
* using udev rules for setting group to non-root on device
* place the user in that group


Next problem:
* conflict with a package like OpenOCD


Solution:
* Working together with other electronic packages as OpenOCD and sigrok.


Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#851427: sysvinit makes /dev/shm a symlink to /run/shm, should be other way round

[Simon McVittie]

Package: initscripts
Version: 2.88dsf-59.8
Severity: normal

On Sat, 14 Jan 2017 at 11:00:51 -0800, Steve Langasek wrote:
> On Fri, Jan 13, 2017 at 03:54:30PM +, Simon McVittie wrote:
> > If I'm reading the initscripts code correctly, sysvinit does the reverse
> > by default, for some reason (/run/shm is the mount point and /dev/shm the
> > symlink). I think the motivation might have been to be able to use the
> > same tmpfs for /run and /run/shm,
> 
> I recall this being a misguided attempt to move it out of /dev "because it's
> not a device".  The migration did not go well, especially in the face of
> chroots that need to have it mounted, and since systemd did not handle this
> the same way sysvinit had, we effectively now have a mess in the other
> direction.
> 
> We should fix it so that everything again treats /dev/shm as the mountpoint.

Let's have a bug number for that, then. Please escalate its severity if you
think that's correct.

Steps to reproduce:

* install Debian (I used vmdebootstrap according to autopkgtest-virt-qemu(1))
* apt install sysvinit-core
* reboot
* mount
* ls -al /dev/shm /root/shm

Expected result:

* /dev/shm is a tmpfs
* /run/shm is a symlink with target /dev/shm

Actual result:

* /dev/shm is a symlink with target /run/shm
* /run/shm is a tmpfs



This might also be related to #697003, #818442.

Bug#813718: Patch in the MRIcron FTBFS bug

[Michalis Kamburelis]

2017-01-14 16:54 GMT+01:00 Andreas Tille :
> Hi Adrian,
>
> On Fri, Jan 13, 2017 at 05:29:01PM +0200, Adrian Bunk wrote:
>> I saw you were just working on the MRIcron package.
>>
>> Can you take a look at the patch in
>>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813718#40
>> ?
>
> Thanks for the ping.  I tried to turn the suggested patch into a quilt
> patch which I commited to Git:
>
>
> https://anonscm.debian.org/git/debian-med/mricron.git/tree/debian/patches/stricter_fpc.patch
>
> Unfortunately there is a Build-Problem:
>
> (3104) Compiling /build/mricron-0.20140804.1~dfsg.1/common/dialogsx.pas
> /build/mricron-0.20140804.1~dfsg.1/common/dialogsx.pas(75,42) Error: (5000) 
> Identifier not found "Dialogs"
> /build/mricron-0.20140804.1~dfsg.1/common/dialogsx.pas(75,42) Fatal: (2003) 
> Syntax error, ";" expected but "." found
> Fatal: (1018) Compilation aborted
> Error: /usr/bin/ppcx64 returned an error exitcode
> Error: (lazarus) Compile Project, Target: dcm2nii: stopped with exit code 256
> ERROR: failed compiling of project 
> /build/mricron-0.20140804.1~dfsg.1/dcm2nii/dcm2nii.lpi
> debian/rules:10: recipe for target 'override_dh_auto_build' failed
>
>
> I admit I can not see where a "." mit be but a ";" is expected but
> the patch seems to have some issue.
>

My patch from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813718#40
assumes that the "Dialogs" unit is in the uses clause. But the
"Dialogs" unit is in the uses clause only when the symbol "GUI" is
defined at compilation. I didn't test the compilation without the GUI
symbol.

I'm attaching a fixed version of the patch:)

Regards,
Michalis
diff -ur mricron-0.20140804.1~dfsg.1/common/dialogsx.pas mricron-0.20140804.1~dfsg.2/common/dialogsx.pas
--- common/dialogsx.pas	2014-01-28 18:06:18.0 +0100
+++ common/dialogsx.pas	2017-01-14 22:07:02.839240363 +0100
@@ -68,13 +68,44 @@
 
 function MsgDlg(const Msg: string; DlgType: TMsgDlgType; Buttons: TMsgDlgButtons; HelpCtx: Longint): Word;
 {$IFDEF GUI}
+
+  { Convert our TMsgDlgButtons type to Dialogs.TMsgDlgButtons type
+in a type-safe manner. Do not assume that memory layout matches between
+- TMsgDlgButtons and Dialogs.TMsgDlgButtons, or
+- TMsgDlgBtn and Dialogs.TMsgDlgBtn. 
+  }
+  function MsgDlgButtonsConvertToStandard(
+const Buttons: TMsgDlgButtons): Dialogs.TMsgDlgButtons;
+  var
+B: TMsgDlgBtn;
+  begin
+Result := [];
+for B := Low(B) to High(B) do
+  if B in Buttons then
+{ convert our TMsgDlgBtn to Dialogs.TMsgDlgBtn type }
+case B of
+  mbYes : Include(Result, Dialogs.mbYes );
+  mbNo  : Include(Result, Dialogs.mbNo  );
+  mbOK  : Include(Result, Dialogs.mbOK  );
+  mbCancel  : Include(Result, Dialogs.mbCancel  );
+  mbAbort   : Include(Result, Dialogs.mbAbort   );
+  mbRetry   : Include(Result, Dialogs.mbRetry   );
+  mbIgnore  : Include(Result, Dialogs.mbIgnore  );
+  mbAll : Include(Result, Dialogs.mbAll );
+  mbNoToAll : Include(Result, Dialogs.mbNoToAll );
+  mbYesToAll: Include(Result, Dialogs.mbYesToAll);
+  mbHelp: Include(Result, Dialogs.mbHelp);
+  else raise Exception.Create('Unsupported TMsgDlgBtn value');
+end;
+  end;
+
 var
lDlgType : Dialogs.TMsgDlgType;
lButtons: Dialogs.TMsgDlgButtons;
 
 begin
   lDlgType :=  Dialogs.TMsgDlgType(DlgType);
-  lButtons:= Dialogs.TMsgDlgButtons(Buttons);
+  lButtons:= MsgDlgButtonsConvertToStandard(Buttons);
   result := MessageDlg(Msg, lDlgType, lButtons,HelpCtx);
 {$ELSE}
 begin

Bug#844165: virtualbox: Virtualbox & guests windows moving "alone" when mouse pointer moves.

[Awtul]

Just a correction. In my previous message I meant:

"As I said, the bug is only present under openbox if autohide feature is 
enabled for tint2 and only virtualbox is affected. Not reproducible under

fluxbox, fvwm and xfce using xfce4-panel and fbpanel or tint2 with autohide 
features enabled (for xfce4-panel, fbpanel and tint2)."

Cheers,

Awtul

Bug#822372: mouse settings have no effect with Cirque Touchpad (was: Bug#825100: Problems with mouse and touchpad settings)

[Sébastien Villemot]

On Mon, 6 Jun 2016 10:02:35 +0200 Emilio Pozuelo Monfort  wrote:

> On 06/06/16 03:04, Leandro Doctors wrote:
> > Dear all.
> > 
> > (CC: to #823372, #821352 and #825100 since I believe all these bugs
> > should be merged.)
> 
> Sorry, there are two bugs here.
> 
> #825100, #821352 are about the ability to configure edge-scrolling,
which was
> removed in GNOME 3.20.
> 
> #822081, #822372 are about the inability to configure the touchpad
when
> synaptics is used.
> 
> I believe your problem is the latter, and you just need to uninstall
> xserver-xorg-input-synaptics and restart your session to get (most)
settings back.

In my case, uninstalling xserver-xorg-input-synaptics does not fix the
issue. Touchpad setting are still not available, and the mouse speed
setting does not work.

My feeling is that this is an issue specific to my hardware (Cirque
Touchpad), that does not seem properly supported by libinput.

Hence I am not sure that the present bug (#822372) is the same as
#822081; the two should probably be unmerged.


-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594



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

Bug#844165: virtualbox: Virtualbox & guests windows moving "alone" when mouse pointer moves.

[Awtul]

Hi,

The bug is now partially solved with Tint2 version 0.12.12-2 updated today 
thanks to upstream patch,

but the bug still reproducible combining openbox (3.6.1-4), tint2 (0.12.12-1) 
and virtualbox (5.1.12-dfsg-2)

using default configs for all of them except "autohide" feature enabled for 
tint2 (not enabled by default - 

tint2rc ---> Panel ---> autohide=1 for enable it). So I attached default 
tint2rc (autohide enabled) and default

openbox rc.xml.

Pretty sure you will be able to reproduce using the following Debian version of:

-openbox: 3.6.1-4

-tint2: 0.12.12-1

-virtualbox: 5.1.12-dfsg-2

as other people have done according to 
https://gitlab.com/o9000/tint2/issues/619   and   
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849228

As I said, the bug is only present under openbox if autohide feature is enabled 
for tint2 and only virtualbox is affected. Not reproducible under

fluxbox, fvwm and xfce using xfce4-panel and fbpanel or tint2 with autohide 
feature disabled.

According to tint2 upstream, the bug "is in either openbox or virtualbox".

Please, let me know if you need more info.

Regards,

Awtul


http://openbox.org/3.4/rc; 
xmlns:xi="http://www.w3.org/2001/XInclude;>
  
10
20
  
  
yes

no

yes

no

200

no

  
  
Smart

yes

Primary

1

  
  
Clearlooks
NLIMC

yes
yes

  sans
  8
  
  bold
  
  normal
  


  sans
  8
  
  bold
  
  normal
  


  sans
  9
  
  normal
  
  normal
  


  sans
  9
  
  normal
  
  normal
  


  sans
  9
  
  bold
  
  normal
  


  sans
  9
  
  bold
  
  normal
  

  
  

4
1

  

875

  
  
yes
Nonpixel

Center


  
  10
  
  10
  

  
  
  
0
0
0
0
  
  
TopLeft

0
0
no
Above

Vertical

no
300

300

Middle

  
  
C-g


  
left
no
  


  
right
no
  


  
up
no
  


  
down
no
  


  
left
no
  


  
right
no
  


  
up
no
  


  
down
no
  


  
1
  


  
2
  


  
3
  


  
4
  


  



  


  
  
  


  
client-menu
  



  
scrot -s
  



  

  
  
  

  


  

  
  
  

  


  
yes
yes

  
  
  

  



  
right
  


  
left
  


  
up
  


  
down
  



  

  true
  Konqueror

kfmclient openProfile filemanagement
  



  
scrot
  

  
  
1

500

400

false


  


  
  

  
  

  
  



  
  

  
  



  
  

  previous

  
  

  next

  
  

  previous

  
  

  next

  
  

  previous

  
  

  next

  


  

  
  

  
  

  no
  




  

  
  

  yes
  


  

  


  



  
  



  
  



  client-menu

  


  

  top

  


  

  left

  


  

  right

  


  

  bottom

  
  



  client-menu

  


  



  
  

  


  


  
  


  
  


  


  




  client-menu

  

Bug#851426: upgrade-reports: afther update reinstalling again. inaf to go back to WIN.

[actualization]

Package: upgrade-reports
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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



-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

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

Bug#851425: initramfs-tools: multiple bugs in initramfs and the booting experience, preventing use of computer

[Testing Reportbug]

Package: initramfs-tools
Version: 0.120+deb8u2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

x

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 17M Jan 14 11:39 /boot/initrd.img-3.16.0-4-amd64
-rw-r--r-- 1 root root 13M May 18  2016 /boot/initrd.img-3.2.0-4-amd64
-rw--- 1 root root 11M Jul 25  2015 /boot/initrd.img-3.2.0-4-amd64--backup
-rw-r--r-- 1 root root 18M Jan 14 11:38 /boot/initrd.img-4.5.0-0.bpo.2-amd64
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 
root=UUID=cc8d4477-498a-429c-a651-44c1f7bddd69 ro

-- resume
RESUME=/dev/mapper/sda7_crypt
-- /proc/filesystems
ext3
ext2
ext4

-- lsmod
Module  Size  Used by
pci_stub   12429  1 
vboxpci22921  0 
vboxnetadp 25540  0 
vboxnetflt 27648  0 
vboxdrv   379703  3 vboxnetadp,vboxnetflt,vboxpci
xt_tcpudp  12527  50 
ip6table_mangle12540  0 
iptable_nat12646  1 
nf_conntrack_ipv4  18448  14 
nf_defrag_ipv4 12483  1 nf_conntrack_ipv4
nf_nat_ipv412912  1 iptable_nat
nf_nat 18241  2 nf_nat_ipv4,iptable_nat
xt_TCPMSS  12588  2 
xt_LOG 17171  42 
ipt_REJECT 12465  0 
iptable_mangle 12536  0 
xt_multiport   12518  0 
xt_state   12503  0 
xt_limit   12601  43 
xt_conntrack   12681  13 
nf_conntrack_ftp   16783  0 
nf_conntrack   87424  7 
nf_nat,xt_state,nf_nat_ipv4,xt_conntrack,nf_conntrack_ftp,iptable_nat,nf_conntrack_ipv4
ip6table_filter12540  1 
ip6_tables 25820  2 ip6table_filter,ip6table_mangle
iptable_filter 12536  1 
ip_tables  21711  3 iptable_filter,iptable_mangle,iptable_nat
x_tables   27399  14 
ip6table_filter,ip6table_mangle,ip_tables,xt_tcpudp,xt_limit,xt_state,xt_conntrack,xt_LOG,xt_multiport,iptable_filter,xt_TCPMSS,ipt_REJECT,iptable_mangle,ip6_tables
binfmt_misc16949  1 
snd_hda_codec_analog13795  1 
snd_hda_codec_generic63181  1 snd_hda_codec_analog
xts12679  2 
gf128mul   12970  1 xts
iTCO_wdt   12831  0 
iTCO_vendor_support12649  1 iTCO_wdt
ppdev  16782  0 
radeon   1349406  2 
snd_hda_intel  26407  1 
dcdbas 13313  0 
snd_hda_controller 26646  1 snd_hda_intel
snd_hda_codec 104500  4 
snd_hda_codec_generic,snd_hda_intel,snd_hda_controller,snd_hda_codec_analog
ttm77862  1 radeon
snd_hwdep  13148  1 snd_hda_codec
snd_pcm_oss44798  0 
coretemp   12820  0 
snd_mixer_oss  22042  1 snd_pcm_oss
evdev  17445  14 
snd_pcm88662  4 
snd_pcm_oss,snd_hda_codec,snd_hda_intel,snd_hda_controller
kvm_intel 139156  0 
drm_kms_helper 49210  1 radeon
kvm   392897  1 kvm_intel
snd_timer  26720  1 snd_pcm
drm   249998  5 ttm,drm_kms_helper,radeon
snd65338  11 
snd_pcm_oss,snd_hwdep,snd_timer,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,snd_mixer_oss,snd_hda_codec_analog
serio_raw  12849  0 
pcspkr 12595  0 
i2c_algo_bit   12751  1 radeon
soundcore  13026  2 snd,snd_hda_codec
i2c_i801   16965  0 
lpc_ich20768  0 
mfd_core   12601  1 lpc_ich
tpm_tis17231  0 
tpm31511  1 tpm_tis
mei_me 17941  0 
mei74977  1 mei_me
parport_pc 26300  0 
parport35749  2 ppdev,parport_pc
shpchp 31121  0 
button 12944  0 
processor  28221  0 
thermal_sys27642  1 processor
i2c_dev13057  0 
i2c_core   46012  6 
drm,i2c_i801,i2c_dev,drm_kms_helper,i2c_algo_bit,radeon
loop   26605  0 
autofs435529  2 
ext4  477894  5 
crc16  12343  1 ext4
mbcache17171  1 ext4
jbd2   82514  1 ext4
sha256_ssse3   25692  6 
sha256_generic 16804  1 sha256_ssse3
ecb12737  0 
cbc12696  3 
algif_skcipher 17349  0 
af_alg 13034  1 algif_skcipher
dm_crypt   22595  5 
dm_mod 89405  11 dm_crypt
hid_generic12393  0 
usbhid 44460  0 
hid   102264  2 hid_generic,usbhid
ses   

Bug#850885: apache2: Using dwww, fails with internal server error when trying to access /usr/share/doc

[Stefan Fritsch]

reassign 850885 dwww
severity 850885 grave
tags 850885 patch
thanks

On Thursday, 12 January 2017 06:50:16 CET Arjan Opmeer wrote:
> > is correct however, here's the HTTP header part:
> > Content-type: text/html
> > Last modified: Tue Dec 13 14:16:35 2016
> > Content-Disposition: inline; filename="index.html"
> 
> Actually the header should read "Last-Modified" (note spelling). After
> patching the dwww script to emit the correct header the error no longer
> occurs with Apache. Therefore I believe the bug should be reassigned to
> dwww.

Exactly. "Last modified" (with a space) is not HTTP compliant as a header name.

> I will reply to the corresponding dwww bug report (#781987) with the fix I
> applied to the dwww script.

I don't think the original issue reported in #781987 is the same issue. But 
the patch you posted there looks ok for this issue (#850885). I am therefore 
reassigning the bug to dwww.

Cheers,
Stefan

Bug#851285: Fails to import lbzip2: failed to generate delta

[Guido Günther]

Hi Tomasz,

On Fri, Jan 13, 2017 at 10:43:38PM +0100, Tomasz Buchert wrote:
> On 13/01/17 18:56, Guido Günther wrote:
> > On Fri, Jan 13, 2017 at 06:21:24PM +0100, Guido Günther wrote:
> > > Package: pristine-tar
> > > Version: 1.37
> > > Severity: normal
> > > 
> > > Hi,
> > > importing lbzip2 fails with:
> > >
> > [...]
> > 
> > libxfce4ui, nsis, thunar-volman, thunar, tumbler, xfce4-cpufreq-plugin,
> > xfce4-dev-tools, xfce4-dict, xfce4-weather-plugin fail with the same
> > error so I'm not filing separate reports.
> > Cheers,
> >  -- Guido
> 
> I didn't check all of these packages, but indeed they do not
> reproduce.  However, note that these packages do not use pristine-tar
> (or gbp, if my sample was significant), so nobody ever tried to
> reproduce their tarballs with pristine-tar. :)

They do not now but they might in the future. My goal here was to make

gbp import-dsc 

work for all packages in the archive [0] for several reasons:

* Making it simple to work on random packages by doing a gbp import-dsc
  (e.g. for security work or doing NMUs) - this requires an exact
  tarball.
* Turning on pristine-tar by default in gbp as discussed at DC16[1]
* (Potentially) create a history of "gbp import-dscs --debsnap" where
  others can fetch from (this doesn't require a reproducible tarball for
  all versions as long as we let users know (e.g. for ancient versions)

pristine-tar actually already does an amazing job. We only have about 20
packages failing and the packages in this this bug form the largest
group (followed by some others that claim to have too big delta, these
are usually quiet big packages like chromium and I need to investigate
this separtely).

> The issue we have here is that it is impossible to "gbp import-dsc
> ..." a random package, because in general tarballs are messy. Correct
> me if I'm wrong, but it looks as if you don't intend to actually keep
> pristine-tar for anything more than temporary help to use gbp with the
> imported package?

We're also using pristine-tar in team maintained packages to have one
repository we can work from. This makes it a lot simpler for people not
that familiar with Debian to just git clone one thing and then have
everything at hand.

> If the answer is yes, then I propose to introduce a mode to
> pristine-tar that will: (1) try to import the given tarball using the
> standard machinery and if that fails (2) import the final tarball
> as-it-is. This sort of defeats the whole idea of pristine-tar, but may
> be a necessary evil for this sort of use and will not harm anyone if
> people won't use it to actually import tarballs into long-term package
> repositories. What do you think?

I intend to make "gbp import-dsc" just continue the import and warn the
user (#851287) when pristine-tar fails. For import-orig we already roll
back all changes and let the user retry without --pristine-tar.
So I don't think adding this mode to pristine-tar is really necessary,
if we can't create a long term stable tarball we'd better fail and let
the user cover up with e.g. by using origtgz.

Thanks a lot for a having a look at all the bugs I filed (and for
maintaining pristine-tar)!
Cheers,
 -- Guido

[0] 
http://lists.alioth.debian.org/pipermail/vcs-pkg-discuss/2017-January/000954.html
[1] http://lists.sigxcpu.org/pipermail/git-buildpackage/2016-July/000143.html

Bug#849769: [mipsel]: string.sub sometimes returns incorrect slice

[James McCoy]

On Fri, Dec 30, 2016 at 02:25:27PM -0500, James McCoy wrote:
> Neovim's test suite was periodically failing on mipsel and after looking
> into it, it turns out that luajit sometimes incorrectly handles
> str:sub(i, j).

This was fixed upstream in 62af10152433c45e5d83e442538fabf1f57f189b.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#850733: [Reportbug-maint] Bug#850733: Crashes with "TypeError: GObject.__init__() takes exactly 0 arguments (1 given)"

[Simon McVittie]

On Fri, 13 Jan 2017 at 15:18:26 -0500, Sandro Tosi wrote:
> would you be able to have a look at this? it looks like it's the
> current issue every user of the GTK interface has.

The patch from James looks correct, please apply it.

> On Mon, Jan 9, 2017 at 2:21 PM, James Clarke  wrote:
> > This is because, while a lot of the constructors have been overridden by
> > PyGObject to handle the deprecated form, Expander has not been
> > overridden, so the explicit form has to be used. Patch attached.
> > Unfortunately, after applying it, it now crashes with:
> >
> >> (reportbug:15278): Gtk-CRITICAL **: gtk_text_attributes_ref: assertion
> >> 'values != NULL' failed
> >>
> >> (reportbug:15278): Gtk-CRITICAL **: gtk_text_attributes_ref: assertion
> >> 'values != NULL' failed
> >>
> >> (reportbug:15278): Pango-CRITICAL **: pango_layout_new: assertion
> >> 'context != NULL' failed
> >> [1]15278 segmentation fault  reportbug src:pymongo

I don't get this error myself (with
"PYTHONPATH=. bin/reportbug -u gtk2 reportbug").

> > I would guess there are some UI
> > interactions happening not on the main UI thread.

I found a couple of places where this was done wrong. I'll send a
patch series soon.

S

Bug#844505: Fix for 844505

[Rami, Elias]

Hello,

because disper stopped working for me, i did this to get it back to work
like a charm again

best regards,
-- 
_
Elias RAMI Unwired Networks GmbH
Support & Technik Tel: +436608377160
elias.r...@unwired.at   www.unwired.at
Gonzagagasse 11/25 1010 Vienna, Austria
diff -Nru disper-0.3.1/debian/changelog disper-0.3.1/debian/changelog
--- disper-0.3.1/debian/changelog   2014-10-16 09:23:03.0 +0200
+++ disper-0.3.1/debian/changelog   2017-01-14 20:24:09.0 +0100
@@ -1,3 +1,10 @@
+disper (0.3.1-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Bugfix for #844505 which made disper unusable for me
+
+ -- Elias Rami   Sat, 14 Jan 2017 20:24:09 +0100
+
 disper (0.3.1-2) unstable; urgency=medium
 
   * Move maintainership of package to the Python Applications Packaging Team
diff -Nru disper-0.3.1/debian/patches/fix-844505 
disper-0.3.1/debian/patches/fix-844505
--- disper-0.3.1/debian/patches/fix-844505  1970-01-01 01:00:00.0 
+0100
+++ disper-0.3.1/debian/patches/fix-844505  2017-01-14 20:24:09.0 
+0100
@@ -0,0 +1,71 @@
+Description: Load 2 Libarys and define return types
+
+ load libXrandr.so.2 and libX11.so.6 and define
+ xopendisplay = xlib.XOpenDisplay and
+ xrrqueryversion = rr.XRRQueryVersion
+
+ disper (0.3.1-2.1) UNRELEASED; urgency=medium
+ .
+   * Non-maintainer upload.
+   * Bugfix for #844505 which made disper unusable for me
+Author: Elias Rami 
+
+---
+The information above should follow the Patch Tagging Guidelines, please
+checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
+are templates for supplementary fields that you might want to add:
+
+Origin: debian/strech disper 0.3.1-2 
http://http.debian.net/debian/pool/main/d/disper/disper_0.3.1-2.dsc
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844505
+Forwarded: 
+Last-Update: 2017-01-14
+
+--- disper-0.3.1.orig/src/xrandr/__init__.py
 disper-0.3.1/src/xrandr/__init__.py
+@@ -41,6 +41,19 @@ __status__ = "development"
+ from ctypes import *
+ import os
+ 
++class Display(Structure):
++pass
++
++xlib = cdll.LoadLibrary("libX11.so.6")
++rr = cdll.LoadLibrary("libXrandr.so.2")
++
++xopendisplay = xlib.XOpenDisplay
++xopendisplay.restype = POINTER(Display)
++xopendisplay.argtypes = [c_char_p]
++
++xrrqueryversion = rr.XRRQueryVersion
++xrrqueryversion.restype = c_int
++xrrqueryversion.argtypes = [POINTER(Display), POINTER(c_int), POINTER(c_int)]
+ 
+ RR_ROTATE_0 = 1
+ RR_ROTATE_90 = 2
+@@ -86,7 +99,7 @@ from core import Screen, xlib, rr
+ def get_current_display():
+ """Returns the currently used display"""
+ display_url = os.getenv("DISPLAY")
+-dpy = xlib.XOpenDisplay(display_url)
++dpy = xopendisplay(display_url)
+ return dpy
+ 
+ def get_current_screen():
+@@ -98,7 +111,7 @@ def get_current_screen():
+ 
+ def get_screen_of_display(display, count):
+ """Returns the screen of the given display"""
+-dpy = xlib.XOpenDisplay(display)
++dpy = xopendisplay(display)
+ return Screen(dpy, count)
+ 
+ def get_version():
+@@ -108,7 +121,7 @@ def get_version():
+ minor = c_int()
+ dpy = get_current_display()
+ if not dpy: return None
+-res = core.rr.XRRQueryVersion(dpy, byref(major), byref(minor))
++res = xrrqueryversion(dpy, byref(major), byref(minor))
+ if res:
+ return (major.value, minor.value)
+ return None
diff -Nru disper-0.3.1/debian/patches/series disper-0.3.1/debian/patches/series
--- disper-0.3.1/debian/patches/series  1970-01-01 01:00:00.0 +0100
+++ disper-0.3.1/debian/patches/series  2017-01-14 20:24:09.0 +0100
@@ -0,0 +1 @@
+fix-844505

Bug#851423: remmina: Out of memory error. Only user programs running were desktop, remmina and chromium browser.

[Duncan Hare]

Package: remmina
Version: 1.1.1-2
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 8.0 (jessie)
Release:8.0
Codename:   jessie
Architecture: armv7l

Kernel: Linux 4.4.34-v7+ (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 remmina depends on:
ii  dbus-x111.8.20-0+deb8u1
ii  libavahi-client30.6.31-5
ii  libavahi-common30.6.31-5
ii  libavahi-ui-gtk3-0  0.6.31-5
ii  libc6   2.19-18+deb8u6
ii  libgcrypt20 1.6.3-2+deb8u2
ii  libgdk-pixbuf2.0-0  2.31.1-2+deb8u5
ii  libglib2.0-02.42.1-1
ii  libgtk-3-0  3.14.5-1+deb8u1rpi1rpi1g
ii  libssh-40.6.3-4+deb8u2
ii  libvte-2.90-9   1:0.36.3-1
ii  libx11-62:1.6.2-3
ii  remmina-common  1.1.1-2

Versions of packages remmina recommends:
ii  remmina-plugin-rdp  1.1.1-2
ii  remmina-plugin-vnc  1.1.1-2

remmina suggests no packages.

-- no debconf information
Jan 14 07:17:01 onlypi CRON[23648]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
Jan 14 08:17:01 onlypi CRON[23675]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
Jan 14 09:17:01 onlypi CRON[23701]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
Jan 14 10:17:01 onlypi CRON[23725]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
Jan 14 11:17:01 onlypi CRON[23751]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
Jan 14 12:17:01 onlypi CRON[23781]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
Jan 14 12:33:27 onlypi dbus[433]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Jan 14 12:33:27 onlypi systemd[1]: Starting Hostname Service...
Jan 14 12:33:27 onlypi systemd-hostnamed[23938]: Warning: nss-myhostname is not 
installed. Changing the local hostname might make it unresolveable. Please 
install nss-myhostname!
Jan 14 12:33:27 onlypi dbus[433]: [system] Successfully activated service 
'org.freedesktop.hostname1'
Jan 14 12:33:27 onlypi systemd[1]: Started Hostname Service.
Jan 14 12:34:33 onlypi dbus[433]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Jan 14 12:34:33 onlypi systemd[1]: Starting Hostname Service...
Jan 14 12:34:33 onlypi systemd-hostnamed[23954]: Warning: nss-myhostname is not 
installed. Changing the local hostname might make it unresolveable. Please 
install nss-myhostname!
Jan 14 12:34:33 onlypi dbus[433]: [system] Successfully activated service 
'org.freedesktop.hostname1'
Jan 14 12:34:33 onlypi systemd[1]: Started Hostname Service.
Jan 14 13:06:48 onlypi dbus[433]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Jan 14 13:06:48 onlypi systemd[1]: Starting Hostname Service...
Jan 14 13:06:49 onlypi systemd-hostnamed[24075]: Warning: nss-myhostname is not 
installed. Changing the local hostname might make it unresolveable. Please 
install nss-myhostname!
Jan 14 13:06:49 onlypi dbus[433]: [system] Successfully activated service 
'org.freedesktop.hostname1'
Jan 14 13:06:49 onlypi systemd[1]: Started Hostname Service.
Jan 14 13:17:01 onlypi CRON[24104]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
Jan 14 14:13:55 onlypi kernel: [415491.906298] lxpanel invoked oom-killer: 
gfp_mask=0x24201ca, order=0, oom_score_adj=0
Jan 14 14:13:55 onlypi kernel: [415491.906317] lxpanel cpuset=/ mems_allowed=0
Jan 14 14:13:55 onlypi kernel: [415491.906348] CPU: 0 PID: 901 Comm: lxpanel 
Not tainted 4.4.34-v7+ #930
Jan 14 14:13:55 onlypi kernel: [415491.906359] Hardware name: BCM2709
Jan 14 14:13:55 onlypi kernel: [415491.906403] [<80018784>] (unwind_backtrace) 
from [<80014058>] (show_stack+0x20/0x24)
Jan 14 14:13:55 onlypi kernel: [415491.906427] [<80014058>] (show_stack) from 
[<803215c4>] (dump_stack+0xd4/0x118)
Jan 14 14:13:55 onlypi kernel: [415491.906454] [<803215c4>] (dump_stack) from 
[<8015519c>] (dump_header+0x64/0x18c)
Jan 14 14:13:55 onlypi kernel: [415491.906481] [<8015519c>] (dump_header) from 
[<80102ca0>] (oom_kill_process+0x350/0x49c)
Jan 14 14:13:55 onlypi kernel: [415491.906502] [<80102ca0>] (oom_kill_process) 
from [<80103170>] (out_of_memory+0x30c/0x344)
Jan 14 14:13:55 onlypi kernel: [415491.906524] [<80103170>] (out_of_memory) 
from [<80108488>] (__alloc_pages_nodemask+0x9a0/0x9e0)
Jan 14 14:13:55 onlypi kernel: [415491.906544] [<80108488>] 

Bug#851166: nmu: forge_0.9.2-2 [RC]

[Ghislain Vaillant]

On Thu, 12 Jan 2017 16:06:31 + Ghislain Antony Vaillant 
 wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu forge_0.9.2-2 . ANY . unstable . -m "Rebuild with fixed glm"
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (900, 'testing'), (300, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.8.0-2-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)

I forgot to mention that this NMU would fix the current RC affecting
forge. The FTBFS was due to a bug in the CMake detection of the glm
library, which I have fixed since.

Ghis

Bug#175064: DocBook XML conversion is read with this script

[Russ Allbery]

Bill Allombert  writes:

> I am concerned that DocBook is much too complex to be used for Debian
> policy.  We need to people to write patches without trouble and we do
> not have many editors available for fixing the XML. Debiandoc-SGML
> virtue is that it is simple.

They seem essentially identical to me?  We've had copyright-format in the
Policy distribution for a while, and it's never seemed any different to me
(as someone not horribly familiar with XML markup) from editing Policy.

The alternative, I guess, would be to use Markdown for the whole thing,
but I think it's worthwhile to have sections and internal links and a bit
more formatting than Markdown gives us.

Anyway, my understanding (see earlier messages in this bug) is that the
maintainer of DebianDoc-SGML is actively trying to transition people away
from it, so I think it's not viable to stay on it even if it's better
along some axes.

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

Bug#822309: cme: fails to detect The Open Group License

[Dominique Dumont]

On Sat, 30 Apr 2016 18:13:22 +0200 Dominique Dumont  wrote:
> The problem comes from licensecheck which fails to detect the dual 
> copyright and licenses:

I've re-assigned the bug to licensecheck package. licensecheck is now handled 
by Jonas. 

All the best

-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Bug#851357: Regression: No longer supports ServerName containing underscore

[Stefan Fritsch]

On Saturday, 14 January 2017 19:36:34 CET Ondřej Surý wrote:
> Stefan,
> 
> JFTR underscores in domain names are allowed, just not for hostnames. SRV,
> TLSA and other RRs make use of them.

But the character restriction for hostnames is valid for all parts of the FQDN 
of a host. From RFC1035 section 2.3.1 (a FQDN consists of multiple labels 
separated by dots):

  The labels must follow the rules for ARPANET host names.  They must
  start with a letter, end with a letter or digit, and have as interior
  characters only letters, digits, and hyphen.  There are also some
  restrictions on the length.  Labels must be 63 characters or less.

For example, while TLSA uses things like _tcp and _443 in the looked up RRs, 
its spec RFC  6698 section 3 explicitly states that the labels in the "base 
domain name" must meet the restrictions from RFC 952, which means no 
underscores.

And for http/https, only hostnames are relevant. Even if they look like a 
domain name like heise.de. 

Jonathan, So , host/domain names with underscores are not RFC compliant even 
though they are common in internal networks. And I looked up some discussions 
on the upstream httpd-dev list and consensus was that they wanted only a 
single knob to switch to legacy behavior. Though underscores in domain names 
were not discussed explicitly.

Also interesting: RFC 7230 section 5.4 says that a http server must respond 
with "400 bad request" if the Host header field contains an invalid field-value 
(though it does not define "invalid" explicitly).

Bug#721255: resolved by removing SOGO connector

[Daniel Pocock]

I've continued to observe two prompts for the master password each time
icedove starts

I removed the SOGo Connector[1] plugin from icedove and restarted and
the master password prompt is only appearing once now.

This leads me to suspect there is something going wrong in the way
plugins initialize when they need to use stored credentials.  The SOGo
Connector stores credentials for access to a CardDAV address book URL.




1.
https://sogo.nu/files/docs/SOGo%20Mozilla%20Thunderbird%20Configuration.pdf

Bug#841724: jessie-pu: package guile-2.0/2.0.11+1-9

[Salvatore Bonaccorso]

Hi Rob,

On Sat, Jan 14, 2017 at 12:58:10PM -0600, Rob Browning wrote:
> Salvatore Bonaccorso  writes:
> 
> > Any news on that upload?
> 
> I should be able to handle it before Tuesday, but let me make sure I
> understand what's desired.  We're talking about the 2.0.11+1-9+deb8u1
> changes I initially proposed?

Disclaimer: I'm not a stable release manager, just tracking open CVEs
for jessie which were no-dsa but proposed to be scheduled via a point
release.

Yes we are talking about the changes, which Adam Barratt, acked in
https://bugs.debian.org/841724#24

Regards,
Salvatore