Bug#784123: vinagre: Grabs mouse and doesn't want to release it

[Michael Neilly]

I can see from gdb that Vinagre receives a window event via 
vinagre_window_state_event_cb that tells it the window is no longer in 
fullscreen mode. There was no preceding call to 
vinagre_window_toggle_fullscreen and I don’t see any other calls to 
gtk_window_fullscreen/unfullscreen.

Setting GTK_DEBUG=updates appears to make the issue go away although it is 
clearly not a solution.

I use focus-mode set to ‘mouse' so that focus follow the mouse. Setting this 
back to the default of ‘click’ appears to make this problem go away. Changing 
the setting back to ‘mouse’ and putting Vinagre back into full screen mode 
immediately exhibits the problem. Perhaps there is an incompatibility between 
focus follows mouse and full screen mode?


> On Sep 17, 2016, at 6:11 PM, Mike Neilly  wrote:
> 
> Package: vinagre
> Version: 3.14.1-1
> Followup-For: Bug #784123
> 
> Dear Maintainer,
> 
> This still exists in Debian 8.6 as shown in the following video:
> 
> https://youtu.be/_Gf5XQkSd8Y
> 
> This video shows a full screen VNC session using vinagre on Debian
> 8.6. "At some point" mouse control is lost. Clicking icons in the
> remote windows VNC session no longer works. Clicking on the terminal
> on the left brings up the Linux terminal used to launch
> vinagre. Leaving full screen with F11 reveals the Linux context menu
> is selected on the desktop behind the VNC session and mouse control is
> lost on the Gnome desktop until hitting Alt-Tab.
> 
> It seems non-deterministic as to just how the situation occurs. Using
> Super-PageUp and Super-PageDown, Alt-Tab and switching in and out of
> full screen with F11 are probably the best way to reproduce
> this. Sometimes it seems stable for a while then things stop working.
> 
> There are also error messages reported by both vinagre and gnome-shell
> at the time of failure:
> 
> Vinagre reports:
> 
> mneilly@spiderbyte2:~$ vinagre
> (vinagre:13166): GLib-CRITICAL **: Source ID 630 was not found when 
> attempting to remove it
> 
> While gnome-shell reports:
> 
> mneilly@spiderbyte2:~$ gnome-shell --replace
> current session already has an ibus-daemon.
> Gjs-Message: JS LOG: Failed to register AuthenticationAgent
> GNOME Shell started at Sat Sep 17 2016 17:49:01 GMT-0700 (PDT)
> Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a 
> timestamp of 0 for 0x207 (Remote Des)
> Gjs-Message: JS LOG: pushModal: invocation of begin_modal failed
> Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a 
> timestamp of 0 for 0x2200010 ()
> 
> -- System Information:
> Debian Release: 8.6
>  APT prefers experimental
>  APT policy: (1000, 'experimental'), (500, 'stable-updates'), (500, 
> 'stable'), (100, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages vinagre depends on:
> ii  dconf-gsettings-backend [gsettings-bac  0.22.0-1
> ii  libavahi-common30.6.31-5
> ii  libavahi-gobject0   0.6.31-5
> ii  libavahi-ui-gtk3-0  0.6.31-5
> ii  libc6   2.19-18+deb8u6
> ii  libcairo2   1.14.0-2.1+deb8u1
> ii  libdbus-glib-1-20.102-1
> ii  libfreerdp-core1.1  
> 1.1.0~git20140921.1.440916e+dfsg1-4
> ii  libfreerdp-gdi1.1   
> 1.1.0~git20140921.1.440916e+dfsg1-4
> ii  libfreerdp-locale1.1
> 1.1.0~git20140921.1.440916e+dfsg1-4
> ii  libgdk-pixbuf2.0-0  2.31.1-2+deb8u5
> ii  libglib2.0-02.42.1-1+b1
> ii  libgtk-3-0  3.14.5-1+deb8u1
> ii  libgtk-vnc-2.0-00.5.3-1.3
> ii  libsecret-1-0   0.18-1+b1
> ii  libspice-client-glib-2.0-8  0.25-1+b1
> ii  libspice-client-gtk-3.0-4   0.25-1+b1
> ii  libtelepathy-glib0  0.24.1-1
> ii  libvte-2.91-0   0.38.1-2
> ii  libxml2 2.9.1+dfsg1-5+deb8u3
> 
> Versions of packages vinagre recommends:
> ii  freerdp-x11  1.1.0~git20140921.1.440916e+dfsg1-4
> 
> vinagre suggests no packages.
> 
> -- no debconf information

Bug#811846: #811846: status?

[Pino Toscano]

Hi,

what's the status of this bug (xbase64 that FTBFS with GCC 6)?
Because of it, xbase64 was removed from testing a couple of months ago,
and now it will prevent calligra (which ships a sybase access driver
for kexi) to migrate to testing.

Any way I can help with this?

Thanks,
-- 
Pino Toscano

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

Bug#838176: mcabber: please update the package to the latest release

[Anatoly Kazantsev]

Package: mcabber
Version: 0.10.2-1
Severity: wishlist

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

Current version of mcabber is 1.0.2 but we still have 0.10 in debian,
so some new features and fixes are missing.

I'd like to help to package a newer release though I'm not a DD or anything 
lile that.
I've already built the latest version using debian tools and offered a help
to you in April via a private email. Also I noticed the previous maintainer
of the packages because hadn't received any response from you.

I will go NMU way if I won't receive any response here.

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

Kernel: Linux 4.6.0-1-686-pae (SMP w/2 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: sysvinit (via /sbin/init)

Versions of packages mcabber depends on:
ii  libaspell15  0.60.7~20110707-3+b1
ii  libassuan0   2.4.3-1
ii  libc62.23-5
ii  libglib2.0-0 2.49.6-1
ii  libgpg-error01.24-1
ii  libgpgme11   1.6.0-3
ii  libidn11 1.33-1
ii  libloudmouth1-0  1.5.3-1
ii  libncursesw5 6.0+20160625-1
ii  libotr5  4.1.1-2
ii  libtinfo56.0+20160625-1

mcabber recommends no packages.

mcabber suggests no packages.

-- no debconf information

Bug#838175: [buildd-tools-devel] Bug#838175: change default locale to C.UTF-8 in chroots

[Johannes Schauer]

Hi,

Quoting Pirate Praveen (2016-09-18 04:56:56)
> (if this should go to debootstrap, then please reassign)

this should not go to debootstrap. The way the chroot is created has no
influence on the variables that are exported during the package build.

> Many packages now expect a UTF-8 locale and we have to manually specify
> LC_ALL=C.UTF-8. I think it is better to make C.UTF-8 as the default locale
> for chroots to avoid fixing so many packages.

sbuild is still the wrong place to fix this.

Even if sbuild would set a locale, packages would *still* have to manually set
if if they would otherwise FTBFS or be unreproducible. The only effect you
would then achieve would be that you would hide that there is a problem for
everybody using sbuild.

The right location to fix this for many packages is either dpkg or debhelper.
And even fixing it there will not make the change propagate to *all* packages
but only to those that choose to use the facilities provided by either.

Remember that our packaging system does not mandate a single package builder
like dpkg-buildpackage. So the right place to fix this bug is not in the tools
that build the package but in the libraries that maintainers might use in their
debian/rules files.

So all you can do is to make it easier for maintainers to export the locale,
for example by talking to dpkg or debhelper people. But you cannot fix one
place and have it affect all package builds at once.

So you might want to re-think your idea and re-assign this bug as appropriate.
I suggest you try dpkg next.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#837352: mpv display (both terminal and video) freezes while playing video

[Nicolas Braud-Santoni]

On Sun, Sep 18, 2016 at 05:46:22AM +0200, Nicolas Braud-Santoni wrote:
> On Sat, Sep 10, 2016 at 10:26:12PM +0100, James Cowgill wrote:
> > 
> > I can't seem to reproduce this on my laptop. Please can you attach the
> > terminal output of 'mpv -v '. Hopefully that may give some more info.
> 
> Attached here.

Actually, attached here.
mpv -v bsd-0159.mp4
[cplayer] Command line options: '-v' 'bsd-0159.mp4'
[cplayer] mpv 0.20.0 (C) 2000-2016 mpv/MPlayer/mplayer2 projects
[cplayer]  built on UNKNOWN
[cplayer] ffmpeg library versions:
[cplayer]libavutil   55.28.100
[cplayer]libavcodec  57.48.101
[cplayer]libavformat 57.41.100
[cplayer]libswscale  4.1.100
[cplayer]libavfilter 6.47.100
[cplayer]libswresample   2.1.100
[cplayer] ffmpeg version: 3.1.3-1+b3
[cplayer]
[cplayer] Configuration: ./waf -v configure --prefix=/usr 
--libdir=/usr/lib/x86_64-linux-gnu --confdir=/etc/mpv 
--zshdir=/usr/share/zsh/vendor-completions --enable-cdda --enable-sdl2 
--enable-sndio --enable-zsh-comp --enable-libmpv-shared --enable-encoding 
--disable-build-date
[cplayer] List of enabled features: alsa any-gl asm atomics audio-input 
av-avpacket-int64-duration av-new-pixdesc av-pix-fmt-mmal av-subtitle-nopict 
av-version-info avcodec-chroma-pos-api avcodec-has-codecpar 
avcodec-new-codec-api avcodec-profile-name avframe-metadata 
avframe-skip-samples avutil-has-hwcontext avutil-h
dr avutil-mastering-metadata c11-tls cdda cplayer debug-build dlopen drm dvbin 
dvdnav dvdread egl-helpers egl-x11 enca encoding fchmod gl gl-wayland gl-x11 
glibc-thread-name glob iconv jack jpeg lcms2 libass libass-osd libav 
libavdevice libavfilter libbluray libdl libguess libm libmpv-shared librt 
libsmbclient libswre
sample linux-fstatfs lua nanosleep optimize oss-audio oss-audio-native plain-gl 
posix posix-or-mingw posix-spawn pthreads pulse resampler rubberband sdl2 shm 
sndio sse4-intrinsics standard-gl stdatomic subprocess termios tv tv-v4l2 vaapi 
vaapi-egl vaapi-glx vaapi-hwaccel vaapi-wayland vaapi-x-egl vaapi-x11 vdpau 
vdpau
-gl-x11 vdpau-hwaccel videodev vt.h wayland x11 xext xinerama xrandr xss xv 
zlib zsh-comp
[global] config path: '' -> '/home/nbraud/.mpv'
[global] config path: 'mpv.conf' -/-> '/home/nbraud/.mpv/mpv.conf'
[global] config path: 'config' -> '/home/nbraud/.mpv/config'
[global] config path: 'mpv.conf' -/-> '/etc/mpv/mpv.conf'
[global] config path: 'config' -/-> '/etc/mpv/config'
[cplayer] Reading config file /home/nbraud/.mpv/config
[cplayer] Setting option 'no-audio-display' = '' (flags = 4)
[cplayer] Setting option 'v' = '' (flags = 8)
[global] config path: 'input.conf' -/-> '/home/nbraud/.mpv/input.conf'
[global] config path: 'input.conf' -/-> '/etc/mpv/input.conf'
[osc] Loading script @osc.lua...
[global] config path: 'scripts' -/-> '/home/nbraud/.mpv/scripts'
[global] config path: 'scripts' -/-> '/etc/mpv/scripts'
[osc] loading mp.defaults
[osc] loading @osc.lua
[global] config path: 'lua-settings/osc.conf' -/-> 
'/home/nbraud/.mpv/lua-settings/osc.conf'
[global] config path: 'lua-settings/osc.conf' -/-> 
'/etc/mpv/lua-settings/osc.conf'
[osc] lua-settings/osc.conf not found.
[cplayer] Run command: define-section, flags=0, args=[showhide, mouse_move 
script-binding osc/__keybinding1
[cplayer] mouse_leave script-binding osc/__keybinding2
[cplayer] , force]
[cplayer] Run command: enable-section, flags=0, args=[showhide, 
allow-hide-cursor+allow-vo-dragging]
[cplayer] Run command: define-section, flags=0, args=[input, mouse_btn0 
script-binding osc/__keybinding3
[cplayer] shift+mouse_btn0 script-binding osc/__keybinding4
[cplayer] mouse_btn2 script-binding osc/__keybinding5
[cplayer] mouse_btn0_dbl ignore
[cplayer] shift+mouse_btn0_dbl ignore
[cplayer] mouse_btn2_dbl ignore
[cplayer] , force]
[cplayer] Run command: enable-section, flags=0, args=[input, ]
[cplayer] Run command: define-section, flags=0, args=[input_osc, del 
script-binding osc/__keybinding6
[cplayer] , default]
[cplayer] Run command: enable-section, flags=0, args=[input_osc, 
allow-hide-cursor+allow-vo-dragging]
[cplayer] Run command: define-section, flags=0, args=[input_forced_osc, , force]
[cplayer] Run command: enable-section, flags=0, args=[input_forced_osc, 
allow-hide-cursor+allow-vo-dragging]
[cplayer] Done loading @osc.lua.
[ytdl_hook] Loading script @ytdl_hook.lua...
[global] config path: 'scripts' -/-> '/home/nbraud/.mpv/scripts'
[global] config path: 'scripts' -/-> '/etc/mpv/scripts'
[ytdl_hook] loading mp.defaults
[cplayer] Run command: disable-section, flags=0, args=[input]
[global] config path: 'fonts' -/-> '/home/nbraud/.mpv/fonts'
[global] config path: 'fonts' -/-> '/etc/mpv/fonts'
[osd/libass] Shaper: FriBidi 0.19.7 (SIMPLE) HarfBuzz-ng 1.2.7 (COMPLEX)
[global] config path: 'subfont.ttf' -/-> '/home/nbraud/.mpv/subfont.ttf'
[global] config path: 'subfont.ttf' -/-> '/etc/mpv/subfont.ttf'
[global] config path: 'fonts.conf' -/-> '/home/nbraud/.mpv/fonts.conf'
[global] config path: 'fonts.conf' -/-> 

Bug#837352: mpv display (both terminal and video) freezes while playing video

[Nicolas Braud-Santoni]

On Sat, Sep 10, 2016 at 10:26:12PM +0100, James Cowgill wrote:
> Control: found -1 0.20.0-1
> Control: tags -1 unreproducible
> 
> Hi Nicolas,
> 
> On 10/09/16 21:27, Nicolas Braud-Santoni wrote:
> > 
> > Seeking updates the UI, but it freezes again within a few frames.
> 
> Did you seek using the terminal? Does the OSD work?

Seeking with either the terminal or mpv's X window in focus works.
The OSD works in the sense that seeking works, but the OSD doesn't refresh 
(unless I seek).

> > I tested the version from sid, but it exhibits the same issue.
> 
> I can't seem to reproduce this on my laptop. Please can you attach the
> terminal output of 'mpv -v '. Hopefully that may give some more info.

Attached here.

For information, I can reliably reproduce the issue, with videos in a variety 
of formats.
Setting --hwdec=no didn't change anything.


Best, and thanks for the help,

  nicoo


signature.asc
Description: PGP signature

Bug#838175: change default locale to C.UTF-8 in chroots

[Pirate Praveen]

package: sbuild
version: 0.71.0-2
severity: wishist

(if this should go to debootstrap, then please reassign)

Many packages now expect a UTF-8 locale and we have to manually specify
LC_ALL=C.UTF-8. I think it is better to make C.UTF-8 as the default
locale for chroots to avoid fixing so many packages.



signature.asc
Description: OpenPGP digital signature

Bug#838174: parsnp: FTBFS: -m64 considered harmful

[Aaron M. Ucko]

Source: parsnp
Version: 1.2+dfsg-1
Severity: important
Justification: fails to build from source

Builds of parsnp for most architectures failed with errors stemming
from the use of -m64, which (like -m32) is generally inappropriate to
specify on any architecture.  Please retire the use of this flag.
*If* 32-bit builds turn out to be a lost cause, it's okay to go ahead
and restrict the package's Architecture field appropriately.

Thanks!

Bug#838050: GDM3-only behaviour; Wayland not totally broken; bad tablets break even that

[Andrew Chadwick]

The behaviour in gdm3 alone (outside of a user session) is different 
from tablet to tablet.


* Wacom Intuos5 USB: no crashes, pen functions as a second crosshair 
pointer
* HUION H610PRO USB: no crashes, pen functions as a second crosshair 
pointer
* Genius EasyPen i405X USB: crashes gnome-session in this environment 
as well, repeatedly, same segfault from gnome-shell. systemd appears to 
be desperately trying to launch Xorg instead afterwards? Which then 
*also* segfaults repeatedly.


The Huion and Wacom tablets work inside GNOME-on-Wayland user sessions, 
and gtk3-demo's "Touch and Drawing Tablets" module presents their extra 
axes (pressure, or pressure+tilt+distance, respectively). However using 
Wayland is not really a great workaround currently given how crashy it 
is (xwayland 2:1.18.4-1, pressing Alt kills Chromium, wow.)


The Genius tablet is well known as a horrid crashy mess generally, 
which is why I bought it. This behaviour is new even for that, however.


-8<-
Sep 18 03:17:32 spatula kernel: [50703.338856] usb 2-1: new low-speed 
USB device number 35 using xhci_hcd
Sep 18 03:17:32 spatula kernel: [50703.532827] usb 2-1: New USB device 
found, idVendor=0458, idProduct=5010
Sep 18 03:17:32 spatula kernel: [50703.532834] usb 2-1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=0
Sep 18 03:17:32 spatula kernel: [50703.532838] usb 2-1: Product: 
EasyPen i405X
Sep 18 03:17:32 spatula kernel: [50703.532841] usb 2-1: Manufacturer: 
Genius
Sep 18 03:17:32 spatula kernel: [50703.561689] input: Genius EasyPen 
i405X as 
/devices/pci:00/:00:14.0/usb2/2-1/2-1:1.0/0003:0458:5010.0040/input/input175
Sep 18 03:17:32 spatula kernel: [50703.615183] kye 0003:0458:5010.0040: 
input,hiddev0,hidraw2: USB HID v1.11 Device [Genius EasyPen i405X] on 
usb-:00:14.0-1/input0
Sep 18 03:17:32 spatula mtp-probe: checking bus 2, device 35: 
"/sys/devices/pci:00/:00:14.0/usb2/2-1"
Sep 18 03:17:32 spatula mtp-probe: bus: 2, device: 35 was not an MTP 
device
Sep 18 03:17:33 spatula gnome-shell[29393]: Could not get tablet 
information for 'Genius EasyPen i405X': (null)
Sep 18 03:17:33 spatula kernel: [50704.317185] gnome-shell[29393]: 
segfault at 10 ip 7fd62869e844 sp 7ffe16cebae0 error 4 in 
libwacom.so.2.5.0[7fd62869b000+9000]

Sep 18 03:17:33 spatula org.gnome.Shell.desktop[29393]: (EE)
Sep 18 03:17:33 spatula org.gnome.Shell.desktop[29393]: Fatal server 
error:
Sep 18 03:17:33 spatula org.gnome.Shell.desktop[29393]: (EE) failed to 
dispatch Wayland events: Broken pipe

Sep 18 03:17:33 spatula org.gnome.Shell.desktop[29393]: (EE)
[... one more segfault ...]
Sep 18 03:17:35 spatula gdm3: Child process -29545 was already dead.
Sep 18 03:17:35 spatula gdm3: Child process 29534 was already dead.
Sep 18 03:17:35 spatula gdm3: Unable to kill session worker process
Sep 18 03:17:35 spatula systemd[1]: Started Session c22 of user 
Debian-gdm.
Sep 18 03:17:35 spatula udev-acl.ck[29583]: g_slice_set_config: 
assertion 'sys_page_size == 0' failed
Sep 18 03:17:35 spatula /usr/lib/gdm3/gdm-x-session[29582]: (--) Log 
file renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-29585.log" 
to "/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
Sep 18 03:17:35 spatula /usr/lib/gdm3/gdm-x-session[29582]: X.Org X 
Server 1.18.4
Sep 18 03:17:35 spatula /usr/lib/gdm3/gdm-x-session[29582]: Release 
Date: 2016-07-19
Sep 18 03:17:35 spatula /usr/lib/gdm3/gdm-x-session[29582]: X Protocol 
Version 11, Revision 0

[... starts up, then a stream of new segfaults ...]
->8-

Bug#822081: Bug#825100: Problems with ouse and touchpad settings (it was:Re: Bug#822081: gnome-control-center: Mouse settings have no effect since 3.20)

[Leandro Doctors]

2016-06-06 5:02 GMT-03:00 Emilio Pozuelo Monfort :
> #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.

Sorry for the delay.
The thread got lost in the pile...

You were right. I wrote to the wrong bug address :-)

Thanks, it worked!
Best,
Leandro

Bug#836567: aptitude: [PATCH] aborts on encountering new DepCompareOp flags

[Aaron M. Ucko]

"Manuel A. Fernandez Montecelo"  writes:

> Thaks for the analysis and the patch.  I'm a bit busy but will try to
> take a deeper look soonish.

I know how that goes. ;-)

> On a first glance, using the module operator rather than bitwise
> operations looks a bit odd.

It's unconventional, but should optimize to bitwise masking in practice
because the modulus is a constant power of two.  Using an explicit mask
would be cleaner, but AFAICT apt's headers don't predefine one.

> Also, the code is from before 2005 (the beginning of the VCS history) so
> it's a bit strange that it survived all these years if it produces
> crashes, but then again maybe the wrong behaviour it's caused by more
> recent changes to support multiarch, or changes in apt, etc.

Right, I presume the flags that are causing trouble are relatively new
additions to apt.

FWIW, my patched aptitude has continued to work well for me with no
further changes.

At any rate, thanks for looking into my report!

-- 
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#838173: usbguard-applet-qt: register the applet with major desktop environments

[Christoph Anton Mitterer]

Package: usbguard-applet-qt
Version: 0.5.14+ds1-2
Severity: wishlist


Hi.

Since usbguard-applet-qt is probably the most usable way for controlling 
usbguard
when running on a desktop, it would be nice to have it somehow registered
with the major desktop environments (Cinnamon, KDE, LXDE, XFCE, GNOME, etc.)
and started automatically per default (one can assume the user wants this, when
he installs the package).

Cinnamon, for e.g. has "Applets" in its system control. But I assume for there
to show up a true cinnamon applet would be needed (or at least some wrapping
around the Qt applet).

Another way could be the "Startup Applications" from its system control.
Having it there, would also allow to easily enable/disable the applet.


Cheers,
Chris.


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

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

Versions of packages usbguard-applet-qt depends on:
ii  libc6   2.24-3
ii  libgcc1 1:6.2.0-4
ii  libqt5core5a5.6.1+dfsg-3+b1
ii  libqt5gui5  5.6.1+dfsg-3+b1
ii  libqt5svg5  5.6.1-2
ii  libqt5widgets5  5.6.1+dfsg-3+b1
ii  libstdc++6  6.2.0-4
ii  libusbguard00.5.14+ds1-2
ii  usbguard0.5.14+ds1-2

usbguard-applet-qt recommends no packages.

usbguard-applet-qt suggests no packages.

-- no debconf information

Bug#838172: usbguard-applet-qt: GUI window cannot be opened again after the first time

[Christoph Anton Mitterer]

Package: usbguard-applet-qt
Version: 0.5.14+ds1-2
Severity: important


Hi.

When using usbguard-applet-qt and clicking on the systray icon to open it's 
window,
then this only works for the first time the program has been started.

Once the window has been closed the following happens when clicking on the icon 
again:
For half a second or so, a minimised window (noted by [] brackets around the 
title)
appears in the window least, which then disappears again.

Having tried that under cinnamon.


Cheers,
Chris.


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

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

Versions of packages usbguard-applet-qt depends on:
ii  libc6   2.24-3
ii  libgcc1 1:6.2.0-4
ii  libqt5core5a5.6.1+dfsg-3+b1
ii  libqt5gui5  5.6.1+dfsg-3+b1
ii  libqt5svg5  5.6.1-2
ii  libqt5widgets5  5.6.1+dfsg-3+b1
ii  libstdc++6  6.2.0-4
ii  libusbguard00.5.14+ds1-2
ii  usbguard0.5.14+ds1-2

usbguard-applet-qt recommends no packages.

usbguard-applet-qt suggests no packages.

-- no debconf information

Bug#838171: duck: detect SourceForge pages for sqlitebrowser as redirects

[Paul Wise]

Package: duck
Version: 0.10
Severity: wishlist

These two pages are detected as OK by DUCK but both should be detected
as not OK because they have text and JavaScript pointing elsewhere.
I've included some suggested phrases for the detection below:

http://sqlitebrowser.sourceforge.net/

window.location =  
Redirecting to
We've moved
Redirecting now
our new website

https://sourceforge.net/projects/sqlitebrowser/

WE'VE MOVED
MOVED TO

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages duck depends on:
ii  devscripts   2.16.7
ii  dpkg-dev 1.18.10
ii  libconfig-inifiles-perl  2.89-1
ii  libconfig-simple-perl4.59-6
ii  libdomain-publicsuffix-perl  0.14.1-1
ii  libfile-which-perl   1.21-1
ii  libmailtools-perl2.13-1
ii  libnet-dns-perl  1.06-1
ii  libparse-debcontrol-perl 2.005-4
ii  libpath-class-perl   0.37-1
ii  libregexp-common-email-address-perl  1.01-4
ii  libregexp-common-perl2016060801-1
ii  libstring-similarity-perl1.04-1+b3
ii  libwww-curl-perl 4.17-2+b1
ii  libxml-xpath-perl1.37-1
ii  libyaml-libyaml-perl 0.63-1
ii  lynx 2.8.9dev9-1
ii  perl 5.22.2-5
ii  publicsuffix 20160805-1

duck recommends no packages.

Versions of packages duck suggests:
ii  bzr 2.7.0+bzr6619-1
ii  git 1:2.9.3-1
ii  mercurial   3.9.1-1
ii  subversion  1.9.4-3

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#838170: lynis 2.3.3-1 CUST-0520 reports warning even when skipped

[Eric Light]

Package: lynis
Version: 2.3.3-1

The custom check CUST-0520 (re ecryptfs) will report a warning even if the 
test is skipped.

The problem exists in /etc/lynis/plugins/plugin_debian_phase1, in the if 
statement beginning at line 379  (or, more accurately, at the else 
statement on line 421).

Running Debian Sid, kernel 4.7.0-1-amd64.

Eric
###
This e-mail is confidential and may contain information subject to legal 
privilege.  If you are not the intended recipient please advise us of our
error by return e-mail then delete this e-mail and any attached files.  
You may not copy, disclose or use the contents in any way.  

The views expressed in this e-mail may not be those of Gallagher Group 
Ltd or subsidiary companies thereof.
###

Bug#838169: duck: temporary file issues: mkdtemp deprecated, hardcodes /tmp

[Paul Wise]

Package: duck
Version: 0.10
Severity: normal
Usertags: tmp

I override the various environment variables that allow you to select a
different location for temporary files. DUCK completely ignores that
and hard-codes /tmp/duckXX as the argument to mkdtemp. The mkdtemp
function should no longer be used for new code. The File::Temp
functions newdir or tempdir should be used instead of mkdtemp.

http://perldoc.perl.org/File/Temp.html

pabs@chianamo ~ $ env | egrep 'TE?MP'
TMPDIR=/tmp/user/1000
TEMP=/tmp/user/1000
TEMPDIR=/tmp/user/1000
TMP=/tmp/user/1000
pabs@chianamo ~ $ env | grep TE?MP^C
pabs@chianamo ~ $ duck -v http://example.org/foo.dsc
Downloading to /tmp/duckbhcrLK
dget: retrieving http://example.org/foo.dsc


dpkg-source: error: cannot read foo.dsc: No such file or directory
pabs@chianamo ~ $ grep /tmp /usr/bin/duck
my $tempdir=mkdtemp("/tmp/duckXX");

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages duck depends on:
ii  devscripts   2.16.7
ii  dpkg-dev 1.18.10
ii  libconfig-inifiles-perl  2.89-1
ii  libconfig-simple-perl4.59-6
ii  libdomain-publicsuffix-perl  0.14.1-1
ii  libfile-which-perl   1.21-1
ii  libmailtools-perl2.13-1
ii  libnet-dns-perl  1.06-1
ii  libparse-debcontrol-perl 2.005-4
ii  libpath-class-perl   0.37-1
ii  libregexp-common-email-address-perl  1.01-4
ii  libregexp-common-perl2016060801-1
ii  libstring-similarity-perl1.04-1+b3
ii  libwww-curl-perl 4.17-2+b1
ii  libxml-xpath-perl1.37-1
ii  libyaml-libyaml-perl 0.63-1
ii  lynx 2.8.9dev9-1
ii  perl 5.22.2-5
ii  publicsuffix 20160805-1

duck recommends no packages.

Versions of packages duck suggests:
ii  bzr 2.7.0+bzr6619-1
ii  git 1:2.9.3-1
ii  mercurial   3.9.1-1
ii  subversion  1.9.4-3

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#834682: mina2: FTBFS in testing (failing tests)

[tony mancill]

On Fri, Sep 16, 2016 at 07:35:58PM +0200, Santiago Vila wrote:
> Hello.
> 
> I tried building this package 20 times this morning.
> 
> It failed 19 times. The build logs are attached in a single tarball.
> 
> There is something which may help in this bug: there is a new upstream
> release of mina available (2.0.14).
> 
> So I'd like to propose that you or anybody in the team maintaining
> this package do this:
> 
> * Raise this to serious (where it belongs, it's a FTBFS bug).
> 
> * Disable completely the tests for this version (trivial patch attached).
>   The upload doing that would naturally close this bug.
> 
>   Disabling only the tests that fail would be also an option, but the tests
>   failing for me are not the same failing for Gregor, and it would not be
>   really productive or useful to determine which of the tests are ok and
>   which ones are not when we have a new upstream release available that may
>   have some or all of the failing tests already fixed.
> 
> * Try to upload mina version 2.0.14 for unstable (but this time without the 
> patch)
>   to see if things improve with the new version. Hopefully this version does 
> not
>   fail anymore, or maybe it fails for you and for me at the same time.
> 
> Would this plan be acceptable to you?
> 
> If yes, please go ahead and stop reading. Thanks a lot!
> 
> If not: there is a tag called stretch-ignore which is the right way to
> make a serious bug like this one not to be RC:
> 
> https://release.debian.org/stretch/rc_policy.txt
> 
> Please read the relevant paragraph: You would have to ask the Release
> Managers for permission first, you can't just downgrade a FTBFS bug on
> your own as a way to make it not RC.
> 
> But I really believe we can skip all that. Believe me, it is not my
> intention or desire to see this package autoremoved from Debian or
> anything like that, everything I ask is that it builds ok, and that's
> very easy to achieve with the attached path.
> 
> Thanks.

Hi Santiago,

Ugh - thank you for putting so much effort into this and for providing
logs.  I have tried to get the build to fail for me locally and can't,
which is also frustrating.  However, I feel like we have an established
precedent for disabling non-deterministic test suites, since flaky tests
can be worse than no tests at all, so I am applying your patch and
preparing an upload.

We can always enable tests down the road, as you suggest, perhaps with
the upload of the next upstream version.  

Cheers,
tony


signature.asc
Description: PGP signature

Bug#838050: Breaks all tablets, no good workaround

[Andrew Chadwick]

My first through was the common Debian situation where there's a
mismatch between libwacom2 (which lags releases regularly) and GNOME
(which advances fast). It may well not be libwacom at fault, but
without a debugging trace we can't tell yet. A recent update to
libwacom 0.22 doesn't fix this issue, however. See also Bug#838047 <
https://bugs.debian.org/838047 >.

This breaks gnome-shell with all the Wacom and non-Wacom graphics
tablets I've tried, crashing gnome-shell at or shortly after the point
when they are connected. However the non-tablet USB devices I've tried
seem OK, including my (non-Wacom, non-pen, regular multitouch)
touchscreen. See bug 838047 for details and log traces.

I cannot get the suggested rmmod workaround to work on my system. The
non-Wacom tablets still cause gnome-shell to crash immediately upon
being plugged in, and when a Wacom tablet is plugged in, the "wacom"
kernel module is automatically loaded and stays loaded.

I am using Wayland gdm3, and Xorg user gnome-shell sessions.

gnome-shell   3.21.91-2
gdm3   3.21.90-1
libwacom2   0.22-1

-- 
Andrew Chadwick

Bug#838168: duck: options to check multiple URLs instead of looking at Debian packaging

[Paul Wise]

Package: duck
Version: 0.10
Severity: wishlist

It would be nice to have an option to check URLs on the command-line
and stdin (one per line). This would be useful during development and
bug reporting to check individual URLs against DUCK's heuristics.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages duck depends on:
ii  devscripts   2.16.7
ii  dpkg-dev 1.18.10
ii  libconfig-inifiles-perl  2.89-1
ii  libconfig-simple-perl4.59-6
ii  libdomain-publicsuffix-perl  0.14.1-1
ii  libfile-which-perl   1.21-1
ii  libmailtools-perl2.13-1
ii  libnet-dns-perl  1.06-1
ii  libparse-debcontrol-perl 2.005-4
ii  libpath-class-perl   0.37-1
ii  libregexp-common-email-address-perl  1.01-4
ii  libregexp-common-perl2016060801-1
ii  libstring-similarity-perl1.04-1+b3
ii  libwww-curl-perl 4.17-2+b1
ii  libxml-xpath-perl1.37-1
ii  libyaml-libyaml-perl 0.63-1
ii  lynx 2.8.9dev9-1
ii  perl 5.22.2-5
ii  publicsuffix 20160805-1

duck recommends no packages.

Versions of packages duck suggests:
ii  bzr 2.7.0+bzr6619-1
ii  git 1:2.9.3-1
ii  mercurial   3.9.1-1
ii  subversion  1.9.4-3

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#838167: duck: AppData support breaks duck when screenshots have captions

[Paul Wise]

Package: duck
Version: 0.10
Severity: important

DUCK breaks hard when there are screenshots in an AppData file that
have captions along with their image URL:

pabs@chianamo ~ $ apt source -qq sqlitebrowser
NOTICE: 'sqlitebrowser' packaging is maintained in the 'Git' version control 
system at:
git://anonscm.debian.org/collab-maint/sqlitebrowser.git
Please use:
git clone git://anonscm.debian.org/collab-maint/sqlitebrowser.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 1,545 kB of source archives.
dpkg-source: info: extracting sqlitebrowser in sqlitebrowser-3.8.0
dpkg-source: info: unpacking sqlitebrowser_3.8.0.orig.tar.gz
dpkg-source: info: unpacking sqlitebrowser_3.8.0-1.debian.tar.xz
dpkg-source: info: applying 0001-Use-external-qcustomplot-and-antlr.patch
pabs@chianamo ~ $ cd sqlitebrowser-3.8.0/
pabs@chianamo ~/sqlitebrowser-3.8.0 $ grep -C1 screenshot  
distri/sqlitebrowser.desktop.appdata.xml
  
  

  
https://raw.githubusercontent.com/sqlitebrowser/db4s-screenshots/master/v3.3/gnome3_2-execute.png;;
  DB Browser for SQLite, executing query


  
https://raw.githubusercontent.com/sqlitebrowser/db4s-screenshots/master/v3.3/gnome3_1-plot.png;;
  DB Browser for SQLite, browsing data with plot


  
https://raw.githubusercontent.com/sqlitebrowser/db4s-screenshots/master/v3.3/kde413_2-blob.png;;
  DB Browser for SQLite, browing a blob field


  
https://raw.githubusercontent.com/sqlitebrowser/db4s-screenshots/master/v3.3/kde413_1-create_table.png;;
  DB Browser for SQLite, creating a table

  
  http://sqlitebrowser.org/
pabs@chianamo ~/sqlitebrowser-3.8.0 $ duck -n
distri/sqlitebrowser.desktop.appdata.xml: component->screenshots->screenshot: 
URL: 
  
https://raw.githubusercontent.com/sqlitebrowser/db4s-screenshots/master/v3.3/gnome3_2-execute.png
  DB Browser for SQLite, executing query
:  DRY RUN
distri/sqlitebrowser.desktop.appdata.xml: component->screenshots->screenshot: 
URL: 
  
https://raw.githubusercontent.com/sqlitebrowser/db4s-screenshots/master/v3.3/gnome3_1-plot.png
  DB Browser for SQLite, browsing data with plot
:  DRY RUN
distri/sqlitebrowser.desktop.appdata.xml: component->screenshots->screenshot: 
URL: 
  
https://raw.githubusercontent.com/sqlitebrowser/db4s-screenshots/master/v3.3/kde413_2-blob.png
  DB Browser for SQLite, browing a blob field
:  DRY RUN
distri/sqlitebrowser.desktop.appdata.xml: component->screenshots->screenshot: 
URL: 
  
https://raw.githubusercontent.com/sqlitebrowser/db4s-screenshots/master/v3.3/kde413_1-create_table.png
  DB Browser for SQLite, creating a table
:  DRY RUN
distri/sqlitebrowser.desktop.appdata.xml: component->url: URL: 
http://sqlitebrowser.org/:  DRY RUN
distri/sqlitebrowser.desktop.appdata.xml: component->url: URL: 
https://github.com/sqlitebrowser/sqlitebrowser/issues:  DRY RUN
debian/control: Maintainer: Arto Jantunen :  DRY RUN
debian/control: Homepage: http://sqlitebrowser.org/:  DRY RUN
debian/control: Vcs-Git: 
git://anonscm.debian.org/collab-maint/sqlitebrowser.git:  DRY RUN
debian/control: Vcs-Browser: 
http://anonscm.debian.org/gitweb/?p=collab-maint/sqlitebrowser.git:  DRY RUN
debian/copyright:1: Email: francois.fevo...@ensta.org:  DRY RUN
debian/copyright:4: URL: http://sqlitebrowser.org/:  DRY RUN
debian/copyright:27: Email: francois.fevo...@ensta.org:  DRY RUN
debian/copyright:28: Email: jari.aa...@cante.net:  DRY RUN
debian/copyright:29: Email: perezme...@gmail.com:  DRY RUN
debian/copyright:30: Email: vi...@debian.org:  DRY RUN
pabs@chianamo ~/sqlitebrowser-3.8.0 $ duck -v
Use of uninitialized value in concatenation (.) or string at /usr/bin/duck line 
446.
E: ERROR (Certainty:)
   Curl:3 HTTP:0 URL using bad/illegal format or missing URL Illegal characters 
found in URL

Use of uninitialized value in concatenation (.) or string at /usr/bin/duck line 
446.
E: ERROR (Certainty:)
   Curl:3 HTTP:0 URL using bad/illegal format or missing URL Illegal characters 
found in URL

Use of uninitialized value in concatenation (.) or string at /usr/bin/duck line 
446.
E: ERROR (Certainty:)
   Curl:3 HTTP:0 URL using bad/illegal format or missing URL Illegal characters 
found in URL

Use of uninitialized value in concatenation (.) or string at /usr/bin/duck line 
446.
E: ERROR (Certainty:)
   Curl:3 HTTP:0 URL using bad/illegal format or missing URL Illegal characters 
found in URL

Use of uninitialized value in concatenation (.) or string at /usr/bin/duck line 
446.
O: OK (Certainty:)

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, 

Bug#838151: jedit: running jedit logs me out.

[tony mancill]

On 09/17/2016 12:34 PM, tim wrote:

Hi Tim,

Ouch, that sounds nasty.  I'm not able to reproduce the behavior
locally, but am guessing that JEdit is not playing well with your window
manager/X driver/similar.

What are you using for your desktop?  Also, when this occurs, is
anything interesting appearing in your ~/.xsession-errors file?

Thanks,
tony



signature.asc
Description: OpenPGP digital signature

Bug#838047: Confirmed: breaks *all* tablets

[Andrew Chadwick]

GNOME sessions with gnome-shell 3.21.91-2 and libwacom2 0.22-1 still
segfault when any any of my USB tablet devices are attached. This
includes the Wacom USB Wireless Accessory Kit: it's fine after being
plugged in initially without the tablet being turned on, but when the
tablet is turned on and begins communicating wirelessly, the session
dies just as above.

I've tried a plain old USB optical mouse, a USB keyboard, and a couple
of USB joypads too - those are unaffected.

>From the console, libwacom-list-local-devices 0.22 detects the plugged
device and lists its features like it should. No segfaults there.

Bug#784123: vinagre: Grabs mouse and doesn't want to release it

[Mike Neilly]

Package: vinagre
Version: 3.14.1-1
Followup-For: Bug #784123

Dear Maintainer,

This still exists in Debian 8.6 as shown in the following video:

https://youtu.be/_Gf5XQkSd8Y

This video shows a full screen VNC session using vinagre on Debian
8.6. "At some point" mouse control is lost. Clicking icons in the
remote windows VNC session no longer works. Clicking on the terminal
on the left brings up the Linux terminal used to launch
vinagre. Leaving full screen with F11 reveals the Linux context menu
is selected on the desktop behind the VNC session and mouse control is
lost on the Gnome desktop until hitting Alt-Tab.

It seems non-deterministic as to just how the situation occurs. Using
Super-PageUp and Super-PageDown, Alt-Tab and switching in and out of
full screen with F11 are probably the best way to reproduce
this. Sometimes it seems stable for a while then things stop working.

There are also error messages reported by both vinagre and gnome-shell
at the time of failure:

Vinagre reports:

mneilly@spiderbyte2:~$ vinagre
(vinagre:13166): GLib-CRITICAL **: Source ID 630 was not found when attempting 
to remove it

While gnome-shell reports:

mneilly@spiderbyte2:~$ gnome-shell --replace
current session already has an ibus-daemon.
Gjs-Message: JS LOG: Failed to register AuthenticationAgent
GNOME Shell started at Sat Sep 17 2016 17:49:01 GMT-0700 (PDT)
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a 
timestamp of 0 for 0x207 (Remote Des)
Gjs-Message: JS LOG: pushModal: invocation of begin_modal failed
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a 
timestamp of 0 for 0x2200010 ()

-- System Information:
Debian Release: 8.6
  APT prefers experimental
  APT policy: (1000, 'experimental'), (500, 'stable-updates'), (500, 'stable'), 
(100, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages vinagre depends on:
ii  dconf-gsettings-backend [gsettings-bac  0.22.0-1
ii  libavahi-common30.6.31-5
ii  libavahi-gobject0   0.6.31-5
ii  libavahi-ui-gtk3-0  0.6.31-5
ii  libc6   2.19-18+deb8u6
ii  libcairo2   1.14.0-2.1+deb8u1
ii  libdbus-glib-1-20.102-1
ii  libfreerdp-core1.1  1.1.0~git20140921.1.440916e+dfsg1-4
ii  libfreerdp-gdi1.1   1.1.0~git20140921.1.440916e+dfsg1-4
ii  libfreerdp-locale1.11.1.0~git20140921.1.440916e+dfsg1-4
ii  libgdk-pixbuf2.0-0  2.31.1-2+deb8u5
ii  libglib2.0-02.42.1-1+b1
ii  libgtk-3-0  3.14.5-1+deb8u1
ii  libgtk-vnc-2.0-00.5.3-1.3
ii  libsecret-1-0   0.18-1+b1
ii  libspice-client-glib-2.0-8  0.25-1+b1
ii  libspice-client-gtk-3.0-4   0.25-1+b1
ii  libtelepathy-glib0  0.24.1-1
ii  libvte-2.91-0   0.38.1-2
ii  libxml2 2.9.1+dfsg1-5+deb8u3

Versions of packages vinagre recommends:
ii  freerdp-x11  1.1.0~git20140921.1.440916e+dfsg1-4

vinagre suggests no packages.

-- no debconf information

Bug#838001: [pkg-cryptsetup-devel] Bug#838001: cryptsetup does not support ZFS

[Richard Laager]

On 09/17/2016 06:45 PM, Guilhem Moulin wrote:
> On Fri, 16 Sep 2016 at 04:32:24 -0500, Richard Laager wrote:
>> The attached patch adds ZFS support to cryptsetup.
> 
> Thanks the patch.  Unfortunately I can't test it easily, and I know
> nothing about ZFS, but I'll try to review your patch anyway.

Thanks for taking the time to look at this. I'm happy to help in
whatever way I can. Whatever you need, just ask, and I'll do my best.

You might find the upstream ZFS-on-Linux project's root-on-ZFS HOWTO
(which I maintain) informative, even though it's written for Ubuntu:
https://github.com/zfsonlinux/zfs/wiki/Ubuntu-16.04-Root-on-ZFS

I have changes all ready-to-go for supporting LUKS, but this "bug"
(read: feature request) is a blocker. It is possible to work-around this
with (otherwise unused) /etc/fstab entries, but I don't want to
encourage that in the wild, lest it cause some other problem in the future.

My general approach to using LUKS with ZFS is that GRUB prompts for the
passphrase, unlocks LUKS, which ZFS is inside, and reads the kernel and
initrd. When the kernel boots, the initrd contains a keyfile which is
used to unlock LUKS again. This maintains the goal of having everything
including /boot, but excluding GRUB, on ZFS.

However, I am aware that it deviates from the Ubuntu approach of an
unencrypted /boot with an initrd that prompts for the LUKS passphrase.
So I'm forced to choose between two major goals: 1) everything on ZFS &
2) stay as close to normal Ubuntu as possible.

Here are some selected parts of the diff, which outline how I'm using
LUKS, ZFS, and cryptsetup.

+# cryptsetup luksFormat -c aes-xts-plain64 -s 256 -h sha256 \
+  /dev/disk/by-id/scsi-SATA_disk1-part1
+# cryptsetup luksOpen /dev/disk/by-id/scsi-SATA_disk1-part1 luks1
+# zpool create -o ashift=12 \
+  -O atime=off -O canmount=off -O compression=lz4 -O
normalization=formD \
+  -O mountpoint=/ -R /mnt \
+  rpool /dev/mapper/luks1


+# mkdir /etc/keys
+# dd bs=64 count=1 if=/dev/urandom of=/etc/keys/root.key
+# chmod 600 /etc/keys/root.key
+# cryptsetup luksAddKey /dev/disk/by-id/scsi-SATA_disk1-part1
/etc/keys/root.key
+# echo luks1 UUID=$(blkid -s UUID -o value \
+  /dev/disk/by-id/scsi-SATA_disk1-part1) /etc/keys/root.key \
+  luks,discard > /etc/crypttab
+
+# vi /etc/initramfs-tools/initramfs.conf
+Add these lines:
+export KEYFILE_PATTERN="/etc/keys/*.key"
+UMASK=077

On a side note, it'd be nice if cryptsetup would automatically set UMASK
when a keyfile is found. And it'd be nice if there as a default where it
looked for keyfiles.


As another resource, here's the upstream HOWTO for Debian, which someone
else maintains:
https://github.com/zfsonlinux/zfs/wiki/HOWTO-install-Debian-GNU-Linux-to-a-Native-ZFS-Root-Filesystem

The HOWTOs share some history, but are not developed in lock-step. The
packaging for Debian and Ubuntu has also been different historically.
Now that ZFS has been accepted into both Ubuntu and Debian, people are
working on reducing the differences.

>> +zfs list -H -o name,canmount,mountpoint 2>/dev/null | \
> 
> Looks like there is support for ZFS filesystems in the /etc/fstab
> .  Since
> it's what other FS are using, I think that's what we should use for ZFS
> too.

ZFS does not normally use /etc/fstab. That's not to say it's impossible
(obviously, it is), but that is absolutely not what users expect of ZFS
nor how it is used in practice.

I don't know why that wiki page leans so heavily on mountpoint=legacy
and /etc/fstab. You won't find that in other ZFS documentation for any
OS, including the more up-to-date FreeBSD documentation linked from the
header on that page.

> Don't the ‘name’ and ‘mountpoint’ columns of your ‘zfs list’
> command respectively correspond to the first and second columns of
> fstab(5)?

Yes.

>> +for dev in $(zpool status -P "${name%%/*}" 2>/dev/null 
>> | awk '($1 ~ /\//) {print $1}'); do
> 
> This looks rather brittle, as the ‘status’ command seems to be intended
> for humans not parsers.

It's not ideal, I admit, but it's "how it's done". The -P flag was added
specifically because the output of `zpool status` is frequently parsed.
Parsing `zpool status` is exactly how GRUB handles ZFS. If its output
changes, GRUB breaks too.

Ideally, there'd be a -H flag that omits extraneous output and spaces,
like on the zfs command.

> Isn't there a more robust way to retrieve the
> underlying device list of a ZFS pool?

Using libzfs is another way, if your application is compiled. However,
that can be a problem for certain applications because of licensing. For
example, GRUB uses libzfs on Solaris where they can take advantage of
the system library exception in the GPL, but they parse `zpool status`
on other OSes, including Linux.

Since cryptsetup is a shell script, a C library is a non-starter anyway.

-- 

Bug#838166: linux-image-4.7.0-1-grsec-amd64: proc_thermal 0000:00:04.0: Unsupported event [0x84]

[xiscu]

Package: src:linux
Version: 4.7.2-1+grsec201608211829+2
Severity: wishlist

Dear Maintainer,
the system is logging following event:

 proc_thermal :00:04.0: Unsupported event [0x84]

Please add support for it,

Thanks in advance,
xiscu

-- Package-specific info:
** Version:
Linux version 4.7.0-1-grsec-amd64 (cor...@debian.org) (gcc version 5.4.1 
20160803 (Debian 5.4.1-1) ) #1 SMP Debian 4.7.2-1+grsec201608211829+2 
(2016-09-02)

** Command line:

-- System Information:
Debian Release: stretch/sid
Architecture: amd64 (x86_64)

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

Versions of packages linux-image-4.7.0-1-grsec-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.125
ii  kmod22-1.1
ii  linux-base  4.4
ii  linux-grsec-base6

Versions of packages linux-image-4.7.0-1-grsec-amd64 recommends:
ii  attr 1:2.4.47-2
ii  firmware-linux-free  3.4
ii  gradm2   3.1~201603152148-1
ii  irqbalance   1.1.0-2
ii  paxctl   0.9-1

Versions of packages linux-image-4.7.0-1-grsec-amd64 suggests:
ii  debian-kernel-handbook  1.0.17
ii  extlinux3:6.03+dfsg-14
ii  grub-pc 2.02~beta2-36
ii  linux-doc-4.7   4.7.2-1

Versions of packages linux-image-4.7.0-1-grsec-amd64 is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
ii  firmware-iwlwifi  20160110-1
pn  firmware-libertas 
pn  firmware-linux-nonfree
pn  firmware-misc-nonfree 
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- debconf-show failed

# lspci
00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 09)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation Device 0a03 (rev 09)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM (rev 
04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4)
00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev e4)
00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4)
00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI 
mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 8 Series Thermal (rev 
04)
02:00.0 Unassigned class [ff00]: Alcor Micro AU6601 PCI-E Flash card reader 
controller
03:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

