Bug#813370: vlc: no video in h264 files - server-xorg-video-intel 2:2.99.917

[Manuel Gräber]

Package: src:vlc
Version: 2.2.2-1
Followup-For: Bug #813370

Dear Maintainer,

I got the same bug. It seems to be related to server-xorg-video-intel. Vlc 
worked fine until I upgraded the server-xorg-video-intel package to 2:2.99.917.

OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 5500 (Broadwell GT2) 
OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.1.1


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

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

Versions of packages vlc depends on:
ii  dpkg1.18.4
ii  fonts-freefont-ttf  20120503-4
ii  libaa1  1.4p5-44
ii  libavcodec-ffmpeg56 7:2.8.5-1+b1
ii  libavutil-ffmpeg54  7:2.8.5-1+b1
ii  libc6   2.21-7
ii  libcaca00.99.beta19-2+b1
ii  libcairo2   1.14.6-1
ii  libegl1-mesa [libegl1-x11]  11.1.1-2
ii  libfreerdp-client1.11.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreerdp-core1.1  1.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreerdp-gdi1.1   1.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreetype62.6.1-0.1
ii  libfribidi0 0.19.7-1
ii  libgcc1 1:5.3.1-7
ii  libgl1-mesa-glx [libgl1]11.1.1-2
ii  libgles1-mesa [libgles1]11.1.1-2
ii  libgles2-mesa [libgles2]11.1.1-2
ii  libglib2.0-02.46.2-3
ii  libpulse0   7.1-2
ii  libqt5core5a5.5.1+dfsg-13
ii  libqt5gui5  5.5.1+dfsg-13
ii  libqt5widgets5  5.5.1+dfsg-13
ii  libqt5x11extras55.5.1-3
ii  librsvg2-2  2.40.13-2
ii  libsdl-image1.2 1.2.12-5+b5
ii  libsdl1.2debian 1.2.15-12
ii  libstdc++6  5.3.1-7
ii  libva-drm1  1.6.2-1
ii  libva-x11-1 1.6.2-1
ii  libva1  1.6.2-1
ii  libvlccore8 2.2.2-1
ii  libvncclient1   0.9.10+dfsg-3+b1
ii  libx11-62:1.6.3-1
ii  libxcb-composite0   1.11.1-1
ii  libxcb-keysyms1 0.4.0-1
ii  libxcb-randr0   1.11.1-1
ii  libxcb-shm0 1.11.1-1
ii  libxcb-xv0  1.11.1-1
ii  libxcb1 1.11.1-1
ii  libxext62:1.3.3-1
ii  libxi6  2:1.7.6-1
ii  libxinerama12:1.1.3-1+b1
ii  libxpm4 1:3.5.11-1+b1
ii  vlc-nox 2.2.2-1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages vlc recommends:
ii  vlc-plugin-notify  2.2.2-1
ii  vlc-plugin-samba   2.2.2-1
ii  xdg-utils  1.1.1-1

vlc suggests no packages.

Versions of packages vlc-nox depends on:
ii  dpkg   1.18.4
ii  liba52-0.7.4   0.7.4-18
ii  libasound2 1.1.0-1
ii  libass50.13.1-1
ii  libavahi-client3   0.6.32~rc+dfsg-1
ii  libavahi-common3   0.6.32~rc+dfsg-1
ii  libavc1394-0   0.5.4-2
ii  libavcodec-ffmpeg567:2.8.5-1+b1
ii  libavformat-ffmpeg56   7:2.8.5-1+b1
ii  libavutil-ffmpeg54 7:2.8.5-1+b1
ii  libbasicusageenvironment1  2016.01.29-2
ii  libbluray1 1:0.9.2-2
ii  libc6  2.21-7
ii  libcddb2   1.3.2-5
ii  libcdio13  0.83-4.2+b1
ii  libchromaprint01.2-2
ii  libcrystalhd3  1:0.0~git20110715.fdd2f19-11+b1
ii  libdbus-1-31.10.6-1
ii  libdc1394-22   2.2.3-1
ii  libdca00.0.5-7
ii  libdirectfb-1.2-9  1.2.10.0-5.1
ii  libdvbpsi101.3.0-4
ii  libdvdnav4 5.0.3-1
ii  libdvdread45.0.3-1
ii  libebml4v5 1.3.3-1
ii  libfaad2   2.8.0~cvs20150510-1
ii  libflac8   1.3.1-4
ii  libfontconfig1 2.11.0-6.3
ii  libfreetype6   2.6.1-0.1
ii  libfribidi00.19.7-1
ii  libgcc11:5.3.1-7
ii  libgcrypt201.6.4-5
ii  libgnutls303.4.8-3
ii  libgpg-error0  1.21-1
ii  libgroupsock8  2016.01.29-2
ii  libjpeg62-turbo1:1.4.2-2
ii  libkate1   0.4.1-5
ii  liblircclient0 0.9.0~pre1-1.2
ii  liblivemedia50 2016.01.29-2
ii  liblua5.2-05.2.4-1
ii  libmad00.15.1b-8
ii  libmatroska6v5 1.4.4-1
ii  libmodplug11:0.8.8.5-2
ii  libmpcdec6 2:0.1~r475-1
ii  libmpeg2-4 0.5.1-7
ii  libmtp91.1.10-2
ii  libncursesw5   6.0+20151024-2

Bug#813534: siproxd: WARNING:couldn't create new PID file: No such file or directory

[Richard van den Berg]

On 02-02-16 23:21, Geert Stappers wrote:
> 'patch' as "unified patch, output of `diff -u`"? (I didn't see it attached) 

Patch as in "trivial to fix, here is how". Sorry for my poor .deb skills.

>> Creating /var/lib/siproxd/var/run/siproxd owned by siproxd:siproxd fixed the 
>> warning.
> And that is a directory what is created?

Yes.

> Please send the outpot of
>   grep run /etc/default/siproxd /etc/siproxd.conf

# grep run /etc/default/siproxd /etc/siproxd.conf
/etc/siproxd.conf:#If siproxd is not running on the host doing the 
masquerading
/etc/siproxd.conf:#   Note: If running in chroot jail, this path starts relative
/etc/siproxd.conf:#   Note: If running in chroot jail, this path starts relative
/etc/siproxd.conf:#pid_file = /var/run/siproxd/siproxd.pid

Bug#734357: [pkg-golang-devel] Bug#734357:

[Tianon Gravi]

On 2 February 2016 at 23:45, Michael Hudson-Doyle
 wrote:
> TBH, I'm a bit vague about what problems exactly this bug actually
> caused (even though I spent half a week fixing it!). So I guess that's
> a shrug from me -- if it's not causing active problems and 1.6 is, as
> you say, around the corner, I'd just as soon leave it out.

Cool, fair enough!  Let's plan to circle back for Go 1.6 then. :)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#807312: src:debian-installer: please provide binary package for use by debian-installer-netboot-images

[Aurelien Jarno]

On 2016-02-02 17:51, Wookey wrote:
> 
> > what do you mean by that? Source packages like cross-gcc-4.9-armhf
> > *do* have cross-arch build-deps. Were you talking about missing
> > support in britney to properly transition source packages with
> > cross-arch build-deps? Is there a bug about this open somewhere?
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770925
> 
> Stalled since debconf. Although that's actually the wanna-build code,
> rather than britney. We've been waiting for w-b to be implemented
> before we could sensibly worry about britney.
> 
> But time is getting short if we are to have this working this release.
> 
> Aurelien - can we help move this along?

Sorry about that. I'll try to work again on it. 3 out of 5 patches have
already been merged, the two others has issues and need to be reworked.
It might help if you or someone else can provide updated patches
addressing the issues.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Bug#813426: warning: /etc/alternatives/compare is dangling; it will be updated with best choice

[Vincent Fourmond]

control: severity -1 serious

  Hello,

On Wed, Feb 3, 2016 at 12:52 AM, 積丹尼 Dan Jacobson  wrote:
>
> What  a   mess.

  I can only agree...

> Preparing to unpack .../libmagickwand-6.q16-2_8%3a6.9.2.10+dfsg-2_i386.deb ...
> Unpacking libmagickwand-6.q16-2:i386 (8:6.9.2.10+dfsg-2) over 
> (8:6.9.2.10+dfsg-1) ...
> Preparing to unpack .../imagemagick-6-doc_8%3a6.9.2.10+dfsg-2_all.deb ...
> Unpacking imagemagick-6-doc (8:6.9.2.10+dfsg-2) over (8:6.9.2.10+dfsg-1) ...
> Preparing to unpack .../imagemagick-doc_8%3a6.9.2.10+dfsg-2_all.deb ...
> Unpacking imagemagick-doc (8:6.9.2.10+dfsg-2) over (8:6.9.2.10+dfsg-1) ...
> Preparing to unpack .../libmagickcore-6.q16-2_8%3a6.9.2.10+dfsg-2_i386.deb ...
> Unpacking libmagickcore-6.q16-2:i386 (8:6.9.2.10+dfsg-2) over 
> (8:6.9.2.10+dfsg-1) ...
> Preparing to unpack .../imagemagick-6-common_8%3a6.9.2.10+dfsg-2_all.deb ...
> Unpacking imagemagick-6-common (8:6.9.2.10+dfsg-2) over (8:6.9.2.10+dfsg-1) 
> ...
> dpkg: warning: unable to delete old directory '/etc/etc/ImageMagick-6': 
> Directory not empty
> dpkg: warning: unable to delete old directory '/etc/etc': Directory not empty
> Preparing to unpack .../libfftw3-single3_3.3.4-2+b1_i386.deb ...
> Unpacking libfftw3-single3:i386 (3.3.4-2+b1) over (3.3.4-2) ...
> Preparing to unpack .../libdebconfclient0_0.204_i386.deb ...
> Unpacking libdebconfclient0:i386 (0.204) over (0.203) ...
> Processing triggers for man-db (2.7.5-1) ...
> Processing triggers for systemd (228-4+b1) ...
> Processing triggers for libc-bin (2.22-0experimental1) ...
> Processing triggers for doc-base (0.10.7) ...
> Processing 1 changed doc-base file...
> Registering documents with scrollkeeper...
> Setting up libdebconfclient0:i386 (0.204) ...
> Processing triggers for libc-bin (2.22-0experimental1) ...
> Preparing to unpack .../isc-dhcp-client_4.3.3-7_i386.deb ...
> Unpacking isc-dhcp-client (4.3.3-7) over (4.3.3-6) ...
> Preparing to unpack .../isc-dhcp-common_4.3.3-7_i386.deb ...
> Unpacking isc-dhcp-common (4.3.3-7) over (4.3.3-6) ...
> Preparing to unpack .../libboost-iostreams1.58.0_1.58.0+dfsg-4.1+b1_i386.deb 
> ...
> Unpacking libboost-iostreams1.58.0:i386 (1.58.0+dfsg-4.1+b1) over 
> (1.58.0+dfsg-4.1) ...
> Preparing to unpack .../libgnutls30_3.4.8-3_i386.deb ...
> Unpacking libgnutls30:i386 (3.4.8-3) over (3.4.8-2) ...
> Preparing to unpack .../libasound2-data_1.1.0-1_all.deb ...
> Unpacking libasound2-data (1.1.0-1) over (1.0.29-1) ...
> Preparing to unpack .../libasound2_1.1.0-1_i386.deb ...
> Unpacking libasound2:i386 (1.1.0-1) over (1.0.29-1) ...
> Preparing to unpack .../alsa-utils_1.1.0-1_i386.deb ...
> Unpacking alsa-utils (1.1.0-1) over (1.0.29-1+b1) ...
> Preparing to unpack .../archives/bdf2psf_1.136_all.deb ...
> Unpacking bdf2psf (1.136) over (1.135) ...
> Preparing to unpack .../debian-policy_3.9.7.0_all.deb ...
> Unpacking debian-policy (3.9.7.0) over (3.9.6.1) ...
> Preparing to unpack .../dosfstools_3.99.0~git20160127-2_i386.deb ...
> Unpacking dosfstools (3.99.0~git20160127-2) over (3.0.28-2) ...
> Preparing to unpack .../imagemagick_8%3a6.9.2.10+dfsg-2_all.deb ...
> dpkg-query: no packages found matching imagemagick:all
> dpkg-query: package 'imagemagick' is not installed
> Use dpkg --info (= dpkg-deb --info) to examine archive files,
> and dpkg --contents (= dpkg-deb --contents) to list their contents.
> dpkg-query: package 'imagemagick' is not installed
> Use dpkg --info (= dpkg-deb --info) to examine archive files,
> and dpkg --contents (= dpkg-deb --contents) to list their contents.
> dpkg-query: package 'imagemagick' is not installed
> Use dpkg --info (= dpkg-deb --info) to examine archive files,
> [...]
> Use dpkg --info (= dpkg-deb --info) to examine archive files,
> and dpkg --contents (= dpkg-deb --contents) to list their contents.

  This looks like a dpkg bug -- dpkg doesn't like so much switching
from arch:any to arch:all, as far as I can tell.

  BTW, you show a very long list of warning messages, did they stop by
themselves ? If yes, I'm very curious why.

> dpkg-maintscript-helper: error: directory '/usr/share/doc/imagemagick' 
> contains files not owned by package imagemagick:all, cannot switch to symlink
> dpkg: error processing archive 
> /var/cache/apt/archives/imagemagick_8%3a6.9.2.10+dfsg-2_all.deb (--unpack):
>  subprocess new pre-installation script returned error exit status 1
> Preparing to unpack .../imagemagick-6.q16_8%3a6.9.2.10+dfsg-2_i386.deb ...
> Unpacking imagemagick-6.q16 (8:6.9.2.10+dfsg-2) over (8:6.9.2.10+dfsg-1) ...
> Preparing to unpack .../iso-codes_3.65-1_all.deb ...

  Thanks !

  Vincent

Bug#734357: [pkg-golang-devel] Bug#734357:

[Michael Hudson-Doyle]

Well,

On 3 February 2016 at 20:41, Tianon Gravi  wrote:
> On 15 December 2015 at 13:32, Michael Hudson-Doyle
>  wrote:
>> FWIW, this bug is fixed properly upstream in git tip and will be part of 1.6.
>
> Nice! :D
>
> The upstream fix applies cleanly against Go 1.5 -- do you think it's
> important enough to include now, or just wait for Go 1.6 to be GA
> (which will be soon anyways)?

TBH, I'm a bit vague about what problems exactly this bug actually
caused (even though I spent half a week fixing it!). So I guess that's
a shrug from me -- if it's not causing active problems and 1.6 is, as
you say, around the corner, I'd just as soon leave it out.

Cheers,
mwh

Bug#813566: imagemagick-6.q16: missing package dependency to librsvg2-bin

[Takahide Nojima]

Package: imagemagick-6.q16
Version: 8:6.8.9.9-7+b1
Severity: important
Tags: newcomer

Hello Maintainer,

I did convert command to svg file , and I got following message,

- here --
convert /usr/share/images/desktop-base/login-background.svg -resize 640x480
tmp.png
convert: delegate failed `"rsvg-convert" -o "%o" "%i"' @
error/delegate.c/InvokeDelegate/1310.
convert: unable to open image `/tmp/magick-13224LvxsIieEAUyO': No such file or
directory @ error/blob.c/OpenBlob/2709.
convert: unable to open file `/tmp/magick-13224LvxsIieEAUyO': No such file or
directory @ error/constitute.c/ReadImage/540.
convert: no images defined `tmp.png' @
error/convert.c/ConvertImageCommand/3210.
-- here ---

As that message,svg-convert command didn't install.
svg-convert command belongs to librsvg2-bin package.

I guess imagemagick-6.q16 doesn't have dependency to librsvg2-bin.

I would appreciate if you could fix dependecncy.

Thank you in advance,

Takahide Nojima



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

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

Versions of packages imagemagick-6.q16 depends on:
ii  hicolor-icon-theme 0.13-1
ii  libc6  2.21-7
ii  libmagickcore-6.q16-2  8:6.8.9.9-7+b1
ii  libmagickwand-6.q16-2  8:6.8.9.9-7+b1

Versions of packages imagemagick-6.q16 recommends:
ii  ghostscript  9.16~dfsg-2.1
pn  libmagickcore-6.q16-2-extra  
ii  netpbm   2:10.0-15.3

Versions of packages imagemagick-6.q16 suggests:
pn  autotrace
ii  curl 7.47.0-1
pn  enscript 
ii  ffmpeg   7:2.8.5-1+b1
pn  gimp 
ii  gnuplot  4.6.6-3
pn  grads
ii  graphviz 2.38.0-12+b1
ii  groff-base   1.22.3-7
pn  hp2xx
pn  html2ps  
pn  imagemagick-doc  
ii  libwmf-bin   0.2.8.4-10.5
ii  lpr  1:2008.05.17.1
ii  mplayer2 [mplayer]   2.0-728-g2c378c7-4+b2
pn  povray   
pn  radiance 
ii  sane-utils   1.0.25-2
ii  texlive-binaries [texlive-base-bin]  2015.20150524.37493-7+b1
ii  transfig 1:3.2.5.e-5
ii  ufraw-batch  0.20-3+b1
ii  xdg-utils1.1.1-1

-- no debconf information

Bug#813563: [Pkg-alsa-devel] Bug#813563: alsa-utils: Overwrite files from unrelated package

[Elimar Riesebieter]

Control: severity -1 serious
Control: merge -1 813479

* Michael Rasmussen  [2016-02-03 08:03 +0100]:

> Package: alsa-utils
> Version: 1.0.29-1+b1
> Severity: critical
> Justification: breaks unrelated software
> 
> This bug: #813528 actually should have been made here. Please link.
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (900, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.3.0-1-amd64 (SMP w/6 CPU cores)
> Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages alsa-utils depends on:
> ii  dialog  1.2-20150920-1
> ii  kmod22-1
> ii  libasound2  1.1.0-1
> ii  libc6   2.21-7
> ii  libncursesw56.0+20151024-2
> ii  libsamplerate0  0.1.8-8
> ii  libtinfo5   6.0+20151024-2
> ii  lsb-base9.20160110
> ii  whiptail0.52.18-2
> 
> alsa-utils recommends no packages.
> 
> alsa-utils suggests no packages.
> 
> -- no debconf information
> 
> 
> 
> This mail was virus scanned and spam checked before delivery.
> This mail is also DKIM signed. See header dkim-signature.
> 
> ___
> Pkg-alsa-devel mailing list
> pkg-alsa-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-alsa-devel
> 

-- 
 Obviously the human brain works like a computer.
  Since there are no stupid computers humans can't be stupid.
  There are just a few running with Windows or even CE ;-)

Bug#734357: [pkg-golang-devel] Bug#734357:

[Tianon Gravi]

On 15 December 2015 at 13:32, Michael Hudson-Doyle
 wrote:
> FWIW, this bug is fixed properly upstream in git tip and will be part of 1.6.

Nice! :D

The upstream fix applies cleanly against Go 1.5 -- do you think it's
important enough to include now, or just wait for Go 1.6 to be GA
(which will be soon anyways)?

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#813426: warning: /etc/alternatives/compare is dangling; it will be updated with best choice

[積丹尼 Dan Jacobson]

Let's downgrade to back out of deep water...

dpkg: warning: downgrading imagemagick-6.q16 from 8:6.9.2.10+dfsg-2 to 
8:6.8.9.9-7+b1
Preparing to unpack .../imagemagick-6.q16_8%3a6.8.9.9-7+b1_i386.deb ...
Unpacking imagemagick-6.q16 (8:6.8.9.9-7+b1) over (8:6.9.2.10+dfsg-2) ...
Processing triggers for mime-support (3.59) ...
Processing triggers for menu (2.1.47) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Processing triggers for hicolor-icon-theme (0.13-1) ...
Setting up imagemagick-6.q16 (8:6.8.9.9-7+b1) ...
Setting up imagemagick (8:6.8.9.9-7+b1) ...
update-alternatives: warning: alternative /usr/bin/compare-im6.q16 (part of 
link group compare) doesn't exist; removing from list of alternatives
update-alternatives: warning: /etc/alternatives/compare is dangling; it will be 
updated with best choice
update-alternatives: using /usr/bin/compare-im6 to provide /usr/bin/compare 
(compare) in auto mode
update-alternatives: warning: alternative /usr/bin/animate-im6.q16 (part of 
link group animate) doesn't exist; removing from list of alternatives
update-alternatives: warning: /etc/alternatives/animate is dangling; it will be 
updated with best choice
update-alternatives: using /usr/bin/animate-im6 to provide /usr/bin/animate 
(animate) in auto mode
update-alternatives: warning: alternative /usr/bin/convert-im6.q16 (part of 
link group convert) doesn't exist; removing from list of alternatives
update-alternatives: warning: /etc/alternatives/convert is dangling; it will be 
updated with best choice
update-alternatives: using /usr/bin/convert-im6 to provide /usr/bin/convert 
(convert) in auto mode
update-alternatives: warning: alternative /usr/bin/composite-im6.q16 (part of 
link group composite) doesn't exist; removing from list of alternatives
update-alternatives: warning: /etc/alternatives/composite is dangling; it will 
be updated with best choice
update-alternatives: using /usr/bin/composite-im6 to provide /usr/bin/composite 
(composite) in auto mode
update-alternatives: warning: alternative /usr/bin/conjure-im6.q16 (part of 
link group conjure) doesn't exist; removing from list of alternatives
update-alternatives: warning: /etc/alternatives/conjure is dangling; it will be 
updated with best choice
...

Bug#813327: linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c

[Carsten Wolff]

Hi Ben,

thanks for the quick answer.

On Sunday 31 January 2016 23:37:56 Ben Hutchings wrote:
> That suggests a regression in the padlock-aes driver, although I don't
> see any functional changes there.  As a workaround, you can blacklist
> it by adding "blacklist=padlock-aes" to the kernel command line.

of course, but this machine is mainly serving files and running backups and 
padlock really makes a difference in throughput.

> I wonder whether the compiler version makes a difference.  Does the
> 3.16 kernel in the wheezy-backports suite behave any differently?

Unfortunatly, that wasn't it. The bp.o kernel shows the same symptoms. 
Anything else I can try out or do to provide more info?

Cheers
Carsten

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

Bug#813410: lock screen is not working when logged into gnome from sddm

[Pirate Praveen]

Control: reassign -1 gnome-shell
Control: reopen -1

Reassigning to gnome-shell
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#813410: lock screen is not working when logged into gnome from sddm

[Tim]

On 03/02/16 00:00, Pirate Praveen wrote:
>
> I used xlock as a workaround, but gnome-shell should fallback to using
> gnome-screensaver if gdm3 is not available. Keeping the machines
> (laptops) unlocked is not a good default, especially when suspended.
>
> This is basic functionality we are talking about and not some exotic
> nice to have feature.
gnome-shell should automatically fallback to locking using gnome-screensaver 
(via dbus activation) when you are not using gdm. So unless things
have changed recently the only requirement is to have gnome-screensaver package 
installed.
>
>>> Same issue for switch user.
>> There is no standard for user switching, gdm, lightdm and probably sddm all 
>> have their own interfaces for user switching.
> It would be good to have a standard and I think debian gdm maintainers
> are the right people to initiate - being in a position to support
> multiple DEs, such a standard.
It would be good, lightdm have a "org.freedesktop.login1.Manager" dbus 
interface which despite the name is not a spec, which works ok as a
fallback but you loose all DE integration. I'm not sure upstreams would take a 
fallback solution and coming up with a standard which allows for
the required integrations seems like it would be difficult.
>
>
>

Bug#813565: xserver-xorg-video-nvidia: This version is incompatible with the current unstable xserver abi

[Eric Valette]

Package: xserver-xorg-video-nvidia
Version: 355.11-1
Severity: critical
Justification: breaks unrelated software

sddm no more starts. starting xserverr manually via startx, nvidia driver
report ABI incompatibilities and suggest to pass -ignoreABI. Doing this
the xserver crash even before I can start my desktop.

So it does not follow the experimental rules that it should work with
unstable pacakges

-- Package-specific info:
uname -a:
Linux tri-yann4 4.4.1 #13 SMP PREEMPT Sun Jan 31 23:22:15 CET 2016 x86_64 
GNU/Linux

/proc/version:
Linux version 4.4.1 (valette@tri-yann4) (gcc version 5.3.1 20160121 (Debian 
5.3.1-7) ) #13 SMP PREEMPT Sun Jan 31 23:22:15 CET 2016

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  355.11  Wed Aug 26 16:35:41 PDT 
2015
GCC version:  gcc version 5.3.1 20160121 (Debian 5.3.1-7) 

lspci 'VGA compatible controller [0300]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 
670] [10de:1189] (rev a1) (prog-if 00 [VGA controller])
Subsystem: CardExpert Technology GK104 [GeForce GTX 670] [10b0:1189]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia_current

