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

[Niels Thykier]

Hilmar Preuße:
> tags 836759 + pending
> stop
> 
> On 19.09.2016 19:29, Niels Thykier wrote:
>> On Sat, 17 Sep 2016 22:36:20 +0200 Hilmar Preusse  wrote:
> 
> Hi,
> 
>>> Is it OK to simply remove that check? Is there an replacement for
>>> hardening-check?
>>>
>> Hi Hilmar :)
>>
>> I believe you can just remove that check.
>>
> Done in git, tag pending.
> 

Thanks,

>> As for a replacement, lintian will still implement the hardening-no-*
>> tags, which were based on the code from hardening-check.
>>
> Hmm: lintian still depends on hardening-includes. Not my problem. ;-)
> 
> Hilmar
> 

Indeed, the dependency will be removed in the next upload. :)

Thanks,
~Niels

Bug#838283: org-mode: notmuch links are unescaped twice

[Bastien Guerry]

Hi David,

David Bremner  writes:

> org-open-at-point calls org-link-unescape on the search term before
> invoking org-notmuch-follow-link, so it's a bad idea to call it again
> in org-notmuch-follow-link. In particular this breaks links with '%'
> in them.
>
> Here is a definition of org-notmuch-follow-link (from org-notmuch.el)
> which seems to work.
>
> (defun org-notmuch-follow-link (search)
>   "Follow a notmuch link to SEARCH.
>
> Can link to more than one message, if so all matching messages are shown."
>   (require 'notmuch)
>   (notmuch-show search))

thanks for reporting this -- agreed, and the fix looks good.

My connection is bad at the moment, I will fix this in contrib/
sometimes next week, unless someone with write access beat me on
this one.

All best,

-- 
 Bastien

Bug#641974: 7kaa: Not translated

[Bertrand Marc]

Hi,

Translation support was added back in 2013, but for some reason upstream 
deactivated the translations in 2015. See 
https://github.com/the3dfxdude/7kaa/commits/master/po.

Cheers,
Bertrand



signature.asc
Description: OpenPGP digital signature

Bug#626760: 7kaa: pressing the window manager close button does not work on the title screen

[Bertrand Marc]

Hi,

It seems this was fixed in (at least) 2.14.5-1 version. Could you please check 
and hopefully close this old bug ?

Cheers,
Bertrand



signature.asc
Description: OpenPGP digital signature

Bug#776527: OpenJDK Server VM warning: ignoring option PermSize=128m; support was removed in 8.0

[U B, Avinash]

Version : 8u102-b14.1

Package: openjdk-8-jre-headless
Tags: patch

Reproducer:

Installation of openjdk-8-jre-headless on i386 or sparc.

Patch:

Warning occurs due to the usage of -XX:PermSize=128m with java during postinst 
script of jre-headless package and PermSize; support was removed in 8.0


diff --git a/debian/JB-jre-headless.postinst.in 
b/debian/JB-jre-headless.postinst.in
index 1f86eeb..0d4bd5b 100644
--- a/debian/JB-jre-headless.postinst.in
+++ b/debian/JB-jre-headless.postinst.in
@@ -110,7 +110,7 @@ configure)
 case @archdir@ in i386|sparc)
rm -f $basedir/jre/lib/@archdir@/client/classes.jsa
log=$(tempfile)
-   if ! $basedir/bin/java -client -Xshare:dump -XX:PermSize=128m > $log; 
then
+   if ! $basedir/bin/java -client -Xshare:dump > $log; then
cat >&2 $log
rm -f $log
# this may fail on some machines/configurations, just ignore it.

Verified the fix, and it works fine.

Thanks,
Avinash UB
HPE

Bug#838194: [Pkg-swan-devel] Bug#838194: support for network-manager-strongswan 1.4?

