Bug#819681: RFS: python-django-gravatar2/1.4.0-1 [ITP]

[Pierre-Elliott Bécue]

Le mercredi 20 avril 2016 à 08:49:27+0200, Nicolas Dandrimont a écrit :
> Tiago, when replying to a RFS, please use the bug report rather than the
> mailing list.
> 
> * Tiago Ilieve  [2016-04-12 03:23:50 -0300]:
> 
> > > When I tried to dput I've been refused it because 1.4.0-1 was already on 
> > > the
> > > server. That's the only way I found. Maybe I did something wrong.
> > 
> > Maybe you uploaded again before mentors.d.n processed the first
> > upload? There's an waiting time ("How long will it take until my
> > upload is available to sponsors?" from its Q&A[5]) between the upload
> > and the package actually being available in there. I'm suggesting this
> > because mentors.d.n even store different versions of the package, even
> > when you did not bump its version. You can always use the delete
> > button from its web interface as well.
> 
> Please don't.
> 
> Pierre-Elliott, please post full error messages when you have an issue, not
> your interpretation of the message. You probably got tripped by the fact that
> dput leaves a .upload file along your .changes to avoid double uploads. You 
> can
> either remove the .upload file or use dput -f to bypass that check.
> 
> No need to bump the revision number (which might end you up forgetting to
> upload the original tarball) or removing the package from mentors.d.n (which
> will remove history).
> 
> Bye,

Oh, well, understood, I missed that.

Thanks for the hint, should I reupload the package with -1 version, after
fixing the changelog? From where I stand that looks awkward but I'm eager to
follow any suggestion.

-- 
PE


signature.asc
Description: PGP signature

Bug#821880: wine: libgnutls30 and libgnutls30:i386 conflict when trying to install wine32

[Yusef Ghazal]

Package: wine
Version: 1.8.1-2
Severity: important

Dear Maintainer,

   * What led up to the situation?
I attempted to install wine. I ran "sudo aptitude install wine". After 
trying
to run the piece of software in wine it came back with a "wine: Bad EXE format" 
error.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
After googling I attempted to install wine32. Here is the aptitude 
output:
--
yghazal@yghazalThinkpad:~$ sudo aptitude install wine32
Note: selecting "wine32:i386" instead of the virtual package "wine32"
The following NEW packages will be installed:
  i965-va-driver:i386{a} libasound2:i386{a} libasound2-plugins:i386{a} 
libasyncns0:i386{a} libattr1:i386{a} libavcodec57:i386{a} 
libavresample3:i386{a} libavutil55:i386{a} libcap2:i386{a} 
libcrystalhd3:i386{a} libdb5.3:i386{a} libdbus-1-3:i386{a} 
  libflac8:i386{a} libfontconfig1:i386{a} libfreetype6:i386{a} 
libgcrypt20:i386{a} libglib2.0-0:i386{a} libglu1-mesa:i386{a} libgmp10:i386{a} 
libgnutls30:i386{ab} libgomp1:i386{a} libgpg-error0:i386{a} libgpm2:i386{a} 
libgsm1:i386{a} libhogweed4:i386{a} 
  libice6:i386{a} libicu55:i386{a} libidn11:i386{a} libjack-jackd2-0:i386{a} 
libjson-c3:i386{a} liblcms2-2:i386{a} libldap-2.4-2:i386{a} liblzma5:i386{a} 
libmp3lame0:i386{a} libmpg123-0:i386{a} libncurses5:i386{a} libnettle6:i386{a} 
libnuma1:i386{a} 
  libogg0:i386{a} libopenal1:i386{a} libopenjpeg5:i386{a} libopus0:i386{a} 
liborc-0.4-0:i386{a} libp11-kit0:i386{a} libpcap0.8:i386{a} libpcre3:i386{a} 
libpng16-16:i386{a} libpulse0:i386{a} libsamplerate0:i386{a} libsasl2-2:i386{a} 
libsasl2-modules:i386{a} 
  libsasl2-modules-db:i386{a} libschroedinger-1.0-0:i386{a} libselinux1:i386{a} 
libshine3:i386{a} libsm6:i386{a} libsnappy1v5:i386{a} libsndfile1:i386{a} 
libsoxr0:i386{a} libspeex1:i386{a} libspeexdsp1:i386{a} libssl1.0.2:i386{a} 
libswresample2:i386{a} 
  libswscale4:i386{a} libsystemd0:i386{a} libtasn1-6:i386{a} libtheora0:i386{a} 
libtwolame0:i386{a} libuuid1:i386{a} libva-x11-1:i386{a} libva1:i386{a} 
libvdpau-va-gl1:i386{a} libvdpau1:i386{a} libvorbis0a:i386{a} 
libvorbisenc2:i386{a} libvpx3:i386{a} 
  libwavpack1:i386{a} libwebp5:i386{a} libwine:i386{a} libwrap0:i386{a} 
libx264-148:i386{a} libx265-79:i386{a} libxcursor1:i386{a} libxi6:i386{a} 
libxml2:i386{a} libxrender1:i386{a} libxtst6:i386{a} libxvidcore4:i386{a} 
libzvbi0:i386{a} 
  mesa-vdpau-drivers:i386{a} ocl-icd-libopencl1:i386{a} va-driver-all:i386{a} 
vdpau-driver-all:i386{a} vdpau-va-driver:i386{a} wine32:i386 
0 packages upgraded, 95 newly installed, 0 to remove and 54 not upgraded.
Need to get 52.6 MB of archives. After unpacking 269 MB will be used.
The following packages have unmet dependencies:
 libgnutls30 : Breaks: libgnutls30:i386 (!= 3.4.10-4) but 3.4.11-3 is to be 
installed
 libgnutls30:i386 : Breaks: libgnutls30 (!= 3.4.11-3) but 3.4.10-4 is installed
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) libgnutls30:i386 [Not Installed]   
2) libldap-2.4-2:i386 [Not Installed] 
3) libwine:i386 [Not Installed]   
4) wine32:i386 [Not Installed]



Accept this solution? [Y/n/q/?]
--

Pressing Y will install nothing, pressing n will give me an alternative outcome 
in
which it unisntalls quite a few packages such as libreoffice, network-manager 
etc.

I then tried rm -rf ~/.wine and installing libwine and wine-development before 
running
wine. this time it tells me 

Could not load wine-gecko. HTML rendering will be disabled.
Could not load wine-gecko. HTML rendering will be disabled.


   * What was the outcome of this action?
I am currently still unable to use wine.
   * What outcome did you expect instead?
That it would work.

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

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

Versions of packages wine depends on:
ii  wine64  1.8.1-2

wine recommends no packages.

Versions of packages wine suggests:
pn  dosbox   
pn  wine-binfmt  

Versions of packages wine is related to:
ii  fonts-wine  1.8.1-2
ii  wine1.8.1-2
pn  wine32  
ii  wine64  1.8.1-2

-- no debconf information

Bug#821868: [PKG-Openstack-devel] Bug#821868: openstack-dashboard: causes trigger loop

[Thomas Goirand]

On 04/20/2016 04:05 AM, Andreas Beckmann wrote:
> Package: openstack-dashboard
> Version: 2:9.0.0-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package causes a trigger loop.
> This was observed during a testing -> sid upgrade test (where
> openstack-dashboard had the same versions in testing and sid, and the
> installation in testing went without problems).
> 
>>From the attached log (scroll to the bottom...):
> 
>   Processing triggers for libc-bin (2.22-6) ...
>   dpkg: cycle found while processing triggers:
>chain of packages whose triggers are or may be responsible:
> openstack-dashboard -> openstack-dashboard
>packages' pending triggers which are or may be unresolvable:
> openstack-dashboard: /usr/share/javascript/jquery: 
> /usr/share/javascript/angular.js
>   dpkg: error processing package openstack-dashboard (--configure):
>triggers looping, abandoned
>   Errors were encountered while processing:
>openstack-dashboard
> 
> 
> cheers,
> 
> Andreas

Hi Andreas,

In fact, I've seen it once myself, on my build box, where I also do
install tests. Just running dpkg again to configure the package solved
the issue.

The thing is, I am really unsure how this happened, and how to fix. Help
would be appreciated a lot. Could you provide the full piuparts command
line, so I can reproduce the issue?

Cheers,

Thomas Goirand (zigo)

Bug#821260: RFS: python-adventure/1.4-1 [ITP]

[Ben Finney]

Markus Koschany  writes:

> The rationale for providing multiple binary packages is that users
> should be able to install a subset of an application and save some
> disk space.

Another important rationale for splitting common files to a separate
binary package, is to avoid duplication and potential divergence.

> In this case they always have to install both packages because
> otherwise the game would be broken. It would be a different case if
> they already had a choice and could choose between different variants.

My intention was to enable existing and future implementations to have
the canonical data file available, without needing to deal with the
Python application.

> I wouldn't decline to upload but you should take this wall of text
> into consideration. In my opinion you can always split the package
> later when a potential port might require it.

Fair enough. I will merge the “common” files into the
‘colossal-cave-adventure’ binary package.

> Indeed they redirect all requests now. I don't know if that comes with
> a performance penalty though. I wonder why we need two fields,
> Vcs-Browser and Vcs-Git, if they are identical...

Because the meanings are different (one is for VCS operations on the
repo, one is for web-browser access to browse the repo). And commonly
they are not the same URL.