# dmesg | grep ACPI 
[0.00] BIOS-e820: [mem 0xc8161000-0xc8167fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xd9c96000-0xda9a4fff] ACPI NVS
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000F0490 24 (v02 _ASUS_)
[0.00] ACPI: XSDT 0xD9D1A0A0 BC (v01 _ASUS_ Notebook 
01072009 AMI  00010013)
[0.00] ACPI: FACP 0xD9D313A8 00010C (v05 _ASUS_ Notebook 
01072009 AMI  00010013)
[0.00] ACPI: DSDT 0xD9D1A278 017130 (v02 _ASUS_ Notebook 
0012 INTL 20120711)
[0.00] ACPI: FACS 0xDA9A2F80 40
[0.00] ACPI: APIC 0xD9D314B8 72 (v03 _ASUS_ Notebook 
01072009 AMI  00010013)
[0.00] ACPI: FPDT 0xD9D31530 44 (v01 _ASUS_ Notebook 
01072009 AMI  00010013)
[0.00] ACPI: ECDT 0xD9D31578 C1 (v01 _ASUS_ Notebook 
01072009 AMI. 0005)
[0.00] ACPI: LPIT 0xD9D31640 94 (v01 ALASKA  
 AMI. 0005)
[0.00] ACPI: SLIC 0xD9D316D8 000176 (v01 _ASUS_ Notebook 
01072009 ASUS 0001)
[0.00] ACPI: SSDT 0xD9D31850 000539 (v01 PmRef  Cpu0Ist  
3000 INTL 20120711)
[0.00] ACPI: SSDT 0xD9D31D90 000AD8 (v01 PmRef  CpuPm

Bug#791419: Through times of full screen(F11) an back , terminal become smaller

[Mike Neilly]

Package: gnome-terminal
Version: 3.14.1-1+deb8u1
Followup-For: Bug #791419

Dear Maintainer,

I still see this in Debian 8.6. The following video demonstrates the issue:

https://youtu.be/KTYCXicvSTY


-- System Information:
Debian Release: 8.6
  APT prefers experimental
  APT policy: (1000, 'experimental'), (500, 'stable-updates'), (500, 'stable'), 
(100, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages gnome-terminal depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  gconf-service3.2.6-3
ii  gnome-terminal-data  3.14.1-1+deb8u1
ii  gsettings-desktop-schemas3.14.1-1
ii  libatk1.0-0  2.14.0-1
ii  libc62.19-18+deb8u6
ii  libcairo-gobject21.14.0-2.1+deb8u1
ii  libcairo21.14.0-2.1+deb8u1
ii  libdconf10.22.0-1
ii  libgconf-2-4 3.2.6-3
ii  libgdk-pixbuf2.0-0   2.31.1-2+deb8u5
ii  libglib2.0-0 2.42.1-1+b1
ii  libgtk-3-0   3.14.5-1+deb8u1
ii  libnautilus-extension1a  3.14.1-2
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libuuid1 2.25.2-6
ii  libvte-2.91-00.38.1-2
ii  libx11-6 2:1.6.2-3

Versions of packages gnome-terminal recommends:
ii  dbus-x11  1.8.20-0+deb8u1
ii  gvfs  1.22.2-1
ii  yelp  3.14.1-1

gnome-terminal suggests no packages.

-- no debconf information

Bug#838142: mate-panel: stickynotes-app crashes with segfault

[Julian]

Package: mate-panel
Version: 1.14.2-1
Followup-For: Bug #838142

Since it started around the same time it could be related to #837889 and
https://github.com/mate-desktop/caja/issues/627



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

Kernel: Linux 4.6.0-1-amd64 (SMP w/2 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 mate-panel depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-1
ii  libatk1.0-0  2.21.90-2
ii  libc62.23-5
ii  libcairo-gobject21.14.6-1+b1
ii  libcairo21.14.6-1+b1
ii  libcanberra-gtk3-0   0.30-3
ii  libcanberra0 0.30-3
ii  libdbus-1-3  1.10.10-1
ii  libdbus-glib-1-2 0.108-1
ii  libdconf10.26.0-1
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.49.6-1
ii  libgtk-3-0   3.21.5-3
ii  libice6  2:1.0.9-1+b1
ii  libmate-desktop-2-17 1.14.1-1
ii  libmate-menu21.14.0-1
ii  libmate-panel-applet-4-1 1.14.2-1
ii  libmateweather1  1.14.1-1
ii  libpango-1.0-0   1.40.2-1
ii  libpangocairo-1.0-0  1.40.2-1
ii  librsvg2-2   2.40.16-1
ii  libsm6   2:1.2.2-1+b1
ii  libstartup-notification0 0.12-4
ii  libwnck-3-0  3.20.1-1
ii  libx11-6 2:1.6.3-1
ii  libxau6  1:1.0.8-1
ii  libxrandr2   2:1.5.0-1
ii  mate-desktop 1.14.1-1
ii  mate-menus   1.14.0-1
ii  mate-panel-common1.14.2-1
ii  mate-polkit  1.14.0-1
ii  menu-xdg 0.5

mate-panel recommends no packages.

mate-panel suggests no packages.

-- no debconf information

Bug#838001: [pkg-cryptsetup-devel] Bug#838001: cryptsetup does not support ZFS

[Guilhem Moulin]

Hi Richard,

On Fri, 16 Sep 2016 at 04:32:24 -0500, Richard Laager wrote:
> The attached patch adds ZFS support to cryptsetup.

Thanks the patch.  Unfortunately I can't test it easily, and I know
nothing about ZFS, but I'll try to review your patch anyway.

> + zfs list -H -o name,canmount,mountpoint 2>/dev/null | \

Looks like there is support for ZFS filesystems in the /etc/fstab
.  Since
it's what other FS are using, I think that's what we should use for ZFS
too.  Don't the ‘name’ and ‘mountpoint’ columns of your ‘zfs list’
command respectively correspond to the first and second columns of
fstab(5)?

> + for dev in $(zpool status -P "${name%%/*}" 2>/dev/null 
> | awk '($1 ~ /\//) {print $1}'); do

This looks rather brittle, as the ‘status’ command seems to be intended
for humans not parsers.  Isn't there a more robust way to retrieve the
underlying device list of a ZFS pool?  (FWIW, our current solution for
BTRFS volumes isn't satisfactory either.)

Cheers,
-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#837629: OpenRD* with debian's u-boot 2016.09

[Rick Thomas]

On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian  wrote:

> There is at one report of an OpenRD ultimate that would not boot with
> the 2016.09~rc2 version of u-boot in debian. Uploaded 2016.09+dfsg-1 to
> unstable a few days ago. Would you be able to confirm if OpenRD variants
> that you have still work with the version in unstable?
> 
>  https://bugs.debian.org/837629
> 
> If it can't be fixed, I'll likely remove OpenRD ultimate at some point
> so that u-boot 2016.09 can migrate to stretch... but it would be more
> ideal to fix it, of course! :)
> 
> 
> live well,
>  vagrant

Sorry!

It looks like you’ll have to pull OpenRD support out of this version.  I tried 
2016.09+dfsg-1 on my OpenRD “Client”.  I got the same result with it as I got 
with 2016.09~rc2+dfsg1-1 on the “Ultimate”, no response following u-boot 
“reset” command.

Enjoy!
Rick

Bug#838165: Bug in package gstreamer1.0-plugins-base_1.8.3-1_amd64, apt-get is not able to install it due to broken pipe error in debian SID

[flipefr]

Package: gstreamer1.0-plugins-base Version: 1.8.3-1:amd64

Severity: serious

I cannot install the package in Debian-SID, here is the shell output in Spanish 
(please read below for same message in English):

=SPANISH
> sudo apt-get -f install
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias
Leyendo la información de estado... Hecho
Corrigiendo dependencias... Listo
Los paquetes indicados a continuación se instalaron de forma automática y ya no 
son necesarios.
libc6-i686:i386 libcommons-net2-java libdata-alias-perl libjetty-java 
libkactivities-bin libkactivities-models1 libnepomukcore4 nepomuk-core-data 
python-dns timelimit vlc-plugin-notify
Utilice «sudo apt autoremove» para eliminarlos.
Se instalarán los siguientes paquetes adicionales:
gstreamer1.0-plugins-base
Se actualizarán los siguientes paquetes:
gstreamer1.0-plugins-base
1 actualizados, 0 nuevos se instalarán, 0 para eliminar y 606 no actualizados.
17 no instalados del todo o eliminados.
Se necesita descargar 0 B/1.394 kB de archivos.
Se liberarán 3.072 B después de esta operación.
¿Desea continuar? [S/n] s
Obteniendo informes de fallo... Finalizado
Analizando información Encontrada/Corregida... Finalizado
Leyendo lista de cambios... Hecho.
dpkg: atención: falta el fichero de lista de ficheros del paquete 
`gstreamer1.0-plugins-base:amd64', se supondrá que el paquete no tiene ningún 
fichero actualmente instalado
(Leyendo la base de datos ... 310835 ficheros o directorios instalados 
actualmente.)
Preparando para desempaquetar .../gstreamer1.0-plugins-base_1.8.3-1_amd64.deb 
...
Desempaquetando gstreamer1.0-plugins-base:amd64 (1.8.3-1) sobre (1.4.4-2) ...
dpkg: error al procesar el archivo 
/var/cache/apt/archives/gstreamer1.0-plugins-base_1.8.3-1_amd64.deb (--unpack):
intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstopus.so', que está también en el 
paquete gstreamer1.0-plugins-bad:amd64 1:1.6.3-dmo2
dpkg-deb: error: el subproceso copiado fue terminado por la señal (Tubería rota)
Se encontraron errores al procesar:
/var/cache/apt/archives/gstreamer1.0-plugins-base_1.8.3-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
=

Let me translate a couple of lines:
=SPANISH
dpkg: error al procesar el archivo 
/var/cache/apt/archives/gstreamer1.0-plugins-base_1.8.3-1_amd64.deb (--unpack):
intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstopus.so', que está también en el 
paquete gstreamer1.0-plugins-bad:amd64 1:1.6.3-dmo2
dpkg-deb: error: el subproceso copiado fue terminado por la señal (Tubería rota)
Se encontraron errores al procesar:
/var/cache/apt/archives/gstreamer1.0-plugins-base_1.8.3-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
=ENGLISH
dpkg: error processing file 
/var/cache/apt/archives/gstreamer1.0-plugins-base_1.8.3-1_amd64.deb (--unpack):
trying to override `/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstopus.so', 
which is also in the package gstreamer1.0-plugins-bad:amd64 1:1.6.3-dmo2
dpkg-deb: error: subprocess copy was terminated by the signal (Broken Pipe)
Errors were found processing:
/var/cache/apt/archives/gstreamer1.0-plugins-base_1.8.3-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
=

I am using Debian sid, kernel 4.1.24-10.pvops.qubes.x86_64

Thanks,
Felipe

Bug#838164: please package new version 0.5.0

[W. Martin Borgert]

Package: profanity
Version: 0.4.7-1
Severity: wishlist

https://github.com/boothj5/profanity/blob/master/CHANGELOG
lists many new and nice features. Thank you!

Bug#838163: linux-image-4.7.0-1-amd64: Kernel 4.7 seems to have broken battery status on MacBookPro11, 1

[Robert Ou]

Package: src:linux
Version: 4.7.2-1+s1
Severity: normal

Dear Maintainer,

After upgrading the kernel to version 4.7, my laptop does not seem to be
able to report battery status anymore. Both xfce4-power-manager and the
"acpi -b" command fail to report a battery status. The kernel dmesg has a
message "sbs: probe of ACPI0002:00 failed with error -62" that is
probably related. I'm pretty sure that this was working on kernel
version 4.6.


-- Package-specific info:
** Version:
Linux version 4.7.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.1 
20160803 (Debian 5.4.1-1) ) #1 SMP Debian 4.7.2-1 (2016-08-28)

** Command line:
BOOT_IMAGE=/vmlinuz-4.7.0-1-amd64 
root=UUID=60978242-e521-42fb-a010-9991813948e3 ro rootflags=subvol=debian 
cgroup_enable=memory intel_iommu=on quiet

** Tainted: POE (12289)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded (currently expected).
** Kernel log:
[   13.122859] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   13.122863] [drm] Driver supports precise vblank timestamp query.
[   13.123403] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   13.143662] ACPI: Video Device [IGPU] (multi-head: yes  rom: no  post: no)
[   13.144354] acpi device:02: registered as cooling_device5
[   13.144507] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input13
[   13.235231] sbs: probe of ACPI0002:00 failed with error -62
[   13.395420] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   13.395439] [drm] Initialized i915 1.6.0 20160425 for :00:02.0 on minor 0
[   13.395752] i801_smbus :00:1f.3: SMBus using PCI interrupt
[   13.413185] fbcon: inteldrmfb (fb0) is primary device
[   13.417446] input: HDA Intel HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.0/sound/card0/input14
[   13.417561] input: HDA Intel HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.0/sound/card0/input15
[   13.417668] input: HDA Intel HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.0/sound/card0/input16
[   13.450356] thunderbolt :07:00.0: initializing Switch at 0x0 (depth: 0, 
up port: 5)
[   13.450358] thunderbolt :07:00.0: old switch config:
[   13.450361] thunderbolt :07:00.0:  Switch: 8086:156d (Revision: 0, TB 
Version: 2)
[   13.450362] thunderbolt :07:00.0:   Max Port Number: 12
[   13.450364] thunderbolt :07:00.0:   Config:
[   13.450366] thunderbolt :07:00.0:Upstream Port Number: 5 Depth: 0 
Route String: 0x0 Enabled: 1, PlugEventsDelay: 255ms
[   13.450367] thunderbolt :07:00.0:unknown1: 0x0 unknown4: 0x0
[   13.450369] thunderbolt :07:00.0: 0: unsupported switch device id 0x156d
[   13.481674] thunderbolt :07:00.0: 0: uid: 0x1000f049dd2e0
[   13.481773] thunderbolt :07:00.0:  Port 0: 8086:156d (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[   13.481774] thunderbolt :07:00.0:   Max hop id (in/out): 7/7
[   13.481775] thunderbolt :07:00.0:   Max counters: 8
[   13.481776] thunderbolt :07:00.0:   NFC Credits: 0x70
[   13.482270] thunderbolt :07:00.0:  Port 1: 8086:156d (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[   13.482271] thunderbolt :07:00.0:   Max hop id (in/out): 15/15
[   13.482272] thunderbolt :07:00.0:   Max counters: 16
[   13.482273] thunderbolt :07:00.0:   NFC Credits: 0x3c0
[   13.482769] thunderbolt :07:00.0:  Port 2: 8086:156d (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[   13.482770] thunderbolt :07:00.0:   Max hop id (in/out): 15/15
[   13.482771] thunderbolt :07:00.0:   Max counters: 16
[   13.482772] thunderbolt :07:00.0:   NFC Credits: 0x3c0
[   13.483301] thunderbolt :07:00.0:  Port 3: 8086:156d (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[   13.483302] thunderbolt :07:00.0:   Max hop id (in/out): 15/15
[   13.483303] thunderbolt :07:00.0:   Max counters: 16
[   13.483304] thunderbolt :07:00.0:   NFC Credits: 0x3c0
[   13.483768] thunderbolt :07:00.0:  Port 4: 8086:156d (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[   13.483769] thunderbolt :07:00.0:   Max hop id (in/out): 15/15
[   13.483770] thunderbolt :07:00.0:   Max counters: 16
[   13.483770] thunderbolt :07:00.0:   NFC Credits: 0x3c0
[   13.483868] thunderbolt :07:00.0:  Port 5: 8086:156d (Revision: 0, TB 
Version: 1, Type: NHI (0x2))
[   13.483869] thunderbolt :07:00.0:   Max hop id (in/out): 11/11
[   13.483870] thunderbolt :07:00.0:   Max counters: 16
[   13.483871] thunderbolt :07:00.0:   NFC Credits: 0xf0
[   13.483968] thunderbolt :07:00.0:  Port 6: 8086:156d (Revision: 0, TB 
Version: 1, Type: PCIe (0x100101))
[   13.483969] thunderbolt :07:00.0:   Max hop id (in/out): 8/8
[   13.483970] thunderbolt :07:00.0:   Max counters: 2
[   13.483971] thunderbolt :07:00.0:   NFC Credits: 0x70
[   

Bug#838109: release.debian.org: binNMU for ccache/amd64 to rebuild against stable

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2016-09-17 at 13:00 +0100, Adam D. Barratt wrote:
> Whilst performing some checks during today's point release, we noticed
> that a new "ccache-dbgsym" binary package appeared on amd64. Neither the
> debhelper version in stable nor stable-backports will generate such
> packages, implying that the upload was built in another, or unclean,
> environment.

I scheduled the binNMU, and it's now in proposed-updates.

Regards,

Adam

Bug#836993: qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis'

[Sebastiaan Couwenberg]

Control: tags -1 pending

Hi Andreas,

On 09/17/2016 06:39 PM, Andreas Beckmann wrote:
> still not completely resolved,

Will the third time be the charm?

I haven't been able to reproduce this issue with my piuparts setup, not
now and not before, I guess piuparts.d.o. does something more
complicated than:

 piuparts -d jessie -d stretch -a qgis

I have now been able reproduce this issue manually in a jessie
cowbuilder chroot by installing qgis (with recommended dependencies),
and upgrading it to stretch via the usual procedure (apt-get upgrade
followed by apt-get dist-upgrade).

> I'll try to find some time to look there myself.
> 
>   Preparing to unpack .../qgis_2.14.6+dfsg-3_amd64.deb ...
>   Unpacking qgis (2.14.6+dfsg-3) over (2.4.0-1+b1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/qgis_2.14.6+dfsg-3_amd64.deb (--unpack):
>trying to overwrite '/usr/bin/qbrowser.bin', which is the diverted version 
> of '/usr/bin/qbrowser' (package: qgis-plugin-grass)

Do you have a more complete log than the above?
piuparts.debian.org/jessie2stretch still reports:

 successfully-tested 2.14.5+dfsg-2

Since the unpack is already failing, I think the diversion should also
be removed by the maintainer scripts for qgis-plugin-grass, not just
qgis as it is now. I suspect the complete log to confirm that
qgis-plugin-grass is upgraded before qgis is, that's what I'm seeing in
my jessie to stretch upgrade.

Some testing of the above reveals that adding the maintainers scripts to
qgis-plugin-grass to remove the diversion is not sufficient. The jessie
version of qgis-plugin-grass only removes the diversion in postrm which
is called after the new package's files are unpacked which is too late
because the unpackaging causes the error.

I think the jessie version of qgis needs to be fixed to remove the
diversion in qgis-plugin-grass.prerm too, because a version of the
package is already "Installed".

Because the qgis-plugin-grass package is being upgraded, the new preinst
could also remove the diversions before the new package's files are
unpacked. But unfortunately that fails with:

dpkg-divert: error: rename involves overwriting `/usr/bin/qgis.bin' with
  different file `/usr/bin/qgis', not allowed

Just removing without renaming in qgis.preinst could be the actual
solution, it seems to give the desired results:

Preparing to unpack .../qgis_2.14.6+dfsg-4_amd64.deb ...
Removing 'diversion of /usr/bin/qgis to /usr/bin/qgis.bin by
qgis-plugin-grass'
Removing 'diversion of /usr/bin/qbrowser to /usr/bin/qbrowser.bin by
qgis-plugin-grass'
Unpacking qgis (2.14.6+dfsg-4) over (2.4.0-1+b1) ...

It's a much simpler change in addition to the one fixing #817176, I
should have thought of that sooner before you led me astray with your
suggestions in this issue.

I'm going to upload the above which should finally fix this issue.

Kind Regards,

Bas

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

Bug#838162: reportbug: Fails to retrieve bug information

[Julian]

Package: reportbug
Version: 6.6.6
Severity: normal

Hi,

Trying to retrieve a bug report (in my case #837889).
The progress bar animation stops after a few seconds and nothing happens
anymore. The window can be closed.
Console output says:

No handlers could be found for logger "pysimplesoap.simplexml"
Exception in thread None:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
self.run()
  File "/usr/lib/python2.7/dist-packages/reportbug/ui/gtk2_ui.py", line 361, in
run
http_proxy=self.http_proxy, archived=self.archived)
  File "/usr/lib/python2.7/dist-packages/reportbug/debbugs.py", line 1405, in
get_report
log = debianbts.get_bug_log(number)
  File "/usr/lib/python2.7/dist-packages/debianbts.py", line 320, in
get_bug_log
reply = _soap_client_call('get_bug_log', nr)
  File "/usr/lib/python2.7/dist-packages/debianbts.py", line 491, in
_soap_client_call
return getattr(soap_client, method_name)(soap_client, *soap_args)
  File "/usr/lib/python2.7/dist-packages/pysimplesoap/client.py", line 179, in

return lambda self=self, *args, **kwargs: self.call(attr, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/pysimplesoap/client.py", line 262, in
call
jetty=self.__soap_server in ('jetty',))
  File "/usr/lib/python2.7/dist-packages/pysimplesoap/simplexml.py", line 56,
in __init__
self.__document = xml.dom.minidom.parseString(text)
  File "/usr/lib/python2.7/xml/dom/minidom.py", line 1928, in parseString
return expatbuilder.parseString(string)
  File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 940, in parseString
return builder.parseString(string)
  File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 223, in parseString
parser.Parse(string, True)
ExpatError: syntax error: line 1, column 49

sys.excepthook is missing
lost sys.stderr



-- Package-specific info:
** Environment settings:
INTERFACE="gtk2"

** /home/styxxx/.reportbugrc:
reportbug_version "6.6.6"
mode advanced
ui gtk2
email "deb...@styxxx.de"
smtphost "mail.belwue.de:587"

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/2 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 reportbug depends on:
ii  apt   1.3~rc4
ii  python-reportbug  6.6.6
pn  python:any

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
pn  debconf-utils  
pn  debsums
pn  dlocate
pn  emacs23-bin-common | emacs24-bin-common
ii  exim4  4.87-3
ii  exim4-daemon-light [mail-transport-agent]  4.87-3
ii  file   1:5.28-4
ii  gnupg  1.4.20-6
ii  python-gtk22.24.0-5
ii  python-gtkspellcheck   3.0-1.1
pn  python-urwid   
ii  python-vte 1:0.28.2-5+b1
ii  xdg-utils  1.1.1-1

Versions of packages python-reportbug depends on:
ii  apt   1.3~rc4
ii  file  1:5.28-4
ii  python-debian 0.1.29
ii  python-debianbts  2.6.1
pn  python:any

python-reportbug suggests no packages.

-- no debconf information

Bug#838161: rtl-sdr: incorrect invocation of rm_conffile

[Chris Lamb]

Source: rtl-sdr
Version: 0.5.3-10
Severity: important
Tags: patch

Hi,

Upon installation, I see:

  Preparing to unpack .../0-librtlsdr0_0.5.3-10_amd64.deb ...
  dpkg: warning: version '--' has bad syntax: version number does not start 
with digit

Your debian/librtlsdr0.maintscript file contains:
 
  rm_conffile /etc/modprobe.d/rtl-sdr-blacklist.conf 0.5.3-10~ -- "$@"

.. but in dh_installdeb(1):

   package.maintscript
   Lines in this file correspond to dpkg-maintscript-helper(1)
   commands and parameters.  However, the "maint-script-
   parameters" should not be included as debhelper will add those
   automatically.

   Example:

   # Correct
   rm_conffile /etc/obsolete.conf 0.2~ foo
   # INCORRECT
   rm_conffile /etc/obsolete.conf 0.2~ foo -- "$@"


Patch attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/debian/librtlsdr0.maintscript b/debian/librtlsdr0.maintscript
index e0c6648..9819521 100644
--- a/debian/librtlsdr0.maintscript
+++ b/debian/librtlsdr0.maintscript
@@ -1 +1 @@
-rm_conffile /etc/modprobe.d/rtl-sdr-blacklist.conf 0.5.3-10~ -- "$@"
+rm_conffile /etc/modprobe.d/rtl-sdr-blacklist.conf 0.5.3-10~

Bug#692105: Removing c-cpp-reference from Debian?

[Pino Toscano]

In data domenica 18 settembre 2016 00:18:41 CEST, Adrian Bunk ha scritto:
> I would like to get an opinion from you as maintainers of KDevelop
> on removal of c-cpp-reference from Debian.
> 
> It seems to be a 15-20 year old reference for KDevelop that comes from 
> http://kdevelop.org

s/comes/it used to come/

Considering the times the kdevelop.org website has changed since that
guide was picked, I really doubt it can be found anywhere else.

> Does it make any sense for KDevelop today?

It seems updated last in KDE 3 times at best, and I I'm pretty sure
recent versions of kdevelop don't even know about it. So no, it does
not make sense, especially ...

> After a quick look at the C part there are tutorial parts that are 
> still useful today, but there are many (including better) tutorials
> available online.

... because of this.

-- 
Pino Toscano

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

Bug#834960: libdaemon-generic-perl: FTBFS too much often (failing tests)

[gregor herrmann]

On Sat, 17 Sep 2016 21:27:33 +0300, Niko Tyni wrote:

> > From starting at t/daemon.t my guess is that we're seeing a race
> > condition or some other timing issue here -- the daemon writes to a
> > log file and the test reads the logfile, and in one case the log
> > message doesn't seem to be there (yet?). At least that's my current
> > guess.
> Indeed, the daemon first opens the file for writing and only then writes
> it (see the logger script at top of daemon.t), while the test waits for
> existence (-e) and then proceeds to check the file contents.
> 
> I think the attached patch should fix it. I was able to reproduce
> the issue sporadically without the patch, and couldn't get it to
> happen after applying this.

Great, thanks.
 
> > I'm tempted to mark this log-reading test as TODO since this seems a
> > bit fragile.
> No objections, but let's try the patch first?

Sure, a fix is always better than a workaround :)


Patch forwarded upstream, package uploaded.


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Tony Joe White: Goin' Down Rockin'


signature.asc
Description: Digital Signature

Bug#834960: Pending fixes for bugs in the libdaemon-generic-perl package

[pkg-perl-maintainers]

tag 834960 + pending
thanks

Some bugs in the libdaemon-generic-perl package are closed in
revision 75331d5d9ccbf69f8b7c3a410ef189dd1eb791a2 in branch 'master'
by gregor herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libdaemon-generic-perl.git/commit/?id=75331d5

Commit message:

Add patch to fix race condition in test suite.

Thanks: Niko Tyni for the patch.
Closes: #834960

Bug#836603: [Pkg-opencl-devel] Bug#836603: beignet: Please use llvm 3.8 or, better, 3.9

[Adrian Bunk]

On Sun, Sep 04, 2016 at 02:14:35PM +0100, Rebecca N. Palmer wrote:
>...
> > This package depends on llvm-toolchain-3.7.
> Only on kfreebsd-* (which aren't release architectures, and can't build
> anything more recent).
>...

Is this something that is expected to be fixed soon, or would removal of 
the kfreebsd binaries of beignet be appropriate?

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#838160: RFS: globjects/0.5.0-1 [experimental]

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: globjects
  Version : 0.5.0-1
  Upstream Author : CG Internals
* URL : http://globjects.org/
* License : Expat
  Section : libs

It builds those binary packages:

  globjects-doc - documentation for globjects
  libglobjects-dev - development files for globjects
  libglobjects0 - cross-platform C++ wrapper for OpenGL API objects

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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/g/globjects/globjects_0.5.0-1.dsc


Successful builds on debomatic:


http://debomatic-amd64.debian.net/distribution#experimental/globjects/0.5.0-1/autopkgtest

http://debomatic-i386.debian.net/distribution#experimental/globjects/0.5.0-1/autopkgtest

http://debomatic-arm64.debian.net/distribution#experimental/globjects/0.5.0-1/autopkgtest 



Changes since the last upload:

  * Initial release. (Closes: #837464)

Regards,
Ghislain Vaillant

Bug#838159: dbconfig-common: Fix missing backticks in MySQL "DROP DATABASE" statement

[Matthias Pigulla]

Package: dbconfig-common
Version: 2.0.4~bpo8+1
Severity: normal
Tags: patch

Dear Maintainer,

when using special characters like a "-" in the database name,
uninstallation fails because the "DROP DATABASE" statement
generated does not use backticks to escape the name.

The patch adds backticks to the SQL statement in question. With those in
place, uninstallation succeeds as expected.

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

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

Versions of packages dbconfig-common depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  ucf3.0030

dbconfig-common recommends no packages.

Versions of packages dbconfig-common suggests:
pn  dbconfig-mysql | dbconfig-pgsql | dbconfig-sqlite | dbconfig-sqlite  

-- debconf information excluded
--- /usr/share/dbconfig-common/internal/mysql.orig	2016-09-17 12:18:23.946798604 +
+++ /usr/share/dbconfig-common/internal/mysql	2016-09-17 12:19:36.907257043 +
@@ -215,7 +215,7 @@
 dbc_logpart "dropping database $dbc_dbname:"
 
 if _dbc_mysql_check_database "$dbc_dbname"; then
-if dbc_mysql_exec_command "DROP DATABASE $dbc_dbname"; then
+if dbc_mysql_exec_command "DROP DATABASE \`$dbc_dbname\`"; then
 dbc_logline "success"
 dbc_logpart "verifying database $dbc_dbname was dropped:"
 if _dbc_mysql_check_database "$dbc_dbname"; then

Bug#838148: autogen: FTBFS on hurd-i386

[Bruce Korb]

--- error.test.original 2016-09-17 18:13:22.0 +
+++ error.test  2016-09-17 18:13:25.0 +
@@ -48,6 +48,7 @@
/^Aborte.*core dumped/q
p'

+  rm -f core
   ${SED} -n "${sedcmd}" $1
 }


Maybe remove anything starting with "core" since that name is oftentimes 
suffixed with a PID number.

Bug#838155: caja: Caja does not open in Debian Testing Stretch using Mate Desktop.

[Jonathan Bustillos]

Package: caja
Version: 1.14.2-1
Followup-For: Bug #838155

This is the output if you execute caja in a shell:

jathan@debian:~$ caja

(caja:15898): Gtk-WARNING **: Theme parsing error: 
mate-applications.css:415:16: not a number

(caja:15898): Gtk-WARNING **: Theme parsing error: 
mate-applications.css:415:16: Expected a string.

(caja:15898): Gtk-WARNING **: Theme parsing error: 
other-applications.css:146:13: not a number

(caja:15898): Gtk-WARNING **: Theme parsing error: 
other-applications.css:146:13: Expected a string.
jathan@debian:~$ 

Regards.

Jathan

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

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

Versions of packages caja depends on:
ii  caja-common   1.14.2-1
ii  desktop-file-utils0.23-1
ii  gvfs  1.29.91-1
ii  libatk1.0-0   2.21.90-2
ii  libc6 2.23-5
ii  libcairo-gobject2 1.14.6-1+b1
ii  libcairo2 1.14.6-1+b1
ii  libcaja-extension11.14.2-1
ii  libexempi32.3.0-2
ii  libexif12 0.6.21-2
ii  libgail-3-0   3.21.5-3
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.49.6-1
ii  libglib2.0-data   2.49.6-1
ii  libgtk-3-03.21.5-3
ii  libice6   2:1.0.9-1+b1
ii  libmate-desktop-2-17  1.14.1-1
ii  libpango-1.0-01.40.2-1
ii  libpangocairo-1.0-0   1.40.2-1
ii  libselinux1   2.5-3
ii  libsm62:1.2.2-1+b1
ii  libstartup-notification0  0.12-4
ii  libunique-3.0-0   3.0.2-2
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.4+dfsg1-1+b1
ii  libxrender1   1:0.9.9-2
ii  mate-desktop  1.14.1-1
ii  shared-mime-info  1.7-1

Versions of packages caja recommends:
ii  gvfs-backends  1.29.91-1

Versions of packages caja suggests:
ii  engrampa1.14.1-1
pn  gstreamer1.0-tools  
pn  meld

-- no debconf information

Bug#804680:

[Joseph Herlant]

Hi,

This bug is fixed with the latest version currently on the review
process in Mentors:
https://mentors.debian.net/package/gnome-shell-pomodoro
It will be uploaded when validated by my mentor.

If you feel like double checking the new package, every constructive
comment is welcome! :-)

Thanks,
Joseph

Bug#837388: jessie-pu: package scons-doc/2.3.1-1

[Adam D. Barratt]

Control: tags -1 + moreinfo

On Sun, 2016-09-11 at 11:13 +0200, Jörg Frings-Fürst wrote:
> the version 2.3.1-1 contains non free svg files[1].
> The attached debdiff replace them with free files from upstream.

So far as I can tell, the situation is that:

- the files are "only" non-free, not also non-distributable
- "replacing" the files in practice just means changing the license
information embedded within the files
- Debian has a valid license to distribute the files under, which is
already documented in the package in unstable

Is all of the above correct? If so, we have generally treated such
situations as representing documentation updates, which means they can
be included as part of uploads to stable alongside other fixes, but not
usually on their own.

Regards,

Adam

Bug#838096: network-manager drives broadcom driver into confused state

[Eduard Bloch]

Hallo,
* Michael Biebl [Sat, Sep 17 2016, 02:10:25PM]:
> Control: owner -1 bl...@unix-ag.uni-kl.de
> 
> 
> [Please always CC the maintainer of the package you are going to
> reassign the package to. Otherwise she/he get's a contextless control
> message which is highly annoying]

Right, right.

> Could you add
> 
> [device]
> wifi.scan-rand-mac-address=no
> 
> to your NetworkManager.conf and see if that changes anything.
> 
> This smells like [1]

Interesting, it partly helps! I can select hotspots with nmcli now and
it seems to be ok so far.

However, now nm-applet does not work anymore. I tried to investigate
strace output and couldn't see the reason. It simply shuts down and
exits shortly after some dbus communication. I tried to trace that
communication but the results are inconclusive (at least IMHO):

method call time=1474147396.626442 sender=:1.32 -> 
destination=org.freedesktop.DBus serial=1 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=Hello
method return time=1474147396.626495 sender=org.freedesktop.DBus -> 
destination=:1.32 serial=1 reply_serial=1
   string ":1.32"
signal time=1474147396.626524 sender=org.freedesktop.DBus -> destination=(null 
destination) serial=34 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.32"
   string ""
   string ":1.32"
signal time=1474147396.626561 sender=org.freedesktop.DBus -> destination=:1.32 
serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; 
member=NameAcquired
   string ":1.32"
method call time=1474147396.628220 sender=:1.32 -> 
destination=org.freedesktop.DBus serial=2 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=RequestName
   string "org.freedesktop.network-manager-applet"
   uint32 4
method return time=1474147396.628298 sender=org.freedesktop.DBus -> 
destination=:1.32 serial=3 reply_serial=2
   uint32 3
method call time=1474147396.629530 sender=:1.32 -> 
destination=org.freedesktop.DBus serial=3 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=AddMatch
   string 
"type='signal',sender='org.freedesktop.network-manager-applet',interface='org.gtk.Actions',member='Changed',path='/org/freedesktop/network_manager_applet'"
method return time=1474147396.629586 sender=org.freedesktop.DBus -> 
destination=:1.32 serial=4 reply_serial=3
method call time=1474147396.630210 sender=:1.32 -> 
destination=org.freedesktop.network-manager-applet serial=4 
path=/org/freedesktop/network_manager_applet; interface=org.gtk.Actions; 
member=DescribeAll
method return time=1474147396.630559 sender=:1.5 -> destination=:1.32 serial=85 
reply_serial=4
   array [
   ]
method call time=1474147396.631686 sender=:1.32 -> 
destination=org.freedesktop.network-manager-applet serial=5 
path=/org/freedesktop/network_manager_applet; interface=org.gtk.Application; 
member=Activate
   array [
  dict entry(
 string "cwd"
 variant array of bytes "/tmp" + \0
  )
   ]
signal time=1474147396.641525 sender=org.freedesktop.DBus -> destination=:1.32 
serial=5 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; 
member=NameLost
   string ":1.32"
signal time=1474147396.641597 sender=org.freedesktop.DBus -> destination=(null 
destination) serial=35 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.32"
   string ":1.32"
   string ""

Regards,
Eduard.


signature.asc
Description: PGP signature

Bug#837607: jessie-pu: package elog/2.9.2+2014.05.11git44800a7-2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2016-09-12 at 22:32 +0200, Roger Kalt wrote:
> Update closes bug https://bugs.debian.org/836505 which allowed to post entry 
> as
> arbitrary username by improper authentication.

+elog (2.9.2+2014.05.11git44800a7-3) jessie; urgency=medium
+
+  * Added patch 0005_elogd_CVE-2016-6342_fix to fix posting entry as
+arbitrary username (Closes: #836505, CVE-2016-6342)

The version number should be "2.9.2+2014.05.11git44800a7-2+deb8u1",
please. With that change, please go ahead.

Regards,

Adam

Bug#837575: jessie-pu: package suckless-tools/40-1+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2016-09-12 at 17:40 +0300, Ilias Tsitsimpis wrote:

> I would like to update suckless-tools in jessie in order to fix a bug in
> the slock command (CVE-2016-6866).

Please go ahead.

Regards,

Adam

Bug#837558: jessie-pu: package sed/4.2.2-4+deb8u1

[Santiago Vila]

On Sat, Sep 17, 2016 at 10:16:56PM +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Mon, 2016-09-12 at 15:49 +0200, Santiago Vila wrote:
> > I'd like to see Bugs #774347 and #835516 fixed in jessie.
> > (This is the bug that makes /bin to be 775, not 755, on new installs).
> > (Well, maybe not the only one, but the one happening on a required package).
> > 
> > The debdiff would be the attached one, which I've initially extracted from
> > the jessie branch in git (as indicated by the maintainer in Bug #835516),
> > and then cleaned up a little bit to be free from artifacts.
> 
> Please go ahead.

Done. Thank you.

Bug#837458: jessie-pu: package mactelnet/0.4.0-1

[Adam D. Barratt]

Control: tags -1 + moreinfo

On Mon, 2016-09-12 at 06:17 +0200, Salvatore Bonaccorso wrote:
> Hi,
> 
> Disclaimer, I'm not member of the release team/stable release managers.

You are, however, correct in your statements. :-)

> > Request for uploading to stable, as there is posted a CVE for a bug
> > in mactelnet-client.
> > This update is a backport of the fix that is done upstream, that
> > fixes only the mentioned bug.
> 
> Generally the stable release managers request that the fix should land
> first in unstable, could you upload the fix as well there? Or Is there
> a new upstream version which could be uploaded?

Please remove the "moreinfo" tag once that's happened.

Regards,

Adam

Bug#837558: jessie-pu: package sed/4.2.2-4+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2016-09-12 at 15:49 +0200, Santiago Vila wrote:
> I'd like to see Bugs #774347 and #835516 fixed in jessie.
> (This is the bug that makes /bin to be 775, not 755, on new installs).
> (Well, maybe not the only one, but the one happening on a required package).
> 
> The debdiff would be the attached one, which I've initially extracted from
> the jessie branch in git (as indicated by the maintainer in Bug #835516),
> and then cleaned up a little bit to be free from artifacts.

Please go ahead.

Regards,

Adam

Bug#692105: Removing c-cpp-reference from Debian?

[Adrian Bunk]

Hi,

I would like to get an opinion from you as maintainers of KDevelop
on removal of c-cpp-reference from Debian.

It seems to be a 15-20 year old reference for KDevelop that comes from 
http://kdevelop.org

Does it make any sense for KDevelop today?

If yes, kdevelop should suggest it and you should consider adopting it.

If no, I would suggest removal from Debian:
After a quick look at the C part there are tutorial parts that are 
still useful today, but there are many (including better) tutorials
available online.

Thanks
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#838158: apt-file: listing source packages does not appear to work

[Guillem Jover]

Package: apt-file
Version: 3.0
Severity: normal

Hi!

The other day I was doing some QA and was checking source files,
enabled the Contents-dsc stanzas in the apt-file.conf. And run
«apt update». After that, something like this works:

  ,---
  $ time apt-file -I dsc search src/querycmd.c
  dpkg: /src/querycmd.c

  real0m1.000s
  user0m1.020s
  sys 0m0.420s
  $
  `---

but this does not appear to work:

  ,---
  $ time apt-file -I dsc list apt-file

  real0m1.003s
  user0m1.208s
  sys 0m0.364s
  $
  `---

but it still seems to be doing something. :)

Thanks,
Guillem

Bug#837989: openocd: can no longer use SheevaPlug JTAGKey FT2232D (regression)

[David Madore]

On Sat, Sep 17, 2016 at 11:18:20PM +0300, Paul Fertser wrote:
> Hm, can't see anything good about it...

Ah, sorry, as I mentioned, behaviour is somewhat erratic even with
openocd-0.5.0.  This log is definitely good (I was able to upload
U-Boot).  Maybe the comparison between the two can be instructive in
some way?  Also, even in the "bad" case (when "JTAG scan chain
interrogation failed: all zeroes"), openocd-0.5.0 will still let me
issue a reset command which works (whereas openocd-0.9.0 won't even
let me telnet).

Sorry about all the confusion!

-- 
 David A. Madore
   ( http://www.madore.org/~david/ )
Open On-Chip Debugger 0.5.0 (2016-09-16-09:33)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
User : 11 0 command.c:557 command_print(): debug_level: 3
Debug: 12 0 configuration.c:45 add_script_search_dir(): adding 
/home/david/.openocd
Debug: 13 0 configuration.c:45 add_script_search_dir(): adding 
/usr/share/openocd/site
Debug: 14 0 configuration.c:45 add_script_search_dir(): adding 
/usr/share/openocd/scripts
Debug: 15 0 configuration.c:87 find_file(): found 
/tmp/openocd-0.5.0/tcl/board/sheevaplug.cfg
Debug: 16 0 configuration.c:87 find_file(): found 
/tmp/openocd-0.5.0/tcl/interface/sheevaplug.cfg
Debug: 17 0 command.c:151 script_debug(): command - ocd_command ocd_command 
type ocd_interface ft2232
Debug: 18 1 command.c:151 script_debug(): command - interface ocd_interface 
ft2232
Debug: 20 1 command.c:364 register_command_handler(): registering 
'ocd_ft2232_device_desc'...
Debug: 21 1 command.c:364 register_command_handler(): registering 
'ocd_ft2232_serial'...
Debug: 22 1 command.c:364 register_command_handler(): registering 
'ocd_ft2232_layout'...
Debug: 23 1 command.c:364 register_command_handler(): registering 
'ocd_ft2232_vid_pid'...
Debug: 24 1 command.c:364 register_command_handler(): registering 
'ocd_ft2232_latency'...
Info : 25 1 transport.c:123 allow_transports(): only one transport option; 
autoselect 'jtag'
Debug: 26 1 command.c:364 register_command_handler(): registering 
'ocd_jtag_flush_queue_sleep'...
Debug: 27 1 command.c:364 register_command_handler(): registering 
'ocd_jtag_rclk'...
Debug: 28 1 command.c:364 register_command_handler(): registering 
'ocd_jtag_ntrst_delay'...
Debug: 29 1 command.c:364 register_command_handler(): registering 
'ocd_jtag_ntrst_assert_width'...
Debug: 30 1 command.c:364 register_command_handler(): registering 
'ocd_scan_chain'...
Debug: 31 1 command.c:364 register_command_handler(): registering 
'ocd_jtag_reset'...
Debug: 32 1 command.c:364 register_command_handler(): registering 
'ocd_runtest'...
Debug: 33 1 command.c:364 register_command_handler(): registering 
'ocd_irscan'...
Debug: 34 1 command.c:364 register_command_handler(): registering 
'ocd_verify_ircapture'...
Debug: 35 1 command.c:364 register_command_handler(): registering 
'ocd_verify_jtag'...
Debug: 36 1 command.c:364 register_command_handler(): registering 
'ocd_tms_sequence'...
Debug: 37 1 command.c:364 register_command_handler(): registering 
'ocd_wait_srst_deassert'...
Debug: 38 1 command.c:364 register_command_handler(): registering 'ocd_jtag'...
Debug: 39 1 command.c:364 register_command_handler(): registering 'ocd_jtag'...
Debug: 40 1 command.c:364 register_command_handler(): registering 'ocd_jtag'...
Debug: 41 1 command.c:364 register_command_handler(): registering 'ocd_jtag'...
Debug: 42 1 command.c:364 register_command_handler(): registering 'ocd_jtag'...
Debug: 43 1 command.c:364 register_command_handler(): registering 'ocd_jtag'...
Debug: 44 1 command.c:364 register_command_handler(): registering 'ocd_jtag'...
Debug: 45 1 command.c:364 register_command_handler(): registering 'ocd_jtag'...
Debug: 46 1 command.c:364 register_command_handler(): registering 'ocd_jtag'...
Debug: 47 1 command.c:364 register_command_handler(): registering 'ocd_jtag'...
Debug: 48 1 command.c:364 register_command_handler(): registering 'ocd_jtag'...
Debug: 49 1 command.c:364 register_command_handler(): registering 'ocd_jtag'...
Debug: 50 1 command.c:364 register_command_handler(): registering 'ocd_jtag'...
Debug: 51 1 command.c:364 register_command_handler(): registering 'ocd_svf'...
Debug: 52 1 command.c:364 register_command_handler(): registering 'ocd_xsvf'...
Debug: 53 1 command.c:151 script_debug(): command - ocd_command ocd_command 
type ocd_ft2232_layout sheevaplug
Debug: 54 1 command.c:151 script_debug(): command - ft2232_layout 
ocd_ft2232_layout sheevaplug
Debug: 56 1 command.c:151 script_debug(): command - ocd_command ocd_command 
type ocd_ft2232_vid_pid 0x9e88 0x9e8f
Debug: 57 1 command.c:151 script_debug(): command - ft2232_vid_pid 
ocd_ft2232_vid_pid 0x9e88 0x9e8f
Debug: 59 1 command.c:151 script_debug(): command - ocd_command ocd_command 
type ocd_ft2232_device_desc SheevaPlug JTAGKey FT2232D B
Debug: 60 1 command.c:151 script_debug(): command - ft2232_device_desc 
ocd_ft2232_device_desc SheevaPlug JTAGKey FT2232D B
Debug: 62 1 

Bug#838157: firmware-b43-installer: Please announce supported hardware using AppStream

[Petter Reinholdtsen]

Package: firmware-b43-installer
Version: 1:019-3
Severity: wishlist
User: p...@hungry.com
Usertags: appstream-modalias

Hi.

The firmware-b43-installer package is one of the packages in the Debian
archive that should be proposed for installation when a given hardware
dongle is inserted or available.  Thanks to the appstream system, this
can now be announced in a way other tools can use and act on.  I've
written the isenkram system to ask the current user if hardware specific
packages should be installed when a new dongle is installed or already
present on a machine, and isenkram now uses appstream as one source for
hardware to package mappings.

You can read more about this on my blog, 
http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
 >.

Instructions on how to create the metadata XML file can be found in
https://wiki.debian.org/AppStream/Guidelines >.

It would be great if you could add an appstream metainfo file to the
firmware-b43-installer package, with content similar to this:

  
  
   [...]
   
pci:v14E4d4312sv*
pci:v14E4d4320sv*

  

If there are other hardware ids also supposed by the package, please add
those too. :)

-- 
Happy hacking
Petter Reinholdtsen

Bug#838156: ITP: haskell-raaz -- crytographic networking library for Haskell

[Sean Whitton]

Package: wnpp
Severity: wishlist
Owner: Sean Whitton 

* Package name: haskell-raaz
  Version : 0.0.2
  Upstream Author : Piyush P Kurur 
* URL : https://github.com/raaz-crypto/raaz
* License : BSD-3-clause
  Programming Lang: Haskell
  Description : crytographic networking library for Haskell

I'm packaging this as a dependency of keysafe, another ITP of mine,

I intend to maintain it as part of the Haskell team.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#836759: proftpd-dfsg: please drop the build dependency on hardening-wrapper

[Hilmar Preusse]

On 05.09.16 Matthias Klose (d...@debian.org) wrote:

Hi Matthias,

> This package builds using the hardening-includes package, which
> is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.
> 
> Please consider dropping the build dependency of hardening-includes
> and use the DEB_BUILD_MAINT_OPTIONS settings.
> 
Currently hardening is implemented like this:

./configure $(shell dpkg-buildflags --export=configure) (...)

..according to [1]. The only place where we use hardening-includes is
that line:

find $(CURDIR)/debian/tmp -type f \( -executable -o -name \*.so\* \) -exec 
hardening-check {} + || true

Is it OK to simply remove that check? Is there an replacement for
hardening-check?

Thanks,
  Hilmar

[1] 
https://wiki.debian.org/HardeningWalkthrough#rules_files_based_on_standard_debhelper_or_hand-written_rules_files
-- 
sigfault


signature.asc
Description: Digital signature

Bug#838155: caja: Caja does not open in Debian Testing Stretch using Mate Desktop.

[Jonathan Bustillos]

Package: caja
Version: 1.14.2-1
Severity: important

Hello. I installed yesterday Debian Stretch with Mate Desktop and Caja File 
Manager can not be open. Regards.

Jathan

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

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

Versions of packages caja depends on:
ii  caja-common   1.14.2-1
ii  desktop-file-utils0.23-1
ii  gvfs  1.29.91-1
ii  libatk1.0-0   2.21.90-2
ii  libc6 2.23-5
ii  libcairo-gobject2 1.14.6-1+b1
ii  libcairo2 1.14.6-1+b1
ii  libcaja-extension11.14.2-1
ii  libexempi32.3.0-2
ii  libexif12 0.6.21-2
ii  libgail-3-0   3.21.5-3
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.49.6-1
ii  libglib2.0-data   2.49.6-1
ii  libgtk-3-03.21.5-3
ii  libice6   2:1.0.9-1+b1
ii  libmate-desktop-2-17  1.14.1-1
ii  libpango-1.0-01.40.2-1
ii  libpangocairo-1.0-0   1.40.2-1
ii  libselinux1   2.5-3
ii  libsm62:1.2.2-1+b1
ii  libstartup-notification0  0.12-4
ii  libunique-3.0-0   3.0.2-2
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.4+dfsg1-1+b1
ii  libxrender1   1:0.9.9-2
ii  mate-desktop  1.14.1-1
ii  shared-mime-info  1.7-1

Versions of packages caja recommends:
ii  gvfs-backends  1.29.91-1

Versions of packages caja suggests:
ii  engrampa1.14.1-1
pn  gstreamer1.0-tools  
pn  meld

-- no debconf information

Bug#835393: ITPs are wishlist, and please coordinate openvas packaging

[Adrian Bunk]

severity 838124 wishlist
thanks

Please work together when re-adding OpenVAS to Debian.

It will likely *not* make sense to have different people maintain 
different parts of OpenVAS - this should be one team working
together on all packages.

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#837989: openocd: can no longer use SheevaPlug JTAGKey FT2232D (regression)

[Paul Fertser]

On Fri, Sep 16, 2016 at 11:59:59PM +0200, David Madore wrote:
> Open On-Chip Debugger 0.5.0 (2016-09-16-09:33)
...
> Error: 217 472 core.c:945 jtag_examine_chain_check(): JTAG scan chain 
> interrogation failed: all zeroes
> Error: 218 472 core.c:946 jtag_examine_chain_check(): Check JTAG interface, 
> timings, target power, etc.
...
> Error: 230 476 feroceon.c:671 feroceon_examine(): unexpected Feroceon EICE 
> version signature

Hm, can't see anything good about it...

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

Bug#838154: alsa-firmware-loaders: Please announce supported hardware using AppStream

[Petter Reinholdtsen]

Package: alsa-firmware-loaders
Version: 1.1.0-1
Severity: wishlist
User: p...@hungry.com
Usertags: appstream-modalias

Hi.

The alsa-firmware-loaders package is one of the packages in the Debian
archive that should be proposed for installation when a given hardware
dongle is inserted or available.  Thanks to the appstream system, this
can now be announced in a way other tools can use and act on.  I've
written the isenkram system to ask the current user if hardware specific
packages should be installed when a new dongle is installed or already
present on a machine, and isenkram now uses appstream as one source for
hardware to package mappings.

You can read more about this on my blog, 
http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
 >.

Instructions on how to create the metadata XML file can be found in
https://wiki.debian.org/AppStream/Guidelines >.

It would be great if you could add an appstream metainfo file to the
alsa-firmware-loaders package, with content similar to this:

  
  
   [...]
   
usb:v1604p8000d*
usb:v1604p8001d*
usb:v1604p8004d*
usb:v1604p8005d*
usb:v1604p8006d*
usb:v1604p8007d*

  

If there are other USB ids also supposed by the package, please add
those too. :)

-- 
Happy hacking
Petter Reinholdtsen

Bug#838153: gnupg: `gpg --fingerprint --list-key` doesn't show the key fingerprint

[Guilhem Moulin]

Package: gnupg
Version: 2.1.15-3
Severity: important

Dear Maintainer,

I think it's actually an upstream bug since
‘d/patches/0020-gpg-print-fingerprint-regardless-of-keyid-format.patch’
seems to have been merged upstream, but in doubt I report this here.

~$ gpg --no-options --list-key 6294BE9B
pub   rsa4096 2011-01-05 [SC]
  DF9B9C49EAA9298432589D76DA87E80D6294BE9B
uid   [ unknown] Debian CD signing key 
sub   rsa4096 2011-01-05 [E]

~$ gpg --no-options --fingerprint --list-key 6294BE9B
pub   rsa4096 2011-01-05 [SC]
uid   [ unknown] Debian CD signing key 
sub   rsa4096 2011-01-05 [E]

The key fingerprint is missing in the latter command output.  I flag the
issue as important since there is no way to reliably identify a key from
a listing when ‘--fingerprint’ (or ‘--with-fingerprint’) is set.

Thanks for maintaining GnuPG in Debian!
-- 
Guilhem.

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/2 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 gnupg depends on:
ii  gnupg-agent2.1.15-3
ii  libassuan0 2.4.3-1
ii  libbz2-1.0 1.0.6-8
ii  libc6  2.24-2
ii  libgcrypt201.7.3-1
ii  libgpg-error0  1.24-1
ii  libksba8   1.3.5-2
ii  libreadline6   6.3-8+b4
ii  libsqlite3-0   3.14.2-1
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages gnupg recommends:
ii  dirmngr 2.1.15-3
pn  gnupg-l10n  

Versions of packages gnupg suggests:
pn  parcimonie  
pn  xloadimage  

-- no debconf information


signature.asc
Description: PGP signature

Bug#838014: RFS: imagemagick

[Bastien ROUCARIÈS]

Le samedi 17 septembre 2016, 17:28:03 CEST Mattia Rizzolo a écrit :
> On Sat, Sep 17, 2016 at 06:23:19PM +0200, Bastien ROUCARIÈS wrote:
> > > I recall you were saying something about this aiming to experimental,
> > > because some SONAME changed (I didn't really checkout), which must also
> > > be the reason you're asking for sponsorship (=> the package will go
> > > through NEW, so you can't upload yourself).  But your upload is
> > > targetting unstable.
> > 
> > Corrected
> 
> That means you're going to start a transition.  I won't help you with
> that unless you get an ACK from the release team, which afaik you
> haven't.

Yes what why I have set experimental as distrib. I am wiaiting for release 
team. When ligh will be green I will reupload to unstable (I could do this 
myself because I am a DM). WIll open a bug for release team

> 
> > > Things I want to see fixed:
> > > 
> > > 1/ you didn't incorporate any NMU
> > 
> > Change included and NMU aknowledge. This version go back before the NMU
> 
> you don't need anymore (since a decade…) to reclose the bugs if you're
> including the old changelog entries.

Removed
> 
> > > 2/ the Vcs-* field, Vcs-Git is plain broken.
> > 
> > Done
> 
> not in git.

Pushed
> 
> > > Other things that you may consider changes in future, not needed now:
> Great that you did most of them, but you didn't push (at least not to
> debian/6.9.5.9+dfsg-1)
> 
> > Now building will remove package from mentors and uploading a new one
> 
> no need if you push to git.
pushed


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

Bug#838151: jedit: running jedit logs me out.

[tim]

Package: jedit
Version: 5.3.0+dfsg-1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
Run jedit from command line or from launcher
   * 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: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=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 jedit depends on:
ii  default-jre [java7-runtime]2:1.8-57
ii  dpkg   1.18.10
ii  java-wrappers  0.1.28
ii  openjdk-8-jre [java7-runtime]  8u102-b14.1-2

jedit recommends no packages.

jedit suggests no packages.

-- no debconf information

Bug#838152: kipi-plugins: Missing dependencies on KDE packages

[Eike von Seggern]

Package: kipi-plugins
Version: 4:5.1.0-2
Severity: important

Dear Maintainer,

after installing digikam with kipi-plugins on a non-KDE system, I cannot
export files via 'Export->Export to remote storage'. On stderr, I get
messages similar to:
  "klauncher not running"
  "no service file for klauncher"
  "kinit not found in $PATH"

(I can try to reproduce the exact messages if necessary).

The problem looks similar to 801308 and
http://askubuntu.com/questions/617955/problem-with-kde-programs-after-upgrading-to-15-04
. Following the recommendations in the latter, I've installed
 * kinit
 * kio
 * kio-extras
 * kded5

This resolved my problems. So I suspect, that some dependencies are
missing, which are implicitly fulfilled on KDE-based systems.

Best regards

Eike


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

Kernel: Linux 4.6.0-1-amd64 (SMP w/2 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 kipi-plugins depends on:
ii  digikam-private-libs  4:5.1.0-2
ii  kipi-plugins-common   4:5.1.0-2
ii  libc6 2.23-5
ii  libkf5archive55.25.0-1
ii  libkf5completion5 5.25.0-1
ii  libkf5configcore5 5.25.0-1
ii  libkf5configgui5  5.25.0-1
ii  libkf5configwidgets5  5.25.0-1
ii  libkf5coreaddons5 5.25.0-1
ii  libkf5i18n5   5.25.0-1
ii  libkf5kiocore55.25.0-1
ii  libkf5kiowidgets5 5.25.0-1
ii  libkf5kipi-bin4:16.08.0-1
ii  libkf5kipi31.0.0  4:16.08.0-1
ii  libkf5service-bin 5.25.0-1
ii  libkf5service55.25.0-1
ii  libkf5windowsystem5   5.25.0-1
ii  libkf5xmlgui5 5.25.0-1
ii  libqt5core5a  5.6.1+dfsg-3+b1
ii  libqt5gui55.6.1+dfsg-3+b1
ii  libqt5network55.6.1+dfsg-3+b1
ii  libqt5printsupport5   5.6.1+dfsg-3+b1
ii  libqt5widgets55.6.1+dfsg-3+b1
ii  libqt5xml55.6.1+dfsg-3+b1
ii  libqt5xmlpatterns55.6.1-2
ii  libstdc++66.1.1-11

Versions of packages kipi-plugins recommends:
ii  enblend  4.2-2
ii  enfuse   4.2-2
ii  hugin2016.2.0~rc1+dfsg-2+b1
ii  imagemagick  8:6.8.9.9-7.2
ii  konqueror4:16.08.0-1
ii  minidlna 1.1.5+dfsg-4

Versions of packages kipi-plugins suggests:
ii  gimp  2.8.16-2.2
pn  kmail 
ii  vorbis-tools  1.4.0-10

-- no debconf information

Bug#835372: [Aptitude-devel] Bug#835372: Bug#835372: aptitude: behavior change with 0.7.6 with packages that can't be installed breaking automated installations

[Thomas Lange]

> On Sat, 17 Sep 2016 17:13:28 +0200, "Manuel A. Fernandez Montecelo" 
>  said:

> The common case when things don't fail should be fast and more "correct"
> when informing about problems.
Yes, but this would still be only a workaround and no clean fix. And
calling aptitude with each package on its own, would be very
slow. JFTR, aptitude -s may help writing a better workaround in FAI.
But I still hope that aptitude will have this option in the future.

-- 
regards Thomas

Bug#838150: ITP: itktools -- command line tools based on the ITK, intended for image processing

[Steve M. Robbins]

Package: wnpp
Severity: wishlist
Owner: "Steve M. Robbins" 

* Package name: itktools
  Version : 0.3.2
  Upstream Author : Marius Staring, Stefan Klein, David Doria
* URL : https://github.com/ITKTools/ITKTools
* License : Apache 2.0
  Programming Lang: C++
  Description : command line tools based on the ITK, intended for image 
processing

Practical command line tools based on the ITK, intended for image
processing. These tools are designed to take one or more input
image(s) from the command line, perform a single operation, and
produce an output image. For example smoothing of an image can be done
with the tool pxgaussianimagefilter.

Note: these tools (specifically pxcastconvert) are required to run the
Elastix test suite.

Bug#741196: libpetsc3.4.2: libpetsc.so.3.4.2 links with both GPL-licensed and GPL-incompatible libraries

[Lucas Nussbaum]

On 17/09/16 at 10:13 +0200, Francesco Poli wrote:
> On Fri, 8 Jul 2016 19:23:48 +0200 Francesco Poli wrote:
> 
> > On Thu, 7 Jul 2016 19:27:47 +0200 Lucas Nussbaum wrote:
> [...]
> > > It seems that the main SCOTCH copyright holders is Francois Pellegrini,
> > 
> > It is my understanding that he is the main author, but the copyright
> > holder is INRIA (along with ENSEIRB and CNRS).
> > Please see
> > https://tracker.debian.org/media/packages/s/scotch/copyright-5.1.12b.dfsg-2
> > 
> > However, I agree with you that François is really the person to be
> > persuaded.
> > 
> > Once he is convinced that SCOTCH should be re-licensed, I think he
> > will know who has to be contacted, in order to obtain the necessary
> > paperwork. Or, at least, I hope so.
> > 
> > > who is very active in the French Free Software community. One of the
> > > colleagues (same Inria research team) of Francois is Brice Goglin, who
> > > is a DD. So it might be useful to try to contact them.
> > 
> > This is the kind of help I have been asking for since I filed these
> > bug reports.
> > If you can get in touch with François Pellegrini, directly or
> > indirectly, and explain the issue to him in a convincing manner,
> > then I would be really really grateful.
> > 
> > As I said, I tried multiple times, but François no longer replies
> > to my e-mail messages. That's why I need help from people more likely
> > to be listened to.
> [...]
> 
> Hello again Lucas,
> is there any progress on this issue?

Not that I'm aware of, sorry.

Lucas

Bug#628848: RM libpam-unix2

[Adrian Bunk]

reassign 628848 ftp.debian.org
retitle 628848 RM: libpam-unix2 -- RoQA; orphaned, dead upstream, not in 
stable, broken
thanks

The feature pam_unix2 has on top of pam_unix is Blowfish support,
but the package is compiled without Blowfish support since 2013
(see #729813 for details).

The package is not in stable, orphaned, dead upstream, and as better 
solution it is now possible to use SHA-256/512 with crypt(3).

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#836215: RFS: phalanx/25-1 [ITA]

[Jose G. López]

On Wed, 14 Sep 2016 09:55:36 + (UTC)
Gianfranco Costamagna  wrote:

> you might even consider fixing the actual RC bug without a new upstream 
> release,
> let the package migrate, and upload the new version (crippled) in experimental
> or later in unstable.

Hi Gianfranco,

All right, I prefer to fix and improve the actual version and not trim
useful features that I as a user, would like to have.
I've uploaded the new debian revision to mentors[0]. To keep the
previous work I have created a new branch (debian/sid) where I
cherry-picked changes.

Thanks for your help and suggestions!

[0]https://mentors.debian.net/package/phalanx
[1]https://gitlab.com/deb-pkg/phalanx/tree/debian/sid


pgpxZUMdO1hYd.pgp
Description: PGP signature

Bug#837971: [Aptitude-devel] Bug#837971: aptitude: [PATCH] Distinguish Debian-specific and upstream upgrades

[Manuel A. Fernandez Montecelo]

2016-09-17 18:21 GMT+02:00 Keshav Kini :
>>
>> But anyway, things like these are possible for years with themes, which
>> are broken also for many years (if they ever worked), and nobody
>> complained about the broken support for years so I tend to think that
>> people don't care too much about these visual tweaks.
>>
>> http://aptitude.alioth.debian.org/doc/en/ch02s05s03.html
>
> I'm not sure if this is what you meant, but I don't think the particular
> UI change implemented by this patch is possible to implement using
> themes, since I had to add a new style

Yes, I think that without your new style wouldn't have been possible to do it.

I meant that I don't know if many people will be bothered to change
the defaults, since I never see this kind of options tweaked in
configs sent to bug reports, or complaints about much more big broken
things like the themes (so I was tempted to scrap theme support
altogether).

> (which means I should have edited
> whatever generates this documentation too... oops).

Yeah, probably :)


-- 
Manuel A. Fernandez Montecelo 

Bug#838149: RFS: minetest-mod-mesecons/2016.09.13-1

[Julien Puydt]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "minetest-mod-mesecons"

 * Package name: minetest-mod-mesecons
   Version : 2016.09.13-1
   Upstream Author : Mesecons Mod Developer Team and contributors
 * URL : http://mesecons.net
 * License : LGPL-3
   Section : games

  It builds those binary packages:

minetest-mod-mesecons - Digital circuitry blocks for minetest

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


  https://mentors.debian.net/package/minetest-mod-mesecons


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

dget -x 
https://mentors.debian.net/debian/pool/main/m/minetest-mod-mesecons/minetest-mod-mesecons_2016.09.13-1.dsc


  It is packaged within the Debian Games Team:
Vcs-Git: https://anonscm.debian.org/git/pkg-games/minetest-mod-mesecons.git
Vcs-Browser: 
https://anonscm.debian.org/cgit/pkg-games/minetest-mod-mesecons.git



  Changes since the last upload: new upstream release.

Thanks,

Snark on #debian-games

Bug#635748: [pgadmin3] Does not respect system background colors in "Object browser"

[Rimas Kudelis]

Hi,

2016-09-17 20:52, Guillaume Lelarge rašė:
> You're right on the issue. Unfortunately, there won't be any more
> pgadmin3 releases. The dev team is working on pgadmin4 right now,
> which is a complete rewrite of pgAdmin. A GA release should be
> available at the end of September if all goes according to plan.
>
> But still, thank you for your patch and your attention to this kind of
> details. They are important to us. I'd have been happy to apply it if
> there would be another release of pgadmin3.
>

Yeah, I saw that pgadmin4 is on the way. However, perhaps it would make
sense to apply this at least as a Debian patch, since I doubt that
pgadmin4 will become available in official Debian or Ubuntu repositories
anytime soon. Or will it?

Rimas

Bug#635748: [pgadmin3] Does not respect system background colors in "Object browser"

[Rimas Kudelis]

Hi Guillaume,

I just want to say that your patch doesn't quite work as expected. 
Instead of just using system default colour unless custom colour is set, 
Pgadmin actually stores that default colour in server configuration, and 
always sets it explicitly. This isn't a problem until you change the 
theme you use, but once you do (like I switched from light to dark 
theme), all your servers are suddently using a colour that is no longer 
the default.


I think the correct behavior would be not to store colour in the 
configuration unless the user sets it explicitly. This way, even if 
PgAdmin stores the default upon initial creation, the user could clear 
that setting manually and it would then always be treated as empty 
instead of being reset to the default colour on first run. Ideally, it 
would even be possible to disable custom colour via a checkbox or 
something like that.


I made a small patch, which prevents storing the empty setting. However, 
it is incomplete due to the server dialog now erring upon load, because 
it actually expects a colour value. I believe this should be easy to fix 
for someone familiar with the code though.


I'm attaching this half-baked patch. Feel free to apply it if PgAdmin is 
still to be supported for some time.


Cheers,
Rimas Kudelis

--- pgadmin3-1.22.0.orig/pgadmin/include/schema/pgServer.h
+++ pgadmin3-1.22.0/pgadmin/include/schema/pgServer.h
@@ -47,7 +47,7 @@ public:
 	pgServer(const wxString  = wxT(""), const wxString  = wxT(""), const wxString  = wxT(""),
 	 const wxString  = wxT(""), const wxString  = wxT(""), const wxString  = wxT(""), int newPort = 5432,
 	 bool storePwd = false, const wxString  = wxT(""), bool restore = true, int sslMode = 0,
-	 const wxString  = wxSystemSettings::GetColour(wxSYS_COLOUR_WINDOW).GetAsString(wxC2S_HTML_SYNTAX), const wxString  = wxEmptyString,
+	 const wxString  = wxEmptyString, const wxString  = wxEmptyString,
 	 bool sshTunnel = false, const wxString  = wxEmptyString, const wxString  = wxEmptyString, bool authModePwd = true,
 	 const wxString  = wxEmptyString, const wxString  = wxEmptyString, const wxString  = wxEmptyString,
 	 const int  = DEFAULT_SSH_PORT);
--- pgadmin3-1.22.0.orig/pgadmin/schema/pgServer.cpp
+++ pgadmin3-1.22.0/pgadmin/schema/pgServer.cpp
@@ -1556,12 +1556,5 @@ pgObject *pgServerFactory::CreateObjects
 colour = wxEmptyString;
 		}

-		if (colour.IsEmpty())
-		{
-			wxColour cColour;
-			cColour.Set(wxSystemSettings::GetColour(wxSYS_COLOUR_WINDOW).GetAsString(wxC2S_HTML_SYNTAX));
-			colour = cColour.GetAsString(wxC2S_HTML_SYNTAX);
-		}
-
 		// SSL mode
 #ifdef PG_SSL

Bug#838148: autogen: FTBFS on hurd-i386

[Samuel Thibault]

Package: autogen
Version: 1:5.18.12-1
Severity: important
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd

Hello,

autogen currently FTBFS on hurd-i386, because error.test fails:

>error-> failure expected->actual
*** error.base1 Sat Sep 17 17:36:27 2016
--- error.err   Sat Sep 17 17:36:27 2016
***
*** 1,2 
--- 1,3 
  #error directive -- in error.def on line 3
The definitions file has a '#error' directive
+ Aborted

What happens is that error.test triggers an abortion several times,
producing a core file each time. It happens that on hurd-i386, a core
file is not overwritten when it already exists, i.e. when running the
abortion test several times, the first time one gets:

Aborted (core dumped)

and the subsequent times, one gets:

Aborted

because the core file was not overwritten. One could strip the
/^Aborte.*core dumped/q sed rule to also catch "Aborted" alone, but
perhaps it's better to remove the core file as the attached tested patch
does, so as to trigger the

Aborted (core dumped)

message each time.

Samuel

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

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

Versions of packages autogen depends on:
ii  guile-2.0-libs  2.0.11+1-12
ii  libc6   2.23-5
ii  libopts25   1:5.18.10-4
ii  libopts25-dev   1:5.18.10-4
ii  libxml2 2.9.4+dfsg1-1+b1

Versions of packages autogen recommends:
ii  autogen-doc  1:5.18.10-4

autogen suggests no packages.

-- no debconf information

-- 
Samuel
"...very few phenomena can pull someone out of Deep Hack Mode, with two
noted exceptions: being struck by lightning, or worse, your *computer*
being struck by lightning."
(By Matt Welsh)
--- error.test.original 2016-09-17 18:13:22.0 +
+++ error.test  2016-09-17 18:13:25.0 +
@@ -48,6 +48,7 @@
/^Aborte.*core dumped/q
p'
 
+  rm -f core
   ${SED} -n "${sedcmd}" $1
 }
 

Bug#834960: libdaemon-generic-perl: FTBFS too much often (failing tests)

[Niko Tyni]

On Sat, Sep 17, 2016 at 07:20:09PM +0200, gregor herrmann wrote:

> CPAN RT has one issue; don't know if it's related:
> https://rt.cpan.org/Public/Bug/Display.html?id=110239

I think it's a different issue.

> From starting at t/daemon.t my guess is that we're seeing a race
> condition or some other timing issue here -- the daemon writes to a
> log file and the test reads the logfile, and in one case the log
> message doesn't seem to be there (yet?). At least that's my current
> guess.

Indeed, the daemon first opens the file for writing and only then writes
it (see the logger script at top of daemon.t), while the test waits for
existence (-e) and then proceeds to check the file contents.

I think the attached patch should fix it. I was able to reproduce
the issue sporadically without the patch, and couldn't get it to
happen after applying this.

> I'm tempted to mark this log-reading test as TODO since this seems a
> bit fragile.

No objections, but let's try the patch first?
-- 
Niko
>From 96209b5ba3df009a495da31bee8e2540c3365ec5 Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Sat, 17 Sep 2016 21:16:16 +0300
Subject: [PATCH] Fix a race condition in the test suite waiting for daemon log
 output

There's a window where the daemon has created a log file but not yet
written anything into it. Wait for the file to become nonempty before
reading it to make sure we're past that window.

Bug-Debian: https://bugs.debian.org/834960
---
 t/daemon.t | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/t/daemon.t b/t/daemon.t
index 30763df..548af21 100644
--- a/t/daemon.t
+++ b/t/daemon.t
@@ -200,7 +200,7 @@ sub do_test
 	chomp($counter1);
 	like($counter1, qr/^\d+$/, "counter1 - $name");
 
-	expect { -e "$tmp/log" };
+	expect { -s "$tmp/log" };
 	like(read_file("$tmp/log"), qr/START LOG/, "logged output");
 
 	expect { my @l = read_file("$tmp/log"); @l > 1 };
-- 
2.9.3

Bug#838147: qemu: CVE-2016-7421: scsi: pvscsi: infinite loop when processing IO requests

[Salvatore Bonaccorso]

Source: qemu
Version: 1:2.1+dfsg-11
Severity: normal
Tags: security upstream

Hi,

the following vulnerability was published for qemu.

CVE-2016-7421[0]:
scsi: pvscsi: infinite loop when processing IO requests

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-7421

Regards,
Salvatore

Bug#838146: qemu: CVE-2016-7422: virtio: null pointer dereference in virtqueue_map_desc

[Salvatore Bonaccorso]

Source: qemu
Version: 1:2.6+dfsg-3
Severity: important
Tags: security upstream

Hi,

the following vulnerability was published for qemu.

CVE-2016-7422[0]:
virtio: null pointer dereference in virtqueue_map_desc

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-7422

Regards,
Salvatore

Bug#635748: [pgadmin3] Does not respect system background colors in "Object browser"

[Guillaume Lelarge]

Le 17 sept. 2016 7:44 PM, "Rimas Kudelis"  a écrit :
>
> Hi Guillaume,
>
> I just want to say that your patch doesn't quite work as expected.
Instead of just using system default colour unless custom colour is set,
Pgadmin actually stores that default colour in server configuration, and
always sets it explicitly. This isn't a problem until you change the theme
you use, but once you do (like I switched from light to dark theme), all
your servers are suddently using a colour that is no longer the default.
>
> I think the correct behavior would be not to store colour in the
configuration unless the user sets it explicitly. This way, even if PgAdmin
stores the default upon initial creation, the user could clear that setting
manually and it would then always be treated as empty instead of being
reset to the default colour on first run. Ideally, it would even be
possible to disable custom colour via a checkbox or something like that.
>
> I made a small patch, which prevents storing the empty setting. However,
it is incomplete due to the server dialog now erring upon load, because it
actually expects a colour value. I believe this should be easy to fix for
someone familiar with the code though.
>
> I'm attaching this half-baked patch. Feel free to apply it if PgAdmin is
still to be supported for some time.
>

You're right on the issue. Unfortunately, there won't be any more pgadmin3
releases. The dev team is working on pgadmin4 right now, which is a
complete rewrite of pgAdmin. A GA release should be available at the end of
September if all goes according to plan.

But still, thank you for your patch and your attention to this kind of
details. They are important to us. I'd have been happy to apply it if there
would be another release of pgadmin3.

Regards.

Bug#838144: owfs-common: missing Breaks: libow-2.8-15

[Andreas Beckmann]

Package: owfs-common
Version: 3.1p1-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + owhttpd owftpd owfs-fuse owserver libow-dev libow-perl 
libow-php5 libow-tcl owfs-dbg python-ow

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy' to 'jessie' to 'stretch'.
After this upgrade a conffile has disappeared from a package, but that
(obsolete) package is still installed:

2m42.6s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /etc/modprobe.d/libow-2.8-15.conf (from 
libow-2.8-15:amd64 package)

Since owfs-common "takes over" that conffile (to make it disappear),
it needs to break the packages that had shipped it in the past.

That problem already exists in stable (after the wheezy->jessie upgrade)
but we had ignored that error there so far.


Andreas


owhttpd_3.1p1-6.log.gz
Description: application/gzip

Bug#838145: qemu: CVE-2016-7423: scsi: mptsas: OOB access when freeing MPTSASRequest object

[Salvatore Bonaccorso]

Source: qemu
Version: 1:2.6+dfsg-3
Severity: important
Tags: security upstream

Hi,

the following vulnerability was published for qemu.

CVE-2016-7423[0]:
scsi: mptsas: OOB access when freeing MPTSASRequest object

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-7423
[1] 
http://git.qemu.org/?p=qemu.git;a=commit;h=670e56d3ed2918b3861d9216f2c0540d9e9ae0d5

Regards,
Salvatore

Bug#837971: [Aptitude-devel] Bug#837971: aptitude: [PATCH] Distinguish Debian-specific and upstream upgrades

[Axel Beckert]

Hi,

Keshav Kini wrote:
> One way to brighten the background color without using the bold
> attribute would be to wait for libncurses in Debian to switch over to
> the ncurses 6.0 ABI, which provides 256-color support.  Then one could
> freely choose a slightly lighter blue color as the background color
> without using attributes like bold.

Interesting. I assume that cwidget needs to gain support for that
first (unless it's that transparent for such things, which I don't
expect).

> I don't know how far in the future that might be, though.  Bug #796835
> seems to indicate that we'll move over to the new ABI after Debian 9 is
> released, but if that's the case I don't really understand why the bug
> was closed.  Maybe I haven't found the right bug number.

You've found the right bug. And as I understand it, it's closed
because it's considered done. Not sure where you've read that the
transition should be _after_ Debian 9 is released. I read it as if the
plan was to transition _before_ the freeze for Debian 9 is started.
And hence it looks perfectly fine to me that the bug is marked as
done.

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#838141: libgnupg-interface-perl: autopkgtest failures in test suite

[gregor herrmann]

On Sat, 17 Sep 2016 20:11:10 +0300, Niko Tyni wrote:

>   t/clearsign.t .. 
>   1..2
>   not ok 1
>   not ok 2
>   Failed 2/2 subtests 
>   [...]
>   Test Summary Report
>   ---
>   t/clearsign.t(Wstat: 0 Tests: 2 Failed: 2)
> Failed tests:  1-2
>   t/decrypt.t  (Wstat: 0 Tests: 4 Failed: 4)
> Failed tests:  1-4
>   t/detach_sign.t  (Wstat: 0 Tests: 2 Failed: 2)
> Failed tests:  1-2
>   t/passphrase_handling.t  (Wstat: 0 Tests: 3 Failed: 3)
> Failed tests:  1-3
>   t/sign.t (Wstat: 0 Tests: 2 Failed: 2)
> Failed tests:  1-2
>   t/sign_and_encrypt.t (Wstat: 0 Tests: 2 Failed: 2)
> Failed tests:  1-2
>   Files=22, Tests=54,  8 wallclock secs ( 0.07 usr  0.01 sys +  4.93 cusr  
> 0.45 csys =  5.46 CPU)
>   Result: FAIL

With:

#v+
% cat debian/tests/pkg-perl/smoke-setup
#!/bin/sh

# this chmod can be dropped once CPAN #102651 is resolved upstream
chmod a+x $TDIR/test/fake-pinentry.pl
#v-

all tests pass except one:

t/encrypt_symmetrically.t .. 
1..2
not ok 1
not ok 2
Failed 2/2 subtests 
[..]
Test Summary Report
---
t/encrypt_symmetrically.t (Wstat: 0 Tests: 2 Failed: 2)
  Failed tests:  1-2
Files=22, Tests=54,  8 wallclock secs ( 0.08 usr  0.02 sys +  4.30 cusr  0.40 
csys =  4.80 CPU)
Result: FAIL

  
Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#838140: RFS: zfs-linux/0.6.5.8-0.1 [NMU] -- git format-patch -- version 3

[lumin]

patch version 3 is just incremental to version 2.

new changes are:

* previously "zfs*.service" files are installed to
  package zfsutils-linux, however zed.service is
  renamed to zfs-zed.service by upstream, so changed
  zfsutils-linux.install to avoid installing the service
  twice.From 5b05d4a5fff78162e9ec4d67dca56b603cb56f77 Mon Sep 17 00:00:00 2001
From: Zhou Mo 
Date: Sat, 17 Sep 2016 17:32:40 +
Subject: [PATCH] Avoid installing zfs-zed.service twice.

---
 zfsutils-linux.install | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/zfsutils-linux.install b/zfsutils-linux.install
index 99cc48c..2b52b35 100644
--- a/zfsutils-linux.install
+++ b/zfsutils-linux.install
@@ -1,5 +1,8 @@
 ../tree/zfsutils/* /
-usr/lib/systemd/system/zfs* lib/systemd/system/
+usr/lib/systemd/system/zfs-mount.service lib/systemd/system/
+usr/lib/systemd/system/zfs-share.service lib/systemd/system/
+usr/lib/systemd/system/zfs-import-scan.service lib/systemd/system/
+usr/lib/systemd/system/zfs-import-cache.service lib/systemd/system/
 usr/lib/systemd/system-preset/ lib/systemd/
 usr/lib/modules-load.d/ lib/
 lib/udev/
-- 
2.9.3

Bug#814426: sympa: New upstream version available (6.2.12)

[Stefan Hornburg (Racke)]

On 09/17/2016 10:50 AM, Stefan Hornburg (Racke) wrote:
> On 09/17/2016 10:10 AM, Emmanuel Bouthenot wrote:
>> Racke,
>>
>> On Fri, Sep 16, 2016 at 09:23:10PM +0200, Stefan Hornburg (Racke) wrote:
>> [...]
>>
 it doesn't look like your branch is available in the Git repository:

 https://anonscm.debian.org/cgit/collab-maint/sympa.git
>>
>> I will push the changes before the end of the week (tomorrow), I'm currently
>> testing installation from scratch and the upgrade path of the new sympa 6.2
>> package.
>>
>> I've still some minor issues to fix, and I will commit the changes
>> accordingly.
> 
> Great :-).
> 
>>
>> While testing upgrade/installation, I noticed that
>> libcrypt-ciphersaber-perl is still a recommends and that it is no more
>> available in sid.
>> As you are the maintainer, could you take a look and upload the latest
>> release in unstable?
>>
>> Regards,
>>
> 
> Yes, I'll take a look into it this weekend.
> 
> Regards
>   Racke
> 

It uploaded the latest release, this is now in the NEW queue.

Regards
Racke


-- 
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration.

Bug#838014: RFS: imagemagick

[Mattia Rizzolo]

On Sat, Sep 17, 2016 at 06:23:19PM +0200, Bastien ROUCARIÈS wrote:
> > I recall you were saying something about this aiming to experimental,
> > because some SONAME changed (I didn't really checkout), which must also
> > be the reason you're asking for sponsorship (=> the package will go
> > through NEW, so you can't upload yourself).  But your upload is
> > targetting unstable.
> 
> Corrected

That means you're going to start a transition.  I won't help you with
that unless you get an ACK from the release team, which afaik you
haven't.

> > Things I want to see fixed:
> > 
> > 1/ you didn't incorporate any NMU
> 
> Change included and NMU aknowledge. This version go back before the NMU

you don't need anymore (since a decade…) to reclose the bugs if you're
including the old changelog entries.

> > 2/ the Vcs-* field, Vcs-Git is plain broken.
> 
> Done

not in git.

> > Other things that you may consider changes in future, not needed now:

Great that you did most of them, but you didn't push (at least not to
debian/6.9.5.9+dfsg-1)

> Now building will remove package from mentors and uploading a new one

no need if you push to git.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#838143: emacs24: missing Breaks: oneliner-el (<= 0.3.6-7.1)

[Andreas Beckmann]

Package: emacs24
Version: 24.5+1-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + oneliner-el

Hi,

during a test with piuparts I noticed that emacs24 is not compatible
with oneliner-el (that may have been left over from a long grown
wheezy installation. Please add an appropriate Breaks against it to
ensure it gets removed (or upgraded in case the package would get
updated at some pooint again) on upgrades to emacs24 in stretch.

>From the attached log (scroll to the bottom...):

  Setting up emacs24 (24.5+1-7) ...
  Install emacsen-common for emacs24
  emacsen-common: Handling install of emacsen flavor emacs24
  Wrote /etc/emacs24/site-start.d/00debian-vars.elc
  Wrote /usr/share/emacs24/site-lisp/debian-startup.elc
  Install oneliner-el for emacs24
  install/oneliner-el: Handling install for emacsen flavor emacs24
  Loading 00debian-vars...
  Loading /etc/emacs/site-start.d/20apel.el (source)...
  Loading /etc/emacs/site-start.d/50oneliner-el.el (source)...
  Loading /etc/emacs/site-start.d/51oneliner-el.el (source)...
  Error while loading 51oneliner-el: Cannot open load file: No such file or 
directory, poe
  
  In toplevel form:
  oneliner.el:225:1:Error: Cannot open load file: No such file or directory, poe
  ERROR: install script from oneliner-el package failed
  dpkg: error processing package emacs24 (--configure):
   subprocess installed post-installation script returned error exit status 1
  Setting up apel (10.8+0.20120427-15) ...
  Install emacsen-common for emacs23
  emacsen-common: Handling install of emacsen flavor emacs23
  Wrote /etc/emacs23/site-start.d/00debian-vars.elc
  Wrote /usr/share/emacs23/site-lisp/debian-startup.elc
  Install emacsen-common for emacs24
  emacsen-common: Handling install of emacsen flavor emacs24
  Wrote /etc/emacs24/site-start.d/00debian-vars.elc
  Wrote /usr/share/emacs24/site-lisp/debian-startup.elc
  Install apel for emacs23
  install/apel: byte-compiling for emacs23, logged in /tmp/elc.FITqQNEcTtCb
  install/apel: deleting /tmp/elc.FITqQNEcTtCb
  install/apel: byte-compiling for reverse dependency
  Install apel for emacs24
  install/apel: byte-compiling for emacs24, logged in /tmp/elc.v8FtAKxmFrHB
  install/apel: deleting /tmp/elc.v8FtAKxmFrHB
  install/apel: byte-compiling for reverse dependency


Andreas


oneliner-el_None.log.gz
Description: application/gzip

Bug#834960: libdaemon-generic-perl: FTBFS too much often (failing tests)

[gregor herrmann]

On Sun, 21 Aug 2016 02:21:52 +0200, gregor herrmann wrote:

> > I tried to build this package in stretch with "dpkg-buildpackage -A"
> > (which is what the "Arch: all" autobuilder would do to build it)
> > but it failed:
> Builds fine for me (amd64 sind cowbuilder).

Some additional information:
cpantesters have very few failures, but they are all the same as what
we see in Santiago#s logs:
http://www.cpantesters.org/cpan/report/8fb11c8e-0653-11e6-a2e4-45f0fcd2507e
http://www.cpantesters.org/cpan/report/9c628bfa-2171-11e6-8c16-9a987137e9a4
http://www.cpantesters.org/cpan/report/66c774ca-7a7b-11e6-979d-6531eb7e2f12
http://www.cpantesters.org/cpan/report/a8b80e96-3132-11e5-8118-e820f1b6abcd

CPAN RT has one issue; don't know if it's related:
https://rt.cpan.org/Public/Bug/Display.html?id=110239


Personally I still can't reproduce the bug.

From starting at t/daemon.t my guess is that we're seeing a race
condition or some other timing issue here -- the daemon writes to a
log file and the test reads the logfile, and in one case the log
message doesn't seem to be there (yet?). At least that's my current
guess.

I'm tempted to mark this log-reading test as TODO since this seems a
bit fragile.


Thoughts?


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#838130: openalpr: Please update to new upstream version (currently 2.3.0)

[Petter Reinholdtsen]

[Petter Reinholdtsen]
> Very good.  I'll upload it as soon as I find time to look closer at
> the package.

Uploaded.  The issues I noticed can be fixed in the next upload. :)

I had to add a "(Closes: #812176)" that somehow was missing in this new
version.  Please check what happend to that part in the 2.2.3-1
changelog.

-- 
Happy hacking
Petter Reinholdtsen

Bug#838140: RFS: zfs-linux/0.6.5.8-0.1 [NMU] -- git format-patch -- version 2

[lumin]

As required by aron.

patch version 2

changes from patch version 1:

* don't attempt to rename zfs-zed.service to zed.service,
  we just follow this upstream change.
  affected patch 0004From c552e462652bebf413812e761c71af8e09aeaf67 Mon Sep 17 00:00:00 2001
From: Zhou Mo 
Date: Sat, 17 Sep 2016 16:54:20 +
Subject: [PATCH 1/4] dch: import upstream release 0.6.5.8

---
 changelog | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/changelog b/changelog
index 57a60c1..ed38d2d 100644
--- a/changelog
+++ b/changelog
@@ -1,3 +1,10 @@
+zfs-linux (0.6.5.8-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * New upstream release.
+
+ -- Zhou Mo   Sat, 17 Sep 2016 16:11:07 +
+
 zfs-linux (0.6.5.7-2) unstable; urgency=medium
 
   [ Aron Xu ]
-- 
2.9.3

From 5697aaa98dd0cda3b878d637c12427cdbf3f89ad Mon Sep 17 00:00:00 2001
From: Zhou Mo 
Date: Sat, 17 Sep 2016 16:56:07 +
Subject: [PATCH 2/4] patches: removed merged patches

---
 changelog  |  4 ++
 .../1003-Add-tunable-to-ignore-hole_birth.patch| 63 --
 patches/1004-ignore-hole_birth-by-default.patch| 20 ---
 patches/series |  2 -
 4 files changed, 4 insertions(+), 85 deletions(-)
 delete mode 100644 patches/1003-Add-tunable-to-ignore-hole_birth.patch
 delete mode 100644 patches/1004-ignore-hole_birth-by-default.patch

diff --git a/changelog b/changelog
index ed38d2d..cd82551 100644
--- a/changelog
+++ b/changelog
@@ -2,6 +2,10 @@ zfs-linux (0.6.5.8-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
   * New upstream release.
+  * Remove merged patches:
+- 1003-Add-tunable-to-ignore-hole_birth.patch
+- 1004-ignore-hole_birth-by-default.patch
+
 
  -- Zhou Mo   Sat, 17 Sep 2016 16:11:07 +
 
diff --git a/patches/1003-Add-tunable-to-ignore-hole_birth.patch b/patches/1003-Add-tunable-to-ignore-hole_birth.patch
deleted file mode 100644
index 3fed916..000
--- a/patches/1003-Add-tunable-to-ignore-hole_birth.patch
+++ /dev/null
@@ -1,63 +0,0 @@
-Description: Add tunable to ignore hole_birth.
-  Adds a module option which disables the hole_birth optimization
-  which has been responsible for several recent bugs, including
-  issue https://github.com/zfsonlinux/zfs/issues/4050.
-Forwarded: https://github.com/zfsonlinux/zfs/pull/4833
-Author: Rich Ercolani 
-Reviewed-By: Brian Behlendorf 
-Applied-Upstream: 6d836e6f8b358270d55a57ad8e8868c957f15bf3 (master commit)
-Last-Update: 2016-08-16

- man/man5/zfs-module-parameters.5 | 13 +
- module/zfs/dmu_traverse.c|  6 +-
- 2 files changed, 18 insertions(+), 1 deletion(-)
-
 a/man/man5/zfs-module-parameters.5
-+++ b/man/man5/zfs-module-parameters.5
-@@ -27,6 +27,19 @@
- .sp
- .ne 2
- .na
-+\fBignore_hole_birth\fR (int)
-+.ad
-+.RS 12n
-+When set, the hole_birth optimization will not be used, and all holes will
-+always be sent on zfs send. Useful if you suspect your datasets are affected
-+by a bug in hole_birth.
-+.sp
-+Use \fB1\fR for on and \fB0\fR (default) for off.
-+.RE
-+
-+.sp
-+.ne 2
-+.na
- \fBl2arc_feed_again\fR (int)
- .ad
- .RS 12n
 a/module/zfs/dmu_traverse.c
-+++ b/module/zfs/dmu_traverse.c
-@@ -39,6 +39,7 @@
- #include 
- 
- int32_t zfs_pd_bytes_max = 50 * 1024 * 1024;	/* 50MB */
-+int32_t ignore_hole_birth = 0;
- 
- typedef struct prefetch_data {
- 	kmutex_t pd_mtx;
-@@ -250,7 +251,7 @@
- 		 *
- 		 * Note that the meta-dnode cannot be reallocated.
- 		 */
--		if ((!td->td_realloc_possible ||
-+		if (!ignore_hole_birth && (!td->td_realloc_possible ||
- 			zb->zb_object == DMU_META_DNODE_OBJECT) &&
- 			td->td_hole_birth_enabled_txg <= td->td_min_txg)
- 			return (0);
-@@ -692,4 +693,7 @@
- 
- module_param(zfs_pd_bytes_max, int, 0644);
- MODULE_PARM_DESC(zfs_pd_bytes_max, "Max number of bytes to prefetch");
-+
-+module_param(ignore_hole_birth, int, 0644);
-+MODULE_PARM_DESC(ignore_hole_birth, "Ignore hole_birth txg for send");
- #endif
diff --git a/patches/1004-ignore-hole_birth-by-default.patch b/patches/1004-ignore-hole_birth-by-default.patch
deleted file mode 100644
index 5eed797..000
--- a/patches/1004-ignore-hole_birth-by-default.patch
+++ /dev/null
@@ -1,20 +0,0 @@
-Description: Enable by default the tunable to ignore hole_birth.
-  Once hole_birth becomes more reliable, this patch should be
-  removed, making the tunable default back to false.
-Bug: https://github.com/zfsonlinux/zfs/issues/4050
-Bug-Debian: https://bugs.debian.org/830824
-Forwarded: https://github.com/zfsonlinux/zfs/pull/4833
-Author: Carlos Alberto Lopez Perez 
-Last-Update: 2016-08-16
-
 a/module/zfs/dmu_traverse.c
-+++ b/module/zfs/dmu_traverse.c
-@@ -39,7 +39,7 @@
- #include 
- 
- int32_t zfs_pd_bytes_max = 50 * 1024 * 1024;	/* 50MB */
--int32_t ignore_hole_birth = 0;
-+int32_t 

Bug#838142: mate-panel: stickynotes-app crashes with segfault

[Julian]

Package: mate-panel
Version: 1.14.2-1
Severity: normal

Hi,

the stickynotes applet crashes instantly with a segfault when it is started.
The important three lines are:

gdk_window_get_display: assertion 'GDK_IS_WINDOW (window)' failed
gdk_x11_display_get_xdisplay: assertion 'GDK_IS_DISPLAY (display)' failed
stickynotes-app[28868]: segfault at 968 ip 7f3a753db323 sp 7ffd71921580
error 4 in libX11.so.6.3.0[7f3a753b2000+13c000]


Besides that it also triggers a lot of  "gtk_widget_size_allocate(): attempt to
underallocate" error messages (wnck-applet and clock-applet). There is an
existing bug report about that already and I don't think they're responsible
for the segfault and just a result of the panel being repainted.



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

Kernel: Linux 4.6.0-1-amd64 (SMP w/2 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 mate-panel depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-1
ii  libatk1.0-0  2.21.90-2
ii  libc62.23-5
ii  libcairo-gobject21.14.6-1+b1
ii  libcairo21.14.6-1+b1
ii  libcanberra-gtk3-0   0.30-3
ii  libcanberra0 0.30-3
ii  libdbus-1-3  1.10.10-1
ii  libdbus-glib-1-2 0.108-1
ii  libdconf10.26.0-1
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.49.6-1
ii  libgtk-3-0   3.21.5-3
ii  libice6  2:1.0.9-1+b1
ii  libmate-desktop-2-17 1.14.1-1
ii  libmate-menu21.14.0-1
ii  libmate-panel-applet-4-1 1.14.2-1
ii  libmateweather1  1.14.1-1
ii  libpango-1.0-0   1.40.2-1
ii  libpangocairo-1.0-0  1.40.2-1
ii  librsvg2-2   2.40.16-1
ii  libsm6   2:1.2.2-1+b1
ii  libstartup-notification0 0.12-4
ii  libwnck-3-0  3.20.1-1
ii  libx11-6 2:1.6.3-1
ii  libxau6  1:1.0.8-1
ii  libxrandr2   2:1.5.0-1
ii  mate-desktop 1.14.1-1
ii  mate-menus   1.14.0-1
ii  mate-panel-common1.14.2-1
ii  mate-polkit  1.14.0-1
ii  menu-xdg 0.5

mate-panel recommends no packages.

mate-panel suggests no packages.

-- no debconf information

Bug#836823: jessie-pu: package glusterfs/3.5.2-2+deb8u2

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2016-09-10 at 11:20 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Tue, 2016-09-06 at 11:20 +0200, Patrick Matthäi wrote:
> > +glusterfs (3.5.2-2+deb8u3) jessie-proposed-updates; urgency=medium
> > +
> > +  * quota: Fix could not start auxiliary mount issue by adding upstream 
> > patch
> > +03-quota-fix-could-not-start-auxiliary-mount-issue.
> > +Closes: #825834
> 
> Please go ahead, bearing in mind that the window for inclusion in 8.6
> closes this weekend.

Uploaded (on Monday, so sadly too late for 8.6) and flagged for
acceptance.

Regards,

Adam

Bug#838141: libgnupg-interface-perl: autopkgtest failures in test suite

[Niko Tyni]

Package: libgnupg-interface-perl
Version: 0.52-4
User: debian-p...@lists.debian.org
Usertags: autopkgtest

This package failed its autopkgtest checks on ci.debian.net, although
the previous version succeeded.

 https://ci.debian.net/packages/libg/libgnupg-interface-perl/unstable/amd64/

  t/clearsign.t .. 
  1..2
  not ok 1
  not ok 2
  Failed 2/2 subtests 
  [...]
  Test Summary Report
  ---
  t/clearsign.t(Wstat: 0 Tests: 2 Failed: 2)
Failed tests:  1-2
  t/decrypt.t  (Wstat: 0 Tests: 4 Failed: 4)
Failed tests:  1-4
  t/detach_sign.t  (Wstat: 0 Tests: 2 Failed: 2)
Failed tests:  1-2
  t/passphrase_handling.t  (Wstat: 0 Tests: 3 Failed: 3)
Failed tests:  1-3
  t/sign.t (Wstat: 0 Tests: 2 Failed: 2)
Failed tests:  1-2
  t/sign_and_encrypt.t (Wstat: 0 Tests: 2 Failed: 2)
Failed tests:  1-2
  Files=22, Tests=54,  8 wallclock secs ( 0.07 usr  0.01 sys +  4.93 cusr  0.45 
csys =  5.46 CPU)
  Result: FAIL
 
-- 
Niko Tyni   nt...@debian.org

Bug#836994: mate-panel: get wnck-applet underallocation notification all the time in journalctl

[Julian]

Package: mate-panel
Version: 1.14.2-1
Followup-For: Bug #836994

Hi,

this is not just about the wnck-applet, others (like the clock-applet) produce
the same error messages.
I guess they're triggered when the applet is being repainted, for example
because a cursor is moved within their region. Also changes on the panel itself
(like starting a new applet) triggers those error messages.


There was a launchpad bug report a few years ago, maybe this might help:
https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/798455



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

Kernel: Linux 4.6.0-1-amd64 (SMP w/2 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 mate-panel depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-1
ii  libatk1.0-0  2.21.90-2
ii  libc62.23-5
ii  libcairo-gobject21.14.6-1+b1
ii  libcairo21.14.6-1+b1
ii  libcanberra-gtk3-0   0.30-3
ii  libcanberra0 0.30-3
ii  libdbus-1-3  1.10.10-1
ii  libdbus-glib-1-2 0.108-1
ii  libdconf10.26.0-1
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.49.6-1
ii  libgtk-3-0   3.21.5-3
ii  libice6  2:1.0.9-1+b1
ii  libmate-desktop-2-17 1.14.1-1
ii  libmate-menu21.14.0-1
ii  libmate-panel-applet-4-1 1.14.2-1
ii  libmateweather1  1.14.1-1
ii  libpango-1.0-0   1.40.2-1
ii  libpangocairo-1.0-0  1.40.2-1
ii  librsvg2-2   2.40.16-1
ii  libsm6   2:1.2.2-1+b1
ii  libstartup-notification0 0.12-4
ii  libwnck-3-0  3.20.1-1
ii  libx11-6 2:1.6.3-1
ii  libxau6  1:1.0.8-1
ii  libxrandr2   2:1.5.0-1
ii  mate-desktop 1.14.1-1
ii  mate-menus   1.14.0-1
ii  mate-panel-common1.14.2-1
ii  mate-polkit  1.14.0-1
ii  menu-xdg 0.5

mate-panel recommends no packages.

mate-panel suggests no packages.

-- no debconf information

Bug#838131: [gnome-photos] Does not work on Intel Core 2 Duo CPU T6600 (64 bit)

[Jason Crain]

On 2016-09-17, Nils Asmussen  wrote:
> after upgrading to the Version 3.21.92-1, I always get an error stating
> "illegal instruction":
> 
> bash$ gnome-photos
> Illegal instruction
> 
> The relevant assembly instruction is "rdtscp".
> I checked this by substituting it by "nop"s:
> With a hexeditor I replaced "0F 01 F9" by "90 90 90". As a result I got
> the gnome-photos main screen flashing on my screen for a short time. (I
> didn't see anything of gnome-photos before.)
> 
> I conclude that changing the compiler flags to support older cpus would
> fix the problem.

>From gnome-photos' configure.ac:
> AC_MSG_CHECKING([for fast counters with rdtscp])
> AC_RUN_IFELSE([AC_LANG_SOURCE([[
> #include 
> int main (int argc, char *argv[]) { int cpu; __builtin_ia32_rdtscp (); 
> return 0; }]])],
>   [have_rdtscp=yes],
>   [have_rdtscp=no])
>   AC_MSG_RESULT([$have_rdtscp])
>   AS_IF([test "$have_rdtscp" = "yes"],
>   [CFLAGS="$CFLAGS -DEGG_HAVE_RDTSCP"])

It looks like they've recently added something called EggCounter which
which compile-time conditionally uses rdtscp.

Bug#838140: RFS: zfs-linux/0.6.5.8-0.1 [NMU] -- git format-patch

[lumin]

As required by aron.
From c552e462652bebf413812e761c71af8e09aeaf67 Mon Sep 17 00:00:00 2001
From: Zhou Mo 
Date: Sat, 17 Sep 2016 16:54:20 +
Subject: [PATCH 1/4] dch: import upstream release 0.6.5.8

---
 changelog | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/changelog b/changelog
index 57a60c1..ed38d2d 100644
--- a/changelog
+++ b/changelog
@@ -1,3 +1,10 @@
+zfs-linux (0.6.5.8-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * New upstream release.
+
+ -- Zhou Mo   Sat, 17 Sep 2016 16:11:07 +
+
 zfs-linux (0.6.5.7-2) unstable; urgency=medium
 
   [ Aron Xu ]
-- 
2.9.3

From 5697aaa98dd0cda3b878d637c12427cdbf3f89ad Mon Sep 17 00:00:00 2001
From: Zhou Mo 
Date: Sat, 17 Sep 2016 16:56:07 +
Subject: [PATCH 2/4] patches: removed merged patches

---
 changelog  |  4 ++
 .../1003-Add-tunable-to-ignore-hole_birth.patch| 63 --
 patches/1004-ignore-hole_birth-by-default.patch| 20 ---
 patches/series |  2 -
 4 files changed, 4 insertions(+), 85 deletions(-)
 delete mode 100644 patches/1003-Add-tunable-to-ignore-hole_birth.patch
 delete mode 100644 patches/1004-ignore-hole_birth-by-default.patch

diff --git a/changelog b/changelog
index ed38d2d..cd82551 100644
--- a/changelog
+++ b/changelog
@@ -2,6 +2,10 @@ zfs-linux (0.6.5.8-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
   * New upstream release.
+  * Remove merged patches:
+- 1003-Add-tunable-to-ignore-hole_birth.patch
+- 1004-ignore-hole_birth-by-default.patch
+
 
  -- Zhou Mo   Sat, 17 Sep 2016 16:11:07 +
 
diff --git a/patches/1003-Add-tunable-to-ignore-hole_birth.patch b/patches/1003-Add-tunable-to-ignore-hole_birth.patch
deleted file mode 100644
index 3fed916..000
--- a/patches/1003-Add-tunable-to-ignore-hole_birth.patch
+++ /dev/null
@@ -1,63 +0,0 @@
-Description: Add tunable to ignore hole_birth.
-  Adds a module option which disables the hole_birth optimization
-  which has been responsible for several recent bugs, including
-  issue https://github.com/zfsonlinux/zfs/issues/4050.
-Forwarded: https://github.com/zfsonlinux/zfs/pull/4833
-Author: Rich Ercolani 
-Reviewed-By: Brian Behlendorf 
-Applied-Upstream: 6d836e6f8b358270d55a57ad8e8868c957f15bf3 (master commit)
-Last-Update: 2016-08-16

- man/man5/zfs-module-parameters.5 | 13 +
- module/zfs/dmu_traverse.c|  6 +-
- 2 files changed, 18 insertions(+), 1 deletion(-)
-
 a/man/man5/zfs-module-parameters.5
-+++ b/man/man5/zfs-module-parameters.5
-@@ -27,6 +27,19 @@
- .sp
- .ne 2
- .na
-+\fBignore_hole_birth\fR (int)
-+.ad
-+.RS 12n
-+When set, the hole_birth optimization will not be used, and all holes will
-+always be sent on zfs send. Useful if you suspect your datasets are affected
-+by a bug in hole_birth.
-+.sp
-+Use \fB1\fR for on and \fB0\fR (default) for off.
-+.RE
-+
-+.sp
-+.ne 2
-+.na
- \fBl2arc_feed_again\fR (int)
- .ad
- .RS 12n
 a/module/zfs/dmu_traverse.c
-+++ b/module/zfs/dmu_traverse.c
-@@ -39,6 +39,7 @@
- #include 
- 
- int32_t zfs_pd_bytes_max = 50 * 1024 * 1024;	/* 50MB */
-+int32_t ignore_hole_birth = 0;
- 
- typedef struct prefetch_data {
- 	kmutex_t pd_mtx;
-@@ -250,7 +251,7 @@
- 		 *
- 		 * Note that the meta-dnode cannot be reallocated.
- 		 */
--		if ((!td->td_realloc_possible ||
-+		if (!ignore_hole_birth && (!td->td_realloc_possible ||
- 			zb->zb_object == DMU_META_DNODE_OBJECT) &&
- 			td->td_hole_birth_enabled_txg <= td->td_min_txg)
- 			return (0);
-@@ -692,4 +693,7 @@
- 
- module_param(zfs_pd_bytes_max, int, 0644);
- MODULE_PARM_DESC(zfs_pd_bytes_max, "Max number of bytes to prefetch");
-+
-+module_param(ignore_hole_birth, int, 0644);
-+MODULE_PARM_DESC(ignore_hole_birth, "Ignore hole_birth txg for send");
- #endif
diff --git a/patches/1004-ignore-hole_birth-by-default.patch b/patches/1004-ignore-hole_birth-by-default.patch
deleted file mode 100644
index 5eed797..000
--- a/patches/1004-ignore-hole_birth-by-default.patch
+++ /dev/null
@@ -1,20 +0,0 @@
-Description: Enable by default the tunable to ignore hole_birth.
-  Once hole_birth becomes more reliable, this patch should be
-  removed, making the tunable default back to false.
-Bug: https://github.com/zfsonlinux/zfs/issues/4050
-Bug-Debian: https://bugs.debian.org/830824
-Forwarded: https://github.com/zfsonlinux/zfs/pull/4833
-Author: Carlos Alberto Lopez Perez 
-Last-Update: 2016-08-16
-
 a/module/zfs/dmu_traverse.c
-+++ b/module/zfs/dmu_traverse.c
-@@ -39,7 +39,7 @@
- #include 
- 
- int32_t zfs_pd_bytes_max = 50 * 1024 * 1024;	/* 50MB */
--int32_t ignore_hole_birth = 0;
-+int32_t ignore_hole_birth = 1;
- 
- typedef struct prefetch_data {
- 	kmutex_t pd_mtx;
diff --git a/patches/series b/patches/series
index d9fac31..26e7ae3 100644
--- a/patches/series
+++ 

Bug#833965: tcsh: uses deprecated BSD union wait type

[Sascha Steinbiss]

Hi,

just a friendly ping whether this is still on anyone’s radar. I assume that 
#837026 [1]
is a direct consequence of this issue?

Cheers
Sascha

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837026

On Thu, 1 Sep 2016 13:02:17 +0200 Thomas Lange  
wrote:
> > On Thu, 1 Sep 2016 12:51:30 +0200, Aurelien Jarno  
> > said:
> 
> > bug to serious. If you don't have time to fix this bug, I can do a
> > non-maintainer upload with the patch which is in the bug log.
> Salut Aurelien,
> 
> feel free to do a NMU.
> 
> -- 
> regards Thomas
> 
> 

Bug#837134: libgnome2-gconf-perl: autopkgtest failure: Failed to start message bus: Abstract socket name too long in @INC

[Niko Tyni]

On Fri, Sep 09, 2016 at 09:52:23AM +0300, Niko Tyni wrote:
> Package: libgnome2-gconf-perl
> Version: 1.044-6
> User: debian-p...@lists.debian.org
> Usertags: autopkgtest
> X-Debbugs-Cc: terce...@debian.org
> 
> This package is failing its autopkgtest runs on ci.debian.net.
> It broke between 2016-09-05 and 2016-09-08, probably related
> to ci.debian.net updates
>  http://softwarelivre.org/terceiro/blog/debian-ci-updates-for-september-2016
> 
>   adt-run [01:42:50]: test command1: /usr/share/pkg-perl-autopkgtest/runner 
> build-deps
>   adt-run [01:42:50]: test command1: [---
>   Failed to start message bus: Abstract socket name too long

>  dbus-daemon --session --fork 
> --address="unix:abstract=$TDIR/dbus-libgnome2-gconf-perl" --print-pid=4 
> 4>pid.tmp

Some observations:

- unix domain sockets have a maximum length of about 108 bytes

- ci.debian.org apparently runs the tests under something like
  
/tmp/tmp.t1UgJ2zs67/autopkgtest-incoming/unstable/amd64/libg/libgnome2-gconf-perl/20160917_041530
  which is 98 bytes

- abstract sockets don't have files associated to them, so the name
  doesn't really need to be "under" $TDIR

- the name probably doesn't need to be unpredictable (the current
  one isn't really), although it might be nice as abstract sockets
  don't apparently have any permission controls (see unix(7))

- it would probably be nice for the name to be unique to the
  autopkgtest session so that concurrent sessions wouldn't clash

- the current way of passing the socket name in smoke-env doesn't
  give much chance of executing commands to derive it (backticks might
  work, but that would be sort of abusing the interface IMO)

I haven't been able to figure out a good solution yet. The best I came
up with is to use something like 'autopkgtest-dbus-libgnome2-gconf-perl' 
and give up on the uniqueness constraint.

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

Bug#837082: mirror submission for mirrors.wikimedia.org

[Faidon Liambotis]

Donald,

Thanks. Considering the size and connectivity of our mirror, would it be
useful to add our mirror to the ftp.us rotation? What would you need for
us?

Thanks,
Faidon

On Mon, Sep 12, 2016 at 10:43:43AM -0400, Donald Norwood wrote:
> Hi Faidon,
> 
> Thank you for your support and for mirroring Debian.
> 
> Your mirror has been added to the official Debian mirrors list.
> 
> To set up push mirroring, consult the master list for a mirror that you
> feel would be best suited for you considering distance, speed, etc...
> then reach out to that mirror admin and they will help you set it up.
> 
> Best regards,
> 
> Donald Norwood
> -Debian Mirrors Team
> 
> On Thu, 08 Sep 2016 16:03:42 + "Faidon Liambotis"
>  wrote:
> > Package: mirrors
> > Severity: wishlist
> > User: mirr...@packages.debian.org
> > Usertags: mirror-submission
> >
> > Submission-Type: new
> > Site: mirrors.wikimedia.org
> > Type: leaf
> > Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386
> kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
> > Archive-http: /debian/
> > IPv6: yes
> > Archive-upstream: ftp2.us.debian.org
> > Updates: four
> > Maintainer: Faidon Liambotis 
> > Country: US United States
> > Location: Ashburn, VA, USA
> > Sponsor: Wikimedia Foundation https://wikimediafoundation.org/
> > Comment: Newly procured dedicated mirror box. Currently mirroring
> Debian, Ubuntu and Tails; ~8-9TB of disk space still free. Lots of RAM,
> HW RAID, 10Gbps NIC, connected on the multi-10G Wikimedia backbone with
> no restrictions. Operated by the Wikimedia operations team, with 4 DDs
> among it (Faidon Liambotis, Filippo Giunchendi, Moritz Mühlenhoff,
> Emanuele Rocca). Public stats.
> >
> > Currently not a push mirror -- I'd like your help on that. Also no FTP
> (is it still needed? weasel said no) and no rsync right now. We're also
> not mirroring debian-cd/debian-archive at the moment, unsure how to do
> that yet.
> >
> > Happy to do all of the above and/or more if needed, as long as it
> makes sense for Debian. Ping me on IRC (paravoid) for anything.
> >
> >
> 
> -- 
> --Donald Norwood
> www.debian.org
> 
> 
>