[Harald Dunkel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Yves,

I can see the new 5.5.0-2 source package on the ftp server,
but many binary packages are still missing, esp. for amd64.
Other platforms look fine.

Is there a problem with the patch?


Regards
Harri

-BEGIN PGP SIGNATURE-

iQEcBAEBCAAGBQJX4MPwAAoJEAqeKp5m04HLlYcH/27qKCYpQLt5iVfVyxMFHajn
QeFiXP8w21Fq0VOhtE7MO4z4N0ECNeAZbh5Mzjqao2iET2I3sqVrTCKj4DKO0wPW
is/GZ8ssPC//5cKita9RLVvbFtj3uvWuZQMb+iGb5oR7AfIc5PMyh4FWVVpvVjPs
KIMkn+hAgTrk5tEyziJy7HdSdLk/RoKipjUR9ohv6AXifvrFHB3RyHZ9u+BCKUUQ
aUyNaBpBwAIbsOOprnmDQU/JQCKS0AFWtWUpGDC0/cBaGVsL3KtaWmzSKJVBvZ42
U/xoSiO5Y9J2n4nlLCeXbipqFtcGphFO0T+ULzarPI/QPautZP6IYoeCSrDcEeM=
=G5Y+
-END PGP SIGNATURE-

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

[lumin]

On Tue, 2016-09-20 at 04:29 +0800, Aron Xu wrote:
> 
> Hi,
> 
> I still have question on your patchset:
> 
> 1. There is no need to override dh_fixperm explicitly for this
> warning, this should be fixed upstream to remove the executable bit.

Ok, got it.

> 
> 2. From what I read the disabled status of zfs-import-scan.service is
> intended, I wonder if this is preventing mounts when ZFS is used as
> rootfs (so you make it enabled explicitly):
> https://github.com/zfsonlinux/zfs/commit/92547bc45ca9a2114662d9343ae5
> 3e5098acb627

Well, this 'enable zfs-import-scan' change is due to my
misunderstanding
in previous discussion, however it's my fault not to check
upstream document about the reason why that default was made.

My root is still ext4 so I cannot verify zfs-initramfs behaviour.

> 
> Thanks,
> Aron

Bug#801366: prototype

[Julien Puydt]

Hi,

On 19/09/2016 22:49, Gordon Ball wrote:

I have put together a more-or-less working jupyter-notebook package [1].
This only requires one as-yet-unpackaged dependency:
libjs-jquery-typeahead [2]. Everything else can be satisfied from
unstable, although a couple of dependencies are technically outdated:

codemirror (>= 5.8, only 5.4 available),
term.js (>= 0.0.7, only 0.0.4 available)
jquery (>= 2.0, 1.12 available - but I think this is equivalent except
version 2 removes shims for old browsers)


Looks good.


The only messy part is google-caja, the upstream for which appears to be
a jupyter-created nodejs repo containing itself the static output of the
upstream caja project, which looks like a nightmare to package. Since
the generated output is non-minified, readable code and includes a
license statement I propose to include it as-is.


Last time I had a look, that was a single file. But if it's generated, 
I'm not sure we can include it as-is -- at least outside of experimental.



The upstream tarball is DFSG'd removing all the web components.


Good.


The resulting package appears to work (tested: markdown, simple python,
matplotlib output, opening the builtin terminal).


Excellent.


The package is only built for python3 - I originally tried to build py2
and py3 support with a common data package, but since this is
effectively an application and you can still run the python2 kernel
there seems little point packaging a python2 version and adding extra
complexity.


Agreed.


The package currently only requires the javascript packages at
build-time, and copies the relevant files into the binary package. It
would be possible to symlink the files on install as well, but I suspect
it would be easier to freeze the set at build (should probably add
built-using headers).


I think symlinking will be needed to get outside of experimental.

That sounds wonderful : congrats for your work!

Snark on #debian-python

Bug#836881: Mea culpa

[Timothy Pearson]

Good catch!  The version was wrong, and in fact was pulled four days
before my commit that fixed this bug last year.  Apologies for the noise,
I had no idea the version in Stretch was that old.

Bug#838338: ITP: python-parquet -- pure-python implementation parquet reader

[陳昌倬]

Package: wnpp
Severity: wishlist
Owner: "ChangZhuo Chen (陳昌倬)" 

* Package name: python-parquet
  Version : 1.1
  Upstream Author : Joe Crobak
* URL : https://github.com/jcrobak/parquet-python
* License : Apache 2.0
  Programming Lang: Python
  Description : pure-python implementation parquet reader

 python-parquet is a pure-python implementation (currently with only
 read-support) of the parquet format. It comes with a script for reading
 parquet files and outputting the data to stdout as JSON or TSV (without the
 overhead of JVM startup). Performance has not yet been optimized, but it's
 useful for debugging and quick viewing of data in files.


This package will be maintained under Debian Python Modules Team.

-- 
ChangZhuo Chen (陳昌倬) 
Debian Developer (https://nm.debian.org/public/person/czchen)
Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D
  BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#837372: #3872: when using gpgme, the signature information is brightyellow making it difficult to read

[Mutt]

#3872: when using gpgme, the signature information is brightyellow making it
difficult to read
+--
  Reporter:  antonio@…  |  Owner:  mutt-dev
  Type:  defect | Status:  new
  Priority:  minor  |  Milestone:
 Component:  crypto |Version:  1.7.0
Resolution: |   Keywords:
+--

Comment (by kevin8t8):

 Thanks Antonio.  The analysis looks correct to me.  We only want to tag
 the "[--..." output with the attachment marker.

 I'll take a closer look at the patch tomorrow.

--
Ticket URL: 
Mutt 
The Mutt mail user agent

Bug#838337: pluma: Wrong mouse cursor when scrolling is invoked

[Julian]

Package: pluma
Version: 1.14.1-1
Severity: normal

Hi,

when the mouse cursor is within a pluma tab and I use the mouse or touchpad
scroll function it is replaced with some kind of "move" cursor (not the one of
the actual theme as far as I can tell).
It stays this way as long as I don't press a key or leave the pluma window with
the cursor.
Leaving the tab (the text input) but staying within the pluma window will
change the cursor only temporarily and it will switch back to "move" when
entering the tab.
When the cursor switches back to normal due to keypressing it doesn't switch to
the move cursor as long as I don't leave and re-enter the pluma window. Even
when I scroll again.
It doesn't have to actually scroll to happen, using the scroll buttons or touch
gesture is enough.

It's not very easy to explain, sorry. ;)
I'll attach a small video.



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

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

Versions of packages pluma depends on:
ii  iso-codes 3.70-1
ii  libatk1.0-0   2.21.90-2
ii  libc6 2.23-5
ii  libcairo-gobject2 1.14.6-1+b1
ii  libcairo2 1.14.6-1+b1
ii  libenchant1c2a1.6.0-11+b1
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.49.6-1
ii  libgtk-3-03.21.5-3
ii  libgtksourceview-3.0-13.21.6-1
ii  libice6   2:1.0.9-1+b1
ii  libmate-desktop-2-17  1.14.1-1
ii  libpango-1.0-01.40.2-1
ii  libpangocairo-1.0-0   1.40.2-1
ii  libsm62:1.2.2-1+b1
ii  libstartup-notification0  0.12-4
ii  libx11-6  2:1.6.3-1
ii  libxml2   2.9.4+dfsg1-2
ii  mate-desktop-common   1.14.1-1
ii  pluma-common  1.14.1-1

Versions of packages pluma recommends:
ii  zenity  3.20.0-1

pluma suggests no packages.


pluma_cursor2.mp4
Description: video/mp4

Bug#727514: blocking the ppc64el architecture bootstrap

[Logan Rosen]

Hi,

taningia now builds successfully on the new(-ish) ppc64el and arm64
architectures thanks to changes made in libtool and debhelper. There
is no longer a specific fix necessary for taningia to build on these
architectures, so this bug can be closed.

Thanks,
Logan

Bug#836691: Info received ()

[Karen Ogburn]

Who is tracking me?
On Sep 19, 2016 9:48 PM, "Debian Bug Tracking System" 
wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian TeX Maintainers 
>
> If you wish to submit further information on this problem, please
> send it to 836...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 836691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836691
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#836691:

[Karen Ogburn]

What is this?

Bug#838336: gnome-control-center: Keybinding panel fail to open

[mathieu rousseau]

Package: gnome-control-center
Version: 1:3.21.92-2
Severity: grave
Justification: renders package unusable

In gnome-control-center, the "keyboard" entry, for keybinding configuration 
fail to open (and gnome-control-center close). The trace i got in terminal is : 

(gnome-control-center:24830): Gtk-CRITICAL **: Error building template class 
'CcKeyboardPanel' for an instance of type 'CcKeyboardPanel': .:2:1622 Invalid 
property: GtkScrolledWindow.propagate_natural_width

(gnome-control-center:24830): Gtk-CRITICAL **: gtk_container_add: assertion 
'GTK_IS_CONTAINER (container)' failed
[…]
(gnome-control-center:24830): Gtk-CRITICAL **: gtk_list_box_set_sort_func: 
assertion 'GTK_IS_LIST_BOX (box)' failed

(gnome-control-center:24830): Gtk-CRITICAL **: gtk_list_box_set_header_func: 
assertion 'GTK_IS_LIST_BOX (box)' failed

(gnome-control-center:24830): Gtk-CRITICAL **: gtk_list_box_set_filter_func: 
assertion 'GTK_IS_LIST_BOX (box)' failed

(gnome-control-center:24830): Gtk-CRITICAL **: gtk_list_box_set_placeholder: 
assertion 'GTK_IS_LIST_BOX (box)' failed

(gnome-control-center:24830): Gtk-CRITICAL **: gtk_box_pack: assertion 
'GTK_IS_WIDGET (child)' failed

(gnome-control-center:24830): GLib-GObject-CRITICAL **: g_object_ref: assertion 
'G_IS_OBJECT (object)' failed

(gnome-control-center:24830): Gtk-CRITICAL **: gtk_size_group_add_widget: 
assertion 'GTK_IS_WIDGET (widget)' failed
**
ERROR:cc-panel.c:202:cc_panel_size_allocate: assertion failed: (child)



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

Kernel: Linux 4.6.0-1-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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-control-center depends on:
ii  accountsservice0.6.40-3
ii  apg2.2.3.dfsg.1-4
ii  colord 1.3.3-2
ii  desktop-file-utils 0.23-1
ii  gnome-control-center-data  1:3.21.92-2
ii  gnome-desktop3-data3.21.92-1
ii  gnome-settings-daemon  3.21.90-2
ii  gsettings-desktop-schemas  3.21.4-2
ii  libaccountsservice00.6.40-3
ii  libatk1.0-02.21.90-2
ii  libc6  2.23-5
ii  libcairo-gobject2  1.14.6-1+b1
ii  libcairo2  1.14.6-1+b1
ii  libcanberra-gtk3-0 0.30-3
ii  libcanberra0   0.30-3
ii  libcheese-gtk253.21.92-1
ii  libcheese8 3.21.92-1
ii  libclutter-1.0-0   1.26.0-2
ii  libclutter-gtk-1.0-0   1.8.0-2
ii  libcolord-gtk1 0.1.26-1
ii  libcolord2 1.3.3-2
ii  libcups2   2.1.4-4
ii  libfontconfig1 2.11.0-6.7
ii  libgdk-pixbuf2.0-0 2.34.0-1
ii  libglib2.0-0   2.49.6-1
ii  libgnome-bluetooth13   3.20.0-1
ii  libgnome-desktop-3-12  3.21.92-1
ii  libgoa-1.0-0b  3.21.91-1
ii  libgoa-backend-1.0-1   3.21.91-1
ii  libgrilo-0.3-0 0.3.2-1
ii  libgtk-3-0 3.21.5-3
ii  libgtop-2.0-10 2.34.1-2
ii  libgudev-1.0-0 230-3
ii  libibus-1.0-5  1.5.11-1
ii  libkrb5-3  1.14.3+dfsg-2
ii  libmm-glib01.6.0-1
ii  libnm0 1.2.4-2
ii  libnma01.2.4-1
ii  libpango-1.0-0 1.40.2-1
ii  libpangocairo-1.0-01.40.2-1
ii  libpolkit-gobject-1-0  0.105-16
ii  libpulse-mainloop-glib09.0-3
ii  libpulse0  9.0-3
ii  libpwquality1  1.3.0-1
ii  libsmbclient   2:4.4.5+dfsg-3
ii  libsoup2.4-1   2.55.90-1
ii  libupower-glib30.99.4-3
ii  libwacom2  0.19-1
ii  libx11-6   2:1.6.3-1
ii  libxi6 2:1.7.6-1
ii  libxml22.9.4+dfsg1-2

Versions of packages gnome-control-center recommends:
ii  cracklib-runtime  2.9.2-3
ii  cups-pk-helper0.2.6-1
ii  gkbd-capplet  3.6.0-1
ii  gnome-online-accounts 3.21.91-1
ii  gnome-user-guide  3.20.2-1
ii  gnome-user-share  3.18.2-1
ii  iso-codes 3.70-1
ii  libnss-myhostname 231-4
ii  mousetweaks   3.12.0-1
ii  network-manager-gnome 1.2.4-1
ii  policykit-1   0.105-16
ii  pulseaudio-module-bluetooth   9.0-3
ii  realmd0.16.3-1
ii  rygel 0.30.3-1
ii  rygel-tracker 0.30.3-1
ii  system-config-printer-common  1.5.7-2

Versions of packages gnome-control-center suggests:
ii  gstreamer1.0-pulseaudio  1.8.3-1+b1
pn  libcanberra-gtk-module   
ii  libcanberra-gtk3-module  0.30-3
ii  x11-xserver-utils7.7+7

-- no debconf information

Bug#798043: Bug update

[salsaman]

Hi,
first of all, I am the main developer of LiVES. Please cc the address
salsaman+li...@gmail.com to all future bugs related to LiVES. You are also
welcome to report bugs on the mailing list or via the issue tracker (
https://sourceforge.net/p/lives/bugs/).

I will look into the issues that you mention, they should certainly be
considered bugs. The idea with making the working directory world writeable
was to allow collaborative editing, but I agree that this would be better
done via umask.

Regarding the second point (creating ~/livestmp even when the user selects
an alternate) that is certainly a bug if it leaves an empty directory
around. It may be that LiVES needs to create it to write some temporary
files during initialisation, but it ought to delete it afterwards at least,
if it wasn' t there prior to the install.

Thanks for your feedback.


Gabriel.




http://lives-video.com
https://www.openhub.net/accounts/salsaman

Bug#756565: Bug update

[salsaman]

Hi,
first of all, I am the main developer of LiVES. Please cc the address
salsaman+li...@gmail.com to all future bugs related to LiVES.

Secondly, there is incorrect information in this bug report.
>>

You'll see that $curtmpdir is set to /tmp/smogrify, via code such as:

$handle=$ARGV[1];
$curtmpdir="$tmpdir/$handle";

>>

In fact $tmpdir is a bit of a misnomer, it points to the LiVES working
directory, which is created for LiVES at install and chosen by the user,
(or a subdirectory of this). $handle is a random number generated for the
clip. So in this case it would be something like
/home/user/livestmp/34736474/ or
/home/user/livestmp/setname/clips/434637826/


In fact /tmp is not used at all.

If there is a genuine problem here I would be happy to correct it.


Regards,

Gabriel.





http://lives-video.com
https://www.openhub.net/accounts/salsaman

Bug#814248: more work done

[Russell Coker]

On Tuesday, 20 September 2016 1:55:14 AM AEST Markus Koschany wrote:
> Confirmed. The same happens here on my machine. Unfortunately that's a
> show-stopper. I think I will upload a new revision that Build-Conflicts
> with automake and thus resolves #824011 and then I push my changes to
> the SVN repo. Perhaps someone else is able to spot the mistake.

I still think that a build-conflicts is the wrong option when you can make it 
build with both packages installed.  My patch allows it to build regardles of 
any other packages installed.

Why do you think that build-conflicts is the right solution?

-- 
My Main Blog http://etbe.coker.com.au/
My Documents Bloghttp://doc.coker.com.au/

Bug#794721: Info received (Bug#794721: Acknowledgement (udev_queue_get_udev_is_active API is broken starting in 221-1))

[Jon DeVree]

The attached patches are about as clean as I can make it. The first one
fixes the initial problem I found during git-bisect. The second one
fixes the part of the problem that upstream pointed out in the issue/PR.


-- 
Jon
Doge Wrangler
X(7): A program for managing terminal windows. See also screen(1) and tmux(1).
>From 96f849cfd2aa1d40309ba050a79e9070a69af01b Mon Sep 17 00:00:00 2001
From: Jon DeVree 
Date: Mon, 19 Sep 2016 21:02:55 -0400
Subject: [PATCH 1/2] Add udev_ctrl_cleanup() to manager_exit()

This fixes the initial bug added in 693d371 (udevd: move main-loop to sd-event)
which results in manager_exit() deleting the udev_ctrl structure before
calling the cleanup routine on it.

Signed-off-by: Jon DeVree 
---
 src/udev/udevd.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/udev/udevd.c b/src/udev/udevd.c
index 19f1c29..1236f73 100644
--- a/src/udev/udevd.c
+++ b/src/udev/udevd.c
@@ -741,6 +741,8 @@ static void manager_exit(Manager *manager) {
   "STOPPING=1\n"
   "STATUS=Starting shutdown...");
 
+udev_ctrl_cleanup(manager->ctrl);
+
 /* close sources of new events and discard buffered events */
 manager->ctrl_event = sd_event_source_unref(manager->ctrl_event);
 manager->ctrl = udev_ctrl_unref(manager->ctrl);
-- 
2.9.3

>From 603e5879b499215937e51d1ec1cdb498881e0dab Mon Sep 17 00:00:00 2001
From: Jon DeVree 
Date: Mon, 19 Sep 2016 21:05:41 -0400
Subject: [PATCH 2/2] Don't throw away udev_ctrl in forking mode.

This fixes a bug in forking mode where udev_ctrl is thrown away
which prevents it from being cleanly disposed of during shutdown.

Signed-off-by: Jon DeVree 
---
 src/udev/udevd.c | 11 +++
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/src/udev/udevd.c b/src/udev/udevd.c
index 1236f73..64615d4 100644
--- a/src/udev/udevd.c
+++ b/src/udev/udevd.c
@@ -1269,13 +1269,14 @@ static int on_post(sd_event_source *s, void *userdata) {
 return 1;
 }
 
-static int listen_fds(int *rctrl, int *rnetlink) {
+static int listen_fds(int *rctrl, int *rnetlink, struct udev_ctrl **ctrlp) {
 _cleanup_udev_unref_ struct udev *udev = NULL;
 int ctrl_fd = -1, netlink_fd = -1;
 int fd, n, r;
 
 assert(rctrl);
 assert(rnetlink);
+assert(ctrlp);
 
 n = sd_listen_fds(true);
 if (n < 0)
@@ -1300,13 +1301,13 @@ static int listen_fds(int *rctrl, int *rnetlink) {
 }
 
 if (ctrl_fd < 0) {
-_cleanup_udev_ctrl_unref_ struct udev_ctrl *ctrl = NULL;
+struct udev_ctrl *ctrl = NULL;
 
 udev = udev_new();
 if (!udev)
 return -ENOMEM;
 
-ctrl = udev_ctrl_new(udev);
+*ctrlp = ctrl = udev_ctrl_new(udev);
 if (!ctrl)
 return log_error_errno(EINVAL, "error initializing udev control socket");
 
@@ -1655,6 +1656,7 @@ exit:
 }
 
 int main(int argc, char *argv[]) {
+_cleanup_udev_ctrl_unref_ struct udev_ctrl *ctrl = NULL;
 _cleanup_free_ char *cgroup = NULL;
 int fd_ctrl = -1, fd_uevent = -1;
 int r;
@@ -1728,7 +1730,7 @@ int main(int argc, char *argv[]) {
 }
 }
 
-r = listen_fds(_ctrl, _uevent);
+r = listen_fds(_ctrl, _uevent, );
 if (r < 0) {
 r = log_error_errno(r, "could not listen on fds: %m");
 goto exit;
@@ -1764,6 +1766,7 @@ int main(int argc, char *argv[]) {
 r = run(fd_ctrl, fd_uevent, cgroup);
 
 exit:
+udev_ctrl_cleanup(ctrl);
 mac_selinux_finish();
 log_close();
 return r < 0 ? EXIT_FAILURE : EXIT_SUCCESS;
-- 
2.9.3

Bug#836691: Note#836690: nancy

[nancy tuggle crabtree]

Thank you please mail it to me
Nancy Crabtree
24 Fox Meadows Dr apt A-2
Lebanon, Va. 24266

Nancy
On Sep 4, 2016 6:21 PM, "#WalPromos"  wrote:

> CongratsThis __is your__1,OOO.OO_Walmart___GiftCard
> 

Bug#838335: Please prepare for vala 0.34

[Michael Biebl]

Source: valabind
Version: 0.10.0-0.1
Severity: important
User: pkg-vala-maintain...@lists.alioth.debian.org
Usertags: vala-0.34

Hi,

your package links against libvala-0.32-0 and will need updates once
vala is updated 0.34.
Atm vala 0.34.0 is available in experimental. Please prepare your
package so it builds against this version.

Regards,
Michael


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

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

Bug#838334: Please prepare for vala 0.34

[Michael Biebl]

Source: valadoc
Version: 0.23.2~git20150422-3.1
Severity: important
User: pkg-vala-maintain...@lists.alioth.debian.org
Usertags: vala-0.34

Hi,

your package links against libvala-0.32-0 and will need updates once
vala is updated 0.34.
Atm vala 0.34.0 is available in experimental. Please prepare your
package so it builds against this version.

Regards,
Michael


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

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

Bug#814248: more work done

[Markus Koschany]

On 20.09.2016 01:42, Russell Coker wrote:
> On Monday, 19 September 2016 8:01:03 PM AEST Markus Koschany wrote:
>> I have disabled the test suite to work around this issue. It probably
>> needs another CMake patch to fix this.
> 
> I don't think it's a CMake issue as such, it's an issue of build flags for 
> code relating to Qt libraries.  If I knew what the wrong flags were and where 
> they are applied then I'm sure it would be easy to fix.

Yeah, that's what I was referring to. It's "just" about passing the
right flags to CMake.

> 
>> There were still some other issues like a missing build-dependency on
>> libssl-dev or a missing appdata file but the game builds now. I'm
>> currently reviewing the debdiff and I think I will do a new release soon.
>>
>> Thanks for working on warzone2100.
> 
> When I run the binary produced from that build the units spin wildly in 3D.  
> It's not possible to play the game when the tanks are breakdancing.  I have 
> no 
> idea how to fix this.
> 

Confirmed. The same happens here on my machine. Unfortunately that's a
show-stopper. I think I will upload a new revision that Build-Conflicts
with automake and thus resolves #824011 and then I push my changes to
the SVN repo. Perhaps someone else is able to spot the mistake.

Markus




signature.asc
Description: OpenPGP digital signature

Bug#833848: [gnome-shell] windows hang detection dialog had bad defaults

[Michael Biebl]

Hi


On Tue, 09 Aug 2016 14:00:05 +0200 Landry MINOZA  wrote:
> Package: gnome-shell
> Version: 3.20.3-1+b1
> Severity: normal
> 
> --- Please enter the report below this line. ---
> When a windowed application hangs, gnome launchs a dialog asking if
> user want to force close the application or wait the the application
> become available.
> This dialog is launched with bad defaults, if one closes it with the
> window decoration button or typing [ESC] key, the application is
> killed.
> It caused me to lose some work a few times when an application is a
> little slow to respond and I press [ESC] key to dismiss the force close
> dialog. This behavior is very counter intuitive.

Thanks for your bug report. This is an issue which should be addressed
upstream. For that, please file a bug at

https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-shell


Regards,
Michael


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



signature.asc
Description: OpenPGP digital signature

Bug#838333: Pending fixes for bugs in the libalien-autotools-perl package

[pkg-perl-maintainers]

tag 838333 + pending
thanks

Some bugs in the libalien-autotools-perl package are closed in
revision 6b60238fa870d630af1450382f37e8b17eb22d4d in branch 'master'
by Joenio Costa

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libalien-autotools-perl.git/commit/?id=6b60238

Commit message:

Closes: #838333

Bug#837759: network configuration stops working reliably

[Felipe Sateler]

Control: tags -1 - unreproducible

On 19 September 2016 at 11:24, Martin Pitt  wrote:
> Control: severity -1 important
> Contro: tag -1 unreproducible
>
> In accordance with the severity definitions [1] I downgrade this to
> "important". It does not completely break systemd, we don't enable
> networkd by default, and it does not affect every installation (it's
> not reproducible on our side yet).

I managed to reproduce. Interestingly, this appears to occur only
during boot, but not if networkd is restarted after the boot. To
reproduce I created a bootable debian raw image with mkosi, and
configured as follows:

0. Install $EDITOR
1. Enable networkd (and add a config for ens* with dhcp)
2. Install iproute2
3. Add the service as described in the first post (make sure to add
DefaultDependencies=no to the unit).

After a reboot, I could see that TEST has no addresses.

Use the following to boot the image:
qemu-system-x86_64 -m 512 -vga virtio -bios /usr/share/ovmf/OVMF.fd \
--enable-kvm -drive file=image.raw,format=raw

-- 

Saludos,
Felipe Sateler

Bug#814248: more work done

[Russell Coker]

On Monday, 19 September 2016 8:01:03 PM AEST Markus Koschany wrote:
> I have disabled the test suite to work around this issue. It probably
> needs another CMake patch to fix this.

I don't think it's a CMake issue as such, it's an issue of build flags for 
code relating to Qt libraries.  If I knew what the wrong flags were and where 
they are applied then I'm sure it would be easy to fix.

> There were still some other issues like a missing build-dependency on
> libssl-dev or a missing appdata file but the game builds now. I'm
> currently reviewing the debdiff and I think I will do a new release soon.
> 
> Thanks for working on warzone2100.

When I run the binary produced from that build the units spin wildly in 3D.  
It's not possible to play the game when the tanks are breakdancing.  I have no 
idea how to fix this.

-- 
My Main Blog http://etbe.coker.com.au/
My Documents Bloghttp://doc.coker.com.au/

Bug#808831: RE: Bug#808831: fwupd: Please install the daemon in non-multiarch path

[Michael Biebl]

On Thu, 7 Jan 2016 14:43:28 -0600  wrote:
> Dell - Internal Use - Confidential 
> 
> That depends on the assumption of whether you would expect the daemon to run 
> in more than one architecture on a given system.  If not, why should it be in 
> the non-multiarch path?  

I'm not sure how this is relevant for fwupd, as this package is not
Multi-Arch: same.
So, using /usr/lib/fwupd or /usr/lib/$(DEB_HOST_MULTIARCH)/fwupd would
both be fine.

The benefit of using /usr/lib/fwupd would be, that the paths to the
binaries are stable across architectures, so it's a tad more convenient
to run the binaries by hand.

That said, I would argue this is mostly a matter of taste.

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



signature.asc
Description: OpenPGP digital signature

Bug#838333: ITP: libalien-autotools-perl -- Perl module for locating binaries for the, GNU build system

[Joenio Costa]

Package: wnpp
Severity: wishlist
Owner: Joenio Costa 

* Package name: libalien-autotools-perl
  Version : 0.0.6
  Upstream Author : Richard Simões 
* URL : https://metacpan.org/release/Alien-Autotools
* License : Perl
  Programming Lang: Perl
  Description : Perl module for locating binaries for the GNU build 
system


Perl's idea of a metapackage to provide external binary dependencies for
Perl applications.
.
Alien::Autotools looks for minimum versions of the tools that make up 
the "GNU build system": autoconf, automake, and libtool. For each tool 
that is not found or below the minimum version, it is downloaded, 
compiled and installedit to the Alien-Autotools distribution's shared 
directory.

Bug#838327: dune-pdelab: FTBFS in testing (error: cannot convert 'mem_usage_t*' to 'GlobalLU_t*')

[Ansgar Burchardt]

Santiago Vila writes:
> /usr/include/dune/istl/superlu.hh: In static member function 'static void 
> Dune::SuperLUSolveChooser::solve(superlu_options_t*, SuperMatrix*, 
> int*, int*, int*, char*, double*, double*, SuperMatrix*, SuperMatrix*, void*, 
> int, SuperMatrix*, SuperMatrix*, double*, double*, double*, double*, 
> mem_usage_t*, SuperLUStat_t*, int*)':
> /usr/include/dune/istl/superlu.hh:172:34: error: cannot convert 
> 'mem_usage_t*' to 'GlobalLU_t*' for argument '19' to 'void 
> dgssvx(superlu_options_t*, SuperMatrix*, int*, int*, int*, char*, double*, 
> double*, SuperMatrix*, SuperMatrix*, void*, int, SuperMatrix*, SuperMatrix*, 
> double*, double*, double*, double*, GlobalLU_t*, mem_usage_t*, 
> SuperLUStat_t*, int*)'
>   memusage, stat, info);
>   ^

That looks like an API change in SuperLU.  The following changelog entry
for SuperLU 5.0 looks related:

+---
|  Remove 'static' variable 'Glu' in *gstrf.c, instead, pass it as an argument.
+---[ http://crd-legacy.lbl.gov/~xiaoye/SuperLU/changes.html ]

I wouldn't be surprised if `GlobalLU_t` and `Glu` were related; will try
to look at this.

Ansgar

Bug#838332: keyboard-configuration/unsupported_config_layout bad question

[積丹尼 Dan Jacobson]

Package: keyboard-configuration
Version: 1.149
Severity: wishlist

We are asked "Keep the current keyboard layout in the configuration file?
 The current keyboard layout in the configuration file
 /etc/default/keyboard is defined as ...
 .
 Please choose whether you want to keep it. If you choose this option,
 no questions about the keyboard layout will be asked and the current
 configuration will be preserved."

OK, but it seems if we answer 'yes' then maybe we are missing out on an
update to an even better configuration. And also staying 'subscribed'
for future updates.

And if we answer 'no' then maybe vooosh... our keyboard gets turned off,
forever, who knows.

And maybe we are using an unsupported_config_layout and should 'get back
on the bandwagon' via answering 'no'... who knows.

Bug#838331: mono-reference-assemblies-3.5: does not contain the reference assemblies

[Felipe Sateler]

Package: mono-reference-assemblies-3.5
Version: 3.12.1+dfsg-1
Severity: grave
Justification: renders package unusable

This package appears to not contain much files. Installing the package
does not allow one to xbuild a project targeting .net 3.5. 

It appears that it is missing the required files:
% dpkg -L mono-reference-assemblies-2.0 | wc -l
103
% dpkg -L mono-reference-assemblies-3.5 | wc -l
16

Saludos

-- System Information:
Debian Release: stretch/sid
  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.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mono-reference-assemblies-3.5 depends on:
ii  mono-runtime-common  4.2.1.102+dfsg2-8

mono-reference-assemblies-3.5 recommends no packages.

mono-reference-assemblies-3.5 suggests no packages.

-- no debconf information

Bug#838050: Fix now in upstream

[Andrew Chadwick]

The fix is included upstream in modified form as
https://git.gnome.org/browse/mutter/commit/?id=3137ddb1a1071407f557a181121695e37e5faf3d.
I have not tested this exact patch, but it should work.

This bug will be fixed by mutter 3.22.0, which seems to have just been
tagged upstream.



-- 
Andrew Chadwick

Bug#838330: upgrading python-libtorrent from 0.16.18-1 to 1.1.0-3 makes deluge daemon unusable

[benoit barthelet]

Package: python-libtorrent
Version: 0.16.18-1
Severity: important

keeping python-libtorrent at 0.16.18-1 solves the issue, upgrading to 1.1.0-3
and the deluge deamon hangs forever without any interesting debug log,

deluge devs apparently won't support libtorrent 1.1.0 (http://forum.deluge-
torrent.org/viewtopic.php?p=223925#p223925)

apologies if this isn't the right place to report, but if upstream decided not
to support 1.1.0 libtorrent, deluge users may have issues.

looks like arch ran into similar issues (https://bugs.archlinux.org/task/49861)



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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 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)

Versions of packages python-libtorrent depends on:
ii  dpkg   1.18.10
ii  libboost-python1.55.0  1.55.0+dfsg-3
ii  libboost-system1.55.0  1.55.0+dfsg-4
ii  libc6  2.23-5
ii  libgcc11:6.1.1-11
ii  libstdc++6 6.1.1-11
ii  libtorrent-rasterbar7  0.16.18-1
ii  python 2.7.11-2

python-libtorrent recommends no packages.

python-libtorrent suggests no packages.

-- no debconf information

Bug#838329: xfce4-goodies: Icon missing (hibernate & sleep)

[otyugh]

Package: xfce4-goodies
Version: 4.10
Severity: minor

There is two image missing in xfce4 default theme for "hibernate" and "sleep".
You see that in xfce4-pannel's plugin that add shut/reboot/hib/sleep buttons ;
then you see some are missing.

There is my workaround awaiting for a fix (not that it might be re-used, it
just point out the location of the file missing and where decent replacement
are) :

#!/bin/bash
cd /usr/share/icons/hicolor/scalable/actions
[ ! -x /usr/bin/convert ] && echo "Need imagemagic"
convert /usr/share/icons/hicolor/48x48/apps/xfsm-suspend.png system-suspend.svg
convert /usr/share/icons/hicolor/48x48/apps/xfsm-hibernate.png system-
hibernate.svg
gtk-update-icon-cache-3.0 -f /usr/share/icons/hicolor
echo "Done"



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

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

Versions of packages xfce4-goodies depends on:
ii  mousepad 0.3.0-2
ii  notification-daemon  0.7.6-2
ii  ristretto0.6.3-2
ii  thunar-archive-plugin0.3.1-3
ii  thunar-media-tags-plugin 0.2.1-1
ii  xfburn   0.5.2-1
ii  xfce4-artwork0.1.1a~git+20110420-1
ii  xfce4-battery-plugin 1.0.5-4
ii  xfce4-clipman-plugin 2:1.2.6-1
ii  xfce4-cpufreq-plugin 1.1.0-1
ii  xfce4-cpugraph-plugin1.0.5-1
ii  xfce4-datetime-plugin0.6.2-2
ii  xfce4-dict   0.7.0-1
ii  xfce4-diskperf-plugin2.5.4-3
ii  xfce4-fsguard-plugin 1.0.1-2
ii  xfce4-genmon-plugin  3.4.0-2
ii  xfce4-mailwatch-plugin   1.2.0-2
ii  xfce4-mount-plugin   0.6.7-1
ii  xfce4-netload-plugin 1.2.0-1
ii  xfce4-notes-plugin   1.7.7-5
ii  xfce4-notifyd [notification-daemon]  0.2.4-3
ii  xfce4-places-plugin  1.6.0-1
ii  xfce4-quicklauncher-plugin   1.9.4-11
ii  xfce4-screenshooter  1.8.1-5
ii  xfce4-sensors-plugin 1.2.5-2
ii  xfce4-smartbookmark-plugin   0.4.5-1
ii  xfce4-systemload-plugin  1.1.1-4
ii  xfce4-taskmanager1.0.1-1
ii  xfce4-terminal   0.6.3-1+b1
ii  xfce4-timer-plugin   1.6.0-1
ii  xfce4-verve-plugin   1.0.0-3
ii  xfce4-volumed0.1.13-5
ii  xfce4-wavelan-plugin 0.5.11-3
ii  xfce4-weather-plugin 0.8.3-2
ii  xfce4-xkb-plugin 1:0.5.6-1

Versions of packages xfce4-goodies recommends:
ii  xfce4-power-manager  1.4.1-1

Versions of packages xfce4-goodies suggests:
pn  gigolo  
pn  parole  
pn  xfce4-cellmodem-plugin  
pn  xfce4-hdaps 
pn  xfce4-linelight-plugin  
pn  xfce4-messenger-plugin  
pn  xfce4-mpc-plugin
pn  xfce4-radio-plugin  
pn  xfce4-xfapplet-plugin   
pn  xfswitch-plugin 

-- no debconf information

Bug#838328: ghostscript: need to backport fix for Ghostscript bug 695862 (segfault on certain machines)

[David Madore]

Package: ghostscript
Version: 9.06~dfsg-2+deb8u1

Ghostscript <=9.15 has a bug which manifests itself only on certain
machines, causing it to segfault on certain PDF files.  This is due to
the incorrect assumption that unlocking an already unlocked mutex is a
no-op, something which is not guaranteed by Single Unix, and may or
may not be true depending on the hardware / kernel / phase of the
moon.  See http://bugs.ghostscript.com/show_bug.cgi?id=695862
 > for details.

I have been bitten by this bug (changed my processor and suddenly all
sorts of PDF files wouldn't print), so it is not theoretical.

I believe Debian should backport some fix for this.  One possible fix
(tested on my machine) is attached: it consists of using
error-checking mutexes instead of fast ones (error-checking mutexes
are documented to return EPERM when unlocked twice).  This fix is
called "hacky" by Chris Liddell in the above-mentioned bug report
page, but I think it is perfectly sensible.  Otherwise, backport the
patch made to the ghostscript upstream itself.

-- 
 David A. Madore
   ( http://www.madore.org/~david/ )
Description: fix ghostscript bug #695862 by using error-checking mutexes
Author: David Madore 
Last-Update: 2016-09-20

Index: ghostscript-9.06~dfsg/base/gp_psync.c
===
--- ghostscript-9.06~dfsg.orig/base/gp_psync.c
+++ ghostscript-9.06~dfsg/base/gp_psync.c
@@ -20,6 +20,7 @@
 #include 
 #include "gserrors.h"
 #include "gpsync.h"
+#include 
 
 /*
  * Thanks to Larry Jones  for this revision of
@@ -64,10 +65,21 @@ gp_semaphore_open(gp_semaphore * sema)
 pt_semaphore_t * const sem = (pt_semaphore_t *)sema;
 int scode;
 
+/* Idiotic threads API won't let you create an error-checking mutex
+ * without creating another "mutexattr" object which itself
+ * has to be initialized.  This is _absurdly_ verbose! */
+static pthread_mutexattr_t mutexattr;
+static char mutexattr_initialized = 0;
+
 if (!sema)
 return -1;		/* semaphores are not movable */
+if ( ! mutexattr_initialized ) {
+	mutexattr_initialized = 1;
+	pthread_mutexattr_init();
+	pthread_mutexattr_settype(, PTHREAD_MUTEX_ERRORCHECK);
+}
 sem->count = 0;
-scode = pthread_mutex_init(>mutex, NULL);
+scode = pthread_mutex_init(>mutex, );
 if (scode == 0)
 scode = pthread_cond_init(>cond, NULL);
 return SEM_ERROR_CODE(scode);
@@ -103,6 +115,8 @@ gp_semaphore_wait(gp_semaphore * sema)
 if (scode == 0)
 --sem->count;
 scode2 = pthread_mutex_unlock(>mutex);
+if ( scode2 == EPERM )
+	scode2 = 0;
 if (scode == 0)
 scode = scode2;
 return SEM_ERROR_CODE(scode);
@@ -120,6 +134,8 @@ gp_semaphore_signal(gp_semaphore * sema)
 if (sem->count++ == 0)
 scode = pthread_cond_signal(>cond);
 scode2 = pthread_mutex_unlock(>mutex);
+if ( scode2 == EPERM )
+	scode2 = 0;
 if (scode == 0)
 scode = scode2;
 return SEM_ERROR_CODE(scode);
@@ -149,11 +165,22 @@ gp_monitor_open(gp_monitor * mona)
 pthread_mutex_t *mon;
 int scode;
 
+/* Idiotic threads API won't let you create an error-checking mutex
+ * without creating another "mutexattr" object which itself
+ * has to be initialized.  This is _absurdly_ verbose! */
+static pthread_mutexattr_t mutexattr;
+static char mutexattr_initialized = 0;
+
 if (!mona)
 return -1;		/* monitors are not movable */
+if ( ! mutexattr_initialized ) {
+	mutexattr_initialized = 1;
+	pthread_mutexattr_init();
+	pthread_mutexattr_settype(, PTHREAD_MUTEX_ERRORCHECK);
+}
 mon = &((gp_pthread_recursive_t *)mona)->mutex;
 ((gp_pthread_recursive_t *)mona)->self_id = 0;	/* Not valid unless mutex is locked */
-scode = pthread_mutex_init(mon, NULL);
+scode = pthread_mutex_init(mon, );
 return SEM_ERROR_CODE(scode);
 }
 
@@ -195,6 +222,8 @@ gp_monitor_leave(gp_monitor * mona)
 int scode;
 
 scode = pthread_mutex_unlock(mon);
+if ( scode == EPERM )
+	scode = 0;
 ((gp_pthread_recursive_t *)mona)->self_id = 0;	/* Not valid unless mutex is locked */
 return SEM_ERROR_CODE(scode);
 }

Bug#832840: license-reconcile: diff for NMU version 0.12+nmu1

[gustavo panizzo (gfa)]

On Mon, Sep 19, 2016 at 07:15:50PM +0200, gregor herrmann wrote:
> On Mon, 19 Sep 2016 00:32:17 +0800, gustavo panizzo (gfa) wrote:
> 
> > I've attached the debdiff, I'll push my changes to the git repo after
> > the NMU has been uploaded, let me know if you don't agree with any of
> > this.
> 
> Thanks for your help.
> 
> It might be easier to push the changes to the git repo before an
> upload, with 0.12 instead of 0.12+nmu1, and we can do a regular tram
> upload. -- Whatever you prefer.

I have no preference on the matter, and you are the maintainer.
I've tried to push to the git repo but I have no perms. so I've attached
the diff between HEAD and your last commit to this email

I've fixed a typo lib/Debian/LicenseReconcile/CopyrightDatum.pm as well

thanks!

-- 
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: https://keybase.io/gfa
diff --git a/debian/changelog b/debian/changelog
index becd035..81e9e09 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,15 +1,3 @@
-license-reconcile (0.12) unstable; urgency=medium
-
-  [ gustavo panizzo ]
-  * Update test cases to match licensecheck output. Thanks Petter Reinholdtsen
-for the patches, Fix FTBFS (Closes: #832840).
-  * Fix typo in lib/Debian/LicenseReconcile/CopyrightDatum.pm.
-
-  [ gregor herrmann ]
-  * Remove Nicholas Bamber from Uploaders. Thanks for your work!
-
- -- gustavo panizzo   Sun, 18 Sep 2016 10:40:39 +0800
-
 license-reconcile (0.11) unstable; urgency=medium
 
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
diff --git a/lib/Debian/LicenseReconcile/App.pm b/lib/Debian/LicenseReconcile/App.pm
index 993a12b..f9fa59f 100644
--- a/lib/Debian/LicenseReconcile/App.pm
+++ b/lib/Debian/LicenseReconcile/App.pm
@@ -289,8 +289,6 @@ This contains the core logic of the tool.
 
 =head2 files
 
-=head2 suggest_stanzas
-
 =head1 AUTHOR
 
 Nicholas Bamber, C<<  >>
diff --git a/lib/Debian/LicenseReconcile/CopyrightDatum.pm b/lib/Debian/LicenseReconcile/CopyrightDatum.pm
index ea8383f..06ea421 100644
--- a/lib/Debian/LicenseReconcile/CopyrightDatum.pm
+++ b/lib/Debian/LicenseReconcile/CopyrightDatum.pm
@@ -253,7 +253,7 @@ This method returns a boolean indicating whether the object contains the argumen
 The method will respect the argument if it is a
 L and otherwise stringify and parse it.
 It may also take an optional reference. If this is set on failing to
-verify containment the reason found will be placed in that reference.
+veryify containment the reason found will be placed in that reference.
 
 =head2 copyright_holders 
 
diff --git a/t/08-licensecheck.t b/t/08-licensecheck.t
index c4faf2f..81fea4e 100644
--- a/t/08-licensecheck.t
+++ b/t/08-licensecheck.t
@@ -86,61 +86,61 @@ cmp_deeply(\@data, bag(
 {
 file=>'Apache_2_0',
 license=>'test1',
-	copyright=>['Copyright: 2000 Testophilus Testownik .'],
+	copyright=>['Copyright: 2000 Testophilus Testownik '],
 },
 {
 file=>'FreeBSD',
 license=>'test2',
-	copyright=>['Copyright: 2001 Testophilus Testownik .'],
+	copyright=>['Copyright: 2001 Testophilus Testownik '],
 },
 {
 file=>'GPL_1',
 license=>'test3',
-	copyright=>['Copyright: 2002 Testophilus Testownik .'],
+	copyright=>['Copyright: 2002 Testophilus Testownik '],
 },
 {
 file=>'GPL_2',
 license=>'test4',
-	copyright=>['Copyright: 2003 Testophilus Testownik .'],
+	copyright=>['Copyright: 2003 Testophilus Testownik '],
 },
 {
 file=>'GPL_3',
 license=>'test5',
-	copyright=>['Copyright: 2004 Testophilus Testownik .'],
+	copyright=>['Copyright: 2004 Testophilus Testownik '],
 },
 {
 file=>'LGPL_2',
 license=>'test6',
-	copyright=>['Copyright: 2005 Testophilus Testownik .'],
+	copyright=>['Copyright: 2005 Testophilus Testownik '],
 },
 {
 file=>'LGPL_2_1',
 license=>'test7',
-	copyright=>['Copyright: 2006 Testophilus Testownik .'],
+	copyright=>['Copyright: 2006 Testophilus Testownik '],
 },
 {
 file=>'LGPL_3_0',
 license=>'test8',
-	copyright=>['Copyright: 2007 Testophilus Testownik .'],
+	copyright=>['Copyright: 2007 Testophilus Testownik '],
 },
 {
 file=>'MIT',
 license=>'test9',
-	copyright=>['Copyright: 2008 Testophilus Testownik .'],
+	copyright=>['Copyright: 2008 Testophilus Testownik '],
 },
 {
 file=>'Mozilla_2_0',
 license=>'test10',
-	copyright=>['Copyright: 2009 Testophilus Testownik .'],
+	copyright=>['Copyright: 2009 Testophilus Testownik '],
 },
 {

Bug#707790: [git] Please add dependency on "meld"

[Jens Reyer]

Control: reassign -1 src:git 1:2.9.3-1
Control: retitle -1 [git] Please add dependency on "meld"
Control: found src:git 1:1.7.10.4-2
Control: tags -1 + patch

Hi,

On 11/05/2013 at 10:47, Jens Reyer wrote:
> for creating an "External diff" gitk requires "meld" to be installed.
> So please add a Recommends or Suggests on the meld package in
> debian/control.

I don't find this "External diff" function in gitk anymore, although
meld can still be found in gitk's preferences as "External diff tool".
So probably a gitk suggests meld would still make sense.

However nowadays I think git-gui should recommend or at least suggest
meld, because as Git-citool it uses it as merge tool. This is something
I regularly use. But on a freshly installed system with git-gui and gitk
meld wasn't installed, and not even hinted for.

Reassigning to src:git because I only request any dependency on meld.
Attached patch takes the minimal approach and only adds a suggests meld
to git-gui.

Greets
jre
diff --git a/debian/control b/debian/control
index 4e4132a..a16feb1 100644
--- a/debian/control
+++ b/debian/control
@@ -257,7 +257,7 @@ Architecture: all
 Multi-Arch: foreign
 Depends: git (>> ${source:Upstream-Version}), git (<< ${source:Upstream-Version}-.), tk
 Recommends: gitk
-Suggests: git-doc, aspell
+Suggests: git-doc, aspell, meld
 Description: fast, scalable, distributed revision control system (GUI)
  Git is popular version control system designed to handle very large
  projects with speed and efficiency; it is used for many high profile

Bug#838327: dune-pdelab: FTBFS in testing (error: cannot convert 'mem_usage_t*' to 'GlobalLU_t*')

[Santiago Vila]

Package: src:dune-pdelab
Version: 2.4.1-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel
   dh_testdir -i -O--parallel
   dh_update_autotools_config -i -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
/usr/bin/dunecontrol autogen
WARNING: could not find module dune-alugrid,
   module is also unknown to pkg-config.
   Maybe you need to adjust PKG_CONFIG_PATH!
   dune-alugrid is suggested by dune-pdelab
Skipping dune-alugrid!
--- going to build dune-pdelab  ---

[... snipped ...]

libtool: link: g++ -std=c++11 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fpermissive -pthread 
-pthread -Wl,-z -Wl,relro -o .libs/testgridfunctionspace 
testgridfunctionspace.o -pthread -Wl,-rpath -Wl,/usr/lib/openmpi/lib 
-Wl,--enable-new-dtags  ../../../lib/.libs/libdunepdelab.so -ldunegrid 
-ldunegeometry -ldunecommon -L/usr/lib/openmpi/lib -lmpi -lugS2 -lugS3 -ldevS 
-lm -pthread
g++ -std=c++11 -DHAVE_CONFIG_H -I. -I../../..  -pthread  -I./ -I./  -I./ -I./  
-I./ -I./  -I./ -I./  -I./ -I./  -I./ -I./ -DENABLE_POSIX_CLOCK -I../../.. 
-DGRIDSDIR="\"./grids\"" -DENABLE_UG   -pthread  -I./ -I./  -I./ -I./  -I./ 
-I./  -I./ -I./  -I./ -I./  -I./ -I./ -DENABLE_POSIX_CLOCK 
-I/usr/lib/openmpi/include/openmpi/opal/mca/event/libevent2021/libevent 
-I/usr/lib/openmpi/include/openmpi/opal/mca/event/libevent2021/libevent/include 
-I/usr/lib/openmpi/include -I/usr/lib/openmpi/include/openmpi -pthread 
-DMPIPP_H -DENABLE_MPI=1  -I/usr/include/superlu -DENABLE_SUPERLU -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fpermissive -c -o 
testelasticity-testelasticity.o `test -f 'testelasticity.cc' || echo 
'./'`testelasticity.cc
In file included from /usr/include/dune/istl/paamg/amg.hh:13:0,
 from 
../../../dune/pdelab/backend/istl/seqistlsolverbackend.hh:15,
 from ../../../dune/pdelab/backend/istl/istlsolverbackend.hh:6,
 from ../../../dune/pdelab/backend/istl.hh:7,
 from testelasticity.cc:20:
/usr/include/dune/istl/superlu.hh: In static member function 'static void 
Dune::SuperLUSolveChooser::solve(superlu_options_t*, SuperMatrix*, 
int*, int*, int*, char*, double*, double*, SuperMatrix*, SuperMatrix*, void*, 
int, SuperMatrix*, SuperMatrix*, double*, double*, double*, double*, 
mem_usage_t*, SuperLUStat_t*, int*)':
/usr/include/dune/istl/superlu.hh:172:34: error: cannot convert 'mem_usage_t*' 
to 'GlobalLU_t*' for argument '19' to 'void dgssvx(superlu_options_t*, 
SuperMatrix*, int*, int*, int*, char*, double*, double*, SuperMatrix*, 
SuperMatrix*, void*, int, SuperMatrix*, SuperMatrix*, double*, double*, 
double*, double*, GlobalLU_t*, mem_usage_t*, SuperLUStat_t*, int*)'
  memusage, stat, info);
  ^
Makefile:1646: recipe for target 'testelasticity-testelasticity.o' failed
make[7]: *** [testelasticity-testelasticity.o] Error 1
make[7]: Leaving directory '/<>/dune/pdelab/test'
Makefile:2231: recipe for target 'check-am' failed
make[6]: *** [check-am] Error 2
make[6]: Leaving directory '/<>/dune/pdelab/test'
Makefile:1808: recipe for target 'check-recursive' failed
make[5]: *** [check-recursive] Error 1
make[5]: Leaving directory '/<>/dune/pdelab/test'
Makefile:638: recipe for target 'check-recursive' failed
make[4]: *** [check-recursive] Error 1
make[4]: Leaving directory '/<>/dune/pdelab'
Makefile:620: recipe for target 'check-recursive' failed
make[3]: *** [check-recursive] Error 1
make[3]: Leaving directory '/<>/dune'
Makefile:798: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
/usr/share/dune/dune-debian.mk:26: recipe for target 'override_dh_auto_test' 
failed
make[1]: *** [override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
debian/rules:10: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Seems a GCC 6 related problem.

Thanks.

Bug#837798: RFS: libcgicc/3.2.16-0.1 NMU -- C++ class library for writing CGI applications

[Thomas Pircher]

On 2016-09-18 19:11, Thomas Pircher wrote:

Thinking again, I guess that's not correct. This would require the
packages to be renamed to libcgicc3.


Hi,

I have uploaded a new build to debian mentors for further review.
https://mentors.debian.net/package/libcgicc

This build should address the issues raised on my previous upload, 
modulo mistakes and misinterpretations on my side.
This version does rename the libraries to libcgicc3 (from libcgicc5), 
replacing and conflicting with the previous name.


Thanks,
Thomas

Bug#838321: papi still FTBFS on hppa architecture

[Andreas Beckmann]

Control: tag -1 pending

On 2016-09-19 22:07, Helge Deller wrote:
> papi still fails to build on hppa, since the patch from bug 751411 is not 
> completely correct.
> 
> The patch in "debian/patches/hppa.patch", line 12, needs to check against 
> $arch==parisc (or parisc64), not against "hppa".

Thanks, fixed in GIT.


Andreas

Bug#838308: Please make gir1.2-flatpak-1.0 multiarch aware

[Simon McVittie]

Control: tags 838308 + pending

On Mon, 19 Sep 2016 at 19:02:58 +0200, Michael Biebl wrote:
> gobject-introspection supports multiarch paths nowadays, so you no
> longer need to move the file back to non-multiarch paths in
> debian/gir1.2-flatpak-1.0.install.

Fixed in git, thanks. I'll upload when 0.6.10-1 has migrated.

> It should then also be possible to use
> Multi-Arch: same for gir1.2-flatpak-1.0.

Also done

> Please also consider making libflatpak-dev depend on gir1.2-flatpak-1.0
> (= ${binary:Version}) as per our g-i mini-policy, see
> /usr/share/doc/gobject-introspection/policy.txt

Also done

Bug#838326: Openbox does not support startup notifications.

[Andriy Grytsenko]

Package: openbox
Version: 3.5.2-8
Version: 3.6.1-2
Severity: important

The openbox package in Debian does not support startup notifications and
such behavior creates big problems, especially on slow machines, tablets
and devices like Raspberry Pi, because users cannot see if application
they tried to start really started, and in some cases duplicated try may
freeze whole system (if memory exhausted for example, or other resourse
locked) so cold reboot is needed. Thus may be severity of this bug should
be "serious" but "important" is the least.

Fix is very much trivial though - just adding libxcursor-dev to build
dependencies will fix the issue. Please, fix it both in jessie and in
sid. Thank you.

Bug#838325: ITP: tendermint-log15 -- Tendermint logging toolkit

[Alessio Treglia]

Package: wnpp
Severity: wishlist
Owner: Alessio Treglia 

* Package name: tendermint-log15
  Version : 2.3-67-g9545b24
  Upstream Author : The Tendermint project
* URL : https://github.com/tendermint/log15
* License : Apache-2.0
  Programming Lang: Go
  Description : Tendermint logging toolkit

 Package log15 provides an opinionated, simple toolkit for
 best-practice logging in Go (golang) that is both human
 and machine readable. It is modeled after the Go standard
 library's io and net/http packages and is an alternative
 to the standard library's log package.
 .
 Features
  - A simple, easy-to-understand API.
  - Promotes structured logging by encouraging use of
key/value pairs.
  - Child loggers which inherit and add their own private context.
  - Lazy evaluation of expensive operations.
  - Simple Handler interface allowing for construction of flexible,
custom logging configurations with a tiny API.
  - Color terminal support.
  - Built-in support for logging to files, streams, syslog, and
the network.
  - Support for forking records to multiple handlers, buffering
records for output, failing over from failed handler writes.

Bug#838324: xfdesktop4: drag and drop copies

[otyugh]

Package: xfdesktop4
Version: 4.10.2-3
Severity: normal

Hey,
from a fresh jessie installation on a xfce session,
moving a file to a directory (the two of them on xfdesktop as icon) make the
file being copied instead of moving.

Bug can be fixed by doing a frankendebian compiling the file from stretch.



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

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

Versions of packages xfdesktop4 depends on:
ii  exo-utils   0.10.2-4
ii  libc6   2.19-18+deb8u6
ii  libcairo2   1.14.0-2.1+deb8u1
ii  libdbus-1-3 1.8.20-0+deb8u1
ii  libdbus-glib-1-20.102-1
ii  libexo-1-0  0.10.2-4
ii  libgarcon-1-0   0.2.1-2
ii  libgdk-pixbuf2.0-0  2.31.1-2+deb8u5
ii  libglib2.0-02.42.1-1+b1
ii  libgtk2.0-0 2.24.25-3+deb8u1
ii  libnotify4  0.7.6-2
ii  libpango-1.0-0  1.36.8-3
ii  libthunarx-2-0  1.6.3-2
ii  libwnck22   2.30.7-2
ii  libx11-62:1.6.2-3
ii  libxfce4ui-1-0  4.10.0-6
ii  libxfce4util6   4.10.1-2
ii  libxfconf-0-2   4.10.0-3
ii  xfdesktop4-data 4.10.2-3

Versions of packages xfdesktop4 recommends:
ii  dbus-x11 1.8.20-0+deb8u1
ii  librsvg2-common  2.40.5-1+deb8u2
ii  xdg-user-dirs0.15-2

Versions of packages xfdesktop4 suggests:
pn  menu  

-- no debconf information

Bug#838323: sysconfig.get_path('purelib') points to site-packages directory

[Dmitry Eremin-Solenikov]

Package: libpython3.5-minimal
Version: 3.5.2-5
Severity: normal

Sysconfig module points to site-packages directory instead of
dist-package if compared to distutils.sysconfig. If someone uses
Automake to build/install python extensions (e.g. like hamlib2 does)
then the python module will go to the wrong directory (as Automake uses
sysconfig instead of distuitls.sysconfig by default). See the following
log:

 CUT ==
$ python3
Python 3.5.2+ (default, Sep 10 2016, 10:24:58) 
[GCC 6.2.0 20160901] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_path('purelib')
'/usr/lib/python3.5/site-packages'
>>> from distutils import sysconfig
>>> sysconfig.get_python_lib(0, 0)
'/usr/lib/python3/dist-packages'
 CUT =

-- 
With best wishes
Dmitry


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

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

Versions of packages libpython3.5-minimal depends on:
ii  libc62.23-5
ii  libssl1.0.2  1.0.2h-1

Versions of packages libpython3.5-minimal recommends:
ii  libpython3.5-stdlib  3.5.2-5

libpython3.5-minimal suggests no packages.

-- no debconf information

Bug#837800: Definitely an improvement from a users perspective

[GEHA]

I support packaging 2.7 with v40 by default from a users perspective.
There are already packages in the forums for testing, working very well
imo. See
http://forums.debian.net/viewtopic.php?f=16=88545=60#p624802

Bug#838322: efi-readvar: add support for MokListRT, MokListXRT

[Linn Crosetto]

Package: efitools
Version: 1.4.2-2
Severity: normal
Tags: upstream patch

efi-readvar attempts to read the MokList variable with the following output:

Variable MokList has no entries

shim creates copies of boot service variables MokList and MokListX in
runtime variables MokListRT and MokListXRT. 

I have attached a patch to add support for these variables to efi-readvar and to
remove MokList since it is not accessible.

Thanks.
>From dfcf6d3bc4c98c624cbc0f724afca8bc97117a49 Mon Sep 17 00:00:00 2001
From: Linn Crosetto 
Date: Mon, 12 Sep 2016 15:43:34 -0600
Subject: [PATCH] efi-readvar: add support for MokListRT, MokListXRT

shim creates copies of boot service variables MokList and MokListX in
runtime variables MokListRT and MokListXRT. Add support for these to
efi-readvar and remove MokList since it is not accessible.

Signed-off-by: Linn Crosetto 
---
 efi-readvar.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/efi-readvar.c b/efi-readvar.c
index 816b306..12c644c 100644
--- a/efi-readvar.c
+++ b/efi-readvar.c
@@ -115,9 +115,9 @@ parse_db(const char *name, uint8_t *data, uint32_t len, int sig, int entry)
 int
 main(int argc, char *argv[])
 {
-  char *variables[] = { "PK", "KEK", "db", "dbx" , "MokList" };
+	char *variables[] = { "PK", "KEK", "db", "dbx" , "MokListRT", "MokListXRT" };
 	char *progname = argv[0], *var = NULL, *file = NULL;
-	EFI_GUID *owners[] = { _GUID, _GUID, _DB, _DB, _OWNER };
+	EFI_GUID *owners[] = { _GUID, _GUID, _DB, _DB, _OWNER, _OWNER };
 	int i, found = 0, sig = -1, entry = -1, fd;
 
 	while (argc > 1 && argv[1][0] == '-') {
-- 
2.8.0.rc3

Bug#801366: prototype

[Gordon Ball]

I have put together a more-or-less working jupyter-notebook package [1].
This only requires one as-yet-unpackaged dependency:
libjs-jquery-typeahead [2]. Everything else can be satisfied from
unstable, although a couple of dependencies are technically outdated:

codemirror (>= 5.8, only 5.4 available),
term.js (>= 0.0.7, only 0.0.4 available)
jquery (>= 2.0, 1.12 available - but I think this is equivalent except
version 2 removes shims for old browsers)

The only messy part is google-caja, the upstream for which appears to be
a jupyter-created nodejs repo containing itself the static output of the
upstream caja project, which looks like a nightmare to package. Since
the generated output is non-minified, readable code and includes a
license statement I propose to include it as-is.

The upstream tarball is DFSG'd removing all the web components.

The resulting package appears to work (tested: markdown, simple python,
matplotlib output, opening the builtin terminal).

The package is only built for python3 - I originally tried to build py2
and py3 support with a common data package, but since this is
effectively an application and you can still run the python2 kernel
there seems little point packaging a python2 version and adding extra
complexity.

The package currently only requires the javascript packages at
build-time, and copies the relevant files into the binary package. It
would be possible to symlink the files on install as well, but I suspect
it would be easier to freeze the set at build (should probably add
built-using headers).

[1]: https://git.chronitis.net/notebook/
[2]: https://git.chronitis.net/jquery-typeahead.js/

Bug#838320: installation-reports: debian stretch (testing) installer freezes on the laptop with Intel Celeron N2840 CPU

[Geert Stappers]

Control: -1 moreinfo
Stop

On Mon, Sep 19, 2016 at 11:03:26PM +0300, Oksana Andrusiv wrote:
> 
> The installation of the base system hangs.
> The very last message in log console is "installed discover".
> The issue was reproduced in 100% of attempts with and without network mirror.
> 
> The debian 8 is currently in use on the same laptop thus I suppose it is a new
> problem.

Good that the new problem is being reported.

Please boot with 'priority=low' to get more messages
and report back..

See https://www.debian.org/releases/stretch/arm64/ch05s03.html.en for additional
information.


Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#838189: The name "tox" is fully misleading and should be better "python-tox"

[Barry Warsaw]

On Sep 18, 2016, at 09:56 AM, Klaus Ethgen wrote:

>I set this bug to normal instead of wishlist as it currently blocks
>somehow packaging of other packages.

What other packages does it block, and how exactly does it block them?

>The name "tox" of this package is extremely misleading as normal use
>associate [0] with this name.

I'd quibble with these characterizations since the Python testing tool named
tox appears to predate the instant message tool named tox by many years.  I'd
claim that it's unfortunate that tox.chat chose a name which is very common,
and with a long history in another context.

>More over, it is somewhat python specific so it is better named python-tox.
>While it might be possible to work around the packaging block, that would
>produce a complete mess. So I ask you to please rename the package (back) to
>python-tox. I believe that this will take some time so please don't defere it
>to long.

I don't want to make life difficult for you, but I'm highly resistant to
changing either the package name or the executable name.  I'll wait for your
response, but I intend to close this bug as wontfix.


pgp96hovhsD05.pgp
Description: OpenPGP digital signature

Bug#623819: #623819 - gnome-system-monitor completely transparent when using compiz

[Pedro Beja]

Hi Carlo,

this is an old bug and it seems obsoleted nowadays.

Could you please still reproduce this issue with newer gnome-system-monitor
3.14.1-1 or 3.21.92-1 ?

thanks
regards
Pedro Beja

Bug#623605: #623605 - gnome-system-monitor: Network usage drops on mouseover

[Pedro Beja]

Hi Conrad,

Hi,

this is an old bug.

Could you please still reproduce this issue with newer gnome-system-monitor
version like 3.14.1-1 or 3.21.92-1 ?

thanks
regards
Pedro Beja

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

[Hilmar Preuße]

tags 836759 + pending
stop

On 19.09.2016 19:29, Niels Thykier wrote:
> On Sat, 17 Sep 2016 22:36:20 +0200 Hilmar Preusse  wrote:

Hi,

>> Is it OK to simply remove that check? Is there an replacement for
>> hardening-check?
>>
> Hi Hilmar :)
> 
> I believe you can just remove that check.
> 
Done in git, tag pending.

> As for a replacement, lintian will still implement the hardening-no-*
> tags, which were based on the code from hardening-check.
> 
Hmm: lintian still depends on hardening-includes. Not my problem. ;-)

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

Bug#828393: libevent: FTBFS with openssl 1.1.0

[Kurt Roeckx]

tags 828393 + patch
thanks

A patch is available at:
https://github.com/libevent/libevent/pull/397


Kurt

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

[Aron Xu]

Hi,

I still have question on your patchset:

1. There is no need to override dh_fixperm explicitly for this
warning, this should be fixed upstream to remove the executable bit.
2. From what I read the disabled status of zfs-import-scan.service is
intended, I wonder if this is preventing mounts when ZFS is used as
rootfs (so you make it enabled explicitly):
https://github.com/zfsonlinux/zfs/commit/92547bc45ca9a2114662d9343ae53e5098acb627

Thanks,
Aron

On Sun, Sep 18, 2016 at 10:50 PM, lumin  wrote:
> Hi,
>
> I refreshed the whole patch stack, with some new changes added.
>
> * add a patch to enable zfs-import-scan.service by default.
>   in 0.6.5.7 all zfs services are enabled, and in 0.6.5.8 all
>   services are enabled by upstream except for zfs-import-scan.
>
> * add the missing zfs.target .

Bug#838047: Confirmed: breaks *all* tablets

[Thomas Renard]

Very grave: it breaks Lenovo Yoga Laptops because they have a buildin
wacom display!

Fortunately Wayland can be used as fallback...

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

[Emmanuel Bouthenot]

On Sat, Sep 17, 2016 at 07:35:50PM +0200, Stefan Hornburg (Racke) wrote:

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

I've updated the git repository of sympa, it's ready to be tested.

I'll will probably upload the package into unstable in a few days.

Regards,

-- 
Emmanuel Bouthenot
  mail: kolter@{openics,debian}.orggpg: 4096R/0x929D42C3
  xmpp: kol...@im.openics.org  irc: kolter@{freenode,oftc}

Bug#838320: installation-reports: debian stretch (testing) installer freezes on the laptop with Intel Celeron N2840 CPU

[Oksana Andrusiv]

Package: installation-reports
Severity: critical
Tags: d-i
Justification: breaks the whole system

Dear Maintainer,

The installation of the base system hangs.
The very last message in log console is "installed discover".
The issue was reproduced in 100% of attempts with and without network mirror.

Used hardware: Lenovo Ideapad 100 with Intel Celeron N2840 CPU and RAM 4Gb.
Used image: netinstall for amd64 (weekly build from September 19, 2016).

The system was successfuly installed from the same image as guest into Virtual
Box.
The debian 8 is currently in use on the same laptop thus I suppose it is a new
problem.



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

Kernel: Linux 3.16.7-ckt11 (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)

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

[Adam D. Barratt]

Control: tags -1 + pending

On Sat, 2016-09-17 at 22:20 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Mon, 2016-09-12 at 17:40 +0300, Ilias Tsitsimpis wrote:
> 
> > I would like to update suckless-tools in jessie in order to fix a bug in
> > the slock command (CVE-2016-6866).
> 
> Please go ahead.

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#838319: installation-reports: fails to load non-free firmware for iwlwifi wireless interface

[David Banks]

Package: installation-reports
Severity: normal

When installing stretch, the wireless network interface was not functional.  The
installer recognized the problem and prompted me to load the non-free firmware
from the USB stick.  However, although I tried both methods of extracting the
firmware so that it would be found, it was not automatically loaded by the
installer.  I tried to extract it directly to the root of the USB stick, and
also tried to extract it to the 'firmware' subdirectory.  However the installer
didn't pick it up, and complained that the iwlwifi ucode files couldn't be
loaded.

There were many messages in dmesg like this:

Direct firmware load for iwlwifi-7265D-21.ucode failed with error -2

It was trying numerous different version numbers after the final dash.

I eventually resolved it by going to the shell.  I tried to manually extract the
firmware and copy it to /lib/firmware, then re-enter the menu and configure the
network again.  That made no difference.  Then I tried to manually 'modprobe
iwlwifi'.  This also made no difference.  To get it to work I had to 'modprobe
-r iwlwifi' first, then after I had copied the firmware files to /lib/firmware I
was able to load the firmware using 'modprobe iwlwifi'.  That is, I had to load
and unload the module before it would recognize that the firmware files had been
extracted to the appropriate place.  I'm not sure what version ended up being
loaded to do the install successfully.  I am currently using
'iwlwifi-7265D-21.ucode' in my running system, but I also have
'iwlwifi-7265D-16.ucode' and a couple of other older firmwares present in
/lib/firmware.  It's possible that version 16 was the one used for the 
installation.

FYI although this log shows apt preference as unstable, I have switched to this
apt preference post install.  During the install I was using stretch.

-- Package-specific info:

Boot method: USB stick
Image version: Stretch Alpha 7
Date: 2016-09-12

Machine: ASUS UX303-R4028T
Partitions:
Filesystem Type 1K-blocks  Used Available Use% Mounted on
udev   devtmpfs   6092676 0   6092676   0% /dev
tmpfs  tmpfs  1220512 47544   1172968   4% /run
/dev/sda1  ext4 177755012 149105836  19596660  89% /
tmpfs  tmpfs  6102544480276   5622268   8% /dev/shm
tmpfs  tmpfs 5120 4  5116   1% /run/lock
tmpfs  tmpfs  6102544 0   6102544   0% /sys/fs/cgroup
/dev/sda4  vfat128031 25394102637  20% /boot/efi
tmpfs  tmpfs  122050820   1220488   1% /run/user/118
tmpfs  tmpfs  122050844   1220464   1% /run/user/30500



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

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

Comments/Problems:

See above.

-- 

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

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

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20160630"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux inktvis 4.6.0-1-amd64 #1 SMP Debian 4.6.2-2 (2016-06-25) x86_64 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host 
Bridge/DRAM Registers [8086:1904] (rev 08)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:1b1d]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Sky 
Lake Integrated Graphics [8086:1916] (rev 07)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:247a]
lspci -knn: 00:04.0 Signal processing controller [1180]: Intel Corporation 
Device [8086:1903] (rev 08)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:1b1d]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Device [8086:9d2f] 
(rev 21)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:201f]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:14.2 Signal processing controller [1180]: Intel Corporation 
Device [8086:9d31] (rev 21)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:1b1d]
lspci -knn: 00:16.0 Communication controller 

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

[Adam D. Barratt]

Control: tags -1 + pending

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

Flagged for acceptance into p-u.

Regards,

Adam

Bug#838321: papi still FTBFS on hppa architecture

[Helge Deller]

Package: papi
Version: 5.5.0-1
Severity: normal
Tags: patch

papi still fails to build on hppa, since the patch from bug 751411 is not 
completely correct.

The patch in "debian/patches/hppa.patch", line 12, needs to check against 
$arch==parisc (or parisc64), not against "hppa".

So, can you please modify it, by changing this single line (line #12 or #13):
Instead of:
+  aarch64|arm*|hppa*)
please change to
+  aarch64|arm*|parisc*)

Thanks,
Helge

Bug#836588: [Cupt-devel] Bug#836588: Bug#836588: cupt: FTBFS on armel/armhf: test failures

[Eugene V. Lyubimkin]

On 18.09.2016 22:40, Eugene V. Lyubimkin wrote:
> Thank you. Turned out it is reproducible in release build (at the least on 
> armel porterbox), but not in debug build.
> 
> I'll look into it.

Ok, something fishy is going on with lambda captures. I believe I found an 
issue in either std::function or GCC
optimizer. Looks like a captured value ("this" in this case) is uninitialized 
or corrupted, but only if previous lambda
captures a certain amount of variables, no matter was it called or not. Ugh. I 
managed to reduce
the code to the following small example:

(sid_armhf-dchroot)jackyf@harris:~/smalltests/small-std-function-arm$ cat hm.cpp
#include 
#include 

struct C
{
void doCb()
{
size_t dummy_a = 1;

std::cout << "Outside: " << this << std::endl;
std::function f;
f = [this, _a]()
{};
f = [this]()
{
std::cout << "Inside: " << this << std::endl;
};
f();
}
};

int main()
{
C c;
c.doCb();
}

(sid_armhf-dchroot)jackyf@harris:~/smalltests/small-std-function-arm$ cat 
Makefile
all:
g++ -O2 -Wall -Wextra hm.cpp -o hm.e
(sid_armhf-dchroot)jackyf@harris:~/smalltests/small-std-function-arm$ ./hm.e
Outside: 0xbeaeb5f4
Inside: 0x2
(sid_armhf-dchroot)jackyf@harris:~/smalltests/small-std-function-arm$ 
~/valgrind/valgrind-3.12.0~svn20160714
/vg-in-place ./hm.e
==9628== Memcheck, a memory error detector
==9628== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==9628== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info
==9628== Command: ./hm.e
==9628==
Outside: 0xbdb6a454
==9628== Use of uninitialised value of size 4
==9628==at 0x4916BF6: ??? (in 
/usr/lib/arm-linux-gnueabihf/libstdc++.so.6.0.22)
==9628==
==9628== Conditional jump or move depends on uninitialised value(s)
==9628==at 0x4916BFC: ??? (in 
/usr/lib/arm-linux-gnueabihf/libstdc++.so.6.0.22)
==9628==
==9628== Conditional jump or move depends on uninitialised value(s)
==9628==at 0x49179FA: std::ostreambuf_iterator std::num_put 
>::_M_insert_int(std::ostreambuf_iterator, std::ios_base&, char, unsigned long) const (in 
/usr/lib/arm-linux-gnueabihf/libstdc++.so.6.0.22)
==9628==by 0x4917AC5: std::num_put
>::do_put(std::ostreambuf_iterator, 
>std::ios_base&, char, void const*) const (in
/usr/lib/arm-linux-gnueabihf/libstdc++.so.6.0.22)
==9628==by 0x491FDA3: std::ostream& std::ostream::_M_insert(void const*) (in
/usr/lib/arm-linux-gnueabihf/libstdc++.so.6.0.22)
==9628==
Inside: 0x2
==9628==
==9628== HEAP SUMMARY:
==9628== in use at exit: 0 bytes in 0 blocks
==9628==   total heap usage: 2 allocs, 2 frees, 21,248 bytes allocated
==9628==
==9628== All heap blocks were freed -- no leaks are possible
==9628==
==9628== For counts of detected and suppressed errors, rerun with: -v
==9628== Use --track-origins=yes to see where uninitialised values come from
==9628== ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)

Bug#837759: network configuration stops working reliably

[Wolfgang Walter]

Hello Martin,

On Monday, 19 September 2016 16:24:12 CEST Martin Pitt wrote:
> Control: severity -1 important
> Contro: tag -1 unreproducible
> 
> In accordance with the severity definitions [1] I downgrade this to
> "important". It does not completely break systemd, we don't enable
> networkd by default, and it does not affect every installation (it's
> not reproducible on our side yet).
> 
> Don't worry, I'm still eager to find out what's happening here; I'll
> look at your logs as soon as possible.
> 
> Martin
> 
> [1] https://www.debian.org/Bugs/Developer#severities

Ok, here as attachment is the log with debugging enabled for systemd-networkd.

In this boot net and TEST have lost all there ip-adresses. The logs shows that 
it is systemd-networkd which removes them.

Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts-- Logs begin at Sat 2016-07-02 20:15:26 CEST, end at Mon 2016-09-19 21:24:41 
CEST. --
Sep 19 21:24:03 maiskolben systemd-journald[182]: Runtime journal 
(/run/log/journal/) is 1.2M, max 9.9M, 8.7M free.
Sep 19 21:24:03 maiskolben kernel: Initializing cgroup subsys cpuset
Sep 19 21:24:03 maiskolben kernel: Initializing cgroup subsys cpu
Sep 19 21:24:03 maiskolben kernel: Initializing cgroup subsys cpuacct
Sep 19 21:24:03 maiskolben kernel: Linux version 4.4.21-debianlike64x+1.4 
(root@maiskolben) (gcc version 6.2.0 20160901 (Debian 6.2.0-3) ) #1 SMP PREEMPT 
Thu Sep 15 21:25:55 CEST 2016
Sep 19 21:24:03 maiskolben kernel: Command line: root=/dev/sda quiet
Sep 19 21:24:03 maiskolben kernel: x86/fpu: Legacy x87 FPU detected.
Sep 19 21:24:03 maiskolben kernel: x86/fpu: Using 'lazy' FPU context switches.
Sep 19 21:24:03 maiskolben kernel: e820: BIOS-provided physical RAM map:
Sep 19 21:24:03 maiskolben kernel: BIOS-e820: [mem 
0x-0x0009fbff] usable
Sep 19 21:24:03 maiskolben kernel: BIOS-e820: [mem 
0x0009fc00-0x0009] reserved
Sep 19 21:24:03 maiskolben kernel: BIOS-e820: [mem 
0x000f-0x000f] reserved
Sep 19 21:24:03 maiskolben kernel: BIOS-e820: [mem 
0x0010-0x3ffdcfff] usable
Sep 19 21:24:03 maiskolben kernel: BIOS-e820: [mem 
0x3ffdd000-0x3fff] reserved
Sep 19 21:24:03 maiskolben kernel: BIOS-e820: [mem 
0xfeffc000-0xfeff] reserved
Sep 19 21:24:03 maiskolben kernel: BIOS-e820: [mem 
0xfffc-0x] reserved
Sep 19 21:24:03 maiskolben kernel: NX (Execute Disable) protection: active
Sep 19 21:24:03 maiskolben kernel: SMBIOS 2.8 present.
Sep 19 21:24:03 maiskolben kernel: DMI: QEMU Standard PC (i440FX + PIIX, 1996), 
BIOS Debian-1.8.2-1 04/01/2014
Sep 19 21:24:03 maiskolben kernel: Hypervisor detected: KVM
Sep 19 21:24:03 maiskolben kernel: e820: update [mem 0x-0x0fff] 
usable ==> reserved
Sep 19 21:24:03 maiskolben kernel: e820: remove [mem 0x000a-0x000f] 
usable
Sep 19 21:24:03 maiskolben kernel: e820: last_pfn = 0x3ffdd max_arch_pfn = 
0x4
Sep 19 21:24:03 maiskolben kernel: MTRR default type: write-back
Sep 19 21:24:03 maiskolben kernel: MTRR fixed ranges enabled:
Sep 19 21:24:03 maiskolben kernel:   0-9 write-back
Sep 19 21:24:03 maiskolben kernel:   A-B uncachable
Sep 19 21:24:03 maiskolben kernel:   C-F write-protect
Sep 19 21:24:03 maiskolben kernel: MTRR variable ranges enabled:
Sep 19 21:24:03 maiskolben kernel:   0 base 008000 mask FF8000 
uncachable
Sep 19 21:24:03 maiskolben kernel:   1 disabled
Sep 19 21:24:03 maiskolben kernel:   2 disabled
Sep 19 21:24:03 maiskolben kernel:   3 disabled
Sep 19 21:24:03 maiskolben kernel:   4 disabled
Sep 19 21:24:03 maiskolben kernel:   5 disabled
Sep 19 21:24:03 maiskolben kernel:   6 disabled
Sep 19 21:24:03 maiskolben kernel:   7 disabled
Sep 19 21:24:03 maiskolben kernel: x86/PAT: PAT not supported by CPU.
Sep 19 21:24:03 maiskolben kernel: x86/PAT: Configuration [0-7]: WB  WT  UC- UC 
 WB  WT  UC- UC  
Sep 19 21:24:03 maiskolben kernel: found SMP MP-table at [mem 
0x000f6610-0x000f661f] mapped at [880f6610]
Sep 19 21:24:03 maiskolben kernel: Base memory trampoline at [88099000] 
99000 size 24576
Sep 19 21:24:03 maiskolben kernel: BRK [0x01c7a000, 0x01c7afff] PGTABLE
Sep 19 21:24:03 maiskolben kernel: BRK [0x01c7b000, 0x01c7bfff] PGTABLE
Sep 19 21:24:03 maiskolben kernel: BRK [0x01c7c000, 0x01c7cfff] PGTABLE
Sep 19 21:24:03 maiskolben kernel: BRK [0x01c7d000, 0x01c7dfff] PGTABLE
Sep 19 21:24:03 maiskolben kernel: RAMDISK: [mem 0x3f08c000-0x3ffc]
Sep 19 21:24:03 maiskolben kernel: ACPI: Early table checksum verification 
disabled
Sep 19 21:24:03 maiskolben kernel: ACPI: RSDP 0x000F6440 14 (v00 
BOCHS )
Sep 19 21:24:03 maiskolben kernel: ACPI: RSDT 0x3FFE1737 30 (v01 
BOCHS  BXPCRSDT 0001 BXPC 0001)
Sep 19 21:24:03 maiskolben kernel: ACPI: FACP 0x3FFE1613 74 (v01 
BOCHS  BXPCFACP 0001 BXPC 0001)
Sep 19 21:24:03 maiskolben kernel: 

Bug#838318: ibus: Characters swapped under certain circumstances

[Michaël Meyer]

Package: ibus
Version: 1.5.11-1
Severity: important

Dear Maintainer,

I'm experiencing an annoying glitch with the "sanskrit - IAST (m17n)" input
method: when I press a key that can be part of an input sequence and then
another key that cannot, the corresponding letters are swapped.

For instance: typing "ape" results in "pae", although typing "aei" or "zrt"
produces the corresponding letter sequences.

I've used ibus for a few years on a variety of systems, but never had this
issue.

Regards,

MM

-- Package-specific info:
default-display-manager: /usr/sbin/lightdm
ibus is /usr/bin/ibus
ibus-setup is /usr/bin/ibus-setup
im-config -l =>  ibus xim
im-config -m => default missing ibus ibus
XMODIFIERS=@im=ibus
GTK_IM_MODULE=ibus
QT4_IM_MODULE=xim
QT_IM_MODULE=ibus
XDG_DATA_DIRS=/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share
XDG_MENU_PREFIX=xfce-
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

ls -l /usr/lib/ibus/
total 392
-rwxr-xr-x 1 root root  19144 Nov 20  2015 ibus-dconf
-rwxr-xr-x 1 root root  35904 Oct 26  2014 ibus-engine-m17n
-rwxr-xr-x 1 root root  10696 Nov 20  2015 ibus-engine-simple
-rwxr-xr-x 1 root root  27568 Oct 26  2014 ibus-setup-m17n
-rwxr-xr-x 1 root root 206568 Nov 20  2015 ibus-ui-gtk3
-rwxr-xr-x 1 root root  92824 Nov 20  2015 ibus-x11

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

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

Versions of packages ibus depends on:
ii  adwaita-icon-theme   3.21.91-1
ii  dconf-cli0.26.0-1
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-1
ii  gir1.2-gtk-3.0   3.21.5-3
ii  gir1.2-ibus-1.0  1.5.11-1
ii  libatk1.0-0  2.21.90-2
ii  libc62.23-5
ii  libcairo21.14.6-1+b1
ii  libdconf10.26.0-1
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.49.6-1
ii  libgtk-3-0   3.21.5-3
ii  libibus-1.0-51.5.11-1
ii  libnotify4   0.7.6-2
ii  libpango-1.0-0   1.40.2-1
ii  libpangocairo-1.0-0  1.40.2-1
ii  librsvg2-common  2.40.16-1
ii  libx11-6 2:1.6.3-1
ii  libxi6   2:1.7.6-1
ii  python3-gi   3.21.92-1
pn  python3:any  

Versions of packages ibus recommends:
ii  im-config   0.29-1.4
ii  libqt5gui5  5.6.1+dfsg-3+b1

Versions of packages ibus suggests:
pn  ibus-clutter  
pn  ibus-doc  
pn  ibus-qt4  
ii  libqt5gui55.6.1+dfsg-3+b1

-- no debconf information

Bug#838317: x264 FTCBFS: configures for the build architecture

[Helmut Grohne]

Source: x264
Version: 2:0.148.2699+gita5e06b9-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

x264 fails to cross build from source, because it configures the build
for the build architecture. After recognizing that it uses a
hand-crafted configure script, figuring the right flags is pretty
simple. For cross compilation it wants --host and --cross-prefix. Once
giving these options, it crosses just fine (at least for ppc64el).
Please consider applying the attached patch.

Helmut
diff --minimal -Nru x264-0.148.2699+gita5e06b9/debian/changelog 
x264-0.148.2699+gita5e06b9/debian/changelog
--- x264-0.148.2699+gita5e06b9/debian/changelog 2016-06-14 23:15:14.0 
+0200
+++ x264-0.148.2699+gita5e06b9/debian/changelog 2016-09-19 21:38:55.0 
+0200
@@ -1,3 +1,10 @@
+x264 (2:0.148.2699+gita5e06b9-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Pass cross flags to configure. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 19 Sep 2016 21:20:58 +0200
+
 x264 (2:0.148.2699+gita5e06b9-1) unstable; urgency=medium
 
   * Update to new stable upstream
diff --minimal -Nru x264-0.148.2699+gita5e06b9/debian/confflags 
x264-0.148.2699+gita5e06b9/debian/confflags
--- x264-0.148.2699+gita5e06b9/debian/confflags 2016-01-18 19:57:53.0 
+0100
+++ x264-0.148.2699+gita5e06b9/debian/confflags 2016-09-19 21:24:48.0 
+0200
@@ -20,6 +20,10 @@
 
 common_confflags += --prefix=/usr --libdir=/usr/lib/$(DEB_HOST_MULTIARCH)
 
+ifneq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE))
+common_confflags += --host=$(DEB_HOST_GNU_TYPE) 
--cross-prefix=$(DEB_HOST_GNU_TYPE)-
+endif
+
 ifneq (,$(filter stage1,$(DEB_BUILD_PROFILES)))
 common_confflags += --disable-avs --disable-ffms --disable-gpac
 endif

Bug#838248: unadf: details of CVE-2016-1243 and CVE-2016-1244

[Tuomas Räsänen]

Hi,

Here's details of these vulnerabilities for the curious:

CVE-2016-1243
=

  void extractTree(struct Volume *vol, struct List* tree, char *path, unsigned 
char *extbuf,
   BOOL pflag, BOOL qflag)
  {
  struct Entry* entry;
  char *buf;
  char sysbuf[200];
  
  while(tree) {
  entry = (struct Entry*)tree->content;
  if (entry->type==ST_DIR) {
  buf = NULL;
  if (strlen(path)>0) {
  buf=(char*)malloc(strlen(path)+1+strlen(entry->name)+1);
  if (!buf) return;
  sprintf(buf,"%s%c%s",path,DIRSEP,entry->name);
  sprintf(sysbuf,"%s %s",MKDIR,buf);

Here, sysbuf can be caused to overflow for example by giving an .adf
archive which has a file with very long name and/or path.

CVE-2016-1244
=

When unadf extracts .adf file, it creates directory paths by executing
mkdir via system(), but does not sanitize pathname strings in any
way. If the user can be tricked to extract specially crafted .adf
file, the attacker can execute arbitrary code with privileges of the
user.

As a proof of concept, I have crafted a file which executes 'ls' when
unpacked by vulnerable unadf: http://tmp.tjjr.fi/boom.adf

Action log:

  $ unadf boom.adf
  unADF v1.0 : a unzip like for .ADF files, powered by ADFlib (v0.7.11a - 
January 20th, 2007)

  Device : Floppy DD. Cylinders = 80, Heads = 2, Sectors = 11. Volumes = 1
  Volume : Floppy 880 KBytes, "Work" between sectors [0-1759]. OFS . Filled at 
0.3%.

  x - somedir;ls/
  adflib.dswAUTHORS.txt  boom.adf  CHANGES.txt  debian  Docs
dynunadf.dsp  FilesToInstall  Lib   README.txt  somedir
staticunadf.dsp
  adfwrapper.h  Bin  Boot  COPYING.txt  Demodynlib.dsp  Faq 
  gen_spec.sh Makefile  snip.c  staticlib.dsp


--
Tuomas

Bug#838050: Patched upstream

[Andrew Chadwick]

Apologies for the big messy merge.

Upstream now have a patch for this, currently pending review, which
applies cleanly to Debian mutter 3.21.92-1 and fixes the knock-on
problems in gnome-shell etc.

https://bugzilla.gnome.org/show_bug.cgi?id=771628
https://bugzilla.gnome.org/attachment.cgi?id=335863=diff

With my patched local build, all the hardware I've tested now works
and doesn't crash gnome-shell in wayland or xorg.

-- 
Andrew Chadwick

Bug#837960: spdylay: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

control: tags -1 fixed-upstream

On 2016-09-17 22:01:25 [+0900], Tatsuhiro Tsujikawa wrote:
> > ​Thank you for the patch.  It has been applied and merged into master
> > branch.
> > I've made another couple of commits​ to fix OpenSSL 1.1.0 deprecation
> > warnings.

That would be
https://github.com/tatsuhiro-t/spdylay/commit/83ab19e842531df45b3f4a06d8ec9ac15c82a177
https://github.com/tatsuhiro-t/spdylay/commit/52e07b266823fa5efa37201ba22ca8e9c52fc406
https://github.com/tatsuhiro-t/spdylay/commit/1ddd0d310f3f9c7b108ed0e555666be49e5c46e5
https://github.com/tatsuhiro-t/spdylay/commit/651e4fd3081a1240199eb86b9132fa13d8691804

> > spdylay end-to-end test (which failed above) require libevent which is
> > also built with OpenSSL 1.1.0.  But it seems the latest stable libevent
> > does not compile OpenSSL 1.1.0.  I guess that the above error "wrong
> > version number" could mean that libevent has been built with older OpenSSL
> > version.
> >
> >
> ​I was wrong.  end_to_end.py does not require libevent, and after upgrading
> key pair, all tests passed.

libevent is somewehre on the list, too. Thanks for taking care of it so
quickly!

> Best regards,
> Tatsuhiro Tsujikawa​

Sebastian

Bug#838316: RM: gcc-4.9 -- RoQA; obsolete GCC version

[Mattia Rizzolo]

package: ftp.debian.org
x-debbugs-cc: gcc-...@packages.debian.org

The switch to gcc-5 happened more than one year ago, and I just managed
to move over the last user of gcc-4.9.
Moreover the default already switched again to gcc-6.

Please remove this obsolete version.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#837588: hppa: Please disable CONFIG_FTRACE for hppa architecture

[Ben Hutchings]

On Mon, 2016-09-19 at 20:50 +0200, Helge Deller wrote:
> Hi Ben,
> 
> On 19.09.2016 19:41, Ben Hutchings wrote:
> > 
> > On Mon, 2016-09-12 at 20:28 +0100, Ben Hutchings wrote:
> > > 
> > > On Mon, 2016-09-12 at 18:17 +0200, Helge Deller wrote:
> > > > 
> > > > So, can you please deactivate CONFIG_FTRACE completely for 32- and
> > > > 64bit hppa configs?
> > > > Is it sufficient to add "CONFIG_FTRACE=n" to
> > > > debian/config/hppa/config ?
> > > 
> > > Done.
> > 
> > But this changes the module ABI, resulting in FTBFS.  From what you've
> > said on this bug, I'm not sure whether the previous version (4.7.2-1)
> > was at all usable. 
> 
> I was able to boot the 4.7.2-1 kernel on one of my machines where /boot was 
> big enough.
> The hppa buildd servers have smaller /boot partitions though  nd the kernel 
> was not useable/installable there.
> 
> > 
> > If not then I will delete the ABI reference for
> > hppa so the change is ignored.
> 
> I'd propose to delete the ABI reference.
> I'm not aware of any hppa-relevant out-of-tree kernel modules either.

OK.

Ben.

-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
A fail-safe circuit will destroy
others.


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

Bug#838315: RM: gnat-4.9 -- RoQA; superseded by gnat-6

[Mattia Rizzolo]

package: ftp.debian.org
X-debbugs-CC: gnat-...@packages.debian.org, debian-...@lists.debian.org

Now all packages migrated to gnat-6, so no rdeps of gnat-4.9 are left.
We have no need of more than one gnat version in the archive, so please
remove it.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#837588: hppa: Please disable CONFIG_FTRACE for hppa architecture

[Helge Deller]

Hi Ben,

On 19.09.2016 19:41, Ben Hutchings wrote:
> On Mon, 2016-09-12 at 20:28 +0100, Ben Hutchings wrote:
>> On Mon, 2016-09-12 at 18:17 +0200, Helge Deller wrote:
>>> So, can you please deactivate CONFIG_FTRACE completely for 32- and
>>> 64bit hppa configs?
>>> Is it sufficient to add "CONFIG_FTRACE=n" to
>>> debian/config/hppa/config ?
>>
>> Done.
> 
> But this changes the module ABI, resulting in FTBFS.  From what you've
> said on this bug, I'm not sure whether the previous version (4.7.2-1)
> was at all usable. 

I was able to boot the 4.7.2-1 kernel on one of my machines where /boot was big 
enough.
The hppa buildd servers have smaller /boot partitions though  nd the kernel was 
not useable/installable there.

> If not then I will delete the ABI reference for
> hppa so the change is ignored.

I'd propose to delete the ABI reference.
I'm not aware of any hppa-relevant out-of-tree kernel modules either.

Helge



signature.asc
Description: OpenPGP digital signature

Bug#484886: RE #484886 - gnome-system-monitor: counts PPPoE traffic twice

[Pedro Beja]

Hi Alexander,

I know this is an old bug but could you please still reproduce this issue
nowadays ?

try with newer versions of gnome-system-monitor like 3.14.1-1 or 3.21.92-1
...

thanks
regards
Pedro Beja

Bug#838311: Pending fixes for bugs in the libdist-zilla-plugin-templatefiles-perl package

[pkg-perl-maintainers]

tag 838311 + pending
thanks

Some bugs in the libdist-zilla-plugin-templatefiles-perl package are
closed in revision 2173408dc774d5ba61276bc231d523dc3dcf3804 in branch
'master' by Joenio Costa

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libdist-zilla-plugin-templatefiles-perl.git/commit/?id=2173408

Commit message:

Closes: #838311

Bug#836156: improper handling of source+binary changes triggering binary builds

[Stephan Sürken]

Hi Sam,

On Di, 2016-09-06 at 08:27 -0400, Sam Hartman wrote:

(...)

> I don't know.  We normally do source only uploads.
> Actually, it may be arch all handling.  The package in question only
> produced an arch all binary.
> So, the most direct thing to test would be a binary+source upload of
> a
> package producing only an arch all deb.

sorry for the delay. I did debug this today, and I can reproduce it.

What I think is happening:

* Binary+source upload is happening.
* Build requests are uploaded to the builders (including debs).
* sbuild is triggered.

Now, sbuild (newly?) fails to overwrite (existing) debs in the builddir
for some reason (and will also state so in the build log via an error
log), but otherwise happily continues as "successful" build.

mini-buildd now (also very happy) mixes the new changes with the old
(not overwritten) deb in the build result.

The first thing were this crashes is when trying to install the binary
via the wrong changes file into the repository via reprepro. This
usually leads to only the source package being installed, and
misleading errors.

It's maybe noteworthy that reproducible builds (i.e., current builds
for sid) often masquerade this bug as the resulting debs may actually
be identical ;).

I am now going towards not adding any *.deb-Files to the build requests
in the first place, which (is some improvement in its own) and should
fix the issue, no matter how sbuild actually behaves.

So this should hopefully be fixed with the next upload.

Thx for spotting this!

S

Bug#838314: ITP: soapyremote -- access SoapySDR devices over the network

[Andreas Bombe]

Package: wnpp
Severity: wishlist
Owner: Andreas Bombe 

* Package name: soapyremote
  Version : 0.3.1
  Upstream Author : Josh Blum 
* URL : https://github.com/pothosware/SoapyRemote/wiki
* License : Boost Software License 1.0
  Programming Lang: C++
  Description : Access SoapySDR devices over the network

The SoapyRemote project provides both a server and a client module that
allow you to use a SoapySDR supported SDR device on a remote machine
just like a local device.


This will be maintained in the hamradio team.

Bug#838313: ITP: soapyuhd -- UHD plugins for SoapySDR

[Andreas Bombe]

Package: wnpp
Severity: wishlist
Owner: Andreas Bombe 

* Package name: soapyuhd
  Version : 0.3.1
  Upstream Author : Josh Blum 
* URL : https://github.com/pothosware/SoapyUHD/wiki
* License : GPL-3
  Programming Lang: C++
  Description : UHD plugins for SoapySDR

The Soapy UHD project provides a SoapySDR module to use devices supported by
the Universal Hardware Driver by Ettus Research within the SoapySDR API and
software that supports SoapySDR. In addition, the project provides a UHD module
to use any SoapySDR device within the UHD API and UHD supported software.


This will be maintained in the hamradio team.

Bug#838312: ifupdown: Missing required variable: vlan_id1

[Sven Joachim]

Package: ifupdown
Version: 0.8.14

Running "ifdown " prints the warning "Missing required
variable: vlan_id1" at the end, which is apparently coming from ifdown
itself (see execute.c in the source code).

Downgrading ifupdown to 0.8.13 fixes this.


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

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

Versions of packages ifupdown depends on:
ii  adduser  3.115
ii  init-system-helpers  1.44
ii  iproute2 4.6.0-4
ii  libc62.24-3
ii  lsb-base 9.20160629

Versions of packages ifupdown recommends:
ii  isc-dhcp-client [dhcp-client]  4.3.5~b1-1

Versions of packages ifupdown suggests:
pn  ppp 
pn  rdnssd  

-- no debconf information

Bug#814248: more work done

[Markus Koschany]

Control: tags -1 pending

On Sun, 11 Sep 2016 16:02:16 +1000 Russell Coker 
wrote:
> I've fixed a number of problems with building 3.2.1, I've attached an archive 
> of the debian/ directory for anyone who wants to build on my work.
> 
> g++ -g -Wno-enum-compare -Wall -Wextra -Wno-unused-parameter 
> -Wno-sign-compare 
> -Wcast-align -Wwrite-strings -Wpointer-arith -Wno-format-security -g -O2 -
> fdebug-prefix-map=/home/rjc/src/wz/warzone2100-3.2.1=. -fPIE -fstack-
> protector-strong -Wformat -Werror=format-security -fPIC -std=c++11 -fstack-
> protector  -lz -rdynamic -fPIE -pie -Wl,-z,relro -Wl,-z,now -fPIC -o maptest 
> mapload.o maptest.o -lphysfs -lpng16 
> mapload.o:(.qtversion[qt_version_tag]+0x0): undefined reference to 
> `qt_version_tag'
> collect2: error: ld returned 1 exit status
> Makefile:407: recipe for target 'maptest' failed
> make: *** [maptest] Error 1
> rjc@athena:~/src/wz/warzone2100-3.2.1/tests$
> 
> I'm currently stuck on the above error.  If anyone could help I'd appreciate 
> it.
> 

I have disabled the test suite to work around this issue. It probably
needs another CMake patch to fix this.

There were still some other issues like a missing build-dependency on
libssl-dev or a missing appdata file but the game builds now. I'm
currently reviewing the debdiff and I think I will do a new release soon.

Thanks for working on warzone2100.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#838310: keyboard-configuration: user configuration lost + error message from setupcon

[Vincent Lefevre]

Same problem on another machine.

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

Bug#838311: ITP: libdist-zilla-plugin-templatefiles-perl -- plugin that enables the use of templates in a Dist::Zilla distribution

[Joenio Costa]

Package: wnpp
Severity: wishlist
Owner: Joenio Costa 

* Package name: libdist-zilla-plugin-templatefiles-perl
  Version : 0.03
  Upstream Author : Jonathan Scott Duff 
* URL : 
https://metacpan.org/release/Dist-Zilla-Plugin-TemplateFiles

* License : Perl
  Programming Lang: Perl
  Description : plugin that enables the use of templates in a 
Dist::Zilla distribution


Dist::Zilla::Plugin::TemplateFiles is a Dist::Zilla plugin that utilize
Text::Template to turn certain files into templates.

Bug#837588: hppa: Please disable CONFIG_FTRACE for hppa architecture

[Ben Hutchings]

On Mon, 2016-09-12 at 20:28 +0100, Ben Hutchings wrote:
> Control: tag -1 pending
> 
> On Mon, 2016-09-12 at 18:17 +0200, Helge Deller wrote:
> [...]
> > 
> > So, can you please deactivate CONFIG_FTRACE completely for 32- and
> > 64bit hppa configs?
> > Is it sufficient to add "CONFIG_FTRACE=n" to
> > debian/config/hppa/config ?
> 
> Done.

But this changes the module ABI, resulting in FTBFS.  From what you've
said on this bug, I'm not sure whether the previous version (4.7.2-1)
was at all usable.  If not then I will delete the ABI reference for
hppa so the change is ignored.

Ben.

-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
A fail-safe circuit will destroy
others.


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

Bug#838310: keyboard-configuration: user configuration lost + error message from setupcon

[Vincent Lefevre]

Some additional information. In "journalctl -b" output after reboot:

[...]
Sep 19 19:10:11 zira keyboard-setup.sh[401]: cannot open file /tmp/tmpkbd.qR4ecU
[...]
Sep 19 19:10:11 zira keyboard-setup.sh[401]: setupcon: The keyboard model is 
unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
[...]
Sep 19 19:10:11 zira console-setup.sh[631]: setupcon: The keyboard model is 
unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
[...]
Sep 19 19:10:11 zira console-setup.sh[631]: setupcon: The keyboard model is 
unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
Sep 19 19:10:11 zira console-setup.sh[631]: setupcon: The keyboard model is 
unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
Sep 19 19:10:11 zira console-setup.sh[631]: setupcon: The keyboard model is 
unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
[...]

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

Bug#838310: keyboard-configuration: user configuration lost + error message from setupcon

[Vincent Lefevre]

Package: keyboard-configuration
Version: 1.149
Severity: grave
Justification: causes non-serious data loss

Just after the upgrade of keyboard-configuration from 1.148 to 1.149,
I could see that my previous configuration was lost. More precisely,
config.dat changed in the following way:

Index: config.dat
===
--- config.dat  (revision 92179)
+++ config.dat  (revision 92180)
@@ -512,7 +512,7 @@
 
 Name: keyboard-configuration/modelcode
 Template: keyboard-configuration/modelcode
-Value: pc105
+Value: 
 Owners: d-i, keyboard-configuration
 Flags: seen
 
@@ -549,6 +549,9 @@
 Template: keyboard-configuration/unsupported_config_layout
 Value: true
 Owners: d-i, keyboard-configuration
+Variables:
+ XKBLAYOUT = gb
+ XKBVARIANT = 
 
 Name: keyboard-configuration/unsupported_config_options
 Template: keyboard-configuration/unsupported_config_options
@@ -581,7 +584,7 @@
 
 Name: keyboard-configuration/xkb-keymap
 Template: keyboard-configuration/xkb-keymap
-Value: gb
+Value: us
 Owners: d-i, keyboard-configuration
 Flags: seen
 

and /etc/default/keyboard changed in the following way:

Index: etc/default/keyboard
===
--- etc/default/keyboard(revision 92179)
+++ etc/default/keyboard(revision 92180)
@@ -2,7 +2,7 @@
 
 # Consult the keyboard(5) manual page.
 
-XKBMODEL="pc105"
+XKBMODEL=""
 XKBLAYOUT="gb"
 XKBVARIANT=""
 XKBOPTIONS=""

I don't know the possible consequences, though. The
/usr/share/doc/keyboard-configuration/changelog.gz file just says:

console-setup (1.149) unstable; urgency=medium

  [ Updated translations ]
  * Danish (da.po) by Joe Hansen

 -- Christian Perrier   Sun, 18 Sep 2016 17:53:38 +0200

Moreover, I can see in the /var/log/apt/term.log file after an
upgrade of the Linux kernel and the nvidia packages:

[...]
Processing triggers for libc-bin (2.24-3) ...
Processing triggers for glx-alternative-nvidia (0.7.3) ...
Processing triggers for update-glx (0.7.3) ...
Processing triggers for glx-alternative-nvidia (0.7.3) ...
Processing triggers for libc-bin (2.24-3) ...
Processing triggers for initramfs-tools (0.125) ...
update-initramfs: Generating /boot/initrd.img-4.7.0-1-amd64
setupcon: The keyboard model is unknown, assuming 'pc105'. Keyboard may be 
configured incorrectly.
Log ended: 2016-09-19  19:08:59

Note: I have

-rw-r--r-- 1 root root 145 2016-09-19 19:03:19 /etc/default/keyboard

Thus this file was modified when keyboard-configuration was upgraded
(and before this upgrade of the Linux kernel and the nvidia packages).
This error message is just a consequence of this bug.

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

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

Versions of packages keyboard-configuration depends on:
ii  debconf 1.5.59
ii  liblocale-gettext-perl  1.07-3

keyboard-configuration recommends no packages.

keyboard-configuration suggests no packages.

Versions of packages console-setup depends on:
ii  console-setup-linux  1.149
ii  debconf  1.5.59
ii  xkb-data 2.17-1

Versions of packages console-setup suggests:
ii  locales   2.24-3
ii  lsb-base  9.20160629

Versions of packages console-setup-linux depends on:
ii  init-system-helpers  1.44
ii  initscripts  2.88dsf-59.8
ii  kbd  2.0.3-2

Versions of packages console-setup-linux suggests:
ii  console-setup  1.149

Versions of packages keyboard-configuration is related to:
pn  console-common
pn  console-data  
pn  console-tools 
pn  gnome-control-center  
ii  kbd   2.0.3-2
ii  systemd   231-6

-- debconf information:
* keyboard-configuration/optionscode:
* keyboard-configuration/altgr: The default for the keyboard layout
  console-setup/fontface47: Fixed
  keyboard-configuration/unsupported_layout: true
  console-setup/framebuffer_only:
* keyboard-configuration/model: Generic 105-key (Intl) PC
  console-setup/fontsize: 8x16
  console-setup/guess_font:
* keyboard-configuration/store_defaults_in_debconf_db: true
  debian-installer/console-setup-udeb/title:
  console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages
  keyboard-configuration/ctrl_alt_bksp: false
  keyboard-configuration/unsupported_config_options: true
  console-setup/use_system_font:
* keyboard-configuration/toggle: No toggling
* keyboard-configuration/layoutcode: gb
  keyboard-configuration/unsupported_options: true
* keyboard-configuration/variantcode:
* keyboard-configuration/variant: English (UK)
* keyboard-configuration/switch: 

Bug#833770: [Debichem-devel] Bug#833770: Bug#833770: avogadro: FTBFS with gcc6/boost1.61

[Anton Gladky]

One need to discuss it with Michael.

Anton


2016-09-19 19:11 GMT+02:00 Graham Inggs :
> What about uploading version 1.1.1 from experimental to unstable?

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

[Niels Thykier]

On Sat, 17 Sep 2016 22:36:20 +0200 Hilmar Preusse  wrote:
> On 05.09.16 Matthias Klose (d...@debian.org) wrote:
> 
> Hi Matthias,
> 
> > [...]
> Is it OK to simply remove that check? Is there an replacement for
> hardening-check?
> 
> Thanks,
>   Hilmar
> 
> [1] 
> https://wiki.debian.org/HardeningWalkthrough#rules_files_based_on_standard_debhelper_or_hand-written_rules_files
> -- 
> sigfault

Hi Hilmar :)

I believe you can just remove that check.

As for a replacement, lintian will still implement the hardening-no-*
tags, which were based on the code from hardening-check.

Thanks,
~Niels

Bug#787549: Agreed!

[Barak A. Pearlmutter]

Agreed, I think this longer and more informative description is an
excellent idea. This should be rectified:

$ apt-cache search 'integrated development' | wc -l

102

$ apt-cache search 'integrated development' | egrep -i emacs | wc -l

0

Bug#833770: [Debichem-devel] Bug#833770: Bug#833770: avogadro: FTBFS with gcc6/boost1.61

[Graham Inggs]

On 19 September 2016 at 19:04, Anton Gladky  wrote:
> I really tried, but did not succeed. One need another try.

What about uploading version 1.1.1 from experimental to unstable?

Bug#832840: license-reconcile: diff for NMU version 0.12+nmu1

[gregor herrmann]

On Mon, 19 Sep 2016 00:32:17 +0800, gustavo panizzo (gfa) wrote:

> I've attached the debdiff, I'll push my changes to the git repo after
> the NMU has been uploaded, let me know if you don't agree with any of
> this.

Thanks for your help.

It might be easier to push the changes to the git repo before an
upload, with 0.12 instead of 0.12+nmu1, and we can do a regular tram
upload. -- Whatever you prefer.
 

Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#838309: gambas3: Please package gambas 3.9.0. before stretch release

[shirish शिरीष]

Package: gambas3
Version: 3.8.4-6
Severity: wishlist

Dear Maintainer,
It would be nice if we can get gambas 3.9.0 before stretch release.


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

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

Versions of packages gambas3 depends on:
ii  gambas3-gb-args 3.8.4-6
ii  gambas3-gb-cairo3.8.4-6+b1
ii  gambas3-gb-chart3.8.4-6
ii  gambas3-gb-clipper  3.8.4-6+b1
ii  gambas3-gb-complex  3.8.4-6+b1
ii  gambas3-gb-compress-bzlib2  3.8.4-6+b1
ii  gambas3-gb-compress-zlib3.8.4-6+b1
ii  gambas3-gb-crypt3.8.4-6+b1
ii  gambas3-gb-data 3.8.4-6+b1
ii  gambas3-gb-db-form  3.8.4-6
ii  gambas3-gb-db-mysql 3.8.4-6+b1
ii  gambas3-gb-db-odbc  3.8.4-6+b1
ii  gambas3-gb-db-postgresql3.8.4-6+b1
ii  gambas3-gb-db-sqlite3   3.8.4-6+b1
ii  gambas3-gb-dbus 3.8.4-6+b1
ii  gambas3-gb-desktop  3.8.4-6+b1
ii  gambas3-gb-desktop-gnome3.8.4-6
ii  gambas3-gb-desktop-x11  3.8.4-6+b1
ii  gambas3-gb-form-dialog  3.8.4-6
ii  gambas3-gb-form-mdi 3.8.4-6
ii  gambas3-gb-form-stock   3.8.4-6
ii  gambas3-gb-gmp  3.8.4-6+b1
ii  gambas3-gb-gsl  3.8.4-6+b1
ii  gambas3-gb-gui-opengl   3.8.4-6+b1
ii  gambas3-gb-gui-qt   3.8.4-6+b1
ii  gambas3-gb-gui-qt-webkit3.8.4-6+b1
ii  gambas3-gb-httpd3.8.4-6+b1
ii  gambas3-gb-image-effect 3.8.4-6+b1
ii  gambas3-gb-image-imlib  3.8.4-6+b1
ii  gambas3-gb-image-io 3.8.4-6+b1
ii  gambas3-gb-inotify  3.8.4-6+b1
ii  gambas3-gb-libxml   3.8.4-6+b1
ii  gambas3-gb-logging  3.8.4-6
ii  gambas3-gb-map  3.8.4-6
ii  gambas3-gb-markdown 3.8.4-6+b1
ii  gambas3-gb-media3.8.4-6+b1
ii  gambas3-gb-memcached3.8.4-6
ii  gambas3-gb-mime 3.8.4-6+b1
ii  gambas3-gb-mysql3.8.4-6+b1
ii  gambas3-gb-ncurses  3.8.4-6+b1
ii  gambas3-gb-net-curl 3.8.4-6+b1
ii  gambas3-gb-net-pop3 3.8.4-6+b1
ii  gambas3-gb-net-smtp 3.8.4-6+b1
ii  gambas3-gb-openal   3.8.4-6+b1
ii  gambas3-gb-opengl-glsl  3.8.4-6+b1
ii  gambas3-gb-opengl-glu   3.8.4-6+b1
ii  gambas3-gb-opengl-sge   3.8.4-6+b1
ii  gambas3-gb-openssl  3.8.4-6+b1
ii  gambas3-gb-option   3.8.4-6+b1
ii  gambas3-gb-pcre 3.8.4-6+b1
ii  gambas3-gb-pdf  3.8.4-6+b1
ii  gambas3-gb-qt5  3.8.4-6+b1
ii  gambas3-gb-qt5-webkit   3.8.4-6+b1
ii  gambas3-gb-report   3.8.4-6
ii  gambas3-gb-report2  3.8.4-6
ii  gambas3-gb-scanner  3.8.4-6+b1
ii  gambas3-gb-sdl-sound3.8.4-6+b1
ii  gambas3-gb-sdl2 3.8.4-6+b1
ii  gambas3-gb-sdl2-audio   3.8.4-6+b1
ii  gambas3-gb-settings 3.8.4-6
ii  gambas3-gb-util 3.8.4-6+b1
ii  gambas3-gb-util-web 3.8.4-6+b1
ii  gambas3-gb-v4l  3.8.4-6+b1
ii  gambas3-gb-vb   3.8.4-6+b1
ii  gambas3-gb-web  3.8.4-6
ii  gambas3-gb-xml-html 3.8.4-6+b1
ii  gambas3-gb-xml-rpc  3.8.4-6
ii  gambas3-gb-xml-xslt 3.8.4-6+b1
ii  gambas3-ide 3.8.4-6
ii  gambas3-templates   3.8.4-6+b1

gambas3 recommends no packages.

gambas3 suggests no packages.

-- no debconf information


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#833770: [Debichem-devel] Bug#833770: avogadro: FTBFS with gcc6/boost1.61

[Anton Gladky]

Hi Emilio,

I really tried, but did not succeed. One need another try.

Regards

Anton


2016-09-19 17:09 GMT+02:00 Emilio Pozuelo Monfort :
> Ping? This is blocking the boost1.58 removal, which in turn is blocking the
> openmpi transition. I'd appreciate it if you could take a look at this.

Bug#838308: Please make gir1.2-flatpak-1.0 multiarch aware

[Michael Biebl]

Source: flatpak
Version: 0.6.10-1
Severity: normal

Hi,

gobject-introspection supports multiarch paths nowadays, so you no
longer need to move the file back to non-multiarch paths in
debian/gir1.2-flatpak-1.0.install.
It should then also be possible to use
Multi-Arch: same for gir1.2-flatpak-1.0.

Please also consider making libflatpak-dev depend on gir1.2-flatpak-1.0
(= ${binary:Version}) as per our g-i mini-policy, see
/usr/share/doc/gobject-introspection/policy.txt

Regards,
Michael


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

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

Bug#838307: qa.debian.org: reports wrong package version in testing

[franck]

Package: qa.debian.org
Severity: important

Dear Maintainer,

Testing currently contains linux 4.6.4-1
But tracker reports 4.7.2-1

https://packages.qa.debian.org/l/linux.html
   testing   4.7.2-1 
   unstable  4.7.4-1 

This may mislead package maintainers into believing package in testing is 
recent when, in reality, testing contains a much older version (with more 
security issues).

Note: New package tracker correctly reports linux version:
https://tracker.debian.org/pkg/linux
testing: 4.6.4-1
   unstable: 4.7.4-1

BR, Franck

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

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

Bug#837885: debian-installer: Installer does not check disk size prior to installation

[Steve McIntyre]

On Thu, Sep 15, 2016 at 03:11:51AM -0400, nils wrote:
>Package: debian-installer
>Version: Stretch Alpha 7
>Severity: important
>Tags: d-i
>
>Dear Maintainer,
>
>- Installing stretch alpha 7 in virtualbox
>- set up an 8gb disk, with full disk partitioning, separate home partition
>- got partitions of 2 (home), 4 (swap) and 2 (home) GB
>- installer failed with a generic error message "A step falied..." when the 
>target disk was full
>- redid it with no separate home partiton, and the installation needs 3,5GB
>
>The installer should check for required disk space before
>installation (or at least once before downloading, and then again
>before isntalling) to check that he disk is big enough. Also, the
>error message should be a little less generic as novices will not
>understand what's wrong.

It's a difficult thing to solve reliably - when you're partitioning,
d-i has very little idea of what tasks/packages you're going to be
installing later.

Another wrinkle is that we don't have reliable data to know how much
space a set of packages will take to install later, which is
(admittedly) not very good. I've spoken to people about that before;
I'll prod again...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"I can't ever sleep on planes ... call it irrational if you like, but I'm
 afraid I'll miss my stop" -- Vivek Das Mohapatra

Bug#838155: issue still exists even with the new mate-themes 3.22.2-1 installed

[shirish शिरीष]

Package: caja
Version: 1.14.2-1
Severity: normal

Dear Maintainer,
I get the following and caja does not come up. GDB doesn't help much
in this situation -

┌─[shirish@debian] - [~] - [10019]
└─[$] caja

(caja:10110): Gtk-WARNING **: Theme parsing error: gtk.css:63:28: The
:prelight pseudo-class is deprecated. Use :hover instead.

(caja:10110): Gtk-WARNING **: Theme parsing error: gtk.css:73:35: The
:prelight pseudo-class is deprecated. Use :hover instead.

>From this, it seems it still needs some fixes for

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

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

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

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

Versions of packages caja suggests:
ii  engrampa1.14.1-1
ii  gstreamer1.0-tools  1.8.3-1
ii  meld3.16.2-1

-- no debconf information



-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#838243: libarchive12: ldconfig warns that libarchive.so.12 is not a symbolic link

[Jonas Meurer]

Hello Bruce,

Am 19.09.2016 um 14:47 schrieb Bruce Toll:
> I reported a bug with the recent (Sept. 10) libarchive12 security update
> (Debian BTS 838243) and heard back from Andreas Henriksson that I should
> reach out to the package uploader and Debian LTS team directly.
> 
> I appreciate the great work that you and the LTS team are doing to keep
> wheezy secure. The issue seems fairly minor and is described in the bug
> tracker, https://bugs.debian.org/838243. Thanks!

Thanks for your bugreport. Indeed, it looks like, something went wrong
with the build of libarchive12 3.0.4-3+wheezy3 on amd64. For the other
supported archs, everything seems fine.

I suspect that this is due to me building the amd64 binaries inside a
virtualbox VM with the build directory mounted as vboxsf share mount.
Apparently, symlinks get screwed up up on vboxsf mounts.

Another LTS update of libarchive is underway anyway, Emilio Pozuelo
Monfort is working on it. I suggest to wait until his upload, which will
fix the bug (except if he builds on a vboxsf share as well) :)

Cheers,
 jonas




signature.asc
Description: OpenPGP digital signature

Bug#838304: Pending fixes for bugs in the libdist-zilla-plugin-bugtracker-perl package

[pkg-perl-maintainers]

tag 838304 + pending
thanks

Some bugs in the libdist-zilla-plugin-bugtracker-perl package are
closed in revision 8e4382e048ce3c8110651282eae6fec7e6bd8880 in branch
'master' by Joenio Costa

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libdist-zilla-plugin-bugtracker-perl.git/commit/?id=8e4382e

Commit message:

Closes: #838304