-- 
 \“I hate it when my foot falls asleep during the day, because |
  `\that means it's gonna be up all night.” —Steven Wright |
_o__)  |
Ben Finney

Bug#821881: apparmor-profiles: sshd unable to read blacklists from openssh-blacklist* packages

[Vincas Dargis]

Package: apparmor-profiles
Version: 2.7.103-4
Severity: normal
Tags: upstream

Dear Maintainer,

In Wheezy I've enabled complain mode for usr.sbin.ssh (from apparmor-profiles
extras directory) and noticed these lines:

Apr 20 08:52:43 vdebian2 kernel: [30870.004961] audit: type=1400
audit(1461131563.110:76): apparmor="ALLOWED" operation="open"
profile="/usr/sbin/sshd" name="/usr/share/ssh/blacklist.RSA-2048" pid=27843
comm="sshd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

Apr 20 08:52:43 vdebian2 kernel: [30870.005132] audit: type=1400
audit(1461131563.110:77): apparmor="ALLOWED" operation="open"
profile="/usr/sbin/sshd" name="/usr/share/ssh/blacklist.DSA-1024" pid=27843
comm="sshd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

Looks like it would be usefull to add rule to allow reading
/usr/share/ssh/blacklist* files:

$ apt-file search ssh/blacklist
openssh-blacklist: /usr/share/ssh/blacklist.DSA-1024
openssh-blacklist: /usr/share/ssh/blacklist.RSA-2048
openssh-blacklist-extra: /usr/share/ssh/blacklist.DSA-2048
openssh-blacklist-extra: /usr/share/ssh/blacklist.RSA-1024
openssh-blacklist-extra: /usr/share/ssh/blacklist.RSA-4096

I do not see this rule HEAD: https://alioth.debian.org/scm/loggerhead/collab-
maint/apparmor/view/head:/profiles/apparmor/profiles/extras/usr.sbin.sshd so I
assume it's still relevant for latest releases.



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

Kernel: Linux 3.2.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 linked to /bin/dash

Versions of packages apparmor-profiles depends on:
ii  apparmor  2.7.103-4

apparmor-profiles recommends no packages.

apparmor-profiles suggests no packages.

-- no debconf information

Bug#819681: RFS: python-django-gravatar2/1.4.0-1 [ITP]

[Tiago Ilieve]

Nicolas,

On 20 April 2016 at 03:49, Nicolas Dandrimont  wrote:
> Tiago, when replying to a RFS, please use the bug report rather than the
> mailing list.

Yeah, I've only noticed this after my last message in the thread. Now
I figured that this happened because I've replied his second message,
which hadn't the bug address in the "Reply-To:" header.

Thanks for the reminder.

Regards,
Tiago.

-- 
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://br.linkedin.com/in/myhro
Montes Claros - MG, Brasil

Bug#821783: Window name on sakura.

[Walter Valenti]

>
> Da: Andreas Ronnquist 
>A: 821...@bugs.debian.org; Walter Valenti  
>Inviato: Martedì 19 Aprile 2016 17:58
>Oggetto: Re: Window name on sakura.
> 
>
>On Tue, 19 Apr 2016 09:28:10 + (UTC) Walter Valenti
> wrote:
>> The name of windows in wrong when the user is 'root'.
>> Example:
>> I open sakura with my user, I see:
>> walter@giada: ~
>> 
>> Now I exec 'su -', but the window name remains "walter@giada: ~"
>> 
>> Note that I switch on another user, the  windows name is correct.
>> Example:
>> I exec: su - test
>> The window name is: test@giada: ~
>
>For me sakura doesn't change title depending on which user is logged in
>- Are you sure you don't have anything setting the title as the user in
>some startup script (like bashrc) or something similar? 
>
>(For example something using something like
>http://tldp.org/HOWTO/Xterm-Title-3.html )
>
>This would explain it if you would get the behaviour for some users,
>but not for others.

>


Yes, I've found this in .bashrc and I've added at root !!!
Thanks


Walter

Bug#821328: ITP: debian-paketmanagement-buch -- German-written book about package management with Debian

[Axel Beckert]

Hi,

Justin B Rye wrote:
> DevRef recommends no extra capitalisation in a synopsis - that would
> be "book about...".  And I wouldn't use "with" quite like that.  How
> about:
> 
> Description:  book in German about Debian package management

I've now committed "book about Debian package management written in
German" as short description. Hope that's still fine for English ears
and eyes. :-)

Thanks for the feedback!

> # This package contains the book "Debian Paketmanagement" by Axel Beckert
> # and Frank Hofmann as a single HTML page, as a
> # PDF document and as an e-book in the epub format.

Fixed, thanks!

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

Bug#821154: chromium: crashes on video

[Sebastian Ramacher]

On 2016-04-16 10:20:26, Michael Gilbert wrote:
> control: tag -1 help, confirmed
> control: severity -1 grave
> x-debbugs-cc: pkg-multimedia-maintain...@lists.alioth.debian.org
> 
> Jose A. Fernandez Gonzalez wrote:
> > Version 49 of Chromium and earlier versions depend on ffmpeg libraries
> > (libavcodec, libavformat, libavutil, ...) and it seems version 50 doesn't
> > depend on those libraries, maybe the problem comes out with HTML5 content
> > because of that.
> 
> Chromium's linking of ffmpeg has somehow changed, so ffmpeg.patch will
> need to be updated, or the embedded copy of ffmpeg could be used
> again.
> 
> I don't have much free time right now, so it may be some time before I
> get to this.  Help is appreciated.

With the attached patch chromium links against ffmpeg at least. Other than that
it's untested.

Regards
-- 
Sebastian Ramacher
diff -Nru chromium-browser-50.0.2661.75/debian/changelog chromium-browser-50.0.2661.75/debian/changelog
--- chromium-browser-50.0.2661.75/debian/changelog	2016-04-14 03:10:04.0 +0200
+++ chromium-browser-50.0.2661.75/debian/changelog	2016-04-19 23:50:29.0 +0200
@@ -1,3 +1,10 @@
+chromium-browser (50.0.2661.75-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * 
+
+ -- Sebastian Ramacher   Tue, 19 Apr 2016 23:50:28 +0200
+
 chromium-browser (50.0.2661.75-1) unstable; urgency=medium
 
   * New upstream stable release:
diff -Nru chromium-browser-50.0.2661.75/debian/patches/system/ffmpeg.patch chromium-browser-50.0.2661.75/debian/patches/system/ffmpeg.patch
--- chromium-browser-50.0.2661.75/debian/patches/system/ffmpeg.patch	2016-04-14 03:49:09.0 +0200
+++ chromium-browser-50.0.2661.75/debian/patches/system/ffmpeg.patch	2016-04-19 23:42:52.0 +0200
@@ -7,7 +7,7 @@
 
 --- a/media/ffmpeg/ffmpeg_common.h
 +++ b/media/ffmpeg/ffmpeg_common.h
-@@ -38,7 +38,6 @@ extern "C" {
+@@ -38,7 +38,6 @@
  MSVC_PUSH_DISABLE_WARNING(4244);
  #include 
  #include 
@@ -17,7 +17,7 @@
  #include 
 --- a/media/filters/ffmpeg_demuxer.cc
 +++ b/media/filters/ffmpeg_demuxer.cc
-@@ -874,7 +874,11 @@ void FFmpegDemuxer::Initialize(DemuxerHo
+@@ -874,7 +874,11 @@
// this does not increase the amount of data downloaded.  The default value
// is 5 AV_TIME_BASE units (1 second each), which prevents some oddly muxed
// streams from being detected properly; this value was chosen arbitrarily.
@@ -29,7 +29,7 @@
  
// Open the AVFormatContext using our glue layer.
CHECK(blocking_thread_.Start());
-@@ -1034,24 +1038,6 @@ void FFmpegDemuxer::OnFindStreamInfoDone
+@@ -1034,24 +1038,6 @@
// If no estimate is found, the stream entry will be kInfiniteDuration().
std::vector start_time_estimates(format_context->nb_streams,
  kInfiniteDuration());
@@ -176,3 +176,152 @@
  '../third_party/mesa/mesa.gyp:osmesa',
],
  }],
+--- a/third_party/webrtc/modules/video_coding/codecs/h264/h264.gypi
 b/third_party/webrtc/modules/video_coding/codecs/h264/h264.gypi
+@@ -38,7 +38,7 @@
+ }],
+   ],
+   'dependencies': [
+-'<(DEPTH)/third_party/ffmpeg/ffmpeg.gyp:ffmpeg',
++'<(DEPTH)/build/linux/unbundle/ffmpeg.gyp:ffmpeg',
+ '<(DEPTH)/third_party/openh264/openh264.gyp:openh264_encoder',
+ '<(webrtc_root)/common_video/common_video.gyp:common_video',
+   ],
+--- a/third_party/webrtc/modules/video_coding/codecs/h264/h264_decoder_impl.cc
 b/third_party/webrtc/modules/video_coding/codecs/h264/h264_decoder_impl.cc
+@@ -15,9 +15,9 @@
+ #include 
+ 
+ extern "C" {
+-#include "third_party/ffmpeg/libavcodec/avcodec.h"
+-#include "third_party/ffmpeg/libavformat/avformat.h"
+-#include "third_party/ffmpeg/libavutil/imgutils.h"
++#include 
++#include 
++#include 
+ }  // extern "C"
+ 
+ #include "webrtc/base/checks.h"
+--- a/third_party/webrtc/modules/video_coding/codecs/h264/h264_decoder_impl.h
 b/third_party/webrtc/modules/video_coding/codecs/h264/h264_decoder_impl.h
+@@ -15,7 +15,7 @@
+ #include "webrtc/modules/video_coding/codecs/h264/include/h264.h"
+ 
+ extern "C" {
+-#include "third_party/ffmpeg/libavcodec/avcodec.h"
++#include 
+ }  // extern "C"
+ 
+ #include "webrtc/base/scoped_ptr.h"
+--- a/tools/gyp/tools/emacs/testdata/media.gyp
 b/tools/gyp/tools/emacs/testdata/media.gyp
+@@ -299,7 +299,7 @@
+ # and exclude the sources which depend on ffmpeg.
+ ['OS != "android"', {
+   'dependencies': [
+-'../third_party/ffmpeg/ffmpeg.gyp:ffmpeg',
++'../build/linux/unbundle/ffmpeg.gyp:ffmpeg',
+   ],
+ }],
+ ['OS == "android"', {
+@@ -721,7 +721,7 @@
+ }],
+ ['OS != "android"', {
+   'dependencies': [
+-'../third_party/ffmpeg/ffmpeg.gyp:ffmpeg',
++'../build/linux/unbundle/ffmpeg.gyp:ffmpeg',
+   ],
+ }],
+ ['OS == "android"', {
+@@ -1022,7

Bug#821883: ImportError: When using gi.repository you must not import static modules like "gobject"

[Anthony DeRobertis]

Package: morituri
Version: 0.2.3-2
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

After a recent apt-get upgrade, appears morituri (from experimental) no
longer works at all (traceback below). I attempted to fix it myself, but
I don't know Python so I didn't really get anywhere...

$ rip cd rip
Using configured read offset 6
Checking device /dev/sr0
CDDB disc id: 3d0cb416
MusicBrainz disc id fmCeZFVMZYuZ5ZGySzKhWgDlNNM-
MusicBrainz lookup URL 
https://musicbrainz.org/cdtoc/attach?toc=1+22+244050+150+17881+24489+34744+62335+65971+67088+70519+74719+86494+93347+98152+104826+128780+146665+148207+152406+162293+176335+193912+204024+233637&tracks=22&id=fmCeZFVMZYuZ5ZGySzKhWgDlNNM-
Disc duration: 00:54:12.000, 22 audio tracks

Matching releases:

Artist  : Richard Strauss; Staatskapelle Weimar, Antoni Wit
Title   : An Alpine Symphony
Duration: 00:54:11.992
URL : https://musicbrainz.org/release/084a9bbb-c722-40ad-8f32-097d697b7b09
Release : 084a9bbb-c722-40ad-8f32-097d697b7b09
Type: Album

Traceback (most recent call last):
  File "/usr/bin/rip", line 46, in 
h.handleImportError(e)
  File "/usr/bin/rip", line 41, in 
sys.exit(main.main(sys.argv[1:]))
  File "/usr/lib/python2.7/dist-packages/morituri/rip/main.py", line 50, in main
h.handleImportError(e)
  File "/usr/lib/python2.7/dist-packages/morituri/rip/main.py", line 45, in main
ret = c.parse(argv)
  File "/usr/lib/python2.7/dist-packages/morituri/rip/main.py", line 123, in 
parse
logcommand.LogCommand.parse(self, argv)
  File "/usr/lib/python2.7/dist-packages/morituri/extern/command/command.py", 
line 401, in parse
return self.subCommands[command].parse(args[1:])
  File "/usr/lib/python2.7/dist-packages/morituri/extern/command/command.py", 
line 401, in parse
return self.subCommands[command].parse(args[1:])
  File "/usr/lib/python2.7/dist-packages/morituri/extern/command/command.py", 
line 363, in parse
ret = self.do(args)
  File "/usr/lib/python2.7/dist-packages/morituri/rip/cd.py", line 160, in do
self.doCommand()
  File "/usr/lib/python2.7/dist-packages/morituri/rip/cd.py", line 276, in 
doCommand
self.program.result.gstreamerVersion = gstreamer.gstreamerVersion()
  File "/usr/lib/python2.7/dist-packages/morituri/common/gstreamer.py", line 
59, in gstreamerVersion
import gi
  File "/usr/lib/python2.7/dist-packages/gi/__init__.py", line 39, in 
raise ImportError(_static_binding_error)
ImportError: When using gi.repository you must not import static modules like 
"gobject". Please change all occurrences of "import gobject" to "from 
gi.repository import GObject". See: 
https://bugzilla.gnome.org/show_bug.cgi?id=709183




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

Kernel: Linux 4.4.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/bash
Init: systemd (via /run/systemd/system)

Versions of packages morituri depends on:
ii  cdparanoia 3.10.2+debian-11
ii  cdrdao 1:1.2.3-2+b1
ii  gstreamer1.0-plugins-good  1.8.0-1+b1
ii  python 2.7.11-1
ii  python-cddb1.4-5.2
ii  python-gi  3.18.2-2+b1
ii  python-gobject 3.18.2-2
ii  python-gst-1.0 1.8.0-1
ii  python-musicbrainzngs  0.5-2
ii  python-pkg-resources   18.8-1

Versions of packages morituri recommends:
ii  gstreamer1.0-libav  1:1.8.0-1+b1
ii  gstreamer1.0-tools  1.8.0-2
ii  python-xdg  0.25-4

Versions of packages morituri suggests:
ii  gstreamer1.0-plugins-ugly  1.8.0-1
ii  python-gtk22.24.0-4
pn  python-pycdio  

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlcXMmIACgkQ+z+IwlXqWf5tuQCfRpYKL8hVlkjvPczvzrSQOt66
tiYAn1XyXHpFtX7G5/7pxkLzH3T//gGQ
=zOKV
-END PGP SIGNATURE-

Bug#821882: RFP: golang-github-k0kubun-pp -- Go library for colored pretty printing

[Daniel Stender]

Package: wnpp
Severity: wishlist
Control: block 820614 by -1

* Package name: golang-github-k0kubun-pp
  Version : 2.1.0
  Upstream Author : Takashi Kokubun 
* URL : https://github.com/k0kubun/pp
* License : Expat
  Programming Lang: Go
  Description : Go library for colored pretty printing

This is a Go library for pretty printing on the terminal output.

It's a requirement for vuls.

Thanks,
DS

Bug#821100: [debian-mysql] Bug#821100: Security fixes from the April 2016 CPU

[Norvald H. Ryeng]

Vulnerabilities fixed by upgrading from 5.5.47 to 5.5.49:

CVE-2016-0640
CVE-2016-0641
CVE-2016-0642
CVE-2016-0643
CVE-2016-0644
CVE-2016-0646
CVE-2016-0647
CVE-2016-0648
CVE-2016-0649
CVE-2016-0650
CVE-2016-0666
CVE-2016-2047

Bug#821094: [debian-mysql] Bug#821094: Security fixes from the April 2016 CPU

[Norvald H. Ryeng]

Vulnerabilities fixed by upgrading from 5.6.28 to 5.6.30:

CVE-2015-3194
CVE-2016-0639
CVE-2016-0640
CVE-2016-0641
CVE-2016-0642
CVE-2016-0643
CVE-2016-0644
CVE-2016-0646
CVE-2016-0647
CVE-2016-0648
CVE-2016-0649
CVE-2016-0650
CVE-2016-0655
CVE-2016-0661
CVE-2016-0665
CVE-2016-0666
CVE-2016-0668
CVE-2016-0705
CVE-2016-2047

Bug#821777: diffoscope fails with "pkg_resources.DistributionNotFound: python-magic"

[Holger Levsen]

control: retitle -1 creating a jessie-backports takes more than a simple 
rebuild (and adopting the version)

On Tue, Apr 19, 2016 at 10:25:41AM +0200, Holger Levsen wrote:
> pkg_resources.DistributionNotFound: python-magic

from irc today:

< mapreri> | h01ger: this is because somehow 
/usr/lib/python3/dist-packages/diffoscope-51.egg-info/requires.txt in the 
backports build contains some lines that are not present in the sid build.
< mapreri> I couldn't figure it out at the time
< h01ger> | mapreri: i dont have that file, i have 
/usr/lib/python3/dist-packages/diffoscope-51_bpo8_1.egg-info/requires.txt which 
has two lines:
< h01ger> | python-magic
< h01ger> | libarchive-c
< mapreri> yeah, that.  the directory name changes with the package version.
< mapreri> python-magic is the problematic line, if you remove that it should 
just works, but I didn't want to do that with "brute force", but rather 
understand why it puts them in there in first place
< h01ger> | on sid, 
/usr/lib/python3/dist-packages/diffoscope-51.egg-info/requires.txt is empty
< h01ger> | when i remove that line…
< h01ger> | running diffoscope against two signed changes files for the same 
distro works \o/

so that is nice and just tells us, that creating a working backport is a bit
harder than just adopting the version and rebuilding…

I've also seen another problem when comparing a signed and unsigned changes
file and between ones from different suites, but let's limit the scope of
this bug report to the issue of creating a working backport for jessie.

Because the above manual workaround is no solution yet…


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#821880: wine: libgnutls30 and libgnutls30:i386 conflict when trying to install wine32

[Adam D. Barratt]

On 2016-04-20 8:12, Yusef Ghazal wrote:

   * What led up to the situation?
	I attempted to install wine. I ran "sudo aptitude install wine". After 
trying

to run the piece of software in wine it came back with a "wine: Bad
EXE format" error.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
	After googling I attempted to install wine32. Here is the aptitude 
output:

[...]

The following packages have unmet dependencies:
 libgnutls30 : Breaks: libgnutls30:i386 (!= 3.4.10-4) but 3.4.11-3 is
to be installed
 libgnutls30:i386 : Breaks: libgnutls30 (!= 3.4.11-3) but 3.4.10-4 is 
installed


This isn't a bug in wine, it's a consequence of the fact that unstable 
currently has different versions of libgnutls30 on i386 and amd64 as the 
most recent upload failed to build on amd64. There's nothing the wine 
maintainers can do about this and the situation will automatically 
resolve itself once the libgnutls30 build failure is fixed. (As a side 
note, this sort of thing will happen in unstable.)


Regards,

Adam

Bug#821363: debian-policy: Allow line-end comments in all Debian packaging control files

[Guillem Jover]

[ Switching from d-p@l.d.o to the bug so that the thread is tracked. ]

On Wed, 2016-04-20 at 11:23:19 +1000, Ben Finney wrote:
> Guillem Jover  writes:
> > On Mon, 2016-04-18 at 14:52:22 +1000, Ben Finney wrote:
> > > What is the rationale for explicitly disallowing line-end comments
> > > in any but that one file?
> >
> > This just predates other files in source packages using deb822 syntax.
> > The reason is that the control file in a binary package does not
> > support comments for example.

> Should the wording at least be changed so that it only prohibits
> line-end comments in binary package control file?

I think an explicit list of files supporting comments instead of one
of those not supporting them would be better.

> I ask this because I'm pretty sure that people who hand-wave a
> specification as “same syntax as ‘debian/control’ file” intend for it to
> have all the allowed syntax of that file, including comments.

Perhaps, but in the end it does not matter, if the file has not been
explicitly specified as supporting them and the current code handling
those other files cannot handle comments anyway.

There are more files with deb822 style syntax that are neither in
source nor binary packages, several of which I'm doubtful might support
comments(?):

  * (In)Release, Packages, Sources, Translation files in repositories.
  * .dsc files
  * .changes files.
  * dpkg origins (or vendor file), specified as supporting comments.
  * dpkg status file (not supported).
  * …

So, as stated I'd list them explicitly, or restrict to only files inside
a source package perhaps. I'll be adding the origins file to the new
deb822(5) man page describing the format in dpkg's git master, though.

Thanks,
Guillem

Bug#726088: roundcube-plugins-extra: Roundcube-plugins-extra is not available for 0.9

[Dimitris T]

Maybe this should be in a different bug report,
but can roundcube-plugins-extra land into jessie-backports?

thx in advance,
dimitris




signature.asc
Description: OpenPGP digital signature

Bug#821363: debian-policy: Allow line-end comments in all Debian packaging control files

[Guillem Jover]

[ Also redireting to the bug report. ]

On Wed, 2016-04-20 at 11:29:05 +1000, Ben Finney wrote:
> Guillem Jover  writes:
> > In the case of the copyright file, the document specifying it does not
> > list # as valid comment markers.
> 
> When we were drafting that specification, I at least intended this text:
> 
>The syntax of the file is the same as for other Debian control files,
>as specified in the Debian Policy Manual. See its section 5.1 for
>details.
> 
> to mean the same syntax as ‘debian/control’. I wasn't even aware when
> drafting it, that a question of comments in one file but not another
> could arise based on the file name.

See my other mail.

> Certainly my intention in that specification was for comments to be
> allowed in the ‘debian/copyright’ file just as they are in
> ‘debian/control’.

If that was clear to everyone then adding it should be fine, indeed.
And then parsers not supporting comments should just be considered
buggy.

> > For example parsing debian/copyright files (or any other file using
> > deb822-based syntax) via the Dpkg::Control::Hash perl module would
> > make it accept such comments, but I don't know if other parsers will
> > accept those too.
> 
> That's a good criterion. Which parsers would you suggest we verify? The
> Emacs mode, the Dpkg Perl modules, and other tools I have used do not
> complain when comments are used in any control-syntax file.
> 
> What would constitute a sufficient degree of investigation of existing
> parsers for this issue?

Some time ago I created a wiki page intended to track this kind of
issues and support in software handling deb822-style syntax:

  

But didn't have the time to check other implementations and add more
detailed features. But I think that might be a good place to track
support for this too.

The list of additional parsers depends on whether you want to check
for support in deb822 parsers in general or just for debian/copyright.
For the latter I'd add at least:

  * libconfig-model-dpkg-perl
  * libdebian-copyright-perla
  * license-reconcile
  * adequate
  * debmake (?)
  * dpkg-dev-el
  * devscripts (?)

For the former also:

  * apt
  * python-apt
  * python-debian
  * ruby-debian
  * vim
  * grep-dctrl
  * lintian

and probably several of the ones listed in either:

  
  

Thanks,
Guillem

Bug#821862: Do not release with stretch

[Andriy Grytsenko]

Well, while your point is right, removal of system-tools-backends will
broke LXDE usability because there is no other alternative package to
manage users - other known users management tools are integrated into
GNOME and KDE, and gnome-system-tools is only standalone package which
can be used in any other DE. Yes, literally, there is no alternative to
the gnome-system-tools and it depends on system-tools-backends.

Bug#796583: [Pkg-kbd-devel] Bug#796583: How are people supposed to deal with the missing setterm calls?

[Andreas Henriksson]

Hello Marga Manterola.

On Tue, Apr 19, 2016 at 02:37:23PM +, Marga Manterola wrote:
> The NEWS.Debian file says that users should move to console-setup instead
> of kbd, which would be fine if console-setup provided the same
> functionality.  For certain things, it doesn't. Look at this snippet from
> the old init script:
> 
> # screensaver stuff
> setterm_args=""
> if [ "$BLANK_TIME" ]; then
> setterm_args="$setterm_args -blank $BLANK_TIME"
> fi
> if [ "$BLANK_DPMS" ]; then
> setterm_args="$setterm_args -powersave $BLANK_DPMS"
> fi
> if [ "$POWERDOWN_TIME" ]; then
> setterm_args="$setterm_args -powerdown $POWERDOWN_TIME"
> fi
> if [ "$setterm_args" ]; then
> setterm $setterm_args
> fi
> 
> As far as I can see, there's nothing in console-setup that provides this
> functionality.  At all.

ACK.

> 
> Is each and every user of kbd expected to now write their own init script
> that calls setterm with the right arguments?

If running setterm is important to you, yes then you could write your
own init script (or other mechanism) to do that.

> 
> Why was this dropped without providing an alternative?

Primarily because very few users are expected to ever care about that
specific part of the init script and obviously noone stepped up to carry
the maintenance burden of keeping it around.
Also this Debian-specific snippet breaks distro-agnostic and more
efficient ways of handling this IIRC. e.g. passing kernel commandline
options. (Maybe that was some other bit of this init scripts though.
My memory is vague since you're joining the party quite late on this
discussion.)
Please also note that Ubuntu was disabling this part for a long time
since they considered it harmful. Please give us the benefit of the
doubt when you jump to the conclution that this was done without careful
consideration.

Why should kbd package ship an init script for a utility that's not part
of kbd in the first place? 
Why should we have duplicate configurations for the same settings?
Why should the burden of carrying this exotic feature be put on the
scarse maintenance resources rather than on the few potential users?
Why should I be required to provide support for people who doesn't
want to do their own research and thinks the bug tracking system
is a support forum?

All above rethorical questions ofcourse... please feel free to not
answer them.

Please feel free to close and archive this bug report again.

Regards,
Andreas Henriksson

Bug#821763: xserver-xorg-video-radeon: LibreOffice Preferences UI font corruption on AMD A6-1450 APU/Radeon HD 8250

[Michel Dänzer]

On 19.04.2016 16:18, J Mo wrote:
> 
> The other system I put my drive into had a Nvidia GTX 970 and definitely
> nouveau as it's newly installed Debian as of last week and I made no
> special configuration changes.

So, can you check whether the Xorg modesetting driver is used with that,
and whether it enables glamor acceleration? And if either is not true,
can you try forcing it in xorg.conf and see if you can reproduce the
problem then?


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer

Bug#821886: proselint: clear_cache() function clears the current directory instead of the cache directory

[Paul Wise]

Package: python3-proselint
Version: 0.5.3-1
Severity: serious
File: /usr/lib/python3/dist-packages/proselint/command_line.py

When I run `proselint --debug` from my home directory it searches my
whole home directory for *.pyc files and deletes them. While *.pyc
files are usually Python bytecode that might not be true for every user
and even if they were, that doesn't mean the user doesn't want to keep
them. Either way it is completely unacceptable to delete stuff from the
user's home directory just because they want to debug proselint.

Also, what happened to removing use of shell=True?

def proselint(paths=None, version=None, initialize=None, clean=None,
  debug=None, score=None, output_json=None, time=None, demo=None,
  compact=None):
...
# In debug or clean mode, delete cache & *.pyc files before running.
if debug or clean:
clear_cache()


def clear_cache():
"""Delete the contents of the cache."""
click.echo("Deleting the cache...")
subprocess.call("find . -name '*.pyc' -delete", shell=True)
subprocess.call(
"rm -rfv proselint/cache > /dev/null && mkdir -p {}".format(
os.path.join(os.path.expanduser("~"), ".proselint")),
shell=True)

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

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

Versions of packages python3-proselint depends on:
ii  python3-click   6.6-1
ii  python3-future  0.15.2-1
ii  python3-six 1.10.0-2
pn  python3:any 

python3-proselint recommends no packages.

python3-proselint suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#821887: new upstream 1.2.5

[Harald Dunkel]

Package: tomcat-native
Version: 1.1.33

Upstream provides version 1.2.5, so I wonder if it would
be reasonable to upgrade the debian package?


Regards
Harri

Bug#821885: RFS: flintqs/1.0-1 (RC #760193)

[Julien Puydt]

Package: sponsorship-requests
Severity: important

Dear mentors,

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

 * Package name: flintqs
   Version : 1.0-1
   Upstream Author : William Hart
 * URL : https://github.com/sagemath/FlintQS
 * License : GPL-2+
   Section : math

  It builds those binary packages:

flintqs- Program using quadratic sieve to factor integers

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


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


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

dget -x 
http://mentors.debian.net/debian/pool/main/f/flintqs/flintqs_1.0-1.dsc


  Changes since the last upload:
  * New upstream release. (Closes: #760193)
  * Point to new upstream repository.
  * Push standards-version up.
  * Simplify packaging as upstream now uses autotools.

Upstream changed their versioning scheme, this is really the latest.

  Regards,
   Julien Puydt

Bug#821888: proselint: --demo option is broken

[Paul Wise]

Package: python3-proselint
Version: 0.5.3-1
Severity: normal
File: /usr/lib/python3/dist-packages/proselint/command_line.py

When I run `proselint --demo` nothing happens:

pabs@chianamo ~/tmp-proselint $ proselint --demo
pabs@chianamo ~/tmp-proselint $ proselint --debug --demo
Deleting the cache...

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

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

Versions of packages python3-proselint depends on:
ii  python3-click   6.6-1
ii  python3-future  0.15.2-1
ii  python3-six 1.10.0-2
pn  python3:any 

python3-proselint recommends no packages.

python3-proselint suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#821365: debian-policy: Clarify which characters constitute the syntax of control files

[Guillem Jover]

Hi!

On Mon, 2016-04-18 at 15:11:38 +1000, Ben Finney wrote:
> Package: debian-policy
> Severity: minor
> Control: tags -1 + patch

> The description of control file syntax in §5.1 references numerous
> characters, some by number and some as simple display of the
> character, and some as informal names. Some of these mentions are
> confusing.
> 
> The section also specifies that all control files are encoded as
> UTF-8, so knowledge of Unicode is (IMO correctly) assumed of the
> reader.
> 
> This patch standardises the mention of characters in §5.1 to
> explicitly give Unicode code point references and (where appropriate)
> the literal character unambiguously quoted.

Ah good idea, I've changed this locally in the deb822(5) man page from
dpkg git, based on your patch, will appear in my next push. Attached
the changes.

Thanks,
Guillem
From e80ec0774a3f95b31b18a4843d1ee10cae019031 Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Wed, 20 Apr 2016 10:43:13 +0200
Subject: [PATCH] man: Clarify what characters constitute the syntax of deb822
 syntax

Based-on-a-patch-by: Ben Finney 
---
 man/deb822.5 | 38 +-
 1 file changed, 21 insertions(+), 17 deletions(-)

diff --git a/man/deb822.5 b/man/deb822.5
index 1d2df4c..dde7384 100644
--- a/man/deb822.5
+++ b/man/deb822.5
@@ -31,8 +31,9 @@ files (\fBdpkg\fP's internal databases are in a similar format).
 A control file consists of one or more paragraphs of fields (the paragraphs
 are also sometimes referred to as stanzas).
 The paragraphs are separated by empty lines.
-Parsers may accept lines consisting solely of spaces and tabs as paragraph
-separators, but control files should use empty lines.
+Parsers may accept lines consisting solely of U+0020 \fBSPACE\fP and
+U+0009 \fBTAB\fP as paragraph separators, but control files should use
+empty lines.
 Some control files allow only one paragraph; others allow several, in which
 case each paragraph usually refers to a different package.
 (For example, in source packages, the first paragraph refers to the source
@@ -41,19 +42,21 @@ source.)
 The ordering of the paragraphs in control files is significant.
 
 Each paragraph consists of a series of data fields.
-Each field consists of the field name followed by a colon and then the
-data/value associated with that field.
+Each field consists of the field name followed by a U+003A \(oq\fB:\fP\(cq,
+and then the data/value associated with that field.
 The field name is composed of US-ASCII characters excluding control
-characters, space, and colon (i.e., characters in the ranges 33-57 and
-59-126, inclusive).
-Field names must not begin with the comment character (\(oq\fB#\fP\(cq),
-nor with the hyphen character (\(oq\fB\-\fP\(cq).
+characters, space, and colon (i.e., characters in the ranges
+U+0021 \(oq\fB!\fP\(cq through U+0039 \(oq\fB9\fP\(cq, and
+U+003B \(oq\fB;\fP\(cq through U+007E \(oq\fB~\fP\(cq, inclusive).
+Field names must not begin with the comment character
+(U+0023 \(oq\fB#\fP\(cq), nor with the hyphen character
+(U+002D \(oq\fB\-\fP\(cq).
 
 The field ends at the end of the line or at the end of the last continuation
 line (see below).
-Horizontal whitespace (spaces and tabs) may occur immediately before or after
-the value and is ignored there; it is conventional to put a single space after
-the colon.
+Horizontal whitespace (U+0020 \fBSPACE\fP and U+0009 \fBTAB\fP) may occur
+immediately before or after the value and is ignored there; it is conventional
+to put a single space after the colon.
 For example, a field might be:
 .RS
 .nf
@@ -81,7 +84,7 @@ specify a different type.
 .B folded
 The value of a folded field is a logical line that may span several lines.
 The lines after the first are called continuation lines and must start with
-a space or a tab.
+a U+0020 \fBSPACE\fP or a U+0009 \fBTAB\fP.
 Whitespace, including any newlines, is not significant in the field values
 of folded fields.
 
@@ -111,13 +114,14 @@ names using mixed case as shown below.
 Field values are case-sensitive unless the description of the field says
 otherwise.
 
-Paragraph separators (empty lines) and lines consisting only of spaces and
-tabs are not allowed within field values or between fields.
+Paragraph separators (empty lines) and lines consisting only of
+U+0020 \fBSPACE\fP and U+0009 \fBTAB\fP, are not allowed within field
+values or between fields.
 Empty lines in field values are usually escaped by representing them by a
-space followed by a dot.
+U+0020 \fBSPACE\fP followed by a U+002E \(oq\fB.\fP\(cq.
 
-Lines starting with \(oq\fB#\fP\(cq without any preceding whitespace are
-comments lines that are only permitted in source package control files
+Lines starting with U+0023 \(oq\fB#\fP\(cq, without any preceding whitespace
+are comments lines that are only permitted in source package control files
 (\fIdebian/control\fP) and in \fBdeb\-origin\fP(5) files.
 These comment lines are ignored, even between two continuation lines.
 The

Bug#821407: debtags: scripts use python3 but have Python 2-only syntax

[Enrico Rossi]

On Wed, Apr 20, 2016 at 09:53:44AM +0800, Paul Wise wrote:
> > both scripts are broken and no longer maintained. I'm going to remove
> > them from the next version.
> 
> Seems like they are useful scripts that should be fixed instead?

First I fixed the syntax, but there are other missing library that need
to be fixed, then I asked Enrico Zini and he confirmed that these
software are no longer maintained and should be removed long ago.
See also #813581 regarding the submit-patch script.

> Please remove python3-debtagshw if you remove debtags-hardware.

Yes I will.
Thanks
Ciao
E.

-- 
GPG Key: 4096R/F2133176 2010-10-19 Enrico Rossi 


signature.asc
Description: PGP signature

Bug#821889: wdm: /etc/X11/wdm/wdm-config adds /usr/bin/X11 to PATH

[Paul Tötterman]

Package: wdm
Version: 1.28-18
Severity: normal

Dear maintainer,

On my debian testing system /etc/X11/wdm/wdm-config contained these lines:

DisplayManager*userPath: /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
DisplayManager*systemPath: 
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11

/usr/bin/X11 is a symlink to /usr/bin so it is a redundant entry and should be
removed from the list.

Cheers,
Paul

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

Kernel: Linux 4.4.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 wdm depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  libc6  2.22-6
ii  libpam-modules 1.1.8-3.2
ii  libpam-runtime 1.1.8-3.2
ii  libpam0g   1.1.8-3.2
ii  libselinux12.4-3+b1
ii  libwings3  0.95.7-6+b1
ii  libwraster50.95.7-6+b1
ii  libwutil5  0.95.7-6+b1
ii  libx11-6   2:1.6.3-1
ii  libxau61:1.0.8-1
ii  libxdmcp6  1:1.1.2-1.1
ii  libxinerama1   2:1.1.3-1+b1
ii  libxmu62:1.1.2-2
ii  psmisc 22.21-2.1+b1
ii  x11-apps   7.7+5+nmu1+b1
ii  x11-common 1:7.7+14
ii  x11-utils  7.7+3
ii  x11-xserver-utils  7.7+7

wdm recommends no packages.

Versions of packages wdm suggests:
ii  xfonts-base  1:1.0.4+nmu1

-- Configuration Files:
/etc/X11/wdm/wdm-config [Errno 13] Permission denied: u'/etc/X11/wdm/wdm-config'

-- debconf information:
  wdm/daemon_name: /usr/bin/wdm
* shared/default-x-display-manager: wdm

Bug#821890: ferm - Job ferm.service/start deleted to break ordering cycle starting with basic.target/start

[Bastian Blank]

Package: ferm
Version: 2.2-3.2
Severity: grave
Tags: stable

ferm is completely broken on stable, it fails to start due to a
dependency cycle.

| systemd[1]: Found ordering cycle on basic.target/start
| systemd[1]: Found dependency on sysinit.target/start
| systemd[1]: Found dependency on ferm.service/start
| systemd[1]: Found dependency on network-online.target/start
| systemd[1]: Found dependency on systemd-networkd-wait-online.service/start
| systemd[1]: Found dependency on systemd-networkd.service/start
| systemd[1]: Found dependency on dbus.service/start
| systemd[1]: Found dependency on basic.target/start
| systemd[1]: Breaking ordering cycle by deleting job ferm.service/start
| systemd[1]: Job ferm.service/start deleted to break ordering cycle starting 
with basic.target/start

Regards,
Bastian

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

Kernel: Linux 4.4.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 ferm depends on:
ii  debconf  1.5.59
ii  init-system-helpers  1.29
ii  iptables 1.6.0-2
ii  lsb-base 9.20160110
ii  perl 5.22.1-9

Versions of packages ferm recommends:
ii  libnet-dns-perl  1.05-1

ferm suggests no packages.

-- Configuration Files:
/etc/ferm/ferm.conf changed [not included]

-- debconf information excluded

Bug#821891: libbde: FTBFS: FAIL: test_bdeinfo.sh

[Chris Lamb]

Source: libbde
Version: 20160418-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

libbde fails to build from source in unstable/amd64:

  [..]

--add-comments=TRANSLATORS: --keyword=_ --keyword=N_  \
--files-from=./POTFILES.in \
--copyright-holder='Joachim Metz' \
--package-name="${package_gnu}libbde" \
--package-version='20160418' \
--msgid-bugs-address="$msgid_bugs_address" \
  ;; \
  esac
  test ! -f libbde.po || { \
if test -f ./libbde.pot; then \
  sed -f remove-potcdate.sed < ./libbde.pot > libbde.1po && \
  sed -f remove-potcdate.sed < libbde.po > libbde.2po && \
  if cmp libbde.1po libbde.2po >/dev/null 2>&1; then \
rm -f libbde.1po libbde.2po libbde.po; \
  else \
rm -f libbde.1po libbde.2po ./libbde.pot && \
mv libbde.po ./libbde.pot; \
  fi; \
else \
  mv libbde.po ./libbde.pot; \
fi; \
  }
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/po'
  test ! -f ./libbde.pot || \
test -z "" || make 
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/po'
  Making all in manuals
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/manuals'
  make[2]: Nothing to be done for 'all'.
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/manuals'
  Making all in tests
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/tests'
  make[2]: Nothing to be done for 'all'.
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/tests'
  Making all in msvscpp
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/msvscpp'
  make[2]: Nothing to be done for 'all'.
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/msvscpp'
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418'
  make[2]: Nothing to be done for 'all-am'.
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418'
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418'
 dh_auto_test -O--parallel
make -j9 check VERBOSE=1
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418'
  Making check in include
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/include'
  make[2]: Nothing to be done for 'check'.
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/include'
  Making check in common
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/common'
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/common'
  Making check in libcstring
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/libcstring'
  make[2]: Nothing to be done for 'check'.
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/libcstring'
  Making check in libcerror
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/libcerror'
  make[2]: Nothing to be done for 'check'.
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/libcerror'
  Making check in libcthreads
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/libcthreads'
  make[2]: Nothing to be done for 'check'.
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/libcthreads'
  Making check in libcdata
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/libcdata'
  make[2]: Nothing to be done for 'check'.
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/libcdata'
  Making check in libclocale
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/libclocale'
  make[2]: Nothing to be done for 'check'.
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/libclocale'
  Making check in libcnotify
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaqTD.libbde/libbde-20160418/libcnotify'
  make[2]: Nothing to be done for 'check'.
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160420095942.L18erNaq

Bug#821260: RFS: python-adventure/1.4-1 [ITP]

[Ben Finney]

Ben Finney  writes:

> I will merge the “common” files into the ‘colossal-cave-adventure’
> binary package.

This is now done, and the updated source package is available:

$ dget -x 
http://mentors.debian.net/debian/pool/main/p/python-adventure/python-adventure_1.4-1.dsc

-- 
 \  “Not using Microsoft products is like being a non-smoker 40 or |
  `\ 50 years ago: You can choose not to smoke, yourself, but it's |
