date:20170421

Package: dnssec-trigger,isc-dhcp-client
Version: dnssec-trigger/0.13-6
Version: isc-dhcp-client/4.3.5-3
Severity: important

Dear dnssec-trigger and ISC DHCP maintainers,

for at least a few weeks now (maybe longer), systems, which have
dnssec-trigger installed together with isc-dhcp-client, get cluttered
with one resolv.conf.dhclient-new.* file per DHCP response in /etc/ as
dnssec-trigger uses chattr to make /etc/resolv.conf immutable and hence
making sure noone else overwrites /etc/resolv.conf (see also #776776 and
#776778).

But since recently (don't know since when exactly) dhclient seems to no
more just overwrite /etc/resolv.conf directly but first creates a
supposed to be temporary /etc/resolv.conf.dhclient-new.$pid file and
then moves it to /etc/resolv.conf (probably to avoid some race
condition). But it seems no more clean up those files if the renaming
fails.

IMHO dhclient should clean up these files in case the renaming
fails. But I can also understand if someone argues that
dnssec-triggerd's methods are too radical and unusual so that other
programs can't be expected to handle such exotic cases.

So I'm not sure which package should be fixed, but at least one of them
should be fixed to not clutter /etc/. And I'd be happy if this could be
fixed even for Stretch.

I can imagine multiple potential ways to fix this:

* dhclient remove /etc/resolv.conf.dhclient-new.$pid again, if the
  renaming failed.

* dhclient prepares resolv.conf.dhclient-new.$pid not in /etc/ but in
  /tmp/. There it's far less annoying if the directory is cluttered with
  small files and those files would be usually cleaned up at
  reboot. (Disavantage: The renaming is often a move from one file
  system to another -- which might not be wanted.)

* dnssec-triggerd cleans up those files, either time-based or
  event-based.

Example files as found on one of my systems in /etc/:

/etc $ ls resolv.conf.dhclient-new.*
resolv.conf.dhclient-new.10093  resolv.conf.dhclient-new.24190
resolv.conf.dhclient-new.10237  resolv.conf.dhclient-new.24468
resolv.conf.dhclient-new.10240  resolv.conf.dhclient-new.24625
resolv.conf.dhclient-new.10354  resolv.conf.dhclient-new.24696
resolv.conf.dhclient-new.1040   resolv.conf.dhclient-new.24892
resolv.conf.dhclient-new.1044   resolv.conf.dhclient-new.25138
resolv.conf.dhclient-new.10445  resolv.conf.dhclient-new.25671
resolv.conf.dhclient-new.10538  resolv.conf.dhclient-new.25907
resolv.conf.dhclient-new.1083   resolv.conf.dhclient-new.25947
resolv.conf.dhclient-new.10878  resolv.conf.dhclient-new.26515
resolv.conf.dhclient-new.11028  resolv.conf.dhclient-new.26989
resolv.conf.dhclient-new.11087  resolv.conf.dhclient-new.27046
resolv.conf.dhclient-new.1117   resolv.conf.dhclient-new.27113
resolv.conf.dhclient-new.11401  resolv.conf.dhclient-new.27293
resolv.conf.dhclient-new.11537  resolv.conf.dhclient-new.27323
resolv.conf.dhclient-new.11668  resolv.conf.dhclient-new.27413
resolv.conf.dhclient-new.11755  resolv.conf.dhclient-new.27613
resolv.conf.dhclient-new.12184  resolv.conf.dhclient-new.27957
resolv.conf.dhclient-new.12438  resolv.conf.dhclient-new.27971
resolv.conf.dhclient-new.12576  resolv.conf.dhclient-new.28008
resolv.conf.dhclient-new.12677  resolv.conf.dhclient-new.28561
resolv.conf.dhclient-new.1291   resolv.conf.dhclient-new.2862
resolv.conf.dhclient-new.12956  resolv.conf.dhclient-new.28736
resolv.conf.dhclient-new.12991  resolv.conf.dhclient-new.28793
resolv.conf.dhclient-new.13251  resolv.conf.dhclient-new.28808
resolv.conf.dhclient-new.13265  resolv.conf.dhclient-new.28816
resolv.conf.dhclient-new.13299  resolv.conf.dhclient-new.28846
resolv.conf.dhclient-new.13310  resolv.conf.dhclient-new.2896
resolv.conf.dhclient-new.13334  resolv.conf.dhclient-new.28988
resolv.conf.dhclient-new.1334   resolv.conf.dhclient-new.2910
resolv.conf.dhclient-new.1344   resolv.conf.dhclient-new.29101
resolv.conf.dhclient-new.13472  resolv.conf.dhclient-new.29225
resolv.conf.dhclient-new.13730  resolv.conf.dhclient-new.29371
resolv.conf.dhclient-new.13896  resolv.conf.dhclient-new.29597
resolv.conf.dhclient-new.13950  resolv.conf.dhclient-new.29803
resolv.conf.dhclient-new.14031  resolv.conf.dhclient-new.30016
resolv.conf.dhclient-new.14214  resolv.conf.dhclient-new.30190
resolv.conf.dhclient-new.14270  resolv.conf.dhclient-new.30291
resolv.conf.dhclient-new.14662  resolv.conf.dhclient-new.30464
resolv.conf.dhclient-new.14695  resolv.conf.dhclient-new.30583
resolv.conf.dhclient-new.14873  resolv.conf.dhclient-new.30980
resolv.conf.dhclient-new.15120  resolv.conf.dhclient-new.31030
resolv.conf.dhclient-new.15142  resolv.conf.dhclient-new.31543
resolv.conf.dhclient-new.15267  resolv.conf.dhclient-new.3165
resolv.conf.dhclient-new.15521  resolv.conf.dhclient-new.31899
resolv.conf.dhclient-new.15922  resolv.conf.dhclient-new.3
resolv.conf.dhclient-new.15964  resolv.conf.dhclient-new.32708
resolv.conf.dhclient-new.16095  resolv.conf.dhclient-new.3274
resolv.conf.dhclient-new.16435

Bug#860927: Tk applications segmentation fault when ibus-daemon IME is restarted

2017-04-21 Thread Jonathan Nieder

debdiff attached.  Still untested.  Sorry for the broken partial patch before.

Thanks,
Jonathan
diff -Nru tk8.6-8.6.6/debian/changelog tk8.6-8.6.6/debian/changelog
--- tk8.6-8.6.6/debian/changelog2016-07-27 20:22:45.0 -0700
+++ tk8.6-8.6.6/debian/changelog2017-04-21 17:11:11.0 -0700
@@ -1,3 +1,10 @@
+tk8.6 (8.6.6-2) local; urgency=medium
+
+  * Added patch from upstream to fix crash when X input methods are
+restarted (closes: #860927).
+
+ -- Jonathan Nieder   Fri, 21 Apr 2017 17:00:08 -0700
+
 tk8.6 (8.6.6-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru tk8.6-8.6.6/debian/patches/series tk8.6-8.6.6/debian/patches/series
--- tk8.6-8.6.6/debian/patches/series   2014-08-27 09:25:53.0 -0700
+++ tk8.6-8.6.6/debian/patches/series   2017-04-21 17:10:25.0 -0700
@@ -4,3 +4,4 @@
 non-linux.diff
 manpages.diff
 xft.diff
+ximgeneration.diff
diff -Nru tk8.6-8.6.6/debian/patches/ximgeneration.diff 
tk8.6-8.6.6/debian/patches/ximgeneration.diff
--- tk8.6-8.6.6/debian/patches/ximgeneration.diff   1969-12-31 
16:00:00.0 -0800
+++ tk8.6-8.6.6/debian/patches/ximgeneration.diff   2017-04-21 
17:13:54.0 -0700
@@ -0,0 +1,186 @@
+Patch by Brad Larson to handle an input method being restarted.
+http://core.tcl.tk/tk/tktview?name=7d967c68a0
+
+--- a/generic/tkEvent.c
 b/generic/tkEvent.c
+@@ -356,6 +356,7 @@ CreateXIC(
+   /* XCreateIC failed. */
+   return;
+ }
++winPtr->ximGeneration = dispPtr->ximGeneration;
+ 
+ /*
+  * Adjust the window's event mask if the IM requires it.
+@@ -1288,6 +1289,14 @@ Tk_HandleEvent(
+  */
+ 
+ #ifdef TK_USE_INPUT_METHODS
++/*
++ * If the XIC has been invalidated, it must be recreated.
++ */
++if (winPtr->dispPtr->ximGeneration != winPtr->ximGeneration) {
++  winPtr->flags &= ~TK_CHECKED_IC;
++  winPtr->inputContext = NULL;
++}
++
+ if ((winPtr->dispPtr->flags & TK_DISPLAY_USE_IM)) {
+   if (!(winPtr->flags & (TK_CHECKED_IC|TK_ALREADY_DEAD))) {
+   winPtr->flags |= TK_CHECKED_IC;
+@@ -1295,7 +1304,9 @@ Tk_HandleEvent(
+   CreateXIC(winPtr);
+   }
+   }
+-  if (eventPtr->type == FocusIn && winPtr->inputContext != NULL) {
++  if ((eventPtr->type == FocusIn) &&
++  (winPtr->dispPtr->inputMethod != NULL) &&
++  (winPtr->inputContext != NULL)) {
+   XSetICFocus(winPtr->inputContext);
+   }
+ }
+--- a/generic/tkInt.h
 b/generic/tkInt.h
+@@ -508,6 +508,9 @@ typedef struct TkDisplay {
+ 
+ int iconDataSize; /* Size of default iconphoto image data. */
+ unsigned char *iconDataPtr;   /* Default iconphoto image data, if 
set. */
++#ifdef TK_USE_INPUT_METHODS
++int ximGeneration;  /* Used to invalidate XIC */
++#endif /* TK_USE_INPUT_METHODS */
+ } TkDisplay;
+ 
+ /*
+@@ -809,6 +812,9 @@ typedef struct TkWindow {
+ int minReqWidth;  /* Minimum requested width. */
+ int minReqHeight; /* Minimum requested height. */
+ char *geometryMaster;
++#ifdef TK_USE_INPUT_METHODS
++int ximGeneration;  /* Used to invalidate XIC */
++#endif /* TK_USE_INPUT_METHODS */
+ } TkWindow;
+ 
+ /*
+--- a/generic/tkWindow.c
 b/generic/tkWindow.c
+@@ -355,6 +355,9 @@ CreateTopLevelWindow(
+  * Set the flags specified in the call.
+  */
+ 
++#ifdef TK_USE_INPUT_METHODS
++winPtr->ximGeneration = 0;
++#endif /*TK_USE_INPUT_METHODS*/
+ winPtr->flags |= flags;
+ 
+ /*
+@@ -650,6 +653,7 @@ TkAllocWindow(
+ winPtr->flags = 0;
+ winPtr->handlerList = NULL;
+ #ifdef TK_USE_INPUT_METHODS
++winPtr->ximGeneration = 0;
+ winPtr->inputContext = NULL;
+ #endif /* TK_USE_INPUT_METHODS */
+ winPtr->tagPtr = NULL;
+@@ -1442,10 +1446,11 @@ Tk_DestroyWindow(
+ UnlinkWindow(winPtr);
+ TkEventDeadWindow(winPtr);
+ #ifdef TK_USE_INPUT_METHODS
+-if (winPtr->inputContext != NULL) {
++if (winPtr->inputContext != NULL &&
++  winPtr->ximGeneration == winPtr->dispPtr->ximGeneration) {
+   XDestroyIC(winPtr->inputContext);
+-  winPtr->inputContext = NULL;
+ }
++winPtr->inputContext = NULL;
+ #endif /* TK_USE_INPUT_METHODS */
+ if (winPtr->tagPtr != NULL) {
+   TkFreeBindingTags(winPtr);
+--- a/unix/tkUnixEvent.c
 b/unix/tkUnixEvent.c
+@@ -38,6 +38,8 @@ static void  DisplayFileProc(ClientData clientData, 
int flags);
+ static void   DisplaySetupProc(ClientData clientData, int flags);
+ static void   TransferXEventsToTcl(Display *display);
+ #ifdef TK_USE_INPUT_METHODS
++static void   InstantiateIMCallback(Display *, XPointer client_data, 
XPointer call_data);
++static void   DestroyIMCallback(XIM im, XPointer client_data, 
XPointer call_data);
+ static void   OpenIM(TkDisplay *dispPtr);
+ #endif
+ 
+@@ -179,6 +181,8 @@ TkpOpenDisplay(
+ dispPtr->flags |= use_xkb;
+ #ifdef

Bug#860927: Tk applications segmentation fault when ibus-daemon IME is restarted

2017-04-21 Thread Jonathan Nieder

Package: tk8.6
Version: 8.6.1-3ubuntu2
Severity: important
Tags: upstream patch
Forwarded: http://core.tcl.tk/tk/tktview?name=7d967c68a0

Hi,

Steve Paik (cc-ed) reported that gitk is crashing periodically.  This
patch, from upstream tk, should fix it.

Thoughts?

Please forgive the whitespace damage.  Copy/paste was the simplest way
to get this here.

Thanks,
Jonathan

commit 0175bc1be685a5ce4a92f7c153eb12e28c28cb1d (origin/bug_7d967c68)
Author: jan.nijtmans 
Date:   Thu Dec 15 16:07:06 2016 +

Proposed fix for [7d967c68a09e07e355358af40f36dd5dd84c7022|7d967c68]: Tk 
applications segmentation fault when ibus-daemon IME is restarted

diff --git a/generic/tkEvent.c b/generic/tkEvent.c
index 95aeda1dd..d058e7cd6 100644
--- a/generic/tkEvent.c
+++ b/generic/tkEvent.c
@@ -356,6 +356,7 @@ CreateXIC(
/* XCreateIC failed. */
return;
 }
+winPtr->ximGeneration = dispPtr->ximGeneration;
 
 /*
  * Adjust the window's event mask if the IM requires it.
@@ -1288,6 +1289,14 @@ Tk_HandleEvent(
  */
 
 #ifdef TK_USE_INPUT_METHODS
+/*
+ * If the XIC has been invalidated, it must be recreated.
+ */
+if (winPtr->dispPtr->ximGeneration != winPtr->ximGeneration) {
+   winPtr->flags &= ~TK_CHECKED_IC;
+   winPtr->inputContext = NULL;
+}
+
 if ((winPtr->dispPtr->flags & TK_DISPLAY_USE_IM)) {
if (!(winPtr->flags & (TK_CHECKED_IC|TK_ALREADY_DEAD))) {
winPtr->flags |= TK_CHECKED_IC;
@@ -1295,7 +1304,9 @@ Tk_HandleEvent(
CreateXIC(winPtr);
}
}
-   if (eventPtr->type == FocusIn && winPtr->inputContext != NULL) {
+   if ((eventPtr->type == FocusIn) &&
+   (winPtr->dispPtr->inputMethod != NULL) &&
+   (winPtr->inputContext != NULL)) {
XSetICFocus(winPtr->inputContext);
}
 }

commit 596abb7b53897447dda6044725ea94a664dae64e
Author: jan.nijtmans 
Date:   Fri Feb 10 11:38:55 2017 +

Fix [7d967c68a09e07e355358af40f36dd5dd84c7022|7d967c68a0] follow-up: Tk 
applications segmentation fault when ibus-daemon IME is restarted. Patch by 
Brad Lanam.

diff --git a/generic/tkWindow.c b/generic/tkWindow.c
index e4d696bdd..690a8412d 100644
--- a/generic/tkWindow.c
+++ b/generic/tkWindow.c
@@ -475,9 +475,6 @@ GetScreen(
dispPtr->cursorFont = None;
dispPtr->warpWindow = NULL;
dispPtr->multipleAtom = None;
-#ifdef TK_USE_INPUT_METHODS
-   dispPtr->ximGeneration = 0;
-#endif /*TK_USE_INPUT_METHODS*/
 
/*
 * By default we do want to collapse motion events in
@@ -656,6 +653,7 @@ TkAllocWindow(
 winPtr->flags = 0;
 winPtr->handlerList = NULL;
 #ifdef TK_USE_INPUT_METHODS
+winPtr->ximGeneration = 0;
 winPtr->inputContext = NULL;
 #endif /* TK_USE_INPUT_METHODS */
 winPtr->tagPtr = NULL;

Bug#857360: gitlab_8.13.11+dfsg-4 no longer available, unable to install

2017-04-21 Thread Joel Maxuel

Hello,

Running Debian Stretch (with the exception of about a dozen Jessie packages
held back) with Systemd.  Kernel 4.9.0-2-amd64.

I have read above, and tried versions
gitlab_8.13.11+dfsg-1-2, gitlab_8.13.11+dfsg-1-3 and gitlab_8.13.11+dfsg-8
with no success.  When originally installing gitlab_8.13.11+dfsg-1-2
automatically via aptitude, dkpg choked on the example file not being
there.  I made a dummy file with touch and re-ran, but I got a different
set of errors and continue to get them after installing different versions,
re-configuring, and even purging/re-installing.

I should add that I am currently using ports 80, 443 and 8080 for other
purposes, so my challenge may be gitlab cannot find a port to bind to.  But
from my perspective it does not even attempt as the available-sites file
does not exist in the apache config directory.

My Config:

user: gitlab
gitlab_url: "http://localhost:8088/;
self_signed_cert: false
repos_path: "/tank/gitlab/repositories"
auth_file: "/usr/share/gitlab/.ssh/authorized_keys"
redis:
  bin: /usr/bin/redis-cli
  host: 127.0.0.1
  port: 6379
  database: 0
  namespace: resque:gitlab
log_level: INFO
audit_usernames: false
git_annex_enabled: false

My Install Stream:

gitlab_user="gitlab"
Creating/updating gitlab user account...
Making gitlab owner of /var/lib/gitlab...
Creating runtime directories for gitlab...
Updating file permissions...
GITLAB_HOST="skynet.maxuel.tk"
Configuring nginx with HTTPS...
GITLAB_HTTPS="true"
Registering /usr/lib/tmpfiles.d/gitlab.conf via ucf
Registering /etc/gitlab-shell/config.yml via ucf
Registering /etc/gitlab/gitlab.yml via ucf
Registering /etc/gitlab/gitlab-debian.conf via ucf
Create database if not present
Make gitlab user owner of gitlab_production database...
ALTER DATABASE
Grant all privileges to gitlab user...
GRANT
NOTICE:  extension "pg_trgm" already exists, skipping
CREATE EXTENSION
Verifying we have all required libraries...
Resolving dependencies...
Using rake 10.5.0
Using RedCloth 4.3.2
Using ace-rails-ap 4.1.1
Using i18n 0.7.0
Using json 1.8.3
Using minitest 5.9.0
Using thread_safe 0.3.5
Using builder 3.2.2
Using erubis 2.7.0
Using nokogiri 1.6.8.1
Using rack 1.6.4
Using mime-types 2.6.1
Using arel 6.0.3
Using multi_json 1.11.2
Using thor 0.19.1
Using addressable 2.4.0
Using akismet 2.0.0
Using allocations 1.0.3
Using multipart-post 1.2.0
Using jwt 1.5.4
Using multi_xml 0.5.5
Using asciidoctor 1.5.4
Using encryptor 3.0.0
Using attr_required 1.0.0
Using execjs 2.6.0
Using ice_nine 0.11.2
Using systemu 2.6.5
Using babel-source 5.8.35
Using babosa 1.0.2
Using base32 0.3.2
Using bcrypt 3.1.11
Using sass 3.4.23
Using browser 2.2.0
Using bundler 1.13.6
Using charlock_holmes 0.7.3
Using chronic 0.10.2
Using numerizer 0.1.1
Using coffee-script-source 1.10.0
Using concurrent-ruby 1.0.0
Using connection_pool 2.2.0
Using safe_yaml 1.0.4
Using creole 0.5.0
Using orm_adapter 0.5.0
Using rotp 2.1.1
Using diff-lcs 1.2.5
Using diffy 3.0.6
Using email_reply_parser 0.5.8
Using equalizer 0.0.10
Using escape_utils 1.1.0
Using excon 0.54.0
Using expression_parser 0.9.1
Using ffi 1.9.10
Using formatador 0.2.1
Using ipaddress 0.8.3
Using rugged 0.24.0
Using get_process_mem 0.2.0
Using posix-spawn 0.3.11
Using gitlab-markup 1.5.1
Using rouge 2.0.2
Using stringex 2.6.1
Using request_store 1.3.0
Using hashie 3.4.4
Using mustermann19 0.4.3
Using temple 0.7.7
Using tilt 2.0.1
Using mimemagic 0.3.0
Using htmlentities 4.3.3
Using httpclient 2.7.1
Using jquery-atwho-rails 1.3.2
Using kgio 2.10.0
Using mail_room 0.8.1
Using method_source 0.8.2
Using mousetrap-rails 1.4.6
Using nested_form 0.3.2
Using net-ldap 0.12.1
Using net-ssh 3.2.0
Using oauth 0.4.7
Using oj 2.17.4
Using timfel-krb5-auth 0.8.3
Using pyu-ruby-sasl 0.0.3.3
Using rubyntlm 0.3.4
Using rubypants 0.6.0
Using pg 0.18.4
Using rack-cors 0.4.0
Using rainbow 2.1.0
Using raindrops 0.17.0
Using rdoc 4.2.1
Using redcarpet 3.3.4
Using redis 3.2.2
Using rinku 1.7.3
Using rqrcode 0.4.2
Using ruby-prof 0.16.2
Using rufus-scheduler 3.1.10
Using settingslogic 2.0.9
Using slack-notifier 1.2.1
Using state_machines 0.4.0
Using u2f 0.2.1
Using underscore-rails 1.8.2
Using unf_ext 0.0.7.2
Using version_sorter 2.1.0
Using vmstat 2.2.0
Using gemojione 3.1.0
Using influxdb 0.2.3
Using recaptcha 3.2.0
Using tzinfo 1.2.2
Using descendants_tracker 0.0.4
Using loofah 2.0.3
Using sanitize 2.1.0
Using ruby-saml 1.4.1
Using rack-test 0.6.3
Using warden 1.2.3
Using rack-accept 0.4.5
Using rack-attack 4.3.1
Using rack-protection 1.5.3
Using mail 2.6.4
Using fog-json 1.0.0
Using select2-rails 3.5.9.3
Using css_parser 1.3.6
Using faraday 0.9.2
Using httparty 0.13.7
Using attr_encrypted 3.0.1
Using autoprefixer-rails 6.6.1
Using uglifier 2.7.2
Using macaddr 1.7.1
Using babel-transpiler 0.7.0
Using chronic_duration 0.10.6
Using coffee-script 2.4.1
Using sprockets 3.7.0
Using crack 0.4.3
Using sys-filesystem 1.1.7
Using fog-core 1.42.0
Using gemnasium-gitlab-service 0.2.6
Using github-linguist 4.7.2
Using gollum-rugged_adapter

Bug#860926: zh translation for badblocks drifting due to bad column counting

2017-04-21 Thread Mingye Wang (Arthur2e5)


Package: e2fsprogs
Version: 1.43.4-2

The current version of e2fsprogs ships a complete Chinese translation. 
This is normally good news, just not quite so with badblocks which 
miscounts columns and gives too few `\b`'s for stepping back.


In zh_CN.po, badblock's status text is translated as:

进度 %6.2f%%，用时 %s。(%d/%d/%d 个错误)

When this goes onto a terminal, however, the user usually ends up 
getting something like:


进度 0.进度 0.进度 0.23%，用时 xx:xx:xx。(0/0/0 个错误)

As mentioned above, this error is caused by badblocks not counting 
columns correctly. Specifically, in misc.badblocks.c:print_status(), the 
number of \b's to use is determined by character counting from mbstowcs. 
Since CJK characters take up two columns onscreen, badblocks ends up 
giving one backspace short for each Chinese character found, and causes 
the screen to drift.


The fix is simple and straightforward -- just store the wstring and do 
some wcswidth counting on it. At the top of the function, declare:


#ifdef HAVE_MBSTOWCS
wchar_t wline_buf[128];
#endif

When it comes to counting columns, do:

#ifdef HAVE_MBSTOWCS
mbstowcs(wline_buf, line_buf, sizeof(line_buf));
len = wcswidth(wline_buf);
#endif

Optionally replace all instances of "len" with "cols", since that is 
what the \b step actually assuming.

--
Cheers,

Arthur2e5



signature.asc
Description: OpenPGP digital signature

Bug#859793: Messages at cnpbagwell.com about bug

2017-04-21 Thread Javier Serrano Polo

Dear Chris Bagwell,

Could you check your messages at cnpbagwell.com about a bug that were
sent from my address?

Thank you.


smime.p7s
Description: S/MIME cryptographic signature

Bug#860925: xfce4: laptop external monitor wallpaper stuck in tiled default

2017-04-21 Thread David Christensen

Package: xfce4
Version: 4.10.1
Severity: normal

Dear Maintainer,

I have a Dell Inspiron E1505/6400 laptop:

http://www.dell.com/support/home/us/en/04/product-support/servicetag/C86YXB1/configuration


I have upgraded the RAM to 2 @ 1 GB and upgraded the processor to an
Intel Core 2 T7400.


I am running Debian 8 with Xfce:

2017-04-21 15:58:26 root@jesse ~
# cat /etc/debian_version 
8.7

2017-04-21 15:58:48 root@jesse ~
# uname -a
Linux jesse 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 
GNU/Linux

2017-04-21 15:59:24 root@jesse ~
# dpkg-query --show xfce4
xfce4   4.10.1


I use an IOGEAR KVM switch:

https://www.iogear.com/product/GCS78KIT


I use an external keyboard, mouse, and LCD monitor (1920x1080
resolution) via a KVM switch.


When I first installed Debian 8, the wallpaper functioned correctly.


After updating Debian several weeks ago, the wall paper changed to
default (1024x768), tiled, and I am unable to adjust the wallpaper image
or the geometry.


I posted to the debain-user mailing list several
weeks ago:

https://lists.debian.org/debian-user/2017/04/msg00120.html


At that time, I indicated that the bug appeared after upgrading to the
following packages:

2017-04-05 20:38:21 dpchrist@jesse ~/src
$ grep upgrade /var/log/dpkg.log
2017-04-02 09:19:25 upgrade libfbembed2.5:amd64 2.5.3.26778.ds4-5 
2.5.3.26778.ds4-5+deb8u1
2017-04-02 09:19:28 upgrade firebird2.5-server-common:amd64 2.5.3.26778.ds4-5 
2.5.3.26778.ds4-5+deb8u1
2017-04-02 09:19:29 upgrade libfbclient2:amd64 2.5.3.26778.ds4-5 
2.5.3.26778.ds4-5+deb8u1
2017-04-02 09:19:30 upgrade firebird2.5-common:all 2.5.3.26778.ds4-5 
2.5.3.26778.ds4-5+deb8u1
2017-04-02 09:19:31 upgrade firebird2.5-common-doc:all 2.5.3.26778.ds4-5 
2.5.3.26778.ds4-5+deb8u1
2017-04-02 09:19:32 upgrade libgstreamer1.0-0:amd64 1.4.4-2 1.4.4-2+deb8u1
2017-04-02 09:19:34 upgrade libgstreamer-plugins-base1.0-0:amd64 1.4.4-2 
1.4.4-2+deb8u1
2017-04-02 09:19:35 upgrade libwbclient0:amd64 2:4.2.14+dfsg-0+deb8u4 
2:4.2.14+dfsg-0+deb8u5
2017-04-02 09:19:37 upgrade libsmbclient:amd64 2:4.2.14+dfsg-0+deb8u4 
2:4.2.14+dfsg-0+deb8u5
2017-04-02 09:19:38 upgrade samba-libs:amd64 2:4.2.14+dfsg-0+deb8u4 
2:4.2.14+dfsg-0+deb8u5
2017-04-02 09:19:40 upgrade samba-common:all 2:4.2.14+dfsg-0+deb8u4 
2:4.2.14+dfsg-0+deb8u5
2017-04-02 09:19:41 upgrade eject:amd64 2.1.5+deb1+cvs20081104-13.1 
2.1.5+deb1+cvs20081104-13.1+deb8u1
2017-04-02 09:19:42 upgrade gir1.2-gstreamer-1.0:amd64 1.4.4-2 1.4.4-2+deb8u1
2017-04-02 09:19:44 upgrade gir1.2-gst-plugins-base-1.0:amd64 1.4.4-2 
1.4.4-2+deb8u1
2017-04-02 09:19:44 upgrade gstreamer1.0-plugins-base:amd64 1.4.4-2 
1.4.4-2+deb8u1
2017-04-02 09:19:46 upgrade gstreamer1.0-plugins-good:amd64 1.4.4-2+deb8u2 
1.4.4-2+deb8u3
2017-04-02 09:19:48 upgrade gstreamer1.0-plugins-ugly:amd64 1.4.4-2+b1 
1.4.4-2+deb8u1
2017-04-02 09:19:50 upgrade gstreamer1.0-x:amd64 1.4.4-2 1.4.4-2+deb8u1 


Please advise.


David



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

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

Versions of packages xfce4 depends on:
ii  gtk2-engines-xfce  3.0.1-2
ii  libxfce4ui-utils   4.10.0-6
ii  orage  4.10.0-1+b2
ii  thunar 1.6.3-2
ii  xfce4-appfinder4.10.1-1
ii  xfce4-mixer4.10.0-3
ii  xfce4-panel4.10.1-1
ii  xfce4-session  4.10.1-10
ii  xfce4-settings 4.10.1-2
ii  xfconf 4.10.0-3
ii  xfdesktop4 4.10.2-3
ii  xfwm4  4.10.1-3

Versions of packages xfce4 recommends:
ii  desktop-base  8.0.2
ii  tango-icon-theme  0.8.90-5
ii  thunar-volman 0.8.0-4
ii  xfce4-notifyd 0.2.4-3
ii  xorg  1:7.7+7

Versions of packages xfce4 suggests:
pn  gtk3-engines-xfce
ii  xfce4-goodies4.10
ii  xfce4-power-manager  1.4.1-1

-- no debconf information

Bug#860920: manpages.debian.org support (dman)

On 2017-04-22 00:44:28, Axel Beckert wrote:
> Control: tag -1 + pending
>
> Hi,
>
> Antoine Beaupré wrote:
>> > W: debian-goodies source: file-without-copyright-information dman.1
>> >
>> > The file itself doesn't contain a license statement. Under which
>> > license is dman.1?
>> 
>> Didn't run lintian, did i... :)
>
> *g*
>
>> Whatever really - let's stick to the same license dman itself uses to
>> simplify thing, i think GPL-3+?
>
> Thanks, added and pushed together with your commits to the git master
> branch.

Awesome, thanks!

A.

-- 
A riot is the language of the unheard.
 - Martin Luther King, Jr.

Bug#860924: unblock libguestfs/1:1.34.6-2

2017-04-21 Thread Hilko Bengen

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

Dear release team,

please unblock version 1:1.34.6-2 of package libguestfs. All it changes
is re-enabling building for all architectures including mips which had
previously been excluded (#816610).

Cheers,
-Hilko

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

Kernel: Linux 4.9.0-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru libguestfs-1.34.6/debian/changelog libguestfs-1.34.6/debian/changelog
--- libguestfs-1.34.6/debian/changelog	2017-03-09 10:14:14.0 +0100
+++ libguestfs-1.34.6/debian/changelog	2017-04-20 23:08:05.0 +0200
@@ -1,3 +1,11 @@
+libguestfs (1:1.34.6-2) unstable; urgency=medium
+
+  * Re-enable building on mips. Thanks to Aurelien Jarno for pointing out
+that #815409 was a kernel bug rather than a bug in qemu. (Closes:
+#816610)
+
+ -- Hilko Bengen   Thu, 20 Apr 2017 23:08:05 +0200
+
 libguestfs (1:1.34.6-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru libguestfs-1.34.6/debian/control libguestfs-1.34.6/debian/control
--- libguestfs-1.34.6/debian/control	2017-01-31 23:48:20.0 +0100
+++ libguestfs-1.34.6/debian/control	2017-04-20 23:08:05.0 +0200
@@ -116,7 +116,7 @@
 XS-Ruby-Versions: all
 
 Package: guestfsd
-Architecture: amd64 arm64 armel armhf i386 mipsel mips64el powerpc ppc64el s390x ppc64
+Architecture: linux-any
 Depends: ${shlibs:Depends}, ${misc:Depends},
   bsdmainutils,
   diffutils,
@@ -145,7 +145,7 @@
 
 Package: libguestfs-dev
 Section: libdevel
-Architecture: amd64 arm64 armel armhf i386 mipsel mips64el powerpc ppc64el s390x ppc64
+Architecture: linux-any
 Multi-Arch: same
 Depends: libguestfs0 (= ${binary:Version}), ${misc:Depends}
 Conflicts: libguestfs0 (<< 1:1.14.9-1~)
@@ -157,7 +157,7 @@
 
 Package: libguestfs0
 Section: libs
-Architecture: amd64 arm64 armel armhf i386 mipsel mips64el powerpc ppc64el s390x ppc64
+Architecture: linux-any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends},
@@ -204,7 +204,7 @@
 
 Package: libguestfs-gfs2
 Section: libs
-Architecture: amd64 arm64 armel armhf i386 mipsel mips64el powerpc ppc64el s390x ppc64
+Architecture: linux-any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: libguestfs0 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
@@ -218,7 +218,7 @@
 
 Package: libguestfs-hfsplus
 Section: libs
-Architecture: amd64 arm64 armel armhf i386 mipsel mips64el powerpc ppc64el s390x ppc64
+Architecture: linux-any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: libguestfs0 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
@@ -231,7 +231,7 @@
 
 Package: libguestfs-jfs
 Section: libs
-Architecture: amd64 arm64 armel armhf i386 mipsel mips64el powerpc ppc64el s390x ppc64
+Architecture: linux-any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: libguestfs0 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
@@ -244,7 +244,7 @@
 
 Package: libguestfs-nilfs
 Section: libs
-Architecture: amd64 arm64 armel armhf i386 mipsel mips64el powerpc ppc64el s390x ppc64
+Architecture: linux-any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: libguestfs0 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
@@ -257,7 +257,7 @@
 
 Package: libguestfs-reiserfs
 Section: libs
-Architecture: amd64 arm64 armel armhf i386 mipsel mips64el powerpc ppc64el s390x ppc64
+Architecture: linux-any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: libguestfs0 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
@@ -270,7 +270,7 @@
 
 Package: libguestfs-rescue
 Section: libs
-Architecture: amd64 arm64 armel armhf i386 mipsel mips64el powerpc ppc64el s390x ppc64
+Architecture: linux-any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: libguestfs0 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
@@ -285,7 +285,7 @@
 
 Package: libguestfs-rsync
 Section: libs
-Architecture: amd64 arm64 armel armhf i386 mipsel mips64el powerpc ppc64el s390x ppc64
+Architecture: linux-any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: libguestfs0 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
@@ -299,7 +299,7 @@
 
 Package: libguestfs-xfs
 Section: libs
-Architecture: amd64 arm64 armel armhf i386 mipsel mips64el powerpc ppc64el s390x ppc64
+Architecture: linux-any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: libguestfs0 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
@@ -325,7 +325,7 @@
 
 Package: libguestfs-tools
 Section: admin
-Architecture: amd64 arm64 armel armhf i386 mipsel mips64el powerpc ppc64el s390x ppc64
+Architecture: linux-any
 Depends:

Bug#833114: Preparing NMU.

2017-04-21 Thread Étienne Millon

Hi,

Thanks for the NMU, this is appreciated.
You can go ahead and upload it immediately if you wish to do so.

I think that your remark about the activity on this package was rude, and I
am surprised that it comes from a Debian Developer who should know better
that motivation and time come and go. The NMU process is here precisely for
that.

Cheers

Bug#860920: manpages.debian.org support (dman)

Control: tag -1 + pending

Hi,

Antoine Beaupré wrote:
> > W: debian-goodies source: file-without-copyright-information dman.1
> >
> > The file itself doesn't contain a license statement. Under which
> > license is dman.1?
> 
> Didn't run lintian, did i... :)

*g*

> Whatever really - let's stick to the same license dman itself uses to
> simplify thing, i think GPL-3+?

Thanks, added and pushed together with your commits to the git master
branch.

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#833114: Preparing NMU.

2017-04-21 Thread Hilko Bengen

control: severity -1 grave
control: tag -1 pending

I can reproduce the issue here and find it quite remarkable that nothing
has been done about this bug (or about the package at all for that
matter) in over a year.

So, I am preparing an NMU to DELAYED/2. Feel free to cancel or
reschedule, whatever. Debdiff attached.

Cheers,
-Hilko
diff -Nru rss2email-3.9/debian/changelog rss2email-3.9/debian/changelog
--- rss2email-3.9/debian/changelog	2015-11-23 22:02:41.0 +0100
+++ rss2email-3.9/debian/changelog	2017-04-22 00:29:25.0 +0200
@@ -1,3 +1,11 @@
+rss2email (1:3.9-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream patch to deal with "OrderedDict mutated during iteration"
+error (Closes: #833114)
+
+ -- Hilko Bengen   Sat, 22 Apr 2017 00:29:25 +0200
+
 rss2email (1:3.9-2) unstable; urgency=medium
 
   * Bump Standards-Version to 3.9.6 (no changes needed)
diff -Nru rss2email-3.9/debian/patches/833114.patch rss2email-3.9/debian/patches/833114.patch
--- rss2email-3.9/debian/patches/833114.patch	1970-01-01 01:00:00.0 +0100
+++ rss2email-3.9/debian/patches/833114.patch	2017-04-22 00:14:16.0 +0200
@@ -0,0 +1,49 @@
+From 60870d9ff7f23441919df79d710ad49ecbcedf73 Mon Sep 17 00:00:00 2001
+From: "W. Trevor King" 
+Date: Wed, 25 Feb 2015 10:07:34 -0800
+Subject: [PATCH] feed: Don't pop from extra_headers while iterating over it
+
+Avoid:
+
+  Traceback (most recent call last):
+...
+  for k,v in extra_headers.items():
+File "/.../Python-3.5.0a1/Lib/_collections_abc.py", line 503, in __iter__
+  for key in self._mapping:
+File "/.../Python-3.5.0a1/Lib/collections/__init__.py", line 112, in __iter__
+  yield curr.key
+  AttributeError: 'NoneType' object has no attribute 'key'
+
+from continuing to iterate on items() after popping a key.  This
+worked in Python 3.4 but no longer works in Python 3.5.  In any case,
+mutating an object while iterating over it is always a bit
+questionable, so rephrase to find the keys in one pass, and then
+remove them after the iteration completes.
+
+Reported-by: Raniere Silva 
+Signed-off-by: W. Trevor King 
+---
+ rss2email/feed.py | 7 ---
+ 1 file changed, 4 insertions(+), 3 deletions(-)
+
+diff --git a/rss2email/feed.py b/rss2email/feed.py
+index ec5c4f6..f2750ef 100644
+--- a/rss2email/feed.py
 b/rss2email/feed.py
+@@ -470,9 +470,10 @@ class Feed (object):
+ ('X-RSS-URL', self._get_entry_link(entry)),
+ ('X-RSS-TAGS', self._get_entry_tags(entry)),
+ ))
+-for k,v in extra_headers.items():  # remove empty tags, etc.
+-if v is None:
+-extra_headers.pop(k)
++# remove empty tags, etc.
++keys = {k for k, v in extra_headers.items() if v is None}
++for key in keys:
++extra_headers.pop(key)
+ if self.bonus_header:
+ for header in self.bonus_header.splitlines():
+ if ':' in header:
+-- 
+2.11.0
+
diff -Nru rss2email-3.9/debian/patches/series rss2email-3.9/debian/patches/series
--- rss2email-3.9/debian/patches/series	2015-11-23 22:02:34.0 +0100
+++ rss2email-3.9/debian/patches/series	2017-04-22 00:14:46.0 +0200
@@ -4,3 +4,4 @@
 sslv3.patch
 dont-overwrite-config.patch
 prettify.patch
+833114.patch

Bug#860920: manpages.debian.org support (dman)

On 2017-04-21 23:48:54, Axel Beckert wrote:
> Hi Antoine,
>
> Antoine Beaupré wrote:
>> >> Or should we just make an upload to experimental?
>> >
>> > That would be an idea. Will do.
>> 
>> Thanks!!
>
> One more question before that. Lintian argues:
>
> W: debian-goodies source: file-without-copyright-information dman.1
>
> The file itself doesn't contain a license statement. Under which
> license is dman.1?

Didn't run lintian, did i... :)

Whatever really - let's stick to the same license dman itself uses to
simplify thing, i think GPL-3+?

a.

-- 
The most prudent course for any society is to start from the
assumption that the Internet should be fundamentally outside the
domain of capital.
- The Internet's Unholy Marriage to Capitalism


signature.asc
Description: PGP signature

Bug#860923: src:dask: New upstream release

2017-04-21 Thread Ghislain Antony Vaillant

Package: src:dask
Severity: wishlist

Dear Maintainer,

A new version of Dask is out (0.14.1) and is required for the latest
version of src:python-xarray. Please consider updating the packaging.

Thanks,
Ghis


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

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

Bug#860908: perl 5.24 segfaults during a dpkg -i of cmanager (and other packages)

2017-04-21 Thread Brad Barnett



 
> Can you reproduce the segfault reliably by running:
> 
>  "deb-systemd-helper unmask cgmanager.service >/dev/null"
> 
> With Perl 5.24?
> 

Hmm.

root@newoldbe:/var/cache/apt/archives# deb-systemd-helper unmask
cgmanager.service >/dev/null /usr/bin/deb-systemd-helper was not called
from dpkg. Exiting.

No segfault.



Now that my system is working, I just completed the apt-get -f, made sure
sysvinit was installed, removed systemd, purged it and such.

I then did a purge of cgmanager and others (they were pulled in for some
reason with sysvinit), and tried a fresh install.  It's fine.

deb-systemd-helper still says the same as the above, with no segfault.

Bug#860920: manpages.debian.org support (dman)

Hi Antoine,

Antoine Beaupré wrote:
> >> Or should we just make an upload to experimental?
> >
> > That would be an idea. Will do.
> 
> Thanks!!

One more question before that. Lintian argues:

W: debian-goodies source: file-without-copyright-information dman.1

The file itself doesn't contain a license statement. Under which
license is dman.1?

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#860920: manpages.debian.org support (dman)

On 2017-04-21 23:18:04, Axel Beckert wrote:
> Hi Antoine,
>
> Antoine Beaupré wrote:
>> There's already one patch pending for stretch/unstable now
>> (#84/4480e81). Is that planned for stretch?
>
> Not necessarily. Only if there's an RC bug found in debian-goodies.
>
>> Or should we just make an upload to experimental?
>
> That would be an idea. Will do.

Thanks!!

A.

-- 
Every time I see an adult on a bicycle I no longer despair for the
future of the human race.
 - H. G. Wells

Bug#860910: screen: support baudrate of 1500000

Control: tag -1 - moreinfo
Control: clone -1 -2
Control: forwarded -1 
https://savannah.gnu.org/bugs/?func=detailitem_id=45741
Control: retitle -2 screen: Should error out on unsupported baud rates instead 
of showing garbled data
Control: severity -2 normal

Hi Vagrant,

Vagrant Cascadian wrote:
> > I currently assume that screen doesn't do that. But I'm not sure
> > either.
> 
> At the very least, it could fail and issue an error with unsupported
> baud rates, rather than silently transmitting and recieving garbled
> data...

Granted. But that should probably be a separate bug request. Will file
a separate bug report upstream once I know the number of the cloned
bug report.

> I don't know how common it is, but I've encountered it with the
> firefly-rk3399:

Thanks for the details!

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#860515: Many translations missing in french KDE lang packages while we're close to release

2017-04-21 Thread Julien Aubin

Hi,

Just checked with a new virgin session to ensure it was not wrong settings
and my side and sadly it is not. The French translations in KDE have
something wrong, definitely (as Polish translations for example are
complete except for the few fields in Kmail editor settings) while the
French ones are far from complete.

Rgds

2017-04-20 18:37 GMT+02:00 Julien Aubin :

> After checking again on polish translations everything is there :
> ok/cancel properly translated, kmail antivirus/antispam wizard, ... The
> only missing translations is in Kmail settings / editor configuration.
>
> So the issue has definitely nothing to see with code but with faultly
> french lang package.
>
> Rgds
>
> 2017-04-20 10:35 GMT+02:00 Julien Aubin :
>
>> Hi
>>
>> Okay check in Kmail settings / editor configuration. Kmail antivirus /
>> antispam wizard left untranslated.
>> In system settings the confirm dialog does contain untranslated buttons
>> but situation has improved.
>> Window configure shortcuts in Dolphin / Konsole is partly left
>> untranslated (click manage schemes).
>> Kate menu file > save as with encoding
>>
>>
>> On Polish locales ok / apply / cancel is translated. Now in French
>> translation is correct when you right click on the clock and reach clock
>> settings. Basically in French 95% of the bottom dialog buttons are
>> untranslated (ex : konsole settings) while polish is not affected.
>> Kopete is also fully translated.
>>
>> Kdevelop browse menu : jump to next / previous
>>
>>
>> Note : if the issue was just ok / apply / cancel I would not have set
>> such high severity.
>>
>> My locale : fr_FR.UTF-8
>>
>>
>> Le 20 avr. 2017 10:12, "Maximiliano Curia"  a écrit :
>>
>> ¡Hola Julien!
>>
>>
>> El 2017-04-20 a las 09:53 +0200, Julien Aubin escribió:
>>
>>> There are also many missing translations in Kmail, System settings and
>>> so on.
>>>
>>
>> "Many" is unspecific, we can't check for "many" missing translations, if
>> you are refering to the Ok/Apply/Cancel buttons I would guess it's the same
>> issue described in the previous mail.
>>
>>
>> Oddly enough I could test on a Polish computer and here (polish)
>>> translations are correct notably in systemsettings.
>>>
>>
>> Can you point to a specific text? Are you claiming that the
>> Ok/Apply/Cancel buttons are translated using a polish locales?
>>
>>
>> I know severity is overrated (and I opened it previously which is bad but
>>> as nothing happened...) but such a bug has to be fixed before release. As
>>> well Gentoo has never been affected with such issue.
>>>
>>
>> Please don't abuse the bug tracking system. And, please provide
>> information in a way that the issue is easily reproducible and easy to
>> check for someone that doesn't have your background (doesn't speak french,
>> or polish, doesn't know what to look for in the window, etc).
>>
>> Happy hacking,
>> --
>> "recursividad 95, 154, 156, 201, 224, 293"
>> -- El Lenguaje de Programacion C, pag. 293 (Kernighan & Ritchie)
>>
>> Saludos /\/\ /\ >< `/
>>
>>
>>
>

Bug#859432: nss-pam-ldapd shouldn't disable PIE

2017-04-21 Thread Arthur de Jong

Control: tags -1 + pending

On Mon, 2017-04-03 at 16:10 +0300, Adrian Bunk wrote:
> With gcc in stretch defaulting to PIE, hardening=+all,-pie changed
> semantics from "enable hardening but not PIE" to "enable all
> hardening and explicitely disable the default PIE".
> The latter is usually not intended.

Thanks for pointing this out and including a patch. This will be fixed
in the next upload.

Thanks,

-- 
-- arthur - adej...@debian.org - https://people.debian.org/~adejong --


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

Bug#860920: manpages.debian.org support (dman)

Hi Antoine,

Antoine Beaupré wrote:
> There's already one patch pending for stretch/unstable now
> (#84/4480e81). Is that planned for stretch?

Not necessarily. Only if there's an RC bug found in debian-goodies.

> Or should we just make an upload to experimental?

That would be an idea. Will do.

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#860910: screen: support baudrate of 1500000

2017-04-21 Thread Vagrant Cascadian

Thanks for the quick response!

On 2017-04-21, Axel Beckert wrote:
> Vagrant Cascadian wrote:
>> Highest speed listed in the source tty.sh (which produces tty.c) is
>> 460800, but it's unclear to me if it also dynamically determines
>> appropriate values for baud rates somehow...
>
> I currently assume that screen doesn't do that. But I'm not sure
> either.

At the very least, it could fail and issue an error with unsupported
baud rates, rather than silently transmitting and recieving garbled
data...


> Is 150 a common baudrate? It doesn't seem to be a multiple of one
> of the common baudrates as I would expect.


I don't know how common it is, but I've encountered it with the
firefly-rk3399:

  http://wiki.t-firefly.com/index.php/Firefly-RK3399/Serial_debug/en

There are two boards in the linux-next tree which use it:

  arch/arm/boot/dts/rk1108-evb.dts:   stdout-path = 
"serial2:150n8";
  arch/arm64/boot/dts/rockchip/rk3328-evb.dts:stdout-path = 
"serial2:150n8";


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#860920: manpages.debian.org support (dman)

On 2017-04-21 22:36:10, Axel Beckert wrote:
>> even though this is collab-maint, I didn't feel comfortable just
>> doing a NMU of this thing without first consulting you.
>
> IMHO this is no more suitable for Stretch, so I'd merge that branch
> after the Stretch release.
>
> But I don't see any reason why we shouldn't merge this.

Great!

There's already one patch pending for stretch/unstable now
(#84/4480e81). Is that planned for stretch?

Or should we just make an upload to experimental?

In other words, should I merge this in master and NMU to experimental?

Or I just let you drive the rest of the way?

I'm fine either way. :)

A.
-- 
Secrecy is the keystone to all tyranny. Not force, but secrecy and
censorship.
   -  Robert A. Heinlein

Bug#835138: it's a matter of char signedness

2017-04-21 Thread Adam Borowski

Control: tags -1 +patch

Hi!
The failure comes from the assumption that char is signed.  That's true on
x86 and mips, but not on a number of other architectures.

A proper fix would require changing hundreds of places in the code; a quick
and dirty patch of compiling with -fsigned-char risks some trouble when
using external headers, but it appears to work for me -- at least it builds
ok and passes the testsuite.

Tested on arm64 and armhf, I assume the patch should also help on armel
ppc64el s390x powerpc ppc64; the FTBFS on x32 is unrelated.

-- 
⢀⣴⠾⠻⢶⣦⠀ Meow!
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Collisions shmolisions, let's see them find a collision or second
⠈⠳⣄ preimage for double rot13!
diff -Nru form-4.1/debian/changelog form-4.1/debian/changelog
--- form-4.1/debian/changelog	2016-07-29 11:55:40.0 +0200
+++ form-4.1/debian/changelog	2017-04-21 21:55:58.0 +0200
@@ -1,3 +1,10 @@
+form (4.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS on architectures with unsigned char (arm*, ppc*, s390x).
+
+ -- Adam Borowski   Fri, 21 Apr 2017 21:55:58 +0200
+
 form (4.1-1) unstable; urgency=medium
 
   * Initial release. (Closes: #832903)
diff -Nru form-4.1/debian/rules form-4.1/debian/rules
--- form-4.1/debian/rules	2016-07-29 11:55:40.0 +0200
+++ form-4.1/debian/rules	2017-04-21 21:04:29.0 +0200
@@ -5,6 +5,7 @@
 
 # see FEATURE AREAS in dpkg-buildflags(1)
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+export DEB_CFLAGS_MAINT_APPEND = -fsigned-char
 
 %:
 	dh $@ --with autotools_dev --parallel

Bug#860910: screen: support baudrate of 1500000

Control: tag -1 + moreinfo upstream

Hi Vagrant,

Vagrant Cascadian wrote:
> Highest speed listed in the source tty.sh (which produces tty.c) is
> 460800, but it's unclear to me if it also dynamically determines
> appropriate values for baud rates somehow...

I currently assume that screen doesn't do that. But I'm not sure
either.

Is 150 a common baudrate? It doesn't seem to be a multiple of one
of the common baudrates as I would expect.

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#860920: manpages.debian.org support (dman)

Control: tag -1 + confirmed

Hi Antoine!

Antoine Beaupre wrote:
> I have pushed my work in a feature branch on the git repository here:

Already had a look at it when I got the push notifications. :-)

> I haven't merged this directly in master because,

Thanks!

> even though this is collab-maint, I didn't feel comfortable just
> doing a NMU of this thing without first consulting you.

IMHO this is no more suitable for Stretch, so I'd merge that branch
after the Stretch release.

But I don't see any reason why we shouldn't merge this.

> The associated issue in the debiman project, which runs
> manpages.debian.org, is here:
> 
> https://github.com/Debian/debiman/issues/57

Subscribed to it, 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#860921: RFS: python-ordered-set/2.0.2-1 [ITP]

2017-04-21 Thread Ghislain Antony Vaillant

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

* Package name: python-ordered-set
  Version : 2.0.2-1
  Upstream Author : Luminoso Technologies, Inc.
* URL : https://github.com/LuminosoInsight/ordered-set/
* License : Expat
  Section : python

One can check out the package by visiting the following URL:

  https://anonscm.debian.org/git/python-modules/packages/python-ordered-set.git

Changes since the last upload:

  * Initial release. (Closes: #860768)

Best regards,
Ghis

Bug#860082: xfce4-equake-plugin: Display quake history

2017-04-21 Thread Jeroen van Aart


On 04/11/2017 01:49 AM, Stephan Seitz wrote:

Package: xfce4-equake-plugin
Version: 1.3.8.1-2
Severity: wishlist

Dear Maintainer,

for now the plugin shows the last quake that happened.

Would it be possible to have a (configurable) history so that for
example the last ten quakes are displayed?


Thank you for your request.

I believe the feature you requested already is present, more or less. If 
you right click on the plugin you will find menu options to display 
earthquakes of the last hour, day and week.


If you mean a (configurable) history in the panel itself. I believe that 
may fall out of the scope of a simple panel plugin. It would make the 
plugin more complex than necessary or desired.

Bug#860920: manpages.debian.org support (dman)

2017-04-21 Thread Antoine Beaupre

Package: debian-goodies
Version: 0.69
Severity: wishlist
Tags: patch

Hi!

We have been working hard on restoring the manpages.debian.org service
in the last months. It's now reliable and complete, yet you need a web
browser to use it.

The neat thing is: manpages.debian.org also ships actual manpages, so
it's possible to use it to get the actual manpage source and load it
locally. This idea first came up over Ubuntu's side as the "dman"
command. This command was never packaged - it is just available on the
manpages.ubuntu.com webpage.

Yet we want people to be able to use this directly right now. The
proper way to ship software is, of course, to use Debian
packages. Since this is just a small shell script, we didn't quite
know where to put it. There's man-db, but that's rather a beastly
thing and the proper thing to do there would be to just patch
/usr/bin/man to check online if the requested manpage is missing
locally. Unfortunately, man is written in C and that would mean a
significant change in that venerable software - easier to just keep
the shell script.

I noticed debian-goodies was already shipping with similar tools:
debman allows a user to browse manpages from an existing .deb or
download the missing .deb if necessary. dman takes a similar approach,
but offloads the extraction to the static manpages.debian.org mirror,
saving a lot of time. It also avoids a lot of guessing, because the
user doesn't need to know which package the manpage is in - the
manpages.debian.org redirector does that for you.

I've considered implementing this as an extension to debman, but it
seemed a little clunky: the functionality is completely orthogonal and
there is very little code reuse between the two programs, if maybe man
-l. :) So I figured it made sense to keep the program separate. In
time, maybe it can trickle down to Ubuntu and we can share a common
codebase there as well.

I have pushed my work in a feature branch on the git repository here:

https://anonscm.debian.org/git/collab-maint/debian-goodies.git/log/?h=debiman-support

I haven't merged this directly in master because, even though this is
collab-maint, I didn't feel comfortable just doing a NMU of this
thing without first consulting you.

You can review the source code here:

https://anonscm.debian.org/git/collab-maint/debian-goodies.git/tree/dman?h=debiman-support

The associated issue in the debiman project, which runs
manpages.debian.org, is here:

https://github.com/Debian/debiman/issues/57

Thank you for your consideration!

-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing'), (1, 'unstable')
Architecture: amd64
(x86_64)
Foreign Architectures: armhf

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

Versions of packages debian-goodies depends on:
ii curl 7.52.1-4
ii dctrl-tools [grep-dctrl] 2.24-2+b1
ii dialog1.3-20160828-2
ii perl 5.24.1-2
ii python3 3.5.3-1
ii whiptail 0.52.19-1+b1

Versions of packages debian-goodies recommends:
ii lsof 4.89+dfsg-0.1

Versions of packages debian-goodies suggests:
ii popularity-contest 1.64
ii xdg-utils 1.1.1-1
ii zenity 3.22.0-1+b1

-- no debconf information

Bug#860919: menu file missing from new package

2017-04-21 Thread Matus UHLAR - fantomas


Package: firefox-esr
Version: 45.9.0esr-1~deb8u1

the firefox-esr package for jessie is missing menu file.
Please provide menu file for jessie version.

--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
42.7 percent of all statistics are made up on the spot.

Bug#860918: menu file missing from new package

2017-04-21 Thread Matus UHLAR - fantomas


Package: thunderbird
Version: 1:45.8.0-3~deb8u1


the thunderbird package for jessie is missing menu file.
Please provide menu file for jessie version
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
I just got lost in thought. It was unfamiliar territory.

Bug#860885: systemd fails to mount five of six system files indicated in /etc/fstab

2017-04-21 Thread MERLIN Philippe

Le vendredi 21 avril 2017, 21:18:07 CEST Michael Biebl a écrit :
> Control: tags -1 + moreinfo
> 
> Am 21.04.2017 um 15:04 schrieb phil-deb1.merlin:
> > Package: systemd
> > Version: 232-22
> > Severity: important
> 
> Can you share more details, like:
> Is this problem reproducible on every boot?
> Does it only happen for certain file systems/drives, i.e. are only file
> systems affected which are *not* on /dev/sda?
> 
> How are your drives connected?
Thank you for looking into my problem so quickly
1)Yes Its reproducible on every boot
2)Not the Swap is /dev/sda1 and its fail to mount
3) Two Disks IDE , One Disk Sata (Sda)

Bug#860254: [Pkg-openssl-devel] Bug#860254:

2017-04-21 Thread Sebastian Andrzej Siewior

On 2017-04-20 09:35:27 [+], Jonathon Delgado wrote:
> Even if something in this script requires full perl, many ca-certificate 
> users won't run it after the initial install (of ca-certificates), and apt 
> won't let me uninstall just perl because of the hard dependency.

The openssl package ships perl scripts. Those scripts require perl which
means that this package depends on perl and this dependency is
automatically added by debhelper as per policy.

Why the need for the `openssl' but no `perl' package? I don't have a
single a box around without perl installed.

Sebastian

Bug#860917: unblock (pre-approval): liferea/1.12~rc3-1

2017-04-21 Thread Paul Gevers

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I am solicitating your opinion on a possible unblock for the package liferea in
case I would upload the third release candidate of upstream. I hadn't
considered packaging that for Debian because it was released after the Stretch
freeze, but I was tricked into asking you this in (normal) bug 860742¹, which
was already fixed upstream. In the discussion in that bug, it turned out that
this third release candidate actual fixes a data-loss bug (not yet filed in the
BTS) and "the other changes look low risk".

Because I already included a rather large commit that now is included in the
upstream package, I provide you with a diff between the PATCHED source trees
(including the debian directory), which I created with the following command. I
excluded the translation files because there were a lot of changes there only
due to line number changes:

diff -U3 --exclude=.pc --exclude=.git --exclude="*.po" --recursive liferea_copy 
liferea > /tmp/liferea_1.12~rc3-1.tree.diff

The png files that are removed/new are actually renames, where git tells me:
diff --git a/pixmaps/flag.png b/pixmaps/emblem-important.png
similarity index 100%
rename from pixmaps/flag.png
rename to pixmaps/emblem-important.png
diff --git a/pixmaps/vfolder.png b/pixmaps/folder-saved-search.png
similarity index 100%
rename from pixmaps/vfolder.png
rename to pixmaps/folder-saved-search.png
diff --git a/pixmaps/directory.png b/pixmaps/folder.png
similarity index 100%
rename from pixmaps/directory.png
rename to pixmaps/folder.png
diff --git a/pixmaps/attachment.png b/pixmaps/mail-attachment.png
similarity index 100%
rename from pixmaps/attachment.png
rename to pixmaps/mail-attachment.png

Thanks for considering. (Of course, the alternative is to just cherry-pick the
fix for the data-loss issue, which is upstream #208: All "Unread" search folder
items marked read at once)

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

unblock liferea/1.12~rc3-1

- -- System Information:
Debian Release: 9.0
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (200, 'experimental'), 
(200, 'testing'), (50, 'experimental'), (50, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlj6ZRYACgkQnFyZ6wW9
dQotTAf+KlgDvXqp0l7ITtl2Qs5ZlKm4ChrYtD9yOMH2f4zI+LHoIdfLkHw7zLWA
MlYoXvLIIVcisLDwg00oNh7zIIPQGXR+OSsM/jCsQS0WoZRg3w73F145QhHOYWfQ
GXuse0dMaqMq6uxfM7fIAsfy1JqTZWONfHpFa7jSSyQ5OvPL9/VQOQTwTbFuAXDB
PPz0arOybgTFSY0lEBZJLhENEb+riJ309VwgvU+aTUdBNPoizWyLrG7ql8vBpY9A
bp+BXAjzR28Woc3VsZHoAzeYPx1GsDX4ktB6TNqRo6vqC7S9DBnIW9ytod2F6DuK
Jk/gxy1oURGPwHMrgQR43DkIMBUh7A==
=2ca5
-END PGP SIGNATURE-
diff -U3 '--exclude=.pc' '--exclude=.git' '--exclude=*.po' --recursive 
liferea_copy/AUTHORS liferea/AUTHORS
--- liferea_copy/AUTHORS2017-04-21 11:45:45.557518685 +0200
+++ liferea/AUTHORS 2017-04-20 22:14:05.991686035 +0200
@@ -108,7 +108,7 @@
 Japanese   Takeshi Hamasaki 
 JapaneseIWAI, Masaharu 
 French Vincent Lefèvre 
-French Guillaume Bernard 
+French Guillaume Bernard 
 SwedishDaniel Nylander 
 SwedishAndreas Ronnquist 

 TurkishMehmet Atif Ergun 
diff -U3 '--exclude=.pc' '--exclude=.git' '--exclude=*.po' --recursive 
liferea_copy/ChangeLog liferea/ChangeLog
--- liferea_copy/ChangeLog  2017-04-21 11:45:45.557518685 +0200
+++ liferea/ChangeLog   2017-04-20 22:14:05.991686035 +0200
@@ -1,6 +1,31 @@
 Open problems before 1.12 release
 
* Article skimming currently broken
+   * Tray icon needs to be auto-disabled along with a popup
+ informing users who previously had it enabled
+
+2017-03-26   Lars Windolf 
+
+   Version 1.12-rc3
+
+   * Fixes #459: Fixes GtkDoc warnings
+ (Leiaz)
+   * Fixes #415: Filter commands are not asynchronous
+ (Rich Coe)
+   * Fixes #363: Missing space above internal browser address bar
+ (reported by nekohayo, patch by Mikel Olasagasti)
+   * Fixes #208: All "Unread" search folder items marked read at once
+ (Leiaz)
+   * Fixes #251: Liferea does not always use theme icons when it is 
launched
+ on system startup (reported by GreenLunar, fix by Leiaz)
+
+   * Updated Finnish translation (Jorma Karvonen)
+   * Updated

Bug#851359: diffoscope: Improve support for comparing images

2017-04-21 Thread Chris Lamb

Hey Maria,

> […]

This is _awesome_! For those who haven't tried this yet, take a look
at:

  http://i.imgur.com/tLHNl5H.jpg


Some very quick thoughts:

- I don't quite follow what Config().html_output is used for (ie.
  needs some comments, etc)

  Perhaps this doesn't need to be a global but rather part of the
  presenter it feels like a bit of an abstraction-layer violation to
  be there.

- Some cosmetic things re. import ordering and superfluous/misleading
  parens, eg.

- if content_diff is not None:
+ if (content_diff is not None) and Config().html_output
 ^^
 
- You also seem to have the "Emacs"-style Python identation, which
  lines up stuff like so:

   logger.debug('Generating visual difference for %s and %s',
self.path, other.path)

  This is suboptimal because changing "logger.debug" means you have
  to adjust the identation of the essentially unrelated line underneath,
  causing unnecessary diff noise.


Regards,

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

Bug#860916: RM: libapache2-authenntlm-perl -- ROM; RC buggy, inactive upstream

Package: ftp.debian.org
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


As discussed in #857327, libapache2-authenntlm-perl seems to be
broken since years without anyone noticing. Instead of trying to fix
code which is abondoned upstream, we'd rather remove the package as
apparently noone is using it anyway.


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlj6YwhfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZv6w/+Nw5eeo1gYH5a5ROIf+zlwF9ZAeZwN5jmOfoA5omiLL4wRDzx0FrR5Liy
qSViNfv6sCGrqDoOgL2EzvAdnnO+YucKb+y6IdFvr7S5wH75NHBiKMxRDyQ8lPWP
HFWbSMqE9sq5i1gSTymWD+Y3gvH28SiplRAKYYAL5qSQWP6nb5G7ekSF31U0q6K0
ZLi5YmMLfrHcQyRETzSczESJ8tJ5N9/qZIZAy8yiCggpsdU7jXkSHYmR+WFFDV9J
ifqysIv43qlZCUXD5LJ24SpGSWCVcN4aH5rTj4KKQgk4hIPQ5oDAPKLTh05LkU8w
OCqZfMIyW0W/j8aNNmovvj7Y3oYWHnfnayL1unxniX4wK35lYf355h1AV1nrvADi
OEmda/sIWghhoA6UKnPHFS6rNOfn2PcJWhMxlrsbBUqtkU9K2rJhc9L43N8HMeod
x0IGDH8XGV/z29XHhVPSuwRkfWy959n9OojokqCNVX26LLXYLnPvymOgtf7wqkd6
WDePBK+SDlWjZ+5h8e7cPqH+zpbKrD7xg1AtZdwnGwHzHUTi7iXow2ZBWcnEqPJF
xTBAY/a01VkeVJzF/pBpoytvjbRVigbW3KY1No2xm7Xx6n83jd6SfF5/GsVP2FB4
5qb8qmZbfRGliZ+rdYhztJxRfBCQ/FSmJJe3ujp5A3/EUxDXgVA=
=aNux
-END PGP SIGNATURE-

Bug#857238: Bug#860914: RM: libwww-dict-leo-org-perl/1.39-1

On Fri, 21 Apr 2017 21:38:26 +0200, gregor herrmann wrote:

> - or to remove 1.39-1 from stable, which looks like the logical way
>   to go forward.

Plus providing a backport once stretch is release and 2.00-1 or later
migrated to buster.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: The Dubliners: Dirty old town


signature.asc
Description: Digital Signature

Bug#860915: cloud-initramfs-tools: Please re-enable generation of the overlayroot package

2017-04-21 Thread Scott Barker

Source: cloud-initramfs-tools
Version: 0.18.debian5
Severity: wishlist

Dear Maintainer,

Please re-enable generation of the overlayroot package. Debian stretch now
includes the overlay filesystem module. Thank you.

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

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

Bug#860908: perl 5.24 segfaults during a dpkg -i of cmanager (and other packages)

2017-04-21 Thread Niels Thykier

Brad Barnett:
> 
> 
>> [...]
> Setting up cgmanager (0.41-2) ...
> Segmentation fault
> Segmentation fault
> Segmentation fault
> Segmentation fault
> Segmentation fault
> Segmentation fault
> Segmentation fault
> Segmentation fault
> Segmentation fault
> Segmentation fault
> dpkg: error processing package cgmanager (--configure):
>  subprocess installed post-installation script returned error exit status 139
> Setting up sysv-rc (2.88dsf-59.9) ...


Hi,

Can you reproduce the segfault reliably by running:

 "deb-systemd-helper unmask cgmanager.service >/dev/null"

With Perl 5.24?

Thanks,
~Niels

Bug#860914: RM: libwww-dict-leo-org-perl/1.39-1

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

libwww-dict-leo-org-perl < 2.00 is broken since dict.leo.org changed
its interface. Cf. #857238

The package is already removed from testing (auto-removal); I just
uploaded a fixed new upstream release 2.00-1 to unstable which is
basically a rewrite to use the new interface.

So for stable this leaves us with a currently broken package, and the
options to
- - upload a new upstream release which probably doesn't make much
  sense for a leave package with hardly any users according to
  popcon;
- - or to remove 1.39-1 from stable, which looks like the logical way
  to go forward.


Cheers,
gregor


-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlj6X7JfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgY3tA//R4ouPaZv7JptCvVjCthB6/EEMqaOxqv8YGzU1oHQWmbtnuvv+bo95j70
KwyFITHMeFG9KkPj61oei3jRuyehHHPd7+3gQ0up49ElcthiFvsavHD/lucUQ8/n
b5z2zjI5rkxbuzZ28oPRY1yUUyB7OFMUXqSpn5dYoz8k3y16OWSOwGd3lzfU97Fe
mIMHCh/TLdm94QuLplmTu4Ay+QYUFAVyLOEylKphU9qUORNPqiCSOkDonASQjXxC
tFxmJ0IGd92cTCmHRwWURenHro61+RR9n5DQki/ne4+etan6vtZS6Z/tBz81W2qn
yn4ZmnVrxNrUc7bdPrD9TsTtsTbf4YT49A6r+m9K6kbC71PW6VwEy5LmYp0mWw3o
nHPNegMrCm5AyrMH1mLrDRADB4FUFWqBnskJ3kw2216PG2CzJ2t6bU1t9tnscs/W
vKoocDuD/jG1xdXN8KpmL8sfcZ2dFOG7WQY1Kci9tA61JBggMVaqz16aT+ZGnHoV
woNsovktZzPkfCpklYJ7AIgbs0ZYO4nKAJGuqWwvUuBkUFEfjtif0yILif/PvBNP
KQKy2Cw3jG7SHp8jJI51Yodt/MzveZe5OoRKhp277dSVJ/UY4jxCkHjZQrPSerXj
vRq2Lsb2nBxTj1cixCa7UW6sL5GsKT4hLq93fcRLSQ3la/1lRyc=
=3NLQ
-END PGP SIGNATURE-

Bug#860913: unblock: opensmtpd/6.0.2p1-2

2017-04-21 Thread Ryan Kavanagh

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

Please unblock package opensmtpd

We used to ship the spool directory tree (until 6.0.2p1-2) for
opensmtpd, with custom permissions for various subdirectories. The
required permissions changed, and as a result, opensmtpd fails to start
and prints out an error message.

The solution is to not ship the spool directory tree: opensmtpd will
create it with the correct permissions if it doesn't exist. Because the
purge directory had incorrect permissions, we also delete it when
upgrading from old versions and let opensmtpd recreate it on its first
run. (Otherwise, opensmtpd would print an error message and exit.) This
is safe to do, even if the directory is not empty, because everything in
the purge directory is slated for deletion anyways.

This fixes bug #843978. A fix has been uploaded to unstable; a debdiff
against testing is attached.

Please let me know if there is anything else you would like me to do.

Best wishes,
Ryan

unblock opensmtpd/6.0.2p1-2

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

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

-- 
|_)|_/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
| \| \  https://ryanak.ca/ |  BD95 8F7B F8FC 4A11 C97A
diff -Nru opensmtpd-6.0.2p1/debian/changelog opensmtpd-6.0.2p1/debian/changelog
--- opensmtpd-6.0.2p1/debian/changelog  2016-11-25 15:51:28.0 -0500
+++ opensmtpd-6.0.2p1/debian/changelog  2017-03-07 09:33:17.0 -0500
@@ -1,3 +1,12 @@
+opensmtpd (6.0.2p1-2) unstable; urgency=medium
+
+  * Let smtpd create its spool directory tree instead of shipping it.
+This fixes errors regarding directories with incorrect owners.
+Thanks to Harald Dunkel for a patch. (Closes: #843978)
+  * Actually remove the spool directory on purge.
+
+ -- Ryan Kavanagh   Tue, 07 Mar 2017 09:33:17 -0500
+
 opensmtpd (6.0.2p1-1) unstable; urgency=medium
 
   * Added Brazilian Portuguese debconf templates translation (Closes: #829336)
diff -Nru opensmtpd-6.0.2p1/debian/dirs opensmtpd-6.0.2p1/debian/dirs
--- opensmtpd-6.0.2p1/debian/dirs   2016-11-06 10:21:34.0 -0500
+++ opensmtpd-6.0.2p1/debian/dirs   2017-03-07 09:33:17.0 -0500
@@ -1,4 +1 @@
 var/lib/opensmtpd/empty
-var/spool/smtpd
-var/spool/smtpd/offline
-var/spool/smtpd/purge
diff -Nru opensmtpd-6.0.2p1/debian/opensmtpd.lintian-overrides 
opensmtpd-6.0.2p1/debian/opensmtpd.lintian-overrides
--- opensmtpd-6.0.2p1/debian/opensmtpd.lintian-overrides2016-11-23 
13:42:28.0 -0500
+++ opensmtpd-6.0.2p1/debian/opensmtpd.lintian-overrides2017-03-07 
09:31:05.0 -0500
@@ -3,9 +3,6 @@
 opensmtpd: hyphen-used-as-minus-sign usr/share/man/man5/smtpd.conf.5.gz:570
 opensmtpd: hyphen-used-as-minus-sign usr/share/man/man8/smtpctl.8.gz:326
 opensmtpd: hyphen-used-as-minus-sign usr/share/man/man8/smtpd.8.gz:96
-opensmtpd: non-standard-dir-perm var/spool/smtpd/ 0711 != 0755
-opensmtpd: non-standard-dir-perm var/spool/smtpd/offline/ 1770 != 0755
-opensmtpd: non-standard-dir-perm var/spool/smtpd/purge/ 1700 != 0755
 # The mistake is in the license text
 opensmtpd: spelling-error-in-copyright GNU Public Licence GNU General Public 
License
 opensmtpd: spelling-error-in-copyright aheared adhered
diff -Nru opensmtpd-6.0.2p1/debian/postinst opensmtpd-6.0.2p1/debian/postinst
--- opensmtpd-6.0.2p1/debian/postinst   2016-11-06 10:21:34.0 -0500
+++ opensmtpd-6.0.2p1/debian/postinst   2017-03-07 09:33:17.0 -0500
@@ -175,9 +175,14 @@
 --no-create-home --disabled-password \
 --gecos "OpenSMTD queue user" \
 --ingroup opensmtpq opensmtpq
-chown root:opensmtpq /var/spool/smtpd/offline
-chmod 770 /var/spool/smtpd/offline
-chmod 700 /var/spool/smtpd/purge
+if dpkg --compare-versions "$2" lt 6.0.2p1-2; then
+# In versions < 6.0.2p1-2, the purge directory was created with
+# permissions that won't work with versions >= 6.0.2p1. We can
+# safely delete it: smtpd will recreate it for us when it starts if
+# it's missing, and the purge directory only contains data that is
+# slated for deletion.
+rm -fr /var/spool/smtpd/purge || true
+fi
 ;;
 
 abort-upgrade|abort-remove|abort-deconfigure|reconfigure)
diff -Nru opensmtpd-6.0.2p1/debian/postrm opensmtpd-6.0.2p1/debian/postrm
--- opensmtpd-6.0.2p1/debian/postrm 2016-11-06 10:21:34.0 -0500
+++ opensmtpd-6.0.2p1/debian/postrm 2017-03-07

Bug#860908: perl 5.24 segfaults during a dpkg -i of cmanager (and other packages)

2017-04-21 Thread Brad Barnett



> Could you perhaps include the following information:
> 
>  * Which architecture are you using?  If you have multi-arch enabled,
>please list the architecture of the perl packages (e.g. in the form
>of "dpkg -l" if you don't mind including a list of all packages
>installed)

amd64, nothing else.

> 
>  * Does perl segfault in general or does it "only" happen when you run
>dpkg/apt?

So far, only when running apt/dpkg.  And, only at specific times (more to
follow, as per Gregor's request)

>- e.g. try running "dpkg-architecture" (if you have dpkg-dev
>  installed)
> 
>  * If you can reproduce the segfault directly, can you provide a
>backtrace with symbols? NB: you will probably need to download some
> of the debug symbols from the new debug archive (see [1])

I can't directly, and strace wasn't very helpful in tracing perl via
dpkg -- even with -f.

EG:

strace -s10024 -f -i -y  -o /tmp/bah dpkg -D1 -i cgmanager_0.41-2_amd64.deb

4848  read(4, "package strict;\n\n$strict::VERSION = \"1.11\";\n\nmy ( 
%bitmask, %explicit_bitmask );\n\nBEGIN {\n
  # Verify that we're called correctly so that strictures will work.\n# 
Can't use Carp, since Carp uses us!\n
 # see also warnings.pm.\ndie sprintf \"Incorrect use of pragma '%s' at %s 
line %d.\\n\", __PACKAGE__, +(caller)[1,2]\nif __FILE__ !~ ( '(?x) \\b  
   '.__PACKAGE__.'  \\.pmc? \\z' )\n&& __FILE__ =~ ( '(?x) \\b (?
i:'.__PACKAGE__.') \\.pmc? \\z' );\n\n%bitmask = (\nrefs => 
0x0002,\nsubs => 0x0200,\n
  vars => 0x0400,\n);\n\n%explicit_bitmask = (\nrefs => 
0x0020,\nsubs => 0x0
040,\nvars => 0x0080,\n);\n\nmy $bits = 0;\n$bits |= $_ 
for values %bitmask;\n\nmy $inline_all_bits = $bits;\n*all_bits = sub 
() { $inline_all_bits };\n\n$bits = 0;\n$bits |= $_ for values %ex
plicit_bitmask;\n\nmy $inline_all_explicit_bits = $bits;\n
*all_explicit_bits = sub () { $inline_all_explicit_bits };\n}\n\nsub bits {\n   
 my $bits = 0;\nmy @wrong;\nforeach my $s (@_) {\nif (exists 
$bitmask{
$s}) {\n$^H |= $explicit_bitmask{$s};\n\n$bits |= 
$bitmask{$s};\n}\nelse {\npush @wrong, $s;\n
}\n}\nif (@wrong) {\nrequire Carp;\nCarp::croak(\"Unkn
own 'strict' tag(s) '@wrong'\");\n}\n$bits;\n}\n\nsub import {\n
shift;\n$^H |= @_ ?  : all_bits | all_explicit_bits;\n}\n\nsub 
unimport {\nshift;\n\nif (@_) {\n$^H &= ~\n}\n
else {\n
$^H &= ~all_bits;\n$^H |= all_explicit_bits;\n
}\n}\n\n1;\n__END__\n\n", 8192) = 1606
4848  --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR, 
si_addr=0x564e95e7d010} ---
4848  +++ killed by SIGSEGV +++
4847  <... wait4 resumed> [{WIFSIGNALED(s) && WTERMSIG(s) == SIGS


-

As per Gregor's request, here's what happened:

- installed a fresh copy of stretch on an older generation (fully amd64 
capable) AMD box

- install went fine.  Installed it today, using V3 of the installer

- tasksel was ONLY 'ssh' and below it 'standard system utilities'

- post boot, modified /etc/network/interfaces, then:

- apt-get installed vim lsof

- installed moreutils

- installed inetutils-tools

- purged inetutils-tools

- installed net-tools

- created /etc/apt/preferences.d/systemd, with contents:

Package: systemd
Pin: release *
Pin-Priority: -1


Package: *systemd*
Pin: release *
Pin-Priority: -1

Package: systemd:i386
Pin: release *
Pin-Priority: -1

Package: systemd:amd64
Pin: release *
Pin-Priority: -1

- apt-get install sysvinit-core

This also did:

Install: startpar:amd64 (0.59-3.1, automatic), insserv:amd64
(1.14.0-5.4+b1, automatic), psmisc:amd64 (22.21-2.1+b2, automatic),
sysvinit-core:amd64 (2.88dsf-59.9), initscripts:amd64 (2.88dsf-59.9,
automatic), sysv-rc:amd64 (2.88dsf-59.9, automatic)

Remove: systemd-sysv:amd64 (232-22), libpam-systemd:amd64 (232-22)

During install:


# apt-get install sysvinit-utils sysvinit-core
Reading package lists... Done
Building dependency tree
Reading state information... Done
sysvinit-utils is already the newest version (2.88dsf-59.9).
The following additional packages will be installed:
  cgmanager initscripts insserv libcgmanager0 libglib2.0-0 libglib2.0-data 
libnih-dbus1 libnih1 psmisc
  shared-mime-info startpar systemd-shim sysv-rc xdg-user-dirs
Suggested packages:
  bootchart2 pm-utils bum bootlogd
The following packages will be REMOVED:
  systemd-sysv
The following NEW packages will be installed:
  cgmanager initscripts insserv libcgmanager0 libglib2.0-0 libglib2.0-data 
libnih-dbus1 libnih1 psmisc
  shared-mime-info startpar systemd-shim sysv-rc sysvinit-core xdg-user-dirs
0 upgraded, 15 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 6,358 kB/6,851 kB of archives.
After this operation, 22.2 MB of additional disk space will be

Bug#860885: systemd fails to mount five of six system files indicated in /etc/fstab

2017-04-21 Thread Michael Biebl

Control: tags -1 + moreinfo

Am 21.04.2017 um 15:04 schrieb phil-deb1.merlin:
> Package: systemd
> Version: 232-22
> Severity: important
> 

Can you share more details, like:
Is this problem reproducible on every boot?
Does it only happen for certain file systems/drives, i.e. are only file
systems affected which are *not* on /dev/sda?

How are your drives connected?


-- 
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#753763: the graphics program crashes with a segfault

2017-04-21 Thread Steffen Möller

Hi Yixuan,

On Fri, 04 Jul 2014 15:18:56 -0400
=?utf-8?b?R3VvIFlpeHVhbiAo6YOt5rqi6K2eKQ==?=  wrote:
> Package: boinc-app-seti-graphics
> Version: 7.28~svn2408-1
> Severity: important
> Tags: upstream

> Currently, clicking on "show graphics" in boinc manager doesn't work for
> seti.
>
> dmesg output:
> setiathome_grap[8764]: segfault at 28 ip 7f19c18d785b sp
> 7fff4a080980 error 6 in setiathome_graphics[7f19c18d2000+a000]

about three years down the road I tend to think that your crash has
auto-repaired itself.
But it still does not run when started as a regular user with the
boinc-manager. It works fine,
however, when invoked as root and in the working directory of the
running task

cd /var/lib/boinc-client/slots/0
/usr/lib/boinc-app-seti-graphics/setiathome_graphics

It all also works just fine when the boincmgr is started as root, which
reduces it to a
permission thingy. And indeed, my account was just assigned to the boinc
group.
That changed fixed the graphics display.

Best,

Steffen

Bug#851885: Please add pseudopackage `manpages.debian.org'

2017-04-21 Thread Antoine Beaupre

On Thu, Mar 23, 2017 at 09:43:00AM -0500, Don Armstrong wrote:
> On Thu, 23 Mar 2017, Michael Stapelberg wrote:
> > Sorry for the late reply.
> > 
> > The description looks good to me.
> 
> Cool.
> 
> > I don’t have a set of bugs to re-assign. I’m not sure whether the BTS was
> > ever used for tracking issues with manpages.debian.org before, and any
> > issues reported likely don’t apply anymore.
> 
> Just a TODO list (or something else) which lists the bugs which you are
> planning to create/reassign is sufficient for my purposes. [This is just
> to make sure that the pseudo package is actually going to be used before
> I create it; it's totally OK if those issues have already been fixed too.]

I'm a little confused here - do we absolutely need to pre-emptively
create a bug against the non-existent manpages.debian.org pseudo-package
for it to be created?

If not, what's blocking creation?

If so, well, I can just create a dummy bug report - the idea is to have
a place people can report issues with the service in general. So far,
there's no issue, but it would be nice to allow people to file issues
without being forced to go through Github or conflating debiman, the
software, with manpages.d.o, the service.

I've documented a little the distinction between the various trackers
here:

https://anonscm.debian.org/git/srv-manpages/debian-assets.git/tree/faq.tmpl?h=faq

Let us know what needs to be done to create the pseudo-package.

Thanks!

A.

signature.asc
Description: PGP signature

Bug#851885: Please add pseudopackage `manpages.debian.org'

2017-04-21 Thread Antoine Beaupre

On Thu, Mar 23, 2017 at 02:55:51PM +, Ian Jackson wrote:
> Michael Stapelberg writes ("Re: Bug#851885: Please add pseudopackage 
> `manpages.debian.org'"):
> > Oh, I m not planning to create any bugs. I m working with GitHub. iwj@ 
> > wanted
> > this pseudo-package to be created, and I agreed to accept bug reports via 
> > the
> > pseudo package, while continuing to use GitHub as the canonical issue 
> > tracker.
> 
> As an example, my personal todo list has an entry to make the code
> behind manpages.debian.org automatically serve up its own source in
> its output.  The result of that would be a patch or pull request which
> I would like to submit as a bug to the Debian BTS.

That sounds like something that should be reported against the upstream
repository on Github, but I guess it's fine if it's reported against
manpages.debian.org if you absolutely don't want to use Github. :)

Should that issue be created now then? I seem to understand that Don
wanted us to create an issue *before* he creates the pseudo-package. I'm
not too familiar with how the internals of the BTS works, so maybe I
misunderstood...

A.

signature.asc
Description: PGP signature

Bug#860912: rkflashtool: Vcs-Git and Vcs-Browser do not contain debian packaging

2017-04-21 Thread Vagrant Cascadian

Package: rkflashtool
Version: 0~20160221-1
Severity: normal

It appears the Vcs-Git and Vcs-Browser entries in debian/control only
reference the upstream source, and do not include the Debian
packaging.

This is mentioned in debian-policy 5.6.26:

 `Vcs-Arch', `Vcs-Bzr' (Bazaar), `Vcs-Cvs', `Vcs-Darcs', `Vcs-Git',
 `Vcs-Hg' (Mercurial), `Vcs-Mtn' (Monotone), `Vcs-Svn' (Subversion)
  The field name identifies the VCS.  The field's value uses the
  version control system's conventional syntax for describing
  repository locations and should be sufficient to locate the
  repository used for packaging.  Ideally, it also locates the
  branch used for development of new versions of the Debian
  package.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#860911: freeipmi-tools: /usr/share/man/man5/bmc-config.conf.5.gz contains a link to an invalid location

2017-04-21 Thread Ryan

Package: freeipmi-tools
Version: 1.4.11-1.1+b1
Severity: minor

Dear Maintainer,

Part 1: Invalid manpage link
Checking manpages with mandb -t reported:
 mandb: can't open /usr/share/man/man8/ipmi-config.conf.5: No such file or 
directory
 mandb: warning: /usr/share/man/man5/bmc-config.conf.5.gz: bad symlink or ROFF 
`.so' request

Checking the man file content shows an invalid link:
~ zcat /usr/share/man/man5/bmc-config.conf.5.gz
.so man8/ipmi-config.conf.5

Fix option a: Text change 'man8' to 'man5'
 .so man5/ipmi-config.conf.5

(If doing this, I'd also suggest _not_ making it gz, it is smaller
uncompressed)

Fix option b: replace the file with a symlink:
bmc-config.conf.5.gz -> ipmi-config.conf.5.gz


backing ref: dpkg-query -S /usr/share/man/man5/ipmi-config.conf.5.gz
freeipmi-tools: /usr/share/man/man5/ipmi-config.conf.5.gz

Thanks,
Ryan

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

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

Versions of packages freeipmi-tools depends on:
ii  freeipmi-common  1.4.11-1.1+b1
ii  libc62.24-9
ii  libfreeipmi161.4.11-1.1+b1
ii  libgcrypt20  1.7.6-1
ii  libipmiconsole2  1.4.11-1.1+b1
ii  libipmidetect0   1.4.11-1.1+b1

freeipmi-tools recommends no packages.

Versions of packages freeipmi-tools suggests:
ii  freeipmi-bmc-watchdog  1.4.11-1.1+b1
ii  freeipmi-ipmidetect1.4.11-1.1+b1

-- no debconf information

Bug#860875: open-vm-tools-desktop: run-vmblock\x2dfuse.mount fails to start during boot

2017-04-21 Thread Oliver Kurth

Yeah, the enabled state remains even after removing (with --purge) the packages 
again:


vmware@debian:~$ ls -l 
/etc/systemd/system/multi-user.target.wants/run-vmblock\\x2dfuse.mount
lrwxrwxrwx 1 root root 45 Apr 20 17:31 
/etc/systemd/system/multi-user.target.wants/run-vmblock\x2dfuse.mount -> 
/lib/systemd/system/run-vmblock\x2dfuse.mount
vmware@debian:~$ ls

When I remove the symlink and install the packages again, it won't be set:

vmware@debian:~$ sudo dpkg -i *.deb
Selecting previously unselected package open-vm-tools.
(Reading database ... 163883 files and directories currently installed.)
Preparing to unpack open-vm-tools_10.1.5-5055683-4_amd64.deb ...
Unpacking open-vm-tools (2:10.1.5-5055683-4) ...
Selecting previously unselected package open-vm-tools-desktop.
Preparing to unpack open-vm-tools-desktop_10.1.5-5055683-4_amd64.deb ...
Unpacking open-vm-tools-desktop (2:10.1.5-5055683-4) ...
Setting up open-vm-tools (2:10.1.5-5055683-4) ...
Created symlink 
/etc/systemd/system/multi-user.target.wants/open-vm-tools.service → 
/lib/systemd/system/open-vm-tools.service.
Created symlink 
/etc/systemd/system/open-vm-tools.service.requires/vgauth.service → 
/lib/systemd/system/vgauth.service.
Setting up open-vm-tools-desktop (2:10.1.5-5055683-4) ...
Processing triggers for libc-bin (2.24-10) ...
Processing triggers for systemd (232-22) ...
Processing triggers for man-db (2.7.6.1-2) ...
vmware@debian:~$ sudo systemctl status run-vmblock\\x2dfuse.mount
● run-vmblock\x2dfuse.mount - VMware vmblock fuse mount
   Loaded: loaded (/lib/systemd/system/run-vmblock\x2dfuse.mount; disabled; 
vendor preset: enabled)
   Active: inactive (dead)
Where: /run/vmblock-fuse
 What: vmware-vmblock-fuse
 Docs: 
https://github.com/vmware/open-vm-tools/blob/master/open-vm-tools/vmblock-fuse/design.txt

Apr 20 17:27:04 debian systemd[1]: Mounting VMware vmblock fuse mount...
Apr 20 17:27:04 debian systemd[1]: Mounted VMware vmblock fuse mount.
Apr 21 10:37:23 debian systemd[1]: Unmounting VMware vmblock fuse mount...
Apr 21 10:37:23 debian systemd[1]: Unmounted VMware vmblock fuse mount.
vmware@debian:~$

So nothing has changed :-(.

Oliver


From: Oliver Kurth
Sent: Friday, April 21, 2017 10:46:36 AM
To: Bernd Zeimetz; Norbert Lange; 860...@bugs.debian.org
Subject: Re: Bug#860875: open-vm-tools-desktop: run-vmblock\x2dfuse.mount fails 
to start during boot


Hm,


looks like the mount unit is enabled now, but not started after installing. 
Actually, I am not sure if the enabled state is still there from my previous 
test, because I do not see it being enabled in the output below, whereas I do 
see it for vmtoolsd and vgauth:


vmware@debian:~$ ls *.deb
open-vm-tools_10.1.5-5055683-4_amd64.deb  
open-vm-tools-desktop_10.1.5-5055683-4_amd64.deb
vmware@debian:~$ sudo dpkg -i *.deb
Selecting previously unselected package open-vm-tools.
(Reading database ... 163886 files and directories currently installed.)
Preparing to unpack open-vm-tools_10.1.5-5055683-4_amd64.deb ...
Unpacking open-vm-tools (2:10.1.5-5055683-4) ...
Selecting previously unselected package open-vm-tools-desktop.
Preparing to unpack open-vm-tools-desktop_10.1.5-5055683-4_amd64.deb ...
Unpacking open-vm-tools-desktop (2:10.1.5-5055683-4) ...
Setting up open-vm-tools (2:10.1.5-5055683-4) ...
Created symlink 
/etc/systemd/system/multi-user.target.wants/open-vm-tools.service → 
/lib/systemd/system/open-vm-tools.service.
Created symlink 
/etc/systemd/system/open-vm-tools.service.requires/vgauth.service → 
/lib/systemd/system/vgauth.service.
Setting up open-vm-tools-desktop (2:10.1.5-5055683-4) ...
Processing triggers for libc-bin (2.24-10) ...
Processing triggers for systemd (232-22) ...
Processing triggers for man-db (2.7.6.1-2) ...
vmware@debian:~$ sudo systemctl status run-vmblock\x2dfuse.mount
Unit run-vmblockx2dfuse.mount could not be found.
vmware@debian:~$ sudo systemctl status run-vmblock\\x2dfuse.mount
● run-vmblock\x2dfuse.mount - VMware vmblock fuse mount
   Loaded: loaded (/lib/systemd/system/run-vmblock\x2dfuse.mount; enabled; 
vendor preset: enabled)
   Active: inactive (dead) since Fri 2017-04-21 10:37:23 PDT; 3min 54s ago
Where: /run/vmblock-fuse
 What: vmware-vmblock-fuse
 Docs: 
https://github.com/vmware/open-vm-tools/blob/master/open-vm-tools/vmblock-fuse/design.txt
   CGroup: /system.slice/run-vmblock\x2dfuse.mount

Apr 20 17:27:04 debian systemd[1]: Mounting VMware vmblock fuse mount...
Apr 20 17:27:04 debian systemd[1]: Mounted VMware vmblock fuse mount.
Apr 21 10:37:23 debian systemd[1]: Unmounting VMware vmblock fuse mount...
Apr 21 10:37:23 debian systemd[1]: Unmounted VMware vmblock fuse mount.


Oliver



From: Bernd Zeimetz 
Sent: Friday, April 21, 2017 4:43:48 AM
To: Norbert Lange; 860...@bugs.debian.org; Oliver Kurth
Subject: Re: Bug#860875: open-vm-tools-desktop: run-vmblock\x2dfuse.mount fails 
to start during boot

Hi Oliver,
hi

Bug#860839: Uploading logs

2017-04-21 Thread Lisandro Damián Nicanor Pérez Meyer

On viernes, 21 de abril de 2017 15:25:02 -03 Lisandro Damián Nicanor Pérez 
Meyer wrote:
> On viernes, 21 de abril de 2017 13:22:41 -03 Harlan Lieberman-Berg wrote:
> [snip qmake info]
> 
> The qmake stuff was just right, but...
> 
> > [hlieberm@crete ~]$ QT_DEBUG_PLUGINS=1 vlc
> > VLC media player 2.2.5 Weatherwax (revision 2.2.5-0-g9275f0fefa)
> > [56310dca2148] core libvlc: Running vlc with the default interface.
> > Use
> > 'cvlc' to use vlc without interface. QFactoryLoader::QFactoryLoader()
> > checking directory path "/usr/bin/platforms"
> 
> ... this is weird, and normally means ther eis Qt stuff not coming from
> Debian packages.
> 
> Have you installed anything Qt-based not using Debian's packages?

To be more verbose, that should be:

/usr/lib/x86_64-linux-gnu/qt5/plugins and not /usr/bin/platforms


-- 
perezmeyer: Gus no tiene inet :-(
PabloOdorico: oh
perezmeyer: te mando una copia de lo que hagamos esta noche
PabloOdorico: de ultima mandame un loro del parque con una flash en la pata ;)

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#860839: Uploading logs

2017-04-21 Thread Lisandro Damián Nicanor Pérez Meyer

On viernes, 21 de abril de 2017 13:22:41 -03 Harlan Lieberman-Berg wrote:
[snip qmake info]

The qmake stuff was just right, but...

> [hlieberm@crete ~]$ QT_DEBUG_PLUGINS=1 vlc
> VLC media player 2.2.5 Weatherwax (revision 2.2.5-0-g9275f0fefa)
> [56310dca2148] core libvlc: Running vlc with the default interface. Use
> 'cvlc' to use vlc without interface. QFactoryLoader::QFactoryLoader()
> checking directory path "/usr/bin/platforms"

... this is weird, and normally means ther eis Qt stuff not coming from Debian 
packages.

Have you installed anything Qt-based not using Debian's packages?


-- 
porque no respeta el orden natural en el que se leen las cosas
>¿por qué top-posting es tan molesto?
>>top-posting
>>>¿cuál es la peor molestia en los emails de respuesta?

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#860910: screen: support baudrate of 1500000

2017-04-21 Thread Vagrant Cascadian

Package: screen
Version: 4.5.0-5
Severity: wishlist

When I run:

  screen /dev/ttyUSB2 150

All I get is gibberish on the screen.


I'm able to access the same device with cu:

  cu --line=/dev/ttyUSB2 --baud=150

And I get expected serial output, so I know the tty device works at
that speed.


Highest speed listed in the source tty.sh (which produces tty.c) is
460800, but it's unclear to me if it also dynamically determines
appropriate values for baud rates somehow...


live well,
  vagrant


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (120, 'unstable'), (1, 'experimental')
Architecture: amd64
 (x86_64)
Foreign Architectures: armhf

Kernel: Linux 4.9.0-2-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 screen depends on:
ii  libc6  2.24-9
ii  libpam0g   1.1.8-3.5
ii  libtinfo5  6.0+20161126-1

screen recommends no packages.

Versions of packages screen suggests:
pn  byobu | screenie | iselect  
ii  ncurses-term6.0+20161126-1

-- no debconf information


signature.asc
Description: PGP signature

Bug#859926: speechd-up: fails to install

2017-04-21 Thread Paul Gevers

Hi

On 21-04-17 16:21, Cobra wrote:
> The man page states:
> "speech-dispatcher is usually started automatically by client libraries
> (i.e. autospawn), so you only need to run it manually if 
> testing/debugging, or when in other explicit need for a special setup."
> 
> So this behaviour doesn't seem broken to me, that's rather exactly as
> expected. Also, starting speechd-up with start-stop-daemon doesn't show
> any failures, despite missing special handling of speech-dispatcher.
> There is an open bug about autospawn with multiple users in #616313,
> but I don't see an immediate connection to our issues; we're always
> root and not touching speechd-up directly.

Hmm, should the speech-dispatcher package than rather NOT ship an init
file? Does it make sense in some setups? An when speech-dispatcher has
no init file, maybe than speechd-up shouldn't "Required-Start"
speech-dispatcher in its init file. Not that it matters, it still
doesn't work when I do that.

> I enabled this line in /etc/speech-dispatcher/speechd.conf:
> CustomLogFile "protocol" 
> "/var/log/speech-dispatcher/speech-dispatcher-protocol.log"
> 
> /var/log/speech-dispatcher/speech-dispatcher-protocol.log stays empty
> when using service (my VM is still using sysvinit-core now), but when I
> use the usual start-stop-daemon command, I get this log:

May it be that starting daemons via service may not have $HOME set? It
occurs to me that when I start speechd-up manually I see this with "ps
aux" (notice the socket location):
root 22182  0.0  0.0 174708  2224 ?Ssl  19:47   0:00
/usr/bin/speech-dispatcher --spawn --communication-method unix_socket
--socket-path /root/.cache/speech-dispatcher/speechd.sock

By the way, with "service" it seems that configuration of
speech-dispatcher is ignored. I find the logging in
/root/.cache/speech-dispatcher... where it now also records what goes
wrong..
[Fri Apr 21 20:04:39 2017 : 549750] speechd: Error [speechd.c:665]:No
speech output modules were loaded - aborting...

I'll try to figure out further.

Paul

signature.asc
Description: OpenPGP digital signature

Bug#860875: open-vm-tools-desktop: run-vmblock\x2dfuse.mount fails to start during boot

2017-04-21 Thread Oliver Kurth

Hm,


looks like the mount unit is enabled now, but not started after installing. 
Actually, I am not sure if the enabled state is still there from my previous 
test, because I do not see it being enabled in the output below, whereas I do 
see it for vmtoolsd and vgauth:


vmware@debian:~$ ls *.deb
open-vm-tools_10.1.5-5055683-4_amd64.deb  
open-vm-tools-desktop_10.1.5-5055683-4_amd64.deb
vmware@debian:~$ sudo dpkg -i *.deb
Selecting previously unselected package open-vm-tools.
(Reading database ... 163886 files and directories currently installed.)
Preparing to unpack open-vm-tools_10.1.5-5055683-4_amd64.deb ...
Unpacking open-vm-tools (2:10.1.5-5055683-4) ...
Selecting previously unselected package open-vm-tools-desktop.
Preparing to unpack open-vm-tools-desktop_10.1.5-5055683-4_amd64.deb ...
Unpacking open-vm-tools-desktop (2:10.1.5-5055683-4) ...
Setting up open-vm-tools (2:10.1.5-5055683-4) ...
Created symlink 
/etc/systemd/system/multi-user.target.wants/open-vm-tools.service → 
/lib/systemd/system/open-vm-tools.service.
Created symlink 
/etc/systemd/system/open-vm-tools.service.requires/vgauth.service → 
/lib/systemd/system/vgauth.service.
Setting up open-vm-tools-desktop (2:10.1.5-5055683-4) ...
Processing triggers for libc-bin (2.24-10) ...
Processing triggers for systemd (232-22) ...
Processing triggers for man-db (2.7.6.1-2) ...
vmware@debian:~$ sudo systemctl status run-vmblock\x2dfuse.mount
Unit run-vmblockx2dfuse.mount could not be found.
vmware@debian:~$ sudo systemctl status run-vmblock\\x2dfuse.mount
● run-vmblock\x2dfuse.mount - VMware vmblock fuse mount
   Loaded: loaded (/lib/systemd/system/run-vmblock\x2dfuse.mount; enabled; 
vendor preset: enabled)
   Active: inactive (dead) since Fri 2017-04-21 10:37:23 PDT; 3min 54s ago
Where: /run/vmblock-fuse
 What: vmware-vmblock-fuse
 Docs: 
https://github.com/vmware/open-vm-tools/blob/master/open-vm-tools/vmblock-fuse/design.txt
   CGroup: /system.slice/run-vmblock\x2dfuse.mount

Apr 20 17:27:04 debian systemd[1]: Mounting VMware vmblock fuse mount...
Apr 20 17:27:04 debian systemd[1]: Mounted VMware vmblock fuse mount.
Apr 21 10:37:23 debian systemd[1]: Unmounting VMware vmblock fuse mount...
Apr 21 10:37:23 debian systemd[1]: Unmounted VMware vmblock fuse mount.


Oliver



From: Bernd Zeimetz 
Sent: Friday, April 21, 2017 4:43:48 AM
To: Norbert Lange; 860...@bugs.debian.org; Oliver Kurth
Subject: Re: Bug#860875: open-vm-tools-desktop: run-vmblock\x2dfuse.mount fails 
to start during boot

Hi Oliver,
hi Norbert,


please test the packages from
https://urldefense.proofpoint.com/v2/url?u=http-3A__shell.bzed.at_-7Ebzed_.publish_2017-2D04-2D21-2D4a17FnEPKxw_=DwIC-g=uilaK90D4TOVoH58JNXRgQ=oHeYwLSPkRE9YQPISb_awkWjWigW3oPkIDc-ePsrBjY=jepfmU6mpuzYaX4nuc56cIxYjH6GcyL3zgmmnhpMdGc=z_3eLUmkTB917kSuUj6a2R7ChkLIM_EI2Yxkp2NIRsA=

they work for me. If nobody complains I'll upload them during the weekend.

Best regards,

Bernd

--
 Bernd ZeimetzDebian GNU/Linux Developer
 
https://urldefense.proofpoint.com/v2/url?u=http-3A__bzed.de=DwIC-g=uilaK90D4TOVoH58JNXRgQ=oHeYwLSPkRE9YQPISb_awkWjWigW3oPkIDc-ePsrBjY=jepfmU6mpuzYaX4nuc56cIxYjH6GcyL3zgmmnhpMdGc=9EfkLOkVa0CNrv7e-SguuYJ_rifsMzTrWYbS0A1hFHY=
 
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.debian.org=DwIC-g=uilaK90D4TOVoH58JNXRgQ=oHeYwLSPkRE9YQPISb_awkWjWigW3oPkIDc-ePsrBjY=jepfmU6mpuzYaX4nuc56cIxYjH6GcyL3zgmmnhpMdGc=NIAaEojMgknC-Y7Nihsi2O2i58qloyxJflONjqU8lgs=
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Bug#860906: thunderbird: Missing debug symbols

2017-04-21 Thread Carsten Schoenert

Control:  merge -1 858919 

Hello Pierre,

On Fri, Apr 21, 2017 at 05:22:18PM +0200, Pierre Rudloff wrote:
> Package: thunderbird
> Version: 1:45.8.0-3~deb8u1
> Severity: minor
> 
> Hello,
> 
> I recently uploaded a Thunderbird crash report and it seems debug symbols are
> missing: https://crash-stats.mozilla.com/report/index/df0ca000-ec38-4507-a0ef-
> 06f9f0170421
> I think you can upload the debug symbols from the Debian build to crash-
> stats.mozilla.com so they are available in crash reports.

this is a know problem, please see 858919.

We need to collect the various used symbols, this isn't happen yet.

Regards
Carsten

Bug#860908: perl 5.24 segfaults during a dpkg -i of cmanager (and other packages)

On Fri, 21 Apr 2017 13:10:44 -0400, Brad Barnett wrote:

> When installing packages right after a fresh stretch install, perl started to
> segfault.
> 
> EG:
> 
> Setting up cgmanager (0.41-2) ...
> Segmentation fault
> Segmentation fault
> Segmentation fault
> Segmentation fault
> Segmentation fault
> Segmentation fault
> Segmentation fault
> Segmentation fault
> Segmentation fault
> Segmentation fault

I can install cgmanager in a stretch amd64 chroot without any
problems:

# apt install cgmanager
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  libcgmanager0 libdbus-1-3 libnih-dbus1 libnih1
Recommended packages:
  dbus
The following NEW packages will be installed:
  cgmanager libcgmanager0 libdbus-1-3 libnih-dbus1 libnih1
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 539 kB of archives.
After this operation, 1338 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://ftp.ch.debian.org/debian stretch/main amd64 libdbus-1-3 amd64 
1.10.18-1 [192 kB]
Get:2 http://ftp.ch.debian.org/debian stretch/main amd64 libnih1 amd64 1.0.3-8 
[125 kB]
Get:3 http://ftp.ch.debian.org/debian stretch/main amd64 libnih-dbus1 amd64 
1.0.3-8 [96.8 kB]
Get:4 http://ftp.ch.debian.org/debian stretch/main amd64 libcgmanager0 amd64 
0.41-2 [41.1 kB]
Get:5 http://ftp.ch.debian.org/debian stretch/main amd64 cgmanager amd64 0.41-2 
[84.0 kB]
Fetched 539 kB in 0s (759 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package libdbus-1-3:amd64.
(Reading database ... 9928 files and directories currently installed.)
Preparing to unpack .../libdbus-1-3_1.10.18-1_amd64.deb ...
Unpacking libdbus-1-3:amd64 (1.10.18-1) ...
Selecting previously unselected package libnih1.
Preparing to unpack .../libnih1_1.0.3-8_amd64.deb ...
Unpacking libnih1 (1.0.3-8) ...
Selecting previously unselected package libnih-dbus1.
Preparing to unpack .../libnih-dbus1_1.0.3-8_amd64.deb ...
Unpacking libnih-dbus1 (1.0.3-8) ...
Selecting previously unselected package libcgmanager0:amd64.
Preparing to unpack .../libcgmanager0_0.41-2_amd64.deb ...
Unpacking libcgmanager0:amd64 (0.41-2) ...
Selecting previously unselected package cgmanager.
Preparing to unpack .../cgmanager_0.41-2_amd64.deb ...
Unpacking cgmanager (0.41-2) ...
Processing triggers for libc-bin (2.24-9) ...
Setting up libnih1 (1.0.3-8) ...
Setting up libdbus-1-3:amd64 (1.10.18-1) ...
Setting up libnih-dbus1 (1.0.3-8) ...
Setting up libcgmanager0:amd64 (0.41-2) ...
Setting up cgmanager (0.41-2) ...
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
Processing triggers for libc-bin (2.24-9) ...

Admittedly, policy-rc.d within the chroot prohibts running the init
scripts from the postinst ...

You mention "other packages" in your bug report; do you happen to
remember which ones?
Do the problems persist if you upgrade to stretch's perl again?

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Bob Dylan: Cry A While

signature.asc
Description: Digital Signature

Bug#860908: perl 5.24 segfaults during a dpkg -i of cmanager (and other packages)

2017-04-21 Thread Niels Thykier

Control: tags -1 moreinfo

On Fri, 21 Apr 2017 13:10:44 -0400 Brad Barnett  wrote:
> Package: perl
> Version: 5.24.1-2
> 
> 
> When installing packages right after a fresh stretch install, perl started to
> segfault.
> 
> EG:
> 
> Setting up cgmanager (0.41-2) ...
> [...]
> 
> 
> I used dpkg + wget, downgraded via --force-all both perl and perl-base to 
> jessie's version.
> 
> The problem went away, and I was able to install cmanager without a segfault.
> 
> System can be down a few days, so I've left it in this state.  I can test / 
> debug / etc.
> 
> Thanks
> 
> 

Hi Brad,

Thanks for filing this bug.

Could you perhaps include the following information:

 * Which architecture are you using?  If you have multi-arch enabled,
   please list the architecture of the perl packages (e.g. in the form
   of "dpkg -l" if you don't mind including a list of all packages
   installed)

 * Does perl segfault in general or does it "only" happen when you run
   dpkg/apt?
   - e.g. try running "dpkg-architecture" (if you have dpkg-dev
 installed)

 * If you can reproduce the segfault directly, can you provide a
   backtrace with symbols? NB: you will probably need to download some
of the debug symbols from the new debug archive (see [1])

Thanks,
~Niels

PS: Please keep me CC'ed in replies.

[1]
https://www.debian.org/releases/stretch/amd64/release-notes/ch-whats-new.en.html#debug-archive

Bug#637348: Mozilla's sponsors driving to privacy problems; please package IceCat for Debian

2017-04-21 Thread Narcis Garcia

I believe that it's very interesting to be supported in the future by
Debian instead of having to install it from third party repository
(Trisquel) or having to use raw Firefox/Chromium at open networks.

IceCat is simply a cleaner Firefox: Unlike TorBrowser and like Firefox,
Icecat works through normal net, but has clean default preferences (eg.
no leaks with the use of Google resources) and better privacy settings
by default and Fingerprinting countermeasures, SpyBlock.

IceCat is generated from Firefox with the scripts available at
http://git.savannah.gnu.org/cgit/gnuzilla.git
-- 


__
I'm using this express-made address because personal addresses aren't
masked enough at Debian list's archives. Mailing lists service
administrator should fix this.

Bug#860876: [Debian-med-packaging] Bug#860876: reapr: FTBFS: Error in system call: R CMD BATCH 00.Sample/gc_vs_cov.R 00.Sample/gc_vs_cov.Rout

2017-04-21 Thread Sascha Steinbiss

reassign 860876 r-cran-kernsmooth
thanks


Hi Chris,

thanks for your bug report. I can reproduce the problem; it looks like an R 
component within REAPR’s build time tests has started to fail, causing the 
whole build to break.

[…]
>  [REAPR preprocess] Error in system call:
>  R CMD BATCH 00.Sample/gc_vs_cov.R 00.Sample/gc_vs_cov.Rout
>  debian/rules:33: recipe for target 'override_dh_auto_test' failed
>  make[1]: *** [override_dh_auto_test] Error 1
>  make[1]: Leaving directory '«BUILDDIR»'
>  debian/rules:4: recipe for target 'build' failed
>  make: *** [build] Error 2
>  dpkg-buildpackage: error: debian/rules build gave error exit status 2

I have traced the error down to the R script in question used by the tests 
(00.Sample/gc_vs_cov.R). Indeed there is an error running it, which is apparent 
when looking at 00.Sample/gc_vs_cov.Rout:

  […]
  > data=read.csv(file="00.Sample/gc_vs_cov.dat", colClasses=c("numeric", 
"integer"), header=F, sep="   ", comment.char="")
  > l=lowess(data)
  > data_out=unique(data.frame(l$x,l$y))
  > write(t(data_out), sep="", ncolumns=2, 
file="00.Sample/gc_vs_cov.lowess.dat.tmp")
  > pdf("00.Sample/gc_vs_cov.lowess.pdf")
  >   smoothScatter(data, xlab="GC", ylab="Coverage")
  Error in linbin2D(x, gpoints1, gpoints2) : object 'F_lbtwod' not found
  Calls: smoothScatter ->  ->  -> linbin2D
  Execution halted

It looks like r-cran-kernsmooth has trouble finding the Fortran components on 
newer R versions (I tested 3.4.0 from unstable). It works fine on R 3.3.3 (as 
it is in stretch). To reproduce without messing with REAPR, it should even be 
enough to try and run the tests/bkfe.R script included in the kernsmooth source:

  [vagrant@vagrant-debian:/vagrant/kernsmooth-2.23-15/tests] $ R CMD BATCH 
bkfe.R
  [vagrant@vagrant-debian:/vagrant/kernsmooth-2.23-15/tests] $ cat bkfe.Rout
  R version 3.4.0 (2017-04-21) -- "You Stupid Darkness"
  Copyright (C) 2017 The R Foundation for Statistical Computing
  Platform: x86_64-pc-linux-gnu (64-bit)

  R is free software and comes with ABSOLUTELY NO WARRANTY.
  You are welcome to redistribute it under certain conditions.
  Type 'license()' or 'licence()' for distribution details.

  R is a collaborative project with many contributors.
  Type 'contributors()' for more information and
  'citation()' on how to cite R or R packages in publications.

  Type 'demo()' for some demos, 'help()' for on-line help, or
  'help.start()' for an HTML browser interface to help.
  Type 'q()' to quit R.

  > ## failed in bkfe with exaxt powers of 2 prior to 2.23-5
  > library(KernSmooth)
  KernSmooth 2.23 loaded
  Copyright M. P. Wand 1997-2009
  > x <- 1:100
  > dpik(x, gridsize = 256)
  Error in linbin(x, gpoints, truncate) : object 'F_linbin' not found
  Calls: dpik -> linbin
  Execution halted

This also works with no problems when run using R 3.3.3. Unfortunately, I am 
not an R expert, so could someone with some more experience please have a look? 
Thanks!

Cheers
Sascha



signature.asc
Description: Message signed with OpenPGP

Bug#860903: Current setup causes breakage when trying to use apt with pkcs11

2017-04-21 Thread Andreas Metzler

On 2017-04-21 Marga Manterola  wrote:
> On Fri, Apr 21, 2017 at 7:10 PM Andreas Metzler  wrote:
[...]
>>> /etc/pkcs11 directory looks like this:

>>> $ ls -ld /etc/pkcs11 /etc/pkcs11/
>>> lrwxrwxrwx 1 root root 21 Jan  3 14:14 /etc/pkcs11 ->
>>> /var/lib/opencryptoki
>>> drwxrwx--- 8 root pkcs11 4096 Apr 21 10:33 /etc/pkcs11/
[...]



>> Isn't this where the actual breakage is located? Afaik /etc should
>> contain configuration files, not symlinks to unreadable empty
>> directories. O are there special mitigating circumstances?

> This is how the opencryptoki package is shipped:
> http://sources.debian.net/src/opencryptoki/2.3.1%2Bdfsg-3/usr/lib/pkcs11/api/Makefile.am/?hl=47#L47

I know, I doublechecked, I was wondering about your opinion. ;-)

> To be honest, I'm not sure if this is breaking policy or not.
> https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files seems
> to say that symlinking is not ideal but possible.  Doesn't talk about the
> permissions. It *is* possible to have files in /etc/ that are not world
> readable

Policy allows symlinks pointing *to* files in /etc as workaround, not
the other way round.

> Regardless of this, I see no reason why p11-kit should be ok with the file
> not existing but not ok with it not being readable by the current process.

I will forward upstream.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#860842: silently exits on first run