Bug#888183: libc6: Breaks openvz virtuals again

[Aurelien Jarno]

On 2018-01-23 19:56, James Cloos wrote:
> AJ> Do you have a list of other packages from the glibc src that are
> AJ> upgraded before?
> 
> The following packages have unmet dependencies:
>  libc-dev-bin : Depends: libc6 (> 2.26) but 2.25-6 is installed
>  libc6-dev : Depends: libc6 (= 2.26-4) but 2.25-6 is installed
>  libc6-i386 : Depends: libc6 (= 2.26-4) but 2.25-6 is installed
>  libc6-pic : Depends: libc6 (= 2.26-4) but 2.25-6 is installed
>  libc6-x32 : Depends: libc6 (= 2.26-4) but 2.25-6 is installed
>  locales : Depends: libc-bin (> 2.26) but 2.25-6 is installed
>  nscd : Depends: libc6 (> 2.26) but 2.25-6 is installed
> 
> And on another box:
> 
> The following packages have unmet dependencies:
>  libc-dev-bin : Depends: libc6 (> 2.26) but 2.25-6 is installed
>  libc6-dev : Depends: libc6 (= 2.26-2) but 2.25-6 is installed
>  libnih1 : Depends: libc6 (> 2.26) but 2.25-6 is installed
>  locales : Depends: libc-bin (> 2.26)
> 
> And a third:
> 
> The following packages have unmet dependencies:
>  libc-dev-bin : Depends: libc6 (> 2.26) but 2.25-6 is installed
>  libc6-dev : Depends: libc6 (= 2.26-4) but 2.25-6 is installed
>  locales : Depends: libc-bin (> 2.26) but 2.25-6 is installed
> 
> Those are after one previous attempt at --fix-broken.

All the above packages have a proper dependency on libc6 >= 2.26. It's
apt which decide they can already be unpacked before libc6 preinst is
ran.

> AJ> In any case it's not something we can control, the abort is done
> AJ> inside the libc6 preinst, there is no way the libc6 package can
> AJ> do that earlier.
> 
> Of course it is.  Just make every deb from the glibc src do that abort.

No, that simply doesn't scale. Other packages than the one in src:glibc
depends on libc6 >= 2.26, and more and more are going to pick up this
dependency in the next months. They might also be unpacked before libc6
preinst is ran. We can't add this check in every package.

Aurelien

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

Bug#870460: anyone working on npm?

[Pirate Praveen]

On Tue, 23 Jan 2018 23:14:32 -0800 Diane Trout  wrote:
> Hello,
> 
> I was looking to update zotero, which needs a newer npm.
> 
> I was curious, so I tried building a npm using upstream's 5.6.0, and I
> have something that almost installs & runs.

Great!

> Several dependencies are out of date in Debian, and there's still a
> fair number of node_modules that don't seem to have a corresponding
> Debian package.
> 
> Would it be worth sharing these changes? How would you prefer to
> receive / review them? There's a few issues I avoided that need some
> discussion. (Like they embed a copy of node-gyp, and several scripts
> hard code relative paths to that copy)