dmesg:
[0.00] Console: colour VGA+ 80x25
[0.265474] vgaarb: setting as boot device: PCI::01:00.0
[0.265476] vgaarb: device added: 
PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none
[0.265481] vgaarb: loaded
[0.265482] vgaarb: bridge control possible :01:00.0
[0.359208] Linux agpgart interface v0.103
[1.038950] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:02.0/:01:00.1/sound/card1/input11
[1.039063] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:02.0/:01:00.1/sound/card1/input12
[1.039169] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:02.0/:01:00.1/sound/card1/input13
[1.039287] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:02.0/:01:00.1/sound/card1/input14
[1.998544] nvidia: module license 'NVIDIA' taints kernel.
[2.007015] vgaarb: device changed decodes: 
PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[2.007407] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on 
minor 0
[2.007420] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  355.11  Wed Aug 
26 16:35:41 PDT 2015

Device node permissions:
crw-rw+ 1 root video 226, 0 Feb  3 08:12 /dev/dri/card0
video:x:44:valette,vdr,hts,sddm

OpenGL and NVIDIA library files installed:
-rw-r--r-- 1 valette valette 1722 Aug 20  2014 /etc/X11/xorg.conf
lrwxrwxrwx 1 rootroot  15 Feb  2 18:16 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 rootroot  49 Sep  2 08:50 
/etc/alternatives/glx--libEGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so
lrwxrwxrwx 1 rootroot  44 Feb  2 18:16 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 rootroot  48 Sep  2 08:50 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 rootroot  48 Sep  2 08:50 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 rootroot  43 Feb  2 18:16 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 rootroot  43 Feb  2 18:16 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 rootroot  50 Feb  2 18:16 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1
lrwxrwxrwx 1 rootroot  50 Feb  2 18:16 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1
lrwxrwxrwx 1 rootroot  52 Sep  2 08:50 
/etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwxrwx 1 rootroot  52 Sep  2 08:50 
/etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwxrwx 1 rootroot  47 Feb  2 18:16 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2
lrwxrwxrwx 1 rootroot  47 Feb  2 18:16 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2
lrwxrwxrwx 1 rootroot  51 Feb  2 18:16 
/etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 rootroot  25 Feb  2 18:16 
/etc/alternatives/glx--

Bug#813564: visp: FTBFS in sid

[Tobias Frost]

Source: visp
Version: 3.0.0-3
Severity: serious
Justification: FTBFS

Hi,
the last upload does not build on the buildds, and I can alos reproduce locally 
when rebuilding
for the libpng transition.

snippet from the buildds:

- Installing: 
/«PKGBUILDDIR»/debian/tmp/usr/include/i386-linux-gnu/visp3/tt_mi/vpTemplateTrackerMIESM.h
-- Installing: 
/«PKGBUILDDIR»/debian/tmp/usr/include/i386-linux-gnu/visp3/tt_mi/vpTemplateTrackerMIBSpline.h
-- Installing: 
/«PKGBUILDDIR»/debian/tmp/usr/include/i386-linux-gnu/visp3/tt_mi/vpTemplateTrackerMI.h
make[1]: Leaving directory '/«PKGBUILDDIR»/obj-i586-linux-gnu'
   debian/rules override_dh_install
make[1]: Entering directory '/«PKGBUILDDIR»'
# On hurd and kfreebsd usr/lib/*/visp/* is empty and produces an error
dh_install "usr/lib/*/visp/*" -p libvisp-dev
dh_install: libvisp-dev missing files: usr/lib/*/visp/*
dh_install: missing files, aborting
debian/rules:111: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 2
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:56: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2

-- 
tobi


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

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

Bug#813563: alsa-utils: Overwrite files from unrelated package

[Michael Rasmussen]

Package: alsa-utils
Version: 1.0.29-1+b1
Severity: critical
Justification: breaks unrelated software

This bug: #813528 actually should have been made here. Please link.

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

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

Versions of packages alsa-utils depends on:
ii  dialog  1.2-20150920-1
ii  kmod22-1
ii  libasound2  1.1.0-1
ii  libc6   2.21-7
ii  libncursesw56.0+20151024-2
ii  libsamplerate0  0.1.8-8
ii  libtinfo5   6.0+20151024-2
ii  lsb-base9.20160110
ii  whiptail0.52.18-2

alsa-utils recommends no packages.

alsa-utils suggests no packages.

-- no debconf information



This mail was virus scanned and spam checked before delivery.
This mail is also DKIM signed. See header dkim-signature.

Bug#807138: golang: gccgo triggers ar warning message when invoked as "go -compiler=gccgo"

[Tianon Gravi]

Control: forwarded -1 https://github.com/golang/go/issues/12310
Control: tags -1 + pending

On 5 December 2015 at 14:30, Eric Cooper  wrote:
> Whenever gccgo is used via the /usr/bin/go command, it calls "ar cru ...",
> which causes this warning:
> $ go build -compiler=gccgo
> # github.com/ecc1/primes
> ar: `u' modifier ignored since `D' is the default (see `U')

Thanks for the report!  There's a fix for this issue officially going
into go1.6, but it seems sane to get it in as soon as we can
(especially since it's such a visible issue) so I've added the patch
upstream included[1] for this to Git and it'll go out with the next
upload. :)

[1]: 
https://github.com/golang/go/commit/321cf6f86dd28248d98e5e24c073740f23c1897b

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#807304: [pkg-golang-devel] Bug#807304: golang: remaining changes from ubuntu's debian/copyright file

[Tianon Gravi]

Control: tags -1 + pending

On 6 December 2015 at 23:42, Michael Hudson-Doyle
 wrote:
> They are minor but they seem like improvements to me.

Indeed!  Patch seems super sane; applied in Git!

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#807299: golang: build-depends overly broad

[Tianon Gravi]

Control: tags -1 + pending

On 6 December 2015 at 23:32, Michael Hudson-Doyle
 wrote:
> bison hasn't been needed for a long time I think... Some of the others are in 
> build-essential.

#win

Applied in Git!

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#807455: golang-src: includes race detector runtime files not built from source in the source package

[Tianon Gravi]

On 8 December 2015 at 18:24, Michael Hudson-Doyle
 wrote:
> The files installed as /usr/share/go/src/runtime/race/*.syso are not built
> during package build, but rather come directly from the Go source 
> distribution.
> To ensure that they are built from what they claim to be, in Ubuntu we do not
> distribute these files in the golang-src package but rather build them in a
> separate golang-race-detector-runtime package which golang-go Recommends:. It
> would be nice if Debian could steal this work :-)

I'm definitely keen on this one!

I think my issue with making it happen (last I looked into it) was
that the files in question needed to come from a separate source (LLVM
was it? [1]), and the exact versioning necessary was a little strange,
and it was sources that already exist in the Debian archive for
another package so I wasn't really clear on whether that's kosher or
whether we should be talking to the existing package maintainer to
keep things sane.  Am I remembering this correctly?  I really
should've made some notes after I spent some time playing with this,
sorry. :(

[1]: https://github.com/golang/go/tree/go1.6rc1/src/runtime/race#readme

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#807303: [pkg-golang-devel] Bug#807303: golang: NEWUSER tests fail on ubuntu (or maybe just new kernel)

[Tianon Gravi]

Control: tags -1 + pending

On 6 December 2015 at 23:37, Michael Hudson-Doyle
 wrote:
> Tests fail in my sid chroot because, on the Ubuntu kernel at least, the tests
> that try to create a new user namespace all fail in a chroot. I fixed this
> upstream but it'd be nice to have this in the 1.5 packaging too so here's a
> backport of the patch.

You've done all the heavy lifting!  This patch is applied in Git, and
will go out with the next upload.  Thanks!

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#807290: golang: does not respect DEB_BUILD_OPTIONS=nocheck

[Tianon Gravi]

Control: tags -1 + pending

On 6 December 2015 at 22:46, Michael Hudson-Doyle
 wrote:
> The package build always runs the tests, irrespective of DEB_BUILD_OPTIONS. 
> Simple patch attached.

Once again, many thanks.  Patch is applied in Git!

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#807294: golang-go: contains some but not all race-enabled packages

[Tianon Gravi]

> + # On linux/amd64 run.bash installs some race enabled standard library
> + # packages. Delete them again to avoid accidentally including them in
> + # the package.
> + rm -rf "$(GOROOT)/pkg/linux_amd64_race/"

This seems like the most correct solution to me, but I'm a little
confused about why we're hard-coding "linux_amd64" here -- shouldn't
this be "$(GOOS)_$(GOARCH)" so that it's whatever architecture we
build on?  Or perhaps "$(GOROOT)"/pkg/*_race/ ?

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#812625: ITA: guitarix -- Rock guitar amplifier for Jack

[Hermann Meyer]

Hi

Thanks Roland for all your work over the years.

Victor, I'm glade you'll take guitarix under the hood of the Multimedia 
Team.


regards
hermann

Bug#813164: coreutils: ls suddenly quotes output

[Jamie Heilman]

Pádraig Brady wrote:
> On 02/02/16 13:19, Jamie Heilman wrote:
> > This behavior needs to be reverted.  There are too many assumptions
> > being made, the quoting used is shell-specific, and not universally
> > supported.  For example, consider a file who's name contains a tab,
> > like "ab".
> > 
> > $ ls
> > 'a'$'\t''b'
> > 
> > OK, so that syntax is supported by bash and zsh, so if you're using
> > one of those shells, maybe you know what it means, and you can cut and
> > paste that and make use of it, but in csh or dash, it doesn't mean the
> > same thing.
> 
> $'...' is in the process of being POSIX standardized.
>
> Even when the shell doesn't support it directly yet,
> surely \t is better than ?

No, it isn't.  Nothing about this behavior is desirable at all.
Unless your goal is to make everyone stop using GNU core utilities
entirely, it will probably see some success at that.

Bug#813562: ITP: ocrmypdf -- add an OCR text layer to PDF files

[Sean Whitton]

Package: wnpp
Severity: wishlist
Owner: Sean Whitton 

* Package name: ocrmypdf
  Version : 3.1.1
  Upstream Author : James R. Barlow 
* URL : https://github.com/jbarlow83/OCRmyPDF
* License : MIT
  Programming Lang: Python
  Description : add an OCR text layer to PDF files

OCRmyPDF is a nice wrapper around the Tesseract OCR engine, and various
other tools to optimise the resulting PDF.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#739035: syncterm/1.0+dfsg-1 [ITP]

[Robert James Clay]

On Monday, February 01, 2016 08:49:10 AM Fernando Toledo wrote:
> 
> Hi all!
> 
> I upload a new version of SyncTerm package.
> 
> feel free for comments/reviews!
> 
> http://mentors.debian.net/package/syncterm

  Glad to see that you were able to update the package! 






Jame
 j...@rocasa.us
 rjc...@gmail.com




 

Bug#813561: RM: fonts-droid -- RoM obsolete

[Vasudev Kamath]

Package: ftp.debian.org
Severity: normal

Dear FTP masters,

fonts-droid is no longer provided as part of fonts-android source since
upstream has shifted from this font to noto fonts. fonts-droid is
currently blocking transition of fonts-android from unstable to
testing. So please remove fonts-droid from unstable.


Best Regards

Bug#813560: utop: FTBFS: Package `cppo_ocamlbuild' not found

[Aaron M. Ucko]

Source: utop
Version: 1.18.1-1
Severity: serious
Justification: fails to build from source

Builds of utop in minimal environments (notably, on the autobuilders)
have been failing:

  ocaml setup.ml -build
  ocamlfind ocamlopt -package unix -package ocamlbuild -linkpkg -package 
cppo_ocamlbuild myocamlbuild.ml /usr/lib/ocaml/ocamlbuild/ocamlbuild.cmx -o 
myocamlbuild
  + ocamlfind ocamlopt -package unix -package ocamlbuild -linkpkg -package 
cppo_ocamlbuild myocamlbuild.ml /usr/lib/ocaml/ocamlbuild/ocamlbuild.cmx -o 
myocamlbuild
  ocamlfind: Package `cppo_ocamlbuild' not found
  Command exited with code 2.

Please declare a build dependency on cppo, and confirm with pbuilder
or the like that you haven't missed anything else.

Thanks!

Bug#813559: ngs-sdk: FTBFS: most platforms explicitly unsupported

[Aaron M. Ucko]

Source: ngs-sdk
Version: 1.2.3-1
Severity: important
Justification: fails to build from source

ngs-sdk fails to build on most platforms because the build system
explicitly refuses to support anything upstream hasn't confirmed to
work -- e.g.,

  checking system type... Linux
  checking machine architecture... aarch64
  configure: error: unsupported architecture 'Linux'

(It looks like a copy-and-paste error resulted in citing Linux rather
than aarch64 there.)

Please either restrict ngs-sdk's Architecture: setting accordingly, or
comment out these checks in all four(!) of ngs-*/setup/konfigure.perl.