_o__)   hard to avoid second-hand smoke.” —Michael Tiemann |
Ben Finney 

Bug#815956: courier-imap: makedat error

[J Mo]

Package: courier-imap
Followup-For: Bug #815956

I just ran into this bug, so it's still an issue for upgrading. I'll go poking 
around the control scripts in a bit and see WTF the issue is.

Like OP said:

Setting up courier-imap (4.16.2+0.75.0-18) ...
Usage: /usr/bin/makedat -src=src -file=file -tmp=tmpfile -hup=hupfile [-cidr]
dpkg: error processing package courier-imap (--configure):
 subprocess installed post-installation script returned error exit status 1



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

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

Versions of packages courier-imap depends on:
ii  courier-authlib 0.66.4-7
ii  courier-base0.75.0-18
ii  courier-mta [mail-transport-agent]  0.75.0-18
ii  debconf [debconf-2.0]   1.5.59
ii  libc6   2.22-7
ii  libcourier-unicode1 1.4-2
ii  libgamin0 [libfam0] 0.1.10-5
ii  libgdbm31.8.3-13.1
ii  libidn111.32-3
ii  sysvinit-utils  2.88dsf-59.3

courier-imap recommends no packages.

Versions of packages courier-imap suggests:
ii  courier-doc   0.75.0-18
ii  mutt [imap-client]1.5.24-1+b1
ii  s-nail [imap-client]  14.8.8-1

-- Configuration Files:
/etc/courier/imapd changed [not included]
/etc/courier/imapd-ssl changed [not included]
/etc/courier/imapd.cnf [Errno 13] Permission denied: u'/etc/courier/imapd.cnf'

-- no debconf information

Bug#821894: cluster-glue: copyright file missing after upgrade (policy 12.5)

[Andreas Beckmann]

Source: cluster-glue
Version: 1.0.12-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This seems to affect all (most?) lib*X and lib*-dev packages built from
src:cluster-glue.

This was observed on the following upgrade paths:

  jessie -> stretch

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

1m55.3s ERROR: WARN: Inadequate results from running adequate!
  libpils2: missing-copyright-file /usr/share/doc/libpils2/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/libpils2/copyright
  # ls -lad /usr/share/doc/libpils2
  drwxr-xr-x 2 root root 40 Apr 14 14:20 /usr/share/doc/libpils2
  # ls -la /usr/share/doc/libpils2/
  total 0
  drwxr-xr-x   2 root root   40 Apr 14 14:20 .
  drwxr-xr-x 155 root root 3340 Apr 14 14:20 ..


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


libpils2_1.0.12-4.log.gz
Description: application/gzip

Bug#821893: uclmmbase: FTBFS: mkdir: cannot create directory 'html': File exists

[Chris Lamb]

Source: uclmmbase
Version: 1.2.16.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

uclmmbase fails to build from source in unstable/amd64:

  [..]

  ((word32*)block)[0] ^= *((word32*)iv[0]);
  ^
  rijndael-api-fst.c:310:4: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
  rijndael-api-fst.c:311:4: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
  ((word32*)block)[1] ^= *((word32*)iv[1]);
  ^
  rijndael-api-fst.c:312:4: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
  ((word32*)block)[2] ^= *((word32*)iv[2]);
  ^
  rijndael-api-fst.c:313:4: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
  ((word32*)block)[3] ^= *((word32*)iv[3]);
  ^
  rijndael-api-fst.c:318:4: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
  *((word32*)iv[0]) = ((word32*)input)[0]; ((word32*)outBuffer)[0] = 
((word32*)block)[0];
  ^
  rijndael-api-fst.c:318:4: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
  rijndael-api-fst.c:319:4: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
  *((word32*)iv[1]) = ((word32*)input)[1]; ((word32*)outBuffer)[1] = 
((word32*)block)[1];
  ^
  rijndael-api-fst.c:320:4: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
  *((word32*)iv[2]) = ((word32*)input)[2]; ((word32*)outBuffer)[2] = 
((word32*)block)[2];
  ^
  rijndael-api-fst.c:321:4: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
  *((word32*)iv[3]) = ((word32*)input)[3]; ((word32*)outBuffer)[3] = 
((word32*)block)[3];
  ^
  rijndael-api-fst.c:332:3: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
 *((word32*)iv[0]) = *((word32*)(cipher->IV));
 ^
  rijndael-api-fst.c:332:3: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
  rijndael-api-fst.c:333:3: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
 *((word32*)iv[1]) = *((word32*)(cipher->IV+ 4));
 ^
  rijndael-api-fst.c:334:3: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
 *((word32*)iv[2]) = *((word32*)(cipher->IV+ 8));
 ^
  rijndael-api-fst.c:335:3: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
 *((word32*)iv[3]) = *((word32*)(cipher->IV+12));
 ^
  rijndael-api-fst.c:339:5: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
   *((word32*) block) = *((word32*)iv[0]);
   ^
  rijndael-api-fst.c:339:5: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
  rijndael-api-fst.c:340:5: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
   *((word32*)(block+ 4)) = *((word32*)iv[1]);
   ^
  rijndael-api-fst.c:341:5: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
   *((word32*)(block+ 8)) = *((word32*)iv[2]);
   ^
  rijndael-api-fst.c:342:5: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
   *((word32*)(block+12)) = *((word32*)iv[3]);
   ^
  rijndael-api-fst.c: In function 'padDecrypt':
  rijndael-api-fst.c:419:4: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
  ((word32*)block)[0] ^= iv[0];
  ^
  rijndael-api-fst.c:430:3: warning: dereferencing type-punned pointer will 