We should package the remaining modules (we have to package about 38
more modules https://pad.disroot.org/p/npm-list ). You can just file
ITPs of missing modules and package them.

We keep this https://wiki.debian.org/Javascript/Nodejs/Tasks/npm
refreshed often.

Also we should try to replace embedded copies with packaged versions.

> I wanted to get in touch with people in the javascript team before
> slogging through updating the copyright file.

Welcome to the team!

We can take a bit of shortcut if the module is too small and unlikely to
be required by other tools by embedding it.
https://salsa.debian.org/js-team/node-react/tree/master/debian/node_modules/ncp

We can always unbundle them if more packages starts depending on them
(like we did with node-asap).



signature.asc
Description: OpenPGP digital signature

Bug#888243: Lack of /opt in base-files causes piuparts issues for in-house packages

[chrysn]

Package: base-files
Version: 10.1
Severity: normal

When a package gets installed and later uninstalled that places files in
/opt (or /etc/opt), that directory gets removed because it was only used
by that package and not owned by any. As a consequence, in-house
packages (which can reasonably install to /opt/) can not pass piuparts
as that complains about /opt and /etc/opt going away.

Now this could be fixed at several places (eg. dpkg could keep them
around, or piupats could mask them), but keeping such directories around
is typically done by base-files. The reason given in the FAQ for /opt
just being added in postinst is that it should be possible for an admin
to rmdir those -- a valid point, but causing inconvenience to packages
going there.

The fix I'd suggest is to have a base-files-fhs package recommended by
base-files but not required, which can be uninstalled if an admin wants
those files gone.


Thanks for your consideration
chrysn

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

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages base-files depends on:
ii  gawk [awk]  1:4.1.4+dfsg-1
ii  mawk [awk]  1.3.3-17+b3

base-files recommends no packages.

base-files suggests no packages.

-- no debconf information

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom


signature.asc
Description: PGP signature

Bug#879585: apparmor: Pin the AppArmor feature set in Stretch to Linux 4.9's

[intrigeri]

intrigeri:
> 1. ensure the blocking kernel bug is fixed:
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883703#32

That's now done in stretch-backports: linux-latest was updated and for
example linux-image-amd64 now pulls linux-image-4.14.0-0.bpo.3-amd64
(version 4.14.13-1~bpo9+1).

So the next steps are:

2. adjust the Stretch packaging branch so it uses the same
   implementation as testing/sid (#879585)

3. update the stretch-pu request (#882697)

Cheers,
-- 
intrigeri

Bug#870460: anyone working on npm?

[Ross Gammon]

Hi Diane,

https://wiki.debian.org/Javascript/Nodejs/Tasks/npm

As far as I know, people have been working on trying to get all the
missing packages packaged, and update the old ones. Unfortunately, I
have not had the time to help myself.

I am not sure if anyone else has tried building npm yet, but it is good
to know we are getting close.

I will let the other more active team members comment on how best to
incorporate your work.

Ross

On 01/24/2018 08:14 AM, Diane Trout wrote:
> Hello,
>
> I was looking to update zotero, which needs a newer npm.
>
> I was curious, so I tried building a npm using upstream's 5.6.0, and I
> have something that almost installs & runs.
>
> Several dependencies are out of date in Debian, and there's still a
> fair number of node_modules that don't seem to have a corresponding
> Debian package.
>
> Would it be worth sharing these changes? How would you prefer to
> receive / review them? There's a few issues I avoided that need some
> discussion. (Like they embed a copy of node-gyp, and several scripts
> hard code relative paths to that copy)
>
> I wanted to get in touch with people in the javascript team before
> slogging through updating the copyright file.
>
> Diane
> detrout on Debian IRC
> Debian Developer

Bug#888242: ieee-data: update-ieee-data should be moved to /usr/sbin

[Herwin Weststrate]

Package: ieee-data
Version: 20160613.1
Severity: minor

Dear Maintainer,

ieee-data includes a script /usr/bin/update-ieee-data to fetch new
versions of the data files. When running this script as a normal user,
the download succeeds but then it fails to move it to /var/lib. Since
this download takes a while, you don't notice the failure directly.

I think it would be clearer to install the update script in /usr/sbin
instead of /usr/bin.

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

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

Versions of packages ieee-data depends on:
ii  curl 7.52.1-5+deb9u3
ii  libwww-perl  6.15-1
ii  wget 1.18-5+deb9u1

ieee-data recommends no packages.

ieee-data suggests no packages.

-- no debconf information

Bug#888241: ieee-data: include the csv files

[Herwin Weststrate]

Package: ieee-data
Version: 20160613.1
Severity: wishlist

Dear Maintainer,

IEEE offers the data included in ieee-data in both text and csv format.
I guess most people prefer machine-readable data, so it would be great
if the csv-files could be included as well.

The locations of the csv files:

http://standards-oui.ieee.org/oui/oui.csv
http://standards-oui.ieee.org/oui28/mam.csv
http://standards-oui.ieee.org/oui36/oui36.csv
http://standards-oui.ieee.org/iab/iab.csv

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

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

Versions of packages ieee-data depends on:
ii  curl 7.52.1-5+deb9u3
ii  libwww-perl  6.15-1
ii  wget 1.18-5+deb9u1

ieee-data recommends no packages.

ieee-data suggests no packages.

-- no debconf information

Bug#870460: anyone working on npm?

[Diane Trout]

Hello,

I was looking to update zotero, which needs a newer npm.

I was curious, so I tried building a npm using upstream's 5.6.0, and I
have something that almost installs & runs.

Several dependencies are out of date in Debian, and there's still a
fair number of node_modules that don't seem to have a corresponding
Debian package.

Would it be worth sharing these changes? How would you prefer to
receive / review them? There's a few issues I avoided that need some
discussion. (Like they embed a copy of node-gyp, and several scripts
hard code relative paths to that copy)

I wanted to get in touch with people in the javascript team before
slogging through updating the copyright file.

Diane
detrout on Debian IRC
Debian Developer

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

Bug#888240: ftp.debian.org: Invalid Changelogs: URL in Release file

[Christoph Biedl]

Package: ftp.debian.org
Severity: normal

Hello,

the generated {,In}Release file contains a Changelogs: line, e.g.
from :

| Origin: Debian
| Label: Debian
| Suite: unstable
| Codename: sid
| Changelogs: 
http://metadata.ftp-master.debian.org/changelogs/@CHANGEPATH@_changelog
| Date: Wed, 24 Jan 2018 02:50:25 UTC

That URL appears to lack a substitution for @CHANGEPATH@ - also I cannot
find any file that reasonably should be describe by that line. Care to
check?

Aside: https support for metadata was nice to have.

Christoph



signature.asc
Description: Digital signature

Bug#814927: [Pkg-swan-devel] Bug#814927: strongSwan misses ChaCha/POLY support

[Stefan Tatschner]

On Sun, 23 Apr 2017 15:17:28 -0700 Gerald Turner  wrote:
> Control: tags -1 + patch
> 
> ---
>  debian/control | 1 +
>  debian/libstrongswan-extra-plugins.install | 3 +++
>  debian/rules   | 1 +
>  3 files changed, 5 insertions(+)

Gentle ping for this bug + patch. :)

Bug#876841: Depends on python3-mock

[Antonio Valentino]

Hi, sorry for the late reply.

AFAIK tables.test() is part of the public API.

$ env PYTHONPATH=. python -c "import tables; tables.test()"

is also mentioned somewhere in the docs.

Anyway, probably it is possible to use the mock module provided by the
standard lib.
Would it be an acceptable solution for you?


regards

-- 
Antonio Valentino

Bug#888020: Package conflict between primus and nvidia 384.111-3 drivers

[Andreas Beckmann]

On 2018-01-22 21:10, Andreas Beckmann wrote:
> I think we may have to update some documentation for this recent change
> (nvidia-driver.README.Debian),

Luca,

can you update the instructions to use the
nvidia-driver-libs{,-nonglvnd} metapackages? With tested commands :-)
I did a lot of tests installing, switching and upgrading in chroots
(with apt-get). More testing, especially if more package become
available in backports would be welcome.

Maybe also mention that primus/optimus users will need the nonglvnd variant.

Thanks


Andreas

Bug#888239: stretch-pu: package nvidia-graphics-drivers-legacy-340xx/340.106-1~deb9u1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Hi,

I'd like to update the 340xx legacy nvidia driver in stretch with a new
upstream version that brings spectre/meltdown mitigation fixes and
related kernel support. Security updates for the non-free drivers have
always been done via proposed-updates.

The package is a plain rebuild from sid with no further changes needed
and therefore contains also all the accumulated bugfixes from the
package in sid (and some of them are already in nvidia-graphics-drivers
in stretch, since we had a security update in the previous stretch point
release). The proposed package is now also available in
stretch-backports to allow further testing.

The changelog stanza in addition to the attached diff (debian/ tree only,
blobs excluded) will be

--- debian/changelog (revision 7831)
+++ debian/changelog (working copy)
@@ -1,3 +1,9 @@
+nvidia-graphics-drivers-legacy-340xx (340.106-1~deb9u1) stretch; urgency=medium
+
+  * Rebuild for stretch.
+
+ -- Andreas Beckmann   Wed, 24 Jan 2018 07:06:23 +0100
+
 nvidia-graphics-drivers-legacy-340xx (340.106-1) unstable; urgency=medium
 
   * New upstream legacy 340xx branch release 340.106 (2018-01-16).




Andreas
Index: debian/libgl1-nvidia-glx.prerm.in
===
--- debian/libgl1-nvidia-glx.prerm.in   (.../tags/340.102-1)(revision 7831)
+++ debian/libgl1-nvidia-glx.prerm.in   (.../trunk) (revision 7831)
@@ -1,13 +0,0 @@
-#!/bin/sh
-set -e
-
-
-if [ "$1" = "remove" ] || [ "$1" = "deconfigure" ]; then
-
-   update-alternatives --remove nvidia /usr/lib/#PRIVATE#
-   dpkg-trigger register-glx-alternative-nvidia
-
-fi
-
-
-#DEBHELPER#
Index: debian/nvidia-alternative.prerm.in
===
--- debian/nvidia-alternative.prerm.in  (.../tags/340.102-1)(revision 7831)
+++ debian/nvidia-alternative.prerm.in  (.../trunk) (revision 7831)
@@ -5,6 +5,7 @@
 if [ "$1" = "remove" ] || [ "$1" = "deconfigure" ]; then
 
update-alternatives --remove nvidia /usr/lib/#PRIVATE#
+   dpkg-trigger --no-await register-glx-alternative-nvidia
 
 fi
 
Index: debian/not-installed.in
===
--- debian/not-installed.in (.../tags/340.102-1)(revision 0)
+++ debian/not-installed.in (.../trunk) (revision 7831)
@@ -0,0 +1,37 @@
+.manifest
+LICENSE
+gl.h
+glext.h
+glx.h
+glxext.h
+libGL.la
+#!armhf#libnvidia-tls.so.#VERSION#
+libnvidia-wfb.so.#VERSION#
+libvdpau.so.#VERSION#
+libvdpau_trace.so.#VERSION#
+makeself-help-script.sh
+makeself.sh
+mkprecompiled
+nvidia-installer
+nvidia-installer.1
+nvidia-modprobe
+nvidia-modprobe.1
+nvidia-persistenced
+nvidia-persistenced-init.tar.bz2
+nvidia-persistenced.1
+nvidia-settings
+nvidia-settings.1
+nvidia-settings.desktop
+nvidia-settings.png
+nvidia-xconfig
+nvidia-xconfig.1
+pci.ids
+pkg-history.txt
+tls_test
+tls_test_dso.so
+
+libOpenCL.so.1.0.0
+nvidia.icd
+nvidia-cuda-mps-control
+nvidia-cuda-mps-control.1
+nvidia-cuda-mps-server
Index: debian/changelog
===
--- debian/changelog(.../tags/340.102-1)(revision 7831)
+++ debian/changelog(.../trunk) (revision 7831)
@@ -1,3 +1,113 @@
+nvidia-graphics-drivers-legacy-340xx (340.106-1) unstable; urgency=medium
+
+  * New upstream legacy 340xx branch release 340.106 (2018-01-16).
+ * Fixed CVE-2017-5753, CVE-2017-5715 (spectre), CVE-2017-5754 (meltdown).
+   https://nvidia.custhelp.com/app/answers/detail/a_id/4611
+   (Closes: #886852)
+* Improved compatibility with recent Linux kernels.
+
+  [ Luca Boccassi ]
+  * Drop nvidia-drm-pci-init.patch and timer.patch, fixed upstream.
+
+ -- Andreas Beckmann   Wed, 17 Jan 2018 20:50:05 +0100
+
+nvidia-graphics-drivers-legacy-340xx (340.104-4) unstable; urgency=medium
+
+  [ Andreas Beckmann ]
+  * Bump Standards-Version to 4.1.3. No changes needed.
+  * Stop shipping the classic libnvidia-tls.so.* and ship the modern one (for
+Linux 2.6 onwards) in the regular libdir instead of the tls/ subdir
+(384.111-1).  (Closes: #883615)
+  * Add #tls# substitution for the tls/ source directory (384.111-1).
+  * nvidia-legacy-340xx-alternative.prerm: Trigger register-glx-alternative-
+nvidia upon removal (384.111-3).  (Closes: #883637)
+  * libgl1-nvidia-legacy-340xx-glx.prerm: Do not forcibly remove the nvidia
+alternative, this would reset it from manual mode to auto mode while it
+could still be needed by other packages, e.g. libcuda1. Let the
+nvidia-legacy-340xx-alternative triggers handle it instead (384.111-3).
+
+  [ Luca Boccassi ]
+  * Add timer.patch to fix kernel module build on Linux 4.15 and newer.
+
+ -- Andreas Beckmann   Tue, 16 Jan 2018 03:08:52 +0100
+

Bug#888237: Fwd: Re: diffoscope and file renames

[Chris Lamb]

- Original message -
From: Marc MERLIN 
To: Chris Lamb 
Subject: Re: diffoscope and file renames
Date: Wed, 24 Jan 2018 17:27:47 +1100

On Wed, Jan 24, 2018 at 11:50:59AM +0530, Chris Lamb wrote:
> Hey,
> 
> > Thanks for your talk today.
> 
> No; thank you! Filed as #888237
> 
> > diffoscope 78
> 
> This might be it; this is quite an old version. Will investigate ASAP!

I'm running debian/testing.
I just installed the debian/unstable version and got version 90, indeed
a big jump :)

Seems the same though:
saruman:/var/cache/apt/archives$ diffoscope youtube-dl_2014.07.15-1_all.deb 
youtube-dl_2017.02.07-1_all.deb > /tmp/diff
saruman:/var/cache/apt/archives$ grep bilibili.py /tmp/diff
│ │ │ │ -usr/lib/python2.7/dist-packages/youtube_dl/extractor/bilibili.py
│ │ │ │ +usr/lib/python3/dist-packages/youtube_dl/extractor/bilibili.py
│ │ │ --rw-r--r--   0 root (0) root (0) 3657 2014-07-13 
15:21:20.00 
./usr/lib/python2.7/dist-packages/youtube_dl/extractor/bilibili.py
│ │ │ +-rw-r--r--   0 root (0) root (0) 9123 2017-02-09 
07:12:11.00 ./usr/lib/python3/dist-packages/youtube_dl/extractor/bilibili.py
saruman:/var/cache/apt/archives$ diffoscope --version
diffoscope 90


By the way, if you're bored or curious, this was the big linux image
that we were doing at google:
http://marc.merlins.org/linux/talks/ProdNG-LCA2014/ProdNG.pdf

probably specifically slide 49
"ProdNG image generation"

Cheers,
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems 
   what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901

Bug#888235: dash breaks debootstrap

[Sven Joachim]

Control: tags -1 + patch

Am 24.01.2018 um 06:16 schrieb Helmut Grohne:

> Package: dash
> Version: 0.5.8-2.7
> Severity: serious
>
> debootstrap sid now fails:
>
> | I: Installing core packages...
> | W: Failure trying to run: chroot $TARGET dpkg --force-depends
> | --install /var/cache/apt/archives/base-passwd_3.5.44_amd64.deb
> | W: See $TARGET/b/debootstrap/debootstrap.log for details
>
> debootstrap.log contains:
>
> | gpgv: Signature made Wed Jan 24 03:52:30 2018 CET
> | gpgv:using RSA key A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553
> | gpgv: Good signature from "Debian Archive Automatic Signing Key 
> (7.0/wheezy) "
> | gpgv: Signature made Wed Jan 24 03:52:30 2018 CET
> | gpgv:using RSA key 126C0D24BD8A2942CC7DF8AC7638D0442B90D010
> | gpgv: Good signature from "Debian Archive Automatic Signing Key (8/jessie) 
> "
> | dpkg: warning: parsing file '/var/lib/dpkg/status' near line 5 package 
> 'dpkg':
> |  missing description
> | dpkg: warning: parsing file '/var/lib/dpkg/status' near line 5 package 
> 'dpkg':
> |  missing architecture
> | dpkg: warning: 'sh' not found in PATH or not executable
> | dpkg: error: 1 expected program not found in PATH or not executable
> | Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and 
> /sbin
>
> $TARGET/bin/sh does not exist.

It is no longer shipped in the package, which does not seem to be
intentional, as it is not mentioned in debian/changelog:

,
| $ debdiff dash_0.5.8-2.5_i386.deb dash_0.5.8-2.7_i386.deb
| [The following lists of changes regard files as different if they have
| different names, permissions or owners.]
| 
| Files in first .deb but not in second
| -
| lrwxrwxrwx  root/root   /bin/sh -> dash
| lrwxrwxrwx  root/root   /usr/share/man/man1/sh.1.gz -> dash.1.gz
`

Attached is a patch which puts the symlinks back into place.

Cheers,
   Sven

>From b9d09de1bcfc898a737dd4485aa658278fb6aa4c Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Wed, 24 Jan 2018 07:10:00 +0100
Subject: [PATCH] Re-add missing symlinks

---
 debian/changelog  | 6 ++
 debian/dash.links | 2 ++
 2 files changed, 8 insertions(+)
 create mode 100644 debian/dash.links

diff --git a/debian/changelog b/debian/changelog
index bb14d91..624f930 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+dash (0.5.8-2.8) UNRELEASED; urgency=medium
+
+  * Re-add the symlinks for /bin/sh and the sh manpage (Closes: #888235).
+
+ -- Sven Joachim   Wed, 24 Jan 2018 07:09:24 +0100
+
 dash (0.5.8-2.7) unstable; urgency=medium
 
   [ James Cowgill ]
diff --git a/debian/dash.links b/debian/dash.links
new file mode 100644
index 000..87a7043
--- /dev/null
+++ b/debian/dash.links
@@ -0,0 +1,2 @@
+bin/dash bin/sh
+/usr/share/man/man1/dash.1 /usr/share/man/man1/sh.1
-- 
2.15.1

Bug#888238: nmu: caffe_1.0.0-5

[Lumin]

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

Hello,

The current binary dependency of libcaffe-cpu1 includes
libboost_python-py35.so.1.62.0
However this shared object is nolonger available in the boost package
since python3.6 turns to default. This problem caused CI failures:

https://ci.debian.net/data/autopkgtest/unstable/amd64/c/caffe/20180107_013801/log.gz
Please rebuild caffe against libboost_python-py36.so.1.62.0
shipped by libboost-python1.62.0 (>= 1.62.0+dfsg-5)
on any architecture.

nmu caffe_1.0.0-5 . ANY . -m "Rebuild against libboost_python-py36.so.1.62.0"

Thanks

-- 
Best,

Bug#888236: torbrowser-launcher: broken by Tor Browser 7.5: No such file or directory: '.../Docs/sources/versions'

[Paul Wise]

Package: torbrowser-launcher
Version: 0.2.8-6
Severity: serious
Usertags: crash

Tor Browser upgraded itself to 7.5 but this broke torbrowser-launcher:

https://blog.torproject.org/tor-browser-75-released

$ torbrowser-launcher 
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.2.8
https://github.com/micahflee/torbrowser-launcher
Refreshing local keyring...
Traceback (most recent call last):
  File "/usr/bin/torbrowser-launcher", line 30, in 
torbrowser_launcher.main()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/__init__.py", line 
62, in main
app = Launcher(common, url_list)
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
91, in __init__
if not self.common.settings['installed'] or not self.check_min_version():
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
603, in check_min_version
for line in open(self.common.paths['tbb']['versions']).readlines():
IOError: [Errno 2] No such file or directory: 
'/home/pabs/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/TorBrowser/Docs/sources/versions'

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

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

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20170717
ii  gnupg 2.2.4-1
ii  libdbus-glib-1-2  0.108-3
ii  python2.7.14-4
ii  python-gtk2   2.24.0-5.1+b1
ii  python-lzma   0.5.3-3
ii  python-parsley1.2-1
ii  python-psutil 5.4.2-1
ii  python-twisted17.9.0-1
ii  python-txsocksx   1.15.0.2-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.2.9-1

Versions of packages torbrowser-launcher suggests:
pn  apparmor   
ii  python-pygame  1.9.1release+dfsg-10+b2

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#888235: dash breaks debootstrap

[Helmut Grohne]

Package: dash
Version: 0.5.8-2.7
Severity: serious

debootstrap sid now fails:

| I: Installing core packages...
| W: Failure trying to run: chroot $TARGET dpkg --force-depends --install 
/var/cache/apt/archives/base-passwd_3.5.44_amd64.deb
| W: See $TARGET/b/debootstrap/debootstrap.log for details

debootstrap.log contains:

| gpgv: Signature made Wed Jan 24 03:52:30 2018 CET
| gpgv:using RSA key A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553
| gpgv: Good signature from "Debian Archive Automatic Signing Key (7.0/wheezy) 
"
| gpgv: Signature made Wed Jan 24 03:52:30 2018 CET
| gpgv:using RSA key 126C0D24BD8A2942CC7DF8AC7638D0442B90D010
| gpgv: Good signature from "Debian Archive Automatic Signing Key (8/jessie) 
"
| dpkg: warning: parsing file '/var/lib/dpkg/status' near line 5 package 'dpkg':
|  missing description
| dpkg: warning: parsing file '/var/lib/dpkg/status' near line 5 package 'dpkg':
|  missing architecture
| dpkg: warning: 'sh' not found in PATH or not executable
| dpkg: error: 1 expected program not found in PATH or not executable
| Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin

$TARGET/bin/sh does not exist.

Helmut

Bug#888233: RFA: ujson -- ultra fast JSON encoder and decoder for Python 2

[Sandro Tosi]

Package: wnpp
Severity: normal

I request an adopter for the ujson package.

The package description is:
 UltraJSON is an ultra fast JSON encoder and decoder written in pure C with
 bindings for Python.

Bug#888232: libreoffice-calc using 100% CPU while idle

[Ali Sayed]

Package: libreoffice-calc
Version: 1:5.4.4-1
Severity: important
Tags: a11y

Dear Maintainer,

If I launch libreoffice-calc with a small spreadsheet (a shopping list) I 
notice the fan on my laptop comes on immediately and 'htop' shows 100% usage on 
one core. 

I am not even using "Calc" its just open and using up too much CPU.  The system 
is usable because I have 3 more cores, but its annoying to hear the fan and 
seeing that "Calc" is misbehaving like all Microsoft Apps.

I am running on "Testing" so I am sure this will be fixed very soon.

thanks

-ali


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

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

Versions of packages libreoffice-calc depends on:
ii  coinor-libcbc3   2.9.9+repack1-1
ii  coinor-libcoinmp1v5  1.8.3-2
ii  coinor-libcoinutils3v5   2.10.14+repack1-1
ii  libblas3 [libblas.so.3]  3.7.1-4
ii  libboost-filesystem1.62.01.62.0+dfsg-5
ii  libboost-iostreams1.62.0 1.62.0+dfsg-5
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.26-4
ii  libetonyek-0.1-1 0.1.7-2
ii  libgcc1  1:7.2.0-19
ii  libicu57 57.1-8
ii  liblapack3 [liblapack.so.3]  3.7.1-4
ii  liblcms2-2   2.9-1
ii  libmwaw-0.3-30.3.13-1
ii  libodfgen-0.1-1  0.1.6-2
ii  liborcus-0.12-0  0.12.1-3+b1
ii  libreoffice-base-core1:5.4.4-1
ii  libreoffice-core 1:5.4.4-1
ii  librevenge-0.0-0 0.0.4-6
ii  libstaroffice-0.0-0  0.0.5-1
ii  libstdc++6   7.2.0-19
ii  libwps-0.4-4 0.4.8-1
ii  libxml2  2.9.4+dfsg1-6.1
ii  lp-solve 5.5.0.15-4+b1
ii  uno-libs35.4.4-1
ii  ure  5.4.4-1
ii  zlib1g   1:1.2.8.dfsg-5

libreoffice-calc recommends no packages.

Versions of packages libreoffice-calc suggests:
ii  ocl-icd-libopencl1  2.2.12-1

Versions of packages libreoffice-core depends on:
ii  fontconfig2.12.6-0.1
ii  fonts-opensymbol  2:102.10+LibO5.4.4-1
ii  libboost-date-time1.62.0  1.62.0+dfsg-5
ii  libc6 2.26-4
ii  libcairo2 1.15.8-3
ii  libclucene-contribs1v52.3.3.4+dfsg-1
ii  libclucene-core1v52.3.3.4+dfsg-1
ii  libcmis-0.5-5v5   0.5.1+git20160603-3+b1
ii  libcups2  2.2.6-4
ii  libcurl3-gnutls   7.57.0-1
ii  libdbus-1-3   1.12.2-1
ii  libdbus-glib-1-2  0.108-3
ii  libdconf1 0.26.1-2
ii  libeot0   0.01-4+b1
ii  libepoxy0 1.4.3-1
ii  libexpat1 2.2.5-3
ii  libexttextcat-2.0-0   3.4.5-1
ii  libfontconfig12.12.6-0.1
ii  libfreetype6  2.8.1-1
ii  libgcc1   1:7.2.0-19
ii  libglib2.0-0  2.54.3-1
ii  libgltf-0.1-1 0.1.0-2
ii  libgpgmepp6   1.10.0-1
ii  libgraphite2-31.3.10-8
ii  libharfbuzz-icu0  1.7.2-1
ii  libharfbuzz0b 1.7.2-1
ii  libhunspell-1.6-0 1.6.2-1
ii  libhyphen02.8.8-5
ii  libice6   2:1.0.9-2
ii  libicu57  57.1-8
ii  libjpeg62-turbo   1:1.5.2-2+b1
ii  liblcms2-22.9-1
ii  libldap-2.4-2 2.4.45+dfsg-1
ii  libmythes-1.2-0   2:1.2.4-3
ii  libneon27-gnutls  0.30.2-2
ii  libnspr4  2:4.16-1+b1
ii  libnss3   2:3.34.1-1
ii  libodfgen-0.1-1   0.1.6-2
ii  liborcus-0.12-0   0.12.1-3+b1
ii  libpcre3  2:8.39-8
ii  libpng16-16   1.6.34-1
ii  libpoppler72  0.61.1-2
ii  librdf0   1.0.17-1.1
ii  libreoffice-common1:5.4.4-1
ii  librevenge-0.0-0  0.0.4-6
ii  libsm62:1.2.2-1+b3
ii  libstdc++67.2.0-19
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxinerama1  2:1.1.3-1+b3
ii  libxml2   2.9.4+dfsg1-6.1
ii  libxmlsec11.2.25-1
ii  libxmlsec1-nss1.2.25-1
ii  libxrandr22:1.5.1-1
ii  libxrender1   1:0.9.10-1
ii  libxslt1.11.1.29-5
ii  uno-libs3 5.4.4-1
ii  ure   5.4.4-1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages libreoffice-core recommends:
ii  libpaper-utils  1.1.24+nmu5

-- no debconf information

Bug#888231: debmirror: agressive cleanup on multiple codenames

[Derek Murphy]

Package: debmirror
Version: 1:2.16+deb8u1

I am using debmirror to mirror all of strech, strech-updates for my amd64
based computers but also use a lot of single board systems that are
currently build with jessie armhf. I have two debmirror scripts that have
the same output root which ends in a very similar folder structure as the
actual debian repo.

url/debian/dists/stretch
url/debian/dists/jessie
url/debian/pool

I like to clean up packages that are no longer needed / obe for new
version. When I use the postcleanup command the second debmirror script to
run will remove all of the pool files from the first script

Order of operations

debmirror stretch
debmirror jessie --- removes all of the files for stretch in the pool

Can we get it to only remove files that it either downloaded or that are
for it's arch only but that would also cause issues if I want to run two
scripts for amd64 jessie and amd64 stretch.

Thanks

Bug#887963: git-debcherry: Exports incorrect patches when fed tags

[James McCoy]

On Sun, Jan 21, 2018 at 11:21:51PM -0500, James McCoy wrote:
> TL;DR, git-debcherry (or maybe just gitpkg's invocation of it) should
> likely force resolving the given treeish to a non-tag with ^{}.
> 
> $ debcheckout neovim-qt && cd neovim-qt
> …
> $ git-debcherry -o ../bug v0.2.8 v0.2.8-2
> Cloning into '/tmp/git-debcherry.KYsPnT/clone'...
> done.

FWIW, this fixes the behavior for me.  However, I haven't understood the
rest of the code to figure out why using tags doesn't work.

-- 8< --
diff --git i/git-debcherry w/git-debcherry
index 1ec1207..342a5f8 100755
--- i/git-debcherry
+++ w/git-debcherry
@@ -149,13 +149,13 @@ fi
 _time $LINENO
 
 upstream=$1
-if ! upstream_sha1=$(git rev-parse "$upstream" 2>$log); then
+if ! upstream_sha1=$(git rev-parse "$upstream"^{} 2>$log); then
 _die "bad or missing ref: $upstream"
 fi
 
 head=${2-$(git symbolic-ref HEAD)}
 head=${head##refs/heads/}
-if ! head_sha1=$(git rev-parse "$head" 2>$log); then
+if ! head_sha1=$(git rev-parse "$head"^{} 2>$log); then
 _die "bad or missing ref: $head"
 fi
 
-- >8 --

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#888230: mate-tweak: Don't depend on python-gobject2

[Jeremy Bicha]

Source: mate-tweak
Version: 18.04.6-1

python-gobject2 is deprecated. Please check whether mate-tweak's
python-gobject2 dependency can be dropped. I suspect the python3-gi
dependency is sufficient.

Thanks,
Jeremy Bicha

Bug#638024: user story --- bad Default-Release breaks unattended-upgrades

[Trent W. Buck]

Hi, I have a user story relevant to #638024.

TL;DR version:

  When Default-Release is set and /var/lib/apt/lists is empty,
  apt-get check errors, and unattended-upgrades silently fail.

Boring backstory follows.

I'm making headless servers to be deployed in the homes of non-technical users.
To harden them against operator error, their OS is a read-only Debian Live 
image.

As part of my Best Current Practice I set Default-Release "stretch",
to prevent accidental dist-upgrades when sources.list is in an unusual state.
(For THIS server, that's unlikely, but it's BCP so I do it everywhere.)

To make the image smaller, /var/lib/apt/lists is not included.
(It'll have to download the full Packages files after each reboot, but
these servers won't reboot regularly, so that's fine.)

As part of my Best Current Practice I install and enable unattended-upgrades.
This won't fix kernel vulns (since it's a read-only image), but
it WILL fix userland vulns (e.g. to glibc).
(It'll have to re-download all the security patches after each reboot, but
these servers won't reboot regularly, so that's fine.)


With this framework, unattended-upgrades doesn't work, and this shows why:

root@datasafe:~# cat >/etc/apt/apt.conf.d/20derp
APT::Periodic::Verbose "2";

root@datasafe:~# /usr/lib/apt/apt.systemd.daily update
verbose level 2
Reading package lists... Done
E: The value 'stretch' is invalid for APT::Default-Release as such a 
release is not available in the sources
error encountered in cron job with "apt-get check".

Note that APT::Default-Release is the ONLY problem here:

root@datasafe:~# apt-get check
Reading package lists... Done
E: The value 'stretch' is invalid for APT::Default-Release as such a 
release is not available in the sources

root@datasafe:~# apt-get check -t ''
Reading package lists... Done
Building dependency tree
Reading state information... Done

Doing the first apt update by hand fixes the immediate problem:

root@datasafe:~# apt update -qq
All packages are up to date.

root@datasafe:~# rm /var/lib/apt/periodic/update-stamp
root@datasafe:~# /usr/lib/apt/apt.systemd.daily update
verbose level 2
Reading package lists... Done
Building dependency tree
Reading state information... Done
check_stamp: missing time stamp file: /var/lib/apt/periodic/update-stamp.
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://cdn-fastly.deb.debian.org/debian stretch InRelease
Hit:3 http://cdn-fastly.deb.debian.org/debian stretch-updates InRelease
Hit:4 http://cdn-fastly.deb.debian.org/debian stretch-backports InRelease
Hit:5 http://cdn-fastly.deb.debian.org/debian stretch Release
Reading package lists... Done
download updated metadata (success).
send dbus signal (success)
check_stamp: interval=0
download upgradable (not run)
unattended-upgrade -d (not run)

Unfortunately that basically means I have to run "apt update" by hand after 
every reboot.
I could do that in a simple @reboot cron job (or systemd.timer equivalent), but
what happens if the user turns on the computer while the network cable is 
unplugged?

In that case, the @reboot apt update will fail, and we're back to 
unattended-upgrades not applying.

I could run apt by hand when "the" network is up, e.g. via 
network-wait-online.target or an interfaces(5) post-up command.
But this actually runs as soon as systemd-networkd has a route to google, not 
when HTTP to deb.debian.org is allowed, so
it can still fail in obscure edge cases (e.g. if the device is booted behind a 
hotel's captive portal).



Is there some way to resolve this on your end?
Allowing Default-Release "foo" when /var/lib/apt/lists is empty would be ideal 
for me, but I suspect not for you. ☺

In the meantime, AFAICT my options are:

  • don't set Default-Release, and
accept the low-chance high-impact risk of accidental dist-upgrade.

  • run apt update by hand whenever "the" network is "up", and
accept the low-chance high-impact risk of no security patches if the update 
fails.

  • make /var/lib/apt/lists persistent across reboots, and
accept the extra cost (for the HDD or whatever), complexity, and
failure modes when the storage dies or gets corrupted.

Bug#888229: Adding a fox to cowsay

[Hansen Wu]

Package: cowsay
Version: 3.03+dfsg1-15
Severity: wishlist

Hello,

I've been using my own fox cowsay for a while and thought it'd be a nice
addition. I've linked to the cowfile and a screenshot of it in action below.

https://github.com/raydarnet/foxsay/blob/master/fox.cow
https://github.com/raydarnet/foxsay/blob/master/readme/fox_example.png

I'm fine with releasing both under the same licensing terms as cowsay. Let
me know if there's any questions.

Much appreciated,

Hansen

Bug#888228: cmake: ignores linker scripts on the Hurd (and kFreeBSD?)

[Aaron M. Ucko]

Package: cmake
Version: 3.9.5-1
Severity: important
Tags: upstream
User: debian-h...@lists.debian.org
Usertags: hurd-i386
Control: affects -1 src:mariadb-connector-c

The build of mariadb-connector-c for hurd-i386 (admittedly not a
release architecture) [1] failed because the symbols came out
unversioned, whereas the .symbols file expects version annotations.
By my reading of [2], CMake encounters the version script on line 378
but evidently neglects to pass it along to the linker.  I suspect
kFreeBSD builds may wind up failing in the same fashion if and when
their autobuilders are back in commission.

Could you please take a look?

Thanks!

[1] 
https://buildd.debian.org/status/fetch.php?pkg=mariadb-connector-c=hurd-i386=3.0.3-1=1516561406=0
[2] 
https://salsa.debian.org/mariadb-team/mariadb-connector-c/blob/master/libmariadb/CMakeLists.txt

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#888227: dash: Dash update remove /bin/sh symlink

[Blake Lee]

Package: dash
Version: 0.5.8-2.6
Severity: important

Dear Maintainer,

I was doing an apt dist-upgrade on sid today when apt stopped and there
was no way to bring it back. Dpkg wouldn't work and neither would apt. I
recreated the symlink and after a few tries was able to get the update to
finish. This also has happened on my laptop. relevant terminal output below

(Reading database ... 194866 files and directories currently installed.)
Preparing to unpack .../dpkg_1.19.0.5_amd64.deb ...
Unpacking dpkg (1.19.0.5) over (1.19.0.4) ...
Setting up dpkg (1.19.0.5) ...
(Reading database ... 194866 files and directories currently installed.)
Preparing to unpack .../dash_0.5.8-2.6_amd64.deb ...
Removing 'diversion of /bin/sh to /bin/sh.distrib by dash'
Adding 'diversion of /bin/sh to /bin/sh.distrib by bash'
Removing 'diversion of /usr/share/man/man1/sh.1.gz to
/usr/share/man/man1/sh.distrib.1.gz by dash'
Adding 'diversion of /usr/share/man/man1/sh.1.gz to
/usr/share/man/man1/sh.distrib.1.gz by bash'
Unpacking dash (0.5.8-2.6) over (0.5.8-2.5) ...
dpkg: warning: 'sh' not found in PATH or not executable
dpkg: error: 1 expected program not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
E: Sub-process /usr/bin/dpkg returned an error code (2)



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

Kernel: Linux 4.14.12-acs (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages dash depends on:
ii  debianutils  4.8.4
ii  dpkg 1.19.0.5
ii  libc62.26-4

dash recommends no packages.

dash suggests no packages.

-- debconf information:
* dash/sh: true

Bug#888206: /usr/bin/vim.basic: Wrong behavior of arrow keys and compose keys.

[James McCoy]

On Tue, Jan 23, 2018 at 11:18:49PM +0100, luciano wrote:
> I connect to remote systems using ssh and use vi and vim on the remote
> systems  for all administrative tasks. Now I see that the arrow keys
> and the compose keys- these are useful for characters as @ and # if
> you use italian keyboard - have a wrog behavior. Arrow keys commute in
> insert mode, add a new line and a character at the very beginning of
> the new line.

That sounds like Vim is in vi-compatible mode or something has done
"set noesckeys".

Can you post what ":verbose set cp? ek?" shows?

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#888112: diffoscope: compare JSON files using Python jsondiff module

[Chris Lamb]

Hi pabs,

> That isn't going to work for UTF-8 JSON, I suggest using the MIME type
> instead of the file type string.

  
https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=f7ced27f52b974b8dac3354b3145637e3bc28f24

> I would suggest also checking for '[' characters (from JSON arrays).

  
https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=de1abeae19067539c8d45758e657634762589451

:)


Regards,

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

Bug#831449: lintian on Sid amd64 reports volatile false spelling errors in binaries

[Chris Lamb]

Jakub Wilk wrote:

> I'm not sure what to do about it on Lintian side. Perhaps we should 
> spell-check only long (say, >= 12 bytes) strings in binaries?

Wouldn't that mean we would only find spelling problems for very long
words? That would seem a little too crippling. :(

Apart from that, I'm not sure what lintian can do here, indeed.


Regards,

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

Bug#888112: diffoscope: compare JSON files using Python jsondiff module

[Paul Wise]

On Wed, 2018-01-24 at 06:47 +0530, Chris Lamb wrote:

> https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=2a758d3d0205e934ed6dffebb5d6462b00fe590d

I would suggest also checking for '[' characters (from JSON arrays).

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#888226: dash: Please package new upstream version

[Boyuan Yang]

Source: dash
Version: 0.5.8-2.7

Dear dash maintainer,

Thank you for maintaining dash in Debian.

Some new upstream version for dash has been released for several years. The 
lastest version of dash is 0.5.9.1 while dash in Debian is 0.5.8. Could you 
please consider packaging it inside Debian?

Thanks!

--
Regards,
Boyuan Yang

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

Bug#888112: diffoscope: compare JSON files using Python jsondiff module

[Paul Wise]

On Wed, 2018-01-24 at 06:47 +0530, Chris Lamb wrote:

> https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=2a758d3d0205e934ed6dffebb5d6462b00fe590d

That isn't going to work for UTF-8 JSON, I suggest using the MIME type
instead of the file type string.

$ curl -s 'https://salsa.debian.org/api/v4/users/1894' > user
$ file user
user: UTF-8 Unicode text, with very long lines, with no line terminators
$ file --mime-type user 
user: text/plain

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#887716: not necessarily not running

[Michael Biebl]

On Fri, 19 Jan 2018 18:46:22 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson
 wrote:
> Package: nftables
> Version: 0.8.1-1
> Severity: minor
> 
> Setting up nftables (0.8.1-1) ...
> nftables.service is a disabled or a static unit not running, not starting it.
> 
> Not completely correct. Yes it is disabled, but actually it is running.

It is correct, nftables.service is disabled and not running.

> # nft list tables
> table ip firewall
> table ip6 firewall
> 

What's relevant to deb-systemd-invoke is the output of
systemctl status nftables.service

If you check that, you will see that the status of nftables.service is
disabled and not running.

-- 
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#878221: linux-image-4.9.0-4-amd64: Screen flickers randomly with Radeon R9 270X since upgrade from 4.9.0-3 to 4.9.0-4

[Robin Gareus]

The recent backport kernel does *not* have this issue. All is fine with

 4.14.0-0.bpo.3-amd64 #1 SMP Debian 4.14.13-1~bpo9+1 (2018-01-14)

This is on a Thinkpad X250 with 00:02.0 VGA compatible controller: Intel
Corporation HD Graphics 5500 (rev 09)

4.9.0-4-amd64 and 4.9.0-5-amd64 on the same box do cause screen flickering.



Chances are that the issue was introduced by the update to upstream
4.9.46. There are a handful of "drm/i915" changes:

https://anonscm.debian.org/git/kernel/linux.git/commit/?h=debian/4.9.65-3%2bdeb9u2=17811b5a4b11b32307baca3b88067398a1168cfb

"Workaround VLV/CHV DSI scanline counter hardware fail" sounds
suspicious, but that's just a guess.

Bug#888225: lamarc: FTBFS on non-Linux: No match for wx-config --toolkit=osx_cocoa

[Aaron M. Ucko]

Source: lamarc
Version: 2.1.10.1+dfsg-1
Severity: important
Tags: upstream
Justification: fails to build from source
User: debian-h...@lists.debian.org
Usertags: hurd-i386

The build of lamarc for hurd-i386 (admittedly not a release
architecture) failed:

  checking build system type... i686-pc-gnu
  checking host system type... i686-pc-gnu
  checking target system type... i686-pc-gnu
  [...]
  DO NOT CHECK THIS config.ac in, it has GUI_TOOLKIT and
  LAMARC_CODE_OSTYPE hardwired for 10.7 mac
  [...]
   Here is error message from wx-config, in case that helps:
  
 Default config is gtk2-unicode-3.0 No config found to match: 
/usr/bin/wx-config --debug=no --toolkit=osx_cocoa --list in 
/usr/lib/i386-gnu/wx/config Please install the desired library build, or 
specify a different prefix where it may be found. If the library is not 
installed you may call its wx-config directly by specifying its full path. Also 
available in /usr: base-unicode-3.0 gtk2-unicode-3.0
  
  *
  configure: error: cannot proceed without suitable wxWidgets library

The kFreeBSD autobuilders still appear to be out of commission (or at
best heavily backlogged), but it looks like they'd run into the same
errors if they were to attempt to build lamarc.

In general, I expect the Linux/FreeBSD settings should make a much
more reasonable default for platforms the build system doesn't
specifically recognize than the settings for macOS, which is not so
mainstream.

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#887716: [pkg-netfilter-team] Bug#887716: not necessarily not running

[Michael Biebl]

After reading your initial bug report again, it seems you have started
nftables not using the nftables.service i.e. nftables.service is indeed
not running. I thus think the message from deb-systemd-invoke is correct.

The only bit that could be maybe be tweaked is:

> } elsif (!$unit_installed && !$unit_active && $action eq "restart") {
> print STDERR "$unit is a disabled or a static unit not running, 
> not starting it.\n";
> }


we should probably say: ", not restarting it."


-- 
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#887716: [pkg-netfilter-team] Bug#887716: not necessarily not running

[Michael Biebl]

Am 24.01.2018 um 02:50 schrieb Michael Biebl:
> Control: reassign -1 init-system-helpers
> Control: tags -1 - moreinfo unreproducible
> 
> 
> Am 23.01.2018 um 23:57 schrieb Michael Biebl:
>> Control: tags -1 + moreinfo unreproducible
>>
>> [please always CC the maintainer if you reassign a bug report]
>>
>> On Mon, 22 Jan 2018 13:31:06 +0100 Arturo Borrero Gonzalez
>>  wrote:
>>> On Fri, 19 Jan 2018 21:58:11 +0800 =?utf-8?B?56mN5Li55bC8?= Dan
>>> Jacobson  wrote:
 I'm just saying
> nftables.service is a disabled or a static unit not running, not starting 
> it.
 perhaps could be better written
> nftables.service is disabled. Not starting it.
 or
> nftables.service is not enabled, so not starting it.
 or
> nftables.service is not enabled, so not starting it.
> If currently running, it was started by other means.


>>>
>>> That message is produced by systemd, not by nftables. Nothing that
>>> could be fixed from the src:nftables point of view.
>>
>> Are you sure this message is coming from systemd?
> 
> So, this message is not from systemd/systemctl, but from
> init-system-helpers, thus reassigning to the correct package.
> 
> 
> https://anonscm.debian.org/git/collab-maint/init-system-helpers.git/tree/script/deb-systemd-invoke#n99
> 
> https://anonscm.debian.org/git/collab-maint/init-system-helpers.git/commit/?id=a4e43fcdabf796
> 

Btw, what the message says is: "You either have a disabled service or a
static unit which is not running, thus not starting it."

At least that's how I read it.

-- 
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#887716: [pkg-netfilter-team] Bug#887716: not necessarily not running

[Michael Biebl]

Control: reassign -1 init-system-helpers
Control: tags -1 - moreinfo unreproducible


Am 23.01.2018 um 23:57 schrieb Michael Biebl:
> Control: tags -1 + moreinfo unreproducible
> 
> [please always CC the maintainer if you reassign a bug report]
> 
> On Mon, 22 Jan 2018 13:31:06 +0100 Arturo Borrero Gonzalez
>  wrote:
>> On Fri, 19 Jan 2018 21:58:11 +0800 =?utf-8?B?56mN5Li55bC8?= Dan
>> Jacobson  wrote:
>>> I'm just saying
 nftables.service is a disabled or a static unit not running, not starting 
 it.
>>> perhaps could be better written
 nftables.service is disabled. Not starting it.
>>> or
 nftables.service is not enabled, so not starting it.
>>> or
 nftables.service is not enabled, so not starting it.
 If currently running, it was started by other means.
>>>
>>>
>>
>> That message is produced by systemd, not by nftables. Nothing that
>> could be fixed from the src:nftables point of view.
> 
> Are you sure this message is coming from systemd?

So, this message is not from systemd/systemctl, but from
init-system-helpers, thus reassigning to the correct package.


https://anonscm.debian.org/git/collab-maint/init-system-helpers.git/tree/script/deb-systemd-invoke#n99

https://anonscm.debian.org/git/collab-maint/init-system-helpers.git/commit/?id=a4e43fcdabf796

-- 
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#888115: ITP: git-secret -- store encrypted private data inside a git repository

[Don Armstrong]

On Wed, 24 Jan 2018, ChangZhuo Chen (陳昌倬) wrote:
> On Tue, Jan 23, 2018 at 10:09:26AM -0800, Don Armstrong wrote:
> > On Tue, 23 Jan 2018, ChangZhuo Chen wrote:
> > > git-secret is a bash tool to store your private data inside a git repo.
> > > How’s that? Basically, it just encrypts, using gpg, the tracked files
> > > with the public keys of all the users that you trust.
> > 
> > I'm curious how this differs from pass[1] or just checking encrypted
> > data directly into a git repo.
> 
> git-secret is used to encrypt credential file (e.g. database passwords,
> application access token, ...) in a code repository.
> 
> 
> Maybe the following description is better?
> 
> Description: store encrypted credential inside source code git repository
>  git-secret is designed to solve the problem where to store the
>  credential file (e.g. password, token, ...) for a service. With
>  git-secret, we can store encrypted credential along with source code in
>  git repository.

Ah, got it; makes more sense now. It's really for deployment
authentication tokens. [So, totally different from pass.]

Thanks!

-- 
Don Armstrong  https://www.donarmstrong.com

For a moment, nothing happened. Then, after a second or so, nothing
continued to happen.
 -- Douglas Adams

Bug#888086: cpphs: Fails to parse newer math.h headers

[Clint Adams]

Control: reassign -1 c2hs

On Tue, Jan 23, 2018 at 05:05:24PM +0100, Markus Ongyerth wrote:
> I'm a dumbo. This should be on c2hs not cpphs.
> And then the relevant upstream fix is:
> https://github.com/haskell/c2hs/commit/e5b1d84682a3f80721cc57e654feef6287cada36#diff-898d7d64ce63bc38886a61f03411d83b
> 
> I'm very sorry for this. Could you kindly move the report to the proper 
> package?

Bug#888112: diffoscope: compare JSON files using Python jsondiff module

[Chris Lamb]

Hi Paul,

> > I wonder how sensible it would be to, say, slurp the first 100 bytes and see
> > whether we start with a "{" (or some other heuristic) and, if so, try and
> > parse the file as JSON etc.
> 
> I think it would make diffoscope very slightly more useful if it could
> fill in the gaps in MIME type detection for this and other cases.

https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=2a758d3d0205e934ed6dffebb5d6462b00fe590d

> If it turns out to be too expensive then it could have an option.

Mo' options, mo' problems :)


Regards,

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

Bug#887716: [pkg-netfilter-team] Bug#887716: not necessarily not running

[積丹尼 Dan Jacobson]

MB> How exactly did you disable the service? If I install the nftables
MB> package I get no such message.

All I know is on my machines I have it disabled,
I think by some '$ systemctrl disable' command I used years ago.
And I only start and stop it via my modem controller script
(no point in having it running when I am offline.)
So as I am usually online when aptitude upgrades are running,
so then it is disabled, but running.

Bug#888224: libde265-0: Provide static library

[Alex Gaynor]

Package: libde265-0
Severity: normal

Currently libde265-0 provides dynamic libraries, however I have a use case
where it'd be great if static libraries were also provided.

Thanks!

Bug#888112: diffoscope: compare JSON files using Python jsondiff module

[Paul Wise]

On Wed, 2018-01-24 at 05:16 +0530, Chris Lamb wrote:

> I wonder how sensible it would be to, say, slurp the first 100 bytes and see
> whether we start with a "{" (or some other heuristic) and, if so, try and
> parse the file as JSON etc.

I think it would make diffoscope very slightly more useful if it could
fill in the gaps in MIME type detection for this and other cases.
If it turns out to be too expensive then it could have an option.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#888183: libc6: Breaks openvz virtuals again

[James Cloos]

AJ> Do you have a list of other packages from the glibc src that are
AJ> upgraded before?

The following packages have unmet dependencies:
 libc-dev-bin : Depends: libc6 (> 2.26) but 2.25-6 is installed
 libc6-dev : Depends: libc6 (= 2.26-4) but 2.25-6 is installed
 libc6-i386 : Depends: libc6 (= 2.26-4) but 2.25-6 is installed
 libc6-pic : Depends: libc6 (= 2.26-4) but 2.25-6 is installed
 libc6-x32 : Depends: libc6 (= 2.26-4) but 2.25-6 is installed
 locales : Depends: libc-bin (> 2.26) but 2.25-6 is installed
 nscd : Depends: libc6 (> 2.26) but 2.25-6 is installed

And on another box:

The following packages have unmet dependencies:
 libc-dev-bin : Depends: libc6 (> 2.26) but 2.25-6 is installed
 libc6-dev : Depends: libc6 (= 2.26-2) but 2.25-6 is installed
 libnih1 : Depends: libc6 (> 2.26) but 2.25-6 is installed
 locales : Depends: libc-bin (> 2.26)

And a third:

The following packages have unmet dependencies:
 libc-dev-bin : Depends: libc6 (> 2.26) but 2.25-6 is installed
 libc6-dev : Depends: libc6 (= 2.26-4) but 2.25-6 is installed
 locales : Depends: libc-bin (> 2.26) but 2.25-6 is installed

Those are after one previous attempt at --fix-broken.

AJ> In any case it's not something we can control, the abort is done
AJ> inside the libc6 preinst, there is no way the libc6 package can
AJ> do that earlier.

Of course it is.  Just make every deb from the glibc src do that abort.

Idealy, w/ a warning on how to hold them so that the rest of the
upgradable packages can do so.

-JimC
-- 
James Cloos  OpenPGP: 0x997A9F17ED7DAEA6

Bug#888084: libparted-fs-resize0: undefined symbols: needs -lparted -luuid

[Paul Wise]

On Tue, 2018-01-23 at 10:48 -0500, Phil Susi wrote:

> What is the proper fix for this?

It looks like you need this line in libparted/fs/Makefile.am:

libparted_fs_resize_la_LIBADD = $(top_builddir)/libparted/libparted.la 
$(UUID_LIBS) $(OS_LIBS) $(INTLLIBS)

debian/rules has --with=autoreconf so rebuilding Makefile.in is covered.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#888223: junit4-doc: Dead links in file:///usr/share/doc/junit4-doc/homepage.html

[Joel Fenwick]

Package: junit4-doc
Version: 4.12-4
Severity: normal

Dear Maintainer,

Installed junit4-doc.

Link to cookbook doesn't exist - checked, file not in package.
A quick check shows it existing in testing.

Just logging that this is broken in stable.

Thanks
Joel

-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')

junit4-doc depends on no packages.

Versions of packages junit4-doc recommends:
ii  default-jdk-doc   2:1.8-58
ii  libhamcrest-java-doc  1.3-6

Versions of packages junit4-doc suggests:
ii  junit4  4.12-4

-- no debconf information

Bug#888221: dash: Fails to install in unstable, breaks many things as /bin/sh

[dmm]

Package: dash
Version: 0.5.8-2.6
Severity: serious

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***
Just doing a typical update for debian unstable.

dmm:/bin/ $ sudo apt-get install dash   
[11:13:29]
Reading package lists... Done
Building dependency tree
Reading state information... Done
dash is already the newest version (0.5.8-2.6).
The following packages were automatically installed and are no longer required:
  linux-image-4.13.0-1-amd64 linux-image-4.14.0-1-amd64
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 139 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up dash (0.5.8-2.6) ...
Removing 'diversion of /bin/sh to /bin/sh.distrib by bash'
Adding 'diversion of /bin/sh to /bin/sh.distrib by dash'
Removing 'diversion of /usr/share/man/man1/sh.1.gz to 
/usr/share/man/man1/sh.distrib.1.gz by bash'
Adding 'diversion of /usr/share/man/man1/sh.1.gz to 
/usr/share/man/man1/sh.distrib.1.gz by dash'
dpkg: error: error executing hook 'if { test "$DPKG_HOOK_ACTION" = 
add-architecture || test "$DPKG_HOOK_ACTION" = remove-architecture; } && test 
-x /usr/share/pkgconf-dpkghook; then /usr/share/pkgconf-dpkghook update; fi', 
exit code 32512
E: Sub-process /usr/bin/dpkg returned an error code (2)

Unfortnuately this has the affect of breaking the symbolic link for
/bin/sh and so many things, like apt-get update then fail.

Quick work arround is to ln bash as sh.
Gets us going again, steps below for anyone in trouble.

dmm:/bin/ $ ls -la /bin/sh  
[11:13:38]
lrwxrwxrwx 1 root root 4 Jan 24 11:13 /bin/sh -> dash
dmm:/bin/ $ sudo rm sh  
[11:14:23]
dmm:/bin/ $ sudo ln -s bash sh  
[11:14:41]
dmm:/bin/ $ ls -la sh   
[11:14:46]
lrwxrwxrwx 1 root root 4 Jan 24 11:14 sh -> bash


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

Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dash depends on:
ii  debianutils  4.8.4
ii  dpkg 1.19.0.5
ii  libc62.26-4

dash recommends no packages.

dash suggests no packages.

-- debconf information:
* dash/sh: true

Bug#878088: [Reportbug-maint] Bug#878088: Bug#878088: reportbug: please inform security and lts teams about security update regressions

[Sandro Tosi]

sorry but did you even actually test your patch? this is the CC list:

X-Debbugs-Cc: mo...@debian.org, t, e, a, m, @, s, e, c, u, r, i, t, y,
., d, e, b, i, a, n, ., o, r, g

this wont work i guess; just use listcc += as in the rest of the code?

On Tue, Jan 23, 2018 at 3:12 PM, Markus Koschany  wrote:
>
>
> Am 23.01.2018 um 05:19 schrieb Sandro Tosi:
>>> What can we do to get this feature into reportbug?
>>
>> * did you update the patch to include the new contact field in
>> distribution.json and not hardcode the email address?
>
> Done.
>
>> * did you test what happen in offline mode and fix the eventual regression?
>
> I have tested reportbug with
>
> reportbug --offline 

the point is that in offline mode, it should *not* use any network
(you know, like if you are offline) and thus default to not copy the
security team and skip the entire branch, smth like "if pkgversion and
not options.offline"

>
> and added a try/except block to catch any exceptions that may occur with
> Python Requests (timeouts, network errors, etc.). If we reach this point
> in our code without a network connection, the program will exit because
> we need the information in distributions.json to proceed. Otherwise
> everything else works as expected.

please support the --timeout cli option and fail gracefully if you
cant contact security.d.o (sys.exit if you cant reach it is extremely
rude to users!) by not copying the security team.

>
>> i did a quick check on the number of bugs reported in a week, and over
>> the 600+ bugs filed, less than 30 where for a stable release (either
>> stretch or previous ones); i think you may also clarify that prompt,
>> as i suspect users will get rather confused "how am i supposed to know
>> if this is a security update? i just apt-get upgrade the system and
>> now this package doesnt work" kind of scenario.
>
> I don't know how I can clarify this prompt at the moment. I have added
> it because the security team does not want to be informed of any bug
> report against a package with a stable update or security update. The
> description of the Y/N choice is quite clear. If you are not sure, press
> N. Otherwise just hit the Enter key. Before we can evaluate the
> usefulness of this prompt we need some data from experience.

Did you check Nis suggestion at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878088#199 to check
apt-cache output (possibly via python3-apt) to see if that version is
coming from the updates stream? since it's on the table and you didnt
comment on it yet, i wanted to point it out.


-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#888114: Info received (Bug#888114 closed by Phil Susi <ps...@ubuntu.com> (Re: Bug#888114: Gparted show no partition if zfs is present))

[Curtis Gedak]

It sounds like you have extra signatures left over from prior actions.
For example perhaps the entire drive was once used with ZFS.

For an example of how one person identified and removed the extra
signatures, see the following report:

GPT disk full of partitions looks like iso9660 with no partitions
https://bugzilla.gnome.org/show_bug.cgi?id=789898

'Hope that helps.

Curtis

Bug#882630: Bug #882630: systemd-bootchart: debian/control refers to CC0 by URL

[Nicolas Braud-Santoni]

Control: tag -1 + patch

Dear maintainer,

Here is a patch, similar to what I did for #882629.


Best,

  nicoo

On Sat, Nov 25, 2017 at 01:43:31AM +0100, Nicolas Braud-Santoni wrote:
> Package: systemd-bootchart
> Severity: normal
> Control: tag -1 + stretch buster
> Control: block -1 by 882628
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Dear maintainer,
> 
> This package refers to the text of the Creative Commons Zero license by its 
> URL
> on creativecommons.org; as far as I understand, the Debian policy requires 
> that
> we ship the actual text of the license [0].
> 
> I requested (in #882628) that CC0 be shipped in /usr/share/common-licences, so
> it might become possible to refer to that file if you do not wish to include 
> the
> whole text in debian/copyright.
> 
> 
> Best,
> 
>   nicoo
> 
> -BEGIN PGP SIGNATURE-
> 
> iQJNBAEBCgA3FiEEiWEbFKE2h/s1SpJPnU+IAQz+GeMFAloYvLAZHG5pY29sYXNA
> YnJhdWQtc2FudG9uaS5ldQAKCRCdT4gBDP4Z46ptD/4htt8y2sskTGj9gEqrS6cB
> ccvvPYkKqJ7an6p7BaEpA/EoAwMPJ67dFfgSw/e0s2a6Ne8asQCGH1prRtOkmXXx
> bW7ZvuGzeQSbSXopGHVWHAMH7cByo5nFPZDSpqaRFaNFLSl9PTIQCrfd/TOlHXZd
> iQujk/iKYyXEs41drTQKF1wxqI7twMtE9dT2osnTwNkcj3bhaOj9x6eWe0yzMCL6
> zhIMkzS0ipsT5BEx6Y1Ifweu3D4dwc6Z0k0UgeueLkkzU0MitjRxBEZv1kB/qKp+
> ceT+2LooMqJ/0ouhFedUqzGTn4gM8jC9bxfN3uQfwO1kXFc1eNX3IaeZY1YqZBnj
> ml/yMCS0ZQ/8BTZMpLysLH7cNC6Z2AlhVLsnhk47ts75P+YFrgFbC9X2XCQ4e/LW
> CakG0JvLjroHOZFxzNgc3KPUNriUifW6DSu8CMjK96dr9AzmBvzLiuE29NZj4gg/
> 5JokPgBXrs5g6gnleO/F+Ogrif79QVCsSxackj1ci06jW/yi1yXvUike1N8bqC7S
> oXNg2TuLgTOO4yPsDcjcpL2pNiDYDCY2AMFvwC/e3PKEeNFAHhwphlz48WNXAvJe
> Jz6YC+hTYLQPAy+Rh43FWEV4asYQpUII9ESnD8q3wZex5dWlJ5jqdKi+yIIZARNz
> JTKkXvFo8CsCYXmiNClEQw==
> =mVQK
> -END PGP SIGNATURE-
> 
commit 250e21ac259a522ec9698f7557927e4853e214bf
Author: Nicolas Braud-Santoni 
Date:   Wed Jan 24 01:06:55 2018 +0100

debian/copyright: Refer to /usr/share/common-licenses

Closes: #882630

diff --git a/debian/copyright b/debian/copyright
index 8e6685c..9680279 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -23,13 +23,14 @@ Files: src/siphash24.h
src/siphash24.c
 Copyright: 2012 Jean-Philippe Aumasson 
2012 Daniel J. Bernstein 
-License: CC0
+License: CC0-1.0
  To the extent possible under law, the author(s) have dedicated all copyright
  and related and neighboring rights to this software to the public domain
  worldwide. This software is distributed without any warranty.
  .
- You should have received a copy of the CC0 Public Domain Dedication along with
- this software. If not, see .
+ The full text of the CC0 1.0 Universal license is available
+ https://creativecommons.org/publicdomain/zero/1.0/ and in
+ /usr/share/common-licenses/CC0-1.0 on Debian systems starting with Buster.
 
 License: LGPL-2.1+
  This program is free software; you can redistribute it and/or modify


signature.asc
Description: PGP signature

Bug#816446:

[Piotr Kowalski]

Bug#887227: lynis should depend on e2fsprogs explicitly

[Andreas Henriksson]

On Sun, Jan 14, 2018 at 08:07:56PM +0100, Helmut Grohne wrote:
> Package: lynis
[...]
> /usr/share/lynis/include/binaries contains lsattr and tune2fs. According to 
> file it is a POSIX shell script, ASCII text executable, with very long lines
[...]

It seems this shell script lists directory contents and based on matches
like lsattr, tune2fs, and many many others, prints a custom message
for that utility.

I don't think there's any need to specify a relationship to any of these
tools.

My conclusion is thus that this bug report should likely just be closed
without any other action.

Would be great to hear from maintainer what's going on.

Regards,
Andreas Henriksson

Bug#888112: diffoscope: compare JSON files using Python jsondiff module

[Chris Lamb]

Hi Mattia & Paul,

> FTR, it seems the only check used to decide whether a file is a json
> file, is to look for a '.json' as a filename suffix (and I'm not sure we
> can do much better without looking into the file, which is probably too
> expensive a check).

I wonder how sensible it would be to, say, slurp the first 100 bytes and see
whether we start with a "{" (or some other heuristic) and, if so, try and
parse the file as JSON etc.


Regards,

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

Bug#888220: ignition-math4: FTBFS on mips(el) and hppa: UNIT_Helpers_TEST fails badly

[Aaron M. Ucko]

Source: ignition-math4
Version: 4.0.0+dfsg1-1
Severity: important
Tags: upstream
Justification: fails to build from source
User: debian-m...@lists.debian.org
Usertags: mips mipsel

Builds of ignition-math4 for mips, mipsel, and the non-release
architecture hppa have been failing as detailed at

https://buildd.debian.org/status/fetch.php?pkg=ignition-math4=mips=4.0.0%2Bdfsg1-1=1516376024=0
https://buildd.debian.org/status/fetch.php?pkg=ignition-math4=mipsel=4.0.0%2Bdfsg1-1=1516373688=0
https://buildd.debian.org/status/fetch.php?pkg=ignition-math4=hppa=4.0.0%2Bdfsg1-1=1516373442=0

On mips, this test manages to make ctest itself to run out of memory:

Start 11: UNIT_Helpers_TEST
  terminate called after throwing an instance of 'std::bad_alloc'
what():  std::bad_alloc
  Makefile:143: recipe for target 'test' failed
  make[2]: *** [test] Aborted

On mipsel and hppa, HelpersTest.Pair spews millions(!) of errors and
then hits a timeout:

  11/75 Test #11: UNIT_Helpers_TEST ..***Timeout 240.12 sec
  [...]
  [ RUN  ] HelpersTest.Pair
  /<>/ignition-math4-4.0.0+dfsg1/src/Helpers_TEST.cc:516: Failure
Expected: a
Which is: 4294962295
  To be equal to: c
Which is: 4294962296
  [...]
  /<>/ignition-math4-4.0.0+dfsg1/src/Helpers_TEST.cc:516: Failure
Expected: a
Which is: 4294963544
  To be equal to: c
Which is: 4294963545
  
Start 12: check_UNIT_Helpers_TEST

(above output from mipsel, hppa is similar)

NB: the mipsel and hppa logs are a couple hundred megs apiece, so you
may wish to consider taking it easy on your browser by downloading raw
logs and viewing them with less. ;-)

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#887389: Bug solved

[Arnaud Courtès]

On Buster (testing at the moment), with the last 4.14 linux kernel 
image, speedstep works again correctly :)


We can say the bug is solved.

Arnaud

Bug#888052: gnome-shell: Restarts every 10 minutes related to dbus-org.freedesktop.hostname1.service

[Manuel Bilderbeek]

Hi,

On 23-01-18 20:49, Jason Crain wrote:

On Tue, Jan 23, 2018 at 01:24:10PM -0600, Jason Crain wrote:

Does downgrading gjs to version 1.50.2-2 fix it?


Sorry, I meant try downgrading libgjs0g to version 1.50.2-2.


So far, it does! No occurrences ever since I downgraded...
I'll evaluate a bit more and let you know.

Thanks a lot for your response!

--
Kind regards,

Manuel

Bug#887184: rsrce should depend on e2fsprogs explicitly

[Andreas Henriksson]

On Sun, Jan 14, 2018 at 08:10:57PM +0100, Helmut Grohne wrote:
> Package: rsrce
[...]
> /usr/bin/rsrce contains chattr. According to file it is a ELF 64-bit LSB 
> executable, x86-64, version 1 (SYSV)
[...]

This match seems to come from:
https://sources.debian.org/src/rsrce/0.2.2/command.c/#L370

Looking at the hooked up cmd_chattr function it doesn't seem to have
anything to do with (launching the) e2fsprogs chattr program.

My conclusion is that this bug report can likely just be closed.

Would be great to hear the maintainers view on this.

Regards,
Andreas Henriksson

Bug#887196: kvpm should depend on e2fsprogs explicitly

[Andreas Henriksson]

Control: retitle -1 kvpm should also recommend e2fsprogs

On Sun, Jan 14, 2018 at 08:05:54PM +0100, Helmut Grohne wrote:
> Package: kvpm
[...]
> /usr/sbin/kvpm contains dumpe2fs and resize2fs. According to file it is a ELF 
> 64-bit LSB shared object, x86-64, version 1 (GNU/Linux)
[...]

The other filesystem specific tools (for non-ext* filesystems) are
already listed under Recommends so I assume that should be extended
with e2fsprogs.

Would be great to hear from the maintainer on this!

Regards,
Andreas Henriksson

Bug#888219: ignition-math4: FTBFS on *i386: OrientedBoxTest.OperatorStreamOut fails

[Aaron M. Ucko]

Source: ignition-math4
Version: 4.0.0+dfsg1-1
Severity: important
Tags: upstream
Justification: fails to build from source

Builds of ignition-math4 for i386 and the non-release architecture
hurd-i386 both failed due to one error in UNIT_OrientedBox_TEST:

  27/75 Test #27: UNIT_OrientedBox_TEST ..***Failed0.01 sec
  Running main() from gtest_main.cc
  [==] Running 13 tests from 1 test case.
  [...]
  [ RUN  ] OrientedBoxTest.OperatorStreamOut
  /<>/ignition-math4-4.0.0+dfsg1/src/OrientedBox_TEST.cc:333: Failure
Expected: stream.str()
Which is: "Size[0.1 1.2 2.3] Pose[3.4 4.5 5.6 -0 -0.1 0.2]"
  To be equal to: "Size[0.1 1.2 2.3] Pose[3.4 4.5 5.6 0 -0.1 0.2]"
  [  FAILED  ] OrientedBoxTest.OperatorStreamOut (0 ms)
  [...]
   1 FAILED TEST
  [...]
  99% tests passed, 1 tests failed out of 75

It may be worth noting that i386 (i387) floating-point registers have
more precision than a standard double, which occasionally yields this
sort of surprise.  You might try disabling that feature by building
with -ffloat-store on these architectures.

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#286979: tar: should sort files before opening them

[Jakub Wilk]

* Florian Weimer , 2004-12-23, 13:03:
tar should sort the data returned by readdir() before opening any files 
(or calling stat).  Sorting files by name (or especially inode number) 
will greatly increase performance on directory-hashing file systems 
such as ext3.


The --sort option was added upstream in 1.28, so I guess this should be 
closed.


--
Jakub Wilk

Bug#888213: RFA: python-tornadorpc -- library for XML/JSON RPC using the Tornado framework

[Sandro Tosi]

Package: wnpp
Severity: normal

I request an adopter for the python-tornadorpc package.

The package description is:
 This library is an implementation of both the JSON-RPC and the XML-RPC
 specification (server-side) for the Tornado web framework. It supports the
 basic features of both, as well as the MultiCall / Batch support for both
 specifications. The JSON-RPC handler supports both the original 1.0
 specification, as well as the new (proposed) 2.0 spec, which includes batch
 submission, keyword arguments, etc.
 .
 There is also a base library that other RPC protocols could use to quickly get
 tied into Tornado.

Bug#888216: RFA: python-junit-xml

[Sandro Tosi]

Package: wnpp
Severity: normal

Bug#888217: RFA: pyvirtualdisplay

[Sandro Tosi]

Package: wnpp
Severity: normal

Bug#888215: RFA: python-scp -- scp module for paramiko

[Sandro Tosi]

Package: wnpp
Severity: normal

I request an adopter for the python-scp package.

The package description is:
 The scp.py module uses a paramiko transport to send and recieve files via the
 scp1 protocol. This is the protocol as referenced from the openssh scp program,
 and has only been tested with this implementation.

Bug#888218: RFA: sortedcontainers

[Sandro Tosi]

Package: wnpp
Severity: normal

Bug#888214: RFA: python-tabulate -- pretty-print tabular data in Python2

[Sandro Tosi]

Package: wnpp
Severity: normal

I request an adopter for the python-tabulate package.

The package description is:
 Pretty-print tabular data in Python, a library and a command-line utility.
 The main use cases of the library are:
 .
  * printing small tables without hassle: just one function call, formatting is
guided by the data itself
  * authoring tabular data for lightweight plain-text markup: multiple output
formats suitable for further editing or transformation
  * readable presentation of mixed textual and numeric data: smart column
alignment, configurable number formatting, alignment by a decimal point
 .
 This package installs the library for Python 2.

Bug#888212: RFA: python-zenoss -- module to work with the Zenoss JSON API

[Sandro Tosi]

Package: wnpp
Severity: normal

I request an adopter for the python-zenoss package.

The package description is:
 zenoss is a Python module that allows you to interact with a Zenoss
 installation thru its JSON APIs.
 .
 This package contains the Python 2 version of zenoss.

Bug#887214: nomad should depend on e2fsprogs explicitly

[Andreas Henriksson]

On Sun, Jan 14, 2018 at 08:08:14PM +0100, Helmut Grohne wrote:
> Package: nomad
[...]
> /usr/bin/nomad contains debugfs. According to file it is a ELF 64-bit LSB 
> executable, x86-64, version 1 (SYSV)
[...]

There doesn't seem to be any match for debugfs in the nomad source, so
I assume this comes from some golang library that's statically linked
into the binary (possibly golang-github-docker-docker-dev).

I'm not sure how or if such dependencies are supposed to automatically
propagate. Should the golang dev package inject dependencies into
misc:Depends or are this supposed to be manualy handled by the consuming
application (which I would think leads to massive amount of
bugs/mistakes as most manual things which doesn't give an obvious
failure when you get it wrong).

Would be great to get some feedback from the maintainer on this!

Regards,
Andreas Henriksson

Bug#735040: lintian: confusing tag name: debian-watch-may-check-gpg-signature

[Andreas Beckmann]

On 2018-01-23 23:28, Chris Lamb wrote:
> tags 735040 + pending
> thanks
> 
> Fixed in Git:
> 
>   
> https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=0cbebd4ba0b2a067383616e18981eeb9de5d7df2

Changelog (and commit) message says: "Rename bar to bar".
Probably caused by a global s/foo/bar/.


Andreas

Bug#735040: lintian: confusing tag name: debian-watch-may-check-gpg-signature

[Chris Lamb]

Hi Andreas,

> Probably caused by a global s/foo/bar/.

Hah, indeed - I did think of this, but I must have failed somehow
with my clipboard-fu. :)

Fixed in:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=2cf59d1b62b4df81c56a36f498544732214db96c


Regards,

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

Bug#874001: FTBFS with Java 9 due to -source/-target only

[Markus Koschany]

Control: tags -1 patch

Dear maintainer,

I've prepared a patch to fix the FTBFS with Java 9.

Please find attached the debdiff.

Regards,

Markus
diff -Nru sonic-0.2.0/debian/changelog sonic-0.2.0/debian/changelog
--- sonic-0.2.0/debian/changelog2017-10-22 17:52:54.0 +0200
+++ sonic-0.2.0/debian/changelog2018-01-24 00:19:34.0 +0100
@@ -1,3 +1,10 @@
+sonic (0.2.0-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with Java 9.
+
+ -- Markus Koschany   Wed, 24 Jan 2018 00:19:34 +0100
+
 sonic (0.2.0-5) unstable; urgency=medium
 
   [ Helmut Grohne ]
diff -Nru sonic-0.2.0/debian/rules sonic-0.2.0/debian/rules
--- sonic-0.2.0/debian/rules2016-10-23 12:00:54.0 +0200
+++ sonic-0.2.0/debian/rules2018-01-24 00:19:34.0 +0100
@@ -15,7 +15,7 @@
 
 sonic/Sonic.class: Sonic.java
[ -L sonic ] || ln -s . sonic
-   javac -source 1.5 -target 1.5 $<
+   javac -source 1.7 -target 1.7 $<
 
 sonic.jar: sonic/Sonic.class
jar -cf $@ $^


signature.asc
Description: OpenPGP digital signature

Bug#888209: [pkg-dhcp-devel] Bug#888209: isc-dhcp-client: hammers DHCP server if it cannot write lease file

[Axel Beckert]

Control: retitle -1 isc-dhcp-client: hammers DHCP server if it cannot write 
lease file (and might use up all available IP addresses in the LAN)
Control: severity -1 important

Hi Toni,

Toni Mueller wrote:
> I recently experienced a problem with dhclient issuing a ton of requests
> in rapid fire mode in an endless loop because the file system where it
> wanted to write its lease file, was mounted read-only. It got a new IP
> everytime and added them all to the interface.

Thanks for that bug report. Nice discovery.

I (not one of the isc-dhcp package maintainers, but lurking on their
list due to a general interest in DHCP) ran into that several times
now (with a single host using up all leases on my DHCP server!), but
only noticed it only due to no more leases being available, i.e. there
was nothing more left to debug.

So I assume it was caused by a temporarily full /var file system or
similar, which went away before I noticed that it also had these
hundreds of additional IPv4 addresses on my box as side effect.

Raising the severity to important as this might have a kind of DoS
effect on the local LAN (not the hammering but the using up of all
available IP addresses). ISC DHCP package maintainers: Feel free to
downgrade again if you disagree.

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

Bug#886508: ITP: paper-icon-theme

[Jeremy Bicha]

On Tue, Jan 23, 2018 at 6:11 PM, Omar Jair Purata Funes
 wrote:
> I re-uploaded a corrected version to mentors.debian.org though I cannot fix
> the
>
> debian-watch-may-check-gpg-signature

You can ignore that Lintian warning.

What about fixing and pushing to
https://salsa.debian.org/desktop-themes-team/paper-icon-theme ?

Thanks,
Jeremy Bicha

Bug#887249: fsarchiver should depend on e2fsprogs explicitly

[Andreas Henriksson]

On Sun, Jan 14, 2018 at 08:04:43PM +0100, Helmut Grohne wrote:
> Package: fsarchiver
[...]
> /usr/sbin/fsarchiver contains e2fsck, mke2fs and tune2fs. According to file 
> it is a ELF 64-bit LSB shared object, x86-64, version 1 (SYSV)
[...]

The commands are all used in the extfs_mkfs function:
https://sources.debian.org/src/fsarchiver/0.8.3-3/src/fs_ext2.c/#L145

Which in turn are called from the ext[234]_mkfs wrapper functions:
https://sources.debian.org/src/fsarchiver/0.8.3-3/src/fs_ext2.c/#L92

Those functions are hooked up at:
https://sources.debian.org/src/fsarchiver/0.8.3-3/src/filesys.c/#L49

Given that all non-ext* filesystems in that table are listed under
Suggests I would guess e2fsprogs should be added to Suggests.
(Or possibly promoted as ext being the favourite child to Recommends.)

Would be great to hear the maintainers view on this...

Regards,
Andreas Henriksson

Bug#887852: /dev/kvm is no longer accessible to local users

[Alexander Kurtz]

Hi!

I did some further digging in git and here's what I found:

In systemd 235, these two rules managed /dev/kvm:

  50-udev-default.rules.in:
KERNEL=="kvm", GROUP="kvm", MODE="@DEV_KVM_MODE@"

https://github.com/systemd/systemd/blob/v235/rules/50-udev-default.rules.in#L78

  70-uaccess.rules:
SUBSYSTEM=="misc", KERNEL=="kvm", TAG+="uaccess"
https://github.com/systemd/systemd/blob/v235/src/login/70-uaccess.rules#L49

Upstream commit b8fd3d82205f632ce001fade74fed287e1564a1a (part of PR
7112) removed the KVM related bits from the second file, but changed
the default value for @DEV_KVM_MODE@ from 0660 to 0666.

Unfortunately Debian has been removing the KVM related bits from the
first file for some time now, see

  
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/patches/debian/Avoid-requiring-a-kvm-system-group.patch

The result is, that in Debian, there is now no systemd-owned udev rule
managing /dev/kvm. This causes the regression that logind does no
longer grant access to /dev/kvm to local users.

Personally, I think that Debian should remove the patch mentioned
above, make kvm a static system group, and remove the udev rule from
QEMU since there *are* other users of /dev/kvm (e.g. kvmtool, which
doesn't ship a udev rule). Then, choose a value for the 'dev-kvm-mode'
meson build option of systemd. I like the upstream default, but there
is Debian bug #640328. But then again, this was in 2011.

So, ultimately this is a maintainer decision, I just wanted to warn you
that people might trip over this on stretch -> buster upgrades!

Best regards

Alexander Kurtz

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

Bug#888211: xserver-xorg-video-intel: Frequent hangs with kernel 4.14.13-1 and i915 chipset

[Chris Chiappa]

Package: xserver-xorg-video-intel
Version: 2:2.99.917+git20171229-1
Severity: normal

On Friday I did an upgrade and have been having frequent hangs since:

[Tue Jan 23 16:12:23 2018] i915 :00:02.0: Resetting rcs0 after gpu hang
[Tue Jan 23 16:12:26 2018] asynchronous wait on fence i915:Xorg[4666]/1:a36f8 
timed out
[Tue Jan 23 16:12:26 2018] asynchronous wait on fence i915:Xorg[4666]/1:a36f8 
timed out
[Tue Jan 23 16:12:31 2018] i915 :00:02.0: Resetting rcs0 after gpu hang
[Tue Jan 23 16:12:39 2018] i915 :00:02.0: Resetting rcs0 after gpu hang
[Tue Jan 23 16:12:51 2018] i915 :00:02.0: Resetting rcs0 after gpu hang
[Tue Jan 23 16:13:01 2018] i915 :00:02.0: Resetting rcs0 after gpu hang

After this, X eventually dies and I can restart it.  The upgrade
definitely moved to linux-image-4.14.0-3-amd64 (probably from
linux-image-4.14.0-1-amd64, but maybe earlier?) and might also have
upgraded me to 2:2.99.917+git20171229-1 .

I don't see any new bugs in the bug system which look like this, but
I'm not sure if this is the right package to be reporting against.
Google turns up random stuff like
https://bugs.archlinux.org/task/55629 and
https://unix.stackexchange.com/questions/401746/drm-i915-resetting-chip-after-gpu-hang
but they don't seem to correspond to the versions which have induced
problems for me.

-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 
[8086:1912] (rev 06)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.14.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.2.0 (Debian 7.2.0-19)) #1 SMP Debian 4.14.13-1 (2018-01-14)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 44951 Jan 23 16:18 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[342836.057] 
X.Org X Server 1.19.5
Release Date: 2017-10-12
[342836.057] X Protocol Version 11, Revision 0
[342836.057] Build Operating System: Linux 4.9.0-4-amd64 x86_64 Debian
[342836.057] Current Operating System: Linux cchiappa-lnx 4.14.0-3-amd64 #1 SMP 
Debian 4.14.13-1 (2018-01-14) x86_64
[342836.057] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.14.0-3-amd64 
root=/dev/mapper/ccora2-root ro quiet
[342836.057] Build Date: 16 October 2017  12:28:38PM
[342836.057] xorg-server 2:1.19.5-1 (https://www.debian.org/support) 
[342836.057] Current version of pixman: 0.34.0
[342836.057]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[342836.057] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[342836.057] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 23 16:13:00 
2018
[342836.063] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[342836.075] (==) No Layout section.  Using the first Screen section.
[342836.075] (==) No screen section available. Using defaults.
[342836.075] (**) |-->Screen "Default Screen Section" (0)
[342836.075] (**) |   |-->Monitor ""
[342836.075] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[342836.075] (==) Automatically adding devices
[342836.075] (==) Automatically enabling devices
[342836.075] (==) Automatically adding GPU devices
[342836.075] (==) Max clients allowed: 256, resource mask: 0x1f
[342836.086] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[342836.086]Entry deleted from font path.
[342836.099] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[342836.099] (==) ModulePath set to "/usr/lib/xorg/modules"
[342836.099] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[342836.099] (II) Loader magic: 0x55fe210f4de0
[342836.099] (II) Module ABI versions:
[342836.099]X.Org ANSI C Emulation: 0.4
[342836.099]X.Org Video Driver: 23.0
[342836.099]X.Org XInput driver : 24.1
[342836.099]X.Org Server Extension : 10.0
[342836.099] (++) using VT number 7

[342836.099] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[342836.099] (II) xfree86: Adding drm device 

Bug#846490: missing tar(5) manpage

[Jakub Wilk]

* Giacomo Catenazzi , 2016-12-01, 14:59:

SEE ALSO
tar(5)

But this manpage (and file) don't exist in this or in other packages.


This manpage is shipped by libarchive-dev:

  $ dpkg -L libarchive-dev | grep -F tar.5.
  /usr/share/man/man5/tar.5.gz

I recommend adding libarchive-dev to Suggest and the following text 
(shamelessly stolen from #662718) to the package description:


  The man page describing the tar(5) archive format can be
  found in the libarchive-dev package.

--
Jakub Wilk

Bug#888183: libc6: Breaks openvz virtuals again

[Aurelien Jarno]

On 2018-01-23 17:57, James Cloos wrote:
> > "AJ" == Aurelien Jarno  writes:
> 
> AJ> It's exactly what the message does. It stopped the upgrade and prevented
> AJ> libc6 to be unpacked. That way your system is still usable.
> 
> But that is NOT what the message does.  The other debs from the glibc
> source are already upgraded and now everything breaks.
> 
> The dialog has to occur before *any* of the debs from the glibc src are
> upgraded.

Do you have a list of other packages from the glibc src that are
upgraded before?

In any case it's not something we can control, the abort is done inside
the libc6 preinst, there is no way the libc6 package can do that
earlier.

Aurelien

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

Bug#735040: lintian: confusing tag name: debian-watch-may-check-gpg-signature

[Chris Lamb]

Mattia,

> It's not, for tag like this people would just put the tag name in the
> override file, which would work with whatever change you do to the
> context.

Of course; my point was that we have improved *other* tags. ie. there is
"prior art" here.


Regards,

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

Bug#888210: tar: please add Homepage field

[Jakub Wilk]

Source: tar
Version: 1.29b-2
Severity: wishlist

Please add:

  Homepage: https://www.gnu.org/software/tar/

to debian/control.

--
Jakub Wilk

Bug#887755: open-vm-tools-desktop: Debian Unstable per-session user-owned vmtoolsd segfaults afer upgrade to 2:10.2.0-1

[Bernd Zeimetz]

Hi Ron,

just uploaded -2 which should fix this issue, if not please reopen the bug.

(will take some hours until its built and on the mirrors).

Thanks for the bug report,

Bernd


On 01/19/2018 06:08 PM, Ron Lovell wrote:
> Package: open-vm-tools-desktop
> Version: 2:10.2.0-1
> Severity: important
> 
> Dear Maintainer,
> 
> After upgrade to open-vm-tools[-desktop] 2:10.2.0-1 in Sid, the
> per-session user-owned vmtoolsd process segfaults in libgdk while
> logging into a Wayland GNOME session. The problem does not occur
> for an Xorg GNOME session.
> 
> This problem appears to be identical to the known problem reported
> in Red Hat Bug 1526952 and (my) SUSE Bug 1073760. Note that in
> openSUSE Tumbleweed the problem occurred for open-vm-tools-desktop
> 10.1.15 as well as 10.2.0, so it might not simply be a bug introduced
> with your upgrade. Note that Fedora have released a workaround, and my
> understanding is that VMware are working on a permanent fix involving
> rework of the plugins to handle Wayland.
> 
> For an Xorg session:
> lovelld@ron5sid:~$ ps -ef | grep vmtoolsd
> root417  1  0 10:30 ?00:00:02 /usr/bin/vmtoolsd
> lovelld3442  1  0 10:41 tty2 00:00:02 /usr/bin/vmtoolsd -n vmusr 
> --blockFd 3
> lovelld4087   3847  0 11:04 pts/200:00:00 grep -d skip --color=auto 
> vmtoolsd
> 
> For a Wayland session, the process running as me (with the -n vmusr option) is
> not present, and the journal shows it segfaults in libgdk. See the Red Hat
> and SUSE bugs for further details, including stack traces.
> 
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.14.0-3-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages open-vm-tools-desktop depends on:
> ii  fuse 2.9.7-1
> ii  libatk1.0-0  2.26.1-2
> ii  libatkmm-1.6-1v5 2.24.2-3
> ii  libc62.26-4
> ii  libcairo-gobject21.15.8-3
> ii  libcairo21.15.8-3
> ii  libcairomm-1.0-1v5   1.12.2-2
> ii  libdrm2  2.4.89-1
> ii  libgcc1  1:7.2.0-19
> ii  libgdk-pixbuf2.0-0   2.36.11-1
> ii  libglib2.0-0 2.54.3-1
> ii  libglibmm-2.4-1v52.54.1-2
> ii  libgtk-3-0   3.22.26-2
> ii  libgtkmm-3.0-1v5 3.22.2-2
> ii  libice6  2:1.0.9-2
> ii  libpango-1.0-0   1.40.14-1
> ii  libpangocairo-1.0-0  1.40.14-1
> ii  libpangomm-1.4-1v5   2.40.1-4
> ii  libsigc++-2.0-0v52.10.0-1
> ii  libsm6   2:1.2.2-1+b3
> ii  libstdc++6   7.2.0-19
> ii  libudev1 236-3
> ii  libx11-6 2:1.6.4-3
> ii  libxext6 2:1.3.3-1+b2
> ii  libxi6   2:1.7.9-1
> ii  libxinerama1 2:1.1.3-1+b3
> ii  libxrandr2   2:1.5.1-1
> ii  libxrender1  1:0.9.10-1
> ii  libxtst6 2:1.2.3-1
> ii  open-vm-tools2:10.2.0-1
> 
> Versions of packages open-vm-tools-desktop recommends:
> ii  xauth   1:1.0.10-1
> pn  xserver-xorg-input-vmmouse  
> ii  xserver-xorg-video-vmware   1:13.2.1-1+b1
> 
> Versions of packages open-vm-tools-desktop suggests:
> ii  xdg-utils  1.1.2-1
> 
> -- no debconf information
> 

-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Bug#887028: uqm: FTBFS: arilouc.c:231:22: error: 'bye_angry_space' undeclared

[Gwyn Ciesla]

Excellent, thank you!


On 01/23/2018 02:29 PM, Michael Martin wrote:
> A 0.7.0-1 release was made last week to address this issue more
> systematically.
>
> On Jan 23, 2018 11:08 AM, "Gwyn Ciesla"  > wrote:
>
>
> On 01/23/2018 12:13 PM, Juhani Numminen wrote:
> > On Fri, 12 Jan 2018 17:56:13 +0100 Andreas Beckmann
> > wrote:
> >> Source: uqm
> >> Version: 0.6.2.dfsg-9.4
> >> Severity: serious
> >>
> >> Hi,
> >>
> >> uqm recently started to FTBFS in sid and buster:
> >>
> >> gcc -c  -o "obj/release/src/sc2code/comm/arilou/arilouc.c.o" -g
> -O2 -fdebug-prefix-map=/build/uqm-0.6.2.dfsg=.
> -specs=/usr/share/dpkg/no-pie-compile.specs
> -fstack-protector-strong -Wformat -Werror=format-security
> >> -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT
> -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -O3
> -DGFXMODULE_SDL -DHAVE_OPENGL  -DSOUNDMODULE_SDL 
>  -DNETPLAY=NETPLAY_FULL -DHAVE_JOYSTICK -DHAVE_ZIP=1  -DUSE_PLA
> >> TFORM_ACCEL -I "." -g -Wdate-time -D_FORTIFY_SOURCE=2 -I src -I
> src/sc2code -I src/sc2code/libs "src/sc2code/comm/arilou/arilouc.c"
> >> In file included from src/sc2code/comm/commall.h:22:0,
> >>                  from src/sc2code/comm/arilou/arilouc.c:19:
> >> src/sc2code/comm/arilou/arilouc.c: In function 'ExitConversation':
> >> src/sc2code/comm/arilou/arilouc.c:231:22: error:
> 'bye_angry_space' undeclared (first use in this function)
> >>   if (PLAYER_SAID (R, bye_angry_space))
> >> [...]
> > The declaration for bye_angry_space is in the adjacent
> uqm/comm/arilou/strings.h[1].
> > However, I think some other strings.h gets included instead.
> That's possibly because
> > some system header started including strings.h recently. My
> suggestion (based on a
> > similar issue[2]) is to rename the local header to some other name.
> >
> > [1]
> 
> https://sourceforge.net/p/sc2/uqm/ci/master/tree/sc2/src/uqm/comm/arilou/strings.h#l119
> 
> 
> > [2] https://github.com/markfasheh/ocfs2-tools/issues/17
> 
> >
> > This bug is in various bug trackers:
> >  * Upstream: https://bugs.uqm.stack.nl/show_bug.cgi?id=1212
> 
> >  * Debian: https://bugs.debian.org/887028
> >  * Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1525239
> 
> >
> >
> > Regards,
> > Juhani
> This works: the following bash allows uqm to build and run.
>
> #rename internal strings.h file to fix FTBFS.
> cd src/uqm/comm/
> for d in */ ; do
>     cd $d
>     mv strings.h ustrings.h
>     cd ..
> done
> find . -type f -name '*.c' | xargs sed -i s/strings.h/ustrings.h/g
> find . -type f -name '*.h' | xargs sed -i s/STRINGS/USTRINGS/g
>
> -G
>
> --
> http://cecinestpasunefromage.wordpress.com/
> 
> 
> in your fear, seek only peace
> in your fear, seek only love
>
> -d. bowie
>
>

-- 
http://cecinestpasunefromage.wordpress.com/

in your fear, seek only peace
in your fear, seek only love

-d. bowie



signature.asc
Description: OpenPGP digital signature

Bug#735040: lintian: confusing tag name: debian-watch-may-check-gpg-signature

[Mattia Rizzolo]

On Wed, Jan 24, 2018 at 04:19:40AM +0530, Chris Lamb wrote:
> We've done it before, including adding additional context data to overrides
> (which is /almost/ the same as renaming it!).

It's not, for tag like this people would just put the tag name in the
override file, which would work with whatever change you do to the
context.

> At some point one just has to rename it to avoid future blah. Note that it
> is a pedantic tag which changes the calculation a little for me.

Right, but this is one of those "noisy" tags that most of the time the
maintainer can do nothing about it, I believe I also overrode it in some
of my packages.

Please apply the following:

diff --git a/data/override/renamed-tags b/data/override/renamed-tags
index 8ee57ef2d..8d3460958 100644
--- a/data/override/renamed-tags
+++ b/data/override/renamed-tags
@@ -1,6 +1,7 @@
 # list of renamed tag old name => new name. Please alpha sort by old name
 dep5-file-paragraph-reference-header-paragraph => 
dep5-file-paragraph-references-header-paragraph
 debian-changelog-has-wrong-weekday => debian-changelog-has-wrong-day-of-week
+debian-watch-may-check-gpg-signature => 
debian-watch-does-not-check-gpg-signature
 package-install-apt-preferences => package-installs-apt-preferences
 package-install-apt-sources => package-installs-apt-sources
 package-install-ieee-data => package-installs-ieee-data


(and if in the future you rename tags with many overrides in the
archive, please add them here).

-- 
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#735040: lintian: confusing tag name: debian-watch-may-check-gpg-signature

[Chris Lamb]

Mattia,

> Please apply the following:

Done!


Regards,

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

Bug#888001: Bug#762261: lintian: introduce a inexistent-file-in-dep5-copyright rather confusing

[Chris Lamb]

Hi Mattia,

> Not sure where you are heading here…  As I suspect you know (☺) I'm not
> interested in naming things.

Right, nor am I, hence the many caveats I added that my names were only
about clarifying what you are after here

> To make it simple: this last paragraph should eming **only one tag**
> saying the file doesn't match any file from the source package.

Thanks.


Regards,

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

Bug#887716: [pkg-netfilter-team] Bug#887716: not necessarily not running

[Michael Biebl]

Control: tags -1 + moreinfo unreproducible

[please always CC the maintainer if you reassign a bug report]

On Mon, 22 Jan 2018 13:31:06 +0100 Arturo Borrero Gonzalez
 wrote:
> On Fri, 19 Jan 2018 21:58:11 +0800 =?utf-8?B?56mN5Li55bC8?= Dan
> Jacobson  wrote:
> > I'm just saying
> > > nftables.service is a disabled or a static unit not running, not starting 
> > > it.
> > perhaps could be better written
> > > nftables.service is disabled. Not starting it.
> > or
> > > nftables.service is not enabled, so not starting it.
> > or
> > > nftables.service is not enabled, so not starting it.
> > > If currently running, it was started by other means.
> >
> >
> 
> That message is produced by systemd, not by nftables. Nothing that
> could be fixed from the src:nftables point of view.

Are you sure this message is coming from systemd?

How exactly did you disable the service? If I install the nftables
package I get no such message.
If you want us to be able to reproduce the issue, you need to provide
more details.

-- 
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#888183: libc6: Breaks openvz virtuals again

[James Cloos]

> "AJ" == Aurelien Jarno  writes:

AJ> It's exactly what the message does. It stopped the upgrade and prevented
AJ> libc6 to be unpacked. That way your system is still usable.

But that is NOT what the message does.  The other debs from the glibc
source are already upgraded and now everything breaks.

The dialog has to occur before *any* of the debs from the glibc src are
upgraded.

-JimC
-- 
James Cloos  OpenPGP: 0x997A9F17ED7DAEA6

Bug#888001: Bug#762261: lintian: introduce a inexistent-file-in-dep5-copyright rather confusing

[Mattia Rizzolo]

On Wed, Jan 24, 2018 at 04:16:38AM +0530, Chris Lamb wrote:
> > >  Files: specific-name
> > >  License: GPL-3
> > 
> > So this paragraph should already (please check if you have simple way
> > to!) cause tag unused-file-paragraph-in-dep5-copyright to appear.
> 
> To 100% clarify; this is because whilst the file exists in this example,
> it should be "covered" by the "*" in "Files: *" below it?

Not sure what you mean by "covered", but to me it's because the next
paragarph overrides this one.

> > >  Files: *
> > >  License: GPL-3
> > >
> > >  Files: file-does-not-exist
> > >  License: GPL-3
> > 
> > This one should trigger the new tag I'm proposing.
> > OTOH I think unused-file-paragraph-in-dep5-copyright is also emitted for
> > this one, so it should stop emitting
> > unused-file-paragraph-in-dep5-copyright and move to
> > inexistent-file-in-dep5-copyright instead.
> 
> I hate name arguments (!) but I think it's partly the names that are
> making this harder than it "should" to understand. How about (at least
> for now) "entry-does-not-match-any-files-in-package" for this last one
> and (again, just for this discussion) "entry-covered-by-another-entry".

Not sure where you are heading here…  As I suspect you know (☺) I'm not
interested in naming things.
To make it simple: this last paragraph should eming **only one tag**
saying the file doesn't match any file from the source package.


> Terrible names, I know, but just to make the clarifications easier!

"entry-coverd-by-another-entry" is probably wrong on many level,
starting by anything else after the 'Files: *', as they would all
"duplicate" a file already covered by the * !! ;)

-- 
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#888001: Bug#762261: lintian: introduce a inexistent-file-in-dep5-copyright rather confusing

[Chris Lamb]

Hi Mattia,


> >  Files: specific-name
> >  License: GPL-3
> 
> So this paragraph should already (please check if you have simple way
> to!) cause tag unused-file-paragraph-in-dep5-copyright to appear.

To 100% clarify; this is because whilst the file exists in this example,
it should be "covered" by the "*" in "Files: *" below it?

> >  Files: *
> >  License: GPL-3
> >
> >  Files: file-does-not-exist
> >  License: GPL-3
> 
> This one should trigger the new tag I'm proposing.
> OTOH I think unused-file-paragraph-in-dep5-copyright is also emitted for
> this one, so it should stop emitting
> unused-file-paragraph-in-dep5-copyright and move to
> inexistent-file-in-dep5-copyright instead.

I hate name arguments (!) but I think it's partly the names that are
making this harder than it "should" to understand. How about (at least
for now) "entry-does-not-match-any-files-in-package" for this last one
and (again, just for this discussion) "entry-covered-by-another-entry".

Terrible names, I know, but just to make the clarifications easier!


Regards,

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

Bug#887852: /dev/kvm is no longer accessible to local users

[Alexander Kurtz]

On Mon, 2018-01-22 at 17:50 +0100, Michael Biebl wrote:
> On Sat, 20 Jan 2018 18:21:33 +0100 Alexander Kurtz  wrote:
> > Package: systemd
> > Version: 236-3
> > 
> > Hi!
> > 
> > Until recently, /dev/kvm was made accessible to local users by this
> > line in /lib/udev/rules.d/70-uaccess.rules:
> > 
> > # KVM
> > SUBSYSTEM=="misc", KERNEL=="kvm", TAG+="uaccess"
> > 
> > However, as of systemd 236, the above rule seems to be gone. After
> > reading up a bit on systemd's upstream and Debian bug tracker, I'm even
> > more confused than before: Which package is supposed to manage
> > permissions on /dev/kvm in Debian? Which package is supposed to create
> > the "kvm" group? Is the missing access for local users intentional?
> 
> Isn't this setup by the qemu package in
> /lib/udev/rules.d/60-qemu-system-common.rules:KERNEL=="kvm",
> GROUP="kvm", MODE="0660"

Yes, but only partially: This is the full rule shipped by QEMU:

$ cat /lib/udev/rules.d/60-qemu-system-common.rules 
KERNEL=="kvm", GROUP="kvm", MODE="0660"
$ 

This rule only manages the basic group ownership and permissions. It
does not add the "uaccess" tag, which is (presumably) used by logind to
dynamically grant local users access via ACLs. This used to work before
with systemd <236 and doesn't work now. Is this intentional?

Best regards

Alexander Kurtz

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

Bug#735040: lintian: confusing tag name: debian-watch-may-check-gpg-signature

[Chris Lamb]

Hi Mattia,

> There are 300something packages overriding this tag.  Renaming the tag
> would cause all those overrides to be for naught, so please don't do it.

We've done it before, including adding additional context data to overrides
(which is /almost/ the same as renaming it!).

At some point one just has to rename it to avoid future blah. Note that it
is a pedantic tag which changes the calculation a little for me.


Regards,

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

Bug#735040: lintian: confusing tag name: debian-watch-may-check-gpg-signature

[Mattia Rizzolo]

On Wed, Jan 24, 2018 at 03:58:40AM +0530, Chris Lamb wrote:
> tags 735040 + pending
> thanks
> 
> Fixed in Git:
> 
>   
> https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=0cbebd4ba0b2a067383616e18981eeb9de5d7df2

There are 300something packages overriding this tag.  Renaming the tag
would cause all those overrides to be for naught, so please don't do it.

ISTR there was a facility in lintian somewhere (was it ever merged into
master?) to support for renamed tags, if it does exist, that would cover
my concerns.

-- 
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#888205: openssh-client: ssh-keygen -t rsa1 fails very late

[Colin Watson]

On Tue, Jan 23, 2018 at 09:52:42PM +, Ian Jackson wrote:
> $ ssh-keygen -t rsa1 -b 2048 -f t
> Generating public/private rsa1 key pair.
> t already exists.
> Overwrite (y/n)? y
> Enter passphrase (empty for no passphrase): 
> Enter same passphrase again: 
> Saving key "t" failed: unknown or unsupported key type
> $
> 
> I guess this is a consequence of dropping SSH v1 protocol support.
> 
> This is inconvenient for me as I have a program which uses RSA, relies
> on an external key generator, and understands the ssh v1 key format.
> So ideally I would like this facility to be restored.

You'll need to install openssh-client-ssh1 and use ssh-keygen1, which
I've preserved for this kind of purpose.  I'm afraid that the
probability of this facility being reintroduced in modern OpenSSH
approaches zero.

> Failing that, I would like ssh-keygen to say "never heard of that key
> type" rather than going ahead and generating a perfectly good RSA key
> before failing to marshal it up into a key file.

I agree that this would be a good idea.  If you have time then it would
speed things up if you could file this upstream at bugzilla.mindrot.org.

-- 
Colin Watson   [cjwat...@debian.org]

Bug#888001: Bug#762261: lintian: introduce a inexistent-file-in-dep5-copyright rather confusing

[Mattia Rizzolo]

On Wed, Jan 24, 2018 at 03:48:31AM +0530, Chris Lamb wrote:
> What do we want to end up with? Let's use this example
> 
>  Files: specific-name
>  License: GPL-3

So this paragraph should already (please check if you have simple way
to!) cause tag unused-file-paragraph-in-dep5-copyright to appear.  I
believe what you did for #762261 to cover this case well enough.

>  Files: *
>  License: GPL-3
> 
>  Files: file-does-not-exist
>  License: GPL-3

This one should trigger the new tag I'm proposing.
OTOH I think unused-file-paragraph-in-dep5-copyright is also emitted for
this one, so it should stop emitting
unused-file-paragraph-in-dep5-copyright and move to
inexistent-file-in-dep5-copyright instead.

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

Bug#888209: isc-dhcp-client: hammers DHCP server if it cannot write lease file

[Toni Mueller]

Package: isc-dhcp-client
Version: 4.3.5-3+b2
Severity: normal


Hi,

I recently experienced a problem with dhclient issuing a ton of requests
in rapid fire mode in an endless loop because the file system where it
wanted to write its lease file, was mounted read-only. It got a new IP
everytime and added them all to the interface. It would be nice if
dhclient could just be content with having one IP address, and then stop
asking until the lease expires, regardless of the state of the file
system, instead of issuing dozens of DHCP requests per second.

I experien


Cheers,
--Toni++



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

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

Versions of packages isc-dhcp-client depends on:
ii  debianutils   4.8.4
ii  iproute2  4.14.1-1
ii  libc6 2.26-4
ii  libdns-export169  1:9.11.2+dfsg-5
ii  libisc-export166  1:9.11.2+dfsg-5

Versions of packages isc-dhcp-client recommends:
ii  isc-dhcp-common  4.3.5-3+b2

Versions of packages isc-dhcp-client suggests:
pn  avahi-autoipd 
pn  isc-dhcp-client-ddns  
pn  resolvconf

-- no debconf information

Bug#867731: RFS: smart-mode-line/2.10.1-1 [ITP]

[Nicholas D Steeves]

Hi Juhani,

On Tue, Jan 23, 2018 at 09:10:50AM +0200, Juhani Numminen wrote:
> Juhani Numminen kirjoitti 22.01.2018 klo 23:24:
> > Nicholas D Steeves kirjoitti 22.01.2018 klo 21:10:
> > 
> >> I use this package every day and have updated the package several
> >> times in the last year.  It's currently at Policy 4.1.3 and dh/compat
> >> level 11.  Please consider sponsoring :-)
> > 
> > The current git repository is hosted on Alioth, which will be shut down and 
> > replaced
> > by Salsa[1]. You should probably migrate the repository there.
> > 
> > It seems that there isn't a Salsa team corresponding to pkg-emacsen yet, so 
> > I suggest you
> > coordinate with the pkg-emacsen folks to create one.
> 
> Oh, now I see that there exists such a team. :) (But apparently searching for 
> emacsen-team
> on the search bar on the top right corner on the Salsa front page won't find 
> it. Maybe that
> only searches for projects.)
> 
> I still think you should update your Vcs-Git and Vcs-Browser for the new 
> repository.
> https://salsa.debian.org/emacsen-team/smart-mode-line
> 
> Juhani

Done!  I decided to target experimental for the initial upload in
light of upstream issues with emacs ≥ 26, and also because I've now
packaged a snapshot of upstream's master, because I noticed my quilt
patch to remove the executable bit triggers a warning when using dget.

Oh, I also asked the team about adding the old team name's to
emacsen-team's description to improve discoverability :-)

Thank you,
Nicholas


signature.asc
Description: PGP signature

Bug#888018: Bug#888019/888018: jessie-pu/stretch-pu: package libdatetime-timezone-perl/*+2018b

[gregor herrmann]

On Mon, 22 Jan 2018 18:27:51 +0100, gregor herrmann wrote:

> Changes in the olson db 2018b, copied from upstream:

And today we had the release of 2018c.

What I see from the announcement [0], the prior discussions, and the
diff (after "perlifying" the code), this just reverts the changes for
Europe/Dublin, as some software doesn't like negative DST offsets.

From what I see this is not relevant for libdatetime-timezone-perl;
not only did the tests pass with the +2018b versions, I also added
additional tests with Europe/Dublin now locally, and they also passed
without an issue.

So I guess we can go ahead with the +2018b versions for jessie and
stretch and save another patching trip.


Cheers,
gregor

[0] https://mm.icann.org/pipermail/tz-announce/2018-January/48.html

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Joe Cocker: Put Out The Lights


signature.asc
Description: Digital Signature

Bug#735040: lintian: confusing tag name: debian-watch-may-check-gpg-signature

[Chris Lamb]

tags 735040 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=0cbebd4ba0b2a067383616e18981eeb9de5d7df2


Regards,

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