Thanks!

Bug#813558: spykeviewer: Section should be “science”

[Ben Finney]

Package: spykeviewer
Version: 0.4.4-1
Severity: minor

Dear Maintainer,

The section “python” is for packages that install the Python
programming language or libraries. Its packages are primarily of
interest only to Python programmers.

The package ‘spykeviewer’ installs primarily an application of
interest regardless of the programming language. It should not be in
the “python” section.

By the section descriptions, this package belongs in section
“science”.

Please set the field “Section” appropriately on this package.


Since the package is already in Debian under a different section, you
will also need to submit a request to override the existing section
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#override-file>.

If the Python libraries are of separate interest to Python
programmers, please consider building separate ‘spykeviewer’ and
‘python3-spykeviewer’ packages. (I can file a bug report requesting
that also, if you like.)

-- 
 \ “Pinky, are you pondering what I'm pondering?” “I think so, |
  `\Brain, but this time *you* put the trousers on the chimp.” |
_o__)   —_Pinky and The Brain_ |
Ben Finney 

Bug#813557: ngs-sdk: FTBFS on i386: libngs-sdk.so not in expected directory

[Aaron M. Ucko]

Source: ngs-sdk
Version: 1.2.3-1
Severity: important
Justification: fails to build from source

The i386 build of ngs-sdk failed:

  d-shlibmove --commit \
--multiarch \
--devunversioned \
--exclude-a \
--exclude-la \
--movedev 
"ngs-sdk/i586-linux-gnu/ngs-sdk/linux/gcc/i586/rel/lib/*.a*" 
usr/lib/i586-linux-gnu \
--movedev 
"ngs-sdk/i586-linux-gnu/ngs-sdk/linux/gcc/i586/rel/ilib/*.a" 
usr/lib/i586-linux-gnu \
ngs-sdk/i586-linux-gnu/ngs-sdk/linux/gcc/i586/rel/lib/libngs-sdk.so
  Library package automatic movement utility
  /usr/bin/d-shlibmove: expected 
[ngs-sdk/i586-linux-gnu/ngs-sdk/linux/gcc/i586/rel/lib/libngs-sdk.so] to be a 
symlink, but it is not
  debian/rules:69: recipe for target 'override_dh_auto_install' failed

It looks like the library wound up in .../i386/..., not .../i586/...;
please try substituting DEB_BUILD_ARCH_CPU for DEB_BUILD_GNU_CPU
accordingly.

Thanks!

Bug#813556: ITP: libprotocol-acme-perl -- Perl Interface to the Let's Encrypt ACME API

[Salvatore Bonaccorso]

Package: wnpp
Owner: Salvatore Bonaccorso 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libprotocol-acme-perl
  Version : 0.11
  Upstream Author : Stephen Ludin 
* URL : https://metacpan.org/release/Protocol-ACME
* License : Artistic-2.0
  Programming Lang: Perl
  Description : Perl Interface to the Let's Encrypt ACME API

The Protocol::ACME is a class implementing an interface for the Let's Encrypt
ACME API.

NOTE: This code at this point is functional but should be considered 'alpha'
quality.

The class handles the protocol details behind provisioning a Let's Encrypt
certificate.

The package will be maintained under the umbrella of the Debian Perl Group.

Bug#813555: darktable: Darktable should depend on lensfun1 instead of lensfun0.

[Josef Wells]

Package: darktable
Version: 2.0.0-1
Severity: important

Dear Maintainer,

   lensfun0 and lensfun1 are the same upstream
   -lensfun0 is 0.2.8
   -lensfun1 is 0.3.2

   darktable 2.* should use lensfun 0.3.2, which is lensfun1 in debian.


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

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

Versions of packages darktable depends on:
ii  libatk1.0-0   2.18.0-1
ii  libc6 2.19-22
ii  libcairo-gobject2 1.14.4-1
ii  libcairo2 1.14.4-1
ii  libcolord-gtk10.1.25-1.1+b1
ii  libcolord21.2.11-1
ii  libcups2  2.1.0-5
ii  libcurl3-gnutls   7.45.0-1+b1
ii  libexiv2-14   0.25-2.1
ii  libflickcurl0 1.25-3
ii  libgcc1   1:5.2.1-23
ii  libgdk-pixbuf2.0-02.32.1-1
ii  libgl1-mesa-glx [libgl1]  10.6.8-1
ii  libglib2.0-0  2.46.1-2
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgomp1  5.2.1-23
ii  libgphoto2-6  2.5.9-3
ii  libgphoto2-port12 2.5.9-3
ii  libgraphicsmagick-q16-3   1.3.22-1
ii  libgtk-3-03.18.2-1
ii  libice6   2:1.0.9-1+b1
ii  libilmbase6v5 1.0.1-6.2
ii  libjpeg62-turbo   1:1.4.1-2
ii  libjs-prototype   1.7.1-3
ii  libjs-scriptaculous   1.9.0-2
ii  libjson-glib-1.0-01.0.4-2
ii  liblcms2-22.6-3+b3
ii  liblensfun0   0.2.8-3
ii  liblua5.2-0   5.2.4-1
ii  libopenexr6v5 1.6.1-8.1+b2
ii  libopenjpeg5  1:1.5.2-3.1
ii  libosmgpsmap-1.0-11.1.0-1
ii  libpango-1.0-01.38.1-1
ii  libpangocairo-1.0-0   1.38.1-1
ii  libpng12-01.2.50-2+b2
ii  libpugixml1v5 1.6-2
ii  librsvg2-22.40.11-1
ii  libsdl1.2debian   1.2.15-12
ii  libsecret-1-0 0.18.3-1
ii  libsm62:1.2.2-1+b1
ii  libsoup2.4-1  2.52.1-1
ii  libsqlite3-0  3.9.1-2
ii  libstdc++65.2.1-23
ii  libtiff5  4.0.5-1
ii  libwebp5  0.4.3-1.3
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.2+zdfsg1-4
ii  libxrandr22:1.5.0-1
ii  zlib1g1:1.2.8.dfsg-2+b1

darktable recommends no packages.

darktable suggests no packages.

-- no debconf information

Bug#813554: closed by Colin Watson (Re: Bug#813554: grub: grub-efi-amd64-bin should be availible on 32 bit systems)

[nerdopolis]

On Wednesday, February 03, 2016 03:36:06 AM you wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the grub-efi-amd64-bin package:
> 
> #813554: grub: grub-efi-amd64-bin should be availible on 32 bit systems
> 
> It has been closed by Colin Watson .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Colin Watson 
>  by
> replying to this email.
> 
> 
> 
Wow. I am not sure how I missed that... Thanks

Bug#780530: [calendarserver]

[Rahul Amaram]

On Wednesday 03 February 2016 12:05 AM, Ximin Luo wrote:

iv. Upload new packages twextpy and pg8000


I've just uploaded these. I fixed a few minor things before uploading, please check git 
and review them. In general, I run "lintian -i -I --pedantic --color auto 
xxx.changes" to catch things like that, and it's a good habit to get into.
I had created two entries in debian/changelog because I had already 
tagged the first release version and did not want to delete the tags. I 
have now, however, deleted the tags and recreated them. Like you said, I 
think it is best to create tags, once the packages are uploaded.
Also, I always run lintian, but don't use the --pedantic option. Will 
start using it hereafter.


As part of the fix to (k) earlier, I pushed another patch to a side branch of 
calendarserver: [1]. You haven't applied it to debian/sid yet, but I think it may be 
necessary. To test, you should try to add/remove events with non-ascii unicode characters 
in them such as "ßßß". If it fails, then try the patch and if it works please 
add it to git as well.

X

[1] 
https://anonscm.debian.org/cgit/calendarserver/calendarserver.git/diff/debian/patches/unicode-fixes.patch?h=debian/_wip_sid&id=4476a73ff4df39baa297606e00e66241f371178c

I will see how I could test unicode characters. Also, I do not know the 
impact of the change. Should I get it reviewed by upstream?


Thanks,
Rahul.

Bug#813554: grub: grub-efi-amd64-bin should be availible on 32 bit systems

[nerdopolis]

Package: grub-efi-amd64-bin
Version: 2.02~beta2-35
Severity: wishlist
File: grub

Dear Maintainer,
grub-efi-amd64-bin should be an installable package even on 32 bit 
x86 computers, as some EFI platforms refuse to load 32 bit EFI
images (tested withTianoCore) with a 64 bit processor


-- Package-specific info:

*** BEGIN /proc/mounts
/dev/sr0 /cdrom iso9660 ro,noatime 0 0
/dev/loop0 /rofs squashfs ro,noatime 0 0
*** END /proc/mounts

*** BEGIN /proc/mdstat
cat: /proc/mdstat: No such file or directory
*** END /proc/mdstat

*** BEGIN /dev/disk/by-id
total 0
lrwxrwxrwx 1 root root 9 Feb  3 03:02 ata-QEMU_DVD-ROM_QM3 -> ../../sr0
lrwxrwxrwx 1 root root 9 Feb  3 03:02 ata-QEMU_HARDDISK_QM4 -> ../../sda
*** END /dev/disk/by-id

*** BEGIN /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 9 Feb  3 03:02 2016-02-03-02-29-48-00 -> ../../sr0
*** END /dev/disk/by-uuid

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

Kernel: Linux 4.3.0-1-686-pae (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 grub-efi-amd64-bin depends on:
ii  efibootmgr   0.12-4
ii  grub-common  2.02~beta2-35

grub-efi-amd64-bin recommends no packages.

grub-efi-amd64-bin suggests no packages.

-- no debconf information

Bug#601139: Overrides for desktop2menu, and add xdg=false

[James McCoy]

On Sat, Oct 23, 2010 at 08:26:17PM +0200, Wouter Verhelst wrote:
> I've been annoyed by the fact that the maintainers of some desktop
> environments in Debian have chosen to ignore the Debian menu, chosing
> instead to only ship .desktop files, since it would be much work to
> write and maintain .menu files for all their packages (as opposed to
> .desktop files, which are usually provided by upstream). The unfortunate
> result is that software which supports the Debian menu system now no
> longer shows all applications that should probably show up in a menu.

Given the CTTE decision regarding the Debian menu
(<20150904033414.gd3...@qor.donarmstring.com>), is this still something
you're interested in?

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy 

Bug#809323: systemd-rfkill.socket doesn't load at startup

[Michael Biebl]

Control: tags -1 + moreinfo

Am 29.12.2015 um 12:00 schrieb Yuri D'Elia:
> Package: systemd
> Version: 228-2+b1
> Severity: normal
> 
> Occasionally I have trouble with rfkill. Digging in the logs shows that
> systemd-rfkill.socket might start too early during boot:
> 
> Dec 03 00:25:48 eab14156nb systemd[1]: systemd-rfkill.socket: Socket service 
> systemd-rfkill.service not loaded, refusing.
> Dec 03 00:25:48 eab14156nb systemd[1]: Failed to listen on Load/Save RF Kill 
> Switch Status /dev/rfkill Watch.
> 
> Shouldn't it Depend/After explictly systemd-rfkill.service?

What's the output of
systemctl status systemd-rfkill.service
systemctl status systemd-rfkill.socket

Booking with systemd.log_level=debug on the kernel command line and
attaching the output of journalctl -alb might be helpful as well when
that problem happens.


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



signature.asc
Description: OpenPGP digital signature

Bug#813164: coreutils: ls suddenly quotes output

[Pádraig Brady]

On 02/02/16 13:19, Jamie Heilman wrote:
> This behavior needs to be reverted.  There are too many assumptions
> being made, the quoting used is shell-specific, and not universally
> supported.  For example, consider a file who's name contains a tab,
> like "ab".
> 
> $ ls
> 'a'$'\t''b'
> 
> OK, so that syntax is supported by bash and zsh, so if you're using
> one of those shells, maybe you know what it means, and you can cut and
> paste that and make use of it, but in csh or dash, it doesn't mean the
> same thing.

$'...' is in the process of being POSIX standardized.

Even when the shell doesn't support it directly yet,
surely \t is better than ?

Bug#813553: gtk-redshift: Fails to start under awesome desktop enviroment

[Alexander Trousevich]

Package: gtk-redshift
Version: 1.9.1-4
Severity: important

Dear Maintainer,

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

   * What led up to the situation?

1. Install awesome window manager. Do not install gnome or anything
else.

2. Run command `gtk-redshift` in terminal emulator.

3. Program silently terminates with exit code 255

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

doctor@trousev-debian-desktop:~$ redshift-gtk
doctor@trousev-debian-desktop:~$ echo $?
255


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

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

Versions of packages gtk-redshift depends on:
ii  gir1.2-appindicator3-0.1  0.4.92-3.1
ii  python-gtk2   2.24.0-4
ii  python3   3.4.2-2
ii  python3-gi3.14.0-1
ii  python3-xdg   0.25-4
pn  python3:any   
ii  redshift  1.9.1-4

Versions of packages gtk-redshift recommends:
ii  at-spi2-core  2.14.0-1

gtk-redshift suggests no packages.

-- no debconf information

Bug#813382: systemd: journalctl shows no output with --since / --until unless --reverse is also specified

[Michael Biebl]

Control: tags -1 + moreinfo

Am 01.02.2016 um 15:16 schrieb Arno Peters:
> Package: systemd
> Version: 215-17+deb8u3
> Severity: normal
> 
> Dear Maintainer,
> 
> NOTE: This only happens on some systems.
> 
> When running journalctl like so (today is February 1st 2016):
> 
> # journalctl --since '2016-01-29 08:08:00' --until '2016-01-29 08:09:00'
..
> # journalctl --since '2016-01-29 08:08:00' --until '2016-01-29 08:09:00'

Those two commands are identical, yet they produce different output?

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



signature.asc
Description: OpenPGP digital signature

Bug#805498: systemd: Systemd errors in syslog: Failed to set cpu.cfs_{period,quota}_us

[Michael Biebl]

Control: tags -1 + moreinfo

On Wed, 18 Nov 2015 21:08:23 +0100 Ralf Jung  wrote:
> Package: systemd
> Version: 215-17+deb8u2
> Severity: normal
> 
> Dear Maintainer,
> 
> I see the following errors frequently pop up in the syslog:
> 
> Nov 18 18:30:21 bridge systemd[1]: Failed to set cpu.cfs_period_us on 
> /system.slice/systemd-tmpfiles-clean.service: Permission denied
> Nov 18 18:30:21 bridge systemd[1]: Failed to set cpu.cfs_quota_us on 
> /system.slice/systemd-tmpfiles-clean.service: Permission denied
> 
> Not sure whether that's a problem... but I probably shouldn't have errors in 
> the log in the default config.
> 

I see that you have docker installed, which might be related [1].
If you purge the docker (related) packages, does the problem go away?
Afaics, the docker package tries to use kernel features which aren't
supported by the Debian kernel in jessie [1].



[1] https://github.com/docker/docker/issues/17587
[2] https://lists.debian.org/debian-kernel/2015/10/msg00313.html
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#765755: udev: systemd-udev - segfault at 0 ip 00007f6c6ba3aa79 in libc-2.19.so[7f6c6b940000+19f000]

[Michael Biebl]

Control: tags -1 + moreinfo

On Fri, 17 Oct 2014 22:52:34 +0300 George Shuklin
 wrote:
> Package: udev
> Version: 215-5+b1
> Severity: normal
> 
> systemd-udev crash periodically
> 
> [98727.385926] systemd-udevd[26001]: segfault at 0 ip 7f6c6ba3aa79 
> sp 7fffe80964a0 error 4 in libc-2.19.so[7f6c6b94+19f000]
> [157684.619642] systemd-udevd[30309]: segfault at 0 ip 7f6c6ba3aa79 
> sp 7fffe80964a0 error 4 in libc-2.19.so[7f6c6b94+19f000]
> [179038.544879] systemd-udevd[17968]: segfault at 0 ip 7f6c6ba3aa79 
> sp 7fffe80964a0 error 4 in libc-2.19.so[7f6c6b94+19f000]
> [187925.052643] systemd-udevd[19819]: segfault at 0 ip 7f6c6ba3aa79 
> sp 7fffe80964a0 error 4 in libc-2.19.so[7f6c6b94+19f000]
> [187950.163097] systemd-udevd[20108]: segfault at 0 ip 7f6c6ba3aa79 
> sp 7fffe80964a0 error 4 in libc-2.19.so[7f6c6b94+19f000]
> [206200.512975] systemd-udevd[24209]: segfault at 0 ip 7f6c6ba3aa79 
> sp 7fffe80964a0 error 4 in libc-2.19.so[7f6c6b94+19f000]
> [256387.474948] systemd-udevd[4754]: segfault at 0 ip 7f6c6ba3aa79 
> sp 7fffe80964a0 error 4 in libc-2.19.so[7f6c6b94+19f000]
> 

Is this problem still reproducible?
If so, please install the systemd-dbg and try to get a proper backtrace.

Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#810021: devscripts: [bts] bts --cache-mode=full cache fails when fetching empty msg parts?

[James McCoy]

On Tue, Jan 05, 2016 at 07:42:14PM +, Adam D. Barratt wrote:
> On Tue, 2016-01-05 at 12:54 -0500, Daniel Kahn Gillmor wrote:
> > 0 dkg@alice:~$ bts --cache --cache-mode=full cache src:gnupg2
> > Downloading http://bugs.debian.org/src:gnupg2 ... (cached new version) 
> > Downloading http://bugs.debian.org/678613 ... bts: failed to download 
> > bugreport.cgi?msg=4;mbox=yes;bug=678613, skipping
> > bts: failed to download bugreport.cgi?mbox=yes;msg=9;bug=678613, skipping
> > (cached new version) 1/116
> [...]
> > Sorry to not have more pointers about what's going wrong here.  Maybe
> > something changed in some perl module about "success" or "failure"
> > when the file fetched has 0 length?
> 
> As far as I can tell, nothing's changed in terms of the code - bts has
> always regarded a 0-byte file as a failure. The oldest machine I have to
> hand to check is wheezy, which has
> 
>   if ($response->is_success) {
> my $content_length = defined $response->content ?
> length($response->content) : 0;
> if ($content_length == 0) {
> warn "$progname: failed to download $ref, skipping\n";
> 
> Presumably only "cache-mode=full" causes the "useless messages" to be
> downloaded.

Keeping above context for owner@.

> What I'm not sure about is whether the BTS has always
> presented those files as 0-bytes and, if so, why it bothers linking to
> the mbox to begin with; the "full text" (i.e. non-mbox) versions appear
> to be populated as expected.

Good questions.  Maybe debbugs folks have some insight.

The bts(1) code has done this since mirroring/cacheing was first
implemented, so it's definitely nothing new.  However, they may be a
little overzealous or maybe were compensating for an issue since fixed
in LWP.

I'm adverse to changing the check, but I also don't think we need a
bunch of zero-length files being mirrored.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy 

Bug#791195: fixed in lttoolbox 3.3.2~r61000-3.1

[Andreas Beckmann]

On Thu, 20 Aug 2015 16:00:44 + Julien Cristau 
wrote:
>  lttoolbox (3.3.2~r61000-3.1) unstable; urgency=medium
>  .
>* Non-maintainer upload.
>* Rename library packages for g++5 ABI transition (closes: 791195).

This change was recently reverted and I'm not convinced that this was a
good idea.

 lttoolbox (3.3.2~r63423-1) unstable; urgency=low
 .
   [ Tino Didriksen ]
   * New upstream snapshop release.
 .
   [ Kartik Mistry ]
   * debian/control:
 + Fixed Vcs-* URLs.
 + Removed dummy library package used for g++5 ABI transition.
   * debian/patches:
 + Added patch to fix hyphen used as minus.



Andreas

Bug#813552: spe: switch dependency from python-wxglade to wxglade

[Andreas Beckmann]

Package: spe
Version: 0.8.4.h-3.1
Severity: serious
Tags: sid stretch

Hi,

python-wxglade has been renamed to wxglade, please update your
dependencies.


Andreas

Bug#813551: blacs-mpi: please enable test suite during build

[Michael Banck]

Package: blacs-mpi
Version: 1.1-33.1
Severity: wishlist
Tags: patch

Hi,

while blacs ships a package with the test suite, I think it is crucial
to also run the test suite during package build in order to catch issues
on unpopular architectures for example.

One issue is that you need at least 4 processes, but the test suite is
rather quick (at least on my notebook) so I think it should be
tolerable.

To enable, you need to add mpi-default-bin to debian/control.in and
something like the following (I put it at the of build-stamp-*):

ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
-(cd TESTING/EXE && mpirun -np 4 ./xFbtest_MPI-LINUX-0-static-openmpi)
-(cd TESTING/EXE && mpirun -np 4 ./xFbtest_MPI-LINUX-0-shared-openmpi)
-(cd TESTING/EXE && mpirun -np 4 ./xCbtest_MPI-LINUX-0-static-openmpi)
-(cd TESTING/EXE && mpirun -np 4 ./xCbtest_MPI-LINUX-0-shared-openmpi)
endif

Ignoring errors is required for openmpi at least cause the test suite
seems to make an abort test at the end which results in an exit code
other than zero for me.


Michael

Bug#813128: Fwd: Bug#813128: transition: openmpi

[Michael Banck]

On Tue, Feb 02, 2016 at 02:40:11PM +, Mattia Rizzolo wrote:
> On Tue, Feb 02, 2016 at 08:44:46AM +0100, Alastair McKinstry wrote:
> > On 01/02/2016 16:34, Michael Banck wrote:
> > > On Mon, Feb 01, 2016 at 11:41:17AM +, Alastair McKinstry wrote:
> > >> Its not fully ready for transition, and I need to put a blocker on it.
> > >> Small fixes for kFreeBSD, Hurd: (conditional use of --verbs in
> > >> configure), pkg-config file handling,
> > >> enabling of static if possible, tests.
> 
> I wonder, why don't you build for s390x? I tried a build on a porterbox
> (version 1.10.2-2 + enable s390x on Architecture:) and it built just
> fine.
> Also I have a gut feeling x32 is going to just work too.
> And at this point it makes me wonder why not just using arch:any.
> 
> The change away from arch:any seems to be (according to the changelog)
> from 2007, version 1.2.3-3, but I'm not sure if this makes sense
> anymore.  At least, the package builds...

That's good news, I agree it makes sense to switch to Arch: any now and
turn on the test suite to see what breaks - that's certainly something
that should've better happened in experimental as intended, but oh well.


Michael

Bug#813550: gitlab: Fails to install with ruby-activesupport=2:4.2.5.1-1

[Viktor Malyarchuk]

Package: gitlab
Version: 8.4.0+dfsg-1
Severity: important

Dear Maintainer,

gitlab fails to install with ruby-activesupport=2:4.2.5.1-1

Verifying we have all required libraries...
Resolving dependencies.
Could not find activesupport-4.2.5 in any of the sources
dpkg: error processing package gitlab (--configure):
 subprocess installed post-installation script returned error exit status 7

There is no ruby-activesupport 4.2.5 in Debain.

Best regards,
Viktor

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

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

Versions of packages gitlab depends on:
ii  adduser3.113+nmu3
ii  asciidoctor1.5.3-1
ii  bc 1.06.95-9+b1
ii  debconf [debconf-2.0]  1.5.58
ii  gitlab-shell   2.6.10-1
ii  gitlab-workhorse   0.5.0-1
ii  libjs-chartjs  1.0.2-1
ii  libjs-clipboard1.4.2-1
ii  libjs-fuzzaldrin-plus  0.3.1-1
ii  libjs-graphael 0.5+dfsg-1
ii  libjs-jquery-cookie10-2
ii  libjs-jquery-history   10-2
ii  libjs-jquery-nicescroll3.6.6-1
ii  nginx  1.9.10-1
ii  nginx-full [nginx] 1.9.10-1
ii  nodejs 4.2.6~dfsg-1
ii  postgresql 9.5+172
ii  postgresql-client-9.5 [postgresql-client]  9.5.0-2
ii  rake   10.4.2-2
ii  redis-server   2:3.0.7-2
ii  ruby   1:2.3~0
ii  ruby-ace-rails-ap  3.0.3-2
ii  ruby-activerecord-deprecated-finders   1.0.4-1
ii  ruby-activerecord-session-store0.1.1-2
ii  ruby-acts-as-taggable-on   3.5.0-2
ii  ruby-addressable   2.3.8-1
ii  ruby-after-commit-queue1.3.0-1
ii  ruby-allocations   1.0.3-1
ii  ruby-asana 0.4.0-1
ii  ruby-attr-encrypted1.3.4-1
ii  ruby-babosa1.0.2-1
ii  ruby-bootstrap-sass3.3.5.1-3
ii  ruby-browser   1.0.1-1
ii  ruby-cal-heatmap-rails 3.5.1+dfsg-1
ii  ruby-carrierwave   0.10.0+gh-1
ii  ruby-charlock-holmes   0.7.3+dfsg-2
ii  ruby-coffee-rails  4.1.0-2
ii  ruby-colorize  0.7.7-1
ii  ruby-connection-pool   2.2.0-1
ii  ruby-creole0.5.0-2
ii  ruby-d3-rails  3.5.6+dfsg-1
ii  ruby-default-value-for 3.0.1-1
ii  ruby-devise3.5.2-3
ii  ruby-devise-async  0.9.0-1
ii  ruby-devise-two-factor 2.0.0-1
ii  ruby-diffy 3.0.6-1
ii  ruby-doorkeeper2.2.1-1
ii  ruby-dropzonejs-rails  0.7.1-1
ii  ruby-email-reply-parser0.5.8-1
ii  ruby-fog   1.34.0-2
ii  ruby-fogbugz   0.2.1-2
ii  ruby-font-awesome-rails4.3.0.0-1
ii  ruby-gemnasium-gitlab-service  0.2.6-1
ii  ruby-github-linguist   4.7.2-1
ii  ruby-github-markup 1.3.3+dfsg-1
ii  ruby-gitlab-emoji  0.2.1-1
ii  ruby-gitlab-flowdock-git-hook  1.0.1-1
ii  ruby-gitlab-git7.2.22-1
ii  ruby-gollum-lib4.1.0-3
ii  ruby-gon   6.0.1-1
ii  ruby-grape 0.13.0-1
ii  ruby-grape-entity  0.4.5-1
ii  ruby-haml-rails0.9.0-4
ii  ruby-hipchat   1.5.2-1
ii  ruby-html-pipeline 1.11.0-1
ii  ruby-httparty  0.13.5-1
ii  ruby-influxdb  0.2.3-1
ii  ruby-jquery-atwho-rails1.3.2-2
ii  ruby-jquery-rails  4.0.5-1
ii  ruby-jquery-scrollto-rails 1.4.3+dfsg-1
ii  ruby-jquery-turbolinks 2.1.0~dfsg-1
ii  ruby-jquery-ui-rails   5.0.5-3
ii  ruby-kaminari 

Bug#813490: Bug #813490: blacs-mpi: patch for blacs-mpi to build with openmpi1.10

[Michael Banck]

On Wed, Feb 03, 2016 at 01:25:46AM +0100, Michael Banck wrote:
> the patch is missing a Build-Depends for pkg-config. Note that
> debian/control is auto-generated so it needs to be added to
> debian/control.in.

And the debian/rules hunk is missing a semicolon at the end.



Michael

Bug#813549: cobbler: New version available upstream

[Heather Ellsworth]

Package: cobbler
Version: 2.6.11
Severity: wishlist

Dear Maintainer,

Version 2.6.11 is available from https://github.com/cobbler/cobbler.git

Thanks,
Heather Ellsworth

-- System Information:
Debian Release: 8.3
  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)

Bug#813490: Bug #813490: blacs-mpi: patch for blacs-mpi to build with openmpi1.10

[Michael Banck]

Hi,

the patch is missing a Build-Depends for pkg-config. Note that
debian/control is auto-generated so it needs to be added to
debian/control.in.


Michael

Bug#782553: sbuild: 'sbuild --source --no-arch-all' fails in a very confusing way

[Dima Kogan]

Johannes Schauer  writes:

> I am not able to reproduce this behaviour. I have $sbuild_source=1; in my
> ~/.sbuildrc but neither do I see any of the above error messages nor do I get
> 'Status: attempted'. Can you confirm that this issue was fixed with the recent
> sbuild release?

Hi. I just tried to reproduce, and once again, things work now. The
cleanup you did in this area must have taken care of this issue. And the
documentation changes are probably sufficient for the option conflicts.
Thank you very much!!!

Bug#669053: smartd.conf.5.in, version 5.42: Escape before "<" and ">", spaces and orthography in the manual.

[Bjarni Ingi Gislason]

On Mon, Feb 01, 2016 at 10:47:23AM +, Jonathan Dowland wrote:
> On Sat, Jan 30, 2016 at 09:47:25PM +, Bjarni Ingi Gislason wrote:
> > On Fri, Jan 29, 2016 at 04:40:19PM +, Jonathan Dowland wrote:
> > > Hi, thanks for getting back in touch.
> > > 
> > > I'm hoping to carry this patch in the next smartmontools upload. Somebody 
> > > needs
> > > to refresh it as ~50% of the hunks no longer apply to the current
> > > smartd.conf.5.
> > > 
> > 
> >   I can make a new patch.
> > Which source file shall I use?
> 
> Please find attached the current smartd.conf.5.
> 

  What  not was done:

  Use a macro to change to the italic font, instead of \fI [1],
if possible.
The macros have the italic corrections.
[1] man-pages(7)

  Use a macro instead of an escape sequence, \f...\P.,
for font style changes.

-- End ---

  What was done for
$Id: smartd.conf.5.in 4103 2015-06-01 19:51:18Z chrfranke $

Enable and fix warnings from 'man' and 'groff'.

:40: warning: escape character ignored before `<'
:40: warning: escape character ignored before `>'

#

Change `` to ".

#

Split lines longer than about 80 characters into two or more
lines.

  References:

  1) man-pages(7) from package \"man-pages\" or
\"www.kernel.org/doc/man-pages\" section 7 or
\"man7.org/linux/man-pages/man7/man-pages.7.html\":

New sentences should be started on new lines.
This makes it easier to see the effect of patches,
which often operate at the level of individual sentences.

  2) groff_diff(7) in package \"groff\":

In GNU troff, as in UNIX troff, you should always follow a sentence
with either a newline or two spaces.

  3) \"info groff\":

  Search for \"sentence\" to get more hints about input conventions.

#

  Remove space at end of lines.

#

The space between sentences in "roff" is two spaces.
Better is to begin each sentence on a new line to avoid different
writers' conventions.

#

Change \' (acute) to \(aq, if used as a quote.
Change \' (acute) to ', if used as an apostrophe.

#

Change - to \(en (en-dash) for a numeric range.

#

Protect a full stop (.) with \&, if
 a) it can be transported to the first column, when the line is
reformatted (split).
 b) it is the last part of an abbreviation that does not end a
sentence.

#

Add a (no-break, "\ ") space between a number and an unit as these
are not one entity

#

Change a hyphen-minus to a minus (\-),
if in front of a name for an option

#

Remove space in the first column,
if not intended.

# End

  Patch is in the attachment.


-- 
Bjarni I. Gíslason


smartd.conf.5.in.diff.gz
Description: GNU Zip compressed data

Bug#800947: ACL for /var/log/journal not set for group adm

[Michael Biebl]

Control: tags -1 + pending

On Mon, 5 Oct 2015 12:26:02 +0200 =?UTF-8?Q?Rapha=c3=abl_Halimi?=
 wrote:
> Package: systemd
> Version: 226-4
> 
> Hi,
> 
> About persistent logging, README.Debian claims :
> 
> "systemd will add an ACL for read permissions for users in the "adm" group."
> 
> This is not working: after creating /var/log/journal with the "install"
> command as instructed in the README.Debian, and even after several
> reboots, the ACL is not set:
> 
> raph@arche:~$ getfacl /var/log/journal/
...

While the idea of shipping /var/log/journal pre-configured in the
package is still an option, I now decided to apply a different fix.

I've cherry-picked two upstream commits which also apply the ACLs to
/var/log/journal (so newly created files inherit them directly) and to
exisiting system.journal files.

I've also updated the instructions in README.Debian (which now match
what's in man systemd-journald(8):

   mkdir -p /var/log/journal
   systemd-tmpfiles --create --prefix /var/log/journal

Those two command are now sufficient to setup the persistent journal
with the correct permissions and ACLs.

This will be part of the upcoming 228-5 release.
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#813426: warning: /etc/alternatives/compare is dangling; it will be updated with best choice

[Vincent Fourmond]

control: tags -1 +moreinfo

  Dear Jidanni,

On Mon, Feb 1, 2016 at 9:00 PM, jidanni1 
wrote:

> Package: imagemagick-6.q16
> Version: 8:6.9.2.10+dfsg-2
>
> Lots of
> update-alternatives: warning: alternative /usr/bin/compare-im6 (part of
> link group compare) doesn't exist; removing from list of alternatives
> update-alternatives: warning: /etc/alternatives/compare is dangling; it
> will be updated with best choice
> update-alternatives: using /usr/bin/compare-im6.q16 to provide
> /usr/bin/compare (compare) in auto mode
> update-alternatives: warning: alternative /usr/bin/animate-im6 (part of
> link group animate) doesn't exist; removing from list of alternatives
>
>
  Could you please paste the full log, if you still have it, or tell us
from which version you're upgrading ? And which version of the imagemagick
package ? If it was updated before/after/not updated ?

  Thanks a lot,

  Vincent

Bug#813350: joe: :include ignores other commands in the file

[Josip Rodin]

On Mon, Feb 01, 2016 at 01:53:24AM +0100, Adam Borowski wrote:
> /usr/share/doc/joe/README.Debian claims you can ":include /etc/joe/jstarrc"
> to avoid having to copy the entire file and to make it work over upgrades.
> However, doing so seems to ignore the entirety of ~/.jstarrc
> 
> Let's say we want to replace
> -rmsg  %S Row %4r Col %3c %t  Ctrl-J for help
> with
> -rmsg  %S Row %4r Col %3c %A
> 
> The following ~/.jstarrc
> =
> :include /etc/joe/jstarrc
> -rmsg  %S Row %4r Col %3c %A
> =
> makes "Ctrl-J for help" show up instead of the Unicode code.
> 
> so does
> =
> -rmsg  %S Row %4r Col %3c %A
> :include /etc/joe/jstarrc
> =
> so it's not a matter of "first setting stays".

Could this be some sort of a special screwup with regard to jstar, like the
previous bug? Because, I still have the latter config with .joerc and it's
working.

-- 
 2. That which causes joy or happiness.

Bug#813547: iceweasel: Wrong colors in framebuffer Xorg fbdev if enable hardware video acceleration on PowerPC

[Gianluca Renzi]

Package: iceweasel
Version: 44.0-1
Severity: important

Dear Maintainer,

After upgrading sid/experimental the iceweasel acceleration enable feature is 
not working good
if using fbdev xorg configuration with swrast (xinerama setup). It hangs the 
CPU near the 100% and all the colors are in a wrong
RGBA order. Color Swap? Bad RGBA ABGR conversion? This setup is a PowerPC BIG 
ENDIAN machine...

The only way is to use the accelerated video driver (i.e. radeon or nouveau in 
my specific setup)
or
disabling the hardware acceleration feature in the iceweasel preferences section

The biggest issue in this configuration is I am unable to upgrade either kernel 
(due to a binutils bug on PPC64 architecture),
so I can not say for sure if it happens with the 4.4.0 drivers.

Right now I am using the 4.1.0-2 kernel version and the lastest xorg drivers. 
(updated today)


-- Package-specific info:

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

Name: Force PDF Download
Location: ${PROFILE_EXTENSIONS}/{d7f46ca0-899d-11da-a72b-0800200c9a65}.xpi
Status: enabled

-- Plugins information
Name: Shockwave Flash
Location: /usr/lib/gnash/libgnashplugin.so
Package: browser-plugin-gnash
Status: enabled


-- Addons package information
ii  browser-plugin 0.8.11~git20 powerpc  GNU Shockwave Flash (SWF) player 
ii  iceweasel  44.0-1   powerpc  Web browser based on Firefox

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

Kernel: Linux 4.1.0-2-powerpc64 (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 iceweasel depends on:
ii  debianutils   4.7
ii  fontconfig2.11.0-6.3
ii  libasound21.1.0-1
ii  libatk1.0-0   2.18.0-1
ii  libatomic15.3.1-7
ii  libc6 2.21-7
ii  libcairo2 1.14.6-1
ii  libdbus-1-3   1.10.6-1
ii  libdbus-glib-1-2  0.106-1
ii  libevent-2.0-52.0.21-stable-2+b1
ii  libffi6   3.2.1-4
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.6.1-0.1
ii  libgcc1   1:5.3.1-7
ii  libgdk-pixbuf2.0-02.32.3-1.2
ii  libglib2.0-0  2.46.2-3
ii  libgtk2.0-0   2.24.29-1
ii  libhunspell-1.3-0 1.3.3-3+b2
ii  libnspr4  2:4.11-1
ii  libnss3   2:3.21-1
ii  libpango-1.0-01.38.1-1
ii  libsqlite3-0  3.10.2-1
ii  libstartup-notification0  0.12-4
ii  libstdc++65.3.1-7
ii  libvpx3   1.5.0-2
ii  libx11-6  2:1.6.3-1
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxrender1   1:0.9.9-2
ii  libxt61:1.1.5-1
ii  procps2:3.3.11-3
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages iceweasel recommends:
ii  gstreamer1.0-libav 1:1.6.3-dmo1
ii  gstreamer1.0-plugins-good  1.6.3-1

Versions of packages iceweasel suggests:
ii  fonts-lmodern  2.004.5-1
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-2.1
ii  libgnomeui-0   2.24.5-3.1
ii  libgssapi-krb5-2   1.13.2+dfsg-4
pn  mozplugger 

-- no debconf information

Bug#813548: RFS: nfft/3.3.0-5

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: nfft
  Version : 3.3.0-5
  Upstream Author : Prof. Dr. Daniel Potts 


* URL :http://www-user.tu-chemnitz.de/~potts/nfft/
* License : GPL-2+
  Section : science

It builds those binary packages:

  libnfft3-2 - library for computing non-uniform Fourier transforms
  libnfft3-dbg - debugging symbols for the NFFT library
  libnfft3-dev - development files for the NFFT library
  libnfft3-doc - documentation for the NFFT library
  libnfft3-double2 - library for computing non-uniform Fourier 
transforms (double prec
  libnfft3-long2 - library for computing non-uniform Fourier transforms 
(long-double
  libnfft3-single2 - library for computing non-uniform Fourier 
transforms (single prec


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


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

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

  dget -x 
http://mentors.debian.net/debian/pool/main/n/nfft/nfft_3.3.0-5.dsc


Changes since the last upload:

  * Upload to unstable.
  * d/control:
- use secure VCS-Git URI.
- add missing Testsuite field.
- cme fix, wrap and sort.
  * d/copyright: correct NFFT3 licensing from GPL-2 to GPL-2+.

Best regards,
Ghislain Vaillant

Bug#660787: joe: hardlocks running in mrxvt; had to kill -9 it and then ctrl-c the console tab

[Josip Rodin]

tag 660787 unreproducible
thanks

On Wed, Feb 22, 2012 at 09:28:28AM +0100, Josip Rodin wrote:
> On Tue, Feb 21, 2012 at 04:00:00PM -0500, cvev...@users.sourceforge.net wrote:
> > Package: joe
> > Version: 3.7-2
> > Severity: important
> > 
> > started in mrxvt tab. 
> > after showing  the help, typed a line then attempted to exit.
> > locked solid, kill would not kill w/o -9
> 
> Can you attach a strace -p to the joe PID at some point in the process?
> Is there anything peculiar in your mrxvt configuration? What is $TERM?

Lacking any debug info whatsoever, I'm afraid I'm going to have to mark this
unreproducible. Can you try with the latest joe 4.1?

-- 
 2. That which causes joy or happiness.

Bug#813349: joe: jstar crashes on startup if old config is present

[Josip Rodin]

forwarded 813349 https://sourceforge.net/p/joe-editor/bugs/341/
thanks

On Mon, Feb 01, 2016 at 12:47:38AM +0100, Adam Borowski wrote:
> Package: joe
> Version: 4.1-2
> Severity: important
> 
> If a ~/.jstarrc from a previous version exists, jstar will segfault on 
> startup.
> This happens even for unmodified configs (ie, a straight copy of
> /etc/joe/jstarrc into ~/.jstarrc).
> 
> Prior versions complained in the presence of an outdated config, but you
> just removed that check (#560182).  But in any case, response to even
> complete garbage should be an error message rather than a segfault.

Thanks for reporting this Adam, I filed it upstream.

-- 
 2. That which causes joy or happiness.

Bug#813474: ITP: libhinawa -- I/O library for IEEE 1394 asynchronous

[HAYASHI Kentaro]

Here is the RFS:

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


> Also, I've sent RFS against bugs.debian.org to find sponsor.

-- 
haya...@clear-code.com

Bug#813546: loop when package is in "Bu" state and one tries to install it

[積丹尼 Dan Jacobson]

Package: aptitude
Version: 0.7.5-3

# aptitude install imagemagick
The following packages will be upgraded:
  imagemagick
The following packages will NOT be UPGRADED:
  libgdal1i  libssl1.0.2{a}  openssl{a}  xorg  xserver-xorg{a}
  xserver-xorg-core{a} (R: xserver-xorg)  xserver-xorg-input-evdev{a}
  xserver-xorg-input-kbd  xserver-xorg-input-mouse
  xserver-xorg-input-synaptics{a} (S: gpointing-device-settings, S: touchfreeze)
  xserver-xorg-input-vmmouse{a}  xserver-xorg-video-all
  xserver-xorg-video-ati{a}  xserver-xorg-video-cirrus{a}
  xserver-xorg-video-fbdev{a}  xserver-xorg-video-intel{a}
  xserver-xorg-video-mach64{a}  xserver-xorg-video-mga{a}
  xserver-xorg-video-neomagic{a}  xserver-xorg-video-nouveau{a}
  xserver-xorg-video-r128{a}  xserver-xorg-video-radeon{a}
  xserver-xorg-video-savage{a}  xserver-xorg-video-sisusb{a}
  xserver-xorg-video-tdfx  xserver-xorg-video-trident{a}
  xserver-xorg-video-vesa{a}  xserver-xorg-video-vmware{a}
1 packages upgraded, 0 newly installed, 0 to remove and 28 not upgraded.
Need to get 0 B/1,454 B of archives. After unpacking 236 kB will be freed.
Do you want to continue? [Y/n/?]
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell 
buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
(Reading database ... 180254 files and directories currently installed.)
Preparing to unpack .../imagemagick_8%3a6.9.2.10+dfsg-2_all.deb ...
dpkg-query: no packages found matching imagemagick:all
dpkg-query: package 'imagemagick' is not installed
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
dpkg-query: package 'imagemagick' is not installed
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.

Repeats until kill -9

# aptitude search ~U
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct 
the problem.
W: Could not lock the cache file; this usually means that dpkg or another apt 
tool is already installing packages.  Opening in read-only mode; any changes 
you make to the states of packages will NOT be preserved!
Bu  imagemagick


Trying again
aptitude install imagemagick

Reading package lists...
Building dependency tree...
Reading state information...
Reading extended state information...
Initializing package states...
Building tag database...
Couldn't find any package whose name or description matched "imaagemagick"
Couldn't find any package whose name or description matched "imaagemagick"
The following packages will NOT be UPGRADED:
  imagemagick{b} (D: imagemagick-6.q16)  libgdal1i  libssl1.0.2{a}
  openssl{a}  xorg  xserver-xorg{a}
  xserver-xorg-core{a} (R: xserver-xorg)  xserver-xorg-input-evdev{a}
  xserver-xorg-input-kbd  xserver-xorg-input-mouse
  xserver-xorg-input-synaptics{a} (S: gpointing-device-settings, S: touchfreeze)
  xserver-xorg-input-vmmouse{a}  xserver-xorg-video-all
  xserver-xorg-video-ati{a}  xserver-xorg-video-cirrus{a}
  xserver-xorg-video-fbdev{a}  xserver-xorg-video-intel{a}
  xserver-xorg-video-mach64{a}  xserver-xorg-video-mga{a}
  xserver-xorg-video-neomagic{a}  xserver-xorg-video-nouveau{a}
  xserver-xorg-video-r128{a}  xserver-xorg-video-radeon{a}
  xserver-xorg-video-savage{a}  xserver-xorg-video-sisusb{a}
  xserver-xorg-video-tdfx  xserver-xorg-video-trident{a}
  xserver-xorg-video-vesa{a}  xserver-xorg-video-vmware{a}
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 29 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
The following packages have unmet dependencies:
 imagemagick : Depends: imagemagick-6.q16 (= 8:6.9.2.10+dfsg-1) but 
8:6.9.2.10+dfsg-2 is installed.
The following actions will resolve these dependencies:

 Remove the following packages:
1) imagemagick



Accept this solution? [Y/n/q/?] The following actions will resolve these 
dependencies:

 Upgrade the following packages:
1) imagemagick [8:6.9.2.10+dfsg-1 (experimental, now) -> 8:6.9.2.10+dfsg-2 (



Accept this solution? [Y/n/q/?] The following packages will be upgraded:
  imagemagick
The following packages will NOT be UPGRADED:
  libgdal1i  libssl1.0.2{a}  openssl{a}  xorg  xserver-xorg{a}
  xserver-xorg-core{a} (R: xserver-xorg)  xserver-xorg-input-evdev{a}
  xserver-xorg-input-kbd  xserver-xorg-input-mouse
  xserver-xorg-input-synaptics{a} (S: gpointing-device-settings, S: touchfreeze)
  xserver-xorg-input-vmmouse{a}  xserver-xorg-video-all
  xserver-xorg-video-ati{a}  xserver-xorg-video-cirrus{a}
  xserver-xorg-video-fbdev{a}  xserver-xorg-video-intel{a}
  xserver-xorg-video-mach64{a}  xserver-xorg-video-mga{a}
  xserver-xorg-video-neomagic{a}  xserver-xorg-video-nouveau{a}
  xserver-xorg-video-r128{a}  xserver-xorg-video-radeon{a}
  xserver-xorg-video-savage{a}  xserver-xorg-video-

Bug#813538: please speed up checking multiple build profiles

[Helmut Grohne]

Package: dose-builddebcheck
Severity: wishlist
User: helm...@debian.org
Usertags: rebootstrap

Hi dose3 developers,

By now, rebootstrap[1] is a heavy user of dose-builddebcheck and
invoking it well over 50 times per run. This starts to manifest in the
time it takes to run rebootstrap. Thus far I am always passing the same
set of build profiles to dose, but in future I would like to ask it for
building some packages with different profiles than others. Of course, I
can simply run dose-builddebcheck for each profile combination, but each
of those invocations incurs the parsing of Packages and Sources and thus
increases the time to run rebootstrap.

For example, I would like to be able to ask dose-builddebcheck whether
util-linux can be built under stage1 or tar can be built with no
profiles.

Johannes suggested splitting the parsing phase into a separate step,
such that multiple queries could be made against the same Packages file
without incurring the cost of parsing multiple times.

Helmut

[1] https://wiki.debian.org/HelmutGrohne/rebootstrap

Bug#813543: vlc: doesn't output any sound

[Vincent Lefevre]

Control: reassign -1 pulseaudio 7.1-2
Control: severity -1 important
Control: retitle -1 pulseaudio: [alsa-sink-ALC3228 Analog] alsa-sink.c: Error 
opening PCM device front:0: Invalid argument

Firefox also had problems.

After logging out and logging in, vlc works again. So, it seems to
be a problem with the pulseaudio daemon. Reassigning.

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

Bug#813543: vlc: doesn't output any sound

[Vincent Lefevre]

Control: found -1 2.2.1-5

On 2016-02-03 00:03:48 +0100, Vincent Lefevre wrote:
> Package: src:vlc
> Version: 2.2.2-1
> Severity: grave
> Justification: renders package unusable
> 
> After the upgrade to 2.2.2, VLC no longer outputs any sound. This is
> specific to VLC as there is no such problem with ogg123, for instance.

Downgrading the VLC packages to 2.2.1-5+b3 doesn't solve the problem.
In the logs, I can find errors like:

Feb 03 00:28:11 zira pulseaudio[1645]: [alsa-sink-ALC3228 Analog] alsa-sink.c: 
Error opening PCM device front:0: Invalid argument
Feb 03 00:28:11 zira pulseaudio[1645]: [alsa-sink-ALC3228 Analog] alsa-sink.c: 
Error opening PCM device front:0: Invalid argument

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

Bug#810748: systemd does not mount /usr in initramfs, breaking split /usr

[Michael Biebl]

Am 02.02.2016 um 22:27 schrieb Michael Biebl:
> Hi Nis
> 
> On Tue, 19 Jan 2016 22:52:57 +0100 Nis Martensen 
> wrote:
>> Control: found -1 228-4
>>
>> Attached a version of the patch that should work for testing/unstable.
>> Again intended as a replacement for the existing patch.
> 
> I've looked a bit closer at your patch, and it looks fine.
> Not generating the systemd-fsck@ instance when the flag file exists,
> looks like a proper solution to this issue.
> 
> I gave the patch a quick test and it seems to work with both dracut and
> initramfs-tools. There are still some (new) issues with a separate /usr
> [1], but that happens with both initramfs-tools and dracut.
> 
> So I think the patch can go in as is.

Fwiw, I think the fix is important enough that it should go into jessie.
Installing dracut should not render a system unbootable.

I'll cherry-pick the fix for our jessie branch once the patch had a bit
of testing in unstable.


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



signature.asc
Description: OpenPGP digital signature

Bug#813537: tails-installer: tails installer fails with extlinux error

[Stefani Banerian]

Package: tails-installer
Version: 4.4.6+dfsg-1~bpo8+1
Severity: normal

Dear Maintainer,


In attempting to run tails installer an error message about missing extlinux 
was encountered.
It is true that this package was not installed on the system.

I did not find a "depends" of extlinux package in the "control" file.
Perhaps extlinux should be required?



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

Kernel: Linux 3.16.0-4-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 tails-installer depends on:
ii  gdisk  0.8.10-2
ii  genisoimage9:1.1.11-3
ii  gir1.2-glib-2.01.42.0-2.2
ii  gir1.2-gtk-3.0 3.14.5-1+deb8u1
ii  gir1.2-udisks-2.0  2.1.3-5
ii  mtools 4.0.18-2
ii  p7zip-full 9.20.1~dfsg.1-4.1+deb8u1
ii  policykit-10.105-8
ii  python 2.7.9-1
ii  python-configobj   5.0.6-1
ii  python-gi  3.14.0-1
ii  python-urlgrabber  3.9.1-4.1
ii  syslinux   3:6.03+dfsg-5+deb8u1

tails-installer recommends no packages.

tails-installer suggests no packages.

-- no debconf information

Bug#813078: git-annex: FTBFS: libgnutls-deb0.so.28: cannot open shared object file: No such file or directory

[peter green]

On 02/02/16 05:37, peter green wrote:

found 813078 5.20150731-1
thanks

Sorry I missed the first sentance of my explanation of the found 
command, the paragraph was meant to say.


In raspbian stretch we have seen this same issue with a binnmu of 
5.20150731-1. Debian reproducability tests in testing are not showing it 
right now, but I strongly suspect that is because some other package 
hasn't been rebuilt yet, not because the underlying issue is not there.




I'm going to try scheduling a binnmu of haskell-network-protocol-xmpp 
in raspbian stretch and see if that fixes things.

I have done this and git-annex rebuilt

I guess the question now is do we just ask the release team to binnmu 
haskell-network-protocol-xmpp in Debian or does someone want to 
investigate and fix the missing dependencies.

Bug#813539: [Pkg-privacy-maintainers] Bug#813539: tails-installer: tails installer fails to sense usb stick

[S. Banerian]

On 02/02/2016 03:14 PM, intrigeri wrote:
> Control: tag -1 + moreinfo
> 
> Hi,
> 
> Stefani Banerian wrote (02 Feb 2016 22:20:31 GMT) :
>> in trying to use the gui, the usb stick was never displayed.
> 
>> I did run the installer from command line:
>> /usr/lib/tails-installer/tails-installer  -v -f /dev/sdb 
> 
> We don't support running the installer this way (not all combinations
> of options result in sane behaviour), that's why this program is not
> in the $PATH.
> 
> Can you please try to reproduce this problem using
> tails-installer-launcher?
> 
> And, still curious: any specific reason why are you picking your own
> set of command-line options? If you have a use case that is not
> addressed by tails-installer-launcher, I'm curious :)
> 
> Cheers!

well, whenever I try the tails-installer-launcher, it never shows the
usb stick.

that's why i tried CLI, to look for more debug information!  :)
If there is a way to use the launcher, and get the installer to sense
the usb stick, that would be nice

-- 
Stefani Banerian
206-598-0302
gpg key 6642E7EE
fingerprint = BD13 875D 2D03 5E1D 1E3B  8BF7 F4B8 63AD 6642 E7EE

Bug#813468: boinc-client: Some https connections fail due to Debian Jessie openssl and ca-certificate interactions

[Christian Beer]

On 02.02.2016 22:04, Tim Small wrote:
>> On Tue, Feb 02, 2016 at 03:04:41PM +0100, Christian Beer wrote:
>> > I will also reference the workaround we advise to "downgrade" the
>> > ca-certificates package:
>> > https://einstein.phys.uwm.edu/forum_thread.php?id=11760&postid=151305
> I think this is the worst solution from a security point of view, as it
> would prevent systems from revoking known-compromised CA certificates,
> should any become known (this has happened multiple times in the past)
> and be rolled out in future Debian security updates.
>
> It is also a system-wide change impacting the security of many other
> pieces of software (including ones which aren't impacted by the openssl
> bug, because they use different certificate chain verification code),
> so until Debian has a fix for this, I think I'd prefer to advise
> per-application workarounds, such as the one reference in the original
> report.

You are right that this impacts security but my goal was to provide a
short non-tech workaround so our volunteers do not get disconnected from
our servers or can reestablish the connection. Telling them to download
a certificate and cat'ing it to a file is also not a good and secure
solution. They would also need to remember and repeat this procedure
every time boinc-client gets updated.

I thought that there could be a quick fix to ca-certificates by
reintroducing cross-signed certificates that would benefit all users.
Instead I now read that it can take some more time to get this fixed.
For the affected BOINC projects it would be now the best solution to add
the "Thawte Premium Server CA" to the ca-bundle.crt shipped with
boinc-client. I'm going to test if this is used on Debian right now, it
normally is only used on Windows. But then we have to get this update
into Jessie too.

Regards
Christian

Bug#813532: transition: libjsoncpp

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 02/02/16 22:04, Peter Spiess-Knafl wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> I would like to start the transition for libjsoncpp.
> 
> Its been on experimental for quite a while now, until I could test all the
> rdepends.
> 
> The following rdepends have been successfully tested:
> 
> cmake
> bamtools
> dcmtkpp
> kodi-pvr-argustv
> lgogdownloader
> libjson-rpc-cpp
> llvm-toolchain-3.7
> minetest
> orthanc
> paraview
> springlobby
> sysdig
> vtk6
> 
> The following rdepends have a FTBFS problem:
> 
> ginkgocadx - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805170

Go ahead.

Cheers,
Emilio

Bug#813164: coreutils: ls suddenly quotes output

[Jamie Heilman]

This behavior needs to be reverted.  There are too many assumptions
being made, the quoting used is shell-specific, and not universally
supported.  For example, consider a file who's name contains a tab,
like "ab".

$ ls
'a'$'\t''b'

OK, so that syntax is supported by bash and zsh, so if you're using
one of those shells, maybe you know what it means, and you can cut and
paste that and make use of it, but in csh or dash, it doesn't mean the
same thing.

Bug#772131: systemd: Suspending by closing the lid opens Polkit dialogue after resume

[Michael Biebl]

Control: reassign -1 kdelibs-bin
Control: retitle -1 kde does not properly cope with logind being restarted

On Mon, 08 Dec 2014 21:51:24 +0100 Ralf Jung  wrote:
> Hi,
> 
> > postinst has:
> > 
> > if [ -n "$2" ]; then
> > systemctl daemon-reexec || true
> > systemctl try-restart systemd-logind.service || true
> > systemctl try-restart systemd-networkd.service || true
> > systemctl try-restart systemd-resolved.service || true
> > systemctl try-restart systemd-timesyncd.service || true
> > fi
> > 
> > 
> > Can you run those commands step-by-step and check if a specific restart
> > is able to trigger the issue?
> > Might be, that some KDE program doesn't cope with the restart of
> > systemd-logind and doesn't properly reconnect to the logind D-Bus service.
> 
> As you guessed: After the systemd-logind restart, suspend is broken.
> 
> It was my understanding that D-Bus operates on a per-call basis and
> there is no such thing as a "connection" between a d-bus client and a
> service it's accessing (there's of course a "connection" between each
> peer and the bus daemon, but that's an implementation detail) - but that
> may just as well be wrong.
> 

I'm going to re-assign this to kdelibs-bin, the package shipping kdeinit4,
which you mentioned in your initial message.
The KDE maintainers can then handle it from there.
It would probably help if you posted the KDE versions you use.

Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#813542: transition: nvidia-cuda-toolkit

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 02/02/16 23:58, Andreas Beckmann wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> Forwarded: 
> https://release.debian.org/transitions/html/auto-nvidia-cuda-toolkit.html
> 
> I'd like to move nvidia-cuda-toolkit 7.0 from experimental to unstable
> to make room for working on 7.5.
> 
> The rdepends have been tested with the new toolkit.
> Since they cannot be autobuilt (B-D in non-free) this will require
> maintainer-provided binNMUs (or sourceful uploads), we are ready to do
> this.
> 
> * boinc is a false positive, it depends on a long list of cuda
>   alternatives, no action required for 7.0
> * starpu-contrib overlaps with the openmpi transition, but would require a
>   manual binNMU/upload anyway for that
> * eztrace-contrib (sid-only) may have to wait for 7.5.
> * hwloc-contrib, pycuda are ready
> 
> (just verified again myself that hwloc-contrib, pycuda, starpu-contrib
> successfully build with nvidia-cuda-toolkit (>= 7) (and openmpi 1.10.x))
> 
> There may be a few RMs be needed in sid since i386 is no longer
> supported, but most i386 rdepends binaries should be gone already.

Ack.

Cheers,
Emilio

Bug#813535: socat: Socat security advisory 8: stack overflow vulnerability in parser

[Salvatore Bonaccorso]

Source: socat
Version: 1.7.1.3-1
Severity: important
Tags: security upstream fixed-upstream

Hi

See: http://www.dest-unreach.org/socat/contrib/socat-secadv8.html for
details.

Regards,
Salvatore

Bug#813536: socat: Socat security advisory 7: Bad DH p paramenter in OpenSSL

[Salvatore Bonaccorso]

Source: socat
Version: 1.7.3.0-1
Severity: important
Tags: security upstream fixed-upstream

Hi

See http://www.dest-unreach.org/socat/contrib/socat-secadv7.html for
details.

Regards,
Salvatore

Bug#813471: network access to the loopback device should be allowed

[Guillem Jover]

Hi!

On Tue, 2016-02-02 at 20:46:03 +0900, Osamu Aoki wrote:
> Package: debian-policy
> Severity: normal
> 
> Bug #770016 "Clarify network access for building packages in main"
> was about not downloading files via network.  This created new lines in
> 4.9 as:
> 
> | For packages in the main archive, no required targets may attempt
> | network access.
> 
> This is too restrictive.
> 
> The build target of devscripts has several tests testing http acess to
> the http server on the loopback device.
> 
> But the above new policy lines may be considered to prohibit this.
> 
> I thought the this should be more like:
> 
> | For packages in the main archive, no required targets may attempt
> | network access except for the access to the loopback device.

> I understand downloading from Debian or non-Debian web site is bad for
> buildd but network operation to the loopback device (like http access)
> should be OK.

This is probably too restrictive too. It would not allow local access
through TAP device or other similar things. It might be better to just
say something like:

| For packages in the main archive, no required targets may attempt
| network access outside the current machine.

or something along those lines.

Thanks,
Guillem

Bug#813545: vlc: freeze followed by segmentation fault after closing the window

[Vincent Lefevre]

Package: src:vlc
Version: 2.2.2-1
Severity: important

After I close the window, VLC froze then crashed (segmentation fault).
I could reproduce this problem another time, but that's all. This never
occurred with previous versions.

Program terminated with signal SIGSEGV, Segmentation fault.
#0  __strcmp_sse2_unaligned ()
at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:30
30  ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S: No such file or 
directory.
[Current thread is 1 (Thread 0x7f07a02e1700 (LWP 15208))]

The backtrace:

Thread 2 (Thread 0x7f07cf935880 (LWP 15092)):
#0  0x7f07cf38d8cf in pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f07ceb7fe95 in vlc_cond_wait (p_condvar=, 
p_mutex=) at posix/thread.c:387
#2  0x7f07ceaff25b in playlist_fetcher_Delete (p_fetcher=0x244e3c0) at 
playlist/fetcher.c:166
p_next = 
album = 
#3  0x7f07ceb033c7 in playlist_preparser_Delete (p_preparser=0x244e330) at 
playlist/preparser.c:120
#4  0x7f07ceaebcea in libvlc_InternalCleanup (p_libvlc=0x2439ee8) at 
libvlc.c:546
#5  0x7f07cf5a5b6e in libvlc_release () at /usr/lib/libvlc.so.5
#6  0x00401396 in  ()
#7  0x7f07cedf9870 in __libc_start_main (main=0x401190, argc=1, 
argv=0x7ffe4950f0f8, init=, fini=, 
rtld_fini=, stack_end=0x7ffe4950f0e8) at libc-start.c:291
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 7486525756343416823, 
4199744, 140730128462064, 0, 0, -7486696018106812425, -7355813339458865161}, 
mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x401bc0, 0x7ffe4950f0f8}, data 
= {prev = 0x0, cleanup = 0x0, canceltype = 4201408}}}
not_first_call = 
#8  0x00401569 in  ()

Thread 1 (Thread 0x7f07a02e1700 (LWP 15208)):
#0  0x7f07cee6935e in __strcmp_sse2_unaligned () at 
../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:30
#1  0x7f07ceebecf0 in __tfind (key=key@entry=0x7f07a02e0980, 
vrootp=vrootp@entry=0x2521a08, compar=compar@entry=0x7f07ceb76700 ) at 
tsearch.c:320
root = 0x7f07cf177c58 
r = 
rootp = 
#2  0x7f07cebb in var_SetChecked (psz_name=0x7f07ceba1c0f 
"item-change", obj=0x2521a98) at misc/variables.c:154
priv = 0x2521a00
pp_var = 
i_ret = 0
oldval = {i_int = 0, b_bool = false, f_float = 0, psz_string = 0x0, 
p_address = 0x0, p_object = 0x0, p_list = 0x0, i_time = 0, coords = {x = 0, y = 
0}}
p_priv = 0x2521a00
#3  0x7f07cebb in var_SetChecked (p_this=0x2521a98, 
psz_name=psz_name@entry=0x7f07ceba1c0f "item-change", 
expected_type=expected_type@entry=112, val=...) at misc/variables.c:712
i_ret = 0
oldval = {i_int = 0, b_bool = false, f_float = 0, psz_string = 0x0, 
p_address = 0x0, p_object = 0x0, p_list = 0x0, i_time = 0, coords = {x = 0, y = 
0}}
p_priv = 0x2521a00
#4  0x7f07ceb05a7c in input_item_changed (ptr=, 
psz_name=0x7f07ceba1c0f "item-change", p_obj=) at 
../include/vlc_variables.h:287
p_item = 
#5  0x7f07ceb05a7c in input_item_changed (p_event=, 
user_data=) at playlist/item.c:180
p_item = 
#6  0x7f07ceb718ea in vlc_event_send (p_em=p_em@entry=0x7f0788047758, 
p_event=p_event@entry=0x7f07a02e0a40) at misc/events.c:237
listeners_group = 
listener = 
array_of_cached_listeners = 0x7f0785813ec0
cached_listener = 0x7f0785813ec0
i = 
i_cached_listeners = 
#7  0x7f07ceb0b2a6 in input_item_SetMeta (p_i=0x7f07880476d0, 
meta_type=vlc_meta_ArtworkURL, psz_val=0x7f0785813df8 
"http://coverartarchive.org/release/c3dd54fa-7eb7-464f-92da-e356d6c3776a/front-500";)
 at input/item.c:143
event = {type = vlc_InputItemMetaChanged, p_obj = 0x7f07880476d0, u = 
{input_state_changed = {new_state = 16}, input_selected_stream_changed = 
{unused = 0x7f070010}, input_item_meta_changed = {meta_type = 
vlc_meta_ArtworkURL}, input_item_subitem_added = {p_new_child = 
0x7f070010}, input_item_subitem_tree_added = {p_root = 0x7f070010}, 
input_item_duration_changed = {new_duration = 139668041498640}, 
input_item_preparsed_changed = {new_status = 16}, input_item_name_changed = 
{new_name = 0x7f070010 }, input_item_info_changed = {unused = 0x7f070010}, 
input_item_error_when_reading_changed = {new_value = 16}, 
services_discovery_item_added = {p_new_item = 0x7f070010, psz_category = 
0x7f07be884b8e "\205\300\017\205\062\001"}, services_discovery_item_removed = 
{p_item = 0x7f070010}, services_discovery_started = {unused = 
0x7f070010}, services_discovery_ended = {unused = 0x7f070010}, 
addon_generic_event = {p_entry = 0x7f070010}}}
#8  0x7f07be884f32 in  () at /usr/lib/vlc/plugins/lua/liblua_plugin.so
#9  0x7f07be887850 in  () at /usr/lib/vlc/plugins/lua/liblua_plugin.so
#10 0x7f07be8852c5 in  () at /usr/lib/vlc/plugins/lua/liblua_plugin.so
#11 0x7f07ceb62505 in module_load (obj=obj@entry=0x7f07840012a8, 
m=m@entry=0

Bug#813128: Fwd: Bug#813128: transition: openmpi

[Michael Banck]

On Wed, Feb 03, 2016 at 12:09:18AM +0100, Michael Banck wrote:
> On Tue, Feb 02, 2016 at 12:19:10AM +0100, Matthias Klose wrote:
> > On 01.02.2016 15:38, Emilio Pozuelo Monfort wrote:
> > >On 01/02/16 12:41, Alastair McKinstry wrote:
> > >>
> > >>The upload of openmpi1.10 triggered an auto-openmpi transition, as
> > >>expected and wanted.
> > >>The rest, is premature.
> > >
> > >The problem is that you uploaded the package directly to unstable, without
> > >asking for a transition slot and without fixing those problems you mention
> > >beforehand. It'd have been better to upload it to experimental until 
> > >things were
> > >ready.
> > >
> > >Since that has already happened, it'd be good to know what packages build 
> > >fine
> > >against the new openmpi and which ones don't.
> > 
> > fyi, I was surprised as well, tried to go forward, and ended up with
> > http://people.canonical.com/~ubuntu-archive/transitions/html/openmpi.html
> > (only tried dependency level 1 to build).
> 
> Thanks!
> 
> I look at some of mine and they seem to FTBFS due to scalapack on longer
> being installable, which in turn is due to blacs-mpi FTBFSing:
> 
> /usr/bin/ld: cannot find -lmpi_f77
> 
> That library has vanished from libopenmpi-dev, Alastair, was that
> intentional, and if so, how is Fortran linking supposed to work now?
> 
> I removed that library from blacs-mpi link line and it built fine, but I
> am not sure this is the right fix.

Nevermind, I saw Alastair has filed a patch (#813490). As blacs-mpi has
been NMU'd before and looks rather central, I suggest to zero-day NMU
this, unless somebody objects.


Michael

Bug#813541: nvidia-graphics-drivers: Huge problems 'upgrading' to legacy version

[Andreas Beckmann]

Hi Manuel,

On 2016-02-02 23:56, Manuel Bilderbeek wrote:
> I did my daily testing dist-upgrade just now, and I noticed I got a version of
> the nvidia driver that is not going to work with my old GeForce 9600. I got a
> nice pop up that the driver is not going to work, so I chose 'No', to not
> install it.
> 
> But afterwards, many packages of 352 were actually installed after all.
> 
> I tried to install all the proper 340xx legacy packages, but as they didn't
> conflict with the normal packages, all the normal stuff was also still
> installed. Apparently that gave a lot of problems, because after booting I 
> only
> got a very blinky text console and no X.

The current and legacy drivers are intended to be coinstallable.

To switch to the -legacy driver while (parts of) -current is still
installed, you could just use the new command

  update-glx --config nvidia

We should probably advertise this more on the legacy warning screen.

> After manually removing all packages of the 352 version and changing 'nvidia'
> in /etc/modules-load.d/nvidia.conf to 'nvidia-legacy-340xx' I finally got a
> working X11 again
> 
> Why did I have to do all that manual work to get X11 working again?
> Which package owns that nvidia.conf anyway? I couldn't find it...

That depends ... on the setting of the alternatives. :-)


Andreas

Bug#788963: quota: Failed to start Check And Enable File System Quotas on Debian Jessie

[Kepi]

Confirmed, same problem our jessie servers. We are not alone according
to quick google search.

-- 
Kepi


signature.asc
Description: PGP signature

Bug#813539: [Pkg-privacy-maintainers] Bug#813539: tails-installer: tails installer fails to sense usb stick

[intrigeri]

Control: tag -1 + moreinfo

Hi,

Stefani Banerian wrote (02 Feb 2016 22:20:31 GMT) :
> in trying to use the gui, the usb stick was never displayed.

> I did run the installer from command line:
> /usr/lib/tails-installer/tails-installer  -v -f /dev/sdb 

We don't support running the installer this way (not all combinations
of options result in sane behaviour), that's why this program is not
in the $PATH.

Can you please try to reproduce this problem using
tails-installer-launcher?

And, still curious: any specific reason why are you picking your own
set of command-line options? If you have a use case that is not
addressed by tails-installer-launcher, I'm curious :)

Cheers!

Bug#813544: prometheus-node-exporter: cannot run as root

[Anton T]

Package: prometheus-node-exporter
Version: 0.12.0+ds-2
Severity: important
Tags: patch

Dear Maintainer,

It seems that setting USER=root in /etc/default/prometheus-node-exporter
breaks the init script because HELPER_ARGS is defined before
/etc/default/$NAME is included.

This patch fixes the issue:
--- /etc/init.d/prometheus-node-exporter.orig   2016-02-02 23:06:36.0 
+
+++ /etc/init.d/prometheus-node-exporter2016-02-02 23:07:06.0 
+
@@ -23,12 +23,12 @@
 PIDFILE=/var/run/prometheus/prometheus-node-exporter.pid
 LOGFILE=/var/log/prometheus/prometheus-node-exporter.log

-HELPER=/usr/bin/daemon
-HELPER_ARGS="--name=$NAME --output=$LOGFILE --pidfile=$PIDFILE --user=$USER"
-
 ARGS=""
 [ -r /etc/default/$NAME ] && . /etc/default/$NAME

+HELPER=/usr/bin/daemon
+HELPER_ARGS="--name=$NAME --output=$LOGFILE --pidfile=$PIDFILE --user=$USER"
+
 do_start_prepare()
 {
 mkdir -p `dirname $PIDFILE` || true


Kind regards,
Anton

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

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 prometheus-node-exporter depends on:
ii  daemon  0.6.4-1
ii  libc6   2.19-18+deb8u1

prometheus-node-exporter recommends no packages.

prometheus-node-exporter suggests no packages.

-- debconf-show failed

Bug#813128: Fwd: Bug#813128: transition: openmpi

[Michael Banck]

On Tue, Feb 02, 2016 at 12:19:10AM +0100, Matthias Klose wrote:
> On 01.02.2016 15:38, Emilio Pozuelo Monfort wrote:
> >On 01/02/16 12:41, Alastair McKinstry wrote:
> >>
> >>The upload of openmpi1.10 triggered an auto-openmpi transition, as
> >>expected and wanted.
> >>The rest, is premature.
> >
> >The problem is that you uploaded the package directly to unstable, without
> >asking for a transition slot and without fixing those problems you mention
> >beforehand. It'd have been better to upload it to experimental until things 
> >were
> >ready.
> >
> >Since that has already happened, it'd be good to know what packages build 
> >fine
> >against the new openmpi and which ones don't.
> 
> fyi, I was surprised as well, tried to go forward, and ended up with
> http://people.canonical.com/~ubuntu-archive/transitions/html/openmpi.html
> (only tried dependency level 1 to build).

Thanks!

I look at some of mine and they seem to FTBFS due to scalapack on longer
being installable, which in turn is due to blacs-mpi FTBFSing:

/usr/bin/ld: cannot find -lmpi_f77

That library has vanished from libopenmpi-dev, Alastair, was that
intentional, and if so, how is Fortran linking supposed to work now?

I removed that library from blacs-mpi link line and it built fine, but I
am not sure this is the right fix.


Michael

Bug#813232: How are bugs #741964 and #813232 related ?

[jhcha54008]

Hi,

Moving setup_devices at the end of first_stage()
would solve partially #741964 
(debootstrap: --variant=fakechroot and --foreign) 
too.

Regards,
JH Chatenet 

Bug#813533: inosync: [PATCH] So someone can -c configfile a dot file

[Eric Côté]

Package: inosync
Version: 0.2.1-1
Severity: normal
Tags: patch

line 134:
add:

  if configfile.startswith("."):
 configfile = configfile.strip(".")

right after the

  if configfile.endswith(".py"):


Thanks,
Eric


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

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

Versions of packages inosync depends on:
ii  python2.7.11-1
ii  python-pyinotify  0.9.5-1
ii  rsync 3.1.1-3

inosync recommends no packages.

inosync suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/bin/inosync (from inosync package)

Bug#813463: janest-core-extended: FTBFS: E: Failure("Command ''/usr/bin/ocamlbuild' src/libcore_extended_stubs.a src/dllcore_extended_stubs.so src/core_extended.cma src/core_extended.cmxa src/core_ext

[Hilko Bengen]

Control: reassign -1 janest-core

* Chris Lamb:

>   make[1]: Leaving directory 
> '/home/lamby/temp/cdt.20160202094953.sKIF2YheZX/janest-core-extended-113.00.00'
>  debian/rules override_dh_auto_build
>   make[1]: Entering directory 
> '/home/lamby/temp/cdt.20160202094953.sKIF2YheZX/janest-core-extended-113.00.00'
>   ocaml setup.ml -build
>   W: Cannot find source file matching module 'selector_lib' in library 
> selector_lib
>   W: Cannot find source file matching module 'core_extended' in library 
> core_extended
>   ocamlfind ocamlopt unix.cmxa -I /usr/lib/ocaml/ocamlbuild 
> /usr/lib/ocaml/ocamlbuild/ocamlbuildlib.cmxa -linkpkg myocamlbuild.ml 
> /usr/lib/ocaml/ocamlbuild/ocamlbuild.cmx -o myocamlbuild
>   /usr/bin/ocamlfind ocamlc -g -I src -package core -thread -ccopt -Isrc -c 
> src/extended_int_stubs.c
>   + /usr/bin/ocamlfind ocamlc -g -I src -package core -thread -ccopt -Isrc -c 
> src/extended_int_stubs.c
>   ocamlfind: Package `enumerate' not found - required by `core'