break strict-aliasing rules [-Wstrict-aliasing]
 ((word32*)block)[0] ^= iv[0];
 ^
  gcc -DINET6 -O2 -Wall -W -Wall -Wwrite-strings -Wbad-function-cast 
-Wmissing-prototypes -Wcast-qual -Wmissing-declarations -DHAVE_CONFIG_H  -fPIC 
-c sdp.c -o sdp.lo
  sdp.c: In function 'sdp_handle_session_key':
  sdp.c:90:19: warning: format '%a' expects argument of type 'float *', but 
argument 3 has type 'char **' [-Wformat=]
   sscanf(value, "%as %as %ld %as %as %as\n", 
 ^
  sdp.c:90:19: warning: format '%a' expects argument of type 'float *', but 
argument 4 has type 'char **' [-Wformat=]
  sdp.c:90:19: warning: format '%a' expects argument of type 'float *', but 
argument 6 has type 'char **' [-Wformat=]
  sdp.c:90:19: warning: format '%a' expects argument of type 'float *', but 
argument 7 has type 'char **' [-Wformat=]
  sdp.c:90:19: warning: format '%a' expects argumen

Bug#821892: pycountry: FTBFS: tests/test_general.py:28: AssertionError

[Chris Lamb]

Source: pycountry
Version: 1.8+ds1-0.1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

pycountry fails to build from source in unstable/amd64:

  [..]

  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'pycountry-build-deps' in 
'../pycountry-build-deps_1.8+ds1-0.1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package pycountry-build-deps.
  (Reading database ... 22998 files and directories currently installed.)
  Preparing to unpack pycountry-build-deps_1.8+ds1-0.1_all.deb ...
  Unpacking pycountry-build-deps (1.8+ds1-0.1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
iso-codes python-py python-pytest python-setuptools python3-pkg-resources
python3-py python3-pytest python3-setuptools unzip
  Suggested packages:
isoquery subversion python-pytest-xdist python-mock python-setuptools-doc
zip
  The following NEW packages will be installed:
iso-codes python-py python-pytest python-setuptools python3-pkg-resources
python3-py python3-pytest python3-setuptools unzip
  0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 3376 kB of archives.
  After this operation, 21.1 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 unzip amd64 6.0-20 
[161 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 python-setuptools all 
20.7.0-1 [202 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 python3-pkg-resources 
all 20.7.0-1 [111 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 python3-setuptools 
all 20.7.0-1 [121 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 python-py all 
1.4.31-1 [81.8 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 python-pytest all 
2.9.1-1 [166 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 python3-py all 
1.4.31-1 [81.9 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 python3-pytest all 
2.9.1-1 [166 kB]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 iso-codes all 3.67-1 
[2285 kB]
  Fetched 3376 kB in 0s (49.2 MB/s)
  Selecting previously unselected package unzip.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23002 files and directories currently installed.)
  Preparing to unpack .../unzip_6.0-20_amd64.deb ...
  Unpacking unzip (6.0-20) ...
  Selecting previously unselected package python-setuptools.
  Preparing to unpack .../python-setuptools_20.7.0-1_all.deb ...
  Unpacking python-setuptools (20.7.0-1) ...
  Selecting previously unselected package python3-pkg-resources.
  Preparing to unpack .../python3-pkg-resources_20.7.0-1_all.deb ...
  Unpacking python3-pkg-resources (20.7.0-1) ...
  Selecting previously unselected package python3-setuptools.
  Preparing to unpack .../python3-setuptools_20.7.0-1_all.deb ...
  Unpacking python3-setuptools (20.7.0-1) ...
  Selecting previously unselected package python-py.
  Preparing to unpack .../python-py_1.4.31-1_all.deb ...
  Unpacking python-py (1.4.31-1) ...
  Selecting previously unselected package python-pytest.
  Preparing to unpack .../python-pytest_2.9.1-1_all.deb ...
  Unpacking python-pytest (2.9.1-1) ...
  Selecting previously unselected package python3-py.
  Preparing to unpack .../python3-py_1.4.31-1_all.deb ...
  Unpacking python3-py (1.4.31-1) ...
  Selecting previously unselected package python3-pytest.
  Preparing to unpack .../python3-pytest_2.9.1-1_all.deb ...
  Unpacking python3-pytest (2.9.1-1) ...
  Selecting previously unselected package iso-codes.
  Preparing to unpack .../iso-codes_3.67-1_all.deb ...
  Unpacking iso-codes (3.67-1) ...
  Processing triggers for mime-support (3.59) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up unzip (6.0-20) ...
  Setting up python-setuptools (20.7.0-1) ...
  Setting up python3-pkg-resources (20.7.0-1) ...
  Setting up python3-s

Bug#821896: RFP: golang-github-jroimartin-gocul -- Go library for creating console user interfaces

[Daniel Stender]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: pkg-go-maintain...@lists.alioth.debian.org
Control: block 820614 by -1


* Package name: golang-github-jroimartin-gocul
  Version : 0.2.0
  Upstream Author : Roi Martin 
* URL : https://github.com/jroimartin/gocui
* License : BSD-3-Clause
  Programming Lang: Go
  Description : Go library for creating console user interfaces

Minimalist Go package aimed at creating console user interfaces.

This a requirement for vuls.

Thanks,
DS

Bug#821183: FW: [Samba] FW: Domain member seems to work, wbinfo -u not (update10)

[L . P . H . van Belle]

Hai again. 


Today i did some new test. 
The trick below ( previous e-mail), works sometime with 4.2.10 and 4.3.8 

The trick works always with 4.4.2

 

My own deb build not installed from source and tested now on 3 servers. 

All same result. 

I checked out the server i did yesterday, still working without any problems. 

 

So im wondering whats the difference between 4.2.10 4.3.8 4.4.1. 

in the debian packages and my debian build of 4.4.2 

 

The 4.4.2 build i made was the source from samba.org. 

I took the "debian" folder from 4.4.1 and added this in the source samba 4.4.2. 

i removed only one patch, since that is in 4.4.2 from source.

Patch:  security-2016-04-12-prerequisite-v4-4-regression-fixes.metze01.txt 

 

I did rebuild tevent ldb tdb talloc etc from debian sid. 

 

And now i cant make it fail again undepended of the settings. 

 

I hope this helps someone. 

 

Greetz, 

 

Louis

 

 

> -Oorspronkelijk bericht-

> Van: samba [mailto:samba-boun...@lists.samba.org] Namens L.P.H. van Belle

> Verzonden: dinsdag 19 april 2016 15:11

> Aan: sa...@lists.samba.org

> Onderwerp: Re: [Samba] FW: Domain member seems to work, wbinfo -u not

> (update8)( solved maybe?)

> 

> Ok.

> New test, debian samba 4.2.10 ( all stock debian packages )

> 

> So others with 4.2.10 stock debian packages, please test also if below

> works.

> 

> 

> The file server on which (wbinfo -u) worked saterday, and not on Sunday

> until now.

> 

> 

> None of these three settings below are in the config and wbinfo -u fails.

> 

> 

> Now adding these settings !! one at the time !!

> And i reloaded samba and restarted winbind every time.

> 

> 

> 

>     client ldap sasl wrapping = plain

>     client ldap sasl wrapping = seal

>     client ldap sasl wrapping = sign

> 

> Result in the end.

> 

> 

> I started with plain, wbinfo -u works, but first time a long delay before

> i see the output, ( long is +4-5 sec)

> 

> Changed it to seal, wbinfo -u works

> 

> 

> And back to the samba default "sign" which now also works.

> So seems fixed now. Strange..

> 

> 

> 

> Removed the client ldap sasl wrapping from the config.

> All still works.

> 

> 

> 

> I'll check this server tomorrow again.

> 

> 

> 

> 

> 

> Greetz,

> 

> 

> 

> Louis

> 

> 

> 

> 

> 

> > -Oorspronkelijk bericht-

> 

> > Van: samba [mailto:samba-boun...@lists.samba.org] Namens L.P.H. van

> Belle

> 

> > Verzonden: dinsdag 19 april 2016 12:48

> 

> > Aan: sa...@lists.samba.org

> 

> > Onderwerp: Re: [Samba] FW: Domain member seems to work, wbinfo -u not

> 

> > (update7)

> 

> >

> 

> > @Patrick Thanks, that helped.

> 

> > @Mathias, only 10.000 objects.

> 

> >

> 

> > >>  client ldap sasl wrapping = plain  <<

> 

> >

> 

> > I've tested that on my members.

> 

> > 4.2.10

> 

> > 4.3.8

> 

> > 4.4.1

> 

> > 4.4.2

> 

> > wbinfo -u now work.

> 

> >

> 

> > Ok tested all 3 options of that settings.

> 

> > Tested als in the order, plain seal sign

> 

> >

> 

> > Samba 4.2.10 (debian stable)

> 

> >    client ldap sasl wrapping = plain   wbinfo -u works.

> 

> >    client ldap sasl wrapping = seal  wbinfo -u fails

> 

> >    client ldap sasl wrapping = sign  wbinfo -u fails

> 

> > only plain works, en keeps working.

> 

> >

> 

> >

> 

> > Other server.

> 

> > Version 4.4.2-LvB ( samba.org packages, own deb, based on debian 4.4.1 )

> 

> > Default it fails, now the funny part.

> 

> > ( default samba setting is sign )

> 

> > We start with a NOT working wbinfo -u.

> 

> >

> 

> > Test with following changes.

> 

> > Try1) client ldap sasl wrapping = plain  wbinfo -u works.

> 

> > Try2) client ldap sasl wrapping = seal wbinfo -u also works now.

> 

> > Try3) client ldap sasl wrapping = sign wbinfo -u also works now.

> 

> >

> 

> > Only the 4.4.2 now keeps working independed of the setting.

> 

> > Lunch first, i'll test the 4.3.8 also.

> 

> >

> 

> >

> 

> > Greetz,

> 

> >

> 

> > Louis

> 

> >

> 

> >

> 

> >

> 

> > > -Oorspronkelijk bericht-

> 

> > > Van: samba [mailto:samba-boun...@lists.samba.org] Namens Patrick G.

> 

> > > Stoesser

> 

> > > Verzonden: dinsdag 19 april 2016 12:21

> 

> > > Aan: sa...@lists.samba.org

> 

> > > Onderwerp: Re: [Samba] After Update to 4.2, Samba is unusuable as

> member

> 

> > > server / No user and goup resolution

> 

> > >

> 

> > > Hello,

> 

> > >

> 

> > > a reply in debianforum.de led me to:

> 

> > >

> 

> > > client ldap sasl wrapping = plain

> 

> > >

> 

> > > and with that setting at least wbinfo works.

> 

> > >

> 

> > > But still my problems are not completely gone: On the filesystem

> level,

> 

> > > AD users and groups are still not resolved. "Invalid user". But kinit

> 

> > > "USER" works. Still have to try...

> 

> > >

> 

> > > Regards, pgs

> 

> > >

> 

> > >

> 

> > > Am 16.04.2016 um 19:08 schrieb Patrick G. Stoesser:

> 

> > > > Hello ev

Bug#821895: ferm - Fails to load rules of /var/cache is read-only

[Bastian Blank]

Package: ferm
Version: 2.2-3.2
Severity: grave

ferm fails to load any rules in the init-script if /var/cache is
read-only.

Bastian

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

Kernel: Linux 4.4.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 ferm depends on:
ii  debconf  1.5.59
ii  init-system-helpers  1.29
ii  iptables 1.6.0-2
ii  lsb-base 9.20160110
ii  perl 5.22.1-9

Versions of packages ferm recommends:
ii  libnet-dns-perl  1.05-1

ferm suggests no packages.

-- Configuration Files:
/etc/ferm/ferm.conf changed [not included]

-- debconf information excluded

Bug#821793: python-llfuse: FTBFS in testing

[Santiago Vila]

affects 821793 python-llfuse
thanks

On Tue, 19 Apr 2016, Nikolaus Rath wrote:

> [...]
> I don't want to dodge the issue, but I think reassigning to "fuse" is
> really the only thing I can do.

Seems ok to me.

I'm using an "affects" as well so that this bug shows in the page for
python-llfuse. This way I will remember not to report it again
next time the package FTBFS.

Thanks.

Bug#770671: redis-server: warning in postinst

[Ricardo F.]

 

Dear Maintainer, 

Please, remove from "debian/redis-server.dirs" the line
"/var/lib/redis". 

Actually, this directory is created before executing "adduser" in
"redis-server.postinst", this command try to create the home dir
"/var/lib/redis" and check the owner, as it owned by root and not by the
new user, it fails. 

Thanks, 
  

Bug#821897: RFP: golang-github-rifflock-lfshook -- local filesystem hook for logrus (Go library)

[Daniel Stender]

Package: wnpp
Severity: wishlist
Control: block 820614 by -1

* Package name: golang-github-rifflock-lfshook
  Version : 1.0
  Upstream Author : Michael Riffle 
* URL : https://github.com/rifflock/lfshook
* License : None yet
  Programming Lang: Go
  Description : local filesystem hook for logrus (Go library)

Sometimes developers like to write directly to a file on the filesystem. This is
a hook for logrus designed to allow users to do just that. The log levels are
dynamic at instanciation of the hook, so it is capable of logging at some or all
levels.

No licensing statement yet, but I've requested it (issue #4). I'll proceed 
filing
this RFP to complete the list of blocks for vuls.

Thanks,
DS

Bug#821424: pulseaudio: Do not put normal users on group audio

[Ben Hutchings]

On Tue, 2016-04-19 at 21:52 +0100, Ben Hutchings wrote:
[...]
> - bluetooth:  unknown, seems broken whether or not I'm a member of the group
[...]

The bluetooth group isn't used for device nodes (so far as I can see)
but in the bluez D-Bus policy (/etc/dbus-1/system.d/bluetooth.conf).
That also has an 'allow' rule for users currently logged in locally, so
again it's not necessary to add desktop users to the group.

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained by stupidity.


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

Bug#770671: redis-server: warning in postinst

[Chris Lamb]

> Please, remove from "debian/redis-server.dirs" the line
> "/var/lib/redis". 

This was actually already removed in https://deb.li/3JZSM :)


Regards,

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

Bug#821861: Drop gnome-screenshot from gnome-core

[Dmitry Shachnev]

Hi Michael,

On Wed, Apr 20, 2016 at 02:06:54AM +0200, Michael Biebl wrote:
> GNOME shell has builtin screenshot functionality and gnome-screenshot is
> no longer used.
> We should therefor drop it from the gnome-core meta package.
>
> The gnome-flashback session probably still want's to pull it in.
> CCing mity...@debian.org

GNOME Flashback is compatible with GNOME Shell: it implements the
org.gnome.Shell.Screenshot D-Bus interface, and gnome-settings-daemon can
use it. So no objections from me _here_.

However, I still find gnome-screenshot very useful: it allows one to set
timeout before screenshot, include/exclude window border, set an effect,
and also has an --interactive mode: much more than what one can achieve
with bare gnome-settings-daemon keybindings.

Also, according to a recent upstream commit [1], they still consider
gnome-screenshot a compulsory part of GNOME. Shall we really drop it?

[1]: https://git.gnome.org/browse/gnome-screenshot/commit/?id=ecf415fd7723fd08

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#821898: opendkim: incompatible SSL versions

[Vincent Lefevre]

Package: opendkim
Version: 2.10.3-3+b1
Severity: grave
Justification: renders package unusable

During an upgrade:

[...]
update-initramfs: Generating /boot/initrd.img-4.2.0-1-amd64
Errors were encountered while processing:
 opendkim
==  How can you help?  (doc: https://wiki.debian.org/how-can-i-help ) ==

-  Show old opportunities as well as new ones: how-can-i-help --old  -
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up opendkim (2.10.3-3+b1) ...
Starting OpenDKIM: opendkim: incompatible SSL versions (library = 0x01000203f, 
filter = 01000204f)
invoke-rc.d: initscript opendkim, action "start" failed.
dpkg: error processing package opendkim (--configure):
 subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
 opendkim

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

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

Versions of packages opendkim depends on:
ii  adduser  3.114
ii  dns-root-data2015052300+h+1
ii  init-system-helpers  1.29
ii  libbsd0  0.7.0-2
ii  libc62.22-7
ii  libdb5.3 5.3.28-11
ii  libldap-2.4-22.4.42+dfsg-2
ii  liblua5.1-0  5.1.5-8
ii  libmemcached11   1.0.18-4
ii  libmemcachedutil21.0.18-4
ii  libmilter1.0.1   8.14.9-4
ii  libopendbx1  1.4.6-9
ii  libopendkim102.10.3-3
ii  librbl1  2.10.3-3
ii  libssl1.0.2  1.0.2g-1
ii  libunbound2  1.4.22-3
ii  libvbr2  2.10.3-3
ii  lsb-base 9.20150917

opendkim recommends no packages.

Versions of packages opendkim suggests:
ii  opendkim-tools  2.10.3-3+b1
pn  unbound 

-- Configuration Files:
/etc/dkimkeys/README.PrivateKeys [Errno 13] Permission denied: 
u'/etc/dkimkeys/README.PrivateKeys'

-- no debconf information

Bug#763352: adduser: Warning: The home directory `/var/lib/polkit-1' does not belong to the user you are currently creating.

[Ricardo F.]

 

Dear Maintainer, 

Some time ago (policykit-1 (0.94-1) - Sun, 27 Sep 2009) remove the use
of adduser as the changelog register "- Drop dependency on adduser.". 

Since it returned to the "policykit-1.postinst" script, the file
"policykit-1.dirs" define the same home directory that adduser try to
create, but it fails because in the installation, this directory is
created with root due the "policykit-1.dirs" definition. 

As "policykit-1.dirs" only have one line with "var/lib/polkit-1/", this
bug can be solved removing the file. 

Thanks, 
  

Bug#821760: Please pull in xserver-xorg-input-libinput

[Julien Cristau]

On Tue, Apr 19, 2016 at 04:26:30 +0200, Michael Biebl wrote:

> Package: xserver-xorg-input-all
> Version: 1:7.7+14
> Severity: normal
> 
> Hi,
> 
> GNOME 3.20 has dropped support for non-libinput mouse configurations [1]
> So any configuration changes you make in gnome-control-center won't have
> any effect unless xserver-xorg-input-libinput is installed, e.g. my
> tap-to-click touchpad settings had no effect otherwise [2]
> 
> We quickly discussed this issue on #debian-gnome IRC where I suggested
> that we let one of the GNOME packages pull in
> xserver-xorg-input-libinput.
> 
> pochu mentioned that doing this via xserver-xorg-input-all might be
> nicer. What's the state of xserver-xorg-input-libinput, Timo? Do you
> consider it ready for the masses and do we want to have it installed
> (and enabled) by default?
> 
I don't know the answer to that question, but if the answer is no, then
it shouldn't be pulled in by gnome either...

Cheers,
Julien

Bug#815162: xserver-xorg-legacy: completely broken (locks up input / xf86OpenConsole: Cannot open virtual console)

[Julien Cristau]

On Sun, Apr 17, 2016 at 06:24:31 +0200, Jan Braun wrote:

> Control: unmerge -1
> Control: severity -1 important
> Control: tag -1 - moreinfo
> Control: retitle -1 xserver-xorg-legacy: locks up input when used with 
> neither libpam-systemd nor manual configuration
> 
> Jan Braun schrob:
> > If you want to downgrade (and merge with #814313), I won't object, but
> > I'll not do that myself because dataloss failure mode and apt-listbugs
> > visibility.
> 
> Sorry, but you merged with #814394 (wishlist moreinfo), not #814313
> (important). If you actually think this bug is a wishlist and/or needs
> more info, please explain.
> 
This is not a bug.  If you ignore the Recommends on libpam-systemd, you
need manual configuration to make things not broken.

Cheers,
Julien

Bug#821899: RFP: golang-github-lackstack-echo -- HTTP server framework for Google Go

[Daniel Stender]

Package: wnpp
Severity: wishlist
Control: block 820615 by -1

* Package name: golang-github-lackstack-echo
  Version : 1.4
  Upstream Author : Vishal Rana 
* URL : https://github.com/labstack/echo
* License : Expat
  Programming Lang: Go
  Description : HTTP server framework for Google Go

Echo is a fast and unfancy HTTP server framework for Go (Golang).

This is a requirement for go-cve-dictionary.

Thanks,
DS

Bug#821900: apt: changelog lookup in incorrect location, hence fails to find it

[Georg Bauhaus]

Package: apt
Version: 1.0.9.8.3
Severity: normal

Dear Maintainer,


   * What led up to the situation?

# apt-get upgrade

It listed the new packages in the usual fashion, including openssh-server,
which in particular suggests to me that I should look at the changelog.

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

$ apt-get changelog openssh-server

   * What was the outcome of this action?

$ apt-get changelog openssh-server
Err Changelog for openssh-server 
(http://packages.debian.org/changelogs/pool/updates/main/o/openssh/openssh_6.7p1-5+deb8u2/changelog)
  404  Not Found [IP: 5.153.231.3 80]
Err Changelog for openssh-server 
(http://security.debian.org/pool/updates/main/o/openssh/openssh_6.7p1-5+deb8u2.changelog)
  404  Not Found [IP: 195.20.242.89 80]
E: changelog download failed

   * What outcome did you expect instead?

To see the changelog. I noticed that the changelog file for 
openssh_6.7p1-5+deb8u1 (note: u1)
on the web is both at a "redirected" site and under a different path, so maybe 
some of apt or
a changelog placement script is uninformed about where the other would write or
where the other should look in this case?  I notice that "changelog not found" 
is not a new
problem either, but maybe the site redirection is, or the inclusion of security 
host's paths
in this scheme?
 apt(8) is a core tool and in this state suggests to the administrator to bye a 
pig in
a poke even when he or she should install security updates such as openssh.



-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-image-3\.2\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-headers-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-headers-3\.2\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-3\.2\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-3\.2\.0-4-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-3\.2\.0-4-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-3\.2\.0-4-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-3\.2\.0-4-amd64$";
APT::NeverAutoRemove:: "^.*-modules-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^.*-modules-3\.2\.0-4-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-3\.2\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.2\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-tools-3\.16\.0-4-amd64$";
APT::NeverAutoRemove:: "^linux-tools-3\.2\.0-4-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Never-MarkAuto-Sections:: "oldlibs";
APT::Never-MarkAuto-Sections:: "restricted/oldlibs";
APT::Never-MarkAuto-Sections:: "universe/oldlibs";
APT::Never-MarkAuto-Sections:: "multiverse/oldlibs";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "1";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "2";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-9n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::bzip2 "";
APT::Compressor::bzip2::Name "bzip2";
APT::Compressor::bzip2::Extension ".bz2";
APT::Compressor::bzip2::Binary "bzip2";
APT::Compressor::bzip2::Cost "3";
APT::Co

Bug#821389: xinput: please support distinct device IDs

[Julien Cristau]

On Mon, Apr 18, 2016 at 13:40:31 +0200, Harald Dunkel wrote:

> Package: xinput
> Version: 1.6.1-1
> 
> Seems that xinput doesn't really know how to identify
> the devices, either. Sample session:
> 
> % xinput list-props "Logitech USB Receiver"
> Warning: There are multiple devices matching 'Logitech USB Receiver'.
> To ensure the correct one is selected, please use the device ID, or prefix the
> device name with 'pointer:' or 'keyboard:' as appropriate.
> 
> unable to find device Logitech USB Receiver
> 
I don't think there's an xinput bug here.  xinput just doesn't have any
more information about the devices...

Cheers,
Julien

Bug#821901: RFP: golang-github-google-subcommands -- a subcommand library for Google Go

[Daniel Stender]

Package: wnpp
Severity: wishlist
Control: block 820615 by -1

* Package name: golang-github-google-subcommands
  Version : 0.0~git20160309.1c71737
  Upstream Author : Andrew Jackura 
* URL : https://github.com/google/subcommands
* License : Apache-2.0
  Programming Lang: Go
  Description : a subcommand library for Google Go

Subcommands is a Go package that implements a simple way for a single command 
to have
many subcommands, each of which takes arguments and so forth. This is not an 
official
Google product.

This a requiremet for go-cve-dictionary.

Thanks,
DS

Bug#821902: Incorrect test for nativeness of binary packages

[Ben Hutchings]

Package: lintian
Version: 2.5.43
Severity: normal
Tags: patch

The binary packages built from linux-signed currently elicit the
debian-changelog-file-missing-or-wrong-name warning, although they do
include a changelog.gz.  lintian expects any binary package whose
version contains a '-' to be non-native and therefore have a
changelog.Debian.gz.  It should be checking whether the *source*
version contains a '-'.

The following patch fixes this.

Ben.

--- a/lib/Lintian/Collect/Binary.pm
+++ b/lib/Lintian/Collect/Binary.pm
@@ -88,7 +88,7 @@
 =item native
 
 Returns true if the binary package is native and false otherwise.
-Nativeness will be judged by its version number.
+Nativeness will be judged by the source version number.
 
 If the version number is absent, this will return false (as
 native packages are a lot rarer than non-native ones).
@@ -100,7 +100,13 @@
 sub native {
 my ($self) = @_;
 return $self->{native} if exists $self->{native};
-my $version = $self->field('version');
+my $version;
+my $source = $self->field('source');
+if (defined $source && $source =~ m/\((.*)\)/) {
+$version = $1;
+} else {
+$version = $self->field('version');
+}
 if (defined $version) {
 $self->{native} = ($version !~ m/-/);
 } else {
--- END ---

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

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

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

Versions of packages lintian recommends:
ii  dpkg 1.18.4
ii  libautodie-perl  2.29-2
ii  libperlio-gzip-perl  0.19-1+b1
ii  perl 5.22.1-9
ii  perl-modules-5.22 [libautodie-perl]  5.22.1-9

Versions of packages lintian suggests:
ii  binutils-multiarch 2.26-8
ii  dpkg-dev   1.18.4
ii  libhtml-parser-perl3.72-1
ii  libtext-template-perl  1.46-1

-- debconf-show failed

Bug#820589: jessie-pu: package opam/1.2.0-1+deb8u1

[Julien Cristau]

Control: tags -1 confirmed

On Mon, Apr 11, 2016 at 00:57:58 +0200, Mehdi Dogguy wrote:

> Hi,
> 
> On 10/04/2016 17:27, Julien Cristau wrote:
> >> --- a/debian/changelog
> >> +++ b/debian/changelog
> >> @@ -1,3 +1,10 @@
> >> +opam (1.2.0-1+deb8u1) jessie; urgency=medium
> >> +
> >> +  * Stop using insecure and no-check-certificate flags when fetching
> >> +files using wget and curl.
> >> +
> > 
> > Missing "closes:"?
> > 
> 
> Fixed in attached new diff.
> 
Looks fine, thanks.

Cheers,
Julien

Bug#816076: wicd-daemon: upgrade reconfigures static ethernet interface, and kills ssh sessions.

[Vincent Lefevre]

On 2016-02-27 19:48:48 +1100, Andrew Vaughan wrote:
> My home server is a headless box, administered from a vnc session tunnelled
> over ssh.  It has no wifi adaptor, just a single ethernet port that is
> statically configured via /etc/network/interfaces.
> 
> During today's package update my ssh connection died partway through, during
> setup of wicd-daemon.  Last line was "Installing new version of config file
> /etc/wicd/encryption/templates/wpa2-peap ..."
> 
> Then ssh refused to re-connect.
> 
> I finally got re-connected after discovering that wicd-daemon had
> reconfigured eth0 to a different ip address.

Probably the same bug as bug 557156 (from 2009!). The problem is that
wicd-daemon tries to reconfigure the ethernet interface even though
it is configured not to connect to it automatically (which should be
and is the default). A workaround is to remove eth0 from the wicd
configuration.

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

Bug#821903: ITP: fbless -- terminal fiction book reader

[Dmitry Bogatov]

Package: wnpp
Severity: wishlist
Owner: Dmitry Bogatov 

* Package Name : fbless
  Version  : 0.2.3
  Upstream Author  : Con Radchenko 
  Url  : https://github.com/matimatik/fbless
  License  : GPL-2+
  Programming Lang : Python
  Description  : terminal fiction book reader

 Fbreader is ncurses fiction book (.fb2) reader with following
 features:
 .
 * customizable color themes
 * last viewed point saving
 * autoscroll mode
 * support for archived books
 * basic links support

I plan to maintain this package myself, keeping debianization
in following Git repository:

https://anonscm.debian.org/cgit/users/kaction-guest/fbless.git

Bug#821904: htop: please add option to "freeze/unfreeze" display

[Karsten Hilbert]

Package: htop
Version: 2.0.1-1
Severity: wishlist
Tags: upstream

I have previously reported a wishlist item for less()ing or tail()ing
files from the list of open files of a process as produced by lsof:

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

This report was tagged WONTFIX on the grounds that showing files goes
beyond the scope of a _process_ viewer. I can agree with this rationale.

However, a typical scenario of (my) htop use is to inspect processes to
find out which (say log-) files they have open -- in order to inspect
the content of those files. I also run gpm courtesy of which I can
copy-paste file paths from htop's lsof screen into another console for
running less on that file. However, while positioning the mouse cursor
for selecting a path to copy-paste the list of open files may change and
thereby the position of the desired path to copy-paste moves away from
under the mouse cursor. This can get rather irritating on processes busy
opening/closing files :-)

Hence my desire to be able to "freeze" InfoScreen instances - after which
they don't auto-refresh anymore until "unfreeze" is commanded.

Makes sense ?

(BTW, this applies to all screens, except the lsof one makes for a good
example)

Thanks for considering,
Karsten

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

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

Versions of packages htop depends on:
ii  libc6 2.22-6
ii  libncursesw5  6.0+20160319-1
ii  libtinfo5 6.0+20160319-1

htop recommends no packages.

Versions of packages htop suggests:
ii  lsof4.89+dfsg-0.1
ii  strace  4.10-3

-- no debconf information

Bug#821905: lynx-cur: accesses network on normal start (privacy violation)

[Thorsten Glaser]

Package: lynx-cur
Version: 2.8.9dev8-4
Severity: important

Despite the setting
* lynx-cur/defaulturl: file:///
lynx accesses the network when started without an URL to navigate to.
Please refer to #721689 for another example when a browser did that
and it was not okay.

The fix is trivial, /etc/lynx-cur/lynx.cfg already contains
#STARTFILE:file://localhost/~/
so you just need to uncomment that and comment the other STARTFILE.


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

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

Versions of packages lynx-cur depends on:
ii  lynx  2.8.9dev8-4

lynx-cur recommends no packages.

lynx-cur suggests no packages.

-- debconf information:
  lynx-cur/etc_lynx.cfg:
* lynx-cur/defaulturl: file:///

Bug#762637: qtile in Debian

[Iain R. Learmonth]

Hi,

Are you still interested in packaging qtile for Debian?

I notice that there is a newer upstream version available, if you can
package this I would be happy to review and upload.

If you're no longer interested in packaging this, I am happy to do the
work, please let me know though.

Thanks,
Iain.

Bug#821906: gbp-dch: generates changelog with too long lines, please break them

[Arturo Borrero Gonzalez]

Package: git-buildpackage
Version: 0.7.3
Severity: normal

Dear Maintainer,

thanks for your work with git-buildpackage, it's really appreciated.

I've found a behaviour which is a bit annoying to me. The `gbp dch' command
generates changelog entries which are too long (longer than 80 chars) and
then a lintian warning will complain.

This happens specially when using '--id-length=7' (which I often use).

Please, break lines at 80 chars to avoid lintian warnings.

thanks, best regards.

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

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

Versions of packages git-buildpackage depends on:
ii  devscripts2.16.2
ii  git   1:2.8.0~rc3-1
ii  man-db2.7.5-1
ii  python-dateutil   2.4.2-1
ii  python-pkg-resources  18.8-1
ii  python-six1.10.0-2
pn  python:any

Versions of packages git-buildpackage recommends:
ii  cowbuilder   0.79
ii  pbuilder 0.223
ii  pristine-tar 1.33
ii  python-requests  2.9.1-2

Versions of packages git-buildpackage suggests:
ii  python-notify  0.1.1-4
ii  sudo   1.8.15-1.1
ii  unzip  6.0-20

-- no debconf information

Bug#821904: htop: please add option to "freeze/unfreeze" display

[Daniel Lange]

lsof screens should only refresh on pressing F5.
The strace screen can be toggled scrolling with F8 and F9 toggles 
tracing on and off.


If you copy & paste from the mail htop screen adding a longer refresh 
delay may help. See man htop (-d option).

Bug#821908: git: Gerrit Pape's email address is not working

[Sandro Tosi]

Package: git
Version: 1:2.1.4-2.1
Severity: serious

Hello,
Gerrit's email is not working:

```
Hi. This is the qmail-send program at a.mx.smarden.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

:
No delivery confirmation received.
```

and even mailing his @debian.org doesnt work

```
Delivery to the following recipient failed permanently:

 p...@debian.org

Technical details of permanent failure:
[8<]

The error that the other server returned was:
550 Please contact the Debian BTS, or try to mail p...@smarden.org
```

(is this even allowed?)

Policy ref: https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer


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

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

Versions of packages git depends on:
ii  git-man   1:2.1.4-2.1
ii  libc6 2.19-18
ii  libcurl3-gnutls   7.43.0-1
ii  liberror-perl 0.17-1.1
ii  libexpat1 2.1.0-6+b3
ii  libpcre3  2:8.35-7
ii  perl-modules-5.22 [perl-modules]  5.22.1-9
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages git recommends:
ii  less 458-3
ii  openssh-client [ssh-client]  1:6.7p1-6
ii  patch2.7.5-1
ii  rsync3.1.1-3

Versions of packages git suggests:
ii  gettext-base  0.19.4-1
pn  git-arch  
pn  git-cvs   
pn  git-daemon-run | git-daemon-sysvinit  
pn  git-doc   
pn  git-el
pn  git-email 
pn  git-gui   
pn  git-mediawiki 
pn  git-svn   
ii  gitk  1:2.1.4-2.1
pn  gitweb

-- no debconf information

Bug#821907: RFS: fbless/0.2.3-1 ITP

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name: fbless
  Version : 0.2.3-1
  Upstream Author : Con Radchenko 
* Url : https://github.com/matimatik/fbless
* Licenses: GPL-2+
  Section : text

It builds those binary packages:

fbless -- terminal fiction book reader

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

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

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

http://mentors.debian.net/debian/pool/main/f/fbless/fbless_0.2.3-1.dsc

Alternatively, you can access package debian/ directory via git from URL:

https://anonscm.debian.org/cgit/users/kaction-guest/fbless.git

More information about fbless can be obtained from 
https://github.com/matimatik/fbless

Changes since last upload:

  * Initial release (Closes: #821903)

Regards,
  Dmitry Bogatov

Bug#821182: “so that one build is done using a 32 bit kernel (686-PAE) and the other build is using a 64 bit kernel”

[Thorsten Glaser]

Hi *,

this is obviously a bug in the buildd setup, because:

tglase@tglase:~ $ uname -m
x86_64
tglase@tglase:~ $ linux32 uname -m
i686

When running a 32-bit system with a 64-bit kernel, one MUST¹ do this:

root@dev:~ # dpkg-divert --list | fgrep init
   
local diversion of /sbin/init to /sbin/init.real
root@dev:~ # cat /sbin/init
#!/bin/mksh-static
exec /usr/bin/linux32 /sbin/init.real "$@"

When running a 32-bit build on a 64-bit system, one MUST invoke
the build tool with linux32 as well, for example:

$ sudo linux32 cowbuilder …

Or “personality=linux32” in /etc/schroot/schroot.conf, as the
already present, commented-out, example shows.

My own packaging of BSD make similarily looks at uname output
to decide for what platform to build, and requires this; bmake
is packaged in Debian too and may or may not require this and/or
may currently have bugs due to this.

bye,
//mirabilos

① leading to a funny situation where I had to add “linux64”
  to the libvirt init script so it recognised the system as amd64,
  but that’s all correct
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Bug#821868: openstack-dashboard: causes trigger loop

[Andreas Beckmann]

On 2016-04-20 09:14, Thomas Goirand wrote:
> The thing is, I am really unsure how this happened, and how to fix. Help
> would be appreciated a lot. Could you provide the full piuparts command
> line, so I can reproduce the issue?

at the beginning of the logfile, after the dump of the Packages entries
of the packages involved


Andreas

Bug#821119: Fw: Change build mechanism for sk [ Re: Debian refcard: call to update translations ]

[victory]

On Tue, 19 Apr 2016 20:59:25 +0200
Holger Wansing wrote:
> victory wrote:

> > wrong translations: original is missing;
> > no translators info: original is there but no translators' ones
> > broken: entire pdf is broken or out of space; original is not completed
> > OK: both of original and translators' exists; translators' info may be wrong

> > base, Makefile patch applied (same results):
> >   wrong translations:cs,he,zh_CN
> >   no translators 
> > info:ar,da,el,es,eu,gl,hi,hu,it,ja,lt,ml,ms,pl,pt_BR,sk,sv,tr,zh_TW
> >   broken:bg,ca,de,fi,fr,nb,nl,pt,ro,ru,uk,vi
> >   OK: [none]

> > fo.xsl patch applied, fo.xsl and Makefile patches applied (same results):
> >   wrong translations:cs,he,zh_CN
> >   no translators info:ar,da,el,es,hu,ml,
> >   broken:bg,ca,de,fi,fr,nb,nl,pt,ro,ru,uk,vi
> >   OK:eu,gl,hi,it,ja,lt,ms,pl,pt_BR,sk,sv,tr,zh_TW

> > so ..., at least on my env,
> > the Makefile patch didn't make significant improvement from this POV

> > about the patch:
> > fo.xsl is used *after* preproc.xsl,
> >  so here no need to exclude the dummy 3rd item in en,
> >  just need to wrap each of them in a block to separate

> I am very sorry, but me personally I am completely lost with your mail.

current fo.xsl deals with only first 2 ... clauses,
so the result pdfs never had 3rd and later.

with the fo.xsl patch, assumed the translation has it,
 correctly represents each one ... clause per a line
([eu,gl,hi,it,ja,lt,ms,pl,pt_BR,sk,sv,tr,zh_TW] are the case)

> I cannot understand, what you did, which files you watched (with a
> webbrowser !), and what is so much broken...

http://debian.blog.bbiq.jp/refcard20160420.tbz
note: r11106 + updated ja; latest fr update is not incorporated

> With my patch included with this bug, I only changed the cs.po and
> el.po and sk.po files. 
> So I am unable so see, why this should break so much files or translations.

no.
your patch broke nothing;
just did not make significant improvement from the POV
broken files are broken regardless of your patch applied or not

note: lt version of fr translations is not broken
  but a4 version is broken

if you still cannot understand, never mind and ignore it
I'm not in trouble with it in any way

-- 
victory
no need to CC me :-)

Bug#819153: libreoffice: LibreOffice crashes when trying to edit diagrams: "does not expose __driDriverGetExtensions_swrast()"

[Leon Winter]

Package: libreoffice
Version: 1:5.1.2-3
Followup-For: Bug #819153

Bug still persists in latest version shipped in Debian testing.

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

Kernel: Linux 3.17.8-64+ (SMP w/32 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libreoffice depends on:
ii  dpkg 1.18.4
ii  fonts-dejavu 2.35-1
ii  fonts-sil-gentium-basic  1.1-7
ii  libreoffice-avmedia-backend-vlc  1:5.1.2-3
ii  libreoffice-base 1:5.1.2-3
ii  libreoffice-calc 1:5.1.2-3
ii  libreoffice-core 1:5.1.2-3
ii  libreoffice-draw 1:5.1.2-3
ii  libreoffice-impress  1:5.1.2-3
ii  libreoffice-java-common  1:5.1.2-3
ii  libreoffice-math 1:5.1.2-3
ii  libreoffice-report-builder-bin   1:5.1.2-3
ii  libreoffice-writer   1:5.1.2-3
ii  python3-uno  1:5.1.2-3

Versions of packages libreoffice recommends:
ii  fonts-liberation  1.07.4-1
ii  libpaper-utils1.1.24+nmu4

Versions of packages libreoffice suggests:
pn  cups-bsd
ii  default-jre [java5-runtime] 2:1.8-57
pn  gstreamer1.0-libav  
ii  gstreamer1.0-plugins-bad1.8.0-1+b1
ii  gstreamer1.0-plugins-base   1.8.0-1
ii  gstreamer1.0-plugins-good   1.8.0-1+b1
pn  gstreamer1.0-plugins-ugly   
ii  hunspell-en-us [hunspell-dictionary]20070829-6
ii  hyphen-de [hyphen-hyphenation-patterns] 1:5.1.2-1
ii  icedove 38.6.0-1
ii  iceweasel   38.7.0esr-1~deb8u1bfw1
ii  imagemagick 8:6.8.9.9-7+b1
ii  libgl1-mesa-glx [libgl1]11.1.2-1
pn  libreoffice-gnome | libreoffice-kde 
pn  libreoffice-grammarcheck
ii  libreoffice-help-de [libreoffice-help-5.1]  1:5.1.2-3
ii  libreoffice-l10n-de [libreoffice-l10n-5.1]  1:5.1.2-3
pn  libreoffice-officebean  
ii  libsane 1.0.23-3+b1bfw1
ii  libxrender1 1:0.9.9-2
ii  myspell-de-de [myspell-dictionary]  20160407-1
ii  mythes-de [mythes-thesaurus]20120516-2
pn  openclipart2-libreoffice | openclipart-libreoffice  
ii  openjdk-6-jre [java5-runtime]   6b35-1.13.7-1
ii  openjdk-7-jre [java5-runtime]   7u91-2.6.3-1
ii  openjdk-8-jre [java5-runtime]   8u72-b15-4
ii  pstoedit3.70-1
pn  unixodbc

Versions of packages libreoffice-core depends on:
ii  fontconfig2.11.0-6.3
ii  fonts-opensymbol  2:102.7+LibO5.1.1-1
ii  libboost-date-time1.58.0  1.58.0+dfsg-5+b1
ii  libc6 2.21-9bfw1
ii  libcairo2 1.14.6-1
ii  libclucene-contribs1v52.3.3.4-4.1
ii  libclucene-core1v52.3.3.4-4.1
ii  libcmis-0.5-5v5   0.5.1-2
ii  libcups2  2.1.3-5
ii  libcurl3-gnutls   7.47.0-1
ii  libdbus-1-3   1.10.6-1bfw1
ii  libdbus-glib-1-2  0.106-1
ii  libdconf1 0.26.0-1
ii  libeot0   0.01-3
ii  libexpat1 2.1.0-7
ii  libexttextcat-2.0-0   3.4.4-1
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.6.3-3
ii  libgcc1   1:5.3.1-14bfw1
ii  libgl1-mesa-glx [libgl1]  11.1.2-1
ii  libglew1.13   1.13.0-2
ii  libglib2.0-0  2.46.2-3
ii  libgltf-0.0-0v5   0.0.2-4+b1
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgraphite2-31.3.7-1
ii  libharfbuzz-icu0  1.0.1-1+b1
ii  libharfbuzz0b 1.0.1-1+b1
ii  libhunspell-1.3-0 1.3.3-4
ii  libhyphen02.8.8-2
ii  libice6   2:1.0.9-1+b1
ii  libicu55  55.1-7
ii  libjpeg62-turbo   1:1.4.2-2
ii  liblangtag1   0.5.7-2
ii  liblcms2-22.6-3+b3
ii  libldap-2.4-2 2.4.42+dfsg-2+b2
ii  libmythes-1.2-0   2:1.2.4-1
ii  libneon27-gnutls  0.30.1-3
ii  libnspr4  2:4.12-1
ii  libnspr4-0d   2:4.12-1
ii  libnss3   2:3.23-1
ii  libnss3-1d2:3.23-1
ii  libodfgen-0.1-1   0.1.6-1
ii  libpcre3  2:8.38-3
ii  libpng16-16   1.6.21-2
ii  librdf0   1.0.

Bug#821909: pki-base: fails to install, remove, and install again

[Andreas Beckmann]

Package: pki-base
Version: 10.2.6+git20160317-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install,
remove (but not purge), and install again.
Before the second installation the package is in config-files-remaining
state. The configuration is remaining from the last version that was
successfully configured - which is the same version that is going to be
installed again.

Like a plain failure on initial install this makes the package too buggy
for a release, thus the severity.

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

  Selecting previously unselected package pki-base.
  (Reading database ... 
(Reading database ... 12821 files and directories currently installed.)
  Preparing to unpack .../pki-base_10.2.6+git20160317-1_amd64.deb ...
  Unpacking pki-base (10.2.6+git20160317-1) ...
  Setting up pki-base (10.2.6+git20160317-1) ...
  dpkg: error processing package pki-base (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   pki-base


cheers,

Andreas


pki-base_10.2.6+git20160317-1.log.gz
Description: application/gzip

Bug#821272: rkt: Can't run docker images

[Iago López Galeiras]

Hi!

Have you tried running the images with the "--no-overlay" option?

E.g:

$ sudo rkt run --no-overlay docker://busybox --interactive

Cheers.

On Tue, Apr 19, 2016 at 11:27 PM Nicolas Le Cam  wrote:
>
> Hi Alban, Dmitry,
>
> Thanks for your feedback.
>
> Default umask is 0022
> I'm using an ext4 FS
>
> running busybox image returns different errors :
> $ sudo rkt fetch --insecure-options=image docker://busybox
> image: remote fetching from URL "docker://busybox"
> Downloading sha256:385e281300c: [==] 676 KB/676 KB
> Downloading sha256:a3ed95caeb0: [==] 32 B/32 B
> sha512-cdb74a334f97f442a4da5230610ccf46
> $ sudo rkt run --interactive docker://busybox --exec bash
> image: using image from file /usr/lib/rkt/stage1-host.aci
> image: using image from local store for url docker://busybox
> networking: loading networks from /etc/rkt/net.d
> networking: loading network default with type ptp
> stage1: failed to write default.target: open
> stage1/rootfs/usr/lib/systemd/system/default.target: operation not
> permitted
> $ sudo rkt run --interactive docker://busybox --exec bash
> image: using image from file /usr/lib/rkt/stage1-host.aci
> image: using image from local store for url docker://busybox
> stage0: error setting up app image: open
> /var/lib/rkt/pods/run/9ba6840a-96d5-493f-8c2d-434184c689c9/stage1/rootfs/opt/stage2/busybox/manifest:
> operation not permitted
> $ sudo rkt run --interactive docker://busybox --exec bash
> image: using image from file /usr/lib/rkt/stage1-host.aci
> image: using image from local store for url docker://busybox
> networking: loading networks from /etc/rkt/net.d
> stage1: failed to setup network: open
> stage-1/rootfs/etc/rkt/net.d/99-default.conf: operation not permitted
>
> Also tried with alpine, same error :
> $ sudo rkt fetch --insecure-options=image docker://alpine
> image: remote fetching from URL "docker://alpine"
> Downloading sha256:420890c9e91: [==] 2.32 MB/2.32 
> MB
> sha512-e738eac1830750ac3fcd152b3c83bf75
> $ sudo rkt run --interactive docker://alpine --exec bash
> image: using image from file /usr/lib/rkt/stage1-host.aci
> image: using image from local store for url docker://alpine
> stage0: error setting up app image: open
> /var/lib/rkt/pods/run/18b328cc-ff10-4e04-8457-7aa6e47aab37/stage1/rootfs/opt/stage2/alpine/manifest:
> operation not permitted
>
> Same error with rkt 1.4.0, also tried with systemd-container and
> btrfs-tools installed, no more luck.
>
> I'll try docker2aci when time will permit but I did understood that
> rkt automatically does the conversion when fetching docker:// uris
>
> regards,
> Nicolas
>
> 2016-04-19 12:22 GMT+02:00 Dmitry Smirnov :
> > Hi Alban,
> >
> > Thank you for checking this issue.
> >
> > FYI by default Debian bug tracker send emails only to maintainers. You need
> > to explicitly CC to reporter or to nn-submit...@bugs.debian.org (added 
> > to
> > CC). See more:
> >
> > https://www.debian.org/Bugs/Developer#followup
> >
> > --
> > Best wishes,
> >  Dmitry Smirnov.
> >
> >
> > On Tuesday, 19 April 2016 11:59:40 AM AEST Alban Crequy (Kinvolk) wrote:
> >> Hi,
> >>
> >> I have not seen that issue before. I cannot reproduce.
> >>
> >> Does it work with other Docker images such as docker://busybox? What
> >> is your default umask when running things with sudo? What is the
> >> filesystem used for /var/lib/rkt (ext4, btfs...)?
> >
>
>
>
> --
> Nicolas Le Cam
>

Bug#821910: gnupg1: fails to upgrade from 'sid' - trying to overwrite /usr/share/info/gnupg1.info.gz

[Andreas Beckmann]

Package: gnupg1
Version: 1.4.20-6+exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package gnupg1.
  (Reading database ... 
(Reading database ... 7352 files and directories currently installed.)
  Preparing to unpack .../gnupg1_1.4.20-6+exp1_amd64.deb ...
  Unpacking gnupg1 (1.4.20-6+exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gnupg1_1.4.20-6+exp1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/info/gnupg1.info.gz', which is also in 
package gnupg 1.4.20-6
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/gnupg1_1.4.20-6+exp1_amd64.deb


cheers,

Andreas


gnupg1_1.4.20-6+exp1.log.gz
Description: application/gzip

Bug#816076: wicd-daemon: upgrade reconfigures static ethernet interface, and kills ssh sessions.

[Andrew Vaughan]

Hi Vincent.

I was just about to update this bug after purging wicd today.

On 20 April 2016 at 19:58, Vincent Lefevre  wrote:
>
> Probably the same bug as bug 557156 (from 2009!). The problem is that
> wicd-daemon tries to reconfigure the ethernet interface even though
> it is configured not to connect to it automatically (which should be
> and is the default). A workaround is to remove eth0 from the wicd
> configuration.
>

As far as I am aware, I have never touched the wicd config files.  And a
package shouldn't ship with a config that will break an otherwise valid
configuration belonging to a different package on package upgrade.
Certainly not without _big_ warnings, and certainly not for a package
pulled in by recommendations from a relatively common metapackage.
(I included a copy of the relevant config files at the bottom of the
original bug report).

Now for the new stuff.  Today I removed wicd and related packages.
I'm pretty sure I purged the config files.  To cut a long story short,
purging wicd and related packages resulted in eth0 having it's IPv4
address removed.  Eth0 was still up with a IPv6 address.  But the
machine was no longer reachable over IPv4.  Probably just a
different variant of the same underlying buggy behaviour.

Thanks for your work on Debian.

Andrew V.

Bug#821766: gle-graphics: FTBFS on hurd-i386, but previously did

[Samuel Thibault]

Hello,

Tobias Frost, on Tue 19 Apr 2016 07:44:40 +0200, wrote:
> sem_open: Operation not supported

The Hurd doesn't have sem_open yet (but it's on its way thanks to recent
developments).

Samuel

Bug#808792: firmware-iwlwifi: iwlwifi-7260-17.ucode is missing

[Laurent Bigonville]

On Wed, 23 Dec 2015 10:48:01 +0900 Mike Hommey 
 wrote:

> Package: firmware-iwlwifi
> Version: 20151207-1
> Severity: normal
>
> # dmesg | grep iwlwifi | head -5
> [ 7.473576] iwlwifi :06:00.0: enabling device ( -> 0002)
> [ 7.475332] iwlwifi :06:00.0: firmware: failed to load 
iwlwifi-7260-17.ucode (-2)
> [ 7.475337] iwlwifi :06:00.0: Direct firmware load for 
iwlwifi-7260-17.ucode failed with error -2
> [ 7.479873] iwlwifi :06:00.0: firmware: direct-loading firmware 
iwlwifi-7260-16.ucode
> [ 7.480478] iwlwifi :06:00.0: loaded firmware version 16.242414.0 
op_mode iwlmvm

>

According to this website[0], the latest maintained versions are 
-19.ucode and -21.ucode.


The -16 which is currently in the package is marked as "end-of-life". 
Might be the time to upgrade the firmware-iwlwifi package?


Cheers,

Laurent Bigonville

[0]https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/core_release

Bug#821861: Drop gnome-screenshot from gnome-core

[Michael Biebl]

Am 20.04.2016 um 11:22 schrieb Dmitry Shachnev:
> Hi Michael,
> 
> On Wed, Apr 20, 2016 at 02:06:54AM +0200, Michael Biebl wrote:
>> GNOME shell has builtin screenshot functionality and gnome-screenshot is
>> no longer used.
>> We should therefor drop it from the gnome-core meta package.
>>
>> The gnome-flashback session probably still want's to pull it in.
>> CCing mity...@debian.org
> 
> GNOME Flashback is compatible with GNOME Shell: it implements the
> org.gnome.Shell.Screenshot D-Bus interface, and gnome-settings-daemon can
> use it. So no objections from me _here_.

Ah, good to know. So it has a builtin screenshot functionality now as well.

> However, I still find gnome-screenshot very useful: it allows one to set
> timeout before screenshot, include/exclude window border, set an effect,
> and also has an --interactive mode: much more than what one can achieve
> with bare gnome-settings-daemon keybindings.
> 
> Also, according to a recent upstream commit [1], they still consider
> gnome-screenshot a compulsory part of GNOME. Shall we really drop it?

My attempt is to trim down the footprint of gnome-core (and maybe gnome)
a bit.
If we keep gnome-screenshot as a dependency, we should at least move it
to the full-blown gnome metapackage and make it a Recommends or Suggests
only, I think.
I have to admit, that I haven't used gnome-screenshot in a very long time.

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#821766: gle-graphics: FTBFS on hurd-i386, but previously did

[Tobias Frost]

Package: gle-graphics
Followup-For: Bug #821766

I checked on #debian-buildd:
On hurd, faketime will not work as sem_open is atm not supported.


-- 
tobi

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
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)

Bug#797074: libical2 transition

[Andreas Henriksson]

Control: retitle -1 transition: libical2

Hello release-team!

A new upstream release of libical is out -> 2.0.0. This version comes
with a new so name. I'm repurposing this old bug report, initially
filed for the unfortunate and unexpected ABI breakage in 1.0.1,
for the new version. A transition to newer libical is needed for
updating evolution-data-server, et.al.

Since I've heard no feedback since my last NMU, I've gone ahead and
uploaded a package of the new version towards experimental.
It's currently stuck in (binary-)NEW.

I've build-tested reverse dependencies and came up with the following
results:

FAIL -- will need sourceful uploads.
==

ical2html-2.1
webcit-9.01-dfsg
citadel-9.01

SUCCESS -- should be binNMUable.
==

jana-0.0.0+git20091215.9ec1da8a
libsynthesis-3.4.0.47.5+syncevolution-1.5.1
orage-4.12.1
osmo-0.2.14
gnome-shell-3.20.1
gnome-todo-3.18.1
gnome-panel-3.18.2
gnome-calendar-3.20.1
gnokii-0.6.30+dfsg
cairo-dock-plug-ins-3.4.0
bluez-5.36
bijiben-3.20.0
asterisk-13.7.2~dfsg
almanah-0.11.1
agenda.app-0.42.2
syncevolution-1.4.99.4
abiword-3.0.1
evolution-ews-3.18.5
evolution-data-server-3.18.5
kdepimlibs-4.14.10
evolution-3.18.5.1
kmymoney-4.6.6

Build logs available at:
https://people.debian.org/~ah/libical-transition/

(All three seems to fail on the same thing which hopefully
means it's easy to fix:
error: 'icalerror_errors_are_fatal' undeclared (first use in this
function)
  icalerror_errors_are_fatal = 0;
)

Once libical has cleared the NEW queue I'll file the bugs
against the failing packages, set them as blockers for this bug
and remove the moreinfo tag when it looks like we're ready to
start the transition. Consider this a heads up warning.

Regards,
Andreas Henriksson

Bug#778462: faketime: does not work in chroot if /run/shm is not mounted as tmpfs inside the chroot ("sem_open: Function not implemented")

[Tobias Frost]

Source: faketime
Followup-For: Bug #778462

Addtional info, after checking on #d-buildd:
sem_open is not supported on hurd, so this will also happen there regardless of 
/run/shm.

-- 
tobi


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
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)

Bug#821911: gpgme1.0: Depends on unavailable package

[Samuel Thibault]

Source: gpgme1.0
Version: 1.6.0-2
Severity: serious
Justification: FTBFS

Hello,

gpgme1.0 keeps failing to build on buildds:

sbuild-build-depends-gpgme1.0-dummy : Depends: gnupg (>= 2) but 1.4.20-5 is to 
be installed

There is such version of gnupg available yet indeed. Looking at the
build-deps:

gnupg (>= 2) | gnupg2

You have to specify gnupg2 first for now, so buildds know they can pick
that one. Buildds indeed always only try to use the first alternative,
to get a deterministic behavior.

Samuel

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

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

-- 
Samuel
 The problem with America is stupidity. I'm not saying there should be a 
capital punishment for stupidity, but why don't we just take the safety labels 
off of everything and let the problem solve itself?

Bug#820309: libwebkit2gtk-4.0-37: missing default theme for checkboxes, scrollbars, select

[Jérémy Lal]

2016-04-08 9:17 GMT+02:00 Alberto Garcia :

> On Thu, Apr 07, 2016 at 02:47:04PM +0200, Alberto Garcia wrote:
>
> > > > This might be caused by me running gnome / gtk 3.20 from
> > > > debian/experimental, i'll downgrade and make sure of that.
> > >
> > > Confirmed ! I downgraded to debian/sid and styles are back again.
> >
> > Yeah, it seems that there was an ABI break in the GTK+ themes in
> > 3.20 and webkit needs to be rebuilt against it.
>
> If you want to give them a try, here are packages of webkit2gtk
> 2.12.0-2 build with gtk+ 3.20:
>
>
> http://debomatic-amd64.debian.net/distribution#experimental/webkit2gtk/2.12.0-2/
>
> Tell me if you try them and still have issues.


Hi,

rebuilding it fixes the issue.

Jérémy.

Bug#734669: avahi: Add DEB_BUILD_PROFILES stage1 support for bootstraping

[John Paul Adrian Glaubitz]

Hi!

Attaching now a debdiff which patches debian/control and debian/rules
in the current version of the avahi package. With this patch applied,
I can build a stage1 version of avahi which allows to break the
dependency cycle between avahi and Qt/GTK.

I would be happy to do an NMU with the updated package, but it is, of
course, up to the maintainers to decide. In any case, the Debian
bootstrap folks and porters would be very happy when this bug
gets resolved.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
diff -Nru avahi-0.6.32~rc+dfsg/debian/control avahi-0.6.32~rc+dfsg/debian/control
--- avahi-0.6.32~rc+dfsg/debian/control	2015-11-04 21:48:19.0 +0100
+++ avahi-0.6.32~rc+dfsg/debian/control	2016-04-20 14:00:05.0 +0200
@@ -16,15 +16,15 @@
libgdbm-dev,
libglib2.0-dev (>= 2.4),
libgtk2.0-dev (>= 2.14.0),
-   libgtk-3-dev,
+   libgtk-3-dev ,
libexpat-dev,
libdaemon-dev (>= 0.11),
libdbus-1-dev (>= 0.60),
python-all-dev (>= 2.6.6-3~),
python-gdbm (>= 2.4.3),
-   python-dbus,
-   python-gtk2 (>= 2.8.6-2),
-   libqt4-dev,
+   python-dbus ,
+   python-gtk2 (>= 2.8.6-2) ,
+   libqt4-dev ,
xmltoman,
intltool (>= 0.35.0)
 Standards-Version: 3.9.6
diff -Nru avahi-0.6.32~rc+dfsg/debian/rules avahi-0.6.32~rc+dfsg/debian/rules
--- avahi-0.6.32~rc+dfsg/debian/rules	2015-11-04 21:48:19.0 +0100
+++ avahi-0.6.32~rc+dfsg/debian/rules	2016-04-20 13:57:52.0 +0200
@@ -1,7 +1,14 @@
 #!/usr/bin/make -f
 
+ifneq (,$(findstring stage1,$(DEB_BUILD_PROFILES)))
+DH_PACKAGE_EXCLUDES := -Npython-avahi -Navahi-discover \
+	-Nlibavahi-qt4-1 -Nlibavahi-qt4-dev \
+	-Nlibavahi-ui0 -Nlibavahi-ui-dev -Navahi-ui-utils \
+	-Nlibavahi-ui-gtk3-0 -Nlibavahi-ui-gtk3-dev
+endif
+
 %:
-	dh $@ --with autotools-dev,python2,systemd,autoreconf
+	dh $@ --with autotools-dev,python2,systemd,autoreconf $(DH_PACKAGE_EXCLUDES)
 
 DEB_HOST_ARCH_OS ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_OS)
 
@@ -13,13 +20,22 @@
 # symbols, and speed up loading.
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,-z,defs -Wl,-O1 -Wl,--as-needed
 
+ifneq (,$(findstring stage1,$(DEB_BUILD_PROFILES)))
+qt_conf_flags := --disable-qt3 --disable-qt4
+gtk_conf_flags := --disable-gtk3 --disable-gtk --disable-pygtk \
+	--disable-python-dbus
+else
+qt_conf_flags := --disable-qt3
+gtk_conf_flags := --enable-gtk3
+endif
+
 override_dh_auto_configure:
 	dh_auto_configure -- $(CONFFLAGS) \
 		--enable-compat-libdns_sd \
 		--disable-mono \
 		--disable-monodoc \
-		--disable-qt3 \
-		--enable-gtk3 \
+		$(qt_conf_flags) \
+		$(gtk_conf_flags) \
 		--with-systemdsystemunitdir=/lib/systemd/system
 
 override_dh_auto_build:
@@ -51,10 +67,10 @@
 	dh_installinit -pavahi-dnsconfd --restart-after-upgrade
 
 override_dh_installdocs:
-	dh_installdocs --all docs/NEWS docs/README
+	dh_installdocs --all $(DH_PACKAGE_EXCLUDES) docs/NEWS docs/README
 
 override_dh_strip:
-	dh_strip --dbg-package=avahi-dbg
+	dh_strip $(DH_PACKAGE_EXCLUDES) --dbg-package=avahi-dbg
 
 override_dh_autoreconf:
 	NOCONFIGURE=1 dh_autoreconf --as-needed ./autogen.sh

Bug#733245: newsbeuter: multiline url autodetection broken

[Nikos Tsipinakis]

control: forwarded -1 https://github.com/akrennmair/newsbeuter/issues/282

Google Code is dead, issue has been migrated to GitHub.

-- 
Best Regards,
Nikos Tsipinakis

Bug#821912: gle-graphics: Please make package multi-arch

[Tobias Frost]

Package: gle-graphics
Severity: normal

Multi-Arch libraries is a release goal since wheezy.

Thanks for considering porting this package :)

More info on multi-Arch:

https://wiki.debian.org/ReleaseGoals/MultiArch
https://wiki.debian.org/Multiarch/HOWTO

-- 
tobi


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
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)

Bug#821913: nmap: do not fail enumerating interfaces if there are unknown link types

[Jan Nordholz]

Package: nmap
Version: 7.01-2
Severity: important

(renders package unusable, but only for an unlucky minority of users)

Hi,

my system configuration includes a firewire network device, so nmap fails to
find any interface whatsoever:

=
root@inti:/tmp# nmap --iflist -d3

Starting Nmap 7.01 ( https://nmap.org ) at 2016-04-20 13:49 CEST
Fetchfile found /usr/bin/../share/nmap/nmap-services
PORTS: Using top 1000 ports found open (TCP:1000, UDP:0, SCTP:0)
INTERFACES: NONE FOUND(!)
Reason: getinterfaces_dnet: intf_loop() failed
ROUTES: NONE FOUND(!)
Reason: getsysroutes_dnet: sysroutes_dnet_find_interfaces() failed
=

(Low-level reason if of interest: addr_ston() has a switch{} on supported
sa_family types, and that firewire interface comes in as (ignore the members
after sin_family, interpretation as sockaddr_in is obviously misleading)

=
Breakpoint 1, 0x004d8bb0 in addr_ston ()
(gdb) p/x *(struct sockaddr_in *)$rdi
$9 = {sin_family = 0x18, sin_port = 0xdef0, sin_addr = {s_addr = 0x636cfff1}, 
sin_zero = {0x40, 0xff, 0xa, 0x2, 0x0, 0x1, 0x0, 0x0}}
=

for which (0x18 == ARPHRD_IEEE1394) there's no case.)

There have been occurrences of this behaviour before[1][2], and it's
ridiculous. The implementation of libdnet's _intf_loop() relies on every
single _intf_get_noalias() and _intf_get_aliases() call to succeed, which
means that if a single address interpretation through addr_ston() fails, the
whole scan comes up empty.

Instead the scan should just ignore unenumerable interfaces and report the
others - that way new link types don't break libdnet (and thus nmap) for
everybody who happens to have such interfaces.

A patch might look like this[att1]. With that applied, nmap --iflist shows
the desired list of interfaces (except for firewire0, as expected) again.


Thanks!

Jan

[1]: http://seclists.org/nmap-dev/2012/q3/997
[2]: http://seclists.org/nmap-dev/2012/q2/478
-- 
Jan Nordholz 
Security in Telecommunications 
TU Berlin / Telekom Innovation Laboratories
Ernst-Reuter-Platz 7, Sekr TEL 17 / D - 10587 Berlin, Germany
phone: +49 30 8353 58663
Description: ignore errors when enumerating interfaces
 When _intf_get_noalias() or _intf_get_aliases() fail, that usually means
 that addr_ston() failed to grab the address for a certain family. As new
 address families pop up all the time it seems ridiculous that failing to
 parse a single address type should render the whole interface scan empty.
 Instead the interface should just be skipped and the other interfaces
 reported properly.
 .
 nmap (7.01-2.1) unstable; urgency=low
 .
   * Don't die while enumerating interfaces if addr_ston() fails.
Author: Jan Christoph Nordholz 

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: , 
Bug: 
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded: 
Reviewed-By: 
Last-Update: 

--- nmap-7.01.orig/libdnet-stripped/src/intf.c
+++ nmap-7.01/libdnet-stripped/src/intf.c
@@ -928,12 +928,10 @@ intf_loop(intf_t *intf, intf_handler cal
entry->intf_len = sizeof(ebuf);

if (_intf_get_noalias(intf, entry) < 0) {
-   ret = -1;
-   break;
+   continue;
}
if (_intf_get_aliases(intf, entry) < 0) {
-   ret = -1;
-   break;
+   continue;
}
if ((ret = (*callback)(entry, arg)) != 0)
break;

Bug#821860: dh-php: dh_php needs manpage

[Ondřej Surý]

Yes, it does. However I am extremely bad at documenting stuff, so ... I
am accepting patches? :) Any takers?

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server

On Wed, Apr 20, 2016, at 02:02, Daniel Kahn Gillmor wrote:
> Package: dh-php
> Version: 0.10
> Severity: normal
> 
> 0 dkg@alice:~/tmp$ dh_php --help
> Usage: dh_php [options]
> 
>   dh_php is a part of debhelper. See debhelper(7)
>   and dh_php(1) for complete usage instructions.
> 1 dkg@alice:~/tmp$ man dh_php
> No manual entry for dh_php
> See 'man 7 undocumented' for help when manual pages are not available.
> 16 dkg@alice:~/tmp$
> 
> please supply dh_php(1)!
> 
> thanks,
> 
> --dkg
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'testing'), (200,
>   'unstable'), (1, 'experimental-debug'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.4.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 dh-php depends on:
> ii  debhelper   9.20160403
> ii  liblist-moreutils-perl  0.413-1+b1
> ii  perl5.22.1-9
> 
> dh-php recommends no packages.
> 
> dh-php suggests no packages.
> 
> -- debconf-show failed

Bug#818050: /usr/bin/colormgr: cannot profile monitor with gretag i1-display2

[Fulano Diego Perez]

hi chris,

you wrote:
> Hm. I see that you don't have colord-sensor-argyll installed. I think
> that might be required to drive your calibration device.
> 
> Can you please try installing it and see if calibration works?

installing colord-sensor-argyll removed the previous error...

> It's a Suggests: rather than a Recommends: because it depends on argyll,
> which is almost 100MB on-disc and is not necessary for quite a lot of
> users, but we could certainly fix the error reported.

ive posted the results of a quick profile - i chose the 15 min (in
reality it completed quicker)

full results and prfiles in txt


it wasn't accurate - i have a feeling it has something to with the
brightness of the display/backlight

mine is set lower to about 1/3 from the gnome top-right menu (whatever
1/3 means)

from my experience with gretag in windows, before proceeding to color
swatch reading it allowed a pre-defined display luminance check (from
memory in candela, possibly 90 or 120 cdM, i hope my memory is right...)

ive had a lot of trouble profiling old monitors with dim backlights and
this may be the problem i saw in gnome

but when i re-profiled again with display/backlight at 100% - almost the
same result - so could be something else

when using the profiles, the display color cast is deep reddish,
obviously not right...

any ideas to further investigate ?


ASUSTeK K55VD (low) 2016-04-20 06-50-45 i1-display2.icc
Description: Binary data


ASUSTeK K55VD (low) 2016-04-20 11-47-11 i1-display2.icc
Description: Binary data


===
display brightness/backlight ~33%
===

Apr 20 16:53:28 hesse org.freedesktop.ColorHelper[1317]: steps were set as [ 3, 
97, -1 ] but should have been: [ 1, 99, -1 ] at cd-main.c:475
Apr 20 16:55:01 hesse CRON[6224]: (root) CMD (command -v debian-sa1 > /dev/null 
&& debian-sa1 1 1)
Apr 20 16:55:03 hesse org.freedesktop.ColorHelper[1317]: steps were set as [ 3, 
97, -1 ] but should have been: [ 3, 97, -1 ] at cd-main.c:475
Apr 20 16:56:37 hesse org.freedesktop.ColorHelper[1317]: steps were set as [ 3, 
97, -1 ] but should have been: [ 3, 97, -1 ] at cd-main.c:475
Apr 20 16:58:16 hesse org.freedesktop.ColorHelper[1317]: steps were set as [ 3, 
97, -1 ] but should have been: [ 3, 97, -1 ] at cd-main.c:475
Apr 20 16:58:16 hesse org.freedesktop.ColorHelper[1317]: child is at 3/4 steps 
and parent done [cd-main.c:788]
Apr 20 16:58:16 hesse org.freedesktop.ColorHelper[1317]: 2) cd-main.c:1341 (0/3)
Apr 20 16:58:16 hesse org.freedesktop.ColorHelper[1317]: 1) cd-main.c:682 (2/5)
Apr 20 16:58:16 hesse org.freedesktop.ColorHelper[1317]: 0) cd-main.c:766 (3/4)
Apr 20 16:58:18 hesse org.freedesktop.ColorHelper[1317]: child is at 3/4 steps 
and parent done [cd-main.c:800]
Apr 20 16:58:18 hesse org.freedesktop.ColorHelper[1317]: 2) cd-main.c:1341 (0/3)
Apr 20 16:58:18 hesse org.freedesktop.ColorHelper[1317]: 1) cd-main.c:682 (2/5)
Apr 20 16:58:18 hesse org.freedesktop.ColorHelper[1317]: 0) cd-main.c:766 (3/4)
Apr 20 16:58:18 hesse org.freedesktop.ColorHelper[1317]: child is at 3/4 steps 
and parent done [cd-main.c:841]
Apr 20 16:58:18 hesse org.freedesktop.ColorHelper[1317]: 2) cd-main.c:1341 (0/3)
Apr 20 16:58:18 hesse org.freedesktop.ColorHelper[1317]: 1) cd-main.c:682 (2/5)
Apr 20 16:58:18 hesse org.freedesktop.ColorHelper[1317]: 0) cd-main.c:766 (3/4)
Apr 20 16:58:18 hesse org.freedesktop.ColorHelper[1317]: child is at 2/5 steps 
and parent done [cd-main.c:1369]
Apr 20 16:58:18 hesse org.freedesktop.ColorHelper[1317]: 1) cd-main.c:1341 (0/3)
Apr 20 16:58:18 hesse org.freedesktop.ColorHelper[1317]: 0) cd-main.c:682 (2/5)
Apr 20 16:58:18 hesse org.freedesktop.ColorHelper[1317]: 0) cd-main.c:1341 (0/3)
Apr 20 16:58:18 hesse org.freedesktop.ColorHelper[1317]: (colord-session:6203): 
Cd-CRITICAL **: percentage should not go down from 54 to 0 on 0x55b788e38070!
Apr 20 16:58:21 hesse org.freedesktop.ColorHelper[1317]: 0) cd-main.c:1341 (0/3)
Apr 20 16:58:21 hesse org.freedesktop.ColorHelper[1317]: (colord-session:6203): 
Cd-CRITICAL **: percentage should not go down from 54 to 2 on 0x55b788e38070!
Apr 20 16:58:23 hesse org.freedesktop.ColorHelper[1317]: 0) cd-main.c:1341 (0/3)
Apr 20 16:58:23 hesse org.freedesktop.ColorHelper[1317]: (colord-session:6203): 
Cd-CRITICAL **: percentage should not go down from 54 to 2 on 0x55b788e38070!
Apr 20 16:58:24 hesse org.freedesktop.ColorHelper[1317]: 0) cd-main.c:1341 (0/3)
Apr 20 16:58:24 hesse org.freedesktop.ColorHelper[1317]: (colord-session:6203): 
Cd-CRITICAL **: percentage should not go down from 54 to 4 on 0x55b788e38070!
Apr 20 16:58:30 hesse org.freedesktop.ColorHelper[1317]: 0) cd-main.c:1341 (0/3)
Apr 20 16:58:30 hesse org.freedesktop.ColorHelper[1317]: (colord-session:6203): 
Cd-CRITICAL **: percentage should not go down from 54 to 5 on 0x55b788e38070!
Apr 20 16:58:33 hesse org.freedesktop.ColorHelper[1317]: 0) cd-main.c:1341 (0/3)
Apr 20 16:58:33 hesse org.freedesktop.ColorHelper[1317]: (colord-session:6203): 