So, libcore-ocaml-dev does not declare dependencies on enumerate, this
looks similar to #813439 (missing dependency to
libcustom-printf-camlp4-dev).

This may well be a toolchain-related problem. Investigating...

Cheers,
-Hilko

Bug#813468: boinc-client: Some https connections fail due to Debian Jessie openssl and ca-certificate interactions

[Kurt Roeckx]

On Tue, Feb 02, 2016 at 08:15:03PM +, Tim Small wrote:
> It would seem that the best fix would be to pull this upstream code
> into an upcoming Jessie point release, because as this gives the least
> surprising / least broken behaviour, and is in-line the the behaviour of
> most (all?) modern SSL/TLS implementations.  

This is one of those changes that I've been trying to get into the
stable point release for a long time now.


Kurt

Bug#813543: vlc: doesn't output any sound

[Vincent Lefevre]

Package: src:vlc
Version: 2.2.2-1
Severity: grave
Justification: renders package unusable

After the upgrade to 2.2.2, VLC no longer outputs any sound. This is
specific to VLC as there is no such problem with ogg123, for instance.

I suspect a major problem with VLC 2.2.2 since it also segfaults. I'm
going to report another bug about this (I don't know whether this is
related).

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, 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 vlc depends on:
ii  dpkg1.18.4
ii  fonts-freefont-ttf  20120503-4
ii  libaa1  1.4p5-44
ii  libavcodec-ffmpeg56 7:2.8.5-1+b1
ii  libavutil-ffmpeg54  7:2.8.5-1+b1
ii  libc6   2.21-7
ii  libcaca00.99.beta19-2+b1
ii  libcairo2   1.14.6-1
ii  libegl1-mesa [libegl1-x11]  11.1.1-2
ii  libfreerdp-client1.11.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreerdp-core1.1  1.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreerdp-gdi1.1   1.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreetype62.6.1-0.1
ii  libfribidi0 0.19.7-1
ii  libgcc1 1:5.3.1-7
ii  libgl1-mesa-glx [libgl1]11.1.1-2
ii  libgles1-mesa [libgles1]11.1.1-2
ii  libgles2-mesa [libgles2]11.1.1-2
ii  libglib2.0-02.46.2-3
ii  libpulse0   7.1-2
ii  libqt5core5a5.5.1+dfsg-13
ii  libqt5gui5  5.5.1+dfsg-13
ii  libqt5widgets5  5.5.1+dfsg-13
ii  libqt5x11extras55.5.1-3
ii  librsvg2-2  2.40.13-2
ii  libsdl-image1.2 1.2.12-5+b5
ii  libsdl1.2debian 1.2.15-12
ii  libstdc++6  5.3.1-7
ii  libva-drm1  1.6.2-1
ii  libva-x11-1 1.6.2-1
ii  libva1  1.6.2-1
ii  libvlccore8 2.2.2-1
ii  libvncclient1   0.9.10+dfsg-3+b1
ii  libx11-62:1.6.3-1
ii  libxcb-composite0   1.11.1-1
ii  libxcb-keysyms1 0.4.0-1
ii  libxcb-randr0   1.11.1-1
ii  libxcb-shm0 1.11.1-1
ii  libxcb-xv0  1.11.1-1
ii  libxcb1 1.11.1-1
ii  libxext62:1.3.3-1
ii  libxi6  2:1.7.6-1
ii  libxinerama12:1.1.3-1+b1
ii  libxpm4 1:3.5.11-1+b1
ii  vlc-nox 2.2.2-1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages vlc recommends:
ii  vlc-plugin-notify  2.2.2-1
ii  vlc-plugin-samba   2.2.2-1
ii  xdg-utils  1.1.1-1

vlc suggests no packages.

Versions of packages vlc-nox depends on:
ii  dpkg   1.18.4
ii  liba52-0.7.4   0.7.4-18
ii  libasound2 1.1.0-1
ii  libass50.13.1-1
ii  libavahi-client3   0.6.32~rc+dfsg-1
ii  libavahi-common3   0.6.32~rc+dfsg-1
ii  libavc1394-0   0.5.4-2
ii  libavcodec-ffmpeg567:2.8.5-1+b1
ii  libavformat-ffmpeg56   7:2.8.5-1+b1
ii  libavutil-ffmpeg54 7:2.8.5-1+b1
ii  libbasicusageenvironment1  2016.01.29-2
ii  libbluray1 1:0.9.2-2
ii  libc6  2.21-7
ii  libcddb2   1.3.2-5
ii  libcdio13  0.83-4.2+b1
ii  libchromaprint01.2-2
ii  libcrystalhd3  1:0.0~git20110715.fdd2f19-11+b1
ii  libdbus-1-31.10.6-1
ii  libdc1394-22   2.2.3-1
ii  libdca00.0.5-7
ii  libdirectfb-1.2-9  1.2.10.0-5.1
ii  libdvbpsi101.3.0-4
ii  libdvdnav4 5.0.3-1
ii  libdvdread45.0.3-1
ii  libebml4v5 1.3.3-1
ii  libfaad2   2.8.0~cvs20150510-1
ii  libflac8   1.3.1-4
ii  libfontconfig1 2.11.0-6.3
ii  libfreetype6   2.6.1-0.1
ii  libfribidi00.19.7-1
ii  libgcc11:5.3.1-7
ii  libgcrypt201.6.4-5
ii  libgnutls303.4.8-3
ii  libgpg-error0  1.21-1
ii  libgroupsock8  2016.01.29-2
ii  libjpeg62-turbo1:1.4.2-2
ii  libkate1   0.4.1-5
ii  liblircclient0 0.9.0~pre1-1.2
ii  liblivemedia50 2016.01.29-2
ii  liblua5.2-05.2.4-1
ii  libmad00.15.1b-8
ii  libmatroska6v5 1.4.4-1
ii  libmodplug11:0.8.8.5-2
ii  libmpcdec6 2:0.1~r475-1
ii  libmpeg2-4 0.5.1-7
ii  libmtp91.1.10-2
ii  