Bug#821914: system-config-lvm: Failed to load module "canberra-gtk-module"

[Herbert Parentes Fortes Neto]

Package: system-config-lvm
Version: 1.1.18-2
Severity: normal

Dear Maintainer,

 system-config-lvm was installed with 'apt-get'. When
I tried to run:

# system-config-lvm 
Gtk-Message: Failed to load module "canberra-gtk-module"

The program ran. But with:

# apt-get install libcanberra-gtk-module

The Gtk-Message disappear.



regards,
Herbert





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

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

Versions of packages system-config-lvm depends on:
ii  gettext0.19.7-2
ii  gsfonts1:8.11+urwcyr1.0.7~pre44-4.2
ii  lvm2   2.02.146-1
ii  menu   2.1.47
ii  python-glade2  2.24.0-4
ii  python-gnome2  2.28.1+dfsg-1.1
ii  python-gtk22.24.0-4
pn  python:any 

system-config-lvm recommends no packages.

system-config-lvm suggests no packages.

-- no debconf information

Bug#821915: ITP: salt-formula-cinder -- Salt formula for OpenStack Cinder

[Filip Pytloun]

Package: wnpp
Version: 2016.4.1
Severity: wishlist
Owner: Filip Pytloun 

* Package name: salt-formula-cinder
  Version : 2016.4.1
  Upstream Author : tcpcloud 
* URL : https://github.com/openstack/salt-formula-cinder
* License : Apache-2.0
  Programming Lang: SaltStack
  Description : Salt formula for OpenStack Cinder

Salt is a powerful remote execution manager that can be used to
administer servers in a fast and efficient way.
.
This SaltStack formula manages both installation and configuration of
OpenStack Cinder


signature.asc
Description: Digital signature

Bug#821916: ITP: salt-formula-glance -- Salt formula for OpenStack glance

[Filip Pytloun]

Package: wnpp
Version: 2016.4.1
Severity: wishlist
Owner: Filip Pytloun 

* Package name: salt-formula-glance
  Version : 2016.4.1
  Upstream Author : tcpcloud 
* URL : https://github.com/openstack/salt-formula-glance
* License : Apache-2.0
  Programming Lang: SaltStack
  Description : Salt formula for OpenStack glance

Salt is a powerful remote execution manager that can be used to
administer servers in a fast and efficient way.
.
This SaltStack formula manages both installation and configuration of
OpenStack Glance


signature.asc
Description: Digital signature

Bug#821911: gpgme1.0: Depends on unavailable package

[Daniel Kahn Gillmor]

Version: 1.6.0-3

On Wed 2016-04-20 07:51:02 -0400, Samuel Thibault wrote:
> gpgme1.0 keeps failing to build on buildds:
>
> sbuild-build-depends-gpgme1.0-dummy : Depends: gnupg (>= 2) but 1.4.20-5 is 
> to be installed
>
> There is such version of gnupg available yet indeed. Looking at the
> build-deps:
>
> gnupg (>= 2) | gnupg2
>
> You have to specify gnupg2 first for now, so buildds know they can pick
> that one. Buildds indeed always only try to use the first alternative,
> to get a deterministic behavior.