Bug#811024: jessie-pu: package imagemagick/8:6.8.9.9-5

[Vincent Fourmond]

  Dear Adam,

On Sun, Jan 31, 2016 at 7:19 PM, Adam D. Barratt 
wrote:

> Control: tags -1 + confirmed
>
> > Essentially, the upload I'm proposing (debdiff to stable attached)
> > makes stable and unstable identical, since there were only security
> > fixes involved (the bulk of the work is happening in experimental, but
> > there are transitions involved, so it's not very fast...). Is that OK
> > for an upload to jpu ?
>
> The no-op changes to the patches you haven't changed (i.e. the first 56)
> are rather noisy.
>

  I'm sorry, this is one of the current shortcomings of gitpkg, which we
find quite comfortable otherwise to deal with such a complex package.


> Some of the new patches also appear to include unrelated changes; for
> instance:
>
> +Subject: [PATCH] Fix PixelColor off by one on i386
> [...]
> +-"XmlMissingElement", ", slot \"%s\"", slot);
> ++"XmlMissingElement",", slot \"%s\"",slot);
>

  These are cosmetic fixes that come from the upstream patches also fixing
the security issues, we didn't feel like editing upstream commits.


> Assuming that the resulting package has been tested on Jessie, please go
> ahead.
>

  Yep, I've just checked it works fine, I'm uploading right away.

  Thanks !

  Vincent