sigh, right.  determinism should really be handled by an independent
process (e.g. the work that the reproducible-builds team is doing), but
i understand the limitations of the current setup.  I've uploaded
1.6.0-3 this morning with the build-dep order reversed.

thanks for the note here.

   --dkg

Bug#821919: ITP: salt-formula-keystone -- Salt formula for OpenStack keystone

[Filip Pytloun]

Package: wnpp
Version: 2016.4.1
Severity: wishlist
Owner: Filip Pytloun 

* Package name: salt-formula-keystone
  Version : 2016.4.1
  Upstream Author : tcpcloud 
* URL : https://github.com/openstack/salt-formula-keystone
* License : Apache-2.0
  Programming Lang: SaltStack
  Description : Salt formula for OpenStack Keystone

Salt is a powerful remote execution manager that can be used to
administer servers in a fast and efficient way.
.
This SaltStack formula manages both installation and configuration of
OpenStack Keystone


signature.asc
Description: Digital signature

Bug#821917: ITP: salt-formula-heat -- Salt formula for OpenStack heat

[Filip Pytloun]

Package: wnpp
Version: 2016.4.1
Severity: wishlist
Owner: Filip Pytloun 

* Package name: salt-formula-heat
  Version : 2016.4.1
  Upstream Author : tcpcloud 