Bug#792880: openvpn does not start

[Diego Fernández Durán]

Hi,

I confirm that after a reboot OpenVPN starts correctly without
modifying /etc/default/openvpn

Thanks.

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

Bug#813542: transition: nvidia-cuda-toolkit

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Forwarded: 
https://release.debian.org/transitions/html/auto-nvidia-cuda-toolkit.html

I'd like to move nvidia-cuda-toolkit 7.0 from experimental to unstable
to make room for working on 7.5.

The rdepends have been tested with the new toolkit.
Since they cannot be autobuilt (B-D in non-free) this will require
maintainer-provided binNMUs (or sourceful uploads), we are ready to do
this.

* boinc is a false positive, it depends on a long list of cuda
  alternatives, no action required for 7.0
* starpu-contrib overlaps with the openmpi transition, but would require a
  manual binNMU/upload anyway for that
* eztrace-contrib (sid-only) may have to wait for 7.5.
* hwloc-contrib, pycuda are ready

(just verified again myself that hwloc-contrib, pycuda, starpu-contrib
successfully build with nvidia-cuda-toolkit (>= 7) (and openmpi 1.10.x))

There may be a few RMs be needed in sid since i386 is no longer
supported, but most i386 rdepends binaries should be gone already.

Ben file: the autogenerated one looks good

Andreas

Bug#813541: nvidia-graphics-drivers: Huge problems 'upgrading' to legacy version

[Manuel Bilderbeek]

Source: nvidia-graphics-drivers
Severity: important

Dear Maintainer,

I did my daily testing dist-upgrade just now, and I noticed I got a version of
the nvidia driver that is not going to work with my old GeForce 9600. I got a
nice pop up that the driver is not going to work, so I chose 'No', to not
install it.

But afterwards, many packages of 352 were actually installed after all.

I tried to install all the proper 340xx legacy packages, but as they didn't
conflict with the normal packages, all the normal stuff was also still
installed. Apparently that gave a lot of problems, because after booting I only
got a very blinky text console and no X.

After manually removing all packages of the 352 version and changing 'nvidia'
in /etc/modules-load.d/nvidia.conf to 'nvidia-legacy-340xx' I finally got a
working X11 again

Why did I have to do all that manual work to get X11 working again?
Which package owns that nvidia.conf anyway? I couldn't find it...

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

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

Bug#813540: [iceweasel] Random, spontaneous returns to source page from linked page

[David Baron]

Package: iceweasel
Version: 44.0-1
Severity: important

--- Please enter the report below this line. ---
Viewing a site page, click a link and view that. Spontaneously, one is 
returned to the main page, this at random.

Workaround is naturally to open the link in another tab or window for now.

--- System information. ---
Architecture: amd64
Kernel:   Linux 4.3.0-1-amd64

Debian Release: stretch/sid
  500 unstableftp.us.debian.org 
  500 testing ftp.us.debian.org 
  500 sid linux.dropbox.com 
  500 lucid   ppa.launchpad.net 
1 experimentalftp.us.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-===
libasound2  (>= 1.0.16) | 
libatk1.0-0 (>= 1.12.4) | 
libc6 (>= 2.17) | 
libcairo2(>= 1.2.4) | 
libdbus-1-3  (>= 1.0.2) | 
libdbus-glib-1-2  (>= 0.78) | 
libevent-2.0-5   (>= 2.0.10-stable) | 
libffi6  (>= 3.0.4) | 
libfontconfig1(>= 2.11) | 
libfreetype6 (>= 2.2.1) | 
libgcc1(>= 1:4.1.1) | 
libgdk-pixbuf2.0-0  (>= 2.22.0) | 
libglib2.0-0(>= 2.37.3) | 
libgtk2.0-0 (>= 2.24.0) | 
libhunspell-1.3-0(>= 1.3.3) | 
libnspr4  (>= 2:4.10.3) | 
libnss3 (>= 2:3.16) | 
libpango-1.0-0  (>= 1.14.0) | 
libsqlite3-0 (>= 3.7.12-1~) | 
libstartup-notification0   (>= 0.8) | 
libstdc++6 (>= 4.9) | 
libvpx1  (>= 1.3.0) | 
libx11-6| 
libxext6| 
libxrender1 | 
libxt6  | 
zlib1g (>= 1:1.2.0) | 
fontconfig  | 
procps  | 
debianutils   (>= 1.16) | 


Package's Recommends field is empty.

Suggests   (Version) | Installed
-+-===
fonts-stix   | 1.1.1-4
 OR otf-stix | 
fonts-oflb-asana-math| 
fonts-mathjax| 
mozplugger   | 
libgssapi-krb5-2 | 
 OR libkrb53 | 
libgnomeui-0 | 
libcanberra0 | 



--- Output from package bug script ---
Warning: locale not supported by C library, locale unchanged

Bug#813534: siproxd: WARNING:couldn't create new PID file: No such file or directory

[Geert Stappers]

Control: tag -1 moreinfo
stop

thanks for reporting


On Tue, Feb 02, 2016 at 10:09:37PM +0100, Richard van den Berg wrote:
> Package: siproxd
> Version: 1:0.8.1-4+b1
> Severity: normal
> Tags: patch

'patch' as "unified patch, output of `diff -u`"?   (I didn't see it attached)

> When running siproxd out of the box I got this in /var/log/messages:
> 
> Feb  2 21:54:48 majoron siproxd[20351]: utils.c:635 WARNING:couldn't create 
> new PID file: No such file or directory
> 
> Creating /var/lib/siproxd/var/run/siproxd owned by siproxd:siproxd fixed the 
> warning.

And that is a directory what is created?

> -- Configuration Files:
> /etc/default/siproxd changed [not included]
> /etc/siproxd.conf changed [not included]

Please send the outpot of

  grep run /etc/default/siproxd /etc/siproxd.conf



Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#788062: os-prober corrupts LVs/partitions while being mounted inside a VM

[Dominik George]

Hi,

> update-grub on a vhost running qemu/kvm virtual machines
> while grub and os-prober is installed on the host might corrupt
> guest virtual machines / guest disks.

confirmed. This just tore Teckids' main infrastructure into pieces.

-nik

-- 
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17  FD26 B79A 3C16 A0C4 F296

Dominik George · Mobil: +49-151-61623918

Teckids e.V. · FrOSCon e.V. · OpenRheinRuhr e.V.
Fellowship of the FSFE · Piratenpartei Deutschland
Opencaching Deutschland e.V. · Debian Contributor

LPIC-3 Linux Enterprise Professional (Security)

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

Bug#793036: sparkleshare: Sparkleshare status icon no longer visible in default Gnome DE after upgrading from wheezy to jessie

[James Cook]

Update:

After a full six months of using Gnome on Debian, I have discovered that if
I move the mouse to the bottom of the screen, and then attempt to move the
mouse down further, the status bar does appear, and I can see the
SparkleShare status.

So, this isn't a problem with SparkleShare, it's just (in my opinion)
terrible discoverability of the Gnome status bar.

James

On 20 July 2015 at 10:35, James Cook  wrote:

> Package: sparkleshare
> Version: 1.2-0.1
> Severity: important
>
> Dear Maintainer,
>
> After upgrading to jessie, I no longer see the Sparkleshare icon.  I
> depend on
> it to tell me whether my repository has been synced.  Sparkleshare is still
> successfully running and syncing in the background, though.
>
> I'm using the default Gnome desktop environment.
>
> In case it helps, below is what appears in a terminal window if I run
> "sparkleshare restart", wait a few seconds, then "sparkleshare stop".
>
> Thanks,
>   James
>
> 
>
> james copter ~ $ sparkleshare restart
> Stopping SparkleShare... Done.
> Starting SparkleShare... Done.
> james copter ~ $ 10:28:31 | Environment | SparkleShare version: 1.2.0,
> Operating system: Unix (Unix 3.16.0.4)
> 10:28:32 | Auth | Imported key
> '/home/james/.config/sparkleshare/sparkleshare.james.c...@utoronto.ca.key'
> 10:28:32 | Auth | The following keys may be used:
> 2048 17:c8:77:9b:0c:e6:e4:7a:e6:df:af:46:cb:33:f0:97 rsa w/o comment (RSA)
> 2048 88:72:48:82:48:98:fb:8c:5a:9e:a0:a3:ce:dd:00:4c james@copter (RSA)
> java version "1.7.0_79"
> OpenJDK Runtime Environment (IcedTea 2.5.5) (7u79-2.5.5-1~deb8u1)
> OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)
> 10:28:32 | /home/james/big/SparkleShare/big | Initializing...
> 10:28:32 | Cmd | big | git log --since=1.month --raw --find-renames
> --date=iso
> --format=medium --no-color --no-merges
> 10:28:32 | Cmd | big | git log -n 75 --raw --find-renames --date=iso
> --format=medium --no-color --no-merges
> 10:28:32 | Cmd | big | git config core.ignorecase false
> 10:28:32 | ListenerFactory | Issued new listener for
> tcp://notifications.sparkleshare.org:443/
> 10:28:32 | Cmd | big | git config --get filter.bin.clean
> 10:28:32 | Cmd | big | git config remote.origin.url "ssh://james-pri@sylph
> /home
> /james-pri/sparkle/big"
> 10:28:32 | /home/james/big/SparkleShare/pri | Initializing...
> 10:28:32 | Cmd | pri | git log --since=1.month --raw --find-renames
> --date=iso
> --format=medium --no-color --no-merges
> 10:28:32 | Git | big | Checking for remote changes...
> 10:28:32 | Cmd | big | git rev-parse HEAD
> 10:28:32 | Cmd | big | git config core.ignorecase true
> 10:28:32 | Cmd | big | git config core.ignorecase false
> 10:28:32 | Cmd | big | git rev-parse --abbrev-ref HEAD
> 10:28:32 | Cmd | big | git ls-remote --heads --exit-code "ssh://james-
> pri@sylph/home/james-pri/sparkle/big" master
> 10:28:32 | Cmd | pri | git config core.ignorecase false
> 10:28:32 | ListenerFactory | Refered to existing listener for
> tcp://notifications.sparkleshare.org:443/
> 10:28:32 | Cmd | pri | git config --get filter.bin.clean
> 10:28:32 | Cmd | pri | git config remote.origin.url "ssh://james-pri@sylph
> /home
> /james-pri/sparkle/pri"
> 10:28:32 | Git | pri | Checking for remote changes...
> 10:28:32 | Cmd | pri | git rev-parse HEAD
> 10:28:32 | Cmd | pri | git config core.ignorecase true
> 10:28:32 | Cmd | pri | git config core.ignorecase false
> 10:28:32 | Cmd | pri | git rev-parse --abbrev-ref HEAD
> 10:28:32 | Cmd | pri | git ls-remote --heads --exit-code "ssh://james-
> pri@sylph/home/james-pri/sparkle/pri" master
> 10:28:33 | Avatars | Invalid certificate for https://www.gravatar.com/
> 10:28:33 | Avatars | Error fetching avatar for james.c...@utoronto.ca:
> Error
> getting response stream (Write: The authentication or decryption has
> failed.):
> SendFailure   at System.Net.HttpWebRequest.EndGetResponse (IAsyncResult
> asyncResult) [0x0] in :0
>   at System.Net.HttpWebRequest.GetResponse () [0x0] in  unknown>:0
>   at System.Net.WebClient.GetWebResponse (System.Net.WebRequest request)
> [0x0] in :0
>   at System.Net.WebClient.ReadAll (System.Net.WebRequest request,
> System.Object
> userToken) [0x0] in :0
>   at System.Net.WebClient.DownloadDataCore (System.Uri address,
> System.Object
> userToken) [0x0] in :0
> 10:28:33 | Git | big | No remote changes, local+remote:
> 227581fcc9709094dfbf59aa6abf31cb1ca9bd6a
> 10:28:33 | Cmd | big | git status --porcelain
> 10:28:33 | Git | pri | No remote changes, local+remote:
> b5945fe5a6eaf02fe471311947498ae982068752
> 10:28:33 | Cmd | pri | git status --porcelain
> sparkleshare stop
> Stopping SparkleShare... Done.
> james copter ~ $
>
>
>
> -- System Information:
> Debian Release: 8.1
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linke

Bug#813539: tails-installer: tails installer fails to sense usb stick

[Stefani Banerian]

Package: tails-installer
Version: 4.4.6+dfsg-1~bpo8+1
Severity: normal

Dear Maintainer,

in trying to use the gui, the usb stick was never displayed.

I did run the installer from command line:
/usr/lib/tails-installer/tails-installer  -v -f /dev/sdb 

** (tails-installer:26025): WARNING **: Couldn't connect to accessibility bus: 
Failed to connect to socket /tmp/dbus-6iecs4mxTn: Connection refused
[creator.py:689 (detect_supported_drives)] DEBUG: {}

the usb stick is seen by the kernel:
Bus 006 Device 007: ID 0951:1607 Kingston Technology DataTraveler 100

and it had a test partition:

parted /dev/sdb print 
Model: Kingston DataTraveler 2.0 (scsi)
Disk /dev/sdb: 4010MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End SizeType File system  Flags
 1  1049kB  4010MB  4009MB  primary  ext2


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

Kernel: Linux 3.16.0-4-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 tails-installer depends on:
ii  gdisk  0.8.10-2
ii  genisoimage9:1.1.11-3
ii  gir1.2-glib-2.01.42.0-2.2
ii  gir1.2-gtk-3.0 3.14.5-1+deb8u1
ii  gir1.2-udisks-2.0  2.1.3-5
ii  mtools 4.0.18-2
ii  p7zip-full 9.20.1~dfsg.1-4.1+deb8u1
ii  policykit-10.105-8
ii  python 2.7.9-1
ii  python-configobj   5.0.6-1
ii  python-gi  3.14.0-1
ii  python-urlgrabber  3.9.1-4.1
ii  syslinux   3:6.03+dfsg-5+deb8u1

tails-installer recommends no packages.

tails-installer suggests no packages.

-- no debconf information