* URL : https://github.com/openstack/salt-formula-heat
* License : Apache-2.0
  Programming Lang: SaltStack
  Description : Salt formula for OpenStack heat

Salt is a powerful remote execution manager that can be used to
administer servers in a fast and efficient way.
.
This SaltStack formula manages both installation and configuration of
OpenStack Heat


signature.asc
Description: Digital signature

Bug#821918: ITP: salt-formula-horizon -- Salt formula for OpenStack horizon

[Filip Pytloun]

Package: wnpp
Version: 2016.4.1
Severity: wishlist
Owner: Filip Pytloun 

* Package name: salt-formula-horizon
  Version : 2016.4.1
  Upstream Author : tcpcloud 
* URL : https://github.com/openstack/salt-formula-horizon
* License : Apache-2.0
  Programming Lang: SaltStack
  Description : Salt formula for OpenStack Horizon

Salt is a powerful remote execution manager that can be used to
administer servers in a fast and efficient way.
.
This SaltStack formula manages both installation and configuration of
OpenStack Horizon


signature.asc
Description: Digital signature

Bug#821860: dh-php: dh_php needs manpage

[Daniel Kahn Gillmor]

On Wed 2016-04-20 08:31:01 -0400, Ondřej Surý wrote:
> Yes, it does. However I am extremely bad at documenting stuff, so ... I
> am accepting patches? :) Any takers?

looks like:

   pod2man /usr/bin/dh_php

should do what you want :)

   --dkg

Bug#821920: ITP: salt-formula-neutron -- Salt formula for OpenStack Neutron

[Filip Pytloun]

Package: wnpp
Version: 2016.4.1
Severity: wishlist
Owner: Filip Pytloun 

* Package name: salt-formula-neutron
  Version : 2016.4.1
  Upstream Author : tcpcloud 
* URL : https://github.com/openstack/salt-formula-neutron
* License : Apache-2.0
  Programming Lang: SaltStack
  Description : Salt formula for OpenStack Neutron

Salt is a powerful remote execution manager that can be used to
administer servers in a fast and efficient way.
.
This SaltStack formula manages both installation and configuration of
OpenStack Neutron


signature.asc
Description: Digital signature

Bug#821860: dh-php: dh_php needs manpage

[Ondřej Surý]

Ah, I vaguely remember writing some documentation, but I didn't believe
my own memories related to writing documentation.

Thanks for catching that. I only had to kill the accented characters
from my name to stop pod2man throwing error (even with -u).

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server

On Wed, Apr 20, 2016, at 14:38, Daniel Kahn Gillmor wrote:
> On Wed 2016-04-20 08:31:01 -0400, Ondřej Surý wrote:
> > Yes, it does. However I am extremely bad at documenting stuff, so ... I
> > am accepting patches? :) Any takers?
> 
> looks like:
> 
>pod2man /usr/bin/dh_php
> 
> should do what you want :)
> 
>--dkg

Bug#821921: ITP: salt-formula-nova -- Salt formula for OpenStack Nova

[Filip Pytloun]

Package: wnpp
Version: 2016.4.1
Severity: wishlist
Owner: Filip Pytloun 

* Package name: salt-formula-nova
  Version : 2016.4.1
  Upstream Author : tcpcloud 
* URL : https://github.com/openstack/salt-formula-nova
* License : Apache-2.0
  Programming Lang: SaltStack
  Description : Salt formula for OpenStack Nova

Salt is a powerful remote execution manager that can be used to
administer servers in a fast and efficient way.
.
This SaltStack formula manages both installation and configuration of
OpenStack Nova


signature.asc
Description: Digital signature

Bug#821914: system-config-lvm: Failed to load module "canberra-gtk-module"

[Philipp Huebner]

Hi,

thank you for your bugreport!

Am 20.04.2016 um 14:40 schrieb Herbert Parentes Fortes Neto:
>  system-config-lvm was installed with 'apt-get'. When
> I tried to run:
> 
> # system-config-lvm 
> Gtk-Message: Failed to load module "canberra-gtk-module"
> 
> The program ran. But with:
> 
> # apt-get install libcanberra-gtk-module
> 
> The Gtk-Message disappear.

This is good to know. Under KDE/Plasma however I don't get that message
even without libcanberra-gtk-module installed, so my guess is this is
related to your desktop environment.

You said the program worked anyway, so unless it caused any problems for
you I would list libcanberra-gtk-module only in the "Suggests:" line of
system-config-lvm.

Regards,
-- 
 .''`.   Philipp Huebner 
: :'  :  pgp fp: 6719 25C5 B8CD E74A 5225  3DF9 E5CA 8C49 25E4 205F
`. `'`
  `-



signature.asc
Description: OpenPGP digital signature

Bug#762637: qtile in Debian

[Tycho Andersen]

Hi Iain,

On Wed, Apr 20, 2016 at 11:21:37AM +0100, Iain R. Learmonth wrote:
> Hi,
> 
> Are you still interested in packaging qtile for Debian?
> 
> I notice that there is a newer upstream version available, if you can
> package this I would be happy to review and upload.
> 
> If you're no longer interested in packaging this, I am happy to do the
> work, please let me know though.

I think the debian/ stuff in the upstream tree should be reasonably
close to what's needed. I don't have time to work on it right now, so
if you're interested in packaging, I'd say go for it.

Thanks!

Tycho

> Thanks,
> Iain.
> 
> -- 
> To unsubscribe, send mail to 762637-unsubscr...@bugs.debian.org.

Bug#821922: virtualbox: Cannot boot any VM

[Jean-Philippe MENGUAL]

Package: virtualbox
Version: 4.3.36-dfsg-1+deb8u1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?

Hi upgraded from 4.3.32 to 4.3.36.

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

After several failures, where I removed hdd (closemedium disk),
re-attached and
re-registered it, with vdi file, etc., I re-built a full new VM. Removed
~/.VirtualBox and ^ÎirtualBox VMs. Then:
VBoxManage createvm --name xp --ostype WindowsXP --register
VBoxManage modifyvm xp --memory "2000" --acpi on --boot1 dvd --boot2
disk --boot3 net --nic1 nat --nic2 hostonly --hostonlyadapter2 vboxnet0
 --audio pulse

VBoxManage storagectl xp --name ide --add ide
VBoxManage storageattach xp --storagectl ide --port 0 --device 0 --type
disk --medium ./xp2.vdi
VBoxManage storageattach xp --storagectl ide --port 0 --device 0 --type
hdd --medium ./xp2.vdi
VBoxManage storageattach xp --storagectl sata --port 0 --device 1 --type
dvddrive --medium host:/dev/sr0

VBoxManage storageattach xp --storagectl ide --port 0 --device 0 --type
hdd --medium ./xp2.vdi
VBoxManage storageattach xp --storagectl sata --port 0 --device 1 --type
dvddrive --medium host:/dev/sr0

   * What was the outcome of this action?

Here's attached file cannot be closed because it is still attached to 1
virtual machines. Nonsense, since I've no
other sessions, a single VM, a single disk.

   * What outcome did you expect instead?

Should start VM.

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

Thanks for your help. I reproduce on 5.0 here, on testing.

Ready to give you any needed info.

Regards,


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

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

Versions of packages virtualbox depends on:
ii  adduser  3.113+nmu3
ii  libc62.19-18+deb8u4
ii  libcurl3-gnutls  7.38.0-4+deb8u3
ii  libgcc1  1:4.9.2-10
ii  libgsoap52.8.17-1
ii  libpng12-0   1.2.50-2+deb8u2
ii  libpython2.7 2.7.9-2
ii  libsdl1.2debian  1.2.15-10+b1
ii  libssl1.0.0  1.0.1k-3+deb8u4

ii  libvncserver00.9.9+dfsg2-6.1+deb8u1
ii  libvpx1  1.3.0-3
ii  libx11-6 2:1.6.2-3
ii  libxcursor1  1:1.1.14-1+b1
ii  libxext6 2:1.3.3-1
ii  libxml2  2.9.1+dfsg1-5+deb8u1
ii  libxmu6  2:1.1.2-1
ii  libxt6   1:1.1.4-1+b1
ii  python   2.7.9-1
ii  python2.72.7.9-2
pn  python:any   
ii  virtualbox-dkms  4.3.36-dfsg-1+deb8u1
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages virtualbox recommends:
ii  libgl1-mesa-glx [libgl1]  10.3.2-1+deb8u1
ii  libqt4-opengl 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  virtualbox-qt 4.3.36-dfsg-1+deb8u1
Versions of packages virtualbox suggests:
pn  vde2
ii  virtualbox-guest-additions-iso  4.3.18-3

-- no debconf information

Bug#818974: packaging

[Roderick MacKenzie]

control: tags -1

Hi All,

  Thanks for all the comments.  Sorry for the delay in responding, I
realized that it would be much better if the code built using
autotools - rather than my random build system.  So, I swapped out the
build system for autotools, this took quite a while.  The old build
system also autogenerated some .c/.h files that I thought was not a
nice thing to do, I think also the debian build system complained
about this.  So I rewrote the plugin system to avoid having to do this
- this also required significant changes to the code – which also took
time.  Below I’ve indicated how I’ve addressed each comment, given on
the thread above.  I also got some comments from IRC, which I’ve put
right at the bottom of the post.  I have indicated comments with a
“Q:” and my answers with an “A:”

A new copy of the deb files can be downloaded from:

https://github.com/roderickmackenzie/gpvdm/releases/tag/gpvdm-4.42

Happy to make more changes if needed,

Rod



Q: $ find -type f \( -iname '*.sh' -o -iname '*.bash' \) -exec bashate
--ignore E002,E003 {} +
E010: Do not on same line as for: 'for i in `find -type f` ; do md5sum
$i; done >list.dat'
 - ./update.sh : L23
E001: Trailing Whitespace: 'mkdir ${rpmdir} '
 - ./make_rpm.sh : L33
E001: Trailing Whitespace: 'cd ${rpmdir} '
 - ./make_rpm.sh : L34
E010: Do not on same line as for: 'for i in `find|grep -v .git|grep -v
.o$|grep -v ~$|grep -v materials|grep -v dll$|grep -v .so$`'
 - ./to_github.sh : L123
4 bashate error(s) found


A:I’ve fixed this now and the command gives no errors.

Q: # Check with upstream where the GIMP XCF source files are.
$ find -type f \( -iname '*.png' -o -iname '*.gif' -o -iname '*.jpg'
-o -iname '*.jpeg' \) -exec grep -iF gimp {} +
Binary file ./images/image.jpg matches
Binary file ./images/icon.png matches
Binary file ./images/splash.png matches

# Check with upstream where the Inkscape SVG source files are.
$ find -type f \( -iname '*.png' -o -iname '*.gif' -o -iname '*.jpg'
-o -iname '*.jpeg' \) -exec grep -iF inkscape {} +
Binary file ./images/dir_file.png matches
Binary file ./images/book.png matches
Binary file ./images/play.png matches
...
A: All inkscape svg files used by the code are now there in the
./images/ directory, and the build system generates the pngs from the
svg files. Three png files did not play nice with rsvg, so I just ship
the svg and png files together and don’t let the build system generate
them. I don’t have the XCF files for the jpgs, I don’t think I ever
saved them.


Q: $ find -type f -iname '*.sh' -exec checkbashisms {} +
could not find any possible bashisms in bash script ./clean_all.sh
could not find any possible bashisms in bash script ./update.sh
could not find any possible bashisms in bash script ./winpub.sh
could not find any possible bashisms in bash script ./buildplugins.sh
could not find any possible bashisms in bash script ./make_rpm.sh
could not find any possible bashisms in bash script ./get_elec_plugins.sh
A: Fixed, no errors are given anymore.


Q: cme check dpkg
...
Warning in 'control source Standards-Version' value '3.9.6': Current
standards version is 3.9.7
File debian/copyright line 1 has a syntax error:
DpkgSyntax error: Invalid line (missing ':' ?) : Copyright
2015 Roderick Charles Ian MacKenzie 
A: Fixed, no errors are given.


Q: $ codespell --quiet-level=3
/inp.c:577: compatability  ==> compatibility
/dump_dynamic.c:399: efficency  ==> efficiency
/makefile:17: inital  ==> initial
/LICENSE:169: publically  ==> publicly
/make_rpm.sh:159: automaticly  ==> automatically
/make_rpm.sh:205: intergration  ==> integration
/gui/update.py:101: forbiden  ==> forbidden
/gui/update.py:145: avaliable  ==> available
/gui/copying.py:48: nTo  ==> not  | disable due to \n
/gui/listen_for_files_on_network.py:70: recived  ==> received
/gui/cmp_class.py:234: extention  ==> extension
/gui/qe.py:234: Efficency  ==> Efficiency
/solvers/newton_norm/newton.c:1470: propper  ==> proper
/solvers/newton/newton.c:1572: propper  ==> proper
A: Fixed


Q: $ find -type f -iname '*.c' -exec complexity {} +

A: This seems to measure the complexity of the code.


Q: $ cppcheck -j1 --quiet -f .
[complex_solver.c:131]: (error) Common realloc mistake: 'x' nulled but
not freed upon failure
[complex_solver.c:132]: (error) Common realloc mistake: 'xz' nulled
but not freed upon failure
[complex_solver.c:133]: (error) Common realloc mistake: 'Ap' nulled
but not freed upon failure
[complex_solver.c:134]: (error) Common realloc mistake: 'Ai' nulled
but not freed upon failure


A: Fixed – now gives no output.

Q: $ find -type f -iname '*.desktop' -exec desktop-file-validate {} \;
/gui/gpvdm.desktop: error: line "   Name=gpvdm" starts with a
space. Comment, group and key-value lines should not start with a
space. The validation will continue, with the leading spaces ignored.
/gui/gpvdm.desktop: error: line "
Icon=/usr/share/gpvdm/gui/image.jpg" starts with a space. Comment,
group and key-value lines should not